<abstract>
<para>
-<quote>All mail clients suck. This one just sucks less.</quote> -me, circa 1995
+<quote>All mail clients suck. This one just sucks less.</quote> — me, circa 1995
</para>
</abstract>
</bookinfo>
</sect1>
<sect1 id="distribution">
-<title>Software Distribution Sites</title>
+<title>Getting Mutt</title>
<para>
Mutt releases can be downloaded from
<ulink url="http://www.mutt.org/download.html">http://www.mutt.org/download.html</ulink>.
</para>
+<para>
+For nightly tarballs and version control access, please refer to the
+<ulink url="http://dev.mutt.org/">Mutt development site</ulink>.
+</para>
+
</sect1>
<sect1 id="irc">
-<title>Mutt online resources</title>
+<title>Mutt Online Resources</title>
<variablelist>
<term>Bug Tracking System</term>
<listitem>
<para>
-The official mutt bug tracking system can be found at
-<ulink url="http://dev.mutt.org/">http://dev.mutt.org/</ulink>
+The official Mutt bug tracking system can be found at
+<ulink url="http://bugs.mutt.org/">http://bugs.mutt.org/</ulink>
</para>
</listitem>
</varlistentry>
<para>
Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
+the Mutt developers always look for skilled translators that help
improve and continue to maintain stale translations.
</para>
</sect1>
<sect1 id="typo">
-<title>Typograhical conventions</title>
+<title>Typograhical Conventions</title>
<para>
This section lists typographical conventions followed throughout this
<row><entry><literal><PageUp></literal></entry><entry>named keys</entry></row>
<row><entry><literal><create-alias></literal></entry><entry>named Mutt function</entry></row>
<row><entry><literal>ˆG</literal></entry><entry>Control+G key combination</entry></row>
-<row><entry><literal>$mail_check</literal></entry><entry>Mutt configuration option</entry></row>
+<row><entry>$mail_check</entry><entry>Mutt configuration option</entry></row>
+<row><entry><literal>$HOME</literal></entry><entry>environment variable</entry></row>
</tbody>
</tgroup>
</table>
<title>Copyright</title>
<para>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
+Mutt is Copyright © 1996-2009 Michael R. Elkins
<email>me@mutt.org</email> and others.
</para>
</para>
<para>
-The first thing you need to do is invoke mutt, simply by typing <literal>mutt</literal>
+The first thing you need to do is invoke Mutt, simply by typing <literal>mutt</literal>
at the command line. There are various command-line options, see
-either the mutt man page or the <link linkend="commandline">reference</link>.
+either the Mutt man page or the <link linkend="commandline">reference</link>.
</para>
<sect1 id="core-concepts">
-<title>Core concepts</title>
+<title>Core Concepts</title>
<para>
Mutt is a text-based application which interacts with users through
interactive commands.
</para>
+<para>
+Mutt is configured through variables which, if the user wants to
+permanently use a non-default value, are written to configuration
+files. Mutt supports a rich config file syntax to make even complex
+configuration files readable and commentable.
+</para>
+
<para>
Because Mutt allows for customizing almost all key bindings, there are
so-called <quote>functions</quote> which can be executed manually (using the
per-folder basis and much more.
</para>
+<para>
+Besides an interactive mode, Mutt can also be used as a command-line
+tool only send messages. It also supports a
+<literal>mailx(1)</literal>-compatible interface, see <xref
+linkend="tab-commandline-options"/> for a complete list of command-line
+options.
+</para>
+
+</sect1>
+
+<sect1 id="concept-screens-and-menus">
+<title>Screens and Menus</title>
+
+<sect2 id="intro-index">
+<title>Index</title>
+
+<para>
+The index is the screen that you usually see first when you start
+Mutt. It gives an overview over your emails in the currently opened
+mailbox. By default, this is your system mailbox. The information you
+see in the index is a list of emails, each with its number on the left,
+its flags (new email, important email, email that has been forwarded or
+replied to, tagged email, ...), the date when email was sent, its
+sender, the email size, and the subject. Additionally, the index also
+shows thread hierarchies: when you reply to an email, and the other
+person replies back, you can see the other's person email in a
+"sub-tree" below. This is especially useful for personal email between
+a group of people or when you've subscribed to mailing lists.
+</para>
+
+</sect2>
+
+<sect2 id="intro-pager">
+<title>Pager</title>
+
+<para>
+The pager is responsible for showing the email content. On the top of
+the pager you have an overview over the most important email headers
+like the sender, the recipient, the subject, and much more
+information. How much information you actually see depends on your
+configuration, which we'll describe below.
+</para>
+
+<para>
+Below the headers, you see the email body which usually contains the
+message. If the email contains any attachments, you will see more
+information about them below the email body, or, if the attachments are
+text files, you can view them directly in the pager.
+</para>
+
+<para>
+To give the user a good overview, it is possible to configure Mutt to
+show different things in the pager with different colors. Virtually
+everything that can be described with a regular expression can be
+colored, e.g. URLs, email addresses or smileys.
+</para>
+
+</sect2>
+
+<sect2 id="intro-browser">
+<title>File Browser</title>
+
+<para>
+The file browser is the interface to the local or remote file
+system. When selecting a mailbox to open, the browser allows custom
+sorting of items, limiting the items shown by a regular expression and a
+freely adjustable format of what to display in which way. It also allows
+for easy navigation through the file system when selecting file(s) to
+attach to a message, select multiple files to attach and many more.
+</para>
+
+</sect2>
+
+<sect2 id="intro-help">
+<title>Help</title>
+
+<para>
+The help screen is meant to offer a quick help to the user. It lists the
+current configuration of key bindings and their associated commands
+including a short description, and currently unbound functions that
+still need to be associated with a key binding (or alternatively, they
+can be called via the Mutt command prompt).
+</para>
+
+</sect2>
+
+<sect2 id="intro-compose">
+<title>Compose Menu</title>
+
+<para>
+The compose menu features a split screen containing the information
+which really matter before actually sending a message by mail: who gets
+the message as what (recipients and who gets what kind of
+copy). Additionally, users may set security options like deciding
+whether to sign, encrypt or sign and encrypt a message with/for what
+keys. Also, it's used to attach messages, to re-edit any attachment
+including the message itself.
+</para>
+
+</sect2>
+
+<sect2 id="intro-alias">
+<title>Alias Menu</title>
+
+<para>
+The alias menu is used to help users finding the recipients of
+messages. For users who need to contact many people, there's no need to
+remember addresses or names completely because it allows for searching,
+too. The alias mechanism and thus the alias menu also features grouping
+several addresses by a shorter nickname, the actual alias, so that users
+don't have to select each single recipient manually.
+</para>
+
+</sect2>
+
+<sect2 id="intro-attach">
+<title>Attachment Menu</title>
+
+<para>
+As will be later discussed in detail, Mutt features a good and stable
+MIME implementation, that is, it supports sending and receiving messages
+of arbitrary MIME types. The attachment menu displays a message's
+structure in detail: what content parts are attached to which parent
+part (which gives a true tree structure), which type is of what type and
+what size. Single parts may saved, deleted or modified to offer great
+and easy access to message's internals.
+</para>
+
+</sect2>
+
</sect1>
<sect1 id="menus">
<title>Moving Around in Menus</title>
<para>
-The most important navigation keys common to all menus are shown in
-<xref linkend="tab-keys-nav"/>.
+The most important navigation keys common to line- or entry-based menus
+are shown in <xref linkend="tab-keys-nav-line"/> and in
+<xref linkend="tab-keys-nav-page"/> for page-based menus.
</para>
-<table id="tab-keys-nav">
-<title>Most common navigation keys</title>
+<table id="tab-keys-nav-line">
+<title>Most common navigation keys in entry-based menus</title>
<tgroup cols="3">
<thead>
<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
</tgroup>
</table>
+<table id="tab-keys-nav-page">
+<title>Most common navigation keys in page-based menus</title>
+<tgroup cols="3">
+<thead>
+<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
+</thead>
+<tbody>
+<row><entry>J or <Return></entry><entry><literal><next-line></literal></entry><entry>scroll down one line</entry></row>
+<row><entry><Backspace></entry><entry><literal><previous-line></literal></entry><entry>sroll up one line</entry></row>
+<row><entry>K, <Space> or <PageDn></entry><entry><literal><next-page></literal></entry><entry>move to the next page</entry></row>
+<row><entry>- or <PageUp></entry><entry><literal><previous-page></literal></entry><entry>move the previous page</entry></row>
+<row><entry><Home></entry><entry><literal><top></literal></entry><entry>move to the top</entry></row>
+<row><entry><End></entry><entry><literal><bottom></literal></entry><entry>move to the bottom</entry></row>
+</tbody>
+</tgroup>
+</table>
+
</sect1>
<sect1 id="editing">
<para>
You can remap the <emphasis>editor</emphasis> functions using the
-<link linkend="bind">bind</link> command. For example, to make
+<link linkend="bind"><command>bind</command></link> command. For example, to make
the <Delete> key delete the character in front of
the cursor rather than under, you could use:
</para>
using <link linkend="history-file">$history_file</link>.
You may cycle through them at an editor prompt by using the
<literal><history-up></literal> and/or
-<literal><history-down></literal> commands.
+<literal><history-down></literal> commands. But notice that Mutt
+does not remember the currently entered text, it only cycles through
+history and wraps around at the end or beginning.
</para>
<para>
</para>
<itemizedlist>
-<listitem><para>muttrc commands</para></listitem>
+<listitem><para><literal>.muttrc</literal> commands</para></listitem>
<listitem><para>addresses and aliases</para></listitem>
<listitem><para>shell commands</para></listitem>
<listitem><para>filenames</para></listitem>
</itemizedlist>
<para>
-Mutt automatically filters out repeated items from the history. It
+Mutt automatically filters out consecutively repeated items from the history. It
also mimics the behavior of some shells by ignoring items starting
with a space. The latter feature can be useful in macros to not clobber
the history's valuable entries with unwanted entries.
</sect1>
<sect1 id="reading">
-<title>Reading Mail - The Index and Pager</title>
+<title>Reading Mail</title>
<para>
Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the <quote>index</quote> in Mutt. The second mode is the display of the
+read in Mutt. The first is a list of messages in the mailbox, which is
+called the <quote>index</quote> menu in Mutt. The second mode is the display of the
message contents. This is called the <quote>pager.</quote>
</para>
<title>The Pager</title>
<para>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <emphasis>less</emphasis> though not nearly as
-featureful.
+By default, Mutt uses its builtin pager to display the contents of
+messages (an external pager such as <literal>less(1)</literal> can be
+configured, see <link linkend="pager">$pager</link> variable).
+The pager is very similar to the Unix program <literal>less(1)</literal>
+though not nearly as featureful.
</para>
<table id="tab-key-pager">
Also, the internal pager supports a couple other advanced features. For
one, it will accept and translate the <quote>standard</quote> nroff sequences for
bold and underline. These sequences are a series of either the letter,
-backspace (ˆH), the letter again for bold or the letter, backspace,
+backspace (<quote>ˆH</quote>), the letter again for bold or the letter, backspace,
<quote>_</quote> for denoting underline. Mutt will attempt to display these
in bold and underline respectively if your terminal supports them. If
not, you can use the bold and underline <link linkend="color">color</link>
-objects to specify a color or mono attribute for them.
+objects to specify a <command>color</command> or mono attribute for them.
</para>
<para>
Note that the search commands in the pager take regular expressions,
which are not quite the same as the more
complex <link linkend="patterns">patterns</link> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
+command in the index. This is because patterns are used to select messages by
+criteria whereas the pager already displays a selected message.
</para>
</note>
<title>Threaded Mode</title>
<para>
-When the mailbox is <link linkend="sort">sorted</link> by <emphasis>threads</emphasis>, there are
-a few additional functions available in the <emphasis>index</emphasis> and <emphasis>pager</emphasis> modes
-as shown in <xref linkend="tab-key-threads"/>.
+So-called <quote>threads</quote> provide a hierarchy of messages where
+replies are linked to their parent message(s). This organizational form
+is extremely useful in mailing lists where different parts of the
+discussion diverge. Mutt displays threads as a tree structure.
+</para>
+
+<para>
+In Mutt, when a mailbox is <link linkend="sort">sorted</link>
+by <emphasis>threads</emphasis>, there are a few additional functions
+available in the <emphasis>index</emphasis>
+and <emphasis>pager</emphasis> modes as shown in
+<xref linkend="tab-key-threads"/>.
</para>
<table id="tab-key-threads">
</tgroup>
</table>
-<note>
<para>
Collapsing a thread displays only the first message
in the thread and hides the others. This is useful when threads
contain so many messages that you can only see a handful of threads on
the screen. See %M in <link linkend="index-format">$index_format</link>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <link linkend="index-format">$index_format</link> to optionally
-display the number of hidden messages if the thread is collapsed.
+For example, you could use <quote>%?M?(#%03M)&(%4l)?</quote> in <link linkend="index-format">$index_format</link> to optionally
+display the number of hidden messages if the thread is
+collapsed. The <literal>%?<char>?<if-part>&<else-part>?</literal>
+syntax is explained in detail in
+<link linkend="formatstrings-conditionals">format string conditionals</link>.
</para>
-</note>
<para>
-See also: <link linkend="strict-threads">$strict_threads</link>.
+Technically, every reply should contain a list of its parent messages in
+the thread tree, but not all do. In these cases, Mutt groups them by
+subject which can be controlled using the
+<link linkend="strict-threads">$strict_threads</link> variable.
</para>
</sect2>
<listitem>
<para>
Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <link linkend="alias">alias</link>
+new one). Once editing is complete, an <link linkend="alias"><command>alias</command></link>
command is added to the file specified by
the <link linkend="alias-file">$alias_file</link> variable
for future use
<note>
<para>
Mutt does not read the <link linkend="alias-file">$alias_file</link>
-upon startup so you must explicitly <link linkend="source">source</link> the file.
+upon startup so you must explicitly <link linkend="source"><command>source</command></link> the file.
</para>
</note>
</listitem>
<listitem>
<para>
Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <link linkend="lists">lists or subscribe</link>
+match the regular expressions given by the <link linkend="lists"><command>lists</command> or <command>subscribe</command></link>
commands, but also honor any <literal>Mail-Followup-To</literal> header(s) if the
<link linkend="honor-followup-to">$honor_followup_to</link>
configuration variable is set. Using this when replying to messages posted
<emphasis>Bouncing</emphasis> a message sends the message as-is to the recipient you
specify. <emphasis>Forwarding</emphasis> a message allows you to add comments or
modify the message you are forwarding. These items are discussed
-in greater detail in the next chapter <quote><link linkend="forwarding-mail">Forwarding
+in greater detail in the next section <quote><link linkend="forwarding-mail">Forwarding
and Bouncing Mail</link>.</quote>
</para>
<para>
Mutt will then enter the <emphasis>compose</emphasis> menu and prompt you for the
-recipients to place on the <quote>To:</quote> header field. Next, it will ask
+recipients to place on the <quote>To:</quote> header field when you hit <literal>m</literal> to start a new message. Next, it will ask
you for the <quote>Subject:</quote> field for the message, providing a default if
-you are replying to or forwarding a message. See also
+you are replying to or forwarding a message. You again
+have the chance to adjust recipients, subject, and security settings
+right before actually sending the message. See also
<link linkend="askcc">$askcc</link>,
<link linkend="askbcc">$askbcc</link>,
<link linkend="autoedit">$autoedit</link>,
<link linkend="bounce">$bounce</link>,
<link linkend="fast-reply">$fast_reply</link>,
and <link linkend="include">$include</link>
-for changing how Mutt asks these questions.
+for changing how and if Mutt asks these questions.
+</para>
+
+<para>
+When replying, Mutt fills these fields with proper values depending on
+the reply type. The types of replying supported are:
+</para>
+
+<variablelist>
+<varlistentry>
+<term>Simple reply</term>
+<listitem>
+<para>
+Reply to the author directly.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>Group reply</term>
+<listitem>
+<para>
+Reply to the author as well to all recipients except you; this consults
+<link linkend="alternates"><command>alternates</command></link>.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>List reply</term>
+<listitem>
+<para>
+Reply to all mailing list addresses found, either specified via
+configuration or auto-detected. See <xref linkend="lists"/> for
+details.
</para>
+</listitem>
+</varlistentry>
+</variablelist>
<para>
-Mutt will then automatically start your <link linkend="editor">$editor</link>
-on the message body. If the <link linkend="edit-headers">$edit_headers</link>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
+After getting recipients for new messages, forwards or replies, Mutt
+will then automatically start your <link
+linkend="editor">$editor</link> on the message body. If the <link
+linkend="edit-headers">$edit_headers</link> variable is
+set, the headers will be at the top of the message in your editor. Any
+messages you are replying to will be added in sort order to the message,
with appropriate <link linkend="attribution">$attribution</link>,
<link linkend="indent-string">$indent_string</link> and
-<link linkend="post-indent-string">$post_indent_string</link>.
-When forwarding a message, if the <link linkend="mime-forward">$mime_forward</link>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <link linkend="signature">$signature</link>, it
-will be appended to the message.
+<link
+linkend="post-indent-string">$post_indent_string</link>.
+When forwarding a message, if the <link
+linkend="mime-forward">$mime_forward</link> variable is
+unset, a copy of the forwarded message will be included. If you have
+specified a <link linkend="signature">$signature</link>, it will
+be appended to the message.
</para>
<para>
</sect2>
<sect2 id="edit-header">
-<title>Editing the message header</title>
+<title>Editing the Message Header</title>
<para>
When editing the header because of <link linkend="edit-headers">$edit_headers</link>
being set, there are a several pseudo headers available which
-will not be included in sent messages.
+will not be included in sent messages but trigger special Mutt behavior.
</para>
<sect3 id="fcc-header">
-<title>Fcc: pseudo header</title>
+<title>Fcc: Pseudo Header</title>
<para>
If you specify
+</para>
+<para>
<literal>Fcc:</literal> <emphasis>filename</emphasis>
+</para>
+<para>
as a header, Mutt will pick up <emphasis>filename</emphasis>
just as if you had used the <literal><edit-fcc></literal> function in the <emphasis>compose</emphasis> menu.
+It can later be changed from the compose menu.
</para>
</sect3>
<sect3 id="attach-header">
-<title>Attach: pseudo header</title>
+<title>Attach: Pseudo Header</title>
<para>
You can also attach files to your message by specifying
+</para>
-<literal>Attach:</literal> <emphasis>filename</emphasis> [ <emphasis>description</emphasis> ]
+<para>
+<literal>Attach:</literal> <emphasis>filename</emphasis>
+[ <emphasis>description</emphasis> ]
+</para>
+<para>
where <emphasis>filename</emphasis> is the file to attach and <emphasis>description</emphasis> is an
-optional string to use as the description of the attached file.
+optional string to use as the description of the attached file. Spaces
+in filenames have to be escaped using backslash (<quote>\</quote>).
+The file can be removed as well as more added from the compose menu.
</para>
</sect3>
<sect3 id="pgp-header">
-<title>Pgp: pseudo header</title>
+<title>Pgp: Pseudo Header</title>
<para>
If you want to use PGP, you can specify
<quote>E</quote> selects encryption, <quote>S</quote> selects signing and
<quote>S<id></quote> selects signing with the given key, setting
<link linkend="pgp-sign-as">$pgp_sign_as</link>
-permanently.
+permanently. The selection can later be changed in the compose menu.
</para>
</sect3>
<sect3 id="in-reply-to-header">
-<title>In-Reply-To: header</title>
+<title>In-Reply-To: Header</title>
<para>
When replying to messages, the <emphasis>In-Reply-To:</emphasis> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
+Message-Id of the message(s) you reply to. If you remove or modify its value, Mutt will not generate a
<emphasis>References:</emphasis> field, which allows you to create a new message thread, for example
to create a new message to a mailing list without having to enter the mailing list's address.
</para>
</sect2>
<sect2 id="sending-crypto">
-<title>Sending cryptographically signed/encrypted messages</title>
+<title>Sending Cryptographically Signed/Encrypted Messages</title>
<para>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
+If you have told Mutt to PGP or S/MIME encrypt a message, it will guide you
through a key selection process when you try to send the message.
Mutt will not ask you any questions about keys which have a
certified user ID matching one of the message recipients' mail
<para>
In these cases, you are dropped into a menu with a list of keys from
-which you can select one. When you quit this menu, or mutt can't
+which you can select one. When you quit this menu, or Mutt can't
find any matching keys, you are prompted for a user ID. You can, as
-usually, abort this prompt using <literal>ˆG</literal>. When you do so, mutt will
+usually, abort this prompt using <literal>ˆG</literal>. When you do so, Mutt will
return to the compose screen.
</para>
</para>
<para>
-The flags sequence (%f) will expand to one of the flags in
+The flags sequence (<quote>%f</quote>) will expand to one of the flags in
<xref linkend="tab-pgp-menuflags"/>.
</para>
</table>
<para>
-The capabilities field (%c) expands to a two-character sequence
+The capabilities field (<quote>%c</quote>) expands to a two-character sequence
representing a key's capabilities. The first character gives
the key's encryption capabilities: A minus sign (<quote>-</quote>) means
that the key cannot be used for encryption. A dot (<quote>.</quote>) means that
</para>
<para>
-Finally, the validity field (%t) indicates how well-certified a user-id
+Finally, the validity field (<quote>%t</quote>) indicates how well-certified a user-id
is. A question mark (<quote>?</quote>) indicates undefined validity, a minus
character (<quote>-</quote>) marks an untrusted association, a space character
means a partially trusted association, and a plus character (<quote>+</quote>)
</sect2>
-<sect2 id="sending-mixmaster">
-<title>Sending anonymous messages via mixmaster</title>
-
-<para>
-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 (beta 45 appears to be the latest) and 2.03.
-It does not support earlier versions or the later so-called version 3 betas,
-of which the latest appears to be called 2.9b23.
-</para>
-
-<para>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <literal>Cc</literal> and <literal>Bcc</literal> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-You can navigate in the chain using the <literal><chain-prev></literal> and
-<literal><chain-next></literal> functions, which are by default bound to the left
-and right arrows and to the <literal>h</literal> and <literal>l</literal> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <literal><insert></literal> function. To append a remailer behind
-the current chain position, use <literal><select-entry></literal> or <literal><append></literal>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<literal><accept></literal> them pressing (by default) the <literal>Return</literal> key.
-</para>
-
-<para>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<link linkend="mix-entry-format">$mix_entry_format</link>). Most important is
-the <quote>middleman</quote> capability, indicated by a capital <quote>M</quote>: 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.
-</para>
-
-</sect2>
-
<sect2 id="ff">
-<title>Sending format=flowed messages</title>
+<title>Sending Format=Flowed Messages</title>
<sect3 id="ff-concept">
<title>Concept</title>
</para>
<para>
-While for text-mode clients like mutt it's the best way to assume only a
+While for text-mode clients like Mutt it's the best way to assume only a
standard 80x25 character cell terminal, it may be desired to let the
receiver decide completely how to view a message.
</para>
</sect3>
<sect3 id="ff-support">
-<title>Mutt support</title>
+<title>Mutt Support</title>
<para>
Mutt only supports setting the required <literal>format=flowed</literal>
<para>
After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
+the compose menu, Mutt properly space-stuffes the message.
<emphasis>Space-stuffing</emphasis> is required by RfC3676 defining
<literal>format=flowed</literal> and means to prepend a space to:
</para>
</sect3>
<sect3 id="ff-editor">
-<title>Editor considerations</title>
+<title>Editor Considerations</title>
<para>
-As mutt provides no additional features to compose <literal>f=f</literal>
+As Mutt provides no additional features to compose <literal>f=f</literal>
messages, it's completely up to the user and his editor to produce
proper messages. Please consider your editor's documentation if you
intend to send <literal>f=f</literal> messages.
attachment, depending on the value of the <link linkend="mime-forward">$mime_forward</link> variable. Decoding of attachments,
like in the pager, can be controlled by the <link linkend="forward-decode">$forward_decode</link> and <link linkend="mime-forward-decode">$mime_forward_decode</link> variables,
respectively. The desired forwarding format may depend on the content,
-therefore <emphasis>$mime_forward</emphasis> is a quadoption which, for
+therefore <link linkend="mime-forward">$mime_forward</link> is a quadoption which, for
example, can be set to <quote>ask-no</quote>.
</para>
<title>Configuration</title>
<sect1 id="configuration-files">
-<title>Location of initialization files</title>
+<title>Location of Initialization Files</title>
<para>
While the default configuration (or <quote>preferences</quote>) make Mutt
<literal>/usr/local/share/mutt/Muttrc</literal> or <literal>/etc/Muttrc</literal>. Mutt
will next look for a file named <literal>.muttrc</literal> in your home
directory. If this file does not exist and your home directory has
-a subdirectory named <literal>.mutt</literal>, mutt try to load a file named
+a subdirectory named <literal>.mutt</literal>, Mutt tries to load a file named
<literal>.mutt/muttrc</literal>.
</para>
</para>
<para>
-In addition, mutt supports version specific configuration files that are
+In addition, Mutt supports version specific configuration files that are
parsed instead of the default files as explained above. For instance, if
your system has a <literal>Muttrc-0.88</literal> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
+directory, and you are running version 0.88 of Mutt, this file will be
sourced instead of the <literal>Muttrc</literal> file. The same is true of the user
configuration file, if you have a file <literal>.muttrc-0.88.6</literal> in your home
-directory, when you run mutt version 0.88.6, it will source this file
+directory, when you run Mutt version 0.88.6, it will source this file
instead of the default <literal>.muttrc</literal> file. The version number is the
same which is visible using the <quote>-v</quote> <link linkend="commandline">command line</link> switch or using the <literal>show-version</literal> key (default:
V) from the index menu.
<para>
An initialization file consists of a series of <link linkend="commands">commands</link>. Each line of the file may contain one or more commands.
When multiple commands are used, they must be separated by a semicolon
-(;).
+(<quote>;</quote>).
</para>
<example id="ex-rc-multiple-cmds">
The hash mark, or pound sign
(<quote>#</quote>), is used as a <quote>comment</quote> character. You can use it to
annotate your initialization file. All text after the comment character
-to the end of the line is ignored. For example,
+to the end of the line is ignored.
</para>
<example id="ex-ec-comment">
</example>
<para>
-Single quotes (') and double quotes (") can be used to quote strings
+Single quotes (<quote>'</quote>) and double quotes (<quote>"</quote>) can be used to quote strings
which contain spaces or other special characters. The difference between
the two types of quotes is similar to that of many popular shell programs,
namely that a single quote is used to specify a literal string (one that is
not interpreted for shell variables or quoting with a backslash [see
next paragraph]), while double quotes indicate a string for which
should be evaluated. For example, backticks are evaluated inside of double
-quotes, but <emphasis role="bold">not</emphasis> for single quotes.
+quotes, but <emphasis>not</emphasis> for single quotes.
</para>
<para>
-\ quotes the next character, just as in shells such as bash and zsh.
+<quote>\</quote> quotes the next character, just as in shells such as bash and zsh.
For example, if want to put quotes <quote>"</quote> inside of a string, you can use
<quote>\</quote> to force the next character to be a literal instead of interpreted
character.
</para>
<para>
-A \ at the end of a line can be used to split commands over
-multiple lines, provided that the split points don't appear in the
-middle of command names.
+A <quote>\</quote> at the end of a line can be used to split commands over
+multiple lines as it <quote>escapes</quote> the line end, provided that the split points don't appear in the
+middle of command names. Lines are first concatenated before
+interpretation so that a multi-line can be commented by commenting out
+the first line only.
</para>
+<example id="ex-rc-split">
+<title>Splitting long configuration commands over several lines</title>
+<screen>
+set status_format="some very \
+long value split \
+over several lines"
+</screen>
+</example>
+
<para>
It is also possible to substitute the output of a Unix command in an
initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
+backticks (``). In <xref linkend="ex-rc-backtick"/>, the output of the
+Unix command <quote>uname -a</quote> will be substituted before the
+line is parsed.
+Since initialization files are line oriented, only
+the first line of output from the Unix command will be substituted.
</para>
<example id="ex-rc-backtick">
</example>
<para>
-The output of the Unix command <quote>uname -a</quote> will be substituted before the
-line is parsed.
-</para>
-
-<note>
-<para>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</para>
-</note>
-
-<para>
-Both environment variables and mutt variables can be accessed by
+Both environment variables and Mutt variables can be accessed by
prepending <quote>$</quote> to the name of the variable. For example,
</para>
</example>
<para>
-will cause mutt to save outgoing messages to a folder named
-<quote>sent_on_kremvax</quote> if the environment variable HOSTNAME is set to
+will cause Mutt to save outgoing messages to a folder named
+<quote>sent_on_kremvax</quote> if the environment variable <literal>$HOSTNAME</literal> is set to
<quote>kremvax.</quote> (See <link linkend="record">$record</link> for
details.)
</para>
</para>
<para>
-The commands understood by mutt are explained in the next paragraphs.
+The commands understood by Mutt are explained in the next paragraphs.
For a complete list, see the <link linkend="commands">command reference</link>.
</para>
If a configuration file is not encoded in the same character set the
<link linkend="config-charset">$config_charset</link>
variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
+from <link linkend="config-charset">$config_charset</link>
+to <link linkend="charset">$charset</link>.
</para>
<para>
<itemizedlist>
<listitem><para>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</para></listitem>
+file with <link linkend="charset">$charset</link> preceding
+<link linkend="config-charset">$config_charset</link> so Mutt
+knows what character set to convert to.</para></listitem>
-<listitem><para>If $config_charset is set, it should be set
+<listitem><para>If <link linkend="config-charset">$config_charset</link> is set, it should be set
in each configuration file because the value is global and <emphasis>not</emphasis>
per configuration file.</para></listitem>
</sect1>
<sect1 id="addrgroup">
-<title>Address groups</title>
+<title>Address Groups</title>
<para>Usage:</para>
<replaceable class="parameter">expr</replaceable>
</arg>
</group>
-</cmdsynopsis>
-<cmdsynopsis>
<command>ungroup</command>
<arg choice="opt" rep="repeat">
<option>-group</option>
</cmdsynopsis>
<para>
-<literal>group</literal> is used to directly add either addresses or
+<command>group</command> is used to directly add either addresses or
regular expressions to the specified group or groups. The different
-categories of arguments to the <literal>group</literal> command can be
+categories of arguments to the <command>group</command> command can be
in any order. The flags <literal>-rx</literal> and
<literal>-addr</literal> specify what the following strings (that cannot
begin with a hyphen) should be interpreted as: either a regular
<para>
These address groups can also be created implicitly by the
-<link linkend="alias">alias</link>, <link linkend="lists">lists</link>,
+<link linkend="alias"><command>alias</command></link>, <link linkend="lists">lists</link>,
<link linkend="lists">subscribe</link> and
-<link linkend="alternates">alternates</link> commands by specifying the
+<link linkend="alternates"><command>alternates</command></link> commands by specifying the
optional <literal>-group</literal> option.
</para>
</para>
<para>
-<literal>ungroup</literal> is used to remove addresses or regular
+<command>ungroup</command> is used to remove addresses or regular
expressions from the specified group or groups. The syntax is similar to
-the <literal>group</literal> command, however the special character
+the <command>group</command> command, however the special character
<literal>*</literal> can be used to empty a group of all of its
contents.
</para>
</sect1>
<sect1 id="alias">
-<title>Defining/Using aliases</title>
+<title>Defining/Using Aliases</title>
<para>Usage:</para>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">address</replaceable>
</arg>
+
+<command>unalias</command>
+<arg choice="opt" rep="repeat">
+<option>-group</option>
+<replaceable>name</replaceable>
+</arg>
+<group choice="req">
+<arg choice="plain">
+<replaceable class="parameter">*</replaceable>
+</arg>
+<arg choice="plain" rep="repeat">
+<replaceable class="parameter">key</replaceable>
+</arg>
+</group>
</cmdsynopsis>
<para>
<note>
<para>
If you want to create an alias for more than
-one address, you <emphasis role="bold">must</emphasis> separate the addresses with a comma (<quote>,</quote>).
+one address, you <emphasis>must</emphasis> separate the addresses with a comma (<quote>,</quote>).
</para>
</note>
<para>
The optional <literal>-group</literal> argument to
-<literal>alias</literal> causes the aliased address(es) to be added to
+<command>alias</command> causes the aliased address(es) to be added to
the named <emphasis>group</emphasis>.
</para>
To remove an alias or aliases (<quote>*</quote> means all aliases):
</para>
-<cmdsynopsis>
-<command>unalias</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">key</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
<screen>
alias muttdude me@cs.hmc.edu (Michael Elkins)
alias theguys manny, moe, jack
<para>
Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <literal>alias</literal> command can appear anywhere in
-a configuration file, as long as this file is <link linkend="source">sourced</link>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
+in a special file. The <command>alias</command> command can appear anywhere in
+a configuration file, as long as this file is <link linkend="source"><command>source</command>d</link>. Consequently, you can have multiple alias files, or
+you can have all aliases defined in your <literal>.muttrc</literal>.
</para>
<para>
function can use only one file, the one pointed to by the <link linkend="alias-file">$alias_file</link> variable (which is
<literal>˜/.muttrc</literal> by default). This file is not special either,
in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <link linkend="source">source</link> this file too.
-</para>
-
-<para>
-For example:
+order for the new aliases to take effect you need to explicitly <link linkend="source"><command>source</command></link> this file too.
</para>
<example id="ex-alias-external">
</example>
<para>
-To use aliases, you merely use the alias at any place in mutt where mutt
+To use aliases, you merely use the alias at any place in Mutt where Mutt
prompts for addresses, such as the <emphasis>To:</emphasis> or <emphasis>Cc:</emphasis> prompt. You can
also enter aliases in your editor at the appropriate headers if you have the
<link linkend="edit-headers">$edit_headers</link> variable set.
<para>
In addition, at the various address prompts, you can use the tab character
to expand a partial alias to the full alias. If there are multiple matches,
-mutt will bring up a menu with the matching aliases. In order to be
-presented with the full list of aliases, you must hit tab with out a partial
+Mutt will bring up a menu with the matching aliases. In order to be
+presented with the full list of aliases, you must hit tab without a partial
alias, such as at the beginning of the prompt or after a comma denoting
multiple addresses.
</para>
</sect1>
<sect1 id="bind">
-<title>Changing the default key bindings</title>
+<title>Changing the Default Key Bindings</title>
<para>Usage:</para>
menus except for the pager and editor modes. If a key is not defined in
another menu, Mutt will look for a binding to use in this menu. This allows
you to bind a key to a certain function in multiple menus instead of having
-multiple bind statements to accomplish the same task.
+multiple <command>bind</command> statements to accomplish the same task.
</para>
</listitem>
</varlistentry>
<listitem>
<para>
The alias menu is the list of your personal aliases as defined in your
-muttrc. It is the mapping from a short alias name to the full email
+<literal>.muttrc</literal>. It is the mapping from a short alias name to the full email
address(es) of the recipient(s).
</para>
</listitem>
</sect1>
<sect1 id="charset-hook">
-<title>Defining aliases for character sets </title>
+<title>Defining Aliases for Character Sets</title>
<para>Usage:</para>
<arg choice="plain">
<replaceable class="parameter">charset</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command>iconv-hook</command>
+<command>iconv-hook<anchor id="iconv-hook"/></command>
<arg choice="plain">
<replaceable class="parameter">charset</replaceable>
</arg>
</cmdsynopsis>
<para>
-The <literal>charset-hook</literal> command defines an alias for a character set.
+The <command>charset-hook</command> command defines an alias for a character set.
This is useful to properly display messages which are tagged with a
-character set name not known to mutt.
+character set name not known to Mutt.
</para>
<para>
-The <literal>iconv-hook</literal> command defines a system-specific name for a
+The <command>iconv-hook</command> command defines a system-specific name for a
character set. This is helpful when your systems character
conversion library insists on using strange, system-specific names
for character sets.
</sect1>
<sect1 id="folder-hook">
-<title>Setting variables based upon mailbox</title>
+<title>Setting Variables Based Upon Mailbox</title>
<para>Usage:</para>
<para>
It is often desirable to change settings based on which mailbox you are
-reading. The folder-hook command provides a method by which you can execute
+reading. The <command>folder-hook</command> command provides a method by which you can execute
any configuration command. <emphasis>regexp</emphasis> is a regular expression specifying
in which mailboxes to execute <emphasis>command</emphasis> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
+matches multiple <command>folder-hook</command>s, they are executed in the order given in the
+<literal>.muttrc</literal>.
</para>
<note>
Settings are <emphasis>not</emphasis> restored when you leave the mailbox.
For example, a command action to perform is to change the sorting method
based upon the mailbox being read:
-</para>
-</note>
<screen>
-folder-hook mutt set sort=threads
-</screen>
+folder-hook mutt "set sort=threads"</screen>
-<para>
However, the sorting method is not restored to its previous value when
reading a different mailbox. To specify a <emphasis>default</emphasis> command, use the
-pattern <quote>.</quote> before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
+pattern <quote>.</quote> before other <command>folder-hook</command>s adjusting a value on a per-folder basis
+because <command>folder-hook</command>s are evaluated in the order given in the
+configuration file.
+</para>
+</note>
+
+<para>
The following example will set the <link linkend="sort">sort</link> variable
to <literal>date-sent</literal> for all folders but to <literal>threads</literal>
for all folders containing <quote>mutt</quote> in their name.
<example id="ex-folder-sorting">
<title>Setting sort method based on mailbox name</title>
<screen>
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
+folder-hook . "set sort=date-sent"
+folder-hook mutt "set sort=threads"
</screen>
</example>
</sect1>
<sect1 id="macro">
-<title>Keyboard macros</title>
+<title>Keyboard Macros</title>
<para>Usage:</para>
<para>
Optionally you can specify a descriptive text after <emphasis>sequence</emphasis>,
-which is shown in the help screens.
+which is shown in the help screens if they contain a description.
</para>
<note>
</sect1>
<sect1 id="color">
-<title>Using color and mono video attributes</title>
+<title>Using Color and Mono Video Attributes</title>
<para>Usage:</para>
<arg choice="plain">
<replaceable class="parameter">background</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>color</command>
<group choice="req">
<arg choice="plain">
<arg choice="plain">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>color</command>
<arg choice="plain">
<option>index</option>
<arg choice="plain">
<replaceable class="parameter">pattern</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>uncolor</command>
+<group choice="req">
<arg choice="plain">
<option>index</option>
</arg>
+<arg choice="plain">
+<option>header</option>
+</arg>
+<arg choice="plain">
+<option>body</option>
+</arg>
+</group>
<group choice="req">
<arg choice="plain">
<replaceable>*</replaceable>
<para>
If your terminal supports color, you can spice up Mutt by creating your own
color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <emphasis role="bold">and</emphasis> a background color (it is not
+must specify both a foreground color <emphasis>and</emphasis> a background color (it is not
possible to only specify one or the other).
</para>
<listitem><para>message (informational messages)</para></listitem>
<listitem><para>normal</para></listitem>
<listitem><para>quoted (text matching <link linkend="quote-regexp">$quote_regexp</link> in the body of a message)</para></listitem>
-<listitem><para>quoted1, quoted2, ..., quoted<emphasis role="bold">N</emphasis> (higher levels of quoting)</para></listitem>
+<listitem><para>quoted1, quoted2, ..., quoted<emphasis>N</emphasis> (higher levels of quoting)</para></listitem>
<listitem><para>search (hiliting of words in the pager)</para></listitem>
<listitem><para>signature</para></listitem><listitem><para>status (mode lines used to display info about the mailbox or message)</para></listitem>
<listitem><para>tilde (the <quote>˜</quote> used to pad blank lines in the pager)</para></listitem>
If your terminal supports it, the special keyword <emphasis>default</emphasis> can be
used as a transparent color. The value <emphasis>brightdefault</emphasis> is also valid.
If Mutt is linked against the <emphasis>S-Lang</emphasis> library, you also need to set
-the <emphasis>COLORFGBG</emphasis> environment variable to the default colors of your
+the <literal>$COLORFGBG</literal> environment variable to the default colors of your
terminal for this to work; for example (for Bourne-like shells):
</para>
<note>
<para>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <emphasis role="bold">must</emphasis> specify the same pattern
-specified in the color command for it to be removed. The pattern <quote>*</quote> is
-a special token which means to clear the color index list of all entries.
+The <command>uncolor</command> command can be applied to the index, header and body objects only. It
+removes entries from the list. You <emphasis>must</emphasis> specify the same pattern
+specified in the <command>color</command> command for it to be removed. The pattern <quote>*</quote> is
+a special token which means to clear the color list of all entries.
</para>
</note>
<para>
Mutt also recognizes the keywords <emphasis>color0</emphasis>, <emphasis>color1</emphasis>, …,
-<emphasis>color</emphasis><emphasis role="bold">N-1</emphasis> (<emphasis role="bold">N</emphasis> being the number of colors supported
+<emphasis>color</emphasis><emphasis>N-1</emphasis> (<emphasis>N</emphasis> being the number of colors supported
by your terminal). This is useful when you remap the colors for your
display (for example by changing the color associated with <emphasis>color2</emphasis>
for your xterm), since color names may then lose their normal meaning.
</para>
+<anchor id="mono"/>
<para>
If your terminal does not support color, it is still possible change the video
-attributes through the use of the <quote>mono</quote> command:
+attributes through the use of the <quote>mono</quote> command. Usage:
</para>
-<anchor id="mono"/>
-<para>Usage:</para>
-
<cmdsynopsis>
<command>mono</command>
<arg choice="plain">
<arg choice="plain">
<replaceable class="parameter">attribute</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>mono</command>
<group choice="req">
<arg choice="plain">
<arg choice="plain">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>mono</command>
<arg choice="plain">
<option>index</option>
<arg choice="plain">
<replaceable class="parameter">pattern</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unmono</command>
+<group choice="req">
<arg choice="plain">
<option>index</option>
</arg>
+<arg choice="plain">
+<option>header</option>
+</arg>
+<arg choice="plain">
+<option>body</option>
+</arg>
+</group>
<group choice="req">
<arg choice="plain">
<replaceable>*</replaceable>
</cmdsynopsis>
<para>
-For <emphasis>object</emphasis>, see the color command. <emphasis>attribute</emphasis>
+For <emphasis>object</emphasis>, see the <command>color</command> command. <emphasis>attribute</emphasis>
can be one of the following:
</para>
</sect1>
-<sect1 id="ignore">
-<title>Message header display</title>
+<sect1 id="msg-hdr-display">
+<title>Message Header Display</title>
+
+<sect2 id="ignore">
+<title>Selecting Headers</title>
<para>Usage:</para>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">pattern</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unignore</command>
<group choice="req">
<arg choice="plain">
<quote>unignore *</quote> will remove all tokens from the ignore list.
</para>
-<para>
-For example:
-</para>
-
<example id="ex-header-weeding">
<title>Header weeding</title>
<screen>
</screen>
</example>
-<anchor id="hdr-order"/>
-<para>Usage:</para>
+</sect2>
+
+<sect2 id="hdr-order">
+<title>Ordering Displayed Headers</title>
+
+<para>Usage:</para>
<cmdsynopsis>
<command>hdr_order</command>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">header</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unhdr_order</command>
<group choice="req">
<arg choice="plain">
</cmdsynopsis>
<para>
-With the <literal>hdr_order</literal> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
+With the <command>hdr_order</command> command you can specify an order in
+which Mutt will attempt to present these headers to you when viewing messages.
</para>
<para>
-<quote>unhdr_order *</quote> will clear all previous headers from the order list,
+<quote><command>unhdr_order</command> *</quote> will clear all previous headers from the order list,
thus removing the header order effects set by the system-wide startup file.
</para>
</screen>
</example>
+</sect2>
</sect1>
<sect1 id="alternates">
-<title>Alternative addresses</title>
+<title>Alternative Addresses</title>
<para>Usage:</para>
<arg choice="opt" rep="repeat">
<replaceable>regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unalternates</command>
<arg choice="opt" rep="repeat">
<option>-group</option>
</cmdsynopsis>
<para>
-With various functions, mutt will treat messages differently,
+With various functions, Mutt will treat messages differently,
depending on whether you sent them or whether you received them from
someone else. For instance, when replying to a message that you
-sent to a different party, mutt will automatically suggest to send
-the response to the original message's recipients -- responding to
+sent to a different party, Mutt will automatically suggest to send
+the response to the original message's recipients — responding to
yourself won't make much sense in many cases. (See <link linkend="reply-to">$reply_to</link>.)
</para>
<para>
Many users receive e-mail under a number of different addresses. To
-fully use mutt's features here, the program must be able to
+fully use Mutt's features here, the program must be able to
recognize what e-mail addresses you receive mail under. That's the
-purpose of the <literal>alternates</literal> command: It takes a list of regular
+purpose of the <command>alternates</command> command: It takes a list of regular
expressions, each of which can identify an address under which you
receive e-mail.
</para>
</screen>
<para>
-mutt will consider <quote><literal>some-user@example</literal></quote> as
+Mutt will consider <quote><literal>some-user@example</literal></quote> as
being your address, too which may not be desired. As a solution, in such
cases addresses should be specified as:
</para>
</para>
<para>
-The <literal>unalternates</literal> command can be used to write exceptions to
-<literal>alternates</literal> patterns. If an address matches something in an
-<literal>alternates</literal> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <literal>unalternates</literal>
+The <command>unalternates</command> command can be used to write exceptions to
+<command>alternates</command> patterns. If an address matches something in an
+<command>alternates</command> command, but you nonetheless do not think it is
+from you, you can list a more precise pattern under an <command>unalternates</command>
command.
</para>
<para>
-To remove a regular expression from the <literal>alternates</literal> list, use the
-<literal>unalternates</literal> command with exactly the same <emphasis>regexp</emphasis>.
-Likewise, if the <emphasis>regexp</emphasis> for an <literal>alternates</literal> command matches
-an entry on the <literal>unalternates</literal> list, that <literal>unalternates</literal>
-entry will be removed. If the <emphasis>regexp</emphasis> for <literal>unalternates</literal>
-is <quote>*</quote>, <emphasis>all entries</emphasis> on <literal>alternates</literal> will be removed.
+To remove a regular expression from the <command>alternates</command> list, use the
+<command>unalternates</command> command with exactly the same <emphasis>regexp</emphasis>.
+Likewise, if the <emphasis>regexp</emphasis> for an <command>alternates</command> command matches
+an entry on the <command>unalternates</command> list, that <command>unalternates</command>
+entry will be removed. If the <emphasis>regexp</emphasis> for <command>unalternates</command>
+is <quote>*</quote>, <emphasis>all entries</emphasis> on <command>alternates</command> will be removed.
</para>
</sect1>
<sect1 id="lists">
-<title>Mailing lists</title>
+<title>Mailing Lists</title>
<anchor id="subscribe"/>
<para>Usage:</para>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unlists</command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<replaceable class="parameter">regexp</replaceable>
</arg>
</group>
-</cmdsynopsis>
-<cmdsynopsis>
<command>subscribe</command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unsubscribe</command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<para>
Mutt has a few nice features for <link linkend="using-lists">handling mailing lists</link>. In order to take advantage of them, you must
specify which addresses belong to mailing lists, and which mailing
-lists you are subscribed to. Once you have done this, the <link linkend="list-reply"><literal><list-reply></literal></link> function will work for all known lists.
-Additionally, when you send a message to a subscribed list, mutt will
+lists you are subscribed to. Mutt also has limited support for
+auto-detecting mailing lists: it supports parsing
+<literal>mailto:</literal> links in the common
+<literal>List-Post:</literal> header which has the same effect as
+specifying the list address via the <command>lists</command> command
+(except the group feature). Once you have done this, the
+<link linkend="list-reply"><literal><list-reply></literal></link>
+function will work for all known lists.
+Additionally, when you send a message to a subscribed list, Mutt will
add a Mail-Followup-To header to tell other users' mail user agents
not to send copies of replies to your personal address.
</para>
receiving personal CCs of list messages. Also note that the generation
of the Mail-Followup-To header is controlled by the
<link linkend="followup-to">$followup_to</link>
-configuration variable.
+configuration variable since it's common practice on some mailing lists
+to send Cc upons replies (which is more a group- than a list-reply).
</para>
</note>
<para>
More precisely, Mutt maintains lists of patterns for the addresses
of known and subscribed mailing lists. Every subscribed mailing
-list is known. To mark a mailing list as known, use the <quote>lists</quote>
-command. To mark it as subscribed, use <quote>subscribe</quote>.
+list is known. To mark a mailing list as known, use the <command>list</command>
+command. To mark it as subscribed, use <command>subscribe</command>.
</para>
<para>
-You can use regular expressions with both commands. To mark all
-messages sent to a specific bug report's address on mutt's bug
+You can use regular expressions with both commands. To mark all
+messages sent to a specific bug report's address on Debian's bug
tracking system as list mail, for instance, you could say
-<quote>subscribe [0-9]*@bugs.guug.de</quote>. Often, it's sufficient to just
-give a portion of the list's e-mail address.
+</para>
+
+<screen>
+subscribe [0-9]*.*@bugs.debian.org</screen>
+
+<para>
+as it's often, it's sufficient to just give a portion of the list's e-mail address.
</para>
<para>
Specify as much of the address as you need to to remove ambiguity. For
example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <emphasis>mutt-users@mutt.org</emphasis>. So, to tell Mutt
-that this is a mailing list, you could add <quote>lists mutt-users@</quote> to your
-initialization file. To tell mutt that you are subscribed to it,
-add <quote>subscribe mutt-users</quote> to your initialization file instead.
+addressed to <literal>mutt-users@mutt.org</literal>. So, to tell Mutt
+that this is a mailing list, you could add <literal>lists mutt-users@</literal> to your
+initialization file. To tell Mutt that you are subscribed to it,
+add <literal><command>subscribe</command> mutt-users</literal> to your initialization file instead.
If you also happen to get mail from someone whose address is
-<emphasis>mutt-users@example.com</emphasis>, you could use
-<quote>lists ^mutt-users@mutt\\.org$</quote>
-or <quote>subscribe ^mutt-users@mutt\\.org$</quote> to
+<literal>mutt-users@example.com</literal>, you could use
+<literal><command>lists</command> ^mutt-users@mutt\\.org$</literal>
+or <literal><command>subscribe</command> ^mutt-users@mutt\\.org$</literal> to
match only mail from the actual list.
</para>
<para>
To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use <quote>unsubscribe</quote>.
+but keep it on the list of known mailing lists, use <command>unsubscribe</command>.
</para>
</sect1>
<sect1 id="mbox-hook">
-<title>Using Multiple spool mailboxes</title>
+<title>Using Multiple Spool Mailboxes</title>
<para>Usage:</para>
</sect1>
<sect1 id="mailboxes">
-<title>Monitoring incoming mail</title>
+<title>Monitoring Incoming Mail</title>
<para>Usage:</para>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">mailbox</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unmailboxes</command>
<group choice="req">
<arg choice="plain">
<note>
<para>
-The folders in the <literal>mailboxes</literal> command are resolved when
+The folders in the <command>mailboxes</command> command are resolved when
the command is executed, so if these names contain <link linkend="shortcuts">shortcut characters</link> (such as <quote>=</quote> and <quote>!</quote>), any variable
definition that affects these characters (like <link linkend="folder">$folder</link> and <link linkend="spoolfile">$spoolfile</link>)
-should be set before the <literal>mailboxes</literal> command. If
+should be set before the <command>mailboxes</command> command. If
none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
+otherwise Mutt tries to find it relative to the directory
+from where Mutt was started which may not always be desired.
</para>
</note>
unreliable, the
<link linkend="check-mbox-size">$check_mbox_size</link>
option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
+mail detection instead which won't work for size-neutral changes.
</para>
</sect1>
<sect1 id="my-hdr">
-<title>User defined headers</title>
+<title>User-Defined Headers</title>
<para>Usage:</para>
<arg choice="plain">
<replaceable class="parameter">string</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unmy_hdr</command>
<group choice="req">
<arg choice="plain">
</cmdsynopsis>
<para>
-The <literal>my_hdr</literal> command allows you to create your own header
-fields which will be added to every message you send.
+The <command>my_hdr</command> command allows you to create your own header
+fields which will be added to every message you send and appear in the
+editor if <link linkend="edit-headers">$edit_headers</link> is set.
</para>
<para>
For example, if you would like to add an <quote>Organization:</quote> header field to
-all of your outgoing messages, you can put the command
+all of your outgoing messages, you can put the command something like
+shown in <xref linkend="ex-my-hdr"/> in your <literal>.muttrc</literal>.
</para>
<example id="ex-my-hdr">
</screen>
</example>
-<para>
-in your <literal>.muttrc</literal>.
-</para>
-
<note>
<para>
Space characters are <emphasis>not</emphasis> allowed between the keyword and
</para>
<para>
-To remove user defined header fields, use the <literal>unmy_hdr</literal>
+To remove user defined header fields, use the <command>unmy_hdr</command>
command. You may specify an asterisk (<quote>*</quote>) to remove all header
fields, or the fields to remove. For example, to remove all <quote>To</quote> and
<quote>Cc</quote> header fields, you could use:
</sect1>
<sect1 id="save-hook">
-<title>Specify default save mailbox</title>
+<title>Specify Default Save Mailbox</title>
<para>Usage:</para>
<emphasis>mailbox</emphasis> after it was expanded.
</para>
-<para>
-Examples:
-</para>
-
<example id="ex-save-hook-exando">
-<title>Using %-expandos in <literal>save-hook</literal></title>
+<title>Using %-expandos in <command>save-hook</command></title>
<screen>
# default: save all to ~/Mail/<author name>
save-hook . ~/Mail/%F
</example>
<para>
-Also see the <link linkend="fcc-save-hook">fcc-save-hook</link> command.
+Also see the <link linkend="fcc-save-hook"><command>fcc-save-hook</command></link> command.
</para>
</sect1>
<sect1 id="fcc-hook">
-<title>Specify default Fcc: mailbox when composing</title>
+<title>Specify Default Fcc: Mailbox When Composing</title>
<para>Usage:</para>
See <xref linkend="pattern-hook"/> for information on the exact format of <emphasis>pattern</emphasis>.
</para>
-<para>
-Example: <literal>fcc-hook [@.]aol\\.com$ +spammers</literal>
-</para>
+<screen>fcc-hook [@.]aol\\.com$ +spammers</screen>
<para>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <link linkend="fcc-save-hook">fcc-save-hook</link> command.
+...will save a copy of all messages going to the aol.com domain to
+the `+spammers' mailbox by default. Also see the <link linkend="fcc-save-hook"><command>fcc-save-hook</command></link> command.
</para>
</sect1>
<sect1 id="fcc-save-hook">
-<title>Specify default save filename and default Fcc: mailbox at once</title>
+<title>Specify Default Save Filename and Default Fcc: Mailbox at Once</title>
<para>Usage:</para>
</cmdsynopsis>
<para>
-This command is a shortcut, equivalent to doing both a <link linkend="fcc-hook">fcc-hook</link>
-and a <link linkend="save-hook">save-hook</link> with its arguments,
+This command is a shortcut, equivalent to doing both a <link linkend="fcc-hook"><command>fcc-hook</command></link>
+and a <link linkend="save-hook"><command>save-hook</command></link> with its arguments,
including %-expansion on <emphasis>mailbox</emphasis> according
to <link linkend="index-format">$index_format</link>.
</para>
</sect1>
<sect1 id="send-hook">
-<title>Change settings based upon message recipients</title>
+<title>Change Settings Based Upon Message Recipients</title>
<anchor id="reply-hook"/>
<anchor id="send2-hook"/>
<arg choice="plain">
<replaceable class="parameter">command</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>send-hook</command>
<arg choice="plain">
<replaceable class="parameter">[!]pattern</replaceable>
<arg choice="plain">
<replaceable class="parameter">command</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>send2-hook</command>
<arg choice="plain">
<replaceable class="parameter">[!]pattern</replaceable>
</para>
<para>
-<literal>reply-hook</literal> is matched against the message you are <emphasis>replying to</emphasis>,
-instead of the message you are <emphasis>sending</emphasis>. <literal>send-hook</literal> is
+<command>reply-hook</command> is matched against the message you are <emphasis>replying to</emphasis>,
+instead of the message you are <emphasis>sending</emphasis>. <command>send-hook</command> is
matched against all messages, both <emphasis>new</emphasis>
and <emphasis>replies</emphasis>.
</para>
<note>
<para>
-<literal>reply-hook</literal>s are matched <emphasis role="bold">before</emphasis> the <literal>send-hook</literal>, <emphasis role="bold">regardless</emphasis>
+<command>reply-hook</command>s are matched <emphasis>before</emphasis> the <command>send-hook</command>, <emphasis>regardless</emphasis>
of the order specified in the user's configuration file.
</para>
</note>
<para>
-<literal>send2-hook</literal> is matched every time a message is changed, either
+<command>send2-hook</command> is matched every time a message is changed, either
by editing it, or by using the compose menu to change its recipients
-or subject. <literal>send2-hook</literal> is executed after <literal>send-hook</literal>, and
+or subject. <command>send2-hook</command> is executed after <command>send-hook</command>, and
can, e.g., be used to set parameters such as the <link linkend="sendmail">$sendmail</link> variable depending on the message's sender
address.
</para>
<para>
-For each type of <literal>send-hook</literal> or <literal>reply-hook</literal>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
+For each type of <command>send-hook</command> or <command>reply-hook</command>, when multiple matches
+occur, commands are executed in the order they are specified in the <literal>.muttrc</literal>
(for that type of hook).
</para>
<para>
-Example: <literal>send-hook mutt "set mime_forward signature=''"</literal>
+Example: <literal><command>send-hook</command> mutt "<command>set</command> mime_forward signature=''"</literal>
</para>
<para>
<note>
<para>
-send-hook's are only executed once after getting the initial
-list of recipients. Adding a recipient after replying or editing the
-message will not cause any send-hook to be executed. Also note that
-<literal>my_hdr</literal> commands which modify recipient headers, or the message's
-subject, don't have any effect on the current message when executed
-from a send-hook.
+<command>send-hook</command>'s are only executed once after getting the
+initial list of recipients. Adding a recipient after replying or
+editing the message will not cause any <command>send-hook</command> to be executed,
+similarily if <link linkend="autoedit">$autoedit</link> is set
+(as then the initial list of recipients is empty). Also note that <link
+linkend="my-hdr"><command>my_hdr</command></link> commands which
+modify recipient headers, or the message's subject, don't have any
+effect on the current message when executed from a
+<command>send-hook</command>.
</para>
</note>
</sect1>
<sect1 id="message-hook">
-<title>Change settings before formatting a message</title>
+<title>Change Settings Before Formatting a Message</title>
<para>Usage:</para>
before viewing or formatting a message based upon information about the message.
<emphasis>command</emphasis> is executed if the <emphasis>pattern</emphasis> matches the message to be
displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
+they are specified in the <literal>.muttrc</literal>.
</para>
<para>
</sect1>
<sect1 id="crypt-hook">
-<title>Choosing the cryptographic key of the recipient</title>
+<title>Choosing the Cryptographic Key of the Recipient</title>
<para>Usage:</para>
key with a given e-mail address automatically, either because the
recipient's public key can't be deduced from the destination address,
or because, for some reasons, you need to override the key Mutt would
-normally use. The <literal>crypt-hook</literal> command provides a
+normally use. The <command>crypt-hook</command> command provides a
method by which you can specify the ID of the public key to be used
when encrypting messages to a certain recipient.
</para>
</sect1>
<sect1 id="push">
-<title>Adding key sequences to the keyboard buffer</title>
+<title>Adding Key Sequences to the Keyboard Buffer</title>
<para>Usage:</para>
contain control characters, key names and function names like the sequence
string in the <link linkend="macro">macro</link> command. You may use it to
automatically run a sequence of commands at startup, or when entering
-certain folders. For example, the following command will automatically
-collapse all threads when entering a folder:
+certain folders. For example, <xref linkend="ex-folder-hook-push"/>
+shows how to automatically collapse all threads when entering a folder.
</para>
<example id="ex-folder-hook-push">
-<title>Embedding <literal>push</literal> in <literal>folder-hook</literal></title>
+<title>Embedding <command>push</command> in <command>folder-hook</command></title>
<screen>
folder-hook . 'push <collapse-all>'
</screen>
</sect1>
<sect1 id="exec">
-<title>Executing functions</title>
+<title>Executing Functions</title>
<para>Usage:</para>
<para>
This command can be used to execute any function. Functions are
listed in the <link linkend="functions">function reference</link>.
-<quote>exec function</quote> is equivalent to <quote>push <function></quote>.
+<quote><command>exec</command><literal>function</literal></quote> is equivalent to
+<quote><literal>push <function></literal></quote>.
</para>
</sect1>
<arg choice="plain">
<replaceable class="parameter">value</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unscore</command>
<group choice="req">
<arg choice="plain">
</cmdsynopsis>
<para>
-The <literal>score</literal> commands adds <emphasis>value</emphasis> to a message's score if <emphasis>pattern</emphasis>
+The <command>score</command> commands adds <emphasis>value</emphasis> to a message's score if <emphasis>pattern</emphasis>
matches it. <emphasis>pattern</emphasis> is a string in the format described in the <link linkend="patterns">patterns</link> section (note: For efficiency reasons, patterns
which scan information not available in the index, such as <literal>˜b</literal>,
<literal>˜B</literal> or <literal>˜h</literal>, may not be used). <emphasis>value</emphasis> is a
positive or negative integer. A message's final score is the sum total of all
-matching <literal>score</literal> entries. However, you may optionally prefix <emphasis>value</emphasis> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
+matching <command>score</command> entries. However, you may optionally prefix <emphasis>value</emphasis> with
+an equal sign (<quote>=</quote>) to cause evaluation to stop at a particular entry if there is
a match. Negative final scores are rounded up to 0.
</para>
<para>
-The <literal>unscore</literal> command removes score entries from the list. You <emphasis role="bold">must</emphasis>
-specify the same pattern specified in the <literal>score</literal> command for it to be
+The <command>unscore</command> command removes score entries from the list. You <emphasis>must</emphasis>
+specify the same pattern specified in the <command>score</command> command for it to be
removed. The pattern <quote>*</quote> is a special token which means to clear the list
of all score entries.
</para>
</sect1>
<sect1 id="spam">
-<title>Spam detection</title>
+<title>Spam Detection</title>
<para>Usage:</para>
<arg choice="plain">
<replaceable class="parameter">format</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>nospam</command>
<group choice="req">
<arg choice="plain">
<para>
Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <literal>spam</literal> and <literal>nospam</literal>
+By defining your spam patterns with the <command>spam</command> and <literal>nospam</literal>
commands, you can <emphasis>limit</emphasis>, <emphasis>search</emphasis>, and <emphasis>sort</emphasis> your
mail based on its spam attributes, as determined by the external
filter. You also can display the spam attributes in your index
<para>
Your first step is to define your external filter's spam patterns using
-the <literal>spam</literal> command. <emphasis>pattern</emphasis> should be a regular expression
+the <command>spam</command> command. <emphasis>pattern</emphasis> should be a regular expression
that matches a header in a mail message. If any message in the mailbox
matches this regular expression, it will receive a <quote>spam tag</quote> or
-<quote>spam attribute</quote> (unless it also matches a <literal>nospam</literal> pattern -- see
+<quote>spam attribute</quote> (unless it also matches a <command>nospam</command> pattern — see
below.) The appearance of this attribute is entirely up to you, and is
governed by the <emphasis>format</emphasis> parameter. <emphasis>format</emphasis> can be any static
text, but it also can include back-references from the <emphasis>pattern</emphasis>
the first back-reference in the regex, <literal>%2</literal> with the second, etc.
</para>
+<para>
+To match spam tags, mutt needs the corresponding header information
+which is always the case for local and POP folders but not for IMAP in
+the default configuration. Depending on the spam header to be analyzed,
+<link linkend="imap-headers">$imap_headers</link> may need
+to be adjusted.
+</para>
+
<para>
If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <literal>spam</literal> patterns for each
+one spam-related header. You can define <command>spam</command> patterns for each
filter you use. If a message matches two or more of these patterns, and
-the $spam_separator variable is set to a string, then the
+the <link linkend="spam-separator">$spam_separator</link> variable is set to a string, then the
message's spam tag will consist of all the <emphasis>format</emphasis> strings joined
-together, with the value of $spam_separator separating
+together, with the value of <link linkend="spam-separator">$spam_separator</link> separating
them.
</para>
<para>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
+For example, suppose one uses DCC, SpamAssassin, and PureMessage, then
+the configuration might look like in <xref linkend="ex-spam"/>.
</para>
<example id="ex-spam">
</example>
<para>
-If I then received a message that DCC registered with <quote>many</quote> hits
+If then a message is received that DCC registered with <quote>many</quote> hits
under the <quote>Fuz2</quote> checksum, and that PureMessage registered with a
97% probability of being spam, that message's spam tag would read
<literal>90+/DCC-Fuz2, 97/PM</literal>. (The four characters before <quote>=many</quote> in a
-DCC report indicate the checksum used -- in this case, <quote>Fuz2</quote>.)
+DCC report indicate the checksum used — in this case, <quote>Fuz2</quote>.)
</para>
<para>
-If the $spam_separator variable is unset, then each
+If the <link linkend="spam-separator">$spam_separator</link> variable is unset, then each
spam pattern match supersedes the previous one. Instead of getting
joined <emphasis>format</emphasis> strings, you'll get only the last one to match.
</para>
<para>
The spam tag is what will be displayed in the index when you use
-<literal>%H</literal> in the <literal>$index_format</literal> variable. It's also the
+<literal>%H</literal> in the <link linkend="index-format">$index_format</link> variable. It's also the
string that the <literal>˜H</literal> pattern-matching expression matches against for
<literal><search></literal> and <literal><limit></literal> functions. And it's what sorting by spam
attribute will use as a sort key.
<para>
That's a pretty complicated example, and most people's actual
environments will have only one spam filter. The simpler your
-configuration, the more effective mutt can be, especially when it comes
+configuration, the more effective Mutt can be, especially when it comes
to sorting.
</para>
<para>
-Generally, when you sort by spam tag, mutt will sort <emphasis>lexically</emphasis> --
+Generally, when you sort by spam tag, Mutt will sort <emphasis>lexically</emphasis> —
that is, by ordering strings alphanumerically. However, if a spam tag
-begins with a number, mutt will sort numerically first, and lexically
+begins with a number, Mutt will sort numerically first, and lexically
only when two numbers are equal in value. (This is like UNIX's
-<literal>sort -n</literal>.) A message with no spam attributes at all -- that is, one
-that didn't match <emphasis>any</emphasis> of your <literal>spam</literal> patterns -- is sorted at
+<literal>sort -n</literal>.) A message with no spam attributes at all — that is, one
+that didn't match <emphasis>any</emphasis> of your <command>spam</command> patterns — is sorted at
lowest priority. Numbers are sorted next, beginning with 0 and ranging
upward. Finally, non-numeric strings are sorted, with <quote>a</quote> taking lower
priority than <quote>z</quote>. Clearly, in general, sorting by spam tags is most
effective when you can coerce your filter to give you a raw number. But
-in case you can't, mutt can still do something useful.
+in case you can't, Mutt can still do something useful.
</para>
<para>
-The <literal>nospam</literal> command can be used to write exceptions to <literal>spam</literal>
-patterns. If a header pattern matches something in a <literal>spam</literal> command,
+The <command>nospam</command> command can be used to write exceptions to <command>spam</command>
+patterns. If a header pattern matches something in a <command>spam</command> command,
but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <literal>nospam</literal> command.
+more precise pattern under a <command>nospam</command> command.
</para>
<para>
-If the <emphasis>pattern</emphasis> given to <literal>nospam</literal> is exactly the same as the
-<emphasis>pattern</emphasis> on an existing <literal>spam</literal> list entry, the effect will be to
+If the <emphasis>pattern</emphasis> given to <command>nospam</command> is exactly the same as the
+<emphasis>pattern</emphasis> on an existing <command>spam</command> list entry, the effect will be to
remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <emphasis>pattern</emphasis> for a <literal>spam</literal> command matches an entry
-on the <literal>nospam</literal> list, that <literal>nospam</literal> entry will be removed. If the
-<emphasis>pattern</emphasis> for <literal>nospam</literal> is <quote>*</quote>, <emphasis>all entries on both lists</emphasis>
-will be removed. This might be the default action if you use <literal>spam</literal>
-and <literal>nospam</literal> in conjunction with a <literal>folder-hook</literal>.
+Likewise, if the <emphasis>pattern</emphasis> for a <command>spam</command> command matches an entry
+on the <command>nospam</command> list, that nospam entry will be removed. If the
+<emphasis>pattern</emphasis> for <command>nospam</command> is <quote>*</quote>, <emphasis>all entries on both lists</emphasis>
+will be removed. This might be the default action if you use <command>spam</command>
+and <command>nospam</command> in conjunction with a <command>folder-hook</command>.
</para>
<para>
-You can have as many <literal>spam</literal> or <literal>nospam</literal> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
+You can have as many <command>spam</command> or <command>nospam</command> commands as you like.
+You can even do your own primitive <command>spam</command> detection within Mutt — for
example, if you consider all mail from <literal>MAILER-DAEMON</literal> to be spam,
-you can use a <literal>spam</literal> command like this:
+you can use a <command>spam</command> command like this:
</para>
<screen>
<sect1 id="set">
<title>Setting and Querying Variables</title>
+<sect2 id="var-types">
+<title>Variable Types</title>
+
+<para>
+Mutt supports these types of configuration variables:
+</para>
+
+<variablelist>
+<varlistentry>
+<term>boolean</term>
+<listitem>
+<para>
+A boolean expression, either <quote>yes</quote> or <quote>no</quote>.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>number</term>
+<listitem>
+<para>
+A signed integer number in the range -32768 to 32767.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>string</term>
+<listitem>
+<para>
+Arbitrary text.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>path</term>
+<listitem>
+<para>
+A specialized string for representing paths including support for
+mailbox shortcuts (see <xref linkend="shortcuts"/>) as well as tilde
+(<quote>˜</quote>) for a user's home directory and more.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>quadoption</term>
+<listitem>
+<para>
+Like a boolean but triggers a prompt when set to <quote>ask-yes</quote>
+or <quote>ask-no</quote> with <quote>yes</quote> and <quote>no</quote>
+preselected respectively.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>sort order</term>
+<listitem>
+<para>
+A specialized string allowing only particular words as values depending
+on the variable.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>regular expression</term>
+<listitem>
+<para>
+A regular expression, see <xref linkend="regexp"/> for an introduction.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>folder magic</term>
+<listitem>
+<para>
+Specifies the type of folder to use: <emphasis>mbox</emphasis>,
+<emphasis>mmdf</emphasis>, <emphasis>mh</emphasis>
+or <emphasis>maildir</emphasis>.
+Currently only used to determine the type for newly created folders.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>e-mail address</term>
+<listitem>
+<para>
+An e-mail address either with or without
+realname. The older <quote><literal>user@example.org (Joe User)</literal></quote>
+form is supported but strongly deprecated.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>user-defined</term>
+<listitem>
+<para>
+Arbitrary text, see <xref linkend="set-myvar"/> for details.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
<sect2 id="set-commands">
<title>Commands</title>
<replaceable class="parameter">variable=value</replaceable>
</arg>
</group>
-<arg choice="opt" rep="repeat"/>
-</cmdsynopsis>
+<arg choice="opt" rep="repeat"></arg>
-<cmdsynopsis>
<command>toggle</command>
<arg choice="plain">
<replaceable class="parameter">variable</replaceable>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">variable</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>unset</command>
<arg choice="plain">
<replaceable class="parameter">variable</replaceable>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">variable</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
<command>reset</command>
<arg choice="plain">
<replaceable class="parameter">variable</replaceable>
</para>
<para>
-Prefixing a variable with <quote>no</quote> will unset it. Example: <literal>set noaskbcc</literal>.
+Prefixing a variable with <quote>no</quote> will unset it. Example: <literal><command>set</command> noaskbcc</literal>.
</para>
<para>
For <emphasis>boolean</emphasis> variables, you may optionally prefix the variable name with
<literal>inv</literal> to toggle the value (on or off). This is useful when writing
-macros. Example: <literal>set invsmart_wrap</literal>.
+macros. Example: <literal><command>set</command> invsmart_wrap</literal>.
</para>
<para>
-The <literal>toggle</literal> command automatically prepends the <literal>inv</literal> prefix to all
+The <command>toggle</command> command automatically prepends the <literal>inv</literal> prefix to all
specified variables.
</para>
<para>
-The <literal>unset</literal> command automatically prepends the <literal>no</literal> prefix to all
+The <command>unset</command> command automatically prepends the <literal>no</literal> prefix to all
specified variables.
</para>
</para>
<para>
-The <literal>reset</literal> command resets all given variables to the compile time
+The <command>reset</command> command resets all given variables to the compile time
defaults (hopefully mentioned in this manual). If you use the command
-<literal>set</literal> and prefix the variable with <quote>&</quote> this has the same
-behavior as the reset command.
+<command>set</command> and prefix the variable with <quote>&</quote> this has the same
+behavior as the <command>reset</command> command.
</para>
<para>
-With the <literal>reset</literal> command there exists the special variable <quote>all</quote>,
+With the <command>reset</command> command there exists the special variable <quote>all</quote>,
which allows you to reset all variables to their system defaults.
</para>
</sect2>
<sect2 id="set-myvar">
-<title>User-defined variables</title>
+<title>User-Defined Variables</title>
<sect3 id="set-myvar-intro">
<title>Introduction</title>
<para>
Along with the variables listed in the
-<link linkend="variables">Configuration variables</link> section, mutt
+<link linkend="variables">Configuration variables</link> section, Mutt
supports user-defined variables with names starting
with <literal>my_</literal> as in, for
example, <literal>my_cfgdir</literal>.
</para>
<para>
-The <literal>set</literal> command either creates a
+The <command>set</command> command either creates a
custom <literal>my_</literal> variable or changes its
-value if it does exist already. The <literal>unset</literal> and <literal>reset</literal>
+value if it does exist already. The <command>unset</command> and <command>reset</command>
commands remove the variable entirely.
</para>
<para>
The following example defines and uses the variable <literal>my_cfgdir</literal>
-to abbreviate the calls of the <link linkend="source">source</link> command:
+to abbreviate the calls of the <link linkend="source"><command>source</command></link> command:
</para>
<example id="ex-myvar1">
</example>
<para>
-Since mutt expands such values already when parsing the configuration
+Since Mutt expands such values already when parsing the configuration
file(s), the value of <literal>$my_delete</literal> in the
-last example would be the value of <literal>$delete</literal> exactly
+last example would be the value of <link linkend="delete">$delete</link> exactly
as it was at that point during parsing the configuration file. If
-another statement would change the value for <literal>$delete</literal>
+another statement would change the value for <link linkend="delete">$delete</link>
later in the same or another file, it would have no effect on
<literal>$my_delete</literal>. However, the expansion can
be deferred to runtime, as shown in the next example, when escaping the
<para>
Note that there is a space
between <literal><enter-command></literal> and
-the <literal>set</literal> configuration command, preventing mutt from
-recording the macro's commands into its history.
+the <command>set</command> configuration command, preventing Mutt from
+recording the <command>macro</command>'s commands into its history.
</para>
</sect3>
</sect1>
<sect1 id="source">
-<title>Reading initialization commands from another file</title>
+<title>Reading Initialization Commands From Another File</title>
<para>Usage:</para>
</para>
<para>
-If the filename ends with a vertical bar (|), then <emphasis>filename</emphasis> is
+If the filename ends with a vertical bar (<quote>|</quote>), then <emphasis>filename</emphasis> is
considered to be an executable program from which to read input (eg.
-<literal>source ˜/bin/myscript|</literal>).
+<literal><command>source</command> ˜/bin/myscript|</literal>).
</para>
</sect1>
<sect1 id="unhook">
-<title>Removing hooks</title>
+<title>Removing Hooks</title>
<para>Usage:</para>
This command permits you to flush hooks you have previously defined.
You can either remove all hooks by giving the <quote>*</quote> character as an
argument, or you can remove all hooks of a specific type by saying
-something like <literal>unhook send-hook</literal>.
+something like <literal><command>unhook</command> send-hook</literal>.
</para>
</sect1>
<para>
Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
+through the Mutt configuration, especially in the
<link linkend="index-format">$index_format</link>,
<link linkend="pager-format">$pager_format</link>,
<link linkend="status-format">$status_format</link>,
-and other <quote>*_format</quote> variables. These can be very straightforward,
+and other related variables. These can be very straightforward,
and it's quite possible you already know how to use them.
</para>
<para>
Some of the modifiers are borrowed right out of C (though you might
know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <literal>%-12.12s</literal>. As with
+the <literal>[-]m.n</literal> modifiers, as in <literal>%-12.12s</literal>. As with
such programming languages, these modifiers allow you to specify the
minimum and maximum size of the resulting string, as well as its
justification. If the <quote>-</quote> sign follows the percent, the string will
be left-justified instead of right-justified. If there's a number
immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
+formatted string will occupy — if it's naturally smaller than that, it
will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
+follow, that's the maximum space allowable — the string will not be
permitted to exceed that width, no matter its natural size. Each of
these three elements is optional, so that all these are legal format
-strings:
-<literal>%-12s</literal>
-<literal>%4c</literal>
-<literal>%.15F</literal>
-<literal>%-12.15L</literal>
+strings: <literal>%-12s</literal>, <literal>%4c</literal>,
+<literal>%.15F</literal> and <literal>%-12.15L</literal>.
</para>
<para>
symbol (<literal>=</literal>) as a numeric prefix (like the minus
above), it will force the string to be centered within its minimum
space range. For example, <literal>%=14y</literal> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<literal>$index_format</literal>. If the expansion
+characters for the %y expansion — that's the X-Label: header, in
+<link linkend="index-format">$index_format</link>. If the expansion
results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like <quote> test </quote>.
+14-character space. If the X-Label for a message were <quote>test</quote>, that
+expansion would look like <quote> test </quote>.
</para>
<para>
</sect2>
+<sect2 id="formatstrings-conditionals">
+<title>Conditionals</title>
+
+<para>
+Depending on the format string variable, some of its sequences can be
+used to optionally print a string if their value is nonzero. For
+example, you may only want to see the number of flagged messages if such
+messages exist, since zero is not particularly meaningful. To optionally
+print a string based upon one of the above sequences, the following
+construct is used:
+</para>
+
+<screen>
+%?<sequence_char>?<optional_string>?</screen>
+
+<para>
+where <emphasis>sequence_char</emphasis> is an expando, and
+<emphasis>optional_string</emphasis> is the string you would like printed if
+<emphasis>sequence_char</emphasis> is nonzero.
+<emphasis>optional_string</emphasis> may contain other
+sequences as well as normal text, but you may not nest optional
+strings.
+</para>
+
+<para>
+Here is an example illustrating how to optionally print the number of
+new messages in a mailbox in
+<link linkend="status-format">$status_format</link>:
+</para>
+
+<screen>
+%?n?%n new messages.?</screen>
+
+<para>
+You can also switch between two strings using the following construct:
+</para>
+
+<screen>
+%?<sequence_char>?<if_string>&<else_string>?</screen>
+
+<para>
+If the value of <emphasis>sequence_char</emphasis> is
+non-zero, <emphasis>if_string</emphasis> will be expanded,
+otherwise <emphasis>else_string</emphasis> will be expanded.
+</para>
+
+</sect2>
+
<sect2 id="formatstrings-filters">
<title>Filters</title>
</example>
<para>
-will make mutt expand <literal>%r</literal>,
+will make Mutt expand <literal>%r</literal>,
<literal>%f</literal> and <literal>%L</literal>
before calling the script. The example also shows that arguments can be
quoted: the script will receive the expanded string between the single quotes
<para>
A practical example is the <literal>mutt_xtitle</literal>
script installed in the <literal>samples</literal>
-subdirectory of the mutt documentation: it can be used as filter for
-<literal>$status_format</literal> to set the current
+subdirectory of the Mutt documentation: it can be used as filter for
+<link linkend="status-format">$status_format</link> to set the current
terminal's title, if supported.
</para>
</sect2>
+<sect2 id="formatstrings-padding">
+<title>Padding</title>
+
+<para>
+In most format strings, Mutt supports different types of padding using
+special %-expandos:
+</para>
+
+<variablelist>
+<varlistentry>
+<term><literal>%|X</literal></term>
+<listitem>
+<para>
+When this occurs, Mutt will fill the rest of the
+line with the character <literal>X</literal>. For
+example, filling the rest of the line with dashes is
+done by setting:
+</para>
+<screen>
+set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"</screen>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>
+<literal>%>X</literal>
+</term>
+<listitem>
+<para>
+Since the previous expando stops at the end of line, there must be a way
+to fill the gap between two items via the <literal>%>X</literal>
+expando: it puts as many characters <literal>X</literal> in between two
+items so that the rest of the line will be right-justified. For example,
+to not put the version string and hostname the above example on the left
+but on the right and fill the gap with spaces, one might use (note the
+space after <literal>%></literal>):
+</para>
+<screen>
+set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"</screen>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><literal>%*X</literal>
+</term>
+<listitem>
+<para>
+Normal right-justification will print everything to the left of the
+<literal>%></literal>, displaying padding and whatever lies to the
+right only if there's room. By contrast, <quote>soft-fill</quote> gives
+priority to the right-hand side, guaranteeing space to display it and
+showing padding only if there's still room. If necessary, soft-fill will
+eat text leftwards to make room for rightward text. For example, to
+right-justify the subject making sure as much as possible of it fits on
+screen, one might use (note two spaces after <literal>%*
+</literal>: the second ensures there's a space between the truncated
+right-hand side and the subject):
+</para>
+<screen>
+set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?)%* %s"</screen>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
</sect1>
</chapter>
<note>
<para>
-Note that <quote>\</quote>
+<quote>\</quote>
must be quoted if used for a regular expression in an initialization
command: <quote>\\</quote>.
</para>
<note>
<para>
-Note that the regular expression can be enclosed/delimited by either "
+The regular expression can be enclosed/delimited by either "
or ' which is useful if the regular expression includes a white-space
character. See <xref linkend="muttrc-syntax"/>
for more information on " and ' delimiter processing. To match a
<para>
A list of characters enclosed by <quote>[</quote> and <quote>]</quote> matches any
single character in that list; if the first character of the list
-is a caret <quote>ˆ</quote> then it matches any character <emphasis role="bold">not</emphasis> in the
-list. For example, the regular expression <emphasis role="bold">[0123456789]</emphasis>
+is a caret <quote>ˆ</quote> then it matches any character <emphasis>not</emphasis> in the
+list. For example, the regular expression <emphasis>[0123456789]</emphasis>
matches any single digit. A range of ASCII characters may be specified
by giving the first and last characters, separated by a hyphen
<quote>-</quote>. Most metacharacters lose their special meaning inside
Note that the brackets in these
class names are part of the symbolic names, and must be included
in addition to the brackets delimiting the bracket list. For
-example, <emphasis role="bold">[[:digit:]]</emphasis> is equivalent to
-<emphasis role="bold">[0-9]</emphasis>.
+example, <emphasis>[[:digit:]]</emphasis> is equivalent to
+<emphasis>[0-9]</emphasis>.
</para>
</note>
<para>
A collating symbol is a multi-character collating element enclosed in
<quote>[.</quote> and <quote>.]</quote>. For example, if <quote>ch</quote> is a collating
-element, then <emphasis role="bold">[[.ch.]]</emphasis> is a regexp that matches
-this collating element, while <emphasis role="bold">[ch]</emphasis> is a regexp that
+element, then <emphasis>[[.ch.]]</emphasis> is a regexp that matches
+this collating element, while <emphasis>[ch]</emphasis> is a regexp that
matches either <quote>c</quote> or <quote>h</quote>.
</para>
</listitem>
characters that are equivalent. The name is enclosed in <quote>[=</quote>
and <quote>=]</quote>. For example, the name <quote>e</quote> might be used to
represent all of <quote>è</quote> <quote>é</quote> and <quote>e</quote>. In this case,
-<emphasis role="bold">[[=e=]]</emphasis> is a regexp that matches any of
+<emphasis>[[=e=]]</emphasis> is a regexp that matches any of
<quote>è</quote>, <quote>é</quote> and <quote>e</quote>.
</para>
</listitem>
<note>
<para>
-If you compile Mutt with the GNU <emphasis>rx</emphasis> package, the
+If you compile Mutt with the included regular expression engine, the
following operators may also be used in regular expressions as described in <xref linkend="regex-gnu-ext"/>.
</para>
</note>
<sect1 id="patterns">
<title>Patterns: Searching, Limiting and Tagging</title>
+<sect2 id="patterns-modifier">
+<title>Pattern Modifier</title>
+
<para>
Many of Mutt's commands allow you to specify a pattern to match
(<literal>limit</literal>, <literal>tag-pattern</literal>,
<row><entry>~n [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a score in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
<row><entry>~N</entry><entry>new messages</entry></row>
<row><entry>~O</entry><entry>old messages</entry></row>
-<row><entry>~p</entry><entry>messages addressed to you (consults alternates)</entry></row>
-<row><entry>~P</entry><entry>messages from you (consults alternates)</entry></row>
+<row><entry>~p</entry><entry>messages addressed to you (consults <command>alternates</command>)</entry></row>
+<row><entry>~P</entry><entry>messages from you (consults <command>alternates</command>)</entry></row>
<row><entry>~Q</entry><entry>messages which have been replied to</entry></row>
<row><entry>~r [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <quote>date-received</quote> in a Date range</entry></row>
<row><entry>~R</entry><entry>read messages</entry></row>
<row><entry>~U</entry><entry>unread messages</entry></row>
<row><entry>~v</entry><entry>messages part of a collapsed thread.</entry></row>
<row><entry>~V</entry><entry>cryptographically verified messages</entry></row>
-<row><entry>~x <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>References</quote> field</entry></row>
+<row><entry>~x <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>References</quote> or <quote>In-Reply-To</quote> field</entry></row>
<row><entry>~X [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> attachments *)</entry></row>
<row><entry>~y <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>X-Label</quote> field</entry></row>
-<row><entry>~z [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a size in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
+<row><entry>~z [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a size in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *) **)</entry></row>
<row><entry>~=</entry><entry>duplicated messages (see <link linkend="duplicate-threads">$duplicate_threads</link>)</entry></row>
<row><entry>~$</entry><entry>unreferenced messages (requires threaded view)</entry></row>
<row><entry>~(<emphasis>PATTERN</emphasis>)</entry><entry>messages in threads
<para>
Where <emphasis>EXPR</emphasis> is a
-<link linkend="regexp">regular expression</link>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
+<link linkend="regexp">regular expression</link>.
+</para>
+
+<para>
+*) The forms <quote><[<emphasis>MAX</emphasis>]</quote>, <quote>>[<emphasis>MIN</emphasis>]</quote>,
+<quote>[<emphasis>MIN</emphasis>]-</quote> and <quote>-[<emphasis>MAX</emphasis>]</quote>
+are allowed, too.
+</para>
+
+<para>
+**) The suffixes <quote>K</quote> and <quote>M</quote> are allowed to specify kilobyte and megabyte respectively.
+</para>
+
+<para>
+Special attention has to be
+payed when using regular expressions inside of patterns. Specifically,
Mutt's parser for these patterns will strip one level of backslash (<quote>\</quote>),
which is normally used for quoting. If it is your intention to use a
backslash in the regular expression, you will need to use two backslashes
-instead (<quote>\\</quote>). You can force mutt to treat <emphasis>EXPR</emphasis> as a simple string
+instead (<quote>\\</quote>). You can force Mutt to treat <emphasis>EXPR</emphasis> as a simple string
instead of a regular expression by using = instead of ˜ in the
pattern name. For example, <literal>=b *.*</literal> will find all messages that contain
the literal string <quote>*.*</quote>. Simple string matches are less powerful than
regular expressions but can be considerably faster. This is especially
true for IMAP folders, because string matches can be performed on the
server instead of by fetching every message. IMAP treats <literal>=h</literal> specially:
-it must be of the form "header: substring" and will not partially
+it must be of the form <quote>header: substring</quote> and will not partially
match header names. The substring part may be omitted if you simply
wish to find messages containing a particular header without regard to
its value.
</para>
<para>
-*) The forms <quote><[<emphasis>MAX</emphasis>]</quote>, <quote>>[<emphasis>MIN</emphasis>]</quote>,
-<quote>[<emphasis>MIN</emphasis>]-</quote> and <quote>-[<emphasis>MAX</emphasis>]</quote>
-are allowed, too.
-</para>
-
-<sect2 id="patterns-modifier">
-<title>Pattern Modifier</title>
-
-<note>
-<para>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
+Patterns matching lists of addresses (notably c, C, p, P and t)
match if there is at least one match in the whole list. If you want to
make sure that all elements of that list match, you need to prefix your
pattern with <quote>ˆ</quote>.
This example matches all mails which only has recipients from Germany.
</para>
-</note>
+<example id="ex-recips">
+<title>Matching all addresses in address lists</title>
<screen>
^~C \.de$
</screen>
+</example>
</sect2>
-<sect2 id="simple-patterns">
-<title>Simple Patterns</title>
+<sect2 id="simple-searches">
+<title>Simple Searches</title>
<para>
-Mutt supports two versions of so called <quote>simple searches</quote> which are
+Mutt supports two versions of so called <quote>simple searches</quote>. These are
issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
+operations does not seem to contain a valid pattern modifier (i.e. it does not contain
one of these characters: <quote>˜</quote>, <quote>=</quote> or <quote>%</quote>). If the query is
supposed to contain one of these special characters, they must be escaped
by prepending a backslash (<quote>\</quote>).
</sect2>
<sect2 id="complex-patterns">
-<title>Complex Patterns</title>
+<title>Nesting and Boolean Operators</title>
<para>
Logical AND is performed by specifying more than one criterion. For
<para>
would select messages which contain the word <quote>mutt</quote> in the list of
-recipients <emphasis role="bold">and</emphasis> that have the word <quote>elkins</quote> in the <quote>From</quote> header
+recipients <emphasis>and</emphasis> that have the word <quote>elkins</quote> in the <quote>From</quote> header
field.
</para>
<listitem>
<para>
-! -- logical NOT operator
+! — logical NOT operator
</para>
</listitem>
<listitem>
<para>
-| -- logical OR operator
+| — logical OR operator
</para>
</listitem>
<listitem>
<para>
-() -- logical grouping operator
+() — logical grouping operator
</para>
</listitem>
<note>
<para>
If a regular expression contains parenthesis, or a vertical bar
-("|"), you <emphasis role="bold">must</emphasis> enclose the expression in double or single quotes since
+("|"), you <emphasis>must</emphasis> enclose the expression in double or single quotes since
those characters are also used to separate different parts of Mutt's
pattern language. For example: <literal>~f "me@(mutt\.org|cs\.hmc\.edu)"</literal>
-</para>
-</note>
-
-<para>
Without the quotes, the parenthesis wouldn't end.
This would be separated to two OR'd patterns: <emphasis>˜f me@(mutt\.org</emphasis>
and <emphasis>cs\.hmc\.edu)</emphasis>. They are never what you want.
</para>
+</note>
</sect2>
Mutt supports two types of dates, <emphasis>absolute</emphasis> and <emphasis>relative</emphasis>.
</para>
+<sect3 id="date-absolute">
+<title>Absolute Dates</title>
+
<para>
-<emphasis role="bold">Absolute</emphasis>. Dates <emphasis role="bold">must</emphasis> be in DD/MM/YY format (month and year are
+Dates <emphasis>must</emphasis> be in DD/MM/YY format (month and year are
optional, defaulting to the current month and year). An example of a valid
range of dates is:
</para>
</para>
<para>
-<emphasis role="bold">Error Margins</emphasis>. You can add error margins to absolute dates.
+You can add error margins to absolute dates.
An error margin is a sign (+ or -), followed by a digit, followed by
one of the units in <xref linkend="tab-date-units"/>. As a special case, you can replace the
sign by a <quote>*</quote> character, which is equivalent to giving identical plus and minus error margins.
Limit to messages matching: ~d 15/1/2001*2w
</screen>
+</sect3>
+
+<sect3 id="dates-relative">
+<title>Relative Dates</title>
+
<para>
-<emphasis role="bold">Relative</emphasis>. This type of date is relative to the current date, and may
+This type of date is relative to the current date, and may
be specified as:
</para>
<listitem>
<para>
-><emphasis>offset</emphasis> (messages older than <emphasis>offset</emphasis> units)
+><emphasis>offset</emphasis> for messages older than <emphasis>offset</emphasis> units
</para>
</listitem>
<listitem>
<para>
-<<emphasis>offset</emphasis> (messages newer than <emphasis>offset</emphasis> units)
+<<emphasis>offset</emphasis> for messages newer than <emphasis>offset</emphasis> units
</para>
</listitem>
<listitem>
<para>
-=<emphasis>offset</emphasis> (messages exactly <emphasis>offset</emphasis> units old)
+=<emphasis>offset</emphasis> for messages exactly <emphasis>offset</emphasis> units old
</para>
</listitem>
<note>
<para>
All dates used when searching are relative to the
-<emphasis role="bold">local</emphasis> time zone, so unless you change the setting of your <link linkend="index-format">$index_format</link> to include a
-<literal>%[...]</literal> format, these are <emphasis role="bold">not</emphasis> the dates shown
+<emphasis>local</emphasis> time zone, so unless you change the setting of your <link linkend="index-format">$index_format</link> to include a
+<literal>%[...]</literal> format, these are <emphasis>not</emphasis> the dates shown
in the main index.
</para>
</note>
+</sect3>
+
</sect2>
</sect1>
<para>
Once you have tagged the desired messages, you can use the
<quote>tag-prefix</quote> operator, which is the <quote>;</quote> (semicolon) key by default.
-When the <quote>tag-prefix</quote> operator is used, the <emphasis role="bold">next</emphasis> operation will
+When the <quote>tag-prefix</quote> operator is used, the <emphasis>next</emphasis> operation will
be applied to all tagged messages if that operation can be used in that
manner. If the <link linkend="auto-tag">$auto_tag</link>
variable is set, the next operation applies to the tagged messages
</para>
<para>
-In <link linkend="macro">macros</link> or <link linkend="push">push</link> commands,
-you can use the <quote>tag-prefix-cond</quote> operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the <quote>end-cond</quote>
-operator; after this operator the rest of the macro will be executed as
+In <link linkend="macro"><command>macro</command>s</link> or <link linkend="push"><command>push</command></link> commands,
+you can use the <literal><tag-prefix-cond></literal> operator. If there are no tagged
+messages, Mutt will <quote>eat</quote> the rest of the macro to abort it's execution.
+Mutt will stop <quote>eating</quote> the macro when it encounters the <literal><end-cond></literal>
+operator; after this operator the rest of the macro will be executed as
normal.
</para>
reading, or to whom you are sending mail. In the Mutt world, a <emphasis>hook</emphasis>
consists of a <link linkend="regexp">regular expression</link> or
<link linkend="patterns">pattern</link> along with a
-configuration option/command. See
+configuration option/command. See:
<itemizedlist>
-<listitem>
+<listitem>
<para>
-<link linkend="folder-hook">folder-hook</link>
+<link linkend="account-hook"><command>account-hook</command></link>
</para>
</listitem>
+
<listitem>
+<para>
+<link linkend="charset-hook"><command>charset-hook</command></link>
+</para>
+</listitem>
+<listitem>
<para>
-<link linkend="send-hook">send-hook</link>
+<link linkend="crypt-hook"><command>crypt-hook</command></link>
</para>
</listitem>
+
<listitem>
+<para>
+<link linkend="fcc-hook"><command>fcc-hook</command></link>
+</para>
+</listitem>
+<listitem>
<para>
-<link linkend="message-hook">message-hook</link>
+<link linkend="fcc-save-hook"><command>fcc-save-hook</command></link>
</para>
</listitem>
+
<listitem>
+<para>
+<link linkend="folder-hook"><command>folder-hook</command></link>
+</para>
+</listitem>
+<listitem>
<para>
-<link linkend="save-hook">save-hook</link>
+<link linkend="iconv-hook"><command>iconv-hook</command></link>
</para>
</listitem>
+
<listitem>
+<para>
+<link linkend="mbox-hook"><command>mbox-hook</command></link>
+</para>
+</listitem>
+<listitem>
<para>
-<link linkend="mbox-hook">mbox-hook</link>
+<link linkend="message-hook"><command>message-hook</command></link>
</para>
</listitem>
+
<listitem>
+<para>
+<link linkend="reply-hook"><command>reply-hook</command></link>
+</para>
+</listitem>
+<listitem>
<para>
-<link linkend="fcc-hook">fcc-hook</link>
+<link linkend="save-hook"><command>save-hook</command></link>
</para>
</listitem>
+
<listitem>
+<para>
+<link linkend="send-hook"><command>send-hook</command></link>
+</para>
+</listitem>
+<listitem>
<para>
-<link linkend="fcc-save-hook">fcc-save-hook</link>
+<link linkend="send2-hook"><command>send2-hook</command></link>
</para>
</listitem>
<note>
<para>
If a hook changes configuration settings, these changes remain
-effective until the end of the current mutt session. As this is generally
-not desired, a default hook needs to be added before all other hooks to
-restore configuration defaults. Here is an example with send-hook and the
-my_hdr directive:
+effective until the end of the current Mutt session. As this is generally
+not desired, a <quote>default</quote> hook needs to be added before all
+other hooks of that type to restore configuration defaults.
</para>
</note>
-<example id="ex-send-hook-my-hdr">
-<title>Combining <literal>send-hook</literal> and <literal>my_hdr</literal></title>
+<example id="ex-default-hook">
+<title>Specifying a <quote>default</quote> hook</title>
<screen>
send-hook . 'unmy_hdr From:'
send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
</screen>
</example>
+<para>
+In <xref linkend="ex-default-hook"/>, by default the value of
+<link linkend="from">$from</link>
+and <link linkend="realname">$realname</link>
+is not overridden. When sending messages either To: or Cc:
+to <literal><b@b.b></literal>, the From: header is changed to
+<literal><c@c.c></literal>.
+</para>
+
<sect2 id="pattern-hook" xreflabel="Message Matching in Hooks">
<title>Message Matching in Hooks</title>
<para>
-Hooks that act upon messages (<literal>message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</literal>) are evaluated in a
+Hooks that act upon messages (<command>message-hook</command>, <command>reply-hook</command>,
+<command>send-hook</command>, <command>send2-hook</command>, <command>save-hook</command>, <command>fcc-hook</command>) are evaluated in a
slightly different manner. For the other
types of hooks, a <link linkend="regexp">regular expression</link> is
sufficient. But in dealing with messages a finer grain of control is
language for matching messages in hook commands. This works in
exactly the same way as it would when <emphasis>limiting</emphasis> or
<emphasis>searching</emphasis> the mailbox, except that you are restricted to those
-operators which match information mutt extracts from the header of
+operators which match information Mutt extracts from the header of
the message (i.e., from, to, cc, date, subject, etc.).
</para>
<para>
Mutt supports connecting to external directory databases such as LDAP,
-ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
+ph/qi, bbdb, or NIS through a wrapper script which connects to Mutt
using a simple interface. Using the <link linkend="query-command">$query_command</link> variable, you specify the wrapper
command to use. For example:
</para>
</screen>
<para>
-There are two mechanisms for accessing the query function of mutt. One
+There are two mechanisms for accessing the query function of Mutt. One
is to do a query from the index menu using the <literal><query></literal> function (default: Q).
This will prompt for a query, then bring up the query menu which will
list the matching responses. From the query menu, you can select
The other mechanism for accessing the query function is for address
completion, similar to the alias completion. In any prompt for address
entry, you can use the <literal><complete-query></literal> function (default: ˆT) to run a
-query based on the current address you have typed. Like aliases, mutt
+query based on the current address you have typed. Like aliases, Mutt
will look for what you have typed back to the last space or comma. If
-there is a single response for that query, mutt will expand the address
-in place. If there are multiple responses, mutt will activate the query
+there is a single response for that query, Mutt will expand the address
+in place. If there are multiple responses, Mutt will activate the query
menu. At the query menu, you can select one or more addresses to be
added to the prompt.
</para>
<title>Mailbox Formats</title>
<para>
-Mutt supports reading and writing of four different mailbox formats:
+Mutt supports reading and writing of four different local mailbox formats:
mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there
is no need to use a flag for different mailbox types. When creating new
-mailboxes, Mutt uses the default specified with the <link linkend="mbox-type">$mbox_type</link> variable.
+mailboxes, Mutt uses the default specified with the
+<link linkend="mbox-type">$mbox_type</link> variable. A
+short description of the formats follows.
</para>
<para>
-<emphasis role="bold">mbox</emphasis>. This is the most widely used mailbox format for UNIX. All
+<emphasis>mbox</emphasis>. This is a widely used mailbox format for UNIX. All
messages are stored in a single file. Each message has a line of the form:
</para>
<para>
to denote the start of a new message (this is often referred to as the
-<quote>From_</quote> line).
+<quote>From_</quote> line). The mbox format requires mailbox
+locking, is prone to mailbox corruption with concurrently writing
+clients or misinterpreted From_ lines. Depending on the
+environment, new mail detection can be unreliable. Mbox folders are fast
+to open and easy to archive.
</para>
<para>
-<emphasis role="bold">MMDF</emphasis>. This is a variant of the <emphasis>mbox</emphasis> format. Each message is
-surrounded by lines containing <quote>ˆAˆAˆAˆA</quote> (four control-A's).
+<emphasis>MMDF</emphasis>. This is a variant of
+the <emphasis>mbox</emphasis> format. Each message is surrounded by
+lines containing <quote>ˆAˆAˆAˆA</quote> (four
+control-A's). The same problems as for mbox apply (also with finding the
+right message separator as four control-A's may appear in message
+bodies).
</para>
<para>
-<emphasis role="bold">MH</emphasis>. A radical departure from <emphasis>mbox</emphasis> and <emphasis>MMDF</emphasis>, a mailbox
+<emphasis>MH</emphasis>. A radical departure from <emphasis>mbox</emphasis> and <emphasis>MMDF</emphasis>, a mailbox
consists of a directory and each message is stored in a separate file.
The filename indicates the message number (however, this is may not
correspond to the message number Mutt displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
+renamed with a comma (<quote>,</quote>) prepended to the filename. Mutt
detects this type of mailbox by looking for either <literal>.mh_sequences</literal>
-or <literal>.xmhcache</literal> (needed to distinguish normal directories from MH
-mailboxes).
+or <literal>.xmhcache</literal> files (needed to distinguish normal directories from MH
+mailboxes). MH is more robust with concurrent clients writing the mailbox,
+but still may suffer from lost flags; message corruption is less likely
+to occur than with mbox/mmdf. It's usually slower to open compared to
+mbox/mmdf since many small files have to be read (Mutt provides
+<xref linkend="header-caching"/> to greatly speed this process up).
+Depending on the environment, MH is not very disk-space efficient.
</para>
<para>
-<emphasis role="bold">Maildir</emphasis>. The newest of the mailbox formats, used by the Qmail MTA (a
+<emphasis>Maildir</emphasis>. The newest of the mailbox formats, used by the Qmail MTA (a
replacement for sendmail). Similar to <emphasis>MH</emphasis>, except that it adds three
subdirectories of the mailbox: <emphasis>tmp</emphasis>, <emphasis>new</emphasis> and <emphasis>cur</emphasis>. Filenames
for the messages are chosen in such a way they are unique, even when two
programs are writing the mailbox over NFS, which means that no file locking
-is needed.
+is needed and corruption is very unlikely. Maildir maybe
+slower to open without caching in Mutt, it too is not very
+disk-space efficient depending on the environment. Since no additional
+files are used for metadata (which is embedded in the message filenames)
+and Maildir is locking-free, it's easy to sync across different machines
+using file-level synchronization tools.
</para>
</sect1>
<para>
There are a number of built in shortcuts which refer to specific mailboxes.
These shortcuts can be used anywhere you are prompted for a file or mailbox
-path.
+path or in path-related configuration variables. Note that these only
+work at the beginning of a string.
</para>
<itemizedlist>
<listitem>
<para>
-! -- refers to your <link linkend="spoolfile">$spoolfile</link> (incoming) mailbox
+! — refers to your <link linkend="spoolfile">$spoolfile</link> (incoming) mailbox
</para>
</listitem>
<listitem>
<para>
-> -- refers to your <link linkend="mbox">$mbox</link> file
+> — refers to your <link linkend="mbox">$mbox</link> file
</para>
</listitem>
<listitem>
<para>
-< -- refers to your <link linkend="record">$record</link> file
+< — refers to your <link linkend="record">$record</link> file
</para>
</listitem>
<listitem>
<para>
-ˆ -- refers to the current mailbox
+ˆ — refers to the current mailbox
</para>
</listitem>
<listitem>
<para>
-- or !! -- refers to the file you've last visited
+- or !! — refers to the file you've last visited
</para>
</listitem>
<listitem>
<para>
-˜ -- refers to your home directory
+˜ — refers to your home directory
</para>
</listitem>
<listitem>
<para>
-= or + -- refers to your <link linkend="folder">$folder</link> directory
+= or + — refers to your <link linkend="folder">$folder</link> directory
</para>
</listitem>
<listitem>
<para>
-@<emphasis>alias</emphasis> -- refers to the <link linkend="save-hook">default save folder</link> as determined by the address of the alias
+@<emphasis>alias</emphasis> — refers to the <link linkend="save-hook">default save folder</link> as determined by the address of the alias
</para>
</listitem>
</itemizedlist>
+<para>
+For example, to store a copy of outgoing messages in the folder they
+were composed in,
+a <link linkend="folder-hook"><command>folder-hook</command></link> can
+be used to set <link linkend="record">$record</link>:
+</para>
+
+<screen>
+folder-hook . 'set record=ˆ'</screen>
+
</sect1>
<sect1 id="using-lists">
know what addresses you consider to be mailing lists (technically
this does not have to be a mailing list, but that is what it is most
often used for), and what lists you are subscribed to. This is
-accomplished through the use of the <link linkend="lists">lists and subscribe</link> commands in your muttrc.
+accomplished through the use of the <link linkend="lists"><command>lists</command> and <command>subscribe</command></link> commands in your <literal>.muttrc</literal>.
</para>
<para>
things, the first of which is the ability to show the name of a list
through which you received a message (i.e., of a subscribed list) in
the <emphasis>index</emphasis> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <link linkend="index-format">$index_format</link> variable, the escape <quote>%L</quote>
-will return the string <quote>To <list></quote> when <quote>list</quote> appears in the
+personal and list mail in the same mailbox. In the <link linkend="index-format">$index_format</link> variable, the expando <quote>%L</quote>
+will print the string <quote>To <list></quote> when <quote>list</quote> appears in the
<quote>To</quote> field, and <quote>Cc <list></quote> when it appears in the <quote>Cc</quote>
-field (otherwise it returns the name of the author).
+field (otherwise it prints the name of the author).
</para>
<para>
<para>
Mutt also supports the <literal>Mail-Followup-To</literal> header. When you send
a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <link linkend="followup-to">$followup_to</link> option is set, mutt will generate
+subscribed mailing lists, and if the <link linkend="followup-to">$followup_to</link> option is set, Mutt will generate
a Mail-Followup-To header which contains all the recipients to whom
you send this message, but not your address. This indicates that
group-replies or list-replies (also known as <quote>followups</quote>) to this
<para>
Conversely, when group-replying or list-replying to a message which
-has a <literal>Mail-Followup-To</literal> header, mutt will respect this header if
+has a <literal>Mail-Followup-To</literal> header, Mutt will respect this header if
the <link linkend="honor-followup-to">$honor_followup_to</link> configuration
-variable is set. Using list-reply will in this case also make sure
+variable is set. Using <link linkend="list-reply">list-reply</link> will in this case also make sure
that the reply goes to the mailing list, even if it's not specified
in the list of recipients in the <literal>Mail-Followup-To</literal>.
</para>
The <quote>X-Label:</quote> header field can be used to further identify mailing
lists or list subject matter (or just to annotate messages
individually). The <link linkend="index-format">$index_format</link> variable's <quote>%y</quote> and
-<quote>%Y</quote> escapes can be used to expand <quote>X-Label:</quote> fields in the
+<quote>%Y</quote> expandos can be used to expand <quote>X-Label:</quote> fields in the
index, and Mutt's pattern-matcher can match regular expressions to
<quote>X-Label:</quote> fields with the <quote>˜y</quote> selector. <quote>X-Label:</quote> is not a
standard message header field, but it can easily be inserted by procmail
When in the index menu and being idle (also see
<link linkend="timeout">$timeout</link>), Mutt periodically checks
for new mail in all folders which have been configured via the
-<literal>mailboxes</literal> command. The interval depends on the folder
+<command>mailboxes</command> command. The interval depends on the folder
type: for local/IMAP folders it consults
<link linkend="mail-check">$mail_check</link> and
<link linkend="pop-checkinterval">$pop_checkinterval</link>
Outside the index menu the directory browser supports checking
for new mail using the <literal><check-new></literal> function which is
unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <literal>mailboxes</literal> command,
+menu showing the files specified by the <command>mailboxes</command> command,
and indicate which contain new messages. Mutt will automatically enter this
mode when invoked from the command line with the <literal>-y</literal> option.
</para>
<para>
For the index, by default Mutt displays the number of mailboxes with new
mail in the status bar, please refer to the
-<link linkend="index-format">$index_format</link>
+<link linkend="status-format">$status_format</link>
variable for details.
</para>
</sect1>
<sect1 id="editing-threads">
-<title>Editing threads</title>
+<title>Editing Threads</title>
<para>
Mutt has the ability to dynamically restructure threads that are broken
either by misconfigured software or bad behavior from some
-correspondents. This allows to clean your mailboxes formats) from these
+correspondents. This allows to clean your mailboxes from these
annoyances which make it hard to follow a discussion.
</para>
<sect2 id="link-threads">
-<title>Linking threads</title>
+<title>Linking Threads</title>
<para>
-Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
-"References:" headers when replying to a message. This results in broken
+Some mailers tend to <quote>forget</quote> to correctly set the <quote>In-Reply-To:</quote> and
+<quote>References:</quote> headers when replying to a message. This results in broken
discussions because Mutt has not enough information to guess the correct
threading.
You can fix this by tagging the reply, then moving to the parent message
and using the <literal><link-threads></literal> function (bound to & by default). The
-reply will then be connected to this "parent" message.
+reply will then be connected to this parent message.
</para>
<para>
You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
+<literal><tag-prefix></literal> command (';') or the <link linkend="auto-tag">$auto_tag</link> option.
</para>
</sect2>
<sect2 id="break-threads">
-<title>Breaking threads</title>
+<title>Breaking Threads</title>
<para>
On mailing lists, some people are in the bad habit of starting a new
-discussion by hitting "reply" to any message from the list and changing
+discussion by hitting <quote>reply</quote> to any message from the list and changing
the subject to a totally unrelated one.
You can fix such threads by using the <literal><break-thread></literal> function (bound
by default to #), which will turn the subthread starting from the
<para>
For SMTP delivery using <link
linkend="smtp-url">$smtp_url</link>, it depends on the
-capabilities announced by the server whether mutt will attempt to
+capabilities announced by the server whether Mutt will attempt to
request DSN or not.
</para>
</sect1>
-</chapter>
+<sect1 id="misc-topics">
+<title>Miscellany</title>
+
+<para>
+This section documents various features that fit nowhere else.
+</para>
+
+<variablelist>
+<varlistentry>
+<term>
+Address normalization
+</term>
+<listitem>
+<para>
+Mutt normalizes all e-mail addresses to the simplest form possible. If
+an address contains a realname, the form
+<emphasis>Joe User <joe@example.com></emphasis> is used and the
+pure e-mail address without angle brackets otherwise, i.e. just
+<emphasis>joe@example.com</emphasis>.
+</para>
+<para>
+This normalization affects all headers Mutt generates including aliases.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>
+Initial folder selection
+</term>
+<listitem>
+<para>
+The folder Mutt opens at startup is determined as follows: the folder
+specified in the <literal>$MAIL</literal> environment variable if
+present. Otherwise, the value of <literal>$MAILDIR</literal> is taken
+into account. If that isn't present either, Mutt takes the user's
+mailbox in the mailspool as determined at compile-time (which may also
+reside in the home directory). The
+<link linkend="spoolfile">$spoolfile</link> setting overrides
+this selection. Highest priority has the mailbox given with the
+<literal>-f</literal> command line option.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect1>
+
+</chapter>
<chapter id="mimesupport">
<title>Mutt's MIME Support</title>
</para>
<sect2 id="mime-pager">
-<title>Viewing MIME messages in the pager</title>
+<title>Viewing MIME Messages in the Pager</title>
<para>
When you select a message from the index and view it in the pager, Mutt
<title>The Attachment Menu</title>
<para>
-The default binding for <literal>view-attachments</literal> is `v', which displays the
+The default binding for <literal><view-attachments></literal> is <quote>v</quote>, which displays the
attachment menu for a message. The attachment menu displays a list of
the attachments in a message. From the attachment menu, you can save,
print, pipe, delete, and view attachments. You can apply these
operations to a group of attachments at once, by tagging the attachments
-and by using the <quote>tag-prefix</quote> operator. You can also reply to the
+and by using the <literal><tag-prefix></literal> operator. You can also reply to the
current message from this menu, and only the current attachment (or the
attachments tagged) will be quoted in your reply. You can view
attachments as text, or view them using the mailcap viewer definition.
<para>
The '-' denotes that Mutt will delete the file after sending (or
postponing, or canceling) the message. It can be toggled with the
-<literal>toggle-unlink</literal> command (default: u). The next field is the MIME
-content-type, and can be changed with the <literal>edit-type</literal> command
+<literal><toggle-unlink></literal> command (default: u). The next field is the MIME
+content-type, and can be changed with the <literal><edit-type></literal> command
(default: ˆT). The next field is the encoding for the attachment,
which allows a binary message to be encoded for transmission on 7bit
-links. It can be changed with the <literal>edit-encoding</literal> command
+links. It can be changed with the <literal><edit-encoding></literal> command
(default: ˆE). The next field is the size of the attachment,
rounded to kilobytes or megabytes. The next field is the filename,
-which can be changed with the <literal>rename-file</literal> command (default: R).
+which can be changed with the <literal><rename-file></literal> command (default: R).
The final field is the description of the attachment, and can be
-changed with the <literal>edit-description</literal> command (default: d).
+changed with the <literal><edit-description></literal> command (default: d).
</para>
</sect2>
</sect1>
<sect1 id="mime-types">
-<title>MIME Type configuration with <literal>mime.types</literal></title>
+<title>MIME Type Configuration with <literal>mime.types</literal></title>
<para>
When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <literal>${HOME}/.mime.types</literal>, and then
-the system mime.types file at <literal>/usr/local/share/mutt/mime.types</literal> or
+personal <literal>mime.types</literal> file at <literal>${HOME}/.mime.types</literal>, and then
+the system <literal>mime.types</literal> file at <literal>/usr/local/share/mutt/mime.types</literal> or
<literal>/etc/mime.types</literal>
</para>
<para>
-The mime.types file consist of lines containing a MIME type and a space
+The <literal>mime.types</literal> file consist of lines containing a MIME type and a space
separated list of extensions. For example:
</para>
information, Mutt will assume that the file is plain text, and mark it
as <literal>text/plain</literal>. If the file contains binary information, then Mutt will
mark it as <literal>application/octet-stream</literal>. You can change the MIME
-type that Mutt assigns to an attachment by using the <literal>edit-type</literal>
+type that Mutt assigns to an attachment by using the <literal><edit-type></literal>
command from the compose menu (default: ˆT). The MIME type is actually a
major mime type followed by the sub-type, separated by a '/'. 6 major
types: application, text, image, video, audio, and model have been approved
after various internet discussions. Mutt recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
+appropriate entry is found in the <literal>mime.types</literal> file. It also recognizes other
major mime types, such as the chemical type that is widely used in the
molecular modeling community to pass molecular data in various forms to
various molecular viewers. Non-recognized mime types should only be used
</sect1>
<sect1 id="mailcap">
-<title>MIME Viewer configuration with <literal>mailcap</literal></title>
+<title>MIME Viewer Configuration with Mailcap</title>
<para>
Mutt supports RFC 1524 MIME Configuration, in particular the Unix
is commonly referred to as the mailcap format. Many MIME compliant
programs utilize the mailcap format, allowing you to specify handling
for all MIME types in one place for all programs. Programs known to
-use this format include Netscape, XMosaic, lynx and metamail.
+use this format include Firefox, lynx and metamail.
</para>
<para>
<para>
where <literal>$HOME</literal> is your home directory. The
<literal>$PKGDATADIR</literal> and the
-<literal>$SYSCONFDIR</literal> directories depend on where mutt
+<literal>$SYSCONFDIR</literal> directories depend on where Mutt
is installed: the former is the default for shared data, the
latter for system configuration files.
</para>
</para>
<sect2 id="mailcap-basics">
-<title>The Basics of the mailcap file</title>
+<title>The Basics of the Mailcap File</title>
<para>
A mailcap file consists of a series of lines which are comments, blank,
</sect2>
<sect2 id="secure-mailcap">
-<title>Secure use of mailcap</title>
+<title>Secure Use of Mailcap</title>
<para>
The interpretation of shell meta-characters embedded in MIME parameters
</para>
<para>
-Although mutt's procedures to invoke programs with mailcap seem to be
+Although Mutt's procedures to invoke programs with mailcap seem to be
safe, there are other applications parsing mailcap, maybe taking less care
of it. Therefore you should pay attention to the following rules:
</para>
</sect2>
<sect2 id="advanced-mailcap">
-<title>Advanced mailcap Usage</title>
+<title>Advanced Mailcap Usage</title>
<sect3 id="optional-mailcap-fields">
<title>Optional Fields</title>
<term>needsterminal</term>
<listitem>
<para>
-Mutt uses this flag when viewing attachments with <link linkend="auto-view">auto_view</link>, in order to decide whether it should honor the setting
+Mutt uses this flag when viewing attachments with <link linkend="auto-view"><command>auto_view</command></link>, in order to decide whether it should honor the setting
of the <link linkend="wait-key">$wait_key</link> variable or
not. When an attachment is viewed using an interactive program, and the
corresponding mailcap entry has a <emphasis>needsterminal</emphasis> flag, Mutt will use
<para>
This flag specifies the command to use to create a new attachment of a
specific MIME type. This command differs from the compose command in
-that mutt will expect standard MIME headers on the data. This can be
+that Mutt will expect standard MIME headers on the data. This can be
used to specify parameters, filename, description, etc. for a new
attachment. Mutt supports this from the compose menu.
</para>
</para>
<screen>
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+text/html; firefox -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s
</screen>
<para>
In this example, Mutt will run the program RunningX which will return 0
if the X Window manager is running, and non-zero if it isn't. If
-RunningX returns 0, then Mutt will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
+RunningX returns 0, then Mutt will call firefox to display the
+<literal>text/html</literal> object. If RunningX doesn't return 0, then Mutt will go on
+to the next entry and use lynx to display the <literal>text/html</literal> object.
</para>
</listitem>
</varlistentry>
</para>
<para>
-In addition, you can use this with <link linkend="auto-view">auto_view</link>
+In addition, you can use this with <link linkend="auto-view"><command>auto_view</command></link>
to denote two commands for viewing an attachment, one to be viewed
automatically, the other to be viewed interactively from the attachment
menu. In addition, you can then use the test feature to determine which
</para>
<screen>
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+text/html; firefox -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s; nametemplate=%s.html
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
</screen>
<para>
-For <link linkend="auto-view">auto_view</link>, Mutt will choose the third
+For <link linkend="auto-view"><command>auto_view</command></link>, Mutt will choose the third
entry because of the copiousoutput tag. For interactive viewing, Mutt
will run the program RunningX to determine if it should use the first
entry. If the program returns non-zero, Mutt will use the second entry
<para>
The various commands defined in the mailcap files are passed to the
-<literal>/bin/sh</literal> shell using the system() function. Before the
+<literal>/bin/sh</literal> shell using the <literal>system(3)</literal> function. Before the
command is passed to <literal>/bin/sh -c</literal>, it is parsed to expand
various special parameters with information from Mutt. The keywords
Mutt expands are:
</sect2>
<sect2 id="mailcap-example">
-<title>Example mailcap files</title>
+<title>Example Mailcap Files</title>
<para>
This mailcap file is fairly simple and standard:
video/*; xanim %s > /dev/null
image/*; xv %s > /dev/null
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
+# I'm always running firefox (if my computer had more memory, maybe)
+text/html; firefox -remote 'openURL(%s)'
</screen>
<para>
# send that to /dev/null so I don't see it
video/*; xanim %s > /dev/null
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
+# Send html to a running firefox by remote
+text/html; firefox -remote 'openURL(%s)'; test=RunningFirefox
-# If I'm not running netscape but I am running X, start netscape on the
+# If I'm not running firefox but I am running X, start firefox on the
# object
-text/html; netscape %s; test=RunningX
+text/html; firefox %s; test=RunningX
# Else use lynx to view it as text
text/html; lynx %s
# I use enscript to print text in two columns to a page
text/*; more %s; print=enscript -2Gr %s
-# Netscape adds a flag to tell itself to view jpegs internally
+# Firefox adds a flag to tell itself to view jpegs internally
image/jpeg;xv %s; x-mozilla-flags=internal
# Use xv to view images if I'm running X
<sect1 id="auto-view">
<title>MIME Autoview</title>
+<para>
+Usage:
+</para>
+
+<cmdsynopsis>
+<command>auto-view</command>
+<arg choice="plain">
+<replaceable>mimetype</replaceable>
+</arg>
+<arg choice="opt" rep="repeat">
+<replaceable>mimetype</replaceable>
+</arg>
+
+<command>unauto-view</command>
+<group choice="req">
+<arg choice="plain">
+<replaceable>*</replaceable>
+</arg>
+<arg choice="plain" rep="repeat">
+<replaceable>mimetype</replaceable>
+</arg>
+</group>
+</cmdsynopsis>
+
<para>
In addition to explicitly telling Mutt to view an attachment with the
MIME viewer defined in the mailcap file, Mutt has support for
</para>
<para>
-You then use the <literal>auto_view</literal> muttrc command to list the
-content-types that you wish to view automatically.
-</para>
-
-<para>
-For instance, if you set auto_view to:
+You then use the <command>auto_view</command> <literal>.muttrc</literal> command to list the
+content-types that you wish to view automatically. For instance, if you
+set it to:
</para>
<screen>
</screen>
<para>
-<quote>unauto_view</quote> can be used to remove previous entries from the autoview list.
-This can be used with message-hook to autoview messages based on size, etc.
-<quote>unauto_view *</quote> will remove all previous entries.
+<command>unauto_view</command> can be used to remove previous entries from the autoview list.
+This can be used with <link linkend="message-hook"><command>message-hook</command></link> to autoview messages based on size, etc.
+<quote><command>unauto_view</command> *</quote> will remove all previous entries.
</para>
</sect1>
<para>
Mutt has some heuristics for determining which attachment of a
-multipart/alternative type to display. First, mutt will check the
-alternative_order list to determine if one of the available types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
+<literal>multipart/alternative</literal> type to display. First, Mutt will check the
+<command>alternative_order</command> list
+to determine if one of the available types is preferred. It consists of
+a number of mimetypes in order, including support for implicit and
+explicit wildcards, for example:
</para>
<screen>
</screen>
<para>
-Next, mutt will check if any of the types have a defined
-<link linkend="auto-view">auto_view</link>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
+Next, Mutt will check if any of the types have a defined
+<link linkend="auto-view"><command>auto_view</command></link>, and use that. Failing
+that, Mutt will look for any text type. As a last attempt, Mutt will
look for any type it knows how to handle.
</para>
<para>
-To remove a MIME type from the <literal>alternative_order</literal> list, use the
-<literal>unalternative_order</literal> command.
+To remove a MIME type from the <command>alternative_order</command> list, use the
+<command>unalternative_order</command> command.
</para>
</sect1>
make your message index display the number of qualifying attachments in
each message, or search for messages by attachment count. You also can
configure what kinds of attachments qualify for this feature with the
-attachments and unattachments commands.
+<command>attachments</command> and <command>unattachments</command> commands.
</para>
<para>
-In order to provide this information, mutt needs to fully MIME-parse
+In order to provide this information, Mutt needs to fully MIME-parse
all messages affected first. This can slow down operation especially for
remote mail folders such as IMAP because all messages have to be
downloaded first regardless whether the user really wants to view them
The syntax is:
</para>
-<screen>
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</screen>
+<cmdsynopsis>
+<command>attachments</command>
+<arg choice="plain">
+<replaceable>{ + | - }disposition</replaceable>
+</arg>
+<arg choice="plain">
+<replaceable>mime-type</replaceable>
+</arg>
+
+<command>unattachments</command>
+<arg choice="plain">
+<replaceable>{ + | - }disposition</replaceable>
+</arg>
+<arg choice="plain">
+<replaceable>mime-type</replaceable>
+</arg>
+
+<command>attachments</command>
+<arg choice="plain">
+<replaceable>?</replaceable>
+</arg>
+</cmdsynopsis>
<para>
-Disposition is the attachment's Content-disposition type -- either
+<emphasis>disposition</emphasis> is the attachment's Content-Disposition type — either
<literal>inline</literal> or <literal>attachment</literal>.
You can abbreviate this to <literal>I</literal> or <literal>A</literal>.
</para>
</para>
<para>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
+<emphasis>mime-type</emphasis> is, unsurprisingly, the MIME type of the attachment you want
to affect. A MIME type is always of the format <literal>major/minor</literal>, where
<literal>major</literal> describes the broad category of document you're looking at, and
<literal>minor</literal> describes the specific type within that category. The major
</para>
<para>
-The MIME types you give to the attachments directive are a kind of
-pattern. When you use the attachments directive, the patterns you
-specify are added to a list. When you use unattachments, the pattern
+The MIME types you give to the <command>attachments</command> directive are a kind of
+pattern. When you use the <command>attachments</command> directive, the patterns you
+specify are added to a list. When you use <command>unattachments</command>, the pattern
is removed from the list. The patterns are not expanded and matched
-to specific MIME types at this time -- they're just text in a list.
+to specific MIME types at this time — they're just text in a list.
They're only matched when actually evaluating a message.
</para>
</example>
<para>
-Entering the command <quote><literal>attachments ?</literal></quote>
+Entering the command <quote><command>attachments</command> ?</quote>
as a command will list your current settings in Muttrc format, so that
it can be pasted elsewhere.
</para>
<sect1 id="mime-lookup">
<title>MIME Lookup</title>
+<para>
+Usage:
+</para>
+
+<cmdsynopsis>
+<command>mime-lookup</command>
+<arg choice="plain">
+<replaceable>mimetype</replaceable>
+</arg>
+<arg choice="opt" rep="repeat">
+<replaceable>mimetype</replaceable>
+</arg>
+
+<command>unmime-lookup</command>
+<group choice="req">
+<arg choice="plain">
+<replaceable>*</replaceable>
+</arg>
+<arg choice="plain" rep="repeat">
+<replaceable>mimetype</replaceable>
+</arg>
+</group>
+</cmdsynopsis>
+
<para>
Mutt's mime_lookup list specifies a list of mime-types that should not
be treated according to their mailcap entry. This option is designed to
-deal with binary types such as application/octet-stream. When an attachment's
+deal with binary types such as <literal>application/octet-stream</literal>. When an attachment's
mime-type is listed in mime_lookup, then the extension of the filename will
-be compared to the list of extensions in the mime.types file. The mime-type
+be compared to the list of extensions in the <literal>mime.types</literal> file. The mime-type
associated with this extension will then be used to process the attachment
according to the rules in the mailcap file and according to any other configuration
-options (such as auto_view) specified. Common usage would be:
+options (such as <command>auto_view</command>) specified. Common usage would be:
</para>
<screen>
</screen>
<para>
-In addition, the unmime_lookup command may be used to disable this feature
-for any particular mime-type if it had been set, for example, in a global
-muttrc.
+In addition, the <literal>unmime_lookup</literal> command may be
+used to disable this feature for any particular mime-type if it had been
+set, for example, in a global <literal>.muttrc</literal>.
</para>
</sect1>
</chapter>
<chapter id="optionalfeatures">
-<title>Optional features</title>
+<title>Optional Features</title>
<sect1 id="optionalfeatures-notes">
-<title>General notes</title>
+<title>General Notes</title>
<sect2 id="compile-time-features">
-<title>Enabling/disabling features</title>
+<title>Enabling/Disabling Features</title>
<para>
Mutt supports several of optional features which can be enabled or
Which features are enabled or disabled can later be determined from the
output of <literal>mutt -v</literal>. If a compile option starts with
<quote>+</quote> it is enabled and disabled if prefixed with <quote>-</quote>. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
+Mutt was compiled using GnuTLS for encrypted communication instead of
OpenSSL, <literal>mutt -v</literal> would contain:
</para>
</sect2>
<sect2 id="url-syntax">
-<title>URL syntax</title>
+<title>URL Syntax</title>
<para>
Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <literal>[]</literal> means it is optional and
+in Mutt is (an item enclosed in <literal>[]</literal> means it is optional and
may be omitted):
</para>
</screen>
<para>
-<literal>proto</literal> is the communication protocol:
+<emphasis>proto</emphasis> is the communication protocol:
<literal>imap</literal> for IMAP, <literal>pop</literal> for POP3 and
-<literal>smtp</literal> for SMTP. If <quote>s</quote> for <quote>secure communication</quote>
-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.
+<literal>smtp</literal> for SMTP. If <quote>s</quote> for <quote>secure
+communication</quote> is appended, Mutt will attempt to establish an
+encrypted communication using SSL or TLS.
</para>
<para>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <literal>pop_user</literal> or
-<literal>imap_user</literal> variables. It may contain the <quote>@</quote> 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.
+Since all protocols supported by Mutt support/require authentication,
+login credentials may be specified in the URL. This has the advantage
+that multiple IMAP, POP3 or SMTP servers may be specified (which isn't
+possible using, for example,
+<link linkend="imap-user">$imap_user</link>). The username
+may contain the <quote>@</quote> 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.
</para>
<para>
-The optional path is only relevant for IMAP.
+If no port number is given, Mutt will use the system's default for the
+given protocol (usually consulting <literal>/etc/services</literal>).
</para>
<para>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <literal>imap://imapserver:port/INBOX</literal>. You can also specify different
-username for each folder: <literal>imap://username@imapserver[:port]/INBOX</literal>
-or <literal>imap://username2@imapserver[:port]/path/to/folder</literal>.
-Replacing <literal>imap://</literal> by <literal>imaps://</literal>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
+The optional path is only relevant for IMAP.
</para>
+<example id="ex-url">
+<title>URLs</title>
+<screen>
+pops://host/
+imaps://user@host/INBOX/Sent
+smtp://user@host:587/
+</screen>
+</example>
+
</sect2>
</sect1>
<title>SSL/TLS Support</title>
<para>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
+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 <emphasis>configure</emphasis> script with the
<emphasis>--enable-ssl=...</emphasis> option for OpenSSL or
<title>POP3 Support</title>
<para>
-If Mutt was compiled with POP3 support (by running the <emphasis>configure</emphasis>
+If Mutt is compiled with POP3 support (by running the <emphasis>configure</emphasis>
script with the <emphasis>--enable-pop</emphasis> flag), it has the ability to work
with mailboxes located on a remote POP3 server and fetch mail for local
browsing.
variable, which defaults to every 60 seconds.
</para>
+<para>
+POP is read-only which doesn't allow for some features like editing
+messages or changing flags. However, using
+<xref linkend="header-caching"/> and <xref linkend="body-caching"/>
+Mutt simulates the new/old/read flags as well as flagged and replied.
+Mutt applies some logic on top of remote messages but cannot change
+them so that modifications of flags are lost when
+messages are downloaded from the POP server (either by Mutt or other
+tools).
+</para>
+
<anchor id="fetch-mail"/>
<para>
-Another way to access your POP3 mail is the <literal><fetch-mail$</literal> function
+Another way to access your POP3 mail is the <literal><fetch-mail></literal> function
(default: G). It allows to connect to <link linkend="pop-host">$pop_host</link>, fetch all your new mail and place it in the
local <link linkend="spoolfile">$spoolfile</link>. After this
point, Mutt runs exactly as if the mail had always been local.
<para>
If you only need to fetch all messages to a
local mailbox you should consider using a specialized program, such as
-<literal>fetchmail</literal>, <literal>getmail</literal> or similar.
+<literal>fetchmail(1)</literal>, <literal>getmail(1)</literal> or similar.
</para>
</note>
<link linkend="mail-check">$mail_check</link>
and
<link linkend="timeout">$timeout</link>
-variables. Personally I use
+variables. Reasonable values are:
</para>
<screen>
</screen>
<para>
-with relatively good results over my slow modem line.
+with relatively good results even over slow modem lines.
</para>
<note>
</note>
<sect2 id="imap-browser">
-<title>The Folder Browser</title>
+<title>The IMAP Folder Browser</title>
<para>
-As of version 1.2, mutt supports browsing mailboxes on an IMAP
+As of version 1.2, Mutt supports browsing mailboxes on an IMAP
server. This is mostly the same as the local file browser, with the
following differences:
</para>
<listitem>
<para>
-In lieu of file permissions, mutt displays the string "IMAP",
-possibly followed by the symbol "+", indicating
+In lieu of file permissions, Mutt displays the string <quote>IMAP</quote>,
+possibly followed by the symbol <quote>+</quote>, indicating
that the entry contains both messages and subfolders. On
Cyrus-like servers folders will often contain both messages and
subfolders.
<para>
You can create, delete and rename mailboxes with the
-<literal>create-mailbox</literal>, <literal>delete-mailbox</literal>, and
-<literal>rename-mailbox</literal> commands (default bindings: <literal>C</literal>,
+<literal><create-mailbox></literal>, <literal><delete-mailbox></literal>, and
+<literal><rename-mailbox></literal> commands (default bindings: <literal>C</literal>,
<literal>d</literal> and <literal>r</literal>, respectively). You may also
-<literal>subscribe</literal> and <literal>unsubscribe</literal> to mailboxes (normally
+<literal><subscribe></literal> and <literal><unsubscribe></literal> to mailboxes (normally
these are bound to <literal>s</literal> and <literal>u</literal>, respectively).
</para>
</listitem>
yet to be integrated into the main tree). There is also support for
the pseudo-protocol ANONYMOUS, which allows you to log in to a public
IMAP server without having an account. To use ANONYMOUS, simply make
-your username blank or "anonymous".
+your username blank or <quote>anonymous</quote>.
</para>
<para>
(including DIGEST-MD5 and possibly GSSAPI), your entire session will be
encrypted and invisible to those teeming network snoops. It is the best
option if you have it. To use it, you must have the Cyrus SASL library
-installed on your system and compile mutt with the <emphasis>--with-sasl</emphasis> flag.
+installed on your system and compile Mutt with the <emphasis>--with-sasl</emphasis> flag.
</para>
<para>
<para>
<link linkend="imap-authenticators">$imap_authenticators</link> - a colon-delimited list of IMAP
authentication methods to try, in the order you wish to try them. If
-specified, this overrides mutt's default (attempt everything, in the order
+specified, this overrides Mutt's default (attempt everything, in the order
listed above).
</para>
</listitem>
<para>
Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
+sendmail-compatible program, Mutt supports delivery through SMTP if it
was configured and built with <literal>--enable-smtp</literal>.
</para>
<para>
If the configuration variable
-<link linkend="smtp-url">$smtp_url</link> is set, mutt
+<link linkend="smtp-url">$smtp_url</link> is set, Mutt
will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <link linkend="sendmail">$sendmail</link>.
+Mutt will use the program specified by <link linkend="sendmail">$sendmail</link>.
</para>
<para>
The built-in SMTP support supports encryption (the <literal>smtps</literal> protocol
using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
for SASL are specified in <link linkend="smtp-authenticators">$smtp_authenticators</link>
-defaulting to an empty list which makes mutt try all available methods
+defaulting to an empty list which makes Mutt try all available methods
from most-secure to least-secure.
</para>
</sect1>
<sect1 id="account-hook">
-<title>Managing multiple accounts</title>
+<title>Managing Multiple Accounts</title>
+
+<para>
+Usage:
+</para>
+
+<cmdsynopsis>
+<command>account-hook</command>
+<arg choice="plain">
+<replaceable class="parameter">pattern</replaceable>
+</arg>
+<arg choice="plain">
+<replaceable class="parameter">command</replaceable>
+</arg>
+</cmdsynopsis>
<para>
If you happen to have accounts on multiple IMAP, POP and/or SMTP servers,
you may find managing all the authentication settings inconvenient and
-error-prone. The account-hook command may help. This hook works like
-folder-hook but is invoked whenever you access a remote mailbox
+error-prone. The <link linkend="account-hook"><command>account-hook</command></link> command may help. This hook works like
+<link linkend="folder-hook"><command>folder-hook</command></link> but is invoked whenever Mutt needs to access a remote mailbox
(including inside the folder browser), not just when you open the
-mailbox which includes (for example) polling for new mail, storing Fcc
+mailbox. This includes (for example) polling for new mail, storing Fcc
messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
+<link linkend="account-hook"><command>account-hook</command></link> should only be used to set connection-related settings such
as passwords or tunnel commands but not settings such as sender
address or name (because in general it should be considered unpredictable
-which account-hook was last used).
+which <link linkend="account-hook"><command>account-hook</command></link> was last used).
</para>
<para>
account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
</screen>
+<para>
+To manage multiple accounts with, for example, different values of
+<link linkend="record">$record</link> or sender addresses,
+<link linkend="folder-hook"><command>folder-hook</command></link>
+has to be be used together with
+the <link linkend="mailboxes"><command>mailboxes</command></link> command.
+</para>
+
+<example id="ex-multiaccount">
+<title>Managing multiple accounts</title>
+<screen>
+mailboxes imap://user@host1/INBOX
+folder-hook imap://user@host1/ 'set folder=imap://host1/ ; set record=+INBOX/Sent'
+
+mailboxes imap://user@host2/INBOX
+folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sent'
+</screen>
+</example>
+
+<para>
+In example
+<xref linkend="ex-multiaccount"/> the folders are defined using
+<link linkend="mailboxes"><command>mailboxes</command></link> so Mutt polls them for new
+mail. Each <link linkend="folder-hook"><command>folder-hook</command></link> triggers when
+one mailbox below each IMAP account is opened and sets
+<link linkend="folder">$folder</link> to the account's root
+folder. Next, it sets <link linkend="record">$record</link> to
+the <emphasis>INBOX/Sent</emphasis> folder below the newly
+set <link linkend="folder">$folder</link>. Please notice that the
+value the <quote>+</quote>
+<link linkend="shortcuts">mailbox shortcut</link> refers to depends on
+the <emphasis>current</emphasis> value
+of <link linkend="folder">$folder</link> and therefore has to be set
+separatedly per account. Setting other values
+like <link linkend="from">$from</link>
+or <link linkend="signature">$signature</link> is analogous to setting
+<link linkend="record">$record</link>.
+</para>
+
</sect1>
<sect1 id="caching">
-<title>Local caching</title>
+<title>Local Caching</title>
<para>
Mutt contains two types of local caching: <emphasis>(1)</emphasis>
<para>
Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
+caching is always enabled if Mutt is compiled with POP and/or IMAP
support as these use it (body caching requires no external library).
</para>
<sect2 id="header-caching">
-<title>Header caching</title>
+<title>Header Caching</title>
<para>
Mutt provides optional support for caching message headers for the
to a directory.
</para>
-<para>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</para>
-
-<screen>
-$ printf '%s' '/path/to/folder' | md5sum
-</screen>
-
-<para>
-The <literal>md5sum</literal> command may also be
-named <literal>md5</literal>, depending on your operating system.
-</para>
-
</sect2>
<sect2 id="body-caching">
-<title>Body caching</title>
+<title>Body Caching</title>
<para>
Both cache methods can be combined using the same directory for storage
<para>
-In addition to caching message headers only, mutt can also cache
+In addition to caching message headers only, Mutt can also cache
whole message bodies. This results in faster display of messages
for POP and IMAP folders because messages usually have to be
downloaded only once.
<para>
For configuration, the variable <link linkend="message-cachedir"
>$message_cachedir</link> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
+directory. There, Mutt will create a hierarchy of subdirectories
named like: <literal>proto:user@hostname</literal> where
<literal>proto</literal> is either <quote>pop</quote> or <quote>imap.</quote> Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</para>
-
-<para>
+there for each folder, Mutt stores messages in single files.
All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
+becomes an issue as Mutt will silently fetch missing items again.
</para>
</sect2>
</para>
<para>
-For body caches, mutt can keep the local cache in sync with the
+For body caches, Mutt can keep the local cache in sync with the
remote mailbox if the
<link linkend="message-cache-clean">$message_cache_clean</link>
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
+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.
</sect1>
<sect1 id="exact-address">
-<title>Exact address generation</title>
+<title>Exact Address Generation</title>
<para>
Mutt supports the <quote>Name <user@host></quote> address syntax for reading and
</sect1>
+<sect1 id="sending-mixmaster">
+<title>Sending Anonymous Messages via Mixmaster</title>
+
+<para>
+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 (beta 45 appears to be the latest) and 2.03.
+It does not support earlier versions or the later so-called version 3 betas,
+of which the latest appears to be called 2.9b23.
+</para>
+
+<para>
+To use it, you'll have to obey certain restrictions. Most
+important, you cannot use the <literal>Cc</literal> and <literal>Bcc</literal> headers. To tell
+Mutt to use mixmaster, you have to select a remailer chain, using
+the mix function on the compose menu.
+</para>
+
+<para>
+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.
+</para>
+
+<para>
+You can navigate in the chain using the <literal><chain-prev></literal> and
+<literal><chain-next></literal> functions, which are by default bound to the left
+and right arrows and to the <literal>h</literal> and <literal>l</literal> keys (think vi
+keyboard bindings). To insert a remailer at the current chain
+position, use the <literal><insert></literal> function. To append a remailer behind
+the current chain position, use <literal><select-entry></literal> or <literal><append></literal>.
+You can also delete entries from the chain, using the corresponding
+function. Finally, to abandon your changes, leave the menu, or
+<literal><accept></literal> them pressing (by default) the <literal>Return</literal> key.
+</para>
+
+<para>
+Note that different remailers do have different capabilities,
+indicated in the %c entry of the remailer menu lines (see
+<link linkend="mix-entry-format">$mix_entry_format</link>). Most important is
+the <quote>middleman</quote> capability, indicated by a capital <quote>M</quote>: 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.
+</para>
+
+</sect1>
+
+</chapter>
+
+<chapter id="security">
+<title>Security Considerations</title>
+
+<para>
+First of all, Mutt contains no security holes included by intention but
+may contain unknown security holes. As a consequence, please run Mutt
+only with as few permissions as possible. Especially, do not run Mutt as
+the super user.
+</para>
+
+<para>
+When configuring Mutt, there're some points to note about secure setups
+so please read this chapter carefully.
+</para>
+
+<sect1 id="security-passwords">
+<title>Passwords</title>
+
+<para>
+Although Mutt can be told the various passwords for accounts, please
+never store passwords in configuration files. Besides the fact that the
+system's operator can always read them, you could forget to mask it out
+when reporting a bug or asking for help via a mailing list. Even worse,
+your mail including your password could be archived by internet search
+engines, mail-to-news gateways etc. It may already be too late before
+you notice your mistake.
+</para>
+
+</sect1>
+
+<sect1 id="security-tempfiles">
+<title>Temporary Files</title>
+
+<para>
+Mutt uses many temporary files for viewing messages, verifying digital
+signatures, etc. As long as being used, these files are visible by other
+users and maybe even readable in case of misconfiguration. Also, a
+different location for these files may be desired which can be changed
+via the <link linkend="tmpdir">$tmpdir</link> variable.
+</para>
+
+</sect1>
+
+<sect1 id="security-leaks">
+<title>Information Leaks</title>
+
+<sect2 id="security-leaks-mid">
+<title>Message-Id: headers</title>
+
+<para>
+Message-Id: headers contain a local part that is to be created in a
+unique fashion. In order to do so, Mutt will <quote>leak</quote> some
+information to the outside world when sending messages: the generation
+of this header includes a step counter which is increased (and rotated)
+with every message sent. In a longer running mutt session, others can
+make assumptions about your mailing habbits depending on the number of
+messages sent. If this is not desired, the header can be manually
+provided using <link
+linkend="edit-headers">$edit_headers</link> (though not
+recommended).
+</para>
+
+</sect2>
+
+<sect2 id="security-leaks-mailto">
+<title><literal>mailto:</literal>-style Links</title>
+
+<para>
+As Mutt be can be set up to be the mail client to handle
+<literal>mailto:</literal> style links in websites, there're security
+considerations, too. Arbitrary header fields can be embedded in these
+links which could override existing header fields or attach arbitrary
+files using <link linkend="attach-header">the Attach:
+psuedoheader</link>. This may be problematic if the <link
+linkend="edit-headers">$edit-headers</link> variable is
+<emphasis>unset</emphasis>, i.e. the user doesn't want to see header
+fields while editing the message and doesn't pay enough attention to the
+compose menu's listing of attachments.
+</para>
+
+<para>
+For example, following a link like
+</para>
+
+<screen>
+mailto:joe@host?Attach=~/.gnupg/secring.gpg</screen>
+
+<para>
+will send out the user's private gnupg keyring to
+<literal>joe@host</literal> if the user doesn't follow the information
+on screen carefully enough.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="security-external">
+<title>External Applications</title>
+
+<para>
+Mutt in many places has to rely on external applications or for
+convenience supports mechanisms involving external applications.
+</para>
+
+<para>
+One of these is the <literal>mailcap</literal> mechanism as defined by
+RfC1524. Details about a secure use of the mailcap mechanisms is given
+in <xref linkend="secure-mailcap"/>.
+</para>
+
+<para>
+Besides the mailcap mechanism, Mutt uses a number of other external
+utilities for operation, for example to provide crypto support, in
+backtick expansion in configuration files or format string filters. The
+same security considerations apply for these as for tools involved via
+mailcap.
+</para>
+
+</sect1>
+
</chapter>
+
<chapter id="tuning">
-<title>Performance tuning</title>
+<title>Performance Tuning</title>
<sect1 id="tuning-mailboxes">
-<title>Reading and writing mailboxes</title>
+<title>Reading and Writing Mailboxes</title>
<para>
Mutt's performance when reading mailboxes can be improved in two ways:
<listitem>
<para>
For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
+one-file-per message storage (Maildir and MH), Mutt's
performance can be greatly improved using
<link linkend="header-caching">header caching</link>.
-Using a single database per folder may further increase
-performance.
+using a single database per folder.
</para>
</listitem>
Mutt provides the <link linkend="read-inc">$read_inc</link>
and <link linkend="write-inc">$write_inc</link>
variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
+counters. If these values are too low, Mutt may spend more
time on updating the progress counter than it spends on
actually reading/writing folders.
</para>
thousand messages, the default value for
<link linkend="read-inc">$read_inc</link>
may be too low. It can be tuned on on a folder-basis using
-<link linkend="folder-hook">folder-hooks</link>:
+<link linkend="folder-hook"><command>folder-hook</command>s</link>:
</para>
<screen>
</sect1>
<sect1 id="tuning-messages">
-<title>Reading messages from remote folders</title>
+<title>Reading Messages from Remote Folders</title>
<para>
Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
+slow especially for large mailboxes since Mutt only caches a very
limited number of recently viewed messages (usually 10) per
session (so that it will be gone for the next session.)
</para>
<para>
To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
+please refer to Mutt's so-called
<link linkend="body-caching">body caching</link> for details.
</para>
</sect1>
<sect1 id="tuning-search">
-<title>Searching and limiting</title>
+<title>Searching and Limiting</title>
<para>
When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
+some patterns Mutt distinguishes between regular expression and string
searches. For regular expressions, patterns are prefixed with
<quote>˜</quote> and with <quote>=</quote> for string searches.
</para>
</para>
<para>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
+As for regular expressions, a lower case string search pattern makes
+Mutt perform a case-insensitive search except for IMAP (because for IMAP
+Mutt performs server-side searches which don't support case-insensivity).
</para>
</sect1>
<title>Reference</title>
<sect1 id="commandline">
-<title>Command line options</title>
+<title>Command-Line Options</title>
<para>
Running <literal>mutt</literal> with no arguments will make Mutt attempt to read your spool
<row><entry>-a</entry><entry>attach a file to a message</entry></row>
<row><entry>-b</entry><entry>specify a blind carbon-copy (BCC) address</entry></row>
<row><entry>-c</entry><entry>specify a carbon-copy (Cc) address</entry></row>
-<row><entry>-D</entry><entry>print the value of all mutt variables to stdout</entry></row>
+<row><entry>-D</entry><entry>print the value of all Mutt variables to stdout</entry></row>
<row><entry>-e</entry><entry>specify a config command to be run after initialization files are read</entry></row>
<row><entry>-f</entry><entry>specify a mailbox to load</entry></row>
<row><entry>-F</entry><entry>specify an alternate file to read initialization commands</entry></row>
<row><entry>-s</entry><entry>specify a subject (enclose in quotes if it contains spaces)</entry></row>
<row><entry>-v</entry><entry>show version number and compile-time definitions</entry></row>
<row><entry>-x</entry><entry>simulate the mailx(1) compose mode</entry></row>
-<row><entry>-y</entry><entry>show a menu containing the files specified by the mailboxes command</entry></row>
+<row><entry>-y</entry><entry>show a menu containing the files specified by the <command>mailboxes</command> command</entry></row>
<row><entry>-z</entry><entry>exit immediately if there are no messages in the mailbox</entry></row>
-<row><entry>-Z</entry><entry>open the first folder with new message,exit immediately if none</entry></row>
+<row><entry>-Z</entry><entry>open the first folder with new message, exit immediately if none</entry></row>
</tbody>
</tgroup>
</table>
<arg choice="opt"><option>-F</option>
<replaceable>muttrc</replaceable>
</arg>
-<arg choice="opt"><option>-a</option>
-<replaceable>file</replaceable>
-</arg>
<arg choice="opt"><option>-c</option>
<replaceable>address</replaceable>
</arg>
<replaceable>subject</replaceable>
</arg>
<arg choice="opt">
-<arg choice="opt" rep="repeat">
+<option>-a</option>
<replaceable>file</replaceable>
+<arg choice="opt" rep="repeat"/>
+--
</arg>
-<arg choice="plain">--</arg>
-</arg>
-<arg choice="plain">
-<replaceable>address</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
+<arg choice="plain" rep="repeat">
<replaceable>address</replaceable>
</arg>
</cmdsynopsis>
input from the file you wish to send. For example,
</para>
-<para>
-<literal>mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</literal>
-</para>
+<screen>
+mutt -s "data set for run #2" professor@bigschool.edu < ˜/run2.dat</screen>
<para>
-This command will send a message to <quote>professor@bigschool.edu</quote> with a subject
+will send a message to <literal><professor@bigschool.edu></literal> with a subject
of <quote>data set for run #2</quote>. In the body of the message will be the contents
of the file <quote>˜/run2.dat</quote>.
</para>
<para>
-All files passed with -a <emphasis>file</emphasis> will be attached as a MIME
-part to the message. To attach several files, use <quote>--</quote> to separate files and
-recipient addresses: <literal>mutt -a *.png -- some@one.org</literal>
+All files passed with <literal>-a</literal> <emphasis>file</emphasis> will be attached as a MIME
+part to the message. To attach a single or several files, use <quote>--</quote> to separate files and
+recipient addresses:
+</para>
+
+<screen>
+mutt -a image.png -- some@one.org</screen>
+
+<para>
+or
+</para>
+
+<screen>
+mutt -a *.png -- some@one.org</screen>
+
+<note>
+<para>
+The <literal>-a</literal> option must be last in the option list.
</para>
+</note>
</sect1>
<title>Configuration Commands</title>
<para>
-The following are the commands understood by mutt.
+The following are the commands understood by Mutt:
</para>
<itemizedlist>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">address</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="alias">unalias</link></command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<arg choice="opt" rep="repeat">
<replaceable>regexp</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="alternates">unalternates</link></command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<arg choice="opt" rep="repeat">
<replaceable>mimetype</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="alternative-order">unalternative-order</link></command>
<group choice="req">
<arg choice="plain">
</cmdsynopsis>
</listitem>
+<listitem>
+<cmdsynopsis>
+<command><link linkend="attachments">attachments</link></command>
+<arg choice="plain">
+<replaceable>{ + | - }disposition</replaceable>
+</arg>
+<arg choice="plain">
+<replaceable>mime-type</replaceable>
+</arg>
+
+<command><link linkend="attachments">unattachments</link></command>
+<arg choice="plain">
+<replaceable>{ + | - }disposition</replaceable>
+</arg>
+<arg choice="plain">
+<replaceable>mime-type</replaceable>
+</arg>
+</cmdsynopsis>
+</listitem>
+
<listitem>
<cmdsynopsis>
<command><link linkend="auto-view">auto-view</link></command>
<arg choice="opt" rep="repeat">
<replaceable>mimetype</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="auto-view">unauto-view</link></command>
<group choice="req">
<arg choice="plain">
<listitem>
<cmdsynopsis>
-<command><link linkend="charset-hook">iconv-hook</link></command>
+<command><link linkend="iconv-hook">iconv-hook</link></command>
<arg choice="plain">
<replaceable class="parameter">charset</replaceable>
</arg>
<arg choice="plain">
<replaceable class="parameter">background</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
+
<command><link linkend="color">color</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="plain">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
+
<command><link linkend="color">color</link></command>
<arg choice="plain">
<option>index</option>
<arg choice="plain">
<replaceable class="parameter">pattern</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="color">uncolor</link></command>
+<group choice="req">
<arg choice="plain">
<option>index</option>
</arg>
+<arg choice="plain">
+<option>header</option>
+</arg>
+<arg choice="plain">
+<option>body</option>
+</arg>
+</group>
+<group choice="req">
+<arg choice="plain">
+<replaceable>*</replaceable>
+</arg>
<arg choice="plain" rep="repeat">
+<replaceable>pattern</replaceable>
+</arg>
+</group>
+</cmdsynopsis>
+</listitem>
+
+<listitem>
+<cmdsynopsis>
+<command><link linkend="crypt-hook">crypt-hook</link></command>
+<arg choice="plain">
<replaceable class="parameter">pattern</replaceable>
</arg>
+<arg choice="plain">
+<replaceable class="parameter">keyid</replaceable>
+</arg>
</cmdsynopsis>
</listitem>
<replaceable class="parameter">expr</replaceable>
</arg>
</group>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="addrgroup">ungroup</link></command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">header</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="hdr-order">unhdr_order</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="opt" rep="repeat">
<replaceable class="parameter">pattern</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="ignore">unignore</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="opt" rep="repeat">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="lists">unlists</link></command>
<arg choice="opt" rep="repeat">
<option>-group</option>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">mailbox</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="mailboxes">unmailboxes</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="opt" rep="repeat">
<replaceable>mimetype</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="mime-lookup">unmime-lookup</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="plain">
<replaceable class="parameter">attribute</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
+
<command><link linkend="mono">mono</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="plain">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-<cmdsynopsis>
+
<command><link linkend="mono">mono</link></command>
<arg choice="plain">
<option>index</option>
<arg choice="plain">
<replaceable class="parameter">pattern</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="mono">unmono</link></command>
+<group choice="req">
<arg choice="plain">
<option>index</option>
</arg>
+<arg choice="plain">
+<option>header</option>
+</arg>
+<arg choice="plain">
+<option>body</option>
+</arg>
+</group>
<group choice="req">
<arg choice="plain">
<replaceable class="parameter">*</replaceable>
<arg choice="plain">
<replaceable class="parameter">string</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="my-hdr">unmy_hdr</link></command>
<group choice="req">
<arg choice="plain">
</cmdsynopsis>
</listitem>
-<listitem>
-<cmdsynopsis>
-<command><link linkend="crypt-hook">crypt-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">keyid</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
<listitem>
<cmdsynopsis>
<command><link linkend="push">push</link></command>
</cmdsynopsis>
</listitem>
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">reset</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
<listitem>
<cmdsynopsis>
<command><link linkend="save-hook">save-hook</link></command>
<arg choice="plain">
<replaceable class="parameter">value</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="score">unscore</link></command>
<group choice="req">
<arg choice="plain">
<replaceable class="parameter">variable=value</replaceable>
</arg>
</group>
-<arg choice="opt" rep="repeat"/>
-</cmdsynopsis>
-</listitem>
+<arg choice="opt" rep="repeat"></arg>
+
+<command><link linkend="set">toggle</link></command>
+<arg choice="plain">
+<replaceable class="parameter">variable</replaceable>
+</arg>
+<arg choice="opt" rep="repeat">
+<replaceable class="parameter">variable</replaceable>
+</arg>
-<listitem>
-<cmdsynopsis>
<command><link linkend="set">unset</link></command>
<arg choice="plain">
<replaceable class="parameter">variable</replaceable>
<arg choice="opt" rep="repeat">
<replaceable class="parameter">variable</replaceable>
</arg>
+
+<command><link linkend="set">reset</link></command>
+<arg choice="plain">
+<replaceable class="parameter">variable</replaceable>
+</arg>
+<arg choice="opt" rep="repeat">
+<replaceable class="parameter">variable</replaceable>
+</arg>
</cmdsynopsis>
</listitem>
<arg choice="plain">
<replaceable class="parameter">format</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="spam">nospam</link></command>
<group choice="req">
<arg choice="plain">
<arg choice="opt" rep="repeat">
<replaceable class="parameter">regexp</replaceable>
</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-<cmdsynopsis>
<command><link linkend="subscribe">unsubscribe</link></command>
<arg choice="opt" rep="repeat">
<option>-group</option>
</cmdsynopsis>
</listitem>
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">toggle</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
<listitem>
<cmdsynopsis>
<command><link linkend="unhook">unhook</link></command>
</sect1>
<sect1 id="variables">
-<title>Configuration variables</title>
+<title>Configuration Variables</title>
projects / software / mutt-debian.git / blobdiff