_\b2_\b._\b1 _\bM_\bo_\bv_\bi_\bn_\bg _\bA_\br_\bo_\bu_\bn_\bd _\bi_\bn _\bM_\be_\bn_\bu_\bs
Information is presented in menus, very similar to ELM. Here is a table show-
- ing the common keys used to navigate menus in Mutt.
+ ing the common keys used to navigate menus in Mutt-ng.
The Mutt-ng E-Mail Client 3
Similar to many other mail clients, there are two modes in which mail is read
in Mutt-ng. 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 ``index'' in Mutt-ng. The second mode is the display of the message con-
+ tents. This is called the ``pager.''
The Mutt-ng E-Mail Client 4
+\bo c\bcl\ble\bea\bar\br-\b-f\bfl\bla\bag\bg (default: W)
Furthermore, the following flags reflect who the message is addressed to. They
- can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.3.315 , page 142) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.3.316 , page 142) variable.
+
message is to you and you only
_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 , page 89) to optionally display the number of
hidden messages if the thread is collapsed.
- See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 6.3.304 , page 139).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 6.3.305 , page 140).
_\b2_\b._\b3_\b._\b4 _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\be_\bo_\bu_\bs _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
Asks for an external Unix command and pipes the current or tagged message(s) to
it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.3.198 , page 113), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
(section 6.3.200 , page 113), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 6.3.199 , page 113) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.3.327 , page 144) control the exact behavior of this
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.3.328 , page 144) control the exact behavior of this
function.
r\bre\bes\bse\ben\bnd\bd-\b-m\bme\bes\bss\bsa\bag\bge\be
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 _\b$_\bw_\be_\be_\bd (section 6.3.328 , page 144) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 6.3.329 , page 145) 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-
(default: !)
Asks for an external Unix command and executes it. The _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section
- 6.3.327 , page 144) can be used to control whether Mutt-ng will wait for a key
+ 6.3.328 , page 144) can be used to control whether Mutt-ng 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.
a message. See also _\b$_\ba_\bs_\bk_\bc_\bc (section 6.3.10 , page 66), _\b$_\ba_\bs_\bk_\bb_\bc_\bc (section
6.3.9 , page 66), _\b$_\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt (section 6.3.17 , page 69), _\b$_\bb_\bo_\bu_\bn_\bc_\be (section
6.3.20 , page 69), and _\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 6.3.59 , page 78) for changing
- how Mutt asks these questions.
+ how Mutt-ng asks these questions.
- Mutt will then automatically start your _\b$_\be_\bd_\bi_\bt_\bo_\br (section 6.3.55 , page 77) on
- the message body. If the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.3.54 , page 77) variable is
- set, the headers will be at the top of the message in your editor. Any mes-
+ Mutt-ng will then automatically start your _\b$_\be_\bd_\bi_\bt_\bo_\br (section 6.3.55 , page 77)
+ on the message body. If the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.3.54 , page 77) 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 _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 6.3.15 , page 68), _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section
6.3.107 , page 89) and _\b$_\bp_\bo_\bs_\bt_\b__\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.3.210 , page 116).
Fcc: _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- Mutt will pick up _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be just as if you had used the _\be_\bd_\bi_\bt_\b-_\bf_\bc_\bc function in the
- _\bc_\bo_\bm_\bp_\bo_\bs_\be menu.
+ Mutt-ng will pick up _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be just as if you had used the _\be_\bd_\bi_\bt_\b-_\bf_\bc_\bc function in
+ the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu.
You can also attach files to your message by specifying
use as the description of the attached file.
When replying to messages, if you remove the _\bI_\bn_\b-_\bR_\be_\bp_\bl_\by_\b-_\bT_\bo_\b: field from the header
- field, Mutt will not generate a _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b: field, which allows you to create a
- new message thread.
+ field, Mutt-ng will not generate a _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b: field, which allows you to cre-
+ ate a new message thread.
Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.3.54 , page 77).
The Mutt-ng E-Mail Client 12
- _\b2_\b._\b4_\b._\b2 _\bU_\bs_\bi_\bn_\bg _\bM_\bu_\bt_\bt _\bw_\bi_\bt_\bh _\bP_\bG_\bP
+ _\b2_\b._\b4_\b._\b2 _\bU_\bs_\bi_\bn_\bg _\bM_\bu_\bt_\bt_\b-_\bn_\bg _\bw_\bi_\bt_\bh _\bP_\bG_\bP
If you want to use PGP, you can specify
_\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.3.190 , page 111) 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.
+ selection process when you try to send the message. Mutt-ng 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,
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
+ not use the Cc and Bcc headers. To tell Mutt-ng 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
ple, can be set to ``ask-no''.
The inclusion of headers is controlled by the current setting of the _\b$_\bw_\be_\be_\bd
- (section 6.3.328 , page 144) variable, unless _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.3.134 ,
+ (section 6.3.329 , page 145) variable, unless _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.3.134 ,
page 97) is set.
Editing the message to forward follows the same procedure as sending or reply-
to compose. When the _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be function is used in the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu,
the body of your message and attachments are stored in the mailbox specified by
the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 6.3.212 , page 116) variable. This means that you can
- recall the message even if you exit Mutt and then restart it at a later time.
+ recall the message even if you exit Mutt-ng 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 _\bc_\bo_\bm_\bp_\bo_\bs_\be a new message
_\b2_\b._\b7 _\bR_\be_\ba_\bd_\bi_\bn_\bg _\bn_\be_\bw_\bs _\bv_\bi_\ba _\bN_\bN_\bT_\bP
- If compiled with ``--enable-nntp'' option, Mutt can read news from newsserver
- via NNTP. You can open a newsgroup with function ``change-newsgroup''
- (default: i). Default newsserver can be obtained from _\bN_\bN_\bT_\bP_\bS_\bE_\bR_\bV_\bE_\bR environment
- variable. Like other news readers, info about subscribed newsgroups is saved
- in file by _\b$_\bn_\be_\bw_\bs_\br_\bc (section , page ) variable. Article headers are cached and
- can be loaded from file when newsgroup entered instead loading from newsserver.
+ If compiled with ``--enable-nntp'' option, Mutt-ng can read news from
+ newsserver via NNTP. You can open a newsgroup with function ``change-news-
+ group'' (default: i). Default newsserver can be obtained from _\bN_\bN_\bT_\bP_\bS_\bE_\bR_\bV_\bE_\bR envi-
+ ronment variable. Like other news readers, info about subscribed newsgroups is
+ saved in file by _\b$_\bn_\be_\bw_\bs_\br_\bc (section , page ) variable. Article headers are
+ cached and can be loaded from file when newsgroup entered instead loading from
+ newsserver.
_\b3_\b. _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn
While the default configuration (or ``preferences'') make Mutt-ng usable right
- out of the box, it is often desirable to tailor Mutt to suit your own tastes.
- When Mutt-ng is first invoked, it will attempt to read the ``system'' configu-
- ration file (defaults set by your local system administrator), unless the
- ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 6.1 , page 62) option is specified. This file is
- typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng users will
- find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will
- next look for a file named .muttrc in your home directory, Mutt-ng will look
- for .muttngrc. If this file does not exist and your home directory has a sub-
- directory named .mutt, mutt try to load a file named .muttng/muttngrc.
+ out of the box, it is often desirable to tailor Mutt-ng to suit your own
+ tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
+ configuration file (defaults set by your local system administrator), unless
+ the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 6.1 , page 62) option is specified. This
+ file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
+ users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
+ Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
The Mutt-ng E-Mail Client 15
+ will look for .muttngrc. If this file does not exist and your home directory
+ has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
+
.muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
- your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 6.2 , page 62) to configure Mutt.
+ your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 6.2 , page 62) to configure Mutt-ng.
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
+ ning version 0.88 of mutt, this file will be sourced instead of the Muttngrc
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
will source this file instead of the default .muttrc file. The version number
62). 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-
+ set realname='Mutt-ng 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
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.
+ The Mutt-ng E-Mail Client 16
+
Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the
end of a line also in comments. This allows you to disable a command split over
multiple lines with only one ``#''.
- The Mutt-ng E-Mail Client 16
-
# folder-hook . \
set realname="Michael \"MuttDude\" Elkins"
Usage: alias _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ The Mutt-ng E-Mail Client 17
+
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
+ are communicating with. Mutt-ng allows you to create ``aliases'' which map a
short string to a full address.
N\bNo\bot\bte\be:\b: if you want to create an alias for a group (by specifying more than one
-
- The Mutt-ng E-Mail Client 17
-
address), you m\bmu\bus\bst\bt separate the addresses with a comma (``,'').
To remove an alias or aliases (``*'' means all aliases):
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 _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.26 , page 32). Consequently, you can have
- multiple alias files, or you can have all aliases defined in your muttrc.
+ Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
+ cial file. The alias command can appear anywhere in a configuration file, as
+ long as this file is _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.26 , page 32). Consequently, you can
+ have multiple alias files, or you can have all aliases defined in your muttrc.
On the other hand, the _\bc_\br_\be_\ba_\bt_\be_\b-_\ba_\bl_\bi_\ba_\bs (section 2.3.4 , page 7) function can use
only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.3.3 , page 65)
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 _\bs_\bo_\bu_\br_\bc_\be (section 3.26 ,
- page 32) this file too.
+ the sense that Mutt-ng will happily append aliases to any file, but in order
+ for the new aliases to take effect you need to explicitly _\bs_\bo_\bu_\br_\bc_\be (section
+ 3.26 , page 32) this file too.
For example:
- source /usr/local/share/Mutt.aliases
+ source /usr/local/share/Mutt-ng.aliases
source ~/.mail_aliases
set alias_file=~/.mail_aliases
Usage: bind _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ The Mutt-ng E-Mail Client 18
+
This command allows you to change the default key bindings (operation invoked
when pressing a key).
- _\bm_\ba_\bp specifies in which menu the binding belongs. Multiple maps may be
-
- The Mutt-ng E-Mail Client 18
-
- specified by separating them with commas (no additional whitespace is allowed).
- The currently defined maps are:
+ _\bm_\ba_\bp 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
+ defined in another menu, Mutt-ng 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.
_\bk_\be_\by is the key (or key sequence) you wish to bind. To specify a control char-
acter, use the sequence _\b\_\bC_\bx, where _\bx is the letter of the control character
(for example, to specify control-A use ``\Ca''). Note that the case of _\bx as
+
+ The Mutt-ng E-Mail Client 19
+
well as _\b\_\bC is ignored, so that _\b\_\bC_\bA, _\b\_\bC_\ba, _\b\_\bc_\bA and _\b\_\bc_\ba are all equivalent. An
alternative form is to specify the key as a three digit octal number prefixed
with a ``\'' (for example _\b\_\b1_\b7_\b7 is equivalent to _\b\_\bc_\b?).
- The Mutt-ng E-Mail Client 19
-
In addition, _\bk_\be_\by may consist of:
\t tab
Usage: folder-hook [!]_\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ The Mutt-ng E-Mail Client 20
+
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. _\br_\be_\bg_\be_\bx_\bp is a regular expression specifying in which
-
- The Mutt-ng E-Mail Client 20
-
mailboxes to execute _\bc_\bo_\bm_\bm_\ba_\bn_\bd before loading. If a mailbox matches multiple
folder-hook's, they are executed in the order given in the muttrc.
Usage: macro _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
Macros are useful when you would like a single key to perform a series of
- actions. When you press _\bk_\be_\by in menu _\bm_\be_\bn_\bu, Mutt will behave as if you had typed
- _\bs_\be_\bq_\bu_\be_\bn_\bc_\be. 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.
+ actions. When you press _\bk_\be_\by in menu _\bm_\be_\bn_\bu, Mutt-ng will behave as if you had
+ typed _\bs_\be_\bq_\bu_\be_\bn_\bc_\be. So if you have a common sequence of commands you type, you can
+ create a macro to execute those commands with a single key.
_\bm_\be_\bn_\bu is the _\bm_\ba_\bp (section 3.3 , page 17) which the macro will be bound. Multi-
ple maps may be specified by separating multiple menu arguments by commas.
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).
+ (eg. the system Muttngrc).
+
+ The Mutt-ng E-Mail Client 21
Optionally you can specify a descriptive text after _\bs_\be_\bq_\bu_\be_\bn_\bc_\be, which is shown in
the help screens.
- The Mutt-ng E-Mail Client 21
-
N\bNo\bot\bte\be:\b: Macro definitions (if any) listed in the help screen(s), are silently
truncated at the screen width, and are not wrapped.
Usage: uncolor index _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- If your terminal supports color, you can spice up Mutt by creating your own
+ If your terminal supports color, you can spice up Mutt-ng by creating your own
color scheme. To define the color of an object (type of information), you must
specify both a foreground color a\ban\bnd\bd a background color (it is not possible to
only specify one or the other).
+\bo bold (highlighting bold patterns in the body of messages)
- +\bo error (error messages printed by Mutt)
+ +\bo error (error messages printed by Mutt-ng)
+\bo header (match _\br_\be_\bg_\be_\bx_\bp in the message header)
+\bo status (mode lines used to display info about the mailbox or message)
- +\bo tilde (the ``~'' used to pad blank lines in the pager)
-
The Mutt-ng E-Mail Client 22
+ +\bo tilde (the ``~'' used to pad blank lines in the pager)
+
+\bo tree (thread tree drawn in the message index and attachment menu)
+\bo underline (highlighting underlined patterns in the body of messages)
ground color boldfaced (e.g., brightred).
If your terminal supports it, the special keyword _\bd_\be_\bf_\ba_\bu_\bl_\bt can be used as a
- transparent color. The value _\bb_\br_\bi_\bg_\bh_\bt_\bd_\be_\bf_\ba_\bu_\bl_\bt is also valid. If Mutt is linked
- against the _\bS_\b-_\bL_\ba_\bn_\bg library, you also need to set the _\bC_\bO_\bL_\bO_\bR_\bF_\bG_\bB_\bG environment
- variable to the default colors of your terminal for this to work; for example
- (for Bourne-like shells):
+ transparent color. The value _\bb_\br_\bi_\bg_\bh_\bt_\bd_\be_\bf_\ba_\bu_\bl_\bt is also valid. If Mutt-ng is
+ linked against the _\bS_\b-_\bL_\ba_\bn_\bg library, you also need to set the _\bC_\bO_\bL_\bO_\bR_\bF_\bG_\bB_\bG environ-
+ ment variable to the default colors of your terminal for this to work; for
+ example (for Bourne-like shells):
set COLORFGBG="green;black"
export COLORFGBG
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 _\bc_\bo_\bl_\bo_\br_\b0, _\bc_\bo_\bl_\bo_\br_\b1, ..., _\bc_\bo_\bl_\bo_\brN\bN-\b-1\b1 (N\bN being the
+ Mutt-ng also recognizes the keywords _\bc_\bo_\bl_\bo_\br_\b0, _\bc_\bo_\bl_\bo_\br_\b1, ..., _\bc_\bo_\bl_\bo_\brN\bN-\b-1\b1 (N\bN 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
_\bc_\bo_\bl_\bo_\br_\b2 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
-
The Mutt-ng E-Mail Client 23
+ If your terminal does not support color, it is still possible change the video
attributes through the use of the ``mono'' command:
Usage: mono _\b<_\bo_\bb_\bj_\be_\bc_\bt_\b> _\b<_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be_\b> [ _\br_\be_\bg_\be_\bx_\bp ]
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''.
+ The ``unignore'' command will make Mutt-ng display headers with the given pat-
+ tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
+ mailer''.
``unignore *'' will remove all tokens from the ignore list.
Usage: [un]alternates _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
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
The Mutt-ng E-Mail Client 24
+ 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
_\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 6.3.231 , page 120).)
Usage: [un]subscribe _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- Mutt has a few nice features for _\bh_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bm_\ba_\bi_\bl_\bi_\bn_\bg _\bl_\bi_\bs_\bt_\bs (section 4.9 , page
+ Mutt-ng has a few nice features for _\bh_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bm_\ba_\bi_\bl_\bi_\bn_\bg _\bl_\bi_\bs_\bt_\bs (section 4.9 , page
44). 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 _\bl_\bi_\bs_\bt_\b-_\br_\be_\bp_\bl_\by (section 2.3.4 , page 8) function will work
header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.3.65 , page 80) configura-
tion 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,
+ More precisely, Mutt-ng 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
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
- addressed to _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs_\b@_\bm_\bu_\bt_\bt_\b._\bo_\br_\bg. So, to tell Mutt that this is a mailing
- list, you could add ``lists mutt-users'' to your initialization file. To tell
+ ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
The Mutt-ng E-Mail Client 25
+ addressed to _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs_\b@_\bm_\bu_\bt_\bt_\b._\bo_\br_\bg. So, to tell Mutt-ng 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 _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs_\b@_\be_\bx_\ba_\bm_\bp_\bl_\be_\b._\bc_\bo_\bm, you could use ``lists mutt-
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.
+ Mutt-ng will automatically enter this mode when invoked from the command line
+ with the -y option.
The ``unmailboxes'' command is used to remove a token from the list of folders
which receive mail. Use ``unmailboxes *'' to remove all tokens.
N\bNo\bot\bte\be:\b: 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.
+ the mailbox might cause Mutt-ng 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.
N\bNo\bot\bte\be:\b: the filenames in the mailboxes command are resolved when the command is
executed, so if these names contain _\bs_\bh_\bo_\br_\bt_\bc_\bu_\bt _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br_\bs (section 4.8 , page
44) (such as ``='' and ``!''), any variable definition that affect these char-
acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.3.63 , page 79) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 6.3.293 , page 135)) should be executed before the mailboxes command.
The Mutt-ng E-Mail Client 26
+ 6.3.293 , page 135)) should be executed before the mailboxes command.
+
_\b3_\b._\b1_\b3 _\bU_\bs_\be_\br _\bd_\be_\bf_\bi_\bn_\be_\bd _\bh_\be_\ba_\bd_\be_\br_\bs
Usage:
N\bNo\bot\bte\be:\b: space characters are _\bn_\bo_\bt allowed between the keyword and the colon
(``:''). The standard for electronic mail (RFC822) says that space is illegal
- there, so Mutt enforces the rule.
+ there, so Mutt-ng enforces the rule.
If you would like to add a header field to a single message, you should either
set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.3.54 , page 77) variable, or use the _\be_\bd_\bi_\bt_\b-
hdr_order From Date: From: To: Cc: Subject:
- _\b3_\b._\b1_\b5 _\bS_\bp_\be_\bc_\bi_\bf_\by _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
-
The Mutt-ng E-Mail Client 27
+ _\b3_\b._\b1_\b5 _\bS_\bp_\be_\bc_\bi_\bf_\by _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+
Usage: save-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
This command is used to override the default filename used when saving mes-
Usage: fcc-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is used to save outgoing mail in a mailbox other than _\b$_\br_\be_\bc_\bo_\br_\bd
- (section 6.3.228 , page 120). Mutt searches the initial list of message
+ (section 6.3.228 , page 120). Mutt-ng searches the initial list of message
recipients for the first matching _\br_\be_\bg_\be_\bx_\bp and uses _\bm_\ba_\bi_\bl_\bb_\bo_\bx as the default Fcc:
mailbox. If no match is found the message will be saved to _\b$_\br_\be_\bc_\bo_\br_\bd (section
6.3.228 , page 120) mailbox.
Usage: send2-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- These commands can be used to execute arbitrary configuration commands based
-
The Mutt-ng E-Mail Client 28
+ These commands can be used to execute arbitrary configuration commands based
upon recipients of the message. _\bp_\ba_\bt_\bt_\be_\br_\bn is a regular expression matching the
desired address. _\bc_\bo_\bm_\bm_\ba_\bn_\bd is executed when _\br_\be_\bg_\be_\bx_\bp matches recipients of the
message.
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.
+ some reasons, you need to override the key Mutt-ng 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.
Usage: nospam _\bp_\ba_\bt_\bt_\be_\br_\bn
- Mutt has generalized support for external spam-scoring filters. By defining
+ Mutt-ng has generalized support for external spam-scoring filters. By defining
your spam patterns with the spam and nospam commands, you can _\bl_\bi_\bm_\bi_\bt, _\bs_\be_\ba_\br_\bc_\bh,
and _\bs_\bo_\br_\bt 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
_\b4_\b._\b1 _\bR_\be_\bg_\bu_\bl_\ba_\br _\bE_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs
- All string patterns in Mutt including those in more complex _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section
- 4.2 , page 36) 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.
+ All string patterns in Mutt-ng including those in more complex _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
+ tion 4.2 , page 36) 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 Mutt-ng E-Mail Client 34
over alternation. A whole subexpression may be enclosed in parentheses to
override these precedence rules.
- N\bNo\bot\bte\be:\b: If you compile Mutt with the GNU _\br_\bx package, the following operators may
- also be used in regular expressions:
+ N\bNo\bot\bte\be:\b: If you compile Mutt-ng with the GNU _\br_\bx 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
_\b4_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
- Many of Mutt's commands allow you to specify a pattern to match (limit, tag-
+ Many of Mutt-ng'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-ng E-Mail Client 38
+
~A all messages
~b EXPR messages which contain EXPR in the message body
~B EXPR messages which contain EXPR in the whole message
~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
+ ~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
~T tagged messages
~t USER messages addressed to USER
~U unread messages
- ~v message is part of a collapsed thread.
- ~V cryptographically verified messages
+ ~v message is part of a collapsed thread.
+ ~V cryptographically verified messages
+ ~w EXPR messages which contain EXPR in the `Newsgroups' field
+ (if compiled with NNTP support)
~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)
- ~* ``From'' contains realname and (syntactically) valid
- address (excluded are addresses matching against
-
- The Mutt-ng E-Mail Client 38
-
- alternates or any alias)
+ ~= duplicated messages (see $duplicate_threads)
+ ~$ unreferenced messages (requires threaded view)
+ ~* ``From'' contains realname and (syntactically) valid
+ address (excluded are addresses matching against
+ alternates or any alias)
Where EXPR, USER, ID, and SUBJECT are _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs (section 4.1 , page
33). 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 (\\).
+ patterns. Specifically, Mutt-ng'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 backslashes instead (\\).
+
+ The Mutt-ng E-Mail Client 39
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
would select messages which contain the word ``mutt'' in the list of recipients
a\ban\bnd\bd that have the word ``elkins'' in the ``From'' header field.
- Mutt also recognizes the following operators to create more complex search pat-
- terns:
+ Mutt-ng also recognizes the following operators to create more complex search
+ patterns:
+\bo ! -- logical NOT operator
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
-
- The Mutt-ng E-Mail Client 39
-
- +SomeoneElse'':
+ +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 m\bmu\bus\bst\bt enclose the expression in double or single quotes since those
- characters are also used to separate different parts of Mutt's pattern lan-
+ characters are also used to separate different parts of Mutt-ng's pattern lan-
guage. For example,
+ The Mutt-ng E-Mail Client 40
+
~f "me@(mutt\.org|cs\.hmc\.edu)"
Without the quotes, the parenthesis wouldn't end. This would be separated to
_\b4_\b._\b2_\b._\b3 _\bS_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg _\bb_\by _\bD_\ba_\bt_\be
- Mutt supports two types of dates, _\ba_\bb_\bs_\bo_\bl_\bu_\bt_\be and _\br_\be_\bl_\ba_\bt_\bi_\bv_\be.
+ Mutt-ng supports two types of dates, _\ba_\bb_\bs_\bo_\bl_\bu_\bt_\be and _\br_\be_\bl_\ba_\bt_\bi_\bv_\be.
A\bAb\bbs\bso\bol\blu\but\bte\be. Dates m\bmu\bus\bst\bt 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
Example: To select any messages two weeks around January 15, 2001, you'd use
the following pattern:
- The Mutt-ng E-Mail Client 40
-
Limit to messages matching: ~d 15/1/2001*2w
R\bRe\bel\bla\bat\bti\biv\bve\be. This type of date is relative to the current date, and may be speci-
+\bo =_\bo_\bf_\bf_\bs_\be_\bt (messages exactly _\bo_\bf_\bf_\bs_\be_\bt units old)
+ The Mutt-ng E-Mail Client 41
+
_\bo_\bf_\bf_\bs_\be_\bt is specified as a positive number with one of the following units:
y years
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 _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 4.2 , page 36) for Mutt's pattern matching
+ default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 4.2 , page 36) for Mutt-ng's pattern matching
syntax.
Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
In _\bm_\ba_\bc_\br_\bo_\bs (section 3.6 , page 20) or _\bp_\bu_\bs_\bh (section 3.21 , page 29) 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.
-
- The Mutt-ng E-Mail Client 41
+ mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng 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.
_\b4_\b._\b4 _\bU_\bs_\bi_\bn_\bg _\bH_\bo_\bo_\bk_\bs
A _\bh_\bo_\bo_\bk 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 _\bh_\bo_\bo_\bk consists of a _\br_\be_\bg_\bu_\bl_\ba_\br
+ whom you are sending mail. In the Mutt-ng world, a _\bh_\bo_\bo_\bk consists of a _\br_\be_\bg_\bu_\bl_\ba_\br
_\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 33) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 4.2 , page 36) along
with a configuration option/command. See
+\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.5 , page 19)
+ The Mutt-ng E-Mail Client 42
+
+\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 27)
+\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 28)
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 _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 4.2 , page 36) language for
- matching messages in hook commands. This works in exactly the same way as it
- would when _\bl_\bi_\bm_\bi_\bt_\bi_\bn_\bg or _\bs_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg the mailbox, except that you are restricted to
- those operators which match information mutt extracts from the header of the
+ Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 4.2 , page 36) language
+ for matching messages in hook commands. This works in exactly the same way as
+ it would when _\bl_\bi_\bm_\bi_\bt_\bi_\bn_\bg or _\bs_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg 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>'
-
- The Mutt-ng E-Mail Client 42
+ send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
which would execute the given command when sending mail to _\bm_\be_\b@_\bc_\bs_\b._\bh_\bm_\bc_\b._\be_\bd_\bu.
However, it is not required that you write the pattern to match using the full
searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the
- other hooks, in which case Mutt will translate your pattern into the full lan-
- guage, using the translation specified by the _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.3.45 ,
- page 75) variable. The pattern is translated at the time the hook is declared,
- so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.3.45 , page 75) that is in effect at
- that time will be used.
+ other hooks, in which case Mutt-ng will translate your pattern into the full
+ language, using the translation specified by the _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section
+ 6.3.45 , page 75) variable. The pattern is translated at the time the hook is
+ declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.3.45 , page 75) that is in
+ effect at that time will be used.
+
+ The Mutt-ng E-Mail Client 43
_\b4_\b._\b5 _\bU_\bs_\bi_\bn_\bg _\bt_\bh_\be _\bs_\bi_\bd_\be_\bb_\ba_\br
Reasonable key bindings look e.g. like this:
- The Mutt-ng E-Mail Client 43
-
bind index \Cp sidebar-prev
bind index \Cn sidebar-next
bind index \Cb sidebar-open
_\b4_\b._\b6 _\bE_\bx_\bt_\be_\br_\bn_\ba_\bl _\bA_\bd_\bd_\br_\be_\bs_\bs _\bQ_\bu_\be_\br_\bi_\be_\bs
- 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 _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.3.219 , page 118) variable,
- you specify the wrapper command to use. For example:
+ The Mutt-ng E-Mail Client 44
+
+ Mutt-ng 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 _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.3.219 , page 118) vari-
+ able, you specify the wrapper command to use. For example:
set query_command = "mutt_ldap_query.pl '%s'"
will activate the query menu. At the query menu, you can select one or more
addresses to be added to the prompt.
- The Mutt-ng E-Mail Client 44
-
_\b4_\b._\b7 _\bM_\ba_\bi_\bl_\bb_\bo_\bx _\bF_\bo_\br_\bm_\ba_\bt_\bs
- Mutt supports reading and writing of four different mailbox formats: mbox,
+ Mutt-ng 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 _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.3.123 , page 95) vari-
- able.
+ use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.3.123 , page 95)
+ variable.
m\bmb\bbo\box\bx. 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-ng E-Mail Client 45
+
to denote the start of a new message (this is often referred to as the
``From_'' line).
M\bMH\bH. A radical departure from _\bm_\bb_\bo_\bx and _\bM_\bM_\bD_\bF, 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
+ sage number (however, this is may not correspond to the message number Mutt-ng
displays). Deleted messages are renamed with a comma (,) prepended to the file-
name. N\bNo\bot\bte\be:\b: Mutt detects this type of mailbox by looking for either
.mh_sequences or .xmhcache (needed to distinguish normal directories from MH
+\bo ~ -- refers to your home directory
- The Mutt-ng E-Mail Client 45
-
+\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.3.63 , page 79) directory
+\bo @_\ba_\bl_\bi_\ba_\bs -- refers to the _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bo_\bl_\bd_\be_\br (section 3.15 , page 26) as
_\b4_\b._\b9 _\bH_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bM_\ba_\bi_\bl_\bi_\bn_\bg _\bL_\bi_\bs_\bt_\bs
- Mutt has a few configuration options that make dealing with large amounts of
+ Mutt-ng 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 _\bl_\bi_\bs_\bt_\bs _\ba_\bn_\bd _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be
(section 3.10 , page 24) 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
+ Now that Mutt-ng knows what your mailing lists are, it can do several things,
+
+ The Mutt-ng E-Mail Client 46
+
+ 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 _\bi_\bn_\bd_\be_\bx menu display.
This is useful to distinguish between personal and list mail in the same mail-
box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 , page 89) variable, the escape
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 _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.3.65 , page 80) 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.
+ Mutt-ng 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 _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.3.65 , page 80) option is set, mutt will
+ generate a Mail-Followup-To header which contains all the recipients to whom
+ you send this message, but not your address. This indicates that group-replies
+ or list-replies (also known as ``followups'') to this message should only be
+ sent to the original recipients of the message, and not separately to you -
+ you'll receive your copy through one of the mailing lists you are subscribed
+ to.
Conversely, when group-replying or list-replying to a message which has a Mail-
Followup-To header, mutt will respect this header if the _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
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.
+ header manually. Mutt-ng 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
-
- The Mutt-ng E-Mail Client 46
-
- address given in the ``Reply-To'' field. Mutt uses the _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section
+ address given in the ``Reply-To'' field. Mutt-ng uses the _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section
6.3.231 , page 120) variable to help decide which address to use. If set to
_\ba_\bs_\bk_\b-_\by_\be_\bs or _\ba_\bs_\bk_\b-_\bn_\bo, 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
The ``X-Label:'' header field can be used to further identify mailing lists or
list subject matter (or just to annotate messages individually). The
_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 , page 89) variable's ``%y'' and ``%Y'' escapes
- can be used to expand ``X-Label:'' fields in the index, and Mutt's pattern-
+ can be used to expand ``X-Label:'' fields in the index, and Mutt-ng'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 _\bs_\bo_\br_\bt (section 6.3.287 , page 133) the mailbox
- into _\bt_\bh_\br_\be_\ba_\bd_\bs (section 2.3.3 , page 7). A thread is a group of messages which
- all relate to the same subject. This is usually organized into a tree-like
- structure where a message and all of its replies are represented graphically.
- If you've ever used a threaded news client, this is the same concept. It makes
- dealing with large volume mailing lists easier because you can easily delete
- uninteresting threads and quickly find topics of value.
+ The Mutt-ng E-Mail Client 47
+
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 6.3.287 , page 133) the mail-
+ box into _\bt_\bh_\br_\be_\ba_\bd_\bs (section 2.3.3 , page 7). A thread is a group of messages
+ which all relate to the same subject. This is usually organized into a tree-
+ like structure where a message and all of its replies are represented graphi-
+ cally. 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.
_\b4_\b._\b1_\b0 _\bE_\bd_\bi_\bt_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
- Mutt has the ability to dynamically restructure threads that are broken either
- by misconfigured software or bad behavior from some correspondents. This allows
- to clean your mailboxes formats) from these annoyances which make it hard to
- follow a discussion.
+ Mutt-ng has the ability to dynamically restructure threads that are broken
+ either by misconfigured software or bad behavior from some correspondents. This
+ allows to clean your mailboxes formats) from these annoyances which make it
+ hard to follow a discussion.
_\b4_\b._\b1_\b0_\b._\b1 _\bL_\bi_\bn_\bk_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
ences:" headers when replying to a message. This results in broken discussions
- because Mutt has not enough information to guess the correct threading. You
+ because Mutt-ng has not enough information to guess the correct threading. You
can fix this by tagging the reply, then moving to the parent message and using
the ``link-threads'' function (bound to & by default). The reply will then be
connected to this "parent" message.
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
-
- The Mutt-ng E-Mail Client 47
-
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.
_\b4_\b._\b1_\b2 _\bP_\bO_\bP_\b3 _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
- If Mutt was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+ If Mutt-ng was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bp_\bo_\bp flag), it has the ability to work with mailboxes located on a
remote POP3 server and fetch mail for local browsing.
+ The Mutt-ng E-Mail Client 48
+
You can access the remote POP3 mailbox by selecting the folder
pop://popserver/.
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 _\b$_\bp_\bo_\bp_\b__\bc_\bh_\be_\bc_\bk_\bi_\bn_\bt_\be_\br_\bv_\ba_\bl (section , page ) variable, which defaults to every 60
- seconds.
-
- If Mutt was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with the
- _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl 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-
+ the frequency at which Mutt-ng will check for mail remotely can be controlled
+ by the _\b$_\bp_\bo_\bp_\b__\bc_\bh_\be_\bc_\bk_\bi_\bn_\bt_\be_\br_\bv_\ba_\bl (section , page ) variable, which defaults to every
+ 60 seconds.
+
+ If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+ the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to POP3 servers can be encrypted. This natu-
+ rally 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 _\bf_\be_\bt_\bc_\bh_\b-_\bm_\ba_\bi_\bl function (default: G).
It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 6.3.204 , page 114), fetch all your
new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.3.293 , page 135).
- After this point, Mutt runs exactly as if the mail had always been local.
+ After this point, Mutt-ng runs exactly as if the mail had always been local.
N\bNo\bot\bte\be:\b: If you only need to fetch all messages to local mailbox you should con-
sider using a specialized program, such as fetchmail
_\b4_\b._\b1_\b3 _\bI_\bM_\bA_\bP _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
- If Mutt was compiled with IMAP support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+ If Mutt-ng was compiled with IMAP support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bi_\bm_\ba_\bp flag), it has the ability to work with folders located on a
remote IMAP server.
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
-
- The Mutt-ng E-Mail Client 48
-
imap://imapserver/path/to/folder where path/to/folder is the path of the folder
you want to access.
You can also specify different username for each folder, i.e.: imap://user-
name@imapserver[:port]/INBOX.
- If Mutt was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with the
- _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl 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-
+ If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+ the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This natu-
+ rally 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, i.e. {[user-
- name@]imapserver[:port][/ssl]}path/to/folder
+ Pine-compatible notation is also supported, i.e.
- 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
+ The Mutt-ng E-Mail Client 49
+
+ {[username@]imapserver[:port][/ssl]}path/to/folder
+
+ Note that not all servers use / as the hierarchy separator. Mutt-ng should
+ correctly 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
Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.3.97 , page 87) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.3.313 , page 141) variables.
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.3.314 , page 142) variables.
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
respectively). You may also subscribe and unsubscribe to mailboxes (nor-
mally these are bound to s and u, respectively).
- The Mutt-ng E-Mail Client 49
-
_\b4_\b._\b1_\b3_\b._\b2 _\bA_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bi_\bo_\bn
- Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI,
+ Mutt-ng 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,
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
+
+ The Mutt-ng E-Mail Client 50
+
and compile mutt with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\ba_\bs_\bl flag.
- Mutt will try whichever methods are compiled in and available on the server, in
- the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
+ Mutt-ng 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:
_\b4_\b._\b1_\b5 _\bS_\bt_\ba_\br_\bt _\ba _\bW_\bW_\bW _\bB_\br_\bo_\bw_\bs_\be_\br _\bo_\bn _\bU_\bR_\bL_\bs _\b(_\bE_\bX_\bT_\bE_\bR_\bN_\bA_\bL_\b)
If a message contains URLs (_\bu_\bn_\bi_\bf_\bi_\be_\bd _\br_\be_\bs_\bo_\bu_\br_\bc_\be _\bl_\bo_\bc_\ba_\bt_\bo_\br = address in the WWW space
-
- The Mutt-ng E-Mail Client 50
-
like _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bm_\bu_\bt_\bt_\b._\bo_\br_\bg_\b/), 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-
_\b4_\b._\b1_\b6 _\bC_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
- If Mutt was compiled with compressed folders support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
- script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd 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.
+ If Mutt-ng was compiled with compressed folders support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\b-
+ _\bu_\br_\be script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd 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 Mutt-ng E-Mail Client 51
The most common use is to open compressed archived folders e.g. with gzip.
empty command) , the folder will be open in the mode. If you specify _\ba_\bp_\bp_\be_\bn_\bd_\b-
_\bh_\bo_\bo_\bk (section 4.16.3 , page 51) 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
+ Note that Mutt-ng 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-
Usage: open-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
- The Mutt-ng E-Mail Client 51
-
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd is the command that can be used for opening the folders whose names
match _\br_\be_\bg_\be_\bx_\bp.
Example:
+ The Mutt-ng E-Mail Client 52
+
open-hook \\.gz$ "gzip -cd %f > %t"
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type.
Usage: append-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
This command is used for saving to an existing compressed folder. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
-
- The Mutt-ng E-Mail Client 52
-
is the command that can be used for appending to the folders whose names match
_\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.16.1 , page 50)
command. The temporary folder in this case contains the messages that are
When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.16.3 , page 51) 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 (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.3.123 , page 95)) type is always
+
+ The Mutt-ng E-Mail Client 53
+
supposed (i.e. this is the format used for the temporary folder).
If the file does not exist when you save to it, _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.16.2 ,
can be read by your system administrator. So think about the security aspects
of this.
- _\b5_\b. _\bM_\bu_\bt_\bt_\b'_\bs _\bM_\bI_\bM_\bE _\bS_\bu_\bp_\bp_\bo_\br_\bt
+ _\b5_\b. _\bM_\bu_\bt_\bt_\b-_\bn_\bg_\b'_\bs _\bM_\bI_\bM_\bE _\bS_\bu_\bp_\bp_\bo_\br_\bt
- Quite a bit of effort has been made to make Mutt the premier text-mode MIME
+ Quite a bit of effort has been made to make Mutt-ng 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
-
- The Mutt-ng E-Mail Client 53
-
- specifies the external commands to use for handling specific MIME types.
+ When configuring Mutt-ng for MIME, there are two extra types of configuration
+ files which Mutt-ng uses. One is the mime.types file, which contains the map-
+ ping 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.
_\b5_\b._\b1 _\bU_\bs_\bi_\bn_\bg _\bM_\bI_\bM_\bE _\bi_\bn _\bM_\bu_\bt_\bt
- There are three areas/menus in Mutt which deal with MIME, they are the pager
+ There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
(while viewing a message), the attachment menu and the compose menu.
_\b5_\b._\b1_\b._\b1 _\bV_\bi_\be_\bw_\bi_\bn_\bg _\bM_\bI_\bM_\bE _\bm_\be_\bs_\bs_\ba_\bg_\be_\bs _\bi_\bn _\bt_\bh_\be _\bp_\ba_\bg_\be_\br
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
+ the message to a text representation. Mutt-ng 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
+ sage/news. In addition, the export controlled version of Mutt-ng 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:
+ Mutt-ng will denote attachments with a couple lines describing them. These
+ lines are of the form:
+
+ The Mutt-ng E-Mail Client 54
[-- 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:
+ If Mutt-ng cannot deal with a MIME type, it will display a message like:
[-- image/gif is unsupported (use 'v' to view this part) --]
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
-
- The Mutt-ng E-Mail Client 54
-
modifying the attachment information, notably the type, encoding and descrip-
tion.
- 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
- canceling) the message. It can be toggled with the toggle-unlink command
+ The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
+ or canceling) 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
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
+
+ The Mutt-ng E-Mail Client 55
+
attachment, and can be changed with the edit-description command (default: d).
_\b5_\b._\b2 _\bM_\bI_\bM_\bE _\bT_\by_\bp_\be _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bw_\bi_\bt_\bh _\bm_\bi_\bm_\be_\b._\bt_\by_\bp_\be_\bs
- When you add an attachment to your mail message, Mutt searches your personal
+ When you add an attachment to your mail message, Mutt-ng 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
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.
+ A sample mime.types file comes with the Mutt-ng distribution, and should con-
+ tain 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
+ If Mutt-ng can not determine the mime type by the extension of the file you
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
+ Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
+ the file contains binary information, then Mutt-ng will mark it as applica-
+ tion/octet-stream. You can change the MIME type that Mutt-ng 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
+ been approved after various internet discussions. Mutt-ng recognises all of
+ these if the appropriate entry is found in the mime.types file. It also recog-
+ nises 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
+ various molecular viewers. Non-recognised mime types should only be used if the
recipient of the message is likely to be expecting such attachments.
_\b5_\b._\b3 _\bM_\bI_\bM_\bE _\bV_\bi_\be_\bw_\be_\br _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bw_\bi_\bt_\bh _\bm_\ba_\bi_\bl_\bc_\ba_\bp
- The Mutt-ng E-Mail Client 55
-
- 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.
+ Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
+ format 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
+ In order to handle various MIME types that Mutt-ng can not handle internally,
+ Mutt-ng 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
+
+ The Mutt-ng E-Mail Client 56
+
as /usr/local/etc/mailcap, which contains some baseline entries.
_\b5_\b._\b3_\b._\b1 _\bT_\bh_\be _\bB_\ba_\bs_\bi_\bc_\bs _\bo_\bf _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be
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 behavior 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.
+ %s as a parameter to your view command. This will cause Mutt-ng 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-ng
+ 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
- The Mutt-ng E-Mail Client 56
-
Or, you could send the message as a file:
text/plain; more %s
_\bv_\bi_\be_\bw _\bt_\bh_\be _\bo_\bb_\bj_\be_\bc_\bt_\b.
On the other hand, maybe you don't want to use lynx interactively, you just
+
+ The Mutt-ng E-Mail Client 57
+
want to have it convert the text/html to text/plain, then you can use:
text/html; lynx -dump %s | more
_\b5_\b._\b3_\b._\b2 _\bS_\be_\bc_\bu_\br_\be _\bu_\bs_\be _\bo_\bf _\bm_\ba_\bi_\bl_\bc_\ba_\bp
The interpretation of shell meta-characters embedded in MIME parameters can
- lead to security problems in general. Mutt tries to quote parameters in expan-
- sion of %s syntaxes properly, and avoids risky characters by substituting them,
- see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 6.3.115 , page 93) variable.
+ lead to security problems in general. Mutt-ng tries to quote parameters in
+ expansion of %s syntaxes properly, and avoids risky characters by substituting
+ them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 6.3.115 , page 93) variable.
Although mutt's procedures to invoke programs with mailcap seem to be safe,
there are other applications parsing mailcap, maybe taking less care of it.
Therefore you should pay attention to the following rules:
_\bK_\be_\be_\bp _\bt_\bh_\be _\b%_\b-_\be_\bx_\bp_\ba_\bn_\bd_\bo_\bs _\ba_\bw_\ba_\by _\bf_\br_\bo_\bm _\bs_\bh_\be_\bl_\bl _\bq_\bu_\bo_\bt_\bi_\bn_\bg_\b. 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
+ double quotes. Mutt-ng does this for you, the right way, as should any other
+ program 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.
inside the backtick expansion is safe, since it is not itself subject to any
further expansion):
- The Mutt-ng E-Mail Client 57
-
text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
_\b5_\b._\b3_\b._\b3_\b._\b1 _\bO_\bp_\bt_\bi_\bo_\bn_\ba_\bl _\bF_\bi_\be_\bl_\bd_\bs
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-
+ semi-colon ';' separated fields to set flags and other options. Mutt-ng 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:
+ This flag tells Mutt-ng that the command passes possibly large
+ amounts of text on stdout. This causes Mutt-ng to invoke a pager
+
+ The Mutt-ng E-Mail Client 58
+
+ (either the internal pager or the external pager defined by the
+ pager variable) on the output of the view command. Without this
+ flag, Mutt-ng 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.
+ and Mutt-ng will use your standard pager to display the results.
needsterminal
- Mutt uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section
- 5.4 , page 60), in order to decide whether it should honor the
- setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.3.327 , page 144) variable or
- not. When an attachment is viewed using an interactive program,
- and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt
- will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.3.327 , page 144) and the exit sta-
- tus of the program to decide if it will ask you to press a key
+ Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
+ tion 5.4 , page 60), in order to decide whether it should honor
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.3.328 , page 144) variable
+ or not. When an attachment is viewed using an interactive program,
+ and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt-
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.3.328 , page 144) and the exit
+ status 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.
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.
+ of a specific MIME type. Mutt-ng 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.
+ for a new attachment. Mutt-ng 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.
+ type. Mutt-ng supports this from the attachment and compose menus.
edit=<command>
This flag specifies the command to use to edit a specific MIME
-
- The Mutt-ng E-Mail Client 58
-
- 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.
+ type. Mutt-ng supports this from the compose menu, and also uses
+ it to compose new attachments. Mutt-ng will default to the defined
+ editor for text attachments.
nametemplate=<template>
This field specifies the format for the file denoted by %s in the
.html. So, you would specify lynx as a text/html viewer with a
line in the mailcap file like:
+ The Mutt-ng E-Mail Client 59
+
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. N\bNo\bot\bte\be:\b: _\bt_\bh_\be _\bc_\bo_\bn_\bt_\be_\bn_\bt_\b-_\bt_\by_\bp_\be _\bm_\bu_\bs_\bt _\bm_\ba_\bt_\bc_\bh
- _\bb_\be_\bf_\bo_\br_\be _\bM_\bu_\bt_\bt _\bp_\be_\br_\bf_\bo_\br_\bm_\bs _\bt_\bh_\be _\bt_\be_\bs_\bt_\b. For example:
+ returns 0, then the test passed, and Mutt-ng uses this entry. If
+ the command returns non-zero, then the test failed, and Mutt-ng
+ continues searching for the right entry. N\bNo\bot\bte\be:\b: _\bt_\bh_\be _\bc_\bo_\bn_\bt_\be_\bn_\bt_\b-_\bt_\by_\bp_\be
+ _\bm_\bu_\bs_\bt _\bm_\ba_\bt_\bc_\bh _\bb_\be_\bf_\bo_\br_\be _\bM_\bu_\bt_\bt_\b-_\bn_\bg _\bp_\be_\br_\bf_\bo_\br_\bm_\bs _\bt_\bh_\be _\bt_\be_\bs_\bt_\b. 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
+ In this example, Mutt-ng 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.
+ isn't. If RunningX returns 0, then Mutt-ng will call netscape to
+ display the text/html object. If RunningX doesn't return 0, then
+ Mutt-ng will go on to the next entry and use lynx to display the
+ text/html object.
_\b5_\b._\b3_\b._\b3_\b._\b2 _\bS_\be_\ba_\br_\bc_\bh _\bO_\br_\bd_\be_\br
- 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:
+ When searching for an entry in the mailcap file, Mutt-ng 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-ng 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
+ Mutt-ng will skip the image/* entry and use the image/gif entry with the print
command.
In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 60) 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
-
- The Mutt-ng E-Mail Client 59
-
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 _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 60), 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.
+ For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 60), Mutt-ng 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-ng will use the second entry for interactive viewing.
+
+ The Mutt-ng E-Mail Client 60
_\b5_\b._\b3_\b._\b3_\b._\b3 _\bC_\bo_\bm_\bm_\ba_\bn_\bd _\bE_\bx_\bp_\ba_\bn_\bs_\bi_\bo_\bn
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:
+ it is parsed to expand various special parameters with information from Mutt-
+ ng. The keywords Mutt-ng 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.
+ use of this keyword causes Mutt-ng to not pass the body of the mes-
+ sage 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.
+ Mutt-ng will expand %t to the text representation of the content
+ type of the message in the same form as the first parameter of the
+ mailcap 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:
+ Mutt-ng 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:
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.
+ then Mutt-ng will expand %{charset} to iso-8859-1. The default
+ metamail 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.
+ Mutt-ng 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
+ handled internally by Mutt-ng.
_\b5_\b._\b3_\b._\b4 _\bE_\bx_\ba_\bm_\bp_\bl_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be_\bs
This mailcap file is fairly simple and standard:
- The Mutt-ng E-Mail Client 60
-
# I'm always running X :)
video/*; xanim %s > /dev/null
image/*; xv %s > /dev/null
This mailcap file shows quite a number of examples:
+ The Mutt-ng E-Mail Client 61
+
# 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
_\b5_\b._\b4 _\bM_\bI_\bM_\bE _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw
- 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.
-
- The Mutt-ng E-Mail Client 61
+ In addition to explicitly telling Mutt-ng to view an attachment with the MIME
+ viewer defined in the mailcap file, Mutt-ng has support for automatically view-
+ ing 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
auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
- Mutt could use the following mailcap entries to automatically view attachments
- of these types.
+ The Mutt-ng E-Mail Client 62
+
+ Mutt-ng could use the following mailcap entries to automatically view attach-
+ ments of these types.
text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
_\b5_\b._\b5 _\bM_\bI_\bM_\bE _\bM_\bu_\bl_\bt_\bi_\bp_\ba_\br_\bt_\b/_\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be
- 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 MIME types in order, including support for
- implicit and explicit wildcards, for example:
+ Mutt-ng has some heuristics for determining which attachment of a multi-
+ part/alternative type to display. First, mutt will check the alternative_order
+ list to determine if one of the available types is preferred. The alterna-
+ tive_order list consists of a number of MIME types 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 _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section
- 5.4 , page 60), 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.
+ 5.4 , page 60), and use that. Failing that, Mutt-ng 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.
_\b5_\b._\b6 _\bM_\bI_\bM_\bE _\bL_\bo_\bo_\bk_\bu_\bp
- Mutt's mime_lookup list specifies a list of mime-types that should not be
+ Mutt-ng'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
-
- The Mutt-ng E-Mail Client 62
-
(such as auto_view) specified. Common usage would be:
mime_lookup application/octet-stream application/X-Lotus-Manuscript
_\b6_\b._\b1 _\bC_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be _\bo_\bp_\bt_\bi_\bo_\bn_\bs
- 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.
+ The Mutt-ng E-Mail Client 63
+
+ Running mutt with no arguments will make Mutt-ng attempt to read your spool
+ mailbox. 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
-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
+ -n do not read the system Muttngrc
-p recall a postponed message
-Q query a configuration variable
-R open mailbox in read-only mode
mutt [ -n ] [ -F _\bm_\bu_\bt_\bt_\br_\bc ] [ -a _\bf_\bi_\bl_\be ] [ -c _\ba_\bd_\bd_\br_\be_\bs_\bs ] [ -i _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ] [ -s _\bs_\bu_\bb_\b-
_\bj_\be_\bc_\bt ] _\ba_\bd_\bd_\br_\be_\bs_\bs [ _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
- Mutt also supports a ``batch'' mode to send prepared messages. Simply redirect
- input from the file you wish to send. For example,
+ Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
+ rect input from the file you wish to send. For example,
mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
- The Mutt-ng E-Mail Client 63
-
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''.
+\bo _\ba_\bl_\bi_\ba_\bs (section 3.2 , page 16) _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ The Mutt-ng E-Mail Client 64
+
+\bo _\bu_\bn_\ba_\bl_\bi_\ba_\bs (section 3.2 , page 16) [ * | _\bk_\be_\by ... ]
+\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.9 , page 23) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.8 , page 23) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- The Mutt-ng E-Mail Client 64
-
+\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.8 , page 23) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+\bo _\bl_\bi_\bs_\bt_\bs (section 3.10 , page 24) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.11 , page 25) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ The Mutt-ng E-Mail Client 65
+
+\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 28) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 61) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.24 , page 29) _\bp_\ba_\bt_\bt_\be_\br_\bn
- The Mutt-ng E-Mail Client 65
-
+\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.10 , page 24) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.10 , page 24) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
_\b6_\b._\b3_\b._\b1 _\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\bs_\bu_\bb_\bj_\be_\bc_\bt
+ The Mutt-ng E-Mail Client 66
+
Type: quadoption
Default: ask-yes
%a
alias name
- The Mutt-ng E-Mail Client 66
-
%f
flags - currently, a 'd' for an alias marked for deletion
%t
character which indicates if the alias is tagged for inclusion
+ The Mutt-ng E-Mail Client 67
+
_\b6_\b._\b3_\b._\b5 _\ba_\bl_\bl_\bo_\bw_\b__\b8_\bb_\bi_\bt
Type: boolean
If _\bs_\be_\bt, Mutt-ng will use plain ASCII characters when displaying thread and
attachment trees, instead of the default ACS characters.
- The Mutt-ng E-Mail Client 67
-
_\b6_\b._\b3_\b._\b9 _\ba_\bs_\bk_\bb_\bc_\bc
Type: boolean
Type: boolean
+ The Mutt-ng E-Mail Client 68
+
Default: no
If _\bs_\be_\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
However, only the first content is valid for the message body. This variable
- is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 6.3.303 , page 139) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 6.3.304 , page 139) is unset.
_\b6_\b._\b3_\b._\b1_\b2 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
%D
deleted flag
- The Mutt-ng E-Mail Client 68
-
%d
description
%I
MIME Content-Disposition: header field (I=inline, A=attachment)
+ The Mutt-ng E-Mail Client 69
+
%m
major MIME type
Default: yes
- The Mutt-ng E-Mail Client 69
-
If this variable is _\bu_\bn_\bs_\be_\bt, when operating (saving, printing, piping, etc) on a
list of tagged attachments, Mutt-ng will concatenate the attachments and will
operate on them as a single attachment. The ``_\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp (section 6.3.13 ,
Default: 'On %d, %n wrote:'
+ The Mutt-ng E-Mail Client 70
+
This is the string that will precede a message which has been included in a
reply. For a full listing of defined printf(3)-like sequences see the section
on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 , page 89)''.
Default: no
- The Mutt-ng E-Mail Client 70
-
When this variable is _\bs_\be_\bt, Mutt-ng will beep whenever it prints a message noti-
fying you of new mail. This is independent of the setting of the ``_\b$_\bb_\be_\be_\bp (sec-
tion 6.3.18 , page 69)'' variable.
Controls whether you will be asked to confirm bouncing messages. If set to _\by_\be_\bs
you don't get asked if you want to bounce a message. Setting this variable to
+
+ The Mutt-ng E-Mail Client 71
+
_\bn_\bo is not generally useful, and thus not recommended, because you are unable to
bounce messages.
Example: set certificate_file=~/.muttng/certificates
- The Mutt-ng E-Mail Client 71
-
_\b6_\b._\b3_\b._\b2_\b4 _\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
Type: boolean
+ The Mutt-ng E-Mail Client 72
+
Default: yes
N\bNo\bot\bte\be:\b: this option only affects _\bm_\ba_\bi_\bl_\bd_\bi_\br and _\bM_\bH style mailboxes.
Mutt-ng version string
See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.301 , page 137)''
-
- The Mutt-ng E-Mail Client 72
-
option for more information on how to set ``_\b$_\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.27 ,
page 71)''.
When defined, Mutt-ng will recode commands in rc files from this encoding.
+ The Mutt-ng E-Mail Client 73
+
_\b6_\b._\b3_\b._\b2_\b9 _\bc_\bo_\bn_\bf_\bi_\br_\bm_\ba_\bp_\bp_\be_\bn_\bd
Type: boolean
Default: yes
- The Mutt-ng E-Mail Client 73
-
This variable controls whether or not copies of your outgoing messages will be
saved for later references. Also see ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.3.228 , page
120)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.3.239 , page 122)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
Default: no
+ The Mutt-ng E-Mail Client 74
+
Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
going messages. This is probably only useful in connection to the _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk
command. It can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when encryption is not
encryption/signing for messages. See also ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt (section
6.3.34 , page 72)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.3.38 , page 73)'',
``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.3.36 , page 73)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
-
- The Mutt-ng E-Mail Client 74
-
6.3.39 , page 73)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.3.275 , page 131)''.
_\b6_\b._\b3_\b._\b3_\b8 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt
If _\bs_\be_\bt, automatically PGP or OpenSSL encrypt replies to messages which are
encrypted. (Crypto only)
+ The Mutt-ng E-Mail Client 75
+
_\b6_\b._\b3_\b._\b3_\b9 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn
Type: boolean
This variable controls the use the GPGME enabled crypto backends. If it is _\bs_\be_\bt
and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
-
- The Mutt-ng E-Mail Client 75
-
will be used instead of the classic code.
N\bNo\bot\bte\be: You need to use this option in your .muttngrc configuration file as it
Default: yes
+ The Mutt-ng E-Mail Client 76
+
If ``_\by_\be_\bs'', always attempt to verify PGP or S/MIME signatures. If ``_\ba_\bs_\bk'', ask
whether or not to verify the signature. If ``_\bn_\bo'', never attempt to verify
cryptographic signatures. (Crypto only)
Controls whether or not messages are really deleted when closing or synchroniz-
ing a mailbox. If set to _\by_\be_\bs, messages marked for deleting will automatically
-
- The Mutt-ng E-Mail Client 76
-
be purged without prompting. If set to _\bn_\bo, messages marked for deletion will
be kept in the mailbox.
If this option is _\bs_\be_\bt, Mutt-ng will untag messages when marking them for dele-
tion. This applies when you either explicitly delete a message, or when you
+
+ The Mutt-ng E-Mail Client 77
+
save it to another folder.
_\b6_\b._\b3_\b._\b4_\b8 _\bd_\bi_\bg_\be_\bs_\bt_\b__\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be
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
-
- The Mutt-ng E-Mail Client 77
-
- following: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notifica-
- tion on transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs,
- to be notified of successful transmission.
+ consists of a comma separated list (no spaces!) of one or more of the follow-
+ ing: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notification on
+ transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs, to be
+ notified of successful transmission.
Example: set dsn_notify='failure,delay'
Default: ''
+ The Mutt-ng E-Mail Client 78
+
N\bNo\bot\bte\be:\b: you should not enable this unless you are using Sendmail 8.8.x or
greater.
Type: boolean
- The Mutt-ng E-Mail Client 78
-
Default: no
When _\bs_\be_\bt, Mutt-ng will quoted-printable encode messages when they contain the
Type: boolean
+ The Mutt-ng E-Mail Client 79
+
Default: no
When _\bs_\be_\bt, Mutt-ng will try to derive the message's _\be_\bn_\bv_\be_\bl_\bo_\bp_\be sender from the
Default: no
- The Mutt-ng E-Mail Client 79
-
When this variable is _\bs_\be_\bt, FCCs will be stored unencrypted and unsigned, even
when the actual message is encrypted and/or signed. (PGP only)
Default: ''
This variable is a colon-separated list of character encoding schemes for text
+
+ The Mutt-ng E-Mail Client 80
+
file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 6.3.24 , page 70) value will
be used instead. For example, the following configuration would work for
Japanese text handling:
%F
file permissions
- The Mutt-ng E-Mail Client 80
-
%g
group name (or numeric gid, if missing)
%s
size in bytes
+ The Mutt-ng E-Mail Client 81
+
%t
* if the file is tagged, blank otherwise
is invoked. When _\bu_\bn_\bs_\be_\bt, _\bb_\bu_\bf_\bf_\by_\b__\bl_\bi_\bs_\bt will just list all mailboxes which are
already known to have new mail.
- The Mutt-ng E-Mail Client 81
-
- Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.3.313 , page 141)'',
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.3.314 , page 142)'',
``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.3.113 , page 93)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
6.3.97 , page 87)''.
This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.3.239 , page 122)'',
except that Mutt-ng will store a copy of your outgoing message by the username
+
+ The Mutt-ng E-Mail Client 82
+
of the address you are sending to even if that mailbox does not exist.
Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.3.228 , page 120)'' variable.
Default: '[%a: %s]'
- The Mutt-ng E-Mail Client 82
-
This variable controls the default subject when forwarding a message. It uses
the same format sequences as the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 , page 89)''
variable.
When _\bs_\be_\bt forwarded messages included in the main body of the message (when
``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.3.134 , page 97)'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
+
+ The Mutt-ng E-Mail Client 83
+
``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.3.107 , page 89)''.
_\b6_\b._\b3_\b._\b7_\b3 _\bf_\br_\bo_\bm
This variable contains a default from address. It can be overridden using
my_hdr (including from send-hooks) and ``_\b$_\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 6.3.234 , page
- 121)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 6.3.322 , page
+ 121)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 6.3.323 , page
143)'' is unset.
E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
Default: yes
- The Mutt-ng E-Mail Client 83
-
When _\bu_\bn_\bs_\be_\bt, the header fields normally added by the ``_\bm_\by_\b__\bh_\bd_\br (section 3.13 ,
page 25)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
ing a new message or replying in order to take effect. If _\bs_\be_\bt, the user
Default: no
+ The Mutt-ng E-Mail Client 84
+
When _\bs_\be_\bt, this variable causes Mutt-ng to include the header of the message you
- are replying to into the edit buffer. The ``_\b$_\bw_\be_\be_\bd (section 6.3.328 , page
- 144)'' setting applies.
+ are replying to into the edit buffer. The ``_\b$_\bw_\be_\be_\bd (section 6.3.329 , page
+ 145)'' setting applies.
_\b6_\b._\b3_\b._\b7_\b7 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be
N\bNo\bot\bte\be:\b: 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-ng is running. Since this variable
- is primarily aimed at new users, neither of these should present a major
-
- The Mutt-ng E-Mail Client 84
-
- problem.
+ is primarily aimed at new users, neither of these should present a major prob-
+ lem.
_\b6_\b._\b3_\b._\b8_\b0 _\bh_\bi_\bd_\bd_\be_\bn_\b__\bh_\bo_\bs_\bt
When _\bs_\be_\bt, Mutt-ng will skip the host name part of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section
6.3.88 , page 85)'' variable when adding the domain part to addresses. This
variable does not affect the generation of Message-ID: header fields, and it
+
+ The Mutt-ng E-Mail Client 85
+
will not lead to the cut-off of first-level domains.
_\b6_\b._\b3_\b._\b8_\b1 _\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
Type: boolean
- The Mutt-ng E-Mail Client 85
-
Default: yes
When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages at the top of
Default: 10
+ The Mutt-ng E-Mail Client 86
+
This variable controls the size (in number of strings remembered) of the string
history buffer. The buffer is cleared each time the variable is changed.
Type: string
- The Mutt-ng E-Mail Client 86
-
Default: ''
Availability: IMAP
If this parameter is _\bu_\bn_\bs_\be_\bt (the default) Mutt-ng will try all available meth-
ods, in order from most-secure to least-secure.
+ The Mutt-ng E-Mail Client 87
+
Example: set imap_authenticators='gssapi:cram-md5:login'
N\bNo\bot\bte\be:\b: Mutt-ng will only fall back to other authentication methods if the previ-
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.
- The Mutt-ng E-Mail Client 87
-
N\bNo\bot\bte\be:\b: This is a space separated list.
_\b6_\b._\b3_\b._\b9_\b4 _\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be
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
+
+ The Mutt-ng E-Mail Client 88
+
to your folders.
_\b6_\b._\b3_\b._\b9_\b5 _\bi_\bm_\ba_\bp_\b__\bk_\be_\be_\bp_\ba_\bl_\bi_\bv_\be
This variable configures how often (in seconds) Mutt-ng should look for new
mail in IMAP folders. This is split from the ``_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.3.113 ,
page 93)'' variable to generate less traffic and get more accurate information
-
- The Mutt-ng E-Mail Client 88
-
for local folders.
_\b6_\b._\b3_\b._\b9_\b8 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
Specifies the password for your IMAP account. If _\bu_\bn_\bs_\be_\bt, Mutt-ng will prompt
you for your password when you invoke the fetch-mail function.
+ The Mutt-ng E-Mail Client 89
+
W\bWa\bar\brn\bni\bin\bng\bg: you should only use this option when you are on a fairly secure
machine, because the superuser can read your configuration even if you are the
only one who can read the file.
Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
connection is lost.
- The Mutt-ng E-Mail Client 89
-
_\b6_\b._\b3_\b._\b1_\b0_\b2 _\bi_\bm_\ba_\bp_\b__\bs_\be_\br_\bv_\be_\br_\bn_\bo_\bi_\bs_\be
Type: boolean
ration problems on the server which are out of the users' hands, you may wish
to suppress them at some point.
+ The Mutt-ng E-Mail Client 90
+
_\b6_\b._\b3_\b._\b1_\b0_\b3 _\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br
Type: string
Controls whether or not Mutt-ng includes only the first attachment of the mes-
sage you are replying.
- The Mutt-ng E-Mail Client 90
-
_\b6_\b._\b3_\b._\b1_\b0_\b7 _\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
Type: string
Type: string
+ The Mutt-ng E-Mail Client 91
+
Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
This variable allows you to customize the message index display to your per-
%e
current message number in thread
- The Mutt-ng E-Mail Client 91
-
%E
number of messages in current thread
%g
newsgroup name (if compiled with nntp support)
+ The Mutt-ng E-Mail Client 92
+
%i
message-id of the current message
`to:' field (recipients)
%T
- the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.3.315 ,
-
- The Mutt-ng E-Mail Client 92
-
+ the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.3.316 ,
page 142) string
%u
%y
`x-label:' field, if present
+ The Mutt-ng E-Mail Client 93
+
%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-
%|X
pad to the end of the line with character 'X'
- See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.3.315 , page 142)''.
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.3.316 , page 142)''.
_\b6_\b._\b3_\b._\b1_\b0_\b9 _\bi_\bs_\bp_\be_\bl_\bl
Type: path
- The Mutt-ng E-Mail Client 93
-
Default: 'ispell'
How to invoke ispell (GNU's spell-checking software).
box to your ``_\b$_\bm_\bb_\bo_\bx (section 6.3.122 , page 95)'' mailbox, or as a result of a
``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.11 , page 25)'' command.
+ The Mutt-ng E-Mail Client 94
+
_\b6_\b._\b3_\b._\b1_\b1_\b1 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
Type: quadoption
This variable specifies which files to consult when attempting to display MIME
bodies not directly supported by Mutt-ng.
- The Mutt-ng E-Mail Client 94
-
_\b6_\b._\b3_\b._\b1_\b1_\b5 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be
Type: boolean
_\b6_\b._\b3_\b._\b1_\b1_\b6 _\bm_\ba_\bi_\bl_\bd_\bi_\br_\b__\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bv_\be_\br_\bi_\bf_\by
+ The Mutt-ng E-Mail Client 95
+
Type: boolean
Default: yes
Type: boolean
- The Mutt-ng E-Mail Client 95
-
Default: yes
Controls the display of wrapped lines in the internal pager. If set, a ``+''
Default: '!^\.[^.]'
A regular expression used in the file browser, optionally preceded by the _\bn_\bo_\bt
+
+ The Mutt-ng E-Mail Client 96
+
operator ``!''. Only files whose names match this mask will be shown. The
match is always case-sensitive.
When _\bs_\be_\bt, the maximum line length for displaying ``format = flowed'' messages
is limited to this length. A value of 0 (which is also the default) means that
the maximum line length is determined by the terminal width and _\b$_\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
- (section 6.3.330 , page 145).
+ (section 6.3.331 , page 145).
_\b6_\b._\b3_\b._\b1_\b2_\b2 _\bm_\bb_\bo_\bx
scrolling through menus. (Similar to ``_\b$_\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 6.3.165 , page
105)''.)
- The Mutt-ng E-Mail Client 96
-
_\b6_\b._\b3_\b._\b1_\b2_\b5 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
Type: boolean
_\b6_\b._\b3_\b._\b1_\b2_\b6 _\bm_\be_\bn_\bu_\b__\bs_\bc_\br_\bo_\bl_\bl
+ The Mutt-ng E-Mail Client 97
+
Type: boolean
Default: no
If _\bu_\bn_\bs_\be_\bt, Mutt-ng will remove your address (see the ``alternates'' command)
from the list of recipients when replying to a message.
- The Mutt-ng E-Mail Client 97
-
_\b6_\b._\b3_\b._\b1_\b3_\b0 _\bm_\bh_\b__\bp_\bu_\br_\bg_\be
Type: boolean
Type: string
+ The Mutt-ng E-Mail Client 98
+
Default: 'flagged'
The name of the MH sequence used for flagged messages.
Type: boolean
- The Mutt-ng E-Mail Client 98
-
Default: no
Controls the decoding of complex MIME messages into text/plain when forwarding
When forwarding multiple attachments of a MIME message from the recvattach
menu, attachments which cannot be decoded in a reasonable manner will be
+
+ The Mutt-ng E-Mail Client 99
+
attached to the newly composed message if this option is set.
_\b6_\b._\b3_\b._\b1_\b3_\b7 _\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: quadoption
- The Mutt-ng E-Mail Client 99
-
Default: ask-no
Controls whether or not Mutt-ng will move read messages from your spool mailbox
Default: '%Y%m%d%h%M%s.G%P%p'
- This is the format for the ``local part'' of the Message-Id: header field gen-
- erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
+ This is the format for the ``local part'' of the Message-Id: header field
+
+ The Mutt-ng E-Mail Client 100
+
+ generated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
generated. The '%' character marks that certain data will be added to the
string, similar to printf(3). The following characters are allowed:
%X
the current UNIX timestamp (hexadecimal)
- The Mutt-ng E-Mail Client 100
-
%Y
the current year (Y2K compliant)
Type: boolean
+ The Mutt-ng E-Mail Client 101
+
Default: no
This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
As for the header caching in connection with IMAP and/or Maildir, this drasti-
cally increases speed and lowers traffic.
- The Mutt-ng E-Mail Client 101
-
_\b6_\b._\b3_\b._\b1_\b4_\b5 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bt_\bc_\bh_\bu_\bp
Type: quadoption
If this variable is _\bs_\be_\bt, Mutt-ng will mark all articles in a newsgroup as read
when you leaving it.
+ The Mutt-ng E-Mail Client 102
+
_\b6_\b._\b3_\b._\b1_\b4_\b6 _\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
Type: number
personal taste. This string is similar to ``_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 ,
page 89)'', but has its own set of printf(3)-like sequences:
- The Mutt-ng E-Mail Client 102
-
%C current newsgroup number
%d description of newsgroup (retrieved from server)
%f newsgroup name
Type: string
+ The Mutt-ng E-Mail Client 103
+
Default: ''
Availability: NNTP
Type: boolean
- The Mutt-ng E-Mail Client 103
-
Default: yes
Availability: NNTP
Availability: NNTP
+ The Mutt-ng E-Mail Client 104
+
The time in seconds until any operations on a newsgroup except posting a new
article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
each operation in index (stepping, read article, etc.).
Type: string
- The Mutt-ng E-Mail Client 104
-
Default: ''
Availability: NNTP
Default: ask-yes
+ The Mutt-ng E-Mail Client 105
+
Availability: NNTP
If set to _\by_\be_\bs, Mutt-ng will post articles to newsgroup that have not permis-
Availability: NNTP
If _\bs_\be_\bt, the newsserver will be asked for new newsgroups on entering the
-
- The Mutt-ng E-Mail Client 105
-
browser. Otherwise, it will be done only once for a newsserver. Also controls
whether or not the number of new articles of subscribed newsgroups will be
checked.
If _\bs_\be_\bt, only subscribed newsgroups that contain unread articles will be dis-
played in the newsgroup browser.
+ The Mutt-ng E-Mail Client 106
+
_\b6_\b._\b3_\b._\b1_\b6_\b1 _\bn_\bn_\bt_\bp_\b__\bu_\bs_\be_\br
Type: string
Default: 'builtin'
- The Mutt-ng E-Mail Client 106
-
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.
Default: 0
+ The Mutt-ng E-Mail Client 107
+
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-ng
will display the line after the last one on the screen at the top of the next
Default: no
- The Mutt-ng E-Mail Client 107
-
When _\bs_\be_\bt, the internal-pager will n\bno\bot\bt move to the next message when you are at
the end of a message and invoke the _\bn_\be_\bx_\bt_\b-_\bp_\ba_\bg_\be function.
ditional-pgp function, Mutt-ng will automatically check the message for tradi-
tional pgp.
+ The Mutt-ng E-Mail Client 108
+
_\b6_\b._\b3_\b._\b1_\b7_\b0 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\bi_\bn_\bl_\bi_\bn_\be
Type: boolean
Note that the use of this format is s\bst\btr\bro\bon\bng\bgl\bly\by d\bde\bep\bpr\bre\bec\bca\bat\bte\bed\bd. (PGP only)
- The Mutt-ng E-Mail Client 108
-
_\b6_\b._\b3_\b._\b1_\b7_\b3 _\bp_\bg_\bp_\b__\bd_\be_\bc_\bo_\bd_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
%f
Expands to the name of a file containing a message.
+ The Mutt-ng E-Mail Client 109
+
%s
Expands to the name of a file containing the signature part of a
multipart/signed attachment when verifying it.
Default: ''
- The Mutt-ng E-Mail Client 109
-
This command is used to both sign and encrypt a body part. (PGP only)
_\b6_\b._\b3_\b._\b1_\b7_\b7 _\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
%k
key id
+ The Mutt-ng E-Mail Client 110
+
%u
user id
Type: string
- The Mutt-ng E-Mail Client 110
-
Default: ''
This command is invoked whenever Mutt-ng will need public key information. %r
_\b6_\b._\b3_\b._\b1_\b8_\b1 _\bp_\bg_\bp_\b__\bi_\bg_\bn_\bo_\br_\be_\b__\bs_\bu_\bb_\bk_\be_\by_\bs
+ The Mutt-ng E-Mail Client 111
+
Type: boolean
Default: yes
Default: ''
This command is used to list the secret key ring's contents. The output format
-
- The Mutt-ng E-Mail Client 111
-
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-ng.
Type: quadoption
+ The Mutt-ng E-Mail Client 112
+
Default: ask-yes
This option controls whether Mutt-ng will prompt you for automatically sending
Default: no
- The Mutt-ng E-Mail Client 112
-
If _\bs_\be_\bt, signed and encrypted messages will consist of nested multipart/signed
and multipart/encrypted body parts.
This includes keys which have been revoked, have expired, or have been marked
as ``disabled'' by the user. (PGP only)
+ The Mutt-ng E-Mail Client 113
+
_\b6_\b._\b3_\b._\b1_\b9_\b0 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs
Type: string
date
sort by key creation date
- The Mutt-ng E-Mail Client 113
-
trust
sort by the trust of the key
non-verifyable PGP signatures, so only change this if you know what you are
doing. (PGP only)
+ The Mutt-ng E-Mail Client 114
+
_\b6_\b._\b3_\b._\b1_\b9_\b4 _\bp_\bg_\bp_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
Type: boolean
- The Mutt-ng E-Mail Client 114
-
Default: no
Used in connection with the _\bp_\bi_\bp_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be command. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will
The separator to add between messages when piping a list of tagged messages to
an external Unix command.
+ The Mutt-ng E-Mail Client 115
+
_\b6_\b._\b3_\b._\b2_\b0_\b0 _\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
Type: boolean
tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
``digest-md5'', ``gssapi'' or ``cram-md5''.
- The Mutt-ng E-Mail Client 115
-
This parameter is case-insensitive. If this parameter is _\bu_\bn_\bs_\be_\bt (the default)
Mutt-ng will try all available methods, in order from most-secure to least-
secure.
Availability: POP
If _\bs_\be_\bt, Mutt-ng will delete successfully downloaded messages from the POP
+
+ The Mutt-ng E-Mail Client 116
+
server when using the ``fetch-mail'' function. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will down-
load messages but also leave them on the POP server.
Availability: POP
- The Mutt-ng E-Mail Client 116
-
This variable configures how often (in seconds) POP should look for new mail.
_\b6_\b._\b3_\b._\b2_\b0_\b7 _\bp_\bo_\bp_\b__\bp_\ba_\bs_\bs
N\bNo\bot\bte\be:\b: Storing passwords in a configuration file presents a security risk since
the superuser of your machine may read it regardless of the file's permissions.
+ The Mutt-ng E-Mail Client 117
+
_\b6_\b._\b3_\b._\b2_\b0_\b8 _\bp_\bo_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Type: quadoption
Default: ask-yes
- The Mutt-ng E-Mail Client 117
-
Controls whether or not messages are saved in the ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section
6.3.212 , page 116)'' mailbox when you elect not to send immediately.
sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.3.211 , page 116)'' variable.
+ The Mutt-ng E-Mail Client 118
+
_\b6_\b._\b3_\b._\b2_\b1_\b3 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Type: string
Type: boolean
- The Mutt-ng E-Mail Client 118
-
Default: yes
Used in connection with the print-message command. If this option is _\bs_\be_\bt, the
Default: no
+ The Mutt-ng E-Mail Client 119
+
Used in connection with the print-message command. If this option is _\bs_\be_\bt, the
command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.3.215 , page 117) is executed
once for each message which is to be printed. If this option is _\bu_\bn_\bs_\be_\bt, the
Default: yes
This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
-
- The Mutt-ng E-Mail Client 119
-
ng. If it set to _\by_\be_\bs, they do quit, if it is set to _\bn_\bo, they have no effect,
and if it is set to _\ba_\bs_\bk_\b-_\by_\be_\bs or _\ba_\bs_\bk_\b-_\bn_\bo, you are prompted for confirmation when
you try to quit.
_\b6_\b._\b3_\b._\b2_\b2_\b2 _\bq_\bu_\bo_\bt_\be_\b__\bq_\bu_\bo_\bt_\be_\bd
+ The Mutt-ng E-Mail Client 120
+
Type: boolean
Default: no
time. When set to 0, only a single message will appear before the reading the
mailbox.
- Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 6.3.332 , page 145)'' variable.
+ Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 6.3.333 , page 145)'' variable.
_\b6_\b._\b3_\b._\b2_\b2_\b5 _\br_\be_\ba_\bd_\b__\bo_\bn_\bl_\by
- The Mutt-ng E-Mail Client 120
-
Type: boolean
Default: no
This variable specifies what ``real'' or ``personal'' name should be used when
sending messages.
+ The Mutt-ng E-Mail Client 121
+
By default, this is the GECOS field from /etc/passwd.
_\bN_\bo_\bt_\be_\b: This variable will _\bn_\bo_\bt be used when the user has set a real name in the
Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
- A regular expression used to recognize reply messages when threading and
-
- The Mutt-ng E-Mail Client 121
-
- replying. The default value corresponds to the English ``Re:'' and the German
+ 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:''.
_\b6_\b._\b3_\b._\b2_\b3_\b0 _\br_\be_\bp_\bl_\by_\b__\bs_\be_\bl_\bf
_\b6_\b._\b3_\b._\b2_\b3_\b1 _\br_\be_\bp_\bl_\by_\b__\bt_\bo
+ The Mutt-ng E-Mail Client 122
+
Type: quadoption
Default: ask-yes
From: abd30425@somewhere.net
It would be displayed in the index menu as ``Joe User'' instead of
-
- The Mutt-ng E-Mail Client 122
-
``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
not human friendly (like CompuServe addresses).
using the address where you received the messages you are replying to i\bif\bf that
address matches your alternates. If the variable is _\bu_\bn_\bs_\be_\bt, or the address that
would be used doesn't match your alternates, the From: line will use your
+
+ The Mutt-ng E-Mail Client 123
+
address on the current machine.
_\b6_\b._\b3_\b._\b2_\b3_\b5 _\br_\be_\bv_\be_\br_\bs_\be_\b__\br_\be_\ba_\bl_\bn_\ba_\bm_\be
Type: boolean
- The Mutt-ng E-Mail Client 123
-
Default: no
If _\bs_\be_\bt, Mutt-ng will take the sender's full address when choosing a default
Default: yes
When _\bu_\bn_\bs_\be_\bt, mailboxes which contain no saved messages will be removed when
+
+ The Mutt-ng E-Mail Client 124
+
closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.3.293 , page 135)'' which is
never removed). If _\bs_\be_\bt, mailboxes are never removed.
Messages which have been assigned a score equal to or lower than the value of
this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
scores are always greater than or equal to zero, the default setting of this
-
- The Mutt-ng E-Mail Client 124
-
variable will never mark a message for deletion.
_\b6_\b._\b3_\b._\b2_\b4_\b2 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bf_\bl_\ba_\bg
Type: number
+ The Mutt-ng E-Mail Client 125
+
Default: -1
Messages which have been assigned a score equal to or lower than the value of
page 124)'' process to finish before giving up and putting delivery in the
background.
- The Mutt-ng E-Mail Client 125
-
Mutt-ng interprets the value of this variable as follows:
>0
will be put in a temporary file. If there is some error, you will be informed
as to where to find the output.
+ The Mutt-ng E-Mail Client 126
+
_\b6_\b._\b3_\b._\b2_\b4_\b7 _\bs_\bh_\be_\bl_\bl
Type: path
Type: string
- The Mutt-ng E-Mail Client 126
-
Default: '%c%?n?(%n)?%?f?[%f]?'
This variable controls how message counts are printed when the sidebar is
%f
Number of flagged messages.
+ The Mutt-ng E-Mail Client 127
+
%n
Number of new messages.
The width of the sidebar.
- The Mutt-ng E-Mail Client 127
-
_\b6_\b._\b3_\b._\b2_\b5_\b5 _\bs_\bi_\bg_\b__\bd_\ba_\bs_\bh_\be_\bs
Type: boolean
For example, Mutt-ng has the ability to highlight the signature in a different
color in the builtin pager.
+ The Mutt-ng E-Mail Client 128
+
_\b6_\b._\b3_\b._\b2_\b5_\b6 _\bs_\bi_\bg_\b__\bo_\bn_\b__\bt_\bo_\bp
Type: boolean
Default: '~f %s | ~s %s'
- The Mutt-ng E-Mail Client 128
-
Specifies how Mutt-ng should expand a simple search into a real search pattern.
A simple search is one that does not contain any of the ~ operators. See
``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 4.2 , page 36)'' for more information on search patterns.
Type: number
+ The Mutt-ng E-Mail Client 129
+
Default: 1
Specifies time, in seconds, to pause while displaying certain informational
_\b6_\b._\b3_\b._\b2_\b6_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn
- The Mutt-ng E-Mail Client 129
-
Type: path
Default: ''
Default: ''
Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
+
+ The Mutt-ng E-Mail Client 130
+
and retrieval of keys by itself. This is very basic right now, and keys and
certificates are stored in two different directories, both named as the hash-
value retrieved from OpenSSL. There is an index file which contains mailbox-
'-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.3.264 , page 128)' or
'-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.3.264 , page 128)'.
- The Mutt-ng E-Mail Client 130
-
For examples on how to configure these formats, see the smime.rc in the sam-
ples/ subdirectory which has been installed on your system alongside the docu-
mentation. (S/MIME only)
If _\bs_\be_\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
mailbox-address to determine the key to use. It will ask you to supply a key,
+
+ The Mutt-ng E-Mail Client 131
+
if it can't find one. (S/MIME only)
_\b6_\b._\b3_\b._\b2_\b6_\b8 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by
_\b6_\b._\b3_\b._\b2_\b7_\b2 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bc_\be_\br_\bt_\b__\be_\bm_\ba_\bi_\bl_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
- The Mutt-ng E-Mail Client 131
-
Type: string
Default: ''
Default: ''
+ The Mutt-ng E-Mail Client 132
+
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:'' header field. (S/MIME only)
address keyid pair, and which can be manually edited. This one points to the
location of the private keys. (S/MIME only)
- The Mutt-ng E-Mail Client 132
-
_\b6_\b._\b3_\b._\b2_\b7_\b7 _\bs_\bm_\bi_\bm_\be_\b__\bp_\bk_\b7_\bo_\bu_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
Default: ''
+ The Mutt-ng E-Mail Client 133
+
This command is used to created S/MIME signatures of type multipart/signed,
which can be read by all mail clients. (S/MIME only)
This command is used to verify S/MIME signatures of type application/x-
pkcs7-mime. (S/MIME only)
- The Mutt-ng E-Mail Client 133
-
_\b6_\b._\b3_\b._\b2_\b8_\b3 _\bs_\bm_\bt_\bp_\b__\ba_\bu_\bt_\bh_\b__\bp_\ba_\bs_\bs_\bw_\bo_\br_\bd
Type: string
N\bNo\bot\bte\be:\b: Storing passwords in a configuration file presents a security risk since
the superuser of your machine may read it regardless of the file's permissions.
+ The Mutt-ng E-Mail Client 134
+
_\b6_\b._\b3_\b._\b2_\b8_\b4 _\bs_\bm_\bt_\bp_\b__\ba_\bu_\bt_\bh_\b__\bu_\bs_\be_\br_\bn_\ba_\bm_\be
Type: string
_\b6_\b._\b3_\b._\b2_\b8_\b7 _\bs_\bo_\br_\bt
- The Mutt-ng E-Mail Client 134
-
Type: sort order
Default: date
Specifies how to sort messages in the _\bi_\bn_\bd_\be_\bx menu. Valid values are:
+ The Mutt-ng E-Mail Client 135
+
date or date-sent
date-received
from
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
-
- The Mutt-ng E-Mail Client 135
-
first, if you have set sort=reverse-threads.)
N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 6.3.287 , page 133)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
(section 6.3.289 , page 134) is reversed again (which is not the right thing
to do, but kept to not break any existing configuration setting).
+ The Mutt-ng E-Mail Client 136
+
_\b6_\b._\b3_\b._\b2_\b9_\b0 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
Type: sort order
Default: yes
This variable is only useful when sorting by threads with ``_\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
- (section 6.3.304 , page 139)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ (section 6.3.305 , page 140)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.3.291 ,
page 135) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
sage by subject if the subject of the child message starts with a substring
match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.3.292 ,
page 135)'' as a separator.
- The Mutt-ng E-Mail Client 136
-
_\b6_\b._\b3_\b._\b2_\b9_\b3 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
Type: path
Default: ''
If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
+
+ The Mutt-ng E-Mail Client 137
+
you can specify its location with this variable. Mutt-ng will automatically
set this variable to the value of the environment variable $MAIL if it is not
set.
Availability: SSL or GNUTLS
- If _\bs_\be_\bt (the default), Mutt-ng will attempt to use STARTTLS on servers
-
- The Mutt-ng E-Mail Client 137
-
- advertising the capability. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not attempt to use START-
- TLS regardless of the server's capabilities.
+ If _\bs_\be_\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
+ ing the capability. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not attempt to use STARTTLS
+ regardless of the server's capabilities.
_\b6_\b._\b3_\b._\b2_\b9_\b8 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b3
Type: boolean
+ The Mutt-ng E-Mail Client 138
+
Default: yes
Availability: SSL or NSS or GNUTLS
string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.108 , page 89)'', but has
its own set of printf(3)-like sequences:
- The Mutt-ng E-Mail Client 138
-
%b
number of mailboxes with new mail *
%d
number of deleted messages *
+ The Mutt-ng E-Mail Client 139
+
%f
the full pathname of the current mailbox
current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 6.3.289 , page
134))
- The Mutt-ng E-Mail Client 139
-
%t
number of tagged messages *
%v
Mutt-ng version string
+ The Mutt-ng E-Mail Client 140
+
%V
currently active limit pattern, if any *
replace any dots in the expansion by underscores. This might be helpful with
IMAP folders that don't like dots in folder names.
- The Mutt-ng E-Mail Client 140
-
_\b6_\b._\b3_\b._\b3_\b0_\b2 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bo_\bn_\b__\bt_\bo_\bp
Type: boolean
Setting this variable causes the ``status bar'' to be displayed on the first
line of the screen rather than near the bottom.
- _\b6_\b._\b3_\b._\b3_\b0_\b3 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
+ The Mutt-ng E-Mail Client 141
+
+ _\b6_\b._\b3_\b._\b3_\b0_\b3 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo
+
+ Type: boolean
+
+ Default: yes
+
+ With mailto: style links, a body as well as arbitrary header information may be
+ embedded. This may lead to (user) headers being overwriten without note if
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.3.54 , page 77)'' is unset.
+
+ If this variable is _\bs_\be_\bt, mutt-ng is strict and allows anything to be changed.
+ If it's _\bu_\bn_\bs_\be_\bt, all headers given will be prefixed with ``X-Mailto-'' and the
+ message including headers will be shown in the editor regardless of what
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.3.54 , page 77)'' is set to.
+
+ _\b6_\b._\b3_\b._\b3_\b0_\b4 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
Type: boolean
a single space to prevent the display of MIME-encoded ``Subject:'' header field
from being devided into multiple lines.
- _\b6_\b._\b3_\b._\b3_\b0_\b4 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
+ _\b6_\b._\b3_\b._\b3_\b0_\b5 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
Type: boolean
mailbox where you might have several unrelated messages with the subject ``hi''
which will get grouped together.
- _\b6_\b._\b3_\b._\b3_\b0_\b5 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
+ _\b6_\b._\b3_\b._\b3_\b0_\b6 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
Type: boolean
Default: no
When _\bs_\be_\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
- matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 6.3.306 , page 140) when replying. This is
+ matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 6.3.307 , page 140) when replying. This is
useful to properly react on subject changes and reduce ``subject noise.'' (esp.
in Usenet)
- _\b6_\b._\b3_\b._\b3_\b0_\b6 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
+ The Mutt-ng E-Mail Client 142
+
+ _\b6_\b._\b3_\b._\b3_\b0_\b7 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
Type: regular expression
Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
- The Mutt-ng E-Mail Client 141
-
- When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 6.3.305 , page 140) is _\bs_\be_\bt, mutt-ng
+ When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 6.3.306 , page 140) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
- _\b6_\b._\b3_\b._\b3_\b0_\b7 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
+ _\b6_\b._\b3_\b._\b3_\b0_\b8 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
Type: boolean
If _\bs_\be_\bt, attachments with flowed format will have their quoting ``stuffed'',
i.e. a space will be inserted between the quote characters and the actual text.
- _\b6_\b._\b3_\b._\b3_\b0_\b8 _\bs_\bu_\bs_\bp_\be_\bn_\bd
+ _\b6_\b._\b3_\b._\b3_\b0_\b9 _\bs_\bu_\bs_\bp_\be_\bn_\bd
Type: boolean
usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
mand like ``xterm -e muttng.''
- _\b6_\b._\b3_\b._\b3_\b0_\b9 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
+ _\b6_\b._\b3_\b._\b3_\b1_\b0 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
Type: boolean
Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.3.107 , page 89) is ignored when this
option is set.
- _\b6_\b._\b3_\b._\b3_\b1_\b0 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b6_\b._\b3_\b._\b3_\b1_\b1 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
Type: boolean
to be searched are decoded before searching. If _\bu_\bn_\bs_\be_\bt, messages are searched
as they appear in the folder.
- _\b6_\b._\b3_\b._\b3_\b1_\b1 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
+ The Mutt-ng E-Mail Client 143
+
+ _\b6_\b._\b3_\b._\b3_\b1_\b2 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
Type: boolean
Default: no
- The Mutt-ng E-Mail Client 142
-
When _\bs_\be_\bt, Mutt-ng uses the date received rather than the date sent to thread
messages by subject.
- _\b6_\b._\b3_\b._\b3_\b1_\b2 _\bt_\bi_\bl_\bd_\be
+ _\b6_\b._\b3_\b._\b3_\b1_\b3 _\bt_\bi_\bl_\bd_\be
Type: boolean
When _\bs_\be_\bt, the internal-pager will pad blank lines to the bottom of the screen
with a tilde (~).
- _\b6_\b._\b3_\b._\b3_\b1_\b3 _\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b6_\b._\b3_\b._\b3_\b1_\b4 _\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
pressed in the main menu before timing out and checking for new mail. A value
of zero or less will cause Mutt-ng to never time out.
- _\b6_\b._\b3_\b._\b3_\b1_\b4 _\bt_\bm_\bp_\bd_\bi_\br
+ _\b6_\b._\b3_\b._\b3_\b1_\b5 _\bt_\bm_\bp_\bd_\bi_\br
Type: path
set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
'/tmp' is used.
- _\b6_\b._\b3_\b._\b3_\b1_\b5 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
+ _\b6_\b._\b3_\b._\b3_\b1_\b6 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
Type: string
indicate mail that was sent by _\by_\bo_\bu. The sixth character is used to indicate
when a mail was sent to a mailing-list you're subscribe to (default: L).
- _\b6_\b._\b3_\b._\b3_\b1_\b6 _\bt_\br_\ba_\bs_\bh
+ The Mutt-ng E-Mail Client 144
+
+ _\b6_\b._\b3_\b._\b3_\b1_\b7 _\bt_\br_\ba_\bs_\bh
Type: path
Default: ''
- The Mutt-ng E-Mail Client 143
-
If _\bs_\be_\bt, this variable specifies the path of the trash folder where the mails
marked for deletion will be moved, instead of being irremediably purged.
N\bNo\bot\bte\be: When you delete a message in the trash folder, it is really deleted, so
that there is no way to recover mail.
- _\b6_\b._\b3_\b._\b3_\b1_\b7 _\bt_\bu_\bn_\bn_\be_\bl
+ _\b6_\b._\b3_\b._\b3_\b1_\b8 _\bt_\bu_\bn_\bn_\be_\bl
Type: string
N\bNo\bot\bte\be:\b: For this example to work you must be able to log in to the remote machine
without having to enter a password.
- _\b6_\b._\b3_\b._\b3_\b1_\b8 _\bu_\bm_\ba_\bs_\bk
+ _\b6_\b._\b3_\b._\b3_\b1_\b9 _\bu_\bm_\ba_\bs_\bk
Type: number
This sets the umask that will be used by Mutt-ng when creating all kinds of
files. If _\bu_\bn_\bs_\be_\bt, the default value is 077.
- _\b6_\b._\b3_\b._\b3_\b1_\b9 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
+ _\b6_\b._\b3_\b._\b3_\b2_\b0 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
Type: boolean
When _\bs_\be_\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
rent thread is _\bu_\bncollapsed.
- _\b6_\b._\b3_\b._\b3_\b2_\b0 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
+ _\b6_\b._\b3_\b._\b3_\b2_\b1 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
Type: boolean
which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be
able to send mail.
+ The Mutt-ng E-Mail Client 145
+
When _\bs_\be_\bt, Mutt-ng will invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.3.245 , page 124)'' with
the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation.
- _\b6_\b._\b3_\b._\b3_\b2_\b1 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
-
- The Mutt-ng E-Mail Client 144
+ _\b6_\b._\b3_\b._\b3_\b2_\b2 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
Type: boolean
tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 6.3.88 , page 85)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
- _\b6_\b._\b3_\b._\b3_\b2_\b2 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
+ _\b6_\b._\b3_\b._\b3_\b2_\b3 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
Type: boolean
sages. If _\bu_\bn_\bs_\be_\bt, no ``From:'' header field will be generated unless the user
explicitly sets one using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.13 , page 25)'' command.
- _\b6_\b._\b3_\b._\b3_\b2_\b3 _\bu_\bs_\be_\b__\bi_\bd_\bn
+ _\b6_\b._\b3_\b._\b3_\b2_\b4 _\bu_\bs_\be_\b__\bi_\bd_\bn
Type: boolean
N\bNo\bot\bte\be:\b: You can use IDNs for addresses even if this is _\bu_\bn_\bs_\be_\bt. This variable only
affects decoding.
- _\b6_\b._\b3_\b._\b3_\b2_\b4 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
+ _\b6_\b._\b3_\b._\b3_\b2_\b5 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
Type: boolean
If this option is _\bu_\bn_\bs_\be_\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
mally, the default should work.
- _\b6_\b._\b3_\b._\b3_\b2_\b5 _\bu_\bs_\be_\br_\b__\ba_\bg_\be_\bn_\bt
+ _\b6_\b._\b3_\b._\b3_\b2_\b6 _\bu_\bs_\be_\br_\b__\ba_\bg_\be_\bn_\bt
Type: boolean
When _\bs_\be_\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
cating which version of Mutt-ng was used for composing them.
- _\b6_\b._\b3_\b._\b3_\b2_\b6 _\bv_\bi_\bs_\bu_\ba_\bl
+ The Mutt-ng E-Mail Client 146
- Type: path
+ _\b6_\b._\b3_\b._\b3_\b2_\b7 _\bv_\bi_\bs_\bu_\ba_\bl
- The Mutt-ng E-Mail Client 145
+ Type: path
Default: ''
Specifies the visual editor to invoke when the _\b~_\bv command is given in the
builtin editor.
- _\b6_\b._\b3_\b._\b3_\b2_\b7 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
+ _\b6_\b._\b3_\b._\b3_\b2_\b8 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
Type: boolean
When _\bs_\be_\bt, Mutt-ng will always ask for a key. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will wait for
a key only if the external command returned a non-zero status.
- _\b6_\b._\b3_\b._\b3_\b2_\b8 _\bw_\be_\be_\bd
+ _\b6_\b._\b3_\b._\b3_\b2_\b9 _\bw_\be_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
replying to messages.
- _\b6_\b._\b3_\b._\b3_\b2_\b9 _\bw_\br_\ba_\bp_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b6_\b._\b3_\b._\b3_\b3_\b0 _\bw_\br_\ba_\bp_\b__\bs_\be_\ba_\br_\bc_\bh
Type: boolean
When _\bs_\be_\bt, searches will wrap around the first (or last) message. When _\bu_\bn_\bs_\be_\bt,
searches will not wrap.
- _\b6_\b._\b3_\b._\b3_\b3_\b0 _\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
+ _\b6_\b._\b3_\b._\b3_\b3_\b1 _\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
Type: number
Controls the size of the margin remaining at the right side of the terminal
when Mutt-ng's pager does smart wrapping.
- _\b6_\b._\b3_\b._\b3_\b3_\b1 _\bw_\br_\bi_\bt_\be_\b__\bb_\bc_\bc
+ The Mutt-ng E-Mail Client 147
- Type: boolean
+ _\b6_\b._\b3_\b._\b3_\b3_\b2 _\bw_\br_\bi_\bt_\be_\b__\bb_\bc_\bc
- The Mutt-ng E-Mail Client 146
+ Type: boolean
Default: yes
Controls whether Mutt-ng writes out the Bcc header when preparing messages to
be sent. Exim users may wish to _\bu_\bn_\bs_\be_\bt this.
- _\b6_\b._\b3_\b._\b3_\b3_\b2 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
+ _\b6_\b._\b3_\b._\b3_\b3_\b3 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
Type: number
Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 6.3.224 , page 119)'' variable.
- _\b6_\b._\b3_\b._\b3_\b3_\b3 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
+ _\b6_\b._\b3_\b._\b3_\b3_\b4 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
Type: string
Default: 'M%?n?AIL&ail?'
Controls the format of the X11 icon title, as long as _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (sec-
- tion 6.3.334 , page 146) is _\bs_\be_\bt. This string is identical in formatting to the
+ tion 6.3.335 , page 146) is _\bs_\be_\bt. This string is identical in formatting to the
one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.301 , page 137)''.
- _\b6_\b._\b3_\b._\b3_\b3_\b4 _\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs
+ _\b6_\b._\b3_\b._\b3_\b3_\b5 _\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs
Type: boolean
you're in an appropriate terminal). The default must be _\bu_\bn_\bs_\be_\bt to force in the
validity checking.
- _\b6_\b._\b3_\b._\b3_\b3_\b5 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
+ _\b6_\b._\b3_\b._\b3_\b3_\b6 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
Type: string
Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
Controls the format of the title bar of the xterm provided that
- _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.3.334 , page 146) has been _\bs_\be_\bt. This string is
+ _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.3.335 , page 146) has been _\bs_\be_\bt. This string is
identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.3.301 ,
page 137)''.
_\b6_\b._\b4 _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
+ The Mutt-ng E-Mail Client 148
+
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 _\bb_\bi_\bn_\bd (section 3.3 , page 17) command.
- The Mutt-ng E-Mail Client 147
-
_\b6_\b._\b4_\b._\b1 _\bg_\be_\bn_\be_\br_\bi_\bc
The _\bg_\be_\bn_\be_\br_\bi_\bc menu is not a real menu, but specifies common functions (such as
_\b6_\b._\b4_\b._\b2 _\bi_\bn_\bd_\be_\bx
- The Mutt-ng E-Mail Client 148
+ The Mutt-ng E-Mail Client 149
bounce-message b remail a message to another user
change-folder c open a different folder
show-version V show the Mutt-ng version number and date
show-limit ESC l show currently active limit pattern, if any
- The Mutt-ng E-Mail Client 149
+ The Mutt-ng E-Mail Client 150
sort-mailbox o sort messages
sort-reverse O sort messages in reverse order
_\b6_\b._\b4_\b._\b3 _\bp_\ba_\bg_\be_\br
- The Mutt-ng E-Mail Client 150
+ The Mutt-ng E-Mail Client 151
bottom not bound jump to the bottom of the message
bounce-message b remail a message to another user
recall-message R recall a postponed message
redraw-screen ^L clear and redraw the screen
- The Mutt-ng E-Mail Client 151
+ The Mutt-ng E-Mail Client 152
reply r reply to a message
save-message s save message/attachment to a file
_\b6_\b._\b4_\b._\b6 _\ba_\bt_\bt_\ba_\bc_\bh
- The Mutt-ng E-Mail Client 152
+ The Mutt-ng E-Mail Client 153
bounce-message b remail a message to another user
collapse-parts v toggle display of subparts
_\b6_\b._\b4_\b._\b7 _\bc_\bo_\bm_\bp_\bo_\bs_\be
- The Mutt-ng E-Mail Client 153
+ The Mutt-ng E-Mail Client 154
attach-file a attach a file(s) to this message
attach-message A attach message(s) to this message
_\b6_\b._\b4_\b._\b9 _\bb_\br_\bo_\bw_\bs_\be_\br
- The Mutt-ng E-Mail Client 154
+ The Mutt-ng E-Mail Client 155
change-dir c change directories
check-new TAB check mailboxes for new mail
_\b7_\b. _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\by
- The Mutt-ng E-Mail Client 155
+ The Mutt-ng E-Mail Client 156
_\b7_\b._\b1 _\bA_\bc_\bk_\bn_\bo_\bw_\bl_\be_\bd_\bg_\bm_\be_\bn_\bt_\bs
Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
- The Mutt-ng E-Mail Client 156
+ The Mutt-ng E-Mail Client 157
Brandon Long <blong@fiction.net>,
This document was written in SGML, and then rendered using the sgml-tools pack-
age.
- The Mutt-ng E-Mail Client 157
+ The Mutt-ng E-Mail Client 158
CONTENTS
3.12 Defining mailboxes which receive mail ............................ 25
3.13 User defined headers ............................................. 26
3.14 Defining the order of headers when viewing messages .............. 26
- 3.15 Specify default save filename .................................... 26
+ 3.15 Specify default save filename .................................... 27
3.16 Specify default Fcc: mailbox when composing ...................... 27
3.17 Specify default save filename and default Fcc: mailbox at once ... 27
3.18 Change settings based upon message recipients .................... 27
i
4.2 Patterns ......................................................... 37
- 4.3 Using Tags ....................................................... 40
+ 4.3 Using Tags ....................................................... 41
4.4 Using Hooks ...................................................... 41
- 4.5 Using the sidebar ................................................ 42
+ 4.5 Using the sidebar ................................................ 43
4.6 External Address Queries ......................................... 43
4.7 Mailbox Formats .................................................. 44
- 4.8 Mailbox Shortcuts ................................................ 44
+ 4.8 Mailbox Shortcuts ................................................ 45
4.9 Handling Mailing Lists ........................................... 45
- 4.10 Editing threads .................................................. 46
- 4.11 Delivery Status Notification (DSN) Support ....................... 46
+ 4.10 Editing threads .................................................. 47
+ 4.11 Delivery Status Notification (DSN) Support ....................... 47
4.12 POP3 Support (OPTIONAL) .......................................... 47
- 4.13 IMAP Support (OPTIONAL) .......................................... 47
- 4.14 Managing multiple IMAP/POP accounts (OPTIONAL) ................... 49
- 4.15 Start a WWW Browser on URLs (EXTERNAL) ........................... 49
+ 4.13 IMAP Support (OPTIONAL) .......................................... 48
+ 4.14 Managing multiple IMAP/POP accounts (OPTIONAL) ................... 50
+ 4.15 Start a WWW Browser on URLs (EXTERNAL) ........................... 50
4.16 Compressed folders Support (OPTIONAL) ............................ 50
- 5. Mutt's MIME Support .................................................... 52
+ 5. Mutt-ng's MIME Support ................................................. 53
5.1 Using MIME in Mutt ............................................... 53
- 5.2 MIME Type configuration with mime.types .......................... 54
- 5.3 MIME Viewer configuration with mailcap ........................... 54
- 5.4 MIME Autoview .................................................... 60
- 5.5 MIME Multipart/Alternative ....................................... 61
- 5.6 MIME Lookup ...................................................... 61
+ 5.2 MIME Type configuration with mime.types .......................... 55
+ 5.3 MIME Viewer configuration with mailcap ........................... 55
+ 5.4 MIME Autoview .................................................... 61
+ 5.5 MIME Multipart/Alternative ....................................... 62
+ 5.6 MIME Lookup ...................................................... 62
6. Reference .............................................................. 62
6.1 Command line options ............................................. 62
6.2 Configuration Commands ........................................... 63
6.3 Configuration variables .......................................... 65
- 6.4 Functions ....................................................... 146
+ 6.4 Functions ....................................................... 147
- 7. Miscellany ............................................................ 154
- 7.1 Acknowledgments ................................................. 155
- 7.2 About this document ............................................. 156
+ 7. Miscellany ............................................................ 155
+ 7.1 Acknowledgments ................................................. 156
+ 7.2 About this document ............................................. 157
ii
projects / apps / madmutt.git / blobdiff