--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/CONTENTS	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,75 @@
+/* ========================================================================
+ * Copyright 1988-2006 University of Washington
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * 
+ * ========================================================================
+ */
+
+			  TOOLKIT DIRECTORY CONTENTS
+
+Documentation:
+ . CONTENTS		this file
+ . LICENSE.txt		software license
+ . NOTICE		copyright notice
+ . README		read this file first
+ . SUPPORT		where to go to ask questions and/or report bugs
+ . docs/BUILD		build and installation instructions
+ . docs/CONFIG		detailed configuration notes
+ . docs/FAQ.html	frequently asked questions and answers
+ . docs/FAQ.txt		text version of FAQ.HTML
+ . docs/RELNOTES	release notes
+ . docs/SSLBUILD	build and installation instructions using SSL
+ . docs/Y2K		information relating to Y2K issues
+ . docs/bugs.txt	known bugs and deficiencies in this software
+ . docs/calendar.txt	information relating to the calendar
+ . docs/commndmt.txt	"ten commandments" on how to write a good IMAP client
+ . docs/draft/		Internet protocol documentation drafts
+ . docs/drivers.txt	how various mailbox format drivers interact, and
+			 comparable features and performance
+ . docs/formats.txt	mailbox formats
+ . docs/internal.txt	programming interfaces
+ . docs/locking.txt	how file locking works
+ . docs/md5.txt		CRAM-MD5 authentication setup instructions
+ . docs/mixfmt.txt	specification of new mix format
+ . docs/naming.txt	mailbox naming conventions
+ . docs/rfc/		Internet protocol documentation
+
+Sources:
+ . Makefile		master makefile for UNIX
+ . makefile.nt		master makefile for NT/Win32
+ . makefile.ntk		master makefile for NT/Win32 using Kerberos V
+ . makefile.os2		master makefile for OS/2
+ . makefile.w2k		master makefile for Windows 2000
+ . makefile.wce		master makefile for Windows CE
+ . src/ansilib		pre-processed ANSI library routines
+ . src/c-client		pre-processed c-client sources
+ . src/charset		pre-processed character set conversion tables
+ . src/dmail		pre-processed user mail delivery sources
+ . src/ipopd		pre-processed POP2/POP3 daemon sources
+ . src/imapd		pre-processed IMAP4rev1 daemon sources
+ . src/mailutil		pre-processed mailbox utility sources
+ . src/mlock		pre-processed mailbox locking sources
+ . src/mtest		pre-processed c-client testbed sources
+ . src/osdep/amiga	pre-processed Amiga-specific sources
+ . src/osdep/dos	pre-processed DOS-specific sources
+ . src/osdep/mac	pre-processed Mac-specific sources
+ . src/osdep/nt		pre-processed NT-specific sources
+ . src/osdep/os2	pre-processed OS/2-specific sources (incomplete)
+ . src/osdep/tops-20	pre-processed TOPS-20 specific sources
+ . src/osdep/unix	pre-processed UNIX-specific sources
+ . src/osdep/vms	pre-processed VAX/VMS specific sources
+ . src/osdep/wce	pre-processed Windows CE-specific sources (incomplete)
+ . src/tmail		pre-processed system mail delivery sources
+ . tools		internal tools needed as part of the build process
+
+Directories created at build time on UNIX and NT/Win32:
+ . c-client		post-processed c-client sources and binary
+ . ipopd		post-processed POP2/POP3 daemon sources and binaries
+ . imapd		post-processed IMAP4rev1 daemon sources and binaries
+ . mtest		post-processed c-client testbed sources and binaries

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/LICENSE.txt	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions. 
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below). 
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Makefile	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,736 @@
+# ========================================================================
+# Copyright 1988-2008 University of Washington
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# 
+# ========================================================================
+
+# Program:	IMAP Toolkit Makefile
+#
+# Author:	Mark Crispin
+#		UW Technology
+#		Seattle, WA  98195
+#		Internet: MRC@Washington.EDU
+#
+# Date:		7 December 1989
+# Last Edited:	12 May 2008
+
+
+# Normal command to build IMAP toolkit:
+#  make <port> [EXTRAAUTHENTICATORS=xxx] [EXTRADRIVERS=xxx] [EXTRACFLAGS=xxx]
+#	       [PASSWDTYPE=xxx] [SSLTYPE=xxx] [IP=n]
+
+
+# Port name.  These refer to the *standard* compiler on the given system.
+# This means, for example, that the hpx port is for HP's compiler and not for
+# a non-standard compiler such as gcc.
+#
+# If you are using gcc and it is not the standard compiler on your system, try
+# using an ANSI port that is close to what you have.  For example, if your
+# system is SVR4ish, try a32 or lnx; if it's more BSDish, try nxt, mct, or bsi.
+#
+# The following ports are bundled:
+# a32	AIX 3.2 for RS/6000
+# a41	AIX 4.1 for RS/6000
+# aix	AIX/370 (not RS/6000!!)
+# ami	AmigaDOS
+# am2	AmigaDOS with a 68020+
+# ama	AmigaDOS using AS225R2
+# amn	AmigaDOS with a 680x0 using "new" socket library
+# aos	AOS for RT
+# art	AIX 2.2.1 for RT
+# asv	Altos SVR4
+# aux	A/UX
+# bs3	BSD/i386 3.0 and higher
+# bsd	generic BSD 4.3 (as in ancient 1980s version)
+# bsf	FreeBSD
+# bsi	BSD/i386
+# bso	OpenBSD (yes, yet another one...)
+# cvx	Convex
+# cyg	Cygwin
+# d-g	Data General DG/UX prior to 5.4 (d41 port no longer exists)
+# d54	Data General DG/UX 5.4
+# do4	Apollo Domain/OS sr10.4
+# dpx	Bull DPX/2 B.O.S.
+# drs	ICL DRS/NX
+# dyn	Dynix
+# epx	EP/IX
+# ga4	GCC AIX 4.x for RS/6000
+# gas	GCC Altos SVR4
+# gcs	GCC Solaris with Blastwave Community Open Source Software
+# gh9   GCC HP-UX 9.x
+# ghp	GCC HP-UX 10.x
+# ghs	GCC HP-UX 10.x with Trusted Computer Base
+# go5	GCC 2.7.1 (95q4 from Skunkware _not_ 98q2!) SCO Open Server 5.0.x
+# gsc	GCC Santa Cruz Operation
+# gsg	GCC SGI
+# gso	GCC Solaris
+# gsu	GCC SUN-OS
+# gul	GCC RISC Ultrix (DEC-5000)
+# h11	HP-UX 11i
+# hpp	HP-UX 9.x (see gh9)
+# hpx	HP-UX 10.x (see ghp, ghs, hxd, and shp)
+# hxd	HP-UX 10.x with DCE security (see shp)
+# isc	Interactive Systems
+# ldb	Debian Linux
+# lfd	Fedora Core 4
+# ln8	Linux for Nokia N800
+# lnx	Linux with traditional passwords and crypt() in the C library
+#	 (see lnp, sl4, sl5, and slx)
+# lnp	Linux with Pluggable Authentication Modules (PAM)
+# lmd	Mandrake Linux
+# lr5	RedHat Enterprise 5 and later (same as lfd)
+# lrh	RedHat Linux 7.2 and later
+# lsu	SuSE Linux (same as lrh)
+# lyn	LynxOS
+# mct	MachTen
+# mnt	Atari ST Mint (not MacMint)
+# neb	NetBSD
+# nec	NEC UX
+# nto	QNX Neutrine RTP
+# nxt	NEXTSTEP
+# nx3	NEXTSTEP 3.x
+# osf	OSF/1 (see sos, os4)
+# os4	OSF/1 (Digital UNIX) 4
+# osi	Apple iPhone and iPod Touch
+# osx	Mac OS X
+# oxp	Mac OS X with Pluggable Authentication Modules (PAM)
+# ptx	PTX
+# pyr	Pyramid
+# qnx	QNX 4
+# s40	SUN-OS 4.0 (*not* Solaris)
+# sc5	SCO Open Server 5.0.x (see go5)
+# sco	Santa Cruz Operation (see sc5, go5)
+# shp	HP-UX with Trusted Computer Base
+# sgi	Silicon Graphics IRIX
+# sg6	Silicon Graphics IRIX 6.5
+# sl4	Linux using -lshadow to get the crypt() function
+# sl5	Linux with shadow passwords, no extra libraries
+# slx	Linux using -lcrypt to get the crypt() function
+# snx	Siemens Nixdorf SININX or Reliant UNIX
+# soc	Solaris with /opt/SUNWspro/bin/cc
+# sol	Solaris (won't work unless "ucbcc" works -- use gso instead)
+# sos	OSF/1 with SecureWare
+# ssn	SUN-OS with shadow password security
+# sua	Windows Vista (Enterprise or Ultima) Subsystem for Unix Applications
+# sun	SUN-OS 4.1 or better (*not* Solaris) (see ssn)
+# sv2	SVR2 on AT&T PC-7300 (incomplete port)
+# sv4	generic SVR4
+# ult	RISC Ultrix (DEC-5000)
+# uw2	UnixWare SVR4.2
+# vul	VAX Ultrix
+# vu2	VAX Ultrix 2.3 (e.g. for VAXstation-2000 or similar old version)
+
+
+# Extra authenticators (e.g. OTP, Kerberos, etc.).  Adds linkage for
+# auth_xxx.c and executes Makefile.xxx, where xxx is the name of the
+# authenticator.  Some authenticators are only available from third parties.
+#
+# The following extra authenticators are bundled:
+# gss	Kerberos V
+
+EXTRAAUTHENTICATORS=
+
+
+# Additional mailbox drivers.  Add linkage for xxxdriver.  Some drivers are
+# only available from third parties.
+#
+# The following extra drivers are bundled:
+# mbox	if file "mbox" exists on the home directory, automatically moves mail
+#	 from the spool directory to "mbox" and uses "mbox" as INBOX.
+
+EXTRADRIVERS=mbox
+
+
+# Plaintext password type.  Defines how plaintext password authentication is
+# done on this system.
+#
+# The following plaintext login types are bundled:
+# afs	AFS authentication database
+# dce	DCE authentication database
+# gss	Kerberos V
+# nul	plaintext authentication never permitted
+# pam	PAM authentication (note: for Linux, you should use the "lnp" port
+#	 instead of setting this...also, you may have to modify PAMLDFLAGS
+#	 in the imap-[]/src/osdep/unix/Makefile
+# pmb	PAM authentication for broken implementations such as Solaris.
+#	 you may have to modify PAMLDFLAGS
+# std	system standard (typically passwd file), determined by port
+# two	try alternative (defined by CHECKPWALT), then std
+
+PASSWDTYPE=std
+
+
+# SSL type.  Defines whether or not SSL support is on this system
+#
+# The following SSL types are bundled:
+# none	no SSL support
+# unix	SSL support using OpenSSL
+# nopwd	SSL support using OpenSSL, and plaintext authentication permitted only
+#	in SSL/TLS sessions
+# sco	link SSL before other libraries (for SCO systems)
+# unix.nopwd	same as nopwd
+# sco.nopwd	same as nopwd, plaintext authentication in SSL/TLS only
+#
+# SSLTYPE=nopwd is now the default as required by RFC 3501
+
+SSLTYPE=nopwd
+
+
+# IP protocol version
+#
+# The following IP protocol versions are defined:
+# o	IPv4 support, no DNS (truly ancient systems)
+# 4	(default) IPv4 support only
+# 6	IPv6 and IPv4 support
+
+IP=4
+IP6=6
+
+
+# The following extra compilation flags are defined.  None of these flags are
+# recommended.  If you use these, include them in the EXTRACFLAGS.
+#
+# -DDISABLE_POP_PROXY
+#	By default, the ipop[23]d servers offer POP->IMAP proxy access,
+#	which allow a POP client to access mail on an IMAP server by using the
+#	POP server as a go-between.  Setting this option disables this
+#	facility.
+#
+# -DOLDFILESUFFIX=\"xxx\"
+#	Change the default suffix appended to the backup .newsrc file from
+#	"old".
+#
+# -DSTRICT_RFC822_TIMEZONES
+#	Disable recognition of the non-standard UTC (0000), MET (+0100),
+#	EET (+0200), JST (+0900), ADT (-0300), AST (-0400), YDT (-0800),
+#	YST (-0900), and HST (-1000) symbolic timezones.
+#
+# -DBRITISH_SUMMER_TIME
+#	Enables recognition of non-standard symbolic timezone BST as +0100.
+#
+# -DBERING_STANDARD_TIME
+#	Enables recognition of non-standard symbolic timezone BST as -1100.
+#
+# -DNEWFOUNDLAND_STANDARD_TIME
+#	Enables recognition of non-standard symbolic timezone NST as -0330.
+#
+# -DNOME_STANDARD_TIME
+#	Enables recognition of non-standard symbolic timezone NST as -1100.
+#
+# -DSAMOA_STANDARD_TIME
+#	Enables recognition of non-standard symbolic timezone SST as -1100.
+#				
+# -DY4KBUGFIX
+#	Turn on the Y4K bugfix (yes, that's year 4000).  It isn't well-known,
+#	but century years evenly divisible by 4000 are *not* leap years in the
+#	Gregorian calendar.  A lot of "Y2K compilant" software does not know
+#	about this rule.  Remember to turn this on sometime in the next 2000
+#	years.
+#
+# -DUSEORTHODOXCALENDAR
+#	Use the more accurate Eastern Orthodox calendar instead of the
+#	Gregorian calendar.  The century years which are leap years happen
+#	at alternating 400 and 500 year intervals without shifts every 4000
+#	years.  The Orthodox and Gregorian calendars diverge by 1 day for
+#	gradually-increasing intervals, starting at 2800-2900, and becoming
+#	permanent at 48,300.
+#
+# -DUSEJULIANCALENDAR
+#	Use the less accurate Julian calendar instead of the Gregorian
+#	calendar.  Leap years are every 4 years, including century years.
+#	My apologies to those in the English-speaking world who object to
+#	the reform of September 2, 1752 -> September 14, 1752, since this
+#	code still uses January 1 (which Julius Ceasar decreed as the start
+#	of the year, which since 153 BCE was the day that Roman consuls
+#	took office), rather than the traditional March 25 used by the
+#	British.  As of 2005, the Julian calendar and the Gregorian calendar
+#	diverge by 15 days.
+
+EXTRACFLAGS=
+
+
+# Extra linker flags (additional/alternative libraries, etc.)
+
+EXTRALDFLAGS=
+
+
+# Special make flags (e.g. to override make environment variables)
+
+EXTRASPECIALS=
+SPECIALS=
+
+
+# Normal commands
+
+CAT=cat
+CD=cd
+LN=ln -s
+MAKE=make
+MKDIR=mkdir
+BUILDTYPE=rebuild
+RM=rm -rf
+SH=sh
+SYSTEM=unix
+TOOLS=tools
+TOUCH=touch
+
+
+# Primary build command
+
+BUILD=$(MAKE) build EXTRACFLAGS='$(EXTRACFLAGS)'\
+ EXTRALDFLAGS='$(EXTRALDFLAGS)'\
+ EXTRADRIVERS='$(EXTRADRIVERS)'\
+ EXTRAAUTHENTICATORS='$(EXTRAAUTHENTICATORS)'\
+ PASSWDTYPE=$(PASSWDTYPE) SSLTYPE=$(SSLTYPE) IP=$(IP)\
+ EXTRASPECIALS='$(EXTRASPECIALS)'
+
+
+# Make the IMAP Toolkit
+
+all:	c-client SPECIALS rebuild bundled
+
+c-client:
+	@echo Not processed yet.  In a first-time build, you must specify
+	@echo the system type so that the sources are properly processed.
+	@false
+
+
+SPECIALS:
+	echo $(SPECIALS) > SPECIALS
+
+# Note on SCO you may have to set LN to "ln".
+
+a32 a41 aix bs3 bsi d-g d54 do4 drs epx ga4 gas gh9 ghp ghs go5 gsc gsg gso gul h11 hpp hpx lnp lyn mct mnt nec nto nxt nx3 osf os4 ptx qnx sc5 sco sgi sg6 shp sl4 sl5 slx snx soc sol sos uw2: an
+	$(BUILD) BUILDTYPE=$@
+
+# If you use sv4, you may find that it works to move it to use the an process.
+# If so, you probably will want to delete the "-Dconst=" from the sv4 CFLAGS in
+# the c-client Makefile.
+
+aos art asv aux bsd cvx dpx dyn isc pyr sv4 ult vul vu2: ua
+	$(BUILD) BUILDTYPE=$@
+
+
+# Knotheads moved Kerberos and SSL locations on these platforms
+
+# Paul Vixie claims that all FreeBSD versions have working IPv6
+
+bsf:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=$@ IP=$(IP6) \
+	PASSWDTYPE=pam \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib PAMLDFLAGS=-lpam"
+
+# I assume that Theo did the right thing for IPv6.  OpenBSD does not have PAM.
+
+bso:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=$@ IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/etc/ssl SSLKEYS=/etc/ssl/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib"
+
+# Info from Joel Reicher about NetBSD SSL paths.  I assume it has PAM because pam is in NetBSD sources...
+
+neb:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=$@ IP=$(IP6) \
+	PASSWDTYPE=pam \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/etc/openssl/certs SSLKEYS=/etc/openssl/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib PAMLDFLAGS=-lpam"
+
+cyg:	an
+	$(BUILD) BUILDTYPE=cyg \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/usr/ssl/certs SSLKEYS=/usr/ssl/certs"
+
+gcs:	an
+	$(BUILD) BUILDTYPE=gso \
+	SPECIALS="SSLINCLUDE=/opt/csw/include/openssl SSLLIB=/opt/csw/lib SSLCERTS=/opt/csw/ssl/certs SSLKEYS=/opt/csw/ssl/certs"
+
+ldb:	an
+	$(BUILD) BUILDTYPE=lnp IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib MAILSPOOL=/var/mail"
+
+lfd:	an
+	$(BUILD) BUILDTYPE=lnp IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/etc/pki/tls/certs SSLKEYS=/etc/pki/tls/private GSSDIR=/usr/kerberos"
+
+ln8:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=slx IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/usr/lib/ssl/certs MAILSPOOL=/var/mail"
+
+
+# RHE5 does not have the IPv6 bug
+
+lr5:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=lnp IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/etc/pki/tls/certs SSLKEYS=/etc/pki/tls/private GSSDIR=/usr/kerberos"
+
+lmd:	an
+	$(BUILD) BUILDTYPE=lnp IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/usr/lib/ssl/certs SSLKEYS=/usr/lib/ssl/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib"
+
+# RHE3 definitely has the IPv6 bug
+
+lrh:	lrhok an
+	$(BUILD) BUILDTYPE=lnp IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/usr/share/ssl/certs SSLKEYS=/usr/share/ssl/private GSSDIR=/usr/kerberos"
+
+lrhok:
+	@$(SH) -c '(test ! -d /etc/pki/tls ) || make lrhwarn'
+	@$(TOUCH) lrhok
+
+lrhwarn:
+	@echo You are building for OLD versions of RedHat Linux.  This build
+	@echo is NOT suitable for RedHat Enterprise 5, which stores SSL/TLS
+	@echo certificates and keys in /etc/pki/tls rather than /usr/share/ssl.
+	@echo If you want to build for modern RedHat Linux, you should use
+	@echo make lr5 instead.
+	@echo Do you want to continue this build?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) exit 1;; esac'
+	@echo OK, I will remember that you really want to build for old
+	@echo RedHat Linux.  You will not see this message again.
+	@echo If you realize that you really wanted to build for modern
+	@echo RedHat Linux, then do the following commands:
+	@echo % rm lrhok
+	@echo % make clean
+	@echo % make lr5
+
+lsu:	an
+	$(BUILD) BUILDTYPE=lnp IP=$(IP6) \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/usr/share/ssl/certs SSLKEYS=/usr/share/ssl/private GSSDIR=/usr/kerberos"
+
+# iToy does not have Kerberos or PAM.  It doesn't have a
+# /System/Library/OpenSSL directory either, but the libcrypto shared library
+# has these locations so this is what we will use.
+
+osi:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=osx IP=$(IP6) CC=arm-apple-darwin-gcc \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/System/Library/OpenSSL/certs SSLKEYS=/System/Library/OpenSSL/private"
+
+oxp:	an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=osx IP=$(IP6) EXTRAAUTHENTICATORS="$(EXTRAAUTHENTICATORS) gss" \
+	PASSWDTYPE=pam \
+	EXTRACFLAGS="$(EXTRACFLAGS) -DMAC_OSX_KLUDGE=1" \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/System/Library/OpenSSL/certs SSLKEYS=/System/Library/OpenSSL/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib PAMDLFLAGS=-lpam"
+
+osx:	osxok an
+	$(TOUCH) ip6
+	$(BUILD) BUILDTYPE=$@ IP=$(IP6) EXTRAAUTHENTICATORS="$(EXTRAAUTHENTICATORS) gss" \
+	SPECIALS="SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib SSLCERTS=/System/Library/OpenSSL/certs SSLKEYS=/System/Library/OpenSSL/private GSSINCLUDE=/usr/include GSSLIB=/usr/lib"
+
+osxok:
+	@$(SH) -c '(test ! -f /usr/include/pam/pam_appl.h ) || make osxwarn'
+	@$(TOUCH) osxok
+
+osxwarn:
+	@echo You are building for OLD versions of Mac OS X.  This build is
+	@echo NOT suitable for modern versions of Mac OS X, such as Tiger,
+	@echo which use PAM-based authentication.  If you want to build for
+	@echo modern Mac OS X, you should use make oxp instead.
+	@echo Do you want to continue this build?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) exit 1;; esac'
+	@echo OK, I will remember that you really want to build for old
+	@echo Mac OS X.  You will not see this message again.
+	@echo If you realize that you really wanted to build for modern
+	@echo Mac OS X, then do the following commands:
+	@echo % rm osxok
+	@echo % make clean
+	@echo % make oxp
+
+
+# Linux shadow password support doesn't build on traditional systems, but most
+# Linux systems are shadow these days.
+
+lnx:	lnxnul an
+	$(BUILD) BUILDTYPE=$@
+
+lnxnul:
+	@$(SH) -c '(test $(PASSWDTYPE) = nul) || make lnxok'
+
+lnxok:
+	@echo You are building for traditional Linux.  Most modern Linux
+	@echo systems require that you build using make slx.
+	@echo Do you want to continue this build?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) exit 1;; esac'
+	@echo OK, I will remember that you really want to build for
+	@echo traditional Linux.  You will not see this message again.
+	@echo If you discover that you can not log in to the POP and IMAP
+	@echo servers, then do the following commands:
+	@echo % rm lnxok
+	@echo % make clean
+	@echo % make slx
+	@echo If slx does not work, try sl4 or sl5.  Be sure to do a
+	@echo make clean between each try!
+	@$(TOUCH) lnxok
+
+
+# SUN-OS C compiler makes you load libdl by hand...
+
+ssn sun: sunok suntools ua
+	$(BUILD) BUILDTYPE=$@
+
+suntools:
+	$(CD) tools;$(MAKE) LDFLAGS=-ldl
+
+gsu:	sunok an
+	$(BUILD) BUILDTYPE=$@
+
+s40:	sunok ua
+	$(BUILD) BUILDTYPE=$@
+
+sunok:
+	@echo You are building for the old BSD-based SUN-OS.  This is NOT
+	@echo the modern SVR4-based Solaris.  If you want to build for
+	@echo Solaris, you should use make gso or make sol or make soc.  Do
+	@echo you want to continue this build?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) exit 1;; esac'
+	@echo OK, I will remember that you really want to build for the old
+	@echo BSD-based SUN-OS.  You will not see this message again.
+	@echo If the build fails and you realize that you really wanted to
+	@echo build for Solaris, then do the following commands:
+	@echo % rm sunok
+	@echo % make clean
+	@echo % make gso
+	@echo If gso does not work, try sol.  Be sure to do a make clean
+	@echo between each try!
+	@$(TOUCH) sunok
+
+
+# SVR2 doesn't have symbolic links (at least my SVR2 system doesn't)
+
+sv2:
+	$(MAKE) ua LN=ln
+	$(BUILD) BUILDTYPE=$@ LN=ln
+
+# Hard links don't quite work right in SUA, and there don't seem to be any
+# SSL includes.  However, IPv6 works.
+
+sua:
+	$(TOUCH) ip6 sslnone
+	$(MAKE) an LN=cp SSLTYPE=none
+	$(BUILD) BUILDTYPE=$@ LN=cp IP=$(IP6) SSLTYPE=none
+
+
+# Pine port names, not distinguished in c-client
+
+bs2:	an
+	$(BUILD) BUILDTYPE=bsi
+
+pt1:	an
+	$(BUILD) BUILDTYPE=ptx
+
+
+# Compatibility
+
+hxd:
+	$(BUILD) BUILDTYPE=hpx PASSWDTYPE=dce
+
+# Amiga
+
+ami am2 ama amn:
+	$(MAKE) an LN=cp SYSTEM=amiga
+	$(BUILD) BUILDTYPE=$@ LN=cp
+
+
+# Courtesy entries for Microsoft systems
+
+nt:
+	nmake /nologo /f makefile.nt
+
+ntk:
+	nmake /nologo /f makefile.ntk
+
+w2k:
+	nmake /nologo /f makefile.w2k
+
+wce:
+	nmake /nologo /f makefile.wce
+
+
+# SSL build choices
+
+sslnopwd sslunix.nopwd sslsco.nopwd:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + Building in full compliance with RFC 3501 security
+	@echo + requirements:
+	@echo ++ TLS/SSL encryption is supported
+	@echo ++ Unencrypted plaintext passwords are prohibited
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+sslunix sslsco:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + Building in PARTIAL compliance with RFC 3501 security
+	@echo + requirements:
+	@echo + Compliant:
+	@echo ++ TLS/SSL encryption is supported
+	@echo + Non-compliant:
+	@echo ++ Unencrypted plaintext passwords are permitted
+	@echo +
+	@echo + In order to rectify this problem, you MUST build with:
+	@echo ++ SSLTYPE=$(SSLTYPE).nopwd
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo
+	@echo Do you want to continue this build anyway?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) (make nounenc;exit 1);; esac'
+
+nounenc:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + At your request, this build with unencrypted authentication has
+	@echo + been CANCELLED.
+	@echo + You must start over with a new make command.
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+
+sslnone:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + Building in NON-COMPLIANCE with RFC 3501 security requirements:
+	@echo + Non-compliant:
+	@echo ++ TLS/SSL encryption is NOT supported
+	@echo ++ Unencrypted plaintext passwords are permitted
+	@echo +
+	@echo + In order to rectify this problem, you MUST build with:
+	@echo ++ SSLTYPE=nopwd
+	@echo + You must also have OpenSSL or equivalent installed.
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo
+	@echo Do you want to continue this build anyway?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) (make nonossl;exit 1);; esac'
+
+nonossl:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + At your request, this build with no TLS/SSL support has been
+	@echo + CANCELLED.
+	@echo + You must start over with a new make command.
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+
+# IP build choices
+
+ip4:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + Building with IPv4 support
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+ip6:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + Building with IPv6 support
+	@echo +
+	@echo + NOTE: Some versions of glibc have a bug in the getaddrinfo
+	@echo + call which does DNS name resolution.  This bug causes host
+	@echo + names to be canonicalized incorrectly, as well as doing an
+	@echo + unnecessary and performance-sapping reverse DNS call.  This
+	@echo + problem does not affect the IPv4 gethostbyname call.
+	@echo +
+	@echo + getaddrinfo works properly on Mac OS X and Windows.  However,
+	@echo + the problem has been observed on some Linux systems.
+	@echo +
+	@echo + If you answer n to the following question the build will be
+	@echo + cancelled and you must rebuild.  If you did not specify IPv6
+	@echo + yourself, try adding IP6=4 to the make command line.
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo
+	@echo Do you want to build with IPv6 anyway?  Type y or n please:
+	@$(SH) -c 'read x; case "$$x" in y) exit 0;; *) (make noip6;exit 1);; esac'
+	@echo OK, I will remember that you really want to build with IPv6.
+	@echo You will not see this message again.
+	@$(TOUCH) ip6
+
+noip6:
+	$(MAKE) clean
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + At your request, this build with IPv6 has been CANCELLED.
+	@echo + You must start over with a new make command.
+	@echo +
+	@echo + If you wish to rebuild without IPv6 support, do one of the
+	@echo + following:
+	@echo +
+	@echo + 1. If you specified IP=6 on the make command line, omit it.
+	@echo +
+	@echo + 2. Some of the Linux builds automatically select IPv6.  If
+	@echo + you choose one of those builds, add IP6=4 to the make command
+	@echo + line.  Note that this is IP6=4, not IP=4.
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+# C compiler types
+
+an ua:
+	@$(MAKE) ssl$(SSLTYPE)
+	@echo Applying $@ process to sources...
+	$(TOOLS)/$@ "$(LN)" src/c-client c-client
+	$(TOOLS)/$@ "$(LN)" src/ansilib c-client
+	$(TOOLS)/$@ "$(LN)" src/charset c-client
+	$(TOOLS)/$@ "$(LN)" src/osdep/$(SYSTEM) c-client
+	$(TOOLS)/$@ "$(LN)" src/mtest mtest
+	$(TOOLS)/$@ "$(LN)" src/ipopd ipopd
+	$(TOOLS)/$@ "$(LN)" src/imapd imapd
+	$(TOOLS)/$@ "$(LN)" src/mailutil mailutil
+	$(TOOLS)/$@ "$(LN)" src/mlock mlock
+	$(TOOLS)/$@ "$(LN)" src/dmail dmail
+	$(TOOLS)/$@ "$(LN)" src/tmail tmail
+	$(LN) $(TOOLS)/$@ .
+
+build:	OSTYPE rebuild rebuildclean bundled
+
+OSTYPE:
+	@$(MAKE) ip$(IP)
+	@echo Building c-client for $(BUILDTYPE)...
+	@$(TOUCH) SPECIALS
+	echo `$(CAT) SPECIALS` $(EXTRASPECIALS) > c-client/SPECIALS
+	$(CD) c-client;$(MAKE) $(BUILDTYPE) EXTRACFLAGS='$(EXTRACFLAGS)'\
+	 EXTRALDFLAGS='$(EXTRALDFLAGS)'\
+	 EXTRADRIVERS='$(EXTRADRIVERS)'\
+	 EXTRAAUTHENTICATORS='$(EXTRAAUTHENTICATORS)'\
+	 PASSWDTYPE=$(PASSWDTYPE) SSLTYPE=$(SSLTYPE) IP=$(IP)\
+	 $(SPECIALS) $(EXTRASPECIALS)
+	echo $(BUILDTYPE) > OSTYPE
+	$(TOUCH) rebuild
+
+rebuild:
+	@$(SH) -c '(test $(BUILDTYPE) = rebuild -o $(BUILDTYPE) = `$(CAT) OSTYPE`) || (echo Already built for `$(CAT) OSTYPE` -- you must do \"make clean\" first && exit 1)'
+	@echo Rebuilding c-client for `$(CAT) OSTYPE`...
+	@$(TOUCH) SPECIALS
+	$(CD) c-client;$(MAKE) all CC=`$(CAT) CCTYPE` \
+	 CFLAGS="`$(CAT) CFLAGS`" `$(CAT) SPECIALS`
+
+rebuildclean:
+	$(SH) -c '$(RM) rebuild || true'
+
+bundled:
+	@echo Building bundled tools...
+	$(CD) mtest;$(MAKE)
+	$(CD) ipopd;$(MAKE)
+	$(CD) imapd;$(MAKE)
+	$(CD) mailutil;$(MAKE)
+	@$(SH) -c '(test -f /usr/include/sysexits.h ) || make sysexitwarn'
+	$(CD) mlock;$(MAKE) || true
+	$(CD) dmail;$(MAKE) || true
+	$(CD) tmail;$(MAKE) || true
+
+
+sysexitwarn:
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+	@echo + Hmm...it does not look like /usr/include/sysexits.h exists.
+	@echo + Either your system is too ancient to have the sysexits.h
+	@echo + include, or your C compiler gets it from some other location
+	@echo + than /usr/include.  If your system is too old to have the
+	@echo + sysexits.h include, you will not be able to build the
+	@echo + following programs.
+	@echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+clean:
+	@echo Removing old processed sources and binaries...
+	$(SH) -c '$(RM) an ua OSTYPE SPECIALS c-client mtest imapd ipopd mailutil mlock dmail tmail || true'
+	$(CD) tools;$(MAKE) clean
+
+
+# A monument to a hack of long ago and far away...
+love:
+	@echo not war?

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/NOTICE	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,17 @@
+UW IMAP toolkit notices:
+
+This software was developed by the University of Washington
+(http://www.washington.edu/).
+
+The Univerity of Washington IMAP Toolkit (c-client API, dmail, imapd,
+ipop2d, ipop3d, mailutil, mlock, mtest, and tmail software; and its
+included text) is Copyright 1988-2007 by the University of Washington.
+
+The c-client library and mtest software are in part based upon code
+developed by Mark Crispin at Stanford University, and is
+
+ * Copyright 1988 Stanford University and was developed in the
+ * Symbolic Systems Resources Group of the Knowledge Systems Laboratory
+ * at Stanford University in 1987-88, and was funded by the
+ * Biomedical Research Technology Program of the National Institutes of
+ * Health under grant number RR-00785.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,74 @@
+/* ========================================================================
+ * Copyright 1988-2007 University of Washington
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * 
+ * ========================================================================
+ */
+
+			   IMAP Toolkit Environment
+			         4 April 2007
+				 Mark Crispin
+
+
+			    UNIX QUICK BUILD NOTES
+
+These quick build notes assume that you have installed OpenSSL before
+attempting to build this software, and that you do not have any non-default
+configuration parameters.
+
+If you need additional information in building this software with OpenSSL,
+please refer to the docs/SSLBUILD file for more information.
+
+If you intend to build this software with a non-default configuration
+(including building a non-compliant server without SSL support), please
+refer to the docs/BUILD file for more information.
+
+1) Look in the top-level Makefile and find your system type code.  For example,
+   modern versions of Linux will use either "slx", "lnp", or one of the
+   lnp-variants (such as "lrh").
+
+2) Type "make" followed by the system type, e.g. "make slx".
+
+3) Install the POP2 daemon (ipopd/ipop2d), the POP3 daemon (ipopd/ipop3d), and
+   the IMAP daemon (imapd/imapd) on a system directory of your choosing.
+
+4) Update /etc/services to register the pop2 service on TCP port 109, the
+   pop3 service on TCP port 110, and the imap service on TCP port 143.  Also
+   update Yellow Pages/NIS/NetInfo/etc. if appropriate on your system.
+
+5) Update /etc/inetd.conf (or install files on /etc/xinetd.d) to invoke the
+   POP2, POP3, and IMAP daemons on their associated services.
+
+6) If your system uses PAM authentication, be sure to set up /etc/pam.d/imap
+   (*not* /etc/pam.d/imapd) and /etc/pam.d/pop (*not* /etc/pam.d/ipop3d or
+   /etc/pam.d/pop3d or /etc/pam.d/popd or /etc/pam.d/pop3).
+
+7) Unless you built your system without SSL support, you will need to set
+   up SSL server certificates as described in docs/SSLBUILD.
+
+6) That's all!
+
+Read the file docs/BUILD and docs/SSLBUILD if you need more detailed
+information and/or you don't understand these quick build instructions.
+
+			     MISCELLANEOUS NOTES
+
+     mtest has been run under UNIX, DOS, Windows, NT, Macintosh, TOPS-20, and
+VMS.  It is a very primitive interface, however, and is suited mainly as a
+model of how to write a main program for c-client.  You should take a look at
+the source to figure out how to use it.  Briefly, it first asks for a mailbox
+name (either a local file path or an IMAP mailbox in the form
+"{hostname}mailbox") and then puts you in a command mode where "?" will give
+you a list of commands.
+
+     Pine is available separately on the FTP.CAC.Washington.EDU archives.
+
+     The focus of development and support is for UNIX and Win32 (including
+Windows 95/98/Millenium, Windows NT, and Windows 2000).  The other ports are
+not frequently used or tested, and may be incomplete.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/SUPPORT	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,22 @@
+/* ========================================================================
+ * Copyright 1988-2006 University of Washington
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * 
+ * ========================================================================
+ */
+
+			     BUG REPORTING ADDRESS
+
+     Bug reports, comments, or questions regarding this software may
+be reported to the imap-uw@u.washington.edu mailing list (this replaces
+the old c-client@u.washington.edu mailing list).  You can subscribe to
+this list by sending a message to:
+	imap-uw-subscribe@mailman.u.washington.edu
+
+     An alternative is to use the comp.mail.imap newsgroup.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/BUILD	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,491 @@
+/* ========================================================================
+ * Copyright 1988-2007 University of Washington
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * 
+ * ========================================================================
+ */
+
+			 BUILD AND INSTALLATION NOTES
+			 Last Updated: 15 November 2007
+
+Table of Contents:
+1. UNIX Build Notes
+2. UNIX Installation Notes
+3. Win32 Build Notes
+4. Win32 Installation Notes
+5. Inactive Ports (TOPS-20, VMS)
+6. Other ports (Macintosh, DOS/Win16, Windows CE, Amiga, OS/2)
+
+
+			       UNIX BUILD NOTES
+
+     The default build on many systems with IPv4 only.  To build with IPv6,
+add "IP=6" to the make command line, e.g.
+	make lnp IP=6
+
+     The default build is to build with SSL and disabling plaintext passwords
+unless SSL/TLS encryption is in effect (SSLTYPE=nopwd).  This means that
+OpenSSL MUST be installed before building the IMAP toolkit.  Please refer to
+the SSLBUILD file for more information.
+
+     To build without SSL, add "SSLTYPE=none" to the make command line.
+Note that doing so will produce an IMAP server which is NON-COMPLIANT with
+RFC 3501.
+
+     You must build through the top-level imap-2007/Makefile, which will run
+a "process" step the first time and create the imap-2007/c-client,
+imap-2007/ipopd, and imap-2007/imapd directories in which building actually
+takes place.
+
+     Before doing a make on UNIX, you should read imap-2007/Makefile and see
+if your system type is known.  The various system types are three-letter codes.
+If your system type is known, then use this as the make option.  After the
+first time you do a make, this option is remembered in a file called OSTYPE,
+so just typing "make" suffices.
+
+     For example, if you are using a more or less modern Linux system, your
+system type is probably one of the specific distribution types (such as lrh for
+RedHat).  For more generic builds, try slx (shadow passwords only) or lnp (PAM).
+To build for RedHat, do:
+	make lrh
+
+     There are other make options, described in imap-2007/src/osdep/Makefile.
+
+     It's probably best to see if an existing port will work on your system
+before inventing a new port.  Try:
+	sv4		generic SVR4, non-ANSI compiler
+	a32		modern SVR4
+	bsd		basic 4.3 BSD, non-ANSI compiler
+	bsf		modern BSD
+
+     If you must invent a new port, you need to create an entry in
+imap-2007/Makefile and imap-2007/src/osdep/Makefile for your new port, as
+well as osdep/os_???.h and osdep/os_???.c files with the appropriate
+OS-dependent support for that system.  You also need to determine which setup
+process to use.  You should use the ua process unless you are sure that your
+compiler supports *ALL* aspects of ANSI C prototyping.  Note that some
+compilers, such as Ultrix, support some aspects of ANSI C but not others;
+c-client really beats on the full prototyping capability of ANSI C so you
+have to use the non-ANSI source tree for such systems.
+
+     If you send a new port back to us, we will make it available for others
+who use your particular system type.
+
+     The mbox driver is now enabled by default.  If the file "mbox" exists on
+the user's home directory and is in UNIX mailbox format, then when INBOX is
+opened this file will be selected as INBOX instead of the mail spool file.
+Messages will be automatically transferred from the mail spool file into the
+mbox file.  To disable this behavior, delete "mbox" from the EXTRADRIVERS list
+in the top-level Makefile and rebuild.
+
+     WARNING: The SVR2 (sv2) port is *incomplete*.  SVR2 does not appear to
+have any way to do ftruncate(), which is needed by the mbox, mbx, mmdf, mtx,
+tenex, and unix drivers.
+
+			   UNIX INSTALLATION NOTES
+
+     Binaries from the build are:
+	imap-2007/mtest/mtest		c-client testbed program
+	imap-2007/ipopd/ipop2d		POP2 daemon
+	imap-2007/ipopd/ipop3d		POP3 daemon
+	imap-2007/imapd/imapd		IMAP4rev1 daemon
+
+     mtest is normally not used except by c-client developers.
+
+STEP 1:	[x]inetd setup
+
+     The ipop2d, ipop3d, and imapd daemons should be installed in a system
+daemon directory and invoked by a listener such as xinetd or inetd.  In the
+following examples, /usr/local/etc is used).
+
+STEP 1(A): xinetd-specific setup
+
+     If your system uses xinetd, the daemons are invoked by files in your
+/etc/xinetd.d directory with names corresponding to the service names (that
+is: imap, pop2, pop3).  You will need to consult your local xinetd
+documentation to see what should go into these files.  Here is a a sample
+/etc/xinetd.d/imap file:
+
+service imap
+{
+	disable		= no
+	socket_type	= stream
+	wait		= no
+	user		= root
+	server		= /usr/local/etc/imapd
+	groups		= yes
+	flags		= REUSE IPv6
+}
+
+STEP 1(B): inetd-specific setup
+
+     If your system still uses inetd, the daemons are invoked by your
+/etc/inetd.conf file with lines such as:
+
+pop	stream	tcp	nowait	root	/usr/local/etc/ipop2d	ipop2d
+pop3	stream	tcp	nowait	root	/usr/local/etc/ipop3d	ipop3d
+imap	stream	tcp	nowait	root	/usr/local/etc/imapd	imapd
+
+     Note that different variants of UNIX have different versions of inetd,
+so you should verify the precise form of these commands (for example, some
+versions of inetd do not require the "nowait").
+
+     IMPORTANT NOTE: inetd has a limit of how many new connections it will
+allow in a certain interval, and when this limit is exceeded, it shuts down
+the server.  If you have anything beyond a small-scale server, you are
+probably going to run up against this limit.  You'll know when it happens;
+your syslog will give the misleading message "imap/tcp server failing
+(looping), service terminated" and users will complain that IMAP service is
+unavailable for the next 10 minutes.  Similarly with "pop3/tcp server
+failing"...
+
+     It must be emphasized that this is *NOT* a bug in the IMAP or POP
+servers, nor is it anything that I can "fix".  It is an inetd problem, and
+the only way to fix it is to change inetd's behavior.
+
+     By default, the parameters of this limit are (from inetd.c source code):
+
+#define TOOMANY         40              /* don't start more than TOOMANY */
+#define CNT_INTVL       60              /* servers in CNT_INTVL sec. */
+#define RETRYTIME       (60*10)         /* retry after bind or server fail */
+
+That is, no more than 40 connections (TOOMANY) in 60 seconds (CNT_INTL), and
+if exceeded, shut down the server for 10 minutes (RETRYTIME).  This was a
+good setting in the 1980s ARPAnet, but is much too small today.
+
+     Some versions of inetd allow you to see a higher maximum in the
+/etc/inetd.conf file.  Read "man inetd" and see if you see something like
+this in the text:
+
+     The wait/nowait entry is applicable to datagram sockets only [...]
+     [...]  The optional ``max'' suffix (separated from
+     ``wait'' or ``nowait'' by a dot) specifies the maximum number of server
+     instances that may be spawned from inetd within an interval of 60 sec-
+     onds. When omitted, ``max'' defaults to 40.
+
+If you see this, then edit the /etc/inetd.conf entry for imapd to be
+something like:
+
+imap	stream	tcp	nowait.100	root	/usr/local/etc/imapd	imapd
+ (or, if you use TCP wrappers)
+imap	stream	tcp	nowait.100	root	/usr/local/etc/tcpd	imapd
+
+     Otherwise, you'll need to edit the inetd source code to set TOOMANY to a
+higher value, then rebuild inetd.
+
+
+STEP 2:	services setup
+
+     You may also have to edit your /etc/services (or Yellow Pages,
+NetInfo, etc. equivalent) to register these services, such as:
+
+pop		109/tcp
+pop3		110/tcp
+imap		143/tcp
+
+
+STEP 3: PAM setup
+
+     If your system has PAM (Pluggable Authentication Modules -- most
+modern systems do) then you need to set up PAM authenticators for imap and
+pop.  The correct file names are
+	/etc/pam.d/imap
+and
+	/etc/pam.d/pop
+
+     It probably works to copy your /etc/pam.d/ftpd file to the above two
+names.
+
+     Many people get these file names wrong, and then spend a lot of time
+trying to figure out why it doesn't work.  Common mistakes are:
+	/etc/pam.d/imapd
+	/etc/pam.d/imap4
+	/etc/pam.d/imap4rev1
+	/etc/pam.d/ipop3d
+	/etc/pam.d/pop3d
+	/etc/pam.d/popd
+	/etc/pam.d/pop3
+
+
+STEP 4:	optional rimap setup
+
+     If you want to enable the rimap capability, which allows users with a
+suitable client and .rhosts file on the server to access IMAP services
+without transmitting her password in the clear over the network, you need
+to have /etc/rimapd as a link to the real copy of imapd.  Assuming you have
+imapd installed on /usr/local/etc as above:
+	% ln -s /usr/local/etc/imapd /etc/rimapd
+
+     Technical note: rimap works by having the client routine tcp_aopen()
+invoke `rsh _host_ exec /etc/rimapd' in an child process, and then returning
+pipes to that process' standard I/O instead of a TCP socket.  You can set up
+`e-mail only accounts' by making the shell be something which accepts only
+that string and not ordinary UNIX shell commands.
+
+
+STEP 4:	notes on privileges
+
+     Neither user "root", not any other UID 0 account, can log in via IMAP or
+POP.  "That's not a bug, it's a feature!"
+
+     This software is designed to run without privileges.  The mail spool
+directory must be protected 1777; that is, with world write and the sticky
+bit.  Of course, mail *files* should be protected 600!
+
+     An alternative to having the mail spool directory protected 1777, at the
+cost of some performance, is to use the external "mlock" program, available
+as part of the imap-utils package.  With mlock installed as /etc/mlock and
+setgid mail, the spool directory can be protected 775 with group mail.
+Please disregard this paragraph if you don't understand it COMPLETELY, and
+know EXACTLY what to do without question.
+
+
+STEP 5:	SVR4 specific setup
+
+     There is one "gotcha" on System V Release 4 based systems such as
+Solaris.  These systems do not use the standard UNIX mail format, but rather a
+variant of that format that depends upon a bogus "Content-Length:" message
+header.  This is widely recognized to have been a terrible mistake.  One
+symptom of the problem is that under certain circumstances, a message may get
+broken up into several messages.  I'm also aware of security bugs caused by
+programs that foolishly trust "Content-Length:" headers with evil values.
+
+    To fix your system, edit your sendmail.cf to change the Mlocal line to
+have the -E flag.  A typical entry will lool like:
+
+Mlocal, P=/usr/lib/mail.local, F=flsSDFMmnPE, S=10, R=20, A=mail.local -d $u
+
+			      WIN32 BUILD NOTES
+
+     Visual C++ 6.0 along with the current Microsoft Platform SDK
+(specifically the CORE SDK and the Internet Development SDK) is required
+to build on Windows 9x/Me/NT/2K/XP.  If you do not have the Platform SDK
+installed or in your path properly, you'll get errors when building os_nt.c,
+typically in env_nt.c, ssl_nt.c, ssl_w2k.c, or gss_shim.c.  You can download
+the Microsoft Platform SDK from Microsoft's web site.
+
+     There is also considerable debate about how new mail is to be snarfed.
+I am currently using something that seems to work with WinSMTP.  Look at
+the definition of MAILFILE in imap-2007/src/osdep/nt/mailfile.h and at the
+sysinbox() function in imap-2007/src/osdep/nt/env_nt.c to see what's there
+now, so you have a clue about how to hack it.
+
+     To build under Windows 95/98/NT, connect to the imap-2007 directory
+and do:
+	nmake -f makefile.nt
+The resulting binaries will support SSL if either schannel.dll or
+security.dll is installed in Windows, using the old, undocumented, SSL
+interfaces.  You can also use this to build under Me/2000/XP, but it is
+not the preferred build on this platform.
+
+     To build with MIT Kerberos support, connect to the imap-2007 directory
+and do:
+	nmake -f makefile.ntk
+The resulting binaries will support SSL if either schannel.dll or
+security.dll is installed in Windows, using the old, undocumented SSL
+interfaces.  They will also support MIT Kerberos.  Note, however, that
+these binaries will only run on systems which have the MIT Kerberos DLLs
+installed, and will not run otherwise.
+
+     To build under Windows Me/2000/XP, connect to the imap-2007 directory
+and do:
+	nmake -f makefile.w2k
+The resulting binaries will support SSL and Microsoft Kerberos, using the
+official, documented, Microsoft interfaces.  Note, however, that these
+binaries will not run under Windows 95, Windows 98, or Windows NT4.
+
+			   WIN32 INSTALLATION NOTES
+
+     The resulting binaries will be:
+	imap-2007\mtest\mtest.exe	(testbed client)
+	imap-2007\ipopd\ipop2d.exe	POP2 server
+	imap-2007\ipopd\ipop3d.exe	POP3 server
+	imap-2007\imapd\imapd.exe	IMAP4rev1 server
+
+     These servers are stdio servers.  I wrote a simple network listener
+for NT called inetlisn; currently it is available as:
+	ftp://ftp.cac.washington.edu/mail/nt/inetlisn.tar
+To build this, use "nmake" after connecting to the inetlisn directory.
+inetlisn takes two arguments, the first being the port number and the second
+being the binary to run to serve a connection on that port, e.g.
+	c:\bin\inetlisn 143 c:\mail_daemons\imapd
+
+     Note that NT imapd must be started as SYSTEM in order to be recognized as
+being "not logged in"; otherwise it will preauth as whatever user it is
+running as which is probably not what you want.  One way to have it run as
+system is to have inetlisn run by an AT command, e.g. if the time now is
+2:05PM, try something like:
+	AT 14:06 "c:\bin\inetlisn 143 c:\mail_daemons\imapd"
+
+     A more advanced network listener called wsinetd is available on:
+	http://wsinetd.sourceforge.net
+It is based on inetlisn, and essentially is a "completed" version of inetlisn.
+
+     Bottom line: this is not plug-and-play.  If you're not a hacker and/or
+are unwilling to invest the time to do some programming, you probably want to
+buy a commercial server product.
+
+				INACTIVE PORTS
+
+     The TOPS-20 and VMS ports were developed at one time or another, but are
+no longer actively developed.  However, from time to time I test build both
+of these to make sure that they compile without errors and that mtest runs,
+and will continue doing so as long as I have access to systems running these
+operating systems.
+
+
+			     TOPS-20 BUILD NOTES
+
+     I have provided a c-client port for TOPS-20 systems, but you're on your
+own in terms of a nice TOPS-20 like main program.  Maybe someday some nice
+person will try porting Pine to TOPS-20.  This assumes the use of KCC 6, and
+probably will not build with other compilers or older versions of KCC.
+
+     You do not use imap-2007/Makefile under TOPS-20, nor do you build any
+components other than c-client and mtest.  Merge the contents of
+imap-2007/src/c-client, imap-2007/src/charset, imap-2007/src/mtest, and
+imap-2007/src/osdep/tops-20 onto a single directory on TOPS-20 and build from
+that.  The command:
+	DO BUILD.CTL
+will build the sources.  If you don't have MIC, then SUBMIT BUILD.CTL and let
+BATCON execute it.
+
+
+			       VMS BUILD NOTES
+
+      The VMS port has been tested with imap-2007, but as I am soon going
+to lose access to a VMS system I will no longer be able able to test and
+this port will be moved to the "other ports" category".
+
+      You do not use imap-2007/Makefile under VMS, nor do you build any
+components other than c-client and mtest.  Merge the contents of
+imap-2007/src/c-client, imap-2007/src/charset, imap-2007/src/mtest, and
+imap-2007/src/osdep/vms onto a single directory on VMS and build from that.
+The command to build it is:
+	@BUILD MULTINET
+or	@BUILD NETLIB
+If you just do @BUILD it will build with dummy TCP code, and since only TCP
+based drivers are provided here this isn't too useful.
+
+     If you aren't on the Pacific coast of the US or Canada, you probably will
+need to change the wired-in timezone in the BUILD.COM file.  Apparently, the
+wonderful VMS system that DEC loves so much doesn't maintain any concept of
+time zone; the VMS C compiler returns a null pointer from gmtime()!
+
+     Otherwise you're pretty much on your own here.
+
+				 OTHER PORTS
+
+     The following ports were developed at one time or another, but are no
+longer actively developed or tested.  It is not known if they still work or
+not.
+
+  Port		Status
+  ----		------
+Macintosh	Obsolete; Mac OS X uses UNIX port
+DOS/Win16	Obsolete; modern PCs use Win32 port
+Windows CE	Never completed
+Amiga		Unknown
+OS/2		Unknown
+
+			     MACINTOSH BUILD NOTES
+
+     This port is for the old Mac OS system, not Mac OS X.
+
+     If you are building a Macintosh client, you will need MacTCP installed on
+your system as well as the MacTCP C includes and libraries.
+
+     You do not use imap-2007/Makefile on the Mac, nor do you build any
+components other than c-client and mtest.  Merge the contents of
+imap-2007/src/c-client, imap-2007/src/charset, imap-2007/src/mtest, and
+imap-2007/src/osdep/mac onto a single directory on the Mac and build from
+that.  mtext.sit.hqx is a THINK C project file and cute icon for building
+mtest, encoded with Binhex and StuffIt.
+
+     THINK C is a truly wretched product which help make me understand why
+Macintosh has lost most of its market share.  Not only does it do cretinous
+things such as barf about a cast in front of an lvalue, it also limits the size
+of code *or* data in a single file to 32K!  So much for having large character
+set tables.  Symantec says that "MacOS requires it, break up your files into
+smaller pieces" yet somehow gcc under MachTen contrives to compile C programs
+without subjecting the programmer to this idiocy.
+
+     As a result of this, I found myself obliged to comment out the #includes
+of the East Asian character sets in utf8.c in order to get it to build.  It's
+also necessary to break up some of the files, at least mail.c and imap4r1.c.
+Maybe you don't have to do this in CodeWarrior or whatever the new compiler is
+called, but I've pretty much given up on Macintosh.
+
+     If you use precompiled headers, you may get some compilation errors since
+some Apple symbols need to be redefined in order to get it to build under all
+versions of MacOS.  Try turning off the precompiled headers (so it will
+re-read the .h files) and see if it builds any better.
+
+     If you use a Mac C compiler with 2-byte ints (such as THINK C's normal
+mode) you will need to fix some bugs in the MacTCP C includes and libraries to
+prevent it from generating bad code, since those MacTCP files violate Apple's
+standards of always using explicit shorts or longs, never ints.  You could
+avoid this if you set 4-byte ints in THINK C; however, the ANSI and UNIX
+libraries in THINK C use 2-byte ints so you will also need to build 4-byte int
+versions of these.  c-client itself is 2-byte int or 4-byte int clean; it can
+be used in either mode.
+
+     The most important bug in the MacTCP files that you need to fix is in the
+file AddressXlation.h, you need to change the definition of the rtnCode member
+of the hostInfo structure to be long instead of int.  There are several other
+changes you need to make if you decide to compile dnr.c under THINK C instead
+of using the Apple-supplied object file; see me for details if you decide to
+undertake such an effort.  This is fixed in newer versions from Apple.
+
+
+			     DOS/WIN16 BUILD NOTES
+
+     If you are building a DOS client, you will need a TCP/IP stack installed
+on your DOS system along with its development environment.  The currently
+supported stacks are Beame & Whiteside, PC-NFS, Novell, PC/IP, Waterloo, and
+Winsock.  mtest and a version of Pine called PC Pine run under DOS.
+
+      You do not use imap-2007/Makefile under DOS, nor do you build any
+components other than c-client and mtest.  Merge the contents of
+imap-2007/src/c-client, imap-2007/src/charset, imap-2007/src/mtest, and
+imap-2007/src/osdep/dos onto a single directory on DOS and build from that.
+The MAKE command on DOS takes an argument identifying the TCP/IP stack in use.
+For example, do:
+	MAKE MAKEFILE OS=WSK   (or MAKE -F MAKEFILE OS=WSK)
+to build for Winsock.  
+
+     If you write a program for DOS/Win16, you will probably have to write a
+replacement cache manager (look at mm_cache()) and otherwise disable most of
+c-client's caching.  Even so, memory limitations will be an ongoing problem,
+particularly with DOS, and you will have some severe performance problems.
+It's a bit better on Win16, but in my opinion you are better off writing a
+32-bit program and telling your Win16 customers to upgrade to Windows 95 or at
+least install Win32s.
+
+
+			    WINDOWS CE BUILD NOTES
+
+     I build using Visual C++ 6.0 with the WCE extensions.  The current code
+has SH3 wired in for the compiler building.
+
+     To build under NT, connect to the imap-2007 directory and do:
+	nmake -f makefile.wce
+
+     The only binary produced is a cclient.lib file.  I haven't gotten as far
+as building mtest on WCE, mainly because I don't have a stdlib library.
+
+
+		      AMIGA BUILD AND INSTALLATION NOTES
+
+     The Amiga port was contributed.  Maybe the UNIX notes will help.
+
+
+			       OS2 BUILD NOTES
+
+     The OS2 port was contributed.  Maybe the Win32 Build Notes will help.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/CONFIG	Mon Sep 14 15:17:45 2009 +0900
@@ -0,0 +1,181 @@
+/* ========================================================================
+ * Copyright 1988-2006 University of Washington
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * 
+ * ========================================================================
+ */
+
+		       UNIX Configuration Notes
+
+     The IMAP and POP3 servers are plug-and-play on standard UNIX
+systems.  There is no special configuration needed.  Please ignore all
+rumors to the effect that you need to create an IMAP configuration
+file.
+
+     If your system is non-standard, virtually everything that you are
+likely to want to modify can be found in the source file
+	.../src/osdep/unix/env_unix.c
+In particular, special attention should be given to the routines:
+ env_init()		initialize c-client environment variables,
+			especially the user name and home directory
+ sysinbox()		return the UNIX path of the INBOX in which
+			mail delivery will place mail
+ mailboxdir()		translate a mailbox name into the associated
+			UNIX directory for listing
+ mailboxfile()		translate a mailbox name into the associated
+			UNIX file for opening
+
+     There are also build options in the top-level makefile which you
+can give on the command line when building the software.  The most
+common build options are "SSLTYPE=unix", to build the software with SSL,
+and "SSLTYPE=nopwd", to build the software with SSL and disable plaintext
+authentication unless the session is encrypted.
+
+     You should modify these routines as necessary for local policy.
+The most common modifications are to env_init(), to modify the
+software's idea of the home directory (which is used everywhere as the
+default directory), and to sysinbox(), to modify where the software
+looks for newly-delivered mail.
+
+     Example 1: suppose your mailer delivers mail to file ".mailbox"
+in the user's home directory instead of the default UNIX mail spool
+directory.  You will want to change routine sysinbox(), changing the
+line that reads:
+
+    sprintf (tmp,"%s/%s",MAILSPOOL,myusername ());
+to be:
+    sprintf (tmp,"%s/.mailbox",myhomedir ());
+
+     Example 2: suppose you want to change c-client's idea of the
+user's mailbox directory to be the "mail" subdirectory of the user's
+home directory instead of the user's home directory.  You will want to
+change variable mailsubdir, changing the line that reads:
+
+static char *mailsubdir = NIL;	/* mail subdirectory name */
+ to be:
+static char *mailsubdir = "mail";/* mail subdirectory name */
+
+     Example 3: suppose you want to disable plaintext authentication in
+the IMAP and POP servers.  If you want to disable plaintext authentication
+in unencrypted sessions but permit it in encrypted sessions, you should use
+"SSLTYPE=nopwd" in the make command line when building the software.  For
+example, to do this on a Linux system with PAM authentication, do:
+	make lnp SSLTYPE=nopwd
+If you want to disable plaintext authentication under all circumstances
+(including SSL or TLS encrypted sessions), use "PASSWDTYPE=nul", e.g.:
+	make lnx EXTRAAUTHENTICATORS=gss PASSWDTYPE=nul
+which will make it impossible to log in except via Kerberos.
+
+     Example 4: suppose you want the IMAP and POP servers to do a chroot()
+to the user's home directory.  This is not recommended; there are known
+ways of attacking chroot() based security mechanisms.  Furthermore, if you
+do this you can not use a traditional UNIX format INBOX in the mail spool
+directory, since chroot() will prevent access to that directory.  If you
+really want to do this, you need to change variable closedBox, changing
+the line which reads:
+
+static short closedBox = NIL;	/* is a closed box */
+ to be:
+static short closedBox = T;	/* is a closed box */
+
+     Example 5: suppose you want to disable non-namespace access to the
+filesystem root and other users' names, but do not want to go to the
+extreme of chroot() and you want to allow access to a traditional UNIX
+format INBOX in the mail spool directory.  You need to change variable
+restrictBox, changing the line which reads:
+
+static short restrictBox = NIL;	/* is a restricted box */
+ to be:
+static short restrictBox = -1;	/* is a restricted box */
+
+Other values to set in restrictBox can be found in env_unix.h.
+
+     Ignore all references in env_unix.c to a configuration file; that
+code is for UW-internal use only.  It is extremely unlikely that that
+facility will work usefully for you; it is extremely likely that you
+will shoot yourself in the foot by using; and it frequently changes in
+an incompatible manner.
+
+     There are two other build-time configuration issues which you may
+need to consider: drivers and authenticators.  Both of these are set
+up in the top-level Makefile -- in particular, by the EXTRADRIVERS and
+EXTRAAUTHENTICATORS variables.
+
+     Drivers are code modules that support different mailbox storage
+technologies.  By default, all drivers are enabled.  There is little
+benefit to be gained by disabling a driver, with one exception.  The
+mbox driver implements the behavior of automatically moving new mail
+from the spool directory to the "mbox" file on the user's home
+directory, if and *only* if the "mbox" exists and is in mailbox
+format.  The mbox driver is listed under EXTRADRIVERS; if you wish to
+disable it just remove it from that list and rebuild.
+
+     Authenticators are code modules that support authentication
+technology for the server (password file lookup, Kerberos, S/Key,
+etc.).  EXTRAAUTHENTICATORS is used to add an authenticator.  This
+subject can be complex; find a wizard if you can't figure it out.
+
+     It is also possible to add your own drivers and authenticators.
+This is a topic for wizards, and is beyond the scope of this text.
+
+			NT Configuration Notes
+
+     This software is not plug-and-play on NT.  If you're not a hacker
+and/or are unwilling to invest the time to do some programming, you
+probably want to buy a commercial server for NT.
+
+     The primary issue that you need to deal with is the format of
+mail, where the INBOX is located, and where secondary folders are
+located.  As distributed, the software supports mail in the default
+format used on UNIX (unix format) as well as mbx, mtx, and tenex
+formats.  mbx format is encouraged if at all possible; mtx and tenex
+format are for compatibility with the past.  However, it all depends
+upon how and where your SMTP server delivers mail.
+
+     To change the default mailbox format, edit the symbol
+DEFAULTDRIVER in:
+	../src/osdep/nt/makefile.nt
+or
+	../src/osdep/nt/makefile.ntk
+To change the default location of INBOX, edit the file:
+	../src/osdep/nt/mailfile.h
+Virtually everything else having to do with environment that you are
+likely to want to modify can be found in the source file:
+	.../src/osdep/nt/env_nt.c
+In particular, special attention should be given to the routines:
+ env_init()		initialize c-client environment variables,
+			especially the user name and home directory
+ sysinbox()		return the NT path of the INBOX in which
+			mail delivery will place mail
+ mailboxdir()		translate a mailbox name into the associated
+			NT directory for listing
+ mailboxfile()		translate a mailbox name into the associated
+			NT file for opening
+
+     You should modify these routines as necessary.  The most common
+modifications are to env_init(), to modify the software's idea of the
+home directory (which is used everywhere as the default directory),
+and to sysinbox(), to modify where the software looks for
+newly-delivered mail.
+
+     There are two other build-time configuration issues which you may
+need to consider: drivers and authenticators.  Both of these are set
+up in the top-level Makefile -- in particular, by the EXTRADRIVERS and
+EXTRAAUTHENTICATORS variables.
+
+     Drivers are code modules that support different mailbox storage
+technologies.  By default, all drivers are enabled.  There is little
+benefit to be gained by disabling a driver.
+
+     Authenticators are code modules that support authentication
+technology for the server (password file lookup, Kerberos, S/Key,
+etc.).  EXTRAAUTHENTICATORS is used to add an authenticator.  This
+subject can be complex; find a wizard if you can't figure it out.
+
+     It is also possible to add your own drivers and authenticators.