--enable-imap
enable IMAP support
+--with-gss[=PFX]
+ Enable GSSAPI authentication to IMAP servers. This should work with
+ both MIT and Heimdal GSSAPI implementations - others haven't been
+ tested. Note that the Cyrus SASL library also supports GSSAPI,
+ and may be able to encrypt your session with it - you should use
+ SASL instead if you can.
+
--with-ssl[=PFX]
- enable SSL support with IMAP. SSL support requires you to have
- OpenSSL headers and libraries properly installed before
+ enable SSL support with IMAP and POP. SSL support requires you to
+ have OpenSSL headers and libraries properly installed before
compiling. If the OpenSSL headers and libraries are not in the
default system pats you can use the optional PFX argument to
define the root directory of your installation. The libraries
are then expected to be found in PFX/lib and headers in
PFX/include/openssl.
+--with-sasl[=PFX]
+ Use the Cyrus SASL library for IMAP or POP authentication. This
+ library provides generic support for several authentication methods,
+ and more may be added by the system administrator without recompiling
+ mutt. SASL may also be able to encrypt your mail session even if
+ SSL is not available.
+
--disable-nls
This switch disables mutt's native language support.
-----------
If you want to have SSL support in mutt, you need to install OpenSSL
(http://www.openssl.org) libraries and headers before compiling.
-OpenSSL versions 0.9.3 and 0.9.4 have been tested.
+OpenSSL versions 0.9.3 through 0.9.6a have been tested.
For SSL support to be enabled, you need to run the ``configure''
script with ``--enable-imap --with-ssl[=PFX]'' parameters. If the
Usage
-----
IMAP/SSL folders can be accessed just like normal IMAP folders, but you
-will also have to add '/ssl' before the closing curly brace.
+will also have to add '/ssl' before the closing curly brace. Or you can
+use IMAP url notation, where the methods is called imaps.
For example:
mailboxes {localhost/ssl}inbox
mailboxes {localhost:994/ssl}inbox
-
+or
+ mailboxes imaps://localhost/inbox
+ mailboxes imaps://localhost:994/inbox
If you get errors about lack of entropy, it means that Mutt was unable
to find a source of random data to initialize SSL library with. Should
this happen, you need to generate the data yourself and save it in a
-file pointed by $SslEntropyFile or $RANDFILE (environment) variables or
+file pointed by $entropy_file or $RANDFILE (environment) variables or
in ~/.rnd.
One way to generate random data would be to run a command which
** is run so don't put anything you can't afford to lose in that file.
The files Mutt will try to use to initialize SSL library with are files
-pointed by $SslEntropyFile and $RANDFILE (or ~/.rnd if unset.) If your
+pointed by $entropy_file and $RANDFILE (or ~/.rnd if unset.) If your
OpenSSL is version 0.9.5 or later, the previous files can also be EGD
sockets (see http://www.lothar.com/tech/crypto/ for more information
about Entropy Gathering Daemon) and in addition sockets in the following