the IMAP server. If you want to access another mail folder at the IMAP
server, you should use <tt>{imapserver}path/to/folder</tt> where
<tt>path/to/folder</tt> is the path of the folder you want to access
-relative to your home directory.
+(relative to your home directory if you aren't using Cyrus).
You can select an alternative port by specifying it with the server, ie:
<tt/{imapserver:port}inbox/.
<em/toggle-subscribed/ command. See also the
<ref id="imap_list_subscribed" name="$imap_list_subscribed"> variable.
-Mutt was designed to work with IMAP4rev1 servers, and has been tested
+Polling for new mail is more expensive over IMAP than locally. For this reason
+the frequency at which Mutt will check for mail remotely can be controlled by
+the
+<ref id="imap_checkinterval" name="$imap_checkinterval">
+variable, which defaults to every 60 seconds.
+
+Mutt is designed to work with IMAP4rev1 servers, and was originally tested
with both the UWash IMAP server v11.241 and the Cyrus IMAP server v1.5.14.
-Note that if you are using mbox as the mail store on the UWash server,
-the server will disconnect a client if another client selects the same
-folder.
+Nowadays it is primarily developed against UW-IMAP 12.250. It works
+more-or-less correctly against Cyrus 1.6.11, though there are a few minor
+quirks in the folder browser.
+
+Note that if you are using mbox as the mail store on UW servers prior to
+v12.250, the server has been reported to disconnect a client if another client
+selects the same folder.
+
+<sect2>Authentication
+<p>
-Mutt currently does not support completion of IMAP folder names. Hit
-the <em/complete/ key again to go to the IMAP browser.
+Mutt supports three authentication methods with IMAP servers: GSSAPI, CRAM-MD5,
+and LOGIN (there is a patch by Grant Edwards to add NTLM authentication for you
+poor exchange users out there, but it has yet to be integrated into the main
+tree). Mutt will try whichever methods are available on the server, in order from
+most secure to least. That is, mutt will first try GSSAPI authentication (ie
+Kerberos V), then CRAM-MD5, and finally LOGIN (the worst possible choice - your
+password travels across the net in the clear).
+
+There are a few variables which control authentication:
+<itemize>
+<item><ref id="imap_user" name="$imap_user"> - controls the
+ username under which you request authentication on the IMAP server, for all
+ authenticators.
+<item><ref id="imap_pass" name="$imap_pass"> - the password
+ to use to authenticate you using the LOGIN method. If this is set, and other
+ methods fail, Mutt will use this without asking you. So if you use GSSAPI
+ or CRAM-MD5, don't set this variable.
+<item><ref id="imap_cramkey" name="$imap_cramkey"> - the
+ secret used in CRAM-MD5 authentication (ie your CRAM password). If this is
+ not set and your server supports CRAM-MD5, Mutt will prompt you for it.
+</itemize>
<bf/Note:/ The IMAP support has had very limited testing due to a lack
of developers using it. It should work with the reference servers