~ubuntu-dev/ubuntu/lucid/mutt/lucid-201002110857

<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.71.1" /><link rel="start" 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="tuning.html" title="Chapter 7. Performance tuning" /></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="tuning.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#id475133">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#id475138">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#id475555">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#id475675">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></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id475133"></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="id475138"></a>1.1. Enabling/disabling features</h3></div></div></div><p>

body { margin-left:2%; margin-right:2%; font-family:serif; }

.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }

h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }

em.replaceable code { font-family:sans-serif; }

p { text-align:justify; }

div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }

.email, .email a { font-family:monospace; }

div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }

div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }

div.table-contents table th {

font-family:sans-serif;

background:#d0d0d0;

font-weight:normal;

vertical-align:top;

}

pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }

div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }

div.note h3:after { content: ":" }

div.note { margin-bottom: 5px; }

</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="tuning.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 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></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>

Mutt supports several of optional features which can be enabled or

disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script

certain arguments. These are listed in the ``Optional features'' section of

certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of

the <span class="emphasis"><em>configure --help</em></span> output.

</p><p>

Which features are enabled or disabled can later be determined from the

output of <code class="literal">mutt -v</code>. If a compile option starts with

``+'' it is enabled and disabled if prefixed with ``-''. For example, if

“<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if

mutt was compiled using GnuTLS for encrypted communication instead of

OpenSSL, <code class="literal">mutt -v</code> would contain:

</p><pre class="screen">

</pre><p>

<code class="literal">proto</code> is the communication protocol:

<code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and

<code class="literal">smtp</code> for SMTP. If ``s'' for ``secure communication''

<code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”

is appended, mutt will attempt to establish an encrypted communication

using SSL or TLS. If no explicit port is given, mutt will use the

system's default for the given protocol.

</p><p>

Since all protocols by mutt support authentication, the username may be

given directly in the URL instead of using the <code class="literal">pop_user</code> or

<code class="literal">imap_user</code> variables. A password can be given, too but

is not recommended if the URL is specified in a configuration file on

disk.

<code class="literal">imap_user</code> variables. It may contain the “<span class="quote">@</span>” symbol

being used by many mail systems as part of the login name. A password can be

given, too but is not recommended if the URL is specified in a configuration

file on disk.

</p><p>

The optional path is only relevant for IMAP.

</p><p>

username for each folder: <code class="literal">imap://username@imapserver[:port]/INBOX</code>

or <code class="literal">imap://username2@imapserver[:port]/path/to/folder</code>.

Replacing <code class="literal">imap://</code> by <code class="literal">imaps://</code>

would make mutt attempt to conect using SSL or TLS on a different port

would make mutt attempt to connect using SSL or TLS on a different port

to encrypt the communication.

</p></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>

If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be

