* Update to version 2.19.1

 *  Upgrade UW-IMAP to Panda IMAP from https://github.com/jonabbey/panda-imap.
 *  Replace tabs by spaces in From and Subject fields to control for size in
    screen of these fields. Change only in index screen display.

1 files changed, 49 insertions, 55 deletions

diff --git a/imap/docs/BUILD b/imap/docs/BUILD
index e094e065..e9492c81 100644
--- a/imap/docs/BUILD
+++ b/imap/docs/BUILD
@@ -1,5 +1,6 @@
 /* ========================================================================
  * Copyright 1988-2007 University of Washington
+ * Copyright 2008-2011 Mark Crispin
  *
  * Licensed under the Apache License, Version 2.0 (the "License");
  * you may not use this file except in compliance with the License.
@@ -12,15 +13,14 @@
  */
 
 			 BUILD AND INSTALLATION NOTES
-			 Last Updated: 15 November 2007
+			 Last Updated: 15 April 2013
 
 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)
+5. Other ports (TOPS-20, VMS, Macintosh, DOS/Win16, Windows CE, Amiga, OS/2)
 
 
 			       UNIX BUILD NOTES
@@ -38,12 +38,12 @@ the SSLBUILD file for more information.
 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
+     You must build through the top-level panda-imap/Makefile, which will run
+a "process" step the first time and create the panda-imap/c-client,
+panda-imap/ipopd, and panda-imap/imapd directories in which building actually
 takes place.
 
-     Before doing a make on UNIX, you should read imap-2007/Makefile and see
+     Before doing a make on UNIX, you should read panda-imap/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,
@@ -55,7 +55,7 @@ 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.
+     There are other make options, described in panda-imap/src/osdep/Makefile.
 
      It's probably best to see if an existing port will work on your system
 before inventing a new port.  Try:
@@ -65,7 +65,7 @@ before inventing a new port.  Try:
 	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
+panda-imap/Makefile and panda-imap/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
@@ -91,10 +91,10 @@ 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
+	panda-imap/mtest/mtest		c-client testbed program
+	panda-imap/ipopd/ipop2d		POP2 daemon
+	panda-imap/ipopd/ipop3d		POP3 daemon
+	panda-imap/imapd/imapd		IMAP4rev1 daemon
 
      mtest is normally not used except by c-client developers.
 
@@ -272,11 +272,11 @@ 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
+the definition of MAILFILE in panda-imap/src/osdep/nt/mailfile.h and at the
+sysinbox() function in panda-imap/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
+     To build under Windows 95/98/NT, connect to the panda-imap directory
 and do:
 	nmake -f makefile.nt
 The resulting binaries will support SSL if either schannel.dll or
@@ -284,7 +284,7 @@ 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
+     To build with MIT Kerberos support, connect to the panda-imap directory
 and do:
 	nmake -f makefile.ntk
 The resulting binaries will support SSL if either schannel.dll or
@@ -293,7 +293,7 @@ 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
+     To build under Windows Me/2000/XP, connect to the panda-imap directory
 and do:
 	nmake -f makefile.w2k
 The resulting binaries will support SSL and Microsoft Kerberos, using the
@@ -303,10 +303,10 @@ 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
+	panda-imap\mtest\mtest.exe	(testbed client)
+	panda-imap\ipopd\ipop2d.exe	POP2 server
+	panda-imap\ipopd\ipop3d.exe	POP3 server
+	panda-imap\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:
@@ -331,14 +331,21 @@ It is based on inetlisn, and essentially is a "completed" version of inetlisn.
 are unwilling to invest the time to do some programming, you probably want to
 buy a commercial server product.
 
-				INACTIVE PORTS
+				 OTHER 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.
+     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
+  ----		------
+TOPS-20		Unsupported since Mark's passing
+VMS		Unsupported since Mark's passing
+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
 
 			     TOPS-20 BUILD NOTES
 
@@ -347,10 +354,10 @@ 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
+     You do not use panda-imap/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
+panda-imap/src/c-client, panda-imap/src/charset, panda-imap/src/mtest, and
+panda-imap/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
@@ -359,14 +366,14 @@ BATCON execute it.
 
 			       VMS BUILD NOTES
 
-      The VMS port has been tested with imap-2007, but as I am soon going
+      The VMS port has been tested with panda-imap, 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
+      You do not use panda-imap/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.
+panda-imap/src/c-client, panda-imap/src/charset, panda-imap/src/mtest, and
+panda-imap/src/osdep/vms onto a single directory on VMS and build from that.
 The command to build it is:
 	@BUILD MULTINET
 or	@BUILD NETLIB
@@ -379,20 +386,7 @@ 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
 
@@ -401,10 +395,10 @@ OS/2		Unknown
      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
+     You do not use panda-imap/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
+panda-imap/src/c-client, panda-imap/src/charset, panda-imap/src/mtest, and
+panda-imap/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.
 
@@ -451,10 +445,10 @@ 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
+      You do not use panda-imap/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.
+panda-imap/src/c-client, panda-imap/src/charset, panda-imap/src/mtest, and
+panda-imap/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)
@@ -474,7 +468,7 @@ least install Win32s.
      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:
+     To build under NT, connect to the panda-imap directory and do:
 	nmake -f makefile.wce
 
      The only binary produced is a cclient.lib file.  I haven't gotten as far