by Andreas Krennmair <ak@synflood.at> and others
originally based on _\bm_\bu_\bt_\bt by Michael Elkins <me@cs.hmc.edu> and others
- version devel-r460
+ version devel-r471
A\bAb\bbs\bst\btr\bra\bac\bct\bt
^G n/a abort
<Return> n/a finish editing
- You can remap the _\be_\bd_\bi_\bt_\bo_\br functions using the _\bb_\bi_\bn_\bd (section 3.5 , page 26) com-
+ You can remap the _\be_\bd_\bi_\bt_\bo_\br functions using the _\bb_\bi_\bn_\bd (section 3.5 , page 27) com-
mand. For example, to make the _\bD_\be_\bl_\be_\bt_\be key delete the character in front of the
cursor rather than under, you could use
+\bo c\bcl\ble\bea\bar\br-\b-f\bfl\bla\bag\bg (default: W)
Furthermore, the following flags reflect who the message is addressed to. They
- can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.330 , page 170) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.339 , page 172) variable.
+
message is to you and you only
letter again for bold or the letter, backspace, ``_'' for denoting underline.
Mutt-ng will attempt to display these in bold and underline respectively if
your terminal supports them. If not, you can use the bold and underline _\bc_\bo_\bl_\bo_\br
- (section 3.9 , page 30) objects to specify a color or mono attribute for them.
+ (section 3.9 , page 31) objects to specify a color or mono attribute for them.
Additionally, the internal pager supports the ANSI escape sequences for charac-
ter attributes. Mutt-ng translates them into the correct color and character
The Mutt Next Generation E-Mail Client 11
Mutt-ng uses these attributes for handling text/enriched messages, and they can
- also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 78) script for high-
+ also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 79) script for high-
lighting purposes. N\bNo\bot\bte\be:\b: If you change the colors for your display, for exam-
ple by changing the color associated with color2 for your xterm, then that
color will be used instead of green.
_\b2_\b._\b5_\b._\b3 _\bT_\bh_\br_\be_\ba_\bd_\be_\bd _\bM_\bo_\bd_\be
- When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.298 , page 160) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
+ When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.307 , page 163) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
a few additional functions available in the _\bi_\bn_\bd_\be_\bx and _\bp_\ba_\bg_\be_\br modes.
^D delete-thread delete all messages in the current thread
N\bNo\bot\bte\be:\b: Collapsing a thread displays only the first message in the thread and
hides the others. This is useful when threads contain so many messages that you
can only see a handful of threads on the screen. See %M in _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (sec-
- tion 7.4.116 , page 115). For example, you could use "%?M?(#%03M)&(%4l)?" in
- _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115) to optionally display the number of
+ tion 7.4.116 , page 116). For example, you could use "%?M?(#%03M)&(%4l)?" in
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116) to optionally display the number of
hidden messages if the thread is collapsed.
- See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 7.4.319 , page 167).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 7.4.328 , page 170).
_\b2_\b._\b5_\b._\b4 _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\be_\bo_\bu_\bs _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
(default: a)
Creates a new alias based upon the current message (or prompts for a new one).
- Once editing is complete, an _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 25) command is added to
- the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 89) variable for
- future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 89) does not
+ Once editing is complete, an _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 26) command is added to
+ the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 90) variable for
+ future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 90) does not
add the aliases specified there-in, you must also _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page
- 45) the file.
+ 46) the file.
c\bch\bhe\bec\bck\bk-\b-t\btr\bra\bad\bdi\bit\bti\bio\bon\bna\bal\bl-\b-p\bpg\bgp\bp
(default: ESC P)
(default: h)
Toggles the weeding of message header fields specified by _\bi_\bg_\bn_\bo_\br_\be (section
- 3.10 , page 32) commands.
+ 3.10 , page 33) commands.
e\bed\bdi\bit\bt
(default: e)
This command is used to temporarily edit an attachment's content type to fix,
for instance, bogus character set parameters. When invoked from the index or
from the pager, you'll have the opportunity to edit the top-level attachment's
- content type. On the _\ba_\bt_\bt_\ba_\bc_\bh_\bm_\be_\bn_\bt _\bm_\be_\bn_\bu (section 5.1.2 , page 70), you can
+ content type. On the _\ba_\bt_\bt_\ba_\bc_\bh_\bm_\be_\bn_\bt _\bm_\be_\bn_\bu (section 5.1.2 , page 71), you can
change any attachment's content type. These changes are not persistent, and get
lost upon changing folders.
Note that this command is also available on the _\bc_\bo_\bm_\bp_\bo_\bs_\be _\bm_\be_\bn_\bu (section 5.1.3 ,
- page 71). There, it's used to fine-tune the properties of attachments you are
+ page 72). There, it's used to fine-tune the properties of attachments you are
going to send.
e\ben\bnt\bte\ber\br-\b-c\bco\bom\bmm\bma\ban\bnd\bd
This command is used to execute any command you would normally put in a config-
uration file. A common use is to check the settings of variables, or in con-
- junction with _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 29) to change settings on the fly.
+ junction with _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 30) to change settings on the fly.
e\bex\bxt\btr\bra\bac\bct\bt-\b-k\bke\bey\bys\bs
(default: ^K)
Reply to the current or tagged message(s) by extracting any addresses which
match the regular expressions given by the _\bl_\bi_\bs_\bt_\bs _\bo_\br _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 ,
- page 35) commands, but also honor any Mail-Followup-To header(s) if the
- _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.94 , page 110) configuration variable is set.
+ page 36) commands, but also honor any Mail-Followup-To header(s) if the
+ _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.94 , page 111) configuration variable is set.
Using this when replying to messages posted to mailing lists helps avoid dupli-
cate copies being sent to the author of the message you are replying to.
(default: |)
Asks for an external Unix command and pipes the current or tagged message(s) to
- it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.207 , page 139), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
- (section 7.4.209 , page 140), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.208 , page 139) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.341 , page 172) control the exact behavior of this
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.216 , page 142), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 7.4.218 , page 142), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.217 , page 142) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.350 , page 174) control the exact behavior of this
function.
r\bre\bes\bse\ben\bnd\bd-\b-m\bme\bes\bss\bsa\bag\bge\be
message. This function is best described as "recall from arbitrary folders".
It can conveniently be used to forward MIME messages while preserving the orig-
inal mail structure. Note that the amount of headers included here depends on
- the value of the _\b$_\bw_\be_\be_\bd (section 7.4.342 , page 172) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 7.4.351 , page 175) variable.
This function is also available from the attachment menu. You can use this to
easily resend a message which was included with a bounce message as a mes-
(default: !)
Asks for an external Unix command and executes it. The _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section
- 7.4.341 , page 172) can be used to control whether Mutt-ng will wait for a key
+ 7.4.350 , page 174) can be used to control whether Mutt-ng will wait for a key
to be pressed when the command returns (presumably to let the user read the
output of the command), based on the return status of the named command.
t\bto\bog\bgg\bgl\ble\be-\b-q\bqu\buo\bot\bte\bed\bd
(default: T)
- The _\bp_\ba_\bg_\be_\br uses the _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.232 , page 145) variable to
+ The _\bp_\ba_\bg_\be_\br uses the _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.241 , page 147) variable to
detect quoted text when displaying the body of the message. This function tog-
gles the display of the quoted material in the message. It is particularly
useful when are interested in just the response and there is a large amount of
sages from. You can now tag messages in that folder and they will be attached
to the message you are sending. Note that certain operations like composing a
new mail, replying, forwarding, etc. are not permitted when you are in that
- folder. The %r in _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.315 , page 164) will change to a
+ folder. The %r in _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.324 , page 167) will change to a
'A' to indicate that you are in attach-message mode.
The Mutt Next Generation E-Mail Client 16
field, Mutt-ng will not generate a _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b: field, which allows you to cre-
ate a new message thread.
- Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102).
+ Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103).
_\b2_\b._\b6_\b._\b4 _\bU_\bs_\bi_\bn_\bg _\bM_\bu_\bt_\bt_\b-_\bn_\bg _\bw_\bi_\bt_\bh _\bP_\bG_\bP
Pgp: [ E | S | S_\b<_\bi_\bd_\b> ]
``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
- _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.199 , page 138) permanently.
+ _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.208 , page 140) permanently.
If you have told mutt to PGP encrypt a message, it will guide you through a key
selection process when you try to send the message. Mutt-ng will not ask you
encrypted using the selected public keys, and sent out.
Most fields of the entries in the key selection menu (see also _\b$_\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\b-
- _\bm_\ba_\bt (section 7.4.186 , page 134)) have obvious meanings. But some explana-
+ _\bm_\ba_\bt (section 7.4.195 , page 137)) have obvious meanings. But some explana-
tions on the capabilities, flags, and validity fields are in order.
The flags sequence (%f) will expand to one of the following flags:
Note that different remailers do have different capabilities, indicated in the
%c entry of the remailer menu lines (see _\b$_\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.146 ,
- page 124)). Most important is the ``middleman'' capability, indicated by a
+ page 125)). Most important is the ``middleman'' capability, indicated by a
capital ``M'': This means that the remailer in question cannot be used as the
final element of a chain, but will only forward messages to other mixmaster
remailers. For details on the other capabilities, please have a look at the
At times it is desirable to delay sending a message that you have already begun
to compose. When the _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be function is used in the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu,
the body of your message and attachments are stored in the mailbox specified by
- the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.221 , page 142) variable. This means that you can
+ the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.230 , page 145) variable. This means that you can
recall the message even if you exit Mutt-ng and then restart it at a later
time.
be in the same folder with the message you replied to for the status of the
message to be updated.
- See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.220 , page 142) quad-option.
+ See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.229 , page 145) quad-option.
_\b3_\b. _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn
out of the box, it is often desirable to tailor Mutt-ng to suit your own
tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
configuration file (defaults set by your local system administrator), unless
- the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 7.1 , page 82) option is specified. This
+ the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 7.1 , page 83) option is specified. This
file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
.muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
- your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 7.3 , page 85) to configure Mutt-ng.
+ your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 7.3 , page 86) to configure Mutt-ng.
_\b3_\b._\b2 _\bB_\ba_\bs_\bi_\bc _\bS_\by_\bn_\bt_\ba_\bx _\bo_\bf _\bI_\bn_\bi_\bt_\bi_\ba_\bl_\bi_\bz_\ba_\bt_\bi_\bo_\bn _\bF_\bi_\bl_\be_\bs
An initialization file consists of a series of _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 7.3 , page
- 85). Each line of the file may contain one or more commands. When multiple
+ 86). Each line of the file may contain one or more commands. When multiple
commands are used, they must be separated by a semicolon (;).
set realname='Mutt-ng user' ; ignore x-
interpreted again.
The commands understood by mutt are explained in the next paragraphs. For a
- complete list, see the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.3 , page 85).
+ complete list, see the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.3 , page 86).
The Mutt Next Generation E-Mail Client 23
- _\b3_\b._\b3 _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be _\bE_\bx_\bp_\ba_\bn_\bs_\bi_\bo_\bn
+ _\b3_\b._\b3 _\bE_\bx_\bp_\ba_\bn_\bs_\bi_\bo_\bn _\bw_\bi_\bt_\bh_\bi_\bn _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+
+ Besides just assign static content to variables, there's plenty of ways of
+ adding external and more or less dynamic content.
_\b3_\b._\b3_\b._\b1 _\bC_\bo_\bm_\bm_\ba_\bn_\bd_\bs_\b' _\bO_\bu_\bt_\bp_\bu_\bt
set record=+sent_on_$HOSTNAME
- sets the _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.237 , page 146) variable to the string _\b+_\bs_\be_\bn_\bt_\b__\bo_\bn_\b_
+ sets the _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.246 , page 148) variable to the string _\b+_\bs_\be_\bn_\bt_\b__\bo_\bn_\b_
and appends the value of the evironment variable $HOSTNAME.
N\bNo\bot\bte\be:\b: There will be no warning if an environment variable is not defined. The
set imap_home_namespace = $folder
- would set the value of _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.101 , page 112) to
- the value to which _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 104) is _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by set to.
+ would set the value of _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.101 , page 113) to
+ the value to which _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 105) is _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by set to.
N\bNo\bot\bte\be:\b: There're no logical links established in such cases so that the the value
- for _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.101 , page 112) won't change even if
- _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 104) gets changed.
+ for _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.101 , page 113) won't change even if
+ _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 105) gets changed.
N\bNo\bot\bte\be:\b: There will be no warning if a configuration variable is not defined or is
empty. The result will of the expansion will then be empty.
+ The Mutt Next Generation E-Mail Client 24
+
_\b3_\b._\b3_\b._\b4 _\bS_\be_\bl_\bf_\b-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
Mutt-ng flexibly allows users to define their own variables. To avoid conflicts
with the standard set and to prevent misleading error messages, there's a
-
- The Mutt Next Generation E-Mail Client 24
-
reserved namespace for them: all user-defined variables must be prefixed with
user_ and can be used just like any ordinary configuration or environment vari-
able.
for generic, pager and index. The alternative is to define a custom variable
like so:
- set user_manualcmd = '!less -r /path/to_manual'
+ set user_manualcmd = "!less -r /path/to_manual"
macro generic <F1> "$user_manualcmd<enter>" "Show manual"
macro pager <F1> "$user_manualcmd<enter>" "Show manual"
macro index <F1> "$user_manualcmd<enter>" "Show manual"
set ?user_foo
- will show 666. After doing the reset via
-
The Mutt Next Generation E-Mail Client 25
+ will show 666. After doing the reset via
+
reset user_foo
a following query will give 42 as the result. After unsetting it via
any query or operation (except the noted expansion within other statements)
will lead to an error message.
- _\b3_\b._\b3_\b._\b5 _\bT_\by_\bp_\be _\bC_\bo_\bn_\bv_\be_\br_\bs_\bi_\bo_\bn_\bs
+ _\b3_\b._\b3_\b._\b5 _\bP_\br_\be_\b-_\bD_\be_\bf_\bi_\bn_\be_\bd _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+
+ In order to allow users to share one setup over a number of different machines
+ without having to change its contents, there's a number of pre-defined vari-
+ ables. These are prefixed with muttng_ and are read-only, i.e. they cannot be
+ set, unset or reset. The reference chapter lists all available variables.
+
+ _\bP_\bl_\be_\ba_\bs_\be _\bc_\bo_\bn_\bs_\bu_\bl_\bt _\bt_\bh_\be _\bl_\bo_\bc_\ba_\bl _\bc_\bo_\bp_\by _\bo_\bf _\by_\bo_\bu_\br _\bm_\ba_\bn_\bu_\ba_\bl _\bf_\bo_\br _\bt_\bh_\be_\bi_\br _\bv_\ba_\bl_\bu_\be_\bs _\ba_\bs _\bt_\bh_\be_\by _\bm_\ba_\by _\bd_\bi_\bf_\b-
+ _\bf_\be_\br _\bf_\br_\bo_\bm _\bd_\bi_\bf_\bf_\be_\br_\be_\bn_\bt _\bm_\ba_\bn_\bu_\ba_\bl _\bs_\bo_\bu_\br_\bc_\be_\bs_\b. Where the manual is installed in can be
+ queried (already using such a variable) by running:
+
+ muttng -Q muttng_docdir
+
+ To extend the example for viewing the manual via self-defined variables, it can
+ be made more readable and more portable by changing the real path in:
+
+ set user_manualcmd = '!less -r /path/to_manual'
+
+ to:
+
+ set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
+
+ which works everywhere if a manual is installed.
+
+ Please note that by the type of quoting, muttng determines when to expand these
+ values: when it finds double quotes, the value will be expanded during reading
+ the setup files but when it finds single quotes, it'll expand it at runtime as
+ needed.
+
+ For example, the statement
+
+ folder-hook . "set user_current_folder = $muttng_folder_name"
+
+ The Mutt Next Generation E-Mail Client 26
+
+ will be already be translated to the following when reading the startup files:
+
+ folder-hook . "set user_current_folder = some_folder"
+
+ with some_folder being the name of the first folder muttng opens. On the con-
+ trary,
+
+ folder-hook . 'set user_current_folder = $muttng_folder_name'
+
+ will be executed at runtime because of the single quotes so that user_cur-
+ rent_folder will always have the value of the currently opened folder.
+
+ A more practical example is:
+
+ folder-hook . 'source ~/.mutt/score-$muttng_folder_name'
+
+ which can be used to source files containing score commands depending on the
+ folder the user enters.
+
+ _\b3_\b._\b3_\b._\b6 _\bT_\by_\bp_\be _\bC_\bo_\bn_\bv_\be_\br_\bs_\bi_\bo_\bn_\bs
A note about variable's types during conversion: internally values are stored
in internal types but for any dump/query or set operation they're converted to
To remove an alias or aliases (``*'' means all aliases):
+ The Mutt Next Generation E-Mail Client 27
+
unalias [ * | _\bk_\be_\by _\b._\b._\b. ]
alias muttdude me@cs.hmc.edu (Michael Elkins)
Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
cial file. The alias command can appear anywhere in a configuration file, as
- long as this file is _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.29 , page 45). Consequently, you can
+ long as this file is _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.29 , page 46). Consequently, you can
have multiple alias files, or you can have all aliases defined in your muttrc.
On the other hand, the _\bc_\br_\be_\ba_\bt_\be_\b-_\ba_\bl_\bi_\ba_\bs (section 2.5.4 , page 11) function can use
-
- The Mutt Next Generation E-Mail Client 26
-
- only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 89)
+ only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 90)
variable (which is ~/.muttrc by default). This file is not special either, in
the sense that Mutt-ng will happily append aliases to any file, but in order
for the new aliases to take effect you need to explicitly _\bs_\bo_\bu_\br_\bc_\be (section
- 3.29 , page 45) this file too.
+ 3.29 , page 46) this file too.
For example:
To use aliases, you merely use the alias at any place in mutt where mutt
prompts for addresses, such as the _\bT_\bo_\b: or _\bC_\bc_\b: prompt. You can also enter
aliases in your editor at the appropriate headers if you have the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs
- (section 7.4.59 , page 102) variable set.
+ (section 7.4.59 , page 103) 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
fied by separating them with commas (no additional whitespace is allowed). The
currently defined maps are:
+ The Mutt Next Generation E-Mail Client 28
+
generic
This is not a real menu, but is used as a fallback for all of the
other menus except for the pager and editor modes. If a key is not
alias
The alias menu is the list of your personal aliases as defined in
-
- The Mutt Next Generation E-Mail Client 27
-
your muttrc. It is the mapping from a short alias name to the full
email address(es) of the recipient(s).
In addition, _\bk_\be_\by may consist of:
- The Mutt Next Generation E-Mail Client 28
+ The Mutt Next Generation E-Mail Client 29
\t tab
<tab> tab
_\bk_\be_\by does not need to be enclosed in quotes unless it contains a space (`` '').
_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn specifies which action to take when _\bk_\be_\by is pressed. For a complete
- list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 174). The special
+ list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 177). The special
function noop unbinds the specified key sequence.
_\b3_\b._\b6 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs _\bf_\bo_\br _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bs_\be_\bt_\bs
It is often desirable to change settings based on which mailbox you are
- The Mutt Next Generation E-Mail Client 29
+ The Mutt Next Generation E-Mail Client 30
reading. The folder-hook command provides a method by which you can execute
any configuration command. _\br_\be_\bg_\be_\bx_\bp is a regular expression specifying in which
mailboxes to execute _\bc_\bo_\bm_\bm_\ba_\bn_\bd before loading. If a mailbox matches multiple
folder-hook's, they are executed in the order given in the muttrc.
- N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.304 , page
- 162) at the beginning of the pattern, you must place it inside of double or
+ N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.313 , page
+ 165) 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.
typed _\bs_\be_\bq_\bu_\be_\bn_\bc_\be. So if you have a common sequence of commands you type, you can
create a macro to execute those commands with a single key.
- _\bm_\be_\bn_\bu is the _\bm_\ba_\bp (section 3.5 , page 26) which the macro will be bound. Multi-
+ _\bm_\be_\bn_\bu is the _\bm_\ba_\bp (section 3.5 , page 28) which the macro will be bound. Multi-
ple maps may be specified by separating multiple menu arguments by commas.
Whitespace may not be used in between the menu arguments and the commas sepa-
rating them.
_\bk_\be_\by and _\bs_\be_\bq_\bu_\be_\bn_\bc_\be are expanded by the same rules as the _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs (section
- 3.5 , page 26). There are some additions however. The first is that control
+ 3.5 , page 27). There are some additions however. The first is that control
characters in _\bs_\be_\bq_\bu_\be_\bn_\bc_\be can also be specified as _\b^_\bx. In order to get a caret
(`^'') you need to use _\b^_\b^. Secondly, to specify a certain key such as _\bu_\bp or to
invoke a function directly, you can use the format _\b<_\bk_\be_\by _\bn_\ba_\bm_\be_\b> and _\b<_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
_\bn_\ba_\bm_\be_\b>. For a listing of key names see the section on _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs (section
- 3.5 , page 26). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
- 7.5 , page 174).
+ 3.5 , page 27). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
+ 7.5 , page 177).
The advantage with using function names directly is that the macros will work
regardless of the current key bindings, so they are not dependent on the user
having particular key definitions. This makes them more robust and portable,
and also facilitates defining of macros in files used by more than one user
- The Mutt Next Generation E-Mail Client 30
+ The Mutt Next Generation E-Mail Client 31
(eg. the system Muttngrc).
+\bo normal
- +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.232 , page 145) in the
+ +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.241 , page 147) in the
body of a message)
+\bo quoted1, quoted2, ..., quotedN\bN (higher levels of quoting)
+\bo search (highlighting of words in the pager)
- The Mutt Next Generation E-Mail Client 31
+ The Mutt Next Generation E-Mail Client 32
+\bo signature
command for it to be removed. The pattern ``*'' is a special token which means
to clear the color index list of all entries.
- The Mutt Next Generation E-Mail Client 32
+ The Mutt Next Generation E-Mail Client 33
Mutt-ng also recognizes the keywords _\bc_\bo_\bl_\bo_\br_\b0, _\bc_\bo_\bl_\bo_\br_\b1, ..., _\bc_\bo_\bl_\bo_\brN\bN-\b-1\b1 (N\bN being the
number of colors supported by your terminal). This is useful when you remap
unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
unignore posted-to:
- The Mutt Next Generation E-Mail Client 33
+ The Mutt Next Generation E-Mail Client 34
_\b3_\b._\b1_\b1 _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be _\ba_\bd_\bd_\br_\be_\bs_\bs_\be_\bs
instance, when replying to a message that you sent to a different party, mutt
will automatically suggest to send the response to the original message's
recipients -- responding to yourself won't make much sense in many cases. (See
- _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.240 , page 147).)
+ _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.249 , page 149).)
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
your terminal. If you want a fixed margin on the right side of your terminal,
you can set the following:
- The Mutt Next Generation E-Mail Client 34
+ The Mutt Next Generation E-Mail Client 35
set wrapmargin = 10
set text_flowed
- The Mutt Next Generation E-Mail Client 35
+ The Mutt Next Generation E-Mail Client 36
Additionally, you have to use an editor which supports writing format=flowed-
conforming emails. For vim, this is done by adding w to the formatoptions (see
"
- For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.51 , page 100) variable pro-
+ For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.51 , page 101) variable pro-
vides the mechanism to generate a DelSp=yes parameter on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg messages.
According to the standard, clients receiving a format=flowed messages should
delete the last space of a flowed line but still interpret the line as flowed.
Usage: [un]subscribe _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
Mutt-ng has a few nice features for _\bh_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bm_\ba_\bi_\bl_\bi_\bn_\bg _\bl_\bi_\bs_\bt_\bs (section 4.10 ,
- page 60). In order to take advantage of them, you must specify which addresses
+ page 61). In order to take advantage of them, you must specify which addresses
belong to mailing lists, and which mailing lists you are subscribed to. Once
you have done this, the _\bl_\bi_\bs_\bt_\b-_\br_\be_\bp_\bl_\by (section 2.5.4 , page 12) function will
work for all known lists. Additionally, when you send a message to a sub-
the Mail-Followup-To header is a non-standard extension which is not supported
by all mail user agents. Adding it is not bullet-proof against receiving per-
sonal CCs of list messages. Also note that the generation of the Mail-Fol-
- lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.72 , page 105)
+ lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.72 , page 106)
configuration variable.
- The Mutt Next Generation E-Mail Client 36
+ The Mutt Next Generation E-Mail Client 37
More precisely, Mutt-ng maintains lists of patterns for the addresses of known
and subscribed mailing lists. Every subscribed mailing list is known. To mark
Pressing TAB in the directory browser will bring up a menu showing the files
specified by the mailboxes command, and indicate which contain new messages.
- The Mutt Next Generation E-Mail Client 37
+ The Mutt Next Generation E-Mail Client 38
Mutt-ng will automatically enter this mode when invoked from the command line
with the -y option.
N\bNo\bot\bte\be:\b: the filenames in the mailboxes command are resolved when the command is
executed, so if these names contain _\bs_\bh_\bo_\br_\bt_\bc_\bu_\bt _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br_\bs (section 4.9 , page
- 60) (such as ``='' and ``!''), any variable definition that affect these char-
- acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 104) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 7.4.304 , page 162)) should be executed before the mailboxes command.
+ 61) (such as ``='' and ``!''), any variable definition that affect these char-
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 105) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 7.4.313 , page 165)) should be executed before the mailboxes command.
_\b3_\b._\b1_\b6 _\bU_\bs_\be_\br _\bd_\be_\bf_\bi_\bn_\be_\bd _\bh_\be_\ba_\bd_\be_\br_\bs
there, so Mutt-ng enforces the rule.
If you would like to add a header field to a single message, you should either
- set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102) variable, or use the _\be_\bd_\bi_\bt_\b-
+ set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103) variable, or use the _\be_\bd_\bi_\bt_\b-
_\bh_\be_\ba_\bd_\be_\br_\bs function (default: ``E'') in the send-menu so that you can edit the
header of your message along with the body.
remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
use:
- The Mutt Next Generation E-Mail Client 38
+ The Mutt Next Generation E-Mail Client 39
unmy_hdr to cc
an address matching _\br_\be_\bg_\be_\bx_\bp or if you are the author and the message is
addressed _\bt_\bo_\b: something matching _\br_\be_\bg_\be_\bx_\bp.
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
+ See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 58) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Examples:
save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
save-hook aol\\.com$ +spam
- Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 39) command.
+ Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 40) command.
_\b3_\b._\b1_\b9 _\bS_\bp_\be_\bc_\bi_\bf_\by _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bF_\bc_\bc_\b: _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\bw_\bh_\be_\bn _\bc_\bo_\bm_\bp_\bo_\bs_\bi_\bn_\bg
Usage: fcc-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is used to save outgoing mail in a mailbox other than _\b$_\br_\be_\bc_\bo_\br_\bd
- (section 7.4.237 , page 146). Mutt-ng searches the initial list of message
+ (section 7.4.246 , page 148). Mutt-ng searches the initial list of message
recipients for the first matching _\br_\be_\bg_\be_\bx_\bp and uses _\bm_\ba_\bi_\bl_\bb_\bo_\bx as the default Fcc:
mailbox. If no match is found the message will be saved to _\b$_\br_\be_\bc_\bo_\br_\bd (section
- 7.4.237 , page 146) mailbox.
+ 7.4.246 , page 148) mailbox.
- The Mutt Next Generation E-Mail Client 39
+ The Mutt Next Generation E-Mail Client 40
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
+ 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 58) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example: fcc-hook [@.]aol\\.com$ +spammers
The above will save a copy of all messages going to the aol.com domain to the
`+spammers' mailbox by default. Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 ,
- page 39) command.
+ page 40) command.
_\b3_\b._\b2_\b0 _\bS_\bp_\be_\bc_\bi_\bf_\by _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be _\ba_\bn_\bd _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bF_\bc_\bc_\b: _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\ba_\bt _\bo_\bn_\bc_\be
Usage: fcc-save-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is a shortcut, equivalent to doing both a _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section
- 3.19 , page 38) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 38) with its arguments.
+ 3.19 , page 39) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 39) with its arguments.
_\b3_\b._\b2_\b1 _\bC_\bh_\ba_\bn_\bg_\be _\bs_\be_\bt_\bt_\bi_\bn_\bg_\bs _\bb_\ba_\bs_\be_\bd _\bu_\bp_\bo_\bn _\bm_\be_\bs_\bs_\ba_\bg_\be _\br_\be_\bc_\bi_\bp_\bi_\be_\bn_\bt_\bs
send2-hook is matched every time a message is changed, either by editing it, or
by using the compose menu to change its recipients or subject. send2-hook is
executed after send-hook, and can, e.g., be used to set parameters such as the
- _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.254 , page 150) variable depending on the message's
+ _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.263 , page 152) variable depending on the message's
sender address.
For each type of send-hook or reply-hook, when multiple matches occur, commands
are executed in the order they are specified in the muttrc (for that type of
hook).
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
+ 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 58) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example: send-hook mutt 'set mime_forward signature='''
Another typical use for this command is to change the values of the
- The Mutt Next Generation E-Mail Client 40
+ The Mutt Next Generation E-Mail Client 41
- _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 93), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.266 , page
- 153) and _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.120 , page 119) variables in order to change the
+ _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 94), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.275 , page
+ 155) and _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.120 , page 120) 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
tiple matches occur, commands are executed in the order they are specified in
the muttrc.
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 57) for information on the
+ See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 58) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example:
This command adds the named string to the keyboard buffer. The string may
- The Mutt Next Generation E-Mail Client 41
+ The Mutt Next Generation E-Mail Client 42
contain control characters, key names and function names like the sequence
- string in the _\bm_\ba_\bc_\br_\bo (section 3.8 , page 29) command. You may use it to auto-
+ string in the _\bm_\ba_\bc_\br_\bo (section 3.8 , page 30) command. You may use it to auto-
matically run a sequence of commands at startup, or when entering certain fold-
ers.
Usage: exec _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
This command can be used to execute any function. Functions are listed in the
- _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 174). ``exec function'' is equivalent
+ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 177). ``exec function'' is equivalent
to ``push <function>''.
_\b3_\b._\b2_\b6 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bS_\bc_\bo_\br_\bi_\bn_\bg
+\bo flag threshold: when a message has a score value equal or higher than the
flag threshold, it will be flagged.
- The Mutt Next Generation E-Mail Client 42
+ The Mutt Next Generation E-Mail Client 43
+\bo read threshold: when a message has a score value equal or lower than the
read threshold, it will be marked as read.
delete threshold, it will be marked as deleted.
These three thresholds can be set via the variables _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bf_\bl_\ba_\bg (sec-
- tion 7.4.251 , page 149), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.252 , page 150),
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.250 , page 149) and. By default,
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.252 , page 150) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
- (section 7.4.250 , page 149) are set to -1, which means that in the default
+ tion 7.4.260 , page 152), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.261 , page 152),
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.259 , page 152) and. By default,
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.261 , page 152) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
+ (section 7.4.259 , page 152) are set to -1, which means that in the default
threshold configuration no message will ever get marked as read or deleted.
Scoring gets especially interesting when combined with the color command and
your spam patterns with the spam and nospam commands, you can _\bl_\bi_\bm_\bi_\bt, _\bs_\be_\ba_\br_\bc_\bh,
and _\bs_\bo_\br_\bt your mail based on its spam attributes, as determined by the external
filter. You also can display the spam attributes in your index display using
- the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115) variable.
+ the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116) variable.
(Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
given message.)
If you're using multiple spam filters, a message can have more than one spam-
- The Mutt Next Generation E-Mail Client 43
+ The Mutt Next Generation E-Mail Client 44
related header. You can define spam patterns for each filter you use. If a mes-
sage matches two or more of these patterns, and the $spam_separator variable is
matches an entry on the nospam list, that nospam entry will be removed. If the
_\bp_\ba_\bt_\bt_\be_\br_\bn for nospam is ``*'', _\ba_\bl_\bl _\be_\bn_\bt_\br_\bi_\be_\bs _\bo_\bn _\bb_\bo_\bt_\bh _\bl_\bi_\bs_\bt_\bs will be removed. This
- The Mutt Next Generation E-Mail Client 44
+ The Mutt Next Generation E-Mail Client 45
might be the default action if you use spam and nospam in conjunction with a
folder-hook.
Usage: reset _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
This command is used to set (and unset) _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 ,
- page 87). There are four basic types of variables: boolean, number, string and
+ page 88). There are four basic types of variables: boolean, number, string and
quadoption. _\bb_\bo_\bo_\bl_\be_\ba_\bn variables can be _\bs_\be_\bt (true) or _\bu_\bn_\bs_\be_\bt (false). _\bn_\bu_\bm_\bb_\be_\br
variables can be assigned a positive integer value.
Using the enter-command function in the _\bi_\bn_\bd_\be_\bx menu, you can query the value of
a variable by prefixing the name of the variable with a question mark:
- The Mutt Next Generation E-Mail Client 45
+ The Mutt Next Generation E-Mail Client 46
set ?allow_8bit
note that while reading the configuration files, this is only respected after
the corresponding declaration appears. It's advised to put the following at the
- The Mutt Next Generation E-Mail Client 46
+ The Mutt Next Generation E-Mail Client 47
very beginning of a users muttngrc:
All available functions, variables and menus are documented elsewhere in this
manual but ``features'' is specific to these two commands. To test for one,
- The Mutt Next Generation E-Mail Client 47
+ The Mutt Next Generation E-Mail Client 48
prefix one of the following keywords with feature_:
An example for testing for variable names can be used if users use different
revisions of mutt-ng whereby the older one may not have a certain variable. To
- test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.105 , page 113),
+ test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.105 , page 114),
use:
ifdef imap_mail_check 'set imap_mail_check = 300'
Provided for completeness is the test for menu names. To set _\b$_\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
- (section 7.4.176 , page 132) only if the pager menu is available, use:
+ (section 7.4.185 , page 134) 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'
- The Mutt Next Generation E-Mail Client 48
+ The Mutt Next Generation E-Mail Client 49
_\b3_\b._\b3_\b2 _\bO_\bb_\bs_\bo_\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
In the process of ensuring and creating more consistency, many variables have
been renamed and some of the old names were already removed. Please see _\bO_\bb_\bs_\bo_\b-
- _\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 , page 87) for a complete list.
+ _\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 , page 88) for a complete list.
_\b4_\b. _\bA_\bd_\bv_\ba_\bn_\bc_\be_\bd _\bU_\bs_\ba_\bg_\be
_\b4_\b._\b1 _\bR_\be_\bg_\bu_\bl_\ba_\br _\bE_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs
All string patterns in Mutt-ng including those in more complex _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
- tion 7.2 , page 83) must be specified using regular expressions (regexp) in
+ tion 7.2 , page 84) 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.
place it anywhere but first. Finally, to include a literal hyphen ``-'' place
it last.
- The Mutt Next Generation E-Mail Client 49
+ The Mutt Next Generation E-Mail Client 50
Certain named classes of characters are predefined. Character classes consist
of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
Collating Symbols
A collating symbol is a multi-character collating element enclosed
- The Mutt Next Generation E-Mail Client 50
+ The Mutt Next Generation E-Mail Client 51
in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
ment, then [\b[[\b[.\b.c\bch\bh.\b.]\b]]\b] is a regexp that matches this collating ele-
Matches the empty string at either the beginning or the end of a
word.
- The Mutt Next Generation E-Mail Client 51
+ The Mutt Next Generation E-Mail Client 52
\\B
Matches the empty string within a word.
to match messages, e.g. for operations like tagging and scoring. A pattern con-
sists of one or more sub-pattern, which can be logically grouped, ORed, and
negated. For a complete listing of these patterns, please refer to table _\bP_\ba_\bt_\b-
- _\bt_\be_\br_\bn_\bs (section 7.2 , page 83) in the Reference chapter.
+ _\bt_\be_\br_\bn_\bs (section 7.2 , page 84) in the Reference chapter.
It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
To logical OR patterns, simply use the | operator. This one especially useful
when using local groups:
- The Mutt Next Generation E-Mail Client 52
+ The Mutt Next Generation E-Mail Client 53
~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
(~b mutt-ng|~s Mutt-ng)
_\b4_\b._\b3_\b._\b1 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn
- The Mutt Next Generation E-Mail Client 53
+ The Mutt Next Generation E-Mail Client 54
The so called _\bF_\bo_\br_\bm_\ba_\bt _\bS_\bt_\br_\bi_\bn_\bg_\bs offer great flexibility when configuring mutt-ng.
In short, they describe what items to print out how in menus and status mes-
+\bo the current mutt-ng version number
The setting for the status bar of the index is controlled via the _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\b-
- _\bm_\ba_\bt (section 7.4.315 , page 164) variable. For the hostname and version
+ _\bm_\ba_\bt (section 7.4.324 , page 167) 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:
For the number of certain types of messages, one more feature of the format
strings is extremely useful. If there aren't messages of a certain type, it may
- The Mutt Next Generation E-Mail Client 54
+ The Mutt Next Generation E-Mail Client 55
not be desired to print just that there aren't any but instead only print some-
thing if there are any.
set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
- The Mutt Next Generation E-Mail Client 55
+ The Mutt Next Generation E-Mail Client 56
As you might see from this rather simple example, one can create very complex
but fancy status messages. Please see the reference chapter for expandos and
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
- The Mutt Next Generation E-Mail Client 56
+ The Mutt Next Generation E-Mail Client 57
- default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 83) for Mutt-ng's pattern matching
+ default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 84) for Mutt-ng's pattern matching
syntax.
Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
operator is used, the n\bne\bex\bxt\bt operation will be applied to all tagged messages if
that operation can be used in that manner. If the _\b$_\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg (section 7.4.19 ,
- page 93) variable is set, the next operation applies to the tagged messages
+ page 94) variable is set, the next operation applies to the tagged messages
automatically, without requiring the ``tag-prefix''.
- In _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 29) or _\bp_\bu_\bs_\bh (section 3.24 , page 40) commands,
+ In _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 30) or _\bp_\bu_\bs_\bh (section 3.24 , page 41) commands,
you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
stop "eating" the macro when it encounters the ``end-cond'' operator; after
arbitrary commands before performing some operation. For example, you may wish
to tailor your configuration based upon which mailbox you are reading, or to
whom you are sending mail. In the Mutt-ng world, a _\bh_\bo_\bo_\bk consists of a _\br_\be_\bg_\bu_\bl_\ba_\br
- _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 48) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 83) along
+ _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 49) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 84) along
with a configuration option/command. See
- +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 28)
+ +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 29)
- +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 39)
+ +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 40)
- +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 40)
+ +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 41)
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 38)
+ +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 39)
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36)
+ +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 37)
- +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)
+ +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 39)
- +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 39)
+ +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 40)
for specific details on each type of _\bh_\bo_\bo_\bk available.
send-hook . 'unmy_hdr From:'
send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
- The Mutt Next Generation E-Mail Client 57
+ The Mutt Next Generation E-Mail Client 58
_\b4_\b._\b5_\b._\b1 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs
Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
evaluated in a slightly different manner. For the other types of hooks, a _\br_\be_\bg_\b-
- _\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 48) is sufficient. But in dealing with
+ _\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 49) is sufficient. But in dealing with
messages a finer grain of control is needed for matching since for different
purposes you want to match different criteria.
- Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 83) language
+ Mutt-ng allows the use of the _\bs_\be_\ba_\br_\bc_\bh _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 84) language
for matching messages in hook commands. This works in exactly the same way as
it would when _\bl_\bi_\bm_\bi_\bt_\bi_\bn_\bg or _\bs_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg the mailbox, except that you are restricted
to those operators which match information mutt extracts from the header of the
searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the
other hooks, in which case Mutt-ng will translate your pattern into the full
language, using the translation specified by the _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section
- 7.4.49 , page 100) variable. The pattern is translated at the time the hook
- is declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 7.4.49 , page 100) that is
+ 7.4.49 , page 101) variable. The pattern is translated at the time the hook
+ is declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 7.4.49 , page 101) 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
You can also specify the colors for mailboxes with new mails by using:
- The Mutt Next Generation E-Mail Client 58
+ The Mutt Next Generation E-Mail Client 59
color sidebar_new red black
color sidebar white black
Mutt-ng supports connecting to external directory databases such as LDAP,
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
- simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.228 , page 144) vari-
+ simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.237 , page 146) vari-
able, you specify the wrapper command to use. For example:
set query_command = "mutt_ldap_query.pl '%s'"
me@cs.hmc.edu Michael Elkins mutt dude
blong@fiction.net Brandon Long mutt and more
- The Mutt Next Generation E-Mail Client 59
+ The Mutt Next Generation E-Mail Client 60
roessler@guug.de Thomas Roessler mutt pgp
Mutt-ng supports reading and writing of four different mailbox formats: mbox,
MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
- uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.132 , page 121)
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.132 , page 122)
variable.
m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All messages are
the mailbox: _\bt_\bm_\bp, _\bn_\be_\bw and _\bc_\bu_\br. Filenames for the messages are chosen in such a
way they are unique, even when two programs are writing the mailbox over NFS,
- The Mutt Next Generation E-Mail Client 60
+ The Mutt Next Generation E-Mail Client 61
which means that no file locking is needed.
These shortcuts can be used anywhere you are prompted for a file or mailbox
path.
- +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.304 , page 162) (incoming)
+ +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.313 , page 165) (incoming)
mailbox
- +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.131 , page 121) file
+ +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.131 , page 122) file
- +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.237 , page 146) file
+ +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.246 , page 148) file
+\bo ^ -- refers to the current mailbox
+\bo ~ -- refers to your home directory
- +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 104) directory
+ +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 105) directory
- +\bo @_\ba_\bl_\bi_\ba_\bs -- refers to the _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bo_\bl_\bd_\be_\br (section 3.18 , page 38) as
+ +\bo @_\ba_\bl_\bi_\ba_\bs -- refers to the _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bo_\bl_\bd_\be_\br (section 3.18 , page 39) as
determined by the address of the alias
_\b4_\b._\b1_\b0 _\bH_\ba_\bn_\bd_\bl_\bi_\bn_\bg _\bM_\ba_\bi_\bl_\bi_\bn_\bg _\bL_\bi_\bs_\bt_\bs
you consider to be mailing lists (technically this does not have to be a mail-
ing list, but that is what it is most often used for), and what lists you are
subscribed to. This is accomplished through the use of the _\bl_\bi_\bs_\bt_\bs _\ba_\bn_\bd _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be
- (section 3.13 , page 35) commands in your muttrc.
+ (section 3.13 , page 36) commands in your muttrc.
Now that Mutt-ng knows what your mailing lists are, it can do several things,
the first of which is the ability to show the name of a list through which you
received a message (i.e., of a subscribed list) in the _\bi_\bn_\bd_\be_\bx menu display.
This is useful to distinguish between personal and list mail in the same mail-
- box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115) variable, the escape
+ box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116) variable, the escape
``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
returns the name of the author).
_\bi_\bn_\bd_\be_\bx menu and _\bp_\ba_\bg_\be_\br, helps reduce the clutter by only replying to the known
mailing list addresses instead of all recipients (except as specified by Mail-
- The Mutt Next Generation E-Mail Client 61
+ The Mutt Next Generation E-Mail Client 62
Followup-To, see below).
Mutt-ng also supports the Mail-Followup-To header. When you send a message to
a list of recipients which includes one or several subscribed mailing lists,
- and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.72 , page 105) option is set, mutt will
+ and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.72 , page 106) option is set, mutt will
generate a Mail-Followup-To header which contains all the recipients to whom
you send this message, but not your address. This indicates that group-replies
or list-replies (also known as ``followups'') to this message should only be
Conversely, when group-replying or list-replying to a message which has a Mail-
Followup-To header, mutt will respect this header if the _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
- (section 7.4.94 , page 110) configuration variable is set. Using list-reply
+ (section 7.4.94 , page 111) configuration variable is set. Using list-reply
will in this case also make sure that the reply goes to the mailing list, even
if it's not specified in the list of recipients in the Mail-Followup-To.
the message. This can create problems when trying to reply directly to the
author in private, since most mail clients will automatically reply to the
address given in the ``Reply-To'' field. Mutt-ng uses the _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section
- 7.4.240 , page 147) variable to help decide which address to use. If set to
+ 7.4.249 , page 149) variable to help decide which address to use. If set to
_\ba_\bs_\bk_\b-_\by_\be_\bs or _\ba_\bs_\bk_\b-_\bn_\bo, you will be prompted as to whether or not you would like to
use the address given in the ``Reply-To'' field, or reply directly to the
address given in the ``From'' field. When set to _\by_\be_\bs, the ``Reply-To'' field
The ``X-Label:'' header field can be used to further identify mailing lists or
list subject matter (or just to annotate messages individually). The
- _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115) variable's ``%y'' and ``%Y''
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116) variable's ``%y'' and ``%Y''
escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
pattern-matcher can match regular expressions to ``X-Label:'' fields with the
``~y'' selector. ``X-Label:'' is not a standard message header field, but it
can easily be inserted by procmail and other mail filtering agents.
- Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 7.4.298 , page 160) the mail-
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 7.4.307 , page 163) 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 graphi-
Mutt-ng has the ability to dynamically restructure threads that are broken
- The Mutt Next Generation E-Mail Client 62
+ The Mutt Next Generation E-Mail Client 63
either by misconfigured software or bad behavior from some correspondents. This
allows to clean your mailboxes formats) from these annoyances which make it
To support this, there are two variables:
- +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.56 , page 101) is used to request receipts for
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.56 , page 102) is used to request receipts for
different results (such as failed message, message delivered, etc.).
- +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 7.4.57 , page 102) requests how much of your message
+ +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 7.4.57 , page 103) requests how much of your message
should be returned with the receipt (headers or full message).
Please see the reference chapter for possible values.
_\b4_\b._\b1_\b3 _\bP_\bO_\bP_\b3 _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
- The Mutt Next Generation E-Mail Client 63
+ The Mutt Next Generation E-Mail Client 64
If Mutt-ng was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bp_\bo_\bp flag), it has the ability to work with mailboxes located on a
Polling for new mail is more expensive over POP3 than locally. For this reason
the frequency at which Mutt-ng will check for mail remotely can be controlled
- by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.215 , page 141) variable, which defaults
+ by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.224 , page 144) variable, which defaults
to every 60 seconds.
If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
name@]popserver[:port]/.
Another way to access your POP3 mail is the _\bf_\be_\bt_\bc_\bh_\b-_\bm_\ba_\bi_\bl function (default: G).
- It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.213 , page 141), fetch all your
- new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.304 , page 162).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.222 , page 143), fetch all your
+ new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.313 , page 165).
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-
If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
- The Mutt Next Generation E-Mail Client 64
+ The Mutt Next Generation E-Mail Client 65
the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This natu-
rally requires that the server supports SSL encrypted connections. To access a
When browsing folders on an IMAP server, you can toggle whether to look at only
the folders you are subscribed to, or all folders with the _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
- command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.103 , page 113)
+ command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.103 , page 114)
variable.
Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
- want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.105 , page 113) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.328 , page 169) variables.
+ want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.105 , page 114) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.337 , page 172) 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
which allows you to log in to a public IMAP server without having an account.
To use ANONYMOUS, simply make your username blank or "anonymous".
- The Mutt Next Generation E-Mail Client 65
+ The Mutt Next Generation E-Mail Client 66
SASL is a special super-authenticator, which selects among several protocols
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
There are a few variables which control authentication:
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.111 , page 114) - controls the username under
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.111 , page 115) - controls the username under
which you request authentication on the IMAP server, for all authentica-
tors. This is overridden by an explicit username in the mailbox path (i.e.
by using a mailbox name of the form {user@host}).
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.106 , page 113) - a password which you may pre-
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.106 , page 114) - a password which you may pre-
set, used by all authentication methods where a password is needed.
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs (section 7.4.97 , page 111) - a colon-delimited list
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs (section 7.4.97 , page 112) - a colon-delimited list
of IMAP authentication methods to try, in the order you wish to try them.
If specified, this overrides mutt's default (attempt everything, in the
order listed above).
The Default newsserver can be obtained from the $NNTPSERVER environment vari-
able. Like other news readers, info about subscribed newsgroups is saved in a
- file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 7.4.163 , page 129) variable.
+ file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 7.4.172 , page 131) 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
to use a killfile has been discussed in _\bM_\be_\bs_\bs_\ba_\bg_\be _\bs_\bc_\bo_\br_\bi_\bn_\bg (section 3.26 , page
- 41).
+ 42).
What has not been discusses in detail is mutt-ng's built-in realname filter.
For may newsreaders including those for ``advanced users'' like _\bs_\bl_\br_\bn or _\bt_\bi_\bn,
In mutt-ng this is as easy as
- The Mutt Next Generation E-Mail Client 66
+ The Mutt Next Generation E-Mail Client 67
score ~* =42
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 62) section) as well as handling the 8BIT-
- MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.335 , page 171).
+ _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 63) section) as well as handling the 8BIT-
+ MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.344 , page 173).
To enable sending mail directly via SMTP without an MTA such as Postfix or
- SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.293 , page 159)
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.302 , page 161)
variable pointing to your SMTP server.
- Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 7.4.297 ,
- page 160) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.294 , page 159) variables.
+ Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 7.4.306 ,
+ page 162) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.303 , page 162) variables.
Transport Encryption via the StartTLS command is also available. For this to
work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
- _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 7.4.296 , page 160) variable must be either set to
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 7.4.305 , page 162) variable must be either set to
``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
supports it: for the second case, the connection will fail if it doesn't while
switching back to unencrypted communication for the first one.
Some mail providers require user's to set a particular envelope sender, i.e.
- The Mutt Next Generation E-Mail Client 67
+ The Mutt Next Generation E-Mail Client 68
they allow for only one value which may not be what the user wants to send as
- the From: header. In this case, the variable _\b$_\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be (section 7.4.292 ,
- page 159) may be used to set the envelope different from the From: header.
+ the From: header. In this case, the variable _\b$_\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be (section 7.4.301 ,
+ page 161) 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)
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 68), _\bc_\bl_\bo_\bs_\be_\b-
- _\bh_\bo_\bo_\bk (section 4.19.2 , page 68) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69))
+ There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 69), _\bc_\bl_\bo_\bs_\be_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.2 , page 69) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 70))
which define commands to uncompress and compress a folder and to append mes-
sages to an existing compressed folder respectively.
- The Mutt Next Generation E-Mail Client 68
+ The Mutt Next Generation E-Mail Client 69
For example:
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 69), the folder will be open and closed again each time you
- will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68) (or give
+ tion 4.19.3 , page 70), 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 69) (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 69) though you'll be able to append to the folder.
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 70) though you'll be able to append to the folder.
Note that Mutt-ng will only try to use hooks if the file is not in one of the
accepted formats. In particular, if the file is empty, mutt supposes it is not
compressed. This is important because it allows the use of programs that do not
have well defined extensions. Just use '.' as a regexp. But this may be sur-
prising if your compressing script produces empty files. In this situation,
- unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 7.4.247 , page 148), so that the compressed file
+ unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 7.4.256 , page 151), 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
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 68) command after some changes were made to it.
+ 4.19.1 , page 69) command after some changes were made to it.
- The Mutt Next Generation E-Mail Client 69
+ The Mutt Next Generation E-Mail Client 70
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 68) command. Temporary folder in this case is the folder previ-
- ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 68) command.
+ 4.19.1 , page 69) 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 69) command.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should n\bno\bot\bt remove the decompressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should return
non-zero exit status if it fails, so mutt knows something's wrong.
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type, and the
file can only be open in the readonly mode.
- _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68) is not called when you exit from the
+ _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 69) is not called when you exit from the
folder if the folder was not changed.
_\b4_\b._\b1_\b9_\b._\b3 _\bA_\bp_\bp_\be_\bn_\bd _\ba _\bm_\be_\bs_\bs_\ba_\bg_\be _\bt_\bo _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx
This command is used for saving to an existing compressed folder. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
is the command that can be used for appending to the folders whose names match
- _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 68)
+ _\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 69)
command. The temporary folder in this case contains the messages that are
being appended.
append-hook \\.gz$ "gzip -c %t >> %f"
- When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69) is used, the folder is not opened,
+ When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 70) is used, the folder is not opened,
which saves time, but this means that we can not find out what the folder type
- is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.132 , page 121)) type is always
+ is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.132 , page 122)) 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 68) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 69). _\ba_\bp_\bp_\be_\bn_\bd_\b-
- _\bh_\bo_\bo_\bk (section 4.19.3 , page 69) is only for appending to existing folders.
+ page 69) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 70). _\ba_\bp_\bp_\be_\bn_\bd_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 70) 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 68) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68)respectively) each
+ 4.19.1 , page 69) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 69)respectively) each
time you will add to it.
- The Mutt Next Generation E-Mail Client 70
+ The Mutt Next Generation E-Mail Client 71
_\b4_\b._\b1_\b9_\b._\b4 _\bE_\bn_\bc_\br_\by_\bp_\bt_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs
Where the Description is the description or filename given for the attachment,
and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
- The Mutt Next Generation E-Mail Client 71
+ The Mutt Next Generation E-Mail Client 72
If Mutt-ng cannot deal with a MIME type, it will display a message like:
When you add an attachment to your mail message, Mutt-ng searches your personal
- The Mutt Next Generation E-Mail Client 72
+ The Mutt Next Generation E-Mail Client 73
mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
/usr/local/share/mutt/mime.types or /etc/mime.types
In particular, the metamail distribution will install a mailcap file, usually
as /usr/local/etc/mailcap, which contains some baseline entries.
- The Mutt Next Generation E-Mail Client 73
+ The Mutt Next Generation E-Mail Client 74
_\b5_\b._\b3_\b._\b1 _\bT_\bh_\be _\bB_\ba_\bs_\bi_\bc_\bs _\bo_\bf _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be
On the other hand, maybe you don't want to use lynx interactively, you just
want to have it convert the text/html to text/plain, then you can use:
- The Mutt Next Generation E-Mail Client 74
+ The Mutt Next Generation E-Mail Client 75
text/html; lynx -dump %s | more
The interpretation of shell meta-characters embedded in MIME parameters can
lead to security problems in general. Mutt-ng tries to quote parameters in
expansion of %s syntaxes properly, and avoids risky characters by substituting
- them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.123 , page 119) variable.
+ them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.123 , page 120) 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.
(either the internal pager or the external pager defined by the
pager variable) on the output of the view command. Without this
- The Mutt Next Generation E-Mail Client 75
+ The Mutt Next Generation E-Mail Client 76
flag, Mutt-ng assumes that the command is interactive. One could
use this to replace the pipe to more in the lynx -dump example in
needsterminal
Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
- tion 5.4 , page 78), in order to decide whether it should honor
- the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.341 , page 172) variable
+ tion 5.4 , page 79), in order to decide whether it should honor
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.350 , page 174) variable
or not. When an attachment is viewed using an interactive program,
and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt-
- ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.341 , page 172) and the exit
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.350 , page 174) 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.
text/html; lynx %s; nametemplate=%s.html
- The Mutt Next Generation E-Mail Client 76
+ The Mutt Next Generation E-Mail Client 77
test=<command>
This field specifies a command to run to test whether this mailcap
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 78) to denote
+ In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 79) to denote
two commands for viewing an attachment, one to be viewed automatically, the
other to be viewed interactively from the attachment menu. In addition, you
can then use the test feature to determine which viewer to use interactively
text/html; 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 78), Mutt-ng will choose the third entry
+ For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 79), Mutt-ng will choose the third entry
because of the copiousoutput tag. For interactive viewing, Mutt will run the
program RunningX to determine if it should use the first entry. If the program
returns non-zero, Mutt-ng will use the second entry for interactive viewing.
The various commands defined in the mailcap files are passed to the /bin/sh
- The Mutt Next Generation E-Mail Client 77
+ The Mutt Next Generation E-Mail Client 78
shell using the system() function. Before the command is passed to /bin/sh -c,
it is parsed to expand various special parameters with information from Mutt-
This mailcap file shows quite a number of examples:
- The Mutt Next Generation E-Mail Client 78
+ The Mutt Next Generation E-Mail Client 79
# Use xanim to view all videos Xanim produces a header on startup,
# send that to /dev/null so I don't see it
For instance, if you set auto_view to:
- The Mutt Next Generation E-Mail Client 79
+ The Mutt Next Generation E-Mail Client 80
auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
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 78), and use that. Failing that, Mutt-ng will look for any text
+ 5.4 , page 79), 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-
In addition, the unmime_lookup command may be used to disable this feature for
- The Mutt Next Generation E-Mail Client 80
+ The Mutt Next Generation E-Mail Client 81
any particular mime-type if it had been set, for example, in a global muttrc.
_\b6_\b._\b2 _\bT_\be_\bm_\bp_\bo_\br_\ba_\br_\by _\bF_\bi_\bl_\be_\bs
Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
- natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.333 , page 170) variable can be used to
+ natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.342 , page 173) variable can be used to
change the default permissions of these files. Please only change it if you
really know what you are doing. Also, a different location for these files may
- be desired which can be changed via the _\b$_\bt_\bm_\bp_\bd_\bi_\br (section 7.4.329 , page 169)
+ be desired which can be changed via the _\b$_\bt_\bm_\bp_\bd_\bi_\br (section 7.4.338 , page 172)
variable.
_\b6_\b._\b3 _\bI_\bn_\bf_\bo_\br_\bm_\ba_\bt_\bi_\bo_\bn _\bL_\be_\ba_\bk_\bs
step counter which is increased (and rotated) with every message sent. If you'd
like to hide this information probably telling others how many mail you sent in
which time, you at least need to remove the %P expando from the default setting
- of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.149 , page 124) variable. Please make sure
+ of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.149 , page 125) variable. Please make sure
that you really know how local parts of these Message-ID: headers are composed.
- The Mutt Next Generation E-Mail Client 81
+ The Mutt Next Generation E-Mail Client 82
_\b6_\b._\b3_\b._\b2 _\bm_\ba_\bi_\bl_\bt_\bo_\b:_\b-_\bs_\bt_\by_\bl_\be _\bl_\bi_\bn_\bk_\bs
default, mutt-ng will be strict in interpreting them which means that arbitrary
header fields can be embedded in these links which could override existing
header fields or attach arbitrary files. This may be problematic if the
- _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102) variable is _\bu_\bn_\bs_\be_\bt, i.e. the user
+ _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103) variable is _\bu_\bn_\bs_\be_\bt, i.e. the user
doesn't want to see header fields while editing the message.
For example, following a link like
will send out the user's private gnupg keyring to joe@host if the user doesn't
follow the information on screen carefully enough.
- When _\bu_\bn_\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.317 , page 167) variable, mutt-
+ When _\bu_\bn_\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.326 , page 169) variable, mutt-
ng will
+\bo be less strict when interpreting these links by prepending a X-Mailto-
string to all header fields embedded in such a link _\ba_\bn_\bd
- +\bo turn on the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102) variable by force
+ +\bo turn on the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103) variable by force
to let the user see all the headers (because they still may leak informa-
tion.)
One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
set up to _\ba_\bu_\bt_\bo_\bm_\ba_\bt_\bi_\bc_\ba_\bl_\bl_\by execute any given utility as listed in one of the mail-
- cap files (see the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh (section 7.4.122 , page 119) variable for
+ cap files (see the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh (section 7.4.122 , page 120) variable for
details.)
These utilities may have a variety of security vulnerabilities, including over-
+\bo periodically check the contents of mailcap files, especially after soft-
ware installations or upgrades
- The Mutt Next Generation E-Mail Client 82
+ The Mutt Next Generation E-Mail Client 83
+\bo keep the software packages referenced in the mailcap file up to date
- +\bo leave the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.123 , page 119) variable in its
+ +\bo leave the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.123 , page 120) variable in its
default state to restrict mailcap expandos to a safe set of characters
_\b6_\b._\b4_\b._\b2 _\bO_\bt_\bh_\be_\br
To read messages in a mailbox
- The Mutt Next Generation E-Mail Client 83
+ The Mutt Next Generation E-Mail Client 84
mutt [ -nz ] [ -F _\bm_\bu_\bt_\bt_\br_\bc ] [ -m _\bt_\by_\bp_\be ] [ -f _\bm_\ba_\bi_\bl_\bb_\bo_\bx ]
_\b7_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
- The Mutt Next Generation E-Mail Client 84
+ The Mutt Next Generation E-Mail Client 85
~A all messages
~b EXPR messages which contain EXPR in the message body
~L EXPR message is either originated or received by EXPR
~l message is addressed to a known mailing list
~m [MIN]-[MAX] message in the range MIN to MAX *)
+ ~M multipart messages
~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
~N new messages
~O old messages
alternates or any alias)
Where EXPR, USER, ID, and SUBJECT are _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs (section 4.1 , page
- 48). Special attention has to be made when using regular expressions inside of
+ 49). Special attention has to be made when using regular expressions inside of
patterns. Specifically, Mutt-ng's parser for these patterns will strip one
level of backslash (\), which is normally used for quoting. If it is your
intention to use a backslash in the regular expression, you will need to use
two backslashes instead (\\).
- The Mutt Next Generation E-Mail Client 85
+ The Mutt Next Generation E-Mail Client 86
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
The following are the commands understood by mutt.
- +\bo _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\b-_\bh_\bo_\bo_\bk (section 4.17 , page 66) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\b-_\bh_\bo_\bo_\bk (section 4.17 , page 67) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 25) _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ +\bo _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 26) _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
- +\bo _\bu_\bn_\ba_\bl_\bi_\ba_\bs (section 3.4 , page 25) [ * | _\bk_\be_\by ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bi_\ba_\bs (section 3.4 , page 26) [ * | _\bk_\be_\by ... ]
- +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 33) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 33) [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 34) [ * | _\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 79) _\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 80) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 80) _\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 69) _\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 70) _\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 78) _\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 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bb_\bi_\bn_\bd (section 3.5 , page 26) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ +\bo _\bb_\bi_\bn_\bd (section 3.5 , page 27) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
- +\bo _\bc_\bh_\ba_\br_\bs_\be_\bt_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 28) _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
+ +\bo _\bc_\bh_\ba_\br_\bs_\be_\bt_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 29) _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
- +\bo _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 68) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 69) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\bo_\bl_\bo_\br (section 3.9 , page 30) _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
+ +\bo _\bc_\bo_\bl_\bo_\br (section 3.9 , page 31) _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
- +\bo _\bu_\bn_\bc_\bo_\bl_\bo_\br (section 3.9 , page 30) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bc_\bo_\bl_\bo_\br (section 3.9 , page 31) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\be_\bx_\be_\bc (section 3.25 , page 41) _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+ +\bo _\be_\bx_\be_\bc (section 3.25 , page 42) _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
- +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 28) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 29) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 38) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ +\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 39) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
- +\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 38) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ +\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 39) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
- +\bo _\bi_\bc_\bo_\bn_\bv_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 28) _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
+ +\bo _\bi_\bc_\bo_\bn_\bv_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 29) _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
- +\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 32) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 33) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- The Mutt Next Generation E-Mail Client 86
+ The Mutt Next Generation E-Mail Client 87
- +\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 32) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 33) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bl_\bi_\bs_\bt_\bs (section 3.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bl_\bi_\bs_\bt_\bs (section 3.13 , page 36) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\bl_\bi_\bs_\bt_\bs (section 3.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\bl_\bi_\bs_\bt_\bs (section 3.13 , page 36) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bm_\ba_\bc_\br_\bo (section 3.8 , page 29) _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
+ +\bo _\bm_\ba_\bc_\br_\bo (section 3.8 , page 30) _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
- +\bo _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.15 , page 36) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
+ +\bo _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.15 , page 37) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 37) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 41) _\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 79) _\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 80) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 79) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 80) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bm_\bo_\bn_\bo (section 3.9 , page 30) _\bo_\bb_\bj_\be_\bc_\bt _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
+ +\bo _\bm_\bo_\bn_\bo (section 3.9 , page 31) _\bo_\bb_\bj_\be_\bc_\bt _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
- +\bo _\bu_\bn_\bm_\bo_\bn_\bo (section 3.9 , page 30) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bm_\bo_\bn_\bo (section 3.9 , page 31) _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 38) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 38) _\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 68) _\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 69) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.23 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
+ +\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.23 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
- +\bo _\bp_\bu_\bs_\bh (section 3.24 , page 40) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bp_\bu_\bs_\bh (section 3.24 , page 41) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\br_\be_\bs_\be_\bt (section 3.28 , page 44) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\br_\be_\bs_\be_\bt (section 3.28 , page 45) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 38) _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 39) _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bc_\bo_\br_\be (section 3.26 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
+ +\bo _\bs_\bc_\bo_\br_\be (section 3.26 , page 42) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
- +\bo _\bu_\bn_\bs_\bc_\bo_\br_\be (section 3.26 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bs_\bc_\bo_\br_\be (section 3.26 , page 42) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 39) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 40) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\br_\be_\bp_\bl_\by_\b-_\bh_\bo_\bo_\bk (section , page ) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bs_\be_\bt (section 3.28 , page 44) [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\bs_\be_\bt (section 3.28 , page 45) [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bu_\bn_\bs_\be_\bt (section 3.28 , page 44) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\bu_\bn_\bs_\be_\bt (section 3.28 , page 45) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 45) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ +\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 46) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bp_\ba_\bm (section 3.27 , page 42) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
+ +\bo _\bs_\bp_\ba_\bm (section 3.27 , page 43) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
- +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.27 , page 42) _\bp_\ba_\bt_\bt_\be_\br_\bn
+ +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.27 , page 43) _\bp_\ba_\bt_\bt_\be_\br_\bn
- The Mutt Next Generation E-Mail Client 87
+ The Mutt Next Generation E-Mail Client 88
- +\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 36) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 35) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 36) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bt_\bo_\bg_\bg_\bl_\be (section 3.28 , page 44) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ +\bo _\bt_\bo_\bg_\bg_\bl_\be (section 3.28 , page 45) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bu_\bn_\bh_\bo_\bo_\bk (section 3.30 , page 45) _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
+ +\bo _\bu_\bn_\bh_\bo_\bo_\bk (section 3.30 , page 46) _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
_\b7_\b._\b4 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
left column contains the old synonym variables, the right column the full/new
name:
- The Mutt Next Generation E-Mail Client 88
+ The Mutt Next Generation E-Mail Client 89
edit_hdrs edit_headers
forw_decode forward_decode
This variable specifies whether to abort sending if no attachment was made but
- The Mutt Next Generation E-Mail Client 89
+ The Mutt Next Generation E-Mail Client 90
the content references them, i.e. the content matches the regular expression
- given in _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 92). If a match was
+ given in _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 93). If a match was
found and this variable is set to _\by_\be_\bs, message sending will be aborted but the
mail will be send nevertheless if set to _\bn_\bo.
- This variable and _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 92) are
+ This variable and _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 93) are
intended to remind the user to attach files if the message's text references
them.
- See also the _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 92) variable.
+ See also the _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 93) variable.
_\b7_\b._\b4_\b._\b2 _\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\bs_\bu_\bb_\bj_\be_\bc_\bt
tion 2.5.4 , page 11)'' function.
N\bNo\bot\bte\be:\b: Mutt-ng will not automatically source this file; you must explicitly use
- the ``_\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 45)'' command for it to be executed.
+ the ``_\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 46)'' command for it to be executed.
_\b7_\b._\b4_\b._\b6 _\ba_\bl_\bi_\ba_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
- The Mutt Next Generation E-Mail Client 90
+ The Mutt Next Generation E-Mail Client 91
Type: string
will make response faster because there is less that has to be redrawn on the
screen when moving to the next or previous entries in the menu.
- The Mutt Next Generation E-Mail Client 91
+ The Mutt Next Generation E-Mail Client 92
_\b7_\b._\b4_\b._\b1_\b0 _\ba_\bs_\bc_\bi_\bi_\b__\bc_\bh_\ba_\br_\bs
set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
However, only the first content is valid for the message body. This variable
- is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 7.4.318 , page 167) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 7.4.327 , page 170) is unset.
_\b7_\b._\b4_\b._\b1_\b4 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
This variable describes the format of the ``attachment'' menu. The following
printf(3)-style sequences are understood:
- The Mutt Next Generation E-Mail Client 92
+ The Mutt Next Generation E-Mail Client 93
%C
charset
Default: 'attach'
- The Mutt Next Generation E-Mail Client 93
+ The Mutt Next Generation E-Mail Client 94
If this variable is non-empty, muttng will scan a message's contents before
sending for this regular expression. If it is found, it will ask for what to do
- depending on the setting of _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 88).
+ depending on the setting of _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 89).
- This variable and _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 88) are intended to
+ This variable and _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 89) are intended to
remind the user to attach files if the message's text references them.
_\b7_\b._\b4_\b._\b1_\b6 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp
If this variable is _\bu_\bn_\bs_\be_\bt, when operating (saving, printing, piping, etc) on a
list of tagged attachments, Mutt-ng will concatenate the attachments and will
operate on them as a single attachment. The ``_\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp (section 7.4.16 ,
- page 93)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
+ page 94)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
operate on the attachments one by one.
_\b7_\b._\b4_\b._\b1_\b8 _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn
This is the string that will precede a message which has been included in a
reply. For a full listing of defined printf(3)-like sequences see the section
- on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115)''.
+ on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116)''.
_\b7_\b._\b4_\b._\b1_\b9 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
Default: no
- The Mutt Next Generation E-Mail Client 94
+ The Mutt Next Generation E-Mail Client 95
- When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102)'', Mutt-ng
+ When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103)'', Mutt-ng
will skip the initial send-menu and allow you to immediately begin editing the
body of your message. The send-menu may still be accessed once you have fin-
ished editing the body of your message.
- Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.66 , page 104)''.
+ Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.66 , page 105)''.
_\b7_\b._\b4_\b._\b2_\b1 _\bb_\be_\be_\bp
When this variable is _\bs_\be_\bt, Mutt-ng will beep whenever it prints a message noti-
fying you of new mail. This is independent of the setting of the ``_\b$_\bb_\be_\be_\bp (sec-
- tion 7.4.21 , page 94)'' variable.
+ tion 7.4.21 , page 95)'' variable.
_\b7_\b._\b4_\b._\b2_\b3 _\bb_\bo_\bu_\bn_\bc_\be
current line in menus, even when the arrow_cursor variable is unset, making it
easier for blind persons using Braille displays to follow these menus. The
- The Mutt Next Generation E-Mail Client 95
+ The Mutt Next Generation E-Mail Client 96
option is disabled by default because many visual terminals don't permit making
the cursor invisible.
When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
sages.
- The Mutt Next Generation E-Mail Client 96
+ The Mutt Next Generation E-Mail Client 97
_\b7_\b._\b4_\b._\b3_\b0 _\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
Controls the format of the status line displayed in the ``compose'' menu. This
- string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.315 , page 164)'', but has
+ string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.324 , page 167)'', but has
its own set of printf(3)-like sequences:
%a
%v
Mutt-ng version string
- See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.315 , page 164)''
+ See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.324 , page 167)''
option for more information on how to set ``_\b$_\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.30 ,
- page 96)''.
+ page 97)''.
_\b7_\b._\b4_\b._\b3_\b1 _\bc_\bo_\bn_\bf_\bi_\bg_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
_\b7_\b._\b4_\b._\b3_\b4 _\bc_\bo_\bn_\bn_\be_\bc_\bt_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
- The Mutt Next Generation E-Mail Client 97
+ The Mutt Next Generation E-Mail Client 98
Type: number
Default: yes
This variable controls whether or not copies of your outgoing messages will be
- saved for later references. Also see ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.237 , page
- 146)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.248 , page 149)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.74 , page 106)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)''.
+ saved for later references. Also see ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.246 , page
+ 148)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.257 , page 151)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.74 , page 107)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 39)''.
_\b7_\b._\b4_\b._\b3_\b7 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt
going messages. This is probably only useful in connection to the _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk
command. It can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when encryption is not
required or signing is requested as well. If ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section
- 7.4.284 , page 157)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
+ 7.4.293 , page 159)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
messages and settings can be overridden by use of the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto
only)
This variable controls whether or not Mutt-ng may automatically enable PGP
encryption/signing for messages. See also ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 7.4.37 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 98)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.42 , page 98)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.284 , page 157)''.
+ 7.4.37 , page 98)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 99)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 98)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 7.4.42 , page 99)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.293 , page 159)''.
- The Mutt Next Generation E-Mail Client 98
+ The Mutt Next Generation E-Mail Client 99
_\b7_\b._\b4_\b._\b3_\b9 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
Setting this variable will cause Mutt-ng to always attempt to cryptographically
sign outgoing messages. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when
signing is not required or encryption is requested as well. If
- ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.284 , page 157)'' is _\bs_\be_\bt, then OpenSSL is
+ ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.293 , page 159)'' is _\bs_\be_\bt, then OpenSSL is
used instead to create S/MIME messages and settings can be overridden by use of
the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto only)
This variable controls whether or not Mutt-ng may automatically enable S/MIME
encryption/signing for messages. See also ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 7.4.37 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 98)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 97)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.42 , page 98)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.284 , page 157)''.
+ 7.4.37 , page 98)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 99)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 98)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 7.4.42 , page 99)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.293 , page 159)''.
_\b7_\b._\b4_\b._\b4_\b1 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt
If _\bs_\be_\bt, automatically PGP or OpenSSL sign replies to messages which are
encrypted. This makes sense in combination with ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 7.4.41 , page 98)'', because it allows you to sign all messages which are
+ 7.4.41 , page 99)'', because it allows you to sign all messages which are
- The Mutt Next Generation E-Mail Client 99
+ The Mutt Next Generation E-Mail Client 100
automatically encrypted. This works around the problem noted in
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section 7.4.42 , page 98)'', that Mutt-ng is not able to
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section 7.4.42 , page 99)'', that Mutt-ng is not able to
find out whether an encrypted message is also signed. (Crypto only)
_\b7_\b._\b4_\b._\b4_\b4 _\bc_\br_\by_\bp_\bt_\b__\bt_\bi_\bm_\be_\bs_\bt_\ba_\bm_\bp
Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
This variable controls the format of the date printed by the ``%d'' sequence in
- ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115)''. This is passed to strftime(3)
+ ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116)''. This is passed to strftime(3)
to process the date.
Unless the first character in the string is a bang (``!''), the month and week
day names are expanded according to the locale specified in the variable
- ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.120 , page 119)''. If the first character in the string
+ ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.120 , page 120)''. If the first character in the string
is a bang, the bang is discarded, and the month and week day names in the rest
of the string are expanded in the _\bC locale (that is in US English).
- The Mutt Next Generation E-Mail Client 100
+ The Mutt Next Generation E-Mail Client 101
_\b7_\b._\b4_\b._\b4_\b8 _\bd_\be_\bb_\bu_\bg_\b__\bl_\be_\bv_\be_\bl
Default: no
When sending messages with format=flowed by _\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd (section
- 7.4.324 , page 168) variable, this variable specifies whether to also set the
+ 7.4.333 , page 171) variable, this variable specifies whether to also set the
DelSp parameter to yes. If this is _\bu_\bn_\bs_\be_\bt, no additional parameter will be send
as a value of no already is the default behavior.
N\bNo\bot\bte\be:\b: this variable only has an effect on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg messages (if _\b$_\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
- (section 7.4.324 , page 168) is _\bs_\be_\bt) but not on incomming.
+ (section 7.4.333 , page 171) is _\bs_\be_\bt) but not on incomming.
- The Mutt Next Generation E-Mail Client 101
+ The Mutt Next Generation E-Mail Client 102
_\b7_\b._\b4_\b._\b5_\b2 _\bd_\be_\bl_\be_\bt_\be_\b__\bu_\bn_\bt_\ba_\bg
When _\bs_\be_\bt, specifies a command used to filter messages. When a message is
viewed it is passed as standard input to _\b$_\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br (section 7.4.54 ,
- page 101), and the filtered message is read from the standard output.
+ page 102), and the filtered message is read from the standard output.
_\b7_\b._\b4_\b._\b5_\b5 _\bd_\bo_\bt_\bl_\bo_\bc_\bk_\b__\bp_\br_\bo_\bg_\br_\ba_\bm
Type: path
- Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
+ Default: '$muttng_bindir/muttng_dotlock'
Availability: Standalone and Dotlock
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.
- The Mutt Next Generation E-Mail Client 102
+ The Mutt Next Generation E-Mail Client 103
Example: set dsn_notify='failure,delay'
the body of your message.
Which empty header fields to show is controlled by the _\b$_\be_\bd_\bi_\bt_\bo_\br_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section
- 7.4.61 , page 102) option.
+ 7.4.61 , page 103) option.
_\b7_\b._\b4_\b._\b6_\b0 _\be_\bd_\bi_\bt_\bo_\br
Type: string
- The Mutt Next Generation E-Mail Client 103
+ The Mutt Next Generation E-Mail Client 104
Default: 'From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To: X-Com-
ment-To:'
- If _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102) is _\bs_\be_\bt, this space-separated list
+ If _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103) is _\bs_\be_\bt, this space-separated list
specifies which _\bn_\bo_\bn_\b-_\be_\bm_\bp_\bt_\by header fields to edit in addition to user-defined
headers.
- Note: if _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102) had to be turned on by
- force because _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.317 , page 167) is _\bu_\bn_\bs_\be_\bt, this
+ Note: if _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103) had to be turned on by
+ force because _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.326 , page 169) is _\bu_\bn_\bs_\be_\bt, this
option has no effect.
_\b7_\b._\b4_\b._\b6_\b2 _\be_\bn_\bc_\bo_\bd_\be_\b__\bf_\br_\bo_\bm
When _\bs_\be_\bt, Mutt-ng will try to derive the message's _\be_\bn_\bv_\be_\bl_\bo_\bp_\be sender from the
``From:'' header field. Note that this information is passed to the sendmail
command using the ``-f' command line switch, so don't set this option if you
- are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.254 , page 150) yourself, or
+ are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.263 , page 152) yourself, or
if the sendmail on your machine doesn't support that command line switch.
_\b7_\b._\b4_\b._\b6_\b5 _\be_\bs_\bc_\ba_\bp_\be
Type: string
- The Mutt Next Generation E-Mail Client 104
+ The Mutt Next Generation E-Mail Client 105
Default: '~'
messages.
N\bNo\bot\bte\be:\b: this variable has no effect when the ``_\b$_\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt (section 7.4.20 , page
- 93)'' variable is _\bs_\be_\bt.
+ 94)'' variable is _\bs_\be_\bt.
_\b7_\b._\b4_\b._\b6_\b7 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
Default: ''
This variable is a colon-separated list of character encoding schemes for text
- file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.27 , page 95) value will
+ file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.27 , page 96) value will
be used instead. For example, the following configuration would work for
Japanese text handling:
Type: path
- The Mutt Next Generation E-Mail Client 105
+ The Mutt Next Generation E-Mail Client 106
Default: '~/Mail'
This variable allows you to customize the file browser display to your personal
taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page
- 115)'', but has its own set of printf(3)-like sequences:
+ 116)'', but has its own set of printf(3)-like sequences:
%C
current file number
%|X
pad to the end of the line with character 'X'
- The Mutt Next Generation E-Mail Client 106
+ The Mutt Next Generation E-Mail Client 107
_\b7_\b._\b4_\b._\b7_\b2 _\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
Controls whether or not the Mail-Followup-To: header field is generated when
sending mail. When _\bs_\be_\bt, Mutt-ng will generate this field when you are replying
to a known mailing list, specified with the ``subscribe'' or ``_\bl_\bi_\bs_\bt_\bs (section
- 3.13 , page 35)'' commands or detected by common mailing list headers.
+ 3.13 , page 36)'' commands or detected by common mailing list headers.
This field has two purposes. First, preventing you from receiving duplicate
copies of replies to messages which you send to mailing lists. Second, ensuring
is invoked. When _\bu_\bn_\bs_\be_\bt, _\bb_\bu_\bf_\bf_\by_\b__\bl_\bi_\bs_\bt will just list all mailboxes which are
already known to have new mail.
- Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.328 , page 169)'',
- ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.121 , page 119)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 7.4.105 , page 113)''.
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.337 , page 172)'',
+ ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.121 , page 120)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
+ 7.4.105 , page 114)''.
_\b7_\b._\b4_\b._\b7_\b4 _\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be
Default: no
- This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.248 , page 149)'',
+ This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.257 , page 151)'',
except that Mutt-ng will store a copy of your outgoing message by the username
of the address you are sending to even if that mailbox does not exist.
- Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.237 , page 146)'' variable.
+ Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.246 , page 148)'' variable.
_\b7_\b._\b4_\b._\b7_\b5 _\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
- The Mutt Next Generation E-Mail Client 107
+ The Mutt Next Generation E-Mail Client 108
- used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 123)'' is _\bu_\bn_\bs_\be_\bt, otherwise
- ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.144 , page 123)'' is used instead.
+ used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 124)'' is _\bu_\bn_\bs_\be_\bt, otherwise
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.144 , page 124)'' is used instead.
_\b7_\b._\b4_\b._\b7_\b6 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
Controls the handling of encrypted messages when forwarding a message. When
_\bs_\be_\bt, the outer layer of encryption is stripped off. This variable is only used
- if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 123)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
- _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.144 , page 123)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
+ if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 124)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.144 , page 124)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
_\b7_\b._\b4_\b._\b7_\b7 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
This variable controls the default subject when forwarding a message. It uses
the same format sequences as the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page
- 115)'' variable.
+ 116)'' variable.
_\b7_\b._\b4_\b._\b7_\b9 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
Default: no
When _\bs_\be_\bt forwarded messages included in the main body of the message (when
- ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 123)'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
- ``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.115 , page 115)''.
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 124)'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
+ ``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.115 , page 116)''.
_\b7_\b._\b4_\b._\b8_\b0 _\bf_\br_\bo_\bm
Default: ''
This variable contains a default from address. It can be overridden using
- my_hdr (including from send-hooks) and ``_\b$_\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 7.4.243 , page
- 147)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.337 , page
- 171)'' is unset.
+ my_hdr (including from send-hooks) and ``_\b$_\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 7.4.252 , page
+ 150)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.346 , page
+ 174)'' is unset.
- The Mutt Next Generation E-Mail Client 108
+ The Mutt Next Generation E-Mail Client 109
E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
<foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
Default: yes
When _\bu_\bn_\bs_\be_\bt, the header fields normally added by the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 ,
- page 37)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
+ page 38)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
ing a new message or replying in order to take effect. If _\bs_\be_\bt, the user
defined header fields are added to every new message.
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 7.4.342 , page
- 172)'' setting applies.
+ are replying to into the edit buffer. The ``_\b$_\bw_\be_\be_\bd (section 7.4.351 , page
+ 175)'' setting applies.
_\b7_\b._\b4_\b._\b8_\b4 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be
Availability: Header Cache
- The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.84 , page 108) variable points to the header
+ The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.84 , page 109) variable points to the header
- The Mutt Next Generation E-Mail Client 109
+ The Mutt Next Generation E-Mail Client 110
cache database.
- If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.84 , page 108) points to a directory it will
+ If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.84 , page 109) points to a directory it will
contain a header cache database per folder. If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section
- 7.4.84 , page 108) points to a file that file will be a single global header
+ 7.4.84 , page 109) points to a file that file will be a single global header
cache. By default it is _\bu_\bn_\bs_\be_\bt so no header caching will be used.
_\b7_\b._\b4_\b._\b8_\b5 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bc_\bo_\bm_\bp_\br_\be_\bs_\bs
Default: no
When _\bs_\be_\bt, Mutt-ng will skip the host name part of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section
- 7.4.95 , page 110)'' variable when adding the domain part to addresses. This
+ 7.4.95 , page 111)'' 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.
_\b7_\b._\b4_\b._\b8_\b9 _\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
- The Mutt Next Generation E-Mail Client 110
+ The Mutt Next Generation E-Mail Client 111
Type: boolean
When _\bs_\be_\bt, Mutt-ng will not show the presence of messages that are hidden by
limiting, at the top of threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\b-
- _\bi_\bn_\bg (section 7.4.89 , page 109) is set, this option will have no effect.
+ _\bi_\bn_\bg (section 7.4.89 , page 110) is set, this option will have no effect.
_\b7_\b._\b4_\b._\b9_\b2 _\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 7.4.88 ,
- page 109) is _\bs_\be_\bt, this option will have no effect.
+ page 110) is _\bs_\be_\bt, this option will have no effect.
_\b7_\b._\b4_\b._\b9_\b3 _\bh_\bi_\bs_\bt_\bo_\br_\by
This variable controls whether or not a Mail-Followup-To: header field is hon-
ored when group-replying to a message.
- The Mutt Next Generation E-Mail Client 111
+ The Mutt Next Generation E-Mail Client 112
_\b7_\b._\b4_\b._\b9_\b5 _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be
Default: no
- The Mutt Next Generation E-Mail Client 112
+ The Mutt Next Generation E-Mail Client 113
When _\bs_\be_\bt, mutt will fetch the set of subscribed folders from your server on
connection, and add them to the set of mailboxes it polls for new mail. See
- also the ``_\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.15 , page 36)'' command.
+ also the ``_\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.15 , page 37)'' command.
_\b7_\b._\b4_\b._\b9_\b9 _\bi_\bm_\ba_\bp_\b__\bd_\be_\bl_\bi_\bm_\b__\bc_\bh_\ba_\br_\bs
This contains the list of characters which you would like to treat as folder
separators for displaying IMAP paths. In particular it helps in using the '='
- shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 104) variable.
+ shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 , page 105) variable.
_\b7_\b._\b4_\b._\b1_\b0_\b0 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
wait before polling open IMAP connections, to prevent the server from closing
them before Mutt-ng has finished with them.
- The Mutt Next Generation E-Mail Client 113
+ The Mutt Next Generation E-Mail Client 114
The default is well within the RFC-specified minimum amount of time (30 min-
utes) before a server is allowed to do this, but in practice the RFC does get
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 7.4.111 , page
- 114).''
+ 115).''
_\b7_\b._\b4_\b._\b1_\b0_\b5 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
This variable configures how often (in seconds) Mutt-ng should look for new
mail in IMAP folders. This is split from the ``_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.121 ,
- page 119)'' variable to generate less traffic and get more accurate information
+ page 120)'' variable to generate less traffic and get more accurate information
for local folders.
_\b7_\b._\b4_\b._\b1_\b0_\b6 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
Specifies the password for your IMAP account. If _\bu_\bn_\bs_\be_\bt, Mutt-ng will prompt
you for your password when you invoke the fetch-mail function.
- The Mutt Next Generation E-Mail Client 114
+ The Mutt Next Generation E-Mail Client 115
W\bWa\bar\brn\bni\bin\bng\bg: you should only use this option when you are on a fairly secure
machine, because the superuser can read your configuration even if you are the
ration problems on the server which are out of the users' hands, you may wish
to suppress them at some point.
- The Mutt Next Generation E-Mail Client 115
+ The Mutt Next Generation E-Mail Client 116
_\b7_\b._\b4_\b._\b1_\b1_\b1 _\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br
Type: string
- The Mutt Next Generation E-Mail Client 116
+ The Mutt Next Generation E-Mail Client 117
Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
%g
newsgroup name (if compiled with nntp support)
- The Mutt Next Generation E-Mail Client 117
+ The Mutt Next Generation E-Mail Client 118
%i
message-id of the current message
`to:' field (recipients)
%T
- the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.330 ,
- page 170) string
+ the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.339 ,
+ page 172) string
%u
user (login) name of the author
%y
`x-label:' field, if present
- The Mutt Next Generation E-Mail Client 118
+ The Mutt Next Generation E-Mail Client 119
%Y
`x-label' field, if present, and (1) not at part of a thread tree,
%|X
pad to the end of the line with character 'X'
- See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.330 , page 170)''.
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.339 , page 172)''.
_\b7_\b._\b4_\b._\b1_\b1_\b7 _\bi_\bs_\bp_\be_\bl_\bl
Default: no
If _\bs_\be_\bt, read messages marked as flagged will not be moved from your spool mail-
- box to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.131 , page 121)'' mailbox, or as a result of
- a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36)'' command.
+ box to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.131 , page 122)'' mailbox, or as a result of
+ a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 37)'' command.
- The Mutt Next Generation E-Mail Client 119
+ The Mutt Next Generation E-Mail Client 120
_\b7_\b._\b4_\b._\b1_\b1_\b9 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
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
- 7.4.105 , page 113).
+ 7.4.105 , page 114).
_\b7_\b._\b4_\b._\b1_\b2_\b2 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
_\b7_\b._\b4_\b._\b1_\b2_\b4 _\bm_\ba_\bi_\bl_\bd_\bi_\br_\b__\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bv_\be_\br_\bi_\bf_\by
- The Mutt Next Generation E-Mail Client 120
+ The Mutt Next Generation E-Mail Client 121
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 7.4.270 , page 154)'' variable.
+ ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 7.4.279 , page 156)'' variable.
_\b7_\b._\b4_\b._\b1_\b2_\b8 _\bm_\ba_\bs_\bk
A regular expression used in the file browser, optionally preceded by the _\bn_\bo_\bt
- The Mutt Next Generation E-Mail Client 121
+ The Mutt Next Generation E-Mail Client 122
operator ``!''. Only files whose names match this mask will be shown. The
match is always case-sensitive.
When _\bs_\be_\bt, the maximum line length for displaying ``format = flowed'' messages
is limited to this length. A value of 0 (which is also the default) means that
the maximum line length is determined by the terminal width and _\b$_\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
- (section 7.4.344 , page 173).
+ (section 7.4.353 , page 175).
_\b7_\b._\b4_\b._\b1_\b3_\b1 _\bm_\bb_\bo_\bx
Default: '~/mbox'
This specifies the folder into which read mail in your ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 7.4.304 , page 162)'' folder will be appended.
+ 7.4.313 , page 165)'' folder will be appended.
_\b7_\b._\b4_\b._\b1_\b3_\b2 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
Default: 0
This variable controls the number of lines of context that are given when
- scrolling through menus. (Similar to ``_\b$_\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.174 , page
- 132)''.)
+ scrolling through menus. (Similar to ``_\b$_\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.183 , page
+ 134)''.)
- The Mutt Next Generation E-Mail Client 122
+ The Mutt Next Generation E-Mail Client 123
_\b7_\b._\b4_\b._\b1_\b3_\b4 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
This is the string displayed in the ``attachment'' menu for attachments of type
message/rfc822. For a full listing of defined printf(3)-like sequences see the
- section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115)''.
+ section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116)''.
_\b7_\b._\b4_\b._\b1_\b3_\b7 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
If _\bu_\bn_\bs_\be_\bt, Mutt-ng will remove your address (see the ``alternates'' command)
from the list of recipients when replying to a message.
- The Mutt Next Generation E-Mail Client 123
+ The Mutt Next Generation E-Mail Client 124
_\b7_\b._\b4_\b._\b1_\b3_\b9 _\bm_\bh_\b__\bp_\bu_\br_\bg_\be
the message as it was delivered to you. If you like to switch between MIME and
not MIME from mail to mail, set this variable to ask-no or ask-yes.
- Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.75 , page 106)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
- _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.144 , page 123)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.75 , page 107)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.144 , page 124)''.
_\b7_\b._\b4_\b._\b1_\b4_\b4 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
- The Mutt Next Generation E-Mail Client 124
+ The Mutt Next Generation E-Mail Client 125
Default: no
Controls the decoding of complex MIME messages into text/plain when forwarding
- a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 123)'' is _\bs_\be_\bt. Other-
- wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.75 , page 106)'' is used instead.
+ a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.143 , page 124)'' is _\bs_\be_\bt. Other-
+ wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.75 , page 107)'' is used instead.
_\b7_\b._\b4_\b._\b1_\b4_\b5 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\br_\be_\bs_\bt
Type: quadoption
- The Mutt Next Generation E-Mail Client 125
+ The Mutt Next Generation E-Mail Client 126
Default: ask-no
Controls whether or not Mutt-ng will move read messages from your spool mailbox
- to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.131 , page 121)'' mailbox, or as a result of a
- ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 36)'' command.
+ to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.131 , page 122)'' mailbox, or as a result of a
+ ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 37)'' command.
_\b7_\b._\b4_\b._\b1_\b4_\b9 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
%X
the current UNIX timestamp (hexadecimal)
- The Mutt Next Generation E-Mail Client 126
+ The Mutt Next Generation E-Mail Client 127
%Y
the current year (Y2K compliant)
N\bNo\bot\bte\be:\b: Please only change this setting if you know what you are doing. Also
make sure to consult RFC2822 to produce technically _\bv_\ba_\bl_\bi_\bd strings.
- _\b7_\b._\b4_\b._\b1_\b5_\b0 _\bn_\ba_\br_\br_\bo_\bw_\b__\bt_\br_\be_\be
+ _\b7_\b._\b4_\b._\b1_\b5_\b0 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bb_\bi_\bn_\bd_\bi_\br
- Type: boolean
+ Type: system property
- Default: no
+ Value: /opt/freebsd4/mutt-ng/bin
- This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
- threads to fit on the screen.
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\bi_\bn_\bg _\bt_\bh_\be
+ _\bm_\bu_\bt_\bt_\bn_\bg _\bb_\bi_\bn_\ba_\br_\by_\b.
- _\b7_\b._\b4_\b._\b1_\b5_\b1 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b1_\b5_\b1 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bd_\bo_\bc_\bd_\bi_\br
- Type: boolean
+ Type: system property
- Default: no
+ Value: /opt/freebsd4/mutt-ng/doc/muttng
- Availability: NNTP
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\bi_\bn_\bg _\bt_\bh_\be
+ _\bm_\bu_\bt_\bt_\bn_\bg _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt_\ba_\bt_\bi_\bo_\bn_\b.
- If _\bs_\be_\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
- ing the body of an outgoing news article.
+ _\b7_\b._\b4_\b._\b1_\b5_\b2 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bf_\bo_\bl_\bd_\be_\br_\b__\bn_\ba_\bm_\be
- _\b7_\b._\b4_\b._\b1_\b5_\b2 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
+ Type: system property
- Type: boolean
+ Value:
- Default: no
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd_\b, _\ba_\bt _\br_\bu_\bn_\bt_\bi_\bm_\be_\b, _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bl_\ba_\bs_\bt _\bp_\ba_\br_\bt _\bo_\bf
+ _\bt_\bh_\be _\bf_\bu_\bl_\bl _\bp_\ba_\bt_\bh _\bo_\br _\bU_\bR_\bI _\bo_\bf _\bt_\bh_\be _\bf_\bo_\bl_\bd_\be_\br _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by _\bo_\bp_\be_\bn _\b(_\bi_\bf _\ba_\bn_\by_\b)_\b, _\bi_\b._\be_\b. _\be_\bv_\be_\br_\by_\bt_\bh_\bi_\bn_\bg
+ _\ba_\bf_\bt_\be_\br _\bt_\bh_\be _\bl_\ba_\bs_\bt _\b`_\b`_\b/_\b'_\b'_\b.
- Availability: NNTP
+ _\b7_\b._\b4_\b._\b1_\b5_\b3 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bf_\bo_\bl_\bd_\be_\br_\b__\bp_\ba_\bt_\bh
- If _\bs_\be_\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
- ing the body of an outgoing news article.
+ Type: system property
- _\b7_\b._\b4_\b._\b1_\b5_\b3 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br
+ Value:
+
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd_\b, _\ba_\bt _\br_\bu_\bn_\bt_\bi_\bm_\be_\b, _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bf_\bu_\bl_\bl _\bp_\ba_\bt_\bh _\bo_\br
+ _\bU_\bR_\bI _\bo_\bf _\bt_\bh_\be _\bf_\bo_\bl_\bd_\be_\br _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by _\bo_\bp_\be_\bn _\b(_\bi_\bf _\ba_\bn_\by_\b)_\b.
+
+ _\b7_\b._\b4_\b._\b1_\b5_\b4 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bh_\bc_\ba_\bc_\bh_\be_\b__\bb_\ba_\bc_\bk_\be_\bn_\bd
+
+ Type: system property
+
+ Value: qdbm
+
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bh_\be_\ba_\bd_\be_\br _\bc_\bh_\ba_\bc_\bh_\bi_\bn_\bg_\b'_\bs _\bd_\ba_\bt_\ba_\b-
+ _\bb_\ba_\bs_\be _\bb_\ba_\bc_\bk_\be_\bn_\bd_\b.
+
+ The Mutt Next Generation E-Mail Client 128
+
+ _\b7_\b._\b4_\b._\b1_\b5_\b5 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bp_\bw_\bd
+
+ Type: system property
+
+ Value:
+
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd_\b, _\ba_\bt _\br_\bu_\bn_\bt_\bi_\bm_\be_\b, _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bc_\bu_\br_\br_\be_\bn_\bt
+ _\bw_\bo_\br_\bk_\bi_\bn_\bg _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by _\bo_\bf _\bt_\bh_\be _\bm_\bu_\bt_\bt_\bn_\bg _\bb_\bi_\bn_\ba_\br_\by_\b.
+
+ _\b7_\b._\b4_\b._\b1_\b5_\b6 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\br_\be_\bv_\bi_\bs_\bi_\bo_\bn
+
+ Type: system property
+
+ Value: 471
+
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bm_\bu_\bt_\bt_\bn_\bg_\b'_\bs _\bs_\bu_\bb_\bv_\be_\br_\bs_\bi_\bo_\bn _\br_\be_\bv_\bi_\bs_\bi_\bo_\bn
+ _\bs_\bt_\br_\bi_\bn_\bg_\b.
+
+ _\b7_\b._\b4_\b._\b1_\b5_\b7 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bs_\by_\bs_\bc_\bo_\bn_\bf_\bd_\bi_\br
+
+ Type: system property
+
+ Value: /opt/freebsd4/mutt-ng/etc
+
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bt_\bh_\be _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by _\bc_\bo_\bn_\bt_\ba_\bi_\bn_\bi_\bn_\bg _\bt_\bh_\be
+ _\bm_\bu_\bt_\bt_\bn_\bg _\bs_\by_\bs_\bt_\be_\bm_\b-_\bw_\bi_\bd_\be _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn_\b.
+
+ _\b7_\b._\b4_\b._\b1_\b5_\b8 _\bm_\bu_\bt_\bt_\bn_\bg_\b__\bv_\be_\br_\bs_\bi_\bo_\bn
+
+ Type: system property
+
+ Value: devel
+
+ _\bT_\bh_\bi_\bs _\bi_\bs _\ba _\br_\be_\ba_\bd_\b-_\bo_\bn_\bl_\by _\bs_\by_\bs_\bt_\be_\bm _\bp_\br_\bo_\bp_\be_\br_\bt_\by _\ba_\bn_\bd _\bs_\bp_\be_\bc_\bi_\bf_\bi_\be_\bs _\bm_\bu_\bt_\bt_\bn_\bg_\b'_\bs _\bv_\be_\br_\bs_\bi_\bo_\bn _\bs_\bt_\br_\bi_\bn_\bg_\b.
+
+ _\b7_\b._\b4_\b._\b1_\b5_\b9 _\bn_\ba_\br_\br_\bo_\bw_\b__\bt_\br_\be_\be
+
+ Type: boolean
+
+ Default: no
+
+ This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
+ threads to fit on the screen.
+
+ _\b7_\b._\b4_\b._\b1_\b6_\b0 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ If _\bs_\be_\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
+ ing the body of an outgoing news article.
+
+ The Mutt Next Generation E-Mail Client 129
+
+ _\b7_\b._\b4_\b._\b1_\b6_\b1 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ If _\bs_\be_\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
+ ing the body of an outgoing news article.
+
+ _\b7_\b._\b4_\b._\b1_\b6_\b2 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br
Type: path
As for the header caching in connection with IMAP and/or Maildir, this drasti-
cally increases speed and lowers traffic.
- The Mutt Next Generation E-Mail Client 127
-
- _\b7_\b._\b4_\b._\b1_\b5_\b4 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bt_\bc_\bh_\bu_\bp
+ _\b7_\b._\b4_\b._\b1_\b6_\b3 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bt_\bc_\bh_\bu_\bp
Type: quadoption
If this variable is _\bs_\be_\bt, Mutt-ng will mark all articles in a newsgroup as read
when you leaving it.
- _\b7_\b._\b4_\b._\b1_\b5_\b5 _\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b4 _\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
Type: number
Availability: NNTP
This variable controls how many news articles to cache per newsgroup (if
- caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 7.4.153 , page 126)) and how
+ caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 7.4.162 , page 129)) and how
many news articles to show in the ``index'' menu.
- If there're more articles than defined with _\b$_\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.155 ,
- page 127), all older ones will be removed/not shown in the index.
+ If there're more articles than defined with _\b$_\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.164 ,
+ page 129), all older ones will be removed/not shown in the index.
+
+ _\b7_\b._\b4_\b._\b1_\b6_\b5 _\bn_\bn_\bt_\bp_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo_\b__\bp_\bo_\bs_\bt_\be_\br
- _\b7_\b._\b4_\b._\b1_\b5_\b6 _\bn_\bn_\bt_\bp_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo_\b__\bp_\bo_\bs_\bt_\be_\br
+ The Mutt Next Generation E-Mail Client 130
Type: quadoption
header field, a follow-up to the newsgroup is not permitted. The message will
be mailed to the submitter of the message via mail.
- _\b7_\b._\b4_\b._\b1_\b5_\b7 _\bn_\bn_\bt_\bp_\b__\bg_\br_\bo_\bu_\bp_\b__\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b6 _\bn_\bn_\bt_\bp_\b__\bg_\br_\bo_\bu_\bp_\b__\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
This variable allows you to customize the newsgroup browser display to your
personal taste. This string is similar to ``_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 ,
- page 115)'', but has its own set of printf(3)-like sequences:
-
- The Mutt Next Generation E-Mail Client 128
+ page 116)'', but has its own set of printf(3)-like sequences:
%C current newsgroup number
%d description of newsgroup (retrieved from server)
%>X right justify the rest of the string and pad with character "X"
%|X pad to the end of the line with character "X"
- _\b7_\b._\b4_\b._\b1_\b5_\b8 _\bn_\bn_\bt_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b7 _\bn_\bn_\bt_\bp_\b__\bh_\bo_\bs_\bt
Type: string
N\bNo\bot\bte\be:\b: Using a password as shown and stored in a configuration file presents a
security risk since the superuser of your machine may read it regardless of the
+
+ The Mutt Next Generation E-Mail Client 131
+
file's permissions.
- _\b7_\b._\b4_\b._\b1_\b5_\b9 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
+ _\b7_\b._\b4_\b._\b1_\b6_\b8 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
Type: path
Example: set inews='/usr/local/bin/inews -hS'
- _\b7_\b._\b4_\b._\b1_\b6_\b0 _\bn_\bn_\bt_\bp_\b__\bl_\bo_\ba_\bd_\b__\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
+ _\b7_\b._\b4_\b._\b1_\b6_\b9 _\bn_\bn_\bt_\bp_\b__\bl_\bo_\ba_\bd_\b__\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
Type: boolean
- The Mutt Next Generation E-Mail Client 129
-
Default: yes
Availability: NNTP
This variable controls whether or not descriptions for newsgroups are to be
loaded when subscribing to a newsgroup.
- _\b7_\b._\b4_\b._\b1_\b6_\b1 _\bn_\bn_\bt_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b1_\b7_\b0 _\bn_\bn_\bt_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
each operation in index (stepping, read article, etc.).
- _\b7_\b._\b4_\b._\b1_\b6_\b2 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b7_\b1 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
Type: boolean
If _\bu_\bn_\bs_\be_\bt, an 8-bit ``Subject:'' header field in a news article will not be
encoded according to RFC2047.
+ The Mutt Next Generation E-Mail Client 132
+
N\bNo\bot\bte\be:\b: Only change this setting if you know what you are doing.
- _\b7_\b._\b4_\b._\b1_\b6_\b3 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
+ _\b7_\b._\b4_\b._\b1_\b7_\b2 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
Type: path
%s newsserver name
- _\b7_\b._\b4_\b._\b1_\b6_\b4 _\bn_\bn_\bt_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b1_\b7_\b3 _\bn_\bn_\bt_\bp_\b__\bp_\ba_\bs_\bs
Type: string
- The Mutt Next Generation E-Mail Client 130
-
Default: ''
Availability: NNTP
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.
- _\b7_\b._\b4_\b._\b1_\b6_\b5 _\bn_\bn_\bt_\bp_\b__\bp_\bo_\bs_\bt_\b__\bm_\bo_\bd_\be_\br_\ba_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b7_\b4 _\bn_\bn_\bt_\bp_\b__\bp_\bo_\bs_\bt_\b__\bm_\bo_\bd_\be_\br_\ba_\bt_\be_\bd
Type: quadoption
N\bNo\bot\bte\be:\b: if the newsserver does not support posting to that newsgroup or a group
is totally read-only, that posting will not have any effect.
- _\b7_\b._\b4_\b._\b1_\b6_\b6 _\bn_\bn_\bt_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b7_\b5 _\bn_\bn_\bt_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Type: quadoption
Availability: NNTP
+ The Mutt Next Generation E-Mail Client 133
+
Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
was connection lost.
- _\b7_\b._\b4_\b._\b1_\b6_\b7 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b7_\b6 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
Type: boolean
When _\bs_\be_\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
file and into the news cache.
- _\b7_\b._\b4_\b._\b1_\b6_\b8 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bn_\be_\bw_\b__\bn_\be_\bw_\bs
+ _\b7_\b._\b4_\b._\b1_\b7_\b7 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bn_\be_\bw_\b__\bn_\be_\bw_\bs
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 131
-
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.
- _\b7_\b._\b4_\b._\b1_\b6_\b9 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bo_\bn_\bl_\by_\b__\bu_\bn_\br_\be_\ba_\bd
+ _\b7_\b._\b4_\b._\b1_\b7_\b8 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bo_\bn_\bl_\by_\b__\bu_\bn_\br_\be_\ba_\bd
Type: boolean
If _\bs_\be_\bt, only subscribed newsgroups that contain unread articles will be dis-
played in the newsgroup browser.
- _\b7_\b._\b4_\b._\b1_\b7_\b0 _\bn_\bn_\bt_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b7_\b9 _\bn_\bn_\bt_\bp_\b__\bu_\bs_\be_\br
Type: string
Your login name on the NNTP server. If _\bu_\bn_\bs_\be_\bt and the server requires authen-
tification, Mutt-ng will prompt you for your account name.
- _\b7_\b._\b4_\b._\b1_\b7_\b1 _\bn_\bn_\bt_\bp_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b1_\b8_\b0 _\bn_\bn_\bt_\bp_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
Type: boolean
Default: no
+ The Mutt Next Generation E-Mail Client 134
+
Availability: NNTP
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.
- _\b7_\b._\b4_\b._\b1_\b7_\b2 _\bo_\bp_\be_\br_\ba_\bt_\bi_\bn_\bg_\b__\bs_\by_\bs_\bt_\be_\bm
+ _\b7_\b._\b4_\b._\b1_\b8_\b1 _\bo_\bp_\be_\br_\ba_\bt_\bi_\bn_\bg_\b__\bs_\by_\bs_\bt_\be_\bm
Type: string
It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
- _\b7_\b._\b4_\b._\b1_\b7_\b3 _\bp_\ba_\bg_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b8_\b2 _\bp_\ba_\bg_\be_\br
Type: path
Default: 'builtin'
- The Mutt Next Generation E-Mail Client 132
-
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.
screen resizes cause lines longer than the screen width to be badly formatted
in the help menu.
- _\b7_\b._\b4_\b._\b1_\b7_\b4 _\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b8_\b3 _\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
Type: number
will display the line after the last one on the screen at the top of the next
page (0 lines of context).
- _\b7_\b._\b4_\b._\b1_\b7_\b5 _\bp_\ba_\bg_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b8_\b4 _\bp_\ba_\bg_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
This variable controls the format of the one-line message ``status'' displayed
before each message in either the internal or an external pager. The valid
- sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115)''
+ sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116)''
section.
- _\b7_\b._\b4_\b._\b1_\b7_\b6 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
+ The Mutt Next Generation E-Mail Client 135
+
+ _\b7_\b._\b4_\b._\b1_\b8_\b5 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
Type: number
folder is less than _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs, then the index will only use as many
lines as it needs.
- _\b7_\b._\b4_\b._\b1_\b7_\b7 _\bp_\ba_\bg_\be_\br_\b__\bs_\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b1_\b8_\b6 _\bp_\ba_\bg_\be_\br_\b__\bs_\bt_\bo_\bp
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 133
-
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.
- _\b7_\b._\b4_\b._\b1_\b7_\b8 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b8_\b7 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
ditional-pgp function, Mutt-ng will automatically check the message for tradi-
tional pgp.
- _\b7_\b._\b4_\b._\b1_\b7_\b9 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\bi_\bn_\bl_\bi_\bn_\be
+ _\b7_\b._\b4_\b._\b1_\b8_\b8 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\bi_\bn_\bl_\bi_\bn_\be
Type: boolean
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
- ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.195 , page 137)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.204 , page 139)''.
+
+ The Mutt Next Generation E-Mail Client 136
Also note that using the old-style PGP message format is s\bst\btr\bro\bon\bng\bgl\bly\by d\bde\bep\bpr\bre\bec\bca\bat\bte\bed\bd.
(PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b0 _\bp_\bg_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\be_\bx_\bi_\bt
+ _\b7_\b._\b4_\b._\b1_\b8_\b9 _\bp_\bg_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\be_\bx_\bi_\bt
Type: boolean
If _\bs_\be_\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b1 _\bp_\bg_\bp_\b__\bc_\bl_\be_\ba_\br_\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b0 _\bp_\bg_\bp_\b__\bc_\bl_\be_\ba_\br_\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
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 134
-
- _\b7_\b._\b4_\b._\b1_\b8_\b2 _\bp_\bg_\bp_\b__\bd_\be_\bc_\bo_\bd_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b1 _\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 7.4.199 , page 138).
+ The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.208 , page 140).
%r
One or more key IDs.
subdirectory which has been installed on your system alongside the documenta-
tion. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b3 _\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 137
+
+ _\b7_\b._\b4_\b._\b1_\b9_\b2 _\bp_\bg_\bp_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to decrypt a PGP encrypted message. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b4 _\bp_\bg_\bp_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bo_\bn_\bl_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b3 _\bp_\bg_\bp_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bo_\bn_\bl_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to encrypt a body part without signing it. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b5 _\bp_\bg_\bp_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b4 _\bp_\bg_\bp_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
Default: ''
- The Mutt Next Generation E-Mail Client 135
-
This command is used to both sign and encrypt a body part. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b6 _\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b9_\b5 _\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
This variable allows you to customize the PGP key selection menu to your per-
sonal taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page
- 115)'', but has its own set of printf(3)-like sequences:
+ 116)'', but has its own set of printf(3)-like sequences:
%n
number
%c
capabilities
+ The Mutt Next Generation E-Mail Client 138
+
%t
trust/validity of the key-uid association
(PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b7 _\bp_\bg_\bp_\b__\be_\bx_\bp_\bo_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b6 _\bp_\bg_\bp_\b__\be_\bx_\bp_\bo_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to export a public key from the user's key ring. (PGP
only)
- _\b7_\b._\b4_\b._\b1_\b8_\b8 _\bp_\bg_\bp_\b__\bg_\be_\bt_\bk_\be_\by_\bs_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b7 _\bp_\bg_\bp_\b__\bg_\be_\bt_\bk_\be_\by_\bs_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
- The Mutt Next Generation E-Mail Client 136
-
Default: ''
This command is invoked whenever Mutt-ng will need public key information. %r
is the only printf(3)-like sequence used with this format. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b9 _\bp_\bg_\bp_\b__\bg_\bo_\bo_\bd_\b__\bs_\bi_\bg_\bn
+ _\b7_\b._\b4_\b._\b1_\b9_\b8 _\bp_\bg_\bp_\b__\bg_\bo_\bo_\bd_\b__\bs_\bi_\bg_\bn
Type: regular expression
Default: ''
If you assign a text to this variable, then a PGP signature is only considered
- verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.205 , page 139)
+ verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.214 , page 141)
contains the text. Use this variable if the exit code from the command is 0
even for bad signatures. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b0 _\bp_\bg_\bp_\b__\bi_\bg_\bn_\bo_\br_\be_\b__\bs_\bu_\bb_\bk_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b1_\b9_\b9 _\bp_\bg_\bp_\b__\bi_\bg_\bn_\bo_\br_\be_\b__\bs_\bu_\bb_\bk_\be_\by_\bs
Type: boolean
the principal key will inherit the subkeys' capabilities. _\bU_\bn_\bs_\be_\bt this if you
want to play interesting key selection games. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b1 _\bp_\bg_\bp_\b__\bi_\bm_\bp_\bo_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b0_\b0 _\bp_\bg_\bp_\b__\bi_\bm_\bp_\bo_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
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 139
+
ring. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b2 _\bp_\bg_\bp_\b__\bl_\bi_\bs_\bt_\b__\bp_\bu_\bb_\br_\bi_\bn_\bg_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b0_\b1 _\bp_\bg_\bp_\b__\bl_\bi_\bs_\bt_\b__\bp_\bu_\bb_\br_\bi_\bn_\bg_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This format is also generated by the pgpring utility which comes with Mutt-ng.
(PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b3 _\bp_\bg_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\be_\bc_\br_\bi_\bn_\bg_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b0_\b2 _\bp_\bg_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\be_\bc_\br_\bi_\bn_\bg_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
Default: ''
This command is used to list the secret key ring's contents. The output format
-
- The Mutt Next Generation E-Mail Client 137
-
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.
(PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b4 _\bp_\bg_\bp_\b__\bl_\bo_\bn_\bg_\b__\bi_\bd_\bs
+ _\b7_\b._\b4_\b._\b2_\b0_\b3 _\bp_\bg_\bp_\b__\bl_\bo_\bn_\bg_\b__\bi_\bd_\bs
Type: boolean
If _\bs_\be_\bt, use 64 bit PGP key IDs. _\bU_\bn_\bs_\be_\bt uses the normal 32 bit Key IDs. (PGP
only)
- _\b7_\b._\b4_\b._\b1_\b9_\b5 _\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo
+ _\b7_\b._\b4_\b._\b2_\b0_\b4 _\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo
Type: quadoption
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)
- _\b7_\b._\b4_\b._\b1_\b9_\b6 _\bp_\bg_\bp_\b__\br_\be_\bp_\bl_\by_\bi_\bn_\bl_\bi_\bn_\be
+ _\b7_\b._\b4_\b._\b2_\b0_\b5 _\bp_\bg_\bp_\b__\br_\be_\bp_\bl_\by_\bi_\bn_\bl_\bi_\bn_\be
Type: boolean
Default: no
+ The Mutt Next Generation E-Mail Client 140
+
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 7.4.195 , page 137)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.204 , page 139)''.
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)
- _\b7_\b._\b4_\b._\b1_\b9_\b7 _\bp_\bg_\bp_\b__\br_\be_\bt_\ba_\bi_\bn_\ba_\bb_\bl_\be_\b__\bs_\bi_\bg_\bs
+ _\b7_\b._\b4_\b._\b2_\b0_\b6 _\bp_\bg_\bp_\b__\br_\be_\bt_\ba_\bi_\bn_\ba_\bb_\bl_\be_\b__\bs_\bi_\bg_\bs
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 138
-
If _\bs_\be_\bt, signed and encrypted messages will consist of nested multipart/signed
and multipart/encrypted body parts.
the outer layer (multipart/encrypted) can be easily removed, while the inner
multipart/signed part is retained. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b8 _\bp_\bg_\bp_\b__\bs_\bh_\bo_\bw_\b__\bu_\bn_\bu_\bs_\ba_\bb_\bl_\be
+ _\b7_\b._\b4_\b._\b2_\b0_\b7 _\bp_\bg_\bp_\b__\bs_\bh_\bo_\bw_\b__\bu_\bn_\bu_\bs_\ba_\bb_\bl_\be
Type: boolean
This includes keys which have been revoked, have expired, or have been marked
as ``disabled'' by the user. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b9 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs
+ _\b7_\b._\b4_\b._\b2_\b0_\b8 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs
Type: string
your private keys to use. It is recommended that you use the keyid form to
specify your key (e.g., ``0x00112233''). (PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b0 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b0_\b9 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
Default: ''
+ The Mutt Next Generation E-Mail Client 141
+
This command is used to create the detached PGP signature for a multi-
part/signed PGP/MIME body part. (PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b1 _\bp_\bg_\bp_\b__\bs_\bo_\br_\bt_\b__\bk_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b2_\b1_\b0 _\bp_\bg_\bp_\b__\bs_\bo_\br_\bt_\b__\bk_\be_\by_\bs
Type: sort order
date
sort by key creation date
- The Mutt Next Generation E-Mail Client 139
-
trust
sort by the trust of the key
If you prefer reverse order of the above values, prefix it with ``reverse-''.
(PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b2 _\bp_\bg_\bp_\b__\bs_\bt_\br_\bi_\bc_\bt_\b__\be_\bn_\bc
+ _\b7_\b._\b4_\b._\b2_\b1_\b1 _\bp_\bg_\bp_\b__\bs_\bt_\br_\bi_\bc_\bt_\b__\be_\bn_\bc
Type: boolean
non-verifyable PGP signatures, so only change this if you know what you are
doing. (PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b3 _\bp_\bg_\bp_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b2_\b1_\b2 _\bp_\bg_\bp_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
The number of seconds after which a cached passphrase will expire if not used.
Default: 300. (PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b4 _\bp_\bg_\bp_\b__\bu_\bs_\be_\b__\bg_\bp_\bg_\b__\ba_\bg_\be_\bn_\bt
+ _\b7_\b._\b4_\b._\b2_\b1_\b3 _\bp_\bg_\bp_\b__\bu_\bs_\be_\b__\bg_\bp_\bg_\b__\ba_\bg_\be_\bn_\bt
Type: boolean
If _\bs_\be_\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b5 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ The Mutt Next Generation E-Mail Client 142
+
+ _\b7_\b._\b4_\b._\b2_\b1_\b4 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to verify PGP signatures. (PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b6 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bk_\be_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b1_\b5 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bk_\be_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to verify key information from the key selection menu.
(PGP only)
- _\b7_\b._\b4_\b._\b2_\b0_\b7 _\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b2_\b1_\b6 _\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
- The Mutt Next Generation E-Mail Client 140
-
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
pipe the messages without any preprocessing. When _\bs_\be_\bt, Mutt-ng will weed head-
ers and will attempt to PGP/MIME decode the messages first.
- _\b7_\b._\b4_\b._\b2_\b0_\b8 _\bp_\bi_\bp_\be_\b__\bs_\be_\bp
+ _\b7_\b._\b4_\b._\b2_\b1_\b7 _\bp_\bi_\bp_\be_\b__\bs_\be_\bp
Type: string
The separator to add between messages when piping a list of tagged messages to
an external Unix command.
- _\b7_\b._\b4_\b._\b2_\b0_\b9 _\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b1_\b8 _\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
Type: boolean
of tagged messages Mutt-ng will concatenate the messages and will pipe them as
a single folder. When _\bs_\be_\bt, Mutt-ng will pipe the messages one by one. In both
cases the messages are piped in the current sorted order, and the ``_\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp
- (section 7.4.208 , page 139)'' separator is added after each message.
+ (section 7.4.217 , page 142)'' separator is added after each message.
- _\b7_\b._\b4_\b._\b2_\b1_\b0 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\b__\bt_\br_\by_\b__\ba_\bl_\bl
+ _\b7_\b._\b4_\b._\b2_\b1_\b9 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\b__\bt_\br_\by_\b__\ba_\bl_\bl
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 143
+
Availability: POP
If _\bs_\be_\bt, Mutt-ng will try all available methods. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will only
able. If a method is available but authentication fails, Mutt-ng will not con-
nect to the POP server.
- _\b7_\b._\b4_\b._\b2_\b1_\b1 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
+ _\b7_\b._\b4_\b._\b2_\b2_\b0 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
Type: string
tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
``digest-md5'', ``gssapi'' or ``cram-md5''.
- The Mutt Next Generation E-Mail Client 141
-
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.
Example: set pop_authenticators='digest-md5:apop:user'
- _\b7_\b._\b4_\b._\b2_\b1_\b2 _\bp_\bo_\bp_\b__\bd_\be_\bl_\be_\bt_\be
+ _\b7_\b._\b4_\b._\b2_\b2_\b1 _\bp_\bo_\bp_\b__\bd_\be_\bl_\be_\bt_\be
Type: quadoption
server when using the ``fetch-mail'' function. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will down-
load messages but also leave them on the POP server.
- _\b7_\b._\b4_\b._\b2_\b1_\b3 _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b2_\b2_\b2 _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt
Type: string
N\bNo\bot\bte\be:\b: Storing passwords in a configuration file presents a security risk since
the superuser of your machine may read it regardless of the file's permissions.
- _\b7_\b._\b4_\b._\b2_\b1_\b4 _\bp_\bo_\bp_\b__\bl_\ba_\bs_\bt
+ The Mutt Next Generation E-Mail Client 144
+
+ _\b7_\b._\b4_\b._\b2_\b2_\b3 _\bp_\bo_\bp_\b__\bl_\ba_\bs_\bt
Type: boolean
retrieving only unread messages from the POP server when using the ``fetch-
mail'' function.
- _\b7_\b._\b4_\b._\b2_\b1_\b5 _\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b2_\b2_\b4 _\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
Availability: POP
- The Mutt Next Generation E-Mail Client 142
-
This variable configures how often (in seconds) POP should look for new mail.
- _\b7_\b._\b4_\b._\b2_\b1_\b6 _\bp_\bo_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b2_\b2_\b5 _\bp_\bo_\bp_\b__\bp_\ba_\bs_\bs
Type: string
N\bNo\bot\bte\be:\b: Storing passwords in a configuration file presents a security risk since
the superuser of your machine may read it regardless of the file's permissions.
- _\b7_\b._\b4_\b._\b2_\b1_\b7 _\bp_\bo_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b2_\b2_\b6 _\bp_\bo_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Type: quadoption
Controls whether or not Mutt-ng will try to reconnect to a POP server when the
connection is lost.
- _\b7_\b._\b4_\b._\b2_\b1_\b8 _\bp_\bo_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b2_\b2_\b7 _\bp_\bo_\bp_\b__\bu_\bs_\be_\br
Type: string
Availability: POP
+ The Mutt Next Generation E-Mail Client 145
+
Your login name on the POP server.
This variable defaults to your user name on the local machine.
- _\b7_\b._\b4_\b._\b2_\b1_\b9 _\bp_\bo_\bs_\bt_\b__\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b2_\b2_\b8 _\bp_\bo_\bs_\bt_\b__\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
Type: string
Default: ''
- Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 93)'' variable, Mutt-ng
+ Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 94)'' variable, Mutt-ng
will append this string after the inclusion of a message which is being replied
to.
- _\b7_\b._\b4_\b._\b2_\b2_\b0 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be
+ _\b7_\b._\b4_\b._\b2_\b2_\b9 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be
Type: quadoption
Default: ask-yes
- The Mutt Next Generation E-Mail Client 143
-
Controls whether or not messages are saved in the ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section
- 7.4.221 , page 142)'' mailbox when you elect not to send immediately.
+ 7.4.230 , page 145)'' mailbox when you elect not to send immediately.
- _\b7_\b._\b4_\b._\b2_\b2_\b1 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd
+ _\b7_\b._\b4_\b._\b2_\b3_\b0 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd
Type: path
Default: '~/postponed'
- Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.220 , page 142)
+ Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.229 , page 145)
sending a message'' which you are editing. When you choose to postpone a mes-
sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
- ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.220 , page 142)'' variable.
+ ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.229 , page 145)'' variable.
- _\b7_\b._\b4_\b._\b2_\b2_\b2 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b2_\b3_\b1 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Type: string
N\bNo\bot\bte\be:\b: For this example to work, you must be able to log in to the remote
machine without having to enter a password.
- _\b7_\b._\b4_\b._\b2_\b2_\b3 _\bp_\br_\bi_\bn_\bt
+ The Mutt Next Generation E-Mail Client 146
+
+ _\b7_\b._\b4_\b._\b2_\b3_\b2 _\bp_\br_\bi_\bn_\bt
Type: quadoption
Controls whether or not Mutt-ng really prints messages. This is set to _\ba_\bs_\bk_\b-_\bn_\bo
by default, because some people accidentally hit ``p'' often.
- _\b7_\b._\b4_\b._\b2_\b2_\b4 _\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b3_\b3 _\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: path
This specifies the command pipe that should be used to print messages.
- _\b7_\b._\b4_\b._\b2_\b2_\b5 _\bp_\br_\bi_\bn_\bt_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b2_\b3_\b4 _\bp_\br_\bi_\bn_\bt_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
- The Mutt Next Generation E-Mail Client 144
-
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 7.4.224 , page 143). If this option is _\bu_\bn_\bs_\be_\bt, no pro-
+ _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.233 , page 146). 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.
- _\b7_\b._\b4_\b._\b2_\b2_\b6 _\bp_\br_\bi_\bn_\bt_\b__\bs_\bp_\bl_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b3_\b5 _\bp_\br_\bi_\bn_\bt_\b__\bs_\bp_\bl_\bi_\bt
Type: boolean
Default: no
Used in connection with the print-message command. If this option is _\bs_\be_\bt, the
- command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.224 , page 143) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.233 , page 146) is executed
once for each message which is to be printed. If this option is _\bu_\bn_\bs_\be_\bt, the
- command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.224 , page 143) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.233 , page 146) is executed
only once, and all the messages are concatenated, with a form feed as the mes-
sage separator.
Those who use the enscript(1) program's mail-printing mode will most likely
want to set this option.
- _\b7_\b._\b4_\b._\b2_\b2_\b7 _\bp_\br_\bo_\bm_\bp_\bt_\b__\ba_\bf_\bt_\be_\br
+ _\b7_\b._\b4_\b._\b2_\b3_\b6 _\bp_\br_\bo_\bm_\bp_\bt_\b__\ba_\bf_\bt_\be_\br
Type: boolean
Default: yes
- If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 7.4.173 , page 131)'', setting this
+ If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 7.4.182 , page 134)'', setting this
variable will cause Mutt-ng to prompt you for a command when the pager exits
+
+ The Mutt Next Generation E-Mail Client 147
+
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.
- _\b7_\b._\b4_\b._\b2_\b2_\b8 _\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b3_\b7 _\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: path
This specifies the command that Mutt-ng will use to make external address
queries. The string should contain a %s, which will be substituted with the
- query string the user types. See ``_\bq_\bu_\be_\br_\by (section 4.7 , page 58)'' for more
+ query string the user types. See ``_\bq_\bu_\be_\br_\by (section 4.7 , page 59)'' for more
information.
- _\b7_\b._\b4_\b._\b2_\b2_\b9 _\bq_\bu_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b3_\b8 _\bq_\bu_\bi_\bt
Type: quadoption
Default: yes
This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
-
- The Mutt Next Generation E-Mail Client 145
-
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.
- _\b7_\b._\b4_\b._\b2_\b3_\b0 _\bq_\bu_\bo_\bt_\be_\b__\be_\bm_\bp_\bt_\by
+ _\b7_\b._\b4_\b._\b2_\b3_\b9 _\bq_\bu_\bo_\bt_\be_\b__\be_\bm_\bp_\bt_\by
Type: boolean
Default: yes
Controls whether or not empty lines will be quoted using ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (sec-
- tion 7.4.115 , page 115)''.
+ tion 7.4.115 , page 116)''.
- _\b7_\b._\b4_\b._\b2_\b3_\b1 _\bq_\bu_\bo_\bt_\be_\b__\bq_\bu_\bo_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b2_\b4_\b0 _\bq_\bu_\bo_\bt_\be_\b__\bq_\bu_\bo_\bt_\be_\bd
Type: boolean
Controls how quoted lines will be quoted. If _\bs_\be_\bt, one quote character will be
added to the end of existing prefix. Otherwise, quoted lines will be prepended
- by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.115 , page 115)''.
+ by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.115 , page 116)''.
- _\b7_\b._\b4_\b._\b2_\b3_\b2 _\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp
+ _\b7_\b._\b4_\b._\b2_\b4_\b1 _\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp
Type: regular expression
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 148
+
set this to a regular expression that matches _\be_\bx_\ba_\bc_\bt_\bl_\by the quote characters at
the beginning of quoted lines.
- _\b7_\b._\b4_\b._\b2_\b3_\b3 _\br_\be_\ba_\bd_\b__\bi_\bn_\bc
+ _\b7_\b._\b4_\b._\b2_\b4_\b2 _\br_\be_\ba_\bd_\b__\bi_\bn_\bc
Type: number
time. When set to 0, only a single message will appear before the reading the
mailbox.
- Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 7.4.346 , page 173)'' variable.
-
- _\b7_\b._\b4_\b._\b2_\b3_\b4 _\br_\be_\ba_\bd_\b__\bo_\bn_\bl_\by
+ Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 7.4.355 , page 175)'' variable.
- The Mutt Next Generation E-Mail Client 146
+ _\b7_\b._\b4_\b._\b2_\b4_\b3 _\br_\be_\ba_\bd_\b__\bo_\bn_\bl_\by
Type: boolean
If set, all folders are opened in read-only mode.
- _\b7_\b._\b4_\b._\b2_\b3_\b5 _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b4_\b4 _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
Type: string
By default, this is the GECOS field from /etc/passwd.
_\bN_\bo_\bt_\be_\b: This variable will _\bn_\bo_\bt be used when the user has set a real name in the
- _\b$_\bf_\br_\bo_\bm (section 7.4.80 , page 107) variable.
+ _\b$_\bf_\br_\bo_\bm (section 7.4.80 , page 108) variable.
- _\b7_\b._\b4_\b._\b2_\b3_\b6 _\br_\be_\bc_\ba_\bl_\bl
+ _\b7_\b._\b4_\b._\b2_\b4_\b5 _\br_\be_\bc_\ba_\bl_\bl
Type: quadoption
Default: ask-yes
Controls whether or not Mutt-ng recalls postponed messages when composing a new
- message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.221 , page 142)''.
+ message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.230 , page 145)''.
Setting this variable to _\by_\be_\bs is not generally useful, and thus not recommended.
- _\b7_\b._\b4_\b._\b2_\b3_\b7 _\br_\be_\bc_\bo_\br_\bd
+ _\b7_\b._\b4_\b._\b2_\b4_\b6 _\br_\be_\bc_\bo_\br_\bd
+
+ The Mutt Next Generation E-Mail Client 149
Type: path
This specifies the file into which your outgoing messages should be appended.
(This is meant as the primary method for saving a copy of your messages, but
- another way to do this is using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37)'' com-
+ another way to do this is using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 38)'' com-
mand to create a Bcc: header field with your email address in it.)
- The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\b7_\b._\b4_\b._\b2_\b3_\b7 _\b, _\bp_\ba_\bg_\be _\b1_\b4_\b6_\b) is overridden by the
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.74 , page 106)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.248 , page 149)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page
- 38)'' command.
+ The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\b7_\b._\b4_\b._\b2_\b4_\b6 _\b, _\bp_\ba_\bg_\be _\b1_\b4_\b8_\b) is overridden by the
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.74 , page 107)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.257 , page 151)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page
+ 39)'' command.
- _\b7_\b._\b4_\b._\b2_\b3_\b8 _\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp
+ _\b7_\b._\b4_\b._\b2_\b4_\b7 _\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp
Type: regular expression
Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
- A regular expression used to recognize reply messages when threading and
-
- The Mutt Next Generation E-Mail Client 147
-
- replying. The default value corresponds to the English ``Re:'' and the German
+ A regular expression used to recognize reply messages when threading and reply-
+ ing. The default value corresponds to the English ``Re:'' and the German
``Aw:''.
- _\b7_\b._\b4_\b._\b2_\b3_\b9 _\br_\be_\bp_\bl_\by_\b__\bs_\be_\bl_\bf
+ _\b7_\b._\b4_\b._\b2_\b4_\b8 _\br_\be_\bp_\bl_\by_\b__\bs_\be_\bl_\bf
Type: boolean
that you want to reply to the recipients of that message rather than to your-
self.
- _\b7_\b._\b4_\b._\b2_\b4_\b0 _\br_\be_\bp_\bl_\by_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b2_\b4_\b9 _\br_\be_\bp_\bl_\by_\b__\bt_\bo
Type: quadoption
header field to the list address and you want to send a private message to the
author of a message.
- _\b7_\b._\b4_\b._\b2_\b4_\b1 _\br_\be_\bs_\bo_\bl_\bv_\be
+ _\b7_\b._\b4_\b._\b2_\b5_\b0 _\br_\be_\bs_\bo_\bl_\bv_\be
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 150
+
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.
- _\b7_\b._\b4_\b._\b2_\b4_\b2 _\br_\be_\bv_\be_\br_\bs_\be_\b__\ba_\bl_\bi_\ba_\bs
+ _\b7_\b._\b4_\b._\b2_\b5_\b1 _\br_\be_\bv_\be_\br_\bs_\be_\b__\ba_\bl_\bi_\ba_\bs
Type: boolean
From: abd30425@somewhere.net
It would be displayed in the index menu as ``Joe User'' instead of
-
- The Mutt Next Generation E-Mail Client 148
-
``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
not human friendly (like CompuServe addresses).
- _\b7_\b._\b4_\b._\b2_\b4_\b3 _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b5_\b2 _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be
Type: boolean
would be used doesn't match your alternates, the From: line will use your
address on the current machine.
- _\b7_\b._\b4_\b._\b2_\b4_\b4 _\br_\be_\bv_\be_\br_\bs_\be_\b__\br_\be_\ba_\bl_\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b5_\b3 _\br_\be_\bv_\be_\br_\bs_\be_\b__\br_\be_\ba_\bl_\bn_\ba_\bm_\be
Type: boolean
Default: yes
- This variable fine-tunes the behaviour of the _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 7.4.243 ,
- page 147) feature. When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming
+ This variable fine-tunes the behaviour of the _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be (section 7.4.252 ,
+ page 150) feature. When it is _\bs_\be_\bt, Mutt-ng will use the address from incoming
messages as-is, possibly including eventual real names. When it is _\bu_\bn_\bs_\be_\bt,
Mutt-ng will override any such real names with the setting of the _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
- (section 7.4.235 , page 145) variable.
+ (section 7.4.244 , page 148) variable.
- _\b7_\b._\b4_\b._\b2_\b4_\b5 _\br_\bf_\bc_\b2_\b0_\b4_\b7_\b__\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b2_\b5_\b4 _\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 151
+
Default: no
When this variable is _\bs_\be_\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
_\bg_\be_\bn_\be_\br_\ba_\bt_\be_\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
encoding specified in RFC 2231.
- _\b7_\b._\b4_\b._\b2_\b4_\b6 _\bs_\ba_\bv_\be_\b__\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b7_\b._\b4_\b._\b2_\b5_\b5 _\bs_\ba_\bv_\be_\b__\ba_\bd_\bd_\br_\be_\bs_\bs
Type: boolean
- The Mutt Next Generation E-Mail Client 149
-
Default: no
If _\bs_\be_\bt, Mutt-ng will take the sender's full address when choosing a default
- folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.248 , page 149)'' or
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.74 , page 106)'' is _\bs_\be_\bt too, the selection of the
+ folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.257 , page 151)'' or
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.74 , page 107)'' is _\bs_\be_\bt too, the selection of the
fcc folder will be changed as well.
- _\b7_\b._\b4_\b._\b2_\b4_\b7 _\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by
+ _\b7_\b._\b4_\b._\b2_\b5_\b6 _\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by
Type: boolean
Default: yes
When _\bu_\bn_\bs_\be_\bt, mailboxes which contain no saved messages will be removed when
- closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.304 , page 162)'' which is
+ closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.313 , page 165)'' 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
and Maildir directories.
- _\b7_\b._\b4_\b._\b2_\b4_\b8 _\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b5_\b7 _\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be
Type: boolean
This variable controls how copies of outgoing messages are saved. When set, a
check is made to see if a mailbox specified by the recipient address exists
(this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.70 ,
- page 104)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
+ page 105)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
mailbox exists, the outgoing message will be saved to that mailbox, otherwise
- the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.237 , page 146)'' mailbox.
+ the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.246 , page 148)'' mailbox.
+
+ The Mutt Next Generation E-Mail Client 152
- Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.74 , page 106)'' variable.
+ Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.74 , page 107)'' variable.
- _\b7_\b._\b4_\b._\b2_\b4_\b9 _\bs_\bc_\bo_\br_\be
+ _\b7_\b._\b4_\b._\b2_\b5_\b8 _\bs_\bc_\bo_\br_\be
Type: boolean
When this variable is _\bu_\bn_\bs_\be_\bt, scoring is turned off. This can be useful to
selectively disable scoring for certain folders when the ``_\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\b-
- _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.250 , page 149)'' variable and friends are used.
+ _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.259 , page 152)'' variable and friends are used.
- _\b7_\b._\b4_\b._\b2_\b5_\b0 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
+ _\b7_\b._\b4_\b._\b2_\b5_\b9 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
Type: number
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 150
-
variable will never mark a message for deletion.
- _\b7_\b._\b4_\b._\b2_\b5_\b1 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bf_\bl_\ba_\bg
+ _\b7_\b._\b4_\b._\b2_\b6_\b0 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bf_\bl_\ba_\bg
Type: number
Messages which have been assigned a score greater than or equal to this vari-
able's value are automatically marked ``flagged''.
- _\b7_\b._\b4_\b._\b2_\b5_\b2 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd
+ _\b7_\b._\b4_\b._\b2_\b6_\b1 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd
Type: number
scores are always greater than or equal to zero, the default setting of this
variable will never mark a message read.
- _\b7_\b._\b4_\b._\b2_\b5_\b3 _\bs_\be_\bn_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b2_\b6_\b2 _\bs_\be_\bn_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
A list of character sets for outgoing messages. Mutt-ng will use the first
character set into which the text can be converted exactly. If your ``_\b$_\bc_\bh_\ba_\br_\bs_\be_\bt
- (section 7.4.27 , page 95)'' is not iso-8859-1 and recipients may not under-
+ (section 7.4.27 , page 96)'' 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 153
+
instead of or after iso-8859-1.
- _\b7_\b._\b4_\b._\b2_\b5_\b4 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl
+ _\b7_\b._\b4_\b._\b2_\b6_\b3 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl
Type: path
Mutt-ng expects that the specified program interprets additional arguments as
recipient addresses.
- _\b7_\b._\b4_\b._\b2_\b5_\b5 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl_\b__\bw_\ba_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b6_\b4 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl_\b__\bw_\ba_\bi_\bt
Type: number
Default: 0
- Specifies the number of seconds to wait for the ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.254 ,
- page 150)'' process to finish before giving up and putting delivery in the
+ Specifies the number of seconds to wait for the ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.263 ,
+ page 152)'' process to finish before giving up and putting delivery in the
background.
- The Mutt Next Generation E-Mail Client 151
-
Mutt-ng interprets the value of this variable as follows:
>0
will be put in a temporary file. If there is some error, you will be informed
as to where to find the output.
- _\b7_\b._\b4_\b._\b2_\b5_\b6 _\bs_\bh_\be_\bl_\bl
+ _\b7_\b._\b4_\b._\b2_\b6_\b5 _\bs_\bh_\be_\bl_\bl
Type: path
Command to use when spawning a subshell. By default, the user's login shell
from /etc/passwd is used.
- _\b7_\b._\b4_\b._\b2_\b5_\b7 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by
+ _\b7_\b._\b4_\b._\b2_\b6_\b6 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by
Type: string
Default: '.'
When the sidebar is displayed and _\b$_\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by (section
- 7.4.261 , page 152) is _\bs_\be_\bt, this variable specifies the characters at which to
+ 7.4.270 , page 154) is _\bs_\be_\bt, this variable specifies the characters at which to
+
+ The Mutt Next Generation E-Mail Client 154
+
split a folder name into ``hierarchy items.''
- _\b7_\b._\b4_\b._\b2_\b5_\b8 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bd_\be_\bl_\bi_\bm
+ _\b7_\b._\b4_\b._\b2_\b6_\b7 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bd_\be_\bl_\bi_\bm
Type: string
This specifies the delimiter between the sidebar (if visible) and other
screens.
- _\b7_\b._\b4_\b._\b2_\b5_\b9 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bn_\be_\bw_\bm_\ba_\bi_\bl_\b__\bo_\bn_\bl_\by
+ _\b7_\b._\b4_\b._\b2_\b6_\b8 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bn_\be_\bw_\bm_\ba_\bi_\bl_\b__\bo_\bn_\bl_\by
Type: boolean
If _\bs_\be_\bt, only folders with new mail will be shown in the sidebar.
- _\b7_\b._\b4_\b._\b2_\b6_\b0 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bn_\bu_\bm_\bb_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b2_\b6_\b9 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bn_\bu_\bm_\bb_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
- The Mutt Next Generation E-Mail Client 152
-
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.
- _\b7_\b._\b4_\b._\b2_\b6_\b1 _\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
+ The Mutt Next Generation E-Mail Client 155
+
+ _\b7_\b._\b4_\b._\b2_\b7_\b0 _\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
- 7.4.263 , page 152)'' is set to a too low value). For example, if the news-
+ 7.4.272 , page 155)'' is set to a too low value). For example, if the news-
group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
get shortened.
At which characters this compression is done is controled via the _\b$_\bs_\bi_\bd_\be_\b-
- _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 7.4.257 , page 151) variable.
+ _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 7.4.266 , page 153) variable.
- _\b7_\b._\b4_\b._\b2_\b6_\b2 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
+ _\b7_\b._\b4_\b._\b2_\b7_\b1 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
Type: boolean
Default: no
This specifies whether or not to show the sidebar (a list of folders specified
-
- The Mutt Next Generation E-Mail Client 153
-
with the ``mailboxes'' command).
- _\b7_\b._\b4_\b._\b2_\b6_\b3 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bw_\bi_\bd_\bt_\bh
+ _\b7_\b._\b4_\b._\b2_\b7_\b2 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bw_\bi_\bd_\bt_\bh
Type: number
The width of the sidebar.
- _\b7_\b._\b4_\b._\b2_\b6_\b4 _\bs_\bi_\bg_\b__\bd_\ba_\bs_\bh_\be_\bs
+ _\b7_\b._\b4_\b._\b2_\b7_\b3 _\bs_\bi_\bg_\b__\bd_\ba_\bs_\bh_\be_\bs
Type: boolean
Default: yes
If set, a line containing ``-- '' (dash, dash, space) will be inserted before
- your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.266 , page 153)''. It is s\bst\btr\bro\bon\bng\bgl\bly\by recommended
+ your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.275 , page 155)''. 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.
For example, Mutt-ng has the ability to highlight the signature in a different
color in the builtin pager.
- _\b7_\b._\b4_\b._\b2_\b6_\b5 _\bs_\bi_\bg_\b__\bo_\bn_\b__\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b2_\b7_\b4 _\bs_\bi_\bg_\b__\bo_\bn_\b__\bt_\bo_\bp
Type: boolean
Default: no
+ The Mutt Next Generation E-Mail Client 156
+
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
guardians.
- _\b7_\b._\b4_\b._\b2_\b6_\b6 _\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be
+ _\b7_\b._\b4_\b._\b2_\b7_\b5 _\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be
Type: path
messages. If the filename ends with a pipe (``|''), it is assumed that file-
name is a shell command and input should be read from its stdout.
- _\b7_\b._\b4_\b._\b2_\b6_\b7 _\bs_\bi_\bg_\bn_\bo_\bf_\bf_\b__\bs_\bt_\br_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b2_\b7_\b6 _\bs_\bi_\bg_\bn_\bo_\bf_\bf_\b__\bs_\bt_\br_\bi_\bn_\bg
Type: string
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 154
-
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.
- _\b7_\b._\b4_\b._\b2_\b6_\b8 _\bs_\bi_\bm_\bp_\bl_\be_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b7_\b._\b4_\b._\b2_\b7_\b7 _\bs_\bi_\bm_\bp_\bl_\be_\b__\bs_\be_\ba_\br_\bc_\bh
Type: 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 7.2 , page 83)'' for more information on search patterns.
+ ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 84)'' 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
~f joe | ~s joe
- _\b7_\b._\b4_\b._\b2_\b6_\b9 _\bs_\bl_\be_\be_\bp_\b__\bt_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b7_\b8 _\bs_\bl_\be_\be_\bp_\b__\bt_\bi_\bm_\be
Type: number
the current folder. The default is to pause one second, so a value of zero for
this option suppresses the pause.
- _\b7_\b._\b4_\b._\b2_\b7_\b0 _\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp
+ The Mutt Next Generation E-Mail Client 157
+
+ _\b7_\b._\b4_\b._\b2_\b7_\b9 _\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 7.4.127 ,
- page 120)'' variable.
+ page 121)'' variable.
- _\b7_\b._\b4_\b._\b2_\b7_\b1 _\bs_\bm_\bi_\bl_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b2_\b8_\b0 _\bs_\bm_\bi_\bl_\be_\by_\bs
Type: regular expression
Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
The _\bp_\ba_\bg_\be_\br uses this variable to catch some common false positives of
- ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.232 , page 145)'', most notably smileys in the
+ ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.241 , page 147)'', most notably smileys in the
beginning of a line
- _\b7_\b._\b4_\b._\b2_\b7_\b2 _\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 155
+ _\b7_\b._\b4_\b._\b2_\b8_\b1 _\bs_\bm_\bi_\bm_\be_\b__\ba_\bs_\bk_\b__\bc_\be_\br_\bt_\b__\bl_\ba_\bb_\be_\bl
Type: boolean
cate about to be added to the database or not. It is _\bs_\be_\bt by default. (S/MIME
only)
- _\b7_\b._\b4_\b._\b2_\b7_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn
+ _\b7_\b._\b4_\b._\b2_\b8_\b2 _\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn
Type: path
This variable contains the name of either a directory, or a file which contains
trusted certificates for use with OpenSSL. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs
+ _\b7_\b._\b4_\b._\b2_\b8_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs
Type: path
address keyid pairs, and which can be manually edited. This one points to the
location of the certificates. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b5 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ The Mutt Next Generation E-Mail Client 158
+
+ _\b7_\b._\b4_\b._\b2_\b8_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
multipart/signed attachment when verifying it.
%k
- The key-pair specified with _\b$_\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by (section 7.4.277 ,
- page 156)
-
- The Mutt Next Generation E-Mail Client 156
+ The key-pair specified with _\b$_\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by (section 7.4.286 ,
+ page 158)
%c
One or more certificate IDs.
%C
CA location: Depending on whether _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section
- 7.4.273 , page 155) points to a directory or file, this expands to
- '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.273 , page 155)' or
- '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.273 , page 155)'.
+ 7.4.282 , page 157) points to a directory or file, this expands to
+ '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.282 , page 157)' or
+ '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.282 , page 157)'.
For examples on how to configure these formats, see the smime.rc in the sam-
ples/ subdirectory which has been installed on your system alongside the docu-
mentation. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bu_\bs_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by
+ _\b7_\b._\b4_\b._\b2_\b8_\b5 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bu_\bs_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by
Type: boolean
mailbox-address to determine the key to use. It will ask you to supply a key,
if it can't find one. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b7 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by
+ _\b7_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by
Type: string
+ The Mutt Next Generation E-Mail Client 159
+
Default: ''
This is the default key-pair to use for signing. This must be set to the keyid
(the hash-value that OpenSSL generates) to work properly (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b8 _\bs_\bm_\bi_\bm_\be_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bi_\bm_\be_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to create encrypted S/MIME messages. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b9 _\bs_\bm_\bi_\bm_\be_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bw_\bi_\bt_\bh
+ _\b7_\b._\b4_\b._\b2_\b8_\b8 _\bs_\bm_\bi_\bm_\be_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bw_\bi_\bt_\bh
Type: string
If _\bu_\bn_\bs_\be_\bt ``_\b3_\bd_\be_\bs'' (TripleDES) is used. (S/MIME only)
- The Mutt Next Generation E-Mail Client 157
-
- _\b7_\b._\b4_\b._\b2_\b8_\b0 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b8_\b9 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to extract X509 certificates from a PKCS7 structure.
(S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bc_\be_\br_\bt_\b__\be_\bm_\ba_\bi_\bl_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b9_\b0 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bc_\be_\br_\bt_\b__\be_\bm_\ba_\bi_\bl_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
tificates, and for verification purposes (to check whether the certificate was
issued for the sender's mailbox). (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b2 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bs_\bi_\bg_\bn_\be_\br_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bg_\be_\bt_\b__\bs_\bi_\bg_\bn_\be_\br_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
signature, so that the certificate's owner may get compared to the email's
``From:'' header field. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b3 _\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
+ The Mutt Next Generation E-Mail Client 160
+
+ _\b7_\b._\b4_\b._\b2_\b9_\b2 _\bs_\bm_\bi_\bm_\be_\b__\bi_\bm_\bp_\bo_\br_\bt_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to import a certificate via smime_keysng. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt
+ _\b7_\b._\b4_\b._\b2_\b9_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt
Type: boolean
select the same application that was used to sign/encrypt the original message.
(Note that this variable can be overridden by unsetting _\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bm_\bi_\bm_\be (sec-
- tion 7.4.40 , page 98).) (S/MIME only)
-
- _\b7_\b._\b4_\b._\b2_\b8_\b5 _\bs_\bm_\bi_\bm_\be_\b__\bk_\be_\by_\bs
+ tion 7.4.40 , page 99).) (S/MIME only)
- The Mutt Next Generation E-Mail Client 158
+ _\b7_\b._\b4_\b._\b2_\b9_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bk_\be_\by_\bs
Type: path
address keyid pair, and which can be manually edited. This one points to the
location of the private keys. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bp_\bk_\b7_\bo_\bu_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b9_\b5 _\bs_\bm_\bi_\bm_\be_\b__\bp_\bk_\b7_\bo_\bu_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to extract PKCS7 structures of S/MIME signatures, in order
to extract the public X509 certificate(s). (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bi_\bm_\be_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to created S/MIME signatures of type multipart/signed,
which can be read by all mail clients. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b8 _\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
+ The Mutt Next Generation E-Mail Client 161
+
+ _\b7_\b._\b4_\b._\b2_\b9_\b7 _\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
pkcs7-signature, which can only be handled by mail clients supporting the
S/MIME extension. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b9 _\bs_\bm_\bi_\bm_\be_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b2_\b9_\b8 _\bs_\bm_\bi_\bm_\be_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
The number of seconds after which a cached passphrase will expire if not used.
(S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b9_\b0 _\bs_\bm_\bi_\bm_\be_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b9_\b9 _\bs_\bm_\bi_\bm_\be_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
Default: ''
- The Mutt Next Generation E-Mail Client 159
-
This command is used to verify S/MIME signatures of type multipart/signed.
(S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bo_\bp_\ba_\bq_\bu_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b3_\b0_\b0 _\bs_\bm_\bi_\bm_\be_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bo_\bp_\ba_\bq_\bu_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to verify S/MIME signatures of type application/x-
pkcs7-mime. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b9_\b2 _\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be
+ _\b7_\b._\b4_\b._\b3_\b0_\b1 _\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be
Type: string
envelope sender but only a particular one which may not be the same as the
user's desired From: header.
- _\b7_\b._\b4_\b._\b2_\b9_\b3 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b3_\b0_\b2 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+
+ The Mutt Next Generation E-Mail Client 162
Type: string
Defines the SMTP host which will be used to deliver mail, as opposed to invok-
ing the sendmail binary. Setting this variable overrides the value of ``_\b$_\bs_\be_\bn_\bd_\b-
- _\bm_\ba_\bi_\bl (section 7.4.254 , page 150)'', and any associated variables.
+ _\bm_\ba_\bi_\bl (section 7.4.263 , page 152)'', and any associated variables.
- _\b7_\b._\b4_\b._\b2_\b9_\b4 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b3_\b0_\b3 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
Type: string
Availability: SMTP
Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section
- 7.4.297 , page 160)'' is set, but this variable is not, you will be prompted
+ 7.4.306 , page 162)'' 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 160
-
- _\b7_\b._\b4_\b._\b2_\b9_\b5 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
+ _\b7_\b._\b4_\b._\b3_\b0_\b4 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
Type: number
Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
will probably desire 587, the mail submission port.
- _\b7_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
+ _\b7_\b._\b4_\b._\b3_\b0_\b5 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
Type: string
continue without TLS in case of an error. Muttng still needs to have SSL sup-
port enabled in order to use it.
- _\b7_\b._\b4_\b._\b2_\b9_\b7 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
+ The Mutt Next Generation E-Mail Client 163
+
+ _\b7_\b._\b4_\b._\b3_\b0_\b6 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
Type: string
Defines the username to use with SMTP AUTH. Setting this variable will cause
Mutt-ng to attempt to use SMTP AUTH when sending.
- _\b7_\b._\b4_\b._\b2_\b9_\b8 _\bs_\bo_\br_\bt
+ _\b7_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bo_\br_\bt
Type: sort order
Specifies how to sort messages in the _\bi_\bn_\bd_\be_\bx menu. Valid values are:
- The Mutt Next Generation E-Mail Client 161
-
date or date-sent
date-received
from
You may optionally use the ``reverse-'' prefix to specify reverse sorting order
(example: set sort=reverse-date-sent).
- _\b7_\b._\b4_\b._\b2_\b9_\b9 _\bs_\bo_\br_\bt_\b__\ba_\bl_\bi_\ba_\bs
+ _\b7_\b._\b4_\b._\b3_\b0_\b8 _\bs_\bo_\br_\bt_\b__\ba_\bl_\bi_\ba_\bs
Type: sort order
alias (sort alphabetically by alias name)
unsorted (leave in order specified in .muttrc)
- _\b7_\b._\b4_\b._\b3_\b0_\b0 _\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ _\b7_\b._\b4_\b._\b3_\b0_\b9 _\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
Type: sort order
+ The Mutt Next Generation E-Mail Client 164
+
Default: date
When sorting by threads, this variable controls how threads are sorted in rela-
tion to other threads, and how the branches of the thread trees are sorted.
- This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 7.4.298 , page 160)'' can,
+ This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 7.4.307 , page 163)'' can,
except threads (in that case, Mutt-ng will just use date-sent). You can also
specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
come after reverse-. The last- prefix causes messages to be sorted against its
is received in a thread, that thread becomes the last one displayed (or the
first, if you have set sort=reverse-threads.)
- N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 7.4.298 , page 160)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
- (section 7.4.300 , page 161) is reversed again (which is not the right thing
+ N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 7.4.307 , page 163)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ (section 7.4.309 , page 163) 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 162
-
- _\b7_\b._\b4_\b._\b3_\b0_\b1 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b3_\b1_\b0 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
Type: sort order
You may optionally use the ``reverse-'' prefix to specify reverse sorting order
(example: set sort_browser=reverse-date).
- _\b7_\b._\b4_\b._\b3_\b0_\b2 _\bs_\bo_\br_\bt_\b__\br_\be
+ _\b7_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bo_\br_\bt_\b__\br_\be
Type: boolean
Default: yes
This variable is only useful when sorting by threads with ``_\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
- (section 7.4.319 , page 167)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
- Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.302 ,
- page 162) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
+ (section 7.4.328 , page 170)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.311 ,
+ page 164) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
sage by subject if the subject of the child message starts with a substring
- matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.238 , page 146)''. With
- _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.302 , page 162) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
+ matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.247 , page 149)''. With
+ _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.311 , page 164) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
whether or not this is the case, as long as the non-``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section
- 7.4.238 , page 146)'' parts of both messages are identical.
+ 7.4.247 , page 149)'' parts of both messages are identical.
+
+ The Mutt Next Generation E-Mail Client 165
- _\b7_\b._\b4_\b._\b3_\b0_\b3 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
+ _\b7_\b._\b4_\b._\b3_\b1_\b2 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
Type: string
Default: ','
- ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.303 , page 162)'' controls what happens when
+ ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.312 , page 164)'' controls what happens when
multiple spam headers are matched: if _\bu_\bn_\bs_\be_\bt, each successive header will over-
write any previous matches value for the spam label. If _\bs_\be_\bt, each successive
- match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.303 ,
- page 162)'' as a separator.
+ match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.312 ,
+ page 164)'' as a separator.
- _\b7_\b._\b4_\b._\b3_\b0_\b4 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
+ _\b7_\b._\b4_\b._\b3_\b1_\b3 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
Type: path
Default: ''
If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
-
- The Mutt Next Generation E-Mail Client 163
-
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.
- _\b7_\b._\b4_\b._\b3_\b0_\b5 _\bs_\bs_\bl_\b__\bc_\ba_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs_\b__\bf_\bi_\bl_\be
+ _\b7_\b._\b4_\b._\b3_\b1_\b4 _\bs_\bs_\bl_\b__\bc_\ba_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs_\b__\bf_\bi_\bl_\be
Type: path
Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
- _\b7_\b._\b4_\b._\b3_\b0_\b6 _\bs_\bs_\bl_\b__\bc_\bl_\bi_\be_\bn_\bt_\b__\bc_\be_\br_\bt
+ _\b7_\b._\b4_\b._\b3_\b1_\b5 _\bs_\bs_\bl_\b__\bc_\bl_\bi_\be_\bn_\bt_\b__\bc_\be_\br_\bt
Type: path
The file containing a client certificate and its associated private key.
- _\b7_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bs_\bl_\b__\bf_\bo_\br_\bc_\be_\b__\bt_\bl_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b6 _\bs_\bs_\bl_\b__\bf_\bo_\br_\bc_\be_\b__\bt_\bl_\bs
Type: boolean
If this variable is _\bs_\be_\bt, mutt-ng will require that all connections to remote
servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
server does not advertise the capability, since it would otherwise have to
+
+ The Mutt Next Generation E-Mail Client 166
+
abort the connection anyway. This option supersedes ``_\b$_\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs (section
- 7.4.309 , page 163)''.
+ 7.4.318 , page 166)''.
- _\b7_\b._\b4_\b._\b3_\b0_\b8 _\bs_\bs_\bl_\b__\bm_\bi_\bn_\b__\bd_\bh_\b__\bp_\br_\bi_\bm_\be_\b__\bb_\bi_\bt_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b7 _\bs_\bs_\bl_\b__\bm_\bi_\bn_\b__\bd_\bh_\b__\bp_\br_\bi_\bm_\be_\b__\bb_\bi_\bt_\bs
Type: number
any Diffie-Hellman key exchange. A value of 0 will use the default from the
GNUTLS library.
- _\b7_\b._\b4_\b._\b3_\b0_\b9 _\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b8 _\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs
Type: quadoption
- The Mutt Next Generation E-Mail Client 164
-
Default: yes
Availability: SSL or GNUTLS
ing the capability. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not attempt to use STARTTLS
regardless of the server's capabilities.
- _\b7_\b._\b4_\b._\b3_\b1_\b0 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b2
+ _\b7_\b._\b4_\b._\b3_\b1_\b9 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b2
Type: boolean
This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
tion process.
- _\b7_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b3
+ _\b7_\b._\b4_\b._\b3_\b2_\b0 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b3
Type: boolean
This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
tion process.
- _\b7_\b._\b4_\b._\b3_\b1_\b2 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bt_\bl_\bs_\bv_\b1
+ _\b7_\b._\b4_\b._\b3_\b2_\b1 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bt_\bl_\bs_\bv_\b1
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 167
+
Availability: SSL or GNUTLS
This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
tion process.
- _\b7_\b._\b4_\b._\b3_\b1_\b3 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
+ _\b7_\b._\b4_\b._\b3_\b2_\b2 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
Type: boolean
If set to _\by_\be_\bs, Mutt-ng will use CA certificates in the system-wide certificate
store when checking if server certificate is signed by a trusted CA.
- _\b7_\b._\b4_\b._\b3_\b1_\b4 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs
-
- The Mutt Next Generation E-Mail Client 165
+ _\b7_\b._\b4_\b._\b3_\b2_\b3 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs
Type: string
Default: '-*%A'
Controls the characters used by the ``%r'' indicator in ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (sec-
- tion 7.4.315 , page 164)''. The first character is used when the mailbox is
+ tion 7.4.324 , page 167)''. The first character is used when the mailbox is
unchanged. The second is used when the mailbox has been changed, and it needs
to be resynchronized. The third is used if the mailbox is in read-only mode, or
if the mailbox will not be written when exiting that mailbox (You can toggle
been opened in attach-message mode (Certain operations like composing a new
mail, replying, forwarding, etc. are not permitted in this mode).
- _\b7_\b._\b4_\b._\b3_\b1_\b5 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b3_\b2_\b4 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%l?]---(%s/%S)-%>-(%P)---'
Controls the format of the status line displayed in the _\bi_\bn_\bd_\be_\bx menu. This
- string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 115)'', but has
+ string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.116 , page 116)'', but has
its own set of printf(3)-like sequences:
%b
%d
number of deleted messages *
+ The Mutt Next Generation E-Mail Client 168
+
%f
the full pathname of the current mailbox
%m
the number of messages in the mailbox *
- The Mutt Next Generation E-Mail Client 166
-
%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 7.4.314 , page 164)
+ to _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs (section 7.4.323 , page 167)
%s
- current sorting mode (_\b$_\bs_\bo_\br_\bt (section 7.4.298 , page 160))
+ current sorting mode (_\b$_\bs_\bo_\br_\bt (section 7.4.307 , page 163))
%S
- current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 7.4.300 , page
- 161))
+ current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 7.4.309 , page
+ 163))
%t
number of tagged messages *
%v
Mutt-ng version string
+ The Mutt Next Generation E-Mail Client 169
+
%V
currently active limit pattern, if any *
%?<sequence_char>?<optional_string>?
- The Mutt Next Generation E-Mail Client 167
-
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
replace any dots in the expansion by underscores. This might be helpful with
IMAP folders that don't like dots in folder names.
- _\b7_\b._\b4_\b._\b3_\b1_\b6 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bo_\bn_\b__\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b3_\b2_\b5 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bo_\bn_\b__\bt_\bo_\bp
Type: boolean
Setting this variable causes the ``status bar'' to be displayed on the first
line of the screen rather than near the bottom.
- _\b7_\b._\b4_\b._\b3_\b1_\b7 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo
+ The Mutt Next Generation E-Mail Client 170
+
+ _\b7_\b._\b4_\b._\b3_\b2_\b6 _\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 7.4.59 , page 102)'' is unset.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103)'' is unset.
If this variable is _\bs_\be_\bt, mutt-ng is strict and allows anything to be changed.
If it's _\bu_\bn_\bs_\be_\bt, all headers given will be prefixed with ``X-Mailto-'' and the
message including headers will be shown in the editor regardless of what
- ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 102)'' is set to.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.59 , page 103)'' is set to.
- _\b7_\b._\b4_\b._\b3_\b1_\b8 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b3_\b2_\b7 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
Type: boolean
- The Mutt Next Generation E-Mail Client 168
-
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 7.4.13 , page 91).
+ Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.13 , page 92).
This option also replaces linear-white-space between encoded-word and *text to
a single space to prevent the display of MIME-encoded ``Subject:'' header field
from being devided into multiple lines.
- _\b7_\b._\b4_\b._\b3_\b1_\b9 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
+ _\b7_\b._\b4_\b._\b3_\b2_\b8 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
Type: boolean
Default: no
If _\bs_\be_\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
- ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 7.4.298 , page 160)'' by mes-
+ ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 7.4.307 , page 163)'' by mes-
sage threads. By default, messages with the same subject are grouped together
in ``pseudo threads.'' This may not always be desirable, such as in a personal
mailbox where you might have several unrelated messages with the subject ``hi''
which will get grouped together.
- _\b7_\b._\b4_\b._\b3_\b2_\b0 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
+ _\b7_\b._\b4_\b._\b3_\b2_\b9 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
Type: boolean
Default: no
When _\bs_\be_\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
- matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 7.4.321 , page 168) when replying. This is
+ matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 7.4.330 , page 170) when replying. This is
useful to properly react on subject changes and reduce ``subject noise.'' (esp.
in Usenet)
- _\b7_\b._\b4_\b._\b3_\b2_\b1 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
+ The Mutt Next Generation E-Mail Client 171
+
+ _\b7_\b._\b4_\b._\b3_\b3_\b0 _\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 7.4.320 , page 168) is _\bs_\be_\bt, mutt-ng
+ When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 7.4.329 , page 170) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
- _\b7_\b._\b4_\b._\b3_\b2_\b2 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b3_\b3_\b1 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
Type: boolean
If _\bs_\be_\bt, attachments with flowed format will have their quoting ``stuffed'',
i.e. a space will be inserted between the quote characters and the actual text.
- The Mutt Next Generation E-Mail Client 169
-
- _\b7_\b._\b4_\b._\b3_\b2_\b3 _\bs_\bu_\bs_\bp_\be_\bn_\bd
+ _\b7_\b._\b4_\b._\b3_\b3_\b2 _\bs_\bu_\bs_\bp_\be_\bn_\bd
Type: boolean
usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
mand like ``xterm -e muttng.''
- _\b7_\b._\b4_\b._\b3_\b2_\b4 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
+ _\b7_\b._\b4_\b._\b3_\b3_\b3 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
Type: boolean
like ordinary text. To actually make use of this format's features, you'll
need support in your editor.
- Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.115 , page 115) is ignored when this
+ Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.115 , page 116) is ignored when this
option is set.
- _\b7_\b._\b4_\b._\b3_\b2_\b5 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b7_\b._\b4_\b._\b3_\b3_\b4 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
Type: boolean
Default: no
Affects the ~b and ~h search operations described in section ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (sec-
- tion 7.2 , page 83)'' above. If _\bs_\be_\bt, the headers and attachments of messages
+ tion 7.2 , page 84)'' 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.
- _\b7_\b._\b4_\b._\b3_\b2_\b6 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
+ The Mutt Next Generation E-Mail Client 172
+
+ _\b7_\b._\b4_\b._\b3_\b3_\b5 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng uses the date received rather than the date sent to thread
messages by subject.
- _\b7_\b._\b4_\b._\b3_\b2_\b7 _\bt_\bi_\bl_\bd_\be
+ _\b7_\b._\b4_\b._\b3_\b3_\b6 _\bt_\bi_\bl_\bd_\be
Type: boolean
When _\bs_\be_\bt, the internal-pager will pad blank lines to the bottom of the screen
with a tilde (~).
- The Mutt Next Generation E-Mail Client 170
-
- _\b7_\b._\b4_\b._\b3_\b2_\b8 _\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b3_\b3_\b7 _\bt_\bi_\bm_\be_\bo_\bu_\bt
Type: number
pressed in the main menu before timing out and checking for new mail. A value
of zero or less will cause Mutt-ng to never time out.
- _\b7_\b._\b4_\b._\b3_\b2_\b9 _\bt_\bm_\bp_\bd_\bi_\br
+ _\b7_\b._\b4_\b._\b3_\b3_\b8 _\bt_\bm_\bp_\bd_\bi_\br
Type: path
set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
'/tmp' is used.
- _\b7_\b._\b4_\b._\b3_\b3_\b0 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
+ _\b7_\b._\b4_\b._\b3_\b3_\b9 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
Type: string
indicate mail that was sent by _\by_\bo_\bu. The sixth character is used to indicate
when a mail was sent to a mailing-list you're subscribe to (default: L).
- _\b7_\b._\b4_\b._\b3_\b3_\b1 _\bt_\br_\ba_\bs_\bh
+ The Mutt Next Generation E-Mail Client 173
+
+ _\b7_\b._\b4_\b._\b3_\b4_\b0 _\bt_\br_\ba_\bs_\bh
Type: path
N\bNo\bot\bte\be: When you delete a message in the trash folder, it is really deleted, so
that there is no way to recover mail.
- _\b7_\b._\b4_\b._\b3_\b3_\b2 _\bt_\bu_\bn_\bn_\be_\bl
+ _\b7_\b._\b4_\b._\b3_\b4_\b1 _\bt_\bu_\bn_\bn_\be_\bl
Type: string
Default: ''
- The Mutt Next Generation E-Mail Client 171
-
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:
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.
- _\b7_\b._\b4_\b._\b3_\b3_\b3 _\bu_\bm_\ba_\bs_\bk
+ _\b7_\b._\b4_\b._\b3_\b4_\b2 _\bu_\bm_\ba_\bs_\bk
Type: number
This sets the umask that will be used by Mutt-ng when creating all kinds of
files. If _\bu_\bn_\bs_\be_\bt, the default value is 077.
- _\b7_\b._\b4_\b._\b3_\b3_\b4 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
+ _\b7_\b._\b4_\b._\b3_\b4_\b3 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
Type: boolean
When _\bs_\be_\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
rent thread is _\bu_\bncollapsed.
- _\b7_\b._\b4_\b._\b3_\b3_\b5 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b3_\b4_\b4 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
Type: boolean
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 174
+
mail.
- When _\bs_\be_\bt, Mutt-ng will either invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.254 , page
- 150)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
+ When _\bs_\be_\bt, Mutt-ng will either invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.263 , page
+ 152)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
negotiation or tell libESMTP to do so.
- _\b7_\b._\b4_\b._\b3_\b3_\b6 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
+ _\b7_\b._\b4_\b._\b3_\b4_\b5 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
Type: boolean
Default: yes
When _\bs_\be_\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
- tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 7.4.95 , page 110)''. If _\bu_\bn_\bs_\be_\bt,
+ tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 7.4.95 , page 111)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
- _\b7_\b._\b4_\b._\b3_\b3_\b7 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
-
- The Mutt Next Generation E-Mail Client 172
+ _\b7_\b._\b4_\b._\b3_\b4_\b6 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
Type: boolean
When _\bs_\be_\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
sages. If _\bu_\bn_\bs_\be_\bt, no ``From:'' header field will be generated unless the user
- explicitly sets one using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 37)'' command.
+ explicitly sets one using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 38)'' command.
- _\b7_\b._\b4_\b._\b3_\b3_\b8 _\bu_\bs_\be_\b__\bi_\bd_\bn
+ _\b7_\b._\b4_\b._\b3_\b4_\b7 _\bu_\bs_\be_\b__\bi_\bd_\bn
Type: boolean
N\bNo\bot\bte\be:\b: You can use IDNs for addresses even if this is _\bu_\bn_\bs_\be_\bt. This variable only
affects decoding.
- _\b7_\b._\b4_\b._\b3_\b3_\b9 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
+ _\b7_\b._\b4_\b._\b3_\b4_\b8 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
Type: boolean
If this option is _\bu_\bn_\bs_\be_\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
mally, the default should work.
- _\b7_\b._\b4_\b._\b3_\b4_\b0 _\bv_\bi_\bs_\bu_\ba_\bl
+ _\b7_\b._\b4_\b._\b3_\b4_\b9 _\bv_\bi_\bs_\bu_\ba_\bl
Type: path
Default: ''
+ The Mutt Next Generation E-Mail Client 175
+
Specifies the visual editor to invoke when the _\b~_\bv command is given in the
builtin editor.
- _\b7_\b._\b4_\b._\b3_\b4_\b1 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
+ _\b7_\b._\b4_\b._\b3_\b5_\b0 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
Type: boolean
_\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
- 78)'', provided that the corresponding mailcap entry has a needsterminal flag,
+ 79)'', 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
-
- The Mutt Next Generation E-Mail Client 173
-
a key only if the external command returned a non-zero status.
- _\b7_\b._\b4_\b._\b3_\b4_\b2 _\bw_\be_\be_\bd
+ _\b7_\b._\b4_\b._\b3_\b5_\b1 _\bw_\be_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
replying to messages.
- _\b7_\b._\b4_\b._\b3_\b4_\b3 _\bw_\br_\ba_\bp_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b7_\b._\b4_\b._\b3_\b5_\b2 _\bw_\br_\ba_\bp_\b__\bs_\be_\ba_\br_\bc_\bh
Type: boolean
When _\bs_\be_\bt, searches will wrap around the first (or last) message. When _\bu_\bn_\bs_\be_\bt,
searches will not wrap.
- _\b7_\b._\b4_\b._\b3_\b4_\b4 _\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
+ _\b7_\b._\b4_\b._\b3_\b5_\b3 _\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
Type: number
Controls the size of the margin remaining at the right side of the terminal
when Mutt-ng's pager does smart wrapping.
- _\b7_\b._\b4_\b._\b3_\b4_\b5 _\bw_\br_\bi_\bt_\be_\b__\bb_\bc_\bc
+ _\b7_\b._\b4_\b._\b3_\b5_\b4 _\bw_\br_\bi_\bt_\be_\b__\bb_\bc_\bc
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 176
+
Controls whether Mutt-ng writes out the Bcc header when preparing messages to
be sent. Exim users may wish to _\bu_\bn_\bs_\be_\bt this.
- _\b7_\b._\b4_\b._\b3_\b4_\b6 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
+ _\b7_\b._\b4_\b._\b3_\b5_\b5 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
Type: number
indicate progress. If set to 0, only a single message will be displayed before
writing a mailbox.
- Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 7.4.233 , page 145)'' variable.
-
- _\b7_\b._\b4_\b._\b3_\b4_\b7 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
+ Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 7.4.242 , page 147)'' variable.
- The Mutt Next Generation E-Mail Client 174
+ _\b7_\b._\b4_\b._\b3_\b5_\b6 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
Type: string
Default: 'M%?n?AIL&ail?'
Controls the format of the X11 icon title, as long as _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (sec-
- tion 7.4.349 , page 174) is _\bs_\be_\bt. This string is identical in formatting to the
- one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.315 , page 164)''.
+ tion 7.4.358 , page 176) is _\bs_\be_\bt. This string is identical in formatting to the
+ one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.324 , page 167)''.
- _\b7_\b._\b4_\b._\b3_\b4_\b8 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
+ _\b7_\b._\b4_\b._\b3_\b5_\b7 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
Type: string
Default: ''
- If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.349 , page 174) is _\bs_\be_\bt, this string will be
+ If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.358 , page 176) is _\bs_\be_\bt, this string will be
used to set the title when leaving mutt-ng. For terminal-based programs,
there's no easy and portable way to read the current title so mutt-ng cannot
read it upon startup and restore it when exiting.
set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
cut -d ''' -f 2`'
- _\b7_\b._\b4_\b._\b3_\b4_\b9 _\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs
+ _\b7_\b._\b4_\b._\b3_\b5_\b8 _\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs
Type: boolean
you're in an appropriate terminal). The default must be _\bu_\bn_\bs_\be_\bt to force in the
validity checking.
- _\b7_\b._\b4_\b._\b3_\b5_\b0 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
+ _\b7_\b._\b4_\b._\b3_\b5_\b9 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
Type: string
+ The Mutt Next Generation E-Mail Client 177
+
Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
Controls the format of the title bar of the xterm provided that
- _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.349 , page 174) has been _\bs_\be_\bt. This string is
- identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.315 ,
- page 164)''.
+ _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.358 , page 176) has been _\bs_\be_\bt. This string is
+ identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.324 ,
+ page 167)''.
_\b7_\b._\b5 _\bF_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
The following is the list of available functions listed by the mapping in which
they are available. The default key setting is given, and an explanation of
what the function does. The key bindings of these functions can be changed
- with the _\bb_\bi_\bn_\bd (section 3.5 , page 26) command.
+ with the _\bb_\bi_\bn_\bd (section 3.5 , page 27) command.
_\b7_\b._\b5_\b._\b1 _\bg_\be_\bn_\be_\br_\bi_\bc
- The Mutt Next Generation E-Mail Client 175
-
The _\bg_\be_\bn_\be_\br_\bi_\bc menu is not a real menu, but specifies common functions (such as
movement) available in all menus except for _\bp_\ba_\bg_\be_\br and _\be_\bd_\bi_\bt_\bo_\br. Changing set-
tings for this menu will affect the default bindings for all menus (except as
top-page H move to the top of the page
what-key not bound display the keycode for a key press
+ The Mutt Next Generation E-Mail Client 178
+
_\b7_\b._\b5_\b._\b2 _\bi_\bn_\bd_\be_\bx
- The Mutt Next Generation E-Mail Client 176
+ The Mutt Next Generation E-Mail Client 179
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 177
+ The Mutt Next Generation E-Mail Client 180
sort-mailbox o sort messages
sort-reverse O sort messages in reverse order
_\b7_\b._\b5_\b._\b3 _\bp_\ba_\bg_\be_\br
- The Mutt Next Generation E-Mail Client 178
+ The Mutt Next Generation E-Mail Client 181
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 179
+ The Mutt Next Generation E-Mail Client 182
reply r reply to a message
save-message s save message/attachment to a file
_\b7_\b._\b5_\b._\b6 _\ba_\bt_\bt_\ba_\bc_\bh
- The Mutt Next Generation E-Mail Client 180
+ The Mutt Next Generation E-Mail Client 183
bounce-message b remail a message to another user
collapse-parts v toggle display of subparts
_\b7_\b._\b5_\b._\b7 _\bc_\bo_\bm_\bp_\bo_\bs_\be
- The Mutt Next Generation E-Mail Client 181
+ The Mutt Next Generation E-Mail Client 184
attach-file a attach a file(s) to this message
attach-message A attach message(s) to this message
_\b7_\b._\b5_\b._\b9 _\bb_\br_\bo_\bw_\bs_\be_\br
- The Mutt Next Generation E-Mail Client 182
+ The Mutt Next Generation E-Mail Client 185
change-dir c change directories
check-new TAB check mailboxes for new mail
_\b8_\b. _\bM_\bi_\bs_\bc_\be_\bl_\bl_\ba_\bn_\by
- The Mutt Next Generation E-Mail Client 183
+ The Mutt Next Generation E-Mail Client 186
_\b8_\b._\b1 _\bA_\bc_\bk_\bn_\bo_\bw_\bl_\be_\bd_\bg_\bm_\be_\bn_\bt_\bs
Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
- The Mutt Next Generation E-Mail Client 184
+ The Mutt Next Generation E-Mail Client 187
Brandon Long <blong@fiction.net>,
Elimar Riesebieter <riesebie@lxtec.de>
- The Mutt Next Generation E-Mail Client 185
+ The Mutt Next Generation E-Mail Client 188
_\b8_\b._\b2 _\bA_\bb_\bo_\bu_\bt _\bt_\bh_\bi_\bs _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt
This document was written in SGML, and then rendered using the sgml-tools pack-
age.
- The Mutt Next Generation E-Mail Client 186
+ The Mutt Next Generation E-Mail Client 189
CONTENTS
3. Configuration ........................................................ 21
3.1 Locations of Configuration Files ............................... 21
3.2 Basic Syntax of Initialization Files ........................... 21
- 3.3 Variable Expansion ........................................... 23
+ 3.3 Expansion within variables ................................... 23
3.3.1 Commands' Output 23
3.3.2 Environment Variables 23
i
3.3.3 Configuration Variables 23
- 3.3.4 Self-Defined Variables 23
- 3.3.5 Type Conversions 25
- 3.4 Defining/Using aliases ......................................... 25
- 3.5 Changing the default key bindings .............................. 26
- 3.6 Defining aliases for character sets ........................... 28
- 3.7 Setting variables based upon mailbox ........................... 28
- 3.8 Keyboard macros ................................................ 29
- 3.9 Using color and mono video attributes .......................... 30
- 3.10 Ignoring (weeding) unwanted message headers .................... 32
- 3.11 Alternative addresses .......................................... 33
- 3.12 Format = Flowed .............................................. 33
- 3.12.1 Introduction 33
- 3.12.2 Receiving: Display Setup 33
- 3.12.3 Sending 34
- 3.12.4 Additional Notes 35
- 3.13 Mailing lists .................................................. 35
- 3.14 Using Multiple spool mailboxes ................................. 36
- 3.15 Defining mailboxes which receive mail .......................... 36
- 3.16 User defined headers ........................................... 37
- 3.17 Defining the order of headers when viewing messages ............ 38
- 3.18 Specify default save filename .................................. 38
- 3.19 Specify default Fcc: mailbox when composing .................... 38
- 3.20 Specify default save filename and default Fcc: mailbox at once . 39
- 3.21 Change settings based upon message recipients .................. 39
- 3.22 Change settings before formatting a message .................... 40
- 3.23 Choosing the cryptographic key of the recipient ................ 40
- 3.24 Adding key sequences to the keyboard buffer .................... 40
- 3.25 Executing functions ............................................ 41
- 3.26 Message Scoring ................................................ 41
- 3.27 Spam detection ................................................. 42
- 3.28 Setting variables .............................................. 44
- 3.29 Reading initialization commands from another file .............. 45
- 3.30 Removing hooks ................................................. 45
- 3.31 Sharing Setups ............................................. 45
- 3.31.1 Character Sets 45
- 3.31.2 Modularization 46
- 3.31.3 Conditional parts 46
- 3.32 Obsolete Variables ............................................. 48
-
- 4. Advanced Usage ....................................................... 48
- 4.1 Regular Expressions ............................................ 48
- 4.2 Patterns ....................................................... 51
- 4.2.1 Complex Patterns 51
- 4.2.2 Patterns and Dates 52
- 4.3 Format Strings ............................................. 52
- 4.3.1 Introduction 52
- 4.3.2 Conditional Expansion 54
- 4.3.3 Modifications and Padding 55
- 4.4 Using Tags ..................................................... 55
- 4.5 Using Hooks .................................................... 56
- 4.5.1 Message Matching in Hooks 57
- 4.6 Using the sidebar .............................................. 57
+ 3.3.4 Self-Defined Variables 24
+ 3.3.5 Pre-Defined Variables 25
+ 3.3.6 Type Conversions 26
+ 3.4 Defining/Using aliases ......................................... 26
+ 3.5 Changing the default key bindings .............................. 27
+ 3.6 Defining aliases for character sets ........................... 29
+ 3.7 Setting variables based upon mailbox ........................... 29
+ 3.8 Keyboard macros ................................................ 30
+ 3.9 Using color and mono video attributes .......................... 31
+ 3.10 Ignoring (weeding) unwanted message headers .................... 33
+ 3.11 Alternative addresses .......................................... 34
+ 3.12 Format = Flowed .............................................. 34
+ 3.12.1 Introduction 34
+ 3.12.2 Receiving: Display Setup 34
+ 3.12.3 Sending 35
+ 3.12.4 Additional Notes 36
+ 3.13 Mailing lists .................................................. 36
+ 3.14 Using Multiple spool mailboxes ................................. 37
+ 3.15 Defining mailboxes which receive mail .......................... 37
+ 3.16 User defined headers ........................................... 38
+ 3.17 Defining the order of headers when viewing messages ............ 39
+ 3.18 Specify default save filename .................................. 39
+ 3.19 Specify default Fcc: mailbox when composing .................... 39
+ 3.20 Specify default save filename and default Fcc: mailbox at once . 40
+ 3.21 Change settings based upon message recipients .................. 40
+ 3.22 Change settings before formatting a message .................... 41
+ 3.23 Choosing the cryptographic key of the recipient ................ 41
+ 3.24 Adding key sequences to the keyboard buffer .................... 41
+ 3.25 Executing functions ............................................ 42
+ 3.26 Message Scoring ................................................ 42
+ 3.27 Spam detection ................................................. 43
+ 3.28 Setting variables .............................................. 45
+ 3.29 Reading initialization commands from another file .............. 46
+ 3.30 Removing hooks ................................................. 46
+ 3.31 Sharing Setups ............................................. 46
+ 3.31.1 Character Sets 46
+ 3.31.2 Modularization 47
+ 3.31.3 Conditional parts 47
+ 3.32 Obsolete Variables ............................................. 49
+
+ 4. Advanced Usage ....................................................... 49
+ 4.1 Regular Expressions ............................................ 49
+ 4.2 Patterns ....................................................... 52
+ 4.2.1 Complex Patterns 52
+ 4.2.2 Patterns and Dates 53
+ 4.3 Format Strings ............................................. 53
+ 4.3.1 Introduction 53
+ 4.3.2 Conditional Expansion 55
+ 4.3.3 Modifications and Padding 56
+ 4.4 Using Tags ..................................................... 56
+ 4.5 Using Hooks .................................................... 57
+ 4.5.1 Message Matching in Hooks 58
ii
- 4.7 External Address Queries ....................................... 58
- 4.8 Mailbox Formats ................................................ 59
- 4.9 Mailbox Shortcuts .............................................. 60
- 4.10 Handling Mailing Lists ......................................... 60
- 4.11 Editing threads ................................................ 61
- 4.11.1 Linking threads 62
- 4.11.2 Breaking threads 62
- 4.12 Delivery Status Notification (DSN) Support ..................... 62
- 4.13 POP3 Support (OPTIONAL) ........................................ 62
- 4.14 IMAP Support (OPTIONAL) ........................................ 63
- 4.14.1 The Folder Browser 64
- 4.14.2 Authentication 64
- 4.15 NNTP Support (OPTIONAL) ........................................ 65
- 4.15.1 Again: Scoring 65
- 4.16 SMTP Support (OPTIONAL) ........................................ 66
- 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 67
- 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 67
- 4.19 Compressed folders Support (OPTIONAL) .......................... 67
- 4.19.1 Open a compressed mailbox for reading 68
- 4.19.2 Write a compressed mailbox 68
- 4.19.3 Append a message to a compressed mailbox 69
- 4.19.4 Encrypted folders 70
-
- 5. Mutt-ng's MIME Support ............................................... 70
- 5.1 Using MIME in Mutt ............................................. 70
- 5.1.1 Viewing MIME messages in the pager 70
- 5.1.2 The Attachment Menu 71
- 5.1.3 The Compose Menu 71
- 5.2 MIME Type configuration with mime.types ........................ 71
- 5.3 MIME Viewer configuration with mailcap ......................... 72
- 5.3.1 The Basics of the mailcap file 73
- 5.3.2 Secure use of mailcap 74
- 5.3.3 Advanced mailcap Usage 74
- 5.3.4 Example mailcap files 77
- 5.4 MIME Autoview .................................................. 78
- 5.5 MIME Multipart/Alternative ..................................... 79
- 5.6 MIME Lookup .................................................... 79
-
- 6. Security Considerations ............................................ 80
- 6.1 Passwords .................................................. 80
- 6.2 Temporary Files ............................................ 80
- 6.3 Information Leaks ............................................ 80
- 6.3.1 Message-ID: headers 80
- 6.3.2 mailto:-style links 81
- 6.4 External applications ...................................... 81
- 6.4.1 mailcap 81
- 6.4.2 Other 82
-
- 7. Reference ............................................................ 82
- 7.1 Command line options ........................................... 82
- 7.2 Patterns ....................................................... 83
- 7.3 Configuration Commands ......................................... 85
- 7.4 Configuration variables .......................................... 87
+ 4.6 Using the sidebar .............................................. 58
+ 4.7 External Address Queries ....................................... 59
+ 4.8 Mailbox Formats ................................................ 60
+ 4.9 Mailbox Shortcuts .............................................. 61
+ 4.10 Handling Mailing Lists ......................................... 61
+ 4.11 Editing threads ................................................ 62
+ 4.11.1 Linking threads 63
+ 4.11.2 Breaking threads 63
+ 4.12 Delivery Status Notification (DSN) Support ..................... 63
+ 4.13 POP3 Support (OPTIONAL) ........................................ 63
+ 4.14 IMAP Support (OPTIONAL) ........................................ 64
+ 4.14.1 The Folder Browser 65
+ 4.14.2 Authentication 65
+ 4.15 NNTP Support (OPTIONAL) ........................................ 66
+ 4.15.1 Again: Scoring 66
+ 4.16 SMTP Support (OPTIONAL) ........................................ 67
+ 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 68
+ 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 68
+ 4.19 Compressed folders Support (OPTIONAL) .......................... 68
+ 4.19.1 Open a compressed mailbox for reading 69
+ 4.19.2 Write a compressed mailbox 69
+ 4.19.3 Append a message to a compressed mailbox 70
+ 4.19.4 Encrypted folders 71
+
+ 5. Mutt-ng's MIME Support ............................................... 71
+ 5.1 Using MIME in Mutt ............................................. 71
+ 5.1.1 Viewing MIME messages in the pager 71
+ 5.1.2 The Attachment Menu 72
+ 5.1.3 The Compose Menu 72
+ 5.2 MIME Type configuration with mime.types ........................ 72
+ 5.3 MIME Viewer configuration with mailcap ......................... 73
+ 5.3.1 The Basics of the mailcap file 74
+ 5.3.2 Secure use of mailcap 75
+ 5.3.3 Advanced mailcap Usage 75
+ 5.3.4 Example mailcap files 78
+ 5.4 MIME Autoview .................................................. 79
+ 5.5 MIME Multipart/Alternative ..................................... 80
+ 5.6 MIME Lookup .................................................... 80
+
+ 6. Security Considerations ............................................ 81
+ 6.1 Passwords .................................................. 81
+ 6.2 Temporary Files ............................................ 81
+ 6.3 Information Leaks ............................................ 81
+ 6.3.1 Message-ID: headers 81
+ 6.3.2 mailto:-style links 82
+ 6.4 External applications ...................................... 82
+ 6.4.1 mailcap 82
+ 6.4.2 Other 83
+
+ 7. Reference ............................................................ 83
+ 7.1 Command line options ........................................... 83
+ 7.2 Patterns ....................................................... 84
+ 7.3 Configuration Commands ......................................... 86
iii
- 7.4.1 abort_noattach 88
- 7.4.2 abort_nosubject 89
- 7.4.3 abort_unmodified 89
- 7.4.4 agent_string 89
- 7.4.5 alias_file 89
- 7.4.6 alias_format 89
- 7.4.7 allow_8bit 90
- 7.4.8 allow_ansi 90
- 7.4.9 arrow_cursor 90
- 7.4.10 ascii_chars 91
- 7.4.11 askbcc 91
- 7.4.12 askcc 91
- 7.4.13 assumed_charset 91
- 7.4.14 attach_format 91
- 7.4.15 attach_remind_regexp 92
- 7.4.16 attach_sep 93
- 7.4.17 attach_split 93
- 7.4.18 attribution 93
- 7.4.19 auto_tag 93
- 7.4.20 autoedit 93
- 7.4.21 beep 94
- 7.4.22 beep_new 94
- 7.4.23 bounce 94
- 7.4.24 bounce_delivered 94
- 7.4.25 braille_friendly 94
- 7.4.26 certificate_file 95
- 7.4.27 charset 95
- 7.4.28 check_new 95
- 7.4.29 collapse_unread 95
- 7.4.30 compose_format 96
- 7.4.31 config_charset 96
- 7.4.32 confirmappend 96
- 7.4.33 confirmcreate 96
- 7.4.34 connect_timeout 96
- 7.4.35 content_type 97
- 7.4.36 copy 97
- 7.4.37 crypt_autoencrypt 97
- 7.4.38 crypt_autopgp 97
- 7.4.39 crypt_autosign 98
- 7.4.40 crypt_autosmime 98
- 7.4.41 crypt_replyencrypt 98
- 7.4.42 crypt_replysign 98
- 7.4.43 crypt_replysignencrypted 98
- 7.4.44 crypt_timestamp 99
- 7.4.45 crypt_use_gpgme 99
- 7.4.46 crypt_verify_sig 99
- 7.4.47 date_format 99
- 7.4.48 debug_level 100
- 7.4.49 default_hook 100
- 7.4.50 delete 100
- 7.4.51 delete_space 100
- 7.4.52 delete_untag 101
- 7.4.53 digest_collapse 101
+ 7.4 Configuration variables .......................................... 88
+ 7.4.1 abort_noattach 89
+ 7.4.2 abort_nosubject 90
+ 7.4.3 abort_unmodified 90
+ 7.4.4 agent_string 90
+ 7.4.5 alias_file 90
+ 7.4.6 alias_format 90
+ 7.4.7 allow_8bit 91
+ 7.4.8 allow_ansi 91
+ 7.4.9 arrow_cursor 91
+ 7.4.10 ascii_chars 92
+ 7.4.11 askbcc 92
+ 7.4.12 askcc 92
+ 7.4.13 assumed_charset 92
+ 7.4.14 attach_format 92
+ 7.4.15 attach_remind_regexp 93
+ 7.4.16 attach_sep 94
+ 7.4.17 attach_split 94
+ 7.4.18 attribution 94
+ 7.4.19 auto_tag 94
+ 7.4.20 autoedit 94
+ 7.4.21 beep 95
+ 7.4.22 beep_new 95
+ 7.4.23 bounce 95
+ 7.4.24 bounce_delivered 95
+ 7.4.25 braille_friendly 95
+ 7.4.26 certificate_file 96
+ 7.4.27 charset 96
+ 7.4.28 check_new 96
+ 7.4.29 collapse_unread 96
+ 7.4.30 compose_format 97
+ 7.4.31 config_charset 97
+ 7.4.32 confirmappend 97
+ 7.4.33 confirmcreate 97
+ 7.4.34 connect_timeout 97
+ 7.4.35 content_type 98
+ 7.4.36 copy 98
+ 7.4.37 crypt_autoencrypt 98
+ 7.4.38 crypt_autopgp 98
+ 7.4.39 crypt_autosign 99
+ 7.4.40 crypt_autosmime 99
+ 7.4.41 crypt_replyencrypt 99
+ 7.4.42 crypt_replysign 99
+ 7.4.43 crypt_replysignencrypted 99
+ 7.4.44 crypt_timestamp 100
+ 7.4.45 crypt_use_gpgme 100
+ 7.4.46 crypt_verify_sig 100
+ 7.4.47 date_format 100
+ 7.4.48 debug_level 101
+ 7.4.49 default_hook 101
+ 7.4.50 delete 101
+ 7.4.51 delete_space 101
+ 7.4.52 delete_untag 102
iv
- 7.4.54 display_filter 101
- 7.4.55 dotlock_program 101
- 7.4.56 dsn_notify 101
- 7.4.57 dsn_return 102
- 7.4.58 duplicate_threads 102
- 7.4.59 edit_headers 102
- 7.4.60 editor 102
- 7.4.61 editor_headers 102
- 7.4.62 encode_from 103
- 7.4.63 entropy_file 103
- 7.4.64 envelope_from 103
- 7.4.65 escape 103
- 7.4.66 fast_reply 104
- 7.4.67 fcc_attach 104
- 7.4.68 fcc_clear 104
- 7.4.69 file_charset 104
- 7.4.70 folder 104
- 7.4.71 folder_format 105
- 7.4.72 followup_to 106
- 7.4.73 force_buffy_check 106
- 7.4.74 force_name 106
- 7.4.75 forward_decode 106
- 7.4.76 forward_decrypt 107
- 7.4.77 forward_edit 107
- 7.4.78 forward_format 107
- 7.4.79 forward_quote 107
- 7.4.80 from 107
- 7.4.81 gecos_mask 108
- 7.4.82 hdrs 108
- 7.4.83 header 108
- 7.4.84 header_cache 108
- 7.4.85 header_cache_compress 109
- 7.4.86 help 109
- 7.4.87 hidden_host 109
- 7.4.88 hide_limited 109
- 7.4.89 hide_missing 109
- 7.4.90 hide_thread_subject 110
- 7.4.91 hide_top_limited 110
- 7.4.92 hide_top_missing 110
- 7.4.93 history 110
- 7.4.94 honor_followup_to 110
- 7.4.95 hostname 111
- 7.4.96 ignore_list_reply_to 111
- 7.4.97 imap_authenticators 111
- 7.4.98 imap_check_subscribed 111
- 7.4.99 imap_delim_chars 112
- 7.4.100 imap_headers 112
- 7.4.101 imap_home_namespace 112
- 7.4.102 imap_keepalive 112
- 7.4.103 imap_list_subscribed 113
- 7.4.104 imap_login 113
- 7.4.105 imap_mail_check 113
- 7.4.106 imap_pass 113
+ 7.4.53 digest_collapse 102
+ 7.4.54 display_filter 102
+ 7.4.55 dotlock_program 102
+ 7.4.56 dsn_notify 102
+ 7.4.57 dsn_return 103
+ 7.4.58 duplicate_threads 103
+ 7.4.59 edit_headers 103
+ 7.4.60 editor 103
+ 7.4.61 editor_headers 103
+ 7.4.62 encode_from 104
+ 7.4.63 entropy_file 104
+ 7.4.64 envelope_from 104
+ 7.4.65 escape 104
+ 7.4.66 fast_reply 105
+ 7.4.67 fcc_attach 105
+ 7.4.68 fcc_clear 105
+ 7.4.69 file_charset 105
+ 7.4.70 folder 105
+ 7.4.71 folder_format 106
+ 7.4.72 followup_to 107
+ 7.4.73 force_buffy_check 107
+ 7.4.74 force_name 107
+ 7.4.75 forward_decode 107
+ 7.4.76 forward_decrypt 108
+ 7.4.77 forward_edit 108
+ 7.4.78 forward_format 108
+ 7.4.79 forward_quote 108
+ 7.4.80 from 108
+ 7.4.81 gecos_mask 109
+ 7.4.82 hdrs 109
+ 7.4.83 header 109
+ 7.4.84 header_cache 109
+ 7.4.85 header_cache_compress 110
+ 7.4.86 help 110
+ 7.4.87 hidden_host 110
+ 7.4.88 hide_limited 110
+ 7.4.89 hide_missing 110
+ 7.4.90 hide_thread_subject 111
+ 7.4.91 hide_top_limited 111
+ 7.4.92 hide_top_missing 111
+ 7.4.93 history 111
+ 7.4.94 honor_followup_to 111
+ 7.4.95 hostname 112
+ 7.4.96 ignore_list_reply_to 112
+ 7.4.97 imap_authenticators 112
+ 7.4.98 imap_check_subscribed 112
+ 7.4.99 imap_delim_chars 113
+ 7.4.100 imap_headers 113
+ 7.4.101 imap_home_namespace 113
+ 7.4.102 imap_keepalive 113
+ 7.4.103 imap_list_subscribed 114
+ 7.4.104 imap_login 114
+ 7.4.105 imap_mail_check 114
v
- 7.4.107 imap_passive 114
- 7.4.108 imap_peek 114
- 7.4.109 imap_reconnect 114
- 7.4.110 imap_servernoise 114
- 7.4.111 imap_user 115
- 7.4.112 implicit_autoview 115
- 7.4.113 include 115
- 7.4.114 include_onlyfirst 115
- 7.4.115 indent_string 115
- 7.4.116 index_format 115
- 7.4.117 ispell 118
- 7.4.118 keep_flagged 118
- 7.4.119 list_reply 119
- 7.4.120 locale 119
- 7.4.121 mail_check 119
- 7.4.122 mailcap_path 119
- 7.4.123 mailcap_sanitize 119
- 7.4.124 maildir_header_cache_verify 119
- 7.4.125 maildir_trash 120
- 7.4.126 mark_old 120
- 7.4.127 markers 120
- 7.4.128 mask 120
- 7.4.129 max_display_recips 121
- 7.4.130 max_line_length 121
- 7.4.131 mbox 121
- 7.4.132 mbox_type 121
- 7.4.133 menu_context 121
- 7.4.134 menu_move_off 122
- 7.4.135 menu_scroll 122
- 7.4.136 message_format 122
- 7.4.137 meta_key 122
- 7.4.138 metoo 122
- 7.4.139 mh_purge 123
- 7.4.140 mh_seq_flagged 123
- 7.4.141 mh_seq_replied 123
- 7.4.142 mh_seq_unseen 123
- 7.4.143 mime_forward 123
- 7.4.144 mime_forward_decode 123
- 7.4.145 mime_forward_rest 124
- 7.4.146 mix_entry_format 124
- 7.4.147 mixmaster 124
- 7.4.148 move 124
- 7.4.149 msgid_format 125
- 7.4.150 narrow_tree 126
- 7.4.151 nntp_ask_followup_to 126
- 7.4.152 nntp_ask_x_comment_to 126
- 7.4.153 nntp_cache_dir 126
- 7.4.154 nntp_catchup 127
- 7.4.155 nntp_context 127
- 7.4.156 nntp_followup_to_poster 127
- 7.4.157 nntp_group_index_format 127
- 7.4.158 nntp_host 128
- 7.4.159 nntp_inews 128
+ 7.4.106 imap_pass 114
+ 7.4.107 imap_passive 115
+ 7.4.108 imap_peek 115
+ 7.4.109 imap_reconnect 115
+ 7.4.110 imap_servernoise 115
+ 7.4.111 imap_user 116
+ 7.4.112 implicit_autoview 116
+ 7.4.113 include 116
+ 7.4.114 include_onlyfirst 116
+ 7.4.115 indent_string 116
+ 7.4.116 index_format 116
+ 7.4.117 ispell 119
+ 7.4.118 keep_flagged 119
+ 7.4.119 list_reply 120
+ 7.4.120 locale 120
+ 7.4.121 mail_check 120
+ 7.4.122 mailcap_path 120
+ 7.4.123 mailcap_sanitize 120
+ 7.4.124 maildir_header_cache_verify 120
+ 7.4.125 maildir_trash 121
+ 7.4.126 mark_old 121
+ 7.4.127 markers 121
+ 7.4.128 mask 121
+ 7.4.129 max_display_recips 122
+ 7.4.130 max_line_length 122
+ 7.4.131 mbox 122
+ 7.4.132 mbox_type 122
+ 7.4.133 menu_context 122
+ 7.4.134 menu_move_off 123
+ 7.4.135 menu_scroll 123
+ 7.4.136 message_format 123
+ 7.4.137 meta_key 123
+ 7.4.138 metoo 123
+ 7.4.139 mh_purge 124
+ 7.4.140 mh_seq_flagged 124
+ 7.4.141 mh_seq_replied 124
+ 7.4.142 mh_seq_unseen 124
+ 7.4.143 mime_forward 124
+ 7.4.144 mime_forward_decode 124
+ 7.4.145 mime_forward_rest 125
+ 7.4.146 mix_entry_format 125
+ 7.4.147 mixmaster 125
+ 7.4.148 move 125
+ 7.4.149 msgid_format 126
+ 7.4.150 muttng_bindir 127
+ 7.4.151 muttng_docdir 127
+ 7.4.152 muttng_folder_name 127
+ 7.4.153 muttng_folder_path 127
+ 7.4.154 muttng_hcache_backend 127
+ 7.4.155 muttng_pwd 128
+ 7.4.156 muttng_revision 128
+ 7.4.157 muttng_sysconfdir 128
+ 7.4.158 muttng_version 128
vi
- 7.4.160 nntp_load_description 128
- 7.4.161 nntp_mail_check 129
- 7.4.162 nntp_mime_subject 129
- 7.4.163 nntp_newsrc 129
- 7.4.164 nntp_pass 129
- 7.4.165 nntp_post_moderated 130
- 7.4.166 nntp_reconnect 130
- 7.4.167 nntp_save_unsubscribed 130
- 7.4.168 nntp_show_new_news 130
- 7.4.169 nntp_show_only_unread 131
- 7.4.170 nntp_user 131
- 7.4.171 nntp_x_comment_to 131
- 7.4.172 operating_system 131
- 7.4.173 pager 131
- 7.4.174 pager_context 132
- 7.4.175 pager_format 132
- 7.4.176 pager_index_lines 132
- 7.4.177 pager_stop 132
- 7.4.178 pgp_auto_decode 133
- 7.4.179 pgp_autoinline 133
- 7.4.180 pgp_check_exit 133
- 7.4.181 pgp_clearsign_command 133
- 7.4.182 pgp_decode_command 134
- 7.4.183 pgp_decrypt_command 134
- 7.4.184 pgp_encrypt_only_command 134
- 7.4.185 pgp_encrypt_sign_command 134
- 7.4.186 pgp_entry_format 135
- 7.4.187 pgp_export_command 135
- 7.4.188 pgp_getkeys_command 135
- 7.4.189 pgp_good_sign 136
- 7.4.190 pgp_ignore_subkeys 136
- 7.4.191 pgp_import_command 136
- 7.4.192 pgp_list_pubring_command 136
- 7.4.193 pgp_list_secring_command 136
- 7.4.194 pgp_long_ids 137
- 7.4.195 pgp_mime_auto 137
- 7.4.196 pgp_replyinline 137
- 7.4.197 pgp_retainable_sigs 137
- 7.4.198 pgp_show_unusable 138
- 7.4.199 pgp_sign_as 138
- 7.4.200 pgp_sign_command 138
- 7.4.201 pgp_sort_keys 138
- 7.4.202 pgp_strict_enc 139
- 7.4.203 pgp_timeout 139
- 7.4.204 pgp_use_gpg_agent 139
- 7.4.205 pgp_verify_command 139
- 7.4.206 pgp_verify_key_command 139
- 7.4.207 pipe_decode 139
- 7.4.208 pipe_sep 140
- 7.4.209 pipe_split 140
- 7.4.210 pop_auth_try_all 140
- 7.4.211 pop_authenticators 140
- 7.4.212 pop_delete 141
+ 7.4.159 narrow_tree 128
+ 7.4.160 nntp_ask_followup_to 128
+ 7.4.161 nntp_ask_x_comment_to 129
+ 7.4.162 nntp_cache_dir 129
+ 7.4.163 nntp_catchup 129
+ 7.4.164 nntp_context 129
+ 7.4.165 nntp_followup_to_poster 129
+ 7.4.166 nntp_group_index_format 130
+ 7.4.167 nntp_host 130
+ 7.4.168 nntp_inews 131
+ 7.4.169 nntp_load_description 131
+ 7.4.170 nntp_mail_check 131
+ 7.4.171 nntp_mime_subject 131
+ 7.4.172 nntp_newsrc 132
+ 7.4.173 nntp_pass 132
+ 7.4.174 nntp_post_moderated 132
+ 7.4.175 nntp_reconnect 132
+ 7.4.176 nntp_save_unsubscribed 133
+ 7.4.177 nntp_show_new_news 133
+ 7.4.178 nntp_show_only_unread 133
+ 7.4.179 nntp_user 133
+ 7.4.180 nntp_x_comment_to 133
+ 7.4.181 operating_system 134
+ 7.4.182 pager 134
+ 7.4.183 pager_context 134
+ 7.4.184 pager_format 134
+ 7.4.185 pager_index_lines 135
+ 7.4.186 pager_stop 135
+ 7.4.187 pgp_auto_decode 135
+ 7.4.188 pgp_autoinline 135
+ 7.4.189 pgp_check_exit 136
+ 7.4.190 pgp_clearsign_command 136
+ 7.4.191 pgp_decode_command 136
+ 7.4.192 pgp_decrypt_command 137
+ 7.4.193 pgp_encrypt_only_command 137
+ 7.4.194 pgp_encrypt_sign_command 137
+ 7.4.195 pgp_entry_format 137
+ 7.4.196 pgp_export_command 138
+ 7.4.197 pgp_getkeys_command 138
+ 7.4.198 pgp_good_sign 138
+ 7.4.199 pgp_ignore_subkeys 138
+ 7.4.200 pgp_import_command 138
+ 7.4.201 pgp_list_pubring_command 139
+ 7.4.202 pgp_list_secring_command 139
+ 7.4.203 pgp_long_ids 139
+ 7.4.204 pgp_mime_auto 139
+ 7.4.205 pgp_replyinline 139
+ 7.4.206 pgp_retainable_sigs 140
+ 7.4.207 pgp_show_unusable 140
+ 7.4.208 pgp_sign_as 140
+ 7.4.209 pgp_sign_command 140
+ 7.4.210 pgp_sort_keys 141
+ 7.4.211 pgp_strict_enc 141
vii
- 7.4.213 pop_host 141
- 7.4.214 pop_last 141
- 7.4.215 pop_mail_check 141
- 7.4.216 pop_pass 142
- 7.4.217 pop_reconnect 142
- 7.4.218 pop_user 142
- 7.4.219 post_indent_string 142
- 7.4.220 postpone 142
- 7.4.221 postponed 143
- 7.4.222 preconnect 143
- 7.4.223 print 143
- 7.4.224 print_command 143
- 7.4.225 print_decode 143
- 7.4.226 print_split 144
- 7.4.227 prompt_after 144
- 7.4.228 query_command 144
- 7.4.229 quit 144
- 7.4.230 quote_empty 145
- 7.4.231 quote_quoted 145
- 7.4.232 quote_regexp 145
- 7.4.233 read_inc 145
- 7.4.234 read_only 145
- 7.4.235 realname 146
- 7.4.236 recall 146
- 7.4.237 record 146
- 7.4.238 reply_regexp 146
- 7.4.239 reply_self 147
- 7.4.240 reply_to 147
- 7.4.241 resolve 147
- 7.4.242 reverse_alias 147
- 7.4.243 reverse_name 148
- 7.4.244 reverse_realname 148
- 7.4.245 rfc2047_parameters 148
- 7.4.246 save_address 148
- 7.4.247 save_empty 149
- 7.4.248 save_name 149
- 7.4.249 score 149
- 7.4.250 score_threshold_delete 149
- 7.4.251 score_threshold_flag 150
- 7.4.252 score_threshold_read 150
- 7.4.253 send_charset 150
- 7.4.254 sendmail 150
- 7.4.255 sendmail_wait 150
- 7.4.256 shell 151
- 7.4.257 sidebar_boundary 151
- 7.4.258 sidebar_delim 151
- 7.4.259 sidebar_newmail_only 151
- 7.4.260 sidebar_number_format 151
- 7.4.261 sidebar_shorten_hierarchy 152
- 7.4.262 sidebar_visible 152
- 7.4.263 sidebar_width 153
- 7.4.264 sig_dashes 153
- 7.4.265 sig_on_top 153
+ 7.4.212 pgp_timeout 141
+ 7.4.213 pgp_use_gpg_agent 141
+ 7.4.214 pgp_verify_command 142
+ 7.4.215 pgp_verify_key_command 142
+ 7.4.216 pipe_decode 142
+ 7.4.217 pipe_sep 142
+ 7.4.218 pipe_split 142
+ 7.4.219 pop_auth_try_all 142
+ 7.4.220 pop_authenticators 143
+ 7.4.221 pop_delete 143
+ 7.4.222 pop_host 143
+ 7.4.223 pop_last 144
+ 7.4.224 pop_mail_check 144
+ 7.4.225 pop_pass 144
+ 7.4.226 pop_reconnect 144
+ 7.4.227 pop_user 144
+ 7.4.228 post_indent_string 145
+ 7.4.229 postpone 145
+ 7.4.230 postponed 145
+ 7.4.231 preconnect 145
+ 7.4.232 print 146
+ 7.4.233 print_command 146
+ 7.4.234 print_decode 146
+ 7.4.235 print_split 146
+ 7.4.236 prompt_after 146
+ 7.4.237 query_command 147
+ 7.4.238 quit 147
+ 7.4.239 quote_empty 147
+ 7.4.240 quote_quoted 147
+ 7.4.241 quote_regexp 147
+ 7.4.242 read_inc 148
+ 7.4.243 read_only 148
+ 7.4.244 realname 148
+ 7.4.245 recall 148
+ 7.4.246 record 148
+ 7.4.247 reply_regexp 149
+ 7.4.248 reply_self 149
+ 7.4.249 reply_to 149
+ 7.4.250 resolve 149
+ 7.4.251 reverse_alias 150
+ 7.4.252 reverse_name 150
+ 7.4.253 reverse_realname 150
+ 7.4.254 rfc2047_parameters 150
+ 7.4.255 save_address 151
+ 7.4.256 save_empty 151
+ 7.4.257 save_name 151
+ 7.4.258 score 152
+ 7.4.259 score_threshold_delete 152
+ 7.4.260 score_threshold_flag 152
+ 7.4.261 score_threshold_read 152
+ 7.4.262 send_charset 152
+ 7.4.263 sendmail 153
+ 7.4.264 sendmail_wait 153
viii
- 7.4.266 signature 153
- 7.4.267 signoff_string 153
- 7.4.268 simple_search 154
- 7.4.269 sleep_time 154
- 7.4.270 smart_wrap 154
- 7.4.271 smileys 154
- 7.4.272 smime_ask_cert_label 154
- 7.4.273 smime_ca_location 155
- 7.4.274 smime_certificates 155
- 7.4.275 smime_decrypt_command 155
- 7.4.276 smime_decrypt_use_default_key 156
- 7.4.277 smime_default_key 156
- 7.4.278 smime_encrypt_command 156
- 7.4.279 smime_encrypt_with 156
- 7.4.280 smime_get_cert_command 157
- 7.4.281 smime_get_cert_email_command 157
- 7.4.282 smime_get_signer_cert_command 157
- 7.4.283 smime_import_cert_command 157
- 7.4.284 smime_is_default 157
- 7.4.285 smime_keys 157
- 7.4.286 smime_pk7out_command 158
- 7.4.287 smime_sign_command 158
- 7.4.288 smime_sign_opaque_command 158
- 7.4.289 smime_timeout 158
- 7.4.290 smime_verify_command 158
- 7.4.291 smime_verify_opaque_command 159
- 7.4.292 smtp_envelope 159
- 7.4.293 smtp_host 159
- 7.4.294 smtp_pass 159
- 7.4.295 smtp_port 160
- 7.4.296 smtp_use_tls 160
- 7.4.297 smtp_user 160
- 7.4.298 sort 160
- 7.4.299 sort_alias 161
- 7.4.300 sort_aux 161
- 7.4.301 sort_browser 162
- 7.4.302 sort_re 162
- 7.4.303 spam_separator 162
- 7.4.304 spoolfile 162
- 7.4.305 ssl_ca_certificates_file 163
- 7.4.306 ssl_client_cert 163
- 7.4.307 ssl_force_tls 163
- 7.4.308 ssl_min_dh_prime_bits 163
- 7.4.309 ssl_starttls 163
- 7.4.310 ssl_use_sslv2 164
- 7.4.311 ssl_use_sslv3 164
- 7.4.312 ssl_use_tlsv1 164
- 7.4.313 ssl_usesystemcerts 164
- 7.4.314 status_chars 164
- 7.4.315 status_format 165
- 7.4.316 status_on_top 167
- 7.4.317 strict_mailto 167
- 7.4.318 strict_mime 167
+ 7.4.265 shell 153
+ 7.4.266 sidebar_boundary 153
+ 7.4.267 sidebar_delim 154
+ 7.4.268 sidebar_newmail_only 154
+ 7.4.269 sidebar_number_format 154
+ 7.4.270 sidebar_shorten_hierarchy 155
+ 7.4.271 sidebar_visible 155
+ 7.4.272 sidebar_width 155
+ 7.4.273 sig_dashes 155
+ 7.4.274 sig_on_top 155
+ 7.4.275 signature 156
+ 7.4.276 signoff_string 156
+ 7.4.277 simple_search 156
+ 7.4.278 sleep_time 156
+ 7.4.279 smart_wrap 157
+ 7.4.280 smileys 157
+ 7.4.281 smime_ask_cert_label 157
+ 7.4.282 smime_ca_location 157
+ 7.4.283 smime_certificates 157
+ 7.4.284 smime_decrypt_command 158
+ 7.4.285 smime_decrypt_use_default_key 158
+ 7.4.286 smime_default_key 158
+ 7.4.287 smime_encrypt_command 159
+ 7.4.288 smime_encrypt_with 159
+ 7.4.289 smime_get_cert_command 159
+ 7.4.290 smime_get_cert_email_command 159
+ 7.4.291 smime_get_signer_cert_command 159
+ 7.4.292 smime_import_cert_command 160
+ 7.4.293 smime_is_default 160
+ 7.4.294 smime_keys 160
+ 7.4.295 smime_pk7out_command 160
+ 7.4.296 smime_sign_command 160
+ 7.4.297 smime_sign_opaque_command 161
+ 7.4.298 smime_timeout 161
+ 7.4.299 smime_verify_command 161
+ 7.4.300 smime_verify_opaque_command 161
+ 7.4.301 smtp_envelope 161
+ 7.4.302 smtp_host 161
+ 7.4.303 smtp_pass 162
+ 7.4.304 smtp_port 162
+ 7.4.305 smtp_use_tls 162
+ 7.4.306 smtp_user 163
+ 7.4.307 sort 163
+ 7.4.308 sort_alias 163
+ 7.4.309 sort_aux 163
+ 7.4.310 sort_browser 164
+ 7.4.311 sort_re 164
+ 7.4.312 spam_separator 165
+ 7.4.313 spoolfile 165
+ 7.4.314 ssl_ca_certificates_file 165
+ 7.4.315 ssl_client_cert 165
+ 7.4.316 ssl_force_tls 165
+ 7.4.317 ssl_min_dh_prime_bits 166
ix
- 7.4.319 strict_threads 168
- 7.4.320 strip_was 168
- 7.4.321 strip_was_regex 168
- 7.4.322 stuff_quoted 168
- 7.4.323 suspend 169
- 7.4.324 text_flowed 169
- 7.4.325 thorough_search 169
- 7.4.326 thread_received 169
- 7.4.327 tilde 169
- 7.4.328 timeout 170
- 7.4.329 tmpdir 170
- 7.4.330 to_chars 170
- 7.4.331 trash 170
- 7.4.332 tunnel 170
- 7.4.333 umask 171
- 7.4.334 uncollapse_jump 171
- 7.4.335 use_8bitmime 171
- 7.4.336 use_domain 171
- 7.4.337 use_from 171
- 7.4.338 use_idn 172
- 7.4.339 use_ipv6 172
- 7.4.340 visual 172
- 7.4.341 wait_key 172
- 7.4.342 weed 173
- 7.4.343 wrap_search 173
- 7.4.344 wrapmargin 173
- 7.4.345 write_bcc 173
- 7.4.346 write_inc 173
- 7.4.347 xterm_icon 173
- 7.4.348 xterm_leave 174
- 7.4.349 xterm_set_titles 174
- 7.4.350 xterm_title 174
- 7.5 Functions ....................................................... 174
- 7.5.1 generic 174
- 7.5.2 index 175
- 7.5.3 pager 177
- 7.5.4 alias 179
- 7.5.5 query 179
- 7.5.6 attach 179
- 7.5.7 compose 180
- 7.5.8 postpone 181
- 7.5.9 browser 181
- 7.5.10 pgp 182
- 7.5.11 editor 182
-
- 8. Miscellany ............................................................ 182
- 8.1 Acknowledgments ................................................. 183
- 8.2 About this document ............................................. 185
+ 7.4.318 ssl_starttls 166
+ 7.4.319 ssl_use_sslv2 166
+ 7.4.320 ssl_use_sslv3 166
+ 7.4.321 ssl_use_tlsv1 166
+ 7.4.322 ssl_usesystemcerts 167
+ 7.4.323 status_chars 167
+ 7.4.324 status_format 167
+ 7.4.325 status_on_top 169
+ 7.4.326 strict_mailto 170
+ 7.4.327 strict_mime 170
+ 7.4.328 strict_threads 170
+ 7.4.329 strip_was 170
+ 7.4.330 strip_was_regex 171
+ 7.4.331 stuff_quoted 171
+ 7.4.332 suspend 171
+ 7.4.333 text_flowed 171
+ 7.4.334 thorough_search 171
+ 7.4.335 thread_received 172
+ 7.4.336 tilde 172
+ 7.4.337 timeout 172
+ 7.4.338 tmpdir 172
+ 7.4.339 to_chars 172
+ 7.4.340 trash 173
+ 7.4.341 tunnel 173
+ 7.4.342 umask 173
+ 7.4.343 uncollapse_jump 173
+ 7.4.344 use_8bitmime 173
+ 7.4.345 use_domain 174
+ 7.4.346 use_from 174
+ 7.4.347 use_idn 174
+ 7.4.348 use_ipv6 174
+ 7.4.349 visual 174
+ 7.4.350 wait_key 175
+ 7.4.351 weed 175
+ 7.4.352 wrap_search 175
+ 7.4.353 wrapmargin 175
+ 7.4.354 write_bcc 175
+ 7.4.355 write_inc 176
+ 7.4.356 xterm_icon 176
+ 7.4.357 xterm_leave 176
+ 7.4.358 xterm_set_titles 176
+ 7.4.359 xterm_title 176
+ 7.5 Functions ....................................................... 177
+ 7.5.1 generic 177
+ 7.5.2 index 178
+ 7.5.3 pager 180
+ 7.5.4 alias 182
+ 7.5.5 query 182
+ 7.5.6 attach 182
+ 7.5.7 compose 183
+ 7.5.8 postpone 184
+ 7.5.9 browser 184
+ 7.5.10 pgp 185
x
+ 7.5.11 editor 185
+
+ 8. Miscellany ............................................................ 185
+ 8.1 Acknowledgments ................................................. 186
+ 8.2 About this document ............................................. 188
+
+ xi
+
projects / apps / madmutt.git / blobdiff