manual.xml.head

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

<para>
This command wipes the passphrase(s) from memory. It is useful, if
you misspelled the passphrase.
</para>

<para>
<emphasis role="bold">list-reply</emphasis><anchor id="list-reply"/> (default: L)

</para>

<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>
commands, but also honor any <literal>Mail-Followup-To</literal> header(s) if the
<link linkend="honor-followup-to">&dollar;honor&lowbar;followup&lowbar;to</link>
configuration variable is set.  Using this when replying to messages posted
to mailing lists helps avoid duplicate copies being sent to the author of
the message you are replying to.
</para>

<para>
<emphasis role="bold">pipe-message</emphasis><anchor id="pipe-message"/> (default: &verbar;)

</para>

<para>
Asks for an external Unix command and pipes the current or
tagged message(s) to it.  The variables <link linkend="pipe-decode">&dollar;pipe&lowbar;decode</link>, <link linkend="pipe-split">&dollar;pipe&lowbar;split</link>,
<link linkend="pipe-sep">&dollar;pipe&lowbar;sep</link> and <link linkend="wait-key">&dollar;wait&lowbar;key</link> control the exact behaviour of this function.
</para>

<para>
<emphasis role="bold">resend-message</emphasis><anchor id="resend-message"/> (default: ESC e)

</para>

<para>
With resend-message, mutt takes the current message as a template for a
new message.  This function is best described as "recall from arbitrary
folders".  It can conveniently be used to forward MIME messages while
preserving the original mail structure. Note that the amount of headers
included here depends on the value of the <link linkend="weed">&dollar;weed</link>
variable.
</para>

<para>
This function is also available from the attachment menu. You can use this
to easily resend a message which was included with a bounce message
as a message/rfc822 body part.
</para>

<para>
<emphasis role="bold">shell-escape</emphasis><anchor id="shell-escape"/> (default: !)

</para>

<para>
Asks for an external Unix command and executes it.  The <link linkend="wait-key">&dollar;wait&lowbar;key</link> can be used to control
whether Mutt will wait for a key to be pressed when the command returns
(presumably to let the user read the output of the command), based on
the return status of the named command.
</para>

<para>
<emphasis role="bold">toggle-quoted</emphasis><anchor id="toggle-quoted"/> (default: T)

</para>

<para>
The <emphasis>pager</emphasis> uses the <link linkend="quote-regexp">&dollar;quote&lowbar;regexp</link> variable to detect quoted text when
displaying the body of the message.  This function toggles the display
of the quoted material in the message.  It is particularly useful when
are interested in just the response and there is a large amount of
quoted text in the way.
</para>

<para>
<emphasis role="bold">skip-quoted</emphasis><anchor id="skip-quoted"/> (default: S)

</para>

<para>
This function will go to the next line of non-quoted text which come
after a line of quoted text in the internal pager.
</para>

</sect2>

</sect1>

<sect1 id="sending">
<title>Sending Mail</title>

<para>
The following bindings are available in the <emphasis>index</emphasis> for sending
messages.
</para>

<para>

<table>
<title>Most commom mail sending keys</title>
<tgroup cols="3">
<thead>
<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry>m</entry><entry>compose</entry><entry>compose a new message</entry></row>
<row><entry>r</entry><entry>reply</entry><entry>reply to sender</entry></row>
<row><entry>g</entry><entry>group-reply</entry><entry>reply to all recipients</entry></row>
<row><entry>L</entry><entry>list-reply</entry><entry>reply to mailing list address</entry></row>
<row><entry>f</entry><entry>forward</entry><entry>forward message</entry></row>
<row><entry>b</entry><entry>bounce</entry><entry>bounce (remail) message</entry></row>
<row><entry>ESC k</entry><entry>mail-key</entry><entry>mail a PGP public key to someone</entry></row>
</tbody>
</tgroup>
</table>

</para>

<para>
Bouncing a message sends the message as is to the recipient you
specify.  Forwarding 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 ``<link linkend="forwarding-mail">Forwarding
and Bouncing Mail</link>.''
</para>

<para>
Mutt will then enter the <emphasis>compose</emphasis> menu and prompt you for the
recipients to place on the ``To:'' header field.  Next, it will ask
you for the ``Subject:'' field for the message, providing a default if
you are replying to or forwarding a message.  See also
<link linkend="askcc">&dollar;askcc</link>,
<link linkend="askbcc">&dollar;askbcc</link>,
<link linkend="autoedit">&dollar;autoedit</link>,
<link linkend="bounce">&dollar;bounce</link>, 
<link linkend="fast-reply">&dollar;fast&lowbar;reply</link>,
and <link linkend="include">&dollar;include</link>
for changing how Mutt asks these questions.
</para>

