advancedusage.html

mutt-1.5.12 源代码。linux 下邮件接受的工具。

single line, each line containing a tab separated address then name then
some other optional information.  On error, or if there are no matching
addresses, return a non-zero exit code and a one line error message.
</p><p>
An example multiple response output:

</p><pre class="screen">
Searching database ... 20 entries ... 3 matching:
[e-mail]           Michael Elkins  mutt dude
[e-mail]       Brandon Long    mutt and more
[e-mail]        Thomas Roessler mutt pgp
</pre><p>

</p><p>
There are two mechanisms for accessing the query function of mutt.  One
is to do a query from the index menu using the query 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
addresses to create aliases, or to mail.  You can tag multiple addresses
to mail, start a new query, or have a new query appended to the current
responses.
</p><p>
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 complete-query function (default: ^T) to run a
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
menu.  At the query menu, you can select one or more addresses to be
added to the prompt.
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailbox-formats"></a>6.聽Mailbox Formats</h2></div></div></div><p>
Mutt supports reading and writing of four different 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 <a href="reference.html#mbox-type" title="3.110.聽mbox_type">$mbox_type</a> variable.
</p><p>
<span class="bold"><strong>mbox</strong></span>.  This is the most widely used mailbox format for UNIX.  All
messages are stored in a single file.  Each message has a line of the form:
</p><p>

</p><pre class="screen">
From [e-mail] Fri, 11 Apr 1997 11:44:56 PST
</pre><p>

