+\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.323 , page 160) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.323 , page 162) variable.
+
message is to you and you only
The Mutt Next Generation E-Mail Client 11
Mutt-ng uses these attributes for handling text/enriched messages, and they can
- also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 74) script for high-
+ also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 75) script for high-
lighting purposes. N\bNo\bot\bte\be:\b: If you change the colors for your display, for exam-
ple by changing the color associated with color2 for your xterm, then that
color will be used instead of green.
_\b2_\b._\b5_\b._\b3 _\bT_\bh_\br_\be_\ba_\bd_\be_\bd _\bM_\bo_\bd_\be
- When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 6.4.291 , page 150) 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 152) 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 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
+ tion 6.4.110 , page 108). 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 108) 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.312 , page 158).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 6.4.312 , page 160).
_\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 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
+ the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 83) 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 83) does not
add the aliases specified there-in, you must also _\bs_\bo_\bu_\br_\bc_\be (section 3.28 , page
42) the file.
lost upon changing folders.
Note that this command is also available on the _\bc_\bo_\bm_\bp_\bo_\bs_\be _\bm_\be_\bn_\bu (section 5.1.3 ,
- page 67). There, it's used to fine-tune the properties of attachments you are
+ page 68). There, it's used to fine-tune the properties of attachments you are
going to send.
e\ben\bnt\bte\ber\br-\b-c\bco\bom\bmm\bma\ban\bnd\bd
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 101) 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 103) 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 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
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.200 , page 131), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 6.4.202 , page 132), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 6.4.201 , page 132) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 164) 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.336 , page 163) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 6.4.336 , page 165) 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.335 , page 162) can be used to control whether Mutt-ng will wait for a key
+ 6.4.335 , page 164) 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 135) 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 137) 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.308 , page 155) 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 157) 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 93).
+ Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 95).
_\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 128) permanently.
+ _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.4.192 , page 130) 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 125)) have obvious meanings. But some explana-
+ _\bm_\ba_\bt (section 6.4.179 , page 127)) 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 114)). Most important is the ``middleman'' capability, indicated by a
+ page 116)). 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 133) variable. This means that you can
+ the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 6.4.214 , page 135) 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 133) quad-option.
+ See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.4.213 , page 134) quad-option.
_\b3_\b. _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn
out of the box, it is often desirable to tailor Mutt-ng to suit your own
tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
configuration file (defaults set by your local system administrator), unless
- the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 6.1 , page 76) option is specified. This
+ the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 6.1 , page 77) option is specified. This
file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
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 81)
+ 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 83)
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 93) variable set.
+ (section 6.4.54 , page 95) 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 165). The special
+ list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 6.5 , page 166). 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
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.297 , page
- 152) at the beginning of the pattern, you must place it inside of double or
+ 154) 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 165).
+ 6.5 , page 166).
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 135) in the
+ +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.225 , page 137) 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 137).)
+ _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 6.4.233 , page 139).)
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 96)
+ lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 6.4.66 , page 98)
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 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.
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 97) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 6.4.297 , page 154)) 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 93) 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 95) 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.
Usage: fcc-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is used to save outgoing mail in a mailbox other than _\b$_\br_\be_\bc_\bo_\br_\bd
- (section 6.4.230 , page 136). Mutt-ng searches the initial list of message
+ (section 6.4.230 , page 138). Mutt-ng searches the initial list of message
recipients for the first matching _\br_\be_\bg_\be_\bx_\bp and uses _\bm_\ba_\bi_\bl_\bb_\bo_\bx as the default Fcc:
mailbox. If no match is found the message will be saved to _\b$_\br_\be_\bc_\bo_\br_\bd (section
- 6.4.230 , page 136) mailbox.
+ 6.4.230 , page 138) mailbox.
See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 53) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
send2-hook is matched every time a message is changed, either by editing it, or
by using the compose menu to change its recipients or subject. send2-hook is
executed after send-hook, and can, e.g., be used to set parameters such as the
- _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page 140) variable depending on the message's
+ _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page 142) variable depending on the message's
sender address.
For each type of send-hook or reply-hook, when multiple matches occur, commands
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 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
+ _\bt_\bi_\bo_\bn (section 6.4.15 , page 86), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 145) and
+ _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 111) 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 165). ``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 166). ``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 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
+ tion 6.4.244 , page 142), _\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 142),
+ _\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 141) 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 142) 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 141) 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 106) variable.
+ the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108) variable.
(Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
given message.)
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 104),
+ 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 105),
use:
ifdef imap_mail_check 'set imap_mail_check = 300'
Provided for completeness is the test for menu names. To set _\b$_\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
- (section 6.4.169 , page 122) only if the pager menu is available, use:
+ (section 6.4.169 , page 124) only if the pager menu is available, use:
ifdef pager 'set pager_index_lines = 10'
ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
+ _\b3_\b._\b3_\b1 _\bO_\bb_\bs_\bo_\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+
+ In the process of ensuring and creating more consistency, many variables have
+ been renamed and some of the old names were already removed. Please see _\bO_\bb_\bs_\bo_\b-
+ _\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 6.4 , page 81) for a complete list.
+
_\b4_\b. _\bA_\bd_\bv_\ba_\bn_\bc_\be_\bd _\bU_\bs_\ba_\bg_\be
_\b4_\b._\b1 _\bR_\be_\bg_\bu_\bl_\ba_\br _\bE_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs
All string patterns in Mutt-ng including those in more complex _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
- tion 6.2 , page 77) must be specified using regular expressions (regexp) in
+ tion 6.2 , page 78) must be specified using regular expressions (regexp) in
the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
and GNU awk). For your convenience, we have included below a brief description
of this syntax.
ace it with \ (backslash).
The fundamental building blocks are the regular expressions that match a single
+
+ The Mutt Next Generation E-Mail Client 46
+
character. Most characters, including all letters and digits, are regular
expressions that match themselves. Any metacharacter with special meaning may
be quoted by preceding it with a backslash.
sign ``$'' are metacharacters that respectively match the empty string at the
beginning and end of a line.
- The Mutt Next Generation E-Mail Client 46
-
A list of characters enclosed by ``['' and ``]'' matches any single character
in that list; if the first character of the list is a caret ``^'' then it
matches any character n\bno\bot\bt in the list. For example, the regular expression
[:space:]
Space characters (such as space, tab and formfeed, to name a few).
+ The Mutt Next Generation E-Mail Client 47
+
[:upper:]
Upper-case alphabetic characters.
A character class is only valid in a regular expression inside the brackets of
a character list. Note that the brackets in these class names are part of the
-
- The Mutt Next Generation E-Mail Client 47
-
symbolic names, and must be included in addition to the brackets delimiting the
bracket list. For example, [\b[[\b[:\b:d\bdi\big\bgi\bit\bt:\b:]\b]]\b] is equivalent to [\b[0\b0-\b-9\b9]\b].
The preceding item is matched at least _\bn times, but no more than _\bm
times.
+ The Mutt Next Generation E-Mail Client 48
+
Two regular expressions may be concatenated; the resulting regular expression
matches any string formed by concatenating two substrings that respectively
match the concatenated subexpressions.
ing regular expression matches any string matching either subexpression.
Repetition takes precedence over concatenation, which in turn takes precedence
-
- The Mutt Next Generation E-Mail Client 48
-
over alternation. A whole subexpression may be enclosed in parentheses to
override these precedence rules.
to match messages, e.g. for operations like tagging and scoring. A pattern con-
sists of one or more sub-pattern, which can be logically grouped, ORed, and
negated. For a complete listing of these patterns, please refer to table _\bP_\ba_\bt_\b-
- _\bt_\be_\br_\bn_\bs (section 6.2 , page 77) in the Reference chapter.
+ _\bt_\be_\br_\bn_\bs (section 6.2 , page 78) in the Reference chapter.
It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
+
+ The Mutt Next Generation E-Mail Client 49
+
expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
possible.
most simple possibility is to logically AND several patterns by stringing them
together:
- The Mutt Next Generation E-Mail Client 49
-
~s 'SPAM' ~U
The pattern above matches all messages that contain ``SPAM'' in the subject and
~d 28/12/2004*1d
The first pattern matches all dates between January 1st, 2005 and January 1st
+
+ The Mutt Next Generation E-Mail Client 50
+
2006. The second pattern matches all dates between October 18th, 2004 and
October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
date ranges between a fixed number of units and the current date. How this
works can be seen in the following example:
- The Mutt Next Generation E-Mail Client 50
-
~d >2w # messages older than two weeks
~d <3d # messages newer than 3 days
~d =1m # messages that are exactly one month old
+\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.308 , page 155) variable. For the hostname and version
+ _\bm_\ba_\bt (section 6.4.308 , page 157) 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:
In the index, there're more useful information one could want to see:
+ The Mutt Next Generation E-Mail Client 51
+
+\bo which mailbox is open
+\bo how man new, flagged or postponed messages
To include the mailbox' name is as easy as:
- The Mutt Next Generation E-Mail Client 51
-
set status_format = "%v on %h: %B: ...
When the currently opened mailbox is Inbox, this will be expanded to:
%?<item>?<string if nonzero>&<string if zero>?
+ The Mutt Next Generation E-Mail Client 52
+
Using this we can make mutt-ng to do the following:
+\bo make it print ``_\bn new messages'' whereby _\bn is the count but only if there
+\bo and make it print ``no new messages'' if there aren't any
- The Mutt Next Generation E-Mail Client 52
-
The corresponding configuration is:
set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
Since the previous expando stops at the end of line, there must be
a way to fill the gap between two items via the %>X expando: it
puts as many characters X in between two items so that the rest of
- the line will be right-justified. For example, to not put the ver-
- sion string and hostname of our example on the left but on the
+ the line will be right-justified. For example, to not put the
+
+ The Mutt Next Generation E-Mail Client 53
+
+ version string and hostname of our example on the left but on the
right and fill the gap with spaces, one might use (note the space
after %>):
set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
- The Mutt Next Generation E-Mail Client 53
-
_\b4_\b._\b4 _\bU_\bs_\bi_\bn_\bg _\bT_\ba_\bg_\bs
Sometimes it is desirable to perform an operation on a group of messages all at
ject. To tag all messages matching a pattern, use the tag-pattern function,
which is bound to ``shift-T'' by default. Or you can select individual mes-
sages by hand using the ``tag-message'' function, which is bound to ``t'' by
- default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 6.2 , page 77) for Mutt-ng's pattern matching
+ default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 6.2 , page 78) for Mutt-ng's pattern matching
syntax.
Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
operator is used, the n\bne\bex\bxt\bt operation will be applied to all tagged messages if
that operation can be used in that manner. If the _\b$_\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg (section 6.4.16 ,
- page 85) variable is set, the next operation applies to the tagged messages
+ page 87) 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,
arbitrary commands before performing some operation. For example, you may wish
to tailor your configuration based upon which mailbox you are reading, or to
whom you are sending mail. In the Mutt-ng world, a _\bh_\bo_\bo_\bk consists of a _\br_\be_\bg_\bu_\bl_\ba_\br
- _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 44) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 6.2 , page 77) along
+ _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 44) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 6.2 , page 78) along
with a configuration option/command. See
+\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 26)
+\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 37)
+ The Mutt Next Generation E-Mail Client 54
+
+\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 35)
+\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 33)
N\bNo\bot\bte\be:\b: if a hook changes configuration settings, these changes remain effective
until the end of the current mutt session. As this is generally not desired, a
default hook needs to be added before all other hooks to restore configuration
-
- The Mutt Next Generation E-Mail Client 54
-
defaults. Here is an example with send-hook and the my_hdr directive:
send-hook . 'unmy_hdr From:'
messages a finer grain of control is needed for matching since for different
purposes you want to match different criteria.
- Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 6.2 , page 77) language
+ Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 6.2 , page 78) language
for matching messages in hook commands. This works in exactly the same way as
it would when _\bl_\bi_\bm_\bi_\bt_\bi_\bn_\bg or _\bs_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg the mailbox, except that you are restricted
to those operators which match information mutt extracts from the header of the
searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the
other hooks, in which case Mutt-ng will translate your pattern into the full
language, using the translation specified by the _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section
- 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
+ 6.4.45 , page 93) 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 93) 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
+ The Mutt Next Generation E-Mail Client 55
+
The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
which looks very similar to the ones you probably know from GUI mail clients.
The sidebar lists all specified mailboxes, shows the number in each and high-
If you want to specify the mailboxes you can do so with:
- The Mutt Next Generation E-Mail Client 55
-
set mbox='=INBOX'
mailboxes INBOX \
MBOX1 \
_\b4_\b._\b7 _\bE_\bx_\bt_\be_\br_\bn_\ba_\bl _\bA_\bd_\bd_\br_\be_\bs_\bs _\bQ_\bu_\be_\br_\bi_\be_\bs
+ The Mutt Next Generation E-Mail Client 56
+
Mutt-ng supports connecting to external directory databases such as LDAP,
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
- simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.221 , page 134) vari-
+ simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.221 , page 136) vari-
able, you specify the wrapper command to use. For example:
set query_command = "mutt_ldap_query.pl '%s'"
The wrapper script should accept the query on the command-line. It should
return a one line message, then each matching response on a single line, each
-
- The Mutt Next Generation E-Mail Client 56
-
line containing a tab separated address then name then some other optional
information. On error, or if there are no matching addresses, return a non-
zero exit code and a one line error message.
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 112)
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.4.125 , page 113)
variable.
m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All messages are
From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
+ The Mutt Next Generation E-Mail Client 57
+
to denote the start of a new message (this is often referred to as the
``From_'' line).
M\bMH\bH. A radical departure from _\bm_\bb_\bo_\bx and _\bM_\bM_\bD_\bF, a mailbox consists of a directory
and each message is stored in a separate file. The filename indicates the mes-
sage number (however, this is may not correspond to the message number Mutt-ng
-
- The Mutt Next Generation E-Mail Client 57
-
displays). Deleted messages are renamed with a comma (,) prepended to the file-
name. N\bNo\bot\bte\be:\b: Mutt detects this type of mailbox by looking for either
.mh_sequences or .xmhcache (needed to distinguish normal directories from MH
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.297 , page 152) (incoming)
+ +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page 154) (incoming)
mailbox
- +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 111) file
+ +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 113) file
- +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 136) file
+ +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 138) file
+\bo ^ -- refers to the current mailbox
+\bo ~ -- refers to your home directory
- +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 95) directory
+ +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 97) 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
mail easier. The first thing you must do is to let Mutt know what addresses
you consider to be mailing lists (technically this does not have to be a mail-
ing list, but that is what it is most often used for), and what lists you are
+
+ The Mutt Next Generation E-Mail Client 58
+
subscribed to. This is accomplished through the use of the _\bl_\bi_\bs_\bt_\bs _\ba_\bn_\bd _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be
(section 3.12 , page 32) commands in your muttrc.
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 106) variable, the escape
+ box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108) variable, the escape
``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
-
- The Mutt Next Generation E-Mail Client 58
-
field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
returns the name of the author).
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 96) 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 98) 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 101) configuration variable is set. Using list-reply
+ (section 6.4.88 , page 103) 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 137) variable to help decide which address to use. If set to
+ 6.4.233 , page 139) 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 106) variable's ``%y'' and ``%Y''
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108) variable's ``%y'' and ``%Y''
+
+ The Mutt Next Generation E-Mail Client 59
+
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.291 , page 150) the mail-
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 6.4.291 , page 152) the mail-
box into _\bt_\bh_\br_\be_\ba_\bd_\bs (section 2.5.3 , page 11). A thread is a group of messages
which all relate to the same subject. This is usually organized into a tree-
- like structure where a message and all of its replies are represented
-
- The Mutt Next Generation E-Mail Client 59
-
- graphically. If you've ever used a threaded news client, this is the same con-
- cept. It makes dealing with large volume mailing lists easier because you can
- easily delete uninteresting threads and quickly find topics of value.
+ like structure where a message and all of its replies are represented graphi-
+ cally. If you've ever used a threaded news client, this is the same concept.
+ It makes dealing with large volume mailing lists easier because you can easily
+ delete uninteresting threads and quickly find topics of value.
_\b4_\b._\b1_\b1 _\bE_\bd_\bi_\bt_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
+\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
+
+ The Mutt Next Generation E-Mail Client 60
+
should be returned.
+\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
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 6.4.51 , page 94) 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
+ +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 6.4.52 , page 94) requests how much of your message
should be returned with the receipt (headers or full message).
Please see the reference chapter for possible values.
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 132) 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 133) 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 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).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.206 , page 133), 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 154).
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-
_\b4_\b._\b1_\b4 _\bI_\bM_\bA_\bP _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
+ The Mutt Next Generation E-Mail Client 61
+
If Mutt-ng was compiled with IMAP support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bi_\bm_\ba_\bp flag), it has the ability to work with folders located on a
remote IMAP server.
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.:
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 103) 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 105) 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 104) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.321 , page 160) 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 105) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.321 , page 161) 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
sages and subfolders. On Cyrus-like servers folders will often contain
both messages and subfolders.
+ The Mutt Next Generation E-Mail Client 62
+
+\bo For the case where an entry can contain both messages and subfolders, the
selection key (bound to enter by default) will choose to descend into the
subfolder view. If you wish to view the messages in that folder, you must
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,
There are a few variables which control authentication:
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 6.4.105 , page 105) - controls the username under
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 6.4.105 , page 107) - 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 104) - a password which you may pre-
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.100 , page 106) - 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 102) - 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 103) - 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).
newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
function from the index/pager which is by default bound to i.
- The Default newsserver can be obtained from the $NNTPSERVER environment vari-
- able. Like other news readers, info about subscribed newsgroups is saved in a
- file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 6.4.156 , page 119) variable.
+ The Default newsserver can be obtained from the $NNTPSERVER environment
+
+ The Mutt Next Generation E-Mail Client 63
+
+ variable. Like other news readers, info about subscribed newsgroups is saved in
+ a file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 6.4.156 , page 121) variable.
Article headers are cached and can be loaded from a file when a newsgroup is
entered instead loading from newsserver; currently, this caching mechanism
still is different from the header caching for maildir/IMAP.
Especially for Usenet, people often ask for advanced filtering and scoring
functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
-
- The Mutt Next Generation E-Mail Client 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).
_\b4_\b._\b1_\b6 _\bS_\bM_\bT_\bP _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
+
+ The Mutt Next Generation E-Mail Client 64
+
functionality. When configure was called with --with-libesmtp or the output
muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
support includes support for Delivery Status Notification (see _\bD_\be_\bl_\bi_\bv_\be_\br_\by _\bS_\bt_\ba_\bt_\bu_\bs
- _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 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).
+ _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 59) 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 163).
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.286 , page 149)
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.286 , page 151)
variable pointing to your SMTP server.
- 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.
+ page 152) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.287 , page 151) 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.289 , page 150) variable must be either set to
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 6.4.289 , page 152) 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.
+ page 151) 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)
macro index \cb |urlview\n
macro pager \cb |urlview\n
+ The Mutt Next Generation E-Mail Client 65
+
_\b4_\b._\b1_\b9 _\bC_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
If Mutt-ng was compiled with compressed folders support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\b-
an arbitrary format, provided that the user has a script to convert from/to
this format to one of the accepted.
- The Mutt Next Generation E-Mail Client 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
may be faster than converting the entire folder to the accepted format, append-
ing to it and converting back to the user-defined format.
- There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64), _\bc_\bl_\bo_\bs_\be_\b-
- _\bh_\bo_\bo_\bk (section 4.19.2 , page 65) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65))
+ There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 65), _\bc_\bl_\bo_\bs_\be_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.2 , page 65) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66))
which define commands to uncompress and compress a folder and to append mes-
sages to an existing compressed folder respectively.
append-hook \\.gz$ "gzip -c %t >> %f"
You do not have to specify all of the commands. If you omit _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (sec-
- tion 4.19.3 , page 65), the folder will be open and closed again each time you
+ tion 4.19.3 , page 66), 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
empty command) , the folder will be open in the mode. If you specify _\ba_\bp_\bp_\be_\bn_\bd_\b-
- _\bh_\bo_\bo_\bk (section 4.19.3 , page 65) though you'll be able to append to the folder.
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 66) though you'll be able to append to the folder.
Note that Mutt-ng will only try to use hooks if the file is not in one of the
accepted formats. In particular, if the file is empty, mutt supposes it is not
compressed. This is important because it allows the use of programs that do not
have well defined extensions. Just use '.' as a regexp. But this may be sur-
prising if your compressing script produces empty files. In this situation,
- unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 6.4.240 , page 139), so that the compressed file
+ unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 6.4.240 , page 141), 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
%f and %t can be repeated any number of times in the command string, and all of
the entries are replaced with the appropriate folder name. In addition, %% is
+
+ The Mutt Next Generation E-Mail Client 66
+
replaced by %, as in printf, and any other %anything is left as is.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should n\bno\bot\bt remove the original compressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should
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.
Usage: close-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
This is used to close the folder that was open with the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 64) command after some changes were made to it.
+ 4.19.1 , page 65) command after some changes were made to it.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd string is the command that can be used for closing the folders
whose names match _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 64) command. Temporary folder in this case is the folder previ-
- ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64) command.
+ 4.19.1 , page 65) command. Temporary folder in this case is the folder previ-
+ ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 65) command.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should n\bno\bot\bt remove the decompressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should return
non-zero exit status if it fails, so mutt knows something's wrong.
This command is used for saving to an existing compressed folder. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
is the command that can be used for appending to the folders whose names match
- _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64)
+ _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 65)
command. The temporary folder in this case contains the messages that are
being appended.
Example:
+ The Mutt Next Generation E-Mail Client 67
+
append-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,
+ When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66) 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 112)) type is always
-
- The Mutt Next Generation E-Mail Client 67
-
+ is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.4.125 , page 113)) type is always
supposed (i.e. this is the format used for the temporary folder).
If the file does not exist when you save to it, _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 ,
- page 65) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65). _\ba_\bp_\bp_\be_\bn_\bd_\b-
- _\bh_\bo_\bo_\bk (section 4.19.3 , page 65) is only for appending to existing folders.
+ page 65) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66). _\ba_\bp_\bp_\be_\bn_\bd_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 66) is only for appending to existing folders.
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type. In this
case, the folder will be open and closed again (using _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 64) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65)respectively) each
+ 4.19.1 , page 65) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65)respectively) each
time you will add to it.
_\b4_\b._\b1_\b9_\b._\b4 _\bE_\bn_\bc_\br_\by_\bp_\bt_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs
There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
(while viewing a message), the attachment menu and the compose menu.
+ The Mutt Next Generation E-Mail Client 68
+
_\b5_\b._\b1_\b._\b1 _\bV_\bi_\be_\bw_\bi_\bn_\bg _\bM_\bI_\bM_\bE _\bm_\be_\bs_\bs_\ba_\bg_\be_\bs _\bi_\bn _\bt_\bh_\be _\bp_\ba_\bg_\be_\br
When you select a message from the index and view it in the pager, Mutt decodes
the message to a text representation. Mutt-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
- 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
+ The Mutt Next Generation E-Mail Client 69
+
The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
or canceling) the message. It can be toggled with the toggle-unlink command
(default: u). The next field is the MIME content-type, and can be changed with
the edit-type command (default: ^T). The next field is the encoding for the
-
- 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
referred to as the mailcap format. Many MIME compliant programs utilize the
mailcap format, allowing you to specify handling for all MIME types in one
place for all programs. Programs known to use this format include Netscape,
+
+ The Mutt Next Generation E-Mail Client 70
+
XMosaic, lynx and metamail.
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
text/plain; more %s
+ The Mutt Next Generation E-Mail Client 71
+
Perhaps you would like to use lynx to interactively view a text/html message:
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
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 110) 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 112) 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.
text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
+ The Mutt Next Generation E-Mail Client 72
+
_\b5_\b._\b3_\b._\b3 _\bA_\bd_\bv_\ba_\bn_\bc_\be_\bd _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bU_\bs_\ba_\bg_\be
_\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:
needsterminal
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
+ tion 5.4 , page 75), 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 164) 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
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 164) 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.
edit=<command>
This flag specifies the command to use to edit a specific MIME
type. Mutt-ng supports this from the compose menu, and also uses
- it to compose new attachments. Mutt-ng will default to the defined
- editor for text attachments.
The Mutt Next Generation E-Mail Client 73
+ it to compose new attachments. Mutt-ng will default to the defined
+ editor for text attachments.
+
nametemplate=<template>
This field specifies the format for the file denoted by %s in the
command fields. Certain programs will require a certain file
Mutt-ng will skip the image/* entry and use the image/gif entry with the print
command.
- In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 74) to denote
+ In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 75) to denote
two commands for viewing an attachment, one to be viewed automatically, the
other to be viewed interactively from the attachment menu. In addition, you
can then use the test feature to determine which viewer to use interactively
depending on your environment.
- text/html; netscape -remote 'openURL(%s)' ; test=RunningX
- text/html; lynx %s; nametemplate=%s.html
-
The Mutt Next Generation E-Mail Client 74
+ text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+ text/html; lynx %s; nametemplate=%s.html
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
- For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 74), Mutt-ng will choose the third entry
+ For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 75), Mutt-ng will choose the third entry
because of the copiousoutput tag. For interactive viewing, Mutt will run the
program RunningX to determine if it should use the first entry. If the program
returns non-zero, Mutt-ng will use the second entry for interactive viewing.
alternative_order text/enriched text/plain text application/postscript image/*
Next, mutt will check if any of the types have a defined _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section
- 5.4 , page 74), and use that. Failing that, Mutt-ng will look for any text
+ 5.4 , page 75), and use that. Failing that, Mutt-ng will look for any text
type. As a last attempt, mutt will look for any type it knows how to handle.
To remove a MIME type from the alternative_order list, use the unalterna-
+\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.10 , page 30) [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 76) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 76) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 74) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 74) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+\bo _\bb_\bi_\bn_\bd (section 3.4 , page 24) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 37) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 76) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 76) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+\bo _\bm_\bo_\bn_\bo (section 3.8 , page 27) _\bo_\bb_\bj_\be_\bc_\bt _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
+\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 34) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
- +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 65) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 37) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
_\b6_\b._\b4 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+ The following list contains all variables which, in the process of providing
+ more consistency, have been renamed and are partially even removed already. The
+ left column contains the old synonym variables, the right column the full/new
+ name:
+
+ The Mutt Next Generation E-Mail Client 83
+
+ edit_hdrs edit_headers
+ forw_decode forward_decode
+ forw_format forward_format
+ forw_quote forward_quote
+ hdr_format index_format
+ indent_str indent_string
+ mime_fwd mime_forward
+ msg_format message_format
+ pgp_autosign crypt_autosign
+ pgp_autoencrypt crypt_autoencrypt
+ pgp_replyencrypt crypt_replyencrypt
+ pgp_replysign crypt_replysign
+ pgp_replysignencrypted crypt_replysignencrypted
+ pgp_verify_sig crypt_verify_sig
+ pgp_create_traditional pgp_autoinline
+ pgp_auto_traditional pgp_replyinline
+ forw_decrypt forward_decrypt
+ smime_sign_as smime_default_key
+ post_indent_str post_indent_string
+ print_cmd print_command
+ shorten_hierarchy sidebar_shorten_hierarchy
+ ask_followup_to nntp_ask_followup_to
+ ask_x_comment_to nntp_ask_x_comment_to
+ catchup_newsgroup nntp_catchup
+ followup_to_poster nntp_followup_to_poster
+ group_index_format nntp_group_index_format
+ inews nntp_inews
+ mime_subject nntp_mime_subject
+ news_cache_dir nntp_cache_dir
+ news_server nntp_host
+ newsrc nntp_newsrc
+ nntp_poll nntp_mail_check
+ pop_checkinterval pop_mail_check
+ post_moderated nntp_post_moderated
+ save_unsubscribed nntp_save_unsubscribed
+ show_new_news nntp_show_new_news
+ show_only_unread nntp_show_only_unread
+ x_comment_to nntp_x_comment_to
+ smtp_auth_username smtp_user
+ smtp_auth_password smtp_pass
+
+ The contrib subdirectory contains a script named update-config.pl which eases
+ migration.
+
+ A complete list of current variables follows.
+
_\b6_\b._\b4_\b._\b1 _\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\bs_\bu_\bb_\bj_\be_\bc_\bt
Type: quadoption
Default: ask-yes
If set to _\by_\be_\bs, when composing messages and no subject is given at the subject
+
+ The Mutt Next Generation E-Mail Client 84
+
prompt, composition will be aborted. If set to _\bn_\bo, composing messages with no
subject given at the subject prompt will never be aborted.
%a
alias name
- The Mutt Next Generation E-Mail Client 83
-
%f
flags - currently, a 'd' for an alias marked for deletion
Default: yes
+ The Mutt Next Generation E-Mail Client 85
+
Controls whether 8-bit data is converted to 7-bit using either quoted-printable
or base64 encoding when sending mail.
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
If _\bs_\be_\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
the body of an outgoing message.
+ The Mutt Next Generation E-Mail Client 86
+
_\b6_\b._\b4_\b._\b1_\b1 _\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
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.311 , page 158) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 6.4.311 , page 159) is unset.
_\b6_\b._\b4_\b._\b1_\b2 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
%D
deleted flag
- The Mutt Next Generation E-Mail Client 85
-
%d
description
%M
MIME subtype
+ The Mutt Next Generation E-Mail Client 87
+
%n
attachment number
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 84)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
+ page 86)'' 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 106)''.
+ on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108)''.
_\b6_\b._\b4_\b._\b1_\b6 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
+ The Mutt Next Generation E-Mail Client 88
+
Type: boolean
Default: no
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 93)'', 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 95)'', 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 94)''.
+ Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 6.4.60 , page 96)''.
_\b6_\b._\b4_\b._\b1_\b8 _\bb_\be_\be_\bp
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 85)'' variable.
+ tion 6.4.18 , page 87)'' variable.
_\b6_\b._\b4_\b._\b2_\b0 _\bb_\bo_\bu_\bn_\bc_\be
Type: boolean
+ The Mutt Next Generation E-Mail Client 89
+
Default: yes
When this variable is _\bs_\be_\bt, Mutt-ng will include Delivered-To: header fields
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
When _\bs_\be_\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
Especially with MH mailboxes, this operation can take quite some time since it
+
+ The Mutt Next Generation E-Mail Client 90
+
involves scanning the directory and checking each file to see if it has already
been looked at. If it's _\bu_\bn_\bs_\be_\bt, no check for new mail is performed while the
mailbox is open.
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.308 , page 155)'', 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 157)'', but has
its own set of printf(3)-like sequences:
%a
%v
Mutt-ng version string
- See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 155)''
-
- The Mutt Next Generation E-Mail Client 89
-
+ See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 157)''
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 87)''.
+ page 89)''.
_\b6_\b._\b4_\b._\b2_\b8 _\bc_\bo_\bn_\bf_\bi_\bg_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Default: yes
When _\bs_\be_\bt, Mutt-ng will prompt for confirmation when appending messages to an
+
+ The Mutt Next Generation E-Mail Client 91
+
existing mailbox.
_\b6_\b._\b4_\b._\b3_\b0 _\bc_\bo_\bn_\bf_\bi_\br_\bm_\bc_\br_\be_\ba_\bt_\be
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 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)''.
+ 138)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 141)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 6.4.68 , page 98)'' 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
going messages. This is probably only useful in connection to the _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk
command. It can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when encryption is not
required or signing is requested as well. If ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section
- 6.4.277 , page 147)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
+ 6.4.277 , page 149)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
messages and settings can be overridden by use of the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto
only)
+ The Mutt Next Generation E-Mail Client 92
+
_\b6_\b._\b4_\b._\b3_\b5 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bp_\bg_\bp
Type: boolean
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 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)''.
+ 6.4.34 , page 90)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 91)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 91)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 6.4.39 , page 91)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 149)''.
_\b6_\b._\b4_\b._\b3_\b6 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
Setting this variable will cause Mutt-ng to always attempt to cryptographically
sign outgoing messages. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when
signing is not required or encryption is requested as well. If
- ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)'' is _\bs_\be_\bt, then OpenSSL is
+ ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 149)'' is _\bs_\be_\bt, then OpenSSL is
used instead to create S/MIME messages and settings can be overridden by use of
the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto only)
This variable controls whether or not Mutt-ng may automatically enable S/MIME
encryption/signing for messages. See also ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 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)''.
+ 6.4.34 , page 90)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 91)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 91)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 6.4.39 , page 91)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 149)''.
_\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 signed.
+ The Mutt Next Generation E-Mail Client 93
+
N\bNo\bot\bte\be:\b: this does not work on messages that are encrypted a\ban\bnd\bd signed! (Crypto
only)
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 90)'', because it allows you to sign all messages which are
+ 6.4.38 , page 91)'', 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 90)'', 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 91)'', 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
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
Type: string
+ The Mutt Next Generation E-Mail Client 94
+
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 106)''. This is passed to strftime(3)
+ ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108)''. 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 109)''. If the first character in the string
+ ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 111)''. 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).
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.
Default: yes
+ The Mutt Next Generation E-Mail Client 95
+
If this option is _\bs_\be_\bt, Mutt-ng's received-attachments menu will not show the
subparts of individual messages in a multipart/digest. To see these subparts,
press 'v' on that menu.
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 92), and the filtered message is read from the standard output.
+ page 94), 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
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
-
- 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.
+ consists of a comma separated list (no spaces!) of one or more of the follow-
+ ing: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notification on
+ transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs, to be
+ notified of successful transmission.
Example: set dsn_notify='failure,delay'
It may be set to either _\bh_\bd_\br_\bs to return just the message header, or _\bf_\bu_\bl_\bl to
return the full message.
+ The Mutt Next Generation E-Mail Client 96
+
Example: set dsn_return=hdrs
_\b6_\b._\b4_\b._\b5_\b3 _\bd_\bu_\bp_\bl_\bi_\bc_\ba_\bt_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
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
The file which includes random data that is used to initialize SSL library
functions.
+ The Mutt Next Generation E-Mail Client 97
+
_\b6_\b._\b4_\b._\b5_\b8 _\be_\bn_\bv_\be_\bl_\bo_\bp_\be_\b__\bf_\br_\bo_\bm
Type: boolean
When _\bs_\be_\bt, Mutt-ng will try to derive the message's _\be_\bn_\bv_\be_\bl_\bo_\bp_\be sender from the
``From:'' header field. Note that this information is passed to the sendmail
command using the ``-f' command line switch, so don't set this option if you
- are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page 140) yourself, or
+ are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page 142) yourself, or
if the sendmail on your machine doesn't support that command line switch.
_\b6_\b._\b4_\b._\b5_\b9 _\be_\bs_\bc_\ba_\bp_\be
messages.
N\bNo\bot\bte\be:\b: this variable has no effect when the ``_\b$_\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt (section 6.4.17 , page
- 85)'' variable is _\bs_\be_\bt.
+ 87)'' 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
Type: string
+ The Mutt Next Generation E-Mail Client 98
+
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 87) value will
+ file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 6.4.24 , page 88) value will
be used instead. For example, the following configuration would work for
Japanese text handling:
This variable allows you to customize the file browser display to your personal
taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page
- 106)'', but has its own set of printf(3)-like sequences:
+ 108)'', 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
%N
N if folder has new mail, blank otherwise
+ The Mutt Next Generation E-Mail Client 99
+
%s
size in bytes
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.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 104)''.
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.321 , page 161)'',
+ ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.115 , page 111)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
+ 6.4.99 , page 105)''.
_\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 139)'',
+ The Mutt Next Generation E-Mail Client 100
+
+ This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 141)'',
except that Mutt-ng will store a copy of your outgoing message by the username
of the address you are sending to even if that mailbox does not exist.
- Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 136)'' variable.
+ Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 138)'' variable.
_\b6_\b._\b4_\b._\b6_\b9 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
Controls the decoding of complex MIME messages into text/plain when forwarding
a message. The message header is also RFC2047 decoded. This variable is only
- used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 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 114)'' is used instead.
+ used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 115)'' 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 115)'' is used instead.
_\b6_\b._\b4_\b._\b7_\b0 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
Controls the handling of encrypted messages when forwarding a message. When
_\bs_\be_\bt, the outer layer of encryption is stripped off. This variable is only used
- if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 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 114)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
+ if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 115)'' 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 115)'' 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
- 106)'' variable.
+ 108)'' variable.
_\b6_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
Default: no
+ The Mutt Next Generation E-Mail Client 101
+
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 106)''.
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 115)'' 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 108)''.
_\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
- 138)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 6.4.330 , page
- 162)'' is unset.
+ 140)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 6.4.330 , page
+ 163)'' 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
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''
Type: boolean
+ The Mutt Next Generation E-Mail Client 102
+
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.336 , page
- 163)'' setting applies.
+ 165)'' 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 99) variable points to the header
+ The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 6.4.78 , page 101) 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 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 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.
+ If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 6.4.78 , page 101) points to a directory it will
+ contain a header cache database per folder. If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section
+ 6.4.78 , page 101) 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.
_\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
_\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 101)'' variable when adding the domain part to addresses. This
+
+ The Mutt Next Generation E-Mail Client 103
+
+ 6.4.89 , page 103)'' 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.
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 100) is set, this option will have no effect.
+ _\bi_\bn_\bg (section 6.4.83 , page 102) 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 100) is _\bs_\be_\bt, this option will have no effect.
+ page 102) is _\bs_\be_\bt, this option will have no effect.
_\b6_\b._\b4_\b._\b8_\b7 _\bh_\bi_\bs_\bt_\bo_\br_\by
Type: number
+ The Mutt Next Generation E-Mail Client 104
+
Default: 10
This variable controls the size (in number of strings remembered) of the string
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
capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
eter is case-insensitive.
+ The Mutt Next Generation E-Mail Client 105
+
If this parameter is _\bu_\bn_\bs_\be_\bt (the default) Mutt-ng will try all available meth-
ods, in order from most-secure to least-secure.
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 95) variable.
+ shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 97) 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
Availability: IMAP
+ The Mutt Next Generation E-Mail Client 106
+
You normally want to see your personal folders alongside your INBOX in the IMAP
browser. If you see something else, you may set this variable to the IMAP path
to your folders.
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
- 105).''
+ 107).''
_\b6_\b._\b4_\b._\b9_\b9 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Default: 300
+ The Mutt Next Generation E-Mail Client 107
+
This variable configures how often (in seconds) Mutt-ng should look for new
mail in IMAP folders. This is split from the ``_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.115 ,
- page 109)'' variable to generate less traffic and get more accurate information
+ page 111)'' variable to generate less traffic and get more accurate information
for local folders.
_\b6_\b._\b4_\b._\b1_\b0_\b0 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
_\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
Availability: IMAP
+ The Mutt Next Generation E-Mail Client 108
+
Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
connection is lost.
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: no
+ The Mutt Next Generation E-Mail Client 109
+
Controls whether or not Mutt-ng includes only the first attachment of the mes-
sage you are replying.
%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).
date and time of the message in the format specified by ``date_for-
mat'' converted to the local time zone
+ The Mutt Next Generation E-Mail Client 110
+
%e
current message number in thread
%M
number of hidden messages if the thread is collapsed.
- The Mutt Next Generation E-Mail Client 109
-
%N
message score
%t
`to:' field (recipients)
+ The Mutt Next Generation E-Mail Client 111
+
%T
the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.323 ,
- page 160) string
+ page 162) string
%u
user (login) name of the author
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.323 , page 160)''.
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 6.4.323 , page 162)''.
_\b6_\b._\b4_\b._\b1_\b1_\b1 _\bi_\bs_\bp_\be_\bl_\bl
+ The Mutt Next Generation E-Mail Client 112
+
Type: path
Default: 'ispell'
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 111)'' mailbox, or as a result of
+ box to your ``_\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 113)'' 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
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 104).
+ 6.4.99 , page 105).
_\b6_\b._\b4_\b._\b1_\b1_\b6 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
Default: ''
This variable specifies which files to consult when attempting to display MIME
+
+ The Mutt Next Generation E-Mail Client 113
+
bodies not directly supported by Mutt-ng.
_\b6_\b._\b4_\b._\b1_\b1_\b7 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be
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.
up with an 'O' next to them in the ``index'' menu, indicating that they are
old.
+ The Mutt Next Generation E-Mail Client 114
+
_\b6_\b._\b4_\b._\b1_\b2_\b1 _\bm_\ba_\br_\bk_\be_\br_\bs
Type: boolean
Controls the display of wrapped lines in the internal pager. If set, a ``+''
marker is displayed at the beginning of wrapped lines. Also see the
- ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 6.4.263 , page 144)'' variable.
+ ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 6.4.263 , page 146)'' variable.
_\b6_\b._\b4_\b._\b1_\b2_\b2 _\bm_\ba_\bs_\bk
When _\bs_\be_\bt, the maximum line length for displaying ``format = flowed'' messages
is limited to this length. A value of 0 (which is also the default) means that
the maximum line length is determined by the terminal width and _\b$_\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
- (section 6.4.338 , page 163).
+ (section 6.4.338 , page 165).
_\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.297 , page 152)'' folder will be appended.
+ 6.4.297 , page 154)'' folder will be appended.
_\b6_\b._\b4_\b._\b1_\b2_\b5 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
Default: 0
+ The Mutt Next Generation E-Mail Client 115
+
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
- 122)''.)
+ 124)''.)
_\b6_\b._\b4_\b._\b1_\b2_\b7 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
This is the string displayed in the ``attachment'' menu for attachments of type
message/rfc822. For a full listing of defined printf(3)-like sequences see the
- section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)''.
-
- The Mutt Next Generation E-Mail Client 114
+ section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108)''.
_\b6_\b._\b4_\b._\b1_\b3_\b0 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
Default: no
+ The Mutt Next Generation E-Mail Client 116
+
If _\bu_\bn_\bs_\be_\bt, Mutt-ng will remove your address (see the ``alternates'' command)
from the list of recipients when replying to a message.
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 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)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.69 , page 99)'' 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 115)''.
+
+ The Mutt Next Generation E-Mail Client 117
_\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
Default: no
Controls the decoding of complex MIME messages into text/plain when forwarding
- a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 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 97)'' is used instead.
+ a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 115)'' 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 99)'' 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
%c
Remailer capabilities.
- The Mutt Next Generation E-Mail Client 116
-
%s
The remailer's short name.
used with various sets of parameters to gather the list of known remailers, and
to finally send a message through the mixmaster chain.
+ The Mutt Next Generation E-Mail Client 118
+
_\b6_\b._\b4_\b._\b1_\b4_\b1 _\bm_\bo_\bv_\be
Type: quadoption
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 111)'' mailbox, or as a result of a
+ to your ``_\b$_\bm_\bb_\bo_\bx (section 6.4.124 , page 113)'' 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
%O
the current UNIX timestamp (octal)
- The Mutt Next Generation E-Mail Client 117
-
%p
the process ID
%T
the current UNIX timestamp (decimal)
+ The Mutt Next Generation E-Mail Client 119
+
%X
the current UNIX timestamp (hexadecimal)
Type: boolean
- The Mutt Next Generation E-Mail Client 118
-
Default: no
Availability: NNTP
ers. If _\bu_\bn_\bs_\be_\bt, headers will not be saved at all and will be reloaded each time
when you enter a newsgroup.
+ The Mutt Next Generation E-Mail Client 120
+
As for the header caching in connection with IMAP and/or Maildir, this drasti-
cally increases speed and lowers traffic.
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 117)) 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 118)) 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 117), all older ones will be removed/not shown in the index.
+ page 119), 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 106)'', but has its own set of printf(3)-like sequences:
+ page 108)'', but has its own set of printf(3)-like sequences:
+
+ The Mutt Next Generation E-Mail Client 121
%C current newsgroup number
%d description of newsgroup (retrieved from server)
_\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: ''
Type: boolean
+ The Mutt Next Generation E-Mail Client 122
+
Default: yes
Availability: NNTP
_\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'
Type: string
+ The Mutt Next Generation E-Mail Client 123
+
Default: ''
Availability: NNTP
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
Availability: NNTP
If _\bs_\be_\bt, the newsserver will be asked for new newsgroups on entering the
+
+ The Mutt Next Generation E-Mail Client 124
+
browser. Otherwise, it will be done only once for a newsserver. Also controls
whether or not the number of new articles of subscribed newsgroups will be
checked.
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.
Default: 'builtin'
+ The Mutt Next Generation E-Mail Client 125
+
This variable specifies which pager you would like to use to view messages.
``builtin'' means to use the builtin pager, otherwise this variable should
specify the pathname of the external pager you would like to use.
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 106)''
+ sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108)''
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
Default: no
+ The Mutt Next Generation E-Mail Client 126
+
When _\bs_\be_\bt, the internal-pager will n\bno\bot\bt move to the next message when you are at
the end of a message and invoke the _\bn_\be_\bx_\bt_\b-_\bp_\ba_\bg_\be function.
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 127)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 6.4.188 , page 129)''.
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
Note that the use of this format is s\bst\btr\bro\bon\bng\bgl\bly\by d\bde\bep\bpr\bre\bec\bca\bat\bte\bed\bd. (PGP only)
+ The Mutt Next Generation E-Mail Client 127
+
_\b6_\b._\b4_\b._\b1_\b7_\b5 _\bp_\bg_\bp_\b__\bd_\be_\bc_\bo_\bd_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
multipart/signed attachment when verifying it.
%a
- The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.4.192 , page 128).
+ The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 6.4.192 , page 130).
%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: ''
Default: ''
+ The Mutt Next Generation E-Mail Client 128
+
This command is used to both sign and encrypt a body part. (PGP only)
_\b6_\b._\b4_\b._\b1_\b7_\b9 _\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
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
- 106)'', but has its own set of printf(3)-like sequences:
+ 108)'', but has its own set of printf(3)-like sequences:
%n
number
%c
capabilities
- The Mutt Next Generation E-Mail Client 127
-
%t
trust/validity of the key-uid association
Type: string
+ The Mutt Next Generation E-Mail Client 129
+
Default: ''
This command is invoked whenever Mutt-ng will need public key information. %r
Default: ''
If you assign a text to this variable, then a PGP signature is only considered
- verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.198 , page 129)
+ verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.198 , page 131)
contains the text. Use this variable if the exit code from the command is 0
even for bad signatures. (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
Default: ''
This command is used to list the secret key ring's contents. The output format
+
+ The Mutt Next Generation E-Mail Client 130
+
must be analogous to the one used by gpg --list-keys --with-colons.
This format is also generated by the pgpring utility which comes with Mutt-ng.
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 127)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 6.4.188 , page 129)''.
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: no
+ The Mutt Next Generation E-Mail Client 131
+
If _\bs_\be_\bt, signed and encrypted messages will consist of nested multipart/signed
and multipart/encrypted body parts.
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)
date
sort by key creation date
+ The Mutt Next Generation E-Mail Client 132
+
trust
sort by the trust of the key
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
Type: boolean
+ The Mutt Next Generation E-Mail Client 133
+
Default: no
Used in connection with the _\bp_\bi_\bp_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be command. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will
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 130)'' separator is added after each message.
+ (section 6.4.201 , page 132)'' 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
tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
``digest-md5'', ``gssapi'' or ``cram-md5''.
+ The Mutt Next Generation E-Mail Client 134
+
This parameter is case-insensitive. If this parameter is _\bu_\bn_\bs_\be_\bt (the default)
Mutt-ng will try all available methods, in order from most-secure to least-
secure.
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
Availability: POP
+ The Mutt Next Generation E-Mail Client 135
+
This variable configures how often (in seconds) POP should look for new mail.
_\b6_\b._\b4_\b._\b2_\b0_\b9 _\bp_\bo_\bp_\b__\bp_\ba_\bs_\bs
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 85)'' variable, Mutt-ng
+ Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 6.4.15 , page 86)'' variable, Mutt-ng
will append this string after the inclusion of a message which is being replied
to.
Default: ask-yes
+ The Mutt Next Generation E-Mail Client 136
+
Controls whether or not messages are saved in the ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section
- 6.4.214 , page 133)'' mailbox when you elect not to send immediately.
+ 6.4.214 , page 135)'' 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 133)
+ Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.4.213 , page 134)
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 133)'' variable.
+ ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 6.4.213 , page 134)'' variable.
_\b6_\b._\b4_\b._\b2_\b1_\b5 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
N\bNo\bot\bte\be:\b: For this example to work, you must be able to log in to the remote
machine without having to enter a password.
- The Mutt Next Generation E-Mail Client 135
-
_\b6_\b._\b4_\b._\b2_\b1_\b6 _\bp_\br_\bi_\bn_\bt
Type: quadoption
Type: boolean
+ The Mutt Next Generation E-Mail Client 137
+
Default: yes
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 134). 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 135). 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 134) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.217 , page 135) 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 134) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 6.4.217 , page 135) is executed
only once, and all the messages are concatenated, with a form feed as the mes-
sage separator.
Default: yes
- If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 6.4.166 , page 122)'', 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 123)'', 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
This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
+
+ The Mutt Next Generation E-Mail Client 138
+
ng. If it set to _\by_\be_\bs, they do quit, if it is set to _\bn_\bo, they have no effect,
and if it is set to _\ba_\bs_\bk_\b-_\by_\be_\bs or _\ba_\bs_\bk_\b-_\bn_\bo, you are prompted for confirmation when
you try to quit.
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 106)''.
+ tion 6.4.109 , page 108)''.
_\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 106)''.
+ by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 6.4.109 , page 108)''.
_\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.340 , page 163)'' variable.
+ Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 6.4.340 , page 165)'' variable.
_\b6_\b._\b4_\b._\b2_\b2_\b7 _\br_\be_\ba_\bd_\b__\bo_\bn_\bl_\by
+ The Mutt Next Generation E-Mail Client 139
+
Type: boolean
Default: no
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 98) variable.
+ _\b$_\bf_\br_\bo_\bm (section 6.4.74 , page 100) variable.
_\b6_\b._\b4_\b._\b2_\b2_\b9 _\br_\be_\bc_\ba_\bl_\bl
Default: ask-yes
Controls whether or not Mutt-ng recalls postponed messages when composing a new
- message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 6.4.214 , page 133)''.
+ message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 6.4.214 , page 135)''.
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: ''
another way to do this is using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 34)'' com-
mand to create a Bcc: header field with your email address in it.)
- The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\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 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
+ 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_\b8_\b) is overridden by the
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 98)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
+ 6.4.241 , page 141)'' 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
Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
- A regular expression used to recognize reply messages when threading and reply-
- ing. The default value corresponds to the English ``Re:'' and the German
+ A regular expression used to recognize reply messages when threading and
+
+ The Mutt Next Generation E-Mail Client 140
+
+ replying. The default value corresponds to the English ``Re:'' and the German
``Aw:''.
_\b6_\b._\b4_\b._\b2_\b3_\b2 _\br_\be_\bp_\bl_\by_\b__\bs_\be_\bl_\bf
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.
From: abd30425@somewhere.net
It would be displayed in the index menu as ``Joe User'' instead of
+
+ The Mutt Next Generation E-Mail Client 141
+
``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
not human friendly (like CompuServe addresses).
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 ,
- page 138) feature. When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming
+ page 140) 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 136) variable.
+ (section 6.4.228 , page 138) 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-
Type: boolean
+ The Mutt Next Generation E-Mail Client 142
+
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 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
+ folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 141)'' or
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 98)'' 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.297 , page 152)'' which is
+ closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page 154)'' which is
never removed). If _\bs_\be_\bt, mailboxes are never removed.
N\bNo\bot\bte\be:\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
This variable controls how copies of outgoing messages are saved. When set, a
check is made to see if a mailbox specified by the recipient address exists
(this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 ,
- page 95)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
+ page 97)'' 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.
+ the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 138)'' mailbox.
- 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.
+ Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 98)'' 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 140)'' variable and friends are used.
+ _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 6.4.243 , page 141)'' 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
Messages which have been assigned a score equal to or lower than the value of
this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
scores are always greater than or equal to zero, the default setting of this
+
+ The Mutt Next Generation E-Mail Client 143
+
variable will never mark a message for deletion.
_\b6_\b._\b4_\b._\b2_\b4_\b4 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bf_\bl_\ba_\bg
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 87)'' is not iso-8859-1 and recipients may not under-
+ (section 6.4.24 , page 88)'' 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
Default: 0
Specifies the number of seconds to wait for the ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 ,
- page 140)'' process to finish before giving up and putting delivery in the
+ page 142)'' process to finish before giving up and putting delivery in the
background.
+ The Mutt Next Generation E-Mail Client 144
+
Mutt-ng interprets the value of this variable as follows:
>0
Default: '.'
When the sidebar is displayed and _\b$_\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by (section
- 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
-
+ 6.4.254 , page 144) is _\bs_\be_\bt, this variable specifies the characters at which to
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
Type: string
+ The Mutt Next Generation E-Mail Client 145
+
Default: '%m%?n?(%n)?%?f?[%f]?'
This variable controls how message counts are printed when the sidebar is
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 143)'' is set to a too low value). For example, if the news-
+ 6.4.256 , page 145)'' 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 141) variable.
+ _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 6.4.250 , page 143) variable.
_\b6_\b._\b4_\b._\b2_\b5_\b5 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
Default: no
This specifies whether or not to show the sidebar (a list of folders specified
+
+ The Mutt Next Generation E-Mail Client 146
+
with the ``mailboxes'' command).
_\b6_\b._\b4_\b._\b2_\b5_\b6 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bw_\bi_\bd_\bt_\bh
Default: yes
If set, a line containing ``-- '' (dash, dash, space) will be inserted before
- your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 143)''. It is s\bst\btr\bro\bon\bng\bgl\bly\by recommended
+ your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 145)''. It is s\bst\btr\bro\bon\bng\bgl\bly\by recommended
that you not unset this variable unless your ``signature'' contains just your
name. The reason for this is because many software packages use ``-- \n'' to
detect your signature.
Default: no
- The Mutt Next Generation E-Mail Client 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
If _\bs_\be_\bt, this string will be inserted before the signature. This is useful for
people that want to sign off every message they send with their name.
+ The Mutt Next Generation E-Mail Client 147
+
If you want to insert your website's URL, additional contact information or
witty quotes into your mails, better use a signature file instead of the sig-
noff string.
Specifies how Mutt-ng should expand a simple search into a real search pattern.
A simple search is one that does not contain any of the ~ operators. See
- ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 6.2 , page 77)'' for more information on search patterns.
+ ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 6.2 , page 78)'' for more information on search patterns.
For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
will automatically expand it to the value specified by this variable. For the
the current folder. The default is to pause one second, so a value of zero for
this option suppresses the pause.
- The Mutt Next Generation E-Mail Client 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 111)'' variable.
+ page 112)'' 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 135)'', most notably smileys in the
+ ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.225 , page 137)'', 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
+ The Mutt Next Generation E-Mail Client 148
+
Type: boolean
Default: yes
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 146)
+ page 148)
+
+ The Mutt Next Generation E-Mail Client 149
%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 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)'.
+ 6.4.266 , page 147) 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 147)' 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 147)'.
For examples on how to configure these formats, see the smime.rc in the sam-
ples/ subdirectory which has been installed on your system alongside the docu-
Type: string
- The Mutt Next Generation E-Mail Client 148
-
Default: ''
This is the default key-pair to use for signing. This must be set to the keyid
If _\bu_\bn_\bs_\be_\bt ``_\b3_\bd_\be_\bs'' (TripleDES) is used. (S/MIME only)
+ The Mutt Next Generation E-Mail Client 150
+
_\b6_\b._\b4_\b._\b2_\b7_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
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
select the same application that was used to sign/encrypt the original message.
(Note that this variable can be overridden by unsetting _\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bm_\bi_\bm_\be (sec-
- tion 6.4.37 , page 89).) (S/MIME only)
+ tion 6.4.37 , page 91).) (S/MIME only)
_\b6_\b._\b4_\b._\b2_\b7_\b8 _\bs_\bm_\bi_\bm_\be_\b__\bk_\be_\by_\bs
+ The Mutt Next Generation E-Mail Client 151
+
Type: path
Default: ''
This command is used to created S/MIME signatures of type multipart/signed,
which can be read by all mail clients. (S/MIME only)
- 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
Default: ''
+ The Mutt Next Generation E-Mail Client 152
+
This command is used to verify S/MIME signatures of type multipart/signed.
(S/MIME only)
_\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: ''
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.
+ _\bm_\ba_\bi_\bl (section 6.4.247 , page 142)'', and any associated variables.
_\b6_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
Availability: SMTP
Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section
- 6.4.290 , page 150)'' is set, but this variable is not, you will be prompted
+ 6.4.290 , page 152)'' 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.
+ The Mutt Next Generation E-Mail Client 153
+
_\b6_\b._\b4_\b._\b2_\b8_\b8 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
Type: number
continue without TLS in case of an error. Muttng still needs to have SSL sup-
port enabled in order to use it.
- The Mutt Next Generation E-Mail Client 152
-
_\b6_\b._\b4_\b._\b2_\b9_\b0 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
Type: string
Specifies how to sort messages in the _\bi_\bn_\bd_\be_\bx menu. Valid values are:
+ The Mutt Next Generation E-Mail Client 154
+
date or date-sent
date-received
from
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.291 , page 150)'' can,
+ This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 152)'' can,
except threads (in that case, Mutt-ng will just use date-sent). You can also
specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
come after reverse-. The last- prefix causes messages to be sorted against its
is received in a thread, that thread becomes the last one displayed (or the
first, if you have set sort=reverse-threads.)
- N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 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
+ N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 152)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ (section 6.4.293 , page 153) is reversed again (which is not the right thing
to do, but kept to not break any existing configuration setting).
+ The Mutt Next Generation E-Mail Client 155
+
_\b6_\b._\b4_\b._\b2_\b9_\b4 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
Type: sort order
Default: yes
This variable is only useful when sorting by threads with ``_\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
- (section 6.4.312 , page 158)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ (section 6.4.312 , page 160)'' _\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-
+ page 154) _\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 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
+ matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.231 , page 138)''. With
+ _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.295 , page 154) _\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 137)'' parts of both messages are identical.
-
- The Mutt Next Generation E-Mail Client 154
+ 6.4.231 , page 138)'' parts of both messages are identical.
_\b6_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
Default: ','
- ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.296 , page 152)'' controls what happens when
+ ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.296 , page 154)'' 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.
+ page 154)'' as a separator.
_\b6_\b._\b4_\b._\b2_\b9_\b7 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
Default: ''
If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
+
+ The Mutt Next Generation E-Mail Client 156
+
you can specify its location with this variable. Mutt-ng will automatically
set this variable to the value of the environment variable $MAIL if it is not
set.
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.302 , page 154)''.
+ 6.4.302 , page 155)''.
_\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: quadoption
+ The Mutt Next Generation E-Mail Client 157
+
Default: yes
Availability: SSL or GNUTLS
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-
_\b6_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs
+ The Mutt Next Generation E-Mail Client 158
+
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.308 , page 155)''. The first character is used when the mailbox is
+ tion 6.4.308 , page 157)''. The first character is used when the mailbox is
unchanged. The second is used when the mailbox has been changed, and it needs
to be resynchronized. The third is used if the mailbox is in read-only mode, or
if the mailbox will not be written when exiting that mailbox (You can toggle
%l?]---(%s/%S)-%>-(%P)---'
Controls the format of the status line displayed in the _\bi_\bn_\bd_\be_\bx menu. This
- string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106)'', but has
+ string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 108)'', 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
%m
the number of messages in the mailbox *
+ The Mutt Next Generation E-Mail Client 159
+
%M
the number of messages shown (i.e., which match the current limit)
*
%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.307 , page 155)
+ to _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs (section 6.4.307 , page 156)
%s
- current sorting mode (_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150))
+ current sorting mode (_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 152))
%S
current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 6.4.293 , page
- 151))
+ 153))
%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 *
%?<sequence_char>?<optional_string>?
+ The Mutt Next Generation E-Mail Client 160
+
where _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\b__\bc_\bh_\ba_\br is a character from the table above, and _\bo_\bp_\bt_\bi_\bo_\bn_\ba_\bl_\b__\bs_\bt_\br_\bi_\bn_\bg is
the string you would like printed if _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\b__\bc_\bh_\ba_\br is nonzero. _\bo_\bp_\bt_\bi_\bo_\bn_\ba_\bl_\b__\bs_\bt_\br_\bi_\bn_\bg
m\bma\bay\by contain other sequences as well as normal text, but you may n\bno\bot\bt nest
Setting this variable causes the ``status bar'' to be displayed on the first
line of the screen rather than near the bottom.
- The Mutt Next Generation E-Mail Client 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 93)'' is unset.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 95)'' 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 93)'' is set to.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 95)'' is set to.
_\b6_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
Type: boolean
+ The Mutt Next Generation E-Mail Client 161
+
Default: yes
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 83).
+ Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 6.4.11 , page 85).
This option also replaces linear-white-space between encoded-word and *text to
a single space to prevent the display of MIME-encoded ``Subject:'' header field
Default: no
If _\bs_\be_\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
- ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150)'' by mes-
+ ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 152)'' by mes-
sage threads. By default, messages with the same subject are grouped together
in ``pseudo threads.'' This may not always be desirable, such as in a personal
mailbox where you might have several unrelated messages with the subject ``hi''
Default: no
When _\bs_\be_\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
- matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 6.4.314 , page 158) 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 160) when replying. This is
useful to properly react on subject changes and reduce ``subject noise.'' (esp.
in Usenet)
- The Mutt Next Generation E-Mail Client 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.313 , page 158) 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 160) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
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.
+ The Mutt Next Generation E-Mail Client 162
+
_\b6_\b._\b4_\b._\b3_\b1_\b6 _\bs_\bu_\bs_\bp_\be_\bn_\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 106) 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 108) is ignored when this
option is set.
_\b6_\b._\b4_\b._\b3_\b1_\b8 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
Default: no
Affects the ~b and ~h search operations described in section ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
- tion 6.2 , page 77)'' above. If _\bs_\be_\bt, the headers and attachments of messages
+ tion 6.2 , page 78)'' above. If _\bs_\be_\bt, the headers and attachments of messages
to be searched are decoded before searching. If _\bu_\bn_\bs_\be_\bt, messages are searched
as they appear in the folder.
- The Mutt Next Generation E-Mail Client 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, the internal-pager will pad blank lines to the bottom of the screen
with a tilde (~).
+ The Mutt Next Generation E-Mail Client 163
+
_\b6_\b._\b4_\b._\b3_\b2_\b1 _\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
indicate mail that was sent by _\by_\bo_\bu. The sixth character is used to indicate
when a mail was sent to a mailing-list you're subscribe to (default: L).
- The Mutt Next Generation E-Mail Client 162
-
_\b6_\b._\b4_\b._\b3_\b2_\b4 _\bt_\br_\ba_\bs_\bh
Type: path
Default: ''
+ The Mutt Next Generation E-Mail Client 164
+
Setting this variable will cause Mutt-ng to open a pipe to a command instead of
a raw socket. You may be able to use this to set up preauthenticated connec-
tions to your IMAP/POP3 server. Example:
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 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 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
+ 142)'' 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_\b9 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
Default: yes
When _\bs_\be_\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
- tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 6.4.89 , page 101)''. 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 103)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
_\b6_\b._\b4_\b._\b3_\b3_\b0 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
+ The Mutt Next Generation E-Mail Client 165
+
Type: boolean
Default: yes
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.
Default: yes
+ The Mutt Next Generation E-Mail Client 166
+
Controls whether Mutt-ng will ask you to press a key after _\bs_\bh_\be_\bl_\bl_\b- _\be_\bs_\bc_\ba_\bp_\be, _\bp_\bi_\bp_\be_\b-
_\bm_\be_\bs_\bs_\ba_\bg_\be, _\bp_\bi_\bp_\be_\b-_\be_\bn_\bt_\br_\by, _\bp_\br_\bi_\bn_\bt_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be, and _\bp_\br_\bi_\bn_\bt_\b-_\be_\bn_\bt_\br_\by commands.
It is also used when viewing attachments with ``_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page
- 74)'', provided that the corresponding mailcap entry has a needsterminal flag,
+ 75)'', provided that the corresponding mailcap entry has a needsterminal flag,
and the external program is interactive.
When _\bs_\be_\bt, Mutt-ng will always ask for a key. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will wait for
Default: 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.
Default: 10
+ The Mutt Next Generation E-Mail Client 167
+
When writing a mailbox, a message will be printed every _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc messages to
indicate progress. If set to 0, only a single message will be displayed before
writing a mailbox.
- Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 6.4.226 , page 135)'' variable.
+ Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 6.4.226 , page 137)'' variable.
_\b6_\b._\b4_\b._\b3_\b4_\b1 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
Default: 'M%?n?AIL&ail?'
Controls the format of the X11 icon title, as long as _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (sec-
- tion 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)''.
+ tion 6.4.343 , page 166) 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 157)''.
_\b6_\b._\b4_\b._\b3_\b4_\b2 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
Default: ''
- If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.343 , page 164) 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 166) is _\bs_\be_\bt, this string will be
used to set the title when leaving mutt-ng. For terminal-based programs,
there's no easy and portable way to read the current title so mutt-ng cannot
read it upon startup and restore it when exiting.
Type: 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
Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
Controls the format of the title bar of the xterm provided that
- _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.343 , page 164) has been _\bs_\be_\bt. This string is
+ _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.343 , page 166) 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)''.
+ page 157)''.
+
+ The Mutt Next Generation E-Mail Client 168
_\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
_\b6_\b._\b5_\b._\b2 _\bi_\bn_\bd_\be_\bx
- The Mutt Next Generation E-Mail Client 168
+ The Mutt Next Generation E-Mail Client 169
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 169
+ The Mutt Next Generation E-Mail Client 170
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 170
+ The Mutt Next Generation E-Mail Client 171
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 171
+ The Mutt Next Generation E-Mail Client 172
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 172
+ The Mutt Next Generation E-Mail Client 173
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 173
+ The Mutt Next Generation E-Mail Client 174
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 174
+ The Mutt Next Generation E-Mail Client 175
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 175
+ The Mutt Next Generation E-Mail Client 176
_\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 176
+ The Mutt Next Generation E-Mail Client 177
Brandon Long <blong@fiction.net>,
Elimar Riesebieter <riesebie@lxtec.de>
- The Mutt Next Generation E-Mail Client 177
+ The Mutt Next Generation E-Mail Client 178
_\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 178
+ The Mutt Next Generation E-Mail Client 179
CONTENTS
3.30.1 Character Sets 43
3.30.2 Modularization 43
3.30.3 Conditional parts 43
+ 3.31 Obsolete Variables ............................................. 45
4. Advanced Usage ....................................................... 45
4.1 Regular Expressions ............................................ 45
4.2 Patterns ....................................................... 48
- 4.2.1 Complex Patterns 48
+ 4.2.1 Complex Patterns 49
4.2.2 Patterns and Dates 49
4.3 Format Strings ............................................. 50
4.3.1 Introduction 50
4.12 Delivery Status Notification (DSN) Support ..................... 59
4.13 POP3 Support (OPTIONAL) ........................................ 60
4.14 IMAP Support (OPTIONAL) ........................................ 60
- 4.14.1 The Folder Browser 61
ii
+ 4.14.1 The Folder Browser 61
4.14.2 Authentication 62
4.15 NNTP Support (OPTIONAL) ........................................ 62
- 4.15.1 Again: Scoring 62
+ 4.15.1 Again: Scoring 63
4.16 SMTP Support (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 Compressed folders Support (OPTIONAL) .......................... 65
4.19.1 Open a compressed mailbox for reading 65
4.19.2 Write a compressed mailbox 66
4.19.3 Append a message to a compressed mailbox 66
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.1 Viewing MIME messages in the pager 68
5.1.2 The Attachment Menu 68
5.1.3 The Compose Menu 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 70
5.3.2 Secure use of mailcap 71
- 5.3.3 Advanced mailcap Usage 71
+ 5.3.3 Advanced mailcap Usage 72
5.3.4 Example mailcap files 74
5.4 MIME Autoview .................................................. 75
5.5 MIME Multipart/Alternative ..................................... 76
6.2 Patterns ....................................................... 78
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 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 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 87
- 6.4.21 bounce_delivered 87
+ 6.4.1 abort_nosubject 83
+ 6.4.2 abort_unmodified 84
+ 6.4.3 alias_file 84
+ 6.4.4 alias_format 84
+ 6.4.5 allow_8bit 84
+ 6.4.6 allow_ansi 85
+ 6.4.7 arrow_cursor 85
+ 6.4.8 ascii_chars 85
+ 6.4.9 askbcc 85
+ 6.4.10 askcc 85
+ 6.4.11 assumed_charset 86
+ 6.4.12 attach_format 86
+ 6.4.13 attach_sep 87
+ 6.4.14 attach_split 87
+ 6.4.15 attribution 87
+ 6.4.16 auto_tag 87
+ 6.4.17 autoedit 88
+ 6.4.18 beep 88
+ 6.4.19 beep_new 88
+ 6.4.20 bounce 88
iii
- 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 90
- 6.4.35 crypt_autopgp 90
- 6.4.36 crypt_autosign 90
- 6.4.37 crypt_autosmime 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 92
- 6.4.44 date_format 92
- 6.4.45 default_hook 92
- 6.4.46 delete 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 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 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 96
- 6.4.63 file_charset 96
- 6.4.64 folder 96
- 6.4.65 folder_format 96
- 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 99
- 6.4.73 forward_quote 99
- 6.4.74 from 99
+ 6.4.21 bounce_delivered 88
+ 6.4.22 braille_friendly 89
+ 6.4.23 certificate_file 89
+ 6.4.24 charset 89
+ 6.4.25 check_new 89
+ 6.4.26 collapse_unread 90
+ 6.4.27 compose_format 90
+ 6.4.28 config_charset 90
+ 6.4.29 confirmappend 90
+ 6.4.30 confirmcreate 91
+ 6.4.31 connect_timeout 91
+ 6.4.32 content_type 91
+ 6.4.33 copy 91
+ 6.4.34 crypt_autoencrypt 91
+ 6.4.35 crypt_autopgp 92
+ 6.4.36 crypt_autosign 92
+ 6.4.37 crypt_autosmime 92
+ 6.4.38 crypt_replyencrypt 92
+ 6.4.39 crypt_replysign 92
+ 6.4.40 crypt_replysignencrypted 93
+ 6.4.41 crypt_timestamp 93
+ 6.4.42 crypt_use_gpgme 93
+ 6.4.43 crypt_verify_sig 93
+ 6.4.44 date_format 93
+ 6.4.45 default_hook 94
+ 6.4.46 delete 94
+ 6.4.47 delete_untag 94
+ 6.4.48 digest_collapse 94
+ 6.4.49 display_filter 95
+ 6.4.50 dotlock_program 95
+ 6.4.51 dsn_notify 95
+ 6.4.52 dsn_return 95
+ 6.4.53 duplicate_threads 96
+ 6.4.54 edit_headers 96
+ 6.4.55 editor 96
+ 6.4.56 encode_from 96
+ 6.4.57 entropy_file 96
+ 6.4.58 envelope_from 97
+ 6.4.59 escape 97
+ 6.4.60 fast_reply 97
+ 6.4.61 fcc_attach 97
+ 6.4.62 fcc_clear 97
+ 6.4.63 file_charset 97
+ 6.4.64 folder 98
+ 6.4.65 folder_format 98
+ 6.4.66 followup_to 99
+ 6.4.67 force_buffy_check 99
+ 6.4.68 force_name 99
+ 6.4.69 forward_decode 100
+ 6.4.70 forward_decrypt 100
+ 6.4.71 forward_edit 100
+ 6.4.72 forward_format 100
+ 6.4.73 forward_quote 100
iv
- 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 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 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 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 104
- 6.4.96 imap_keepalive 104
- 6.4.97 imap_list_subscribed 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 106
- 6.4.104 imap_servernoise 106
- 6.4.105 imap_user 106
- 6.4.106 implicit_autoview 106
- 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 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 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 113
- 6.4.126 menu_context 113
- 6.4.127 menu_move_off 113
+ 6.4.74 from 101
+ 6.4.75 gecos_mask 101
+ 6.4.76 hdrs 101
+ 6.4.77 header 101
+ 6.4.78 header_cache 102
+ 6.4.79 header_cache_compress 102
+ 6.4.80 help 102
+ 6.4.81 hidden_host 102
+ 6.4.82 hide_limited 103
+ 6.4.83 hide_missing 103
+ 6.4.84 hide_thread_subject 103
+ 6.4.85 hide_top_limited 103
+ 6.4.86 hide_top_missing 103
+ 6.4.87 history 103
+ 6.4.88 honor_followup_to 104
+ 6.4.89 hostname 104
+ 6.4.90 ignore_list_reply_to 104
+ 6.4.91 imap_authenticators 104
+ 6.4.92 imap_check_subscribed 105
+ 6.4.93 imap_delim_chars 105
+ 6.4.94 imap_headers 105
+ 6.4.95 imap_home_namespace 105
+ 6.4.96 imap_keepalive 106
+ 6.4.97 imap_list_subscribed 106
+ 6.4.98 imap_login 106
+ 6.4.99 imap_mail_check 106
+ 6.4.100 imap_pass 107
+ 6.4.101 imap_passive 107
+ 6.4.102 imap_peek 107
+ 6.4.103 imap_reconnect 107
+ 6.4.104 imap_servernoise 108
+ 6.4.105 imap_user 108
+ 6.4.106 implicit_autoview 108
+ 6.4.107 include 108
+ 6.4.108 include_onlyfirst 108
+ 6.4.109 indent_string 109
+ 6.4.110 index_format 109
+ 6.4.111 ispell 111
+ 6.4.112 keep_flagged 112
+ 6.4.113 list_reply 112
+ 6.4.114 locale 112
+ 6.4.115 mail_check 112
+ 6.4.116 mailcap_path 112
+ 6.4.117 mailcap_sanitize 113
+ 6.4.118 maildir_header_cache_verify 113
+ 6.4.119 maildir_trash 113
+ 6.4.120 mark_old 113
+ 6.4.121 markers 114
+ 6.4.122 mask 114
+ 6.4.123 max_line_length 114
+ 6.4.124 mbox 114
+ 6.4.125 mbox_type 114
+ 6.4.126 menu_context 114
v
- 6.4.128 menu_scroll 113
- 6.4.129 message_format 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 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 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 119
- 6.4.151 nntp_host 119
- 6.4.152 nntp_inews 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 121
- 6.4.158 nntp_post_moderated 121
- 6.4.159 nntp_reconnect 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 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 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 126
- 6.4.178 pgp_encrypt_sign_command 126
- 6.4.179 pgp_entry_format 126
- 6.4.180 pgp_export_command 127
+ 6.4.127 menu_move_off 115
+ 6.4.128 menu_scroll 115
+ 6.4.129 message_format 115
+ 6.4.130 meta_key 115
+ 6.4.131 metoo 115
+ 6.4.132 mh_purge 116
+ 6.4.133 mh_seq_flagged 116
+ 6.4.134 mh_seq_replied 116
+ 6.4.135 mh_seq_unseen 116
+ 6.4.136 mime_forward 116
+ 6.4.137 mime_forward_decode 117
+ 6.4.138 mime_forward_rest 117
+ 6.4.139 mix_entry_format 117
+ 6.4.140 mixmaster 117
+ 6.4.141 move 118
+ 6.4.142 msgid_format 118
+ 6.4.143 narrow_tree 119
+ 6.4.144 nntp_ask_followup_to 119
+ 6.4.145 nntp_ask_x_comment_to 119
+ 6.4.146 nntp_cache_dir 119
+ 6.4.147 nntp_catchup 120
+ 6.4.148 nntp_context 120
+ 6.4.149 nntp_followup_to_poster 120
+ 6.4.150 nntp_group_index_format 120
+ 6.4.151 nntp_host 121
+ 6.4.152 nntp_inews 121
+ 6.4.153 nntp_load_description 121
+ 6.4.154 nntp_mail_check 122
+ 6.4.155 nntp_mime_subject 122
+ 6.4.156 nntp_newsrc 122
+ 6.4.157 nntp_pass 122
+ 6.4.158 nntp_post_moderated 123
+ 6.4.159 nntp_reconnect 123
+ 6.4.160 nntp_save_unsubscribed 123
+ 6.4.161 nntp_show_new_news 123
+ 6.4.162 nntp_show_only_unread 124
+ 6.4.163 nntp_user 124
+ 6.4.164 nntp_x_comment_to 124
+ 6.4.165 operating_system 124
+ 6.4.166 pager 124
+ 6.4.167 pager_context 125
+ 6.4.168 pager_format 125
+ 6.4.169 pager_index_lines 125
+ 6.4.170 pager_stop 125
+ 6.4.171 pgp_auto_decode 126
+ 6.4.172 pgp_autoinline 126
+ 6.4.173 pgp_check_exit 126
+ 6.4.174 pgp_clearsign_command 126
+ 6.4.175 pgp_decode_command 127
+ 6.4.176 pgp_decrypt_command 127
+ 6.4.177 pgp_encrypt_only_command 127
+ 6.4.178 pgp_encrypt_sign_command 127
+ 6.4.179 pgp_entry_format 128
vi
- 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 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 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 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 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 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 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 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 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 138
- 6.4.232 reply_self 138
- 6.4.233 reply_to 138
+ 6.4.180 pgp_export_command 128
+ 6.4.181 pgp_getkeys_command 128
+ 6.4.182 pgp_good_sign 129
+ 6.4.183 pgp_ignore_subkeys 129
+ 6.4.184 pgp_import_command 129
+ 6.4.185 pgp_list_pubring_command 129
+ 6.4.186 pgp_list_secring_command 129
+ 6.4.187 pgp_long_ids 130
+ 6.4.188 pgp_mime_auto 130
+ 6.4.189 pgp_replyinline 130
+ 6.4.190 pgp_retainable_sigs 130
+ 6.4.191 pgp_show_unusable 131
+ 6.4.192 pgp_sign_as 131
+ 6.4.193 pgp_sign_command 131
+ 6.4.194 pgp_sort_keys 131
+ 6.4.195 pgp_strict_enc 132
+ 6.4.196 pgp_timeout 132
+ 6.4.197 pgp_use_gpg_agent 132
+ 6.4.198 pgp_verify_command 132
+ 6.4.199 pgp_verify_key_command 132
+ 6.4.200 pipe_decode 132
+ 6.4.201 pipe_sep 133
+ 6.4.202 pipe_split 133
+ 6.4.203 pop_auth_try_all 133
+ 6.4.204 pop_authenticators 133
+ 6.4.205 pop_delete 134
+ 6.4.206 pop_host 134
+ 6.4.207 pop_last 134
+ 6.4.208 pop_mail_check 134
+ 6.4.209 pop_pass 135
+ 6.4.210 pop_reconnect 135
+ 6.4.211 pop_user 135
+ 6.4.212 post_indent_string 135
+ 6.4.213 postpone 135
+ 6.4.214 postponed 136
+ 6.4.215 preconnect 136
+ 6.4.216 print 136
+ 6.4.217 print_command 136
+ 6.4.218 print_decode 136
+ 6.4.219 print_split 137
+ 6.4.220 prompt_after 137
+ 6.4.221 query_command 137
+ 6.4.222 quit 137
+ 6.4.223 quote_empty 138
+ 6.4.224 quote_quoted 138
+ 6.4.225 quote_regexp 138
+ 6.4.226 read_inc 138
+ 6.4.227 read_only 138
+ 6.4.228 realname 139
+ 6.4.229 recall 139
+ 6.4.230 record 139
+ 6.4.231 reply_regexp 139
+ 6.4.232 reply_self 140
vii
- 6.4.234 resolve 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 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 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 145
- 6.4.260 signoff_string 145
- 6.4.261 simple_search 145
- 6.4.262 sleep_time 145
- 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 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 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
+ 6.4.233 reply_to 140
+ 6.4.234 resolve 140
+ 6.4.235 reverse_alias 140
+ 6.4.236 reverse_name 141
+ 6.4.237 reverse_realname 141
+ 6.4.238 rfc2047_parameters 141
+ 6.4.239 save_address 141
+ 6.4.240 save_empty 142
+ 6.4.241 save_name 142
+ 6.4.242 score 142
+ 6.4.243 score_threshold_delete 142
+ 6.4.244 score_threshold_flag 143
+ 6.4.245 score_threshold_read 143
+ 6.4.246 send_charset 143
+ 6.4.247 sendmail 143
+ 6.4.248 sendmail_wait 143
+ 6.4.249 shell 144
+ 6.4.250 sidebar_boundary 144
+ 6.4.251 sidebar_delim 144
+ 6.4.252 sidebar_newmail_only 144
+ 6.4.253 sidebar_number_format 144
+ 6.4.254 sidebar_shorten_hierarchy 145
+ 6.4.255 sidebar_visible 145
+ 6.4.256 sidebar_width 146
+ 6.4.257 sig_dashes 146
+ 6.4.258 sig_on_top 146
+ 6.4.259 signature 146
+ 6.4.260 signoff_string 146
+ 6.4.261 simple_search 147
+ 6.4.262 sleep_time 147
+ 6.4.263 smart_wrap 147
+ 6.4.264 smileys 147
+ 6.4.265 smime_ask_cert_label 147
+ 6.4.266 smime_ca_location 148
+ 6.4.267 smime_certificates 148
+ 6.4.268 smime_decrypt_command 148
+ 6.4.269 smime_decrypt_use_default_key 149
+ 6.4.270 smime_default_key 149
+ 6.4.271 smime_encrypt_command 149
+ 6.4.272 smime_encrypt_with 149
+ 6.4.273 smime_get_cert_command 150
+ 6.4.274 smime_get_cert_email_command 150
+ 6.4.275 smime_get_signer_cert_command 150
+ 6.4.276 smime_import_cert_command 150
+ 6.4.277 smime_is_default 150
+ 6.4.278 smime_keys 150
+ 6.4.279 smime_pk7out_command 151
+ 6.4.280 smime_sign_command 151
+ 6.4.281 smime_sign_opaque_command 151
+ 6.4.282 smime_timeout 151
+ 6.4.283 smime_verify_command 151
+ 6.4.284 smime_verify_opaque_command 152
+ 6.4.285 smtp_envelope 152
viii
- 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
+ 6.4.286 smtp_host 152
+ 6.4.287 smtp_pass 152
+ 6.4.288 smtp_port 153
+ 6.4.289 smtp_use_tls 153
+ 6.4.290 smtp_user 153
+ 6.4.291 sort 153
+ 6.4.292 sort_alias 154
+ 6.4.293 sort_aux 154
+ 6.4.294 sort_browser 155
+ 6.4.295 sort_re 155
+ 6.4.296 spam_separator 155
+ 6.4.297 spoolfile 155
+ 6.4.298 ssl_ca_certificates_file 156
+ 6.4.299 ssl_client_cert 156
+ 6.4.300 ssl_force_tls 156
+ 6.4.301 ssl_min_dh_prime_bits 156
+ 6.4.302 ssl_starttls 156
+ 6.4.303 ssl_use_sslv2 157
+ 6.4.304 ssl_use_sslv3 157
+ 6.4.305 ssl_use_tlsv1 157
+ 6.4.306 ssl_usesystemcerts 157
+ 6.4.307 status_chars 157
+ 6.4.308 status_format 158
+ 6.4.309 status_on_top 160
+ 6.4.310 strict_mailto 160
+ 6.4.311 strict_mime 160
+ 6.4.312 strict_threads 161
+ 6.4.313 strip_was 161
+ 6.4.314 strip_was_regex 161
+ 6.4.315 stuff_quoted 161
+ 6.4.316 suspend 162
+ 6.4.317 text_flowed 162
+ 6.4.318 thorough_search 162
+ 6.4.319 thread_received 162
+ 6.4.320 tilde 162
+ 6.4.321 timeout 163
+ 6.4.322 tmpdir 163
+ 6.4.323 to_chars 163
+ 6.4.324 trash 163
+ 6.4.325 tunnel 163
+ 6.4.326 umask 164
+ 6.4.327 uncollapse_jump 164
+ 6.4.328 use_8bitmime 164
+ 6.4.329 use_domain 164
+ 6.4.330 use_from 164
+ 6.4.331 use_idn 165
+ 6.4.332 use_ipv6 165
+ 6.4.333 user_agent 165
+ 6.4.334 visual 165
+ 6.4.335 wait_key 165
+ 6.4.336 weed 166
+ 6.4.337 wrap_search 166
+ 6.4.338 wrapmargin 166
ix
- 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
+ 6.4.339 write_bcc 166
+ 6.4.340 write_inc 166
+ 6.4.341 xterm_icon 167
+ 6.4.342 xterm_leave 167
+ 6.4.343 xterm_set_titles 167
+ 6.4.344 xterm_title 167
+ 6.5 Functions ....................................................... 168
+ 6.5.1 generic 168
+ 6.5.2 index 168
+ 6.5.3 pager 170
+ 6.5.4 alias 172
+ 6.5.5 query 172
+ 6.5.6 attach 172
+ 6.5.7 compose 173
+ 6.5.8 postpone 174
+ 6.5.9 browser 174
+ 6.5.10 pgp 175
+ 6.5.11 editor 175
+
+ 7. Miscellany ............................................................ 175
+ 7.1 Acknowledgments ................................................. 176
+ 7.2 About this document ............................................. 178
x
projects / apps / madmutt.git / commitdiff