			   SSL IMAP Patchkit
			     14 July 1999
			     Mark Crispin

			 * * * * * * * * * *
Export Regulations. Software, including technical data, is subject to U.S.
export control laws, including the U.S. Export Administration Act and its
associated regulations, and may be subject to export or import regulations
in other countries. Licensee agrees to comply strictly with all such
regulations and acknowledges that it has the responsibility to obtain
licenses to export, re-export, or import Software. Software may not be
downloaded, or otherwise exported or re-exported (i) into, or to a
national or resident of, Cuba, Iraq, Iran, North Korea, Libya, Sudan,
Syria or any country to which the U.S. has embargoed goods; or (ii) to
anyone on the U.S. Treasury Department's list of Specially Designated
Nations or the U.S. Commerce Department's Table of Denial Orders.
			 * * * * * * * * * *

     The SSL IMAP toolkit consists of a set of modules and patches to
the IMAP toolkit to enable SSL (also known as TLS) support in the
client code in c-client and the server code in ipop3d and imapd.

     This applies only for imap-4.7 series.  SSL support is fully
integrated in imap-2000.

     To build the SSL IMAP toolkit, put the IMAP toolkit at the same
directory level as this directory (e.g. "simap" and "imap-4.7c" should
be in the same directory).  Then, inside simap, do the same make
command that you would have done inside imap-4.7c.

     For example, if you normally build the IMAP toolkit with Kerberos
V enabled as extra authenticators on a Linux system with PAM, you
would do the same
	make lnp EXTRAAUTHENTICATORS=gss
that you would normally do.  Don't include ssl inside
EXTRAAUTHENTICATORS since the SSL toolkit will do this for you.

     Similarly, on Windows, do "nmake nt" or "nmake ntk" (Kerberos V)
as appropriate.  However, we encourage you to do Windows development
using imap-2000 (which has SSL integrated and Windows 2000 support)
instead.
