If Mutt was compiled with IMAP support (by running the configure script with the --enable-imap flag), it has the ability to work with folders located on a remote IMAP server.
You can access the remote inbox by selecting the folder
imap://imapserver/INBOX
, where imapserver
is the name of the
IMAP server and INBOX
is the special name for your spool mailbox on
the IMAP server. If you want to access another mail folder at the IMAP
server, you should use imap://imapserver/path/to/folder
where
path/to/folder
is the path of the folder you want to access.
You can select an alternative port by specifying it with the server, ie:
imap://imapserver:port/INBOX
.
You can also specify different username for each folder, ie:
imap://username@imapserver[:port]/INBOX
.
If Mutt was compiled with SSL support (by running the configure
script with the --with-ssl flag), connections to IMAP servers
can be encrypted. This naturally requires that the server supports
SSL encrypted connections. To access a folder with IMAP/SSL, you should
use imaps://[username@]imapserver[:port]/path/to/folder
as your
folder path.
Pine-compatible notation is also supported, ie
{[username@]imapserver[:port][/ssl]}path/to/folder
Note that not all servers use / as the hierarchy separator. Mutt should correctly notice which separator is being used by the server and convert paths accordingly.
When browsing folders on an IMAP server, you can toggle whether to look at only the folders you are subscribed to, or all folders with the toggle-subscribed command. See also the $imap_list_subscribed variable.
Polling for new mail on an IMAP server can cause noticeable delays. So, you'll want to carefully tune the $mail_check and $timeout variables. Personally I use
set mail_check=90
set timeout=15
with relatively good results over my slow modem line.
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.