<para>
Mutt will then automatically start your <link linkend="editor">&dollar;editor</link> on the message body.  If the <link linkend="edit-headers">&dollar;edit&lowbar;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">&dollar;attribution</link>, <link linkend="indent-string">&dollar;indent&lowbar;string</link> and <link linkend="post-indent-string">&dollar;post&lowbar;indent&lowbar;string</link>.  When forwarding a
message, if the <link linkend="mime-forward">&dollar;mime&lowbar;forward</link>
variable is unset, a copy of the forwarded message will be included.  If
you have specified a <link linkend="signature">&dollar;signature</link>, it
will be appended to the message.
</para>

<para>
Once you have finished editing the body of your mail message, you are
returned to the <emphasis>compose</emphasis> menu.  The following functions are available:
</para>

<para>

<table>
<title>Most common compose menu keys</title>
<tgroup cols="3">
<thead>
<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry>a</entry><entry>attach-file</entry><entry>attach a file</entry></row>
<row><entry>A</entry><entry>attach-message</entry><entry>attach message(s) to the message</entry></row>
<row><entry>ESC k</entry><entry>attach-key</entry><entry>attach a PGP public key</entry></row>
<row><entry>d</entry><entry>edit-description</entry><entry>edit description on attachment</entry></row>
<row><entry>D</entry><entry>detach-file</entry><entry>detach a file</entry></row>
<row><entry>t</entry><entry>edit-to</entry><entry>edit the To field</entry></row>
<row><entry>ESC f</entry><entry>edit-from</entry><entry>edit the From field</entry></row>
<row><entry>r</entry><entry>edit-reply-to</entry><entry>edit the Reply-To field</entry></row>
<row><entry>c</entry><entry>edit-cc</entry><entry>edit the Cc field</entry></row>
<row><entry>b</entry><entry>edit-bcc</entry><entry>edit the Bcc field</entry></row>
<row><entry>y</entry><entry>send-message</entry><entry>send the message</entry></row>
<row><entry>s</entry><entry>edit-subject</entry><entry>edit the Subject</entry></row>
<row><entry>S</entry><entry>smime-menu</entry><entry>select S/MIME options</entry></row>
<row><entry>f</entry><entry>edit-fcc</entry><entry>specify an ``Fcc'' mailbox</entry></row>
<row><entry>p</entry><entry>pgp-menu</entry><entry>select PGP options</entry></row>
<row><entry>P</entry><entry>postpone-message</entry><entry>postpone this message until later</entry></row>
<row><entry>q</entry><entry>quit</entry><entry>quit (abort) sending the message</entry></row>
<row><entry>w</entry><entry>write-fcc</entry><entry>write the message to a folder</entry></row>
<row><entry>i</entry><entry>ispell</entry><entry>check spelling (if available on your system)</entry></row>
<row><entry>&circ;F</entry><entry>forget-passphrase</entry><entry>wipe passphrase(s) from memory</entry></row>
</tbody>
</tgroup>
</table>

</para>

<para>
<emphasis role="bold">Note:</emphasis> The attach-message function will prompt you for a folder to
attach messages from. You can now tag messages in that folder and they
will be attached to the message you are sending. Note that certain
operations like composing a new mail, replying, forwarding, etc. are
not permitted when you are in that folder. The &percnt;r in <link linkend="status-format">&dollar;status&lowbar;format</link> will change to
a 'A' to indicate that you are in attach-message mode.
</para>

<sect2>
<title>Editing the message header</title>

<para>
When editing the header of your outgoing message, there are a couple of
special features available.
</para>

<para>
If you specify

<literal>Fcc:</literal> <emphasis>filename</emphasis>

Mutt will pick up <emphasis>filename</emphasis>
just as if you had used the <emphasis>edit-fcc</emphasis> function in the <emphasis>compose</emphasis> menu.
</para>

<para>
You can also attach files to your message by specifying

<literal>Attach:</literal> <emphasis>filename</emphasis>  &lsqb; <emphasis>description</emphasis> &rsqb;

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

<para>
When replying to messages, if you remove the <emphasis>In-Reply-To:</emphasis> field from
the header field, Mutt will not generate a <emphasis>References:</emphasis> field, which
allows you to create a new message thread.
</para>