</p><p>
to denote the start of a new message (this is often referred to as the
``From_'' line).
</p><p>
<span class="bold"><strong>MMDF</strong></span>.  This is a variant of the <span class="emphasis"><em>mbox</em></span> format.  Each message is
surrounded by lines containing ``^A^A^A^A'' (four control-A's).
</p><p>
<span class="bold"><strong>MH</strong></span>. A radical departure from <span class="emphasis"><em>mbox</em></span> and <span class="emphasis"><em>MMDF</em></span>, 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. <span class="bold"><strong>Note:</strong></span> Mutt
detects this type of mailbox by looking for either <code class="literal">.mh_sequences</code>
or <code class="literal">.xmhcache</code> (needed to distinguish normal directories from MH
mailboxes).
</p><p>
<span class="bold"><strong>Maildir</strong></span>.  The newest of the mailbox formats, used by the Qmail MTA (a
replacement for sendmail).  Similar to <span class="emphasis"><em>MH</em></span>, except that it adds three
subdirectories of the mailbox: <span class="emphasis"><em>tmp</em></span>, <span class="emphasis"><em>new</em></span> and <span class="emphasis"><em>cur</em></span>.  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.
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="shortcuts"></a>7.聽Mailbox Shortcuts</h2></div></div></div><p>
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.
</p><p>

</p><div class="itemizedlist"><ul type="disc"><li><p>
! -- refers to your <a href="reference.html#spoolfile" title="3.264.聽spoolfile">$spoolfile</a> (incoming) mailbox
</p></li><li><p>
&gt; -- refers to your <a href="reference.html#mbox" title="3.109.聽mbox">$mbox</a> file
</p></li><li><p>
&lt; -- refers to your <a href="reference.html#record" title="3.231.聽record">$record</a> file
</p></li><li><p>
^ -- refers to the current mailbox
</p></li><li><p>
- or !! -- refers to the file you've last visited
</p></li><li><p>
藴 -- refers to your home directory
</p></li><li><p>
= or + -- refers to your <a href="reference.html#folder" title="3.54.聽folder">$folder</a> directory
</p></li><li><p>
@<span class="emphasis"><em>alias</em></span> -- refers to the <a href="configuration.html#save-hook" title="15.聽Specify default save filename">default save folder</a> as determined by the address of the alias
</p></li></ul></div><p>

</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-lists"></a>8.聽Handling Mailing Lists</h2></div></div></div><p>
Mutt has a few configuration options that make dealing with large
amounts of mail easier.  The first thing you must do is to let Mutt
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 <a href="configuration.html#lists" title="10.聽Mailing lists">lists and subscribe</a> commands in your muttrc.
</p><p>
Now that Mutt knows what your mailing lists are, it can do several
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 <span class="emphasis"><em>index</em></span> menu display.  This is useful to distinguish between
personal and list mail in the same mailbox.  In the <a href="reference.html#index-format" title="3.95.聽index_format">$index_format</a> variable, the escape ``%L''
will return the string ``To &lt;list&gt;'' when ``list'' appears in the
``To'' field, and ``Cc &lt;list&gt;'' when it appears in the ``Cc''
field (otherwise it returns the name of the author).
</p><p>
Often times the ``To'' and ``Cc'' fields in mailing list messages
tend to get quite large. Most people do not bother to remove the
author of the message they are reply to from the list, resulting in
two or more copies being sent to that person.  The ``list-reply''
function, which by default is bound to ``L'' in the <span class="emphasis"><em>index</em></span> menu
and <span class="emphasis"><em>pager</em></span>, helps reduce the clutter by only replying to the
known mailing list addresses instead of all recipients (except as
specified by <code class="literal">Mail-Followup-To</code>, see below).
</p><p>
Mutt also supports the <code class="literal">Mail-Followup-To</code> header.  When you send
a message to a list of recipients which includes one or several
subscribed mailing lists, and if the <a href="reference.html#followup-to" title="3.56.聽followup_to">$followup_to</a> 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 ``followups'') to this
message should only be sent to the original recipients of the
message, and not separately to you - you'll receive your copy through
one of the mailing lists you are subscribed to.
</p><p>
Conversely, when group-replying or list-replying to a message which
has a <code class="literal">Mail-Followup-To</code> header, mutt will respect this header if
the <a href="reference.html#honor-followup-to" title="3.74.聽honor_followup_to">$honor_followup_to</a> configuration
variable is set.  Using list-reply 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 <code class="literal">Mail-Followup-To</code>.
</p><p>
Note that, when header editing is enabled, you can create a
<code class="literal">Mail-Followup-To</code> header manually.  Mutt will only auto-generate
this header if it doesn't exist when you send the message.
</p><p>
The other method some mailing list admins use is to generate a
``Reply-To'' field which points back to the mailing list address rather
than the author of the message.  This can create problems when trying
to reply directly to the author in private, since most mail clients
will automatically reply to the address given in the ``Reply-To''
field.  Mutt uses the <a href="reference.html#reply-to" title="3.234.聽reply_to">$reply_to</a>
variable to help decide which address to use.  If set to <span class="emphasis"><em>ask-yes</em></span> or
<span class="emphasis"><em>ask-no</em></span>, you will be
prompted as to whether or not you would like to use the address given in
the ``Reply-To'' field, or reply directly to the address given in the
``From'' field.  When set to <span class="emphasis"><em>yes</em></span>, the ``Reply-To'' field will be used when
present.
</p><p>
The ``X-Label:'' header field can be used to further identify mailing
lists or list subject matter (or just to annotate messages
individually).  The <a href="reference.html#index-format" title="3.95.聽index_format">$index_format</a> variable's ``%y'' and
``%Y'' escapes can be used to expand ``X-Label:'' fields in the
index, and Mutt's pattern-matcher can match regular expressions to
``X-Label:'' fields with the ``藴y'' selector.  ``X-Label:'' is not a
standard message header field, but it can easily be inserted by procmail
and other mail filtering agents.
</p><p>
Lastly, Mutt has the ability to <a href="reference.html#sort" title="3.258.聽sort">sort</a> the mailbox into
<a href="gettingstarted.html#threads" title="3.3.聽Threaded Mode">threads</a>.  A thread is a group of messages which all relate to the same
subject.  This is usually organized into a tree-like structure where a
message and all of its replies are represented graphically.  If you've ever
used a threaded news client, this is the same concept.  It makes dealing
with large volume mailing lists easier because you can easily delete
uninteresting threads and quickly find topics of value.
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing-threads"></a>9.聽Editing threads</h2></div></div></div><p>
Mutt has the ability to dynamically restructure threads that are broken
either by misconfigured software or bad behaviour from some
correspondents. This allows to clean your mailboxes formats) from these
annoyances which make it hard to follow a discussion.
</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id2687015"></a>9.1.聽Linking threads</h3></div></div></div><p>
Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
"References:" 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 ``link-threads'' function (bound to &amp; by default). The
reply will then be connected to this "parent" message.
</p><p>
You can also connect multiple childs at once, tagging them and using the
tag-prefix command (';') or the auto_tag option.
</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id2687044"></a>9.2.聽Breaking threads</h3></div></div></div><p>
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
the subject to a totally unrelated one.
You can fix such threads by using the ``break-thread'' function (bound
by default to #), which will turn the subthread starting from the
current message into a whole different thread.
</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="dsn"></a>10.聽Delivery Status Notification (DSN) Support</h2></div></div></div><p>
RFC1894 defines a set of MIME content types for relaying information
about the status of electronic mail messages.  These can be thought of as
``return receipts.'' Berkeley sendmail 8.8.x currently has some command
line options in which the mail client can make requests as to what type
of status messages should be returned.
</p><p>
To support this, there are two variables. <a href="reference.html#dsn-notify" title="3.43.聽dsn_notify">$dsn_notify</a> is used to request receipts for
different results (such as failed message, message delivered, etc.).
<a href="reference.html#dsn-return" title="3.44.聽dsn_return">$dsn_return</a> requests how much
of your message should be returned with the receipt (headers or full
message).  Refer to the man page on sendmail for more details on DSN.
</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>11.聽POP3 Support (OPTIONAL)</h2></div></div></div><p>
If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
with mailboxes located on a remote POP3 server and fetch mail for local
browsing.
</p><p>
You can access the remote POP3 mailbox by selecting the folder
<code class="literal">pop://popserver/</code>.
</p><p>
You can select an alternative port by specifying it with the server, ie:
<code class="literal">pop://popserver:port/</code>.
</p><p>
You can also specify different username for each folder, ie:
<code class="literal">pop://username@popserver[:port]/</code>.
</p><p>
Polling for new mail is more expensive over POP3 than locally. For this
reason the frequency at which Mutt will check for mail remotely can be
controlled by the
<a href="reference.html#pop-checkinterval" title="3.208.聽pop_checkinterval">$pop_checkinterval</a>
variable, which defaults to every 60 seconds.
</p><p>
If Mutt was compiled with SSL support (by running the <span class="emphasis"><em>configure</em></span>
script with the <span class="emphasis"><em>--with-ssl</em></span> flag), connections to POP3 servers