








				   TThhee MMuutttt EE--MMaaiill CClliieenntt


			      by Michael Elkins <me@cs.hmc.edu>


					version 1.5.9





					  AAbbssttrraacctt


	    ``All mail clients suck.  This one just sucks less.'' -me, circa 1995




       _1_.  _I_n_t_r_o_d_u_c_t_i_o_n

       MMuutttt is a small but very powerful text-based MIME mail client.  Mutt is highly
       configurable, and is well suited to the mail power user with advanced features
       like key bindings, keyboard macros, mail threading, regular expression searches
       and a powerful pattern matching language for selecting groups of messages.

       _1_._1  _M_u_t_t _H_o_m_e _P_a_g_e

       http://www.mutt.org/

       _1_._2  _M_a_i_l_i_n_g _L_i_s_t_s

       To subscribe to one of the following mailing lists, send a message with the
       word _s_u_b_s_c_r_i_b_e in the body to list-name_-_r_e_q_u_e_s_t@mutt.org.

	   mutt-announce@mutt.org -- low traffic list for announcements

	   mutt-users@mutt.org -- help, bug reports and feature requests

	   mutt-dev@mutt.org -- development mailing list

       NNoottee:: all messages posted to _m_u_t_t_-_a_n_n_o_u_n_c_e are automatically forwarded to _m_u_t_t_-
       _u_s_e_r_s, so you do not need to be subscribed to both lists.

       _1_._3  _S_o_f_t_w_a_r_e _D_i_s_t_r_i_b_u_t_i_o_n _S_i_t_e_s

	   ftp://ftp.mutt.org/mutt/

       For a list of mirror sites, please refer to http://www.mutt.org/download.html.




       The Mutt E-Mail Client							     1





       The Mutt E-Mail Client							     2



       _1_._4  _I_R_C

       Visit channel _#_m_u_t_t on irc.freenode.net (www.freenode.net) to chat with other
       people interested in Mutt.

       _1_._5  _U_S_E_N_E_T

       See the newsgroup comp.mail.mutt.

       _1_._6  _C_o_p_y_r_i_g_h_t

       Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and others

       This program is free software; you can redistribute it and/or modify it under
       the terms of the GNU General Public License as published by the Free Software
       Foundation; either version 2 of the License, or (at your option) any later ver-
       sion.

       This program is distributed in the hope that it will be useful, but WITHOUT ANY
       WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
       PARTICULAR PURPOSE.  See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with
       this program; if not, write to the Free Software Foundation, Inc., 59 Temple
       Place - Suite 330, Boston, MA  02111, USA.


       _2_.  _G_e_t_t_i_n_g _S_t_a_r_t_e_d

       This section is intended as a brief overview of how to use Mutt.  There are
       many other features which are described elsewhere in the manual.  There is even
       more information available in the Mutt FAQ and various web pages.  See the Mutt
       Page for more details.

       The keybindings described in this section are the defaults as distributed.
       Your local system administrator may have altered the defaults for your site.
       You can always type ``?'' in any menu to display the current bindings.

       The first thing you need to do is invoke mutt, simply by typing mutt at the
       command line.  There are various command-line options, see either the mutt man
       page or the _r_e_f_e_r_e_n_c_e (section 6.1  , page 60).

       _2_._1  _M_o_v_i_n_g _A_r_o_u_n_d _i_n _M_e_n_u_s

       Information is presented in menus, very similar to ELM.	Here is a table show-
       ing the common keys used to navigate menus in Mutt.
















       The Mutt E-Mail Client							     3



	    j or Down	    next-entry	    move to the next entry
	    k or Up	    previous-entry  move to the previous entry
	    z or PageDn     page-down	    go to the next page
	    Z or PageUp     page-up	    go to the previous page
	    = or Home	    first-entry     jump to the first entry
	    * or End	    last-entry	    jump to the last entry
	    q		    quit	    exit the current menu
	    ?		    help	    list all keybindings for the current menu


       _2_._2  _E_d_i_t_i_n_g _I_n_p_u_t _F_i_e_l_d_s

       Mutt has a builtin line editor which is used as the primary way to input tex-
       tual data such as email addresses or filenames.	The keys used to move around
       while editing are very similar to those of Emacs.


	    ^A or <Home>    bol 	    move to the start of the line
	    ^B or <Left>    backward-char   move back one char
	    Esc B	    backward-word   move back one word
	    ^D or <Delete>  delete-char     delete the char under the cursor
	    ^E or <End>     eol 	    move to the end of the line
	    ^F or <Right>   forward-char    move forward one char
	    Esc F	    forward-word    move forward one word
	    <Tab>	    complete	    complete filename or alias
	    ^T		    complete-query  complete address with query
	    ^K		    kill-eol	    delete to the end of the line
	    ESC d	    kill-eow	    delete to the end ot the word
	    ^W		    kill-word	    kill the word in front of the cursor
	    ^U		    kill-line	    delete entire line
	    ^V		    quote-char	    quote the next typed key
	    <Up>	    history-up	    recall previous string from history
	    <Down>	    history-down    recall next string from history
	    <BackSpace>     backspace	    kill the char in front of the cursor
	    Esc u	    upcase-word     convert word to upper case
	    Esc l	    downcase-word   convert word to lower case
	    Esc c	    capitalize-word capitalize the word
	    ^G		    n/a 	    abort
	    <Return>	    n/a 	    finish editing


       You can remap the _e_d_i_t_o_r functions using the _b_i_n_d (section 3.3  , page 16) com-
       mand.  For example, to make the _D_e_l_e_t_e key delete the character in front of the
       cursor rather than under, you could use

       bind editor <delete> backspace

       _2_._3  _R_e_a_d_i_n_g _M_a_i_l _- _T_h_e _I_n_d_e_x _a_n_d _P_a_g_e_r

       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 ``index'' in Mutt.  The second mode is the display of the message contents.
       This is called the ``pager.''









       The Mutt E-Mail Client							     4



       The next few sections describe the functions provided in each of these modes.

       _2_._3_._1  _T_h_e _M_e_s_s_a_g_e _I_n_d_e_x


	    c		    change to a different mailbox
	    ESC c	    change to a folder in read-only mode
	    C		    copy the current message to another mailbox
	    ESC C	    decode a message and copy it to a folder
	    ESC s	    decode a message and save it to a folder
	    D		    delete messages matching a pattern
	    d		    delete the current message
	    F		    mark as important
	    l		    show messages matching a pattern
	    N		    mark message as new
	    o		    change the current sort method
	    O		    reverse sort the mailbox
	    q		    save changes and exit
	    s		    save-message
	    T		    tag messages matching a pattern
	    t		    toggle the tag on a message
	    ESC t	    toggle tag on entire message thread
	    U		    undelete messages matching a pattern
	    u		    undelete-message
	    v		    view-attachments
	    x		    abort changes and exit
	    <Return>	    display-message
	    <Tab>	    jump to the next new message
	    @		    show the author's full e-mail address
	    $		    save changes to mailbox
	    /		    search
	    ESC /	    search-reverse
	    ^L		    clear and redraw the screen
	    ^T		    untag messages matching a pattern


       _2_._3_._1_._1	_S_t_a_t_u_s _F_l_a_g_s

       In addition to who sent the message and the subject, a short summary of the
       disposition of each message is printed beside the message number.  Zero or more
       of the following ``flags'' may appear, which mean:

	     D
		   message is deleted (is marked for deletion)

	     d
		   message have attachments marked for deletion

	     K
		   contains a PGP public key

	     N
		   message is new









       The Mutt E-Mail Client							     5



	     O
		   message is old

	     P
		   message is PGP encrypted

	     r
		   message has been replied to

	     S
		   message is signed, and the signature is succesfully verified

	     s
		   message is signed

	     !
		   message is flagged

	     *
		   message is tagged

       Some of the status flags can be turned on or off using

	   sseett--ffllaagg (default: w)

	   cclleeaarr--ffllaagg (default: W)

       Furthermore, the following flags reflect who the message is addressed to.  They
       can be customized with the _$_t_o___c_h_a_r_s (section 6.3.270  , page 125) variable.

	     +
		   message is to you and you only

	     T
		   message is to you, but also to or cc'ed to others

	     C
		   message is cc'ed to you

	     F
		   message is from you

	     L
		   message is sent to a subscribed mailing list

       _2_._3_._2  _T_h_e _P_a_g_e_r

       By default, Mutt uses its builtin pager to display the body of messages.  The
       pager is very similar to the Unix program _l_e_s_s though not nearly as featureful.













       The Mutt E-Mail Client							     6



	    <Return>	    go down one line
	    <Space>	    display the next page (or next message if at the end of a message)
	    -		    go back to the previous page
	    n		    search for next match
	    S		    skip beyond quoted text
	    T		    toggle display of quoted text
	    ?		    show keybindings
	    /		    search for a regular expression (pattern)
	    ESC /	    search backwards for a regular expression
	    \		    toggle search pattern coloring
	    ^		    jump to the top of the message


       In addition, many of the functions from the _i_n_d_e_x are available in the pager,
       such as _d_e_l_e_t_e_-_m_e_s_s_a_g_e or _c_o_p_y_-_m_e_s_s_a_g_e (this is one advantage over using an
       external pager to view messages).

       Also, the internal pager supports a couple other advanced features. For one, it
       will accept and translate the ``standard'' nroff sequences for bold and under-
       line. These sequences are a series of either the letter, backspace (^H), the
       letter again for bold or the letter, backspace, ``_'' 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 _c_o_l_o_r (sec-
       tion 3.7  , page 20) objects to specify a color or mono attribute for them.

       Additionally, the internal pager supports the ANSI escape sequences for charac-
       ter attributes.	Mutt translates them into the correct color and character set-
       tings.  The sequences Mutt supports are:


	    ESC [ Ps;Ps;Ps;...;Ps m
	    where Ps =
	    0	 All Attributes Off
	    1	 Bold on
	    4	 Underline on
	    5	 Blink on
	    7	 Reverse video on
	    3x	 Foreground color is x
	    4x	 Background color is x

	    Colors are
	    0	 black
	    1	 red
	    2	 green
	    3	 yellow
	    4	 blue
	    5	 magenta
	    6	 cyan
	    7	 white


       Mutt uses these attributes for handling text/enriched messages, and they can
       also be used by an external _a_u_t_o_v_i_e_w (section 5.4  , page 58) script for high-
       lighting purposes.  NNoottee:: If you change the colors for your display, for








       The Mutt E-Mail Client							     7



       example by changing the color associated with color2 for your xterm, then that
       color will be used instead of green.

       _2_._3_._3  _T_h_r_e_a_d_e_d _M_o_d_e

       When the mailbox is _s_o_r_t_e_d (section 6.3.252  , page 119) by _t_h_r_e_a_d_s, there are
       a few additional functions available in the _i_n_d_e_x and _p_a_g_e_r modes.


	    ^D	    delete-thread	    delete all messages in the current thread
	    ^U	    undelete-thread	    undelete all messages in the current thread
	    ^N	    next-thread 	    jump to the start of the next thread
	    ^P	    previous-thread	    jump to the start of the previous thread
	    ^R	    read-thread 	    mark the current thread as read
	    ESC d   delete-subthread	    delete all messages in the current subthread
	    ESC u   undelete-subthread	    undelete all messages in the current subthread
	    ESC n   next-subthread	    jump to the start of the next subthread
	    ESC p   previous-subthread	    jump to the start of the previous subthread
	    ESC r   read-subthread	    mark the current subthread as read
	    ESC t   tag-thread		    toggle the tag on the current thread
	    ESC v   collapse-thread	    toggle collapse for the current thread
	    ESC V   collapse-all	    toggle collapse for all threads
	    P	    parent-message	    jump to parent message in thread


       NNoottee:: 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 _$_i_n_d_e_x___f_o_r_m_a_t (sec-
       tion 6.3.93  , page 83).  For example, you could use "%?M?(#%03M)&(%4l)?" in
       _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83) to optionally display the number of
       hidden messages if the thread is collapsed.

       See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 6.3.262  , page 124).

       _2_._3_._4  _M_i_s_c_e_l_l_a_n_e_o_u_s _F_u_n_c_t_i_o_n_s

       ccrreeaattee--aalliiaass
	(default: a)

       Creates a new alias based upon the current message (or prompts for a new one).
       Once editing is complete, an _a_l_i_a_s (section 3.2	, page 15) command is added to
       the file specified by the _$_a_l_i_a_s___f_i_l_e (section 6.3.3  , page 63) variable for
       future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 6.3.3  , page 63) does not
       add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.26  , page
       31) the file.

       cchheecckk--ttrraaddiittiioonnaall--ppggpp
	(default: ESC P)

       This function will search the current message for content signed or encrypted
       with PGP the "traditional" way, that is, without proper MIME tagging.  Techni-
       cally, this function will temporarily change the MIME content types of the body
       parts containing PGP data; this is similar to the _e_d_i_t_-_t_y_p_e (section 2.3.4  ,
       page 8) function's effect.








       The Mutt E-Mail Client							     8



       ddiissppllaayy--ttooggggllee--wweeeedd
	(default: h)

       Toggles the weeding of message header fields specified by _i_g_n_o_r_e (section
       3.8  , page 22) commands.

       eeddiitt
	(default: e)

       This command (available in the ``index'' and ``pager'') allows you to edit the
       raw current message as it's present in the mail folder.	After you have fin-
       ished editing, the changed message will be appended to the current folder, and
       the original message will be marked for deletion.

       eeddiitt--ttyyppee

       (default: ^E on the attachment menu, and in the pager and index menus; ^T on
       the compose menu)

       This command is used to temporarily edit an attachment's content type to fix,
       for instance, bogus character set parameters.  When invoked from the index or
       from the pager, you'll have the opportunity to edit the top-level attachment's
       content type.  On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2  , page 50), you can
       change any attachment's content type. These changes are not persistent, and get
       lost upon changing folders.

       Note that this command is also available on the _c_o_m_p_o_s_e _m_e_n_u (section 5.1.3  ,
       page 51).  There, it's used to fine-tune the properties of attachments you are
       going to send.

       eenntteerr--ccoommmmaanndd
	(default: ``:'')

       This command is used to execute any command you would normally put in a config-
       uration file.  A common use is to check the settings of variables, or in con-
       junction with _m_a_c_r_o_s (section 3.6  , page 19) to change settings on the fly.

       eexxttrraacctt--kkeeyyss
	(default: ^K)

       This command extracts PGP public keys from the current or tagged message(s) and
       adds them to your PGP public key ring.

       ffoorrggeett--ppaasssspphhrraassee
	(default: ^F)


       This command wipes the passphrase(s) from memory. It is useful, if you mis-
       spelled the passphrase.

       lliisstt--rreeppllyy
	(default: L)

       Reply to the current or tagged message(s) by extracting any addresses which








       The Mutt E-Mail Client							     9



       match the regular expressions given by the _l_i_s_t_s _o_r _s_u_b_s_c_r_i_b_e (section 3.10  ,
       page 23) commands, but also honor any Mail-Followup-To header(s) if the
       _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o (section 6.3.74  , page 79) configuration variable is set.
       Using this when replying to messages posted to mailing lists helps avoid dupli-
       cate copies being sent to the author of the message you are replying to.

       ppiippee--mmeessssaaggee
	(default: |)

       Asks for an external Unix command and pipes the current or tagged message(s) to
       it.  The variables _$_p_i_p_e___d_e_c_o_d_e (section 6.3.196  , page 107), _$_p_i_p_e___s_p_l_i_t
       (section 6.3.195  , page 107), _$_p_i_p_e___s_e_p (section 6.3.197  , page 107) and
       _$_w_a_i_t___k_e_y (section 6.3.278  , page 127) control the exact behaviour of this
       function.

       rreesseenndd--mmeessssaaggee
	(default: ESC e)

       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 orig-
       inal mail structure. Note that the amount of headers included here depends on
       the value of the _$_w_e_e_d (section 6.3.279	, page 127) variable.

       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 mes-
       sage/rfc822 body part.

       sshheellll--eessccaappee
	(default: !)

       Asks for an external Unix command and executes it.  The _$_w_a_i_t___k_e_y (section
       6.3.278	, page 127) 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.

       ttooggggllee--qquuootteedd
	(default: T)

       The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.220  , page 112) variable to
       detect quoted text when displaying the body of the message.  This function tog-
       gles 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.

       sskkiipp--qquuootteedd
	(default: S)

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

       _2_._4  _S_e_n_d_i_n_g _M_a_i_l

       The following bindings are available in the _i_n_d_e_x for sending messages.








       The Mutt E-Mail Client							    10



	    m	    compose	    compose a new message
	    r	    reply	    reply to sender
	    g	    group-reply     reply to all recipients
	    L	    list-reply	    reply to mailing list address
	    f	    forward	    forward message
	    b	    bounce	    bounce (remail) message
	    ESC k   mail-key	    mail a PGP public key to someone


       Bouncing a message sends the message as is to the recipient you specify.  For-
       warding a message allows you to add comments or modify the message you are for-
       warding.  These items are discussed in greater detail in the next chapter
       _`_`_F_o_r_w_a_r_d_i_n_g _a_n_d _B_o_u_n_c_i_n_g _M_a_i_l_'_' (section 2.5  , page 13).

       Mutt will then enter the _c_o_m_p_o_s_e 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 _$_a_s_k_c_c (section 6.3.10  , page 64), _$_a_s_k_b_c_c (section
       6.3.9  , page 64), _$_a_u_t_o_e_d_i_t (section 6.3.15  , page 66), _$_b_o_u_n_c_e (section
       6.3.19  , page 67), and _$_f_a_s_t___r_e_p_l_y (section 6.3.51  , page 74) for changing
       how Mutt asks these questions.

       Mutt will then automatically start your _$_e_d_i_t_o_r (section 6.3.47	, page 73) on
       the message body.  If the _$_e_d_i_t___h_e_a_d_e_r_s (section 6.3.46	, page 73) variable is
       set, the headers will be at the top of the message in your editor.  Any mes-
       sages you are replying to will be added in sort order to the message, with
       appropriate _$_a_t_t_r_i_b_u_t_i_o_n (section 6.3.14  , page 66), _$_i_n_d_e_n_t___s_t_r_i_n_g (section
       6.3.92  , page 83) and _$_p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g (section 6.3.207  , page 109).  When
       forwarding a message, if the _$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  , page 89) vari-
       able is unset, a copy of the forwarded message will be included.  If you have
       specified a _$_s_i_g_n_a_t_u_r_e (section 6.3.247	, page 118), it will be appended to
       the message.

       Once you have finished editing the body of your mail message, you are returned
       to the _c_o_m_p_o_s_e menu.  The following options are available:



























       The Mutt E-Mail Client							    11



	    a	    attach-file 	    attach a file
	    A	    attach-message	    attach message(s) to the message
	    ESC k   attach-key		    attach a PGP public key
	    d	    edit-description	    edit description on attachment
	    D	    detach-file 	    detach a file
	    t	    edit-to		    edit the To field
	    ESC f   edit-from		    edit the From field
	    r	    edit-reply-to	    edit the Reply-To field
	    c	    edit-cc		    edit the Cc field
	    b	    edit-bcc		    edit the Bcc field
	    y	    send-message	    send the message
	    s	    edit-subject	    edit the Subject
	    S	    smime-menu		    select S/MIME options
	    f	    edit-fcc		    specify an ``Fcc'' mailbox
	    p	    pgp-menu		    select PGP options
	    P	    postpone-message	    postpone this message until later
	    q	    quit		    quit (abort) sending the message
	    w	    write-fcc		    write the message to a folder
	    i	    ispell		    check spelling (if available on your system)
	    ^F	    forget-passphrase	    wipe passphrase(s) from memory


       NNoottee:: The attach-message function will prompt you for a folder to attach mes-
       sages 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 %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.3.260  , page 121) will change to a
       'A' to indicate that you are in attach-message mode.

       _2_._4_._1  _E_d_i_t_i_n_g _t_h_e _m_e_s_s_a_g_e _h_e_a_d_e_r

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

       If you specify

       Fcc: _f_i_l_e_n_a_m_e

       Mutt will pick up _f_i_l_e_n_a_m_e just as if you had used the _e_d_i_t_-_f_c_c function in the
       _c_o_m_p_o_s_e menu.

       You can also attach files to your message by specifying

       Attach: _f_i_l_e_n_a_m_e  [ _d_e_s_c_r_i_p_t_i_o_n ]

       where _f_i_l_e_n_a_m_e is the file to attach and _d_e_s_c_r_i_p_t_i_o_n is an optional string to
       use as the description of the attached file.

       When replying to messages, if you remove the _I_n_-_R_e_p_l_y_-_T_o_: field from the header
       field, Mutt will not generate a _R_e_f_e_r_e_n_c_e_s_: field, which allows you to create a
       new message thread.

       Also see _e_d_i_t___h_e_a_d_e_r_s (section 6.3.46  , page 73).









       The Mutt E-Mail Client							    12



       _2_._4_._2  _U_s_i_n_g _M_u_t_t _w_i_t_h _P_G_P

       If you want to use PGP, you can specify

       Pgp: [ E | S | S_<_i_d_> ]

       ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
       _$_p_g_p___s_i_g_n___a_s (section 6.3.149  , page 97) permanently.

       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.

       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
       ^G.  When you do so, mutt will return to the compose screen.

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

       Most fields of the entries in the key selection menu (see also _$_p_g_p___e_n_t_r_y___f_o_r_-
       _m_a_t (section 6.3.141  , page 95)) have obvious meanings.  But some explanations
       on the capabilities, flags, and validity fields are in order.

       The flags sequence (%f) will expand to one of the following flags:

	    R		 The key has been revoked and can't be used.
	    X		 The key is expired and can't be used.
	    d		 You have marked the key as disabled.
	    c		 There are unknown critical self-signature
			 packets.


       The capabilities field (%c) expands to a two-character sequence representing a
       key's capabilities.  The first character gives the key's encryption capabili-
       ties: A minus sign (--) means that the key cannot be used for encryption.  A dot
       (..) means that it's marked as a signature key in one of the user IDs, but may
       also be used for encryption.  The letter ee indicates that this key can be used
       for encryption.

       The second character indicates the key's signing capabilities.  Once again, a
       ``--'' implies ``not for signing'', ``..'' implies that the key is marked as an
       encryption key in one of the user-ids, and ``ss'' denotes a key which can be
       used for signing.

       Finally, the validity field (%t) indicates how well-certified a user-id is.  A
       question mark (??) indicates undefined validity, a minus character (--) marks an
       untrusted association, a space character means a partially trusted association,
       and a plus character (++) indicates complete validity.









       The Mutt E-Mail Client							    13



       _2_._4_._3  _S_e_n_d_i_n_g _a_n_o_n_y_m_o_u_s _m_e_s_s_a_g_e_s _v_i_a _m_i_x_m_a_s_t_e_r_.

       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 ver-
       sions or the later so-called version 3 betas, of which the latest appears to be
       called 2.9b23.

       To use it, you'll have to obey certain restrictions.  Most important, you can-
       not use the Cc and Bcc headers.	To tell Mutt to use mixmaster, you have to
       select a remailer chain, using the mix function on the compose menu.

       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.

       You can navigate in the chain using the chain-prev and chain-next functions,
       which are by default bound to the left and right arrows and to the h and l keys
       (think vi keyboard bindings).  To insert a remailer at the current chain posi-
       tion, use the insert function.  To append a remailer behind the current chain
       position, use select-entry or append.  You can also delete entries from the
       chain, using the corresponding function.  Finally, to abandon your changes,
       leave the menu, or accept them pressing (by default) the Return key.

       Note that different remailers do have different capabilities, indicated in the
       %c entry of the remailer menu lines (see _$_m_i_x___e_n_t_r_y___f_o_r_m_a_t (section 6.3.118  ,
       page 90)).  Most important is the ``middleman'' capability, indicated by a cap-
       ital ``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.

       _2_._5  _F_o_r_w_a_r_d_i_n_g _a_n_d _B_o_u_n_c_i_n_g _M_a_i_l

       Bouncing and forwarding let you send an existing message to recipients that you
       specify.  Bouncing a message uses the _s_e_n_d_m_a_i_l (section 6.3.242	, page 117)
       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 com-
       ments).

       The following keys are bound by default:


	    f	    forward	    forward message
	    b	    bounce	    bounce (remail) message


       Forwarding can be done by including the original message in the new message's
       body (surrounded by indicating lines) or including it as a MIME attachment,
       depending on the value of the _$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  , page 89) vari-
       able.  Decoding of attachments, like in the pager, can be controlled by the
       _$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.3.58	, page 76) and _$_m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e (section








       The Mutt E-Mail Client							    14



       6.3.116	, page 90) variables, respectively.  The desired forwarding format may
       depend on the content, therefore _$_m_i_m_e___f_o_r_w_a_r_d is a quadoption which, for exam-
       ple, can be set to ``ask-no''.

       The inclusion of headers is controlled by the current setting of the _$_w_e_e_d
       (section 6.3.279  , page 127) variable, unless _m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  ,
       page 89) is set.

       Editing the message to forward follows the same procedure as sending or reply-
       ing to a message does.

       _2_._6  _P_o_s_t_p_o_n_i_n_g _M_a_i_l

       At times it is desirable to delay sending a message that you have already begun
       to compose.  When the _p_o_s_t_p_o_n_e_-_m_e_s_s_a_g_e function is used in the _c_o_m_p_o_s_e menu,
       the body of your message and attachments are stored in the mailbox specified by
       the _$_p_o_s_t_p_o_n_e_d (section 6.3.209	, page 109) variable.  This means that you can
       recall the message even if you exit Mutt and then restart it at a later time.

       Once a message is postponed, there are several ways to resume it.  From the
       command line you can use the ``-p'' option, or if you _c_o_m_p_o_s_e a new message
       from the _i_n_d_e_x or _p_a_g_e_r you will be prompted if postponed messages exist.  If
       multiple messages are currently postponed, the _p_o_s_t_p_o_n_e_d menu will pop up and
       you can select which message you would like to resume.

       NNoottee:: If you postpone a reply to a message, the reply setting of the message is
       only updated when you actually finish the message and send it.  Also, you must
       be in the same folder with the message you replied to for the status of the
       message to be updated.

       See also the _$_p_o_s_t_p_o_n_e (section 6.3.208	, page 109) quad-option.


       _3_.  _C_o_n_f_i_g_u_r_a_t_i_o_n

       While the default configuration (or ``preferences'') make Mutt usable right out
       of the box, it is often desirable to tailor Mutt to suit your own tastes. When
       Mutt is first invoked, it will attempt to read the ``system'' configuration
       file (defaults set by your local system administrator), unless the ``-n'' _c_o_m_-
       _m_a_n_d _l_i_n_e (section 6.1  , page 60) option is specified.	This file is typically
       /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a file
       named .muttrc in your home directory.  If this file does not exist and your
       home directory has a subdirectory named .mutt, mutt try to load a file named
       .mutt/muttrc.

       .muttrc is the file where you will usually place your _c_o_m_m_a_n_d_s (section 6.2  ,
       page 60) to configure Mutt.

       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 Muttrc-0.88 file in the system configuration directory, and you are run-
       ning version 0.88 of mutt, this file will be sourced instead of the Muttrc
       file.  The same is true of the user configuration file, if you have a file
       .muttrc-0.88.6 in your home directory, when you run mutt version 0.88.6, it








       The Mutt E-Mail Client							    15



       will source this file instead of the default .muttrc file.  The version number
       is the same which is visible using the ``-v'' _c_o_m_m_a_n_d _l_i_n_e (section 6.1	, page
       60) switch or using the show-version key (default: V) from the index menu.

       _3_._1  _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s

       An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 6.2  , page
       60).  Each line of the file may contain one or more commands.  When multiple
       commands are used, they must be separated by a semicolon (;).

	    set realname='Mutt user' ; ignore x-


       The hash mark, or pound sign (``#''), is used as a ``comment'' 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,


	    my_hdr X-Disclaimer: Why are you listening to me? # This is a comment


       Single quotes (') and double quotes (') can be used to quote strings which con-
       tain 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 sin-
       gle 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, backtics
       are evaluated inside of double quotes, but nnoott for single quotes.

       \ quotes the next character, just as in shells such as bash and zsh.  For exam-
       ple, if want to put quotes ``''' inside of a string, you can use ``\'' to force
       the next character to be a literal instead of interpreted character.

	    set realname="Michael \"MuttDude\" Elkins"


       ``\\'' means to insert a literal ``\'' into the line.  ``\n'' and ``\r'' have
       their usual C meanings of linefeed and carriage-return, respectively.

       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.

       It is also possible to substitute the output of a Unix command in an initial-
       ization file.  This is accomplished by enclosing the command in backquotes
       (``).  For example,

	    my_hdr X-Operating-System: `uname -a`


       The output of the Unix command ``uname -a'' will be substituted before the line
       is parsed.  Note that since initialization files are line oriented, only the
       first line of output from the Unix command will be substituted.

       UNIX environments can be accessed like the way it is done in shells like sh and








       The Mutt E-Mail Client							    16



       bash: Prepend the name of the environment by a ``$''.  For example,

	    set record=+sent_on_$HOSTNAME


       The commands understood by mutt are explained in the next paragraphs.  For a
       complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 6.2  , page 60).

       _3_._2  _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s

       Usage: alias _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ]

       It's usually very cumbersome to remember or type out the address of someone you
       are communicating with.	Mutt allows you to create ``aliases'' which map a
       short string to a full address.

       NNoottee:: if you want to create an alias for a group (by specifying more than one
       address), you mmuusstt separate the addresses with a comma (``,'').

       To remove an alias or aliases (``*'' means all aliases):

       unalias [ * | _k_e_y _._._. ]


	    alias muttdude me@cs.hmc.edu (Michael Elkins)
	    alias theguys manny, moe, jack


       Unlike other mailers, Mutt doesn't require aliases to be defined in a special
       file.  The alias command can appear anywhere in a configuration file, as long
       as this file is _s_o_u_r_c_e_d (section 3.26  , page 31).  Consequently, you can have
       multiple alias files, or you can have all aliases defined in your muttrc.

       On the other hand, the _c_r_e_a_t_e_-_a_l_i_a_s (section 2.3.4  , page 7) function can use
       only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 6.3.3  , page 63)
       variable (which is ~/.muttrc 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 _s_o_u_r_c_e (section 3.26  ,
       page 31) this file too.

       For example:


	    source /usr/local/share/Mutt.aliases
	    source ~/.mail_aliases
	    set alias_file=~/.mail_aliases


       To use aliases, you merely use the alias at any place in mutt where mutt
       prompts for addresses, such as the _T_o_: or _C_c_: prompt.  You can also enter
       aliases in your editor at the appropriate headers if you have the _$_e_d_i_t___h_e_a_d_e_r_s
       (section 6.3.46	, page 73) variable set.

       In addition, at the various address prompts, you can use the tab character to








       The Mutt E-Mail Client							    17



       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 alias, such as at
       the beginning of the prompt or after a comma denoting multiple addresses.

       In the alias menu, you can select as many aliases as you want with the _s_e_l_e_c_t_-
       _e_n_t_r_y key (default: RET), and use the _e_x_i_t key (default: q) to return to the
       address prompt.

       _3_._3  _C_h_a_n_g_i_n_g _t_h_e _d_e_f_a_u_l_t _k_e_y _b_i_n_d_i_n_g_s

       Usage: bind _m_a_p _k_e_y _f_u_n_c_t_i_o_n

       This command allows you to change the default key bindings (operation invoked
       when pressing a key).

       _m_a_p specifies in which menu the binding belongs.  Multiple maps may be speci-
       fied by separating them with commas (no additional whitespace is allowed). The
       currently defined maps are:



	     generic
		   This is not a real menu, but is used as a fallback for all of the
		   other 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 accom-
		   plish the same task.

	     alias
		   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 address(es) of the recipient(s).

	     attach
		   The attachment menu is used to access the attachments on received
		   messages.

	     browser
		   The browser is used for both browsing the local directory struc-
		   ture, and for listing all of your incoming mailboxes.

	     editor
		   The editor is the line-based editor the user enters text data.

	     index
		   The index is the list of messages contained in a mailbox.

	     compose
		   The compose menu is the screen used when sending a new message.

	     pager
		   The pager is the mode used to display message/attachment data, and








       The Mutt E-Mail Client							    18



		   help listings.

	     pgp
		   The pgp menu is used to select the OpenPGP keys used for encrypting
		   outgoing messages.

	     postpone
		   The postpone menu is similar to the index menu, except is used when
		   recalling a message the user was composing, but saved until later.

       _k_e_y is the key (or key sequence) you wish to bind.  To specify a control char-
       acter, use the sequence _\_C_x, where _x is the letter of the control character
       (for example, to specify control-A use ``\Ca'').  Note that the case of _x as
       well as _\_C is ignored, so that _\_C_A, _\_C_a, _\_c_A and _\_c_a are all equivalent.  An
       alternative form is to specify the key as a three digit octal number prefixed
       with a ``\'' (for example _\_1_7_7 is equivalent to _\_c_?).

       In addition, _k_e_y may consist of:


	    \t		    tab
	    <tab>	    tab
	    \r		    carriage return
	    \n		    newline
	    \e		    escape
	    <esc>	    escape
	    <up>	    up arrow
	    <down>	    down arrow
	    <left>	    left arrow
	    <right>	    right arrow
	    <pageup>	    Page Up
	    <pagedown>	    Page Down
	    <backspace>     Backspace
	    <delete>	    Delete
	    <insert>	    Insert
	    <enter>	    Enter
	    <return>	    Return
	    <home>	    Home
	    <end>	    End
	    <space>	    Space bar
	    <f1>	    function key 1
	    <f10>	    function key 10


       _k_e_y does not need to be enclosed in quotes unless it contains a space (`` '').

       _f_u_n_c_t_i_o_n specifies which action to take when _k_e_y is pressed.  For a complete
       list of functions, see the _r_e_f_e_r_e_n_c_e (section 6.4  , page 128).	The special
       function noop unbinds the specified key sequence.

       _3_._4  _D_e_f_i_n_i_n_g _a_l_i_a_s_e_s _f_o_r _c_h_a_r_a_c_t_e_r _s_e_t_s

       Usage: charset-hook _a_l_i_a_s _c_h_a_r_s_e_t









       The Mutt E-Mail Client							    19



       Usage: iconv-hook _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t

       The charset-hook 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.

       The iconv-hook 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.

       _3_._5  _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s _b_a_s_e_d _u_p_o_n _m_a_i_l_b_o_x

       Usage: folder-hook [!]_r_e_g_e_x_p _c_o_m_m_a_n_d

       It is often desirable to change settings based on which mailbox you are read-
       ing.  The folder-hook command provides a method by which you can execute any
       configuration command.  _r_e_g_e_x_p is a regular expression specifying in which
       mailboxes to execute _c_o_m_m_a_n_d before loading.  If a mailbox matches multiple
       folder-hook's, they are executed in the order given in the muttrc.

       NNoottee:: if you use the ``!'' shortcut for _$_s_p_o_o_l_f_i_l_e (section 6.3.258  , page
       121) at the beginning of the pattern, you must place it inside of double or
       single quotes in order to distinguish it from the logical _n_o_t operator for the
       expression.

       Note that the settings are _n_o_t restored when you leave the mailbox.  For exam-
       ple, a command action to perform is to change the sorting method based upon the
       mailbox being read:


	    folder-hook mutt set sort=threads


       However, the sorting method is not restored to its previous value when reading
       a different mailbox.  To specify a _d_e_f_a_u_l_t command, use the pattern ``.'':


	    folder-hook . set sort=date-sent


       _3_._6  _K_e_y_b_o_a_r_d _m_a_c_r_o_s

       Usage: macro _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ]

       Macros are useful when you would like a single key to perform a series of
       actions.  When you press _k_e_y in menu _m_e_n_u, Mutt will behave as if you had typed
       _s_e_q_u_e_n_c_e.  So if you have a common sequence of commands you type, you can cre-
       ate a macro to execute those commands with a single key.

       _m_e_n_u is the _m_a_p (section 3.3  , page 16) which the macro will be bound.	Multi-
       ple maps may be specified by separating multiple menu arguments by commas.
       Whitespace may not be used in between the menu arguments and the commas sepa-
       rating them.









       The Mutt E-Mail Client							    20



       _k_e_y and _s_e_q_u_e_n_c_e are expanded by the same rules as the _k_e_y _b_i_n_d_i_n_g_s (section
       3.3  , page 16).  There are some additions however.  The first is that control
       characters in _s_e_q_u_e_n_c_e can also be specified as _^_x.  In order to get a caret
       (`^'') you need to use _^_^.  Secondly, to specify a certain key such as _u_p or to
       invoke a function directly, you can use the format _<_k_e_y _n_a_m_e_> and _<_f_u_n_c_t_i_o_n
       _n_a_m_e_>.  For a listing of key names see the section on _k_e_y _b_i_n_d_i_n_g_s (section
       3.3  , page 16).  Functions are listed in the _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section
       6.4  , page 128).

       The advantage with using function names directly is that the macros will work
       regardless of the current key bindings, so they are not dependent on the user
       having particular key definitions.  This makes them more robust and portable,
       and also facilitates defining of macros in files used by more than one user
       (eg. the system Muttrc).

       Optionally you can specify a descriptive text after _s_e_q_u_e_n_c_e, which is shown in
       the help screens.

       NNoottee:: Macro definitions (if any) listed in the help screen(s), are silently
       truncated at the screen width, and are not wrapped.

       _3_._7  _U_s_i_n_g _c_o_l_o_r _a_n_d _m_o_n_o _v_i_d_e_o _a_t_t_r_i_b_u_t_e_s

       Usage: color _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ]

       Usage: color index _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d _p_a_t_t_e_r_n

       Usage: uncolor index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ...  ]

       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 aanndd a background color (it is not possible to
       only specify one or the other).

       _o_b_j_e_c_t can be one of:

	   attachment

	   body (match _r_e_g_e_x_p in the body of messages)

	   bold (hiliting bold patterns in the body of messages)

	   error (error messages printed by Mutt)

	   header (match _r_e_g_e_x_p in the message header)

	   hdrdefault (default color of the message header in the pager)

	   index (match _p_a_t_t_e_r_n in the message index)

	   indicator (arrow or bar used to indicate the current item in a menu)

	   markers (the ``+'' markers at the beginning of wrapped lines in the pager)









       The Mutt E-Mail Client							    21



	   message (informational messages)

	   normal

	   quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.220  , page 112) in the
	    body of a message)

	   quoted1, quoted2, ..., quotedNN (higher levels of quoting)

	   search (hiliting of words in the pager)

	   signature

	   status (mode lines used to display info about the mailbox or message)

	   tilde (the ``~'' used to pad blank lines in the pager)

	   tree (thread tree drawn in the message index and attachment menu)

	   underline (hiliting underlined patterns in the body of messages)

       _f_o_r_e_g_r_o_u_n_d and _b_a_c_k_g_r_o_u_n_d can be one of the following:

	   white

	   black

	   green

	   magenta

	   blue

	   cyan

	   yellow

	   red

	   default

	   color_x

       _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make the fore-
       ground color boldfaced (e.g., brightred).

       If your terminal supports it, the special keyword _d_e_f_a_u_l_t can be used as a
       transparent color.  The value _b_r_i_g_h_t_d_e_f_a_u_l_t is also valid.  If Mutt is linked
       against the _S_-_L_a_n_g library, you also need to set the _C_O_L_O_R_F_G_B_G environment
       variable to the default colors of your terminal for this to work; for example
       (for Bourne-like shells):


	    set COLORFGBG="green;black"








       The Mutt E-Mail Client							    22



	    export COLORFGBG


       NNoottee:: The _S_-_L_a_n_g library requires you to use the _l_i_g_h_t_g_r_a_y and _b_r_o_w_n keywords
       instead of _w_h_i_t_e and _y_e_l_l_o_w when setting this variable.

       NNoottee:: The uncolor command can be applied to the index object only.  It removes
       entries from the list. You mmuusstt specify the same pattern specified in the color
       command for it to be removed.  The pattern ``*'' is a special token which means
       to clear the color index list of all entries.

       Mutt also recognizes the keywords _c_o_l_o_r_0, _c_o_l_o_r_1, ..., _c_o_l_o_rNN--11 (NN 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
       _c_o_l_o_r_2 for your xterm), since color names may then lose their normal meaning.

       If your terminal does not support color, it is still possible change the video
       attributes through the use of the ``mono'' command:

       Usage: mono _<_o_b_j_e_c_t_> _<_a_t_t_r_i_b_u_t_e_> [ _r_e_g_e_x_p ]

       Usage: mono index _a_t_t_r_i_b_u_t_e _p_a_t_t_e_r_n

       Usage: unmono index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ...  ]

       where _a_t_t_r_i_b_u_t_e is one of the following:

	   none

	   bold

	   underline

	   reverse

	   standout

       _3_._8  _I_g_n_o_r_i_n_g _(_w_e_e_d_i_n_g_) _u_n_w_a_n_t_e_d _m_e_s_s_a_g_e _h_e_a_d_e_r_s

       Usage: [un]ignore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

       Messages often have many header fields added by automatic processing systems,
       or which may not seem useful to display on the screen.  This command allows you
       to specify header fields which you don't normally want to see.

       You do not need to specify the full header field name.  For example, ``ignore
       content-'' will ignore all header fields that begin with the pattern ``con-
       tent-''. ``ignore *'' will ignore all headers.

       To remove a previously added token from the list, use the ``unignore'' command.
       The ``unignore'' command will make Mutt display headers with the given pattern.
       For example, if you do ``ignore x-'' it is possible to ``unignore x-mailer''.

       ``unignore *'' will remove all tokens from the ignore list.








       The Mutt E-Mail Client							    23



       For example:

	    # Sven's draconian header weeding
	    ignore *
	    unignore from date subject to cc
	    unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
	    unignore posted-to:


       _3_._9  _A_l_t_e_r_n_a_t_i_v_e _a_d_d_r_e_s_s_e_s

       Usage: [un]alternates _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

       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 yourself won't make much sense in many cases.  (See
       _$_r_e_p_l_y___t_o (section 6.3.228  , page 113).)

       Many users receive e-mail under a number of different addresses. 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 alternates command:
       It takes a list of regular expressions, each of which can identify an address
       under which you receive e-mail.

       The unalternates command can be used to write exceptions to alternates pat-
       terns. If an address matches something in an alternates command, but you none-
       theless do not think it is from you, you can list a more precise pattern under
       an unalternates command.

       To remove a regular expression from the alternates list, use the unalternates
       command with exactly the same _r_e_g_e_x_p.  Likewise, if the _r_e_g_e_x_p for a alternates
       command matches an entry on the unalternates list, that unalternates entry will
       be removed. If the _r_e_g_e_x_p for unalternates is ``*'', _a_l_l _e_n_t_r_i_e_s on alternates
       will be removed.

       _3_._1_0  _M_a_i_l_i_n_g _l_i_s_t_s

       Usage: [un]lists _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

       Usage: [un]subscribe _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

       Mutt has a few nice features for _h_a_n_d_l_i_n_g _m_a_i_l_i_n_g _l_i_s_t_s (section 4.8  , page
       42).  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 _l_i_s_t_-_r_e_p_l_y (section 2.3.4  , page 8) 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.	Note that the
       Mail-Followup-To header is a non-standard extension which is not supported by
       all mail user agents.  Adding it is not bullet-proof against receiving personal
       CCs of list messages.  Also note that the generation of the Mail-Followup-To
       header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 6.3.56  , page 75)








       The Mutt E-Mail Client							    24



       configuration variable.

       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 ``lists'' command.  To mark it as subscribed,
       use ``subscribe''.

       You can use regular expressions with both commands.  To mark all messages sent
       to a specific bug report's address on mutt's bug tracking system as list mail,
       for instance, you could say ``subscribe [0-9]*@bugs.guug.de''.  Often, it's
       sufficient to just give a portion of the list's e-mail address.

       Specify as much of the address as you need to to remove ambiguity.  For exam-
       ple, if you've subscribed to the Mutt mailing list, you will receive mail
       addresssed to _m_u_t_t_-_u_s_e_r_s_@_m_u_t_t_._o_r_g.  So, to tell Mutt that this is a mailing
       list, you could add ``lists mutt-users'' to your initialization file.  To tell
       mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
       tialization file instead.  If you also happen to get mail from someone whose
       address is _m_u_t_t_-_u_s_e_r_s_@_e_x_a_m_p_l_e_._c_o_m, you could use ``lists mutt-
       users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
       from the actual list.

       The ``unlists'' command is used to remove a token from the list of known and
       subscribed mailing-lists. Use ``unlists *'' to remove all tokens.

       To remove a mailing list from the list of subscribed mailing lists, but keep it
       on the list of known mailing lists, use ``unsubscribe''.

       _3_._1_1  _U_s_i_n_g _M_u_l_t_i_p_l_e _s_p_o_o_l _m_a_i_l_b_o_x_e_s

       Usage: mbox-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x

       This command is used to move read messages from a specified mailbox to a dif-
       ferent mailbox automatically when you quit or change folders.  _p_a_t_t_e_r_n is a
       regular expression specifying the mailbox to treat as a ``spool'' mailbox and
       _m_a_i_l_b_o_x specifies where mail should be saved when read.

       Unlike some of the other _h_o_o_k commands, only the _f_i_r_s_t matching pattern is used
       (it is not possible to save read mail in more than a single mailbox).

       _3_._1_2  _D_e_f_i_n_i_n_g _m_a_i_l_b_o_x_e_s _w_h_i_c_h _r_e_c_e_i_v_e _m_a_i_l

       Usage: [un]mailboxes [!]_f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ]

       This command specifies folders which can receive mail and which will be checked
       for new messages.  By default, the main menu status bar displays how many of
       these folders have new messages.

       When changing folders, pressing _s_p_a_c_e will cycle through folders with new mail.

       Pressing TAB in the directory browser will bring up a menu showing the files
       specified by the mailboxes command, and indicate which contain new messages.
       Mutt will automatically enter this mode when invoked from the command line with
       the -y option.








       The Mutt E-Mail Client							    25



       The ``unmailboxes'' command is used to remove a token from the list of folders
       which receive mail. Use ``unmailboxes *'' to remove all tokens.

       NNoottee:: new mail is detected by comparing the last modification time to the last
       access time.  Utilities like biff or frm or any other program which accesses
       the mailbox might cause Mutt to never detect new mail for that mailbox if they
       do not properly reset the access time.  Backup tools are another common reason
       for updated access times.

       NNoottee:: the filenames in the mailboxes command are resolved when the command is
       executed, so if these names contain _s_h_o_r_t_c_u_t _c_h_a_r_a_c_t_e_r_s (section 4.7  , page
       42) (such as ``='' and ``!''), any variable definition that affect these char-
       acters (like _$_f_o_l_d_e_r (section 6.3.54  , page 74) and _$_s_p_o_o_l_f_i_l_e (section
       6.3.258	, page 121)) should be executed before the mailboxes command.

       _3_._1_3  _U_s_e_r _d_e_f_i_n_e_d _h_e_a_d_e_r_s

       Usage:

       my_hdr _s_t_r_i_n_g

       unmy_hdr _f_i_e_l_d [ _f_i_e_l_d ... ]

       The ``my_hdr'' command allows you to create your own header fields which will
       be added to every message you send.

       For example, if you would like to add an ``Organization:'' header field to all
       of your outgoing messages, you can put the command


	    my_hdr Organization: A Really Big Company, Anytown, USA


       in your .muttrc.

       NNoottee::  space characters are _n_o_t allowed between the keyword and the colon
       (``:'').  The standard for electronic mail (RFC822) says that space is illegal
       there, so Mutt enforces the rule.

       If you would like to add a header field to a single message, you should either
       set the _e_d_i_t___h_e_a_d_e_r_s (section 6.3.46  , page 73) variable, or use the _e_d_i_t_-
       _h_e_a_d_e_r_s function (default: ``E'') in the send-menu so that you can edit the
       header of your message along with the body.

       To remove user defined header fields, use the ``unmy_hdr'' command.  You may
       specify an asterisk (``*'') to remove all header fields, or the fields to
       remove.	For example, to remove all ``To'' and ``Cc'' header fields, you could
       use:


	    unmy_hdr to cc











       The Mutt E-Mail Client							    26



       _3_._1_4  _D_e_f_i_n_i_n_g _t_h_e _o_r_d_e_r _o_f _h_e_a_d_e_r_s _w_h_e_n _v_i_e_w_i_n_g _m_e_s_s_a_g_e_s

       Usage: hdr_order _h_e_a_d_e_r_1 _h_e_a_d_e_r_2 _h_e_a_d_e_r_3

       With this command, you can specify an order in which mutt will attempt to
       present headers to you when viewing messages.

       ``unhdr_order *'' will clear all previous headers from the order list, thus
       removing the header order effects set by the system-wide startup file.


	    hdr_order From Date: From: To: Cc: Subject:


       _3_._1_5  _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e

       Usage: save-hook [!]_p_a_t_t_e_r_n _f_i_l_e_n_a_m_e

       This command is used to override the default filename used when saving mes-
       sages.  _f_i_l_e_n_a_m_e will be used as the default filename if the message is _F_r_o_m_:
       an address matching _r_e_g_e_x_p or if you are the author and the message is
       addressed _t_o_: something matching _r_e_g_e_x_p.

       See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.4.1  , page 40) for information on the
       exact format of _p_a_t_t_e_r_n.

       Examples:


	    save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
	    save-hook aol\\.com$ +spam


       Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.17  , page 26) command.

       _3_._1_6  _S_p_e_c_i_f_y _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _w_h_e_n _c_o_m_p_o_s_i_n_g

       Usage: fcc-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x

       This command is used to save outgoing mail in a mailbox other than _$_r_e_c_o_r_d
       (section 6.3.225  , page 113).  Mutt searches the initial list of message
       recipients for the first matching _r_e_g_e_x_p and uses _m_a_i_l_b_o_x as the default Fcc:
       mailbox.  If no match is found the message will be saved to _$_r_e_c_o_r_d (section
       6.3.225	, page 113) mailbox.

       See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.4.1  , page 40) for information on the
       exact format of _p_a_t_t_e_r_n.

       Example: fcc-hook [@.]aol\\.com$ +spammers

       The above will save a copy of all messages going to the aol.com domain to the
       `+spammers' mailbox by default.	Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.17  ,
       page 26) command.









       The Mutt E-Mail Client							    27



       _3_._1_7  _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e _a_n_d _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _a_t _o_n_c_e

       Usage: fcc-save-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x

       This command is a shortcut, equivalent to doing both a _f_c_c_-_h_o_o_k (section
       3.16  , page 26) and a _s_a_v_e_-_h_o_o_k (section 3.15  , page 25) with its arguments.

       _3_._1_8  _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_a_s_e_d _u_p_o_n _m_e_s_s_a_g_e _r_e_c_i_p_i_e_n_t_s

       Usage: reply-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d

       Usage: send-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d

       Usage: send2-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d

       These commands can be used to execute arbitrary configuration commands based
       upon recipients of the message.	_p_a_t_t_e_r_n is a regular expression matching the
       desired address.  _c_o_m_m_a_n_d is executed when _r_e_g_e_x_p matches recipients of the
       message.

       reply-hook is matched against the message you are _r_e_p_l_y_i_n_g ttoo, instead of the
       message you are _s_e_n_d_i_n_g.  send-hook is matched against all messages, both _n_e_w
       and _r_e_p_l_i_e_s.  NNoottee:: reply-hooks are matched bbeeffoorree the send-hook, rreeggaarrddlleessss of
       the order specified in the users's configuration file.

       send2-hook is matched every time a message is changed, either by editing it, or
       by using the compose menu to change its recipients or subject.  send2-hook is
       executed after send-hook, and can, e.g., be used to set parameters such as the
       _$_s_e_n_d_m_a_i_l (section 6.3.242  , page 117) variable depending on the message's
       sender address.

       For each type of send-hook or reply-hook, when multiple matches occur, commands
       are executed in the order they are specified in the muttrc (for that type of
       hook).

       See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.4.1  , page 40) for information on the
       exact format of _p_a_t_t_e_r_n.

       Example: send-hook mutt 'set mime_forward signature='''

       Another typical use for this command is to change the values of the _$_a_t_t_r_i_b_u_-
       _t_i_o_n (section 6.3.14  , page 66), _$_s_i_g_n_a_t_u_r_e (section 6.3.247  , page 118) and
       _$_l_o_c_a_l_e (section 6.3.96	, page 86) variables in order to change the language
       of the attributions and signatures based upon the recipients.

       NNoottee:: the 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 my_hdr commands which mod-
       ify recipient headers, or the message's subject, don't have any effect on the
       current message when executed from a send-hook.

       _3_._1_9  _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_e_f_o_r_e _f_o_r_m_a_t_t_i_n_g _a _m_e_s_s_a_g_e

       Usage: message-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d








       The Mutt E-Mail Client							    28



       This command can be used to execute arbitrary configuration commands before
       viewing or formatting a message based upon information about the message.  _c_o_m_-
       _m_a_n_d is executed if the _p_a_t_t_e_r_n matches the message to be displayed. When mul-
       tiple matches occur, commands are executed in the order they are specified in
       the muttrc.

       See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.4.1  , page 40) for information on the
       exact format of _p_a_t_t_e_r_n.

       Example:

	    message-hook ~A 'set pager=builtin'
	    message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'


       _3_._2_0  _C_h_o_o_s_i_n_g _t_h_e _c_r_y_p_t_o_g_r_a_p_h_i_c _k_e_y _o_f _t_h_e _r_e_c_i_p_i_e_n_t

       Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d

       When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
       tain key with a given e-mail address automatically, either because the recipi-
       ent'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 crypt-
       hook 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.

       The meaning of "key id" is to be taken broadly in this context:	You can either
       put a numerical key ID here, an e-mail address, or even just a real name.

       _3_._2_1  _A_d_d_i_n_g _k_e_y _s_e_q_u_e_n_c_e_s _t_o _t_h_e _k_e_y_b_o_a_r_d _b_u_f_f_e_r

       Usage: push _s_t_r_i_n_g

       This command adds the named string to the keyboard buffer. The string may con-
       tain control characters, key names and function names like the sequence string
       in the _m_a_c_r_o (section 3.6  , page 19) command. You may use it to automatically
       run a sequence of commands at startup, or when entering certain folders.

       _3_._2_2  _E_x_e_c_u_t_i_n_g _f_u_n_c_t_i_o_n_s

       Usage: exec _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ]

       This command can be used to execute any function. Functions are listed in the
       _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section 6.4	, page 128).  ``exec function'' is equivalent
       to ``push <function>''.

       _3_._2_3  _M_e_s_s_a_g_e _S_c_o_r_i_n_g

       Usage: score _p_a_t_t_e_r_n _v_a_l_u_e

       Usage: unscore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

       The score commands adds _v_a_l_u_e to a message's score if _p_a_t_t_e_r_n matches it.  _p_a_t_-
       _t_e_r_n is a string in the format described in the _p_a_t_t_e_r_n_s (section 4.2  , page








       The Mutt E-Mail Client							    29



       35) section (note: For efficiency reasons, patterns which scan information not
       available in the index, such as ~b, ~B or ~h, may not be used).	_v_a_l_u_e is a
       positive or negative integer.  A message's final score is the sum total of all
       matching score entries.	However, you may optionally prefix _v_a_l_u_e with an equal
       sign (=) to cause evaluation to stop at a particular entry if there is a match.
       Negative final scores are rounded up to 0.

       The unscore command removes score entries from the list.  You mmuusstt specify the
       same pattern specified in the score command for it to be removed.  The pattern
       ``*'' is a special token which means to clear the list of all score entries.

       _3_._2_4  _S_p_a_m _d_e_t_e_c_t_i_o_n

       Usage: spam _p_a_t_t_e_r_n _f_o_r_m_a_t

       Usage: nospam _p_a_t_t_e_r_n

       Mutt has generalized support for external spam-scoring filters.	By defining
       your spam patterns with the spam and nospam commands, you can _l_i_m_i_t, _s_e_a_r_c_h,
       and _s_o_r_t your mail based on its spam attributes, as determined by the external
       filter. You also can display the spam attributes in your index display using
       the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83) variable.
       (Tip: try %?H?[%H] ?  to display spam tags only when they are defined for a
       given message.)

       Your first step is to define your external filter's spam patterns using the
       spam command. _p_a_t_t_e_r_n 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 ``spam tag'' or ``spam attribute'' (unless it also matches a
       nospam pattern -- see below.) The appearance of this attribute is entirely up
       to you, and is governed by the _f_o_r_m_a_t parameter. _f_o_r_m_a_t can be any static text,
       but it also can include back-references from the _p_a_t_t_e_r_n expression. (A regular
       expression ``back-reference'' refers to a sub-expression contained within
       parentheses.) %1 is replaced with the first back-reference in the regex, %2
       with the second, etc.

       If you're using multiple spam filters, a message can have more than one spam-
       related header. You can define spam patterns for each filter you use. If a mes-
       sage matches two or more of these patterns, and the $spam_separator variable is
       set to a string, then the message's spam tag will consist of all the _f_o_r_m_a_t
       strings joined together, with the value of $spam_separator separating them.

       For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
       these spam settings:

	    spam "X-DCC-.*-Metrics:.*(....)=many"	  "90+/DCC-%1"
	    spam "X-Spam-Status: Yes"			  "90+/SA"
	    spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
	    set spam_separator=", "


       If I then received a message that DCC registered with ``many'' hits under the
       ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
       being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four








       The Mutt E-Mail Client							    30



       characters before ``=many'' in a DCC report indicate the checksum used -- in
       this case, ``Fuz2''.)

       If the $spam_separator variable is unset, then each spam pattern match
       supercedes the previous one. Instead of getting joined _f_o_r_m_a_t strings, you'll
       get only the last one to match.

       The spam tag is what will be displayed in the index when you use %H in the
       $index_format variable. It's also the string that the ~H pattern-matching
       expression matches against for _s_e_a_r_c_h and _l_i_m_i_t functions. And it's what sort-
       ing by spam attribute will use as a sort key.

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

       Generally, when you sort by spam tag, mutt will sort _l_e_x_i_c_a_l_l_y -- that is, by
       ordering strings alphnumerically. However, if a spam tag begins with a number,
       mutt will sort numerically first, and lexically only when two numbers are equal
       in value. (This is like UNIX's sort -n.) A message with no spam attributes at
       all -- that is, one that didn't match _a_n_y of your spam patterns -- is sorted at
       lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
       Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
       ``z''. 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.

       The nospam command can be used to write exceptions to spam patterns. If a
       header pattern matches something in a spam command, but you nonetheless do not
       want it to receive a spam tag, you can list a more precise pattern under a
       nospam command.

       If the _p_a_t_t_e_r_n given to nospam is exactly the same as the _p_a_t_t_e_r_n on an exist-
       ing spam list entry, the effect will be to remove the entry from the spam list,
       instead of adding an exception.	Likewise, if the _p_a_t_t_e_r_n for a spam command
       matches an entry on the nospam list, that nospam entry will be removed. If the
       _p_a_t_t_e_r_n for nospam is ``*'', _a_l_l _e_n_t_r_i_e_s _o_n _b_o_t_h _l_i_s_t_s will be removed. This
       might be the default action if you use spam and nospam in conjunction with a
       folder-hook.

       You can have as many spam or nospam commands as you like.  You can even do your
       own primitive spam detection within mutt -- for example, if you consider all
       mail from MAILER-DAEMON to be spam, you can use a spam command like this:


	    spam "^From: .*MAILER-DAEMON"	"999"


       _3_._2_5  _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s

       Usage: set [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ]

       Usage: toggle _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ]









       The Mutt E-Mail Client							    31



       Usage: unset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ]

       Usage: reset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ]

       This command is used to set (and unset) _c_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s (section 6.3  ,
       page 62).  There are four basic types of variables: boolean, number, string and
       quadoption.  _b_o_o_l_e_a_n variables can be _s_e_t (true) or _u_n_s_e_t (false).  _n_u_m_b_e_r
       variables can be assigned a positive integer value.

       _s_t_r_i_n_g variables consist of any number of printable characters.	_s_t_r_i_n_g_s must
       be enclosed in quotes if they contain spaces or tabs.  You may also use the
       ``C'' escape sequences \\nn and \\tt for newline and tab, respectively.

       _q_u_a_d_o_p_t_i_o_n variables are used to control whether or not to be prompted for cer-
       tain actions, or to specify a default action.  A value of _y_e_s will cause the
       action to be carried out automatically as if you had answered yes to the ques-
       tion.  Similarly, a value of _n_o will cause the the action to be carried out as
       if you had answered ``no.''  A value of _a_s_k_-_y_e_s will cause a prompt with a
       default answer of ``yes'' and _a_s_k_-_n_o will provide a default answer of ``no.''

       Prefixing a variable with ``no'' will unset it.	Example: set noaskbcc.

       For _b_o_o_l_e_a_n variables, you may optionally prefix the variable name with inv to
       toggle the value (on or off).  This is useful when writing macros.  Example:
       set invsmart_wrap.

       The toggle command automatically prepends the inv prefix to all specified vari-
       ables.

       The unset command automatically prepends the no prefix to all specified vari-
       ables.

       Using the enter-command function in the _i_n_d_e_x menu, you can query the value of
       a variable by prefixing the name of the variable with a question mark:


	    set ?allow_8bit


       The question mark is actually only required for boolean and quadoption vari-
       ables.

       The reset command resets all given variables to the compile time defaults
       (hopefully mentioned in this manual). If you use the command set and prefix the
       variable with ``&'' this has the same behavior as the reset command.

       With the reset command there exists the special variable ``all'', which allows
       you to reset all variables to their system defaults.

       _3_._2_6  _R_e_a_d_i_n_g _i_n_i_t_i_a_l_i_z_a_t_i_o_n _c_o_m_m_a_n_d_s _f_r_o_m _a_n_o_t_h_e_r _f_i_l_e

       Usage: source _f_i_l_e_n_a_m_e

       This command allows the inclusion of initialization commands from other files.








       The Mutt E-Mail Client							    32



       For example, I place all of my aliases in ~/.mail_aliases so that I can make my
       ~/.muttrc readable and keep my aliases private.

       If the filename begins with a tilde (``~''), it will be expanded to the path of
       your home directory.

       If the filename ends with a vertical bar (|), then _f_i_l_e_n_a_m_e is considered to be
       an executable program from which to read input (eg.  source ~/bin/myscript|).

       _3_._2_7  _R_e_m_o_v_i_n_g _h_o_o_k_s

       Usage: unhook [ * | _h_o_o_k_-_t_y_p_e ]

       This command permits you to flush hooks you have previously defined.  You can
       either remove all hooks by giving the ``*'' character as an argument, or you
       can remove all hooks of a specific type by saying something like unhook send-
       hook.


       _4_.  _A_d_v_a_n_c_e_d _U_s_a_g_e

       _4_._1  _R_e_g_u_l_a_r _E_x_p_r_e_s_s_i_o_n_s

       All string patterns in Mutt including those in more complex _p_a_t_t_e_r_n_s (section
       4.2  , page 35) must be specified using regular expressions (regexp) in the
       ``POSIX extended'' syntax (which is more or less the syntax used by egrep and
       GNU awk).  For your convenience, we have included below a brief description of
       this syntax.

       The search is case sensitive if the pattern contains at least one upper case
       letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
       for a regular expression in an initialization command: ``\\''.

       A regular expression is a pattern that describes a set of strings.  Regular
       expressions are constructed analogously to arithmetic expressions, by using
       various operators to combine smaller expressions.

       Note that the regular expression can be enclosed/delimited by either ' or '
       which is useful if the regular expression includes a white-space character.
       See _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s (section 3.1	, page 14) for more informa-
       tion on ' and ' delimiter processing.  To match a literal ' or ' you must pref-
       ace it with \ (backslash).

       The fundamental building blocks are the regular expressions that match a single
       character.  Most characters, including all letters and digits, are regular
       expressions that match themselves.  Any metacharacter with special meaning may
       be quoted by preceding it with a backslash.

       The period ``.'' matches any single character.  The caret ``^'' and the dollar
       sign ``$'' are metacharacters that respectively match the empty string at the
       beginning and end of a line.

       A list of characters enclosed by ``['' and ``]'' matches any single character
       in that list; if the first character of the list is a caret ``^'' then it








       The Mutt E-Mail Client							    33



       matches any character nnoott in the list.  For example, the regular expression
       [[00112233445566778899]] matches any single digit.  A range of ASCII characters may be
       specified by giving the first and last characters, separated by a hyphen ``-''.
       Most metacharacters lose their special meaning inside lists.  To include a lit-
       eral ``]'' place it first in the list.  Similarly, to include a literal ``^''
       place it anywhere but first.  Finally, to include a literal hyphen ``-'' place
       it last.

       Certain named classes of characters are predefined.  Character classes consist
       of ``[:'', a keyword denoting the class, and ``:]''.  The following classes are
       defined by the POSIX standard:

	     [:alnum:]
		   Alphanumeric characters.

	     [:alpha:]
		   Alphabetic characters.

	     [:blank:]
		   Space or tab characters.

	     [:cntrl:]
		   Control characters.

	     [:digit:]
		   Numeric characters.

	     [:graph:]
		   Characters that are both printable and visible.  (A space is print-
		   able, but not visible, while an ``a'' is both.)

	     [:lower:]
		   Lower-case alphabetic characters.

	     [:print:]
		   Printable characters (characters that are not control characters.)

	     [:punct:]
		   Punctuation characters (characters that are not letter, digits,
		   control characters, or space characters).

	     [:space:]
		   Space characters (such as space, tab and formfeed, to name a few).

	     [:upper:]
		   Upper-case alphabetic characters.

	     [:xdigit:]
		   Characters that are hexadecimal digits.

       A character class is only valid in a regular expression inside the brackets of
       a character list.  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, [[[[::ddiiggiitt::]]]] is equivalent to [[00--99]].








       The Mutt E-Mail Client							    34



       Two additional special sequences can appear in character lists.	These apply to
       non-ASCII character sets, which can have single symbols (called collating ele-
       ments) that are represented with more than one character, as well as several
       characters that are equivalent for collating or sorting purposes:

	     Collating Symbols
		   A collating symbol is a multi-character collating element enclosed
		   in ``[.'' and ``.]''.  For example, if ``ch'' is a collating ele-
		   ment, then [[[[..cchh..]]]] is a regexp that matches this collating ele-
		   ment, while [[cchh]] is a regexp that matches either ``c'' or ``h''.

	     Equivalence Classes
		   An equivalence class is a locale-specific name for a list of char-
		   acters that are equivalent. The name is enclosed in ``[='' and
		   ``=]''.  For example, the name ``e'' might be used to represent all
		   of ``'' ``'' and ``e''.  In this case, [[[[==ee==]]]] is a regexp that
		   matches any of ``'', ``'' and ``e''.

       A regular expression matching a single character may be followed by one of sev-
       eral repetition operators:

	     ?
		   The preceding item is optional and matched at most once.

	     *
		   The preceding item will be matched zero or more times.

	     +
		   The preceding item will be matched one or more times.

	     {n}
		   The preceding item is matched exactly _n times.

	     {n,}
		   The preceding item is matched _n or more times.

	     {,m}
		   The preceding item is matched at most _m times.

	     {n,m}
		   The preceding item is matched at least _n times, but no more than _m
		   times.

       Two regular expressions may be concatenated; the resulting regular expression
       matches any string formed by concatenating two substrings that respectively
       match the concatenated subexpressions.

       Two regular expressions may be joined by the infix operator ``|''; the result-
       ing regular expression matches any string matching either subexpression.

       Repetition takes precedence over concatenation, which in turn takes precedence
       over alternation.  A whole subexpression may be enclosed in parentheses to
       override these precedence rules.









       The Mutt E-Mail Client							    35



       NNoottee:: If you compile Mutt with the GNU _r_x package, the following operators may
       also be used in regular expressions:

	     \\y
		   Matches the empty string at either the beginning or the end of a
		   word.

	     \\B
		   Matches the empty string within a word.

	     \\<
		   Matches the empty string at the beginning of a word.

	     \\>
		   Matches the empty string at the end of a word.

	     \\w
		   Matches any word-constituent character (letter, digit, or under-
		   score).

	     \\W
		   Matches any character that is not word-constituent.

	     \\`
		   Matches the empty string at the beginning of a buffer (string).

	     \\'
		   Matches the empty string at the end of a buffer.

       Please note however that these operators are not defined by POSIX, so they may
       or may not be available in stock libraries on various systems.

       _4_._2  _P_a_t_t_e_r_n_s

       Many of Mutt's commands allow you to specify a pattern to match (limit, tag-
       pattern, delete-pattern, etc.).	There are several ways to select messages:


























       The Mutt E-Mail Client							    36



	    ~a		    messages in threads that contain at least one tagged message;
			    this is the same as ~(~T) [see below for ~(..)]
	    ~A		    all messages
	    ~b EXPR	    messages which contain EXPR in the message body
	    ~B EXPR	    messages which contain EXPR in the whole message
	    ~c USER	    messages carbon-copied to USER
	    ~C EXPR	    message is either to: or cc: EXPR
	    ~D		    deleted messages
	    ~d [MIN]-[MAX]  messages with ``date-sent'' in a Date range
	    ~E		    expired messages
	    ~e EXPR	    message which contains EXPR in the ``Sender'' field
	    ~F		    flagged messages
	    ~f USER	    messages originating from USER
	    ~g		    cryptographically signed messages
	    ~G		    cryptographically encrypted messages
	    ~H EXPR	    messages with a spam attribute matching EXPR
	    ~h EXPR	    messages which contain EXPR in the message header
	    ~k		    message contains PGP key material
	    ~i ID	    message which match ID in the ``Message-ID'' field
	    ~L EXPR	    message is either originated or received by EXPR
	    ~l		    message is addressed to a known mailing list
	    ~m [MIN]-[MAX]  message in the range MIN to MAX *)
	    ~n [MIN]-[MAX]  messages with a score in the range MIN to MAX *)
	    ~N		    new messages
	    ~O		    old messages
	    ~p		    message is addressed to you (consults alternates)
	    ~P		    message is from you (consults alternates)
	    ~Q		    messages which have been replied to
	    ~R		    read messages
	    ~r [MIN]-[MAX]  messages with ``date-received'' in a Date range
	    ~S		    superseded messages
	    ~s SUBJECT	    messages having SUBJECT in the ``Subject'' field.
	    ~T		    tagged messages
	    ~t USER	    messages addressed to USER
	    ~U		    unread messages
	    ~v		    message is part of a collapsed thread.
	    ~V		    cryptographically verified messages
	    ~x EXPR	    messages which contain EXPR in the `References' field
	    ~y EXPR	    messages which contain EXPR in the `X-Label' field
	    ~z [MIN]-[MAX]  messages with a size in the range MIN to MAX *)
	    ~=		    duplicated messages (see $duplicate_threads)
	    ~$		    unreferenced messages (requires threaded view)
	    ~(PATTERN)	    messages in threads containing messages matching a certain
			    pattern, e.g. all threads containing messages from you: ~(~P)


       Where EXPR, USER, ID, and SUBJECT are _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n_s (section 4.1  , page
       31).  Special attention has to be made when using regular expressions inside of
       patterns.  Specifically, Mutt's parser for these patterns will strip one level
       of backslash (\), 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 back-
       slashes instead (\\).

       *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.








       The Mutt E-Mail Client							    37



       _4_._2_._1  _P_a_t_t_e_r_n _M_o_d_i_f_i_e_r

       Note that 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 ^.  This
       example matches all mails which only has recipients from Germany.


	    ^~C \.de$


       _4_._2_._2  _C_o_m_p_l_e_x _P_a_t_t_e_r_n_s

       Logical AND is performed by specifying more than one criterion.	For example:


	    ~t mutt ~f elkins


       would select messages which contain the word ``mutt'' in the list of recipients
       aanndd that have the word ``elkins'' in the ``From'' header field.

       Mutt also recognizes the following operators to create more complex search pat-
       terns:

	   ! -- logical NOT operator

	   | -- logical OR operator

	   () -- logical grouping operator

       Here is an example illustrating a complex search pattern.  This pattern will
       select all messages which do not contain ``mutt'' in the ``To'' or ``Cc'' field
       and which are from ``elkins''.


	    !(~t mutt|~c mutt) ~f elkins


       Here is an example using white space in the regular expression (note the ' and
       ' delimiters).  For this to match, the mail's subject must match the ``^Junk
       +From +Me$'' and it must be from either ``Jim +Somebody'' or ``Ed +Some-
       oneElse'':


	     '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'


       Note that if a regular expression contains parenthesis, or a veritical bar
       ("|"), you mmuusstt enclose the expression in double or single quotes since those
       characters are also used to separate different parts of Mutt's pattern lan-
       guage.  For example,










       The Mutt E-Mail Client							    38



	    ~f "me@(mutt\.org|cs\.hmc\.edu)"


       Without the quotes, the parenthesis wouldn't end.  This would be seperated to
       two OR'd patterns: _~_f _m_e_@_(_m_u_t_t_\_._o_r_g and _c_s_\_._h_m_c_\_._e_d_u_). They are never what you
       want.

       _4_._2_._3  _S_e_a_r_c_h_i_n_g _b_y _D_a_t_e

       Mutt supports two types of dates, _a_b_s_o_l_u_t_e and _r_e_l_a_t_i_v_e.

       AAbbssoolluuttee.  Dates mmuusstt 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:


	    Limit to messages matching: ~d 20/1/95-31/10


       If you omit the minimum (first) date, and just specify ``-DD/MM/YY'', all mes-
       sages _b_e_f_o_r_e the given date will be selected.  If you omit the maximum (second)
       date, and specify ``DD/MM/YY-'', all messages _a_f_t_e_r the given date will be
       selected.  If you specify a single date with no dash (``-''), only messages
       sent on the given date will be selected.

       EErrrroorr MMaarrggiinnss.  You can add error margins to absolute dates.  An error margin
       is a sign (+ or -), followed by a digit, followed by one of the following
       units:

	    y	    years
	    m	    months
	    w	    weeks
	    d	    days


       As a special case, you can replace the sign by a ``*'' character, which is
       equivalent to giving identical plus and minus error margins.

       Example: To select any messages two weeks around January 15, 2001, you'd use
       the following pattern:


	    Limit to messages matching: ~d 15/1/2001*2w


       RReellaattiivvee.  This type of date is relative to the current date, and may be speci-
       fied as:

	   >_o_f_f_s_e_t (messages older than _o_f_f_s_e_t units)

	   <_o_f_f_s_e_t (messages newer than _o_f_f_s_e_t units)

	   =_o_f_f_s_e_t (messages exactly _o_f_f_s_e_t units old)









       The Mutt E-Mail Client							    39



       _o_f_f_s_e_t is specified as a positive number with one of the following units:

	    y	    years
	    m	    months
	    w	    weeks
	    d	    days


       Example: to select messages less than 1 month old, you would use

	    Limit to messages matching: ~d <1m


       NNoottee:: all dates used when searching are relative to the llooccaall time zone, so
       unless you change the setting of your _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83)
       to include a %[...] format, these are nnoott the dates shown in the main index.

       _4_._3  _U_s_i_n_g _T_a_g_s

       Sometimes it is desirable to perform an operation on a group of messages all at
       once rather than one at a time.	An example might be to save messages to a
       mailing list to a separate folder, or to delete all messages with a given sub-
       ject.  To tag all messages matching a pattern, use the tag-pattern function,
       which is bound to ``shift-T'' by default.  Or you can select individual mes-
       sages by hand using the ``tag-message'' function, which is bound to ``t'' by
       default.  See _p_a_t_t_e_r_n_s (section 4.2  , page 35) for Mutt's pattern matching
       syntax.

       Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
       ator, which is the ``;'' (semicolon) key by default.  When the ``tag-prefix''
       operator is used, the nneexxtt operation will be applied to all tagged messages if
       that operation can be used in that manner.  If the _$_a_u_t_o___t_a_g (section 6.3.16  ,
       page 67) variable is set, the next operation applies to the tagged messages
       automatically, without requiring the ``tag-prefix''.

       In _m_a_c_r_o_s (section 3.6  , page 19) or _p_u_s_h (section 3.21  , page 28) commands,
       you can use the ``tag-prefix-cond'' 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 ``end-cond'' operator;  after this
       operator the rest of the macro will be executed as normal.

       _4_._4  _U_s_i_n_g _H_o_o_k_s

       A _h_o_o_k is a concept borrowed from the EMACS editor which allows you to execute
       arbitrary commands before performing some operation.  For example, you may wish
       to tailor your configuration based upon which mailbox you are reading, or to
       whom you are sending mail.  In the Mutt world, a _h_o_o_k consists of a _r_e_g_u_l_a_r
       _e_x_p_r_e_s_s_i_o_n (section 4.1	, page 31) or _p_a_t_t_e_r_n (section 4.2  , page 35) along
       with a configuration option/command.  See

	   _f_o_l_d_e_r_-_h_o_o_k (section 3.5  , page 18)

	   _s_e_n_d_-_h_o_o_k (section 3.18  , page 26)









       The Mutt E-Mail Client							    40



	   _m_e_s_s_a_g_e_-_h_o_o_k (section 3.19  , page 27)

	   _s_a_v_e_-_h_o_o_k (section 3.15  , page 25)

	   _m_b_o_x_-_h_o_o_k (section 3.11  , page 24)

	   _f_c_c_-_h_o_o_k (section 3.16  , page 26)

	   _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.17	, page 26)

       for specific details on each type of _h_o_o_k available.

       NNoottee:: 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:


	    send-hook . 'unmy_hdr From:'
	    send-hook ~C'^b@b\.b$' my_hdr from: c@c.c


       _4_._4_._1  _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s

       Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
       evaluated in a slightly different manner.  For the other types of hooks, a _r_e_g_-
       _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1  , page 31) is sufficient.	But in dealing with
       messages a finer grain of control is needed for matching since for different
       purposes you want to match different criteria.

       Mutt allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 4.2  , page 35) language for
       matching messages in hook commands.  This works in exactly the same way as it
       would when _l_i_m_i_t_i_n_g or _s_e_a_r_c_h_i_n_g the mailbox, except that you are restricted to
       those operators which match information mutt extracts from the header of the
       message (i.e.  from, to, cc, date, subject, etc.).

       For example, if you wanted to set your return address based upon sending mail
       to a specific address, you could do something like:

	    send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'


       which would execute the given command when sending mail to _m_e_@_c_s_._h_m_c_._e_d_u.

       However, it is not required that you write the pattern to match using the full
       searching language.  You can still specify a simple _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n like the
       other hooks, in which case Mutt will translate your pattern into the full lan-
       guage, using the translation specified by the _$_d_e_f_a_u_l_t___h_o_o_k (section 6.3.37  ,
       page 71) variable.  The pattern is translated at the time the hook is declared,
       so the value of _$_d_e_f_a_u_l_t___h_o_o_k (section 6.3.37  , page 71) that is in effect at
       that time will be used.

       _4_._5  _E_x_t_e_r_n_a_l _A_d_d_r_e_s_s _Q_u_e_r_i_e_s









       The Mutt E-Mail Client							    41



       Mutt supports connecting to external directory databases such as LDAP, ph/qi,
       bbdb, or NIS through a wrapper script which connects to mutt using a simple
       interface.  Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 6.3.216  , page 111) variable,
       you specify the wrapper command to use.	For example:


	    set query_command = "mutt_ldap_query.pl '%s'"


       The wrapper script should accept the query on the command-line.	It should
       return a one line message, then each matching response on a 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.

       An example multiple response output:

	    Searching database ... 20 entries ... 3 matching:
	    me@cs.hmc.edu	    Michael Elkins  mutt dude
	    blong@fiction.net	    Brandon Long    mutt and more
	    roessler@guug.de	    Thomas Roessler mutt pgp


       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.

       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.

       _4_._6  _M_a_i_l_b_o_x _F_o_r_m_a_t_s

       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 _$_m_b_o_x___t_y_p_e (section 6.3.105  , page 87) vari-
       able.

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


	    From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST










       The Mutt E-Mail Client							    42



       to denote the start of a new message (this is often referred to as the
       ``From_'' line).

       MMMMDDFF.  This is a variant of the _m_b_o_x format.  Each message is surrounded by
       lines containing ``^A^A^A^A'' (four control-A's).

       MMHH. A radical departure from _m_b_o_x and _M_M_D_F, a mailbox consists of a directory
       and each message is stored in a separate file.  The filename indicates the mes-
       sage number (however, this is may not correspond to the message number Mutt
       displays). Deleted messages are renamed with a comma (,) prepended to the file-
       name. NNoottee:: Mutt detects this type of mailbox by looking for either
       .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
       mailboxes).

       MMaaiillddiirr.  The newest of the mailbox formats, used by the Qmail MTA (a replace-
       ment for sendmail).  Similar to _M_H, except that it adds three subdirectories of
       the mailbox: _t_m_p, _n_e_w and _c_u_r.  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.

       _4_._7  _M_a_i_l_b_o_x _S_h_o_r_t_c_u_t_s

       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.

	   ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 6.3.258  , page 121) (incoming)
	    mailbox

	   > -- refers to your _$_m_b_o_x (section 6.3.104  , page 87) file

	   < -- refers to your _$_r_e_c_o_r_d (section 6.3.225  , page 113) file

	   - or !! -- refers to the file you've last visited

	   ~ -- refers to your home directory

	   = or + -- refers to your _$_f_o_l_d_e_r (section 6.3.54  , page 74) directory

	   @_a_l_i_a_s -- refers to the _d_e_f_a_u_l_t _s_a_v_e _f_o_l_d_e_r (section 3.15  , page 25) as
	    determined by the address of the alias

       _4_._8  _H_a_n_d_l_i_n_g _M_a_i_l_i_n_g _L_i_s_t_s

       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 mail-
       ing 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 _l_i_s_t_s _a_n_d _s_u_b_s_c_r_i_b_e
       (section 3.10  , page 23) commands in your muttrc.

       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 _i_n_d_e_x menu display.








       The Mutt E-Mail Client							    43



       This is useful to distinguish between personal and list mail in the same mail-
       box.  In the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83) variable, the escape
       ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
       field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
       returns the name of the author).

       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
       _i_n_d_e_x menu and _p_a_g_e_r, helps reduce the clutter by only replying to the known
       mailing list addresses instead of all recipients (except as specified by Mail-
       Followup-To, see below).

       Mutt also supports the Mail-Followup-To header.	When you send a message to a
       list of recipients which includes one or several subscribed mailing lists, and
       if the _$_f_o_l_l_o_w_u_p___t_o (section 6.3.56  , page 75) option is set, mutt will gener-
       ate 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.

       Conversely, when group-replying or list-replying to a message which has a Mail-
       Followup-To header, mutt will respect this header if the _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o
       (section 6.3.74	, page 79) 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 Mail-Followup-To.

       Note that, when header editing is enabled, you can create a Mail-Followup-To
       header manually.  Mutt will only auto-generate this header if it doesn't exist
       when you send the message.

       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 _$_r_e_p_l_y___t_o (section
       6.3.228	, page 113) variable to help decide which address to use.  If set to
       _a_s_k_-_y_e_s or _a_s_k_-_n_o, 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 _y_e_s, the ``Reply-To'' field
       will be used when present.

       The ``X-Label:'' header field can be used to further identify mailing lists or
       list subject matter (or just to annotate messages individually).  The
       _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83) 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 eas-
       ily be inserted by procmail and other mail filtering agents.

       Lastly, Mutt has the ability to _s_o_r_t (section 6.3.252  , page 119) the mailbox
       into _t_h_r_e_a_d_s (section 2.3.3  , page 7).	A thread is a group of messages which








       The Mutt E-Mail Client							    44



       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.

       _4_._9  _D_e_l_i_v_e_r_y _S_t_a_t_u_s _N_o_t_i_f_i_c_a_t_i_o_n _(_D_S_N_) _S_u_p_p_o_r_t

       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.

       To support this, there are two variables. _$_d_s_n___n_o_t_i_f_y (section 6.3.43  , page
       72) is used to request receipts for different results (such as failed message,
       message delivered, etc.).  _$_d_s_n___r_e_t_u_r_n (section 6.3.44  , page 72) requests how
       much of your message should be returned with the receipt (headers or full mes-
       sage).  Refer to the man page on sendmail for more details on DSN.

       _4_._1_0  _P_O_P_3 _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_)

       If Mutt was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with
       the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to work with mailboxes located on a
       remote POP3 server and fetch mail for local browsing.

       You can access the remote POP3 mailbox by selecting the folder
       pop://popserver/.

       You can select an alternative port by specifying it with the server, ie:
       pop://popserver:port/.

       You can also specify different username for each folder, ie: pop://user-
       name@popserver[:port]/.

       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 _$_p_o_p___c_h_e_c_k_i_n_t_e_r_v_a_l (section 6.3.200	, page 108) variable, which defaults
       to every 60 seconds.

       If Mutt was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with the
       _-_-_w_i_t_h_-_s_s_l flag), connections to POP3 servers can be encrypted. This naturally
       requires that the server supports SSL encrypted connections. To access a folder
       with POP3/SSL, you should use pops: prefix, ie: pops://[user-
       name@]popserver[:port]/.

       Another way to access your POP3 mail is the _f_e_t_c_h_-_m_a_i_l function (default: G).
       It allows to connect to _p_o_p___h_o_s_t (section 6.3.202  , page 108), fetch all your
       new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.3.258  , page 121).
       After this point, Mutt runs exactly as if the mail had always been local.

       NNoottee:: If you only need to fetch all messages to local mailbox you should con-
       sider using a specialized program, such as fetchmail









       The Mutt E-Mail Client							    45



       _4_._1_1  _I_M_A_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_)

       If Mutt was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with
       the _-_-_e_n_a_b_l_e_-_i_m_a_p flag), it has the ability to work with folders located on a
       remote IMAP server.

       You can access the remote inbox by selecting the folder
       imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
       INBOX is the special name for your spool mailbox on the IMAP server. If you
       want to access another mail folder at the IMAP server, you should use
       imap://imapserver/path/to/folder where path/to/folder is the path of the folder
       you want to access.

       You can select an alternative port by specifying it with the server, ie:
       imap://imapserver:port/INBOX.

       You can also specify different username for each folder, ie: imap://user-
       name@imapserver[:port]/INBOX.

       If Mutt was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with the
       _-_-_w_i_t_h_-_s_s_l flag), connections to IMAP servers can be encrypted. This naturally
       requires that the server supports SSL encrypted connections. To access a folder
       with IMAP/SSL, you should use imaps://[user-
       name@]imapserver[:port]/path/to/folder as your folder path.

       Pine-compatible notation is also supported, ie {[user-
       name@]imapserver[:port][/ssl]}path/to/folder

       Note that not all servers use / as the hierarchy separator.  Mutt should cor-
       rectly notice which separator is being used by the server and convert paths
       accordingly.

       When browsing folders on an IMAP server, you can toggle whether to look at only
       the folders you are subscribed to, or all folders with the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d
       command.  See also the _$_i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d (section 6.3.83  , page 81) vari-
       able.

       Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
       want to carefully tune the _$_m_a_i_l___c_h_e_c_k (section 6.3.97  , page 86) and _$_t_i_m_e_o_u_t
       (section 6.3.268  , page 125) variables. Personally I use

	    set mail_check=90
	    set timeout=15


       with relatively good results over my slow modem line.

       Note that if you are using mbox as the mail store on UW servers prior to
       v12.250, the server has been reported to disconnect a client if another client
       selects the same folder.

       _4_._1_1_._1  _T_h_e _F_o_l_d_e_r _B_r_o_w_s_e_r

       As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is








       The Mutt E-Mail Client							    46



       mostly the same as the local file browser, with the following differences:

	   In lieu of file permissions, mutt displays the string "IMAP", possibly
	    followed by the symbol "+", indicating that the entry contains both mes-
	    sages and subfolders. On Cyrus-like servers folders will often contain
	    both messages and subfolders.

	   For the case where an entry can contain both messages and subfolders, the
	    selection key (bound to enter by default) will choose to descend into the
	    subfolder view. If you wish to view the messages in that folder, you must
	    use view-file instead (bound to space by default).

	   You can create, delete and rename mailboxes with the create-mailbox,
	    delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
	    respectively). You may also subscribe and unsubscribe to mailboxes (nor-
	    mally these are bound to s and u, respectively).

       _4_._1_1_._2  _A_u_t_h_e_n_t_i_c_a_t_i_o_n

       Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI,
       CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
       tion for you poor exchange users out there, but it has 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".

       SASL is a special super-authenticator, which selects among several protocols
       (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
       available on your host and the server. Using some of these methods (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 _-_-_w_i_t_h_-_s_a_s_l flag.

       Mutt will try whichever methods are compiled in and available on the server, in
       the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.

       There are a few variables which control authentication:

	   _$_i_m_a_p___u_s_e_r (section 6.3.88  , page 82) - controls the username under which
	    you request authentication on the IMAP server, for all authenticators.
	    This is overridden by an explicit username in the mailbox path (ie by
	    using a mailbox name of the form {user@host}).

	   _$_i_m_a_p___p_a_s_s (section 6.3.84  , page 81) - a password which you may preset,
	    used by all authentication methods where a password is needed.

	   _$_i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s (section 6.3.77  , page 80) - 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 listed above).

       _4_._1_2  _M_a_n_a_g_i_n_g _m_u_l_t_i_p_l_e _I_M_A_P_/_P_O_P _a_c_c_o_u_n_t_s _(_O_P_T_I_O_N_A_L_)









       The Mutt E-Mail Client							    47



       If you happen to have accounts on multiple IMAP and/or POP 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 (including inside the folder
       browser), not just when you open the mailbox.

       Some examples:


	    account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
	    account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
	    account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'


       _4_._1_3  _S_t_a_r_t _a _W_W_W _B_r_o_w_s_e_r _o_n _U_R_L_s _(_E_X_T_E_R_N_A_L_)

       If a message contains URLs (_u_n_i_f_i_e_d _r_e_s_o_u_r_c_e _l_o_c_a_t_o_r = address in the WWW space
       like _h_t_t_p_:_/_/_w_w_w_._m_u_t_t_._o_r_g_/), it is efficient to get a menu with all the URLs and
       start a WWW browser on one of them.  This functionality is provided by the
       external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
       trib/ and the configuration commands:

	    macro index \cb |urlview\n
	    macro pager \cb |urlview\n


       _4_._1_4  _C_o_m_p_r_e_s_s_e_d _f_o_l_d_e_r_s _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_)

       If Mutt was compiled with compressed folders support (by running the _c_o_n_f_i_g_u_r_e
       script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d flag), Mutt can open folders stored in an
       arbitrary format, provided that the user has a script to convert from/to this
       format to one of the accepted.

       The most common use is to open compressed archived folders e.g. with gzip.

       In addition, the user can provide a script that gets a folder in an accepted
       format and appends its context to the folder in the user-defined format, which
       may be faster than converting the entire folder to the accepted format, append-
       ing to it and converting back to the user-defined format.

       There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.14.1  , page 48), _c_l_o_s_e_-
       _h_o_o_k (section 4.14.2  , page 48) and _a_p_p_e_n_d_-_h_o_o_k (section 4.14.3  , page 49))
       which define commands to uncompress and compress a folder and to append mes-
       sages to an existing compressed folder respectively.

       For example:


	    open-hook \\.gz$ "gzip -cd %f > %t"
	    close-hook \\.gz$ "gzip -c %t > %f"
	    append-hook \\.gz$ "gzip -c %t >> %f"


       You do not have to specify all of the commands. If you omit _a_p_p_e_n_d_-_h_o_o_k








       The Mutt E-Mail Client							    48



       (section 4.14.3	, page 49), the folder will be open and closed again each time
       you will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.14.2  , page 48) (or give
       empty command) , the folder will be open in the	mode. If you specify _a_p_p_e_n_d_-
       _h_o_o_k (section 4.14.3  , page 49) though you'll be able to append to the folder.

       Note that Mutt will only try to use hooks if the file is not in one of the
       accepted formats. In particular, if the file is empty, mutt supposes it is not
       compressed. This is important because it allows the use of programs that do not
       have well defined extensions. Just use '.' as a regexp. But this may be sur-
       prising if your compressing script produces empty files. In this situation,
       unset _$_s_a_v_e___e_m_p_t_y (section 6.3.235  , page 115), so that the compressed file
       will be removed if you delete all of the messages.

       _4_._1_4_._1  _O_p_e_n _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x _f_o_r _r_e_a_d_i_n_g

       Usage: open-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d'

       The _c_o_m_m_a_n_d is the command that can be used for opening the folders whose names
       match _r_e_g_e_x_p.

       The _c_o_m_m_a_n_d string is the printf-like format string, and it should accept two
       parameters: %f, which is replaced with the (compressed) folder name, and %t
       which is replaced with the name of the temporary folder to which to write.

       %f and %t can be repeated any number of times in the command string, and all of
       the entries are replaced with the appropriate folder name. In addition, %% is
       replaced by %, as in printf, and any other %anything is left as is.

       The _c_o_m_m_a_n_d should nnoott remove the original compressed file.  The _c_o_m_m_a_n_d should
       return non-zero exit status if it fails, so mutt knows something's wrong.

       Example:


	    open-hook \\.gz$ "gzip -cd %f > %t"


       If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type.

       _4_._1_4_._2  _W_r_i_t_e _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x

       Usage: close-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d'

       This is used to close the folder that was open with the _o_p_e_n_-_h_o_o_k (section
       4.14.1  , page 48) command after some changes were made to it.

       The _c_o_m_m_a_n_d string is the command that can be used for closing the folders
       whose names match _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section
       4.14.1  , page 48) command. Temporary folder in this case is the folder previ-
       ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.14.1  , page 48) command.

       The _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d should return
       non-zero exit status if it fails, so mutt knows something's wrong.









       The Mutt E-Mail Client							    49



       Example:


	    close-hook \\.gz$ "gzip -c %t > %f"


       If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type, and the
       file can only be open in the readonly mode.

       _c_l_o_s_e_-_h_o_o_k (section 4.14.2  , page 48) is not called when you exit from the
       folder if the folder was not changed.

       _4_._1_4_._3  _A_p_p_e_n_d _a _m_e_s_s_a_g_e _t_o _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x

       Usage: append-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d'

       This command is used for saving to an existing compressed folder.  The _c_o_m_m_a_n_d
       is the command that can be used for appending to the folders whose names match
       _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.14.1  , page 48)
       command.  The temporary folder in this case contains the messages that are
       being appended.

       The _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d should return
       non-zero exit status if it fails, so mutt knows something's wrong.

       Example:


	    append-hook \\.gz$ "gzip -c %t >> %f"


       When _a_p_p_e_n_d_-_h_o_o_k (section 4.14.3  , page 49) is used, the folder is not opened,
       which saves time, but this means that we can not find out what the folder type
       is. Thus the default (_$_m_b_o_x___t_y_p_e (section 6.3.105  , page 87)) type is always
       supposed (i.e.  this is the format used for the temporary folder).

       If the file does not exist when you save to it, _c_l_o_s_e_-_h_o_o_k (section 4.14.2  ,
       page 48) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.14.3	, page 49). _a_p_p_e_n_d_-
       _h_o_o_k (section 4.14.3  , page 49) is only for appending to existing folders.

       If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. In this
       case, the folder will be open and closed again (using _o_p_e_n_-_h_o_o_k (section
       4.14.1  , page 48) and _c_l_o_s_e_-_h_o_o_k (section 4.14.2  , page 48)respectively) each
       time you will add to it.

       _4_._1_4_._4  _E_n_c_r_y_p_t_e_d _f_o_l_d_e_r_s

       The compressed folders support can also be used to handle encrypted folders. If
       you want to encrypt a folder with PGP, you may want to use the following hooks:


	    open-hook  \\.pgp$ "pgp -f < %f > %t"
	    close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"









       The Mutt E-Mail Client							    50



       Please note, that PGP does not support appending to an encrypted folder, so
       there is no append-hook defined.

       NNoottee:: the folder is temporary stored decrypted in the /tmp directory, where it
       can be read by your system administrator. So think about the security aspects
       of this.


       _5_.  _M_u_t_t_'_s _M_I_M_E _S_u_p_p_o_r_t

       Quite a bit of effort has been made to make Mutt the premier text-mode MIME
       MUA.  Every effort has been made to provide the functionality that the discern-
       ing MIME user requires, and the conformance to the standards wherever possible.
       When configuring Mutt for MIME, there are two extra types of configuration
       files which Mutt uses.  One is the mime.types file, which contains the mapping
       of file extensions to IANA MIME types.  The other is the mailcap file, which
       specifies the external commands to use for handling specific MIME types.

       _5_._1  _U_s_i_n_g _M_I_M_E _i_n _M_u_t_t

       There are three areas/menus in Mutt which deal with MIME, they are the pager
       (while viewing a message), the attachment menu and the compose menu.

       _5_._1_._1  _V_i_e_w_i_n_g _M_I_M_E _m_e_s_s_a_g_e_s _i_n _t_h_e _p_a_g_e_r

       When you select a message from the index and view it in the pager, Mutt decodes
       the message to a text representation.  Mutt internally supports a number of
       MIME types, including text/plain, text/enriched, message/rfc822, and mes-
       sage/news.  In addition, the export controlled version of Mutt recognizes a
       variety of PGP MIME types, including PGP/MIME and application/pgp.

       Mutt will denote attachments with a couple lines describing them.  These lines
       are of the form:

	    [-- Attachment #1: Description --]
	    [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]


       Where the Description is the description or filename given for the attachment,
       and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.

       If Mutt cannot deal with a MIME type, it will display a message like:

	    [-- image/gif is unsupported (use 'v' to view this part) --]


       _5_._1_._2  _T_h_e _A_t_t_a_c_h_m_e_n_t _M_e_n_u

       The default binding for view-attachments is `v', 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 ``tag-prefix'' operator.  You
       can also reply to the current message from this menu, and only the current








       The Mutt E-Mail Client							    51



       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.

       Finally, you can apply the usual message-related functions (like _r_e_s_e_n_d_-_m_e_s_s_a_g_e
       (section 2.3.4  , page 9), and the reply and forward functions) to attachments
       of type message/rfc822.

       See the help on the attachment menu for more information.

       _5_._1_._3  _T_h_e _C_o_m_p_o_s_e _M_e_n_u

       The compose menu is the menu you see before you send a message.	It allows you
       to edit the recipient list, the subject, and other aspects of your message.  It
       also contains a list of the attachments of your message, including the main
       body.  From this menu, you can print, copy, filter, pipe, edit, compose,
       review, and rename an attachment or a list of tagged attachments.  You can also
       modifying the attachment information, notably the type, encoding and descrip-
       tion.

       Attachments appear as follows:

	    -	1 [text/plain, 7bit, 1K]	     /tmp/mutt-euler-8082-0 <no description>
		2 [applica/x-gunzip, base64, 422K]   ~/src/mutt-0.85.tar.gz <no description>


       The '-' denotes that Mutt will delete the file after sending (or postponing, or
       cancelling) the message.  It can be toggled with the toggle-unlink command
       (default: u).  The next field is the MIME content-type, and can be changed with
       the edit-type 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 edit-encoding 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
       rename-file command (default: R).  The final field is the description of the
       attachment, and can be changed with the edit-description command (default: d).

       _5_._2  _M_I_M_E _T_y_p_e _c_o_n_f_i_g_u_r_a_t_i_o_n _w_i_t_h _m_i_m_e_._t_y_p_e_s

       When you add an attachment to your mail message, Mutt searches your personal
       mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
       /usr/local/share/mutt/mime.types or /etc/mime.types

       The mime.types file consist of lines containing a MIME type and a space sepa-
       rated list of extensions.  For example:

	    application/postscript	    ps eps
	    application/pgp		    pgp
	    audio/x-aiff		    aif aifc aiff


       A sample mime.types file comes with the Mutt distribution, and should contain
       most of the MIME types you are likely to use.

       If Mutt can not determine the mime type by the extension of the file you








       The Mutt E-Mail Client							    52



       attach, it will look at the file.  If the file is free of binary information,
       Mutt will assume that the file is plain text, and mark it as text/plain.  If
       the file contains binary information, then Mutt will mark it as applica-
       tion/octet-stream.  You can change the MIME type that Mutt assigns to an
       attachment by using the edit-type 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 recognises all of these
       if the appropriate entry is found in the mime.types file. It also recognises
       other major mime types, such as the chemical type that is widely used in the
       molecular modelling community to pass molecular data in various forms to vari-
       ous molecular viewers. Non-recognised mime types should only be used if the
       recipient of the message is likely to be expecting such attachments.

       _5_._3  _M_I_M_E _V_i_e_w_e_r _c_o_n_f_i_g_u_r_a_t_i_o_n _w_i_t_h _m_a_i_l_c_a_p

       Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific for-
       mat specified in Appendix A of RFC 1524.  This file format 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.

       In order to handle various MIME types that Mutt can not handle internally, Mutt
       parses a series of external configuration files to find an external handler.
       The default search string for these files is a colon delimited list set to

	    ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap


       where $HOME is your home directory.

       In particular, the metamail distribution will install a mailcap file, usually
       as /usr/local/etc/mailcap, which contains some baseline entries.

       _5_._3_._1  _T_h_e _B_a_s_i_c_s _o_f _t_h_e _m_a_i_l_c_a_p _f_i_l_e

       A mailcap file consists of a series of lines which are comments, blank, or def-
       initions.

       A comment line consists of a # character followed by anything you want.

       A blank line is blank.

       A definition line consists of a content type, a view command, and any number of
       optional fields.  Each field of a definition line is divided by a semicolon ';'
       character.

       The content type is specified in the MIME standard type/subtype method.	For
       example, text/plain, text/html, image/gif, etc.	In addition, the mailcap for-
       mat includes two formats for wildcards, one using the special '*' subtype, the
       other is the implicit wild, where you only include the major type.  For exam-
       ple, image/*, or video, will match all image types and video types, respec-
       tively.








       The Mutt E-Mail Client							    53



       The view command is a Unix command for viewing the type specified. There are
       two different types of commands supported. The default is to send the body of
       the MIME message to the command on stdin. You can change this behaviour by
       using %s as a parameter to your view command.  This will cause Mutt to save the
       body of the MIME message to a temporary file, and then call the view command
       with the %s replaced by the name of the temporary file. In both cases, Mutt
       will turn over the terminal to the view program until the program quits, at
       which time Mutt will remove the temporary file if it exists.

       So, in the simplest form, you can send a text/plain message to the external
       pager more on stdin:

	    text/plain; more


       Or, you could send the message as a file:

	    text/plain; more %s


       Perhaps you would like to use lynx to interactively view a text/html message:

	    text/html; lynx %s


       In this case, lynx does not support viewing a file from stdin, so you must use
       the %s syntax.  NNoottee:: _S_o_m_e _o_l_d_e_r _v_e_r_s_i_o_n_s _o_f _l_y_n_x _c_o_n_t_a_i_n _a _b_u_g _w_h_e_r_e _t_h_e_y _w_i_l_l
       _c_h_e_c_k _t_h_e _m_a_i_l_c_a_p _f_i_l_e _f_o_r _a _v_i_e_w_e_r _f_o_r _t_e_x_t_/_h_t_m_l_.  _T_h_e_y _w_i_l_l _f_i_n_d _t_h_e _l_i_n_e
       _w_h_i_c_h _c_a_l_l_s _l_y_n_x_, _a_n_d _r_u_n _i_t_.  _T_h_i_s _c_a_u_s_e_s _l_y_n_x _t_o _c_o_n_t_i_n_u_o_u_s_l_y _s_p_a_w_n _i_t_s_e_l_f _t_o
       _v_i_e_w _t_h_e _o_b_j_e_c_t_.

       On the other hand, maybe you don't want to use lynx interactively, you just
       want to have it convert the text/html to text/plain, then you can use:

	    text/html; lynx -dump %s | more


       Perhaps you wish to use lynx to view text/html files, and a pager on all other
       text formats, then you would use the following:

	    text/html; lynx %s
	    text/*; more


       This is the simplest form of a mailcap file.

       _5_._3_._2  _S_e_c_u_r_e _u_s_e _o_f _m_a_i_l_c_a_p

       The interpretion of shell meta-characters embedded in MIME parameters can lead
       to security problems in general.  Mutt tries to quote parameters in expansion
       of %s syntaxes properly, and avoids risky characters by substituting them, see
       the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 6.3.99  , page 86) variable.

       Although mutt's procedures to invoke programs with mailcap seem to be safe,








       The Mutt E-Mail Client							    54



       there are other applications parsing mailcap, maybe taking less care of it.
       Therefore you should pay attention to the following rules:

       _K_e_e_p _t_h_e _%_-_e_x_p_a_n_d_o_s _a_w_a_y _f_r_o_m _s_h_e_l_l _q_u_o_t_i_n_g_.  Don't quote them with single or
       double quotes.  Mutt does this for you, the right way, as should any other pro-
       gram which interprets mailcap.  Don't put them into backtick expansions.  Be
       highly careful with eval statements, and avoid them if possible at all.	Trying
       to fix broken behaviour with quotes introduces new leaks - there is no alterna-
       tive to correct quoting in the first place.

       If you have to use the %-expandos' values in context where you need quoting or
       backtick expansions, put that value into a shell variable and reference the
       shell variable where necessary, as in the following example (using $charset
       inside the backtick expansion is safe, since it is not itself subject to any
       further expansion):


	    text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
		    && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1


       _5_._3_._3  _A_d_v_a_n_c_e_d _m_a_i_l_c_a_p _U_s_a_g_e

       _5_._3_._3_._1	_O_p_t_i_o_n_a_l _F_i_e_l_d_s

       In addition to the required content-type and view command fields, you can add
       semi-colon ';' separated fields to set flags and other options.	Mutt recog-
       nizes the following optional fields:

	     copiousoutput
		   This flag tells Mutt that the command passes possibly large amounts
		   of text on stdout.  This causes Mutt to invoke a pager (either the
		   internal pager or the external pager defined by the pager variable)
		   on the output of the view command.  Without this flag, Mutt assumes
		   that the command is interactive.  One could use this to replace the
		   pipe to more in the lynx -dump example in the Basic section:

			text/html; lynx -dump %s ; copiousoutput


		   This will cause lynx to format the text/html output as text/plain
		   and Mutt will use your standard pager to display the results.

	     needsterminal
		   Mutt uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (section
		   5.4	, page 58), in order to decide whether it should honor the
		   setting of the _$_w_a_i_t___k_e_y (section 6.3.278  , page 127) variable or
		   not.  When an attachment is viewed using an interactive program,
		   and the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, Mutt
		   will use _$_w_a_i_t___k_e_y (section 6.3.278	, page 127) and the exit sta-
		   tus of the program to decide if it will ask you to press a key
		   after the external program has exited.  In all other situations it
		   will not prompt you for a key.









       The Mutt E-Mail Client							    55



	     compose=<command>
		   This flag specifies the command to use to create a new attachment
		   of a specific MIME type.  Mutt supports this from the compose menu.

	     composetyped=<command>
		   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 used to specify parameters, filename, description, etc.
		   for a new attachment.   Mutt supports this from the compose menu.

	     print=<command>
		   This flag specifies the command to use to print a specific MIME
		   type.  Mutt supports this from the attachment and compose menus.

	     edit=<command>
		   This flag specifies the command to use to edit a specific MIME
		   type.  Mutt supports this from the compose menu, and also uses it
		   to compose new attachments.	Mutt will default to the defined edi-
		   tor for text attachments.

	     nametemplate=<template>
		   This field specifies the format for the file denoted by %s in the
		   command fields.  Certain programs will require a certain file
		   extension, for instance, to correctly view a file.  For instance,
		   lynx will only interpret a file as text/html if the file ends in
		   .html.  So, you would specify lynx as a text/html viewer with a
		   line in the mailcap file like:

			text/html; lynx %s; nametemplate=%s.html


	     test=<command>
		   This field specifies a command to run to test whether this mailcap
		   entry should be used.  The command is defined with the command
		   expansion rules defined in the next section.  If the command
		   returns 0, then the test passed, and Mutt uses this entry.  If the
		   command returns non-zero, then the test failed, and Mutt continues
		   searching for the right entry.  NNoottee:: _t_h_e _c_o_n_t_e_n_t_-_t_y_p_e _m_u_s_t _m_a_t_c_h
		   _b_e_f_o_r_e _M_u_t_t _p_e_r_f_o_r_m_s _t_h_e _t_e_s_t_.  For example:

			text/html; netscape -remote 'openURL(%s)' ; test=RunningX
			text/html; lynx %s


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

       _5_._3_._3_._2	_S_e_a_r_c_h _O_r_d_e_r









       The Mutt E-Mail Client							    56



       When searching for an entry in the mailcap file, Mutt will search for the most
       useful entry for its purpose.  For instance, if you are attempting to print an
       image/gif, and you have the following entries in your mailcap file, Mutt will
       search for an entry with the print command:

	    image/*;	    xv %s
	    image/gif;	    ; print= anytopnm %s | pnmtops | lpr; \
			    nametemplate=%s.gif


       Mutt will skip the image/* entry and use the image/gif entry with the print
       command.

       In addition, you can use this with _A_u_t_o_v_i_e_w (section 5.4  , page 58) 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 viewer to use interactively
       depending on your environment.

	    text/html;	    netscape -remote 'openURL(%s)' ; test=RunningX
	    text/html;	    lynx %s; nametemplate=%s.html
	    text/html;	    lynx -dump %s; nametemplate=%s.html; copiousoutput


       For _A_u_t_o_v_i_e_w (section 5.4  , page 58), 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 for interactive viewing.

       _5_._3_._3_._3	_C_o_m_m_a_n_d _E_x_p_a_n_s_i_o_n

       The various commands defined in the mailcap files are passed to the /bin/sh
       shell using the system() function.  Before the command is passed to /bin/sh -c,
       it is parsed to expand various special parameters with information from Mutt.
       The keywords Mutt expands are:

	     %s
		   As seen in the basic mailcap section, this variable is expanded to
		   a filename specified by the calling program.  This file contains
		   the body of the message to view/print/edit or where the composing
		   program should place the results of composition.  In addition, the
		   use of this keyword causes Mutt to not pass the body of the message
		   to the view/print/edit program on stdin.

	     %t
		   Mutt will expand %t to the text representation of the content type
		   of the message in the same form as the first parameter of the mail-
		   cap definition line, ie text/html or image/gif.

	     %{<parameter>}
		   Mutt will expand this to the value of the specified parameter from
		   the Content-Type: line of the mail message.	For instance, if Your
		   mail message contains:









       The Mutt E-Mail Client							    57



			Content-Type: text/plain; charset=iso-8859-1


		   then Mutt will expand %{charset} to iso-8859-1.  The default meta-
		   mail mailcap file uses this feature to test the charset to spawn an
		   xterm using the right charset to view the message.

	     \%
		   This will be replaced by a %

       Mutt does not currently support the %F and %n keywords specified in RFC 1524.
       The main purpose of these parameters is for multipart messages, which is han-
       dled internally by Mutt.

       _5_._3_._4  _E_x_a_m_p_l_e _m_a_i_l_c_a_p _f_i_l_e_s

       This mailcap file is fairly simple and standard:

	    # I'm always running X :)
	    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)'


       This mailcap file shows quite a number of examples:



































       The Mutt E-Mail Client							    58



	    # Use xanim to view all videos   Xanim produces a header on startup,
	    # 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

	    # If I'm not running netscape but I am running X, start netscape on the
	    # object
	    text/html;	    netscape %s; test=RunningX

	    # Else use lynx to view it as text
	    text/html;	    lynx %s

	    # This version would convert the text/html to text/plain
	    text/html;	    lynx -dump %s; copiousoutput

	    # 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
	    image/jpeg;xv %s; x-mozilla-flags=internal

	    # Use xv to view images if I'm running X
	    # In addition, this uses the \ to extend the line and set my editor
	    # for images
	    image/*;xv %s; test=RunningX; \
		    edit=xpaint %s

	    # Convert images to text using the netpbm tools
	    image/*;  (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
	    pbmtoascii -1x2 ) 2>&1 ; copiousoutput

	    # Send excel spreadsheets to my NT box
	    application/ms-excel; open.pl %s


       _5_._4  _M_I_M_E _A_u_t_o_v_i_e_w

       In addition to explicitly telling Mutt to view an attachment with the MIME
       viewer defined in the mailcap file, Mutt has support for automatically viewing
       MIME attachments while in the pager.

       To work, you must define a viewer in the mailcap file which uses the copi-
       ousoutput option to denote that it is non-interactive.  Usually, you also use
       the entry to convert the attachment to a text representation which you can view
       in the pager.

       You then use the auto_view muttrc command to list the content-types that you
       wish to view automatically.

       For instance, if you set auto_view to:

	    auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz








       The Mutt E-Mail Client							    59



       Mutt could use the following mailcap entries to automatically view attachments
       of these types.

	    text/html;	    lynx -dump %s; copiousoutput; nametemplate=%s.html
	    image/*;	    anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
	    application/x-gunzip;   gzcat; copiousoutput
	    application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
	    application/postscript; ps2ascii %s; copiousoutput


       ``unauto_view'' 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.
       ``unauto_view *'' will remove all previous entries.

       _5_._5  _M_I_M_E _M_u_l_t_i_p_a_r_t_/_A_l_t_e_r_n_a_t_i_v_e

       Mutt has some heuristics for determining which attachment of a multipart/alter-
       native 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:

	    alternative_order text/enriched text/plain text application/postscript image/*


       Next, mutt will check if any of the types have a defined _a_u_t_o___v_i_e_w (section
       5.4  , page 58), 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.

       To remove a MIME type from the alternative_order list, use the unalterna-
       tive_order command.

       _5_._6  _M_I_M_E _L_o_o_k_u_p

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

	    mime_lookup application/octet-stream application/X-Lotus-Manuscript


       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.


       _6_.  _R_e_f_e_r_e_n_c_e

       _6_._1  _C_o_m_m_a_n_d _l_i_n_e _o_p_t_i_o_n_s









       The Mutt E-Mail Client							    60



       Running mutt with no arguments will make Mutt attempt to read your spool mail-
       box.  However, it is possible to read other mailboxes and to send messages from
       the command line as well.


	    -A	    expand an alias
	    -a	    attach a file to a message
	    -b	    specify a blind carbon-copy (BCC) address
	    -c	    specify a carbon-copy (Cc) address
	    -e	    specify a config command to be run after initilization files are read
	    -f	    specify a mailbox to load
	    -F	    specify an alternate file to read initialization commands
	    -h	    print help on command line options
	    -H	    specify a draft file from which to read a header and body
	    -i	    specify a file to include in a message composition
	    -m	    specify a default mailbox type
	    -n	    do not read the system Muttrc
	    -p	    recall a postponed message
	    -Q	    query a configuration variable
	    -R	    open mailbox in read-only mode
	    -s	    specify a subject (enclose in quotes if it contains spaces)
	    -v	    show version number and compile-time definitions
	    -x	    simulate the mailx(1) compose mode
	    -y	    show a menu containing the files specified by the mailboxes command
	    -z	    exit immediately if there are no messages in the mailbox
	    -Z	    open the first folder with new message,exit immediately if none


       To read messages in a mailbox

       mutt [ -nz ] [ -F _m_u_t_t_r_c ] [ -m _t_y_p_e ] [ -f _m_a_i_l_b_o_x ]

       To compose a new message

       mutt [ -n ] [ -F _m_u_t_t_r_c ] [ -a _f_i_l_e ] [ -c _a_d_d_r_e_s_s ] [ -i _f_i_l_e_n_a_m_e ] [ -s _s_u_b_-
       _j_e_c_t ] _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s ... ]

       Mutt also supports a ``batch'' mode to send prepared messages.  Simply redirect
       input from the file you wish to send.  For example,

       mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat

       This command will send a message to ``professor@bigschool.edu'' with a subject
       of ``data set for run #2''.  In the body of the message will be the contents of
       the file ``~/run2.dat''.

       _6_._2  _C_o_n_f_i_g_u_r_a_t_i_o_n _C_o_m_m_a_n_d_s

       The following are the commands understood by mutt.

	   _a_c_c_o_u_n_t_-_h_o_o_k (section 4.12  , page 46) _p_a_t_t_e_r_n _c_o_m_m_a_n_d

	   _a_l_i_a_s (section 3.2  , page 15) _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ]









       The Mutt E-Mail Client							    61



	   _u_n_a_l_i_a_s (section 3.2  , page 15) [ * | _k_e_y ... ]

	   _a_l_t_e_r_n_a_t_e_s (section 3.9  , page 22) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

	   _u_n_a_l_t_e_r_n_a_t_e_s (section 3.9  , page 22) [ * | _r_e_g_e_x_p ... ]

	   _a_l_t_e_r_n_a_t_i_v_e___o_r_d_e_r (section 5.5  , page 59) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]

	   _u_n_a_l_t_e_r_n_a_t_i_v_e___o_r_d_e_r (section 5.5  , page 59) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]

	   _a_p_p_e_n_d_-_h_o_o_k (section 4.14.3	, page 49) _r_e_g_e_x_p _c_o_m_m_a_n_d

	   _a_u_t_o___v_i_e_w (section 5.4  , page 58) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]

	   _u_n_a_u_t_o___v_i_e_w (section 5.4  , page 58) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]

	   _b_i_n_d (section 3.3  , page 16) _m_a_p _k_e_y _f_u_n_c_t_i_o_n

	   _c_h_a_r_s_e_t_-_h_o_o_k (section 3.4  , page 18) _a_l_i_a_s _c_h_a_r_s_e_t

	   _c_l_o_s_e_-_h_o_o_k (section 4.14.2  , page 48) _r_e_g_e_x_p _c_o_m_m_a_n_d

	   _c_o_l_o_r (section 3.7  , page 20) _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ]

	   _u_n_c_o_l_o_r (section 3.7  , page 20) _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

	   _e_x_e_c (section 3.22  , page 28) _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ]

	   _f_c_c_-_h_o_o_k (section 3.16  , page 26) _p_a_t_t_e_r_n _m_a_i_l_b_o_x

	   _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.17	, page 26) _p_a_t_t_e_r_n _m_a_i_l_b_o_x

	   _f_o_l_d_e_r_-_h_o_o_k (section 3.5  , page 18) _p_a_t_t_e_r_n _c_o_m_m_a_n_d

	   _h_d_r___o_r_d_e_r (section 3.14  , page 25) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ]

	   _u_n_h_d_r___o_r_d_e_r (section 3.14  , page 25) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ]

	   _i_c_o_n_v_-_h_o_o_k (section 3.4  , page 18) _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t

	   _i_g_n_o_r_e (section 3.8	, page 22) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

	   _u_n_i_g_n_o_r_e (section 3.8  , page 22) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

	   _l_i_s_t_s (section 3.10	, page 23) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

	   _u_n_l_i_s_t_s (section 3.10  , page 23) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

	   _m_a_c_r_o (section 3.6  , page 19) _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ]

	   _m_a_i_l_b_o_x_e_s (section 3.12  , page 24) _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ]

	   _m_b_o_x_-_h_o_o_k (section 3.11  , page 24) _p_a_t_t_e_r_n _m_a_i_l_b_o_x









       The Mutt E-Mail Client							    62



	   _m_e_s_s_a_g_e_-_h_o_o_k (section 3.19  , page 27) _p_a_t_t_e_r_n _c_o_m_m_a_n_d

	   _m_i_m_e___l_o_o_k_u_p (section 5.6  , page 59) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]

	   _u_n_m_i_m_e___l_o_o_k_u_p (section 5.6  , page 59) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ]

	   _m_o_n_o (section 3.7  , page 20) _o_b_j_e_c_t _a_t_t_r_i_b_u_t_e [ _r_e_g_e_x_p ]

	   _u_n_m_o_n_o (section 3.7	, page 20) _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

	   _m_y___h_d_r (section 3.13  , page 24) _s_t_r_i_n_g

	   _u_n_m_y___h_d_r (section 3.13  , page 24) _f_i_e_l_d [ _f_i_e_l_d ... ]

	   _o_p_e_n_-_h_o_o_k (section 4.14.1  , page 48) _r_e_g_e_x_p _c_o_m_m_a_n_d

	   _c_r_y_p_t_-_h_o_o_k (section 3.20  , page 27) _p_a_t_t_e_r_n _k_e_y_-_i_d

	   _p_u_s_h (section 3.21  , page 28) _s_t_r_i_n_g

	   _r_e_s_e_t (section 3.25	, page 30) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ]

	   _s_a_v_e_-_h_o_o_k (section 3.15  , page 25) _r_e_g_e_x_p _f_i_l_e_n_a_m_e

	   _s_c_o_r_e (section 3.23	, page 28) _p_a_t_t_e_r_n _v_a_l_u_e

	   _u_n_s_c_o_r_e (section 3.23  , page 28) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ]

	   _s_e_n_d_-_h_o_o_k (section 3.18  , page 26) _r_e_g_e_x_p _c_o_m_m_a_n_d

	   _r_e_p_l_y_-_h_o_o_k (section , page ) _r_e_g_e_x_p _c_o_m_m_a_n_d

	   _s_e_t (section 3.25  , page 30) [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ]

	   _u_n_s_e_t (section 3.25	, page 30) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ]

	   _s_o_u_r_c_e (section 3.26  , page 31) _f_i_l_e_n_a_m_e

	   _s_p_a_m (section 3.24  , page 28) _p_a_t_t_e_r_n _f_o_r_m_a_t

	   _n_o_s_p_a_m (section 3.24  , page 28) _p_a_t_t_e_r_n

	   _s_u_b_s_c_r_i_b_e (section 3.10  , page 23) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

	   _u_n_s_u_b_s_c_r_i_b_e (section 3.10  , page 23) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ]

	   _t_o_g_g_l_e (section 3.25  , page 30) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ]

	   _u_n_h_o_o_k (section 3.27  , page 31) _h_o_o_k_-_t_y_p_e

       _6_._3  _C_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s

       _6_._3_._1  _a_b_o_r_t___n_o_s_u_b_j_e_c_t









       The Mutt E-Mail Client							    63



       Type: quadoption

       Default: ask-yes

       If set to _y_e_s, when composing messages and no subject is given at the subject
       prompt, composition will be aborted.  If set to _n_o, composing messages with no
       subject given at the subject prompt will never be aborted.

       _6_._3_._2  _a_b_o_r_t___u_n_m_o_d_i_f_i_e_d

       Type: quadoption

       Default: yes

       If set to _y_e_s, composition will automatically abort after editing the message
       body if no changes are made to the file (this check only happens after the
       _f_i_r_s_t edit of the file).  When set to _n_o, composition will never be aborted.

       _6_._3_._3  _a_l_i_a_s___f_i_l_e

       Type: path

       Default: '~/.muttrc'

       The default file in which to save aliases created by the ``_c_r_e_a_t_e_-_a_l_i_a_s (sec-
       tion 2.3.4  , page 7)'' function.

       NNoottee:: Mutt will not automatically source this file; you must explicitly use the
       ``_s_o_u_r_c_e (section 3.26  , page 31)'' command for it to be executed.

       _6_._3_._4  _a_l_i_a_s___f_o_r_m_a_t

       Type: string

       Default: '%4n %2f %t %-10a   %r'

       Specifies the format of the data displayed for the `alias' menu.  The following
       printf(3)-style sequences are available:

	     %a
		   alias name

	     %f
		   flags - currently, a 'd' for an alias marked for deletion

	     %n
		   index number

	     %r
		   address which alias expands to

	     %t
		   character which indicates if the alias is tagged for inclusion









       The Mutt E-Mail Client							    64



       _6_._3_._5  _a_l_l_o_w___8_b_i_t

       Type: boolean

       Default: yes

       Controls whether 8-bit data is converted to 7-bit using either Quoted- Print-
       able or Base64 encoding when sending mail.

       _6_._3_._6  _a_l_l_o_w___a_n_s_i

       Type: boolean

       Default: no

       Controls whether ANSI color codes in messages (and color tags in rich text mes-
       sages) are to be interpreted.  Messages containing these codes are rare, but if
       this option is set, their text will be colored accordingly. Note that this may
       override your color choices, and even present a security problem, since a mes-
       sage could include a line like '[-- PGP output follows ...' and give it the
       same color as your attachment color.

       _6_._3_._7  _a_r_r_o_w___c_u_r_s_o_r

       Type: boolean

       Default: no

       When set, an arrow (``->'') will be used to indicate the current entry in menus
       instead of highlighting the whole line.	On slow network or modem links this
       will make response faster because there is less that has to be redrawn on the
       screen when moving to the next or previous entries in the menu.

       _6_._3_._8  _a_s_c_i_i___c_h_a_r_s

       Type: boolean

       Default: no

       If set, Mutt will use plain ASCII characters when displaying thread and attach-
       ment trees, instead of the default _A_C_S characters.

       _6_._3_._9  _a_s_k_b_c_c

       Type: boolean

       Default: no

       If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before
       editing an outgoing message.

       _6_._3_._1_0  _a_s_k_c_c

       Type: boolean








       The Mutt E-Mail Client							    65



       Default: no

       If set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the
       body of an outgoing message.

       _6_._3_._1_1  _a_t_t_a_c_h___f_o_r_m_a_t

       Type: string

       Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '

       This variable describes the format of the `attachment' menu.  The following
       printf-style sequences are understood:

	     %C
		   charset

	     %c
		   requires charset conversion (n or c)

	     %D
		   deleted flag

	     %d
		   description

	     %e
		   MIME content-transfer-encoding

	     %f
		   filename

	     %I
		   disposition (I=inline, A=attachment)

	     %m
		   major MIME type

	     %M
		   MIME subtype

	     %n
		   attachment number

	     %s
		   size

	     %t
		   tagged flag

	     %T
		   graphic tree characters










       The Mutt E-Mail Client							    66



	     %u
		   unlink (=to delete) flag

	     %>X
		   right justify the rest of the string and pad with character 'X'

	     %|X
		   pad to the end of the line with character 'X'

       _6_._3_._1_2  _a_t_t_a_c_h___s_e_p

       Type: string

       Default: '\n'

       The separator to add between attachments when operating (saving, printing, pip-
       ing, etc) on a list of tagged attachments.

       _6_._3_._1_3  _a_t_t_a_c_h___s_p_l_i_t

       Type: boolean

       Default: yes

       If this variable is unset, when operating (saving, printing, piping, etc) on a
       list of tagged attachments, Mutt will concatenate the attachments and will
       operate on them as a single attachment. The ``_$_a_t_t_a_c_h___s_e_p (section 6.3.12  ,
       page 66)'' separator is added after each attachment. When set, Mutt will oper-
       ate on the attachments one by one.

       _6_._3_._1_4  _a_t_t_r_i_b_u_t_i_o_n

       Type: string

       Default: 'On %d, %n wrote:'

       This is the string that will precede a message which has been included in a
       reply.  For a full listing of defined printf()-like sequences see the section
       on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83)''.

       _6_._3_._1_5  _a_u_t_o_e_d_i_t

       Type: boolean

       Default: no

       When set along with ``_$_e_d_i_t___h_e_a_d_e_r_s (section 6.3.46  , page 73)'', Mutt will
       skip the initial send-menu and allow you to immediately begin editing the body
       of your message.  The send-menu may still be accessed once you have finished
       editing the body of your message.

       Also see ``_$_f_a_s_t___r_e_p_l_y (section 6.3.51  , page 74)''.










       The Mutt E-Mail Client							    67



       _6_._3_._1_6  _a_u_t_o___t_a_g

       Type: boolean

       Default: no

       When set, functions in the _i_n_d_e_x menu which affect a message will be applied to
       all tagged messages (if there are any).	When unset, you must first use the
       tag-prefix function (default: ';') to make the next function apply to all
       tagged messages.

       _6_._3_._1_7  _b_e_e_p

       Type: boolean

       Default: yes

       When this variable is set, mutt will beep when an error occurs.

       _6_._3_._1_8  _b_e_e_p___n_e_w

       Type: boolean

       Default: no

       When this variable is set, mutt will beep whenever it prints a message notify-
       ing you of new mail.  This is independent of the setting of the ``_$_b_e_e_p (sec-
       tion 6.3.17  , page 67)'' variable.

       _6_._3_._1_9  _b_o_u_n_c_e

       Type: quadoption

       Default: ask-yes

       Controls whether you will be asked to confirm bouncing messages.  If set to _y_e_s
       you don't get asked if you want to bounce a message. Setting this variable to
       _n_o is not generally useful, and thus not recommended, because you are unable to
       bounce messages.

       _6_._3_._2_0  _b_o_u_n_c_e___d_e_l_i_v_e_r_e_d

       Type: boolean

       Default: yes

       When this variable is set, mutt will include Delivered-To headers when bouncing
       messages.  Postfix users may wish to unset this variable.

       _6_._3_._2_1  _c_h_a_r_s_e_t

       Type: string

       Default: ''








       The Mutt E-Mail Client							    68



       Character set your terminal uses to display and enter textual data.

       _6_._3_._2_2  _c_h_e_c_k___n_e_w

       Type: boolean

       Default: yes

       NNoottee:: this option only affects _m_a_i_l_d_i_r and _M_H style mailboxes.

       When _s_e_t, Mutt will check for new mail delivered while the mailbox is open.
       Especially with MH mailboxes, this operation can take quite some time since it
       involves scanning the directory and checking each file to see if it has already
       been looked at.	If _c_h_e_c_k___n_e_w is _u_n_s_e_t, no check for new mail is performed
       while the mailbox is open.

       _6_._3_._2_3  _c_o_l_o_r___a_f_t_e_r___e_o_l

       Type: boolean

       Default: yes

       When _s_e_t, Mutt will color a line after the last character extending to the end
       of the window.

       _6_._3_._2_4  _c_o_l_l_a_p_s_e___u_n_r_e_a_d

       Type: boolean

       Default: yes

       When _u_n_s_e_t, Mutt will not collapse a thread if it contains any unread messages.

       _6_._3_._2_5  _u_n_c_o_l_l_a_p_s_e___j_u_m_p

       Type: boolean

       Default: no

       When _s_e_t, Mutt will jump to the next unread message, if any, when the current
       thread is _u_ncollapsed.

       _6_._3_._2_6  _c_o_m_p_o_s_e___f_o_r_m_a_t

       Type: string

       Default: '-- Mutt: Compose  [Approx. msg size: %l   Atts: %a]%>-'

       Controls the format of the status line displayed in the _C_o_m_p_o_s_e menu.  This
       string is similar to ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.3.260  , page 121)'', but has
       its own set of printf()-like sequences:

	     %a
		   total number of attachments








       The Mutt E-Mail Client							    69



	     %h
		   local hostname

	     %l
		   approximate size (in bytes) of the current message

	     %v
		   Mutt version string

       See the text describing the ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.3.260  , page 121)''
       option for more information on how to set ``_$_c_o_m_p_o_s_e___f_o_r_m_a_t (section 6.3.26  ,
       page 68)''.

       _6_._3_._2_7  _c_o_n_f_i_g___c_h_a_r_s_e_t

       Type: string

       Default: ''

       When defined, Mutt will recode commands in rc files from this encoding.

       _6_._3_._2_8  _c_o_n_f_i_r_m_a_p_p_e_n_d

       Type: boolean

       Default: yes

       When set, Mutt will prompt for confirmation when appending messages to an
       existing mailbox.

       _6_._3_._2_9  _c_o_n_f_i_r_m_c_r_e_a_t_e

       Type: boolean

       Default: yes

       When set, Mutt will prompt for confirmation when saving messages to a mailbox
       which does not yet exist before creating it.

       _6_._3_._3_0  _c_o_n_n_e_c_t___t_i_m_e_o_u_t

       Type: number

       Default: 30

       Causes Mutt to timeout a network connection (for IMAP or POP) after this many
       seconds if the connection is not able to be established.  A negative value
       causes Mutt to wait indefinitely for the connection to succeed.

       _6_._3_._3_1  _c_o_n_t_e_n_t___t_y_p_e

       Type: string

       Default: 'text/plain'








       The Mutt E-Mail Client							    70



       Sets the default Content-Type for the body of newly composed messages.

       _6_._3_._3_2  _c_o_p_y

       Type: quadoption

       Default: yes

       This variable controls whether or not copies of your outgoing messages will be
       saved for later references.  Also see ``_$_r_e_c_o_r_d (section 6.3.225  , page
       113)'', ``_$_s_a_v_e___n_a_m_e (section 6.3.236  , page 115)'', ``_$_f_o_r_c_e___n_a_m_e (section
       6.3.57  , page 76)'' and ``_f_c_c_-_h_o_o_k (section 3.16  , page 26)''.

       _6_._3_._3_3  _c_r_y_p_t___u_s_e___g_p_g_m_e

       Type: boolean

       Default: no

       This variable controls the use the GPGME enabled crypto backends.  If it is set
       and Mutt was build with gpgme support, the gpgme code for S/MIME and PGP will
       be used instead of the classic code.  Note, that you need to use this option in
       .muttrc as it won't have any effect when used interactively.

       _6_._3_._3_4  _c_r_y_p_t___a_u_t_o_p_g_p

       Type: boolean

       Default: yes

       This variable controls whether or not mutt may automatically enable PGP encryp-
       tion/signing for messages.  See also ``_$_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t (section 6.3.129  ,
       page 92)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 6.3.131  , page 93)'',
       ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 6.3.128  , page 92)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section
       6.3.132	, page 93)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.3.137  , page 94)''.

       _6_._3_._3_5  _c_r_y_p_t___a_u_t_o_s_m_i_m_e

       Type: boolean

       Default: yes

       This variable controls whether or not mutt may automatically enable S/MIME
       encryption/signing for messages. See also ``_$_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t (section
       6.3.129	, page 92)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 6.3.131  , page 93)'',
       ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 6.3.128  , page 92)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section
       6.3.132	, page 93)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.3.137  , page 94)''.

       _6_._3_._3_6  _d_a_t_e___f_o_r_m_a_t

       Type: string

       Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'









       The Mutt E-Mail Client							    71



       This variable controls the format of the date printed by the ``%d'' sequence in
       ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93	, page 83)''.  This is passed to the _s_t_r_f_t_i_m_e
       call to process the date. See the man page for _s_t_r_f_t_i_m_e_(_3_) for the proper syn-
       tax.

       Unless the first character in the string is a bang (``!''), the month and week
       day names are expanded according to the locale specified in the variable
       ``_$_l_o_c_a_l_e (section 6.3.96  , page 86)''. If the first character in the string
       is a bang, the bang is discarded, and the month and week day names in the rest
       of the string are expanded in the _C locale (that is in US English).

       _6_._3_._3_7  _d_e_f_a_u_l_t___h_o_o_k

       Type: string

       Default: '~f %s !~P | (~P ~C %s)'

       This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
       will be interpreted if they are specified with only a simple regexp, instead of
       a matching pattern.  The hooks are expanded when they are declared, so a hook
       will be interpreted according to the value of this variable at the time the
       hook is declared.  The default value matches if the message is either from a
       user matching the regular expression given, or if it is from you (if the from
       address matches ``alternates'') and is to or cc'ed to a user matching the given
       regular expression.

       _6_._3_._3_8  _d_e_l_e_t_e

       Type: quadoption

       Default: ask-yes

       Controls whether or not messages are really deleted when closing or synchroniz-
       ing a mailbox.  If set to _y_e_s, messages marked for deleting will automatically
       be purged without prompting.  If set to _n_o, messages marked for deletion will
       be kept in the mailbox.

       _6_._3_._3_9  _d_e_l_e_t_e___u_n_t_a_g

       Type: boolean

       Default: yes

       If this option is _s_e_t, mutt will untag messages when marking them for deletion.
       This applies when you either explicitly delete a message, or when you save it
       to another folder.

       _6_._3_._4_0  _d_i_g_e_s_t___c_o_l_l_a_p_s_e

       Type: boolean

       Default: yes

       If this option is _s_e_t, mutt's received-attachments menu will not show the








       The Mutt E-Mail Client							    72



       subparts of individual messages in a multipart/digest.  To see these subparts,
       press 'v' on that menu.

       _6_._3_._4_1  _d_i_s_p_l_a_y___f_i_l_t_e_r

       Type: path

       Default: ''

       When set, specifies a command used to filter messages.  When a message is
       viewed it is passed as standard input to _$_d_i_s_p_l_a_y___f_i_l_t_e_r (section 6.3.41  ,
       page 72), and the filtered message is read from the standard output.

       _6_._3_._4_2  _d_o_t_l_o_c_k___p_r_o_g_r_a_m

       Type: path

       Default: '/usr/local/bin/mutt_dotlock'

       Contains the path of the mutt_dotlock (8) binary to be used by mutt.

       _6_._3_._4_3  _d_s_n___n_o_t_i_f_y

       Type: string

       Default: ''

       NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or
       greater.

       This variable sets the request for when notification is returned.  The string
       consists of a comma separated list (no spaces!) of one or more of the follow-
       ing: _n_e_v_e_r, to never request notification, _f_a_i_l_u_r_e, to request notification on
       transmission failure, _d_e_l_a_y, to be notified of message delays, _s_u_c_c_e_s_s, to be
       notified of successful transmission.

       Example: set dsn_notify='failure,delay'

       _6_._3_._4_4  _d_s_n___r_e_t_u_r_n

       Type: string

       Default: ''

       NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or
       greater.

       This variable controls how much of your message is returned in DSN messages.
       It may be set to either _h_d_r_s to return just the message header, or _f_u_l_l to
       return the full message.

       Example: set dsn_return=hdrs










       The Mutt E-Mail Client							    73



       _6_._3_._4_5  _d_u_p_l_i_c_a_t_e___t_h_r_e_a_d_s

       Type: boolean

       Default: yes

       This variable controls whether mutt, when sorting by threads, threads messages
       with the same message-id together.  If it is set, it will indicate that it
       thinks they are duplicates of each other with an equals sign in the thread dia-
       gram.

       _6_._3_._4_6  _e_d_i_t___h_e_a_d_e_r_s

       Type: boolean

       Default: no

       This option allows you to edit the header of your outgoing messages along with
       the body of your message.

       _6_._3_._4_7  _e_d_i_t_o_r

       Type: path

       Default: ''

       This variable specifies which editor is used by mutt.  It defaults to the value
       of the VISUAL, or EDITOR, environment variable, or to the string 'vi' if nei-
       ther of those are set.

       _6_._3_._4_8  _e_n_c_o_d_e___f_r_o_m

       Type: boolean

       Default: no

       When _s_e_t, mutt will quoted-printable encode messages when they contain the
       string 'From ' in the beginning of a line.  Useful to avoid the tampering cer-
       tain mail delivery and transport agents tend to do with messages.

       _6_._3_._4_9  _e_n_v_e_l_o_p_e___f_r_o_m

       Type: boolean

       Default: no

       When _s_e_t, mutt will try to derive the message's _e_n_v_e_l_o_p_e sender from the
       'From:' header.	Note that this information is passed to sendmail command using
       the '-f' command line switch, so don't set this option if you are using that
       switch in _$_s_e_n_d_m_a_i_l (section 6.3.242  , page 117) yourself, or if the sendmail
       on your machine doesn't support that command line switch.

       _6_._3_._5_0  _e_s_c_a_p_e









       The Mutt E-Mail Client							    74



       Type: string

       Default: '~'

       Escape character to use for functions in the builtin editor.

       _6_._3_._5_1  _f_a_s_t___r_e_p_l_y

       Type: boolean

       Default: no

       When set, the initial prompt for recipients and subject are skipped when reply-
       ing to messages, and the initial prompt for subject is skipped when forwarding
       messages.

       NNoottee:: this variable has no effect when the ``_$_a_u_t_o_e_d_i_t (section 6.3.15  , page
       66)'' variable is set.

       _6_._3_._5_2  _f_c_c___a_t_t_a_c_h

       Type: boolean

       Default: yes

       This variable controls whether or not attachments on outgoing messages are
       saved along with the main body of your message.

       _6_._3_._5_3  _f_c_c___c_l_e_a_r

       Type: boolean

       Default: no

       When this variable is set, FCCs will be stored unencrypted and unsigned, even
       when the actual message is encrypted and/or signed.  (PGP only)

       _6_._3_._5_4  _f_o_l_d_e_r

       Type: path

       Default: '~/Mail'

       Specifies the default location of your mailboxes.  A `+' or `=' at the begin-
       ning of a pathname will be expanded to the value of this variable.  Note that
       if you change this variable from the default value you need to make sure that
       the assignment occurs _b_e_f_o_r_e you use `+' or `=' for any other variables since
       expansion takes place during the `set' command.

       _6_._3_._5_5  _f_o_l_d_e_r___f_o_r_m_a_t

       Type: string

       Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'








       The Mutt E-Mail Client							    75



       This variable allows you to customize the file browser display to your personal
       taste.  This string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page
       83)'', but has its own set of printf()-like sequences:

	     %C
		   current file number

	     %d
		   date/time folder was last modified

	     %f
		   filename

	     %F
		   file permissions

	     %g
		   group name (or numeric gid, if missing)

	     %l
		   number of hard links

	     %N
		   N if folder has new mail, blank otherwise

	     %s
		   size in bytes

	     %t
		   * if the file is tagged, blank otherwise

	     %u
		   owner name (or numeric uid, if missing)

	     %>X
		   right justify the rest of the string and pad with character 'X'

	     %|X
		   pad to the end of the line with character 'X'

       _6_._3_._5_6  _f_o_l_l_o_w_u_p___t_o

       Type: boolean

       Default: yes

       Controls whether or not the _M_a_i_l_-_F_o_l_l_o_w_u_p_-_T_o header field is generated when
       sending mail.  When _s_e_t, Mutt will generate this field when you are replying to
       a known mailing list, specified with the ``subscribe'' or ``_l_i_s_t_s (section
       3.10  , page 23)'' commands.

       This field has two purposes.  First, preventing you from receiving duplicate
       copies of replies to messages which you send to mailing lists, and second,
       ensuring that you do get a reply separately for any messages sent to known








       The Mutt E-Mail Client							    76



       lists to which you are not subscribed.  The header will contain only the list's
       address for subscribed lists, and both the list address and your own email
       address for unsubscribed lists.	Without this header, a group reply to your
       message sent to a subscribed list will be sent to both the list and your
       address, resulting in two copies of the same email for you.

       _6_._3_._5_7  _f_o_r_c_e___n_a_m_e

       Type: boolean

       Default: no

       This variable is similar to ``_$_s_a_v_e___n_a_m_e (section 6.3.236  , page 115)'',
       except that Mutt will store a copy of your outgoing message by the username of
       the address you are sending to even if that mailbox does not exist.

       Also see the ``_$_r_e_c_o_r_d (section 6.3.225	, page 113)'' variable.

       _6_._3_._5_8  _f_o_r_w_a_r_d___d_e_c_o_d_e

       Type: boolean

       Default: yes

       Controls the decoding of complex MIME messages into text/plain when forwarding
       a message.  The message header is also RFC2047 decoded.	This variable is only
       used, if ``_$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  , page 89)'' is _u_n_s_e_t, otherwise
       ``_$_m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.3.116	, page 90)'' is used instead.

       _6_._3_._5_9  _f_o_r_w_a_r_d___e_d_i_t

       Type: quadoption

       Default: yes

       This quadoption controls whether or not the user is automatically placed in the
       editor when forwarding messages.  For those who always want to forward with no
       modification, use a setting of ``no''.

       _6_._3_._6_0  _f_o_r_w_a_r_d___f_o_r_m_a_t

       Type: string

       Default: '[%a: %s]'

       This variable controls the default subject when forwarding a message.  It uses
       the same format sequences as the ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83)''
       variable.

       _6_._3_._6_1  _f_o_r_w_a_r_d___q_u_o_t_e

       Type: boolean

       Default: no








       The Mutt E-Mail Client							    77



       When _s_e_t forwarded messages included in the main body of the message (when
       ``_$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  , page 89)'' is _u_n_s_e_t) will be quoted using
       ``_$_i_n_d_e_n_t___s_t_r_i_n_g (section 6.3.92  , page 83)''.

       _6_._3_._6_2  _f_r_o_m

       Type: e-mail address

       Default: ''

       When set, this variable contains a default from address.  It can be overridden
       using my_hdr (including from send-hooks) and ``_$_r_e_v_e_r_s_e___n_a_m_e (section
       6.3.231	, page 114)''.	This variable is ignored if ``_$_u_s_e___f_r_o_m (section
       6.3.274	, page 126)'' is unset.

       Defaults to the contents of the environment variable EMAIL.

       _6_._3_._6_3  _g_e_c_o_s___m_a_s_k

       Type: regular expression

       Default: '^[^,]*'

       A regular expression used by mutt to parse the GECOS field of a password entry
       when expanding the alias.  By default the regular expression is set to '^[^,]*'
       which will return the string up to the first ',' encountered.  If the GECOS
       field contains a string like 'lastname, firstname' then you should set the
       gecos_mask='.*'.

       This can be useful if you see the following behavior: you address a e-mail to
       user ID stevef whose full name is Steve Franklin.  If mutt expands stevef to
       'Franklin' stevef@foo.bar then you should set the gecos_mask to a regular
       expression that will match the whole name so mutt will expand 'Franklin' to
       'Franklin, Steve'.

       _6_._3_._6_4  _h_d_r_s

       Type: boolean

       Default: yes

       When unset, the header fields normally added by the ``_m_y___h_d_r (section 3.13  ,
       page 24)'' command are not created.  This variable _m_u_s_t be unset before compos-
       ing a new message or replying in order to take effect.  If set, the user
       defined header fields are added to every new message.

       _6_._3_._6_5  _h_e_a_d_e_r

       Type: boolean

       Default: no

       When set, this variable causes Mutt to include the header of the message you
       are replying to into the edit buffer.  The ``_$_w_e_e_d (section 6.3.279  , page








       The Mutt E-Mail Client							    78



       127)'' setting applies.

       _6_._3_._6_6  _h_e_l_p

       Type: boolean

       Default: yes

       When set, help lines describing the bindings for the major functions provided
       by each menu are displayed on the first line of the screen.

       NNoottee:: The binding will not be displayed correctly if the function is bound to a
       sequence rather than a single keystroke.  Also, the help line may not be
       updated if a binding is changed while Mutt is running.  Since this variable is
       primarily aimed at new users, neither of these should present a major problem.

       _6_._3_._6_7  _h_i_d_d_e_n___h_o_s_t

       Type: boolean

       Default: no

       When set, mutt will skip the host name part of ``_$_h_o_s_t_n_a_m_e (section 6.3.75  ,
       page 79)'' variable when adding the domain part to addresses.  This variable
       does not affect the generation of Message-IDs, and it will not lead to the cut-
       off of first-level domains.

       _6_._3_._6_8  _h_i_d_e___l_i_m_i_t_e_d

       Type: boolean

       Default: no

       When set, mutt will not show the presence of messages that are hidden by limit-
       ing, in the thread tree.

       _6_._3_._6_9  _h_i_d_e___m_i_s_s_i_n_g

       Type: boolean

       Default: yes

       When set, mutt will not show the presence of missing messages in the thread
       tree.

       _6_._3_._7_0  _h_i_d_e___t_h_r_e_a_d___s_u_b_j_e_c_t

       Type: boolean

       Default: yes

       When set, mutt will not show the subject of messages in the thread tree that
       have the same subject as their parent or closest previously displayed sibling.









       The Mutt E-Mail Client							    79



       _6_._3_._7_1  _h_i_d_e___t_o_p___l_i_m_i_t_e_d

       Type: boolean

       Default: no

       When set, mutt will not show the presence of messages that are hidden by limit-
       ing, at the top of threads in the thread tree.  Note that when _$_h_i_d_e___m_i_s_s_i_n_g
       (section 6.3.69	, page 78) is set, this option will have no effect.

       _6_._3_._7_2  _h_i_d_e___t_o_p___m_i_s_s_i_n_g

       Type: boolean

       Default: yes

       When set, mutt will not show the presence of missing messages at the top of
       threads in the thread tree.  Note that when _$_h_i_d_e___l_i_m_i_t_e_d (section 6.3.68  ,
       page 78) is set, this option will have no effect.

       _6_._3_._7_3  _h_i_s_t_o_r_y

       Type: number

       Default: 10

       This variable controls the size (in number of strings remembered) of the string
       history buffer. The buffer is cleared each time the variable is set.

       _6_._3_._7_4  _h_o_n_o_r___f_o_l_l_o_w_u_p___t_o

       Type: quadoption

       Default: yes

       This variable controls whether or not a Mail-Followup-To header is honored when
       group-replying to a message.

       _6_._3_._7_5  _h_o_s_t_n_a_m_e

       Type: string

       Default: ''

       Specifies the hostname to use after the ``@'' in local e-mail addresses.  This
       overrides the compile time definition obtained from /etc/resolv.conf.

       _6_._3_._7_6  _i_g_n_o_r_e___l_i_s_t___r_e_p_l_y___t_o

       Type: boolean

       Default: no

       Affects the behaviour of the _r_e_p_l_y function when replying to messages from








       The Mutt E-Mail Client							    80



       mailing lists.  When set, if the ``Reply-To:'' field is set to the same value
       as the ``To:'' field, Mutt assumes that the ``Reply-To:'' field was set by the
       mailing list to automate responses to the list, and will ignore this field.  To
       direct a response to the mailing list when this option is set, use the _l_i_s_t_-
       _r_e_p_l_y function; _g_r_o_u_p_-_r_e_p_l_y will reply to both the sender and the list.

       _6_._3_._7_7  _i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s

       Type: string

       Default: ''

       This is a colon-delimited list of authentication methods mutt may attempt to
       use to log in to an IMAP server, in the order mutt should try them.  Authenti-
       cation methods are either 'login' or the right side of an IMAP 'AUTH=xxx' capa-
       bility string, eg 'digest-md5', 'gssapi' or 'cram-md5'. This parameter is case-
       insensitive. If this parameter is unset (the default) mutt will try all avail-
       able methods, in order from most-secure to least-secure.

       Example: set imap_authenticators='gssapi:cram-md5:login'

       NNoottee:: Mutt will only fall back to other authentication methods if the previous
       methods are unavailable. If a method is available but authentication fails,
       mutt will not connect to the IMAP server.

       _6_._3_._7_8  _i_m_a_p___d_e_l_i_m___c_h_a_r_s

       Type: string

       Default: '/.'

       This contains the list of characters which you would like to treat as folder
       separators for displaying IMAP paths. In particular it helps in using the '='
       shortcut for your _f_o_l_d_e_r variable.

       _6_._3_._7_9  _i_m_a_p___f_o_r_c_e___s_s_l

       Type: boolean

       Default: no

       If this variable is set, Mutt will always use SSL when connecting to IMAP
       servers.

       _6_._3_._8_0  _i_m_a_p___h_e_a_d_e_r_s

       Type: string

       Default: ''

       Mutt requests these header fields in addition to the default headers ('DATE
       FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
       REPLY-TO REPLY-TO LINES X-LABEL') from IMAP servers before displaying the index
       menu. You may want to add more headers for spam detection. NNoottee:: This is a








       The Mutt E-Mail Client							    81



       space separated list.

       _6_._3_._8_1  _i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e

       Type: string

       Default: ''

       You normally want to see your personal folders alongside your INBOX in the IMAP
       browser. If you see something else, you may set this variable to the IMAP path
       to your folders.

       _6_._3_._8_2  _i_m_a_p___k_e_e_p_a_l_i_v_e

       Type: number

       Default: 900

       This variable specifies the maximum amount of time in seconds that mutt will
       wait before polling open IMAP connections, to prevent the server from closing
       them before mutt has finished with them. The default is well within the RFC-
       specified minimum amount of time (30 minutes) before a server is allowed to do
       this, but in practice the RFC does get violated every now and then. Reduce this
       number if you find yourself getting disconnected from your IMAP server due to
       inactivity.

       _6_._3_._8_3  _i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d

       Type: boolean

       Default: no

       This variable configures whether IMAP folder browsing will look for only sub-
       scribed folders or all folders.	This can be toggled in the IMAP browser with
       the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d function.

       _6_._3_._8_4  _i_m_a_p___p_a_s_s

       Type: string

       Default: ''

       Specifies the password for your IMAP account.  If unset, Mutt will prompt you
       for your password when you invoke the fetch-mail function.  WWaarrnniinngg: you should
       only use this option when you are on a fairly secure machine, because the supe-
       ruser can read your muttrc even if you are the only one who can read the file.

       _6_._3_._8_5  _i_m_a_p___p_a_s_s_i_v_e

       Type: boolean

       Default: yes

       When set, mutt will not open new IMAP connections to check for new mail.  Mutt








       The Mutt E-Mail Client							    82



       will only check for new mail over existing IMAP connections.  This is useful if
       you don't want to be prompted to user/password pairs on mutt invocation, or if
       opening the connection is slow.

       _6_._3_._8_6  _i_m_a_p___p_e_e_k

       Type: boolean

       Default: yes

       If set, mutt will avoid implicitly marking your mail as read whenever you fetch
       a message from the server. This is generally a good thing, but can make closing
       an IMAP folder somewhat slower. This option exists to appease speed freaks.

       _6_._3_._8_7  _i_m_a_p___s_e_r_v_e_r_n_o_i_s_e

       Type: boolean

       Default: yes

       When set, mutt will display warning messages from the IMAP server as error mes-
       sages. Since these messages are often harmless, or generated due to configura-
       tion problems on the server which are out of the users' hands, you may wish to
       suppress them at some point.

       _6_._3_._8_8  _i_m_a_p___u_s_e_r

       Type: string

       Default: ''

       Your login name on the IMAP server.

       This variable defaults to your user name on the local machine.

       _6_._3_._8_9  _i_m_p_l_i_c_i_t___a_u_t_o_v_i_e_w

       Type: boolean

       Default: no

       If set to ``yes'', mutt will look for a mailcap entry with the copiousoutput
       flag set for _e_v_e_r_y MIME attachment it doesn't have an internal viewer defined
       for.  If such an entry is found, mutt will use the viewer defined in that entry
       to convert the body part to text form.

       _6_._3_._9_0  _i_n_c_l_u_d_e

       Type: quadoption

       Default: ask-yes

       Controls whether or not a copy of the message(s) you are replying to is
       included in your reply.








       The Mutt E-Mail Client							    83



       _6_._3_._9_1  _i_n_c_l_u_d_e___o_n_l_y_f_i_r_s_t

       Type: boolean

       Default: no

       Controls whether or not Mutt includes only the first attachment of the message
       you are replying.

       _6_._3_._9_2  _i_n_d_e_n_t___s_t_r_i_n_g

       Type: string

       Default: '> '

       Specifies the string to prepend to each line of text quoted in a message to
       which you are replying.	You are strongly encouraged not to change this value,
       as it tends to agitate the more fanatical netizens.

       _6_._3_._9_3  _i_n_d_e_x___f_o_r_m_a_t

       Type: string

       Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'

       This variable allows you to customize the message index display to your per-
       sonal taste.

       ``Format strings'' are similar to the strings used in the ``C'' function printf
       to format output (see the man page for more detail).  The following sequences
       are defined in Mutt:

	     %a
		   address of the author

	     %A
		   reply-to address (if present; otherwise: address of author)

	     %b
		   filename of the original message folder (think mailBox)

	     %B
		   the list to which the letter was sent, or else the folder name
		   (%b).

	     %c
		   number of characters (bytes) in the message

	     %C
		   current message number

	     %d
		   date and time of the message in the format specified by ``date_for-
		   mat'' converted to sender's time zone








       The Mutt E-Mail Client							    84



	     %D
		   date and time of the message in the format specified by ``date_for-
		   mat'' converted to the local time zone

	     %e
		   current message number in thread

	     %E
		   number of messages in current thread

	     %f
		   entire From: line (address + real name)

	     %F
		   author name, or recipient name if the message is from you

	     %H
		   spam attribute(s) of this message

	     %i
		   message-id of the current message

	     %l
		   number of lines in the message (does not work with maildir, mh, and
		   possibly IMAP folders)

	     %L
		   If an address in the To or CC header field matches an address
		   defined by the users ``subscribe'' command, this displays 'To
		   <list-name>', otherwise the same as %F.

	     %m
		   total number of message in the mailbox

	     %M
		   number of hidden messages if the thread is collapsed.

	     %N
		   message score

	     %n
		   author's real name (or address if missing)

	     %O
		   (_O_riginal save folder)  Where mutt would formerly have stashed
		   the message: list name or recipient name if no list

	     %s
		   subject of the message

	     %S
		   status of the message (N/D/d/!/r/*)










       The Mutt E-Mail Client							    85



	     %t
		   `to:' field (recipients)

	     %T
		   the appropriate character from the _$_t_o___c_h_a_r_s (section 6.3.270  ,
		   page 125) string

	     %u
		   user (login) name of the author

	     %v
		   first name of the author, or the recipient if the message is from
		   you

	     %y
		   `x-label:' field, if present

	     %Y
		   `x-label' field, if present, and (1) not at part of a thread tree,
		   (2) at the top of a thread, or (3) `x-label' is different from pre-
		   ceding message's `x-label'.

	     %Z
		   message status flags

	     %{fmt}
		   the date and time of the message is converted to sender's time
		   zone, and ``fmt'' is expanded by the library function ``strftime'';
		   a leading bang disables locales

	     %[fmt]
		   the date and time of the message is converted to the local time
		   zone, and ``fmt'' is expanded by the library function ``strftime'';
		   a leading bang disables locales

	     %(fmt)
		   the local date and time when the message was received.  ``fmt'' is
		   expanded by the library function ``strftime''; a leading bang dis-
		   ables locales

	     %<fmt>
		   the current local time. ``fmt'' is expanded by the library function
		   ``strftime''; a leading bang disables locales.

	     %>X
		   right justify the rest of the string and pad with character 'X'

	     %|X
		   pad to the end of the line with character 'X'

       See also: ``_$_t_o___c_h_a_r_s (section 6.3.270  , page 125)''.

       _6_._3_._9_4  _i_s_p_e_l_l









       The Mutt E-Mail Client							    86



       Type: path

       Default: 'ispell'

       How to invoke ispell (GNU's spell-checking software).

       _6_._3_._9_5  _k_e_e_p___f_l_a_g_g_e_d

       Type: boolean

       Default: no

       If set, read messages marked as flagged will not be moved from your spool mail-
       box to your ``_$_m_b_o_x (section 6.3.104  , page 87)'' mailbox, or as a result of a
       ``_m_b_o_x_-_h_o_o_k (section 3.11  , page 24)'' command.

       _6_._3_._9_6  _l_o_c_a_l_e

       Type: string

       Default: 'C'

       The locale used by _s_t_r_f_t_i_m_e_(_3_) to format dates. Legal values are the strings
       your system accepts for the locale variable _L_C___T_I_M_E.

       _6_._3_._9_7  _m_a_i_l___c_h_e_c_k

       Type: number

       Default: 5

       This variable configures how often (in seconds) mutt should look for new mail.

       _6_._3_._9_8  _m_a_i_l_c_a_p___p_a_t_h

       Type: string

       Default: ''

       This variable specifies which files to consult when attempting to display MIME
       bodies not directly supported by Mutt.

       _6_._3_._9_9  _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e

       Type: boolean

       Default: yes

       If set, mutt will restrict possible characters in mailcap % expandos to a well-
       defined set of safe characters.	This is the safe setting, but we are not sure
       it doesn't break some more advanced MIME stuff.

       DDOONN''TT CCHHAANNGGEE TTHHIISS SSEETTTTIINNGG UUNNLLEESSSS YYOOUU AARREE RREEAALLLLYY SSUURREE WWHHAATT YYOOUU AARREE DDOOIINNGG!!









       The Mutt E-Mail Client							    87



       _6_._3_._1_0_0	_m_a_i_l_d_i_r___t_r_a_s_h

       Type: boolean

       Default: no

       If set, messages marked as deleted will be saved with the maildir (T)rashed
       flag instead of unlinked.  NNOOTTEE:: this only applies to maildir-style mailboxes.
       Setting it will have no effect on other mailbox types.

       _6_._3_._1_0_1	_m_a_r_k___o_l_d

       Type: boolean

       Default: yes

       Controls whether or not mutt marks _n_e_w uunnrreeaadd messages as _o_l_d if you exit a
       mailbox without reading them.  With this option set, the next time you start
       mutt, the messages will show up with an 'O' next to them in the index menu,
       indicating that they are old.

       _6_._3_._1_0_2	_m_a_r_k_e_r_s

       Type: boolean

       Default: yes

       Controls the display of wrapped lines in the internal pager. If set, a ``+''
       marker is displayed at the beginning of wrapped lines. Also see the
       ``_$_s_m_a_r_t___w_r_a_p (section 6.3.249  , page 118)'' variable.

       _6_._3_._1_0_3	_m_a_s_k

       Type: regular expression

       Default: '!^\.[^.]'

       A regular expression used in the file browser, optionally preceded by the _n_o_t
       operator ``!''.	Only files whose names match this mask will be shown. The
       match is always case-sensitive.

       _6_._3_._1_0_4	_m_b_o_x

       Type: path

       Default: '~/mbox'

       This specifies the folder into which read mail in your ``_$_s_p_o_o_l_f_i_l_e (section
       6.3.258	, page 121)'' folder will be appended.

       _6_._3_._1_0_5	_m_b_o_x___t_y_p_e

       Type: folder magic









       The Mutt E-Mail Client							    88



       Default: mbox

       The default mailbox type used when creating new folders. May be any of mbox,
       MMDF, MH and Maildir.

       _6_._3_._1_0_6	_m_e_t_o_o

       Type: boolean

       Default: no

       If unset, Mutt will remove your address (see the ``alternates'' command) from
       the list of recipients when replying to a message.

       _6_._3_._1_0_7	_m_e_n_u___c_o_n_t_e_x_t

       Type: number

       Default: 0

       This variable controls the number of lines of context that are given when
       scrolling through menus. (Similar to ``_$_p_a_g_e_r___c_o_n_t_e_x_t (section 6.3.124  , page
       91)''.)

       _6_._3_._1_0_8	_m_e_n_u___m_o_v_e___o_f_f

       Type: boolean

       Default: no

       When _u_n_s_e_t, the bottom entry of menus will never scroll up past the bottom of
       the screen, unless there are less entries than lines.  When _s_e_t, the bottom
       entry may move off the bottom.

       _6_._3_._1_0_9	_m_e_n_u___s_c_r_o_l_l

       Type: boolean

       Default: no

       When _s_e_t, menus will be scrolled up or down one line when you attempt to move
       across a screen boundary.  If _u_n_s_e_t, the screen is cleared and the next or pre-
       vious page of the menu is displayed (useful for slow links to avoid many
       redraws).

       _6_._3_._1_1_0	_m_e_t_a___k_e_y

       Type: boolean

       Default: no

       If set, forces Mutt to interpret keystrokes with the high bit (bit 8) set as if
       the user had pressed the ESC key and whatever key remains after having the high
       bit removed.  For example, if the key pressed has an ASCII value of 0xf4, then








       The Mutt E-Mail Client							    89



       this is treated as if the user had pressed ESC then ``x''.  This is because the
       result of removing the high bit from ``0xf4'' is ``0x74'', which is the ASCII
       character ``x''.

       _6_._3_._1_1_1	_m_h___p_u_r_g_e

       Type: boolean

       Default: no

       When unset, mutt will mimic mh's behaviour and rename deleted messages to _,_<_o_l_d
       _f_i_l_e _n_a_m_e_> in mh folders instead of really deleting them.  If the variable is
       set, the message files will simply be deleted.

       _6_._3_._1_1_2	_m_h___s_e_q___f_l_a_g_g_e_d

       Type: string

       Default: 'flagged'

       The name of the MH sequence used for flagged messages.

       _6_._3_._1_1_3	_m_h___s_e_q___r_e_p_l_i_e_d

       Type: string

       Default: 'replied'

       The name of the MH sequence used to tag replied messages.

       _6_._3_._1_1_4	_m_h___s_e_q___u_n_s_e_e_n

       Type: string

       Default: 'unseen'

       The name of the MH sequence used for unseen messages.

       _6_._3_._1_1_5	_m_i_m_e___f_o_r_w_a_r_d

       Type: quadoption

       Default: no

       When set, the message you are forwarding will be attached as a separate MIME
       part instead of included in the main body of the message.  This is useful for
       forwarding MIME messages so the receiver can properly view the message as it
       was delivered to you. If you like to switch between MIME and not MIME from mail
       to mail, set this variable to ask-no or ask-yes.

       Also see ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.3.58  , page 76)'' and ``_$_m_i_m_e___f_o_r_-
       _w_a_r_d___d_e_c_o_d_e (section 6.3.116  , page 90)''.










       The Mutt E-Mail Client							    90



       _6_._3_._1_1_6	_m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e

       Type: boolean

       Default: no

       Controls the decoding of complex MIME messages into text/plain when forwarding
       a message while ``_$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  , page 89)'' is _s_e_t. Other-
       wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.3.58  , page 76)'' is used instead.

       _6_._3_._1_1_7	_m_i_m_e___f_o_r_w_a_r_d___r_e_s_t

       Type: quadoption

       Default: yes

       When forwarding multiple attachments of a MIME message from the recvattach
       menu, attachments which cannot be decoded in a reasonable manner will be
       attached to the newly composed message if this option is set.

       _6_._3_._1_1_8	_m_i_x___e_n_t_r_y___f_o_r_m_a_t

       Type: string

       Default: '%4n %c %-16s %a'

       This variable describes the format of a remailer line on the mixmaster chain
       selection screen.  The following printf-like sequences are supported:

	     %n
		   The running number on the menu.

	     %c
		   Remailer capabilities.

	     %s
		   The remailer's short name.

	     %a
		   The remailer's e-mail address.

       _6_._3_._1_1_9	_m_i_x_m_a_s_t_e_r

       Type: path

       Default: 'mixmaster'

       This variable contains the path to the Mixmaster binary on your system.	It is
       used with various sets of parameters to gather the list of known remailers, and
       to finally send a message through the mixmaster chain.

       _6_._3_._1_2_0	_m_o_v_e

       Type: quadoption








       The Mutt E-Mail Client							    91



       Default: ask-no

       Controls whether or not Mutt will move read messages from your spool mailbox to
       your ``_$_m_b_o_x (section 6.3.104  , page 87)'' mailbox, or as a result of a
       ``_m_b_o_x_-_h_o_o_k (section 3.11  , page 24)'' command.

       _6_._3_._1_2_1	_m_e_s_s_a_g_e___f_o_r_m_a_t

       Type: string

       Default: '%s'

       This is the string displayed in the ``attachment'' menu for attachments of type
       message/rfc822.	For a full listing of defined printf()-like sequences see the
       section on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83)''.

       _6_._3_._1_2_2	_n_a_r_r_o_w___t_r_e_e

       Type: boolean

       Default: no

       This variable, when set, makes the thread tree narrower, allowing deeper
       threads to fit on the screen.

       _6_._3_._1_2_3	_p_a_g_e_r

       Type: path

       Default: 'builtin'

       This variable specifies which pager you would like to use to view messages.
       builtin means to use the builtin pager, otherwise this variable should specify
       the pathname of the external pager you would like to use.

       Using an external pager may have some disadvantages: Additional keystrokes are
       necessary because you can't call mutt functions directly from the pager, and
       screen resizes cause lines longer than the screen width to be badly formatted
       in the help menu.

       _6_._3_._1_2_4	_p_a_g_e_r___c_o_n_t_e_x_t

       Type: number

       Default: 0

       This variable controls the number of lines of context that are given when dis-
       playing the next or previous page in the internal pager.  By default, Mutt will
       display the line after the last one on the screen at the top of the next page
       (0 lines of context).

       _6_._3_._1_2_5	_p_a_g_e_r___f_o_r_m_a_t

       Type: string








       The Mutt E-Mail Client							    92



       Default: '-%Z- %C/%m: %-20.20n	%s'

       This variable controls the format of the one-line message ``status'' displayed
       before each message in either the internal or an external pager.  The valid
       sequences are listed in the ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83)'' sec-
       tion.

       _6_._3_._1_2_6	_p_a_g_e_r___i_n_d_e_x___l_i_n_e_s

       Type: number

       Default: 0

       Determines the number of lines of a mini-index which is shown when in the
       pager.  The current message, unless near the top or bottom of the folder, will
       be roughly one third of the way down this mini-index, giving the reader the
       context of a few messages before and after the message.	This is useful, for
       example, to determine how many messages remain to be read in the current
       thread.	One of the lines is reserved for the status bar from the index, so a
       _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s of 6 will only show 5 lines of the actual index.  A value of
       0 results in no index being shown.  If the number of messages in the current
       folder is less than _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s, then the index will only use as many
       lines as it needs.

       _6_._3_._1_2_7	_p_a_g_e_r___s_t_o_p

       Type: boolean

       Default: no

       When set, the internal-pager will nnoott move to the next message when you are at
       the end of a message and invoke the _n_e_x_t_-_p_a_g_e function.

       _6_._3_._1_2_8	_c_r_y_p_t___a_u_t_o_s_i_g_n

       Type: boolean

       Default: no

       Setting this variable will cause Mutt to always attempt to cryptographically
       sign outgoing messages.	This can be overridden by use of the _p_g_p_-_m_e_n_u, when
       signing is not required or encryption is requested as well. If
       ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.3.137  , page 94)'' is set, then OpenSSL is used
       instead to create S/MIME messages and settings can be overridden by use of the
       _s_m_i_m_e_-_m_e_n_u.  (Crypto only)

       _6_._3_._1_2_9	_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t

       Type: boolean

       Default: no

       Setting this variable will cause Mutt to always attempt to PGP encrypt outgoing
       messages.  This is probably only useful in connection to the _s_e_n_d_-_h_o_o_k command.








       The Mutt E-Mail Client							    93



       It can be overridden by use of the _p_g_p_-_m_e_n_u, when encryption is not required or
       signing is requested as well.  IF ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.3.137  , page
       94)'' is set, then OpenSSL is used instead to create S/MIME messages and set-
       tings can be overridden by use of the _s_m_i_m_e_-_m_e_n_u.  (Crypto only)

       _6_._3_._1_3_0	_p_g_p___i_g_n_o_r_e___s_u_b_k_e_y_s

       Type: boolean

       Default: yes

       Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, the
       principal key will inherit the subkeys' capabilities.  Unset this if you want
       to play interesting key selection games.  (PGP only)

       _6_._3_._1_3_1	_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t

       Type: boolean

       Default: yes

       If set, automatically PGP or OpenSSL encrypt replies to messages which are
       encrypted.  (Crypto only)

       _6_._3_._1_3_2	_c_r_y_p_t___r_e_p_l_y_s_i_g_n

       Type: boolean

       Default: no

       If set, automatically PGP or OpenSSL sign replies to messages which are signed.

       NNoottee:: this does not work on messages that are encrypted aanndd signed!  (Crypto
       only)

       _6_._3_._1_3_3	_c_r_y_p_t___r_e_p_l_y_s_i_g_n_e_n_c_r_y_p_t_e_d

       Type: boolean

       Default: no

       If set, automatically PGP or OpenSSL sign replies to messages which are
       encrypted. This makes sense in combination with ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section
       6.3.131	, page 93)'', because it allows you to sign all messages which are
       automatically encrypted.  This works around the problem noted in
       ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section 6.3.132  , page 93)'', that mutt is not able to
       find out whether an encrypted message is also signed.  (Crypto only)

       _6_._3_._1_3_4	_c_r_y_p_t___t_i_m_e_s_t_a_m_p

       Type: boolean

       Default: yes









       The Mutt E-Mail Client							    94



       If set, mutt will include a time stamp in the lines surrounding PGP or S/MIME
       output, so spoofing such lines is more difficult.  If you are using colors to
       mark these lines, and rely on these, you may unset this setting.  (Crypto only)

       _6_._3_._1_3_5	_p_g_p___u_s_e___g_p_g___a_g_e_n_t

       Type: boolean

       Default: no

       If set, mutt will use a possibly-running gpg-agent process.  (PGP only)

       _6_._3_._1_3_6	_c_r_y_p_t___v_e_r_i_f_y___s_i_g

       Type: quadoption

       Default: yes

       If ``yes'', always attempt to verify PGP or S/MIME signatures.  If ``ask'', ask
       whether or not to verify the signature.	If ``no'', never attempt to verify
       cryptographic signatures.  (Crypto only)

       _6_._3_._1_3_7	_s_m_i_m_e___i_s___d_e_f_a_u_l_t

       Type: boolean

       Default: no

       The default behaviour of mutt is to use PGP on all auto-sign/encryption opera-
       tions. To override and to use OpenSSL instead this must be set.	However, this
       has no effect while replying, since mutt will automatically select the same
       application that was used to sign/encrypt the original message.	(Note that
       this variable can be overridden by unsetting _$_c_r_y_p_t___a_u_t_o_s_m_i_m_e (section
       6.3.35  , page 70).)  (S/MIME only)

       _6_._3_._1_3_8	_s_m_i_m_e___a_s_k___c_e_r_t___l_a_b_e_l

       Type: boolean

       Default: yes

       This flag controls whether you want to be asked to enter a label for a certifi-
       cate about to be added to the database or not. It is set by default.  (S/MIME
       only)

       _6_._3_._1_3_9	_s_m_i_m_e___d_o_n_t___c_h_e_c_k___s_e_n_d_e_r

       Type: boolean

       Default: no

       This flag controls wether you want the skip the check for the sender's email
       address against the email address stored in the certificate.  This can be use-
       ful if most of your email senders use SMIMEv3 which no longer needs email-








       The Mutt E-Mail Client							    95



       addresses as part of the certificates.  It is not set by default.

       _6_._3_._1_4_0	_s_m_i_m_e___d_e_c_r_y_p_t___u_s_e___d_e_f_a_u_l_t___k_e_y

       Type: boolean

       Default: yes

       If set (default) this tells mutt to use the default key for decryption. Other-
       wise, if manage multiple certificate-key-pairs, mutt will try to use the mail-
       box-address to determine the key to use. It will ask you to supply a key, if it
       can't find one.	(S/MIME only)

       _6_._3_._1_4_1	_p_g_p___e_n_t_r_y___f_o_r_m_a_t

       Type: string

       Default: '%4n %t%f %4l/0x%k %-4a %2c %u'

       This variable allows you to customize the PGP key selection menu to your per-
       sonal taste. This string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page
       83)'', but has its own set of printf()-like sequences:

	     %n
		   number

	     %k
		   key id

	     %u
		   user id

	     %a
		   algorithm

	     %l
		   key length

	     %f
		   flags

	     %c
		   capabilities

	     %t
		   trust/validity of the key-uid association

	     %[<s>]
		   date of the key where <s> is an strftime(3) expression

       (PGP only)

       _6_._3_._1_4_2	_p_g_p___g_o_o_d___s_i_g_n









       The Mutt E-Mail Client							    96



       Type: regular expression

       Default: ''

       If you assign a text to this variable, then a PGP signature is only considered
       verified if the output from _$_p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d (section 6.3.157  , page 99)
       contains the text. Use this variable if the exit code from the command is 0
       even for bad signatures.  (PGP only)

       _6_._3_._1_4_3	_p_g_p___c_h_e_c_k___e_x_i_t

       Type: boolean

       Default: yes

       If set, mutt will check the exit code of the PGP subprocess when signing or
       encrypting.  A non-zero exit code means that the subprocess failed.  (PGP only)

       _6_._3_._1_4_4	_p_g_p___l_o_n_g___i_d_s

       Type: boolean

       Default: no

       If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs.  (PGP
       only)

       _6_._3_._1_4_5	_p_g_p___r_e_t_a_i_n_a_b_l_e___s_i_g_s

       Type: boolean

       Default: no

       If set, signed and encrypted messages will consist of nested multipart/signed
       and multipart/encrypted body parts.

       This is useful for applications like encrypted and signed mailing lists, where
       the outer layer (multipart/encrypted) can be easily removed, while the inner
       multipart/signed part is retained.  (PGP only)

       _6_._3_._1_4_6	_p_g_p___a_u_t_o_i_n_l_i_n_e

       Type: boolean

       Default: no

       This option controls whether Mutt generates old-style inline (traditional) PGP
       encrypted or signed messages under certain circumstances.  This can be overrid-
       den by use of the _p_g_p_-_m_e_n_u, when inline is not required.

       Note that Mutt might automatically use PGP/MIME for messages which consist of
       more than a single MIME part.  Mutt can be configured to ask before sending
       PGP/MIME messages when inline (traditional) would not work.  See also:
       ``_$_p_g_p___m_i_m_e___a_u_t_o (section 6.3.153  , page 98)''.








       The Mutt E-Mail Client							    97



       Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd.
       (PGP only)

       _6_._3_._1_4_7	_p_g_p___r_e_p_l_y_i_n_l_i_n_e

       Type: boolean

       Default: no

       Setting this variable will cause Mutt to always attempt to create an inline
       (traditional) message when replying to a message which is PGP encrypted/signed
       inline.	This can be overridden by use of the _p_g_p_-_m_e_n_u, when inline is not
       required.  This option does not automatically detect if the (replied-to) mes-
       sage is inline; instead it relies on Mutt internals for previously
       checked/flagged messages.

       Note that Mutt might automatically use PGP/MIME for messages which consist of
       more than a single MIME part.  Mutt can be configured to ask before sending
       PGP/MIME messages when inline (traditional) would not work.  See also:
       ``_$_p_g_p___m_i_m_e___a_u_t_o (section 6.3.153  , page 98)''.

       Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd.
       (PGP only)

       _6_._3_._1_4_8	_p_g_p___s_h_o_w___u_n_u_s_a_b_l_e

       Type: boolean

       Default: yes

       If set, mutt will display non-usable keys on the PGP key selection menu.  This
       includes keys which have been revoked, have expired, or have been marked as
       ``disabled'' by the user.  (PGP only)

       _6_._3_._1_4_9	_p_g_p___s_i_g_n___a_s

       Type: string

       Default: ''

       If you have more than one key pair, this option allows you to specify which of
       your private keys to use.  It is recommended that you use the keyid form to
       specify your key (e.g., ``0x00112233'').  (PGP only)

       _6_._3_._1_5_0	_p_g_p___s_t_r_i_c_t___e_n_c

       Type: boolean

       Default: yes

       If set, Mutt will automatically encode PGP/MIME signed messages as _q_u_o_t_e_d_-
       _p_r_i_n_t_a_b_l_e.  Please note that unsetting this variable may lead to problems with
       non-verifyable PGP signatures, so only change this if you know what you are
       doing.  (PGP only)








       The Mutt E-Mail Client							    98



       _6_._3_._1_5_1	_p_g_p___t_i_m_e_o_u_t

       Type: number

       Default: 300

       The number of seconds after which a cached passphrase will expire if not used.
       (PGP only)

       _6_._3_._1_5_2	_p_g_p___s_o_r_t___k_e_y_s

       Type: sort order

       Default: address

       Specifies how the entries in the `pgp keys' menu are sorted. The following are
       legal values:

	     address
		   sort alphabetically by user id

	     keyid
		   sort alphabetically by key id

	     date
		   sort by key creation date

	     trust
		   sort by the trust of the key

       If you prefer reverse order of the above values, prefix it with `reverse-'.
       (PGP only)

       _6_._3_._1_5_3	_p_g_p___m_i_m_e___a_u_t_o

       Type: quadoption

       Default: ask-yes

       This option controls whether Mutt will prompt you for automatically sending a
       (signed/encrypted) message using PGP/MIME when inline (traditional) fails (for
       any reason).

       Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd.
       (PGP only)

       _6_._3_._1_5_4	_p_g_p___a_u_t_o___d_e_c_o_d_e

       Type: boolean

       Default: no

       If set, mutt will automatically attempt to decrypt traditional PGP messages
       whenever the user performs an operation which ordinarily would result in the








       The Mutt E-Mail Client							    99



       contents of the message being operated on.  For example, if the user displays a
       pgp-traditional message which has not been manually checked with the check-tra-
       ditional-pgp function, mutt will automatically check the message for tradi-
       tional pgp.

       _6_._3_._1_5_5	_p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This format strings specifies a command which is used to decode application/pgp
       attachments.

       The PGP command formats have their own set of printf-like sequences:

	     %p
		   Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
		   string otherwise. Note: This may be used with a %? construct.

	     %f
		   Expands to the name of a file containing a message.

	     %s
		   Expands to the name of a file containing the signature part of a
		   multipart/signed attachment when verifying it.

	     %a
		   The value of _$_p_g_p___s_i_g_n___a_s (section 6.3.149  , page 97).

	     %r
		   One or more key IDs.

       For examples on how to configure these formats for the various versions of PGP
       which are floating around, see the pgp*.rc and gpg.rc files in the share/exam-
       ples/mutt subdirectory which has been installed on your system.	(PGP only)

       _6_._3_._1_5_6	_p_g_p___g_e_t_k_e_y_s___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is invoked whenever mutt will need public key information.	%r is
       the only printf-like sequence used with this format.  (PGP only)

       _6_._3_._1_5_7	_p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to verify PGP signatures.  (PGP only)









       The Mutt E-Mail Client							   100



       _6_._3_._1_5_8	_p_g_p___d_e_c_r_y_p_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to decrypt a PGP encrypted message.  (PGP only)

       _6_._3_._1_5_9	_p_g_p___c_l_e_a_r_s_i_g_n___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This format is used to create a old-style 'clearsigned' PGP message.  Note that
       the use of this format is ssttrroonnggllyy ddeepprreeccaatteedd.  (PGP only)

       _6_._3_._1_6_0	_p_g_p___s_i_g_n___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to create the detached PGP signature for a multi-
       part/signed PGP/MIME body part.	(PGP only)

       _6_._3_._1_6_1	_p_g_p___e_n_c_r_y_p_t___s_i_g_n___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to both sign and encrypt a body part.  (PGP only)

       _6_._3_._1_6_2	_p_g_p___e_n_c_r_y_p_t___o_n_l_y___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to encrypt a body part without signing it.	(PGP only)

       _6_._3_._1_6_3	_p_g_p___i_m_p_o_r_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to import a key from a message into the user's public key
       ring.  (PGP only)

       _6_._3_._1_6_4	_p_g_p___e_x_p_o_r_t___c_o_m_m_a_n_d

       Type: string








       The Mutt E-Mail Client							   101



       Default: ''

       This command is used to export a public key from the user's key ring.  (PGP
       only)

       _6_._3_._1_6_5	_p_g_p___v_e_r_i_f_y___k_e_y___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to verify key information from the key selection menu.
       (PGP only)

       _6_._3_._1_6_6	_p_g_p___l_i_s_t___s_e_c_r_i_n_g___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to list the secret key ring's contents.  The output format
       must be analogous to the one used by gpg --list-keys --with-colons.

       This format is also generated by the pgpring utility which comes with mutt.
       (PGP only)

       _6_._3_._1_6_7	_p_g_p___l_i_s_t___p_u_b_r_i_n_g___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to list the public key ring's contents.  The output format
       must be analogous to the one used by gpg --list-keys --with-colons.

       This format is also generated by the pgpring utility which comes with mutt.
       (PGP only)

       _6_._3_._1_6_8	_f_o_r_w_a_r_d___d_e_c_r_y_p_t

       Type: boolean

       Default: yes

       Controls the handling of encrypted messages when forwarding a message.  When
       set, the outer layer of encryption is stripped off.  This variable is only used
       if ``_$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.115  , page 89)'' is _s_e_t and ``_$_m_i_m_e___f_o_r_-
       _w_a_r_d___d_e_c_o_d_e (section 6.3.116  , page 90)'' is _u_n_s_e_t.  (PGP only)

       _6_._3_._1_6_9	_s_m_i_m_e___e_n_c_r_y_p_t___s_e_l_f

       Type: quadoption

       Default: yes








       The Mutt E-Mail Client							   102



       Encrypt the message to smime_default_key too.

       _6_._3_._1_7_0	_s_m_i_m_e___t_i_m_e_o_u_t

       Type: number

       Default: 300

       The number of seconds after which a cached passphrase will expire if not used.
       (S/MIME only)

       _6_._3_._1_7_1	_s_m_i_m_e___e_n_c_r_y_p_t___w_i_t_h

       Type: string

       Default: ''

       This sets the algorithm that should be used for encryption.  Valid choices are
       'des', 'des3', 'rc2-40', 'rc2-64', 'rc2-128'.  If unset '3des' (TripleDES) is
       used.  (S/MIME only)

       _6_._3_._1_7_2	_s_m_i_m_e___k_e_y_s

       Type: path

       Default: ''

       Since there is no pubring/secring as with PGP, mutt has to handle storage ad
       retrieval of keys/certs by itself. This is very basic right now, and stores
       keys and certificates in two different directories, both named as the hash-
       value retrieved from OpenSSL. There is an index file which contains mailbox-
       address keyid pair, and which can be manually edited. This one points to the
       location of the private keys.  (S/MIME only)

       _6_._3_._1_7_3	_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n

       Type: path

       Default: ''

       This variable contains the name of either a directory, or a file which contains
       trusted certificates for use with OpenSSL.  (S/MIME only)

       _6_._3_._1_7_4	_s_m_i_m_e___c_e_r_t_i_f_i_c_a_t_e_s

       Type: path

       Default: ''

       Since there is no pubring/secring as with PGP, mutt has to handle storage and
       retrieval of keys by itself. This is very basic right now, and keys and cer-
       tificates are stored in two different directories, both named as the hash-value
       retrieved from OpenSSL. There is an index file which contains mailbox-address
       keyid pairs, and which can be manually edited. This one points to the location








       The Mutt E-Mail Client							   103



       of the certificates.  (S/MIME only)

       _6_._3_._1_7_5	_s_m_i_m_e___d_e_c_r_y_p_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This format string specifies a command which is used to decrypt application/x-
       pkcs7-mime attachments.

       The OpenSSL command formats have their own set of printf-like sequences similar
       to PGP's:

	     %f
		   Expands to the name of a file containing a message.

	     %s
		   Expands to the name of a file containing the signature part of a
		   multipart/signed attachment when verifying it.

	     %k
		   The key-pair specified with _$_s_m_i_m_e___d_e_f_a_u_l_t___k_e_y (section 6.3.186  ,
		   page 105)

	     %c
		   One or more certificate IDs.

	     %a
		   The algorithm used for encryption.

	     %C
		   CA location:  Depending on whether _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section
		   6.3.173  , page 102) points to a directory or file, this expands to
		   '-CApath _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 6.3.173  , page 102)' or
		   '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 6.3.173  , page 102)'.

       For examples on how to configure these formats, see the smime.rc in the
       share/examples/mutt subdirectory which has been installed on your system.
       (S/MIME only)

       _6_._3_._1_7_6	_s_m_i_m_e___v_e_r_i_f_y___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to verify S/MIME signatures of type multipart/signed.
       (S/MIME only)

       _6_._3_._1_7_7	_s_m_i_m_e___v_e_r_i_f_y___o_p_a_q_u_e___c_o_m_m_a_n_d

       Type: string









       The Mutt E-Mail Client							   104



       Default: ''

       This command is used to verify S/MIME signatures of type application/x-
       pkcs7-mime.  (S/MIME only)

       _6_._3_._1_7_8	_s_m_i_m_e___s_i_g_n___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to created S/MIME signatures of type multipart/signed,
       which can be read by all mail clients.  (S/MIME only)

       _6_._3_._1_7_9	_s_m_i_m_e___s_i_g_n___o_p_a_q_u_e___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to created S/MIME signatures of type application/x-
       pkcs7-signature, which can only be handled by mail clients supporting the
       S/MIME extension.  (S/MIME only)

       _6_._3_._1_8_0	_s_m_i_m_e___e_n_c_r_y_p_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to create encrypted S/MIME messages.  (S/MIME only)

       _6_._3_._1_8_1	_s_m_i_m_e___p_k_7_o_u_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to extract PKCS7 structures of S/MIME signatures, in order
       to extract the public X509 certificate(s).  (S/MIME only)

       _6_._3_._1_8_2	_s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to extract X509 certificates from a PKCS7 structure.
       (S/MIME only)

       _6_._3_._1_8_3	_s_m_i_m_e___g_e_t___s_i_g_n_e_r___c_e_r_t___c_o_m_m_a_n_d

       Type: string









       The Mutt E-Mail Client							   105



       Default: ''

       This command is used to extract only the signers X509 certificate from a S/MIME
       signature, so that the certificate's owner may get compared to the email's
       'From'-field.  (S/MIME only)

       _6_._3_._1_8_4	_s_m_i_m_e___i_m_p_o_r_t___c_e_r_t___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to import a certificate via smime_keys.  (S/MIME only)

       _6_._3_._1_8_5	_s_m_i_m_e___g_e_t___c_e_r_t___e_m_a_i_l___c_o_m_m_a_n_d

       Type: string

       Default: ''

       This command is used to extract the mail address(es) used for storing X509 cer-
       tificates, and for verification purposes (to check whether the certificate was
       issued for the sender's mailbox).  (S/MIME only)

       _6_._3_._1_8_6	_s_m_i_m_e___d_e_f_a_u_l_t___k_e_y

       Type: string

       Default: ''

       This is the default key-pair to use for signing. This must be set to the keyid
       (the hash-value that OpenSSL generates) to work properly (S/MIME only)

       _6_._3_._1_8_7	_s_s_l___c_l_i_e_n_t___c_e_r_t

       Type: path

       Default: ''

       The file containing a client certificate and its associated private key.

       _6_._3_._1_8_8	_s_s_l___s_t_a_r_t_t_l_s

       Type: quadoption

       Default: yes

       If set (the default), mutt will attempt to use STARTTLS on servers advertising
       the capability. When unset, mutt will not attempt to use STARTTLS regardless of
       the server's capabilities.

       _6_._3_._1_8_9	_c_e_r_t_i_f_i_c_a_t_e___f_i_l_e

       Type: path








       The Mutt E-Mail Client							   106



       Default: '~/.mutt_certificates'

       This variable specifies the file where the certificates you trust are saved.
       When an unknown certificate is encountered, you are asked if you accept it or
       not. If you accept it, the certificate can also be saved in this file and fur-
       ther connections are automatically accepted.

       You can also manually add CA certificates in this file. Any server certificate
       that is signed with one of these CA certificates are also automatically
       accepted.

       Example: set certificate_file=~/.mutt/certificates

       _6_._3_._1_9_0	_s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s

       Type: boolean

       Default: yes

       If set to _y_e_s, mutt will use CA certificates in the system-wide certificate
       store when checking if server certificate is signed by a trusted CA.

       _6_._3_._1_9_1	_e_n_t_r_o_p_y___f_i_l_e

       Type: path

       Default: ''

       The file which includes random data that is used to initialize SSL library
       functions.

       _6_._3_._1_9_2	_s_s_l___u_s_e___s_s_l_v_2

       Type: boolean

       Default: yes

       This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
       tion process.

       _6_._3_._1_9_3	_s_s_l___u_s_e___s_s_l_v_3

       Type: boolean

       Default: yes

       This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
       tion process.

       _6_._3_._1_9_4	_s_s_l___u_s_e___t_l_s_v_1

       Type: boolean

       Default: yes








       The Mutt E-Mail Client							   107



       This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
       tion process.

       _6_._3_._1_9_5	_p_i_p_e___s_p_l_i_t

       Type: boolean

       Default: no

       Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command and the ``tag- prefix'' opera-
       tor.  If this variable is unset, when piping a list of tagged messages Mutt
       will concatenate the messages and will pipe them as a single folder.  When set,
       Mutt will pipe the messages one by one.	In both cases the messages are piped
       in the current sorted order, and the ``_$_p_i_p_e___s_e_p (section 6.3.197  , page
       107)'' separator is added after each message.

       _6_._3_._1_9_6	_p_i_p_e___d_e_c_o_d_e

       Type: boolean

       Default: no

       Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command.  When unset, Mutt will pipe
       the messages without any preprocessing. When set, Mutt will weed headers and
       will attempt to PGP/MIME decode the messages first.

       _6_._3_._1_9_7	_p_i_p_e___s_e_p

       Type: string

       Default: '\n'

       The separator to add between messages when piping a list of tagged messages to
       an external Unix command.

       _6_._3_._1_9_8	_p_o_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s

       Type: string

       Default: ''

       This is a colon-delimited list of authentication methods mutt may attempt to
       use to log in to an POP server, in the order mutt should try them.  Authentica-
       tion methods are either 'user', 'apop' or any SASL mechanism, eg 'digest-md5',
       'gssapi' or 'cram-md5'.	This parameter is case-insensitive. If this parameter
       is unset (the default) mutt will try all available methods, in order from most-
       secure to least-secure.

       Example: set pop_authenticators='digest-md5:apop:user'

       _6_._3_._1_9_9	_p_o_p___a_u_t_h___t_r_y___a_l_l

       Type: boolean









       The Mutt E-Mail Client							   108



       Default: yes

       If set, Mutt will try all available methods. When unset, Mutt will only fall
       back to other authentication methods if the previous methods are unavailable.
       If a method is available but authentication fails, Mutt will not connect to the
       POP server.

       _6_._3_._2_0_0	_p_o_p___c_h_e_c_k_i_n_t_e_r_v_a_l

       Type: number

       Default: 60

       This variable configures how often (in seconds) POP should look for new mail.

       _6_._3_._2_0_1	_p_o_p___d_e_l_e_t_e

       Type: quadoption

       Default: ask-no

       If set, Mutt will delete successfully downloaded messages from the POP server
       when using the fetch-mail function.  When unset, Mutt will download messages
       but also leave them on the POP server.

       _6_._3_._2_0_2	_p_o_p___h_o_s_t

       Type: string

       Default: ''

       The name of your POP server for the fetch-mail function.  You can also specify
       an alternative port, username and password, ie:

       [pop[s]://][username[:password]@]popserver[:port]

       _6_._3_._2_0_3	_p_o_p___l_a_s_t

       Type: boolean

       Default: no

       If this variable is set, mutt will try to use the 'LAST' POP command for
       retrieving only unread messages from the POP server when using the fetch-mail
       function.

       _6_._3_._2_0_4	_p_o_p___r_e_c_o_n_n_e_c_t

       Type: quadoption

       Default: ask-yes

       Controls whether or not Mutt will try to reconnect to POP server when connec-
       tion lost.








       The Mutt E-Mail Client							   109



       _6_._3_._2_0_5	_p_o_p___u_s_e_r

       Type: string

       Default: ''

       Your login name on the POP server.

       This variable defaults to your user name on the local machine.

       _6_._3_._2_0_6	_p_o_p___p_a_s_s

       Type: string

       Default: ''

       Specifies the password for your POP account.  If unset, Mutt will prompt you
       for your password when you open POP mailbox.  WWaarrnniinngg: you should only use this
       option when you are on a fairly secure machine, because the superuser can read
       your muttrc even if you are the only one who can read the file.

       _6_._3_._2_0_7	_p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g

       Type: string

       Default: ''

       Similar to the ``_$_a_t_t_r_i_b_u_t_i_o_n (section 6.3.14  , page 66)'' variable, Mutt will
       append this string after the inclusion of a message which is being replied to.

       _6_._3_._2_0_8	_p_o_s_t_p_o_n_e

       Type: quadoption

       Default: ask-yes

       Controls whether or not messages are saved in the ``_$_p_o_s_t_p_o_n_e_d (section
       6.3.209	, page 109)'' mailbox when you elect not to send immediately.

       _6_._3_._2_0_9	_p_o_s_t_p_o_n_e_d

       Type: path

       Default: '~/postponed'

       Mutt allows you to indefinitely ``_p_o_s_t_p_o_n_e (section 6.3.208  , page 109) send-
       ing a message'' which you are editing.  When you choose to postpone a message,
       Mutt saves it in the mailbox specified by this variable.  Also see the ``_$_p_o_s_t_-
       _p_o_n_e (section 6.3.208  , page 109)'' variable.

       _6_._3_._2_1_0	_p_r_e_c_o_n_n_e_c_t

       Type: string









       The Mutt E-Mail Client							   110



       Default: ''

       If set, a shell command to be executed if mutt fails to establish a connection
       to the server. This is useful for setting up secure connections, e.g. with
       ssh(1). If the command returns a  nonzero status, mutt gives up opening the
       server. Example:

       preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
       /dev/null > /dev/null'

       Mailbox 'foo' on mailhost.net can now be reached as '{localhost:1234}foo'.

       NOTE: For this example to work, you must be able to log in to the remote
       machine without having to enter a password.

       _6_._3_._2_1_1	_p_r_i_n_t

       Type: quadoption

       Default: ask-no

       Controls whether or not Mutt really prints messages.  This is set to _a_s_k_-_n_o by
       default, because some people accidentally hit ``p'' often (like me).

       _6_._3_._2_1_2	_p_r_i_n_t___c_o_m_m_a_n_d

       Type: path

       Default: 'lpr'

       This specifies the command pipe that should be used to print messages.

       _6_._3_._2_1_3	_p_r_i_n_t___d_e_c_o_d_e

       Type: boolean

       Default: yes

       Used in connection with the print-message command.  If this option is set, the
       message is decoded before it is passed to the external command specified by
       _$_p_r_i_n_t___c_o_m_m_a_n_d (section 6.3.212	, page 110).  If this option is unset, no pro-
       cessing will be applied to the message when printing it.  The latter setting
       may be useful if you are using some advanced printer filter which is able to
       properly format e-mail messages for printing.

       _6_._3_._2_1_4	_p_r_i_n_t___s_p_l_i_t

       Type: boolean

       Default: no

       Used in connection with the print-message command.  If this option is set, the
       command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 6.3.212  , page 110) is executed
       once for each message which is to be printed.  If this option is unset, the








       The Mutt E-Mail Client							   111



       command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 6.3.212  , page 110) is executed
       only once, and all the messages are concatenated, with a form feed as the mes-
       sage separator.

       Those who use the eennssccrriipptt(1) program's mail-printing mode will most likely
       want to set this option.

       _6_._3_._2_1_5	_p_r_o_m_p_t___a_f_t_e_r

       Type: boolean

       Default: yes

       If you use an _e_x_t_e_r_n_a_l ``_$_p_a_g_e_r (section 6.3.123  , page 91)'', setting this
       variable will cause Mutt to prompt you for a command when the pager exits
       rather than returning to the index menu.  If unset, Mutt will return to the
       index menu when the external pager exits.

       _6_._3_._2_1_6	_q_u_e_r_y___c_o_m_m_a_n_d

       Type: path

       Default: ''

       This specifies the command that mutt will use to make external address queries.
       The string should contain a %s, which will be substituted with the query string
       the user types.	See ``_q_u_e_r_y (section 4.5  , page 41)'' for more information.

       _6_._3_._2_1_7	_q_u_i_t

       Type: quadoption

       Default: yes

       This variable controls whether ``quit'' and ``exit'' actually quit from mutt.
       If it set to yes, they do quit, if it is set to no, they have no effect, and if
       it is set to ask-yes or ask-no, you are prompted for confirmation when you try
       to quit.

       _6_._3_._2_1_8	_q_u_o_t_e___e_m_p_t_y

       Type: boolean

       Default: yes

       Controls whether or not empty lines will be quoted using ``_i_n_d_e_n_t___s_t_r_i_n_g (sec-
       tion 6.3.92  , page 83)''.

       _6_._3_._2_1_9	_q_u_o_t_e___q_u_o_t_e_d

       Type: boolean

       Default: no









       The Mutt E-Mail Client							   112



       Controls how quoted lines will be quoted. If set, one quote character will be
       added to the end of existing prefix.  Otherwise, quoted lines will be prepended
       by ``_i_n_d_e_n_t___s_t_r_i_n_g (section 6.3.92  , page 83)''.

       _6_._3_._2_2_0	_q_u_o_t_e___r_e_g_e_x_p

       Type: regular expression

       Default: '^([ \t]*[|>:}#])+'

       A regular expression used in the internal-pager to determine quoted sections of
       text in the body of a message.

       NNoottee:: In order to use the _q_u_o_t_e_dxx patterns in the internal pager, you need to
       set this to a regular expression that matches _e_x_a_c_t_l_y the quote characters at
       the beginning of quoted lines.

       _6_._3_._2_2_1	_r_e_a_d___i_n_c

       Type: number

       Default: 10

       If set to a value greater than 0, Mutt will display which message it is cur-
       rently on when reading a mailbox.  The message is printed after _r_e_a_d___i_n_c mes-
       sages have been read (e.g., if set to 25, Mutt will print a message when it
       reads message 25, and then again when it gets to message 50).  This variable is
       meant to indicate progress when reading large mailboxes which may take some
       time.  When set to 0, only a single message will appear before the reading the
       mailbox.

       Also see the ``_$_w_r_i_t_e___i_n_c (section 6.3.282  , page 128)'' variable.

       _6_._3_._2_2_2	_r_e_a_d___o_n_l_y

       Type: boolean

       Default: no

       If set, all folders are opened in read-only mode.

       _6_._3_._2_2_3	_r_e_a_l_n_a_m_e

       Type: string

       Default: ''

       This variable specifies what 'real' or 'personal' name should be used when
       sending messages.

       By default, this is the GECOS field from /etc/passwd.  Note that this variable
       will _n_o_t be used when the user has set a real name in the _$_f_r_o_m (section
       6.3.62  , page 77) variable.









       The Mutt E-Mail Client							   113



       _6_._3_._2_2_4	_r_e_c_a_l_l

       Type: quadoption

       Default: ask-yes

       Controls whether or not Mutt recalls postponed messages when composing a new
       message.  Also see ``_$_p_o_s_t_p_o_n_e_d (section 6.3.209  , page 109)''.

       Setting this variable to ``yes'' is not generally useful, and thus not recom-
       mended.

       _6_._3_._2_2_5	_r_e_c_o_r_d

       Type: path

       Default: ''

       This specifies the file into which your outgoing messages should be appended.
       (This is meant as the primary method for saving a copy of your messages, but
       another way to do this is using the ``_m_y___h_d_r (section 3.13  , page 24)'' com-
       mand to create a _B_c_c_: field with your email address in it.)

       The value of _$_r_e_c_o_r_d _(_s_e_c_t_i_o_n _6_._3_._2_2_5  _, _p_a_g_e _1_1_3_) is overridden by the
       ``_$_f_o_r_c_e___n_a_m_e (section 6.3.57  , page 76)'' and ``_$_s_a_v_e___n_a_m_e (section
       6.3.236	, page 115)'' variables, and the ``_f_c_c_-_h_o_o_k (section 3.16  , page
       26)'' command.

       _6_._3_._2_2_6	_r_e_p_l_y___r_e_g_e_x_p

       Type: regular expression

       Default: '^(re([\[0-9\]+])*|aw):[ \t]*'

       A regular expression used to recognize reply messages when threading and reply-
       ing. The default value corresponds to the English 'Re:' and the German 'Aw:'.

       _6_._3_._2_2_7	_r_e_p_l_y___s_e_l_f

       Type: boolean

       Default: no

       If unset and you are replying to a message sent by you, Mutt will assume that
       you want to reply to the recipients of that message rather than to yourself.

       _6_._3_._2_2_8	_r_e_p_l_y___t_o

       Type: quadoption

       Default: ask-yes

       If set, when replying to a message, Mutt will use the address listed in the
       Reply-to: header as the recipient of the reply.	If unset, it will use the








       The Mutt E-Mail Client							   114



       address in the From: header field instead.  This option is useful for reading a
       mailing list that sets the Reply-To: header field to the list address and you
       want to send a private message to the author of a message.

       _6_._3_._2_2_9	_r_e_s_o_l_v_e

       Type: boolean

       Default: yes

       When set, the cursor will be automatically advanced to the next (possibly
       undeleted) message whenever a command that modifies the current message is exe-
       cuted.

       _6_._3_._2_3_0	_r_e_v_e_r_s_e___a_l_i_a_s

       Type: boolean

       Default: no

       This variable controls whether or not Mutt will display the 'personal' name
       from your aliases in the index menu if it finds an alias that matches the mes-
       sage's sender.  For example, if you have the following alias:


	    alias juser abd30425@somewhere.net (Joe User)


       and then you receive mail which contains the following header:


	    From: abd30425@somewhere.net


       It would be displayed in the index menu as ``Joe User'' instead of
       ``abd30425@somewhere.net.''  This is useful when the person's e-mail address is
       not human friendly (like CompuServe addresses).

       _6_._3_._2_3_1	_r_e_v_e_r_s_e___n_a_m_e

       Type: boolean

       Default: no

       It may sometimes arrive that you receive mail to a certain machine, move the
       messages to another machine, and reply to some the messages from there.	If
       this variable is set, the default _F_r_o_m_: line of the reply messages is built
       using the address where you received the messages you are replying to iiff that
       address matches your alternates.  If the variable is unset, or the address that
       would be used doesn't match your alternates, the _F_r_o_m_: line will use your
       address on the current machine.

       _6_._3_._2_3_2	_r_e_v_e_r_s_e___r_e_a_l_n_a_m_e









       The Mutt E-Mail Client							   115



       Type: boolean

       Default: yes

       This variable fine-tunes the behaviour of the _r_e_v_e_r_s_e___n_a_m_e (section 6.3.231  ,
       page 114) feature.  When it is set, mutt will use the address from incoming
       messages as-is, possibly including eventual real names.	When it is unset, mutt
       will override any such real names with the setting of the _r_e_a_l_n_a_m_e (section
       6.3.223	, page 112) variable.

       _6_._3_._2_3_3	_r_f_c_2_0_4_7___p_a_r_a_m_e_t_e_r_s

       Type: boolean

       Default: no

       When this variable is set, Mutt will decode RFC-2047-encoded MIME parameters.
       You want to set this variable when mutt suggests you to save attachments to
       files named like this: =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=

       When this variable is set interactively, the change doesn't have the desired
       effect before you have changed folders.

       Note that this use of RFC 2047's encoding is explicitly, prohibited by the
       standard, but nevertheless encountered in the wild.  Also note that setting
       this parameter will _n_o_t have the effect that mutt _g_e_n_e_r_a_t_e_s this kind of encod-
       ing.  Instead, mutt will unconditionally use the encoding specified in RFC
       2231.

       _6_._3_._2_3_4	_s_a_v_e___a_d_d_r_e_s_s

       Type: boolean

       Default: no

       If set, mutt will take the sender's full address when choosing a default folder
       for saving a mail. If ``_$_s_a_v_e___n_a_m_e (section 6.3.236  , page 115)'' or
       ``_$_f_o_r_c_e___n_a_m_e (section 6.3.57  , page 76)'' is set too, the selection of the
       fcc folder will be changed as well.

       _6_._3_._2_3_5	_s_a_v_e___e_m_p_t_y

       Type: boolean

       Default: yes

       When unset, mailboxes which contain no saved messages will be removed when
       closed (the exception is ``_$_s_p_o_o_l_f_i_l_e (section 6.3.258  , page 121)'' which is
       never removed).	If set, mailboxes are never removed.

       NNoottee:: This only applies to mbox and MMDF folders, Mutt does not delete MH and
       Maildir directories.










       The Mutt E-Mail Client							   116



       _6_._3_._2_3_6	_s_a_v_e___n_a_m_e

       Type: boolean

       Default: no

       This variable controls how copies of outgoing messages are saved.  When set, a
       check is made to see if a mailbox specified by the recipient address exists
       (this is done by searching for a mailbox in the ``_$_f_o_l_d_e_r (section 6.3.54  ,
       page 74)'' directory with the _u_s_e_r_n_a_m_e part of the recipient address).  If the
       mailbox exists, the outgoing message will be saved to that mailbox, otherwise
       the message is saved to the ``_$_r_e_c_o_r_d (section 6.3.225  , page 113)'' mailbox.

       Also see the ``_$_f_o_r_c_e___n_a_m_e (section 6.3.57  , page 76)'' variable.

       _6_._3_._2_3_7	_s_c_o_r_e

       Type: boolean

       Default: yes

       When this variable is _u_n_s_e_t, scoring is turned off.  This can be useful to
       selectively disable scoring for certain folders when the ``_$_s_c_o_r_e___t_h_r_e_s_h_-
       _o_l_d___d_e_l_e_t_e (section 6.3.238  , page 116)'' variable and friends are used.

       _6_._3_._2_3_8	_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e

       Type: number

       Default: -1

       Messages which have been assigned a score equal to or lower than the value of
       this variable are automatically marked for deletion by mutt.  Since mutt scores
       are always greater than or equal to zero, the default setting of this variable
       will never mark a message for deletion.

       _6_._3_._2_3_9	_s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g

       Type: number

       Default: 9999

       Messages which have been assigned a score greater than or equal to this vari-
       able's value are automatically marked 'flagged'.

       _6_._3_._2_4_0	_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d

       Type: number

       Default: -1

       Messages which have been assigned a score equal to or lower than the value of
       this variable are automatically marked as read by mutt.	Since mutt scores are
       always greater than or equal to zero, the default setting of this variable will








       The Mutt E-Mail Client							   117



       never mark a message read.

       _6_._3_._2_4_1	_s_e_n_d___c_h_a_r_s_e_t

       Type: string

       Default: 'us-ascii:iso-8859-1:utf-8'

       A list of character sets for outgoing messages. Mutt will use the first charac-
       ter set into which the text can be converted exactly.  If your ``_$_c_h_a_r_s_e_t (sec-
       tion 6.3.21  , page 67)'' is not iso-8859-1 and recipients may not understand
       UTF-8, it is advisable to include in the list an appropriate widely used stan-
       dard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either instead
       of or after 'iso-8859-1'.

       _6_._3_._2_4_2	_s_e_n_d_m_a_i_l

       Type: path

       Default: '/usr/sbin/sendmail -oem -oi'

       Specifies the program and arguments used to deliver mail sent by Mutt.  Mutt
       expects that the specified program interprets additional arguments as recipient
       addresses.

       _6_._3_._2_4_3	_s_e_n_d_m_a_i_l___w_a_i_t

       Type: number

       Default: 0

       Specifies the number of seconds to wait for the ``_$_s_e_n_d_m_a_i_l (section 6.3.242  ,
       page 117)'' process to finish before giving up and putting delivery in the
       background.

       Mutt interprets the value of this variable as follows:

	     >0
		   number of seconds to wait for sendmail to finish before continuing

	     0
		   wait forever for sendmail to finish

	     <0
		   always put sendmail in the background without waiting

       Note that if you specify a value other than 0, the output of the child process
       will be put in a temporary file.  If there is some error, you will be informed
       as to where to find the output.

       _6_._3_._2_4_4	_s_h_e_l_l

       Type: path









       The Mutt E-Mail Client							   118



       Default: ''

       Command to use when spawning a subshell.  By default, the user's login shell
       from /etc/passwd is used.

       _6_._3_._2_4_5	_s_i_g___d_a_s_h_e_s

       Type: boolean

       Default: yes

       If set, a line containing ``-- '' will be inserted before your ``_$_s_i_g_n_a_t_u_r_e
       (section 6.3.247  , page 118)''.  It is ssttrroonnggllyy recommended that you not unset
       this variable unless your ``signature'' contains just your name.  The reason
       for this is because many software packages use ``-- \n'' to detect your signa-
       ture.  For example, Mutt has the ability to highlight the signature in a dif-
       ferent color in the builtin pager.

       _6_._3_._2_4_6	_s_i_g___o_n___t_o_p

       Type: boolean

       Default: no

       If set, the signature will be included before any quoted or forwarded text.  It
       is ssttrroonnggllyy recommended that you do not set this variable unless you really
       know what you are doing, and are prepared to take some heat from netiquette
       guardians.

       _6_._3_._2_4_7	_s_i_g_n_a_t_u_r_e

       Type: path

       Default: '~/.signature'

       Specifies the filename of your signature, which is appended to all outgoing
       messages.   If the filename ends with a pipe (``|''), it is assumed that file-
       name is a shell command and input should be read from its stdout.

       _6_._3_._2_4_8	_s_i_m_p_l_e___s_e_a_r_c_h

       Type: string

       Default: '~f %s | ~s %s'

       Specifies how Mutt should expand a simple search into a real search pattern.  A
       simple search is one that does not contain any of the ~ operators.  See ``_p_a_t_-
       _t_e_r_n_s (section 4.2  , page 35)'' for more information on search patterns.

       For example, if you simply type joe at a search or limit prompt, Mutt will
       automatically expand it to the value specified by this variable.  For the
       default value it would be:

       ~f joe | ~s joe








       The Mutt E-Mail Client							   119



       _6_._3_._2_4_9	_s_m_a_r_t___w_r_a_p

       Type: boolean

       Default: yes

       Controls the display of lines longer than the screen width in the internal
       pager. If set, long lines are wrapped at a word boundary.  If unset, lines are
       simply wrapped at the screen edge. Also see the ``_$_m_a_r_k_e_r_s (section 6.3.102  ,
       page 87)'' variable.

       _6_._3_._2_5_0	_s_m_i_l_e_y_s

       Type: regular expression

       Default: '(>From )|(:[-^]?[][)(><}{|/DP])'

       The _p_a_g_e_r uses this variable to catch some common false positives of
       ``_$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.220  , page 112)'', most notably smileys in the
       beginning of a line

       _6_._3_._2_5_1	_s_l_e_e_p___t_i_m_e

       Type: number

       Default: 1

       Specifies time, in seconds, to pause while displaying certain informational
       messages, while moving from folder to folder and after expunging messages from
       the current folder.  The default is to pause one second, so a value of zero for
       this option suppresses the pause.

       _6_._3_._2_5_2	_s_o_r_t

       Type: sort order

       Default: date

       Specifies how to sort messages in the _i_n_d_e_x menu.  Valid values are:


	       date or date-sent
	       date-received
	       from
	       mailbox-order (unsorted)
	       score
	       size
	       spam
	       subject
	       threads
	       to


       You may optionally use the reverse- prefix to specify reverse sorting order








       The Mutt E-Mail Client							   120



       (example: set sort=reverse-date-sent).

       _6_._3_._2_5_3	_s_o_r_t___a_l_i_a_s

       Type: sort order

       Default: alias

       Specifies how the entries in the `alias' menu are sorted.  The following are
       legal values:


	       address (sort alphabetically by email address)
	       alias (sort alphabetically by alias name)
	       unsorted (leave in order specified in .muttrc)


       _6_._3_._2_5_4	_s_o_r_t___a_u_x

       Type: sort order

       Default: date

       When sorting by threads, this variable controls how threads are sorted in rela-
       tion to other threads, and how the branches of the thread trees are sorted.
       This can be set to any value that ``_$_s_o_r_t (section 6.3.252  , page 119)'' can,
       except threads (in that case, mutt will just use date-sent).  You can also
       specify the last- prefix in addition to the reverse- prefix, but last- must
       come after reverse-.  The last- prefix causes messages to be sorted against its
       siblings by which has the last descendant, using the rest of sort_aux as an
       ordering.  For instance, set sort_aux=last- date-received would mean that if a
       new message is received in a thread, that thread becomes the last one displayed
       (or the first, if you have set sort=reverse-threads.) Note: For reversed
       ``_$_s_o_r_t (section 6.3.252  , page 119)'' order _$_s_o_r_t___a_u_x (section 6.3.254  ,
       page 120) is reversed again (which is not the right thing to do, but kept to
       not break any existing configuration setting).

       _6_._3_._2_5_5	_s_o_r_t___b_r_o_w_s_e_r

       Type: sort order

       Default: alpha

       Specifies how to sort entries in the file browser.  By default, the entries are
       sorted alphabetically.  Valid values:


	       alpha (alphabetically)
	       date
	       size
	       unsorted


       You may optionally use the reverse- prefix to specify reverse sorting order








       The Mutt E-Mail Client							   121



       (example: set sort_browser=reverse-date).

       _6_._3_._2_5_6	_s_o_r_t___r_e

       Type: boolean

       Default: yes

       This variable is only useful when sorting by threads with ``_$_s_t_r_i_c_t___t_h_r_e_a_d_s
       (section 6.3.262  , page 124)'' unset.  In that case, it changes the heuristic
       mutt uses to thread messages by subject.  With sort_re set, mutt will only
       attach a message as the child of another message by subject if the subject of
       the child message starts with a substring matching the setting of ``_$_r_e_p_l_y___r_e_g_-
       _e_x_p (section 6.3.226  , page 113)''.  With sort_re unset, mutt will attach the
       message whether or not this is the case, as long as the non-``_$_r_e_p_l_y___r_e_g_e_x_p
       (section 6.3.226  , page 113)'' parts of both messages are identical.

       _6_._3_._2_5_7	_s_p_a_m___s_e_p_a_r_a_t_o_r

       Type: string

       Default: ','

       ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 6.3.257  , page 121)'' controls what happens when
       multiple spam headers are matched: if unset, each successive header will over-
       write any previous matches value for the spam label. If set, each successive
       match will append to the previous, using ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 6.3.257  ,
       page 121)'' as a separator.

       _6_._3_._2_5_8	_s_p_o_o_l_f_i_l_e

       Type: path

       Default: ''

       If your spool mailbox is in a non-default place where Mutt cannot find it, you
       can specify its location with this variable.  Mutt will automatically set this
       variable to the value of the environment variable $MAIL if it is not set.

       _6_._3_._2_5_9	_s_t_a_t_u_s___c_h_a_r_s

       Type: string

       Default: '-*%A'

       Controls the characters used by the '%r' indicator in ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section
       6.3.260	, page 121)''. The first character is used when the mailbox is
       unchanged. The second is used when the mailbox has been changed, and it needs
       to be resynchronized. The third is used if the mailbox is in read-only mode, or
       if the mailbox will not be written when exiting that mailbox (You can toggle
       whether to write changes to a mailbox with the toggle-write operation, bound by
       default to '%'). The fourth is used to indicate that the current folder has
       been opened in attach- message mode (Certain operations like composing a new
       mail, replying, forwarding, etc. are not permitted in this mode).








       The Mutt E-Mail Client							   122



       _6_._3_._2_6_0	_s_t_a_t_u_s___f_o_r_m_a_t

       Type: string

       Default: '-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F?
       Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---'

       Controls the format of the status line displayed in the _i_n_d_e_x menu.  This
       string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.93  , page 83)'', but has its
       own set of printf()-like sequences:

	     %b
		   number of mailboxes with new mail *

	     %d
		   number of deleted messages *

	     %f
		   the full pathname of the current mailbox

	     %F
		   number of flagged messages *

	     %h
		   local hostname

	     %l
		   size (in bytes) of the current mailbox *

	     %L
		   size (in bytes) of the messages shown (i.e., which match the cur-
		   rent limit) *

	     %m
		   the number of messages in the mailbox *

	     %M
		   the number of messages shown (i.e., which match the current limit)
		   *

	     %n
		   number of new messages in the mailbox *

	     %o
		   number of old unread messages *

	     %p
		   number of postponed messages *

	     %P
		   percentage of the way through the index

	     %r
		   modified/read-only/won't-write/attach-message indicator, according








       The Mutt E-Mail Client							   123



		   to _$_s_t_a_t_u_s___c_h_a_r_s (section 6.3.259  , page 121)

	     %s
		   current sorting mode (_$_s_o_r_t (section 6.3.252  , page 119))

	     %S
		   current aux sorting method (_$_s_o_r_t___a_u_x (section 6.3.254  , page
		   120))

	     %t
		   number of tagged messages *

	     %u
		   number of unread messages *

	     %v
		   Mutt version string

	     %V
		   currently active limit pattern, if any *

	     %>X
		   right justify the rest of the string and pad with 'X'

	     %|X
		   pad to the end of the line with 'X'

       * = can be optionally printed if nonzero

       Some of the above 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

       %?<sequence_char>?<optional_string>?

       where _s_e_q_u_e_n_c_e___c_h_a_r is a character from the table above, and _o_p_t_i_o_n_a_l___s_t_r_i_n_g is
       the string you would like printed if _s_e_q_u_e_n_c_e___c_h_a_r is nonzero.  _o_p_t_i_o_n_a_l___s_t_r_i_n_g
       mmaayy contain other sequences as well as normal text, but you may nnoott nest
       optional strings.

       Here is an example illustrating how to optionally print the number of new mes-
       sages in a mailbox: %?n?%n new messages.?

       Additionally you can switch between two strings, the first one, if a value is
       zero, the second one, if the value is nonzero, by using the following con-
       struct: %?<sequence_char>?<if_string>&<else_string>?

       You can additionally force the result of any printf-like sequence to be lower-
       case by prefixing the sequence character with an underscore (_) sign.  For
       example, if you want to display the local hostname in lowercase, you would use:
       %_h









       The Mutt E-Mail Client							   124



       If you prefix the sequence character with a colon (:) character, mutt will
       replace any dots in the expansion by underscores. This might be helpful with
       IMAP folders that don't like dots in folder names.

       _6_._3_._2_6_1	_s_t_a_t_u_s___o_n___t_o_p

       Type: boolean

       Default: no

       Setting this variable causes the ``status bar'' to be displayed on the first
       line of the screen rather than near the bottom.

       _6_._3_._2_6_2	_s_t_r_i_c_t___t_h_r_e_a_d_s

       Type: boolean

       Default: no

       If set, threading will only make use of the ``In-Reply-To'' and ``References''
       fields when you ``_$_s_o_r_t (section 6.3.252  , page 119)'' by message threads.  By
       default, messages with the same subject are grouped together in ``pseudo
       threads.''  This may not always be desirable, such as in a personal mailbox
       where you might have several unrelated messages with the subject ``hi'' which
       will get grouped together.

       _6_._3_._2_6_3	_s_u_s_p_e_n_d

       Type: boolean

       Default: yes

       When _u_n_s_e_t, mutt won't stop when the user presses the terminal's _s_u_s_p key, usu-
       ally ``control-Z''. This is useful if you run mutt inside an xterm using a com-
       mand like xterm -e mutt.

       _6_._3_._2_6_4	_t_e_x_t___f_l_o_w_e_d

       Type: boolean

       Default: no

       When set, mutt will generate text/plain; format=flowed attachments.  This for-
       mat is easier to handle for some mailing software, and generally just looks
       like ordinary text.  To actually make use of this format's features, you'll
       need support in your editor.

       Note that _$_i_n_d_e_n_t___s_t_r_i_n_g (section 6.3.92  , page 83) is ignored when this
       option is set.

       _6_._3_._2_6_5	_t_h_r_e_a_d___r_e_c_e_i_v_e_d

       Type: boolean









       The Mutt E-Mail Client							   125



       Default: no

       When set, mutt uses the date received rather than the date sent to thread mes-
       sages by subject.

       _6_._3_._2_6_6	_t_h_o_r_o_u_g_h___s_e_a_r_c_h

       Type: boolean

       Default: no

       Affects the _~_b and _~_h search operations described in section ``_p_a_t_t_e_r_n_s (sec-
       tion 4.2  , page 35)'' above.  If set, the headers and attachments of messages
       to be searched are decoded before searching.  If unset, messages are searched
       as they appear in the folder.

       _6_._3_._2_6_7	_t_i_l_d_e

       Type: boolean

       Default: no

       When set, the internal-pager will pad blank lines to the bottom of the screen
       with a tilde (~).

       _6_._3_._2_6_8	_t_i_m_e_o_u_t

       Type: number

       Default: 600

       This variable controls the _n_u_m_b_e_r _o_f _s_e_c_o_n_d_s Mutt will wait for a key to be
       pressed in the main menu before timing out and checking for new mail.  A value
       of zero or less will cause Mutt to never time out.

       _6_._3_._2_6_9	_t_m_p_d_i_r

       Type: path

       Default: ''

       This variable allows you to specify where Mutt will place its temporary files
       needed for displaying and composing messages.  If this variable is not set, the
       environment variable TMPDIR is used.  If TMPDIR is not set then '/tmp' is used.

       _6_._3_._2_7_0	_t_o___c_h_a_r_s

       Type: string

       Default: ' +TCFL'

       Controls the character used to indicate mail addressed to you.  The first char-
       acter is the one used when the mail is NOT addressed to your address (default:
       space).	The second is used when you are the only recipient of the message








       The Mutt E-Mail Client							   126



       (default: +).  The third is when your address appears in the TO header field,
       but you are not the only recipient of the message (default: T).	The fourth
       character is used when your address is specified in the CC header field, but
       you are not the only recipient.	The fifth character is used to indicate mail
       that was sent by _y_o_u.  The sixth character is used to indicate when a mail was
       sent to a mailing-list you subscribe to (default: L).

       _6_._3_._2_7_1	_t_u_n_n_e_l

       Type: string

       Default: ''

       Setting this variable will cause mutt to open a pipe to a command instead of a
       raw socket. You may be able to use this to set up preauthenticated connections
       to your IMAP/POP3 server. Example:

       tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'

       NOTE: For this example to work you must be able to log in to the remote machine
       without having to enter a password.

       _6_._3_._2_7_2	_u_s_e___8_b_i_t_m_i_m_e

       Type: boolean

       Default: no

       WWaarrnniinngg:: do not set this variable unless you are using a version of sendmail
       which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be
       able to send mail.

       When _s_e_t, Mutt will invoke ``_$_s_e_n_d_m_a_i_l (section 6.3.242	, page 117)'' with the
       -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation.

       _6_._3_._2_7_3	_u_s_e___d_o_m_a_i_n

       Type: boolean

       Default: yes

       When set, Mutt will qualify all local addresses (ones without the @host por-
       tion) with the value of ``_$_h_o_s_t_n_a_m_e (section 6.3.75  , page 79)''.  If _u_n_s_e_t,
       no addresses will be qualified.

       _6_._3_._2_7_4	_u_s_e___f_r_o_m

       Type: boolean

       Default: yes

       When _s_e_t, Mutt will generate the `From:' header field when sending messages.
       If _u_n_s_e_t, no `From:' header field will be generated unless the user explicitly
       sets one using the ``_m_y___h_d_r (section 3.13  , page 24)'' command.








       The Mutt E-Mail Client							   127



       _6_._3_._2_7_5	_u_s_e___i_p_v_6

       Type: boolean

       Default: yes

       When _s_e_t, Mutt will look for IPv6 addresses of hosts it tries to contact.  If
       this option is unset, Mutt will restrict itself to IPv4 addresses.  Normally,
       the default should work.

       _6_._3_._2_7_6	_u_s_e_r___a_g_e_n_t

       Type: boolean

       Default: yes

       When _s_e_t, mutt will add a 'User-Agent' header to outgoing messages, indicating
       which version of mutt was used for composing them.

       _6_._3_._2_7_7	_v_i_s_u_a_l

       Type: path

       Default: ''

       Specifies the visual editor to invoke when the _~_v command is given in the
       builtin editor.

       _6_._3_._2_7_8	_w_a_i_t___k_e_y

       Type: boolean

       Default: yes

       Controls whether Mutt will ask you to press a key after _s_h_e_l_l_- _e_s_c_a_p_e, _p_i_p_e_-
       _m_e_s_s_a_g_e, _p_i_p_e_-_e_n_t_r_y, _p_r_i_n_t_-_m_e_s_s_a_g_e, and _p_r_i_n_t_-_e_n_t_r_y commands.

       It is also used when viewing attachments with ``_a_u_t_o___v_i_e_w (section 5.4  , page
       58)'', provided that the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag,
       and the external program is interactive.

       When set, Mutt will always ask for a key. When unset, Mutt will wait for a key
       only if the external command returned a non-zero status.

       _6_._3_._2_7_9	_w_e_e_d

       Type: boolean

       Default: yes

       When set, mutt will weed headers when displaying, forwarding, printing, or
       replying to messages.










       The Mutt E-Mail Client							   128



       _6_._3_._2_8_0	_w_r_a_p___s_e_a_r_c_h

       Type: boolean

       Default: yes

       Controls whether searches wrap around the end of the mailbox.

       When set, searches will wrap around the first (or last) message. When unset,
       searches will not wrap.

       _6_._3_._2_8_1	_w_r_a_p_m_a_r_g_i_n

       Type: number

       Default: 0

       Controls the size of the margin remaining at the right side of the terminal
       when mutt's pager does smart wrapping.

       _6_._3_._2_8_2	_w_r_i_t_e___i_n_c

       Type: number

       Default: 10

       When writing a mailbox, a message will be printed every _w_r_i_t_e___i_n_c messages to
       indicate progress.  If set to 0, only a single message will be displayed before
       writing a mailbox.

       Also see the ``_$_r_e_a_d___i_n_c (section 6.3.221  , page 112)'' variable.

       _6_._3_._2_8_3	_w_r_i_t_e___b_c_c

       Type: boolean

       Default: yes

       Controls whether mutt writes out the Bcc header when preparing messages to be
       sent.  Exim users may wish to unset this.

       _6_._4  _F_u_n_c_t_i_o_n_s

       The following is the list of available functions listed by the mapping in which
       they are available.  The default key setting is given, and an explanation of
       what the function does.	The key bindings of these functions can be changed
       with the _b_i_n_d (section 3.3  , page 16) command.

       _6_._4_._1  _g_e_n_e_r_i_c

       The _g_e_n_e_r_i_c menu is not a real menu, but specifies common functions (such as
       movement) available in all menus except for _p_a_g_e_r and _e_d_i_t_o_r.  Changing set-
       tings for this menu will affect the default bindings for all menus (except as
       noted).








       The Mutt E-Mail Client							   129



	    bottom-page 	       L   move to the bottom of the page
	    current-bottom     not bound   move current entry to bottom of page
	    current-middle     not bound   move current entry to middle of page
	    current-top        not bound   move current entry to top of page
	    enter-command	       :   enter a muttrc command
	    exit		       q   exit this menu
	    first-entry 	       =   move to the first entry
	    half-down		       ]   scroll down 1/2 page
	    half-up		       [   scroll up 1/2 page
	    help		       ?   this screen
	    jump		  number   jump to an index number
	    last-entry		       *   move to the last entry
	    middle-page 	       M   move to the middle of the page
	    next-entry		       j   move to the next entry
	    next-line		       >   scroll down one line
	    next-page		       z   move to the next page
	    previous-entry	       k   move to the previous entry
	    previous-line	       <   scroll up one line
	    previous-page	       Z   move to the previous page
	    refresh		      ^L   clear and redraw the screen
	    search		       /   search for a regular expression
	    search-next 	       n   search for next match
	    search-opposite    not bound   search for next match in opposite direction
	    search-reverse	   ESC /   search backwards for a regular expression
	    select-entry	     RET   select the current entry
	    shell-escape	       !   run a program in a subshell
	    tag-entry		       t   toggle the tag on the current entry
	    tag-prefix		       ;   apply next command to tagged entries
	    tag-prefix-cond    not bound   apply next function ONLY to tagged messages
	    top-page		       H   move to the top of the page
	    what-key	       not bound   display the keycode for a key press


       _6_._4_._2  _i_n_d_e_x




























       The Mutt E-Mail Client							   130



	    bounce-message	       b   remail a message to another user
	    change-folder	       c   open a different folder
	    change-folder-readonly ESC c   open a different folder in read only mode
	    check-traditional-pgp  ESC P   check for classic pgp
	    clear-flag		       W   clear a status flag from a message
	    copy-message	       C   copy a message to a file/mailbox
	    create-alias	       a   create an alias from a message sender
	    decode-copy 	   ESC C   decode a message and copy it to a file/mailbox
	    decode-save 	   ESC s   decode a message and save it to a file/mailbox
	    delete-message	       d   delete the current entry
	    delete-pattern	       D   delete messages matching a pattern
	    delete-subthread	   ESC d   delete all messages in subthread
	    delete-thread	      ^D   delete all messages in thread
	    display-address	       @   display full address of sender
	    display-toggle-weed        h   display message and toggle header weeding
	    display-message	     RET   display a message
	    edit		       e   edit the current message
	    edit-type		      ^E   edit the current message's Content-Type
	    exit		       x   exit without saving changes
	    extract-keys	      ^K   extract PGP public keys
	    fetch-mail		       G   retrieve mail from POP server
	    flag-message	       F   toggle a message's 'important' flag
	    forget-passphrase	      ^F   wipe PGP passphrase from memory
	    forward-message	       f   forward a message with comments
	    group-reply 	       g   reply to all recipients
	    limit		       l   show only messages matching a pattern
	    list-reply		       L   reply to specified mailing list
	    mail		       m   compose a new mail message
	    mail-key		   ESC k   mail a PGP public key
	    next-new		     TAB   jump to the next new message
	    next-subthread	   ESC n   jump to the next subthread
	    next-thread 	      ^N   jump to the next thread
	    next-undeleted	       j   move to the next undeleted message
	    next-unread        not bound   jump to the next unread message
	    parent-message	       P   jump to parent message in thread
	    pipe-message	       |   pipe message/attachment to a shell command
	    previous-new	 ESC TAB   jump to the previous new message
	    previous-page	       Z   move to the previous page
	    previous-subthread	   ESC p   jump to previous subthread
	    previous-thread	      ^P   jump to previous thread
	    previous-undeleted	       k   move to the last undelete message
	    previous-unread    not bound   jump to the previous unread message
	    print-message	       p   print the current entry
	    query		       Q   query external program for addresses
	    quit		       q   save changes to mailbox and quit
	    read-subthread	   ESC r   mark the current subthread as read
	    read-thread 	      ^R   mark the current thread as read
	    recall-message	       R   recall a postponed message
	    reply		       r   reply to a message
	    resend-message	   ESC e   resend message and preserve MIME structure
	    save-message	       s   save message/attachment to a file
	    set-flag		       w   set a status flag on a message
	    show-version	       V   show the Mutt version number and date
	    show-limit		   ESC l   show currently active limit pattern, if any








       The Mutt E-Mail Client							   131



	    sort-mailbox	       o   sort messages
	    sort-reverse	       O   sort messages in reverse order
	    sync-mailbox	       $   save changes to mailbox
	    tag-pattern 	       T   tag messages matching a pattern
	    tag-thread		   ESC t   tag/untag all messages in the current thread
	    toggle-new		       N   toggle a message's 'new' flag
	    toggle-write	       %   toggle whether the mailbox will be rewritten
	    undelete-message	       u   undelete the current entry
	    undelete-pattern	       U   undelete messages matching a pattern
	    undelete-subthread	   ESC u   undelete all messages in subthread
	    undelete-thread	      ^U   undelete all messages in thread
	    untag-pattern	      ^T   untag messages matching a pattern
	    view-attachments	       v   show MIME attachments


       _6_._4_._3  _p_a_g_e_r














































       The Mutt E-Mail Client							   132



	    bottom	       not bound   jump to the bottom of the message
	    bounce-message	       b   remail a message to another user
	    change-folder	       c   open a different folder
	    change-folder-readonly ESC c   open a different folder in read only mode
	    check-traditional-pgp  ESC P   check for classic pgp
	    copy-message	       C   copy a message to a file/mailbox
	    create-alias	       a   create an alias from a message sender
	    decode-copy 	   ESC C   decode a message and copy it to a file/mailbox
	    decode-save 	   ESC s   decode a message and save it to a file/mailbox
	    delete-message	       d   delete the current entry
	    delete-subthread	   ESC d   delete all messages in subthread
	    delete-thread	      ^D   delete all messages in thread
	    display-address	       @   display full address of sender
	    display-toggle-weed        h   display message and toggle header weeding
	    edit		       e   edit the current message
	    edit-type		      ^E   edit the current message's Content-Type
	    enter-command	       :   enter a muttrc command
	    exit		       i   return to the main-menu
	    extract-keys	      ^K   extract PGP public keys
	    flag-message	       F   toggle a message's 'important' flag
	    forget-passphrase	      ^F   wipe PGP passphrase from memory
	    forward-message	       f   forward a message with comments
	    group-reply 	       g   reply to all recipients
	    half-up	       not bound   move up one-half page
	    half-down	       not bound   move down one-half page
	    help		       ?   this screen
	    list-reply		       L   reply to specified mailing list
	    mail		       m   compose a new mail message
	    mail-key		   ESC k   mail a PGP public key
	    mark-as-new 	       N   toggle a message's 'new' flag
	    next-line		     RET   scroll down one line
	    next-entry		       J   move to the next entry
	    next-new		     TAB   jump to the next new message
	    next-page			   move to the next page
	    next-subthread	   ESC n   jump to the next subthread
	    next-thread 	      ^N   jump to the next thread
	    next-undeleted	       j   move to the next undeleted message
	    next-unread        not bound   jump to the next unread message
	    parent-message	       P   jump to parent message in thread
	    pipe-message	       |   pipe message/attachment to a shell command
	    previous-line      BackSpace   scroll up one line
	    previous-entry	       K   move to the previous entry
	    previous-new       not bound   jump to the previous new message
	    previous-page	       -   move to the previous page
	    previous-subthread	   ESC p   jump to previous subthread
	    previous-thread	      ^P   jump to previous thread
	    previous-undeleted	       k   move to the last undelete message
	    previous-unread    not bound   jump to the previous unread message
	    print-message	       p   print the current entry
	    quit		       Q   save changes to mailbox and quit
	    read-subthread	   ESC r   mark the current subthread as read
	    read-thread 	      ^R   mark the current thread as read
	    recall-message	       R   recall a postponed message
	    redraw-screen	      ^L   clear and redraw the screen








       The Mutt E-Mail Client							   133



	    reply		       r   reply to a message
	    save-message	       s   save message/attachment to a file
	    search		       /   search for a regular expression
	    search-next 	       n   search for next match
	    search-opposite    not bound   search for next match in opposite direction
	    search-reverse	   ESC /   search backwards for a regular expression
	    search-toggle	       \   toggle search pattern coloring
	    shell-escape	       !   invoke a command in a subshell
	    show-version	       V   show the Mutt version number and date
	    skip-quoted 	       S   skip beyond quoted text
	    sync-mailbox	       $   save changes to mailbox
	    tag-message 	       t   tag a message
	    toggle-quoted	       T   toggle display of quoted text
	    top 		       ^   jump to the top of the message
	    undelete-message	       u   undelete the current entry
	    undelete-subthread	   ESC u   undelete all messages in subthread
	    undelete-thread	      ^U   undelete all messages in thread
	    view-attachments	       v   show MIME attachments


       _6_._4_._4  _a_l_i_a_s


	    search		       /   search for a regular expression
	    search-next 	       n   search for next match
	    search-reverse	   ESC /   search backwards for a regular expression


       _6_._4_._5  _q_u_e_r_y


	    create-alias	       a   create an alias from a message sender
	    mail		       m   compose a new mail message
	    query		       Q   query external program for addresses
	    query-append	       A   append new query results to current results
	    search		       /   search for a regular expression
	    search-next 	       n   search for next match
	    search-opposite    not bound   search for next match in opposite direction
	    search-reverse	   ESC /   search backwards for a regular expression


       _6_._4_._6  _a_t_t_a_c_h




















       The Mutt E-Mail Client							   134



	    bounce-message	       b   remail a message to another user
	    collapse-parts	       v   toggle display of subparts
	    delete-entry	       d   delete the current entry
	    display-toggle-weed        h   display message and toggle header weeding
	    edit-type		      ^E   edit the current entry's Content-Type
	    extract-keys	      ^K   extract PGP public keys
	    forward-message	       f   forward a message with comments
	    group-reply 	       g   reply to all recipients
	    list-reply		       L   reply to specified mailing list
	    pipe-entry		       |   pipe message/attachment to a shell command
	    print-entry 	       p   print the current entry
	    reply		       r   reply to a message
	    resend-message	   ESC e   resend message and preserve MIME structure
	    save-entry		       s   save message/attachment to a file
	    undelete-entry	       u   undelete the current entry
	    view-attach 	     RET   view attachment using mailcap entry if necessary
	    view-mailcap	       m   force viewing of attachment using mailcap
	    view-text		       T   view attachment as text


       _6_._4_._7  _c_o_m_p_o_s_e









































       The Mutt E-Mail Client							   135



	    attach-file 	       a   attach a file(s) to this message
	    attach-message	       A   attach message(s) to this message
	    attach-key		   ESC k   attach a PGP public key
	    copy-file		       C   save message/attachment to a file
	    detach-file 	       D   delete the current entry
	    display-toggle-weed        h   display message and toggle header weeding
	    edit-bcc		       b   edit the BCC list
	    edit-cc		       c   edit the CC list
	    edit-description	       d   edit attachment description
	    edit-encoding	      ^E   edit attachment transfer-encoding
	    edit-fcc		       f   enter a file to save a copy of this message in
	    edit-from		   ESC f   edit the from: field
	    edit-file		    ^X e   edit the file to be attached
	    edit-headers	       E   edit the message with headers
	    edit		       e   edit the message
	    edit-mime		       m   edit attachment using mailcap entry
	    edit-reply-to	       r   edit the Reply-To field
	    edit-subject	       s   edit the subject of this message
	    edit-to		       t   edit the TO list
	    edit-type		      ^T   edit attachment type
	    filter-entry	       F   filter attachment through a shell command
	    forget-passphrase	      ^F   wipe PGP passphrase from memory
	    ispell		       i   run ispell on the message
	    new-mime		       n   compose new attachment using mailcap entry
	    pgp-menu		       p   show PGP options
	    pipe-entry		       |   pipe message/attachment to a shell command
	    postpone-message	       P   save this message to send later
	    print-entry 	       l   print the current entry
	    rename-file 	       R   rename/move an attached file
	    send-message	       y   send the message
	    toggle-unlink	       u   toggle whether to delete file after sending it
	    view-attach 	     RET   view attachment using mailcap entry if necessary
	    write-fcc	      w   write the message to a folder


       _6_._4_._8  _p_o_s_t_p_o_n_e


	    delete-entry	       d   delete the current entry
	    undelete-entry	       u   undelete the current entry


       _6_._4_._9  _b_r_o_w_s_e_r



















       The Mutt E-Mail Client							   136



	    change-dir		       c   change directories
	    check-new		     TAB   check mailboxes for new mail
	    enter-mask		       m   enter a file mask
	    search		       /   search for a regular expression
	    search-next 	       n   search for next match
	    search-reverse	   ESC /   search backwards for a regular expression
	    select-new		       N   select a new file in this directory
	    sort		       o   sort messages
	    sort-reverse	       O   sort messages in reverse order
	    toggle-mailboxes	     TAB   toggle whether to browse mailboxes or all files
	    view-file		   SPACE   view file
	    subscribe		       s   subscribe to current mailbox (IMAP Only)
	    unsubscribe 	       u   unsubscribe to current mailbox (IMAP Only)
	    toggle-subscribed	       T   toggle view all/subscribed mailboxes (IMAP Only)


       _6_._4_._1_0  _p_g_p


	    view-name		       %   view the key's user id
	    verify-key		       c   verify a PGP public key


       _6_._4_._1_1  _e_d_i_t_o_r


	    backspace	       BackSpace   delete the char in front of the cursor
	    backward-char	      ^B   move the cursor one character to the left
	    backward-word	   ESC b   move the cursor to the previous word
	    bol 		      ^A   jump to the beginning of the line
	    buffy-cycle 	   Space   cycle among incoming mailboxes
	    capitalize-word	   ESC c   uppercase the first character in the word
	    complete		     TAB   complete filename or alias
	    complete-query	      ^T   complete address with query
	    delete-char 	      ^D   delete the char under the cursor
	    downcase-word	   ESC l   lowercase all characters in current word
	    eol 		      ^E   jump to the end of the line
	    forward-char	      ^F   move the cursor one character to the right
	    forward-word	   ESC f   move the cursor to the next word
	    history-down       not bound   scroll down through the history list
	    history-up	       not bound   scroll up through the history list
	    kill-eol		      ^K   delete chars from cursor to end of line
	    kill-eow		   ESC d   delete chars from cursor to end of word
	    kill-line		      ^U   delete all chars on the line
	    kill-word		      ^W   delete the word in front of the cursor
	    quote-char		      ^V   quote the next typed key
	    transpose-chars    not bound   transpose character under cursor with previous
	    upcase-word 	   ESC u   uppercase all characters in current word



       _7_.  _M_i_s_c_e_l_l_a_n_y










       The Mutt E-Mail Client							   137



       _7_._1  _A_c_k_n_o_w_l_e_d_g_e_m_e_n_t_s

       Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
       back in the ELM-ME days.

       The following people have been very helpful to the development of Mutt:

       Vikas Agnihotri <vikasa@writeme.com>,

       Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,

       Aric Blumer <aric@fore.com>,

       John Capo <jc@irbs.com>,

       David Champion <dgc@uchicago.edu,

       Brendan Cully <brendan@kublai.com>,

       Liviu Daia <daia@stoilow.imar.ro>,

       Thomas E. Dickey <dickey@herndon4.his.com>,

       David DeSimone <fox@convex.hp.com>,

       Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,

       Ruslan Ermilov <ru@freebsd.org>,

       Edmund Grimley Evans <edmundo@rano.org,

       Michael Finken <finken@conware.de>,

       Sven Guckes <guckes@math.fu-berlin.de>,

       Lars Hecking <lhecking@nmrc.ie>,

       Mark Holloman <holloman@nando.net>,

       Andreas Holzmann <holzmann@fmi.uni-passau.de>,

       Marco d'Itri <md@linux.it>,

       Bjrn Jacke <bjacke@suse.com>,

       Byrial Jensen <byrial@image.dk>,

       David Jeske <jeske@igcom.net>,

       Christophe Kalt <kalt@hugo.int-evry.fr>,

       Tommi Komulainen <Tommi.Komulainen@iki.fi>,

       Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,








       The Mutt E-Mail Client							   138



       Brandon Long <blong@fiction.net>,

       Jimmy Mkel <jmy@flashback.net>,

       Lars Marowsky-Bree <lmb@pointer.in-minden.de>,

       Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,

       Andrew W. Nosenko <awn@bcs.zp.ua>,

       David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,

       Clint Olsen <olsenc@ichips.intel.com>,

       Park Myeong Seok <pms@romance.kaist.ac.kr>,

       Thomas Parmelan <tom@ankh.fr.eu.org>,

       Ollivier Robert <roberto@keltia.freenix.fr>,

       Thomas Roessler <roessler@does-not-exist.org>,

       Roland Rosenfeld <roland@spinnaker.de>,

       TAKIZAWA Takashi <taki@luna.email.ne.jp>,

       Allain Thivillon <Allain.Thivillon@alma.fr>,

       Gero Treuner <gero@faveve.uni-stuttgart.de>,

       Vsevolod Volkov <vvv@lucky.net>,

       Ken Weinert <kenw@ihs.com>

       _7_._2  _A_b_o_u_t _t_h_i_s _d_o_c_u_m_e_n_t

       This document was written in SGML, and then rendered using the sgml-tools pack-
       age.
























       The Mutt E-Mail Client							   139





































































					  CONTENTS



       1.  Introduction ............................................................ 1
	   1.1	 Mutt Home Page .................................................... 1
	   1.2	 Mailing Lists ..................................................... 1
	   1.3	 Software Distribution Sites ....................................... 1
	   1.4	 IRC ............................................................... 2
	   1.5	 USENET ............................................................ 2
	   1.6	 Copyright ......................................................... 2

       2.  Getting Started ......................................................... 2
	   2.1	 Moving Around in Menus ............................................ 2
	   2.2	 Editing Input Fields .............................................. 3
	   2.3	 Reading Mail - The Index and Pager ................................ 3
	   2.4	 Sending Mail ...................................................... 9
	   2.5	 Forwarding and Bouncing Mail ..................................... 13
	   2.6	 Postponing Mail .................................................. 14

       3.  Configuration .......................................................... 14
	   3.1	 Syntax of Initialization Files ................................... 15
	   3.2	 Defining/Using aliases ........................................... 16
	   3.3	 Changing the default key bindings ................................ 17
	   3.4	 Defining aliases for character sets  ............................. 18
	   3.5	 Setting variables based upon mailbox ............................. 19
	   3.6	 Keyboard macros .................................................. 19
	   3.7	 Using color and mono video attributes ............................ 20
	   3.8	 Ignoring (weeding) unwanted message headers ...................... 22
	   3.9	 Alternative addresses ............................................ 23
	   3.10  Mailing lists .................................................... 23
	   3.11  Using Multiple spool mailboxes ................................... 24
	   3.12  Defining mailboxes which receive mail ............................ 24
	   3.13  User defined headers ............................................. 25
	   3.14  Defining the order of headers when viewing messages .............. 26
	   3.15  Specify default save filename .................................... 26
	   3.16  Specify default Fcc: mailbox when composing ...................... 26
	   3.17  Specify default save filename and default Fcc: mailbox at once ... 27
	   3.18  Change settings based upon message recipients .................... 27
	   3.19  Change settings before formatting a message ...................... 27
	   3.20  Choosing the cryptographic key of the recipient .................. 28
	   3.21  Adding key sequences to the keyboard buffer ...................... 28
	   3.22  Executing functions .............................................. 28
	   3.23  Message Scoring .................................................. 28
	   3.24  Spam detection ................................................... 29
	   3.25  Setting variables ................................................ 30
	   3.26  Reading initialization commands from another file ................ 31
	   3.27  Removing hooks ................................................... 32

       4.  Advanced Usage ......................................................... 32
	   4.1	 Regular Expressions .............................................. 32
	   4.2	 Patterns ......................................................... 35
	   4.3	 Using Tags ....................................................... 39



					      i









	   4.4	 Using Hooks ...................................................... 39
	   4.5	 External Address Queries ......................................... 40
	   4.6	 Mailbox Formats .................................................. 41
	   4.7	 Mailbox Shortcuts ................................................ 42
	   4.8	 Handling Mailing Lists ........................................... 42
	   4.9	 Delivery Status Notification (DSN) Support ....................... 44
	   4.10  POP3 Support (OPTIONAL) .......................................... 44
	   4.11  IMAP Support (OPTIONAL) .......................................... 45
	   4.12  Managing multiple IMAP/POP accounts (OPTIONAL) ................... 46
	   4.13  Start a WWW Browser on URLs (EXTERNAL) ........................... 47
	   4.14  Compressed folders Support (OPTIONAL) ............................ 47

       5.  Mutt's MIME Support .................................................... 50
	   5.1	 Using MIME in Mutt ............................................... 50
	   5.2	 MIME Type configuration with mime.types .......................... 51
	   5.3	 MIME Viewer configuration with mailcap ........................... 52
	   5.4	 MIME Autoview .................................................... 58
	   5.5	 MIME Multipart/Alternative ....................................... 59
	   5.6	 MIME Lookup ...................................................... 59

       6.  Reference .............................................................. 59
	   6.1	 Command line options ............................................. 59
	   6.2	 Configuration Commands ........................................... 60
	   6.3	 Configuration variables .......................................... 62
	   6.4	 Functions ....................................................... 128

       7.  Miscellany ............................................................ 136
	   7.1	 Acknowledgements ................................................ 137
	   7.2	 About this document ............................................. 138



























					      ii