<para>
Also see <link linkend="edit-headers">&dollar;edit&lowbar;headers</link>.
</para>

</sect2>

<sect2>
<title>Using Mutt with PGP</title>

<para>
If you want to use PGP, you can specify 
</para>

<para>
<literal>Pgp:</literal> &lsqb; <literal>E</literal> &verbar; <literal>S</literal> &verbar; <literal>S</literal><emphasis>&lt;id&gt;</emphasis> &rsqb; 

</para>

<para>
``E'' encrypts, ``S'' signs and
``S&lt;id&gt;'' signs with the given key, setting <link linkend="pgp-sign-as">&dollar;pgp&lowbar;sign&lowbar;as</link> permanently.
</para>

<para>
If you have told mutt to PGP 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
addresses.  However, there may be situations in which there are
several keys, weakly certified user ID fields, or where no matching
keys can be found.
</para>

<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
find any matching keys, you are prompted for a user ID.  You can, as
usually, abort this prompt using <literal>&circ;G</literal>.  When you do so, mutt will
return to the compose screen.
</para>

<para>
Once you have successfully finished the key selection, the message
will be encrypted using the selected public keys, and sent out.
</para>

<para>
Most fields of the entries in the key selection menu (see also <link linkend="pgp-entry-format">&dollar;pgp&lowbar;entry&lowbar;format</link>) 
have obvious meanings.  But some explanations on the capabilities, flags, 
and validity fields are in order.
</para>

<para>
The flags sequence (&percnt;f) will expand to one of the following flags:

<table>
<title>PGP key menu flags</title>
<tgroup cols="2">
<thead>
<row><entry>Flag</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry>R</entry><entry>The key has been revoked and can't be used.</entry></row>
<row><entry>X</entry><entry>The key is expired and can't be used.</entry></row>
<row><entry>d</entry><entry>You have marked the key as disabled.</entry></row>
<row><entry>c</entry><entry>There are unknown critical self-signature packets.</entry></row>
</tbody>
</tgroup>
</table>

</para>

<para>
The capabilities field (&percnt;c) expands to a two-character sequence
representing a key's capabilities.  The first character gives
the key's encryption capabilities: A minus sign (<emphasis role="bold">-</emphasis>) means 
that the key cannot be used for encryption.  A dot (<emphasis role="bold">.</emphasis>) means that
it's marked as a signature key in one of the user IDs, but may 
also be used for encryption.  The letter <emphasis role="bold">e</emphasis> indicates that 
this key can be used for encryption.
</para>

<para>
The second character indicates the key's signing capabilities.  Once 
again, a ``<emphasis role="bold">-</emphasis>'' implies ``not for signing'', ``<emphasis role="bold">.</emphasis>'' implies
that the key is marked as an encryption key in one of the user-ids, and
``<emphasis role="bold">s</emphasis>'' denotes a key which can be used for signing.
</para>

<para>
Finally, the validity field (&percnt;t) indicates how well-certified a user-id
is.  A question mark (<emphasis role="bold">?</emphasis>) indicates undefined validity, a minus 
character (<emphasis role="bold">-</emphasis>) marks an untrusted association, a space character 
means a partially trusted association, and a plus character (<emphasis role="bold">+</emphasis>) 
indicates complete validity.
</para>

</sect2>

<sect2>
<title>Sending anonymous messages via mixmaster.</title>

<para>
You may also have configured 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 &percnt;c entry of the remailer menu lines (see
<link linkend="mix-entry-format">&dollar;mix&lowbar;entry&lowbar;format</link>).  Most important is
the ``middleman'' capability, indicated by a capital ``M'': 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>

</sect1>

<sect1 id="forwarding-mail">
<title>Forwarding and Bouncing Mail</title>

<para>
Bouncing and forwarding let you send an existing message to recipients
that you specify.  Bouncing a message uses the <link linkend="sendmail">&dollar;sendmail</link> command to send a copy to alternative addresses as if
they were the message's original recipients.  Forwarding a message, on
the other hand, allows you to modify the message before it is resent
(for example, by adding your own comments).
</para>

<para>
The following keys are bound by default:
</para>

<para>

<table>
<title>Message forwarding/bouncing keys</title>
<tgroup cols="3">
<thead>
<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry>f</entry><entry>forward</entry><entry>forward message</entry></row>
<row><entry>b</entry><entry>bounce</entry><entry>bounce (remail) message</entry></row>
</tbody>
</tgroup>