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-r394
+ version devel-r392
A\bAb\bbs\bst\btr\bra\bac\bct\bt
+\bo c\bcl\ble\bea\bar\br-\b-f\bfl\bla\bag\bg (default: W)
Furthermore, the following flags reflect who the message is addressed to. They
- can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.322 , page 159) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.323 , page 160) variable.
+
message is to you and you only
_\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 6.4.290 , page 149) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
+ When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 6.4.291 , page 150) 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 6.4.110 , page 105). For example, you could use "%?M?(#%03M)&(%4l)?" in
- _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 105) to optionally display the number of
+ tion 6.4.110 , page 106). For example, you could use "%?M?(#%03M)&(%4l)?" in
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106) to optionally display the number of
hidden messages if the thread is collapsed.
- See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 6.4.311 , page 157).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 6.4.312 , page 158).
_\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
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.3 , page 23) command is added to
- the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 80) variable for
- future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 80) does not
+ the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 81) variable for
+ future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 81) does not
add the aliases specified there-in, you must also _\bs_\bo_\bu_\br_\bc_\be (section 3.28 , page
42) the file.
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.12 ,
page 32) 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 6.4.88 , page 100) configuration variable is set.
+ _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.4.88 , page 101) 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 6.4.200 , page 129), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
- (section 6.4.202 , page 129), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 6.4.201 , page 129) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.334 , page 161) control the exact behavior of this
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.200 , page 130), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 6.4.202 , page 130), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 6.4.201 , page 130) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 162) control the exact behavior of this
function.
r\bre\bes\bse\ben\bnd\bd-\b-m\bme\bes\bss\bsa\bag\bge\be
message. This function is best described as "recall from arbitrary folders".
It can conveniently be used to forward MIME messages while preserving the orig-
inal mail structure. Note that the amount of headers included here depends on
- the value of the _\b$_\bw_\be_\be_\bd (section 6.4.335 , page 162) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 6.4.336 , page 163) variable.
This function is also available from the attachment menu. You can use this to
easily resend a message which was included with a bounce message as a mes-
(default: !)
Asks for an external Unix command and executes it. The _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section
- 6.4.334 , page 161) can be used to control whether Mutt-ng will wait for a key
+ 6.4.335 , page 162) 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 6.4.225 , page 134) variable to
+ The _\bp_\ba_\bg_\be_\br uses the _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.225 , page 135) 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 6.4.307 , page 154) will change to a
+ folder. The %r in _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 155) 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 6.4.54 , page 92).
+ Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 93).
_\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 6.4.192 , page 127) permanently.
+ _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.4.192 , page 128) 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 6.4.179 , page 124)) have obvious meanings. But some explana-
+ _\bm_\ba_\bt (section 6.4.179 , page 125)) 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 6.4.139 ,
- page 113)). Most important is the ``middleman'' capability, indicated by a
+ page 114)). 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 6.4.214 , page 132) variable. This means that you can
+ the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 6.4.214 , page 133) 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 6.4.213 , page 132) quad-option.
+ See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.4.213 , page 133) quad-option.
_\b3_\b. _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn
has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
.muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
- your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 6.3 , page 78) to configure Mutt-ng.
+ your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 6.3 , page 79) to configure Mutt-ng.
_\b3_\b._\b2 _\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 6.3 , page
- 78). Each line of the file may contain one or more commands. When multiple
+ 79). 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-
set record=+sent_on_$HOSTNAME
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 6.3 , page 78).
+ complete list, see the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 6.3 , page 79).
_\b3_\b._\b3 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg_\b/_\bU_\bs_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs
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 6.4.3 , page 80)
+ only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 81)
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
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 6.4.54 , page 92) variable set.
+ (section 6.4.54 , page 93) 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
_\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 6.5 , page 164). The special
+ list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 6.5 , page 165). The special
function noop unbinds the specified key sequence.
_\b3_\b._\b5 _\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
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 6.4.296 , page
- 151) at the beginning of the pattern, you must place it inside of double or
+ N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page
+ 152) 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.
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.4 , page 24). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
- 6.5 , page 164).
+ 6.5 , page 165).
The advantage with using function names directly is that the macros will work
regardless of the current key bindings, so they are not dependent on the user
+\bo normal
- +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.225 , page 134) in the
+ +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.225 , page 135) in the
body of a message)
+\bo quoted1, quoted2, ..., quotedN\bN (higher levels of quoting)
instance, when replying to a message that you sent to a different party, mutt
will automatically suggest to send the response to the original message's
recipients -- responding to yourself won't make much sense in many cases. (See
- _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 6.4.233 , page 136).)
+ _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 6.4.233 , page 137).)
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
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 6.4.66 , page 95)
+ lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.4.66 , page 96)
configuration variable.
More precisely, Mutt-ng maintains lists of patterns for the addresses of known
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
56) (such as ``='' and ``!''), any variable definition that affect these char-
- acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 94) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 6.4.296 , page 151)) should be executed before the mailboxes command.
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 95) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 6.4.297 , page 152)) should be executed before the mailboxes command.
_\b3_\b._\b1_\b5 _\bU_\bs_\be_\br _\bd_\be_\bf_\bi_\bn_\be_\bd _\bh_\be_\ba_\bd_\be_\br_\bs
there, so Mutt-ng enforces the rule.
If you would like to add a header field to a single message, you should either
- set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 92) variable, or use the _\be_\bd_\bi_\bt_\b-
+ set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 93) 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.
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 6.4.15 , page 84), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 143) and
- _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 108) variables in order to change the language
+ _\bt_\bi_\bo_\bn (section 6.4.15 , page 85), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 143) and
+ _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 109) 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
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 6.5 , page 164). ``exec function'' is equivalent
+ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 6.5 , page 165). ``exec function'' is equivalent
to ``push <function>''.
_\b3_\b._\b2_\b5 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bS_\bc_\bo_\br_\bi_\bn_\bg
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 6.4.244 , page 139), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 6.4.245 , page 139),
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 6.4.243 , page 139) 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 6.4.245 , page 139) 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 6.4.243 , page 139) are set to -1, which means that in the default
+ tion 6.4.244 , page 140), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 6.4.245 , page 140),
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 6.4.243 , page 140) 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 6.4.245 , page 140) 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 6.4.243 , page 140) 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
The Mutt Next Generation E-Mail Client 40
- the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 105) variable.
+ the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106) variable.
(Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
given message.)
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 6.4 ,
- page 80). There are four basic types of variables: boolean, number, string and
+ page 81). 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.
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 6.4.99 , page 103),
+ test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.99 , page 104),
use:
ifdef imap_mail_check 'set imap_mail_check = 300'
+\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 6.4.307 , page 154) variable. For the hostname and version
+ _\bm_\ba_\bt (section 6.4.308 , page 155) 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:
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 6.4.16 ,
- page 84) variable is set, the next operation applies to the tagged messages
+ page 85) 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.7 , page 27) or _\bp_\bu_\bs_\bh (section 3.23 , page 37) commands,
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
- 6.4.45 , page 90) variable. The pattern is translated at the time the hook is
- declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.4.45 , page 90) that is in
+ 6.4.45 , page 91) variable. The pattern is translated at the time the hook is
+ declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.4.45 , page 91) 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
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 6.4.125 , page 111)
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.4.125 , page 112)
variable.
m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All messages are
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 6.4.296 , page 151) (incoming)
+ +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page 152) (incoming)
mailbox
- +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 110) file
+ +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 111) file
+\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 136) file
+\bo ~ -- refers to your home directory
- +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 94) directory
+ +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 95) 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.17 , page 35) as
determined by the address of the alias
the first of which is the ability to show the name of a list through which you
received a message (i.e., of a subscribed list) in the _\bi_\bn_\bd_\be_\bx menu display.
This is useful to distinguish between personal and list mail in the same mail-
- box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 105) variable, the escape
+ box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106) variable, the escape
``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
The Mutt Next Generation E-Mail Client 58
Mutt-ng also supports the Mail-Followup-To header. When you send a message to
a list of recipients which includes one or several subscribed mailing lists,
- and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.4.66 , page 95) option is set, mutt will
+ and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.4.66 , page 96) 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 6.4.88 , page 100) configuration variable is set. Using list-reply
+ (section 6.4.88 , page 101) 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
- 6.4.233 , page 136) variable to help decide which address to use. If set to
+ 6.4.233 , page 137) 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 6.4.110 , page 105) variable's ``%y'' and ``%Y''
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106) 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 6.4.290 , page 149) the mail-
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 6.4.291 , page 150) 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
RFC1894 defines a set of MIME content types for relaying information about the
status of electronic mail messages. These can be thought of as ``return
- receipts.'' Berkeley sendmail 8.8.x currently has some command line options in
- which the mail client can make requests as to what type of status messages
- should be returned.
+ receipts.''
- To support this, there are two variables. _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 6.4.51 , page
- 91) is used to request receipts for different results (such as failed message,
- message delivered, etc.). _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 6.4.52 , page 92) requests how
- much of your message should be returned with the receipt (headers or full mes-
- sage). Refer to the man page on sendmail for more details on DSN.
+ Users can make use of it in one of the following two ways:
- _\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)
+ +\bo Berkeley sendmail 8.8.x currently has some command line options in which
+ the mail client can make requests as to what type of status messages
+ should be returned.
- If Mutt-ng was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+ +\bo The SMTP support via libESMTP supports it, too.
+
+ To support this, there are two variables:
+
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 6.4.51 , page 92) is used to request receipts for
+ different results (such as failed message, message delivered, etc.).
The Mutt Next Generation E-Mail Client 60
+ +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 6.4.52 , page 93) 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)
+
+ 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 6.4.208 , page 131) variable, which defaults
+ by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.208 , page 132) 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 6.4.206 , page 130), fetch all your
- new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.296 , page 151).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.206 , page 131), fetch all your
+ new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page 152).
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 61
+
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 _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This
-
- The Mutt Next Generation E-Mail Client 61
-
- naturally requires that the server supports SSL encrypted connections. To
- access a folder with IMAP/SSL, you should use imaps://[user-
+ the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This natu-
+ rally requires that the server supports SSL encrypted connections. To access a
+ folder with IMAP/SSL, you should use imaps://[user-
name@]imapserver[:port]/path/to/folder as your folder path.
Pine-compatible notation is also supported, i.e. {[user-
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 6.4.97 , page 102) vari-
+ 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 6.4.97 , page 103) vari-
able.
Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
- want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.99 , page 103) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.320 , page 159) variables.
+ want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.99 , page 104) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.321 , page 160) 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 62
+
_\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,
To use ANONYMOUS, simply make your username blank or "anonymous".
SASL is a special super-authenticator, which selects among several protocols
-
- The Mutt Next Generation E-Mail Client 62
-
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
available on your host and the server. Using some of these methods (including
DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
There are a few variables which control authentication:
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 6.4.105 , page 104) - controls the username under
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 6.4.105 , page 105) - 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 6.4.100 , page 103) - a password which you may pre-
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.100 , page 104) - 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 6.4.91 , page 101) - 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 6.4.91 , page 102) - 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).
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 63
+
to use a killfile has been discussed in _\bM_\be_\bs_\bs_\ba_\bg_\be _\bs_\bc_\bo_\br_\bi_\bn_\bg (section 3.25 , page
38).
In mutt-ng this is as easy as
- The Mutt Next Generation E-Mail Client 63
-
score ~* =42
This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
functionality. When configure was called with --with-libesmtp or the output
- muttng -v contains +USE_LIBESMTP, this will be or is the case already.
+ 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 58) 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 6.4.328 , page 161).
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 6.4.285 , page 148)
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.286 , page 149)
variable pointing to your SMTP server.
- Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 6.4.289 ,
- page 149) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.286 , page 148) variables.
+ The Mutt Next Generation E-Mail Client 64
+
+ Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 6.4.290 ,
+ page 150) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.287 , page 149) 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 6.4.288 , page 149) variable must be either set to
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 6.4.289 , page 150) 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.
+ 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 6.4.285 ,
+ page 149) 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)
If you happen to have accounts on multiple IMAP and/or POP servers, you may
find managing all the authentication settings inconvenient and error-prone.
-
- The Mutt Next Generation E-Mail Client 64
-
The account-hook command may help. This hook works like folder-hook but is
invoked whenever you access a remote mailbox (including inside the folder
browser), not just when you open the mailbox.
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 65
+
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
close-hook \\.gz$ "gzip -c %t > %f"
append-hook \\.gz$ "gzip -c %t >> %f"
- The Mutt Next Generation E-Mail Client 65
-
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 65), 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 65) (or give
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 6.4.240 , page 138), so that the compressed file
+ unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 6.4.240 , page 139), 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 66
+
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.
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.
- The Mutt Next Generation E-Mail Client 66
-
Example:
close-hook \\.gz$ "gzip -c %t > %f"
When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65) is used, the folder is not opened,
which saves time, but this means that we can not find out what the folder type
- is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.4.125 , page 111)) type is always
+ is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.4.125 , page 112)) type is always
+
+ The Mutt Next Generation E-Mail Client 67
+
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 ,
open-hook \\.pgp$ "pgp -f < %f > %t"
close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
- The Mutt Next Generation E-Mail Client 67
-
Please note, that PGP does not support appending to an encrypted folder, so
there is no append-hook defined.
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 68
+
variety of PGP MIME types, including PGP/MIME and application/pgp.
Mutt-ng will denote attachments with a couple lines describing them. These
The default binding for view-attachments is `v', which displays the attachment
menu for a message. The attachment menu displays a list of the attachments in
-
- The Mutt Next Generation E-Mail Client 68
-
a message. From the attachment menu, you can save, print, pipe, delete, and
view attachments. You can apply these operations to a group of attachments at
once, by tagging the attachments and by using the ``tag-prefix'' operator. You
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 69
+
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
application/pgp pgp
audio/x-aiff aif aifc aiff
- The Mutt Next Generation E-Mail Client 69
-
A sample mime.types file comes with the Mutt-ng distribution, and should con-
tain most of the MIME types you are likely to use.
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 70
+
handler. The default search string for these files is a colon delimited list
set to
optional fields. Each field of a definition line is divided by a semicolon ';'
character.
- The Mutt Next Generation E-Mail Client 70
-
The content type is specified in the MIME standard type/subtype method. For
example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
mat includes two formats for wildcards, one using the special '*' subtype, the
text/html; lynx %s
+ The Mutt Next Generation E-Mail Client 71
+
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
This is the simplest form of a mailcap file.
- The Mutt Next Generation E-Mail Client 71
-
_\b5_\b._\b3_\b._\b2 _\bS_\be_\bc_\bu_\br_\be _\bu_\bs_\be _\bo_\bf _\bm_\ba_\bi_\bl_\bc_\ba_\bp
The interpretation of shell meta-characters embedded in MIME parameters can
lead to security problems in general. Mutt-ng tries to quote parameters in
expansion of %s syntaxes properly, and avoids risky characters by substituting
- them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 6.4.117 , page 109) variable.
+ them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 6.4.117 , page 110) 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 72
+
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:
and Mutt-ng will use your standard pager to display the results.
needsterminal
- Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw
-
- The Mutt Next Generation E-Mail Client 72
-
- (section 5.4 , page 74), in order to decide whether it should
- honor the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.334 , page 161)
- variable or not. When an attachment is viewed using an interactive
- program, and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl
- flag, Mutt-ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.334 , page 161) 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.
+ Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
+ tion 5.4 , page 74), in order to decide whether it should honor
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 162) variable
+ or not. When an attachment is viewed using an interactive program,
+ and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt-
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 162) and the exit
+ status of the program to decide if it will ask you to press a key
+ after the external program has exited. In all other situations it
+ will not prompt you for a key.
compose=<command>
This flag specifies the command to use to create a new attachment
it to compose new attachments. Mutt-ng will default to the defined
editor for text attachments.
+ The Mutt Next Generation E-Mail Client 73
+
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; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s
- The Mutt Next Generation E-Mail Client 73
-
In this example, Mutt-ng will run the program RunningX which will
return 0 if the X Window manager is running, and non-zero if it
isn't. If RunningX returns 0, then Mutt-ng will call netscape to
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s; nametemplate=%s.html
+
+ The Mutt Next Generation E-Mail Client 74
+
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 74), Mutt-ng will choose the third entry
use of this keyword causes Mutt-ng to not pass the body of the mes-
sage to the view/print/edit program on stdin.
- The Mutt Next Generation E-Mail Client 74
-
%t
Mutt-ng will expand %t to the text representation of the content
type of the message in the same form as the first parameter of the
This mailcap file is fairly simple and standard:
+ The Mutt Next Generation E-Mail Client 75
+
# 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 75
-
# 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 view-
- ing MIME attachments while in the pager.
+ viewer defined in the mailcap file, Mutt-ng has support for automatically
+
+ The Mutt Next Generation E-Mail Client 76
+
+ viewing MIME attachments while in the pager.
To work, you must define a viewer in the mailcap file which uses the copi-
ousoutput option to denote that it is non-interactive. Usually, you also use
For instance, if you set auto_view to:
- The Mutt Next Generation E-Mail Client 76
-
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-
_\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 77
+
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 77
-
any particular mime-type if it had been set, for example, in a global muttrc.
_\b6_\b. _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be
To read messages in a mailbox
+ The Mutt Next Generation E-Mail Client 78
+
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
mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
- The Mutt Next Generation E-Mail Client 78
-
This command will send a message to ``professor@bigschool.edu'' with a subject
of ``data set for run #2''. In the body of the message will be the contents of
the file ``~/run2.dat''.
_\b6_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
+ The Mutt Next Generation E-Mail Client 79
+
~A all messages
~b EXPR messages which contain EXPR in the message body
~B EXPR messages which contain EXPR in the whole message
address (excluded are addresses matching against
alternates or any alias)
- The Mutt Next Generation E-Mail Client 79
-
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
44). Special attention has to be made when using regular expressions inside of
patterns. Specifically, Mutt-ng's parser for these patterns will strip one
intention to use a backslash in the regular expression, you will need to use
two backslashes instead (\\).
+ The Mutt Next Generation E-Mail Client 80
+
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
_\b6_\b._\b3 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bC_\bo_\bm_\bm_\ba_\bn_\bd_\bs
+\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 26) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- The Mutt Next Generation E-Mail Client 80
-
+\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 35) _\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.16 , page 35) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.9 , page 30) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ The Mutt Next Generation E-Mail Client 81
+
+\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.9 , page 30) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+\bo _\bl_\bi_\bs_\bt_\bs (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bs_\be_\bt (section 3.27 , page 41) [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- The Mutt Next Generation E-Mail Client 81
-
+\bo _\bu_\bn_\bs_\be_\bt (section 3.27 , page 41) _\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.28 , page 42) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.26 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn
+ The Mutt Next Generation E-Mail Client 82
+
+\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 32) _\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.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
Type: string
- The Mutt Next Generation E-Mail Client 82
-
Default: '%4n %2f %t %-10a %r'
Specifies the format of the data displayed for the ``alias'' menu. The follow-
%a
alias name
+ The Mutt Next Generation E-Mail Client 83
+
%f
flags - currently, a 'd' for an alias marked for deletion
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 83
-
_\b6_\b._\b4_\b._\b8 _\ba_\bs_\bc_\bi_\bi_\b__\bc_\bh_\ba_\br_\bs
Type: boolean
If _\bs_\be_\bt, Mutt-ng will use plain ASCII characters when displaying thread and
attachment trees, instead of the default ACS characters.
+ The Mutt Next Generation E-Mail Client 84
+
_\b6_\b._\b4_\b._\b9 _\ba_\bs_\bk_\bb_\bc_\bc
Type: boolean
set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
However, only the first content is valid for the message body. This variable
- is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 6.4.310 , page 156) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 6.4.311 , page 158) is unset.
_\b6_\b._\b4_\b._\b1_\b2 _\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 84
-
%C
charset
%D
deleted flag
+ The Mutt Next Generation E-Mail Client 85
+
%d
description
Default: '\n'
- The Mutt Next Generation E-Mail Client 85
-
The separator to add between attachments when operating (saving, printing, pip-
ing, etc) on a list of tagged attachments.
Default: yes
+ The Mutt Next Generation E-Mail Client 86
+
If this variable is _\bu_\bn_\bs_\be_\bt, when operating (saving, printing, piping, etc) on a
list of tagged attachments, Mutt-ng will concatenate the attachments and will
operate on them as a single attachment. The ``_\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp (section 6.4.13 ,
- page 83)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
+ page 84)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
operate on the attachments one by one.
_\b6_\b._\b4_\b._\b1_\b5 _\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 6.4.110 , page 105)''.
+ on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)''.
_\b6_\b._\b4_\b._\b1_\b6 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
Default: no
- When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 92)'', Mutt-ng will
+ When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 93)'', 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 finished
editing the body of your message.
- Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 6.4.60 , page 93)''.
+ Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 6.4.60 , page 94)''.
_\b6_\b._\b4_\b._\b1_\b8 _\bb_\be_\be_\bp
Default: yes
- The Mutt Next Generation E-Mail Client 86
-
When this variable is _\bs_\be_\bt, Mutt-ng will beep when an error occurs.
_\b6_\b._\b4_\b._\b1_\b9 _\bb_\be_\be_\bp_\b__\bn_\be_\bw
Default: no
+ The Mutt Next Generation E-Mail Client 87
+
When this variable is _\bs_\be_\bt, Mutt-ng will beep whenever it prints a message noti-
fying you of new mail. This is independent of the setting of the ``_\b$_\bb_\be_\be_\bp (sec-
- tion 6.4.18 , page 84)'' variable.
+ tion 6.4.18 , page 85)'' variable.
_\b6_\b._\b4_\b._\b2_\b0 _\bb_\bo_\bu_\bn_\bc_\be
This variable specifies the file where the certificates you trust are saved.
When an unknown certificate is encountered, you are asked if you accept it or
-
- The Mutt Next Generation E-Mail Client 87
-
not. If you accept it, the certificate can also be saved in this file and fur-
ther connections are automatically accepted.
Example: set certificate_file=~/.muttng/certificates
+ The Mutt Next Generation E-Mail Client 88
+
_\b6_\b._\b4_\b._\b2_\b4 _\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
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 6.4.307 , page 154)'', but has
+ string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 155)'', but has
its own set of printf(3)-like sequences:
%a
total number of attachments
- The Mutt Next Generation E-Mail Client 88
-
%h
local hostname
%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 6.4.307 , page 154)''
+ See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 155)''
+
+ The Mutt Next Generation E-Mail Client 89
+
option for more information on how to set ``_\b$_\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.27 ,
- page 86)''.
+ page 87)''.
_\b6_\b._\b4_\b._\b2_\b8 _\bc_\bo_\bn_\bf_\bi_\bg_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Default: 'text/plain'
- The Mutt Next Generation E-Mail Client 89
-
Sets the default Content-Type: header field for the body of newly composed mes-
sages.
Default: yes
+ The Mutt Next Generation E-Mail Client 90
+
This variable controls whether or not copies of your outgoing messages will be
saved for later references. Also see ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page
- 136)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 138)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
- 6.4.68 , page 96)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 35)''.
+ 136)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 139)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 6.4.68 , page 97)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 35)''.
_\b6_\b._\b4_\b._\b3_\b4 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt
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
- 6.4.34 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 89)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 6.4.39 , page 89)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
+ 6.4.34 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 90)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 6.4.39 , page 90)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
_\b6_\b._\b4_\b._\b3_\b6 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
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)
- The Mutt Next Generation E-Mail Client 90
-
_\b6_\b._\b4_\b._\b3_\b7 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bm_\bi_\bm_\be
Type: boolean
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
- 6.4.34 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 89)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 6.4.39 , page 89)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
+ 6.4.34 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 90)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+
+ The Mutt Next Generation E-Mail Client 91
+
+ 6.4.39 , page 90)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
_\b6_\b._\b4_\b._\b3_\b8 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt
If _\bs_\be_\bt, automatically PGP or OpenSSL 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
- 6.4.38 , page 89)'', because it allows you to sign all messages which are
+ 6.4.38 , page 90)'', because it allows you to sign all messages which are
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 6.4.39 , page 89)'', that Mutt-ng is not able to
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section 6.4.39 , page 90)'', that Mutt-ng is not able to
find out whether an encrypted message is also signed. (Crypto only)
_\b6_\b._\b4_\b._\b4_\b1 _\bc_\br_\by_\bp_\bt_\b__\bt_\bi_\bm_\be_\bs_\bt_\ba_\bm_\bp
If _\bs_\be_\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
S/MIME output, so spoofing such lines is more difficult. If you are using col-
ors to mark these lines, and rely on these, you may _\bu_\bn_\bs_\be_\bt this setting.
-
- The Mutt Next Generation E-Mail Client 91
-
(Crypto only)
_\b6_\b._\b4_\b._\b4_\b2 _\bc_\br_\by_\bp_\bt_\b__\bu_\bs_\be_\b__\bg_\bp_\bg_\bm_\be
This variable controls the use the GPGME enabled crypto backends. If it is _\bs_\be_\bt
and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
+
+ The Mutt Next Generation E-Mail Client 92
+
will be used instead of the classic code.
N\bNo\bot\bte\be: You need to use this option in your .muttngrc configuration file as it
Default: '!%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 6.4.110 , page 105)''. This is passed to strftime(3)
+ ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)''. 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 6.4.114 , page 108)''. If the first character in the string
+ ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 109)''. 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).
hook is declared. The default value matches if the message is either from a
user matching the regular expression given, or if it is from you (if the from
address matches ``alternates'') and is to or cc'ed to a user matching the given
-
- The Mutt Next Generation E-Mail Client 92
-
regular expression.
_\b6_\b._\b4_\b._\b4_\b6 _\bd_\be_\bl_\be_\bt_\be
Controls whether or not messages are really deleted when closing or synchroniz-
ing a mailbox. If set to _\by_\be_\bs, messages marked for deleting will automatically
+
+ The Mutt Next Generation E-Mail Client 93
+
be purged without prompting. If set to _\bn_\bo, messages marked for deletion will
be kept in the mailbox.
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 6.4.49 ,
- page 91), and the filtered message is read from the standard output.
+ page 92), and the filtered message is read from the standard output.
_\b6_\b._\b4_\b._\b5_\b0 _\bd_\bo_\bt_\bl_\bo_\bc_\bk_\b__\bp_\br_\bo_\bg_\br_\ba_\bm
Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
- The Mutt Next Generation E-Mail Client 93
-
_\b6_\b._\b4_\b._\b5_\b1 _\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by
Type: string
Default: ''
- N\bNo\bot\bte\be:\b: you should not enable this unless you are using Sendmail 8.8.x or
- greater.
+ N\bNo\bot\bte\be:\b: you should not enable this unless you are using Sendmail 8.8.x or greater
+ or in connection with the SMTP support via libESMTP.
This variable sets the request for when notification is returned. The string
- consists of a comma separated list (no spaces!) of one or more of the follow-
- ing: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notification on
- transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs, to be
- notified of successful transmission.
+ consists of a comma separated list (no spaces!) of one or more of the
+
+ The Mutt Next Generation E-Mail Client 94
+
+ following: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notifica-
+ tion on transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs,
+ to be notified of successful transmission.
Example: set dsn_notify='failure,delay'
Default: ''
- N\bNo\bot\bte\be:\b: you should not enable this unless you are using Sendmail 8.8.x or
- greater.
+ N\bNo\bot\bte\be:\b: you should not enable this unless you are using Sendmail 8.8.x or greater
+ or in connection with the SMTP support via libESMTP.
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
_\b6_\b._\b4_\b._\b5_\b5 _\be_\bd_\bi_\bt_\bo_\br
- The Mutt Next Generation E-Mail Client 94
-
Type: path
Default: ''
Type: boolean
+ The Mutt Next Generation E-Mail Client 95
+
Default: no
When _\bs_\be_\bt, Mutt-ng will quoted-printable encode messages when they contain the
Type: boolean
- The Mutt Next Generation E-Mail Client 95
-
Default: no
When _\bs_\be_\bt, the initial prompt for recipients and subject are skipped when reply-
messages.
N\bNo\bot\bte\be:\b: this variable has no effect when the ``_\b$_\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt (section 6.4.17 , page
- 84)'' variable is _\bs_\be_\bt.
+ 85)'' variable is _\bs_\be_\bt.
_\b6_\b._\b4_\b._\b6_\b1 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
Type: boolean
+ The Mutt Next Generation E-Mail Client 96
+
Default: yes
This variable controls whether or not attachments on outgoing messages are
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 6.4.24 , page 86) value will
+ file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 6.4.24 , page 87) value will
be used instead. For example, the following configuration would work for
Japanese text handling:
that the assignment occurs _\bb_\be_\bf_\bo_\br_\be you use ``+'' or ``='' for any other vari-
ables since expansion takes place during the ``set'' command.
- The Mutt Next Generation E-Mail Client 96
-
_\b6_\b._\b4_\b._\b6_\b5 _\bf_\bo_\bl_\bd_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
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 6.4.110 , page
- 105)'', but has its own set of printf(3)-like sequences:
+ 106)'', but has its own set of printf(3)-like sequences:
%C
current file number
+ The Mutt Next Generation E-Mail Client 97
+
%d
date/time folder was last modified
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
-
- The Mutt Next Generation E-Mail Client 97
-
to a known mailing list, specified with the ``subscribe'' or ``_\bl_\bi_\bs_\bt_\bs (section
3.12 , page 32)'' commands or detected by common mailing list headers.
a subscribed list will be sent to both the list and your address, resulting in
two copies of the same email for you.
+ The Mutt Next Generation E-Mail Client 98
+
_\b6_\b._\b4_\b._\b6_\b7 _\bf_\bo_\br_\bc_\be_\b__\bb_\bu_\bf_\bf_\by_\b__\bc_\bh_\be_\bc_\bk
Type: boolean
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.
- Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.320 , page 159)'',
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.321 , page 160)'',
``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.115 , page 109)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 6.4.99 , page 103)''.
+ 6.4.99 , page 104)''.
_\b6_\b._\b4_\b._\b6_\b8 _\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 6.4.241 , page 138)'',
+ This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 139)'',
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.
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 6.4.136 , page 113)'' 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 6.4.137 , page 113)'' is used instead.
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.137 , page 114)'' is used instead.
_\b6_\b._\b4_\b._\b7_\b0 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
Default: yes
- The Mutt Next Generation E-Mail Client 98
-
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 6.4.136 , page 113)'' 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 6.4.137 , page 113)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.137 , page 114)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
_\b6_\b._\b4_\b._\b7_\b1 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
Default: yes
+ The Mutt Next Generation E-Mail Client 99
+
This quadoption controls whether or not the user is automatically placed in the
editor when forwarding messages. For those who always want to forward with no
modification, use a setting of _\bn_\bo.
This variable controls the default subject when forwarding a message. It uses
the same format sequences as the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page
- 105)'' variable.
+ 106)'' variable.
_\b6_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
When _\bs_\be_\bt forwarded messages included in the main body of the message (when
``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 113)'' 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 6.4.109 , page 105)''.
+ ``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.4.109 , page 106)''.
_\b6_\b._\b4_\b._\b7_\b4 _\bf_\br_\bo_\bm
This variable contains a default from address. It can be overridden using
my_hdr (including from send-hooks) and ``_\b$_\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 6.4.236 , page
- 137)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 6.4.329 , page
- 160)'' is unset.
+ 138)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 6.4.330 , page
+ 162)'' 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
_\b6_\b._\b4_\b._\b7_\b5 _\bg_\be_\bc_\bo_\bs_\b__\bm_\ba_\bs_\bk
- The Mutt Next Generation E-Mail Client 99
-
Type: regular expression
Default: '^[^,]*'
do: set gecos_mask='.*'.
This can be useful if you see the following behavior: you address a e-mail to
+
+ The Mutt Next Generation E-Mail Client 100
+
user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
expression that will match the whole name so Mutt-ng will expand ``Franklin''
Default: no
When _\bs_\be_\bt, this variable causes Mutt-ng to include the header of the message you
- are replying to into the edit buffer. The ``_\b$_\bw_\be_\be_\bd (section 6.4.335 , page
- 162)'' setting applies.
+ are replying to into the edit buffer. The ``_\b$_\bw_\be_\be_\bd (section 6.4.336 , page
+ 163)'' setting applies.
_\b6_\b._\b4_\b._\b7_\b8 _\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 6.4.78 , page 98) variable points to the header
+ The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 6.4.78 , page 99) variable points to the header
cache database.
- If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 6.4.78 , page 98) points to a directory it will con-
+ If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 6.4.78 , page 99) points to a directory it will con-
tain a header cache database per folder. If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 6.4.78 ,
- page 98) points to a file that file will be a single global header cache. By
+ page 99) 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.
- The Mutt Next Generation E-Mail Client 100
-
_\b6_\b._\b4_\b._\b7_\b9 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bc_\bo_\bm_\bp_\br_\be_\bs_\bs
Type: boolean
_\b6_\b._\b4_\b._\b8_\b0 _\bh_\be_\bl_\bp
+ The Mutt Next Generation E-Mail Client 101
+
Type: boolean
Default: yes
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
- 6.4.89 , page 100)'' variable when adding the domain part to addresses. This
+ 6.4.89 , page 101)'' 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 missing messages in the thread
tree.
- The Mutt Next Generation E-Mail Client 101
-
_\b6_\b._\b4_\b._\b8_\b4 _\bh_\bi_\bd_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
Type: boolean
Type: boolean
+ The Mutt Next Generation E-Mail Client 102
+
Default: no
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 6.4.83 , page 99) is set, this option will have no effect.
+ _\bi_\bn_\bg (section 6.4.83 , page 100) is set, this option will have no effect.
_\b6_\b._\b4_\b._\b8_\b6 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
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 6.4.82 ,
- page 99) is _\bs_\be_\bt, this option will have no effect.
+ page 100) is _\bs_\be_\bt, this option will have no effect.
_\b6_\b._\b4_\b._\b8_\b7 _\bh_\bi_\bs_\bt_\bo_\br_\by
Default: ''
Specifies the hostname to use after the ``@'' in local e-mail addresses and
-
- The Mutt Next Generation E-Mail Client 102
-
during generation of Message-Id: headers.
Please be sure to really know what you are doing when changing this variable to
Affects the behaviour of the _\br_\be_\bp_\bl_\by function when replying to messages from
mailing lists. When _\bs_\be_\bt, if the ``Reply-To:'' header field is set to the same
+
+ The Mutt Next Generation E-Mail Client 103
+
value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
header field was set by the mailing list to automate responses to the list, and
will ignore this field. To direct a response to the mailing list when this
_\b6_\b._\b4_\b._\b9_\b3 _\bi_\bm_\ba_\bp_\b__\bd_\be_\bl_\bi_\bm_\b__\bc_\bh_\ba_\br_\bs
- The Mutt Next Generation E-Mail Client 103
-
Type: string
Default: '/.'
This contains the list of characters which you would like to treat as folder
separators for displaying IMAP paths. In particular it helps in using the '='
- shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 94) variable.
+ shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 95) variable.
_\b6_\b._\b4_\b._\b9_\b4 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
Type: string
+ The Mutt Next Generation E-Mail Client 104
+
Default: ''
Availability: IMAP
violated every now and then.
Reduce this number if you find yourself getting disconnected from your IMAP
-
- The Mutt Next Generation E-Mail Client 104
-
server due to inactivity.
_\b6_\b._\b4_\b._\b9_\b7 _\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
scribed folders or all folders. This can be toggled in the IMAP browser with
the _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd function.
+ The Mutt Next Generation E-Mail Client 105
+
_\b6_\b._\b4_\b._\b9_\b8 _\bi_\bm_\ba_\bp_\b__\bl_\bo_\bg_\bi_\bn
Type: string
Your login name on the IMAP server.
This variable defaults to the value of ``_\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 6.4.105 , page
- 104).''
+ 105).''
_\b6_\b._\b4_\b._\b9_\b9 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
machine, because the superuser can read your configuration even if you are the
only one who can read the file.
- The Mutt Next Generation E-Mail Client 105
-
_\b6_\b._\b4_\b._\b1_\b0_\b1 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs_\bi_\bv_\be
Type: boolean
_\b6_\b._\b4_\b._\b1_\b0_\b2 _\bi_\bm_\ba_\bp_\b__\bp_\be_\be_\bk
+ The Mutt Next Generation E-Mail Client 106
+
Type: boolean
Default: yes
Type: string
- The Mutt Next Generation E-Mail Client 106
-
Default: ''
Availability: IMAP
Default: no
If _\bs_\be_\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
+
+ The Mutt Next Generation E-Mail Client 107
+
set for _\be_\bv_\be_\br_\by MIME attachment it doesn't have an internal viewer defined for.
If such an entry is found, Mutt-ng will use the viewer defined in that entry to
convert the body part to text form.
Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
- This variable allows you to customize the message index display to your
-
- The Mutt Next Generation E-Mail Client 107
-
- personal taste.
+ This variable allows you to customize the message index display to your per-
+ sonal taste.
``Format strings'' are similar to the strings used in the ``C'' function
printf(3) to format output (see the man page for more detail). The following
%b
filename of the original message folder (think mailBox)
+ The Mutt Next Generation E-Mail Client 108
+
%B
the list to which the letter was sent, or else the folder name
(%b).
%i
message-id of the current message
- The Mutt Next Generation E-Mail Client 108
-
%l
number of lines in the message (does not work with maildir, mh, and
possibly IMAP folders)
%M
number of hidden messages if the thread is collapsed.
+ The Mutt Next Generation E-Mail Client 109
+
%N
message score
`to:' field (recipients)
%T
- the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.322 ,
- page 159) string
+ the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.323 ,
+ page 160) string
%u
user (login) name of the author
%Y
`x-label' field, if present, and (1) not at part of a thread tree,
- (2) at the top of a thread, or (3) `x-label' is different from
-
- The Mutt Next Generation E-Mail Client 109
-
- preceding message's `x-label'.
+ (2) at the top of a thread, or (3) `x-label' is different from pre-
+ ceding message's `x-label'.
%Z
message status flags
zone, and ``fmt'' is expanded by the library function ``strftime'';
a leading bang disables locales
+ The Mutt Next Generation E-Mail Client 110
+
%(fmt)
the local date and time when the message was received. ``fmt'' is
expanded by the library function ``strftime''; a leading bang dis-
%|X
pad to the end of the line with character 'X'
- See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.322 , page 159)''.
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.323 , page 160)''.
_\b6_\b._\b4_\b._\b1_\b1_\b1 _\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 6.4.124 , page 110)'' mailbox, or as a result of
+ box to your ``_\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 111)'' mailbox, or as a result of
a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 33)'' command.
_\b6_\b._\b4_\b._\b1_\b1_\b3 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
Type: quadoption
- The Mutt Next Generation E-Mail Client 110
-
Default: no
When _\bs_\be_\bt, address replies to the mailing list the original message came from
The locale used by strftime(3) to format dates. Legal values are the strings
your system accepts for the locale variable LC_TIME.
+ The Mutt Next Generation E-Mail Client 111
+
_\b6_\b._\b4_\b._\b1_\b1_\b5 _\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
mail.
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
- 6.4.99 , page 103).
+ 6.4.99 , page 104).
_\b6_\b._\b4_\b._\b1_\b1_\b6 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
Default: yes
- The Mutt Next Generation E-Mail Client 111
-
Availability: Header Cache
Check for Maildir unaware programs other than Mutt-ng having modified maildir
If _\bs_\be_\bt, messages marked as deleted will be saved with the maildir (T)rashed
flag instead of physically deleted.
+ The Mutt Next Generation E-Mail Client 112
+
N\bNO\bOT\bTE\bE:\b: this only applies to maildir-style mailboxes. Setting it will have no
effect on other mailbox types.
operator ``!''. Only files whose names match this mask will be shown. The
match is always case-sensitive.
- The Mutt Next Generation E-Mail Client 112
-
_\b6_\b._\b4_\b._\b1_\b2_\b3 _\bm_\ba_\bx_\b__\bl_\bi_\bn_\be_\b__\bl_\be_\bn_\bg_\bt_\bh
Type: number
When _\bs_\be_\bt, the maximum line length for displaying ``format = flowed'' messages
is limited to this length. A value of 0 (which is also the default) means that
the maximum line length is determined by the terminal width and _\b$_\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
- (section 6.4.337 , page 162).
+ (section 6.4.338 , page 163).
_\b6_\b._\b4_\b._\b1_\b2_\b4 _\bm_\bb_\bo_\bx
Default: '~/mbox'
+ The Mutt Next Generation E-Mail Client 113
+
This specifies the folder into which read mail in your ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 6.4.296 , page 151)'' folder will be appended.
+ 6.4.297 , page 152)'' folder will be appended.
_\b6_\b._\b4_\b._\b1_\b2_\b5 _\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 6.4.167 , page
- 121)''.)
+ 122)''.)
_\b6_\b._\b4_\b._\b1_\b2_\b7 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
Default: no
- The Mutt Next Generation E-Mail Client 113
-
When _\bs_\be_\bt, menus will be scrolled up or down one line when you attempt to move
across a screen boundary. If _\bu_\bn_\bs_\be_\bt, the screen is cleared and the next or pre-
vious page of the menu is displayed (useful for slow links to avoid many
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 6.4.110 , page 105)''.
+ section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)''.
+
+ The Mutt Next Generation E-Mail Client 114
_\b6_\b._\b4_\b._\b1_\b3_\b0 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
The name of the MH sequence used for flagged messages.
- The Mutt Next Generation E-Mail Client 114
-
_\b6_\b._\b4_\b._\b1_\b3_\b4 _\bm_\bh_\b__\bs_\be_\bq_\b__\br_\be_\bp_\bl_\bi_\be_\bd
Type: string
Default: 'unseen'
+ The Mutt Next Generation E-Mail Client 115
+
The name of the MH sequence used for unseen messages.
_\b6_\b._\b4_\b._\b1_\b3_\b6 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd
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 6.4.69 , page 96)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
- _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.137 , page 113)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.69 , page 97)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.137 , page 114)''.
_\b6_\b._\b4_\b._\b1_\b3_\b7 _\bm_\bi_\bm_\be_\b__\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 while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 113)'' is _\bs_\be_\bt. Other-
- wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.69 , page 96)'' is used instead.
+ wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.69 , page 97)'' is used instead.
_\b6_\b._\b4_\b._\b1_\b3_\b8 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\br_\be_\bs_\bt
_\b6_\b._\b4_\b._\b1_\b3_\b9 _\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
- The Mutt Next Generation E-Mail Client 115
-
Type: string
Default: '%4n %c %-16s %a'
%c
Remailer capabilities.
+ The Mutt Next Generation E-Mail Client 116
+
%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 6.4.124 , page 110)'' mailbox, or as a result of a
+ to your ``_\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 111)'' mailbox, or as a result of a
``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 33)'' command.
_\b6_\b._\b4_\b._\b1_\b4_\b2 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
generated. The '%' character marks that certain data will be added to the
string, similar to printf(3). The following characters are allowed:
- The Mutt Next Generation E-Mail Client 116
-
%d
the current day of month
%O
the current UNIX timestamp (octal)
+ The Mutt Next Generation E-Mail Client 117
+
%p
the process ID
This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
threads to fit on the screen.
- The Mutt Next Generation E-Mail Client 117
-
_\b6_\b._\b4_\b._\b1_\b4_\b4 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
Type: boolean
Type: boolean
+ The Mutt Next Generation E-Mail Client 118
+
Default: no
Availability: NNTP
Default: 1000
- The Mutt Next Generation E-Mail Client 118
-
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 6.4.146 , page 116)) and how
+ caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 6.4.146 , page 117)) 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 6.4.148 ,
- page 116), all older ones will be removed/not shown in the index.
+ page 117), all older ones will be removed/not shown in the index.
_\b6_\b._\b4_\b._\b1_\b4_\b9 _\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 119
+
Availability: NNTP
If this variable is _\bs_\be_\bt and the keyword 'poster' is present in the Followup-To:
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 6.4.110 ,
- page 105)'', but has its own set of printf(3)-like sequences:
+ page 106)'', but has its own set of printf(3)-like sequences:
%C current newsgroup number
%d description of newsgroup (retrieved from server)
This variable specifies the name (or address) of the NNTP server to be used.
- The Mutt Next Generation E-Mail Client 119
-
It defaults to the value specified via the environment variable $NNTPSERVER or
contained in the file /etc/nntpserver.
_\b6_\b._\b4_\b._\b1_\b5_\b2 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
+ The Mutt Next Generation E-Mail Client 120
+
Type: path
Default: ''
article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
each operation in index (stepping, read article, etc.).
- The Mutt Next Generation E-Mail Client 120
-
_\b6_\b._\b4_\b._\b1_\b5_\b5 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
Type: boolean
_\b6_\b._\b4_\b._\b1_\b5_\b6 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
+ The Mutt Next Generation E-Mail Client 121
+
Type: path
Default: '~/.newsrc'
If set to _\by_\be_\bs, Mutt-ng will post articles to newsgroup that have not permis-
sions to post (e.g. moderated).
- The Mutt Next Generation E-Mail Client 121
-
N\bNo\bot\bte\be:\b: if the newsserver does not support posting to that newsgroup or a group
is totally read-only, that posting will not have any effect.
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 122
+
_\b6_\b._\b4_\b._\b1_\b6_\b0 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
Type: boolean
Default: ''
- The Mutt Next Generation E-Mail Client 122
-
Availability: NNTP
Your login name on the NNTP server. If _\bu_\bn_\bs_\be_\bt and the server requires authen-
Availability: NNTP
+ The Mutt Next Generation E-Mail Client 123
+
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.
will display the line after the last one on the screen at the top of the next
page (0 lines of context).
- The Mutt Next Generation E-Mail Client 123
-
_\b6_\b._\b4_\b._\b1_\b6_\b8 _\bp_\ba_\bg_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
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 6.4.110 , page 105)''
+ sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)''
section.
_\b6_\b._\b4_\b._\b1_\b6_\b9 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
+ The Mutt Next Generation E-Mail Client 124
+
Type: number
Default: 0
Type: boolean
- The Mutt Next Generation E-Mail Client 124
-
Default: no
This option controls whether Mutt-ng generates old-style inline (traditional)
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 6.4.188 , page 126)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 6.4.188 , page 127)''.
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 125
+
_\b6_\b._\b4_\b._\b1_\b7_\b3 _\bp_\bg_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\be_\bx_\bi_\bt
Type: boolean
Expands to the name of a file containing the signature part of a
multipart/signed attachment when verifying it.
- The Mutt Next Generation E-Mail Client 125
-
%a
- The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.4.192 , page 127).
+ The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.4.192 , page 128).
%r
One or more key IDs.
_\b6_\b._\b4_\b._\b1_\b7_\b6 _\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 126
+
Type: string
Default: ''
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 6.4.110 , page
- 105)'', but has its own set of printf(3)-like sequences:
+ 106)'', but has its own set of printf(3)-like sequences:
%n
number
%u
user id
- The Mutt Next Generation E-Mail Client 126
-
%a
algorithm
%c
capabilities
+ The Mutt Next Generation E-Mail Client 127
+
%t
trust/validity of the key-uid association
Default: yes
- The Mutt Next Generation E-Mail Client 127
-
Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
the principal key will inherit the subkeys' capabilities. _\bU_\bn_\bs_\be_\bt this if you
want to play interesting key selection games. (PGP only)
Default: ''
This command is used to import a key from a message into the user's public key
+
+ The Mutt Next Generation E-Mail Client 128
+
ring. (PGP only)
_\b6_\b._\b4_\b._\b1_\b8_\b5 _\bp_\bg_\bp_\b__\bl_\bi_\bs_\bt_\b__\bp_\bu_\bb_\br_\bi_\bn_\bg_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
This option controls whether Mutt-ng will prompt you for automatically sending
a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
-
- The Mutt Next Generation E-Mail Client 128
-
(for any reason).
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.
Default: no
+ The Mutt Next Generation E-Mail Client 129
+
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
inline. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when inline is not
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 6.4.188 , page 126)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 6.4.188 , page 127)''.
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 129
-
If you have more than one key pair, this option allows you to specify which of
your private keys to use. It is recommended that you use the keyid form to
specify your key (e.g., ``0x00112233''). (PGP only)
Default: ''
+ The Mutt Next Generation E-Mail Client 130
+
This command is used to create the detached PGP signature for a multi-
part/signed PGP/MIME body part. (PGP only)
Default: 300
- The Mutt Next Generation E-Mail Client 130
-
The number of seconds after which a cached passphrase will expire if not used.
Default: 300. (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 131
+
_\b6_\b._\b4_\b._\b1_\b9_\b8 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
Default: no
Used in connection with the _\bp_\bi_\bp_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be command and the ``tag- prefix'' or
-
- The Mutt Next Generation E-Mail Client 131
-
``tag-prefix-cond'' operators. If this variable is _\bu_\bn_\bs_\be_\bt, when piping a list
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 6.4.201 , page 129)'' separator is added after each message.
+ (section 6.4.201 , page 130)'' separator is added after each message.
_\b6_\b._\b4_\b._\b2_\b0_\b3 _\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 132
+
Availability: POP
If _\bs_\be_\bt, Mutt-ng will try all available methods. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will only
Type: string
- The Mutt Next Generation E-Mail Client 132
-
Default: ''
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 133
+
_\b6_\b._\b4_\b._\b2_\b0_\b7 _\bp_\bo_\bp_\b__\bl_\ba_\bs_\bt
Type: boolean
Default: ask-yes
- The Mutt Next Generation E-Mail Client 133
-
Availability: POP
Controls whether or not Mutt-ng will try to reconnect to a POP server when the
Availability: POP
+ The Mutt Next Generation E-Mail Client 134
+
Your login name on the POP server.
This variable defaults to your user name on the local machine.
Default: ''
- Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 6.4.15 , page 84)'' variable, Mutt-ng
+ Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 6.4.15 , page 85)'' 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
- 6.4.214 , page 132)'' mailbox when you elect not to send immediately.
+ 6.4.214 , page 133)'' mailbox when you elect not to send immediately.
_\b6_\b._\b4_\b._\b2_\b1_\b4 _\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 6.4.213 , page 132)
+ Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.4.213 , page 133)
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 6.4.213 , page 132)'' variable.
+ ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.4.213 , page 133)'' variable.
_\b6_\b._\b4_\b._\b2_\b1_\b5 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Default: ''
- If _\bs_\be_\bt, a shell command to be executed if Mutt-ng fails to establish a
-
- The Mutt Next Generation E-Mail Client 134
-
- connection to the server. This is useful for setting up secure connections,
- e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up
- opening the server. Example:
+ If _\bs_\be_\bt, a shell command to be executed if Mutt-ng fails to establish a connec-
+ tion to the server. This is useful for setting up secure connections, e.g. with
+ ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the
+ server. Example:
preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
/dev/null > /dev/null'
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 135
+
_\b6_\b._\b4_\b._\b2_\b1_\b6 _\bp_\br_\bi_\bn_\bt
Type: quadoption
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 6.4.217 , page 133). 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 6.4.217 , page 134). 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 6.4.217 , page 133) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.217 , page 134) 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 6.4.217 , page 133) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.217 , page 134) is executed
only once, and all the messages are concatenated, with a form feed as the mes-
sage separator.
- The Mutt Next Generation E-Mail Client 135
-
Those who use the enscript(1) program's mail-printing mode will most likely
want to set this option.
Default: yes
- If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 6.4.166 , page 121)'', setting this
+ If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 6.4.166 , page 122)'', setting this
variable will cause Mutt-ng to prompt you for a command when the pager exits
+
+ The Mutt Next Generation E-Mail Client 136
+
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.
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 6.4.109 , page 105)''.
+ tion 6.4.109 , page 106)''.
_\b6_\b._\b4_\b._\b2_\b2_\b4 _\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 6.4.109 , page 105)''.
-
- The Mutt Next Generation E-Mail Client 136
+ by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.4.109 , page 106)''.
_\b6_\b._\b4_\b._\b2_\b2_\b5 _\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp
text in the body of a message.
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 137
+
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 6.4.339 , page 162)'' variable.
+ Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 6.4.340 , page 163)'' variable.
_\b6_\b._\b4_\b._\b2_\b2_\b7 _\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 6.4.74 , page 97) variable.
+ _\b$_\bf_\br_\bo_\bm (section 6.4.74 , page 98) variable.
_\b6_\b._\b4_\b._\b2_\b2_\b9 _\br_\be_\bc_\ba_\bl_\bl
Type: quadoption
- The Mutt Next Generation E-Mail Client 137
-
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 6.4.214 , page 132)''.
+ message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 6.4.214 , page 133)''.
Setting this variable to _\by_\be_\bs is not generally useful, and thus not recommended.
_\b6_\b._\b4_\b._\b2_\b3_\b0 _\br_\be_\bc_\bo_\br_\bd
+ The Mutt Next Generation E-Mail Client 138
+
Type: path
Default: ''
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 _\b6_\b._\b4_\b._\b2_\b3_\b0 _\b, _\bp_\ba_\bg_\be _\b1_\b3_\b6_\b) is overridden by the
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 96)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
- 6.4.241 , page 138)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 97)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
+ 6.4.241 , page 139)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page
35)'' command.
_\b6_\b._\b4_\b._\b2_\b3_\b1 _\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp
use the address in the ``From:'' header field instead.
This option is useful for reading a mailing list that sets the ``Reply-To:''
-
- The Mutt Next Generation E-Mail Client 138
-
header field to the list address and you want to send a private message to the
author of a message.
Default: yes
+ The Mutt Next Generation E-Mail Client 139
+
When set, the cursor will be automatically advanced to the next (possibly
undeleted) message whenever a command that modifies the current message is exe-
cuted.
Default: yes
This variable fine-tunes the behaviour of the _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 6.4.236 ,
-
- The Mutt Next Generation E-Mail Client 139
-
- page 137) feature. When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming
+ page 138) 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 6.4.228 , page 135) variable.
+ (section 6.4.228 , page 136) variable.
_\b6_\b._\b4_\b._\b2_\b3_\b8 _\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 140
+
Default: no
When this variable is _\bs_\be_\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
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 6.4.241 , page 138)'' or
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 96)'' 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 6.4.241 , page 139)'' or
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 97)'' is _\bs_\be_\bt too, the selection of the
fcc folder will be changed as well.
_\b6_\b._\b4_\b._\b2_\b4_\b0 _\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 6.4.296 , page 151)'' which is
+ closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page 152)'' 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
Type: boolean
- The Mutt Next Generation E-Mail Client 140
-
Default: no
This variable controls how copies of outgoing messages are saved. When set, a
check is made to see if a mailbox specified by the recipient address exists
(this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 ,
- page 94)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
+ page 95)'' 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 6.4.230 , page 136)'' mailbox.
- Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 96)'' variable.
+ The Mutt Next Generation E-Mail Client 141
+
+ Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 97)'' variable.
_\b6_\b._\b4_\b._\b2_\b4_\b2 _\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 6.4.243 , page 139)'' variable and friends are used.
+ _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 6.4.243 , page 140)'' variable and friends are used.
_\b6_\b._\b4_\b._\b2_\b4_\b3 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
_\b6_\b._\b4_\b._\b2_\b4_\b6 _\bs_\be_\bn_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
- The Mutt Next Generation E-Mail Client 141
-
Type: string
Default: 'us-ascii:iso-8859-1:utf-8'
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 6.4.24 , page 86)'' is not iso-8859-1 and recipients may not under-
+ (section 6.4.24 , page 87)'' 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 142
+
instead of or after iso-8859-1.
_\b6_\b._\b4_\b._\b2_\b4_\b7 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl
Command to use when spawning a subshell. By default, the user's login shell
from /etc/passwd is used.
- The Mutt Next Generation E-Mail Client 142
-
_\b6_\b._\b4_\b._\b2_\b5_\b0 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by
Type: string
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
6.4.254 , page 142) is _\bs_\be_\bt, this variable specifies the characters at which to
+
+ The Mutt Next Generation E-Mail Client 143
+
split a folder name into ``hierarchy items.''
_\b6_\b._\b4_\b._\b2_\b5_\b1 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bd_\be_\bl_\bi_\bm
%M
Total number of messages shown, i.e. not hidden by a limit. 1)
- The Mutt Next Generation E-Mail Client 143
-
%n
Number of new messages.
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 144
+
_\b6_\b._\b4_\b._\b2_\b5_\b4 _\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
Type: boolean
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
- 6.4.256 , page 142)'' is set to a too low value). For example, if the news-
+ 6.4.256 , page 143)'' 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 6.4.250 , page 140) variable.
+ _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 6.4.250 , page 141) variable.
_\b6_\b._\b4_\b._\b2_\b5_\b5 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
name. The reason for this is because many software packages use ``-- \n'' to
detect your signature.
- The Mutt Next Generation E-Mail Client 144
-
For example, Mutt-ng has the ability to highlight the signature in a different
color in the builtin pager.
Default: no
+ The Mutt Next Generation E-Mail Client 145
+
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
know what you are doing, and are prepared to take some heat from netiquette
~f joe | ~s joe
- The Mutt Next Generation E-Mail Client 145
-
_\b6_\b._\b4_\b._\b2_\b6_\b2 _\bs_\bl_\be_\be_\bp_\b__\bt_\bi_\bm_\be
Type: number
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 146
+
_\b6_\b._\b4_\b._\b2_\b6_\b3 _\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp
Type: boolean
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 6.4.121 ,
- page 110)'' variable.
+ page 111)'' variable.
_\b6_\b._\b4_\b._\b2_\b6_\b4 _\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 6.4.225 , page 134)'', most notably smileys in the
+ ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.225 , page 135)'', most notably smileys in the
beginning of a line
_\b6_\b._\b4_\b._\b2_\b6_\b5 _\bs_\bm_\bi_\bm_\be_\b__\ba_\bs_\bk_\b__\bc_\be_\br_\bt_\b__\bl_\ba_\bb_\be_\bl
Type: path
- The Mutt Next Generation E-Mail Client 146
-
Default: ''
Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
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 147
+
_\b6_\b._\b4_\b._\b2_\b6_\b8 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
%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 6.4.270 ,
- page 145)
+ page 146)
%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
- 6.4.266 , page 144) 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 6.4.266 , page 144)' or
- '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.4.266 , page 144)'.
+ 6.4.266 , page 145) 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 6.4.266 , page 145)' or
+ '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.4.266 , page 145)'.
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-
Default: yes
- The Mutt Next Generation E-Mail Client 147
-
If _\bs_\be_\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
mailbox-address to determine the key to use. It will ask you to supply a key,
Type: string
+ The Mutt Next Generation E-Mail Client 148
+
Default: ''
This is the default key-pair to use for signing. This must be set to the keyid
_\b6_\b._\b4_\b._\b2_\b7_\b5 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bs_\bi_\bg_\bn_\be_\br_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
- The Mutt Next Generation E-Mail Client 148
-
Type: string
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 149
+
_\b6_\b._\b4_\b._\b2_\b7_\b6 _\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
Type: string
This command is used to extract PKCS7 structures of S/MIME signatures, in order
to extract the public X509 certificate(s). (S/MIME only)
- The Mutt Next Generation E-Mail Client 149
-
_\b6_\b._\b4_\b._\b2_\b8_\b0 _\bs_\bm_\bi_\bm_\be_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
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 150
+
_\b6_\b._\b4_\b._\b2_\b8_\b1 _\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
Type: string
This command is used to verify S/MIME signatures of type application/x-
pkcs7-mime. (S/MIME only)
- _\b6_\b._\b4_\b._\b2_\b8_\b5 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+ _\b6_\b._\b4_\b._\b2_\b8_\b5 _\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be
Type: string
Availability: SMTP
- The Mutt Next Generation E-Mail Client 150
+ If this variable is non-empty, it'll be used as the envelope sender. If it's
+ empty (the default), the value of the regular From: header will be used.
+
+ This may be necessary as some providers don't allow for arbitrary values as the
+ envelope sender but only a particular one which may not be the same as the
+ user's desired From: header.
+
+ _\b6_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+
+ The Mutt Next Generation E-Mail Client 151
+
+ Type: string
+
+ Default: ''
+
+ Availability: SMTP
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 6.4.247 , page 140)'', and any associated variables.
- _\b6_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
+ _\b6_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
Type: string
Availability: SMTP
- Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\ba_\bu_\bt_\bh_\b__\bu_\bs_\be_\br_\bn_\ba_\bm_\be (section
- , page )'' is set, but this variable is not, you will be prompted for a pass-
- word when sending.
+ Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section
+ 6.4.290 , page 150)'' 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
the superuser of your machine may read it regardless of the file's permissions.
- _\b6_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
+ _\b6_\b._\b4_\b._\b2_\b8_\b8 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
Type: number
Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
will probably desire 587, the mail submission port.
- _\b6_\b._\b4_\b._\b2_\b8_\b8 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
+ _\b6_\b._\b4_\b._\b2_\b8_\b9 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
Type: string
continue without TLS in case of an error. Muttng still needs to have SSL sup-
port enabled in order to use it.
- _\b6_\b._\b4_\b._\b2_\b8_\b9 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
+ The Mutt Next Generation E-Mail Client 152
+
+ _\b6_\b._\b4_\b._\b2_\b9_\b0 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
Type: string
Availability: SMTP
- The Mutt Next Generation E-Mail Client 151
-
Defines the username to use with SMTP AUTH. Setting this variable will cause
Mutt-ng to attempt to use SMTP AUTH when sending.
- _\b6_\b._\b4_\b._\b2_\b9_\b0 _\bs_\bo_\br_\bt
+ _\b6_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bo_\br_\bt
Type: sort order
You may optionally use the ``reverse-'' prefix to specify reverse sorting order
(example: set sort=reverse-date-sent).
- _\b6_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bo_\br_\bt_\b__\ba_\bl_\bi_\ba_\bs
+ _\b6_\b._\b4_\b._\b2_\b9_\b2 _\bs_\bo_\br_\bt_\b__\ba_\bl_\bi_\ba_\bs
Type: sort order
alias (sort alphabetically by alias name)
unsorted (leave in order specified in .muttrc)
- _\b6_\b._\b4_\b._\b2_\b9_\b2 _\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ _\b6_\b._\b4_\b._\b2_\b9_\b3 _\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
Type: sort order
+ The Mutt Next Generation E-Mail Client 153
+
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 6.4.290 , page 149)'' can,
+ This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150)'' 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
-
- The Mutt Next Generation E-Mail Client 152
-
siblings by which has the last descendant, using the rest of sort_aux as an
ordering.
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 6.4.290 , page 149)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
- (section 6.4.292 , page 150) is reversed again (which is not the right thing
+ N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ (section 6.4.293 , page 151) is reversed again (which is not the right thing
to do, but kept to not break any existing configuration setting).
- _\b6_\b._\b4_\b._\b2_\b9_\b3 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
+ _\b6_\b._\b4_\b._\b2_\b9_\b4 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
Type: sort order
You may optionally use the ``reverse-'' prefix to specify reverse sorting order
(example: set sort_browser=reverse-date).
- _\b6_\b._\b4_\b._\b2_\b9_\b4 _\bs_\bo_\br_\bt_\b__\br_\be
+ _\b6_\b._\b4_\b._\b2_\b9_\b5 _\bs_\bo_\br_\bt_\b__\br_\be
Type: boolean
Default: yes
This variable is only useful when sorting by threads with ``_\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
- (section 6.4.311 , page 157)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
- Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.294 ,
- page 151) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
+ (section 6.4.312 , page 158)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.295 ,
+ page 152) _\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 6.4.231 , page 136)''. With
- _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.294 , page 151) _\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 6.4.231 , page 137)''. With
+ _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.295 , page 152) _\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
- 6.4.231 , page 136)'' parts of both messages are identical.
+ 6.4.231 , page 137)'' parts of both messages are identical.
+
+ The Mutt Next Generation E-Mail Client 154
- _\b6_\b._\b4_\b._\b2_\b9_\b5 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
+ _\b6_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
Type: string
Default: ','
- ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.295 , page 151)'' controls what happens when
- multiple spam headers are matched: if _\bu_\bn_\bs_\be_\bt, each successive header will
+ ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.296 , page 152)'' 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 6.4.296 ,
+ page 152)'' as a separator.
- The Mutt Next Generation E-Mail Client 153
-
- overwrite any previous matches value for the spam label. If _\bs_\be_\bt, each succes-
- sive match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section
- 6.4.295 , page 151)'' as a separator.
-
- _\b6_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
+ _\b6_\b._\b4_\b._\b2_\b9_\b7 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
Type: path
set this variable to the value of the environment variable $MAIL if it is not
set.
- _\b6_\b._\b4_\b._\b2_\b9_\b7 _\bs_\bs_\bl_\b__\bc_\ba_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs_\b__\bf_\bi_\bl_\be
+ _\b6_\b._\b4_\b._\b2_\b9_\b8 _\bs_\bs_\bl_\b__\bc_\ba_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs_\b__\bf_\bi_\bl_\be
Type: path
Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
- _\b6_\b._\b4_\b._\b2_\b9_\b8 _\bs_\bs_\bl_\b__\bc_\bl_\bi_\be_\bn_\bt_\b__\bc_\be_\br_\bt
+ _\b6_\b._\b4_\b._\b2_\b9_\b9 _\bs_\bs_\bl_\b__\bc_\bl_\bi_\be_\bn_\bt_\b__\bc_\be_\br_\bt
Type: path
The file containing a client certificate and its associated private key.
- _\b6_\b._\b4_\b._\b2_\b9_\b9 _\bs_\bs_\bl_\b__\bf_\bo_\br_\bc_\be_\b__\bt_\bl_\bs
+ _\b6_\b._\b4_\b._\b3_\b0_\b0 _\bs_\bs_\bl_\b__\bf_\bo_\br_\bc_\be_\b__\bt_\bl_\bs
Type: boolean
If this variable is _\bs_\be_\bt, mutt-ng will require that all connections to remote
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 155
+
abort the connection anyway. This option supersedes ``_\b$_\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs (section
- 6.4.301 , page 152)''.
+ 6.4.302 , page 154)''.
- _\b6_\b._\b4_\b._\b3_\b0_\b0 _\bs_\bs_\bl_\b__\bm_\bi_\bn_\b__\bd_\bh_\b__\bp_\br_\bi_\bm_\be_\b__\bb_\bi_\bt_\bs
+ _\b6_\b._\b4_\b._\b3_\b0_\b1 _\bs_\bs_\bl_\b__\bm_\bi_\bn_\b__\bd_\bh_\b__\bp_\br_\bi_\bm_\be_\b__\bb_\bi_\bt_\bs
Type: number
Default: 0
- The Mutt Next Generation E-Mail Client 154
-
Availability: GNUTLS
This variable specifies the minimum acceptable prime size (in bits) for use in
any Diffie-Hellman key exchange. A value of 0 will use the default from the
GNUTLS library.
- _\b6_\b._\b4_\b._\b3_\b0_\b1 _\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs
+ _\b6_\b._\b4_\b._\b3_\b0_\b2 _\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs
Type: quadoption
ing the capability. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not attempt to use STARTTLS
regardless of the server's capabilities.
- _\b6_\b._\b4_\b._\b3_\b0_\b2 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b2
+ _\b6_\b._\b4_\b._\b3_\b0_\b3 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b2
Type: boolean
This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
tion process.
- _\b6_\b._\b4_\b._\b3_\b0_\b3 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b3
+ _\b6_\b._\b4_\b._\b3_\b0_\b4 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b3
Type: boolean
This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
tion process.
- _\b6_\b._\b4_\b._\b3_\b0_\b4 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bt_\bl_\bs_\bv_\b1
+ _\b6_\b._\b4_\b._\b3_\b0_\b5 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bt_\bl_\bs_\bv_\b1
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 156
+
Availability: SSL or GNUTLS
This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
tion process.
- _\b6_\b._\b4_\b._\b3_\b0_\b5 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
+ _\b6_\b._\b4_\b._\b3_\b0_\b6 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
Type: boolean
- The Mutt Next Generation E-Mail Client 155
-
Default: yes
Availability: SSL
If set to _\by_\be_\bs, Mutt-ng will use CA certificates in the system-wide certificate
store when checking if server certificate is signed by a trusted CA.
- _\b6_\b._\b4_\b._\b3_\b0_\b6 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs
+ _\b6_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs
Type: string
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 6.4.307 , page 154)''. The first character is used when the mailbox is
+ tion 6.4.308 , page 155)''. 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
been opened in attach-message mode (Certain operations like composing a new
mail, replying, forwarding, etc. are not permitted in this mode).
- _\b6_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b6_\b._\b4_\b._\b3_\b0_\b8 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%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 6.4.110 , page 105)'', but has
+ string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)'', but has
its own set of printf(3)-like sequences:
%b
%d
number of deleted messages *
+ The Mutt Next Generation E-Mail Client 157
+
%f
the full pathname of the current mailbox
%h
local hostname
- The Mutt Next Generation E-Mail Client 156
-
%l
size (in bytes) 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 6.4.306 , page 154)
+ to _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs (section 6.4.307 , page 155)
%s
- current sorting mode (_\b$_\bs_\bo_\br_\bt (section 6.4.290 , page 149))
+ current sorting mode (_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150))
%S
- current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 6.4.292 , page
- 150))
+ current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 6.4.293 , page
+ 151))
%t
number of tagged messages *
%v
Mutt-ng version string
+ The Mutt Next Generation E-Mail Client 158
+
%V
currently active limit pattern, if any *
%|X
pad to the end of the line with 'X'
- The Mutt Next Generation E-Mail Client 157
-
* = can be optionally printed if nonzero
Some of the above sequences can be used to optionally print a string if their
replace any dots in the expansion by underscores. This might be helpful with
IMAP folders that don't like dots in folder names.
- _\b6_\b._\b4_\b._\b3_\b0_\b8 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bo_\bn_\b__\bt_\bo_\bp
+ _\b6_\b._\b4_\b._\b3_\b0_\b9 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bo_\bn_\b__\bt_\bo_\bp
Type: boolean
Setting this variable causes the ``status bar'' to be displayed on the first
line of the screen rather than near the bottom.
- _\b6_\b._\b4_\b._\b3_\b0_\b9 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo
+ The Mutt Next Generation E-Mail Client 159
+
+ _\b6_\b._\b4_\b._\b3_\b1_\b0 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo
Type: boolean
With mailto: style links, a body as well as arbitrary header information may be
embedded. This may lead to (user) headers being overwriten without note if
- ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 92)'' is unset.
-
- The Mutt Next Generation E-Mail Client 158
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 93)'' is unset.
If this variable is _\bs_\be_\bt, mutt-ng is strict and allows anything to be changed.
If it's _\bu_\bn_\bs_\be_\bt, all headers given will be prefixed with ``X-Mailto-'' and the
message including headers will be shown in the editor regardless of what
- ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 92)'' is set to.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 93)'' is set to.
- _\b6_\b._\b4_\b._\b3_\b1_\b0 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
+ _\b6_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
Type: boolean
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 6.4.11 , page 82).
+ Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 6.4.11 , page 83).
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
from being devided into multiple lines.
- _\b6_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
+ _\b6_\b._\b4_\b._\b3_\b1_\b2 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
Type: boolean
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 6.4.290 , page 149)'' by mes-
+ ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150)'' 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''
which will get grouped together.
- _\b6_\b._\b4_\b._\b3_\b1_\b2 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
+ _\b6_\b._\b4_\b._\b3_\b1_\b3 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
Type: boolean
Default: no
When _\bs_\be_\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
- matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 6.4.313 , page 157) when replying. This is
+ matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 6.4.314 , page 158) when replying. This is
useful to properly react on subject changes and reduce ``subject noise.'' (esp.
in Usenet)
- _\b6_\b._\b4_\b._\b3_\b1_\b3 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
+ The Mutt Next Generation E-Mail Client 160
+
+ _\b6_\b._\b4_\b._\b3_\b1_\b4 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
Type: regular expression
Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
- When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 6.4.312 , page 157) is _\bs_\be_\bt, mutt-ng
+ When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 6.4.313 , page 158) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
- The Mutt Next Generation E-Mail Client 159
-
- _\b6_\b._\b4_\b._\b3_\b1_\b4 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
+ _\b6_\b._\b4_\b._\b3_\b1_\b5 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
Type: boolean
If _\bs_\be_\bt, attachments with flowed format will have their quoting ``stuffed'',
i.e. a space will be inserted between the quote characters and the actual text.
- _\b6_\b._\b4_\b._\b3_\b1_\b5 _\bs_\bu_\bs_\bp_\be_\bn_\bd
+ _\b6_\b._\b4_\b._\b3_\b1_\b6 _\bs_\bu_\bs_\bp_\be_\bn_\bd
Type: boolean
usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
mand like ``xterm -e muttng.''
- _\b6_\b._\b4_\b._\b3_\b1_\b6 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
+ _\b6_\b._\b4_\b._\b3_\b1_\b7 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
Type: boolean
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 6.4.109 , page 105) is ignored when this
+ Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.4.109 , page 106) is ignored when this
option is set.
- _\b6_\b._\b4_\b._\b3_\b1_\b7 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b6_\b._\b4_\b._\b3_\b1_\b8 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
Type: boolean
to be searched are decoded before searching. If _\bu_\bn_\bs_\be_\bt, messages are searched
as they appear in the folder.
- _\b6_\b._\b4_\b._\b3_\b1_\b8 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
+ The Mutt Next Generation E-Mail Client 161
+
+ _\b6_\b._\b4_\b._\b3_\b1_\b9 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng uses the date received rather than the date sent to thread
messages by subject.
- The Mutt Next Generation E-Mail Client 160
-
- _\b6_\b._\b4_\b._\b3_\b1_\b9 _\bt_\bi_\bl_\bd_\be
+ _\b6_\b._\b4_\b._\b3_\b2_\b0 _\bt_\bi_\bl_\bd_\be
Type: boolean
When _\bs_\be_\bt, the internal-pager will pad blank lines to the bottom of the screen
with a tilde (~).
- _\b6_\b._\b4_\b._\b3_\b2_\b0 _\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b6_\b._\b4_\b._\b3_\b2_\b1 _\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
pressed in the main menu before timing out and checking for new mail. A value
of zero or less will cause Mutt-ng to never time out.
- _\b6_\b._\b4_\b._\b3_\b2_\b1 _\bt_\bm_\bp_\bd_\bi_\br
+ _\b6_\b._\b4_\b._\b3_\b2_\b2 _\bt_\bm_\bp_\bd_\bi_\br
Type: path
set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
'/tmp' is used.
- _\b6_\b._\b4_\b._\b3_\b2_\b2 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
+ _\b6_\b._\b4_\b._\b3_\b2_\b3 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
Type: string
indicate mail that was sent by _\by_\bo_\bu. The sixth character is used to indicate
when a mail was sent to a mailing-list you're subscribe to (default: L).
- _\b6_\b._\b4_\b._\b3_\b2_\b3 _\bt_\br_\ba_\bs_\bh
+ The Mutt Next Generation E-Mail Client 162
+
+ _\b6_\b._\b4_\b._\b3_\b2_\b4 _\bt_\br_\ba_\bs_\bh
Type: path
If _\bs_\be_\bt, this variable specifies the path of the trash folder where the mails
marked for deletion will be moved, instead of being irremediably purged.
- The Mutt Next Generation E-Mail Client 161
-
N\bNo\bot\bte\be: When you delete a message in the trash folder, it is really deleted, so
that there is no way to recover mail.
- _\b6_\b._\b4_\b._\b3_\b2_\b4 _\bt_\bu_\bn_\bn_\be_\bl
+ _\b6_\b._\b4_\b._\b3_\b2_\b5 _\bt_\bu_\bn_\bn_\be_\bl
Type: string
N\bNo\bot\bte\be:\b: For this example to work you must be able to log in to the remote machine
without having to enter a password.
- _\b6_\b._\b4_\b._\b3_\b2_\b5 _\bu_\bm_\ba_\bs_\bk
+ _\b6_\b._\b4_\b._\b3_\b2_\b6 _\bu_\bm_\ba_\bs_\bk
Type: number
This sets the umask that will be used by Mutt-ng when creating all kinds of
files. If _\bu_\bn_\bs_\be_\bt, the default value is 077.
- _\b6_\b._\b4_\b._\b3_\b2_\b6 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
+ _\b6_\b._\b4_\b._\b3_\b2_\b7 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
Type: boolean
When _\bs_\be_\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
rent thread is _\bu_\bncollapsed.
- _\b6_\b._\b4_\b._\b3_\b2_\b7 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
+ _\b6_\b._\b4_\b._\b3_\b2_\b8 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
Type: boolean
Default: no
W\bWa\bar\brn\bni\bin\bng\bg:\b: do not set this variable unless you are using a version of sendmail
- which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be
- able to send mail.
+ 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 163
+
+ mail.
- When _\bs_\be_\bt, Mutt-ng will invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page 140)'' with
- the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation.
+ When _\bs_\be_\bt, Mutt-ng will either invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page
+ 140)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
+ negotiation or tell libESMTP to do so.
- _\b6_\b._\b4_\b._\b3_\b2_\b8 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
+ _\b6_\b._\b4_\b._\b3_\b2_\b9 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
Type: boolean
Default: yes
- The Mutt Next Generation E-Mail Client 162
-
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 6.4.89 , page 100)''. If _\bu_\bn_\bs_\be_\bt,
+ tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 6.4.89 , page 101)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
- _\b6_\b._\b4_\b._\b3_\b2_\b9 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
+ _\b6_\b._\b4_\b._\b3_\b3_\b0 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
Type: boolean
sages. If _\bu_\bn_\bs_\be_\bt, no ``From:'' header field will be generated unless the user
explicitly sets one using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 34)'' command.
- _\b6_\b._\b4_\b._\b3_\b3_\b0 _\bu_\bs_\be_\b__\bi_\bd_\bn
+ _\b6_\b._\b4_\b._\b3_\b3_\b1 _\bu_\bs_\be_\b__\bi_\bd_\bn
Type: boolean
N\bNo\bot\bte\be:\b: You can use IDNs for addresses even if this is _\bu_\bn_\bs_\be_\bt. This variable only
affects decoding.
- _\b6_\b._\b4_\b._\b3_\b3_\b1 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
+ _\b6_\b._\b4_\b._\b3_\b3_\b2 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
Type: boolean
If this option is _\bu_\bn_\bs_\be_\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
mally, the default should work.
- _\b6_\b._\b4_\b._\b3_\b3_\b2 _\bu_\bs_\be_\br_\b__\ba_\bg_\be_\bn_\bt
+ _\b6_\b._\b4_\b._\b3_\b3_\b3 _\bu_\bs_\be_\br_\b__\ba_\bg_\be_\bn_\bt
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 164
+
When _\bs_\be_\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
cating which version of Mutt-ng was used for composing them.
- _\b6_\b._\b4_\b._\b3_\b3_\b3 _\bv_\bi_\bs_\bu_\ba_\bl
+ _\b6_\b._\b4_\b._\b3_\b3_\b4 _\bv_\bi_\bs_\bu_\ba_\bl
Type: path
Specifies the visual editor to invoke when the _\b~_\bv command is given in the
builtin editor.
- The Mutt Next Generation E-Mail Client 163
-
- _\b6_\b._\b4_\b._\b3_\b3_\b4 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
+ _\b6_\b._\b4_\b._\b3_\b3_\b5 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
Type: boolean
When _\bs_\be_\bt, Mutt-ng will always ask for a key. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will wait for
a key only if the external command returned a non-zero status.
- _\b6_\b._\b4_\b._\b3_\b3_\b5 _\bw_\be_\be_\bd
+ _\b6_\b._\b4_\b._\b3_\b3_\b6 _\bw_\be_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
replying to messages.
- _\b6_\b._\b4_\b._\b3_\b3_\b6 _\bw_\br_\ba_\bp_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b6_\b._\b4_\b._\b3_\b3_\b7 _\bw_\br_\ba_\bp_\b__\bs_\be_\ba_\br_\bc_\bh
Type: boolean
When _\bs_\be_\bt, searches will wrap around the first (or last) message. When _\bu_\bn_\bs_\be_\bt,
searches will not wrap.
- _\b6_\b._\b4_\b._\b3_\b3_\b7 _\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
+ _\b6_\b._\b4_\b._\b3_\b3_\b8 _\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
Type: number
Default: 0
+ The Mutt Next Generation E-Mail Client 165
+
Controls the size of the margin remaining at the right side of the terminal
when Mutt-ng's pager does smart wrapping.
- _\b6_\b._\b4_\b._\b3_\b3_\b8 _\bw_\br_\bi_\bt_\be_\b__\bb_\bc_\bc
+ _\b6_\b._\b4_\b._\b3_\b3_\b9 _\bw_\br_\bi_\bt_\be_\b__\bb_\bc_\bc
Type: boolean
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.
- The Mutt Next Generation E-Mail Client 164
-
- _\b6_\b._\b4_\b._\b3_\b3_\b9 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
+ _\b6_\b._\b4_\b._\b3_\b4_\b0 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
Type: number
Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 6.4.226 , page 135)'' variable.
- _\b6_\b._\b4_\b._\b3_\b4_\b0 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
+ _\b6_\b._\b4_\b._\b3_\b4_\b1 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
Type: string
Default: 'M%?n?AIL&ail?'
Controls the format of the X11 icon title, as long as _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (sec-
- tion 6.4.342 , page 163) is _\bs_\be_\bt. This string is identical in formatting to the
- one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.307 , page 154)''.
+ tion 6.4.343 , page 164) is _\bs_\be_\bt. This string is identical in formatting to the
+ one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 155)''.
- _\b6_\b._\b4_\b._\b3_\b4_\b1 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
+ _\b6_\b._\b4_\b._\b3_\b4_\b2 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
Type: string
Default: ''
- If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.342 , page 163) 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 6.4.343 , page 164) 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.
set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
cut -d ''' -f 2`'
- _\b6_\b._\b4_\b._\b3_\b4_\b2 _\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs
+ _\b6_\b._\b4_\b._\b3_\b4_\b3 _\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs
Type: boolean
+ The Mutt Next Generation E-Mail Client 166
+
Default: no
Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
you're in an appropriate terminal). The default must be _\bu_\bn_\bs_\be_\bt to force in the
validity checking.
- _\b6_\b._\b4_\b._\b3_\b4_\b3 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
+ _\b6_\b._\b4_\b._\b3_\b4_\b4 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
Type: string
Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
- The Mutt Next Generation E-Mail Client 165
-
Controls the format of the title bar of the xterm provided that
- _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.342 , page 163) has been _\bs_\be_\bt. This string is
- identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.307 ,
- page 154)''.
+ _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.343 , page 164) has been _\bs_\be_\bt. This string is
+ identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 ,
+ page 155)''.
_\b6_\b._\b5 _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
tings for this menu will affect the default bindings for all menus (except as
noted).
+ The Mutt Next Generation E-Mail Client 167
+
bottom-page L move to the bottom of the page
current-bottom not bound move current entry to bottom of page
current-middle not bound move current entry to middle of page
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 166
-
_\b6_\b._\b5_\b._\b2 _\bi_\bn_\bd_\be_\bx
- The Mutt Next Generation E-Mail Client 167
+ The Mutt Next Generation E-Mail Client 168
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 168
+ The Mutt Next Generation E-Mail Client 169
sort-mailbox o sort messages
sort-reverse O sort messages in reverse order
_\b6_\b._\b5_\b._\b3 _\bp_\ba_\bg_\be_\br
- The Mutt Next Generation E-Mail Client 169
+ The Mutt Next Generation E-Mail Client 170
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 170
+ The Mutt Next Generation E-Mail Client 171
reply r reply to a message
save-message s save message/attachment to a file
_\b6_\b._\b5_\b._\b6 _\ba_\bt_\bt_\ba_\bc_\bh
- The Mutt Next Generation E-Mail Client 171
+ The Mutt Next Generation E-Mail Client 172
bounce-message b remail a message to another user
collapse-parts v toggle display of subparts
_\b6_\b._\b5_\b._\b7 _\bc_\bo_\bm_\bp_\bo_\bs_\be
- The Mutt Next Generation E-Mail Client 172
+ The Mutt Next Generation E-Mail Client 173
attach-file a attach a file(s) to this message
attach-message A attach message(s) to this message
_\b6_\b._\b5_\b._\b9 _\bb_\br_\bo_\bw_\bs_\be_\br
- The Mutt Next Generation E-Mail Client 173
+ The Mutt Next Generation E-Mail Client 174
change-dir c change directories
check-new TAB check mailboxes for new mail
_\b7_\b. _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\by
- The Mutt Next Generation E-Mail Client 174
+ The Mutt Next Generation E-Mail Client 175
_\b7_\b._\b1 _\bA_\bc_\bk_\bn_\bo_\bw_\bl_\be_\bd_\bg_\bm_\be_\bn_\bt_\bs
Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
- The Mutt Next Generation E-Mail Client 175
+ The Mutt Next Generation E-Mail Client 176
Brandon Long <blong@fiction.net>,
Elimar Riesebieter <riesebie@lxtec.de>
- The Mutt Next Generation E-Mail Client 176
+ The Mutt Next Generation E-Mail Client 177
_\b7_\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 177
+ The Mutt Next Generation E-Mail Client 178
CONTENTS
4.11.1 Linking threads 59
4.11.2 Breaking threads 59
4.12 Delivery Status Notification (DSN) Support ..................... 59
- 4.13 POP3 Support (OPTIONAL) ........................................ 59
+ 4.13 POP3 Support (OPTIONAL) ........................................ 60
4.14 IMAP Support (OPTIONAL) ........................................ 60
4.14.1 The Folder Browser 61
ii
- 4.14.2 Authentication 61
+ 4.14.2 Authentication 62
4.15 NNTP Support (OPTIONAL) ........................................ 62
4.15.1 Again: Scoring 62
4.16 SMTP Support (OPTIONAL) ........................................ 63
- 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 63
+ 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 64
4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64
4.19 Compressed folders Support (OPTIONAL) .......................... 64
4.19.1 Open a compressed mailbox for reading 65
- 4.19.2 Write a compressed mailbox 65
+ 4.19.2 Write a compressed mailbox 66
4.19.3 Append a message to a compressed mailbox 66
- 4.19.4 Encrypted folders 66
+ 4.19.4 Encrypted folders 67
5. Mutt-ng's MIME Support ............................................... 67
5.1 Using MIME in Mutt ............................................. 67
5.1.1 Viewing MIME messages in the pager 67
- 5.1.2 The Attachment Menu 67
+ 5.1.2 The Attachment Menu 68
5.1.3 The Compose Menu 68
- 5.2 MIME Type configuration with mime.types ........................ 68
+ 5.2 MIME Type configuration with mime.types ........................ 69
5.3 MIME Viewer configuration with mailcap ......................... 69
- 5.3.1 The Basics of the mailcap file 69
+ 5.3.1 The Basics of the mailcap file 70
5.3.2 Secure use of mailcap 71
5.3.3 Advanced mailcap Usage 71
5.3.4 Example mailcap files 74
6. Reference ............................................................ 77
6.1 Command line options ........................................... 77
6.2 Patterns ....................................................... 78
- 6.3 Configuration Commands ......................................... 79
- 6.4 Configuration variables .......................................... 81
- 6.4.1 abort_nosubject 81
- 6.4.2 abort_unmodified 81
- 6.4.3 alias_file 81
- 6.4.4 alias_format 81
- 6.4.5 allow_8bit 82
- 6.4.6 allow_ansi 82
- 6.4.7 arrow_cursor 82
+ 6.3 Configuration Commands ......................................... 80
+ 6.4 Configuration variables .......................................... 82
+ 6.4.1 abort_nosubject 82
+ 6.4.2 abort_unmodified 82
+ 6.4.3 alias_file 82
+ 6.4.4 alias_format 82
+ 6.4.5 allow_8bit 83
+ 6.4.6 allow_ansi 83
+ 6.4.7 arrow_cursor 83
6.4.8 ascii_chars 83
- 6.4.9 askbcc 83
- 6.4.10 askcc 83
- 6.4.11 assumed_charset 83
- 6.4.12 attach_format 83
- 6.4.13 attach_sep 84
+ 6.4.9 askbcc 84
+ 6.4.10 askcc 84
+ 6.4.11 assumed_charset 84
+ 6.4.12 attach_format 84
+ 6.4.13 attach_sep 85
6.4.14 attach_split 85
- 6.4.15 attribution 85
- 6.4.16 auto_tag 85
- 6.4.17 autoedit 85
- 6.4.18 beep 85
+ 6.4.15 attribution 86
+ 6.4.16 auto_tag 86
+ 6.4.17 autoedit 86
+ 6.4.18 beep 86
6.4.19 beep_new 86
- 6.4.20 bounce 86
- 6.4.21 bounce_delivered 86
+ 6.4.20 bounce 87
+ 6.4.21 bounce_delivered 87
iii
- 6.4.22 braille_friendly 86
- 6.4.23 certificate_file 86
- 6.4.24 charset 87
- 6.4.25 check_new 87
- 6.4.26 collapse_unread 87
- 6.4.27 compose_format 87
- 6.4.28 config_charset 88
- 6.4.29 confirmappend 88
- 6.4.30 confirmcreate 88
- 6.4.31 connect_timeout 88
- 6.4.32 content_type 88
+ 6.4.22 braille_friendly 87
+ 6.4.23 certificate_file 87
+ 6.4.24 charset 88
+ 6.4.25 check_new 88
+ 6.4.26 collapse_unread 88
+ 6.4.27 compose_format 88
+ 6.4.28 config_charset 89
+ 6.4.29 confirmappend 89
+ 6.4.30 confirmcreate 89
+ 6.4.31 connect_timeout 89
+ 6.4.32 content_type 89
6.4.33 copy 89
- 6.4.34 crypt_autoencrypt 89
- 6.4.35 crypt_autopgp 89
- 6.4.36 crypt_autosign 89
+ 6.4.34 crypt_autoencrypt 90
+ 6.4.35 crypt_autopgp 90
+ 6.4.36 crypt_autosign 90
6.4.37 crypt_autosmime 90
- 6.4.38 crypt_replyencrypt 90
- 6.4.39 crypt_replysign 90
- 6.4.40 crypt_replysignencrypted 90
- 6.4.41 crypt_timestamp 90
+ 6.4.38 crypt_replyencrypt 91
+ 6.4.39 crypt_replysign 91
+ 6.4.40 crypt_replysignencrypted 91
+ 6.4.41 crypt_timestamp 91
6.4.42 crypt_use_gpgme 91
- 6.4.43 crypt_verify_sig 91
- 6.4.44 date_format 91
- 6.4.45 default_hook 91
+ 6.4.43 crypt_verify_sig 92
+ 6.4.44 date_format 92
+ 6.4.45 default_hook 92
6.4.46 delete 92
- 6.4.47 delete_untag 92
- 6.4.48 digest_collapse 92
- 6.4.49 display_filter 92
- 6.4.50 dotlock_program 92
+ 6.4.47 delete_untag 93
+ 6.4.48 digest_collapse 93
+ 6.4.49 display_filter 93
+ 6.4.50 dotlock_program 93
6.4.51 dsn_notify 93
- 6.4.52 dsn_return 93
- 6.4.53 duplicate_threads 93
- 6.4.54 edit_headers 93
- 6.4.55 editor 93
+ 6.4.52 dsn_return 94
+ 6.4.53 duplicate_threads 94
+ 6.4.54 edit_headers 94
+ 6.4.55 editor 94
6.4.56 encode_from 94
- 6.4.57 entropy_file 94
- 6.4.58 envelope_from 94
- 6.4.59 escape 94
- 6.4.60 fast_reply 94
+ 6.4.57 entropy_file 95
+ 6.4.58 envelope_from 95
+ 6.4.59 escape 95
+ 6.4.60 fast_reply 95
6.4.61 fcc_attach 95
- 6.4.62 fcc_clear 95
- 6.4.63 file_charset 95
- 6.4.64 folder 95
+ 6.4.62 fcc_clear 96
+ 6.4.63 file_charset 96
+ 6.4.64 folder 96
6.4.65 folder_format 96
- 6.4.66 followup_to 96
- 6.4.67 force_buffy_check 97
- 6.4.68 force_name 97
- 6.4.69 forward_decode 97
- 6.4.70 forward_decrypt 97
+ 6.4.66 followup_to 97
+ 6.4.67 force_buffy_check 98
+ 6.4.68 force_name 98
+ 6.4.69 forward_decode 98
+ 6.4.70 forward_decrypt 98
6.4.71 forward_edit 98
- 6.4.72 forward_format 98
- 6.4.73 forward_quote 98
- 6.4.74 from 98
+ 6.4.72 forward_format 99
+ 6.4.73 forward_quote 99
+ 6.4.74 from 99
iv
- 6.4.75 gecos_mask 98
- 6.4.76 hdrs 99
- 6.4.77 header 99
- 6.4.78 header_cache 99
+ 6.4.75 gecos_mask 99
+ 6.4.76 hdrs 100
+ 6.4.77 header 100
+ 6.4.78 header_cache 100
6.4.79 header_cache_compress 100
6.4.80 help 100
- 6.4.81 hidden_host 100
- 6.4.82 hide_limited 100
- 6.4.83 hide_missing 100
+ 6.4.81 hidden_host 101
+ 6.4.82 hide_limited 101
+ 6.4.83 hide_missing 101
6.4.84 hide_thread_subject 101
6.4.85 hide_top_limited 101
- 6.4.86 hide_top_missing 101
- 6.4.87 history 101
- 6.4.88 honor_followup_to 101
- 6.4.89 hostname 101
+ 6.4.86 hide_top_missing 102
+ 6.4.87 history 102
+ 6.4.88 honor_followup_to 102
+ 6.4.89 hostname 102
6.4.90 ignore_list_reply_to 102
- 6.4.91 imap_authenticators 102
- 6.4.92 imap_check_subscribed 102
- 6.4.93 imap_delim_chars 102
+ 6.4.91 imap_authenticators 103
+ 6.4.92 imap_check_subscribed 103
+ 6.4.93 imap_delim_chars 103
6.4.94 imap_headers 103
- 6.4.95 imap_home_namespace 103
- 6.4.96 imap_keepalive 103
+ 6.4.95 imap_home_namespace 104
+ 6.4.96 imap_keepalive 104
6.4.97 imap_list_subscribed 104
- 6.4.98 imap_login 104
- 6.4.99 imap_mail_check 104
- 6.4.100 imap_pass 104
+ 6.4.98 imap_login 105
+ 6.4.99 imap_mail_check 105
+ 6.4.100 imap_pass 105
6.4.101 imap_passive 105
6.4.102 imap_peek 105
- 6.4.103 imap_reconnect 105
- 6.4.104 imap_servernoise 105
- 6.4.105 imap_user 105
+ 6.4.103 imap_reconnect 106
+ 6.4.104 imap_servernoise 106
+ 6.4.105 imap_user 106
6.4.106 implicit_autoview 106
- 6.4.107 include 106
- 6.4.108 include_onlyfirst 106
- 6.4.109 indent_string 106
- 6.4.110 index_format 106
- 6.4.111 ispell 109
- 6.4.112 keep_flagged 109
- 6.4.113 list_reply 109
+ 6.4.107 include 107
+ 6.4.108 include_onlyfirst 107
+ 6.4.109 indent_string 107
+ 6.4.110 index_format 107
+ 6.4.111 ispell 110
+ 6.4.112 keep_flagged 110
+ 6.4.113 list_reply 110
6.4.114 locale 110
- 6.4.115 mail_check 110
- 6.4.116 mailcap_path 110
- 6.4.117 mailcap_sanitize 110
- 6.4.118 maildir_header_cache_verify 110
+ 6.4.115 mail_check 111
+ 6.4.116 mailcap_path 111
+ 6.4.117 mailcap_sanitize 111
+ 6.4.118 maildir_header_cache_verify 111
6.4.119 maildir_trash 111
- 6.4.120 mark_old 111
- 6.4.121 markers 111
- 6.4.122 mask 111
+ 6.4.120 mark_old 112
+ 6.4.121 markers 112
+ 6.4.122 mask 112
6.4.123 max_line_length 112
6.4.124 mbox 112
- 6.4.125 mbox_type 112
- 6.4.126 menu_context 112
- 6.4.127 menu_move_off 112
+ 6.4.125 mbox_type 113
+ 6.4.126 menu_context 113
+ 6.4.127 menu_move_off 113
v
- 6.4.128 menu_scroll 112
+ 6.4.128 menu_scroll 113
6.4.129 message_format 113
- 6.4.130 meta_key 113
- 6.4.131 metoo 113
- 6.4.132 mh_purge 113
- 6.4.133 mh_seq_flagged 113
+ 6.4.130 meta_key 114
+ 6.4.131 metoo 114
+ 6.4.132 mh_purge 114
+ 6.4.133 mh_seq_flagged 114
6.4.134 mh_seq_replied 114
6.4.135 mh_seq_unseen 114
- 6.4.136 mime_forward 114
- 6.4.137 mime_forward_decode 114
- 6.4.138 mime_forward_rest 114
- 6.4.139 mix_entry_format 114
- 6.4.140 mixmaster 115
- 6.4.141 move 115
- 6.4.142 msgid_format 115
- 6.4.143 narrow_tree 116
+ 6.4.136 mime_forward 115
+ 6.4.137 mime_forward_decode 115
+ 6.4.138 mime_forward_rest 115
+ 6.4.139 mix_entry_format 115
+ 6.4.140 mixmaster 116
+ 6.4.141 move 116
+ 6.4.142 msgid_format 116
+ 6.4.143 narrow_tree 117
6.4.144 nntp_ask_followup_to 117
6.4.145 nntp_ask_x_comment_to 117
- 6.4.146 nntp_cache_dir 117
- 6.4.147 nntp_catchup 117
- 6.4.148 nntp_context 117
+ 6.4.146 nntp_cache_dir 118
+ 6.4.147 nntp_catchup 118
+ 6.4.148 nntp_context 118
6.4.149 nntp_followup_to_poster 118
- 6.4.150 nntp_group_index_format 118
- 6.4.151 nntp_host 118
+ 6.4.150 nntp_group_index_format 119
+ 6.4.151 nntp_host 119
6.4.152 nntp_inews 119
- 6.4.153 nntp_load_description 119
- 6.4.154 nntp_mail_check 119
+ 6.4.153 nntp_load_description 120
+ 6.4.154 nntp_mail_check 120
6.4.155 nntp_mime_subject 120
6.4.156 nntp_newsrc 120
- 6.4.157 nntp_pass 120
- 6.4.158 nntp_post_moderated 120
+ 6.4.157 nntp_pass 121
+ 6.4.158 nntp_post_moderated 121
6.4.159 nntp_reconnect 121
- 6.4.160 nntp_save_unsubscribed 121
- 6.4.161 nntp_show_new_news 121
- 6.4.162 nntp_show_only_unread 121
- 6.4.163 nntp_user 121
+ 6.4.160 nntp_save_unsubscribed 122
+ 6.4.161 nntp_show_new_news 122
+ 6.4.162 nntp_show_only_unread 122
+ 6.4.163 nntp_user 122
6.4.164 nntp_x_comment_to 122
- 6.4.165 operating_system 122
- 6.4.166 pager 122
- 6.4.167 pager_context 122
+ 6.4.165 operating_system 123
+ 6.4.166 pager 123
+ 6.4.167 pager_context 123
6.4.168 pager_format 123
6.4.169 pager_index_lines 123
- 6.4.170 pager_stop 123
- 6.4.171 pgp_auto_decode 123
- 6.4.172 pgp_autoinline 123
- 6.4.173 pgp_check_exit 124
- 6.4.174 pgp_clearsign_command 124
- 6.4.175 pgp_decode_command 124
+ 6.4.170 pager_stop 124
+ 6.4.171 pgp_auto_decode 124
+ 6.4.172 pgp_autoinline 124
+ 6.4.173 pgp_check_exit 125
+ 6.4.174 pgp_clearsign_command 125
+ 6.4.175 pgp_decode_command 125
6.4.176 pgp_decrypt_command 125
- 6.4.177 pgp_encrypt_only_command 125
- 6.4.178 pgp_encrypt_sign_command 125
- 6.4.179 pgp_entry_format 125
- 6.4.180 pgp_export_command 126
+ 6.4.177 pgp_encrypt_only_command 126
+ 6.4.178 pgp_encrypt_sign_command 126
+ 6.4.179 pgp_entry_format 126
+ 6.4.180 pgp_export_command 127
vi
- 6.4.181 pgp_getkeys_command 126
- 6.4.182 pgp_good_sign 126
- 6.4.183 pgp_ignore_subkeys 126
+ 6.4.181 pgp_getkeys_command 127
+ 6.4.182 pgp_good_sign 127
+ 6.4.183 pgp_ignore_subkeys 127
6.4.184 pgp_import_command 127
- 6.4.185 pgp_list_pubring_command 127
- 6.4.186 pgp_list_secring_command 127
- 6.4.187 pgp_long_ids 127
- 6.4.188 pgp_mime_auto 127
+ 6.4.185 pgp_list_pubring_command 128
+ 6.4.186 pgp_list_secring_command 128
+ 6.4.187 pgp_long_ids 128
+ 6.4.188 pgp_mime_auto 128
6.4.189 pgp_replyinline 128
- 6.4.190 pgp_retainable_sigs 128
- 6.4.191 pgp_show_unusable 128
- 6.4.192 pgp_sign_as 128
+ 6.4.190 pgp_retainable_sigs 129
+ 6.4.191 pgp_show_unusable 129
+ 6.4.192 pgp_sign_as 129
6.4.193 pgp_sign_command 129
- 6.4.194 pgp_sort_keys 129
- 6.4.195 pgp_strict_enc 129
- 6.4.196 pgp_timeout 129
+ 6.4.194 pgp_sort_keys 130
+ 6.4.195 pgp_strict_enc 130
+ 6.4.196 pgp_timeout 130
6.4.197 pgp_use_gpg_agent 130
- 6.4.198 pgp_verify_command 130
- 6.4.199 pgp_verify_key_command 130
- 6.4.200 pipe_decode 130
- 6.4.201 pipe_sep 130
- 6.4.202 pipe_split 130
+ 6.4.198 pgp_verify_command 131
+ 6.4.199 pgp_verify_key_command 131
+ 6.4.200 pipe_decode 131
+ 6.4.201 pipe_sep 131
+ 6.4.202 pipe_split 131
6.4.203 pop_auth_try_all 131
- 6.4.204 pop_authenticators 131
- 6.4.205 pop_delete 131
- 6.4.206 pop_host 131
- 6.4.207 pop_last 132
- 6.4.208 pop_mail_check 132
- 6.4.209 pop_pass 132
- 6.4.210 pop_reconnect 132
+ 6.4.204 pop_authenticators 132
+ 6.4.205 pop_delete 132
+ 6.4.206 pop_host 132
+ 6.4.207 pop_last 133
+ 6.4.208 pop_mail_check 133
+ 6.4.209 pop_pass 133
+ 6.4.210 pop_reconnect 133
6.4.211 pop_user 133
- 6.4.212 post_indent_string 133
- 6.4.213 postpone 133
- 6.4.214 postponed 133
- 6.4.215 preconnect 133
- 6.4.216 print 134
- 6.4.217 print_command 134
- 6.4.218 print_decode 134
- 6.4.219 print_split 134
+ 6.4.212 post_indent_string 134
+ 6.4.213 postpone 134
+ 6.4.214 postponed 134
+ 6.4.215 preconnect 134
+ 6.4.216 print 135
+ 6.4.217 print_command 135
+ 6.4.218 print_decode 135
+ 6.4.219 print_split 135
6.4.220 prompt_after 135
- 6.4.221 query_command 135
- 6.4.222 quit 135
- 6.4.223 quote_empty 135
- 6.4.224 quote_quoted 135
+ 6.4.221 query_command 136
+ 6.4.222 quit 136
+ 6.4.223 quote_empty 136
+ 6.4.224 quote_quoted 136
6.4.225 quote_regexp 136
- 6.4.226 read_inc 136
- 6.4.227 read_only 136
- 6.4.228 realname 136
- 6.4.229 recall 136
+ 6.4.226 read_inc 137
+ 6.4.227 read_only 137
+ 6.4.228 realname 137
+ 6.4.229 recall 137
6.4.230 record 137
- 6.4.231 reply_regexp 137
- 6.4.232 reply_self 137
- 6.4.233 reply_to 137
+ 6.4.231 reply_regexp 138
+ 6.4.232 reply_self 138
+ 6.4.233 reply_to 138
vii
6.4.234 resolve 138
- 6.4.235 reverse_alias 138
- 6.4.236 reverse_name 138
- 6.4.237 reverse_realname 138
+ 6.4.235 reverse_alias 139
+ 6.4.236 reverse_name 139
+ 6.4.237 reverse_realname 139
6.4.238 rfc2047_parameters 139
- 6.4.239 save_address 139
- 6.4.240 save_empty 139
- 6.4.241 save_name 139
- 6.4.242 score 140
- 6.4.243 score_threshold_delete 140
- 6.4.244 score_threshold_flag 140
- 6.4.245 score_threshold_read 140
- 6.4.246 send_charset 140
- 6.4.247 sendmail 141
- 6.4.248 sendmail_wait 141
- 6.4.249 shell 141
+ 6.4.239 save_address 140
+ 6.4.240 save_empty 140
+ 6.4.241 save_name 140
+ 6.4.242 score 141
+ 6.4.243 score_threshold_delete 141
+ 6.4.244 score_threshold_flag 141
+ 6.4.245 score_threshold_read 141
+ 6.4.246 send_charset 141
+ 6.4.247 sendmail 142
+ 6.4.248 sendmail_wait 142
+ 6.4.249 shell 142
6.4.250 sidebar_boundary 142
- 6.4.251 sidebar_delim 142
- 6.4.252 sidebar_newmail_only 142
- 6.4.253 sidebar_number_format 142
- 6.4.254 sidebar_shorten_hierarchy 143
- 6.4.255 sidebar_visible 143
- 6.4.256 sidebar_width 143
- 6.4.257 sig_dashes 143
+ 6.4.251 sidebar_delim 143
+ 6.4.252 sidebar_newmail_only 143
+ 6.4.253 sidebar_number_format 143
+ 6.4.254 sidebar_shorten_hierarchy 144
+ 6.4.255 sidebar_visible 144
+ 6.4.256 sidebar_width 144
+ 6.4.257 sig_dashes 144
6.4.258 sig_on_top 144
- 6.4.259 signature 144
- 6.4.260 signoff_string 144
- 6.4.261 simple_search 144
+ 6.4.259 signature 145
+ 6.4.260 signoff_string 145
+ 6.4.261 simple_search 145
6.4.262 sleep_time 145
- 6.4.263 smart_wrap 145
- 6.4.264 smileys 145
- 6.4.265 smime_ask_cert_label 145
- 6.4.266 smime_ca_location 145
- 6.4.267 smime_certificates 145
- 6.4.268 smime_decrypt_command 146
- 6.4.269 smime_decrypt_use_default_key 146
+ 6.4.263 smart_wrap 146
+ 6.4.264 smileys 146
+ 6.4.265 smime_ask_cert_label 146
+ 6.4.266 smime_ca_location 146
+ 6.4.267 smime_certificates 146
+ 6.4.268 smime_decrypt_command 147
+ 6.4.269 smime_decrypt_use_default_key 147
6.4.270 smime_default_key 147
- 6.4.271 smime_encrypt_command 147
- 6.4.272 smime_encrypt_with 147
- 6.4.273 smime_get_cert_command 147
- 6.4.274 smime_get_cert_email_command 147
- 6.4.275 smime_get_signer_cert_command 147
- 6.4.276 smime_import_cert_command 148
- 6.4.277 smime_is_default 148
- 6.4.278 smime_keys 148
- 6.4.279 smime_pk7out_command 148
+ 6.4.271 smime_encrypt_command 148
+ 6.4.272 smime_encrypt_with 148
+ 6.4.273 smime_get_cert_command 148
+ 6.4.274 smime_get_cert_email_command 148
+ 6.4.275 smime_get_signer_cert_command 148
+ 6.4.276 smime_import_cert_command 149
+ 6.4.277 smime_is_default 149
+ 6.4.278 smime_keys 149
+ 6.4.279 smime_pk7out_command 149
6.4.280 smime_sign_command 149
- 6.4.281 smime_sign_opaque_command 149
- 6.4.282 smime_timeout 149
- 6.4.283 smime_verify_command 149
- 6.4.284 smime_verify_opaque_command 149
- 6.4.285 smtp_host 149
- 6.4.286 smtp_pass 150
+ 6.4.281 smime_sign_opaque_command 150
+ 6.4.282 smime_timeout 150
+ 6.4.283 smime_verify_command 150
+ 6.4.284 smime_verify_opaque_command 150
+ 6.4.285 smtp_envelope 150
+ 6.4.286 smtp_host 150
viii
- 6.4.287 smtp_port 150
- 6.4.288 smtp_use_tls 150
- 6.4.289 smtp_user 150
- 6.4.290 sort 151
- 6.4.291 sort_alias 151
- 6.4.292 sort_aux 151
- 6.4.293 sort_browser 152
- 6.4.294 sort_re 152
- 6.4.295 spam_separator 152
- 6.4.296 spoolfile 153
- 6.4.297 ssl_ca_certificates_file 153
- 6.4.298 ssl_client_cert 153
- 6.4.299 ssl_force_tls 153
- 6.4.300 ssl_min_dh_prime_bits 153
- 6.4.301 ssl_starttls 154
- 6.4.302 ssl_use_sslv2 154
- 6.4.303 ssl_use_sslv3 154
- 6.4.304 ssl_use_tlsv1 154
- 6.4.305 ssl_usesystemcerts 154
- 6.4.306 status_chars 155
- 6.4.307 status_format 155
- 6.4.308 status_on_top 157
- 6.4.309 strict_mailto 157
- 6.4.310 strict_mime 158
- 6.4.311 strict_threads 158
- 6.4.312 strip_was 158
- 6.4.313 strip_was_regex 158
- 6.4.314 stuff_quoted 159
- 6.4.315 suspend 159
- 6.4.316 text_flowed 159
- 6.4.317 thorough_search 159
- 6.4.318 thread_received 159
- 6.4.319 tilde 160
- 6.4.320 timeout 160
- 6.4.321 tmpdir 160
- 6.4.322 to_chars 160
- 6.4.323 trash 160
- 6.4.324 tunnel 161
- 6.4.325 umask 161
- 6.4.326 uncollapse_jump 161
- 6.4.327 use_8bitmime 161
- 6.4.328 use_domain 161
- 6.4.329 use_from 162
- 6.4.330 use_idn 162
- 6.4.331 use_ipv6 162
- 6.4.332 user_agent 162
- 6.4.333 visual 162
- 6.4.334 wait_key 163
- 6.4.335 weed 163
- 6.4.336 wrap_search 163
- 6.4.337 wrapmargin 163
- 6.4.338 write_bcc 163
- 6.4.339 write_inc 164
+ 6.4.287 smtp_pass 151
+ 6.4.288 smtp_port 151
+ 6.4.289 smtp_use_tls 151
+ 6.4.290 smtp_user 152
+ 6.4.291 sort 152
+ 6.4.292 sort_alias 152
+ 6.4.293 sort_aux 152
+ 6.4.294 sort_browser 153
+ 6.4.295 sort_re 153
+ 6.4.296 spam_separator 154
+ 6.4.297 spoolfile 154
+ 6.4.298 ssl_ca_certificates_file 154
+ 6.4.299 ssl_client_cert 154
+ 6.4.300 ssl_force_tls 154
+ 6.4.301 ssl_min_dh_prime_bits 155
+ 6.4.302 ssl_starttls 155
+ 6.4.303 ssl_use_sslv2 155
+ 6.4.304 ssl_use_sslv3 155
+ 6.4.305 ssl_use_tlsv1 155
+ 6.4.306 ssl_usesystemcerts 156
+ 6.4.307 status_chars 156
+ 6.4.308 status_format 156
+ 6.4.309 status_on_top 158
+ 6.4.310 strict_mailto 159
+ 6.4.311 strict_mime 159
+ 6.4.312 strict_threads 159
+ 6.4.313 strip_was 159
+ 6.4.314 strip_was_regex 160
+ 6.4.315 stuff_quoted 160
+ 6.4.316 suspend 160
+ 6.4.317 text_flowed 160
+ 6.4.318 thorough_search 160
+ 6.4.319 thread_received 161
+ 6.4.320 tilde 161
+ 6.4.321 timeout 161
+ 6.4.322 tmpdir 161
+ 6.4.323 to_chars 161
+ 6.4.324 trash 162
+ 6.4.325 tunnel 162
+ 6.4.326 umask 162
+ 6.4.327 uncollapse_jump 162
+ 6.4.328 use_8bitmime 162
+ 6.4.329 use_domain 163
+ 6.4.330 use_from 163
+ 6.4.331 use_idn 163
+ 6.4.332 use_ipv6 163
+ 6.4.333 user_agent 163
+ 6.4.334 visual 164
+ 6.4.335 wait_key 164
+ 6.4.336 weed 164
+ 6.4.337 wrap_search 164
+ 6.4.338 wrapmargin 164
+ 6.4.339 write_bcc 165
ix
- 6.4.340 xterm_icon 164
- 6.4.341 xterm_leave 164
- 6.4.342 xterm_set_titles 164
- 6.4.343 xterm_title 164
- 6.5 Functions ....................................................... 165
- 6.5.1 generic 165
- 6.5.2 index 166
- 6.5.3 pager 168
- 6.5.4 alias 170
- 6.5.5 query 170
- 6.5.6 attach 170
- 6.5.7 compose 171
- 6.5.8 postpone 172
- 6.5.9 browser 172
- 6.5.10 pgp 173
- 6.5.11 editor 173
-
- 7. Miscellany ............................................................ 173
- 7.1 Acknowledgments ................................................. 174
- 7.2 About this document ............................................. 176
+ 6.4.340 write_inc 165
+ 6.4.341 xterm_icon 165
+ 6.4.342 xterm_leave 165
+ 6.4.343 xterm_set_titles 165
+ 6.4.344 xterm_title 166
+ 6.5 Functions ....................................................... 166
+ 6.5.1 generic 166
+ 6.5.2 index 167
+ 6.5.3 pager 169
+ 6.5.4 alias 171
+ 6.5.5 query 171
+ 6.5.6 attach 171
+ 6.5.7 compose 172
+ 6.5.8 postpone 173
+ 6.5.9 browser 173
+ 6.5.10 pgp 174
+ 6.5.11 editor 174
+
+ 7. Miscellany ............................................................ 174
+ 7.1 Acknowledgments ................................................. 175
+ 7.2 About this document ............................................. 177
x