by Andreas Krennmair <ak@synflood.at> and others
originally based on _\bm_\bu_\bt_\bt by Michael Elkins <me@cs.hmc.edu> and others
- version devel-r446
+ version devel-r449
A\bAb\bbs\bst\btr\bra\bac\bct\bt
^G n/a abort
<Return> n/a finish editing
- You can remap the _\be_\bd_\bi_\bt_\bo_\br functions using the _\bb_\bi_\bn_\bd (section 3.5 , page 25) com-
+ You can remap the _\be_\bd_\bi_\bt_\bo_\br functions using the _\bb_\bi_\bn_\bd (section 3.5 , page 26) com-
mand. For example, to make the _\bD_\be_\bl_\be_\bt_\be key delete the character in front of the
cursor rather than under, you could use
+\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 7.4.328 , page 168) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 , page 169) variable.
+
message is to you and you only
letter again for bold or the letter, backspace, ``_'' for denoting underline.
Mutt-ng will attempt to display these in bold and underline respectively if
your terminal supports them. If not, you can use the bold and underline _\bc_\bo_\bl_\bo_\br
- (section 3.9 , page 29) objects to specify a color or mono attribute for them.
+ (section 3.9 , page 30) objects to specify a color or mono attribute for them.
Additionally, the internal pager supports the ANSI escape sequences for charac-
ter attributes. Mutt-ng translates them into the correct color and character
The Mutt Next Generation E-Mail Client 11
Mutt-ng uses these attributes for handling text/enriched messages, and they can
- also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 77) script for high-
+ also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 78) script for high-
lighting purposes. N\bNo\bot\bte\be:\b: If you change the colors for your display, for exam-
ple by changing the color associated with color2 for your xterm, then that
color will be used instead of green.
_\b2_\b._\b5_\b._\b3 _\bT_\bh_\br_\be_\ba_\bd_\be_\bd _\bM_\bo_\bd_\be
- When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.296 , page 158) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
+ When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.296 , page 159) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
a few additional functions available in the _\bi_\bn_\bd_\be_\bx and _\bp_\ba_\bg_\be_\br modes.
^D delete-thread delete all messages in the current thread
N\bNo\bot\bte\be:\b: Collapsing a thread displays only the first message in the thread and
hides the others. This is useful when threads contain so many messages that you
can only see a handful of threads on the screen. See %M in _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (sec-
- tion 7.4.114 , page 114). For example, you could use "%?M?(#%03M)&(%4l)?" in
- _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114) to optionally display the number of
+ tion 7.4.114 , page 115). For example, you could use "%?M?(#%03M)&(%4l)?" in
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115) 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 7.4.317 , page 166).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 7.4.317 , page 167).
_\b2_\b._\b5_\b._\b4 _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\be_\bo_\bu_\bs _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
(default: a)
Creates a new alias based upon the current message (or prompts for a new one).
- Once editing is complete, an _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 24) command is added to
- the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 88) variable for
- future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 88) does not
+ Once editing is complete, an _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 25) command is added to
+ the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 89) variable for
+ future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 89) does not
add the aliases specified there-in, you must also _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page
- 44) the file.
+ 45) the file.
c\bch\bhe\bec\bck\bk-\b-t\btr\bra\bad\bdi\bit\bti\bio\bon\bna\bal\bl-\b-p\bpg\bgp\bp
(default: ESC P)
(default: h)
Toggles the weeding of message header fields specified by _\bi_\bg_\bn_\bo_\br_\be (section
- 3.10 , page 31) commands.
+ 3.10 , page 32) commands.
e\bed\bdi\bit\bt
(default: e)
This command is used to temporarily edit an attachment's content type to fix,
for instance, bogus character set parameters. When invoked from the index or
from the pager, you'll have the opportunity to edit the top-level attachment's
- content type. On the _\ba_\bt_\bt_\ba_\bc_\bh_\bm_\be_\bn_\bt _\bm_\be_\bn_\bu (section 5.1.2 , page 69), you can
+ content type. On the _\ba_\bt_\bt_\ba_\bc_\bh_\bm_\be_\bn_\bt _\bm_\be_\bn_\bu (section 5.1.2 , page 70), you can
change any attachment's content type. These changes are not persistent, and get
lost upon changing folders.
Note that this command is also available on the _\bc_\bo_\bm_\bp_\bo_\bs_\be _\bm_\be_\bn_\bu (section 5.1.3 ,
- page 70). There, it's used to fine-tune the properties of attachments you are
+ page 71). There, it's used to fine-tune the properties of attachments you are
going to send.
e\ben\bnt\bte\ber\br-\b-c\bco\bom\bmm\bma\ban\bnd\bd
This command is used to execute any command you would normally put in a config-
uration file. A common use is to check the settings of variables, or in con-
- junction with _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 28) to change settings on the fly.
+ junction with _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 29) to change settings on the fly.
e\bex\bxt\btr\bra\bac\bct\bt-\b-k\bke\bey\bys\bs
(default: ^K)
Reply to the current or tagged message(s) by extracting any addresses which
match the regular expressions given by the _\bl_\bi_\bs_\bt_\bs _\bo_\br _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 ,
- page 34) commands, but also honor any Mail-Followup-To header(s) if the
- _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.92 , page 109) configuration variable is set.
+ page 35) commands, but also honor any Mail-Followup-To header(s) if the
+ _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.92 , page 110) configuration variable is set.
Using this when replying to messages posted to mailing lists helps avoid dupli-
cate copies being sent to the author of the message you are replying to.
(default: |)
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 7.4.205 , page 138), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
- (section 7.4.207 , page 138), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.206 , page 138) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 170) control the exact behavior of this
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.205 , page 139), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 7.4.207 , page 139), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.206 , page 139) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 171) 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 7.4.340 , page 171) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 7.4.340 , page 172) 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
- 7.4.339 , page 170) can be used to control whether Mutt-ng will wait for a key
+ 7.4.339 , page 171) 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.
t\bto\bog\bgg\bgl\ble\be-\b-q\bqu\buo\bot\bte\bed\bd
(default: T)
- The _\bp_\ba_\bg_\be_\br uses the _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 143) variable to
+ The _\bp_\ba_\bg_\be_\br uses the _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 144) variable to
detect quoted text when displaying the body of the message. This function tog-
gles the display of the quoted material in the message. It is particularly
useful when are interested in just the response and there is a large amount of
sages from. You can now tag messages in that folder and they will be attached
to the message you are sending. Note that certain operations like composing a
new mail, replying, forwarding, etc. are not permitted when you are in that
- folder. The %r in _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163) will change to a
+ folder. The %r in _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 164) will change to a
'A' to indicate that you are in attach-message mode.
The Mutt Next Generation E-Mail Client 16
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 7.4.58 , page 101).
+ Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102).
_\b2_\b._\b6_\b._\b4 _\bU_\bs_\bi_\bn_\bg _\bM_\bu_\bt_\bt_\b-_\bn_\bg _\bw_\bi_\bt_\bh _\bP_\bG_\bP
Pgp: [ E | S | S_\b<_\bi_\bd_\b> ]
``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
- _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.197 , page 136) permanently.
+ _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.197 , page 137) 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-ng will not ask you
encrypted using the selected public keys, and sent out.
Most fields of the entries in the key selection menu (see also _\b$_\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\b-
- _\bm_\ba_\bt (section 7.4.184 , page 133)) have obvious meanings. But some explana-
+ _\bm_\ba_\bt (section 7.4.184 , page 134)) have obvious meanings. But some explana-
tions on the capabilities, flags, and validity fields are in order.
The flags sequence (%f) will expand to one of the following flags:
Note that different remailers do have different capabilities, indicated in the
%c entry of the remailer menu lines (see _\b$_\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.144 ,
- page 122)). Most important is the ``middleman'' capability, indicated by a
+ page 123)). Most important is the ``middleman'' capability, indicated by a
capital ``M'': This means that the remailer in question cannot be used as the
final element of a chain, but will only forward messages to other mixmaster
remailers. For details on the other capabilities, please have a look at the
At times it is desirable to delay sending a message that you have already begun
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 7.4.219 , page 141) variable. This means that you can
+ the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.219 , page 142) variable. This means that you can
recall the message even if you exit Mutt-ng and then restart it at a later
time.
be in the same folder with the message you replied to for the status of the
message to be updated.
- See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 141) quad-option.
+ See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 142) quad-option.
_\b3_\b. _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn
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 7.1 , page 81) option is specified. This
+ the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 7.1 , page 82) 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
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 7.3 , page 84) to configure Mutt-ng.
+ your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 7.3 , page 85) to configure Mutt-ng.
_\b3_\b._\b2 _\bB_\ba_\bs_\bi_\bc _\bS_\by_\bn_\bt_\ba_\bx _\bo_\bf _\bI_\bn_\bi_\bt_\bi_\ba_\bl_\bi_\bz_\ba_\bt_\bi_\bo_\bn _\bF_\bi_\bl_\be_\bs
An initialization file consists of a series of _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 7.3 , page
- 84). Each line of the file may contain one or more commands. When multiple
+ 85). 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-ng user' ; ignore x-
interpreted again.
The commands understood by mutt are explained in the next paragraphs. For a
- complete list, see the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.3 , page 84).
+ complete list, see the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.3 , page 85).
The Mutt Next Generation E-Mail Client 23
set record=+sent_on_$HOSTNAME
- sets the _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144) variable to the string _\b+_\bs_\be_\bn_\bt_\b__\bo_\bn_\b_
+ sets the _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 145) variable to the string _\b+_\bs_\be_\bn_\bt_\b__\bo_\bn_\b_
and appends the value of the evironment variable $HOSTNAME.
N\bNo\bot\bte\be:\b: There will be no warning if an environment variable is not defined. The
set imap_home_namespace = $folder
- would set the value of _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.99 , page 110) to the
- value to which _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) is _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by set to.
+ would set the value of _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.99 , page 111) to the
+ value to which _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 104) is _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by set to.
N\bNo\bot\bte\be:\b: There're no logical links established in such cases so that the the value
- for _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.99 , page 110) won't change even if
- _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) gets changed.
+ for _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.99 , page 111) won't change even if
+ _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 104) gets changed.
N\bNo\bot\bte\be:\b: There will be no warning if a configuration variable is not defined or is
empty. The result will of the expansion will then be empty.
The Mutt Next Generation E-Mail Client 24
- reserved namespace for them. All user-defined variables must be prefixed with
+ reserved namespace for them: all user-defined variables must be prefixed with
user_ and can be used just like any ordinary configuration or environment vari-
able.
reused where necessary. More advanced scenarios could include to save a vari-
able's value at the beginning of macro sequence and restore it at end.
+ When the variable is first defined, the first value it gets assigned is also
+ the initial value to which it can be reset using the reset command.
+
+ The complete removal is done via the unset keyword.
+
+ After the following sequence:
+
+ set user_foo = 42
+ set user_foo = 666
+
+ the variable $user_foo has a current value of 666 and an initial of 42. The
+ query
+
+ set ?user_foo
+
+ will show 666. After doing the reset via
+
+ reset user_foo
+
+ a following query will give 42 as the result. After unsetting it via
+
+ The Mutt Next Generation E-Mail Client 25
+
+ unset user_foo
+
+ any query or operation (except the noted expansion within other statements)
+ will lead to an error message.
+
_\b3_\b._\b3_\b._\b5 _\bT_\by_\bp_\be _\bC_\bo_\bn_\bv_\be_\br_\bs_\bi_\bo_\bn_\bs
A note about variable's types during conversion: internally values are stored
N\bNo\bot\bte\be:\b: if you want to create an alias for a group (by specifying more than one
address), you m\bmu\bus\bst\bt separate the addresses with a comma (``,'').
- The Mutt Next Generation E-Mail Client 25
-
To remove an alias or aliases (``*'' means all aliases):
unalias [ * | _\bk_\be_\by _\b._\b._\b. ]
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.29 , page 44). Consequently, you can
+ long as this file is _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.29 , page 45). 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.5.4 , page 11) function can use
- only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 88)
+ only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 89)
variable (which is ~/.muttrc by default). This file is not special either, in
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.29 , page 44) this file too.
+ 3.29 , page 45) this file too.
+
+ The Mutt Next Generation E-Mail Client 26
For example:
To use aliases, you merely use the alias at any place in mutt where mutt
prompts for addresses, such as the _\bT_\bo_\b: or _\bC_\bc_\b: prompt. You can also enter
aliases in your editor at the appropriate headers if you have the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs
- (section 7.4.58 , page 101) variable set.
+ (section 7.4.58 , page 102) variable set.
In addition, at the various address prompts, you can use the tab character to
expand a partial alias to the full alias. If there are multiple matches, mutt
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 Next Generation E-Mail Client 26
-
- 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
The attachment menu is used to access the attachments on received
messages.
+ The Mutt Next Generation E-Mail Client 27
+
browser
The browser is used for both browsing the local directory struc-
ture, and for listing all of your incoming mailboxes.
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 Next Generation E-Mail Client 27
-
In addition, _\bk_\be_\by may consist of:
+ The Mutt Next Generation E-Mail Client 28
+
\t tab
<tab> tab
<backtab> backtab / shift-tab
_\bk_\be_\by does not need to be enclosed in quotes unless it contains a space (`` '').
_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn specifies which action to take when _\bk_\be_\by is pressed. For a complete
- list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 172). The special
+ list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 173). The special
function noop unbinds the specified key sequence.
_\b3_\b._\b6 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs _\bf_\bo_\br _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bs_\be_\bt_\bs
_\b3_\b._\b7 _\bS_\be_\bt_\bt_\bi_\bn_\bg _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs _\bb_\ba_\bs_\be_\bd _\bu_\bp_\bo_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- The Mutt Next Generation E-Mail Client 28
-
Usage: folder-hook [!]_\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- 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
+ It is often desirable to change settings based on which mailbox you are
+
+ The Mutt Next Generation E-Mail Client 29
+
+ reading. 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
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.
N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page
- 160) at the beginning of the pattern, you must place it inside of double or
+ 161) at the beginning of the pattern, you must place it inside of double or
single quotes in order to distinguish it from the logical _\bn_\bo_\bt operator for the
expression.
rating them.
_\bk_\be_\by and _\bs_\be_\bq_\bu_\be_\bn_\bc_\be are expanded by the same rules as the _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs (section
- 3.5 , page 25). There are some additions however. The first is that control
+ 3.5 , page 26). There are some additions however. The first is that control
characters in _\bs_\be_\bq_\bu_\be_\bn_\bc_\be can also be specified as _\b^_\bx. In order to get a caret
(`^'') you need to use _\b^_\b^. Secondly, to specify a certain key such as _\bu_\bp or to
invoke a function directly, you can use the format _\b<_\bk_\be_\by _\bn_\ba_\bm_\be_\b> and _\b<_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
_\bn_\ba_\bm_\be_\b>. For a listing of key names see the section on _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs (section
- 3.5 , page 25). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
- 7.5 , page 172).
+ 3.5 , page 26). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
+ 7.5 , page 173).
The advantage with using function names directly is that the macros will work
-
- The Mutt Next Generation E-Mail Client 29
-
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
+
+ The Mutt Next Generation E-Mail Client 30
+
(eg. the system Muttngrc).
Optionally you can specify a descriptive text after _\bs_\be_\bq_\bu_\be_\bn_\bc_\be, which is shown in
+\bo normal
- +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 143) in the
+ +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 144) in the
body of a message)
- The Mutt Next Generation E-Mail Client 30
-
+\bo quoted1, quoted2, ..., quotedN\bN (higher levels of quoting)
+\bo search (highlighting of words in the pager)
+ The Mutt Next Generation E-Mail Client 31
+
+\bo signature
+\bo status (mode lines used to display info about the mailbox or message)
instead of _\bw_\bh_\bi_\bt_\be and _\by_\be_\bl_\bl_\bo_\bw when setting this variable.
N\bNo\bot\bte\be:\b: The uncolor command can be applied to the index object only. It removes
-
- The Mutt Next Generation E-Mail Client 31
-
entries from the list. You m\bmu\bus\bst\bt specify the same pattern specified in the color
command for it to be removed. The pattern ``*'' is a special token which means
to clear the color index list of all entries.
+ The Mutt Next Generation E-Mail Client 32
+
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
For example:
- The Mutt Next Generation E-Mail Client 32
-
# Sven's draconian header weeding
ignore *
unignore from date subject to cc
unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
unignore posted-to:
+ The Mutt Next Generation E-Mail Client 33
+
_\b3_\b._\b1_\b1 _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be _\ba_\bd_\bd_\br_\be_\bs_\bs_\be_\bs
Usage: [un]alternates _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
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 7.4.238 , page 145).)
+ _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.238 , page 146).)
Many users receive e-mail under a number of different addresses. To fully use
mutt's features here, the program must be able to recognize what e-mail
fixed-size terminals.
For introductory information on format=flowed messages, see
-
- The Mutt Next Generation E-Mail Client 33
-
<http://www.joeclark.org/ffaq.html>.
_\b3_\b._\b1_\b2_\b._\b2 _\bR_\be_\bc_\be_\bi_\bv_\bi_\bn_\bg_\b: _\bD_\bi_\bs_\bp_\bl_\ba_\by _\bS_\be_\bt_\bu_\bp
your terminal. If you want a fixed margin on the right side of your terminal,
you can set the following:
+ The Mutt Next Generation E-Mail Client 34
+
set wrapmargin = 10
The code above makes the line break 10 columns before the right side of the
> production server that we want to set up before our customer's
> project will go live.
- The Mutt Next Generation E-Mail Client 34
-
_\b3_\b._\b1_\b2_\b._\b3 _\bS_\be_\bn_\bd_\bi_\bn_\bg
If you want mutt-ng to send emails with format=flowed set, you need to explic-
set text_flowed
+ The Mutt Next Generation E-Mail Client 35
+
Additionally, you have to use an editor which supports writing format=flowed-
conforming emails. For vim, this is done by adding w to the formatoptions (see
:h formatoptions and :h fo-table) when writing emails.
"
- For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.50 , page 99) variable pro-
+ For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.50 , page 100) variable pro-
vides the mechanism to generate a DelSp=yes parameter on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg messages.
According to the standard, clients receiving a format=flowed messages should
delete the last space of a flowed line but still interpret the line as flowed.
Usage: [un]subscribe _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
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.10 ,
- page 59). In order to take advantage of them, you must specify which addresses
-
- The Mutt Next Generation E-Mail Client 35
-
+ page 60). 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.5.4 , page 12) function will
work for all known lists. Additionally, when you send a message to a sub-
the Mail-Followup-To header is a non-standard extension which is not supported
by all mail user agents. Adding it is not bullet-proof against receiving per-
sonal CCs of list messages. Also note that the generation of the Mail-Fol-
- lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.70 , page 104)
+ lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.70 , page 105)
configuration variable.
+ The Mutt Next Generation E-Mail Client 36
+
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,
Unlike some of the other _\bh_\bo_\bo_\bk commands, only the _\bf_\bi_\br_\bs_\bt matching pattern is used
(it is not possible to save read mail in more than a single mailbox).
- The Mutt Next Generation E-Mail Client 36
-
_\b3_\b._\b1_\b5 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs _\bw_\bh_\bi_\bc_\bh _\br_\be_\bc_\be_\bi_\bv_\be _\bm_\ba_\bi_\bl
Usage: [un]mailboxes [!]_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
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.
+
+ The Mutt Next Generation E-Mail Client 37
+
Mutt-ng will automatically enter this mode when invoked from the command line
with the -y option.
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.9 , page
- 59) (such as ``='' and ``!''), any variable definition that affect these char-
- acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 7.4.302 , page 160)) should be executed before the mailboxes command.
+ 60) (such as ``='' and ``!''), any variable definition that affect these char-
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 104) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 7.4.302 , page 161)) should be executed before the mailboxes command.
_\b3_\b._\b1_\b6 _\bU_\bs_\be_\br _\bd_\be_\bf_\bi_\bn_\be_\bd _\bh_\be_\ba_\bd_\be_\br_\bs
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
-
- The Mutt Next Generation E-Mail Client 37
-
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 7.4.58 , page 101) variable, or use the _\be_\bd_\bi_\bt_\b-
+ set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102) variable, or use the _\be_\bd_\bi_\bt_\b-
_\bh_\be_\ba_\bd_\be_\br_\bs function (default: ``E'') in the send-menu so that you can edit the
header of your message along with the body.
remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
use:
+ The Mutt Next Generation E-Mail Client 38
+
unmy_hdr to cc
_\b3_\b._\b1_\b7 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\bt_\bh_\be _\bo_\br_\bd_\be_\br _\bo_\bf _\bh_\be_\ba_\bd_\be_\br_\bs _\bw_\bh_\be_\bn _\bv_\bi_\be_\bw_\bi_\bn_\bg _\bm_\be_\bs_\bs_\ba_\bg_\be_\bs
an address matching _\br_\be_\bg_\be_\bx_\bp or if you are the author and the message is
addressed _\bt_\bo_\b: something matching _\br_\be_\bg_\be_\bx_\bp.
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 56) for information on the
+ See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Examples:
save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
save-hook aol\\.com$ +spam
- Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 38) command.
-
- The Mutt Next Generation E-Mail Client 38
+ Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 39) command.
_\b3_\b._\b1_\b9 _\bS_\bp_\be_\bc_\bi_\bf_\by _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bF_\bc_\bc_\b: _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\bw_\bh_\be_\bn _\bc_\bo_\bm_\bp_\bo_\bs_\bi_\bn_\bg
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 7.4.235 , page 144). Mutt-ng searches the initial list of message
+ (section 7.4.235 , page 145). 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
- 7.4.235 , page 144) mailbox.
+ 7.4.235 , page 145) mailbox.
+
+ The Mutt Next Generation E-Mail Client 39
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 56) for information on the
+ See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example: fcc-hook [@.]aol\\.com$ +spammers
The above will save a copy of all messages going to the aol.com domain to the
`+spammers' mailbox by default. Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 ,
- page 38) command.
+ page 39) command.
_\b3_\b._\b2_\b0 _\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 _\ba_\bn_\bd _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bF_\bc_\bc_\b: _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\ba_\bt _\bo_\bn_\bc_\be
Usage: fcc-save-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is a shortcut, equivalent to doing both a _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section
- 3.19 , page 38) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 37) with its arguments.
+ 3.19 , page 38) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 38) with its arguments.
_\b3_\b._\b2_\b1 _\bC_\bh_\ba_\bn_\bg_\be _\bs_\be_\bt_\bt_\bi_\bn_\bg_\bs _\bb_\ba_\bs_\be_\bd _\bu_\bp_\bo_\bn _\bm_\be_\bs_\bs_\ba_\bg_\be _\br_\be_\bc_\bi_\bp_\bi_\be_\bn_\bt_\bs
send2-hook is matched every time a message is changed, either by editing it, or
by using the compose menu to change its recipients or subject. send2-hook is
executed after send-hook, and can, e.g., be used to set parameters such as the
- _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page 148) variable depending on the message's
+ _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page 149) variable depending on the message's
sender address.
- The Mutt Next Generation E-Mail Client 39
-
For each type of send-hook or reply-hook, when multiple matches occur, commands
are executed in the order they are specified in the muttrc (for that type of
hook).
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 56) for information on the
+ See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example: send-hook mutt 'set mime_forward signature='''
- Another typical use for this command is to change the values of the _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\b-
- _\bt_\bi_\bo_\bn (section 7.4.18 , page 92), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.264 , page 151) and
- _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.118 , page 117) variables in order to change the language
- of the attributions and signatures based upon the recipients.
+ Another typical use for this command is to change the values of the
+
+ The Mutt Next Generation E-Mail Client 40
+
+ _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 93), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.264 , page
+ 152) and _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.118 , page 118) variables in order to change the
+ language of the attributions and signatures based upon the recipients.
N\bNo\bot\bte\be:\b: the send-hook's are only executed ONCE after getting the initial list of
recipients. Adding a recipient after replying or editing the message will NOT
tiple matches occur, commands are executed in the order they are specified in
the muttrc.
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 56) for information on the
+ See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example:
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 Mutt Next Generation E-Mail Client 40
-
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: push _\bs_\bt_\br_\bi_\bn_\bg
- This command adds the named string to the keyboard buffer. The string may con-
- tain control characters, key names and function names like the sequence string
- in the _\bm_\ba_\bc_\br_\bo (section 3.8 , page 28) command. You may use it to automatically
- run a sequence of commands at startup, or when entering certain folders.
+ This command adds the named string to the keyboard buffer. The string may
+
+ The Mutt Next Generation E-Mail Client 41
+
+ contain control characters, key names and function names like the sequence
+ string in the _\bm_\ba_\bc_\br_\bo (section 3.8 , page 29) command. You may use it to auto-
+ matically run a sequence of commands at startup, or when entering certain fold-
+ ers.
_\b3_\b._\b2_\b5 _\bE_\bx_\be_\bc_\bu_\bt_\bi_\bn_\bg _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
Usage: exec _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
This command can be used to execute any function. Functions are listed in the
- _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 172). ``exec function'' is equivalent
+ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 173). ``exec function'' is equivalent
to ``push <function>''.
_\b3_\b._\b2_\b6 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bS_\bc_\bo_\br_\bi_\bn_\bg
score "~f santaclaus@northpole\.int" =666
- The Mutt Next Generation E-Mail Client 41
-
What is important to note is that negative score values will be rounded up to
0.
+\bo flag threshold: when a message has a score value equal or higher than the
flag threshold, it will be flagged.
+ The Mutt Next Generation E-Mail Client 42
+
+\bo read threshold: when a message has a score value equal or lower than the
read threshold, it will be marked as read.
delete threshold, it will be marked as deleted.
These three thresholds can be set via the variables _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bf_\bl_\ba_\bg (sec-
- tion 7.4.249 , page 148), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.250 , page 148),
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.248 , page 148) and. By default,
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.250 , page 148) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
- (section 7.4.248 , page 148) are set to -1, which means that in the default
+ tion 7.4.249 , page 149), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.250 , page 149),
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.248 , page 149) and. By default,
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.250 , page 149) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
+ (section 7.4.248 , page 149) are set to -1, which means that in the default
threshold configuration no message will ever get marked as read or deleted.
Scoring gets especially interesting when combined with the color command and
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
- the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114) variable.
+ the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115) variable.
(Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
given message.)
Your first step is to define your external filter's spam patterns using the
spam command. _\bp_\ba_\bt_\bt_\be_\br_\bn should be a regular expression that matches a header in a
mail message. If any message in the mailbox matches this regular expression, it
-
- The Mutt Next Generation E-Mail Client 42
-
will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
nospam pattern -- see below.) The appearance of this attribute is entirely up
to you, and is governed by the _\bf_\bo_\br_\bm_\ba_\bt parameter. _\bf_\bo_\br_\bm_\ba_\bt can be any static text,
with the second, etc.
If you're using multiple spam filters, a message can have more than one spam-
+
+ The Mutt Next Generation E-Mail Client 43
+
related header. You can define spam patterns for each filter you use. If a mes-
sage matches two or more of these patterns, and the $spam_separator variable is
set to a string, then the message's spam tag will consist of all the _\bf_\bo_\br_\bm_\ba_\bt
still do something useful.
The nospam command can be used to write exceptions to spam patterns. If a
-
- The Mutt Next Generation E-Mail Client 43
-
header pattern matches something in a spam command, but you nonetheless do not
want it to receive a spam tag, you can list a more precise pattern under a
nospam command.
instead of adding an exception. Likewise, if the _\bp_\ba_\bt_\bt_\be_\br_\bn for a spam command
matches an entry on the nospam list, that nospam entry will be removed. If the
_\bp_\ba_\bt_\bt_\be_\br_\bn for nospam is ``*'', _\ba_\bl_\bl _\be_\bn_\bt_\br_\bi_\be_\bs _\bo_\bn _\bb_\bo_\bt_\bh _\bl_\bi_\bs_\bt_\bs will be removed. This
+
+ The Mutt Next Generation E-Mail Client 44
+
might be the default action if you use spam and nospam in conjunction with a
folder-hook.
Usage: reset _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
This command is used to set (and unset) _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 ,
- page 86). There are four basic types of variables: boolean, number, string and
+ page 87). There are four basic types of variables: boolean, number, string and
quadoption. _\bb_\bo_\bo_\bl_\be_\ba_\bn variables can be _\bs_\be_\bt (true) or _\bu_\bn_\bs_\be_\bt (false). _\bn_\bu_\bm_\bb_\be_\br
variables can be assigned a positive integer value.
toggle the value (on or off). This is useful when writing macros. Example:
set invsmart_wrap.
- The Mutt Next Generation E-Mail Client 44
-
The toggle command automatically prepends the inv prefix to all specified vari-
ables.
Using the enter-command function in the _\bi_\bn_\bd_\be_\bx menu, you can query the value of
a variable by prefixing the name of the variable with a question mark:
+ The Mutt Next Generation E-Mail Client 45
+
set ?allow_8bit
The question mark is actually only required for boolean and quadoption vari-
_\b3_\b._\b3_\b1 _\bS_\bh_\ba_\br_\bi_\bn_\bg _\bS_\be_\bt_\bu_\bp_\bs
- The Mutt Next Generation E-Mail Client 45
-
_\b3_\b._\b3_\b1_\b._\b1 _\bC_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bS_\be_\bt_\bs
As users may run mutt-ng on different systems, the configuration must be main-
specify in which character set their configuration files are encoded. Please
note that while reading the configuration files, this is only respected after
the corresponding declaration appears. It's advised to put the following at the
+
+ The Mutt Next Generation E-Mail Client 46
+
very beginning of a users muttngrc:
set config_charset = "..."
...whereby <item> can be one of:
- The Mutt Next Generation E-Mail Client 46
-
+\bo a function name
+\bo a variable name
All available functions, variables and menus are documented elsewhere in this
manual but ``features'' is specific to these two commands. To test for one,
+
+ The Mutt Next Generation E-Mail Client 47
+
prefix one of the following keywords with feature_:
ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
An example for testing for variable names can be used if users use different
revisions of mutt-ng whereby the older one may not have a certain variable. To
- test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.103 , page 111),
+ test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.103 , page 112),
use:
ifdef imap_mail_check 'set imap_mail_check = 300'
Provided for completeness is the test for menu names. To set _\b$_\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
- (section 7.4.174 , page 130) only if the pager menu is available, use:
+ (section 7.4.174 , page 131) only if the pager menu is available, use:
ifdef pager 'set pager_index_lines = 10'
ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
- The Mutt Next Generation E-Mail Client 47
-
...and...
ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
+ The Mutt Next Generation E-Mail Client 48
+
_\b3_\b._\b3_\b2 _\bO_\bb_\bs_\bo_\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
In the process of ensuring and creating more consistency, many variables have
been renamed and some of the old names were already removed. Please see _\bO_\bb_\bs_\bo_\b-
- _\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 , page 86) for a complete list.
+ _\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 , page 87) for a complete list.
_\b4_\b. _\bA_\bd_\bv_\ba_\bn_\bc_\be_\bd _\bU_\bs_\ba_\bg_\be
_\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-ng including those in more complex _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
- tion 7.2 , page 82) must be specified using regular expressions (regexp) in
+ tion 7.2 , page 83) 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.
sign ``$'' are metacharacters that respectively match the empty string at the
beginning and end of a line.
- The Mutt Next Generation E-Mail Client 48
-
A list of characters enclosed by ``['' and ``]'' matches any single character
in that list; if the first character of the list is a caret ``^'' then it
matches any character n\bno\bot\bt in the list. For example, the regular expression
place it anywhere but first. Finally, to include a literal hyphen ``-'' place
it last.
+ The Mutt Next Generation E-Mail Client 49
+
Certain named classes of characters are predefined. Character classes consist
of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
defined by the POSIX standard:
A character class is only valid in a regular expression inside the brackets of
a character list. Note that the brackets in these class names are part of the
-
- The Mutt Next Generation E-Mail Client 49
-
symbolic names, and must be included in addition to the brackets delimiting the
bracket list. For example, [\b[[\b[:\b:d\bdi\big\bgi\bit\bt:\b:]\b]]\b] is equivalent to [\b[0\b0-\b-9\b9]\b].
Collating Symbols
A collating symbol is a multi-character collating element enclosed
+
+ The Mutt Next Generation E-Mail Client 50
+
in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
ment, then [\b[[\b[.\b.c\bch\bh.\b.]\b]]\b] is a regexp that matches this collating ele-
ment, while [\b[c\bch\bh]\b] is a regexp that matches either ``c'' or ``h''.
ing regular expression matches any string matching either subexpression.
Repetition takes precedence over concatenation, which in turn takes precedence
-
- The Mutt Next Generation E-Mail Client 50
-
over alternation. A whole subexpression may be enclosed in parentheses to
override these precedence rules.
Matches the empty string at either the beginning or the end of a
word.
+ The Mutt Next Generation E-Mail Client 51
+
\\B
Matches the empty string within a word.
to match messages, e.g. for operations like tagging and scoring. A pattern con-
sists of one or more sub-pattern, which can be logically grouped, ORed, and
negated. For a complete listing of these patterns, please refer to table _\bP_\ba_\bt_\b-
- _\bt_\be_\br_\bn_\bs (section 7.2 , page 82) in the Reference chapter.
+ _\bt_\be_\br_\bn_\bs (section 7.2 , page 83) in the Reference chapter.
It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
most simple possibility is to logically AND several patterns by stringing them
together:
- The Mutt Next Generation E-Mail Client 51
-
~s 'SPAM' ~U
The pattern above matches all messages that contain ``SPAM'' in the subject and
To logical OR patterns, simply use the | operator. This one especially useful
when using local groups:
+ The Mutt Next Generation E-Mail Client 52
+
~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
(~b mutt-ng|~s Mutt-ng)
!~x '@synflood\.at'
date ranges between a fixed number of units and the current date. How this
works can be seen in the following example:
- The Mutt Next Generation E-Mail Client 52
-
~d >2w # messages older than two weeks
~d <3d # messages newer than 3 days
~d =1m # messages that are exactly one month old
_\b4_\b._\b3_\b._\b1 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn
+ The Mutt Next Generation E-Mail Client 53
+
The so called _\bF_\bo_\br_\bm_\ba_\bt _\bS_\bt_\br_\bi_\bn_\bg_\bs offer great flexibility when configuring mutt-ng.
In short, they describe what items to print out how in menus and status mes-
sages.
+\bo the current mutt-ng version number
The setting for the status bar of the index is controlled via the _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\b-
- _\bm_\ba_\bt (section 7.4.313 , page 163) variable. For the hostname and version
+ _\bm_\ba_\bt (section 7.4.313 , page 164) variable. For the hostname and version
string, there's an expando for $status_format: %h expands to the hostname and
%v to the version string. When just configuring:
To include the mailbox' name is as easy as:
- The Mutt Next Generation E-Mail Client 53
-
set status_format = "%v on %h: %B: ...
When the currently opened mailbox is Inbox, this will be expanded to:
For the number of certain types of messages, one more feature of the format
strings is extremely useful. If there aren't messages of a certain type, it may
+
+ The Mutt Next Generation E-Mail Client 54
+
not be desired to print just that there aren't any but instead only print some-
thing if there are any.
+\bo and make it print ``no new messages'' if there aren't any
- The Mutt Next Generation E-Mail Client 54
-
The corresponding configuration is:
set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
+ The Mutt Next Generation E-Mail Client 55
+
As you might see from this rather simple example, one can create very complex
but fancy status messages. Please see the reference chapter for expandos and
those which may be printed nonzero.
set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
- The Mutt Next Generation E-Mail Client 55
-
_\b4_\b._\b4 _\bU_\bs_\bi_\bn_\bg _\bT_\ba_\bg_\bs
Sometimes it is desirable to perform an operation on a group of messages all at
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 7.2 , page 82) for Mutt-ng's pattern matching
+
+ The Mutt Next Generation E-Mail Client 56
+
+ default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 83) for Mutt-ng's pattern matching
syntax.
Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
operator is used, the n\bne\bex\bxt\bt operation will be applied to all tagged messages if
that operation can be used in that manner. If the _\b$_\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg (section 7.4.19 ,
- page 92) variable is set, the next operation applies to the tagged messages
+ page 93) variable is set, the next operation applies to the tagged messages
automatically, without requiring the ``tag-prefix''.
- In _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 28) or _\bp_\bu_\bs_\bh (section 3.24 , page 40) commands,
+ In _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 29) or _\bp_\bu_\bs_\bh (section 3.24 , page 40) 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-ng will
stop "eating" the macro when it encounters the ``end-cond'' operator; after
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-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 47) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 82) along
+ _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 48) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 83) along
with a configuration option/command. See
+\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 28)
- +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 38)
+ +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 39)
- +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 39)
+ +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 40)
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 37)
+ +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 38)
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35)
+ +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36)
+\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)
- +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 38)
+ +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 39)
for specific details on each type of _\bh_\bo_\bo_\bk available.
N\bNo\bot\bte\be:\b: if a hook changes configuration settings, these changes remain effective
until the end of the current mutt session. As this is generally not desired, a
default hook needs to be added before all other hooks to restore configuration
-
- The Mutt Next Generation E-Mail Client 56
-
defaults. Here is an example with send-hook and the my_hdr directive:
send-hook . 'unmy_hdr From:'
send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
+ The Mutt Next Generation E-Mail Client 57
+
_\b4_\b._\b5_\b._\b1 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs
Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
evaluated in a slightly different manner. For the other types of hooks, a _\br_\be_\bg_\b-
- _\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 47) is sufficient. But in dealing with
+ _\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 48) is sufficient. But in dealing with
messages a finer grain of control is needed for matching since for different
purposes you want to match different criteria.
- Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 82) language
+ Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 83) 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
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-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
- 7.4.48 , page 98) 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 7.4.48 , page 98) that is in
+ 7.4.48 , page 99) 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 7.4.48 , page 99) that is in
effect at that time will be used.
_\b4_\b._\b6 _\bU_\bs_\bi_\bn_\bg _\bt_\bh_\be _\bs_\bi_\bd_\be_\bb_\ba_\br
If you want to specify the mailboxes you can do so with:
- The Mutt Next Generation E-Mail Client 57
-
set mbox='=INBOX'
mailboxes INBOX \
MBOX1 \
You can also specify the colors for mailboxes with new mails by using:
+ The Mutt Next Generation E-Mail Client 58
+
color sidebar_new red black
color sidebar white black
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 7.4.226 , page 142) vari-
+ simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.226 , page 143) vari-
able, you specify the wrapper command to use. For example:
set query_command = "mutt_ldap_query.pl '%s'"
The wrapper script should accept the query on the command-line. It should
return a one line message, then each matching response on a single line, each
-
- The Mutt Next Generation E-Mail Client 58
-
line containing a tab separated address then name then some other optional
information. On error, or if there are no matching addresses, return a non-
zero exit code and a one line error message.
Searching database ... 20 entries ... 3 matching:
me@cs.hmc.edu Michael Elkins mutt dude
blong@fiction.net Brandon Long mutt and more
+
+ The Mutt Next Generation E-Mail Client 59
+
roessler@guug.de Thomas Roessler mutt pgp
There are two mechanisms for accessing the query function of mutt. One is to
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-ng
- uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.130 , page 119)
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.130 , page 120)
variable.
m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All messages are
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-ng
-
- The Mutt Next Generation E-Mail Client 59
-
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
ment for sendmail). Similar to _\bM_\bH, except that it adds three subdirectories of
the mailbox: _\bt_\bm_\bp, _\bn_\be_\bw and _\bc_\bu_\br. Filenames for the messages are chosen in such a
way they are unique, even when two programs are writing the mailbox over NFS,
+
+ The Mutt Next Generation E-Mail Client 60
+
which means that no file locking is needed.
_\b4_\b._\b9 _\bM_\ba_\bi_\bl_\bb_\bo_\bx _\bS_\bh_\bo_\br_\bt_\bc_\bu_\bt_\bs
These shortcuts can be used anywhere you are prompted for a file or mailbox
path.
- +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 160) (incoming)
+ +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 161) (incoming)
mailbox
- +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 119) file
+ +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 120) file
- +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144) file
+ +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 145) file
+\bo ^ -- refers to the current mailbox
+\bo ~ -- refers to your home directory
- +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) directory
+ +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 104) 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.18 , page 37) as
+ +\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.18 , page 38) as
determined by the address of the alias
_\b4_\b._\b1_\b0 _\bH_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bM_\ba_\bi_\bl_\bi_\bn_\bg _\bL_\bi_\bs_\bt_\bs
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.13 , page 34) commands in your muttrc.
+ (section 3.13 , page 35) commands in your muttrc.
Now that Mutt-ng knows what your mailing lists are, it can do several things,
the first of which is the ability to show the name of a list through which you
received a message (i.e., of a subscribed list) in the _\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 7.4.114 , page 114) variable, the escape
+ box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115) variable, the escape
``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
-
- The Mutt Next Generation E-Mail Client 60
-
field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
returns the name of the author).
person. The ``list-reply'' function, which by default is bound to ``L'' in the
_\bi_\bn_\bd_\be_\bx menu and _\bp_\ba_\bg_\be_\br, helps reduce the clutter by only replying to the known
mailing list addresses instead of all recipients (except as specified by Mail-
+
+ The Mutt Next Generation E-Mail Client 61
+
Followup-To, see below).
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 7.4.70 , page 104) option is set, mutt will
+ and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.70 , page 105) 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
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
- (section 7.4.92 , page 109) configuration variable is set. Using list-reply
+ (section 7.4.92 , page 110) configuration variable is set. Using list-reply
will in this case also make sure that the reply goes to the mailing list, even
if it's not specified in the list of recipients in the Mail-Followup-To.
the message. This can create problems when trying to reply directly to the
author in private, since most mail clients will automatically reply to the
address given in the ``Reply-To'' field. Mutt-ng uses the _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section
- 7.4.238 , page 145) variable to help decide which address to use. If set to
+ 7.4.238 , page 146) 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
address given in the ``From'' field. When set to _\by_\be_\bs, the ``Reply-To'' field
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 7.4.114 , page 114) variable's ``%y'' and ``%Y''
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115) variable's ``%y'' and ``%Y''
escapes 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 easily be inserted by procmail and other mail filtering agents.
- Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 7.4.296 , page 158) the mail-
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 7.4.296 , page 159) the mail-
box into _\bt_\bh_\br_\be_\ba_\bd_\bs (section 2.5.3 , page 11). 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
-
- The Mutt Next Generation E-Mail Client 61
-
- graphically. If you've ever used a threaded news client, this is the same con-
- cept. It makes dealing with large volume mailing lists easier because you can
- easily delete uninteresting threads and quickly find topics of value.
+ 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_\b1 _\bE_\bd_\bi_\bt_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
Mutt-ng has the ability to dynamically restructure threads that are broken
+
+ The Mutt Next Generation E-Mail Client 62
+
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.
To support this, there are two variables:
- +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.55 , page 100) is used to request receipts for
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.55 , page 101) is used to request receipts for
different results (such as failed message, message delivered, etc.).
- The Mutt Next Generation E-Mail Client 62
-
- +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 7.4.56 , page 100) requests how much of your message
+ +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 7.4.56 , page 101) requests how much of your message
should be returned with the receipt (headers or full message).
Please see the reference chapter for possible values.
_\b4_\b._\b1_\b3 _\bP_\bO_\bP_\b3 _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
+ The Mutt Next Generation E-Mail Client 63
+
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.
Polling for new mail is more expensive over POP3 than locally. For this reason
the frequency at which Mutt-ng will check for mail remotely can be controlled
- by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.213 , page 140) variable, which defaults
+ by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.213 , page 141) 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
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 7.4.211 , page 139), fetch all your
- new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 160).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.211 , page 140), fetch all your
+ new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 161).
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-
INBOX is the special name for your spool mailbox on the IMAP server. If you
want to access another mail folder at the IMAP server, you should use
imap://imapserver/path/to/folder where path/to/folder is the path of the folder
-
- The Mutt Next Generation E-Mail Client 63
-
you want to access.
You can select an alternative port by specifying it with the server, i.e.:
name@imapserver[:port]/INBOX.
If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+
+ The Mutt Next Generation E-Mail Client 64
+
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-
When browsing folders on an IMAP server, you can toggle whether to look at only
the folders you are subscribed to, or all folders with the _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
- command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.101 , page 111)
+ command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.101 , page 112)
variable.
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 7.4.103 , page 111) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.326 , page 168) variables.
+ want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.103 , page 112) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.326 , page 169) 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 Next Generation E-Mail Client 64
-
_\b4_\b._\b1_\b4_\b._\b2 _\bA_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bi_\bo_\bn
Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
which allows you to log in to a public IMAP server without having an account.
To use ANONYMOUS, simply make your username blank or "anonymous".
+ The Mutt Next Generation E-Mail Client 65
+
SASL is a special super-authenticator, which selects among several protocols
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
available on your host and the server. Using some of these methods (including
There are a few variables which control authentication:
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.109 , page 113) - controls the username under
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.109 , page 114) - controls the username under
which you request authentication on the IMAP server, for all authentica-
tors. This is overridden by an explicit username in the mailbox path (i.e.
by using a mailbox name of the form {user@host}).
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.104 , page 112) - a password which you may pre-
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.104 , page 113) - a password which you may pre-
set, used by all authentication methods where a password is needed.
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs (section 7.4.95 , page 109) - a colon-delimited list
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs (section 7.4.95 , page 110) - a colon-delimited list
of IMAP authentication methods to try, in the order you wish to try them.
If specified, this overrides mutt's default (attempt everything, in the
order listed above).
The Default newsserver can be obtained from the $NNTPSERVER environment vari-
able. Like other news readers, info about subscribed newsgroups is saved in a
- file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 7.4.161 , page 127) variable.
+ file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 7.4.161 , page 128) variable.
Article headers are cached and can be loaded from a file when a newsgroup is
entered instead loading from newsserver; currently, this caching mechanism
still is different from the header caching for maildir/IMAP.
Especially for Usenet, people often ask for advanced filtering and scoring
functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
-
- The Mutt Next Generation E-Mail Client 65
-
to use a killfile has been discussed in _\bM_\be_\bs_\bs_\ba_\bg_\be _\bs_\bc_\bo_\br_\bi_\bn_\bg (section 3.26 , page
- 40).
+ 41).
What has not been discusses in detail is mutt-ng's built-in realname filter.
For may newsreaders including those for ``advanced users'' like _\bs_\bl_\br_\bn or _\bt_\bi_\bn,
In mutt-ng this is as easy as
+ The Mutt Next Generation E-Mail Client 66
+
score ~* =42
This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
functionality. When configure was called with --with-libesmtp or the output
muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
support includes support for Delivery Status Notification (see _\bD_\be_\bl_\bi_\bv_\be_\br_\by _\bS_\bt_\ba_\bt_\bu_\bs
- _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 61) section) as well as handling the 8BIT-
- MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.333 , page 169).
+ _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 62) section) as well as handling the 8BIT-
+ MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.333 , page 170).
To enable sending mail directly via SMTP without an MTA such as Postfix or
- SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.291 , page 157)
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.291 , page 158)
variable pointing to your SMTP server.
- The Mutt Next Generation E-Mail Client 66
-
Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 7.4.295 ,
- page 158) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.292 , page 157) variables.
+ page 159) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.292 , page 158) variables.
Transport Encryption via the StartTLS command is also available. For this to
work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
- _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 7.4.294 , page 158) variable must be either set to
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 7.4.294 , page 159) variable must be either set to
``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
supports it: for the second case, the connection will fail if it doesn't while
switching back to unencrypted communication for the first one.
Some mail providers require user's to set a particular envelope sender, i.e.
+
+ The Mutt Next Generation E-Mail Client 67
+
they allow for only one value which may not be what the user wants to send as
the From: header. In this case, the variable _\b$_\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be (section 7.4.290 ,
- page 157) may be used to set the envelope different from the From: header.
+ page 158) may be used to set the envelope different from the From: header.
_\b4_\b._\b1_\b7 _\bM_\ba_\bn_\ba_\bg_\bi_\bn_\bg _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bI_\bM_\bA_\bP_\b/_\bP_\bO_\bP_\b/_\bN_\bN_\bT_\bP _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\bs _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
an arbitrary format, provided that the user has a script to convert from/to
this format to one of the accepted.
- The Mutt Next Generation E-Mail Client 67
-
The most common use is to open compressed archived folders e.g. with gzip.
In addition, the user can provide a script that gets a folder in an accepted
may be faster than converting the entire folder to the accepted format, append-
ing to it and converting back to the user-defined format.
- There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 67), _\bc_\bl_\bo_\bs_\be_\b-
- _\bh_\bo_\bo_\bk (section 4.19.2 , page 67) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68))
+ There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 68), _\bc_\bl_\bo_\bs_\be_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.2 , page 68) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69))
which define commands to uncompress and compress a folder and to append mes-
sages to an existing compressed folder respectively.
+ The Mutt Next Generation E-Mail Client 68
+
For example:
open-hook \\.gz$ "gzip -cd %f > %t"
append-hook \\.gz$ "gzip -c %t >> %f"
You do not have to specify all of the commands. If you omit _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (sec-
- tion 4.19.3 , page 68), the folder will be open and closed again each time you
- will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67) (or give
+ tion 4.19.3 , page 69), the folder will be open and closed again each time you
+ will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68) (or give
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.19.3 , page 68) though you'll be able to append to the folder.
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 69) though you'll be able to append to the folder.
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-
prising if your compressing script produces empty files. In this situation,
- unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 7.4.245 , page 147), so that the compressed file
+ unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 7.4.245 , page 148), so that the compressed file
will be removed if you delete all of the messages.
_\b4_\b._\b1_\b9_\b._\b1 _\bO_\bp_\be_\bn _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\bf_\bo_\br _\br_\be_\ba_\bd_\bi_\bn_\bg
Example:
- The Mutt Next Generation E-Mail Client 68
-
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: close-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
This is used to close the folder that was open with the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 67) command after some changes were made to it.
+ 4.19.1 , page 68) command after some changes were made to it.
+
+ The Mutt Next Generation E-Mail Client 69
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd string is the command that can be used for closing 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.19.1 , page 67) command. Temporary folder in this case is the folder previ-
- ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 67) command.
+ 4.19.1 , page 68) command. Temporary folder in this case is the folder previ-
+ ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 68) command.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should n\bno\bot\bt remove the decompressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should return
non-zero exit status if it fails, so mutt knows something's wrong.
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type, and the
file can only be open in the readonly mode.
- _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67) is not called when you exit from the
+ _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68) is not called when you exit from the
folder if the folder was not changed.
_\b4_\b._\b1_\b9_\b._\b3 _\bA_\bp_\bp_\be_\bn_\bd _\ba _\bm_\be_\bs_\bs_\ba_\bg_\be _\bt_\bo _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is used for saving to an existing compressed folder. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
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.19.1 , page 67)
+ _\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.19.1 , page 68)
command. The temporary folder in this case contains the messages that are
being appended.
append-hook \\.gz$ "gzip -c %t >> %f"
- When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68) is used, the folder is not opened,
+ When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69) 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 7.4.130 , page 119)) type is always
-
- The Mutt Next Generation E-Mail Client 69
-
+ is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.130 , page 120)) type is always
supposed (i.e. this is the format used for the temporary folder).
If the file does not exist when you save to it, _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 ,
- page 67) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68). _\ba_\bp_\bp_\be_\bn_\bd_\b-
- _\bh_\bo_\bo_\bk (section 4.19.3 , page 68) is only for appending to existing folders.
+ page 68) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69). _\ba_\bp_\bp_\be_\bn_\bd_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 69) is only for appending to existing folders.
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type. In this
case, the folder will be open and closed again (using _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 67) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67)respectively) each
+ 4.19.1 , page 68) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68)respectively) each
time you will add to it.
+ The Mutt Next Generation E-Mail Client 70
+
_\b4_\b._\b1_\b9_\b._\b4 _\bE_\bn_\bc_\br_\by_\bp_\bt_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs
The compressed folders support can also be used to handle encrypted folders. If
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-ng recognizes a
-
- The Mutt Next Generation E-Mail Client 70
-
variety of PGP MIME types, including PGP/MIME and application/pgp.
Mutt-ng will denote attachments with a couple lines describing them. These
Where the Description is the description or filename given for the attachment,
and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
+ The Mutt Next Generation E-Mail Client 71
+
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) --]
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
-
- The Mutt Next Generation E-Mail Client 71
-
attachment, which allows a binary message to be encoded for transmission on
7bit links. It can be changed with the edit-encoding command (default: ^E).
The next field is the size of the attachment, rounded to kilobytes or
_\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-ng searches your personal
+
+ The Mutt Next Generation E-Mail Client 72
+
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
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
-
- The Mutt Next Generation E-Mail Client 72
-
handler. The default search string for these files is a colon delimited list
set to
In particular, the metamail distribution will install a mailcap file, usually
as /usr/local/etc/mailcap, which contains some baseline entries.
+ The Mutt Next Generation E-Mail Client 73
+
_\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
A mailcap file consists of a series of lines which are comments, blank, or def-
text/html; lynx %s
- The Mutt Next Generation E-Mail Client 73
-
In this case, lynx does not support viewing a file from stdin, so you must use
the %s syntax. N\bNo\bot\bte\be:\b: _\bS_\bo_\bm_\be _\bo_\bl_\bd_\be_\br _\bv_\be_\br_\bs_\bi_\bo_\bn_\bs _\bo_\bf _\bl_\by_\bn_\bx _\bc_\bo_\bn_\bt_\ba_\bi_\bn _\ba _\bb_\bu_\bg _\bw_\bh_\be_\br_\be _\bt_\bh_\be_\by _\bw_\bi_\bl_\bl
_\bc_\bh_\be_\bc_\bk _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be _\bf_\bo_\br _\ba _\bv_\bi_\be_\bw_\be_\br _\bf_\bo_\br _\bt_\be_\bx_\bt_\b/_\bh_\bt_\bm_\bl_\b. _\bT_\bh_\be_\by _\bw_\bi_\bl_\bl _\bf_\bi_\bn_\bd _\bt_\bh_\be _\bl_\bi_\bn_\be
On the other hand, maybe you don't want to use lynx interactively, you just
want to have it convert the text/html to text/plain, then you can use:
+ The Mutt Next Generation E-Mail Client 74
+
text/html; lynx -dump %s | more
Perhaps you wish to use lynx to view text/html files, and a pager on all other
The interpretation of shell meta-characters embedded in MIME parameters can
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 7.4.121 , page 118) variable.
+ them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.121 , page 119) 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.
_\b5_\b._\b3_\b._\b3_\b._\b1 _\bO_\bp_\bt_\bi_\bo_\bn_\ba_\bl _\bF_\bi_\be_\bl_\bd_\bs
- The Mutt Next Generation E-Mail Client 74
-
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-ng recog-
nizes the following optional fields:
amounts of text on stdout. This causes Mutt-ng 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
+
+ The Mutt Next Generation E-Mail Client 75
+
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:
needsterminal
Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
- tion 5.4 , page 77), in order to decide whether it should honor
- the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 170) variable
+ tion 5.4 , page 78), in order to decide whether it should honor
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 171) 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 7.4.339 , page 170) and the exit
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 171) 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.
it to compose new attachments. Mutt-ng will default to the defined
editor for text attachments.
- The Mutt Next Generation E-Mail Client 75
-
nametemplate=<template>
This field specifies the format for the file denoted by %s in the
command fields. Certain programs will require a certain file
text/html; lynx %s; nametemplate=%s.html
+ The Mutt Next Generation E-Mail Client 76
+
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
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 77) to denote
+ In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 78) 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
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s; nametemplate=%s.html
-
- The Mutt Next Generation E-Mail Client 76
-
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
- For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 77), Mutt-ng will choose the third entry
+ For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 78), 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.
_\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
+
+ The Mutt Next Generation E-Mail Client 77
+
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-
ng. The keywords Mutt-ng expands are:
This mailcap file is fairly simple and standard:
- The Mutt Next Generation E-Mail Client 77
-
# 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 Next Generation E-Mail Client 78
+
# 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-ng to view an attachment with the MIME
- viewer defined in the mailcap file, Mutt-ng has support for automatically
-
- The Mutt Next Generation E-Mail Client 78
-
- viewing MIME attachments while in the pager.
+ 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
For instance, if you set auto_view to:
+ The Mutt Next Generation E-Mail Client 79
+
auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
Mutt-ng could use the following mailcap entries to automatically view attach-
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 77), and use that. Failing that, Mutt-ng will look for any text
+ 5.4 , page 78), 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-
_\b5_\b._\b6 _\bM_\bI_\bM_\bE _\bL_\bo_\bo_\bk_\bu_\bp
Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
-
- The Mutt Next Generation E-Mail Client 79
-
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
mime_lookup application/octet-stream application/X-Lotus-Manuscript
In addition, the unmime_lookup command may be used to disable this feature for
+
+ The Mutt Next Generation E-Mail Client 80
+
any particular mime-type if it had been set, for example, in a global muttrc.
_\b6_\b. _\bS_\be_\bc_\bu_\br_\bi_\bt_\by _\bC_\bo_\bn_\bs_\bi_\bd_\be_\br_\ba_\bt_\bi_\bo_\bn_\bs
_\b6_\b._\b2 _\bT_\be_\bm_\bp_\bo_\br_\ba_\br_\by _\bF_\bi_\bl_\be_\bs
Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
- natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.331 , page 169) variable can be used to
+ natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.331 , page 170) variable can be used to
change the default permissions of these files. Please only change it if you
really know what you are doing. Also, a different location for these files may
- be desired which can be changed via the _\b$_\bt_\bm_\bp_\bd_\bi_\br (section 7.4.327 , page 168)
+ be desired which can be changed via the _\b$_\bt_\bm_\bp_\bd_\bi_\br (section 7.4.327 , page 169)
variable.
- The Mutt Next Generation E-Mail Client 80
-
_\b6_\b._\b3 _\bI_\bn_\bf_\bo_\br_\bm_\ba_\bt_\bi_\bo_\bn _\bL_\be_\ba_\bk_\bs
_\b6_\b._\b3_\b._\b1 _\bM_\be_\bs_\bs_\ba_\bg_\be_\b-_\bI_\bD_\b: _\bh_\be_\ba_\bd_\be_\br_\bs
step counter which is increased (and rotated) with every message sent. If you'd
like to hide this information probably telling others how many mail you sent in
which time, you at least need to remove the %P expando from the default setting
- of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.147 , page 123) variable. Please make sure
+ of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.147 , page 124) variable. Please make sure
that you really know how local parts of these Message-ID: headers are composed.
+ The Mutt Next Generation E-Mail Client 81
+
_\b6_\b._\b3_\b._\b2 _\bm_\ba_\bi_\bl_\bt_\bo_\b:_\b-_\bs_\bt_\by_\bl_\be _\bl_\bi_\bn_\bk_\bs
As mutt-ng be can be set up to be the mail client to handle mailto: style links
default, mutt-ng will be strict in interpreting them which means that arbitrary
header fields can be embedded in these links which could override existing
header fields or attach arbitrary files. This may be problematic if the
- _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101) variable is _\bu_\bn_\bs_\be_\bt, i.e. the user
+ _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102) variable is _\bu_\bn_\bs_\be_\bt, i.e. the user
doesn't want to see header fields while editing the message.
For example, following a link like
will send out the user's private gnupg keyring to joe@host if the user doesn't
follow the information on screen carefully enough.
- When _\bu_\bn_\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.315 , page 165) variable, mutt-
+ When _\bu_\bn_\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.315 , page 166) variable, mutt-
ng will
+\bo be less strict when interpreting these links by prepending a X-Mailto-
string to all header fields embedded in such a link _\ba_\bn_\bd
- +\bo turn on the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101) variable by force
+ +\bo turn on the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102) variable by force
to let the user see all the headers (because they still may leak informa-
tion.)
One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
set up to _\ba_\bu_\bt_\bo_\bm_\ba_\bt_\bi_\bc_\ba_\bl_\bl_\by execute any given utility as listed in one of the mail-
- cap files (see the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh (section 7.4.120 , page 117) variable for
+ cap files (see the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh (section 7.4.120 , page 118) variable for
details.)
- These utilities may have a variety of security vulnerabilities, including
-
- The Mutt Next Generation E-Mail Client 81
-
- overwriting of arbitrary files, information leaks or other exploitable bugs.
- These vulnerabilities may go unnoticed by the user, especially when they are
- called automatically (and without interactive prompting) from the mailcap
- file(s). When using mutt-ng's autoview mechanism in combination with mailcap
- files, please be sure to...
+ These utilities may have a variety of security vulnerabilities, including over-
+ writing of arbitrary files, information leaks or other exploitable bugs. These
+ vulnerabilities may go unnoticed by the user, especially when they are called
+ automatically (and without interactive prompting) from the mailcap file(s).
+ When using mutt-ng's autoview mechanism in combination with mailcap files,
+ please be sure to...
+\bo manually select trustworth applications with a reasonable calling sequence
+\bo periodically check the contents of mailcap files, especially after soft-
ware installations or upgrades
+ The Mutt Next Generation E-Mail Client 82
+
+\bo keep the software packages referenced in the mailcap file up to date
- +\bo leave the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.121 , page 118) variable in its
+ +\bo leave the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.121 , page 119) variable in its
default state to restrict mailcap expandos to a safe set of characters
_\b6_\b._\b4_\b._\b2 _\bO_\bt_\bh_\be_\br
mailbox. However, it is possible to read other mailboxes and to send messages
from the command line as well.
- The Mutt Next Generation E-Mail Client 82
-
-A expand an alias
-a attach a file to a message
-b specify a blind carbon-copy (BCC) address
To read messages in a mailbox
+ The Mutt Next Generation E-Mail Client 83
+
mutt [ -nz ] [ -F _\bm_\bu_\bt_\bt_\br_\bc ] [ -m _\bt_\by_\bp_\be ] [ -f _\bm_\ba_\bi_\bl_\bb_\bo_\bx ]
To compose a new message
_\b7_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
- The Mutt Next Generation E-Mail Client 83
+ The Mutt Next Generation E-Mail Client 84
~A all messages
~b EXPR messages which contain EXPR in the message body
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
- 47). Special attention has to be made when using regular expressions inside of
+ 48). Special attention has to be made when using regular expressions inside of
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 Next Generation E-Mail Client 84
+ The Mutt Next Generation E-Mail Client 85
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
The following are the commands understood by mutt.
- +\bo _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\b-_\bh_\bo_\bo_\bk (section 4.17 , page 65) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\b-_\bh_\bo_\bo_\bk (section 4.17 , page 66) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 24) _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ +\bo _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 25) _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
- +\bo _\bu_\bn_\ba_\bl_\bi_\ba_\bs (section 3.4 , page 24) [ * | _\bk_\be_\by ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bi_\ba_\bs (section 3.4 , page 25) [ * | _\bk_\be_\by ... ]
- +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 33) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 32) [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 33) [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 77) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 77) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bb_\bi_\bn_\bd (section 3.5 , page 25) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ +\bo _\bb_\bi_\bn_\bd (section 3.5 , page 26) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
- +\bo _\bc_\bh_\ba_\br_\bs_\be_\bt_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 27) _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
+ +\bo _\bc_\bh_\ba_\br_\bs_\be_\bt_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 28) _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
- +\bo _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\bo_\bl_\bo_\br (section 3.9 , page 29) _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
+ +\bo _\bc_\bo_\bl_\bo_\br (section 3.9 , page 30) _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
- +\bo _\bu_\bn_\bc_\bo_\bl_\bo_\br (section 3.9 , page 29) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bc_\bo_\bl_\bo_\br (section 3.9 , page 30) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\be_\bx_\be_\bc (section 3.25 , page 40) _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+ +\bo _\be_\bx_\be_\bc (section 3.25 , page 41) _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 38) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 28) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 37) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ +\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 38) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
- +\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 37) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ +\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 38) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
- +\bo _\bi_\bc_\bo_\bn_\bv_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 27) _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
+ +\bo _\bi_\bc_\bo_\bn_\bv_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 28) _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
- +\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 31) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 32) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- The Mutt Next Generation E-Mail Client 85
+ The Mutt Next Generation E-Mail Client 86
- +\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 31) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 32) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bl_\bi_\bs_\bt_\bs (section 3.13 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bl_\bi_\bs_\bt_\bs (section 3.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\bl_\bi_\bs_\bt_\bs (section 3.13 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\bl_\bi_\bs_\bt_\bs (section 3.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bm_\ba_\bc_\br_\bo (section 3.8 , page 28) _\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 ]
+ +\bo _\bm_\ba_\bc_\br_\bo (section 3.8 , page 29) _\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 ]
+\bo _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.15 , page 36) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 40) _\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 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bm_\bo_\bn_\bo (section 3.9 , page 29) _\bo_\bb_\bj_\be_\bc_\bt _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
+ +\bo _\bm_\bo_\bn_\bo (section 3.9 , page 30) _\bo_\bb_\bj_\be_\bc_\bt _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
- +\bo _\bu_\bn_\bm_\bo_\bn_\bo (section 3.9 , page 29) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bm_\bo_\bn_\bo (section 3.9 , page 30) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
- +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 67) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 68) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.23 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
+ +\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.23 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
+\bo _\bp_\bu_\bs_\bh (section 3.24 , page 40) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\br_\be_\bs_\be_\bt (section 3.28 , page 43) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\br_\be_\bs_\be_\bt (section 3.28 , page 44) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 37) _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 38) _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bc_\bo_\br_\be (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
+ +\bo _\bs_\bc_\bo_\br_\be (section 3.26 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
- +\bo _\bu_\bn_\bs_\bc_\bo_\br_\be (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bs_\bc_\bo_\br_\be (section 3.26 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 38) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 39) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\br_\be_\bp_\bl_\by_\b-_\bh_\bo_\bo_\bk (section , page ) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bs_\be_\bt (section 3.28 , page 43) [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\bs_\be_\bt (section 3.28 , page 44) [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bu_\bn_\bs_\be_\bt (section 3.28 , page 43) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\bu_\bn_\bs_\be_\bt (section 3.28 , page 44) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 44) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ +\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 45) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bp_\ba_\bm (section 3.27 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
+ +\bo _\bs_\bp_\ba_\bm (section 3.27 , page 42) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
- +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.27 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn
+ +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.27 , page 42) _\bp_\ba_\bt_\bt_\be_\br_\bn
- The Mutt Next Generation E-Mail Client 86
+ The Mutt Next Generation E-Mail Client 87
- +\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 35) _\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.13 , page 34) _\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.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bt_\bo_\bg_\bg_\bl_\be (section 3.28 , page 43) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\bt_\bo_\bg_\bg_\bl_\be (section 3.28 , page 44) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bu_\bn_\bh_\bo_\bo_\bk (section 3.30 , page 44) _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
+ +\bo _\bu_\bn_\bh_\bo_\bo_\bk (section 3.30 , page 45) _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
_\b7_\b._\b4 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
left column contains the old synonym variables, the right column the full/new
name:
- The Mutt Next Generation E-Mail Client 87
+ The Mutt Next Generation E-Mail Client 88
edit_hdrs edit_headers
forw_decode forward_decode
This variable specifies whether to abort sending if no attachment was made but
- The Mutt Next Generation E-Mail Client 88
+ The Mutt Next Generation E-Mail Client 89
the content references them, i.e. the content matches the regular expression
- given in _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 91). If a match was
+ given in _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 92). If a match was
found and this variable is set to _\by_\be_\bs, message sending will be aborted but the
mail will be send nevertheless if set to _\bn_\bo.
- This variable and _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 91) are
+ This variable and _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 92) are
intended to remind the user to attach files if the message's text references
them.
- See also the _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 91) variable.
+ See also the _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 92) variable.
_\b7_\b._\b4_\b._\b2 _\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\bs_\bu_\bb_\bj_\be_\bc_\bt
tion 2.5.4 , page 11)'' function.
N\bNo\bot\bte\be:\b: Mutt-ng will not automatically source this file; you must explicitly use
- the ``_\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 44)'' command for it to be executed.
+ the ``_\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 45)'' command for it to be executed.
_\b7_\b._\b4_\b._\b6 _\ba_\bl_\bi_\ba_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
- The Mutt Next Generation E-Mail Client 89
+ The Mutt Next Generation E-Mail Client 90
Type: string
will make response faster because there is less that has to be redrawn on the
screen when moving to the next or previous entries in the menu.
- The Mutt Next Generation E-Mail Client 90
+ The Mutt Next Generation E-Mail Client 91
_\b7_\b._\b4_\b._\b1_\b0 _\ba_\bs_\bc_\bi_\bi_\b__\bc_\bh_\ba_\br_\bs
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 7.4.316 , page 166) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 7.4.316 , page 167) is unset.
_\b7_\b._\b4_\b._\b1_\b4 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
This variable describes the format of the ``attachment'' menu. The following
printf(3)-style sequences are understood:
- The Mutt Next Generation E-Mail Client 91
+ The Mutt Next Generation E-Mail Client 92
%C
charset
Default: 'attach'
- The Mutt Next Generation E-Mail Client 92
+ The Mutt Next Generation E-Mail Client 93
If this variable is non-empty, muttng will scan a message's contents before
sending for this regular expression. If it is found, it will ask for what to do
- depending on the setting of _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 87).
+ depending on the setting of _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 88).
- This variable and _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 87) are intended to
+ This variable and _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 88) are intended to
remind the user to attach files if the message's text references them.
_\b7_\b._\b4_\b._\b1_\b6 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp
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 7.4.16 ,
- page 92)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
+ page 93)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
operate on the attachments one by one.
_\b7_\b._\b4_\b._\b1_\b8 _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn
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 7.4.114 , page 114)''.
+ on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115)''.
_\b7_\b._\b4_\b._\b1_\b9 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
Default: no
- The Mutt Next Generation E-Mail Client 93
+ The Mutt Next Generation E-Mail Client 94
- When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101)'', Mutt-ng
+ When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102)'', Mutt-ng
will skip the initial send-menu and allow you to immediately begin editing the
body of your message. The send-menu may still be accessed once you have fin-
ished editing the body of your message.
- Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.64 , page 102)''.
+ Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.64 , page 103)''.
_\b7_\b._\b4_\b._\b2_\b1 _\bb_\be_\be_\bp
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 7.4.21 , page 93)'' variable.
+ tion 7.4.21 , page 94)'' variable.
_\b7_\b._\b4_\b._\b2_\b3 _\bb_\bo_\bu_\bn_\bc_\be
current line in menus, even when the arrow_cursor variable is unset, making it
easier for blind persons using Braille displays to follow these menus. The
- The Mutt Next Generation E-Mail Client 94
+ The Mutt Next Generation E-Mail Client 95
option is disabled by default because many visual terminals don't permit making
the cursor invisible.
When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
sages.
- The Mutt Next Generation E-Mail Client 95
+ The Mutt Next Generation E-Mail Client 96
_\b7_\b._\b4_\b._\b3_\b0 _\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
Controls the format of the status line displayed in the ``compose'' menu. This
- string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163)'', but has
+ string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 164)'', but has
its own set of printf(3)-like sequences:
%a
%v
Mutt-ng version string
- See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163)''
+ See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 164)''
option for more information on how to set ``_\b$_\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.30 ,
- page 95)''.
+ page 96)''.
_\b7_\b._\b4_\b._\b3_\b1 _\bc_\bo_\bn_\bf_\bi_\bg_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
_\b7_\b._\b4_\b._\b3_\b4 _\bc_\bo_\bn_\bn_\be_\bc_\bt_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
- The Mutt Next Generation E-Mail Client 96
+ The Mutt Next Generation E-Mail Client 97
Type: number
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 7.4.235 , page
- 144)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 147)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.72 , page 105)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)''.
+ 145)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 148)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.72 , page 106)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)''.
_\b7_\b._\b4_\b._\b3_\b7 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt
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
required or signing is requested as well. If ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section
- 7.4.282 , page 155)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
+ 7.4.282 , page 156)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
messages and settings can be overridden by use of the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto
only)
This variable controls whether or not Mutt-ng may automatically enable PGP
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
- 7.4.37 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 97)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.42 , page 97)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 155)''.
+ 7.4.37 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 98)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 7.4.42 , page 98)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 156)''.
- The Mutt Next Generation E-Mail Client 97
+ The Mutt Next Generation E-Mail Client 98
_\b7_\b._\b4_\b._\b3_\b9 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
Setting this variable will cause Mutt-ng to always attempt to cryptographically
sign outgoing messages. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when
signing is not required or encryption is requested as well. If
- ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 155)'' is _\bs_\be_\bt, then OpenSSL is
+ ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 156)'' is _\bs_\be_\bt, then OpenSSL is
used instead to create S/MIME messages and settings can be overridden by use of
the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto only)
This variable controls whether or not Mutt-ng may automatically enable S/MIME
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
- 7.4.37 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 97)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.42 , page 97)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 155)''.
+ 7.4.37 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 98)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 7.4.42 , page 98)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 156)''.
_\b7_\b._\b4_\b._\b4_\b1 _\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 sign replies to messages which are
encrypted. This makes sense in combination with ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 7.4.41 , page 97)'', because it allows you to sign all messages which are
+ 7.4.41 , page 98)'', because it allows you to sign all messages which are
- The Mutt Next Generation E-Mail Client 98
+ The Mutt Next Generation E-Mail Client 99
automatically encrypted. This works around the problem noted in
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section 7.4.42 , page 97)'', that Mutt-ng is not able to
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section 7.4.42 , page 98)'', that Mutt-ng is not able to
find out whether an encrypted message is also signed. (Crypto only)
_\b7_\b._\b4_\b._\b4_\b4 _\bc_\br_\by_\bp_\bt_\b__\bt_\bi_\bm_\be_\bs_\bt_\ba_\bm_\bp
Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
This variable controls the format of the date printed by the ``%d'' sequence in
- ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)''. This is passed to strftime(3)
+ ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115)''. This is passed to strftime(3)
to process the date.
Unless the first character in the string is a bang (``!''), the month and week
day names are expanded according to the locale specified in the variable
- ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.118 , page 117)''. If the first character in the string
+ ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.118 , page 118)''. If the first character in the string
is a bang, the bang is discarded, and the month and week day names in the rest
of the string are expanded in the _\bC locale (that is in US English).
- The Mutt Next Generation E-Mail Client 99
+ The Mutt Next Generation E-Mail Client 100
_\b7_\b._\b4_\b._\b4_\b8 _\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk
Default: no
When sending messages with format=flowed by _\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd (section
- 7.4.322 , page 167) variable, this variable specifies whether to also set the
+ 7.4.322 , page 168) variable, this variable specifies whether to also set the
DelSp parameter to yes. If this is _\bu_\bn_\bs_\be_\bt, no additional parameter will be send
as a value of no already is the default behavior.
N\bNo\bot\bte\be:\b: this variable only has an effect on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg messages (if _\b$_\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
- (section 7.4.322 , page 167) is _\bs_\be_\bt) but not on incomming.
+ (section 7.4.322 , page 168) is _\bs_\be_\bt) but not on incomming.
_\b7_\b._\b4_\b._\b5_\b1 _\bd_\be_\bl_\be_\bt_\be_\b__\bu_\bn_\bt_\ba_\bg
Type: boolean
- The Mutt Next Generation E-Mail Client 100
+ The Mutt Next Generation E-Mail Client 101
Default: yes
When _\bs_\be_\bt, specifies a command used to filter messages. When a message is
viewed it is passed as standard input to _\b$_\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br (section 7.4.53 ,
- page 100), and the filtered message is read from the standard output.
+ page 101), and the filtered message is read from the standard output.
_\b7_\b._\b4_\b._\b5_\b4 _\bd_\bo_\bt_\bl_\bo_\bc_\bk_\b__\bp_\br_\bo_\bg_\br_\ba_\bm
This variable controls how much of your message is returned in DSN messages.
It may be set to either _\bh_\bd_\br_\bs to return just the message header, or _\bf_\bu_\bl_\bl to
- The Mutt Next Generation E-Mail Client 101
+ The Mutt Next Generation E-Mail Client 102
return the full message.
Type: path
- The Mutt Next Generation E-Mail Client 102
+ The Mutt Next Generation E-Mail Client 103
Default: ''
When _\bs_\be_\bt, Mutt-ng will try to derive the message's _\be_\bn_\bv_\be_\bl_\bo_\bp_\be sender from the
``From:'' header field. Note that this information is passed to the sendmail
command using the ``-f' command line switch, so don't set this option if you
- are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page 148) yourself, or
+ are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page 149) yourself, or
if the sendmail on your machine doesn't support that command line switch.
_\b7_\b._\b4_\b._\b6_\b3 _\be_\bs_\bc_\ba_\bp_\be
messages.
N\bNo\bot\bte\be:\b: this variable has no effect when the ``_\b$_\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt (section 7.4.20 , page
- 92)'' variable is _\bs_\be_\bt.
+ 93)'' variable is _\bs_\be_\bt.
_\b7_\b._\b4_\b._\b6_\b5 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
Default: no
- The Mutt Next Generation E-Mail Client 103
+ The Mutt Next Generation E-Mail Client 104
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
- file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.27 , page 94) value will
+ file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.27 , page 95) value will
be used instead. For example, the following configuration would work for
Japanese text handling:
This variable allows you to customize the file browser display to your personal
taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page
- 114)'', but has its own set of printf(3)-like sequences:
+ 115)'', but has its own set of printf(3)-like sequences:
%C
current file number
%F
file permissions
- The Mutt Next Generation E-Mail Client 104
+ The Mutt Next Generation E-Mail Client 105
%g
group name (or numeric gid, if missing)
Controls whether or not the Mail-Followup-To: header field is generated when
sending mail. When _\bs_\be_\bt, Mutt-ng will generate this field when you are replying
to a known mailing list, specified with the ``subscribe'' or ``_\bl_\bi_\bs_\bt_\bs (section
- 3.13 , page 34)'' commands or detected by common mailing list headers.
+ 3.13 , page 35)'' commands or detected by common mailing list headers.
This field has two purposes. First, preventing you from receiving duplicate
copies of replies to messages which you send to mailing lists. Second, ensuring
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 Next Generation E-Mail Client 105
+ The Mutt Next Generation E-Mail Client 106
- Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.326 , page 168)'',
- ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.119 , page 117)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 7.4.103 , page 111)''.
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.326 , page 169)'',
+ ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.119 , page 118)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
+ 7.4.103 , page 112)''.
_\b7_\b._\b4_\b._\b7_\b2 _\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be
Default: no
- This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 147)'',
+ This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 148)'',
except that Mutt-ng will store a copy of your outgoing message by the username
of the address you are sending to even if that mailbox does not exist.
- Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144)'' variable.
+ Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 145)'' variable.
_\b7_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
Controls the decoding of complex MIME messages into text/plain when forwarding
a message. The message header is also RFC2047 decoded. This variable is only
- used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bu_\bn_\bs_\be_\bt, otherwise
- ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 122)'' is used instead.
+ used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 122)'' is _\bu_\bn_\bs_\be_\bt, otherwise
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 123)'' is used instead.
_\b7_\b._\b4_\b._\b7_\b4 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
Controls the handling of encrypted messages when forwarding a message. When
_\bs_\be_\bt, the outer layer of encryption is stripped off. This variable is only used
- if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
- _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 122)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
+ if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 122)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 123)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
_\b7_\b._\b4_\b._\b7_\b5 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
Default: '[%a: %s]'
- The Mutt Next Generation E-Mail Client 106
+ The Mutt Next Generation E-Mail Client 107
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 7.4.114 , page
- 114)'' variable.
+ 115)'' variable.
_\b7_\b._\b4_\b._\b7_\b7 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
Default: no
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 7.4.141 , page 121)'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
- ``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 114)''.
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 122)'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
+ ``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 115)''.
_\b7_\b._\b4_\b._\b7_\b8 _\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 7.4.241 , page
- 146)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.335 , page
- 170)'' is unset.
+ 147)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.335 , page
+ 171)'' is unset.
E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
<foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
Default: yes
- The Mutt Next Generation E-Mail Client 107
+ The Mutt Next Generation E-Mail Client 108
When _\bu_\bn_\bs_\be_\bt, the header fields normally added by the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 ,
- page 36)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
+ page 37)'' 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
defined header fields are added to every new message.
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 7.4.340 , page
- 171)'' setting applies.
+ 172)'' setting applies.
_\b7_\b._\b4_\b._\b8_\b2 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be
Availability: Header Cache
- The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.82 , page 107) variable points to the header
+ The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.82 , page 108) variable points to the header
cache database.
- If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.82 , page 107) points to a directory it will
+ If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.82 , page 108) points to a directory it will
contain a header cache database per folder. If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section
- 7.4.82 , page 107) points to a file that file will be a single global header
+ 7.4.82 , page 108) points to a file that file will be a single global header
cache. By default it is _\bu_\bn_\bs_\be_\bt so no header caching will be used.
_\b7_\b._\b4_\b._\b8_\b3 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bc_\bo_\bm_\bp_\br_\be_\bs_\bs
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 Next Generation E-Mail Client 108
+ The Mutt Next Generation E-Mail Client 109
problem.
Default: no
When _\bs_\be_\bt, Mutt-ng will skip the host name part of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section
- 7.4.93 , page 109)'' variable when adding the domain part to addresses. This
+ 7.4.93 , page 110)'' variable when adding the domain part to addresses. This
variable does not affect the generation of Message-ID: header fields, and it
will not lead to the cut-off of first-level domains.
When _\bs_\be_\bt, Mutt-ng will not show the presence of messages that are hidden by
limiting, at the top of threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\b-
- _\bi_\bn_\bg (section 7.4.87 , page 108) is set, this option will have no effect.
+ _\bi_\bn_\bg (section 7.4.87 , page 109) is set, this option will have no effect.
_\b7_\b._\b4_\b._\b9_\b0 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
Type: boolean
- The Mutt Next Generation E-Mail Client 109
+ The Mutt Next Generation E-Mail Client 110
Default: yes
When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages at the top of
threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd (section 7.4.86 ,
- page 108) is _\bs_\be_\bt, this option will have no effect.
+ page 109) is _\bs_\be_\bt, this option will have no effect.
_\b7_\b._\b4_\b._\b9_\b1 _\bh_\bi_\bs_\bt_\bo_\br_\by
Type: string
- The Mutt Next Generation E-Mail Client 110
+ The Mutt Next Generation E-Mail Client 111
Default: ''
This contains the list of characters which you would like to treat as folder
separators for displaying IMAP paths. In particular it helps in using the '='
- shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) variable.
+ shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 104) variable.
_\b7_\b._\b4_\b._\b9_\b8 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
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 Next Generation E-Mail Client 111
+ The Mutt Next Generation E-Mail Client 112
N\bNo\bot\bte\be:\b: This is a space separated list.
Your login name on the IMAP server.
- The Mutt Next Generation E-Mail Client 112
+ The Mutt Next Generation E-Mail Client 113
This variable defaults to the value of ``_\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.109 , page
- 113).''
+ 114).''
_\b7_\b._\b4_\b._\b1_\b0_\b3 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
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 7.4.119 ,
- page 117)'' variable to generate less traffic and get more accurate information
+ page 118)'' variable to generate less traffic and get more accurate information
for local folders.
_\b7_\b._\b4_\b._\b1_\b0_\b4 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
closing an IMAP folder somewhat slower. This option exists to appease speed
freaks.
- The Mutt Next Generation E-Mail Client 113
+ The Mutt Next Generation E-Mail Client 114
_\b7_\b._\b4_\b._\b1_\b0_\b7 _\bi_\bm_\ba_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Controls whether or not a copy of the message(s) you are replying to is
- The Mutt Next Generation E-Mail Client 114
+ The Mutt Next Generation E-Mail Client 115
included in your reply.
%C
current message number
- The Mutt Next Generation E-Mail Client 115
+ The Mutt Next Generation E-Mail Client 116
%d
date and time of the message in the format specified by ``date_for-
(_O_riginal save folder) Where Mutt-ng would formerly have stashed
the message: list name or recipient name if no list
- The Mutt Next Generation E-Mail Client 116
+ The Mutt Next Generation E-Mail Client 117
%s
subject of the message
%T
the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 ,
- page 168) string
+ page 169) string
%u
user (login) name of the author
the current local time. ``fmt'' is expanded by the library function
``strftime''; a leading bang disables locales.
- The Mutt Next Generation E-Mail Client 117
+ The Mutt Next Generation E-Mail Client 118
%>X
right justify the rest of the string and pad with character 'X'
%|X
pad to the end of the line with character 'X'
- See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 , page 168)''.
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 , page 169)''.
_\b7_\b._\b4_\b._\b1_\b1_\b5 _\bi_\bs_\bp_\be_\bl_\bl
Default: no
If _\bs_\be_\bt, read messages marked as flagged will not be moved from your spool mail-
- box to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 119)'' mailbox, or as a result of
- a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35)'' command.
+ box to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 120)'' mailbox, or as a result of
+ a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36)'' command.
_\b7_\b._\b4_\b._\b1_\b1_\b7 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
This variable configures how often (in seconds) Mutt-ng should look for new
mail.
- The Mutt Next Generation E-Mail Client 118
+ The Mutt Next Generation E-Mail Client 119
N\bNo\bot\bte\be:\b: This does not apply to IMAP mailboxes, see _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 7.4.103 , page 111).
+ 7.4.103 , page 112).
_\b7_\b._\b4_\b._\b1_\b2_\b0 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
Type: boolean
- The Mutt Next Generation E-Mail Client 119
+ The Mutt Next Generation E-Mail Client 120
Default: yes
Controls the display of wrapped lines in the internal pager. If set, a ``+''
marker is displayed at the beginning of wrapped lines. Also see the
- ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 7.4.268 , page 152)'' variable.
+ ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 7.4.268 , page 153)'' variable.
_\b7_\b._\b4_\b._\b1_\b2_\b6 _\bm_\ba_\bs_\bk
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 7.4.342 , page 171).
+ (section 7.4.342 , page 172).
_\b7_\b._\b4_\b._\b1_\b2_\b9 _\bm_\bb_\bo_\bx
Type: path
- The Mutt Next Generation E-Mail Client 120
+ The Mutt Next Generation E-Mail Client 121
Default: '~/mbox'
This specifies the folder into which read mail in your ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 7.4.302 , page 160)'' folder will be appended.
+ 7.4.302 , page 161)'' folder will be appended.
_\b7_\b._\b4_\b._\b1_\b3_\b0 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
This variable controls the number of lines of context that are given when
scrolling through menus. (Similar to ``_\b$_\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.172 , page
- 130)''.)
+ 131)''.)
_\b7_\b._\b4_\b._\b1_\b3_\b2 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
This is the string displayed in the ``attachment'' menu for attachments of type
message/rfc822. 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 7.4.114 , page 114)''.
+ section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115)''.
- The Mutt Next Generation E-Mail Client 121
+ The Mutt Next Generation E-Mail Client 122
_\b7_\b._\b4_\b._\b1_\b3_\b5 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
Default: 'unseen'
- The Mutt Next Generation E-Mail Client 122
+ The Mutt Next Generation E-Mail Client 123
The name of the MH sequence used for unseen messages.
the message as it was delivered to you. If you like to switch between MIME and
not MIME from mail to mail, set this variable to ask-no or ask-yes.
- Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.73 , page 105)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
- _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 122)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.73 , page 106)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 123)''.
_\b7_\b._\b4_\b._\b1_\b4_\b2 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
Default: no
Controls the decoding of complex MIME messages into text/plain when forwarding
- a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bs_\be_\bt. Other-
- wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.73 , page 105)'' is used instead.
+ a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 122)'' is _\bs_\be_\bt. Other-
+ wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.73 , page 106)'' is used instead.
_\b7_\b._\b4_\b._\b1_\b4_\b3 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\br_\be_\bs_\bt
%c
Remailer capabilities.
- The Mutt Next Generation E-Mail Client 123
+ The Mutt Next Generation E-Mail Client 124
%s
The remailer's short name.
Default: ask-no
Controls whether or not Mutt-ng will move read messages from your spool mailbox
- to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 119)'' mailbox, or as a result of a
- ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35)'' command.
+ to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 120)'' mailbox, or as a result of a
+ ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36)'' command.
_\b7_\b._\b4_\b._\b1_\b4_\b7 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
%O
the current UNIX timestamp (octal)
- The Mutt Next Generation E-Mail Client 124
+ The Mutt Next Generation E-Mail Client 125
%p
the process ID
Type: boolean
- The Mutt Next Generation E-Mail Client 125
+ The Mutt Next Generation E-Mail Client 126
Default: no
Availability: NNTP
This variable controls how many news articles to cache per newsgroup (if
- caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 7.4.151 , page 125)) and how
+ caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 7.4.151 , page 126)) and how
many news articles to show in the ``index'' menu.
If there're more articles than defined with _\b$_\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.153 ,
- page 125), all older ones will be removed/not shown in the index.
+ page 126), all older ones will be removed/not shown in the index.
_\b7_\b._\b4_\b._\b1_\b5_\b4 _\bn_\bn_\bt_\bp_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo_\b__\bp_\bo_\bs_\bt_\be_\br
Default: ask-yes
- The Mutt Next Generation E-Mail Client 126
+ The Mutt Next Generation E-Mail Client 127
Availability: NNTP
This variable allows you to customize the newsgroup browser display to your
personal taste. This string is similar to ``_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 ,
- page 114)'', but has its own set of printf(3)-like sequences:
+ page 115)'', but has its own set of printf(3)-like sequences:
%C current newsgroup number
%d description of newsgroup (retrieved from server)
_\b7_\b._\b4_\b._\b1_\b5_\b7 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
- The Mutt Next Generation E-Mail Client 127
+ The Mutt Next Generation E-Mail Client 128
Type: path
_\b7_\b._\b4_\b._\b1_\b6_\b1 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
- The Mutt Next Generation E-Mail Client 128
+ The Mutt Next Generation E-Mail Client 129
Type: path
Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
was connection lost.
- The Mutt Next Generation E-Mail Client 129
+ The Mutt Next Generation E-Mail Client 130
_\b7_\b._\b4_\b._\b1_\b6_\b5 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
Availability: NNTP
- The Mutt Next Generation E-Mail Client 130
+ The Mutt Next Generation E-Mail Client 131
If _\bs_\be_\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
name of the original article author) to articles that you followup to.
This variable controls the format of the one-line message ``status'' displayed
before each message in either the internal or an external pager. The valid
- sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)''
+ sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115)''
section.
_\b7_\b._\b4_\b._\b1_\b7_\b4 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
- The Mutt Next Generation E-Mail Client 131
+ The Mutt Next Generation E-Mail Client 132
Type: number
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
- ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.193 , page 135)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.193 , page 136)''.
Also note that using the old-style PGP message 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 Next Generation E-Mail Client 132
+ The Mutt Next Generation E-Mail Client 133
_\b7_\b._\b4_\b._\b1_\b7_\b8 _\bp_\bg_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\be_\bx_\bi_\bt
multipart/signed attachment when verifying it.
%a
- The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.197 , page 136).
+ The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.197 , page 137).
%r
One or more key IDs.
_\b7_\b._\b4_\b._\b1_\b8_\b1 _\bp_\bg_\bp_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
- The Mutt Next Generation E-Mail Client 133
+ The Mutt Next Generation E-Mail Client 134
Type: string
This variable allows you to customize the PGP key selection menu to your per-
sonal taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page
- 114)'', but has its own set of printf(3)-like sequences:
+ 115)'', but has its own set of printf(3)-like sequences:
%n
number
%c
capabilities
- The Mutt Next Generation E-Mail Client 134
+ The Mutt Next Generation E-Mail Client 135
%t
trust/validity of the key-uid association
Default: ''
If you assign a text to this variable, then a PGP signature is only considered
- verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.203 , page 137)
+ verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.203 , page 138)
contains the text. Use this variable if the exit code from the command is 0
even for bad signatures. (PGP only)
This command is used to import a key from a message into the user's public key
- The Mutt Next Generation E-Mail Client 135
+ The Mutt Next Generation E-Mail Client 136
ring. (PGP only)
Default: no
- The Mutt Next Generation E-Mail Client 136
+ The Mutt Next Generation E-Mail Client 137
Setting this variable will cause Mutt-ng to always attempt to create an inline
(traditional) message when replying to a message which is PGP encrypted/signed
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
- ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.193 , page 135)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.193 , page 136)''.
Also note that using the old-style PGP message format is s\bst\btr\bro\bon\bng\bgl\bly\by d\bde\bep\bpr\bre\bec\bca\bat\bte\bed\bd.
(PGP only)
Default: ''
- The Mutt Next Generation E-Mail Client 137
+ The Mutt Next Generation E-Mail Client 138
This command is used to create the detached PGP signature for a multi-
part/signed PGP/MIME body part. (PGP only)
If _\bs_\be_\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
- The Mutt Next Generation E-Mail Client 138
+ The Mutt Next Generation E-Mail Client 139
_\b7_\b._\b4_\b._\b2_\b0_\b3 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
of tagged messages Mutt-ng will concatenate the messages and will pipe them as
a single folder. When _\bs_\be_\bt, Mutt-ng will pipe the messages one by one. In both
cases the messages are piped in the current sorted order, and the ``_\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp
- (section 7.4.206 , page 138)'' separator is added after each message.
+ (section 7.4.206 , page 139)'' separator is added after each message.
_\b7_\b._\b4_\b._\b2_\b0_\b8 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\b__\bt_\br_\by_\b__\ba_\bl_\bl
Default: yes
- The Mutt Next Generation E-Mail Client 139
+ The Mutt Next Generation E-Mail Client 140
Availability: POP
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 Next Generation E-Mail Client 140
+ The Mutt Next Generation E-Mail Client 141
_\b7_\b._\b4_\b._\b2_\b1_\b2 _\bp_\bo_\bp_\b__\bl_\ba_\bs_\bt
Availability: POP
- The Mutt Next Generation E-Mail Client 141
+ The Mutt Next Generation E-Mail Client 142
Your login name on the POP server.
Default: ''
- Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 92)'' variable, Mutt-ng
+ Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 93)'' variable, Mutt-ng
will append this string after the inclusion of a message which is being replied
to.
Default: ask-yes
Controls whether or not messages are saved in the ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section
- 7.4.219 , page 141)'' mailbox when you elect not to send immediately.
+ 7.4.219 , page 142)'' mailbox when you elect not to send immediately.
_\b7_\b._\b4_\b._\b2_\b1_\b9 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd
Default: '~/postponed'
- Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 141)
+ Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 142)
sending a message'' which you are editing. When you choose to postpone a mes-
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 7.4.218 , page 141)'' variable.
+ ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 142)'' variable.
_\b7_\b._\b4_\b._\b2_\b2_\b0 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
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.
- The Mutt Next Generation E-Mail Client 142
+ The Mutt Next Generation E-Mail Client 143
_\b7_\b._\b4_\b._\b2_\b2_\b1 _\bp_\br_\bi_\bn_\bt
Used in connection with the print-message command. If this option is _\bs_\be_\bt, the
message is decoded before it is passed to the external command specified by
- _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 142). If this option is _\bu_\bn_\bs_\be_\bt, no pro-
+ _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 143). If this option is _\bu_\bn_\bs_\be_\bt, no pro-
cessing will be applied to the message when printing it. The latter setting
may be useful if you are using some advanced printer filter which is able to
properly format e-mail messages for printing.
Default: no
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 7.4.222 , page 142) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 143) is executed
once for each message which is to be printed. If this option is _\bu_\bn_\bs_\be_\bt, the
- command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 142) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 143) is executed
only once, and all the messages are concatenated, with a form feed as the mes-
sage separator.
Default: yes
- If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 7.4.171 , page 130)'', setting this
+ If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 7.4.171 , page 131)'', setting this
variable will cause Mutt-ng to prompt you for a command when the pager exits
- The Mutt Next Generation E-Mail Client 143
+ The Mutt Next Generation E-Mail Client 144
rather than returning to the index menu. If _\bu_\bn_\bs_\be_\bt, Mutt-ng will return to the
index menu when the external pager exits.
This specifies the command that Mutt-ng will use to make external address
queries. The string should contain a %s, which will be substituted with the
- query string the user types. See ``_\bq_\bu_\be_\br_\by (section 4.7 , page 57)'' for more
+ query string the user types. See ``_\bq_\bu_\be_\br_\by (section 4.7 , page 58)'' for more
information.
_\b7_\b._\b4_\b._\b2_\b2_\b7 _\bq_\bu_\bi_\bt
Default: yes
Controls whether or not empty lines will be quoted using ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (sec-
- tion 7.4.113 , page 114)''.
+ tion 7.4.113 , page 115)''.
_\b7_\b._\b4_\b._\b2_\b2_\b9 _\bq_\bu_\bo_\bt_\be_\b__\bq_\bu_\bo_\bt_\be_\bd
Controls how quoted lines will be quoted. If _\bs_\be_\bt, one quote character will be
added to the end of existing prefix. Otherwise, quoted lines will be prepended
- by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 114)''.
+ by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 115)''.
_\b7_\b._\b4_\b._\b2_\b3_\b0 _\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp
N\bNo\bot\bte\be:\b: In order to use the _\bq_\bu_\bo_\bt_\be_\bdx\bx patterns in the internal pager, you need to
- The Mutt Next Generation E-Mail Client 144
+ The Mutt Next Generation E-Mail Client 145
set this to a regular expression that matches _\be_\bx_\ba_\bc_\bt_\bl_\by the quote characters at
the beginning of quoted lines.
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 7.4.344 , page 171)'' variable.
+ Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 7.4.344 , page 172)'' variable.
_\b7_\b._\b4_\b._\b2_\b3_\b2 _\br_\be_\ba_\bd_\b__\bo_\bn_\bl_\by
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
- _\b$_\bf_\br_\bo_\bm (section 7.4.78 , page 106) variable.
+ _\b$_\bf_\br_\bo_\bm (section 7.4.78 , page 107) variable.
_\b7_\b._\b4_\b._\b2_\b3_\b4 _\br_\be_\bc_\ba_\bl_\bl
Default: ask-yes
Controls whether or not Mutt-ng recalls postponed messages when composing a new
- message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.219 , page 141)''.
+ message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.219 , page 142)''.
Setting this variable to _\by_\be_\bs is not generally useful, and thus not recommended.
_\b7_\b._\b4_\b._\b2_\b3_\b5 _\br_\be_\bc_\bo_\br_\bd
- The Mutt Next Generation E-Mail Client 145
+ The Mutt Next Generation E-Mail Client 146
Type: path
This specifies the file into which your outgoing messages should be appended.
(This is meant as the primary method for saving a copy of your messages, but
- another way to do this is using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36)'' com-
+ another way to do this is using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37)'' com-
mand to create a Bcc: header field with your email address in it.)
- The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\b7_\b._\b4_\b._\b2_\b3_\b5 _\b, _\bp_\ba_\bg_\be _\b1_\b4_\b4_\b) is overridden by the
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 105)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.246 , page 147)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page
+ The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\b7_\b._\b4_\b._\b2_\b3_\b5 _\b, _\bp_\ba_\bg_\be _\b1_\b4_\b5_\b) is overridden by the
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 106)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.246 , page 148)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page
38)'' command.
_\b7_\b._\b4_\b._\b2_\b3_\b6 _\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp
Default: yes
- The Mutt Next Generation E-Mail Client 146
+ The Mutt Next Generation E-Mail Client 147
When set, the cursor will be automatically advanced to the next (possibly
undeleted) message whenever a command that modifies the current message is exe-
Default: yes
This variable fine-tunes the behaviour of the _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 7.4.241 ,
- page 146) feature. When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming
+ page 147) feature. When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming
messages as-is, possibly including eventual real names. When it is _\bu_\bn_\bs_\be_\bt,
Mutt-ng will override any such real names with the setting of the _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
- (section 7.4.233 , page 144) variable.
+ (section 7.4.233 , page 145) variable.
_\b7_\b._\b4_\b._\b2_\b4_\b3 _\br_\bf_\bc_\b2_\b0_\b4_\b7_\b__\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs
Type: boolean
- The Mutt Next Generation E-Mail Client 147
+ The Mutt Next Generation E-Mail Client 148
Default: no
Default: no
If _\bs_\be_\bt, Mutt-ng will take the sender's full address when choosing a default
- folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 147)'' or
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 105)'' is _\bs_\be_\bt too, the selection of the
+ folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 148)'' or
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 106)'' is _\bs_\be_\bt too, the selection of the
fcc folder will be changed as well.
_\b7_\b._\b4_\b._\b2_\b4_\b5 _\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by
Default: yes
When _\bu_\bn_\bs_\be_\bt, mailboxes which contain no saved messages will be removed when
- closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 160)'' which is
+ closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 161)'' which is
never removed). If _\bs_\be_\bt, mailboxes are never removed.
N\bNo\bot\bte\be:\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
This variable controls how copies of outgoing messages are saved. When set, a
check is made to see if a mailbox specified by the recipient address exists
(this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 ,
- page 103)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
+ page 104)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
mailbox exists, the outgoing message will be saved to that mailbox, otherwise
- the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144)'' mailbox.
+ the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 145)'' mailbox.
- The Mutt Next Generation E-Mail Client 148
+ The Mutt Next Generation E-Mail Client 149
- Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 105)'' variable.
+ Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 106)'' variable.
_\b7_\b._\b4_\b._\b2_\b4_\b7 _\bs_\bc_\bo_\br_\be
When this variable is _\bu_\bn_\bs_\be_\bt, scoring is turned off. This can be useful to
selectively disable scoring for certain folders when the ``_\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\b-
- _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.248 , page 148)'' variable and friends are used.
+ _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.248 , page 149)'' variable and friends are used.
_\b7_\b._\b4_\b._\b2_\b4_\b8 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
A list of character sets for outgoing messages. Mutt-ng will use the first
character set into which the text can be converted exactly. If your ``_\b$_\bc_\bh_\ba_\br_\bs_\be_\bt
- (section 7.4.27 , page 94)'' is not iso-8859-1 and recipients may not under-
+ (section 7.4.27 , page 95)'' is not iso-8859-1 and recipients may not under-
stand UTF-8, it is advisable to include in the list an appropriate widely used
standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
- The Mutt Next Generation E-Mail Client 149
+ The Mutt Next Generation E-Mail Client 150
instead of or after iso-8859-1.
Default: 0
Specifies the number of seconds to wait for the ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 ,
- page 148)'' process to finish before giving up and putting delivery in the
+ page 149)'' process to finish before giving up and putting delivery in the
background.
Mutt-ng interprets the value of this variable as follows:
Default: '.'
When the sidebar is displayed and _\b$_\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by (section
- 7.4.259 , page 150) is _\bs_\be_\bt, this variable specifies the characters at which to
+ 7.4.259 , page 151) is _\bs_\be_\bt, this variable specifies the characters at which to
- The Mutt Next Generation E-Mail Client 150
+ The Mutt Next Generation E-Mail Client 151
split a folder name into ``hierarchy items.''
1) These expandos only have a non-zero value for the current mailbox and will
always be zero otherwise.
- The Mutt Next Generation E-Mail Client 151
+ The Mutt Next Generation E-Mail Client 152
_\b7_\b._\b4_\b._\b2_\b5_\b9 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by
When _\bs_\be_\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
they cannot be printed in full length (because ``_\b$_\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bw_\bi_\bd_\bt_\bh (section
- 7.4.261 , page 151)'' is set to a too low value). For example, if the news-
+ 7.4.261 , page 152)'' is set to a too low value). For example, if the news-
group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
get shortened.
At which characters this compression is done is controled via the _\b$_\bs_\bi_\bd_\be_\b-
- _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 7.4.255 , page 149) variable.
+ _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 7.4.255 , page 150) variable.
_\b7_\b._\b4_\b._\b2_\b6_\b0 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
Default: yes
If set, a line containing ``-- '' (dash, dash, space) will be inserted before
- your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.264 , page 151)''. It is s\bst\btr\bro\bon\bng\bgl\bly\by recommended
+ your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.264 , page 152)''. It is s\bst\btr\bro\bon\bng\bgl\bly\by recommended
that you not unset this variable unless your ``signature'' contains just your
name. The reason for this is because many software packages use ``-- \n'' to
detect your signature.
Default: no
- The Mutt Next Generation E-Mail Client 152
+ The Mutt Next Generation E-Mail Client 153
If _\bs_\be_\bt, the signature will be included before any quoted or forwarded text. It
is s\bst\btr\bro\bon\bng\bgl\bly\by recommended that you do not set this variable unless you really
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 7.2 , page 82)'' for more information on search patterns.
+ ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 83)'' for more information on search patterns.
For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
will automatically expand it to the value specified by this variable. For the
the current folder. The default is to pause one second, so a value of zero for
this option suppresses the pause.
- The Mutt Next Generation E-Mail Client 153
+ The Mutt Next Generation E-Mail Client 154
_\b7_\b._\b4_\b._\b2_\b6_\b8 _\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp
Controls the display of lines longer than the screen width in the internal
pager. If _\bs_\be_\bt, long lines are wrapped at a word boundary. If _\bu_\bn_\bs_\be_\bt, lines are
simply wrapped at the screen edge. Also see the ``_\b$_\bm_\ba_\br_\bk_\be_\br_\bs (section 7.4.125 ,
- page 119)'' variable.
+ page 120)'' variable.
_\b7_\b._\b4_\b._\b2_\b6_\b9 _\bs_\bm_\bi_\bl_\be_\by_\bs
Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
The _\bp_\ba_\bg_\be_\br uses this variable to catch some common false positives of
- ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 143)'', most notably smileys in the
+ ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 144)'', most notably smileys in the
beginning of a line
_\b7_\b._\b4_\b._\b2_\b7_\b0 _\bs_\bm_\bi_\bm_\be_\b__\ba_\bs_\bk_\b__\bc_\be_\br_\bt_\b__\bl_\ba_\bb_\be_\bl
address keyid pairs, and which can be manually edited. This one points to the
location of the certificates. (S/MIME only)
- The Mutt Next Generation E-Mail Client 154
+ The Mutt Next Generation E-Mail Client 155
_\b7_\b._\b4_\b._\b2_\b7_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
%k
The key-pair specified with _\b$_\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by (section 7.4.275 ,
- page 154)
+ page 155)
%c
One or more certificate IDs.
%C
CA location: Depending on whether _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section
- 7.4.271 , page 153) points to a directory or file, this expands to
- '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.271 , page 153)' or
- '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.271 , page 153)'.
+ 7.4.271 , page 154) points to a directory or file, this expands to
+ '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.271 , page 154)' or
+ '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.271 , page 154)'.
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-
Type: string
- The Mutt Next Generation E-Mail Client 155
+ The Mutt Next Generation E-Mail Client 156
Default: ''
signature, so that the certificate's owner may get compared to the email's
``From:'' header field. (S/MIME only)
- The Mutt Next Generation E-Mail Client 156
+ The Mutt Next Generation E-Mail Client 157
_\b7_\b._\b4_\b._\b2_\b8_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bi_\bm_\bp_\bo_\br_\bt_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
select the same application that was used to sign/encrypt the original message.
(Note that this variable can be overridden by unsetting _\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bm_\bi_\bm_\be (sec-
- tion 7.4.40 , page 97).) (S/MIME only)
+ tion 7.4.40 , page 98).) (S/MIME only)
_\b7_\b._\b4_\b._\b2_\b8_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bk_\be_\by_\bs
This command is used to created S/MIME signatures of type multipart/signed,
which can be read by all mail clients. (S/MIME only)
- The Mutt Next Generation E-Mail Client 157
+ The Mutt Next Generation E-Mail Client 158
_\b7_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bs_\bi_\bg_\bn_\b__\bo_\bp_\ba_\bq_\bu_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
_\b7_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
- The Mutt Next Generation E-Mail Client 158
+ The Mutt Next Generation E-Mail Client 159
Type: string
Defines the SMTP host which will be used to deliver mail, as opposed to invok-
ing the sendmail binary. Setting this variable overrides the value of ``_\b$_\bs_\be_\bn_\bd_\b-
- _\bm_\ba_\bi_\bl (section 7.4.252 , page 148)'', and any associated variables.
+ _\bm_\ba_\bi_\bl (section 7.4.252 , page 149)'', and any associated variables.
_\b7_\b._\b4_\b._\b2_\b9_\b2 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
Availability: SMTP
Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section
- 7.4.295 , page 158)'' is set, but this variable is not, you will be prompted
+ 7.4.295 , page 159)'' is set, but this variable is not, you will be prompted
for a password when sending.
N\bNo\bot\bte\be:\b: Storing passwords in a configuration file presents a security risk since
continue without TLS in case of an error. Muttng still needs to have SSL sup-
port enabled in order to use it.
- The Mutt Next Generation E-Mail Client 159
+ The Mutt Next Generation E-Mail Client 160
_\b7_\b._\b4_\b._\b2_\b9_\b5 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
Type: sort order
- The Mutt Next Generation E-Mail Client 160
+ The Mutt Next Generation E-Mail Client 161
Default: date
When sorting by threads, this variable controls how threads are sorted in rela-
tion to other threads, and how the branches of the thread trees are sorted.
- This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158)'' can,
+ This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 159)'' can,
except threads (in that case, Mutt-ng will just use date-sent). You can also
specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
come after reverse-. The last- prefix causes messages to be sorted against its
is received in a thread, that thread becomes the last one displayed (or the
first, if you have set sort=reverse-threads.)
- N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
- (section 7.4.298 , page 159) is reversed again (which is not the right thing
+ N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 159)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ (section 7.4.298 , page 160) is reversed again (which is not the right thing
to do, but kept to not break any existing configuration setting).
_\b7_\b._\b4_\b._\b2_\b9_\b9 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
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 7.4.317 , page 166)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ (section 7.4.317 , page 167)'' _\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 7.4.300 ,
- page 160) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
+ page 161) _\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
- matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.236 , page 145)''. With
- _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.300 , page 160) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
+ matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.236 , page 146)''. With
+ _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.300 , page 161) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
whether or not this is the case, as long as the non-``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section
- 7.4.236 , page 145)'' parts of both messages are identical.
+ 7.4.236 , page 146)'' parts of both messages are identical.
- The Mutt Next Generation E-Mail Client 161
+ The Mutt Next Generation E-Mail Client 162
_\b7_\b._\b4_\b._\b3_\b0_\b1 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
Default: ','
- ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.301 , page 160)'' controls what happens when
+ ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.301 , page 161)'' controls what happens when
multiple spam headers are matched: if _\bu_\bn_\bs_\be_\bt, each successive header will over-
write any previous matches value for the spam label. If _\bs_\be_\bt, each successive
match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.301 ,
- page 160)'' as a separator.
+ page 161)'' as a separator.
_\b7_\b._\b4_\b._\b3_\b0_\b2 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
server does not advertise the capability, since it would otherwise have to
- The Mutt Next Generation E-Mail Client 162
+ The Mutt Next Generation E-Mail Client 163
abort the connection anyway. This option supersedes ``_\b$_\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs (section
- 7.4.307 , page 162)''.
+ 7.4.307 , page 163)''.
_\b7_\b._\b4_\b._\b3_\b0_\b6 _\bs_\bs_\bl_\b__\bm_\bi_\bn_\b__\bd_\bh_\b__\bp_\br_\bi_\bm_\be_\b__\bb_\bi_\bt_\bs
Default: yes
- The Mutt Next Generation E-Mail Client 163
+ The Mutt Next Generation E-Mail Client 164
Availability: SSL or GNUTLS
Default: '-*%A'
Controls the characters used by the ``%r'' indicator in ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (sec-
- tion 7.4.313 , page 163)''. The first character is used when the mailbox is
+ tion 7.4.313 , page 164)''. The first character is used when the mailbox is
unchanged. The second is used when the mailbox has been changed, and it needs
to be resynchronized. The third is used if the mailbox is in read-only mode, or
if the mailbox will not be written when exiting that mailbox (You can toggle
%l?]---(%s/%S)-%>-(%P)---'
Controls the format of the status line displayed in the _\bi_\bn_\bd_\be_\bx menu. This
- string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)'', but has
+ string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 115)'', but has
its own set of printf(3)-like sequences:
%b
%d
number of deleted messages *
- The Mutt Next Generation E-Mail Client 164
+ The Mutt Next Generation E-Mail Client 165
%f
the full pathname of the current mailbox
%r
modified/read-only/won't-write/attach-message indicator, according
- to _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs (section 7.4.312 , page 163)
+ to _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs (section 7.4.312 , page 164)
%s
- current sorting mode (_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158))
+ current sorting mode (_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 159))
%S
current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 7.4.298 , page
- 159))
+ 160))
%t
number of tagged messages *
%v
Mutt-ng version string
- The Mutt Next Generation E-Mail Client 165
+ The Mutt Next Generation E-Mail Client 166
%V
currently active limit pattern, if any *
Setting this variable causes the ``status bar'' to be displayed on the first
line of the screen rather than near the bottom.
- The Mutt Next Generation E-Mail Client 166
+ The Mutt Next Generation E-Mail Client 167
_\b7_\b._\b4_\b._\b3_\b1_\b5 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo
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 7.4.58 , page 101)'' is unset.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102)'' 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 7.4.58 , page 101)'' is set to.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 102)'' is set to.
_\b7_\b._\b4_\b._\b3_\b1_\b6 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
When _\bu_\bn_\bs_\be_\bt, non MIME-compliant messages that doesn't have any charset indica-
tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
messages are often generated by old mailers or buggy mailers like MS Outlook
- Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.13 , page 90).
+ Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.13 , page 91).
This option also replaces linear-white-space between encoded-word and *text to
a single space to prevent the display of MIME-encoded ``Subject:'' header field
Default: no
If _\bs_\be_\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
- ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158)'' by mes-
+ ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 159)'' by mes-
sage threads. By default, messages with the same subject are grouped together
in ``pseudo threads.'' This may not always be desirable, such as in a personal
mailbox where you might have several unrelated messages with the subject ``hi''
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 7.4.319 , page 166) when replying. This is
+ matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 7.4.319 , page 167) when replying. This is
useful to properly react on subject changes and reduce ``subject noise.'' (esp.
in Usenet)
- The Mutt Next Generation E-Mail Client 167
+ The Mutt Next Generation E-Mail Client 168
_\b7_\b._\b4_\b._\b3_\b1_\b9 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
- When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 7.4.318 , page 166) is _\bs_\be_\bt, mutt-ng
+ When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 7.4.318 , page 167) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
like ordinary text. To actually make use of this format's features, you'll
need support in your editor.
- Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 114) is ignored when this
+ Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 115) is ignored when this
option is set.
_\b7_\b._\b4_\b._\b3_\b2_\b3 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
Default: no
Affects the ~b and ~h search operations described in section ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
- tion 7.2 , page 82)'' above. If _\bs_\be_\bt, the headers and attachments of messages
+ tion 7.2 , page 83)'' above. If _\bs_\be_\bt, the headers and attachments of messages
to be searched are decoded before searching. If _\bu_\bn_\bs_\be_\bt, messages are searched
as they appear in the folder.
- The Mutt Next Generation E-Mail Client 168
+ The Mutt Next Generation E-Mail Client 169
_\b7_\b._\b4_\b._\b3_\b2_\b4 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
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).
- The Mutt Next Generation E-Mail Client 169
+ The Mutt Next Generation E-Mail Client 170
_\b7_\b._\b4_\b._\b3_\b2_\b9 _\bt_\br_\ba_\bs_\bh
which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
with the SMTP support via libESMTP. Otherwise you may not be able to send
- The Mutt Next Generation E-Mail Client 170
+ The Mutt Next Generation E-Mail Client 171
mail.
When _\bs_\be_\bt, Mutt-ng will either invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page
- 148)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
+ 149)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
negotiation or tell libESMTP to do so.
_\b7_\b._\b4_\b._\b3_\b3_\b4 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
Default: yes
When _\bs_\be_\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
- tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 7.4.93 , page 109)''. If _\bu_\bn_\bs_\be_\bt,
+ tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 7.4.93 , page 110)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
_\b7_\b._\b4_\b._\b3_\b3_\b5 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
When _\bs_\be_\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
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.16 , page 36)'' command.
+ explicitly sets one using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37)'' command.
_\b7_\b._\b4_\b._\b3_\b3_\b6 _\bu_\bs_\be_\b__\bi_\bd_\bn
Default: ''
- The Mutt Next Generation E-Mail Client 171
+ The Mutt Next Generation E-Mail Client 172
Specifies the visual editor to invoke when the _\b~_\bv command is given in the
builtin editor.
_\bm_\be_\bs_\bs_\ba_\bg_\be, _\bp_\bi_\bp_\be_\b-_\be_\bn_\bt_\br_\by, _\bp_\br_\bi_\bn_\bt_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be, and _\bp_\br_\bi_\bn_\bt_\b-_\be_\bn_\bt_\br_\by commands.
It is also used when viewing attachments with ``_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page
- 77)'', provided that the corresponding mailcap entry has a needsterminal flag,
+ 78)'', provided that the corresponding mailcap entry has a needsterminal flag,
and the external program is interactive.
When _\bs_\be_\bt, Mutt-ng will always ask for a key. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will wait for
Default: yes
- The Mutt Next Generation E-Mail Client 172
+ The Mutt Next Generation E-Mail Client 173
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.
indicate progress. If set to 0, only a single message will be displayed before
writing a mailbox.
- Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 7.4.231 , page 143)'' variable.
+ Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 7.4.231 , page 144)'' variable.
_\b7_\b._\b4_\b._\b3_\b4_\b5 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
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 7.4.347 , page 172) 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 7.4.313 , page 163)''.
+ tion 7.4.347 , page 173) 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 7.4.313 , page 164)''.
_\b7_\b._\b4_\b._\b3_\b4_\b6 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
Default: ''
- If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.347 , page 172) is _\bs_\be_\bt, this string will be
+ If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.347 , page 173) is _\bs_\be_\bt, this string will be
used to set the title when leaving mutt-ng. For terminal-based programs,
there's no easy and portable way to read the current title so mutt-ng cannot
read it upon startup and restore it when exiting.
Type: string
- The Mutt Next Generation E-Mail Client 173
+ The Mutt Next Generation E-Mail Client 174
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 7.4.347 , page 172) 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 7.4.347 , page 173) 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 7.4.313 ,
- page 163)''.
+ page 164)''.
_\b7_\b._\b5 _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
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.5 , page 25) command.
+ with the _\bb_\bi_\bn_\bd (section 3.5 , page 26) command.
_\b7_\b._\b5_\b._\b1 _\bg_\be_\bn_\be_\br_\bi_\bc
top-page H move to the top of the page
what-key not bound display the keycode for a key press
- The Mutt Next Generation E-Mail Client 174
+ The Mutt Next Generation E-Mail Client 175
_\b7_\b._\b5_\b._\b2 _\bi_\bn_\bd_\be_\bx
- The Mutt Next Generation E-Mail Client 175
+ The Mutt Next Generation E-Mail Client 176
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 Next Generation E-Mail Client 176
+ The Mutt Next Generation E-Mail Client 177
sort-mailbox o sort messages
sort-reverse O sort messages in reverse order
_\b7_\b._\b5_\b._\b3 _\bp_\ba_\bg_\be_\br
- The Mutt Next Generation E-Mail Client 177
+ The Mutt Next Generation E-Mail Client 178
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 Next Generation E-Mail Client 178
+ The Mutt Next Generation E-Mail Client 179
reply r reply to a message
save-message s save message/attachment to a file
_\b7_\b._\b5_\b._\b6 _\ba_\bt_\bt_\ba_\bc_\bh
- The Mutt Next Generation E-Mail Client 179
+ The Mutt Next Generation E-Mail Client 180
bounce-message b remail a message to another user
collapse-parts v toggle display of subparts
_\b7_\b._\b5_\b._\b7 _\bc_\bo_\bm_\bp_\bo_\bs_\be
- The Mutt Next Generation E-Mail Client 180
+ The Mutt Next Generation E-Mail Client 181
attach-file a attach a file(s) to this message
attach-message A attach message(s) to this message
_\b7_\b._\b5_\b._\b9 _\bb_\br_\bo_\bw_\bs_\be_\br
- The Mutt Next Generation E-Mail Client 181
+ The Mutt Next Generation E-Mail Client 182
change-dir c change directories
check-new TAB check mailboxes for new mail
_\b8_\b. _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\by
- The Mutt Next Generation E-Mail Client 182
+ The Mutt Next Generation E-Mail Client 183
_\b8_\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 Next Generation E-Mail Client 183
+ The Mutt Next Generation E-Mail Client 184
Brandon Long <blong@fiction.net>,
Elimar Riesebieter <riesebie@lxtec.de>
- The Mutt Next Generation E-Mail Client 184
+ The Mutt Next Generation E-Mail Client 185
_\b8_\b._\b2 _\bA_\bb_\bo_\bu_\bt _\bt_\bh_\bi_\bs _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt
This document was written in SGML, and then rendered using the sgml-tools pack-
age.
- The Mutt Next Generation E-Mail Client 185
+ The Mutt Next Generation E-Mail Client 186
CONTENTS
3.3.3 Configuration Variables 23
3.3.4 Self-Defined Variables 23
- 3.3.5 Type Conversions 24
- 3.4 Defining/Using aliases ......................................... 24
- 3.5 Changing the default key bindings .............................. 25
- 3.6 Defining aliases for character sets ........................... 27
- 3.7 Setting variables based upon mailbox ........................... 27
- 3.8 Keyboard macros ................................................ 28
- 3.9 Using color and mono video attributes .......................... 29
- 3.10 Ignoring (weeding) unwanted message headers .................... 31
- 3.11 Alternative addresses .......................................... 32
- 3.12 Format = Flowed .............................................. 32
- 3.12.1 Introduction 32
+ 3.3.5 Type Conversions 25
+ 3.4 Defining/Using aliases ......................................... 25
+ 3.5 Changing the default key bindings .............................. 26
+ 3.6 Defining aliases for character sets ........................... 28
+ 3.7 Setting variables based upon mailbox ........................... 28
+ 3.8 Keyboard macros ................................................ 29
+ 3.9 Using color and mono video attributes .......................... 30
+ 3.10 Ignoring (weeding) unwanted message headers .................... 32
+ 3.11 Alternative addresses .......................................... 33
+ 3.12 Format = Flowed .............................................. 33
+ 3.12.1 Introduction 33
3.12.2 Receiving: Display Setup 33
3.12.3 Sending 34
- 3.12.4 Additional Notes 34
- 3.13 Mailing lists .................................................. 34
- 3.14 Using Multiple spool mailboxes ................................. 35
+ 3.12.4 Additional Notes 35
+ 3.13 Mailing lists .................................................. 35
+ 3.14 Using Multiple spool mailboxes ................................. 36
3.15 Defining mailboxes which receive mail .......................... 36
- 3.16 User defined headers ........................................... 36
- 3.17 Defining the order of headers when viewing messages ............ 37
- 3.18 Specify default save filename .................................. 37
+ 3.16 User defined headers ........................................... 37
+ 3.17 Defining the order of headers when viewing messages ............ 38
+ 3.18 Specify default save filename .................................. 38
3.19 Specify default Fcc: mailbox when composing .................... 38
- 3.20 Specify default save filename and default Fcc: mailbox at once . 38
- 3.21 Change settings based upon message recipients .................. 38
- 3.22 Change settings before formatting a message .................... 39
- 3.23 Choosing the cryptographic key of the recipient ................ 39
+ 3.20 Specify default save filename and default Fcc: mailbox at once . 39
+ 3.21 Change settings based upon message recipients .................. 39
+ 3.22 Change settings before formatting a message .................... 40
+ 3.23 Choosing the cryptographic key of the recipient ................ 40
3.24 Adding key sequences to the keyboard buffer .................... 40
- 3.25 Executing functions ............................................ 40
- 3.26 Message Scoring ................................................ 40
- 3.27 Spam detection ................................................. 41
- 3.28 Setting variables .............................................. 43
- 3.29 Reading initialization commands from another file .............. 44
- 3.30 Removing hooks ................................................. 44
- 3.31 Sharing Setups ............................................. 44
+ 3.25 Executing functions ............................................ 41
+ 3.26 Message Scoring ................................................ 41
+ 3.27 Spam detection ................................................. 42
+ 3.28 Setting variables .............................................. 44
+ 3.29 Reading initialization commands from another file .............. 45
+ 3.30 Removing hooks ................................................. 45
+ 3.31 Sharing Setups ............................................. 45
3.31.1 Character Sets 45
- 3.31.2 Modularization 45
- 3.31.3 Conditional parts 45
- 3.32 Obsolete Variables ............................................. 47
-
- 4. Advanced Usage ....................................................... 47
- 4.1 Regular Expressions ............................................ 47
- 4.2 Patterns ....................................................... 50
- 4.2.1 Complex Patterns 50
- 4.2.2 Patterns and Dates 51
+ 3.31.2 Modularization 46
+ 3.31.3 Conditional parts 46
+ 3.32 Obsolete Variables ............................................. 48
+
+ 4. Advanced Usage ....................................................... 48
+ 4.1 Regular Expressions ............................................ 48
+ 4.2 Patterns ....................................................... 51
+ 4.2.1 Complex Patterns 51
+ 4.2.2 Patterns and Dates 52
4.3 Format Strings ............................................. 52
4.3.1 Introduction 52
- 4.3.2 Conditional Expansion 53
- 4.3.3 Modifications and Padding 54
+ 4.3.2 Conditional Expansion 54
+ 4.3.3 Modifications and Padding 55
4.4 Using Tags ..................................................... 55
- 4.5 Using Hooks .................................................... 55
- 4.5.1 Message Matching in Hooks 56
- 4.6 Using the sidebar .............................................. 56
+ 4.5 Using Hooks .................................................... 56
+ 4.5.1 Message Matching in Hooks 57
+ 4.6 Using the sidebar .............................................. 57
ii
- 4.7 External Address Queries ....................................... 57
- 4.8 Mailbox Formats ................................................ 58
- 4.9 Mailbox Shortcuts .............................................. 59
- 4.10 Handling Mailing Lists ......................................... 59
+ 4.7 External Address Queries ....................................... 58
+ 4.8 Mailbox Formats ................................................ 59
+ 4.9 Mailbox Shortcuts .............................................. 60
+ 4.10 Handling Mailing Lists ......................................... 60
4.11 Editing threads ................................................ 61
- 4.11.1 Linking threads 61
- 4.11.2 Breaking threads 61
- 4.12 Delivery Status Notification (DSN) Support ..................... 61
+ 4.11.1 Linking threads 62
+ 4.11.2 Breaking threads 62
+ 4.12 Delivery Status Notification (DSN) Support ..................... 62
4.13 POP3 Support (OPTIONAL) ........................................ 62
- 4.14 IMAP Support (OPTIONAL) ........................................ 62
- 4.14.1 The Folder Browser 63
+ 4.14 IMAP Support (OPTIONAL) ........................................ 63
+ 4.14.1 The Folder Browser 64
4.14.2 Authentication 64
- 4.15 NNTP Support (OPTIONAL) ........................................ 64
- 4.15.1 Again: Scoring 64
- 4.16 SMTP Support (OPTIONAL) ........................................ 65
- 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 66
- 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 66
- 4.19 Compressed folders Support (OPTIONAL) .......................... 66
- 4.19.1 Open a compressed mailbox for reading 67
+ 4.15 NNTP Support (OPTIONAL) ........................................ 65
+ 4.15.1 Again: Scoring 65
+ 4.16 SMTP Support (OPTIONAL) ........................................ 66
+ 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 67
+ 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 67
+ 4.19 Compressed folders Support (OPTIONAL) .......................... 67
+ 4.19.1 Open a compressed mailbox for reading 68
4.19.2 Write a compressed mailbox 68
- 4.19.3 Append a message to a compressed mailbox 68
- 4.19.4 Encrypted folders 69
-
- 5. Mutt-ng's MIME Support ............................................... 69
- 5.1 Using MIME in Mutt ............................................. 69
- 5.1.1 Viewing MIME messages in the pager 69
- 5.1.2 The Attachment Menu 70
- 5.1.3 The Compose Menu 70
+ 4.19.3 Append a message to a compressed mailbox 69
+ 4.19.4 Encrypted folders 70
+
+ 5. Mutt-ng's MIME Support ............................................... 70
+ 5.1 Using MIME in Mutt ............................................. 70
+ 5.1.1 Viewing MIME messages in the pager 70
+ 5.1.2 The Attachment Menu 71
+ 5.1.3 The Compose Menu 71
5.2 MIME Type configuration with mime.types ........................ 71
- 5.3 MIME Viewer configuration with mailcap ......................... 71
- 5.3.1 The Basics of the mailcap file 72
- 5.3.2 Secure use of mailcap 73
- 5.3.3 Advanced mailcap Usage 73
- 5.3.4 Example mailcap files 76
- 5.4 MIME Autoview .................................................. 77
- 5.5 MIME Multipart/Alternative ..................................... 78
- 5.6 MIME Lookup .................................................... 78
-
- 6. Security Considerations ............................................ 79
- 6.1 Passwords .................................................. 79
- 6.2 Temporary Files ............................................ 79
+ 5.3 MIME Viewer configuration with mailcap ......................... 72
+ 5.3.1 The Basics of the mailcap file 73
+ 5.3.2 Secure use of mailcap 74
+ 5.3.3 Advanced mailcap Usage 74
+ 5.3.4 Example mailcap files 77
+ 5.4 MIME Autoview .................................................. 78
+ 5.5 MIME Multipart/Alternative ..................................... 79
+ 5.6 MIME Lookup .................................................... 79
+
+ 6. Security Considerations ............................................ 80
+ 6.1 Passwords .................................................. 80
+ 6.2 Temporary Files ............................................ 80
6.3 Information Leaks ............................................ 80
6.3.1 Message-ID: headers 80
- 6.3.2 mailto:-style links 80
- 6.4 External applications ...................................... 80
- 6.4.1 mailcap 80
- 6.4.2 Other 81
+ 6.3.2 mailto:-style links 81
+ 6.4 External applications ...................................... 81
+ 6.4.1 mailcap 81
+ 6.4.2 Other 82
- 7. Reference ............................................................ 81
- 7.1 Command line options ........................................... 81
- 7.2 Patterns ....................................................... 82
- 7.3 Configuration Commands ......................................... 84
- 7.4 Configuration variables .......................................... 86
+ 7. Reference ............................................................ 82
+ 7.1 Command line options ........................................... 82
+ 7.2 Patterns ....................................................... 83
+ 7.3 Configuration Commands ......................................... 85
+ 7.4 Configuration variables .......................................... 87
iii
- 7.4.1 abort_noattach 87
- 7.4.2 abort_nosubject 88
- 7.4.3 abort_unmodified 88
- 7.4.4 agent_string 88
- 7.4.5 alias_file 88
- 7.4.6 alias_format 88
- 7.4.7 allow_8bit 89
- 7.4.8 allow_ansi 89
- 7.4.9 arrow_cursor 89
- 7.4.10 ascii_chars 90
- 7.4.11 askbcc 90
- 7.4.12 askcc 90
- 7.4.13 assumed_charset 90
- 7.4.14 attach_format 90
- 7.4.15 attach_remind_regexp 91
- 7.4.16 attach_sep 92
- 7.4.17 attach_split 92
- 7.4.18 attribution 92
- 7.4.19 auto_tag 92
- 7.4.20 autoedit 92
- 7.4.21 beep 93
- 7.4.22 beep_new 93
- 7.4.23 bounce 93
- 7.4.24 bounce_delivered 93
- 7.4.25 braille_friendly 93
- 7.4.26 certificate_file 94
- 7.4.27 charset 94
- 7.4.28 check_new 94
- 7.4.29 collapse_unread 94
- 7.4.30 compose_format 95
- 7.4.31 config_charset 95
- 7.4.32 confirmappend 95
- 7.4.33 confirmcreate 95
- 7.4.34 connect_timeout 95
- 7.4.35 content_type 96
- 7.4.36 copy 96
- 7.4.37 crypt_autoencrypt 96
- 7.4.38 crypt_autopgp 96
- 7.4.39 crypt_autosign 97
- 7.4.40 crypt_autosmime 97
- 7.4.41 crypt_replyencrypt 97
- 7.4.42 crypt_replysign 97
- 7.4.43 crypt_replysignencrypted 97
- 7.4.44 crypt_timestamp 98
- 7.4.45 crypt_use_gpgme 98
- 7.4.46 crypt_verify_sig 98
- 7.4.47 date_format 98
- 7.4.48 default_hook 99
- 7.4.49 delete 99
- 7.4.50 delete_space 99
- 7.4.51 delete_untag 99
- 7.4.52 digest_collapse 99
- 7.4.53 display_filter 100
+ 7.4.1 abort_noattach 88
+ 7.4.2 abort_nosubject 89
+ 7.4.3 abort_unmodified 89
+ 7.4.4 agent_string 89
+ 7.4.5 alias_file 89
+ 7.4.6 alias_format 89
+ 7.4.7 allow_8bit 90
+ 7.4.8 allow_ansi 90
+ 7.4.9 arrow_cursor 90
+ 7.4.10 ascii_chars 91
+ 7.4.11 askbcc 91
+ 7.4.12 askcc 91
+ 7.4.13 assumed_charset 91
+ 7.4.14 attach_format 91
+ 7.4.15 attach_remind_regexp 92
+ 7.4.16 attach_sep 93
+ 7.4.17 attach_split 93
+ 7.4.18 attribution 93
+ 7.4.19 auto_tag 93
+ 7.4.20 autoedit 93
+ 7.4.21 beep 94
+ 7.4.22 beep_new 94
+ 7.4.23 bounce 94
+ 7.4.24 bounce_delivered 94
+ 7.4.25 braille_friendly 94
+ 7.4.26 certificate_file 95
+ 7.4.27 charset 95
+ 7.4.28 check_new 95
+ 7.4.29 collapse_unread 95
+ 7.4.30 compose_format 96
+ 7.4.31 config_charset 96
+ 7.4.32 confirmappend 96
+ 7.4.33 confirmcreate 96
+ 7.4.34 connect_timeout 96
+ 7.4.35 content_type 97
+ 7.4.36 copy 97
+ 7.4.37 crypt_autoencrypt 97
+ 7.4.38 crypt_autopgp 97
+ 7.4.39 crypt_autosign 98
+ 7.4.40 crypt_autosmime 98
+ 7.4.41 crypt_replyencrypt 98
+ 7.4.42 crypt_replysign 98
+ 7.4.43 crypt_replysignencrypted 98
+ 7.4.44 crypt_timestamp 99
+ 7.4.45 crypt_use_gpgme 99
+ 7.4.46 crypt_verify_sig 99
+ 7.4.47 date_format 99
+ 7.4.48 default_hook 100
+ 7.4.49 delete 100
+ 7.4.50 delete_space 100
+ 7.4.51 delete_untag 100
+ 7.4.52 digest_collapse 100
+ 7.4.53 display_filter 101
iv
- 7.4.54 dotlock_program 100
- 7.4.55 dsn_notify 100
- 7.4.56 dsn_return 100
- 7.4.57 duplicate_threads 101
- 7.4.58 edit_headers 101
- 7.4.59 editor 101
- 7.4.60 encode_from 101
- 7.4.61 entropy_file 101
- 7.4.62 envelope_from 102
- 7.4.63 escape 102
- 7.4.64 fast_reply 102
- 7.4.65 fcc_attach 102
- 7.4.66 fcc_clear 102
- 7.4.67 file_charset 103
- 7.4.68 folder 103
- 7.4.69 folder_format 103
- 7.4.70 followup_to 104
- 7.4.71 force_buffy_check 104
- 7.4.72 force_name 105
- 7.4.73 forward_decode 105
- 7.4.74 forward_decrypt 105
- 7.4.75 forward_edit 105
- 7.4.76 forward_format 105
- 7.4.77 forward_quote 106
- 7.4.78 from 106
- 7.4.79 gecos_mask 106
- 7.4.80 hdrs 106
- 7.4.81 header 107
- 7.4.82 header_cache 107
- 7.4.83 header_cache_compress 107
- 7.4.84 help 107
- 7.4.85 hidden_host 108
- 7.4.86 hide_limited 108
- 7.4.87 hide_missing 108
- 7.4.88 hide_thread_subject 108
- 7.4.89 hide_top_limited 108
- 7.4.90 hide_top_missing 108
- 7.4.91 history 109
- 7.4.92 honor_followup_to 109
- 7.4.93 hostname 109
- 7.4.94 ignore_list_reply_to 109
- 7.4.95 imap_authenticators 109
- 7.4.96 imap_check_subscribed 110
- 7.4.97 imap_delim_chars 110
- 7.4.98 imap_headers 110
- 7.4.99 imap_home_namespace 111
- 7.4.100 imap_keepalive 111
- 7.4.101 imap_list_subscribed 111
- 7.4.102 imap_login 111
- 7.4.103 imap_mail_check 112
- 7.4.104 imap_pass 112
- 7.4.105 imap_passive 112
- 7.4.106 imap_peek 112
+ 7.4.54 dotlock_program 101
+ 7.4.55 dsn_notify 101
+ 7.4.56 dsn_return 101
+ 7.4.57 duplicate_threads 102
+ 7.4.58 edit_headers 102
+ 7.4.59 editor 102
+ 7.4.60 encode_from 102
+ 7.4.61 entropy_file 102
+ 7.4.62 envelope_from 103
+ 7.4.63 escape 103
+ 7.4.64 fast_reply 103
+ 7.4.65 fcc_attach 103
+ 7.4.66 fcc_clear 103
+ 7.4.67 file_charset 104
+ 7.4.68 folder 104
+ 7.4.69 folder_format 104
+ 7.4.70 followup_to 105
+ 7.4.71 force_buffy_check 105
+ 7.4.72 force_name 106
+ 7.4.73 forward_decode 106
+ 7.4.74 forward_decrypt 106
+ 7.4.75 forward_edit 106
+ 7.4.76 forward_format 106
+ 7.4.77 forward_quote 107
+ 7.4.78 from 107
+ 7.4.79 gecos_mask 107
+ 7.4.80 hdrs 107
+ 7.4.81 header 108
+ 7.4.82 header_cache 108
+ 7.4.83 header_cache_compress 108
+ 7.4.84 help 108
+ 7.4.85 hidden_host 109
+ 7.4.86 hide_limited 109
+ 7.4.87 hide_missing 109
+ 7.4.88 hide_thread_subject 109
+ 7.4.89 hide_top_limited 109
+ 7.4.90 hide_top_missing 109
+ 7.4.91 history 110
+ 7.4.92 honor_followup_to 110
+ 7.4.93 hostname 110
+ 7.4.94 ignore_list_reply_to 110
+ 7.4.95 imap_authenticators 110
+ 7.4.96 imap_check_subscribed 111
+ 7.4.97 imap_delim_chars 111
+ 7.4.98 imap_headers 111
+ 7.4.99 imap_home_namespace 112
+ 7.4.100 imap_keepalive 112
+ 7.4.101 imap_list_subscribed 112
+ 7.4.102 imap_login 112
+ 7.4.103 imap_mail_check 113
+ 7.4.104 imap_pass 113
+ 7.4.105 imap_passive 113
+ 7.4.106 imap_peek 113
v
- 7.4.107 imap_reconnect 113
- 7.4.108 imap_servernoise 113
- 7.4.109 imap_user 113
- 7.4.110 implicit_autoview 113
- 7.4.111 include 113
- 7.4.112 include_onlyfirst 114
- 7.4.113 indent_string 114
- 7.4.114 index_format 114
- 7.4.115 ispell 117
- 7.4.116 keep_flagged 117
- 7.4.117 list_reply 117
- 7.4.118 locale 117
- 7.4.119 mail_check 117
- 7.4.120 mailcap_path 118
- 7.4.121 mailcap_sanitize 118
- 7.4.122 maildir_header_cache_verify 118
- 7.4.123 maildir_trash 118
- 7.4.124 mark_old 118
- 7.4.125 markers 119
- 7.4.126 mask 119
- 7.4.127 max_display_recips 119
- 7.4.128 max_line_length 119
- 7.4.129 mbox 119
- 7.4.130 mbox_type 120
- 7.4.131 menu_context 120
- 7.4.132 menu_move_off 120
- 7.4.133 menu_scroll 120
- 7.4.134 message_format 120
- 7.4.135 meta_key 121
- 7.4.136 metoo 121
- 7.4.137 mh_purge 121
- 7.4.138 mh_seq_flagged 121
- 7.4.139 mh_seq_replied 121
- 7.4.140 mh_seq_unseen 121
- 7.4.141 mime_forward 122
- 7.4.142 mime_forward_decode 122
- 7.4.143 mime_forward_rest 122
- 7.4.144 mix_entry_format 122
- 7.4.145 mixmaster 123
- 7.4.146 move 123
- 7.4.147 msgid_format 123
- 7.4.148 narrow_tree 124
- 7.4.149 nntp_ask_followup_to 124
- 7.4.150 nntp_ask_x_comment_to 124
- 7.4.151 nntp_cache_dir 125
- 7.4.152 nntp_catchup 125
- 7.4.153 nntp_context 125
- 7.4.154 nntp_followup_to_poster 125
- 7.4.155 nntp_group_index_format 126
- 7.4.156 nntp_host 126
- 7.4.157 nntp_inews 126
- 7.4.158 nntp_load_description 127
- 7.4.159 nntp_mail_check 127
+ 7.4.107 imap_reconnect 114
+ 7.4.108 imap_servernoise 114
+ 7.4.109 imap_user 114
+ 7.4.110 implicit_autoview 114
+ 7.4.111 include 114
+ 7.4.112 include_onlyfirst 115
+ 7.4.113 indent_string 115
+ 7.4.114 index_format 115
+ 7.4.115 ispell 118
+ 7.4.116 keep_flagged 118
+ 7.4.117 list_reply 118
+ 7.4.118 locale 118
+ 7.4.119 mail_check 118
+ 7.4.120 mailcap_path 119
+ 7.4.121 mailcap_sanitize 119
+ 7.4.122 maildir_header_cache_verify 119
+ 7.4.123 maildir_trash 119
+ 7.4.124 mark_old 119
+ 7.4.125 markers 120
+ 7.4.126 mask 120
+ 7.4.127 max_display_recips 120
+ 7.4.128 max_line_length 120
+ 7.4.129 mbox 120
+ 7.4.130 mbox_type 121
+ 7.4.131 menu_context 121
+ 7.4.132 menu_move_off 121
+ 7.4.133 menu_scroll 121
+ 7.4.134 message_format 121
+ 7.4.135 meta_key 122
+ 7.4.136 metoo 122
+ 7.4.137 mh_purge 122
+ 7.4.138 mh_seq_flagged 122
+ 7.4.139 mh_seq_replied 122
+ 7.4.140 mh_seq_unseen 122
+ 7.4.141 mime_forward 123
+ 7.4.142 mime_forward_decode 123
+ 7.4.143 mime_forward_rest 123
+ 7.4.144 mix_entry_format 123
+ 7.4.145 mixmaster 124
+ 7.4.146 move 124
+ 7.4.147 msgid_format 124
+ 7.4.148 narrow_tree 125
+ 7.4.149 nntp_ask_followup_to 125
+ 7.4.150 nntp_ask_x_comment_to 125
+ 7.4.151 nntp_cache_dir 126
+ 7.4.152 nntp_catchup 126
+ 7.4.153 nntp_context 126
+ 7.4.154 nntp_followup_to_poster 126
+ 7.4.155 nntp_group_index_format 127
+ 7.4.156 nntp_host 127
+ 7.4.157 nntp_inews 127
+ 7.4.158 nntp_load_description 128
+ 7.4.159 nntp_mail_check 128
vi
- 7.4.160 nntp_mime_subject 127
- 7.4.161 nntp_newsrc 127
- 7.4.162 nntp_pass 128
- 7.4.163 nntp_post_moderated 128
- 7.4.164 nntp_reconnect 128
- 7.4.165 nntp_save_unsubscribed 129
- 7.4.166 nntp_show_new_news 129
- 7.4.167 nntp_show_only_unread 129
- 7.4.168 nntp_user 129
- 7.4.169 nntp_x_comment_to 129
- 7.4.170 operating_system 130
- 7.4.171 pager 130
- 7.4.172 pager_context 130
- 7.4.173 pager_format 130
- 7.4.174 pager_index_lines 130
- 7.4.175 pager_stop 131
- 7.4.176 pgp_auto_decode 131
- 7.4.177 pgp_autoinline 131
- 7.4.178 pgp_check_exit 132
- 7.4.179 pgp_clearsign_command 132
- 7.4.180 pgp_decode_command 132
- 7.4.181 pgp_decrypt_command 132
- 7.4.182 pgp_encrypt_only_command 133
- 7.4.183 pgp_encrypt_sign_command 133
- 7.4.184 pgp_entry_format 133
- 7.4.185 pgp_export_command 134
- 7.4.186 pgp_getkeys_command 134
- 7.4.187 pgp_good_sign 134
- 7.4.188 pgp_ignore_subkeys 134
- 7.4.189 pgp_import_command 134
- 7.4.190 pgp_list_pubring_command 135
- 7.4.191 pgp_list_secring_command 135
- 7.4.192 pgp_long_ids 135
- 7.4.193 pgp_mime_auto 135
- 7.4.194 pgp_replyinline 135
- 7.4.195 pgp_retainable_sigs 136
- 7.4.196 pgp_show_unusable 136
- 7.4.197 pgp_sign_as 136
- 7.4.198 pgp_sign_command 136
- 7.4.199 pgp_sort_keys 137
- 7.4.200 pgp_strict_enc 137
- 7.4.201 pgp_timeout 137
- 7.4.202 pgp_use_gpg_agent 137
- 7.4.203 pgp_verify_command 138
- 7.4.204 pgp_verify_key_command 138
- 7.4.205 pipe_decode 138
- 7.4.206 pipe_sep 138
- 7.4.207 pipe_split 138
- 7.4.208 pop_auth_try_all 138
- 7.4.209 pop_authenticators 139
- 7.4.210 pop_delete 139
- 7.4.211 pop_host 139
- 7.4.212 pop_last 140
+ 7.4.160 nntp_mime_subject 128
+ 7.4.161 nntp_newsrc 128
+ 7.4.162 nntp_pass 129
+ 7.4.163 nntp_post_moderated 129
+ 7.4.164 nntp_reconnect 129
+ 7.4.165 nntp_save_unsubscribed 130
+ 7.4.166 nntp_show_new_news 130
+ 7.4.167 nntp_show_only_unread 130
+ 7.4.168 nntp_user 130
+ 7.4.169 nntp_x_comment_to 130
+ 7.4.170 operating_system 131
+ 7.4.171 pager 131
+ 7.4.172 pager_context 131
+ 7.4.173 pager_format 131
+ 7.4.174 pager_index_lines 131
+ 7.4.175 pager_stop 132
+ 7.4.176 pgp_auto_decode 132
+ 7.4.177 pgp_autoinline 132
+ 7.4.178 pgp_check_exit 133
+ 7.4.179 pgp_clearsign_command 133
+ 7.4.180 pgp_decode_command 133
+ 7.4.181 pgp_decrypt_command 133
+ 7.4.182 pgp_encrypt_only_command 134
+ 7.4.183 pgp_encrypt_sign_command 134
+ 7.4.184 pgp_entry_format 134
+ 7.4.185 pgp_export_command 135
+ 7.4.186 pgp_getkeys_command 135
+ 7.4.187 pgp_good_sign 135
+ 7.4.188 pgp_ignore_subkeys 135
+ 7.4.189 pgp_import_command 135
+ 7.4.190 pgp_list_pubring_command 136
+ 7.4.191 pgp_list_secring_command 136
+ 7.4.192 pgp_long_ids 136
+ 7.4.193 pgp_mime_auto 136
+ 7.4.194 pgp_replyinline 136
+ 7.4.195 pgp_retainable_sigs 137
+ 7.4.196 pgp_show_unusable 137
+ 7.4.197 pgp_sign_as 137
+ 7.4.198 pgp_sign_command 137
+ 7.4.199 pgp_sort_keys 138
+ 7.4.200 pgp_strict_enc 138
+ 7.4.201 pgp_timeout 138
+ 7.4.202 pgp_use_gpg_agent 138
+ 7.4.203 pgp_verify_command 139
+ 7.4.204 pgp_verify_key_command 139
+ 7.4.205 pipe_decode 139
+ 7.4.206 pipe_sep 139
+ 7.4.207 pipe_split 139
+ 7.4.208 pop_auth_try_all 139
+ 7.4.209 pop_authenticators 140
+ 7.4.210 pop_delete 140
+ 7.4.211 pop_host 140
+ 7.4.212 pop_last 141
vii
- 7.4.213 pop_mail_check 140
- 7.4.214 pop_pass 140
- 7.4.215 pop_reconnect 140
- 7.4.216 pop_user 140
- 7.4.217 post_indent_string 141
- 7.4.218 postpone 141
- 7.4.219 postponed 141
- 7.4.220 preconnect 141
- 7.4.221 print 142
- 7.4.222 print_command 142
- 7.4.223 print_decode 142
- 7.4.224 print_split 142
- 7.4.225 prompt_after 142
- 7.4.226 query_command 143
- 7.4.227 quit 143
- 7.4.228 quote_empty 143
- 7.4.229 quote_quoted 143
- 7.4.230 quote_regexp 143
- 7.4.231 read_inc 144
- 7.4.232 read_only 144
- 7.4.233 realname 144
- 7.4.234 recall 144
- 7.4.235 record 144
- 7.4.236 reply_regexp 145
- 7.4.237 reply_self 145
- 7.4.238 reply_to 145
- 7.4.239 resolve 145
- 7.4.240 reverse_alias 146
- 7.4.241 reverse_name 146
- 7.4.242 reverse_realname 146
- 7.4.243 rfc2047_parameters 146
- 7.4.244 save_address 147
- 7.4.245 save_empty 147
- 7.4.246 save_name 147
- 7.4.247 score 148
- 7.4.248 score_threshold_delete 148
- 7.4.249 score_threshold_flag 148
- 7.4.250 score_threshold_read 148
- 7.4.251 send_charset 148
- 7.4.252 sendmail 149
- 7.4.253 sendmail_wait 149
- 7.4.254 shell 149
- 7.4.255 sidebar_boundary 149
- 7.4.256 sidebar_delim 150
- 7.4.257 sidebar_newmail_only 150
- 7.4.258 sidebar_number_format 150
- 7.4.259 sidebar_shorten_hierarchy 151
- 7.4.260 sidebar_visible 151
- 7.4.261 sidebar_width 151
- 7.4.262 sig_dashes 151
- 7.4.263 sig_on_top 151
- 7.4.264 signature 152
- 7.4.265 signoff_string 152
+ 7.4.213 pop_mail_check 141
+ 7.4.214 pop_pass 141
+ 7.4.215 pop_reconnect 141
+ 7.4.216 pop_user 141
+ 7.4.217 post_indent_string 142
+ 7.4.218 postpone 142
+ 7.4.219 postponed 142
+ 7.4.220 preconnect 142
+ 7.4.221 print 143
+ 7.4.222 print_command 143
+ 7.4.223 print_decode 143
+ 7.4.224 print_split 143
+ 7.4.225 prompt_after 143
+ 7.4.226 query_command 144
+ 7.4.227 quit 144
+ 7.4.228 quote_empty 144
+ 7.4.229 quote_quoted 144
+ 7.4.230 quote_regexp 144
+ 7.4.231 read_inc 145
+ 7.4.232 read_only 145
+ 7.4.233 realname 145
+ 7.4.234 recall 145
+ 7.4.235 record 145
+ 7.4.236 reply_regexp 146
+ 7.4.237 reply_self 146
+ 7.4.238 reply_to 146
+ 7.4.239 resolve 146
+ 7.4.240 reverse_alias 147
+ 7.4.241 reverse_name 147
+ 7.4.242 reverse_realname 147
+ 7.4.243 rfc2047_parameters 147
+ 7.4.244 save_address 148
+ 7.4.245 save_empty 148
+ 7.4.246 save_name 148
+ 7.4.247 score 149
+ 7.4.248 score_threshold_delete 149
+ 7.4.249 score_threshold_flag 149
+ 7.4.250 score_threshold_read 149
+ 7.4.251 send_charset 149
+ 7.4.252 sendmail 150
+ 7.4.253 sendmail_wait 150
+ 7.4.254 shell 150
+ 7.4.255 sidebar_boundary 150
+ 7.4.256 sidebar_delim 151
+ 7.4.257 sidebar_newmail_only 151
+ 7.4.258 sidebar_number_format 151
+ 7.4.259 sidebar_shorten_hierarchy 152
+ 7.4.260 sidebar_visible 152
+ 7.4.261 sidebar_width 152
+ 7.4.262 sig_dashes 152
+ 7.4.263 sig_on_top 152
+ 7.4.264 signature 153
+ 7.4.265 signoff_string 153
viii
- 7.4.266 simple_search 152
- 7.4.267 sleep_time 152
- 7.4.268 smart_wrap 153
- 7.4.269 smileys 153
- 7.4.270 smime_ask_cert_label 153
- 7.4.271 smime_ca_location 153
- 7.4.272 smime_certificates 153
- 7.4.273 smime_decrypt_command 154
- 7.4.274 smime_decrypt_use_default_key 154
- 7.4.275 smime_default_key 154
- 7.4.276 smime_encrypt_command 155
- 7.4.277 smime_encrypt_with 155
- 7.4.278 smime_get_cert_command 155
- 7.4.279 smime_get_cert_email_command 155
- 7.4.280 smime_get_signer_cert_command 155
- 7.4.281 smime_import_cert_command 156
- 7.4.282 smime_is_default 156
- 7.4.283 smime_keys 156
- 7.4.284 smime_pk7out_command 156
- 7.4.285 smime_sign_command 156
- 7.4.286 smime_sign_opaque_command 157
- 7.4.287 smime_timeout 157
- 7.4.288 smime_verify_command 157
- 7.4.289 smime_verify_opaque_command 157
- 7.4.290 smtp_envelope 157
- 7.4.291 smtp_host 157
- 7.4.292 smtp_pass 158
- 7.4.293 smtp_port 158
- 7.4.294 smtp_use_tls 158
- 7.4.295 smtp_user 159
- 7.4.296 sort 159
- 7.4.297 sort_alias 159
- 7.4.298 sort_aux 159
- 7.4.299 sort_browser 160
- 7.4.300 sort_re 160
- 7.4.301 spam_separator 161
- 7.4.302 spoolfile 161
- 7.4.303 ssl_ca_certificates_file 161
- 7.4.304 ssl_client_cert 161
- 7.4.305 ssl_force_tls 161
- 7.4.306 ssl_min_dh_prime_bits 162
- 7.4.307 ssl_starttls 162
- 7.4.308 ssl_use_sslv2 162
- 7.4.309 ssl_use_sslv3 162
- 7.4.310 ssl_use_tlsv1 162
- 7.4.311 ssl_usesystemcerts 163
- 7.4.312 status_chars 163
- 7.4.313 status_format 163
- 7.4.314 status_on_top 165
- 7.4.315 strict_mailto 166
- 7.4.316 strict_mime 166
- 7.4.317 strict_threads 166
- 7.4.318 strip_was 166
+ 7.4.266 simple_search 153
+ 7.4.267 sleep_time 153
+ 7.4.268 smart_wrap 154
+ 7.4.269 smileys 154
+ 7.4.270 smime_ask_cert_label 154
+ 7.4.271 smime_ca_location 154
+ 7.4.272 smime_certificates 154
+ 7.4.273 smime_decrypt_command 155
+ 7.4.274 smime_decrypt_use_default_key 155
+ 7.4.275 smime_default_key 155
+ 7.4.276 smime_encrypt_command 156
+ 7.4.277 smime_encrypt_with 156
+ 7.4.278 smime_get_cert_command 156
+ 7.4.279 smime_get_cert_email_command 156
+ 7.4.280 smime_get_signer_cert_command 156
+ 7.4.281 smime_import_cert_command 157
+ 7.4.282 smime_is_default 157
+ 7.4.283 smime_keys 157
+ 7.4.284 smime_pk7out_command 157
+ 7.4.285 smime_sign_command 157
+ 7.4.286 smime_sign_opaque_command 158
+ 7.4.287 smime_timeout 158
+ 7.4.288 smime_verify_command 158
+ 7.4.289 smime_verify_opaque_command 158
+ 7.4.290 smtp_envelope 158
+ 7.4.291 smtp_host 158
+ 7.4.292 smtp_pass 159
+ 7.4.293 smtp_port 159
+ 7.4.294 smtp_use_tls 159
+ 7.4.295 smtp_user 160
+ 7.4.296 sort 160
+ 7.4.297 sort_alias 160
+ 7.4.298 sort_aux 160
+ 7.4.299 sort_browser 161
+ 7.4.300 sort_re 161
+ 7.4.301 spam_separator 162
+ 7.4.302 spoolfile 162
+ 7.4.303 ssl_ca_certificates_file 162
+ 7.4.304 ssl_client_cert 162
+ 7.4.305 ssl_force_tls 162
+ 7.4.306 ssl_min_dh_prime_bits 163
+ 7.4.307 ssl_starttls 163
+ 7.4.308 ssl_use_sslv2 163
+ 7.4.309 ssl_use_sslv3 163
+ 7.4.310 ssl_use_tlsv1 163
+ 7.4.311 ssl_usesystemcerts 164
+ 7.4.312 status_chars 164
+ 7.4.313 status_format 164
+ 7.4.314 status_on_top 166
+ 7.4.315 strict_mailto 167
+ 7.4.316 strict_mime 167
+ 7.4.317 strict_threads 167
+ 7.4.318 strip_was 167
ix
- 7.4.319 strip_was_regex 167
- 7.4.320 stuff_quoted 167
- 7.4.321 suspend 167
- 7.4.322 text_flowed 167
- 7.4.323 thorough_search 167
- 7.4.324 thread_received 168
- 7.4.325 tilde 168
- 7.4.326 timeout 168
- 7.4.327 tmpdir 168
- 7.4.328 to_chars 168
- 7.4.329 trash 169
- 7.4.330 tunnel 169
- 7.4.331 umask 169
- 7.4.332 uncollapse_jump 169
- 7.4.333 use_8bitmime 169
- 7.4.334 use_domain 170
- 7.4.335 use_from 170
- 7.4.336 use_idn 170
- 7.4.337 use_ipv6 170
- 7.4.338 visual 170
- 7.4.339 wait_key 171
- 7.4.340 weed 171
- 7.4.341 wrap_search 171
- 7.4.342 wrapmargin 171
- 7.4.343 write_bcc 171
- 7.4.344 write_inc 172
- 7.4.345 xterm_icon 172
- 7.4.346 xterm_leave 172
- 7.4.347 xterm_set_titles 172
- 7.4.348 xterm_title 172
- 7.5 Functions ....................................................... 173
- 7.5.1 generic 173
- 7.5.2 index 174
- 7.5.3 pager 176
- 7.5.4 alias 178
- 7.5.5 query 178
- 7.5.6 attach 178
- 7.5.7 compose 179
- 7.5.8 postpone 180
- 7.5.9 browser 180
- 7.5.10 pgp 181
- 7.5.11 editor 181
-
- 8. Miscellany ............................................................ 181
- 8.1 Acknowledgments ................................................. 182
- 8.2 About this document ............................................. 184
+ 7.4.319 strip_was_regex 168
+ 7.4.320 stuff_quoted 168
+ 7.4.321 suspend 168
+ 7.4.322 text_flowed 168
+ 7.4.323 thorough_search 168
+ 7.4.324 thread_received 169
+ 7.4.325 tilde 169
+ 7.4.326 timeout 169
+ 7.4.327 tmpdir 169
+ 7.4.328 to_chars 169
+ 7.4.329 trash 170
+ 7.4.330 tunnel 170
+ 7.4.331 umask 170
+ 7.4.332 uncollapse_jump 170
+ 7.4.333 use_8bitmime 170
+ 7.4.334 use_domain 171
+ 7.4.335 use_from 171
+ 7.4.336 use_idn 171
+ 7.4.337 use_ipv6 171
+ 7.4.338 visual 171
+ 7.4.339 wait_key 172
+ 7.4.340 weed 172
+ 7.4.341 wrap_search 172
+ 7.4.342 wrapmargin 172
+ 7.4.343 write_bcc 172
+ 7.4.344 write_inc 173
+ 7.4.345 xterm_icon 173
+ 7.4.346 xterm_leave 173
+ 7.4.347 xterm_set_titles 173
+ 7.4.348 xterm_title 173
+ 7.5 Functions ....................................................... 174
+ 7.5.1 generic 174
+ 7.5.2 index 175
+ 7.5.3 pager 177
+ 7.5.4 alias 179
+ 7.5.5 query 179
+ 7.5.6 attach 179
+ 7.5.7 compose 180
+ 7.5.8 postpone 181
+ 7.5.9 browser 181
+ 7.5.10 pgp 182
+ 7.5.11 editor 182
+
+ 8. Miscellany ............................................................ 182
+ 8.1 Acknowledgments ................................................. 183
+ 8.2 About this document ............................................. 185
x
projects / apps / madmutt.git / commitdiff