« back to all changes in this revision
Viewing changes to doc/optionalfeatures.html
- browse files at revision 31
- compare with another revision
- download diff
- download tarball
- view history from revision 31
- Committer: Package Import Robot
- Author(s): أحمد المحمودي (Ahmed El-Mahmoudy)
- Date: 2010-12-17 14:28:28 UTC
- mfrom: (16.2.3 experimental)
- Revision ID: package-import@ubuntu.com-20101217142828-ve8yy0xf1zomtnx9
Tags: 1.5.21-1ubuntu1
* Merge with Debian experimental (LP: #691512), remaining changes:
+ debian/control, debian/patches/debian-specific/build_doc_adjustments.diff:
Use w3m (main) instead of elinks (universe) for generating documentation.
+ Drop libtokyocabinet-dev (universe) from Build-Depends, use always
libgdbm-dev and also use gdbm for the header cache backend. (lp: #607448)
+ debian/control, debian/patches/debian-specific/build_doc_adjustments.diff:
Use w3m (main) instead of elinks (universe) for generating documentation.
+ Drop libtokyocabinet-dev (universe) from Build-Depends, use always
libgdbm-dev and also use gdbm for the header cache backend. (lp: #607448)
- files added:
- debian/patches/features/imap_fast_trash
- files modified:
- ChangeLog
added
removed
doc/optionalfeatures.html
1
1
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2
2
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Optional Features</title><meta name="generator" content="DocBook XSL Stylesheets V1.74.3" /><link rel="home" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="mimesupport.html" title="Chapter 5. Mutt's MIME Support" /><link rel="next" href="security.html" title="Chapter 7. Security Considerations" /><style xmlns="" type="text/css">
3
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Optional Features</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="mimesupport.html" title="Chapter 5. Mutt's MIME Support" /><link rel="next" href="security.html" title="Chapter 7. Security Considerations" /><style xmlns="" type="text/css">
4
4
body { margin-left:2%; margin-right:2%; font-family:serif; }
5
5
.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
6
6
h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
22
22
div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
23
23
div.note h3:after { content: ":" }
24
24
div.note { margin-bottom: 5px; }
25
strong.command { font-family: monospace; font-weight: normal; }
25
.command { font-family: monospace; font-weight: normal; }
26
.command strong { font-weight: normal; }
26
27
tr { vertical-align: top; }
28
.comment { color:#707070; }
27
29
28
</style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Optional Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional Features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="optionalfeatures.html#optionalfeatures-notes">1. General Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#compile-time-features">1.1. Enabling/Disabling Features</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#url-syntax">1.2. URL Syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#imap-browser">4.1. The IMAP Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#account-hook">6. Managing Multiple Accounts</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#caching">7. Local Caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#header-caching">7.1. Header Caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#body-caching">7.2. Body Caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#exact-address">8. Exact Address Generation</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#sending-mixmaster">9. Sending Anonymous Messages via Mixmaster</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General Notes</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/Disabling Features</h3></div></div></div><p>
30
</style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Optional Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr></table><hr /></div><div class="chapter" title="Chapter 6. Optional Features"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional Features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="optionalfeatures.html#optionalfeatures-notes">1. General Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#compile-time-features">1.1. Enabling/Disabling Features</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#url-syntax">1.2. URL Syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#imap-browser">4.1. The IMAP Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#account-hook">6. Managing Multiple Accounts</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#caching">7. Local Caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#header-caching">7.1. Header Caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#body-caching">7.2. Body Caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#cache-dirs">7.3. Cache Directories</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#maint-cache">7.4. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#exact-address">8. Exact Address Generation</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#sending-mixmaster">9. Sending Anonymous Messages via Mixmaster</a></span></dt></dl></div><div class="sect1" title="1. General Notes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General Notes</h2></div></div></div><div class="sect2" title="1.1. Enabling/Disabling Features"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/Disabling Features</h3></div></div></div><p>
29
31
Mutt supports several of optional features which can be enabled or
30
disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script
31
certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of
32
the <span class="emphasis"><em>configure --help</em></span> output.
32
disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span>
33
script certain arguments. These are listed in the <span class="quote">“<span class="quote">Optional
34
features</span>”</span> section of the <span class="emphasis"><em>configure --help</em></span>
35
output.
33
36
</p><p>
34
37
Which features are enabled or disabled can later be determined from the
35
38
output of <code class="literal">mutt -v</code>. If a compile option starts with
36
“<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if
37
Mutt was compiled using GnuTLS for encrypted communication instead of
38
OpenSSL, <code class="literal">mutt -v</code> would contain:
39
<span class="quote">“<span class="quote">+</span>”</span> it is enabled and disabled if prefixed with
40
<span class="quote">“<span class="quote">-</span>”</span>. For example, if Mutt was compiled using GnuTLS for
41
encrypted communication instead of OpenSSL, <code class="literal">mutt -v</code>
42
would contain:
39
43
</p><pre class="screen">
40
-USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL Syntax</h3></div></div></div><p>
44
-USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" title="1.2. URL Syntax"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL Syntax</h3></div></div></div><p>
41
45
Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
42
46
to access servers using URLs. The canonical syntax for specifying URLs
43
in Mutt is (an item enclosed in <code class="literal">[]</code> means it is optional and
44
may be omitted):
47
in Mutt is (an item enclosed in <code class="literal">[]</code> means it is
48
optional and may be omitted):
45
49
</p><pre class="screen">
46
proto[s]://[username[:password]@]server[:port]/[path]
50
proto[s]://[username[:password]@]server[:port][/path]
47
51
</pre><p>
48
52
<span class="emphasis"><em>proto</em></span> is the communication protocol:
49
53
<code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and
50
<code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure
51
communication</span>” is appended, Mutt will attempt to establish an
54
<code class="literal">smtp</code> for SMTP. If <span class="quote">“<span class="quote">s</span>”</span> for <span class="quote">“<span class="quote">secure
55
communication</span>”</span> is appended, Mutt will attempt to establish an
52
56
encrypted communication using SSL or TLS.
53
57
</p><p>
54
58
Since all protocols supported by Mutt support/require authentication,
55
59
login credentials may be specified in the URL. This has the advantage
56
60
that multiple IMAP, POP3 or SMTP servers may be specified (which isn't
57
possible using, for example,
58
<a class="link" href="reference.html#imap-user" title="3.109. imap_user">$imap_user</a>). The username
59
may contain the “<span class="quote">@</span>” symbol being used by many mail systems
60
as part of the login name. A password can be given, too but is not
61
recommended if the URL is specified in a configuration file on disk.
61
possible using, for example, <a class="link" href="reference.html#imap-user" title="3.109. imap_user">$imap_user</a>). The username may contain the
62
<span class="quote">“<span class="quote">@</span>”</span> symbol being used by many mail systems as part of the
63
login name. The special characters <span class="quote">“<span class="quote">/</span>”</span>
64
(<code class="literal">%2F</code>), <span class="quote">“<span class="quote">:</span>”</span> (<code class="literal">%3A</code>) and
65
<span class="quote">“<span class="quote">%</span>”</span> (<code class="literal">%25</code>) have to be URL-encoded in
66
usernames using the <code class="literal">%</code>-notation.
67
</p><p>
68
A password can be given, too but is not recommended if the URL is
69
specified in a configuration file on disk.
62
70
</p><p>
63
71
If no port number is given, Mutt will use the system's default for the
64
72
given protocol (usually consulting <code class="literal">/etc/services</code>).
65
73
</p><p>
66
The optional path is only relevant for IMAP.
74
The optional path is only relevant for IMAP and ignored elsewhere.
67
75
</p><div class="example"><a id="ex-url"></a><p class="title"><b>Example 6.1. URLs</b></p><div class="example-contents"><pre class="screen">
68
76
pops://host/
69
77
imaps://user@host/INBOX/Sent
70
78
smtp://user@host:587/
71
</pre></div></div><br class="example-break" /></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
79
</pre></div></div><br class="example-break" /></div></div><div class="sect1" title="2. SSL/TLS Support"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
72
80
If Mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
73
compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
74
by running the <span class="emphasis"><em>configure</em></span> script with the
81
compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( by
82
running the <span class="emphasis"><em>configure</em></span> script with the
75
83
<span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or
76
84
<span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then
77
85
attempt to encrypt communication with remote servers if these protocols
78
are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.
79
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
80
If Mutt is compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
81
script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
82
with mailboxes located on a remote POP3 server and fetch mail for local
86
are suffixed with <span class="quote">“<span class="quote">s</span>”</span> for <span class="quote">“<span class="quote">secure
87
communication</span>”</span>.
88
</p></div><div class="sect1" title="3. POP3 Support"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
89
If Mutt is compiled with POP3 support (by running the
90
<span class="emphasis"><em>configure</em></span> script with the
91
<span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work with
92
mailboxes located on a remote POP3 server and fetch mail for local
83
93
browsing.
84
94
</p><p>
85
Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol
86
for unencrypted and <code class="literal">pops</code> for encrypted
87
communication, see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL Syntax">Section 1.2, “URL Syntax”</a> for details.
95
Remote POP3 servers can be accessed using URLs with the
96
<code class="literal">pop</code> protocol for unencrypted and
97
<code class="literal">pops</code> for encrypted communication, see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL Syntax">Section 1.2, “URL Syntax”</a> for details.
88
98
</p><p>
89
99
Polling for new mail is more expensive over POP3 than locally. For this
90
100
reason the frequency at which Mutt will check for mail remotely can be
91
controlled by the
92
<a class="link" href="reference.html#pop-checkinterval" title="3.187. pop_checkinterval">$pop_checkinterval</a>
93
variable, which defaults to every 60 seconds.
101
controlled by the <a class="link" href="reference.html#pop-checkinterval" title="3.188. pop_checkinterval">$pop_checkinterval</a> variable, which
102
defaults to every 60 seconds.
94
103
</p><p>
95
104
POP is read-only which doesn't allow for some features like editing
96
messages or changing flags. However, using
97
<a class="xref" href="optionalfeatures.html#header-caching" title="7.1. Header Caching">Section 7.1, “Header Caching”</a> and <a class="xref" href="optionalfeatures.html#body-caching" title="7.2. Body Caching">Section 7.2, “Body Caching”</a>
98
Mutt simulates the new/old/read flags as well as flagged and replied.
99
Mutt applies some logic on top of remote messages but cannot change
100
them so that modifications of flags are lost when
101
messages are downloaded from the POP server (either by Mutt or other
102
tools).
105
messages or changing flags. However, using <a class="xref" href="optionalfeatures.html#header-caching" title="7.1. Header Caching">Section 7.1, “Header Caching”</a> and <a class="xref" href="optionalfeatures.html#body-caching" title="7.2. Body Caching">Section 7.2, “Body Caching”</a> Mutt
106
simulates the new/old/read flags as well as flagged and replied. Mutt
107
applies some logic on top of remote messages but cannot change them so
108
that modifications of flags are lost when messages are downloaded from
109
the POP server (either by Mutt or other tools).
103
110
</p><a id="fetch-mail"></a><p>
104
Another way to access your POP3 mail is the <code class="literal"><fetch-mail></code> function
105
(default: G). It allows to connect to <a class="link" href="reference.html#pop-host" title="3.189. pop_host">$pop_host</a>, fetch all your new mail and place it in the
106
local <a class="link" href="reference.html#spoolfile" title="3.269. spoolfile">$spoolfile</a>. After this
107
point, Mutt runs exactly as if the mail had always been local.
108
</p><div class="note"><h3 class="title">Note</h3><p>
109
If you only need to fetch all messages to a
110
local mailbox you should consider using a specialized program, such as
111
<code class="literal">fetchmail(1)</code>, <code class="literal">getmail(1)</code> or similar.
112
</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
113
If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>
114
script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
111
Another way to access your POP3 mail is the
112
<code class="literal"><fetch-mail></code> function (default: G). It allows
113
to connect to <a class="link" href="reference.html#pop-host" title="3.190. pop_host">$pop_host</a>, fetch all your
114
new mail and place it in the local <a class="link" href="reference.html#spoolfile" title="3.270. spoolfile">$spoolfile</a>. After this point, Mutt runs
115
exactly as if the mail had always been local.
116
</p><div class="note" title="Note"><h3 class="title">Note</h3><p>
117
If you only need to fetch all messages to a local mailbox you should
118
consider using a specialized program, such as
119
<code class="literal">fetchmail(1)</code>, <code class="literal">getmail(1)</code> or
120
similar.
121
</p></div></div><div class="sect1" title="4. IMAP Support"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
122
If Mutt was compiled with IMAP support (by running the
123
<span class="emphasis"><em>configure</em></span> script with the
124
<span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
115
125
with folders located on a remote IMAP server.
116
126
</p><p>
117
You can access the remote inbox by selecting the folder by its URL
118
(see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL Syntax">Section 1.2, “URL Syntax”</a> for details) using the
127
You can access the remote inbox by selecting the folder by its URL (see
128
<a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL Syntax">Section 1.2, “URL Syntax”</a> for details) using the
119
129
<code class="literal">imap</code> or <code class="literal">imaps</code> protocol.
120
Alternatively, a pine-compatible notation is also supported, ie
130
Alternatively, a pine-compatible notation is also supported, i.e.
121
131
<code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>
122
132
</p><p>
123
Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should
124
correctly notice which separator is being used by the server and convert
125
paths accordingly.
133
Note that not all servers use <span class="quote">“<span class="quote">/</span>”</span> as the hierarchy
134
separator. Mutt should correctly notice which separator is being used
135
by the server and convert paths accordingly.
126
136
</p><p>
127
137
When browsing folders on an IMAP server, you can toggle whether to look
128
138
at only the folders you are subscribed to, or all folders with the
129
<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the
130
<a class="link" href="reference.html#imap-list-subscribed" title="3.102. imap_list_subscribed">$imap_list_subscribed</a> variable.
139
<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the <a class="link" href="reference.html#imap-list-subscribed" title="3.102. imap_list_subscribed">$imap_list_subscribed</a> variable.
131
140
</p><p>
132
Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
133
want to carefully tune the
134
<a class="link" href="reference.html#mail-check" title="3.118. mail_check">$mail_check</a>
135
and
136
<a class="link" href="reference.html#timeout" title="3.291. timeout">$timeout</a>
137
variables. Reasonable values are:
141
Polling for new mail on an IMAP server can cause noticeable delays. So,
142
you'll want to carefully tune the <a class="link" href="reference.html#mail-check" title="3.118. mail_check">$mail_check</a> and <a class="link" href="reference.html#timeout" title="3.292. timeout">$timeout</a> variables. Reasonable values are:
138
143
</p><pre class="screen">
139
144
set mail_check=90
140
145
set timeout=15
141
146
</pre><p>
142
147
with relatively good results even over slow modem lines.
143
</p><div class="note"><h3 class="title">Note</h3><p>
148
</p><div class="note" title="Note"><h3 class="title">Note</h3><p>
144
149
Note that if you are using mbox as the mail store on UW servers prior to
145
v12.250, the server has been reported to disconnect a client if another client
146
selects the same folder.
147
</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The IMAP Folder Browser</h3></div></div></div><p>
150
v12.250, the server has been reported to disconnect a client if another
151
client selects the same folder.
152
</p></div><div class="sect2" title="4.1. The IMAP Folder Browser"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The IMAP Folder Browser</h3></div></div></div><p>
148
153
As of version 1.2, Mutt supports browsing mailboxes on an IMAP
149
154
server. This is mostly the same as the local file browser, with the
150
155
following differences:
151
</p><div class="itemizedlist"><ul type="disc"><li><p>
152
In lieu of file permissions, Mutt displays the string “<span class="quote">IMAP</span>”,
153
possibly followed by the symbol “<span class="quote">+</span>”, indicating
154
that the entry contains both messages and subfolders. On
156
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
157
In lieu of file permissions, Mutt displays the string
158
<span class="quote">“<span class="quote">IMAP</span>”</span>, possibly followed by the symbol <span class="quote">“<span class="quote">+</span>”</span>,
159
indicating that the entry contains both messages and subfolders. On
155
160
Cyrus-like servers folders will often contain both messages and
156
161
subfolders.
157
</p></li><li><p>
158
For the case where an entry can contain both messages and
159
subfolders, the selection key (bound to <code class="literal">enter</code> by default)
160
will choose to descend into the subfolder view. If you wish to view
161
the messages in that folder, you must use <code class="literal">view-file</code> instead
162
(bound to <code class="literal">space</code> by default).
163
</p></li><li><p>
162
</p></li><li class="listitem"><p>
163
For the case where an entry can contain both messages and subfolders,
164
the selection key (bound to <code class="literal">enter</code> by default) will
165
choose to descend into the subfolder view. If you wish to view the
166
messages in that folder, you must use <code class="literal">view-file</code>
167
instead (bound to <code class="literal">space</code> by default).
168
</p></li><li class="listitem"><p>
164
169
You can create, delete and rename mailboxes with the
165
<code class="literal"><create-mailbox></code>, <code class="literal"><delete-mailbox></code>, and
166
<code class="literal"><rename-mailbox></code> commands (default bindings: <code class="literal">C</code>,
167
<code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also
168
<code class="literal"><subscribe></code> and <code class="literal"><unsubscribe></code> to mailboxes (normally
169
these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
170
</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
170
<code class="literal"><create-mailbox></code>,
171
<code class="literal"><delete-mailbox></code>, and
172
<code class="literal"><rename-mailbox></code> commands (default bindings:
173
<code class="literal">C</code>, <code class="literal">d</code> and <code class="literal">r</code>,
174
respectively). You may also <code class="literal"><subscribe></code> and
175
<code class="literal"><unsubscribe></code> to mailboxes (normally these are
176
bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
177
</p></li></ul></div></div><div class="sect2" title="4.2. Authentication"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
171
178
Mutt supports four authentication methods with IMAP servers: SASL,
172
179
GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
173
180
NTLM authentication for you poor exchange users out there, but it has
174
yet to be integrated into the main tree). There is also support for
175
the pseudo-protocol ANONYMOUS, which allows you to log in to a public
176
IMAP server without having an account. To use ANONYMOUS, simply make
177
your username blank or “<span class="quote">anonymous</span>”.
178
</p><p>
179
SASL is a special super-authenticator, which selects among several protocols
180
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure
181
method available on your host and the server. Using some of these methods
182
(including DIGEST-MD5 and possibly GSSAPI), your entire session will be
183
encrypted and invisible to those teeming network snoops. It is the best
184
option if you have it. To use it, you must have the Cyrus SASL library
185
installed on your system and compile Mutt with the <span class="emphasis"><em>--with-sasl</em></span> flag.
186
</p><p>
187
Mutt will try whichever methods are compiled in and available on the server,
188
in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
181
yet to be integrated into the main tree). There is also support for the
182
pseudo-protocol ANONYMOUS, which allows you to log in to a public IMAP
183
server without having an account. To use ANONYMOUS, simply make your
184
username blank or <span class="quote">“<span class="quote">anonymous</span>”</span>.
185
</p><p>
186
SASL is a special super-authenticator, which selects among several
187
protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the
188
most secure method available on your host and the server. Using some of
189
these methods (including DIGEST-MD5 and possibly GSSAPI), your entire
190
session will be encrypted and invisible to those teeming network
191
snoops. It is the best option if you have it. To use it, you must have
192
the Cyrus SASL library installed on your system and compile Mutt with
193
the <span class="emphasis"><em>--with-sasl</em></span> flag.
194
</p><p>
195
Mutt will try whichever methods are compiled in and available on the
196
server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5,
197
LOGIN.
189
198
</p><p>
190
199
There are a few variables which control authentication:
191
</p><div class="itemizedlist"><ul type="disc"><li><p>
192
<a class="link" href="reference.html#imap-user" title="3.109. imap_user">$imap_user</a> - controls
193
the username under which you request authentication on the IMAP server,
194
for all authenticators. This is overridden by an explicit username in
195
the mailbox path (ie by using a mailbox name of the form
200
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
201
<a class="link" href="reference.html#imap-user" title="3.109. imap_user">$imap_user</a> - controls the username
202
under which you request authentication on the IMAP server, for all
203
authenticators. This is overridden by an explicit username in the
204
mailbox path (i.e. by using a mailbox name of the form
196
205
<code class="literal">{user@host}</code>).
197
</p></li><li><p>
198
<a class="link" href="reference.html#imap-pass" title="3.104. imap_pass">$imap_pass</a> - a
199
password which you may preset, used by all authentication methods where
200
a password is needed.
201
</p></li><li><p>
202
<a class="link" href="reference.html#imap-authenticators" title="3.96. imap_authenticators">$imap_authenticators</a> - a colon-delimited list of IMAP
203
authentication methods to try, in the order you wish to try them. If
204
specified, this overrides Mutt's default (attempt everything, in the order
205
listed above).
206
</p></li></ul></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
206
</p></li><li class="listitem"><p>
207
<a class="link" href="reference.html#imap-pass" title="3.104. imap_pass">$imap_pass</a> - a password which you may
208
preset, used by all authentication methods where a password is needed.
209
</p></li><li class="listitem"><p>
210
<a class="link" href="reference.html#imap-authenticators" title="3.96. imap_authenticators">$imap_authenticators</a> - a
211
colon-delimited list of IMAP authentication methods to try, in the order
212
you wish to try them. If specified, this overrides Mutt's default
213
(attempt everything, in the order listed above).
214
</p></li></ul></div></div></div><div class="sect1" title="5. SMTP Support"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
207
215
Besides supporting traditional mail delivery through a
208
216
sendmail-compatible program, Mutt supports delivery through SMTP if it
209
217
was configured and built with <code class="literal">--enable-smtp</code>.
210
218
</p><p>
211
If the configuration variable
212
<a class="link" href="reference.html#smtp-url" title="3.262. smtp_url">$smtp_url</a> is set, Mutt
213
will contact the given SMTP server to deliver messages; if it is unset,
214
Mutt will use the program specified by <a class="link" href="reference.html#sendmail" title="3.230. sendmail">$sendmail</a>.
219
If the configuration variable <a class="link" href="reference.html#smtp-url" title="3.263. smtp_url">$smtp_url</a>
220
is set, Mutt will contact the given SMTP server to deliver messages; if
221
it is unset, Mutt will use the program specified by <a class="link" href="reference.html#sendmail" title="3.231. sendmail">$sendmail</a>.
215
222
</p><p>
216
223
For details on the URL syntax, please see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL Syntax">Section 1.2, “URL Syntax”</a>.
217
224
</p><p>
218
The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol
219
using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
220
for SASL are specified in <a class="link" href="reference.html#smtp-authenticators" title="3.260. smtp_authenticators">$smtp_authenticators</a>
221
defaulting to an empty list which makes Mutt try all available methods
222
from most-secure to least-secure.
223
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing Multiple Accounts</h2></div></div></div><p>
225
The built-in SMTP support supports encryption (the
226
<code class="literal">smtps</code> protocol using SSL or TLS) as well as SMTP
227
authentication using SASL. The authentication mechanisms for SASL are
228
specified in <a class="link" href="reference.html#smtp-authenticators" title="3.261. smtp_authenticators">$smtp_authenticators</a> defaulting to
229
an empty list which makes Mutt try all available methods from
230
most-secure to least-secure.
231
</p></div><div class="sect1" title="6. Managing Multiple Accounts"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing Multiple Accounts</h2></div></div></div><p>
224
232
Usage:
225
233
</p><div class="cmdsynopsis"><p><code class="command">account-hook</code>
226
234
<em class="replaceable"><code>pattern</code></em>
227
235
228
236
<em class="replaceable"><code>command</code></em>
229
237
</p></div><p>
230
If you happen to have accounts on multiple IMAP, POP and/or SMTP servers,
231
you may find managing all the authentication settings inconvenient and
232
error-prone. The <a class="link" href="optionalfeatures.html#account-hook" title="6. Managing Multiple Accounts"><span class="command"><strong>account-hook</strong></span></a> command may help. This hook works like
233
<a class="link" href="configuration.html#folder-hook" title="7. Setting Variables Based Upon Mailbox"><span class="command"><strong>folder-hook</strong></span></a> but is invoked whenever Mutt needs to access a remote mailbox
234
(including inside the folder browser), not just when you open the
235
mailbox. This includes (for example) polling for new mail, storing Fcc
236
messages and saving messages to a folder. As a consequence,
237
<a class="link" href="optionalfeatures.html#account-hook" title="6. Managing Multiple Accounts"><span class="command"><strong>account-hook</strong></span></a> should only be used to set connection-related settings such
238
as passwords or tunnel commands but not settings such as sender
239
address or name (because in general it should be considered unpredictable
240
which <a class="link" href="optionalfeatures.html#account-hook" title="6. Managing Multiple Accounts"><span class="command"><strong>account-hook</strong></span></a> was last used).
238
If you happen to have accounts on multiple IMAP, POP and/or SMTP
239
servers, you may find managing all the authentication settings
240
inconvenient and error-prone. The <a class="link" href="optionalfeatures.html#account-hook" title="6. Managing Multiple Accounts"><span class="command"><strong>account-hook</strong></span></a> command
241
may help. This hook works like <a class="link" href="configuration.html#folder-hook" title="7. Setting Variables Based Upon Mailbox"><span class="command"><strong>folder-hook</strong></span></a> but is
242
invoked whenever Mutt needs to access a remote mailbox (including inside
243
the folder browser), not just when you open the mailbox. This includes
244
(for example) polling for new mail, storing Fcc messages and saving
245
messages to a folder. As a consequence, <a class="link" href="optionalfeatures.html#account-hook" title="6. Managing Multiple Accounts"><span class="command"><strong>account-hook</strong></span></a> should
246
only be used to set connection-related settings such as passwords or
247
tunnel commands but not settings such as sender address or name (because
248
in general it should be considered unpredictable which <a class="link" href="optionalfeatures.html#account-hook" title="6. Managing Multiple Accounts"><span class="command"><strong>account-hook</strong></span></a> was last
249
used).
241
250
</p><p>
242
251
Some examples:
243
252
</p><pre class="screen">
246
255
account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
247
256
account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
248
257
</pre><p>
249
To manage multiple accounts with, for example, different values of
250
<a class="link" href="reference.html#record" title="3.211. record">$record</a> or sender addresses,
251
<a class="link" href="configuration.html#folder-hook" title="7. Setting Variables Based Upon Mailbox"><span class="command"><strong>folder-hook</strong></span></a>
252
has to be be used together with
253
the <a class="link" href="configuration.html#mailboxes" title="14. Monitoring Incoming Mail"><span class="command"><strong>mailboxes</strong></span></a> command.
258
To manage multiple accounts with, for example, different values of <a class="link" href="reference.html#record" title="3.212. record">$record</a> or sender addresses, <a class="link" href="configuration.html#folder-hook" title="7. Setting Variables Based Upon Mailbox"><span class="command"><strong>folder-hook</strong></span></a> has to be be
259
used together with the <a class="link" href="configuration.html#mailboxes" title="14. Monitoring Incoming Mail"><span class="command"><strong>mailboxes</strong></span></a> command.
254
260
</p><div class="example"><a id="ex-multiaccount"></a><p class="title"><b>Example 6.2. Managing multiple accounts</b></p><div class="example-contents"><pre class="screen">
255
261
mailboxes imap://user@host1/INBOX
256
262
folder-hook imap://user@host1/ 'set folder=imap://host1/ ; set record=+INBOX/Sent'
258
264
mailboxes imap://user@host2/INBOX
259
265
folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sent'
260
266
</pre></div></div><br class="example-break" /><p>
261
In example
262
<a class="xref" href="optionalfeatures.html#ex-multiaccount" title="Example 6.2. Managing multiple accounts">Example 6.2, “Managing multiple accounts”</a> the folders are defined using
263
<a class="link" href="configuration.html#mailboxes" title="14. Monitoring Incoming Mail"><span class="command"><strong>mailboxes</strong></span></a> so Mutt polls them for new
264
mail. Each <a class="link" href="configuration.html#folder-hook" title="7. Setting Variables Based Upon Mailbox"><span class="command"><strong>folder-hook</strong></span></a> triggers when
265
one mailbox below each IMAP account is opened and sets
266
<a class="link" href="reference.html#folder" title="3.66. folder">$folder</a> to the account's root
267
folder. Next, it sets <a class="link" href="reference.html#record" title="3.211. record">$record</a> to
268
the <span class="emphasis"><em>INBOX/Sent</em></span> folder below the newly
269
set <a class="link" href="reference.html#folder" title="3.66. folder">$folder</a>. Please notice that the
270
value the “<span class="quote">+</span>”
271
<a class="link" href="advancedusage.html#shortcuts" title="7. Mailbox Shortcuts">mailbox shortcut</a> refers to depends on
272
the <span class="emphasis"><em>current</em></span> value
273
of <a class="link" href="reference.html#folder" title="3.66. folder">$folder</a> and therefore has to be set
274
separatedly per account. Setting other values
275
like <a class="link" href="reference.html#from" title="3.75. from">$from</a>
276
or <a class="link" href="reference.html#signature" title="3.235. signature">$signature</a> is analogous to setting
277
<a class="link" href="reference.html#record" title="3.211. record">$record</a>.
278
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local Caching</h2></div></div></div><p>
279
Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>
280
the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the
281
so-called “<span class="quote">body caching</span>” which are both described in this section.
267
In example <a class="xref" href="optionalfeatures.html#ex-multiaccount" title="Example 6.2. Managing multiple accounts">Example 6.2, “Managing multiple accounts”</a> the folders are defined
268
using <a class="link" href="configuration.html#mailboxes" title="14. Monitoring Incoming Mail"><span class="command"><strong>mailboxes</strong></span></a> so
269
Mutt polls them for new mail. Each <a class="link" href="configuration.html#folder-hook" title="7. Setting Variables Based Upon Mailbox"><span class="command"><strong>folder-hook</strong></span></a> triggers
270
when one mailbox below each IMAP account is opened and sets <a class="link" href="reference.html#folder" title="3.66. folder">$folder</a> to the account's root folder. Next, it
271
sets <a class="link" href="reference.html#record" title="3.212. record">$record</a> to the
272
<span class="emphasis"><em>INBOX/Sent</em></span> folder below the newly set <a class="link" href="reference.html#folder" title="3.66. folder">$folder</a>. Please notice that the value the
273
<span class="quote">“<span class="quote">+</span>”</span> <a class="link" href="advancedusage.html#shortcuts" title="8. Mailbox Shortcuts">mailbox shortcut</a>
274
refers to depends on the <span class="emphasis"><em>current</em></span> value of <a class="link" href="reference.html#folder" title="3.66. folder">$folder</a> and therefore has to be set separately
275
per account. Setting other values like <a class="link" href="reference.html#from" title="3.75. from">$from</a>
276
or <a class="link" href="reference.html#signature" title="3.236. signature">$signature</a> is analogous to setting
277
<a class="link" href="reference.html#record" title="3.212. record">$record</a>.
278
</p></div><div class="sect1" title="7. Local Caching"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local Caching</h2></div></div></div><p>
279
Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span> the
280
so-called <span class="quote">“<span class="quote">header caching</span>”</span> and <span class="emphasis"><em>(2)</em></span> the
281
so-called <span class="quote">“<span class="quote">body caching</span>”</span> which are both described in this
282
section.
282
283
</p><p>
283
284
Header caching is optional as it depends on external libraries, body
284
285
caching is always enabled if Mutt is compiled with POP and/or IMAP
285
286
support as these use it (body caching requires no external library).
286
</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header Caching</h3></div></div></div><p>
287
</p><div class="sect2" title="7.1. Header Caching"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header Caching</h3></div></div></div><p>
287
288
Mutt provides optional support for caching message headers for the
288
289
following types of folders: IMAP, POP, Maildir and MH. Header caching
289
greatly improves speed because for remote folders, headers
290
usually only need to be downloaded once. For Maildir and MH, reading the
291
headers from a single file is much faster than looking at possibly
292
thousands of single files (since Maildir and MH use one file per message.)
290
greatly speeds up opening large folders because for remote folders,
291
headers usually only need to be downloaded once. For Maildir and MH,
292
reading the headers from a single file is much faster than looking at
293
possibly thousands of single files (since Maildir and MH use one file
294
per message.)
293
295
</p><p>
294
296
Header caching can be enabled via the configure script and the
295
<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on
296
by default because external database libraries are required: one
297
of tokyocabinet, qdbm, gdbm or bdb must be present.
297
<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on by
298
default because external database libraries are required: one of
299
tokyocabinet, qdbm, gdbm or bdb must be present.
298
300
</p><p>
299
301
If enabled, <a class="link" href="reference.html#header-cache" title="3.79. header_cache">$header_cache</a> can be
300
used to either point to a file or a directory. If set to point to
301
a file, one database file for all folders will be used (which may
302
result in lower performance), but one file per folder if it points
303
to a directory.
304
</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body Caching</h3></div></div></div><p>
302
used to either point to a file or a directory. If set to point to a
303
file, one database file for all folders will be used (which may result
304
in lower performance), but one file per folder if it points to a
305
directory.
306
</p></div><div class="sect2" title="7.2. Body Caching"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body Caching</h3></div></div></div><p>
305
307
Both cache methods can be combined using the same directory for storage
306
308
(and for IMAP/POP even provide meaningful file names) which simplifies
307
309
manual maintenance tasks.
308
310
</p><p>
309
In addition to caching message headers only, Mutt can also cache
310
whole message bodies. This results in faster display of messages
311
for POP and IMAP folders because messages usually have to be
312
downloaded only once.
313
</p><p>
314
For configuration, the variable <a class="link" href="reference.html#message-cachedir" title="3.132. message_cachedir">$message_cachedir</a> must point to a
315
directory. There, Mutt will create a hierarchy of subdirectories
311
In addition to caching message headers only, Mutt can also cache whole
312
message bodies. This results in faster display of messages for POP and
313
IMAP folders because messages usually have to be downloaded only once.
314
</p><p>
315
For configuration, the variable <a class="link" href="reference.html#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a directory. There, Mutt will
316
create a hierarchy of subdirectories named like the account and mailbox
317
path the cache is for.
318
</p></div><div class="sect2" title="7.3. Cache Directories"><div class="titlepage"><div><div><h3 class="title"><a id="cache-dirs"></a>7.3. Cache Directories</h3></div></div></div><p>
319
For using both, header and body caching, <a class="link" href="reference.html#header-cache" title="3.79. header_cache">$header_cache</a> and <a class="link" href="reference.html#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> can be safely set
320
to the same value.
321
</p><p>
322
In a header or body cache directory, Mutt creates a directory hierarchy
316
323
named like: <code class="literal">proto:user@hostname</code> where
317
<code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within
318
there for each folder, Mutt stores messages in single files.
319
All files can be removed as needed if the consumed disk space
320
becomes an issue as Mutt will silently fetch missing items again.
321
</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.3. Maintenance</h3></div></div></div><p>
324
<code class="literal">proto</code> is either <span class="quote">“<span class="quote">pop</span>”</span> or
325
<span class="quote">“<span class="quote">imap.</span>”</span> Within there, for each folder, Mutt stores messages
326
in single files and header caches in files with the
327
<span class="quote">“<span class="quote">.hcache</span>”</span> extension. All files can be removed as needed if
328
the consumed disk space becomes an issue as Mutt will silently fetch
329
missing items again. Pathnames are always stored in UTF-8 encoding.
330
</p><p>
331
For Maildir and MH, the header cache files are named after the MD5
332
checksum of the path.
333
</p></div><div class="sect2" title="7.4. Maintenance"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.4. Maintenance</h3></div></div></div><p>
322
334
Mutt does not (yet) support maintenance features for header cache
323
335
database files so that files have to be removed in case they grow too
324
336
big. It depends on the database library used for header caching whether
325
337
disk space freed by removing messages is re-used.
326
338
</p><p>
327
For body caches, Mutt can keep the local cache in sync with the
328
remote mailbox if the
329
<a class="link" href="reference.html#message-cache-clean" title="3.131. message_cache_clean">$message_cache_clean</a>
330
variable is set. Cleaning means to remove messages from the cache which
331
are no longer present in the mailbox which only happens when other mail
332
clients or instances of Mutt using a different body cache location
333
delete messages (Mutt itself removes deleted messages from the cache
334
when syncing a mailbox). As cleaning can take a noticeable amount of time,
335
it should not be set in general but only occasionally.
336
</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact Address Generation</h2></div></div></div><p>
337
Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and
338
writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when
339
reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
340
switch can be given to configure to build it with write-support
341
for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
342
<code class="literal">mutt -v</code> indicates whether it's supported.
343
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending-mixmaster"></a>9. Sending Anonymous Messages via Mixmaster</h2></div></div></div><p>
339
For body caches, Mutt can keep the local cache in sync with the remote
340
mailbox if the <a class="link" href="reference.html#message-cache-clean" title="3.132. message_cache_clean">$message_cache_clean</a> variable is
341
set. Cleaning means to remove messages from the cache which are no
342
longer present in the mailbox which only happens when other mail clients
343
or instances of Mutt using a different body cache location delete
344
messages (Mutt itself removes deleted messages from the cache when
345
syncing a mailbox). As cleaning can take a noticeable amount of time, it
346
should not be set in general but only occasionally.
347
</p></div></div><div class="sect1" title="8. Exact Address Generation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact Address Generation</h2></div></div></div><p>
348
Mutt supports the <span class="quote">“<span class="quote">Name <user@host></span>”</span> address syntax
349
for reading and writing messages, the older <span class="quote">“<span class="quote">user@host
350
(Name)</span>”</span> syntax is only supported when reading messages. The
351
<span class="emphasis"><em>--enable-exact-address</em></span> switch can be given to
352
configure to build it with write-support for the latter
353
syntax. <code class="literal">EXACT_ADDRESS</code> in the output of <code class="literal">mutt
354
-v</code> indicates whether it's supported.
355
</p></div><div class="sect1" title="9. Sending Anonymous Messages via Mixmaster"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending-mixmaster"></a>9. Sending Anonymous Messages via Mixmaster</h2></div></div></div><p>
344
356
You may also have compiled Mutt to co-operate with Mixmaster, an
345
357
anonymous remailer. Mixmaster permits you to send your messages
346
358
anonymously using a chain of remailers. Mixmaster support in Mutt is for
347
mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03.
348
It does not support earlier versions or the later so-called version 3 betas,
349
of which the latest appears to be called 2.9b23.
350
</p><p>
351
To use it, you'll have to obey certain restrictions. Most
352
important, you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code> headers. To tell
353
Mutt to use mixmaster, you have to select a remailer chain, using
354
the mix function on the compose menu.
355
</p><p>
356
The chain selection screen is divided into two parts. In the
357
(larger) upper part, you get a list of remailers you may use. In
358
the lower part, you see the currently selected chain of remailers.
359
</p><p>
360
You can navigate in the chain using the <code class="literal"><chain-prev></code> and
361
<code class="literal"><chain-next></code> functions, which are by default bound to the left
362
and right arrows and to the <code class="literal">h</code> and <code class="literal">l</code> keys (think vi
363
keyboard bindings). To insert a remailer at the current chain
364
position, use the <code class="literal"><insert></code> function. To append a remailer behind
365
the current chain position, use <code class="literal"><select-entry></code> or <code class="literal"><append></code>.
366
You can also delete entries from the chain, using the corresponding
367
function. Finally, to abandon your changes, leave the menu, or
368
<code class="literal"><accept></code> them pressing (by default) the <code class="literal">Return</code> key.
369
</p><p>
370
Note that different remailers do have different capabilities,
371
indicated in the %c entry of the remailer menu lines (see
372
<a class="link" href="reference.html#mix-entry-format" title="3.143. mix_entry_format">$mix_entry_format</a>). Most important is
373
the “<span class="quote">middleman</span>” capability, indicated by a capital “<span class="quote">M</span>”: This
374
means that the remailer in question cannot be used as the final
375
element of a chain, but will only forward messages to other
376
mixmaster remailers. For details on the other capabilities, please
377
have a look at the mixmaster documentation.
359
mixmaster version 2.04 or later.
360
</p><p>
361
To use it, you'll have to obey certain restrictions. Most important,
362
you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code>
363
headers. To tell Mutt to use mixmaster, you have to select a remailer
364
chain, using the mix function on the compose menu.
365
</p><p>
366
The chain selection screen is divided into two parts. In the (larger)
367
upper part, you get a list of remailers you may use. In the lower part,
368
you see the currently selected chain of remailers.
369
</p><p>
370
You can navigate in the chain using the
371
<code class="literal"><chain-prev></code> and
372
<code class="literal"><chain-next></code> functions, which are by default
373
bound to the left and right arrows and to the <code class="literal">h</code> and
374
<code class="literal">l</code> keys (think vi keyboard bindings). To insert a
375
remailer at the current chain position, use the
376
<code class="literal"><insert></code> function. To append a remailer behind
377
the current chain position, use <code class="literal"><select-entry></code>
378
or <code class="literal"><append></code>. You can also delete entries from
379
the chain, using the corresponding function. Finally, to abandon your
380
changes, leave the menu, or <code class="literal"><accept></code> them
381
pressing (by default) the <code class="literal">Return</code> key.
382
</p><p>
383
Note that different remailers do have different capabilities, indicated
384
in the %c entry of the remailer menu lines (see <a class="link" href="reference.html#mix-entry-format" title="3.144. mix_entry_format">$mix_entry_format</a>). Most important is
385
the <span class="quote">“<span class="quote">middleman</span>”</span> capability, indicated by a capital
386
<span class="quote">“<span class="quote">M</span>”</span>: This means that the remailer in question cannot be
387
used as the final element of a chain, but will only forward messages to
388
other mixmaster remailers. For details on the other capabilities,
389
please have a look at the mixmaster documentation.
378
390
</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Mutt's MIME Support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Security Considerations</td></tr></table></div></body></html>
Loggerhead is a web-based interface for Breezy
Version: 2.0.1