compiled with support for SSL or TLS using either OpenSSL or GnuTLS (

by running the <span class="emphasis"><em>configure</em></span> script with the

<span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or

<span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then

attempt to encrypt communication with remote servers if these protocols

are suffixed with ``s'' for ``secure communication''.

are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.

</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>

If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>

script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work

</p><p>

Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol

for unencrypted and <code class="literal">pops</code> for encrypted

communication, see <a href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.

communication, see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.

</p><p>

Polling for new mail is more expensive over POP3 than locally. For this

reason the frequency at which Mutt will check for mail remotely can be

controlled by the

<a href="reference.html#pop-checkinterval" title="3.215. pop_checkinterval">$pop_checkinterval</a>

<a class="link" href="reference.html#pop-checkinterval" title="3.216. pop_checkinterval">$pop_checkinterval</a>

variable, which defaults to every 60 seconds.

</p><p>

Another way to access your POP3 mail is the <span class="emphasis"><em>fetch-mail</em></span> function

(default: G). It allows to connect to <a href="reference.html#pop-host" title="3.217. pop_host">$pop_host</a>, fetch all your new mail and place it in the

local <a href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a>. After this

</p><a id="fetch-mail"></a><p>

Another way to access your POP3 mail is the <code class="literal"><fetch-mail$</code> function

(default: G). It allows to connect to <a class="link" href="reference.html#pop-host" title="3.218. pop_host">$pop_host</a>, fetch all your new mail and place it in the

local <a class="link" href="reference.html#spoolfile" title="3.277. spoolfile">$spoolfile</a>. After this

point, Mutt runs exactly as if the mail had always been local.

</p><p>

<span class="bold"><strong>Note:</strong></span> If you only need to fetch all messages to a

</p><div class="note"><h3 class="title">Note</h3><p>

If you only need to fetch all messages to a

local mailbox you should consider using a specialized program, such as

<code class="literal">fetchmail</code>, <code class="literal">getmail</code> or similar.

</p></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>

</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>

100

If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>

101

script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work

102

with folders located on a remote IMAP server.

103

</p><p>

104

You can access the remote inbox by selecting the folder by its URL

(see <a href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the

105

(see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the

106

<code class="literal">imap</code> or <code class="literal">imaps</code> protocol.

107

Alternatively, a pine-compatible notation is also supported, ie

108

<code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>

109

</p><p>

Note that not all servers use ``/'' as the hierarchy separator. Mutt should

110

Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should

111

correctly notice which separator is being used by the server and convert

112

paths accordingly.

113

</p><p>

114

When browsing folders on an IMAP server, you can toggle whether to look

115

at only the folders you are subscribed to, or all folders with the

<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the

<a href="reference.html#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.

116

<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the

117

<a class="link" href="reference.html#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.

118

</p><p>

119

Polling for new mail on an IMAP server can cause noticeable delays. So, you'll

120

want to carefully tune the

<a href="reference.html#mail-check" title="3.104. mail_check">$mail_check</a>

121

<a class="link" href="reference.html#mail-check" title="3.105. mail_check">$mail_check</a>

100

122

and

101

<a href="reference.html#timeout" title="3.287. timeout">$timeout</a>

123

<a class="link" href="reference.html#timeout" title="3.288. timeout">$timeout</a>

102

124

variables. Personally I use

103

104

125

</p><pre class="screen">

105

126

set mail_check=90

106

127

set timeout=15

107

128

</pre><p>

108

109

129

with relatively good results over my slow modem line.

110

</p><p>

130

</p><div class="note"><h3 class="title">Note</h3><p>

111

131

Note that if you are using mbox as the mail store on UW servers prior to

112

132

v12.250, the server has been reported to disconnect a client if another client

113

133

selects the same folder.

114

</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id475555"></a>4.1. The Folder Browser</h3></div></div></div><p>

134

</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 Folder Browser</h3></div></div></div><p>

115

135

As of version 1.2, mutt supports browsing mailboxes on an IMAP

116

136

server. This is mostly the same as the local file browser, with the

117

137

following differences:

118

119

138

</p><div class="itemizedlist"><ul type="disc"><li><p>

120

139

In lieu of file permissions, mutt displays the string "IMAP",

121

140

possibly followed by the symbol "+", indicating

122

141

that the entry contains both messages and subfolders. On

123

142

Cyrus-like servers folders will often contain both messages and

124

subfolders.

143

subfolders.

125

144

</p></li><li><p>

126

145

For the case where an entry can contain both messages and

127

146

subfolders, the selection key (bound to <code class="literal">enter</code> by default)

135

154

<code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also

136

155

<code class="literal">subscribe</code> and <code class="literal">unsubscribe</code> to mailboxes (normally

137

156

these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).

138

</p></li></ul></div><p>

139

140

</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id475675"></a>4.2. Authentication</h3></div></div></div><p>

157

</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>

141

158

Mutt supports four authentication methods with IMAP servers: SASL,

142

159

GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add

143

160

NTLM authentication for you poor exchange users out there, but it has

157

174

Mutt will try whichever methods are compiled in and available on the server,

158

175

in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.

159

176

</p><p>

160

There are a few variables which control authentication:

161

177

There are a few variables which control authentication:

162

178

</p><div class="itemizedlist"><ul type="disc"><li><p>

163

<a href="reference.html#imap-user" title="3.95. imap_user">$imap_user</a> - controls

179

<a class="link" href="reference.html#imap-user" title="3.96. imap_user">$imap_user</a> - controls

164

180

the username under which you request authentication on the IMAP server,

165

181

for all authenticators. This is overridden by an explicit username in

166

182

the mailbox path (ie by using a mailbox name of the form

167

183

<code class="literal">{user@host}</code>).

168

184

</p></li><li><p>

169

<a href="reference.html#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a

185

<a class="link" href="reference.html#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a

170

186

password which you may preset, used by all authentication methods where

171

187

a password is needed.

172

188

</p></li><li><p>

173

<a href="reference.html#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - a colon-delimited list of IMAP

189

<a class="link" href="reference.html#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - a colon-delimited list of IMAP

174

190

authentication methods to try, in the order you wish to try them. If

175

191

specified, this overrides mutt's default (attempt everything, in the order

176

192

listed above).

177

</p></li></ul></div><p>

178

179

</p></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>

193

</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>

180

194

Besides supporting traditional mail delivery through a

181

195

sendmail-compatible program, mutt supports delivery through SMTP if it

182

196

was configured and built with <code class="literal">--enable-smtp</code>.

183

197

</p><p>

184

If the configuration variable

185

<a href="reference.html#smtp-url" title="3.269. smtp_url">$smtp_url</a> is set, mutt

186

will contact the given SMTP server to deliver messages; if it is unset,

187

mutt will use the program specified by <a href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a>.

198

If the configuration variable

199

<a class="link" href="reference.html#smtp-url" title="3.270. smtp_url">$smtp_url</a> is set, mutt

200

will contact the given SMTP server to deliver messages; if it is unset,

201

mutt will use the program specified by <a class="link" href="reference.html#sendmail" title="3.258. sendmail">$sendmail</a>.

188

202

</p><p>

189

For details on the URL syntax, please see <a href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>.

203

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>.

190

204

</p><p>

191

205

The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol

192

206

using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms

193

for SASL are specified in <a href="reference.html#smtp-authenticators" title="3.267. smtp_authenticators">$smtp_authenticators</a>

207

for SASL are specified in <a class="link" href="reference.html#smtp-authenticators" title="3.268. smtp_authenticators">$smtp_authenticators</a>

194

208

defaulting to an empty list which makes mutt try all available methods

195

209

from most-secure to least-secure.

196

210

</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>

199

213

error-prone. The account-hook command may help. This hook works like

200

214

folder-hook but is invoked whenever you access a remote mailbox

201

215

(including inside the folder browser), not just when you open the

202

mailbox.

216

mailbox which includes (for example) polling for new mail, storing Fcc

217

messages and saving messages to a folder. As a consequence,

218

account-hook should only be used to set connection-related settings such

219

as passwords or tunnel commands but not settings such as sender

220

address or name (because in general it should be considered unpredictable

221

which account-hook was last used).

203

222

</p><p>

204

223

Some examples:

205

</p><p>

206

207

224

</p><pre class="screen">

208

225

account-hook . 'unset imap_user; unset imap_pass; unset tunnel'

209

226

account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'

210

227

account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'

211

228

account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'

212

</pre><p>

213

214

</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>

229

</pre></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>

215

230

Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>

216

the so-called ``header caching'' and <span class="emphasis"><em>(2)</em></span> the

217

so-called ``body caching'' which are both described in this section.

231

the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the

232

so-called “<span class="quote">body caching</span>” which are both described in this section.

218

233

</p><p>

219

234

Header caching is optional as it depends on external libraries, body

220

235

caching is always enabled if mutt is compiled with POP and/or IMAP

230

245

Header caching can be enabled via the configure script and the

231

246

<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on

232

247

by default because external database libraries are required: one

233

of qdbm, gdbm or bdb must be present.

248

of tokyocabinet, qdbm, gdbm or bdb must be present.

234

249

</p><p>

235

If enabled, <a href="reference.html#header-cache" title="3.107. header_cache">$header_cache</a> can be

250

If enabled, <a class="link" href="reference.html#header-cache" title="3.108. header_cache">$header_cache</a> can be

236

251

used to either point to a file or a directory. If set to point to

237

252

a file, one database file for all folders will be used (which may

238

253

result in lower performance), but one file per folder if it points

244

259

files may be safely removed if a system is short on space. You

245

260

can compute the name of the header cache file for a particular local folder

246

261

through a command like the following:

247

</p><p>

248

262

</p><pre class="screen">

249

263

$ printf '%s' '/path/to/folder' | md5sum

250

264

</pre><p>

251

</p><p>

252

265

The <code class="literal">md5sum</code> command may also be

253

266

named <code class="literal">md5</code>, depending on your operating system.

254

267

</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>

261

274

for POP and IMAP folders because messages usually have to be

262

275

downloaded only once.

263

276

</p><p>

264

For configuration, the variable <a href="reference.html#message-cachedir" title="3.132. message_cachedir">$message_cachedir</a> must point to a

277

For configuration, the variable <a class="link" href="reference.html#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a

265

278

directory. There, mutt will create a hierarchy of subdirectories

266

279

named like: <code class="literal">proto:user@hostname</code> where

267

<code class="literal">proto</code> is either ``pop'' or ``imap.'' Within

280

<code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within

268

281

there for each folder, mutt stores messages in single files (just

269

282

like Maildir) so that with manual symlink creation these cache

270

283

directories can be examined with mutt as read-only Maildir folders.

279

292

</p><p>

280

293

For body caches, mutt can keep the local cache in sync with the

281

294

remote mailbox if the

282

<a href="reference.html#message-cache-clean" title="3.133. message_cache_clean">$message_cache_clean</a>

295

<a class="link" href="reference.html#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a>

283

296

variable is set. Cleaning means to remove messages from the cache which

284

297

are no longer present in the mailbox which only happens when other mail

285

298

clients or instances of mutt using a different body cache location

287

300

when syncing a mailbox). As cleaning can take a noticeable amount of time,

288

301

it should not be set in general but only occasionally.

289

302

</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>

290

Mutt supports the ``Name <user@host>'' address syntax for reading and

291

writing messages, the older ``user@host (Name)'' syntax is only supported when

303

Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and

304

writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when

292

305

reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>

293

306

switch can be given to configure to build it with write-support

294

307

for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of

Older »