-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<a href="reference.html#message-cache-clean" title="3.133. message_cache_clean">$message_cache_clean</a>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</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>
-Mutt supports the ``Name <user@host>'' address syntax for reading and
-writing messages, the older ``user@host (Name)'' syntax is only supported when
-reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
-switch can be given to configure to build it with write-support
-for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
-<code class="literal">mutt -v</code> indicates whether it's supported.
-</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="tuning.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. Performance tuning</td></tr></table></div></body></html>
+For body caches, Mutt can keep the local cache in sync with the remote
+mailbox if the <a class="link" href="reference.html#message-cache-clean" title="3.132. message_cache_clean">$message_cache_clean</a> variable is
+set. Cleaning means to remove messages from the cache which are no
+longer present in the mailbox which only happens when other mail clients
+or instances of Mutt using a different body cache location delete
+messages (Mutt itself removes deleted messages from the cache when
+syncing a mailbox). As cleaning can take a noticeable amount of time, it
+should not be set in general but only occasionally.
+</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>
+Mutt supports the <span class="quote">“<span class="quote">Name <user@host></span>”</span> address syntax
+for reading and writing messages, the older <span class="quote">“<span class="quote">user@host
+(Name)</span>”</span> syntax is only supported when reading messages. The
+<span class="emphasis"><em>--enable-exact-address</em></span> switch can be given to
+configure to build it with write-support for the latter
+syntax. <code class="literal">EXACT_ADDRESS</code> in the output of <code class="literal">mutt
+-v</code> indicates whether it's supported.
+</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>
+You may also have compiled Mutt to co-operate with Mixmaster, an
+anonymous remailer. Mixmaster permits you to send your messages
+anonymously using a chain of remailers. Mixmaster support in Mutt is for
+mixmaster version 2.04 or later.
+</p><p>
+To use it, you'll have to obey certain restrictions. Most important,
+you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code>
+headers. To tell Mutt to use mixmaster, you have to select a remailer
+chain, using the mix function on the compose menu.
+</p><p>
+The chain selection screen is divided into two parts. In the (larger)
+upper part, you get a list of remailers you may use. In the lower part,
+you see the currently selected chain of remailers.
+</p><p>
+You can navigate in the chain using the
+<code class="literal"><chain-prev></code> and
+<code class="literal"><chain-next></code> functions, which are by default
+bound to the left and right arrows and to the <code class="literal">h</code> and
+<code class="literal">l</code> keys (think vi keyboard bindings). To insert a
+remailer at the current chain position, use the
+<code class="literal"><insert></code> function. To append a remailer behind
+the current chain position, use <code class="literal"><select-entry></code>
+or <code class="literal"><append></code>. You can also delete entries from
+the chain, using the corresponding function. Finally, to abandon your
+changes, leave the menu, or <code class="literal"><accept></code> them
+pressing (by default) the <code class="literal">Return</code> key.
+</p><p>
+Note that different remailers do have different capabilities, indicated
+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
+the <span class="quote">“<span class="quote">middleman</span>”</span> capability, indicated by a capital
+<span class="quote">“<span class="quote">M</span>”</span>: This means that the remailer in question cannot be
+used as the final element of a chain, but will only forward messages to
+other mixmaster remailers. For details on the other capabilities,
+please have a look at the mixmaster documentation.
+</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>