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
+ version devel-r446
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.4 , page 24) com-
+ You can remap the _\be_\bd_\bi_\bt_\bo_\br functions using the _\bb_\bi_\bn_\bd (section 3.5 , page 25) 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.327 , page 167) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 , page 168) 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.8 , page 28) objects to specify a color or mono attribute for them.
+ (section 3.9 , page 29) 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 76) script for high-
+ also be used by an external _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 77) 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.295 , page 157) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
+ When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.296 , page 158) 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.113 , page 113). 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.113 , page 113) to optionally display the number of
+ tion 7.4.114 , page 114). For example, you could use "%?M?(#%03M)&(%4l)?" in
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114) to optionally display the number of
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.316 , page 165).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 7.4.317 , page 166).
_\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.3 , page 23) command is added to
- the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.4 , page 87) 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.4 , page 87) does not
- add the aliases specified there-in, you must also _\bs_\bo_\bu_\br_\bc_\be (section 3.28 , page
- 43) the file.
+ Once editing is complete, an _\ba_\bl_\bi_\ba_\bs (section 3.4 , page 24) command is added to
+ the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 88) variable for
+ future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 88) does not
+ add the aliases specified there-in, you must also _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page
+ 44) 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.9 , page 30) commands.
+ 3.10 , page 31) 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 68), 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 69), 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 69). There, it's used to fine-tune the properties of attachments you are
+ page 70). 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.7 , page 27) to change settings on the fly.
+ junction with _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 28) to change settings on the fly.
e\bex\bxt\btr\bra\bac\bct\bt-\b-k\bke\bey\bys\bs
(default: ^K)
(default: L)
Reply to the current or tagged message(s) by extracting any addresses which
- match the regular expressions given by the _\bl_\bi_\bs_\bt_\bs _\bo_\br _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 ,
- page 33) 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.91 , page 108) configuration variable is set.
+ match the regular expressions given by the _\bl_\bi_\bs_\bt_\bs _\bo_\br _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 ,
+ page 34) commands, but also honor any Mail-Followup-To header(s) if the
+ _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.92 , page 109) configuration variable is set.
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.204 , page 136), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
- (section 7.4.206 , page 137), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.205 , page 137) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 169) control the exact behavior of this
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.205 , page 138), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 7.4.207 , page 138), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.206 , page 138) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 170) control the exact behavior of this
function.
r\bre\bes\bse\ben\bnd\bd-\b-m\bme\bes\bss\bsa\bag\bge\be
message. This function is best described as "recall from arbitrary folders".
It can conveniently be used to forward MIME messages while preserving the orig-
inal mail structure. Note that the amount of headers included here depends on
- the value of the _\b$_\bw_\be_\be_\bd (section 7.4.340 , page 170) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 7.4.340 , page 171) variable.
This function is also available from the attachment menu. You can use this to
easily resend a message which was included with a bounce message as a mes-
(default: !)
Asks for an external Unix command and executes it. The _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section
- 7.4.339 , page 169) can be used to control whether Mutt-ng will wait for a key
+ 7.4.339 , page 170) 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.229 , page 142) variable to
+ The _\bp_\ba_\bg_\be_\br uses the _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 143) 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.312 , page 162) will change to a
+ folder. The %r in _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163) 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.57 , page 100).
+ Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101).
_\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.196 , page 135) permanently.
+ _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.197 , page 136) 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.183 , page 132)) have obvious meanings. But some explana-
+ _\bm_\ba_\bt (section 7.4.184 , page 133)) 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:
leave the menu, or accept them pressing (by default) the Return key.
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.143 ,
- page 121)). Most important is the ``middleman'' capability, indicated by a
+ %c entry of the remailer menu lines (see _\b$_\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.144 ,
+ page 122)). Most important is the ``middleman'' capability, indicated by a
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.218 , page 140) variable. This means that you can
+ the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.219 , page 141) 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.217 , page 139) quad-option.
+ See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 141) 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 80) option is specified. This
+ the ``-n'' _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bl_\bi_\bn_\be (section 7.1 , page 81) 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 83) to configure Mutt-ng.
+ your _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs (section 7.3 , page 84) to configure Mutt-ng.
- _\b3_\b._\b2 _\bS_\by_\bn_\bt_\ba_\bx _\bo_\bf _\bI_\bn_\bi_\bt_\bi_\ba_\bl_\bi_\bz_\ba_\bt_\bi_\bo_\bn _\bF_\bi_\bl_\be_\bs
+ _\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
- 83). Each line of the file may contain one or more commands. When multiple
+ 84). 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-
which includes line3 and line4. line5 is a new line of its own and thus is
interpreted again.
- It is also possible to substitute the output of a Unix command in an initial-
- ization file. This is accomplished by enclosing the command in backquotes
- (``). For example,
+ The commands understood by mutt are explained in the next paragraphs. For a
+ complete list, see the _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.3 , page 84).
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_\b._\b1 _\bC_\bo_\bm_\bm_\ba_\bn_\bd_\bs_\b' _\bO_\bu_\bt_\bp_\bu_\bt
+
+ It is possible to substitute the output of a Unix command in an initialization
+ file. This is accomplished by enclosing the command in backquotes (``) as in,
+ for example:
+
my_hdr X-Operating-System: `uname -a`
The output of the Unix command ``uname -a'' will be substituted before the line
- is parsed. Note that since initialization files are line oriented, only the
+ is parsed. Note that since initialization files are line oriented, only the
first line of output from the Unix command will be substituted.
+ _\b3_\b._\b3_\b._\b2 _\bE_\bn_\bv_\bi_\br_\bo_\bn_\bm_\be_\bn_\bt _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+
UNIX environments can be accessed like the way it is done in shells like sh and
- bash: Prepend the name of the environment by a ``$''. For example,
+ bash: Prepend the name of the environment by a ``$'' sign. For example,
set record=+sent_on_$HOSTNAME
- This also applies for all configuration variables known to mutt-ng, for example
+ sets the _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144) variable to the string _\b+_\bs_\be_\bn_\bt_\b__\bo_\bn_\b_
+ 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
+ result will of the expansion will then be empty.
+
+ _\b3_\b._\b3_\b._\b3 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+
+ As for environment variables, the values of all configuration variables as
+ string can be used in the same way, too. For example,
set imap_home_namespace = $folder
- 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 83).
+ would set the value of _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.99 , page 110) to the
+ value to which _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) is _\bc_\bu_\br_\br_\be_\bn_\bt_\bl_\by set to.
+
+ N\bNo\bot\bte\be:\b: There're no logical links established in such cases so that the the value
+ for _\b$_\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be (section 7.4.99 , page 110) won't change even if
+ _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) gets changed.
+
+ 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.
+
+ _\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
- _\b3_\b._\b3 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg_\b/_\bU_\bs_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs
+ 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 example, to view the manual, users can either define three macros like the
+ following
+
+ macro generic <F1> "!less -r /path/to/manual" "Show manual"
+ macro pager <F1> "!less -r /path/to/manual" "Show manual"
+ macro index <F1> "!less -r /path/to/manual" "Show manual"
+
+ for generic, pager and index. The alternative is to define a custom variable
+ like so:
+
+ 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"
+
+ Using this feature, arbitrary sequences can be defined once and recalled and
+ reused where necessary. More advanced scenarios could include to save a vari-
+ able's value at the beginning of macro sequence and restore it at end.
+
+ _\b3_\b._\b3_\b._\b5 _\bT_\by_\bp_\be _\bC_\bo_\bn_\bv_\be_\br_\bs_\bi_\bo_\bn_\bs
+
+ A note about variable's types during conversion: internally values are stored
+ in internal types but for any dump/query or set operation they're converted to
+ and from string. That means that there's no need to worry about types when ref-
+ erencing any variable. As an example, the following can be used without harm
+ (besides makeing muttng very likely behave strange):
+
+ set read_inc = 100
+ set folder = $read_inc
+ set $read_inc = $folder
+ set user_magic_number = 42
+ set folder = $user_magic_number
+
+ _\b3_\b._\b4 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg_\b/_\bU_\bs_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs
Usage: alias _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
N\bNo\bot\bte\be:\b: if you want to create an alias for a group (by specifying more than one
address), you m\bmu\bus\bst\bt separate the addresses with a comma (``,'').
+ The Mutt Next Generation E-Mail Client 25
+
To remove an alias or aliases (``*'' means all aliases):
unalias [ * | _\bk_\be_\by _\b._\b._\b. ]
Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
cial file. The alias command can appear anywhere in a configuration file, as
- long as this file is _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.28 , page 43). Consequently, you can
+ long as this file is _\bs_\bo_\bu_\br_\bc_\be_\bd (section 3.29 , page 44). Consequently, you can
have multiple alias files, or you can have all aliases defined in your muttrc.
On the other hand, the _\bc_\br_\be_\ba_\bt_\be_\b-_\ba_\bl_\bi_\ba_\bs (section 2.5.4 , page 11) function can use
- only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.4 , page 87)
+ only one file, the one pointed to by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 7.4.5 , page 88)
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.28 , page 43) this file too.
-
- The Mutt Next Generation E-Mail Client 24
+ 3.29 , page 44) 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.57 , page 100) variable set.
+ (section 7.4.58 , page 101) 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
_\be_\bn_\bt_\br_\by key (default: RET), and use the _\be_\bx_\bi_\bt key (default: q) to return to the
address prompt.
- _\b3_\b._\b4 _\bC_\bh_\ba_\bn_\bg_\bi_\bn_\bg _\bt_\bh_\be _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs
+ _\b3_\b._\b5 _\bC_\bh_\ba_\bn_\bg_\bi_\bn_\bg _\bt_\bh_\be _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs
Usage: bind _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
This command allows you to change the default key bindings (operation invoked
when pressing a key).
- _\bm_\ba_\bp specifies in which menu the binding belongs. Multiple maps may be speci-
- fied by separating them with commas (no additional whitespace is allowed). The
- currently defined maps are:
+ _\bm_\ba_\bp specifies in which menu the binding belongs. Multiple maps may be
+
+ The Mutt Next Generation E-Mail Client 26
+
+ specified by separating them with commas (no additional whitespace is allowed).
+ The currently defined maps are:
generic
This is not a real menu, but is used as a fallback for all of the
The attachment menu is used to access the attachments on received
messages.
- The Mutt Next Generation E-Mail Client 25
-
browser
The browser is used for both browsing the local directory struc-
ture, and for listing all of your incoming mailboxes.
alternative form is to specify the key as a three digit octal number prefixed
with a ``\'' (for example _\b\_\b1_\b7_\b7 is equivalent to _\b\_\bc_\b?).
- In addition, _\bk_\be_\by may consist of:
+ The Mutt Next Generation E-Mail Client 27
- The Mutt Next Generation E-Mail Client 26
+ In addition, _\bk_\be_\by may consist of:
\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 171). The special
+ list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 172). The special
function noop unbinds the specified key sequence.
- _\b3_\b._\b5 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs _\bf_\bo_\br _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bs_\be_\bt_\bs
+ _\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
Usage: charset-hook _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
This is helpful when your systems character conversion library insists on using
strange, system-specific names for character sets.
- _\b3_\b._\b6 _\bS_\be_\bt_\bt_\bi_\bn_\bg _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs _\bb_\ba_\bs_\be_\bd _\bu_\bp_\bo_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ _\b3_\b._\b7 _\bS_\be_\bt_\bt_\bi_\bn_\bg _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs _\bb_\ba_\bs_\be_\bd _\bu_\bp_\bo_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- Usage: folder-hook [!]_\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
-
- It is often desirable to change settings based on which mailbox you are
+ The Mutt Next Generation E-Mail Client 28
- The Mutt Next Generation E-Mail Client 27
+ Usage: folder-hook [!]_\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- 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
+ It is often desirable to change settings based on which mailbox you are read-
+ ing. The folder-hook command provides a method by which you can execute any
+ configuration command. _\br_\be_\bg_\be_\bx_\bp is a regular expression specifying in which
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.301 , page
- 159) 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.302 , page
+ 160) 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.
folder-hook . set sort=date-sent
- _\b3_\b._\b7 _\bK_\be_\by_\bb_\bo_\ba_\br_\bd _\bm_\ba_\bc_\br_\bo_\bs
+ _\b3_\b._\b8 _\bK_\be_\by_\bb_\bo_\ba_\br_\bd _\bm_\ba_\bc_\br_\bo_\bs
Usage: macro _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
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.4 , page 24) which the macro will be bound. Multi-
+ _\bm_\be_\bn_\bu is the _\bm_\ba_\bp (section 3.5 , page 26) 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.4 , page 24). There are some additions however. The first is that control
+ 3.5 , page 25). 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.4 , page 24). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
- 7.5 , page 171).
+ 3.5 , page 25). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
+ 7.5 , page 172).
The advantage with using function names directly is that the macros will work
+
+ The Mutt Next Generation E-Mail Client 29
+
regardless of the current key bindings, so they are not dependent on the user
having particular key definitions. This makes them more robust and portable,
and also facilitates defining of macros in files used by more than one user
-
- The Mutt Next Generation E-Mail Client 28
-
(eg. the system Muttngrc).
Optionally you can specify a descriptive text after _\bs_\be_\bq_\bu_\be_\bn_\bc_\be, which is shown in
N\bNo\bot\bte\be:\b: Macro definitions (if any) listed in the help screen(s), are silently
truncated at the screen width, and are not wrapped.
- _\b3_\b._\b8 _\bU_\bs_\bi_\bn_\bg _\bc_\bo_\bl_\bo_\br _\ba_\bn_\bd _\bm_\bo_\bn_\bo _\bv_\bi_\bd_\be_\bo _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be_\bs
+ _\b3_\b._\b9 _\bU_\bs_\bi_\bn_\bg _\bc_\bo_\bl_\bo_\br _\ba_\bn_\bd _\bm_\bo_\bn_\bo _\bv_\bi_\bd_\be_\bo _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be_\bs
Usage: color _\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 normal
- +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.229 , page 142) in the
+ +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 143) in the
body of a message)
+ The Mutt Next Generation E-Mail Client 30
+
+\bo quoted1, quoted2, ..., quotedN\bN (higher levels of quoting)
+\bo search (highlighting of words in the pager)
- The Mutt Next Generation E-Mail Client 29
-
+\bo signature
+\bo status (mode lines used to display info about the mailbox or message)
instead of _\bw_\bh_\bi_\bt_\be and _\by_\be_\bl_\bl_\bo_\bw when setting this variable.
N\bNo\bot\bte\be:\b: The uncolor command can be applied to the index object only. It removes
+
+ The Mutt Next Generation E-Mail Client 31
+
entries from the list. You m\bmu\bus\bst\bt specify the same pattern specified in the color
command for it to be removed. The pattern ``*'' is a special token which means
to clear the color index list of all entries.
- The Mutt Next Generation E-Mail Client 30
-
Mutt-ng also recognizes the keywords _\bc_\bo_\bl_\bo_\br_\b0, _\bc_\bo_\bl_\bo_\br_\b1, ..., _\bc_\bo_\bl_\bo_\brN\bN-\b-1\b1 (N\bN being the
number of colors supported by your terminal). This is useful when you remap
the colors for your display (for example by changing the color associated with
+\bo standout
- _\b3_\b._\b9 _\bI_\bg_\bn_\bo_\br_\bi_\bn_\bg _\b(_\bw_\be_\be_\bd_\bi_\bn_\bg_\b) _\bu_\bn_\bw_\ba_\bn_\bt_\be_\bd _\bm_\be_\bs_\bs_\ba_\bg_\be _\bh_\be_\ba_\bd_\be_\br_\bs
+ _\b3_\b._\b1_\b0 _\bI_\bg_\bn_\bo_\br_\bi_\bn_\bg _\b(_\bw_\be_\be_\bd_\bi_\bn_\bg_\b) _\bu_\bn_\bw_\ba_\bn_\bt_\be_\bd _\bm_\be_\bs_\bs_\ba_\bg_\be _\bh_\be_\ba_\bd_\be_\br_\bs
Usage: [un]ignore _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
For example:
+ The Mutt Next Generation E-Mail Client 32
+
# Sven's draconian header weeding
ignore *
unignore from date subject to cc
unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
unignore posted-to:
- The Mutt Next Generation E-Mail Client 31
-
- _\b3_\b._\b1_\b0 _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be _\ba_\bd_\bd_\br_\be_\bs_\bs_\be_\bs
+ _\b3_\b._\b1_\b1 _\bA_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be _\ba_\bd_\bd_\br_\be_\bs_\bs_\be_\bs
Usage: [un]alternates _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
instance, when replying to a message that you sent to a different party, mutt
will automatically suggest to send the response to the original message's
recipients -- responding to yourself won't make much sense in many cases. (See
- _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.237 , page 144).)
+ _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.238 , page 145).)
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
be removed. If the _\br_\be_\bg_\be_\bx_\bp for unalternates is ``*'', _\ba_\bl_\bl _\be_\bn_\bt_\br_\bi_\be_\bs on alternates
will be removed.
- _\b3_\b._\b1_\b1 _\bF_\bo_\br_\bm_\ba_\bt _\b= _\bF_\bl_\bo_\bw_\be_\bd
+ _\b3_\b._\b1_\b2 _\bF_\bo_\br_\bm_\ba_\bt _\b= _\bF_\bl_\bo_\bw_\be_\bd
- _\b3_\b._\b1_\b1_\b._\b1 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn
+ _\b3_\b._\b1_\b2_\b._\b1 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn
Mutt-ng contains support for so-called format=flowed messages. In the begin-
ning of email, each message had a fixed line width, and it was enough for dis-
fixed-size terminals.
For introductory information on format=flowed messages, see
+
+ The Mutt Next Generation E-Mail Client 33
+
<http://www.joeclark.org/ffaq.html>.
- _\b3_\b._\b1_\b1_\b._\b2 _\bR_\be_\bc_\be_\bi_\bv_\bi_\bn_\bg_\b: _\bD_\bi_\bs_\bp_\bl_\ba_\by _\bS_\be_\bt_\bu_\bp
+ _\b3_\b._\b1_\b2_\b._\b2 _\bR_\be_\bc_\be_\bi_\bv_\bi_\bn_\bg_\b: _\bD_\bi_\bs_\bp_\bl_\ba_\by _\bS_\be_\bt_\bu_\bp
When you receive emails that are marked as format=flowed messages, and is for-
matted correctly, mutt-ng will try to reformat the message to optimally fit on
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 32
-
set wrapmargin = 10
The code above makes the line break 10 columns before the right side of the
> production server that we want to set up before our customer's
> project will go live.
- _\b3_\b._\b1_\b1_\b._\b3 _\bS_\be_\bn_\bd_\bi_\bn_\bg
+ The Mutt Next Generation E-Mail Client 34
+
+ _\b3_\b._\b1_\b2_\b._\b3 _\bS_\be_\bn_\bd_\bi_\bn_\bg
If you want mutt-ng to send emails with format=flowed set, you need to explic-
itly set it:
set text_flowed
- The Mutt Next Generation E-Mail Client 33
-
Additionally, you have to use an editor which supports writing format=flowed-
conforming emails. For vim, this is done by adding w to the formatoptions (see
:h formatoptions and :h fo-table) when writing emails.
Please make sure that you manually prepend a space to each of them.
- _\b3_\b._\b1_\b1_\b._\b4 _\bA_\bd_\bd_\bi_\bt_\bi_\bo_\bn_\ba_\bl _\bN_\bo_\bt_\be_\bs
+ _\b3_\b._\b1_\b2_\b._\b4 _\bA_\bd_\bd_\bi_\bt_\bi_\bo_\bn_\ba_\bl _\bN_\bo_\bt_\be_\bs
"
- For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.49 , page 98) variable pro-
+ For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.50 , page 99) 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.
able and is intended for languages rarely using spaces. So please use this set-
ting only if you're sure what you're doing.
- _\b3_\b._\b1_\b2 _\bM_\ba_\bi_\bl_\bi_\bn_\bg _\bl_\bi_\bs_\bt_\bs
+ _\b3_\b._\b1_\b3 _\bM_\ba_\bi_\bl_\bi_\bn_\bg _\bl_\bi_\bs_\bt_\bs
Usage: [un]lists _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
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 58). In order to take advantage of them, you must specify which addresses
+ page 59). In order to take advantage of them, you must specify which addresses
+
+ The Mutt Next Generation E-Mail Client 35
+
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.69 , page 103)
+ lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.70 , page 104)
configuration variable.
- The Mutt Next Generation E-Mail Client 34
-
More precisely, Mutt-ng maintains lists of patterns for the addresses of known
and subscribed mailing lists. Every subscribed mailing list is known. To mark
a mailing list as known, use the ``lists'' command. To mark it as subscribed,
To remove a mailing list from the list of subscribed mailing lists, but keep it
on the list of known mailing lists, use ``unsubscribe''.
- _\b3_\b._\b1_\b3 _\bU_\bs_\bi_\bn_\bg _\bM_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bs_\bp_\bo_\bo_\bl _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs
+ _\b3_\b._\b1_\b4 _\bU_\bs_\bi_\bn_\bg _\bM_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bs_\bp_\bo_\bo_\bl _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs
Usage: mbox-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
Unlike some of the other _\bh_\bo_\bo_\bk commands, only the _\bf_\bi_\br_\bs_\bt matching pattern is used
(it is not possible to save read mail in more than a single mailbox).
- _\b3_\b._\b1_\b4 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs _\bw_\bh_\bi_\bc_\bh _\br_\be_\bc_\be_\bi_\bv_\be _\bm_\ba_\bi_\bl
+ The Mutt Next Generation E-Mail Client 36
+
+ _\b3_\b._\b1_\b5 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs _\bw_\bh_\bi_\bc_\bh _\br_\be_\bc_\be_\bi_\bv_\be _\bm_\ba_\bi_\bl
Usage: [un]mailboxes [!]_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
Pressing TAB in the directory browser will bring up a menu showing the files
specified by the mailboxes command, and indicate which contain new messages.
-
- The Mutt Next Generation E-Mail Client 35
-
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
- 58) (such as ``='' and ``!''), any variable definition that affect these char-
- acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.67 , page 102) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 7.4.301 , page 159)) should be executed before the mailboxes command.
+ 59) (such as ``='' and ``!''), any variable definition that affect these char-
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 7.4.302 , page 160)) should be executed before the mailboxes command.
- _\b3_\b._\b1_\b5 _\bU_\bs_\be_\br _\bd_\be_\bf_\bi_\bn_\be_\bd _\bh_\be_\ba_\bd_\be_\br_\bs
+ _\b3_\b._\b1_\b6 _\bU_\bs_\be_\br _\bd_\be_\bf_\bi_\bn_\be_\bd _\bh_\be_\ba_\bd_\be_\br_\bs
Usage:
N\bNo\bot\bte\be:\b: space characters are _\bn_\bo_\bt allowed between the keyword and the colon
(``:''). The standard for electronic mail (RFC822) says that space is illegal
+
+ The Mutt Next Generation E-Mail Client 37
+
there, so Mutt-ng enforces the rule.
If you would like to add a header field to a single message, you should either
- set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.57 , page 100) variable, or use the _\be_\bd_\bi_\bt_\b-
+ set the _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101) 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 36
-
unmy_hdr to cc
- _\b3_\b._\b1_\b6 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\bt_\bh_\be _\bo_\br_\bd_\be_\br _\bo_\bf _\bh_\be_\ba_\bd_\be_\br_\bs _\bw_\bh_\be_\bn _\bv_\bi_\be_\bw_\bi_\bn_\bg _\bm_\be_\bs_\bs_\ba_\bg_\be_\bs
+ _\b3_\b._\b1_\b7 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\bt_\bh_\be _\bo_\br_\bd_\be_\br _\bo_\bf _\bh_\be_\ba_\bd_\be_\br_\bs _\bw_\bh_\be_\bn _\bv_\bi_\be_\bw_\bi_\bn_\bg _\bm_\be_\bs_\bs_\ba_\bg_\be_\bs
Usage: hdr_order _\bh_\be_\ba_\bd_\be_\br_\b1 _\bh_\be_\ba_\bd_\be_\br_\b2 _\bh_\be_\ba_\bd_\be_\br_\b3
hdr_order From Date: From: To: Cc: Subject:
- _\b3_\b._\b1_\b7 _\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
+ _\b3_\b._\b1_\b8 _\bS_\bp_\be_\bc_\bi_\bf_\by _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
Usage: save-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
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 55) 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 56) 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.19 , page 37) command.
+ Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 38) command.
+
+ The Mutt Next Generation E-Mail Client 38
- _\b3_\b._\b1_\b8 _\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
+ _\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.234 , page 143). Mutt-ng searches the initial list of message
+ (section 7.4.235 , page 144). 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.234 , page 143) mailbox.
+ 7.4.235 , page 144) mailbox.
- The Mutt Next Generation E-Mail Client 37
-
- 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 55) 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 56) 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.19 ,
- page 37) command.
+ `+spammers' mailbox by default. Also see the _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 ,
+ page 38) command.
- _\b3_\b._\b1_\b9 _\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
+ _\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.18 , page 36) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 36) with its arguments.
+ 3.19 , page 38) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 37) with its arguments.
- _\b3_\b._\b2_\b0 _\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
+ _\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
Usage: reply-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
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.251 , page 147) variable depending on the message's
+ _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page 148) variable depending on the message's
sender address.
+ The Mutt Next Generation E-Mail Client 39
+
For each type of send-hook or reply-hook, when multiple matches occur, commands
are executed in the order they are specified in the muttrc (for that type of
hook).
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 55) 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 56) 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 38
-
- _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.17 , page 91), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.263 , page
- 150) and _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.117 , page 116) variables in order to change the
- language of the attributions and signatures based upon the recipients.
+ Another typical use for this command is to change the values of the _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\b-
+ _\bt_\bi_\bo_\bn (section 7.4.18 , page 92), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.264 , page 151) and
+ _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.118 , page 117) variables in order to change the language
+ of the attributions and signatures based upon the recipients.
N\bNo\bot\bte\be:\b: the send-hook's are only executed ONCE after getting the initial list of
recipients. Adding a recipient after replying or editing the message will NOT
ify recipient headers, or the message's subject, don't have any effect on the
current message when executed from a send-hook.
- _\b3_\b._\b2_\b1 _\bC_\bh_\ba_\bn_\bg_\be _\bs_\be_\bt_\bt_\bi_\bn_\bg_\bs _\bb_\be_\bf_\bo_\br_\be _\bf_\bo_\br_\bm_\ba_\bt_\bt_\bi_\bn_\bg _\ba _\bm_\be_\bs_\bs_\ba_\bg_\be
+ _\b3_\b._\b2_\b2 _\bC_\bh_\ba_\bn_\bg_\be _\bs_\be_\bt_\bt_\bi_\bn_\bg_\bs _\bb_\be_\bf_\bo_\br_\be _\bf_\bo_\br_\bm_\ba_\bt_\bt_\bi_\bn_\bg _\ba _\bm_\be_\bs_\bs_\ba_\bg_\be
Usage: message-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
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 55) 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 56) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example:
message-hook ~A 'set pager=builtin'
message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
- _\b3_\b._\b2_\b2 _\bC_\bh_\bo_\bo_\bs_\bi_\bn_\bg _\bt_\bh_\be _\bc_\br_\by_\bp_\bt_\bo_\bg_\br_\ba_\bp_\bh_\bi_\bc _\bk_\be_\by _\bo_\bf _\bt_\bh_\be _\br_\be_\bc_\bi_\bp_\bi_\be_\bn_\bt
+ _\b3_\b._\b2_\b3 _\bC_\bh_\bo_\bo_\bs_\bi_\bn_\bg _\bt_\bh_\be _\bc_\br_\by_\bp_\bt_\bo_\bg_\br_\ba_\bp_\bh_\bi_\bc _\bk_\be_\by _\bo_\bf _\bt_\bh_\be _\br_\be_\bc_\bi_\bp_\bi_\be_\bn_\bt
Usage: crypt-hook _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\bi_\bd
crypt-hook command provides a method by which you can specify the ID of the
public key to be used when encrypting messages to a certain recipient.
+ The Mutt Next Generation E-Mail Client 40
+
The meaning of "key id" is to be taken broadly in this context: You can either
put a numerical key ID here, an e-mail address, or even just a real name.
- _\b3_\b._\b2_\b3 _\bA_\bd_\bd_\bi_\bn_\bg _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\bs _\bt_\bo _\bt_\bh_\be _\bk_\be_\by_\bb_\bo_\ba_\br_\bd _\bb_\bu_\bf_\bf_\be_\br
+ _\b3_\b._\b2_\b4 _\bA_\bd_\bd_\bi_\bn_\bg _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\bs _\bt_\bo _\bt_\bh_\be _\bk_\be_\by_\bb_\bo_\ba_\br_\bd _\bb_\bu_\bf_\bf_\be_\br
Usage: push _\bs_\bt_\br_\bi_\bn_\bg
- This command adds the named string to the keyboard buffer. The string may
-
- The Mutt Next Generation E-Mail Client 39
+ This command adds the named string to the keyboard buffer. The string may con-
+ tain control characters, key names and function names like the sequence string
+ in the _\bm_\ba_\bc_\br_\bo (section 3.8 , page 28) command. You may use it to automatically
+ run a sequence of commands at startup, or when entering certain folders.
- contain control characters, key names and function names like the sequence
- string in the _\bm_\ba_\bc_\br_\bo (section 3.7 , page 27) command. You may use it to auto-
- matically run a sequence of commands at startup, or when entering certain fold-
- ers.
-
- _\b3_\b._\b2_\b4 _\bE_\bx_\be_\bc_\bu_\bt_\bi_\bn_\bg _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
+ _\b3_\b._\b2_\b5 _\bE_\bx_\be_\bc_\bu_\bt_\bi_\bn_\bg _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn_\bs
Usage: exec _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
This command can be used to execute any function. Functions are listed in the
- _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 171). ``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 172). ``exec function'' is equivalent
to ``push <function>''.
- _\b3_\b._\b2_\b5 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bS_\bc_\bo_\br_\bi_\bn_\bg
+ _\b3_\b._\b2_\b6 _\bM_\be_\bs_\bs_\ba_\bg_\be _\bS_\bc_\bo_\br_\bi_\bn_\bg
Usage: score _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
score "~f santaclaus@northpole\.int" =666
+ The Mutt Next Generation E-Mail Client 41
+
What is important to note is that negative score values will be rounded up to
0.
+\bo flag threshold: when a message has a score value equal or higher than the
flag threshold, it will be flagged.
- The Mutt Next Generation E-Mail Client 40
-
+\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.248 , page 147), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.249 , page 147),
- _\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.247 , page 146) 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.249 , page 147) 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.247 , page 146) are set to -1, which means that in the default
+ tion 7.4.249 , page 148), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.250 , page 148),
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.248 , page 148) and. By default,
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.250 , page 148) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
+ (section 7.4.248 , page 148) are set to -1, which means that in the default
threshold configuration no message will ever get marked as read or deleted.
Scoring gets especially interesting when combined with the color command and
This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
but it is more flexible, as it visually marks different scores.
- _\b3_\b._\b2_\b6 _\bS_\bp_\ba_\bm _\bd_\be_\bt_\be_\bc_\bt_\bi_\bo_\bn
+ _\b3_\b._\b2_\b7 _\bS_\bp_\ba_\bm _\bd_\be_\bt_\be_\bc_\bt_\bi_\bo_\bn
Usage: spam _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
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.113 , page 113) variable.
+ the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114) variable.
(Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
given message.)
Your first step is to define your external filter's spam patterns using the
spam command. _\bp_\ba_\bt_\bt_\be_\br_\bn should be a regular expression that matches a header in a
mail message. If any message in the mailbox matches this regular expression, it
+
+ The Mutt Next Generation E-Mail Client 42
+
will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
nospam pattern -- see below.) The appearance of this attribute is entirely up
to you, and is governed by the _\bf_\bo_\br_\bm_\ba_\bt parameter. _\bf_\bo_\br_\bm_\ba_\bt can be any static text,
with the second, etc.
If you're using multiple spam filters, a message can have more than one spam-
-
- The Mutt Next Generation E-Mail Client 41
-
related header. You can define spam patterns for each filter you use. If a mes-
sage matches two or more of these patterns, and the $spam_separator variable is
set to a string, then the message's spam tag will consist of all the _\bf_\bo_\br_\bm_\ba_\bt
still do something useful.
The nospam command can be used to write exceptions to spam patterns. If a
+
+ The Mutt Next Generation E-Mail Client 43
+
header pattern matches something in a spam command, but you nonetheless do not
want it to receive a spam tag, you can list a more precise pattern under a
nospam command.
instead of adding an exception. Likewise, if the _\bp_\ba_\bt_\bt_\be_\br_\bn for a spam command
matches an entry on the nospam list, that nospam entry will be removed. If the
_\bp_\ba_\bt_\bt_\be_\br_\bn for nospam is ``*'', _\ba_\bl_\bl _\be_\bn_\bt_\br_\bi_\be_\bs _\bo_\bn _\bb_\bo_\bt_\bh _\bl_\bi_\bs_\bt_\bs will be removed. This
-
- The Mutt Next Generation E-Mail Client 42
-
might be the default action if you use spam and nospam in conjunction with a
folder-hook.
spam "^From: .*MAILER-DAEMON" "999"
- _\b3_\b._\b2_\b7 _\bS_\be_\bt_\bt_\bi_\bn_\bg _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+ _\b3_\b._\b2_\b8 _\bS_\be_\bt_\bt_\bi_\bn_\bg _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
Usage: set [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
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 85). There are four basic types of variables: boolean, number, string and
+ page 86). There are four basic types of variables: boolean, number, string and
quadoption. _\bb_\bo_\bo_\bl_\be_\ba_\bn variables can be _\bs_\be_\bt (true) or _\bu_\bn_\bs_\be_\bt (false). _\bn_\bu_\bm_\bb_\be_\br
variables can be assigned a positive integer value.
toggle the value (on or off). This is useful when writing macros. Example:
set invsmart_wrap.
+ The Mutt Next Generation E-Mail Client 44
+
The toggle command automatically prepends the inv prefix to all specified vari-
ables.
Using the enter-command function in the _\bi_\bn_\bd_\be_\bx menu, you can query the value of
a variable by prefixing the name of the variable with a question mark:
- The Mutt Next Generation E-Mail Client 43
-
set ?allow_8bit
The question mark is actually only required for boolean and quadoption vari-
With the reset command there exists the special variable ``all'', which allows
you to reset all variables to their system defaults.
- _\b3_\b._\b2_\b8 _\bR_\be_\ba_\bd_\bi_\bn_\bg _\bi_\bn_\bi_\bt_\bi_\ba_\bl_\bi_\bz_\ba_\bt_\bi_\bo_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs _\bf_\br_\bo_\bm _\ba_\bn_\bo_\bt_\bh_\be_\br _\bf_\bi_\bl_\be
+ _\b3_\b._\b2_\b9 _\bR_\be_\ba_\bd_\bi_\bn_\bg _\bi_\bn_\bi_\bt_\bi_\ba_\bl_\bi_\bz_\ba_\bt_\bi_\bo_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bs _\bf_\br_\bo_\bm _\ba_\bn_\bo_\bt_\bh_\be_\br _\bf_\bi_\bl_\be
Usage: source _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
If the filename ends with a vertical bar (|), then _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be is considered to be
an executable program from which to read input (eg. source ~/bin/myscript|).
- _\b3_\b._\b2_\b9 _\bR_\be_\bm_\bo_\bv_\bi_\bn_\bg _\bh_\bo_\bo_\bk_\bs
+ _\b3_\b._\b3_\b0 _\bR_\be_\bm_\bo_\bv_\bi_\bn_\bg _\bh_\bo_\bo_\bk_\bs
Usage: unhook [ * | _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be ]
can remove all hooks of a specific type by saying something like unhook send-
hook.
- _\b3_\b._\b3_\b0 _\bS_\bh_\ba_\br_\bi_\bn_\bg _\bS_\be_\bt_\bu_\bp_\bs
+ _\b3_\b._\b3_\b1 _\bS_\bh_\ba_\br_\bi_\bn_\bg _\bS_\be_\bt_\bu_\bp_\bs
- _\b3_\b._\b3_\b0_\b._\b1 _\bC_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bS_\be_\bt_\bs
+ The Mutt Next Generation E-Mail Client 45
+
+ _\b3_\b._\b3_\b1_\b._\b1 _\bC_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bS_\be_\bt_\bs
As users may run mutt-ng on different systems, the configuration must be main-
tained because it's likely that people want to use the setup everywhere they
specify in which character set their configuration files are encoded. Please
note that while reading the configuration files, this is only respected after
the corresponding declaration appears. It's advised to put the following at the
-
- The Mutt Next Generation E-Mail Client 44
-
very beginning of a users muttngrc:
set config_charset = "..."
while, again, replacing the dots with the appropriate name. This tells vim as
which character set to read and save the file.
- _\b3_\b._\b3_\b0_\b._\b2 _\bM_\bo_\bd_\bu_\bl_\ba_\br_\bi_\bz_\ba_\bt_\bi_\bo_\bn
+ _\b3_\b._\b3_\b1_\b._\b2 _\bM_\bo_\bd_\bu_\bl_\ba_\br_\bi_\bz_\ba_\bt_\bi_\bo_\bn
``Modularization'' means to divide the setup into several files while sorting
the options or commands by topic. Especially for longer setups (e.g. with many
When using separation, setups may be, as a whole or in fractions, shared over
different systems.
- _\b3_\b._\b3_\b0_\b._\b3 _\bC_\bo_\bn_\bd_\bi_\bt_\bi_\bo_\bn_\ba_\bl _\bp_\ba_\br_\bt_\bs
+ _\b3_\b._\b3_\b1_\b._\b3 _\bC_\bo_\bn_\bd_\bi_\bt_\bi_\bo_\bn_\ba_\bl _\bp_\ba_\br_\bt_\bs
When using a configuration on different systems, the user may not always have
influence on how mutt-ng is installed and which features it includes.
...whereby <item> can be one of:
+ The Mutt Next Generation E-Mail Client 46
+
+\bo a function name
+\bo a variable name
All available functions, variables and menus are documented elsewhere in this
manual but ``features'' is specific to these two commands. To test for one,
-
- The Mutt Next Generation E-Mail Client 45
-
prefix one of the following keywords with feature_:
ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
An example for testing for variable names can be used if users use different
revisions of mutt-ng whereby the older one may not have a certain variable. To
- test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.102 , page 110),
+ test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.103 , page 111),
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.173 , page 129) only if the pager menu is available, use:
+ (section 7.4.174 , page 130) only if the pager menu is available, use:
ifdef pager 'set pager_index_lines = 10'
ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
+ The Mutt Next Generation E-Mail Client 47
+
...and...
ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
- The Mutt Next Generation E-Mail Client 46
-
- _\b3_\b._\b3_\b1 _\bO_\bb_\bs_\bo_\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs
+ _\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 85) for a complete list.
+ _\bl_\be_\bt_\be _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs (section 7.4 , page 86) 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 81) must be specified using regular expressions (regexp) in
+ tion 7.2 , page 82) must be specified using regular expressions (regexp) in
the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
and GNU awk). For your convenience, we have included below a brief description
of this syntax.
sign ``$'' are metacharacters that respectively match the empty string at the
beginning and end of a line.
+ The Mutt Next Generation E-Mail Client 48
+
A list of characters enclosed by ``['' and ``]'' matches any single character
in that list; if the first character of the list is a caret ``^'' then it
matches any character n\bno\bot\bt in the list. For example, the regular expression
place it anywhere but first. Finally, to include a literal hyphen ``-'' place
it last.
- The Mutt Next Generation E-Mail Client 47
-
Certain named classes of characters are predefined. Character classes consist
of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
defined by the POSIX standard:
A character class is only valid in a regular expression inside the brackets of
a character list. Note that the brackets in these class names are part of the
+
+ The Mutt Next Generation E-Mail Client 49
+
symbolic names, and must be included in addition to the brackets delimiting the
bracket list. For example, [\b[[\b[:\b:d\bdi\big\bgi\bit\bt:\b:]\b]]\b] is equivalent to [\b[0\b0-\b-9\b9]\b].
Collating Symbols
A collating symbol is a multi-character collating element enclosed
-
- The Mutt Next Generation E-Mail Client 48
-
in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
ment, then [\b[[\b[.\b.c\bch\bh.\b.]\b]]\b] is a regexp that matches this collating ele-
ment, while [\b[c\bch\bh]\b] is a regexp that matches either ``c'' or ``h''.
ing regular expression matches any string matching either subexpression.
Repetition takes precedence over concatenation, which in turn takes precedence
+
+ The Mutt Next Generation E-Mail Client 50
+
over alternation. A whole subexpression may be enclosed in parentheses to
override these precedence rules.
Matches the empty string at either the beginning or the end of a
word.
- The Mutt Next Generation E-Mail Client 49
-
\\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 81) in the Reference chapter.
+ _\bt_\be_\br_\bn_\bs (section 7.2 , page 82) in the Reference chapter.
It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
most simple possibility is to logically AND several patterns by stringing them
together:
+ The Mutt Next Generation E-Mail Client 51
+
~s 'SPAM' ~U
The pattern above matches all messages that contain ``SPAM'' in the subject and
To logical OR patterns, simply use the | operator. This one especially useful
when using local groups:
- The Mutt Next Generation E-Mail Client 50
-
~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
(~b mutt-ng|~s Mutt-ng)
!~x '@synflood\.at'
date ranges between a fixed number of units and the current date. How this
works can be seen in the following example:
+ The Mutt Next Generation E-Mail Client 52
+
~d >2w # messages older than two weeks
~d <3d # messages newer than 3 days
~d =1m # messages that are exactly one month old
_\b4_\b._\b3_\b._\b1 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn
- The Mutt Next Generation E-Mail Client 51
-
The so called _\bF_\bo_\br_\bm_\ba_\bt _\bS_\bt_\br_\bi_\bn_\bg_\bs offer great flexibility when configuring mutt-ng.
In short, they describe what items to print out how in menus and status mes-
sages.
+\bo the current mutt-ng version number
The setting for the status bar of the index is controlled via the _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\b-
- _\bm_\ba_\bt (section 7.4.312 , page 162) variable. For the hostname and version
+ _\bm_\ba_\bt (section 7.4.313 , page 163) variable. For the hostname and version
string, there's an expando for $status_format: %h expands to the hostname and
%v to the version string. When just configuring:
To include the mailbox' name is as easy as:
+ The Mutt Next Generation E-Mail Client 53
+
set status_format = "%v on %h: %B: ...
When the currently opened mailbox is Inbox, this will be expanded to:
For the number of certain types of messages, one more feature of the format
strings is extremely useful. If there aren't messages of a certain type, it may
-
- The Mutt Next Generation E-Mail Client 52
-
not be desired to print just that there aren't any but instead only print some-
thing if there are any.
+\bo and make it print ``no new messages'' if there aren't any
+ The Mutt Next Generation E-Mail Client 54
+
The corresponding configuration is:
set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
- The Mutt Next Generation E-Mail Client 53
-
As you might see from this rather simple example, one can create very complex
but fancy status messages. Please see the reference chapter for expandos and
those which may be printed nonzero.
set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
+ The Mutt Next Generation E-Mail Client 55
+
_\b4_\b._\b4 _\bU_\bs_\bi_\bn_\bg _\bT_\ba_\bg_\bs
Sometimes it is desirable to perform an operation on a group of messages all at
ject. To tag all messages matching a pattern, use the tag-pattern function,
which is bound to ``shift-T'' by default. Or you can select individual mes-
sages by hand using the ``tag-message'' function, which is bound to ``t'' by
-
- The Mutt Next Generation E-Mail Client 54
-
- default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 81) for Mutt-ng's pattern matching
+ default. See _\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 82) 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.18 ,
- page 91) variable is set, the next operation applies to the tagged messages
+ that operation can be used in that manner. If the _\b$_\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg (section 7.4.19 ,
+ page 92) variable is set, the next operation applies to the tagged messages
automatically, without requiring the ``tag-prefix''.
- In _\bm_\ba_\bc_\br_\bo_\bs (section 3.7 , page 27) or _\bp_\bu_\bs_\bh (section 3.23 , page 38) commands,
+ In _\bm_\ba_\bc_\br_\bo_\bs (section 3.8 , page 28) or _\bp_\bu_\bs_\bh (section 3.24 , page 40) commands,
you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
stop "eating" the macro when it encounters the ``end-cond'' operator; after
arbitrary commands before performing some operation. For example, you may wish
to tailor your configuration based upon which mailbox you are reading, or to
whom you are sending mail. In the Mutt-ng world, a _\bh_\bo_\bo_\bk consists of a _\br_\be_\bg_\bu_\bl_\ba_\br
- _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 46) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 81) along
+ _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 47) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 82) along
with a configuration option/command. See
- +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 26)
+ +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 28)
- +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 37)
+ +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 38)
- +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 38)
+ +\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 39)
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 36)
+ +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 37)
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34)
+ +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35)
- +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 36)
+ +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)
- +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 37)
+ +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 38)
for specific details on each type of _\bh_\bo_\bo_\bk available.
N\bNo\bot\bte\be:\b: if a hook changes configuration settings, these changes remain effective
until the end of the current mutt session. As this is generally not desired, a
default hook needs to be added before all other hooks to restore configuration
+
+ The Mutt Next Generation E-Mail Client 56
+
defaults. Here is an example with send-hook and the my_hdr directive:
send-hook . 'unmy_hdr From:'
send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
- The Mutt Next Generation E-Mail Client 55
-
_\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 46) is sufficient. But in dealing with
+ _\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 47) is sufficient. But in dealing with
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 81) 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 82) 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.47 , page 97) 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.47 , page 97) that is in
+ 7.4.48 , page 98) variable. The pattern is translated at the time the hook is
+ declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 7.4.48 , page 98) that is in
effect at that time will be used.
_\b4_\b._\b6 _\bU_\bs_\bi_\bn_\bg _\bt_\bh_\be _\bs_\bi_\bd_\be_\bb_\ba_\br
If you want to specify the mailboxes you can do so with:
+ The Mutt Next Generation E-Mail Client 57
+
set mbox='=INBOX'
mailboxes INBOX \
MBOX1 \
You can also specify the colors for mailboxes with new mails by using:
- The Mutt Next Generation E-Mail Client 56
-
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.225 , page 141) vari-
+ simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.226 , page 142) vari-
able, you specify the wrapper command to use. For example:
set query_command = "mutt_ldap_query.pl '%s'"
The wrapper script should accept the query on the command-line. It should
return a one line message, then each matching response on a single line, each
+
+ The Mutt Next Generation E-Mail Client 58
+
line containing a tab separated address then name then some other optional
information. On error, or if there are no matching addresses, return a non-
zero exit code and a one line error message.
Searching database ... 20 entries ... 3 matching:
me@cs.hmc.edu Michael Elkins mutt dude
blong@fiction.net Brandon Long mutt and more
-
- The Mutt Next Generation E-Mail Client 57
-
roessler@guug.de Thomas Roessler mutt pgp
There are two mechanisms for accessing the query function of mutt. One is to
Mutt-ng supports reading and writing of four different mailbox formats: mbox,
MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
- uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.129 , page 118)
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.130 , page 119)
variable.
m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All messages are
M\bMH\bH. A radical departure from _\bm_\bb_\bo_\bx and _\bM_\bM_\bD_\bF, a mailbox consists of a directory
and each message is stored in a separate file. The filename indicates the mes-
sage number (however, this is may not correspond to the message number Mutt-ng
+
+ The Mutt Next Generation E-Mail Client 59
+
displays). Deleted messages are renamed with a comma (,) prepended to the file-
name. N\bNo\bot\bte\be:\b: Mutt detects this type of mailbox by looking for either
.mh_sequences or .xmhcache (needed to distinguish normal directories from MH
ment for sendmail). Similar to _\bM_\bH, except that it adds three subdirectories of
the mailbox: _\bt_\bm_\bp, _\bn_\be_\bw and _\bc_\bu_\br. Filenames for the messages are chosen in such a
way they are unique, even when two programs are writing the mailbox over NFS,
-
- The Mutt Next Generation E-Mail Client 58
-
which means that no file locking is needed.
_\b4_\b._\b9 _\bM_\ba_\bi_\bl_\bb_\bo_\bx _\bS_\bh_\bo_\br_\bt_\bc_\bu_\bt_\bs
These shortcuts can be used anywhere you are prompted for a file or mailbox
path.
- +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.301 , page 159) (incoming)
+ +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 160) (incoming)
mailbox
- +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.128 , page 118) file
+ +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 119) file
- +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.234 , page 143) file
+ +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144) 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.67 , page 102) directory
+ +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) directory
- +\bo @_\ba_\bl_\bi_\ba_\bs -- refers to the _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bo_\bl_\bd_\be_\br (section 3.17 , page 36) 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 37) 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.12 , page 33) commands in your muttrc.
+ (section 3.13 , page 34) 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.113 , page 113) variable, the escape
+ box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114) variable, the escape
``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
+
+ The Mutt Next Generation E-Mail Client 60
+
field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
returns the name of the author).
person. The ``list-reply'' function, which by default is bound to ``L'' in the
_\bi_\bn_\bd_\be_\bx menu and _\bp_\ba_\bg_\be_\br, helps reduce the clutter by only replying to the known
mailing list addresses instead of all recipients (except as specified by Mail-
-
- The Mutt Next Generation E-Mail Client 59
-
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.69 , page 103) option is set, mutt will
+ and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.70 , page 104) 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.91 , page 108) configuration variable is set. Using list-reply
+ (section 7.4.92 , page 109) 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.237 , page 144) variable to help decide which address to use. If set to
+ 7.4.238 , page 145) 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.113 , page 113) variable's ``%y'' and ``%Y''
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114) 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.295 , page 157) the mail-
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 7.4.296 , page 158) 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-
- cally. If you've ever used a threaded news client, this is the same concept.
- It makes dealing with large volume mailing lists easier because you can easily
- delete uninteresting threads and quickly find topics of value.
+ like structure where a message and all of its replies are represented
- _\b4_\b._\b1_\b1 _\bE_\bd_\bi_\bt_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
+ The Mutt Next Generation E-Mail Client 61
- Mutt-ng has the ability to dynamically restructure threads that are broken
+ graphically. If you've ever used a threaded news client, this is the same con-
+ cept. It makes dealing with large volume mailing lists easier because you can
+ easily delete uninteresting threads and quickly find topics of value.
- The Mutt Next Generation E-Mail Client 60
+ _\b4_\b._\b1_\b1 _\bE_\bd_\bi_\bt_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
+ Mutt-ng has the ability to dynamically restructure threads that are broken
either by misconfigured software or bad behavior from some correspondents. This
allows to clean your mailboxes formats) from these annoyances which make it
hard to follow a discussion.
To support this, there are two variables:
- +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.54 , page 99) is used to request receipts for
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.55 , page 100) 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.55 , page 99) requests how much of your message
+ The Mutt Next Generation E-Mail Client 62
+
+ +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 7.4.56 , page 100) requests how much of your message
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 61
-
If Mutt-ng was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bp_\bo_\bp flag), it has the ability to work with mailboxes located on a
remote POP3 server and fetch mail for local browsing.
Polling for new mail is more expensive over POP3 than locally. For this reason
the frequency at which Mutt-ng will check for mail remotely can be controlled
- by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.212 , page 138) variable, which defaults
+ by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.213 , page 140) 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.210 , page 138), fetch all your
- new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.301 , page 159).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.211 , page 139), fetch all your
+ new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 160).
After this point, Mutt-ng runs exactly as if the mail had always been local.
N\bNo\bot\bte\be:\b: If you only need to fetch all messages to local mailbox you should con-
INBOX is the special name for your spool mailbox on the IMAP server. If you
want to access another mail folder at the IMAP server, you should use
imap://imapserver/path/to/folder where path/to/folder is the path of the folder
+
+ The Mutt Next Generation E-Mail Client 63
+
you want to access.
You can select an alternative port by specifying it with the server, i.e.:
name@imapserver[:port]/INBOX.
If Mutt-ng was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
-
- The Mutt Next Generation E-Mail Client 62
-
the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This natu-
rally requires that the server supports SSL encrypted connections. To access a
folder with IMAP/SSL, you should use imaps://[user-
When browsing folders on an IMAP server, you can toggle whether to look at only
the folders you are subscribed to, or all folders with the _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
- command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.100 , page 110)
+ command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.101 , page 111)
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.102 , page 110) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.325 , page 166) variables.
+ want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.103 , page 111) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.326 , page 168) variables.
Note that if you are using mbox as the mail store on UW servers prior to
v12.250, the server has been reported to disconnect a client if another client
respectively). You may also subscribe and unsubscribe to mailboxes (nor-
mally these are bound to s and u, respectively).
+ The Mutt Next Generation E-Mail Client 64
+
_\b4_\b._\b1_\b4_\b._\b2 _\bA_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bi_\bo_\bn
Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
which allows you to log in to a public IMAP server without having an account.
To use ANONYMOUS, simply make your username blank or "anonymous".
- The Mutt Next Generation E-Mail Client 63
-
SASL is a special super-authenticator, which selects among several protocols
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
available on your host and the server. Using some of these methods (including
There are a few variables which control authentication:
- +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.108 , page 112) - controls the username under
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.109 , page 113) - 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.103 , page 111) - a password which you may pre-
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.104 , page 112) - 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.94 , page 108) - a colon-delimited list
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs (section 7.4.95 , page 109) - 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.160 , page 126) variable.
+ file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 7.4.161 , page 127) 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.25 , page
- 39).
+
+ The Mutt Next Generation E-Mail Client 65
+
+ to use a killfile has been discussed in _\bM_\be_\bs_\bs_\ba_\bg_\be _\bs_\bc_\bo_\br_\bi_\bn_\bg (section 3.26 , page
+ 40).
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 64
-
score ~* =42
This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
functionality. When configure was called with --with-libesmtp or the output
muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
support includes support for Delivery Status Notification (see _\bD_\be_\bl_\bi_\bv_\be_\br_\by _\bS_\bt_\ba_\bt_\bu_\bs
- _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 60) 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.332 , page 168).
+ _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 61) section) as well as handling the 8BIT-
+ MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.333 , page 169).
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.290 , page 156)
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.291 , page 157)
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.294 ,
- page 157) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.291 , page 156) variables.
+ The Mutt Next Generation E-Mail Client 66
+
+ Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 7.4.295 ,
+ page 158) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.292 , page 157) variables.
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.293 , page 157) variable must be either set to
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 7.4.294 , page 158) variable must be either set to
``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 65
-
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.289 ,
- page 156) 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.290 ,
+ page 157) may be used to set the envelope different from the From: header.
_\b4_\b._\b1_\b7 _\bM_\ba_\bn_\ba_\bg_\bi_\bn_\bg _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bI_\bM_\bA_\bP_\b/_\bP_\bO_\bP_\b/_\bN_\bN_\bT_\bP _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\bs _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
an arbitrary format, provided that the user has a script to convert from/to
this format to one of the accepted.
+ The Mutt Next Generation E-Mail Client 67
+
The most common use is to open compressed archived folders e.g. with gzip.
In addition, the user can provide a script that gets a folder in an accepted
may be faster than converting the entire folder to the accepted format, append-
ing to it and converting back to the user-defined format.
- There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 66), _\bc_\bl_\bo_\bs_\be_\b-
- _\bh_\bo_\bo_\bk (section 4.19.2 , page 66) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 67))
+ There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 67), _\bc_\bl_\bo_\bs_\be_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.2 , page 67) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68))
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 66
-
For example:
open-hook \\.gz$ "gzip -cd %f > %t"
append-hook \\.gz$ "gzip -c %t >> %f"
You do not have to specify all of the commands. If you omit _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (sec-
- tion 4.19.3 , page 67), 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 66) (or give
+ tion 4.19.3 , page 68), the folder will be open and closed again each time you
+ will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67) (or give
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 67) though you'll be able to append to the folder.
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 68) 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.244 , page 146), so that the compressed file
+ unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 7.4.245 , page 147), so that the compressed file
will be removed if you delete all of the messages.
_\b4_\b._\b1_\b9_\b._\b1 _\bO_\bp_\be_\bn _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\bf_\bo_\br _\br_\be_\ba_\bd_\bi_\bn_\bg
Example:
+ The Mutt Next Generation E-Mail Client 68
+
open-hook \\.gz$ "gzip -cd %f > %t"
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type.
Usage: close-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
This is used to close the folder that was open with the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 66) command after some changes were made to it.
-
- The Mutt Next Generation E-Mail Client 67
+ 4.19.1 , page 67) command after some changes were made to it.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd string is the command that can be used for closing the folders
whose names match _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 66) 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 66) command.
+ 4.19.1 , page 67) command. Temporary folder in this case is the folder previ-
+ ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 67) command.
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 66) is not called when you exit from the
+ _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67) 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 66)
+ _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 67)
command. 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 67) is used, the folder is not opened,
+ When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68) is used, the folder is not opened,
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.129 , page 118)) type is always
+ is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.130 , page 119)) type is always
+
+ The Mutt Next Generation E-Mail Client 69
+
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 66) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 67). _\ba_\bp_\bp_\be_\bn_\bd_\b-
- _\bh_\bo_\bo_\bk (section 4.19.3 , page 67) is only for appending to existing folders.
+ page 67) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 68). _\ba_\bp_\bp_\be_\bn_\bd_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 68) is only for appending to existing folders.
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 66) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 66)respectively) each
+ 4.19.1 , page 67) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 67)respectively) each
time you will add to it.
- The Mutt Next Generation E-Mail Client 68
-
_\b4_\b._\b1_\b9_\b._\b4 _\bE_\bn_\bc_\br_\by_\bp_\bt_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs
The compressed folders support can also be used to handle encrypted folders. If
the message to a text representation. Mutt-ng internally supports a number of
MIME types, including text/plain, text/enriched, message/rfc822, and mes-
sage/news. In addition, the export controlled version of Mutt-ng recognizes a
+
+ The Mutt Next Generation E-Mail Client 70
+
variety of PGP MIME types, including PGP/MIME and application/pgp.
Mutt-ng will denote attachments with a couple lines describing them. These
Where the Description is the description or filename given for the attachment,
and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
- The Mutt Next Generation E-Mail Client 69
-
If Mutt-ng cannot deal with a MIME type, it will display a message like:
[-- image/gif is unsupported (use 'v' to view this part) --]
or canceling) the message. It can be toggled with the toggle-unlink command
(default: u). The next field is the MIME content-type, and can be changed with
the edit-type command (default: ^T). The next field is the encoding for the
+
+ The Mutt Next Generation E-Mail Client 71
+
attachment, which allows a binary message to be encoded for transmission on
7bit links. It can be changed with the edit-encoding command (default: ^E).
The next field is the size of the attachment, rounded to kilobytes or
_\b5_\b._\b2 _\bM_\bI_\bM_\bE _\bT_\by_\bp_\be _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bw_\bi_\bt_\bh _\bm_\bi_\bm_\be_\b._\bt_\by_\bp_\be_\bs
When you add an attachment to your mail message, Mutt-ng searches your personal
-
- The Mutt Next Generation E-Mail Client 70
-
mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
/usr/local/share/mutt/mime.types or /etc/mime.types
In order to handle various MIME types that Mutt-ng can not handle internally,
Mutt-ng parses a series of external configuration files to find an external
+
+ The Mutt Next Generation E-Mail Client 72
+
handler. The default search string for these files is a colon delimited list
set to
In particular, the metamail distribution will install a mailcap file, usually
as /usr/local/etc/mailcap, which contains some baseline entries.
- The Mutt Next Generation E-Mail Client 71
-
_\b5_\b._\b3_\b._\b1 _\bT_\bh_\be _\bB_\ba_\bs_\bi_\bc_\bs _\bo_\bf _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be
A mailcap file consists of a series of lines which are comments, blank, or def-
text/html; lynx %s
+ The Mutt Next Generation E-Mail Client 73
+
In this case, lynx does not support viewing a file from stdin, so you must use
the %s syntax. N\bNo\bot\bte\be:\b: _\bS_\bo_\bm_\be _\bo_\bl_\bd_\be_\br _\bv_\be_\br_\bs_\bi_\bo_\bn_\bs _\bo_\bf _\bl_\by_\bn_\bx _\bc_\bo_\bn_\bt_\ba_\bi_\bn _\ba _\bb_\bu_\bg _\bw_\bh_\be_\br_\be _\bt_\bh_\be_\by _\bw_\bi_\bl_\bl
_\bc_\bh_\be_\bc_\bk _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be _\bf_\bo_\br _\ba _\bv_\bi_\be_\bw_\be_\br _\bf_\bo_\br _\bt_\be_\bx_\bt_\b/_\bh_\bt_\bm_\bl_\b. _\bT_\bh_\be_\by _\bw_\bi_\bl_\bl _\bf_\bi_\bn_\bd _\bt_\bh_\be _\bl_\bi_\bn_\be
On the other hand, maybe you don't want to use lynx interactively, you just
want to have it convert the text/html to text/plain, then you can use:
- The Mutt Next Generation E-Mail Client 72
-
text/html; lynx -dump %s | more
Perhaps you wish to use lynx to view text/html files, and a pager on all other
The interpretation of shell meta-characters embedded in MIME parameters can
lead to security problems in general. Mutt-ng tries to quote parameters in
expansion of %s syntaxes properly, and avoids risky characters by substituting
- them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.120 , page 117) variable.
+ them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.121 , page 118) variable.
Although mutt's procedures to invoke programs with mailcap seem to be safe,
there are other applications parsing mailcap, maybe taking less care of it.
_\b5_\b._\b3_\b._\b3_\b._\b1 _\bO_\bp_\bt_\bi_\bo_\bn_\ba_\bl _\bF_\bi_\be_\bl_\bd_\bs
+ The Mutt Next Generation E-Mail Client 74
+
In addition to the required content-type and view command fields, you can add
semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
nizes the following optional fields:
amounts of text on stdout. This causes Mutt-ng to invoke a pager
(either the internal pager or the external pager defined by the
pager variable) on the output of the view command. Without this
-
- The Mutt Next Generation E-Mail Client 73
-
flag, Mutt-ng assumes that the command is interactive. One could
use this to replace the pipe to more in the lynx -dump example in
the Basic section:
needsterminal
Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
- tion 5.4 , page 76), in order to decide whether it should honor
- the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 169) variable
+ tion 5.4 , page 77), in order to decide whether it should honor
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 170) variable
or not. When an attachment is viewed using an interactive program,
and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt-
- ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 169) and the exit
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.339 , page 170) and the exit
status of the program to decide if it will ask you to press a key
after the external program has exited. In all other situations it
will not prompt you for a key.
it to compose new attachments. Mutt-ng will default to the defined
editor for text attachments.
+ The Mutt Next Generation E-Mail Client 75
+
nametemplate=<template>
This field specifies the format for the file denoted by %s in the
command fields. Certain programs will require a certain file
text/html; lynx %s; nametemplate=%s.html
- The Mutt Next Generation E-Mail Client 74
-
test=<command>
This field specifies a command to run to test whether this mailcap
entry should be used. The command is defined with the command
Mutt-ng will skip the image/* entry and use the image/gif entry with the print
command.
- In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 76) to denote
+ In addition, you can use this with _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 77) to denote
two commands for viewing an attachment, one to be viewed automatically, the
other to be viewed interactively from the attachment menu. In addition, you
can then use the test feature to determine which viewer to use interactively
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s; nametemplate=%s.html
+
+ The Mutt Next Generation E-Mail Client 76
+
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
- For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 76), Mutt-ng will choose the third entry
+ For _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw (section 5.4 , page 77), Mutt-ng will choose the third entry
because of the copiousoutput tag. For interactive viewing, Mutt will run the
program RunningX to determine if it should use the first entry. If the program
returns non-zero, Mutt-ng will use the second entry for interactive viewing.
_\b5_\b._\b3_\b._\b3_\b._\b3 _\bC_\bo_\bm_\bm_\ba_\bn_\bd _\bE_\bx_\bp_\ba_\bn_\bs_\bi_\bo_\bn
The various commands defined in the mailcap files are passed to the /bin/sh
-
- The Mutt Next Generation E-Mail Client 75
-
shell using the system() function. Before the command is passed to /bin/sh -c,
it is parsed to expand various special parameters with information from Mutt-
ng. The keywords Mutt-ng expands are:
This mailcap file is fairly simple and standard:
+ The Mutt Next Generation E-Mail Client 77
+
# I'm always running X :)
video/*; xanim %s > /dev/null
image/*; xv %s > /dev/null
This mailcap file shows quite a number of examples:
- The Mutt Next Generation E-Mail Client 76
-
# Use xanim to view all videos Xanim produces a header on startup,
# send that to /dev/null so I don't see it
video/*; xanim %s > /dev/null
_\b5_\b._\b4 _\bM_\bI_\bM_\bE _\bA_\bu_\bt_\bo_\bv_\bi_\be_\bw
In addition to explicitly telling Mutt-ng to view an attachment with the MIME
- viewer defined in the mailcap file, Mutt-ng has support for automatically view-
- ing MIME attachments while in the pager.
+ viewer defined in the mailcap file, Mutt-ng has support for automatically
+
+ The Mutt Next Generation E-Mail Client 78
+
+ viewing MIME attachments while in the pager.
To work, you must define a viewer in the mailcap file which uses the copi-
ousoutput option to denote that it is non-interactive. Usually, you also use
For instance, if you set auto_view to:
- The Mutt Next Generation E-Mail Client 77
-
auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
Mutt-ng could use the following mailcap entries to automatically view attach-
alternative_order text/enriched text/plain text application/postscript image/*
Next, mutt will check if any of the types have a defined _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section
- 5.4 , page 76), and use that. Failing that, Mutt-ng will look for any text
+ 5.4 , page 77), and use that. Failing that, Mutt-ng will look for any text
type. As a last attempt, mutt will look for any type it knows how to handle.
To remove a MIME type from the alternative_order list, use the unalterna-
_\b5_\b._\b6 _\bM_\bI_\bM_\bE _\bL_\bo_\bo_\bk_\bu_\bp
Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
+
+ The Mutt Next Generation E-Mail Client 79
+
treated according to their mailcap entry. This option is designed to deal with
binary types such as application/octet-stream. When an attachment's mime-type
is listed in mime_lookup, then the extension of the filename will be compared
mime_lookup application/octet-stream application/X-Lotus-Manuscript
In addition, the unmime_lookup command may be used to disable this feature for
-
- The Mutt Next Generation E-Mail Client 78
-
any particular mime-type if it had been set, for example, in a global muttrc.
_\b6_\b. _\bS_\be_\bc_\bu_\br_\bi_\bt_\by _\bC_\bo_\bn_\bs_\bi_\bd_\be_\br_\ba_\bt_\bi_\bo_\bn_\bs
_\b6_\b._\b2 _\bT_\be_\bm_\bp_\bo_\br_\ba_\br_\by _\bF_\bi_\bl_\be_\bs
Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
- natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.330 , page 168) variable can be used to
+ natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.331 , page 169) 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.326 , page 167)
+ be desired which can be changed via the _\b$_\bt_\bm_\bp_\bd_\bi_\br (section 7.4.327 , page 168)
variable.
+ The Mutt Next Generation E-Mail Client 80
+
_\b6_\b._\b3 _\bI_\bn_\bf_\bo_\br_\bm_\ba_\bt_\bi_\bo_\bn _\bL_\be_\ba_\bk_\bs
_\b6_\b._\b3_\b._\b1 _\bM_\be_\bs_\bs_\ba_\bg_\be_\b-_\bI_\bD_\b: _\bh_\be_\ba_\bd_\be_\br_\bs
step counter which is increased (and rotated) with every message sent. If you'd
like to hide this information probably telling others how many mail you sent in
which time, you at least need to remove the %P expando from the default setting
- of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.146 , page 122) variable. Please make sure
+ of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.147 , page 123) variable. Please make sure
that you really know how local parts of these Message-ID: headers are composed.
- The Mutt Next Generation E-Mail Client 79
-
_\b6_\b._\b3_\b._\b2 _\bm_\ba_\bi_\bl_\bt_\bo_\b:_\b-_\bs_\bt_\by_\bl_\be _\bl_\bi_\bn_\bk_\bs
As mutt-ng be can be set up to be the mail client to handle mailto: style links
default, mutt-ng will be strict in interpreting them which means that arbitrary
header fields can be embedded in these links which could override existing
header fields or attach arbitrary files. This may be problematic if the
- _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.57 , page 100) variable is _\bu_\bn_\bs_\be_\bt, i.e. the user
+ _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101) 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.314 , page 164) variable, mutt-
+ When _\bu_\bn_\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo (section 7.4.315 , page 165) 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.57 , page 100) variable by force
+ +\bo turn on the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101) 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.119 , page 116) variable for
+ cap files (see the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh (section 7.4.120 , page 117) variable for
details.)
- These utilities may have a variety of security vulnerabilities, including over-
- writing of arbitrary files, information leaks or other exploitable bugs. These
- vulnerabilities may go unnoticed by the user, especially when they are called
- automatically (and without interactive prompting) from the mailcap file(s).
- When using mutt-ng's autoview mechanism in combination with mailcap files,
- please be sure to...
+ These utilities may have a variety of security vulnerabilities, including
+
+ The Mutt Next Generation E-Mail Client 81
+
+ overwriting of arbitrary files, information leaks or other exploitable bugs.
+ These vulnerabilities may go unnoticed by the user, especially when they are
+ called automatically (and without interactive prompting) from the mailcap
+ file(s). When using mutt-ng's autoview mechanism in combination with mailcap
+ files, please be sure to...
+\bo manually select trustworth applications with a reasonable calling sequence
+\bo periodically check the contents of mailcap files, especially after soft-
ware installations or upgrades
- The Mutt Next Generation E-Mail Client 80
-
+\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.120 , page 117) variable in its
+ +\bo leave the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.121 , page 118) variable in its
default state to restrict mailcap expandos to a safe set of characters
_\b6_\b._\b4_\b._\b2 _\bO_\bt_\bh_\be_\br
mailbox. However, it is possible to read other mailboxes and to send messages
from the command line as well.
+ The Mutt Next Generation E-Mail Client 82
+
-A expand an alias
-a attach a file to a message
-b specify a blind carbon-copy (BCC) address
-c specify a carbon-copy (Cc) address
- -D print the value of all variables on stdout
-e specify a config command to be run after initialization files are read
-f specify a mailbox to load
-F specify an alternate file to read initialization commands
-Q query a configuration variable
-R open mailbox in read-only mode
-s specify a subject (enclose in quotes if it contains spaces)
+ -t dump the value of all variables to stdout
+ -T dump the value of all changed variables to stdout
-v show version number and compile-time definitions
-x simulate the mailx(1) compose mode
-y show a menu containing the files specified by the mailboxes command
To read messages in a mailbox
- The Mutt Next Generation E-Mail Client 81
-
mutt [ -nz ] [ -F _\bm_\bu_\bt_\bt_\br_\bc ] [ -m _\bt_\by_\bp_\be ] [ -f _\bm_\ba_\bi_\bl_\bb_\bo_\bx ]
To compose a new message
_\b7_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
- The Mutt Next Generation E-Mail Client 82
+ The Mutt Next Generation E-Mail Client 83
~A all messages
~b EXPR messages which contain EXPR in the message body
alternates or any alias)
Where EXPR, USER, ID, and SUBJECT are _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs (section 4.1 , page
- 46). Special attention has to be made when using regular expressions inside of
+ 47). 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 83
+ The Mutt Next Generation E-Mail Client 84
*) 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 64) _\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 65) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\ba_\bl_\bi_\ba_\bs (section 3.3 , page 23) _\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 24) _\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.3 , page 23) [ * | _\bk_\be_\by ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bi_\ba_\bs (section 3.4 , page 24) [ * | _\bk_\be_\by ... ]
- +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.10 , page 31) _\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 32) _\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.10 , page 31) [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\be_\bs (section 3.11 , page 32) [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 77) _\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 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 77) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 67) _\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 68) _\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 76) _\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 77) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 76) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 77) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bb_\bi_\bn_\bd (section 3.4 , page 24) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ +\bo _\bb_\bi_\bn_\bd (section 3.5 , page 25) _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
- +\bo _\bc_\bh_\ba_\br_\bs_\be_\bt_\b-_\bh_\bo_\bo_\bk (section 3.5 , page 26) _\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 27) _\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 66) _\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 67) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\bo_\bl_\bo_\br (section 3.8 , page 28) _\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 29) _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
- +\bo _\bu_\bn_\bc_\bo_\bl_\bo_\br (section 3.8 , page 28) _\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 29) _\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.24 , page 39) _\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 40) _\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.18 , page 36) _\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 38) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 37) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ +\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 38) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
- +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.6 , page 26) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bf_\bo_\bl_\bd_\be_\br_\b-_\bh_\bo_\bo_\bk (section 3.7 , page 28) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 36) _\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 37) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
- +\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 36) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ +\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.17 , page 37) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
- +\bo _\bi_\bc_\bo_\bn_\bv_\b-_\bh_\bo_\bo_\bk (section 3.5 , page 26) _\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 27) _\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.9 , page 30) _\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 31) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- The Mutt Next Generation E-Mail Client 84
+ The Mutt Next Generation E-Mail Client 85
- +\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.9 , page 30) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ +\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.10 , page 31) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bl_\bi_\bs_\bt_\bs (section 3.12 , page 33) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bl_\bi_\bs_\bt_\bs (section 3.13 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\bl_\bi_\bs_\bt_\bs (section 3.12 , page 33) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\bl_\bi_\bs_\bt_\bs (section 3.13 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bm_\ba_\bc_\br_\bo (section 3.7 , page 27) _\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 28) _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
- +\bo _\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.14 , page 34) _\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 36) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34) _\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 35) _\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.21 , page 38) _\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 39) _\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 77) _\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 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 77) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ +\bo _\bu_\bn_\bm_\bi_\bm_\be_\b__\bl_\bo_\bo_\bk_\bu_\bp (section 5.6 , page 78) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\bm_\bo_\bn_\bo (section 3.8 , page 28) _\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 29) _\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.8 , page 28) _\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 29) _\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.15 , page 35) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 35) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
- +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 66) _\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 67) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 38) _\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 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
- +\bo _\bp_\bu_\bs_\bh (section 3.23 , page 38) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bp_\bu_\bs_\bh (section 3.24 , page 40) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\br_\be_\bs_\be_\bt (section 3.27 , page 42) _\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 43) _\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.17 , page 36) _\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 37) _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bc_\bo_\br_\be (section 3.25 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
+ +\bo _\bs_\bc_\bo_\br_\be (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
- +\bo _\bu_\bn_\bs_\bc_\bo_\br_\be (section 3.25 , page 39) _\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 40) _\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.20 , page 37) _\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 38) _\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.27 , page 42) [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 43) [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bu_\bn_\bs_\be_\bt (section 3.27 , page 42) _\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 43) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.28 , page 43) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ +\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 44) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bp_\ba_\bm (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
+ +\bo _\bs_\bp_\ba_\bm (section 3.27 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
- +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn
+ +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.27 , page 41) _\bp_\ba_\bt_\bt_\be_\br_\bn
- The Mutt Next Generation E-Mail Client 85
+ The Mutt Next Generation E-Mail Client 86
- +\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 33) _\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 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 33) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.13 , page 34) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- +\bo _\bt_\bo_\bg_\bg_\bl_\be (section 3.27 , page 42) _\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 43) _\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.29 , page 43) _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
+ +\bo _\bu_\bn_\bh_\bo_\bo_\bk (section 3.30 , page 44) _\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 86
+ The Mutt Next Generation E-Mail Client 87
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 87
+ The Mutt Next Generation E-Mail Client 88
the content references them, i.e. the content matches the regular expression
- given in $attach_remind_regexp. 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.
+ given in _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 91). If a match was
+ 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 $attach_remind_regexp are intended to remind the user to
- attach files if the message's text references them.
+ This variable and _\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.15 , page 91) are
+ intended to remind the user to attach files if the message's text references
+ them.
- See also the $attach_remind_regexp 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 91) variable.
_\b7_\b._\b4_\b._\b2 _\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\bs_\bu_\bb_\bj_\be_\bc_\bt
body if no changes are made to the file (this check only happens after the
_\bf_\bi_\br_\bs_\bt edit of the file). When set to _\bn_\bo, composition will never be aborted.
- _\b7_\b._\b4_\b._\b4 _\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be
+ _\b7_\b._\b4_\b._\b4 _\ba_\bg_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
+
+ Type: boolean
+
+ Default: yes
+
+ When _\bs_\be_\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
+ cating which version of Mutt-ng was used for composing them.
+
+ _\b7_\b._\b4_\b._\b5 _\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be
Type: path
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.28 , page 43)'' command for it to be executed.
+ the ``_\bs_\bo_\bu_\br_\bc_\be (section 3.29 , page 44)'' command for it to be executed.
+
+ _\b7_\b._\b4_\b._\b6 _\ba_\bl_\bi_\ba_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
- _\b7_\b._\b4_\b._\b5 _\ba_\bl_\bi_\ba_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
+ The Mutt Next Generation E-Mail Client 89
Type: string
%a
alias name
- The Mutt Next Generation E-Mail Client 88
-
%f
flags - currently, a 'd' for an alias marked for deletion
%t
character which indicates if the alias is tagged for inclusion
- _\b7_\b._\b4_\b._\b6 _\ba_\bl_\bl_\bo_\bw_\b__\b8_\bb_\bi_\bt
+ _\b7_\b._\b4_\b._\b7 _\ba_\bl_\bl_\bo_\bw_\b__\b8_\bb_\bi_\bt
Type: boolean
Controls whether 8-bit data is converted to 7-bit using either quoted-printable
or base64 encoding when sending mail.
- _\b7_\b._\b4_\b._\b7 _\ba_\bl_\bl_\bo_\bw_\b__\ba_\bn_\bs_\bi
+ _\b7_\b._\b4_\b._\b8 _\ba_\bl_\bl_\bo_\bw_\b__\ba_\bn_\bs_\bi
Type: boolean
sage could include a line like ``[-- PGP output follows ...' and give it the
same color as your attachment color.
- _\b7_\b._\b4_\b._\b8 _\ba_\br_\br_\bo_\bw_\b__\bc_\bu_\br_\bs_\bo_\br
+ _\b7_\b._\b4_\b._\b9 _\ba_\br_\br_\bo_\bw_\b__\bc_\bu_\br_\bs_\bo_\br
Type: boolean
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.
- _\b7_\b._\b4_\b._\b9 _\ba_\bs_\bc_\bi_\bi_\b__\bc_\bh_\ba_\br_\bs
+ The Mutt Next Generation E-Mail Client 90
+
+ _\b7_\b._\b4_\b._\b1_\b0 _\ba_\bs_\bc_\bi_\bi_\b__\bc_\bh_\ba_\br_\bs
Type: boolean
If _\bs_\be_\bt, Mutt-ng will use plain ASCII characters when displaying thread and
attachment trees, instead of the default ACS characters.
- The Mutt Next Generation E-Mail Client 89
-
- _\b7_\b._\b4_\b._\b1_\b0 _\ba_\bs_\bk_\bb_\bc_\bc
+ _\b7_\b._\b4_\b._\b1_\b1 _\ba_\bs_\bk_\bb_\bc_\bc
Type: boolean
If _\bs_\be_\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
editing an outgoing message.
- _\b7_\b._\b4_\b._\b1_\b1 _\ba_\bs_\bk_\bc_\bc
+ _\b7_\b._\b4_\b._\b1_\b2 _\ba_\bs_\bk_\bc_\bc
Type: boolean
If _\bs_\be_\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
the body of an outgoing message.
- _\b7_\b._\b4_\b._\b1_\b2 _\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b1_\b3 _\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
However, only the first content is valid for the message body. This variable
- is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 7.4.315 , page 164) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 7.4.316 , page 166) is unset.
- _\b7_\b._\b4_\b._\b1_\b3 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b4 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
This variable describes the format of the ``attachment'' menu. The following
printf(3)-style sequences are understood:
+ The Mutt Next Generation E-Mail Client 91
+
%C
charset
%D
deleted flag
- The Mutt Next Generation E-Mail Client 90
-
%d
description
%|X
pad to the end of the line with character 'X'
- _\b7_\b._\b4_\b._\b1_\b4 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp
+ _\b7_\b._\b4_\b._\b1_\b5 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\br_\be_\bm_\bi_\bn_\bd_\b__\br_\be_\bg_\be_\bx_\bp
Type: regular expression
Default: 'attach'
+ The Mutt Next Generation E-Mail Client 92
+
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 $abort_noattach.
-
- This variable and $abort_noattach are intended to remind the user to attach
- files if the message's text references them.
+ depending on the setting of _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 87).
- _\b7_\b._\b4_\b._\b1_\b5 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp
+ This variable and _\b$_\ba_\bb_\bo_\br_\bt_\b__\bn_\bo_\ba_\bt_\bt_\ba_\bc_\bh (section 7.4.1 , page 87) are intended to
+ remind the user to attach files if the message's text references them.
- The Mutt Next Generation E-Mail Client 91
+ _\b7_\b._\b4_\b._\b1_\b6 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp
Type: string
The separator to add between attachments when operating (saving, printing, pip-
ing, etc) on a list of tagged attachments.
- _\b7_\b._\b4_\b._\b1_\b6 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\bp_\bl_\bi_\bt
+ _\b7_\b._\b4_\b._\b1_\b7 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\bp_\bl_\bi_\bt
Type: boolean
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.15 ,
- page 91)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
+ operate on them as a single attachment. The ``_\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp (section 7.4.16 ,
+ page 92)'' separator is added after each attachment. When _\bs_\be_\bt, Mutt-ng will
operate on the attachments one by one.
- _\b7_\b._\b4_\b._\b1_\b7 _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn
+ _\b7_\b._\b4_\b._\b1_\b8 _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn
Type: string
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.113 , page 113)''.
+ on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)''.
- _\b7_\b._\b4_\b._\b1_\b8 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
+ _\b7_\b._\b4_\b._\b1_\b9 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
Type: boolean
``tag-prefix'' function (default: ';') to make the next function apply to all
tagged messages.
- _\b7_\b._\b4_\b._\b1_\b9 _\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b0 _\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt
Type: boolean
Default: no
- When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.57 , page 100)'', Mutt-ng
+ The Mutt Next Generation E-Mail Client 93
+
+ When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101)'', Mutt-ng
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.63 , page 101)''.
+ Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.64 , page 102)''.
- The Mutt Next Generation E-Mail Client 92
-
- _\b7_\b._\b4_\b._\b2_\b0 _\bb_\be_\be_\bp
+ _\b7_\b._\b4_\b._\b2_\b1 _\bb_\be_\be_\bp
Type: boolean
When this variable is _\bs_\be_\bt, Mutt-ng will beep when an error occurs.
- _\b7_\b._\b4_\b._\b2_\b1 _\bb_\be_\be_\bp_\b__\bn_\be_\bw
+ _\b7_\b._\b4_\b._\b2_\b2 _\bb_\be_\be_\bp_\b__\bn_\be_\bw
Type: boolean
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.20 , page 92)'' variable.
+ tion 7.4.21 , page 93)'' variable.
- _\b7_\b._\b4_\b._\b2_\b2 _\bb_\bo_\bu_\bn_\bc_\be
+ _\b7_\b._\b4_\b._\b2_\b3 _\bb_\bo_\bu_\bn_\bc_\be
Type: quadoption
_\bn_\bo is not generally useful, and thus not recommended, because you are unable to
bounce messages.
- _\b7_\b._\b4_\b._\b2_\b3 _\bb_\bo_\bu_\bn_\bc_\be_\b__\bd_\be_\bl_\bi_\bv_\be_\br_\be_\bd
+ _\b7_\b._\b4_\b._\b2_\b4 _\bb_\bo_\bu_\bn_\bc_\be_\b__\bd_\be_\bl_\bi_\bv_\be_\br_\be_\bd
Type: boolean
When this variable is _\bs_\be_\bt, Mutt-ng will include Delivered-To: header fields
when bouncing messages. Postfix users may wish to _\bu_\bn_\bs_\be_\bt this variable.
- _\b7_\b._\b4_\b._\b2_\b4 _\bb_\br_\ba_\bi_\bl_\bl_\be_\b__\bf_\br_\bi_\be_\bn_\bd_\bl_\by
+ _\b7_\b._\b4_\b._\b2_\b5 _\bb_\br_\ba_\bi_\bl_\bl_\be_\b__\bf_\br_\bi_\be_\bn_\bd_\bl_\by
Type: boolean
When this variable is set, mutt will place the cursor at the beginning of the
current line in menus, even when the arrow_cursor variable is unset, making it
easier for blind persons using Braille displays to follow these menus. The
+
+ The Mutt Next Generation E-Mail Client 94
+
option is disabled by default because many visual terminals don't permit making
the cursor invisible.
- _\b7_\b._\b4_\b._\b2_\b5 _\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\b__\bf_\bi_\bl_\be
+ _\b7_\b._\b4_\b._\b2_\b6 _\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\b__\bf_\bi_\bl_\be
Type: path
- The Mutt Next Generation E-Mail Client 93
-
Default: '~/.mutt_certificates'
Availability: SSL or GNUTLS
Example: set certificate_file=~/.muttng/certificates
- _\b7_\b._\b4_\b._\b2_\b6 _\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b2_\b7 _\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
Character set your terminal uses to display and enter textual data.
- _\b7_\b._\b4_\b._\b2_\b7 _\bc_\bh_\be_\bc_\bk_\b__\bn_\be_\bw
+ _\b7_\b._\b4_\b._\b2_\b8 _\bc_\bh_\be_\bc_\bk_\b__\bn_\be_\bw
Type: boolean
been looked at. If it's _\bu_\bn_\bs_\be_\bt, no check for new mail is performed while the
mailbox is open.
- _\b7_\b._\b4_\b._\b2_\b8 _\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bu_\bn_\br_\be_\ba_\bd
+ _\b7_\b._\b4_\b._\b2_\b9 _\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bu_\bn_\br_\be_\ba_\bd
Type: boolean
When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
sages.
- _\b7_\b._\b4_\b._\b2_\b9 _\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
+ The Mutt Next Generation E-Mail Client 95
+
+ _\b7_\b._\b4_\b._\b3_\b0 _\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
Controls the format of the status line displayed in the ``compose'' menu. This
- string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.312 , page 162)'', but has
-
- The Mutt Next Generation E-Mail Client 94
-
+ string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163)'', but has
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.312 , page 162)''
- 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.29 ,
- page 93)''.
+ See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163)''
+ option for more information on how to set ``_\b$_\bc_\bo_\bm_\bp_\bo_\bs_\be_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.30 ,
+ page 95)''.
- _\b7_\b._\b4_\b._\b3_\b0 _\bc_\bo_\bn_\bf_\bi_\bg_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b3_\b1 _\bc_\bo_\bn_\bf_\bi_\bg_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
When defined, Mutt-ng will recode commands in rc files from this encoding.
- _\b7_\b._\b4_\b._\b3_\b1 _\bc_\bo_\bn_\bf_\bi_\br_\bm_\ba_\bp_\bp_\be_\bn_\bd
+ _\b7_\b._\b4_\b._\b3_\b2 _\bc_\bo_\bn_\bf_\bi_\br_\bm_\ba_\bp_\bp_\be_\bn_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng will prompt for confirmation when appending messages to an
existing mailbox.
- _\b7_\b._\b4_\b._\b3_\b2 _\bc_\bo_\bn_\bf_\bi_\br_\bm_\bc_\br_\be_\ba_\bt_\be
+ _\b7_\b._\b4_\b._\b3_\b3 _\bc_\bo_\bn_\bf_\bi_\br_\bm_\bc_\br_\be_\ba_\bt_\be
Type: boolean
When _\bs_\be_\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
box which does not yet exist before creating it.
- _\b7_\b._\b4_\b._\b3_\b3 _\bc_\bo_\bn_\bn_\be_\bc_\bt_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b3_\b4 _\bc_\bo_\bn_\bn_\be_\bc_\bt_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
+
+ The Mutt Next Generation E-Mail Client 96
Type: number
many seconds if the connection is not able to be established. A negative value
causes Mutt-ng to wait indefinitely for the connection to succeed.
- The Mutt Next Generation E-Mail Client 95
-
- _\b7_\b._\b4_\b._\b3_\b4 _\bc_\bo_\bn_\bt_\be_\bn_\bt_\b__\bt_\by_\bp_\be
+ _\b7_\b._\b4_\b._\b3_\b5 _\bc_\bo_\bn_\bt_\be_\bn_\bt_\b__\bt_\by_\bp_\be
Type: string
Sets the default Content-Type: header field for the body of newly composed mes-
sages.
- _\b7_\b._\b4_\b._\b3_\b5 _\bc_\bo_\bp_\by
+ _\b7_\b._\b4_\b._\b3_\b6 _\bc_\bo_\bp_\by
Type: quadoption
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.234 , page
- 143)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.245 , page 146)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.71 , page 103)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 36)''.
+ saved for later references. Also see ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page
+ 144)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 147)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.72 , page 105)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 38)''.
- _\b7_\b._\b4_\b._\b3_\b6 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt
+ _\b7_\b._\b4_\b._\b3_\b7 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt
Type: boolean
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.281 , page 154)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
+ 7.4.282 , page 155)'' 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)
- _\b7_\b._\b4_\b._\b3_\b7 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bp_\bg_\bp
+ _\b7_\b._\b4_\b._\b3_\b8 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bp_\bg_\bp
Type: boolean
This variable controls whether or not Mutt-ng may automatically enable PGP
encryption/signing for messages. See also ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 7.4.36 , page 95)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.40 , page 96)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.38 , page 95)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.41 , page 96)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.281 , page 154)''.
+ 7.4.37 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 97)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 7.4.42 , page 97)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 155)''.
- _\b7_\b._\b4_\b._\b3_\b8 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
+ The Mutt Next Generation E-Mail Client 97
+
+ _\b7_\b._\b4_\b._\b3_\b9 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
Type: boolean
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
-
- The Mutt Next Generation E-Mail Client 96
-
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.281 , page 154)'' is _\bs_\be_\bt, then OpenSSL is
+ ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 155)'' 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)
- _\b7_\b._\b4_\b._\b3_\b9 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bm_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b4_\b0 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bm_\bi_\bm_\be
Type: boolean
This variable controls whether or not Mutt-ng may automatically enable S/MIME
encryption/signing for messages. See also ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt (section
- 7.4.36 , page 95)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.40 , page 96)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.38 , page 95)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.41 , page 96)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.281 , page 154)''.
+ 7.4.37 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.41 , page 97)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.39 , page 96)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 7.4.42 , page 97)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.282 , page 155)''.
- _\b7_\b._\b4_\b._\b4_\b0 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt
+ _\b7_\b._\b4_\b._\b4_\b1 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt
Type: boolean
If _\bs_\be_\bt, automatically PGP or OpenSSL encrypt replies to messages which are
encrypted. (Crypto only)
- _\b7_\b._\b4_\b._\b4_\b1 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn
+ _\b7_\b._\b4_\b._\b4_\b2 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn
Type: boolean
N\bNo\bot\bte\be:\b: this does not work on messages that are encrypted a\ban\bnd\bd signed! (Crypto
only)
- _\b7_\b._\b4_\b._\b4_\b2 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn_\be_\bn_\bc_\br_\by_\bp_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b4_\b3 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn_\be_\bn_\bc_\br_\by_\bp_\bt_\be_\bd
Type: boolean
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.40 , page 96)'', because it allows you to sign all messages which are
+ 7.4.41 , page 97)'', because it allows you to sign all messages which are
+
+ The Mutt Next Generation E-Mail Client 98
+
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.41 , page 96)'', 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 97)'', that Mutt-ng is not able to
find out whether an encrypted message is also signed. (Crypto only)
- _\b7_\b._\b4_\b._\b4_\b3 _\bc_\br_\by_\bp_\bt_\b__\bt_\bi_\bm_\be_\bs_\bt_\ba_\bm_\bp
+ _\b7_\b._\b4_\b._\b4_\b4 _\bc_\br_\by_\bp_\bt_\b__\bt_\bi_\bm_\be_\bs_\bt_\ba_\bm_\bp
Type: boolean
- The Mutt Next Generation E-Mail Client 97
-
Default: yes
If _\bs_\be_\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
ors to mark these lines, and rely on these, you may _\bu_\bn_\bs_\be_\bt this setting.
(Crypto only)
- _\b7_\b._\b4_\b._\b4_\b4 _\bc_\br_\by_\bp_\bt_\b__\bu_\bs_\be_\b__\bg_\bp_\bg_\bm_\be
+ _\b7_\b._\b4_\b._\b4_\b5 _\bc_\br_\by_\bp_\bt_\b__\bu_\bs_\be_\b__\bg_\bp_\bg_\bm_\be
Type: boolean
N\bNo\bot\bte\be: You need to use this option in your .muttngrc configuration file as it
won't have any effect when used interactively.
- _\b7_\b._\b4_\b._\b4_\b5 _\bc_\br_\by_\bp_\bt_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bs_\bi_\bg
+ _\b7_\b._\b4_\b._\b4_\b6 _\bc_\br_\by_\bp_\bt_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bs_\bi_\bg
Type: quadoption
whether or not to verify the signature. If ``_\bn_\bo'', never attempt to verify
cryptographic signatures. (Crypto only)
- _\b7_\b._\b4_\b._\b4_\b6 _\bd_\ba_\bt_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b4_\b7 _\bd_\ba_\bt_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
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.113 , page 113)''. This is passed to strftime(3)
+ ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)''. This is passed to strftime(3)
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.117 , page 116)''. If the first character in the string
+ ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.118 , page 117)''. 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).
- _\b7_\b._\b4_\b._\b4_\b7 _\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk
+ The Mutt Next Generation E-Mail Client 99
+
+ _\b7_\b._\b4_\b._\b4_\b8 _\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk
Type: string
This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
will be interpreted if they are specified with only a simple regexp, instead of
-
- The Mutt Next Generation E-Mail Client 98
-
a matching pattern. The hooks are expanded when they are declared, so a hook
will be interpreted according to the value of this variable at the time the
hook is declared. The default value matches if the message is either from a
address matches ``alternates'') and is to or cc'ed to a user matching the given
regular expression.
- _\b7_\b._\b4_\b._\b4_\b8 _\bd_\be_\bl_\be_\bt_\be
+ _\b7_\b._\b4_\b._\b4_\b9 _\bd_\be_\bl_\be_\bt_\be
Type: quadoption
be purged without prompting. If set to _\bn_\bo, messages marked for deletion will
be kept in the mailbox.
- _\b7_\b._\b4_\b._\b4_\b9 _\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be
+ _\b7_\b._\b4_\b._\b5_\b0 _\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be
Type: boolean
Default: no
- When sending messages with format=flowed by _\bs_\be_\bt_\bt_\bi_\bn_\bg the $text_flowed 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.
+ When sending messages with format=flowed by _\bs_\be_\bt_\bt_\bi_\bn_\bg the _\b$_\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd (section
+ 7.4.322 , page 167) variable, this variable specifies whether to also set the
+ 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 $text_flowed is
- _\bs_\be_\bt) but not on incomming.
+ N\bNo\bot\bte\be:\b: this variable only has an effect on _\bo_\bu_\bt_\bg_\bo_\bi_\bn_\bg messages (if _\b$_\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
+ (section 7.4.322 , page 167) is _\bs_\be_\bt) but not on incomming.
- _\b7_\b._\b4_\b._\b5_\b0 _\bd_\be_\bl_\be_\bt_\be_\b__\bu_\bn_\bt_\ba_\bg
+ _\b7_\b._\b4_\b._\b5_\b1 _\bd_\be_\bl_\be_\bt_\be_\b__\bu_\bn_\bt_\ba_\bg
Type: boolean
tion. This applies when you either explicitly delete a message, or when you
save it to another folder.
- _\b7_\b._\b4_\b._\b5_\b1 _\bd_\bi_\bg_\be_\bs_\bt_\b__\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be
+ _\b7_\b._\b4_\b._\b5_\b2 _\bd_\bi_\bg_\be_\bs_\bt_\b__\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be
Type: boolean
+ The Mutt Next Generation E-Mail Client 100
+
Default: yes
If this option is _\bs_\be_\bt, Mutt-ng's received-attachments menu will not show the
subparts of individual messages in a multipart/digest. To see these subparts,
press 'v' on that menu.
- _\b7_\b._\b4_\b._\b5_\b2 _\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br
-
- The Mutt Next Generation E-Mail Client 99
+ _\b7_\b._\b4_\b._\b5_\b3 _\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br
Type: path
Default: ''
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.52 ,
- page 98), and the filtered message is read from the standard output.
+ viewed it is passed as standard input to _\b$_\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br (section 7.4.53 ,
+ page 100), and the filtered message is read from the standard output.
- _\b7_\b._\b4_\b._\b5_\b3 _\bd_\bo_\bt_\bl_\bo_\bc_\bk_\b__\bp_\br_\bo_\bg_\br_\ba_\bm
+ _\b7_\b._\b4_\b._\b5_\b4 _\bd_\bo_\bt_\bl_\bo_\bc_\bk_\b__\bp_\br_\bo_\bg_\br_\ba_\bm
Type: path
Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
- _\b7_\b._\b4_\b._\b5_\b4 _\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by
+ _\b7_\b._\b4_\b._\b5_\b5 _\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by
Type: string
Example: set dsn_notify='failure,delay'
- _\b7_\b._\b4_\b._\b5_\b5 _\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn
+ _\b7_\b._\b4_\b._\b5_\b6 _\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn
Type: string
This variable controls how much of your message is returned in DSN messages.
It may be set to either _\bh_\bd_\br_\bs to return just the message header, or _\bf_\bu_\bl_\bl to
+
+ The Mutt Next Generation E-Mail Client 101
+
return the full message.
Example: set dsn_return=hdrs
- _\b7_\b._\b4_\b._\b5_\b6 _\bd_\bu_\bp_\bl_\bi_\bc_\ba_\bt_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
+ _\b7_\b._\b4_\b._\b5_\b7 _\bd_\bu_\bp_\bl_\bi_\bc_\ba_\bt_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
Type: boolean
- The Mutt Next Generation E-Mail Client 100
-
Default: yes
This variable controls whether Mutt-ng, when sorting by threads, threads mes-
indicate that it thinks they are duplicates of each other with an equals sign
in the thread diagram.
- _\b7_\b._\b4_\b._\b5_\b7 _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b5_\b8 _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs
Type: boolean
This option allows you to edit the header of your outgoing messages along with
the body of your message.
- _\b7_\b._\b4_\b._\b5_\b8 _\be_\bd_\bi_\bt_\bo_\br
+ _\b7_\b._\b4_\b._\b5_\b9 _\be_\bd_\bi_\bt_\bo_\br
Type: path
value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
if neither of those are set.
- _\b7_\b._\b4_\b._\b5_\b9 _\be_\bn_\bc_\bo_\bd_\be_\b__\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b6_\b0 _\be_\bn_\bc_\bo_\bd_\be_\b__\bf_\br_\bo_\bm
Type: boolean
Alternatively, you must take care of space-stuffing <tt/From / lines (with a
trailing space) yourself.
- _\b7_\b._\b4_\b._\b6_\b0 _\be_\bn_\bt_\br_\bo_\bp_\by_\b__\bf_\bi_\bl_\be
+ _\b7_\b._\b4_\b._\b6_\b1 _\be_\bn_\bt_\br_\bo_\bp_\by_\b__\bf_\bi_\bl_\be
Type: path
+ The Mutt Next Generation E-Mail Client 102
+
Default: ''
Availability: SSL
The file which includes random data that is used to initialize SSL library
functions.
- The Mutt Next Generation E-Mail Client 101
-
- _\b7_\b._\b4_\b._\b6_\b1 _\be_\bn_\bv_\be_\bl_\bo_\bp_\be_\b__\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b6_\b2 _\be_\bn_\bv_\be_\bl_\bo_\bp_\be_\b__\bf_\br_\bo_\bm
Type: boolean
When _\bs_\be_\bt, Mutt-ng will try to derive the message's _\be_\bn_\bv_\be_\bl_\bo_\bp_\be sender from the
``From:'' header field. Note that this information is passed to the sendmail
command using the ``-f' command line switch, so don't set this option if you
- are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.251 , page 147) yourself, or
+ are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.252 , page 148) yourself, or
if the sendmail on your machine doesn't support that command line switch.
- _\b7_\b._\b4_\b._\b6_\b2 _\be_\bs_\bc_\ba_\bp_\be
+ _\b7_\b._\b4_\b._\b6_\b3 _\be_\bs_\bc_\ba_\bp_\be
Type: string
Escape character to use for functions in the builtin editor.
- _\b7_\b._\b4_\b._\b6_\b3 _\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by
+ _\b7_\b._\b4_\b._\b6_\b4 _\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by
Type: boolean
ing to messages, and the initial prompt for subject is skipped when forwarding
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.19 , page
- 91)'' variable is _\bs_\be_\bt.
+ N\bNo\bot\bte\be:\b: this variable has no effect when the ``_\b$_\ba_\bu_\bt_\bo_\be_\bd_\bi_\bt (section 7.4.20 , page
+ 92)'' variable is _\bs_\be_\bt.
- _\b7_\b._\b4_\b._\b6_\b4 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
+ _\b7_\b._\b4_\b._\b6_\b5 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
Type: boolean
This variable controls whether or not attachments on outgoing messages are
saved along with the main body of your message.
- _\b7_\b._\b4_\b._\b6_\b5 _\bf_\bc_\bc_\b__\bc_\bl_\be_\ba_\br
+ _\b7_\b._\b4_\b._\b6_\b6 _\bf_\bc_\bc_\b__\bc_\bl_\be_\ba_\br
Type: boolean
Default: no
+ The Mutt Next Generation E-Mail Client 103
+
When this variable is _\bs_\be_\bt, FCCs will be stored unencrypted and unsigned, even
when the actual message is encrypted and/or signed. (PGP only)
- _\b7_\b._\b4_\b._\b6_\b6 _\bf_\bi_\bl_\be_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b6_\b7 _\bf_\bi_\bl_\be_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
- The Mutt Next Generation E-Mail Client 102
-
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.26 , page 93) value will
+ file attatchments. If _\bu_\bn_\bs_\be_\bt, _\b$_\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.27 , page 94) value will
be used instead. For example, the following configuration would work for
Japanese text handling:
Note: ``iso-2022-*'' must be put at the head of the value as shown above if
included.
- _\b7_\b._\b4_\b._\b6_\b7 _\bf_\bo_\bl_\bd_\be_\br
+ _\b7_\b._\b4_\b._\b6_\b8 _\bf_\bo_\bl_\bd_\be_\br
Type: path
that the assignment occurs _\bb_\be_\bf_\bo_\br_\be you use ``+'' or ``='' for any other vari-
ables since expansion takes place during the ``set'' command.
- _\b7_\b._\b4_\b._\b6_\b8 _\bf_\bo_\bl_\bd_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b6_\b9 _\bf_\bo_\bl_\bd_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
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.113 , page
- 113)'', but has its own set of printf(3)-like sequences:
+ taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page
+ 114)'', but has its own set of printf(3)-like sequences:
%C
current file number
%F
file permissions
+ The Mutt Next Generation E-Mail Client 104
+
%g
group name (or numeric gid, if missing)
%N
N if folder has new mail, blank otherwise
- The Mutt Next Generation E-Mail Client 103
-
%s
size in bytes
%|X
pad to the end of the line with character 'X'
- _\b7_\b._\b4_\b._\b6_\b9 _\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b7_\b0 _\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
Type: boolean
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.12 , page 33)'' commands or detected by common mailing list headers.
+ 3.13 , page 34)'' 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
a subscribed list will be sent to both the list and your address, resulting in
two copies of the same email for you.
- _\b7_\b._\b4_\b._\b7_\b0 _\bf_\bo_\br_\bc_\be_\b__\bb_\bu_\bf_\bf_\by_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b7_\b1 _\bf_\bo_\br_\bc_\be_\b__\bb_\bu_\bf_\bf_\by_\b__\bc_\bh_\be_\bc_\bk
Type: boolean
is invoked. When _\bu_\bn_\bs_\be_\bt, _\bb_\bu_\bf_\bf_\by_\b__\bl_\bi_\bs_\bt will just list all mailboxes which are
already known to have new mail.
- Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.325 , page 166)'',
- ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.118 , page 116)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 7.4.102 , page 110)''.
+ The Mutt Next Generation E-Mail Client 105
+
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.326 , page 168)'',
+ ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.119 , page 117)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
+ 7.4.103 , page 111)''.
- _\b7_\b._\b4_\b._\b7_\b1 _\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b7_\b2 _\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 104
-
- This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.245 , page 146)'',
+ This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 147)'',
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.234 , page 143)'' variable.
+ Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144)'' variable.
- _\b7_\b._\b4_\b._\b7_\b2 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
Controls the decoding of complex MIME messages into text/plain when forwarding
a message. The message header is also RFC2047 decoded. This variable is only
- used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.140 , page 120)'' 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.141 , page 121)'' is used instead.
+ used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bu_\bn_\bs_\be_\bt, otherwise
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 122)'' is used instead.
- _\b7_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
+ _\b7_\b._\b4_\b._\b7_\b4 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
Type: boolean
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.140 , page 120)'' 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.141 , page 121)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
+ if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 122)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
- _\b7_\b._\b4_\b._\b7_\b4 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
+ _\b7_\b._\b4_\b._\b7_\b5 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
Type: quadoption
editor when forwarding messages. For those who always want to forward with no
modification, use a setting of _\bn_\bo.
- _\b7_\b._\b4_\b._\b7_\b5 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b7_\b6 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
Default: '[%a: %s]'
+ The Mutt Next Generation E-Mail Client 106
+
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.113 , page
- 113)'' variable.
+ the same format sequences as the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page
+ 114)'' variable.
- _\b7_\b._\b4_\b._\b7_\b6 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
+ _\b7_\b._\b4_\b._\b7_\b7 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 105
-
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.140 , page 120)'' 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.112 , page 113)''.
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bu_\bn_\bs_\be_\bt) will be quoted using
+ ``_\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 114)''.
- _\b7_\b._\b4_\b._\b7_\b7 _\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b7_\b8 _\bf_\br_\bo_\bm
Type: e-mail address
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.240 , page
- 145)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.334 , page
- 168)'' 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.241 , page
+ 146)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.335 , page
+ 170)'' is unset.
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
Defaults to the contents of the environment variable $EMAIL.
- _\b7_\b._\b4_\b._\b7_\b8 _\bg_\be_\bc_\bo_\bs_\b__\bm_\ba_\bs_\bk
+ _\b7_\b._\b4_\b._\b7_\b9 _\bg_\be_\bc_\bo_\bs_\b__\bm_\ba_\bs_\bk
Type: regular expression
expression that will match the whole name so Mutt-ng will expand ``Franklin''
to ``Franklin, Steve''.
- _\b7_\b._\b4_\b._\b7_\b9 _\bh_\bd_\br_\bs
+ _\b7_\b._\b4_\b._\b8_\b0 _\bh_\bd_\br_\bs
Type: boolean
Default: yes
- When _\bu_\bn_\bs_\be_\bt, the header fields normally added by the ``_\bm_\by_\b__\bh_\bd_\br (section 3.15 ,
- page 35)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
+ The Mutt Next Generation E-Mail Client 107
+
+ When _\bu_\bn_\bs_\be_\bt, the header fields normally added by the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 ,
+ page 36)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
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.
- _\b7_\b._\b4_\b._\b8_\b0 _\bh_\be_\ba_\bd_\be_\br
+ _\b7_\b._\b4_\b._\b8_\b1 _\bh_\be_\ba_\bd_\be_\br
Type: boolean
- The Mutt Next Generation E-Mail Client 106
-
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.340 , page
- 170)'' setting applies.
+ 171)'' setting applies.
- _\b7_\b._\b4_\b._\b8_\b1 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be
+ _\b7_\b._\b4_\b._\b8_\b2 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be
Type: path
Availability: Header Cache
- The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.81 , page 106) variable points to the header
+ The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.82 , page 107) variable points to the header
cache database.
- If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.81 , page 106) points to a directory it will
+ If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.82 , page 107) 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.81 , page 106) points to a file that file will be a single global header
+ 7.4.82 , page 107) 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_\b2 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bc_\bo_\bm_\bp_\br_\be_\bs_\bs
+ _\b7_\b._\b4_\b._\b8_\b3 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be_\b__\bc_\bo_\bm_\bp_\br_\be_\bs_\bs
Type: boolean
diskspace is used, but the uncompression can result in a slower open of the
cached folder.
- _\b7_\b._\b4_\b._\b8_\b3 _\bh_\be_\bl_\bp
+ _\b7_\b._\b4_\b._\b8_\b4 _\bh_\be_\bl_\bp
Type: boolean
N\bNo\bot\bte\be:\b: The binding will not be displayed correctly if the function is bound to a
sequence rather than a single keystroke. Also, the help line may not be
updated if a binding is changed while Mutt-ng is running. Since this variable
- is primarily aimed at new users, neither of these should present a major prob-
- lem.
+ is primarily aimed at new users, neither of these should present a major
+
+ The Mutt Next Generation E-Mail Client 108
+
+ problem.
- _\b7_\b._\b4_\b._\b8_\b4 _\bh_\bi_\bd_\bd_\be_\bn_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b8_\b5 _\bh_\bi_\bd_\bd_\be_\bn_\b__\bh_\bo_\bs_\bt
Type: boolean
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
-
- The Mutt Next Generation E-Mail Client 107
-
- 7.4.92 , page 108)'' variable when adding the domain part to addresses. This
+ 7.4.93 , page 109)'' 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_\b5 _\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b8_\b6 _\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng will not show the presence of messages that are hidden by
limiting, in the thread tree.
- _\b7_\b._\b4_\b._\b8_\b6 _\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b8_\b7 _\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
Type: boolean
When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages in the thread
tree.
- _\b7_\b._\b4_\b._\b8_\b7 _\bh_\bi_\bd_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b8_\b8 _\bh_\bi_\bd_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
Type: boolean
When _\bs_\be_\bt, Mutt-ng will not show the subject of messages in the thread tree that
have the same subject as their parent or closest previously displayed sibling.
- _\b7_\b._\b4_\b._\b8_\b8 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b8_\b9 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
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.86 , page 107) is set, this option will have no effect.
+ _\bi_\bn_\bg (section 7.4.87 , page 108) is set, this option will have no effect.
- _\b7_\b._\b4_\b._\b8_\b9 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b9_\b0 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
Type: boolean
+ The Mutt Next Generation E-Mail Client 109
+
Default: yes
When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages at the top of
- threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd (section 7.4.85 ,
- page 107) is _\bs_\be_\bt, this option will have no effect.
+ threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd (section 7.4.86 ,
+ page 108) is _\bs_\be_\bt, this option will have no effect.
- _\b7_\b._\b4_\b._\b9_\b0 _\bh_\bi_\bs_\bt_\bo_\br_\by
+ _\b7_\b._\b4_\b._\b9_\b1 _\bh_\bi_\bs_\bt_\bo_\br_\by
Type: number
- The Mutt Next Generation E-Mail Client 108
-
Default: 10
This variable controls the size (in number of strings remembered) of the string
history buffer. The buffer is cleared each time the variable is changed.
- _\b7_\b._\b4_\b._\b9_\b1 _\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b9_\b2 _\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
Type: quadoption
This variable controls whether or not a Mail-Followup-To: header field is hon-
ored when group-replying to a message.
- _\b7_\b._\b4_\b._\b9_\b2 _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b9_\b3 _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be
Type: string
Please be sure to really know what you are doing when changing this variable to
configure a custom domain part of Message-IDs.
- _\b7_\b._\b4_\b._\b9_\b3 _\bi_\bg_\bn_\bo_\br_\be_\b__\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b9_\b4 _\bi_\bg_\bn_\bo_\br_\be_\b__\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by_\b__\bt_\bo
Type: boolean
option is set, use the _\bl_\bi_\bs_\bt_\b-_\br_\be_\bp_\bl_\by function; _\bg_\br_\bo_\bu_\bp_\b-_\br_\be_\bp_\bl_\by will reply to both the
sender and the list.
- _\b7_\b._\b4_\b._\b9_\b4 _\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
+ _\b7_\b._\b4_\b._\b9_\b5 _\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
Type: string
+ The Mutt Next Generation E-Mail Client 110
+
Default: ''
Availability: IMAP
capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
eter is case-insensitive.
- The Mutt Next Generation E-Mail Client 109
-
If this parameter is _\bu_\bn_\bs_\be_\bt (the default) Mutt-ng will try all available meth-
ods, in order from most-secure to least-secure.
ous methods are unavailable. If a method is available but authentication fails,
Mutt-ng will not connect to the IMAP server.
- _\b7_\b._\b4_\b._\b9_\b5 _\bi_\bm_\ba_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
+ _\b7_\b._\b4_\b._\b9_\b6 _\bi_\bm_\ba_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
Type: boolean
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.14 , page 34)'' command.
+ also the ``_\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.15 , page 36)'' command.
- _\b7_\b._\b4_\b._\b9_\b6 _\bi_\bm_\ba_\bp_\b__\bd_\be_\bl_\bi_\bm_\b__\bc_\bh_\ba_\br_\bs
+ _\b7_\b._\b4_\b._\b9_\b7 _\bi_\bm_\ba_\bp_\b__\bd_\be_\bl_\bi_\bm_\b__\bc_\bh_\ba_\br_\bs
Type: string
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.67 , page 102) variable.
+ shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 , page 103) variable.
- _\b7_\b._\b4_\b._\b9_\b7 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b9_\b8 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
Type: string
REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
``index'' menu. You may want to add more headers for spam detection.
+ The Mutt Next Generation E-Mail Client 111
+
N\bNo\bot\bte\be:\b: This is a space separated list.
- _\b7_\b._\b4_\b._\b9_\b8 _\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be
+ _\b7_\b._\b4_\b._\b9_\b9 _\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be
Type: string
Availability: IMAP
- The Mutt Next Generation E-Mail Client 110
-
You normally want to see your personal folders alongside your INBOX in the IMAP
browser. If you see something else, you may set this variable to the IMAP path
to your folders.
- _\b7_\b._\b4_\b._\b9_\b9 _\bi_\bm_\ba_\bp_\b__\bk_\be_\be_\bp_\ba_\bl_\bi_\bv_\be
+ _\b7_\b._\b4_\b._\b1_\b0_\b0 _\bi_\bm_\ba_\bp_\b__\bk_\be_\be_\bp_\ba_\bl_\bi_\bv_\be
Type: number
Reduce this number if you find yourself getting disconnected from your IMAP
server due to inactivity.
- _\b7_\b._\b4_\b._\b1_\b0_\b0 _\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b0_\b1 _\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
Type: boolean
scribed folders or all folders. This can be toggled in the IMAP browser with
the _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd function.
- _\b7_\b._\b4_\b._\b1_\b0_\b1 _\bi_\bm_\ba_\bp_\b__\bl_\bo_\bg_\bi_\bn
+ _\b7_\b._\b4_\b._\b1_\b0_\b2 _\bi_\bm_\ba_\bp_\b__\bl_\bo_\bg_\bi_\bn
Type: string
Your login name on the IMAP server.
- This variable defaults to the value of ``_\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.108 , page
- 112).''
+ The Mutt Next Generation E-Mail Client 112
+
+ This variable defaults to the value of ``_\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.109 , page
+ 113).''
- _\b7_\b._\b4_\b._\b1_\b0_\b2 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b1_\b0_\b3 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
Default: 300
- The Mutt Next Generation E-Mail Client 111
-
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.118 ,
- page 116)'' variable to generate less traffic and get more accurate information
+ mail in IMAP folders. This is split from the ``_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.119 ,
+ page 117)'' variable to generate less traffic and get more accurate information
for local folders.
- _\b7_\b._\b4_\b._\b1_\b0_\b3 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b1_\b0_\b4 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
Type: string
machine, because the superuser can read your configuration even if you are the
only one who can read the file.
- _\b7_\b._\b4_\b._\b1_\b0_\b4 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs_\bi_\bv_\be
+ _\b7_\b._\b4_\b._\b1_\b0_\b5 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs_\bi_\bv_\be
Type: boolean
useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
cation, or if opening the connection is slow.
- _\b7_\b._\b4_\b._\b1_\b0_\b5 _\bi_\bm_\ba_\bp_\b__\bp_\be_\be_\bk
+ _\b7_\b._\b4_\b._\b1_\b0_\b6 _\bi_\bm_\ba_\bp_\b__\bp_\be_\be_\bk
Type: boolean
closing an IMAP folder somewhat slower. This option exists to appease speed
freaks.
- _\b7_\b._\b4_\b._\b1_\b0_\b6 _\bi_\bm_\ba_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ The Mutt Next Generation E-Mail Client 113
+
+ _\b7_\b._\b4_\b._\b1_\b0_\b7 _\bi_\bm_\ba_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
Type: quadoption
Availability: IMAP
- The Mutt Next Generation E-Mail Client 112
-
Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
connection is lost.
- _\b7_\b._\b4_\b._\b1_\b0_\b7 _\bi_\bm_\ba_\bp_\b__\bs_\be_\br_\bv_\be_\br_\bn_\bo_\bi_\bs_\be
+ _\b7_\b._\b4_\b._\b1_\b0_\b8 _\bi_\bm_\ba_\bp_\b__\bs_\be_\br_\bv_\be_\br_\bn_\bo_\bi_\bs_\be
Type: boolean
ration problems on the server which are out of the users' hands, you may wish
to suppress them at some point.
- _\b7_\b._\b4_\b._\b1_\b0_\b8 _\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b0_\b9 _\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br
Type: string
This variable defaults to your user name on the local machine.
- _\b7_\b._\b4_\b._\b1_\b0_\b9 _\bi_\bm_\bp_\bl_\bi_\bc_\bi_\bt_\b__\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw
+ _\b7_\b._\b4_\b._\b1_\b1_\b0 _\bi_\bm_\bp_\bl_\bi_\bc_\bi_\bt_\b__\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw
Type: boolean
If such an entry is found, Mutt-ng will use the viewer defined in that entry to
convert the body part to text form.
- _\b7_\b._\b4_\b._\b1_\b1_\b0 _\bi_\bn_\bc_\bl_\bu_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b1_\b1 _\bi_\bn_\bc_\bl_\bu_\bd_\be
Type: quadoption
Default: ask-yes
Controls whether or not a copy of the message(s) you are replying to is
+
+ The Mutt Next Generation E-Mail Client 114
+
included in your reply.
- _\b7_\b._\b4_\b._\b1_\b1_\b1 _\bi_\bn_\bc_\bl_\bu_\bd_\be_\b__\bo_\bn_\bl_\by_\bf_\bi_\br_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b1_\b2 _\bi_\bn_\bc_\bl_\bu_\bd_\be_\b__\bo_\bn_\bl_\by_\bf_\bi_\br_\bs_\bt
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 113
-
Controls whether or not Mutt-ng includes only the first attachment of the mes-
sage you are replying.
- _\b7_\b._\b4_\b._\b1_\b1_\b2 _\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b1_\b1_\b3 _\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
Type: string
which you are replying. You are strongly encouraged not to change this value,
as it tends to agitate the more fanatical netizens.
- _\b7_\b._\b4_\b._\b1_\b1_\b3 _\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b1_\b4 _\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%C
current message number
+ The Mutt Next Generation E-Mail Client 115
+
%d
date and time of the message in the format specified by ``date_for-
mat'' converted to sender's time zone
date and time of the message in the format specified by ``date_for-
mat'' converted to the local time zone
- The Mutt Next Generation E-Mail Client 114
-
%e
current message number in thread
(_O_riginal save folder) Where Mutt-ng would formerly have stashed
the message: list name or recipient name if no list
+ The Mutt Next Generation E-Mail Client 116
+
%s
subject of the message
%t
`to:' field (recipients)
- The Mutt Next Generation E-Mail Client 115
-
%T
- the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.327 ,
- page 167) string
+ the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 ,
+ page 168) string
%u
user (login) name of the author
the current local time. ``fmt'' is expanded by the library function
``strftime''; a leading bang disables locales.
+ The Mutt Next Generation E-Mail Client 117
+
%>X
right justify the rest of the string and pad with character 'X'
%|X
pad to the end of the line with character 'X'
- See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.327 , page 167)''.
-
- _\b7_\b._\b4_\b._\b1_\b1_\b4 _\bi_\bs_\bp_\be_\bl_\bl
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.328 , page 168)''.
- The Mutt Next Generation E-Mail Client 116
+ _\b7_\b._\b4_\b._\b1_\b1_\b5 _\bi_\bs_\bp_\be_\bl_\bl
Type: path
How to invoke ispell (GNU's spell-checking software).
- _\b7_\b._\b4_\b._\b1_\b1_\b5 _\bk_\be_\be_\bp_\b__\bf_\bl_\ba_\bg_\bg_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b1_\b6 _\bk_\be_\be_\bp_\b__\bf_\bl_\ba_\bg_\bg_\be_\bd
Type: boolean
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.128 , page 118)'' mailbox, or as a result of
- a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34)'' command.
+ box to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 119)'' mailbox, or as a result of
+ a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35)'' command.
- _\b7_\b._\b4_\b._\b1_\b1_\b6 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
+ _\b7_\b._\b4_\b._\b1_\b1_\b7 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
Type: quadoption
(instead to the author only). Setting this option to ``_\ba_\bs_\bk_\b-_\by_\be_\bs'' or ``_\ba_\bs_\bk_\b-_\bn_\bo''
will ask if you really intended to reply to the author only.
- _\b7_\b._\b4_\b._\b1_\b1_\b7 _\bl_\bo_\bc_\ba_\bl_\be
+ _\b7_\b._\b4_\b._\b1_\b1_\b8 _\bl_\bo_\bc_\ba_\bl_\be
Type: string
The locale used by strftime(3) to format dates. Legal values are the strings
your system accepts for the locale variable LC_TIME.
- _\b7_\b._\b4_\b._\b1_\b1_\b8 _\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b1_\b1_\b9 _\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
This variable configures how often (in seconds) Mutt-ng should look for new
mail.
+ The Mutt Next Generation E-Mail Client 118
+
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.102 , page 110).
+ 7.4.103 , page 111).
- _\b7_\b._\b4_\b._\b1_\b1_\b9 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
+ _\b7_\b._\b4_\b._\b1_\b2_\b0 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
Type: string
Default: ''
This variable specifies which files to consult when attempting to display MIME
-
- The Mutt Next Generation E-Mail Client 117
-
bodies not directly supported by Mutt-ng.
- _\b7_\b._\b4_\b._\b1_\b2_\b0 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be
+ _\b7_\b._\b4_\b._\b1_\b2_\b1 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be
Type: boolean
D\bDO\bON\bN'\b'T\bT C\bCH\bHA\bAN\bNG\bGE\bE T\bTH\bHI\bIS\bS S\bSE\bET\bTT\bTI\bIN\bNG\bG U\bUN\bNL\bLE\bES\bSS\bS Y\bYO\bOU\bU A\bAR\bRE\bE R\bRE\bEA\bAL\bLL\bLY\bY S\bSU\bUR\bRE\bE W\bWH\bHA\bAT\bT Y\bYO\bOU\bU A\bAR\bRE\bE D\bDO\bOI\bIN\bNG\bG!\b!
- _\b7_\b._\b4_\b._\b1_\b2_\b1 _\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
+ _\b7_\b._\b4_\b._\b1_\b2_\b2 _\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
Type: boolean
files when the header cache is in use. This incurs one stat(2) per message
every time the folder is opened.
- _\b7_\b._\b4_\b._\b1_\b2_\b2 _\bm_\ba_\bi_\bl_\bd_\bi_\br_\b__\bt_\br_\ba_\bs_\bh
+ _\b7_\b._\b4_\b._\b1_\b2_\b3 _\bm_\ba_\bi_\bl_\bd_\bi_\br_\b__\bt_\br_\ba_\bs_\bh
Type: boolean
It is similiar to the trash option.
- _\b7_\b._\b4_\b._\b1_\b2_\b3 _\bm_\ba_\br_\bk_\b__\bo_\bl_\bd
+ _\b7_\b._\b4_\b._\b1_\b2_\b4 _\bm_\ba_\br_\bk_\b__\bo_\bl_\bd
Type: boolean
+ The Mutt Next Generation E-Mail Client 119
+
Default: yes
Controls whether or not Mutt-ng marks _\bn_\be_\bw u\bun\bnr\bre\bea\bad\bd messages as _\bo_\bl_\bd if you exit a
up with an 'O' next to them in the ``index'' menu, indicating that they are
old.
- The Mutt Next Generation E-Mail Client 118
-
- _\b7_\b._\b4_\b._\b1_\b2_\b4 _\bm_\ba_\br_\bk_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b1_\b2_\b5 _\bm_\ba_\br_\bk_\be_\br_\bs
Type: boolean
Controls the display of wrapped lines in the internal pager. If set, a ``+''
marker is displayed at the beginning of wrapped lines. Also see the
- ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 7.4.267 , page 151)'' variable.
+ ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 7.4.268 , page 152)'' variable.
- _\b7_\b._\b4_\b._\b1_\b2_\b5 _\bm_\ba_\bs_\bk
+ _\b7_\b._\b4_\b._\b1_\b2_\b6 _\bm_\ba_\bs_\bk
Type: regular expression
operator ``!''. Only files whose names match this mask will be shown. The
match is always case-sensitive.
- _\b7_\b._\b4_\b._\b1_\b2_\b6 _\bm_\ba_\bx_\b__\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\br_\be_\bc_\bi_\bp_\bs
+ _\b7_\b._\b4_\b._\b1_\b2_\b7 _\bm_\ba_\bx_\b__\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\br_\be_\bc_\bi_\bp_\bs
Type: number
case the number of lines exeeds its value, the last line will have 3 dots
appended.
- _\b7_\b._\b4_\b._\b1_\b2_\b7 _\bm_\ba_\bx_\b__\bl_\bi_\bn_\be_\b__\bl_\be_\bn_\bg_\bt_\bh
+ _\b7_\b._\b4_\b._\b1_\b2_\b8 _\bm_\ba_\bx_\b__\bl_\bi_\bn_\be_\b__\bl_\be_\bn_\bg_\bt_\bh
Type: number
When _\bs_\be_\bt, the maximum line length for displaying ``format = flowed'' messages
is limited to this length. A value of 0 (which is also the default) means that
the maximum line length is determined by the terminal width and _\b$_\bw_\br_\ba_\bp_\bm_\ba_\br_\bg_\bi_\bn
- (section 7.4.342 , page 170).
+ (section 7.4.342 , page 171).
- _\b7_\b._\b4_\b._\b1_\b2_\b8 _\bm_\bb_\bo_\bx
+ _\b7_\b._\b4_\b._\b1_\b2_\b9 _\bm_\bb_\bo_\bx
Type: path
+ The Mutt Next Generation E-Mail Client 120
+
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.301 , page 159)'' folder will be appended.
+ 7.4.302 , page 160)'' folder will be appended.
- _\b7_\b._\b4_\b._\b1_\b2_\b9 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
+ _\b7_\b._\b4_\b._\b1_\b3_\b0 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
Type: folder magic
- The Mutt Next Generation E-Mail Client 119
-
Default: mbox
The default mailbox type used when creating new folders. May be any of mbox,
MMDF, MH and Maildir.
- _\b7_\b._\b4_\b._\b1_\b3_\b0 _\bm_\be_\bn_\bu_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b3_\b1 _\bm_\be_\bn_\bu_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
Type: number
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.171 , page
- 129)''.)
+ scrolling through menus. (Similar to ``_\b$_\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.172 , page
+ 130)''.)
- _\b7_\b._\b4_\b._\b1_\b3_\b1 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
+ _\b7_\b._\b4_\b._\b1_\b3_\b2 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
Type: boolean
the screen, unless there are less entries than lines. When _\bs_\be_\bt, the bottom
entry may move off the bottom.
- _\b7_\b._\b4_\b._\b1_\b3_\b2 _\bm_\be_\bn_\bu_\b__\bs_\bc_\br_\bo_\bl_\bl
+ _\b7_\b._\b4_\b._\b1_\b3_\b3 _\bm_\be_\bn_\bu_\b__\bs_\bc_\br_\bo_\bl_\bl
Type: boolean
vious page of the menu is displayed (useful for slow links to avoid many
redraws).
- _\b7_\b._\b4_\b._\b1_\b3_\b3 _\bm_\be_\bs_\bs_\ba_\bg_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b3_\b4 _\bm_\be_\bs_\bs_\ba_\bg_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
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.113 , page 113)''.
+ section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)''.
+
+ The Mutt Next Generation E-Mail Client 121
- _\b7_\b._\b4_\b._\b1_\b3_\b4 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
+ _\b7_\b._\b4_\b._\b1_\b3_\b5 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
Type: boolean
If _\bs_\be_\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
if the user had pressed the ESC key and whatever key remains after having the
-
- The Mutt Next Generation E-Mail Client 120
-
high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
then this is treated as if the user had pressed ESC then ``x''. This is
because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
the ASCII character ``x''.
- _\b7_\b._\b4_\b._\b1_\b3_\b5 _\bm_\be_\bt_\bo_\bo
+ _\b7_\b._\b4_\b._\b1_\b3_\b6 _\bm_\be_\bt_\bo_\bo
Type: boolean
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.
- _\b7_\b._\b4_\b._\b1_\b3_\b6 _\bm_\bh_\b__\bp_\bu_\br_\bg_\be
+ _\b7_\b._\b4_\b._\b1_\b3_\b7 _\bm_\bh_\b__\bp_\bu_\br_\bg_\be
Type: boolean
_\b,_\b<_\bo_\bl_\bd _\bf_\bi_\bl_\be _\bn_\ba_\bm_\be_\b> in mh folders instead of really deleting them. If the vari-
able is set, the message files will simply be deleted.
- _\b7_\b._\b4_\b._\b1_\b3_\b7 _\bm_\bh_\b__\bs_\be_\bq_\b__\bf_\bl_\ba_\bg_\bg_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b3_\b8 _\bm_\bh_\b__\bs_\be_\bq_\b__\bf_\bl_\ba_\bg_\bg_\be_\bd
Type: string
The name of the MH sequence used for flagged messages.
- _\b7_\b._\b4_\b._\b1_\b3_\b8 _\bm_\bh_\b__\bs_\be_\bq_\b__\br_\be_\bp_\bl_\bi_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b3_\b9 _\bm_\bh_\b__\bs_\be_\bq_\b__\br_\be_\bp_\bl_\bi_\be_\bd
Type: string
The name of the MH sequence used to tag replied messages.
- _\b7_\b._\b4_\b._\b1_\b3_\b9 _\bm_\bh_\b__\bs_\be_\bq_\b__\bu_\bn_\bs_\be_\be_\bn
+ _\b7_\b._\b4_\b._\b1_\b4_\b0 _\bm_\bh_\b__\bs_\be_\bq_\b__\bu_\bn_\bs_\be_\be_\bn
Type: string
Default: 'unseen'
+ The Mutt Next Generation E-Mail Client 122
+
The name of the MH sequence used for unseen messages.
- _\b7_\b._\b4_\b._\b1_\b4_\b0 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd
+ _\b7_\b._\b4_\b._\b1_\b4_\b1 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd
Type: quadoption
Default: no
- The Mutt Next Generation E-Mail Client 121
-
When _\bs_\be_\bt, the message you are forwarding will be attached as a separate MIME
part instead of included in the main body of the message.
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.72 , page 104)'' 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.141 , page 121)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.73 , page 105)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.142 , page 122)''.
- _\b7_\b._\b4_\b._\b1_\b4_\b1 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b4_\b2 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
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.140 , page 120)'' is _\bs_\be_\bt. Other-
- wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.72 , page 104)'' is used instead.
+ a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.141 , page 121)'' is _\bs_\be_\bt. Other-
+ wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.73 , page 105)'' is used instead.
- _\b7_\b._\b4_\b._\b1_\b4_\b2 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\br_\be_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b4_\b3 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\br_\be_\bs_\bt
Type: quadoption
menu, attachments which cannot be decoded in a reasonable manner will be
attached to the newly composed message if this option is set.
- _\b7_\b._\b4_\b._\b1_\b4_\b3 _\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b4_\b4 _\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%c
Remailer capabilities.
+ The Mutt Next Generation E-Mail Client 123
+
%s
The remailer's short name.
%a
The remailer's e-mail address.
- The Mutt Next Generation E-Mail Client 122
-
- _\b7_\b._\b4_\b._\b1_\b4_\b4 _\bm_\bi_\bx_\bm_\ba_\bs_\bt_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b4_\b5 _\bm_\bi_\bx_\bm_\ba_\bs_\bt_\be_\br
Type: path
used with various sets of parameters to gather the list of known remailers, and
to finally send a message through the mixmaster chain.
- _\b7_\b._\b4_\b._\b1_\b4_\b5 _\bm_\bo_\bv_\be
+ _\b7_\b._\b4_\b._\b1_\b4_\b6 _\bm_\bo_\bv_\be
Type: quadoption
Default: ask-no
Controls whether or not Mutt-ng will move read messages from your spool mailbox
- to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.128 , page 118)'' mailbox, or as a result of a
- ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34)'' command.
+ to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.129 , page 119)'' mailbox, or as a result of a
+ ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.14 , page 35)'' command.
- _\b7_\b._\b4_\b._\b1_\b4_\b6 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b4_\b7 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%O
the current UNIX timestamp (octal)
+ The Mutt Next Generation E-Mail Client 124
+
%p
the process ID
the current Message-ID prefix (a character rotating with every Mes-
sage-ID being generated)
- The Mutt Next Generation E-Mail Client 123
-
%r
a random integer value (decimal)
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_\b4_\b7 _\bn_\ba_\br_\br_\bo_\bw_\b__\bt_\br_\be_\be
+ _\b7_\b._\b4_\b._\b1_\b4_\b8 _\bn_\ba_\br_\br_\bo_\bw_\b__\bt_\br_\be_\be
Type: boolean
This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
threads to fit on the screen.
- _\b7_\b._\b4_\b._\b1_\b4_\b8 _\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_\b4_\b9 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
Type: boolean
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_\b4_\b9 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b1_\b5_\b0 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
Type: boolean
+ The Mutt Next Generation E-Mail Client 125
+
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.
- The Mutt Next Generation E-Mail Client 124
-
- _\b7_\b._\b4_\b._\b1_\b5_\b0 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br
+ _\b7_\b._\b4_\b._\b1_\b5_\b1 _\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.
- _\b7_\b._\b4_\b._\b1_\b5_\b1 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bt_\bc_\bh_\bu_\bp
+ _\b7_\b._\b4_\b._\b1_\b5_\b2 _\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_\b2 _\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b5_\b3 _\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.150 , page 123)) and how
+ caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 7.4.151 , page 125)) 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.152 ,
- page 124), 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.153 ,
+ page 125), all older ones will be removed/not shown in the index.
- _\b7_\b._\b4_\b._\b1_\b5_\b3 _\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_\b4 _\bn_\bn_\bt_\bp_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo_\b__\bp_\bo_\bs_\bt_\be_\br
Type: quadoption
Default: ask-yes
+ The Mutt Next Generation E-Mail Client 126
+
Availability: NNTP
If this variable is _\bs_\be_\bt and the keyword 'poster' is present in the Followup-To:
header field, a follow-up to the newsgroup is not permitted. The message will
be mailed to the submitter of the message via mail.
- The Mutt Next Generation E-Mail Client 125
-
- _\b7_\b._\b4_\b._\b1_\b5_\b4 _\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_\b5_\b5 _\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
Availability: NNTP
This variable allows you to customize the newsgroup browser display to your
- personal taste. This string is similar to ``_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.113 ,
- page 113)'', but has its own set of printf(3)-like sequences:
+ personal taste. This string is similar to ``_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 ,
+ page 114)'', but has its own set of printf(3)-like sequences:
%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_\b5 _\bn_\bn_\bt_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b5_\b6 _\bn_\bn_\bt_\bp_\b__\bh_\bo_\bs_\bt
Type: string
security risk since the superuser of your machine may read it regardless of the
file's permissions.
- _\b7_\b._\b4_\b._\b1_\b5_\b6 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
+ _\b7_\b._\b4_\b._\b1_\b5_\b7 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
+
+ The Mutt Next Generation E-Mail Client 127
Type: path
Availability: NNTP
- The Mutt Next Generation E-Mail Client 126
-
If _\bs_\be_\bt, specifies the program and arguments used to deliver news posted by
Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
lowing printf(3)-style sequence is understood:
Example: set inews='/usr/local/bin/inews -hS'
- _\b7_\b._\b4_\b._\b1_\b5_\b7 _\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_\b5_\b8 _\bn_\bn_\bt_\bp_\b__\bl_\bo_\ba_\bd_\b__\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn
Type: boolean
This variable controls whether or not descriptions for newsgroups are to be
loaded when subscribing to a newsgroup.
- _\b7_\b._\b4_\b._\b1_\b5_\b8 _\bn_\bn_\bt_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b1_\b5_\b9 _\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_\b5_\b9 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b0 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
Type: boolean
N\bNo\bot\bte\be:\b: Only change this setting if you know what you are doing.
- _\b7_\b._\b4_\b._\b1_\b6_\b0 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
+ _\b7_\b._\b4_\b._\b1_\b6_\b1 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
+
+ The Mutt Next Generation E-Mail Client 128
Type: path
Availability: NNTP
- The Mutt Next Generation E-Mail Client 127
-
This file contains information about subscribed newsgroup and articles read so
far.
%s newsserver name
- _\b7_\b._\b4_\b._\b1_\b6_\b1 _\bn_\bn_\bt_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b1_\b6_\b2 _\bn_\bn_\bt_\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._\b1_\b6_\b2 _\bn_\bn_\bt_\bp_\b__\bp_\bo_\bs_\bt_\b__\bm_\bo_\bd_\be_\br_\ba_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b6_\b3 _\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_\b3 _\bn_\bn_\bt_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b4 _\bn_\bn_\bt_\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 newsserver when the
was connection lost.
- _\b7_\b._\b4_\b._\b1_\b6_\b4 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
+ The Mutt Next Generation E-Mail Client 129
+
+ _\b7_\b._\b4_\b._\b1_\b6_\b5 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 128
-
Availability: NNTP
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_\b5 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bn_\be_\bw_\b__\bn_\be_\bw_\bs
+ _\b7_\b._\b4_\b._\b1_\b6_\b6 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bn_\be_\bw_\b__\bn_\be_\bw_\bs
Type: boolean
whether or not the number of new articles of subscribed newsgroups will be
checked.
- _\b7_\b._\b4_\b._\b1_\b6_\b6 _\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_\b6_\b7 _\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_\b6_\b7 _\bn_\bn_\bt_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b6_\b8 _\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_\b6_\b8 _\bn_\bn_\bt_\bp_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b1_\b6_\b9 _\bn_\bn_\bt_\bp_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
Type: boolean
Availability: NNTP
+ The Mutt Next Generation E-Mail Client 130
+
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_\b6_\b9 _\bo_\bp_\be_\br_\ba_\bt_\bi_\bn_\bg_\b__\bs_\by_\bs_\bt_\be_\bm
+ _\b7_\b._\b4_\b._\b1_\b7_\b0 _\bo_\bp_\be_\br_\ba_\bt_\bi_\bn_\bg_\b__\bs_\by_\bs_\bt_\be_\bm
Type: string
- The Mutt Next Generation E-Mail Client 129
-
Default: ''
This specifies the operating system name for the User-Agent: header field. If
It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
- _\b7_\b._\b4_\b._\b1_\b7_\b0 _\bp_\ba_\bg_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b7_\b1 _\bp_\ba_\bg_\be_\br
Type: path
screen resizes cause lines longer than the screen width to be badly formatted
in the help menu.
- _\b7_\b._\b4_\b._\b1_\b7_\b1 _\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b7_\b2 _\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_\b2 _\bp_\ba_\bg_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b7_\b3 _\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.113 , page 113)''
+ sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)''
section.
- _\b7_\b._\b4_\b._\b1_\b7_\b3 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
+ _\b7_\b._\b4_\b._\b1_\b7_\b4 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
+
+ The Mutt Next Generation E-Mail Client 131
Type: number
Determines the number of lines of a mini-index which is shown when in the
pager. The current message, unless near the top or bottom of the folder, will
be roughly one third of the way down this mini-index, giving the reader the
-
- The Mutt Next Generation E-Mail Client 130
-
context of a few messages before and after the message. This is useful, for
example, to determine how many messages remain to be read in the current
thread. One of the lines is reserved for the status bar from the index, so a
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_\b4 _\bp_\ba_\bg_\be_\br_\b__\bs_\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b1_\b7_\b5 _\bp_\ba_\bg_\be_\br_\b__\bs_\bt_\bo_\bp
Type: boolean
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_\b5 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b7_\b6 _\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_\b6 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\bi_\bn_\bl_\bi_\bn_\be
+ _\b7_\b._\b4_\b._\b1_\b7_\b7 _\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.192 , page 134)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.193 , page 135)''.
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_\b7_\b7 _\bp_\bg_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\be_\bx_\bi_\bt
+ The Mutt Next Generation E-Mail Client 132
+
+ _\b7_\b._\b4_\b._\b1_\b7_\b8 _\bp_\bg_\bp_\b__\bc_\bh_\be_\bc_\bk_\b__\be_\bx_\bi_\bt
Type: boolean
Default: yes
- The Mutt Next Generation E-Mail Client 131
-
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_\b7_\b8 _\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_\b7_\b9 _\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)
- _\b7_\b._\b4_\b._\b1_\b7_\b9 _\bp_\bg_\bp_\b__\bd_\be_\bc_\bo_\bd_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b8_\b0 _\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.196 , page 135).
+ The value of _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.197 , page 136).
%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_\b0 _\bp_\bg_\bp_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b8_\b1 _\bp_\bg_\bp_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+
+ The Mutt Next Generation E-Mail Client 133
Type: string
This command is used to decrypt a PGP encrypted message. (PGP only)
- The Mutt Next Generation E-Mail Client 132
-
- _\b7_\b._\b4_\b._\b1_\b8_\b1 _\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_\b8_\b2 _\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_\b2 _\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_\b8_\b3 _\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
This command is used to both sign and encrypt a body part. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b3 _\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b8_\b4 _\bp_\bg_\bp_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
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.113 , page
- 113)'', but has its own set of printf(3)-like sequences:
+ sonal taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page
+ 114)'', but has its own set of printf(3)-like sequences:
%n
number
%c
capabilities
+ The Mutt Next Generation E-Mail Client 134
+
%t
trust/validity of the key-uid association
(PGP only)
- The Mutt Next Generation E-Mail Client 133
-
- _\b7_\b._\b4_\b._\b1_\b8_\b4 _\bp_\bg_\bp_\b__\be_\bx_\bp_\bo_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b8_\b5 _\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_\b5 _\bp_\bg_\bp_\b__\bg_\be_\bt_\bk_\be_\by_\bs_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b8_\b6 _\bp_\bg_\bp_\b__\bg_\be_\bt_\bk_\be_\by_\bs_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
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_\b6 _\bp_\bg_\bp_\b__\bg_\bo_\bo_\bd_\b__\bs_\bi_\bg_\bn
+ _\b7_\b._\b4_\b._\b1_\b8_\b7 _\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.202 , page 136)
+ verified if the output from _\b$_\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.203 , page 137)
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_\b8_\b7 _\bp_\bg_\bp_\b__\bi_\bg_\bn_\bo_\br_\be_\b__\bs_\bu_\bb_\bk_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b1_\b8_\b8 _\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_\b8_\b8 _\bp_\bg_\bp_\b__\bi_\bm_\bp_\bo_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b8_\b9 _\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 135
+
ring. (PGP only)
- _\b7_\b._\b4_\b._\b1_\b8_\b9 _\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._\b1_\b9_\b0 _\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
Default: ''
- The Mutt Next Generation E-Mail Client 134
-
This command is used to list the public key ring's contents. The output format
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_\b0 _\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._\b1_\b9_\b1 _\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
This format is also generated by the pgpring utility which comes with Mutt-ng.
(PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b1 _\bp_\bg_\bp_\b__\bl_\bo_\bn_\bg_\b__\bi_\bd_\bs
+ _\b7_\b._\b4_\b._\b1_\b9_\b2 _\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_\b2 _\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo
+ _\b7_\b._\b4_\b._\b1_\b9_\b3 _\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_\b3 _\bp_\bg_\bp_\b__\br_\be_\bp_\bl_\by_\bi_\bn_\bl_\bi_\bn_\be
+ _\b7_\b._\b4_\b._\b1_\b9_\b4 _\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 136
+
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
checked/flagged messages.
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
-
- The Mutt Next Generation E-Mail Client 135
-
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.192 , page 134)''.
+ ``_\b$_\bp_\bg_\bp_\b__\bm_\bi_\bm_\be_\b__\ba_\bu_\bt_\bo (section 7.4.193 , page 135)''.
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_\b4 _\bp_\bg_\bp_\b__\br_\be_\bt_\ba_\bi_\bn_\ba_\bb_\bl_\be_\b__\bs_\bi_\bg_\bs
+ _\b7_\b._\b4_\b._\b1_\b9_\b5 _\bp_\bg_\bp_\b__\br_\be_\bt_\ba_\bi_\bn_\ba_\bb_\bl_\be_\b__\bs_\bi_\bg_\bs
Type: boolean
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_\b5 _\bp_\bg_\bp_\b__\bs_\bh_\bo_\bw_\b__\bu_\bn_\bu_\bs_\ba_\bb_\bl_\be
+ _\b7_\b._\b4_\b._\b1_\b9_\b6 _\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_\b6 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs
+ _\b7_\b._\b4_\b._\b1_\b9_\b7 _\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._\b1_\b9_\b7 _\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b1_\b9_\b8 _\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 137
+
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._\b1_\b9_\b8 _\bp_\bg_\bp_\b__\bs_\bo_\br_\bt_\b__\bk_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b1_\b9_\b9 _\bp_\bg_\bp_\b__\bs_\bo_\br_\bt_\b__\bk_\be_\by_\bs
Type: sort order
Default: address
- The Mutt Next Generation E-Mail Client 136
-
Specifies how the entries in the ``pgp keys'' menu are sorted. The following
are legal values:
If you prefer reverse order of the above values, prefix it with ``reverse-''.
(PGP only)
- _\b7_\b._\b4_\b._\b1_\b9_\b9 _\bp_\bg_\bp_\b__\bs_\bt_\br_\bi_\bc_\bt_\b__\be_\bn_\bc
+ _\b7_\b._\b4_\b._\b2_\b0_\b0 _\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_\b0 _\bp_\bg_\bp_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b2_\b0_\b1 _\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_\b1 _\bp_\bg_\bp_\b__\bu_\bs_\be_\b__\bg_\bp_\bg_\b__\ba_\bg_\be_\bn_\bt
+ _\b7_\b._\b4_\b._\b2_\b0_\b2 _\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_\b2 _\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 138
+
+ _\b7_\b._\b4_\b._\b2_\b0_\b3 _\bp_\bg_\bp_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to verify PGP signatures. (PGP only)
- The Mutt Next Generation E-Mail Client 137
-
- _\b7_\b._\b4_\b._\b2_\b0_\b3 _\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_\b0_\b4 _\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_\b4 _\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b2_\b0_\b5 _\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
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_\b5 _\bp_\bi_\bp_\be_\b__\bs_\be_\bp
+ _\b7_\b._\b4_\b._\b2_\b0_\b6 _\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_\b6 _\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b0_\b7 _\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.205 , page 137)'' separator is added after each message.
+ (section 7.4.206 , page 138)'' separator is added after each message.
- _\b7_\b._\b4_\b._\b2_\b0_\b7 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\b__\bt_\br_\by_\b__\ba_\bl_\bl
+ _\b7_\b._\b4_\b._\b2_\b0_\b8 _\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 139
+
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.
- The Mutt Next Generation E-Mail Client 138
-
- _\b7_\b._\b4_\b._\b2_\b0_\b8 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
+ _\b7_\b._\b4_\b._\b2_\b0_\b9 _\bp_\bo_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
Type: string
Example: set pop_authenticators='digest-md5:apop:user'
- _\b7_\b._\b4_\b._\b2_\b0_\b9 _\bp_\bo_\bp_\b__\bd_\be_\bl_\be_\bt_\be
+ _\b7_\b._\b4_\b._\b2_\b1_\b0 _\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_\b0 _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b2_\b1_\b1 _\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_\b1 _\bp_\bo_\bp_\b__\bl_\ba_\bs_\bt
+ The Mutt Next Generation E-Mail Client 140
+
+ _\b7_\b._\b4_\b._\b2_\b1_\b2 _\bp_\bo_\bp_\b__\bl_\ba_\bs_\bt
Type: boolean
Availability: POP
- The Mutt Next Generation E-Mail Client 139
-
If this variable is _\bs_\be_\bt, Mutt-ng will try to use the ``LAST'' POP command for
retrieving only unread messages from the POP server when using the ``fetch-
mail'' function.
- _\b7_\b._\b4_\b._\b2_\b1_\b2 _\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b2_\b1_\b3 _\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
This variable configures how often (in seconds) POP should look for new mail.
- _\b7_\b._\b4_\b._\b2_\b1_\b3 _\bp_\bo_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b2_\b1_\b4 _\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_\b4 _\bp_\bo_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b2_\b1_\b5 _\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_\b5 _\bp_\bo_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b2_\b1_\b6 _\bp_\bo_\bp_\b__\bu_\bs_\be_\br
Type: string
Availability: POP
+ The Mutt Next Generation E-Mail Client 141
+
Your login name on the POP server.
This variable defaults to your user name on the local machine.
- _\b7_\b._\b4_\b._\b2_\b1_\b6 _\bp_\bo_\bs_\bt_\b__\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b2_\b1_\b7 _\bp_\bo_\bs_\bt_\b__\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
Type: string
- The Mutt Next Generation E-Mail Client 140
-
Default: ''
- Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.17 , page 91)'' variable, Mutt-ng
+ Similar to the ``_\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.18 , page 92)'' variable, Mutt-ng
will append this string after the inclusion of a message which is being replied
to.
- _\b7_\b._\b4_\b._\b2_\b1_\b7 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be
+ _\b7_\b._\b4_\b._\b2_\b1_\b8 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be
Type: quadoption
Default: ask-yes
Controls whether or not messages are saved in the ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section
- 7.4.218 , page 140)'' mailbox when you elect not to send immediately.
+ 7.4.219 , page 141)'' mailbox when you elect not to send immediately.
- _\b7_\b._\b4_\b._\b2_\b1_\b8 _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd
+ _\b7_\b._\b4_\b._\b2_\b1_\b9 _\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.217 , page 139)
+ Mutt-ng allows you to indefinitely ``_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 141)
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.217 , page 139)'' variable.
+ ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.218 , page 141)'' variable.
- _\b7_\b._\b4_\b._\b2_\b1_\b9 _\bp_\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b2_\b2_\b0 _\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_\b0 _\bp_\br_\bi_\bn_\bt
+ The Mutt Next Generation E-Mail Client 142
+
+ _\b7_\b._\b4_\b._\b2_\b2_\b1 _\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.
- The Mutt Next Generation E-Mail Client 141
-
- _\b7_\b._\b4_\b._\b2_\b2_\b1 _\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b2_\b2 _\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_\b2 _\bp_\br_\bi_\bn_\bt_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b2_\b2_\b3 _\bp_\br_\bi_\bn_\bt_\b__\bd_\be_\bc_\bo_\bd_\be
Type: boolean
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.221 , page 140). If this option is _\bu_\bn_\bs_\be_\bt, no pro-
+ _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 142). 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_\b3 _\bp_\br_\bi_\bn_\bt_\b__\bs_\bp_\bl_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b2_\b4 _\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.221 , page 140) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 142) is executed
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.221 , page 140) is executed
+ command specified by _\b$_\bp_\br_\bi_\bn_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 142) is executed
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_\b4 _\bp_\br_\bo_\bm_\bp_\bt_\b__\ba_\bf_\bt_\be_\br
+ _\b7_\b._\b4_\b._\b2_\b2_\b5 _\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.170 , page 129)'', setting this
+ If you use an _\be_\bx_\bt_\be_\br_\bn_\ba_\bl ``_\b$_\bp_\ba_\bg_\be_\br (section 7.4.171 , page 130)'', setting this
variable will cause Mutt-ng to prompt you for a command when the pager exits
+
+ The Mutt Next Generation E-Mail Client 143
+
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_\b5 _\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b2_\b6 _\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: path
Default: ''
- The Mutt Next Generation E-Mail Client 142
-
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 56)'' for more
+ query string the user types. See ``_\bq_\bu_\be_\br_\by (section 4.7 , page 57)'' for more
information.
- _\b7_\b._\b4_\b._\b2_\b2_\b6 _\bq_\bu_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b2_\b7 _\bq_\bu_\bi_\bt
Type: quadoption
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_\b2_\b7 _\bq_\bu_\bo_\bt_\be_\b__\be_\bm_\bp_\bt_\by
+ _\b7_\b._\b4_\b._\b2_\b2_\b8 _\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.112 , page 113)''.
+ tion 7.4.113 , page 114)''.
- _\b7_\b._\b4_\b._\b2_\b2_\b8 _\bq_\bu_\bo_\bt_\be_\b__\bq_\bu_\bo_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b2_\b2_\b9 _\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.112 , page 113)''.
+ by ``_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 114)''.
- _\b7_\b._\b4_\b._\b2_\b2_\b9 _\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp
+ _\b7_\b._\b4_\b._\b2_\b3_\b0 _\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 144
+
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_\b0 _\br_\be_\ba_\bd_\b__\bi_\bn_\bc
+ _\b7_\b._\b4_\b._\b2_\b3_\b1 _\br_\be_\ba_\bd_\b__\bi_\bn_\bc
Type: number
Default: 10
- The Mutt Next Generation E-Mail Client 143
-
If set to a value greater than 0, Mutt-ng will display which message it is cur-
rently on when reading a mailbox. The message is printed after _\br_\be_\ba_\bd_\b__\bi_\bn_\bc mes-
sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
time. When set to 0, only a single message will appear before the reading the
mailbox.
- Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 7.4.344 , page 170)'' variable.
+ Also see the ``_\b$_\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc (section 7.4.344 , page 171)'' variable.
- _\b7_\b._\b4_\b._\b2_\b3_\b1 _\br_\be_\ba_\bd_\b__\bo_\bn_\bl_\by
+ _\b7_\b._\b4_\b._\b2_\b3_\b2 _\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_\b2 _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b3_\b3 _\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.77 , page 105) variable.
+ _\b$_\bf_\br_\bo_\bm (section 7.4.78 , page 106) variable.
- _\b7_\b._\b4_\b._\b2_\b3_\b3 _\br_\be_\bc_\ba_\bl_\bl
+ _\b7_\b._\b4_\b._\b2_\b3_\b4 _\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.218 , page 140)''.
+ message. Also see ``_\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.219 , page 141)''.
Setting this variable to _\by_\be_\bs is not generally useful, and thus not recommended.
- _\b7_\b._\b4_\b._\b2_\b3_\b4 _\br_\be_\bc_\bo_\br_\bd
+ _\b7_\b._\b4_\b._\b2_\b3_\b5 _\br_\be_\bc_\bo_\br_\bd
+
+ The Mutt Next Generation E-Mail Client 145
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.15 , page 35)'' com-
+ another way to do this is using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36)'' com-
mand to create a Bcc: header field with your email address in it.)
- The Mutt Next Generation E-Mail Client 144
-
- The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\b7_\b._\b4_\b._\b2_\b3_\b4 _\b, _\bp_\ba_\bg_\be _\b1_\b4_\b3_\b) is overridden by the
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.71 , page 103)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.245 , page 146)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page
- 36)'' command.
+ The value of _\b$_\br_\be_\bc_\bo_\br_\bd _\b(_\bs_\be_\bc_\bt_\bi_\bo_\bn _\b7_\b._\b4_\b._\b2_\b3_\b5 _\b, _\bp_\ba_\bg_\be _\b1_\b4_\b4_\b) is overridden by the
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 105)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.246 , page 147)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.19 , page
+ 38)'' command.
- _\b7_\b._\b4_\b._\b2_\b3_\b5 _\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp
+ _\b7_\b._\b4_\b._\b2_\b3_\b6 _\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp
Type: regular expression
ing. The default value corresponds to the English ``Re:'' and the German
``Aw:''.
- _\b7_\b._\b4_\b._\b2_\b3_\b6 _\br_\be_\bp_\bl_\by_\b__\bs_\be_\bl_\bf
+ _\b7_\b._\b4_\b._\b2_\b3_\b7 _\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_\b3_\b7 _\br_\be_\bp_\bl_\by_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b2_\b3_\b8 _\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_\b3_\b8 _\br_\be_\bs_\bo_\bl_\bv_\be
+ _\b7_\b._\b4_\b._\b2_\b3_\b9 _\br_\be_\bs_\bo_\bl_\bv_\be
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 146
+
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_\b3_\b9 _\br_\be_\bv_\be_\br_\bs_\be_\b__\ba_\bl_\bi_\ba_\bs
+ _\b7_\b._\b4_\b._\b2_\b4_\b0 _\br_\be_\bv_\be_\br_\bs_\be_\b__\ba_\bl_\bi_\ba_\bs
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 145
-
This variable controls whether or not Mutt-ng will display the ``personal''
name from your aliases in the index menu if it finds an alias that matches the
message's sender. For example, if you have the following alias:
``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_\b0 _\br_\be_\bv_\be_\br_\bs_\be_\b__\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b4_\b1 _\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_\b1 _\br_\be_\bv_\be_\br_\bs_\be_\b__\br_\be_\ba_\bl_\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b4_\b2 _\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.240 ,
- page 145) 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.241 ,
+ page 146) 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.232 , page 143) variable.
+ (section 7.4.233 , page 144) variable.
- _\b7_\b._\b4_\b._\b2_\b4_\b2 _\br_\bf_\bc_\b2_\b0_\b4_\b7_\b__\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b2_\b4_\b3 _\br_\bf_\bc_\b2_\b0_\b4_\b7_\b__\bp_\ba_\br_\ba_\bm_\be_\bt_\be_\br_\bs
Type: boolean
+ The Mutt Next Generation E-Mail Client 147
+
Default: no
When this variable is _\bs_\be_\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
When this variable is _\bs_\be_\bt interactively, the change doesn't have the desired
effect before you have changed folders.
- The Mutt Next Generation E-Mail Client 146
-
Note that this use of RFC 2047's encoding is explicitly, prohibited by the
standard, but nevertheless encountered in the wild.
_\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_\b3 _\bs_\ba_\bv_\be_\b__\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b7_\b._\b4_\b._\b2_\b4_\b4 _\bs_\ba_\bv_\be_\b__\ba_\bd_\bd_\br_\be_\bs_\bs
Type: boolean
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.245 , page 146)'' or
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.71 , page 103)'' is _\bs_\be_\bt too, the selection of the
+ folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.246 , page 147)'' or
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 105)'' is _\bs_\be_\bt too, the selection of the
fcc folder will be changed as well.
- _\b7_\b._\b4_\b._\b2_\b4_\b4 _\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by
+ _\b7_\b._\b4_\b._\b2_\b4_\b5 _\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.301 , page 159)'' which is
+ closed (the exception is ``_\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.302 , page 160)'' 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_\b5 _\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b4_\b6 _\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.67 ,
- page 102)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
+ (this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.68 ,
+ page 103)'' directory with the _\bu_\bs_\be_\br_\bn_\ba_\bm_\be part of the recipient address). If the
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.234 , page 143)'' mailbox.
+ the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.235 , page 144)'' mailbox.
- Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.71 , page 103)'' variable.
+ The Mutt Next Generation E-Mail Client 148
+
+ Also see the ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 7.4.72 , page 105)'' variable.
- _\b7_\b._\b4_\b._\b2_\b4_\b6 _\bs_\bc_\bo_\br_\be
+ _\b7_\b._\b4_\b._\b2_\b4_\b7 _\bs_\bc_\bo_\br_\be
Type: boolean
Default: yes
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
-
- The Mutt Next Generation E-Mail Client 147
+ selectively disable scoring for certain folders when the ``_\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\b-
+ _\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 7.4.248 , page 148)'' variable and friends are used.
- ``_\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.247 , page 146)'' variable and friends
- are used.
-
- _\b7_\b._\b4_\b._\b2_\b4_\b7 _\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_\b4_\b8 _\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
Type: number
scores are always greater than or equal to zero, the default setting of this
variable will never mark a message for deletion.
- _\b7_\b._\b4_\b._\b2_\b4_\b8 _\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_\b4_\b9 _\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_\b4_\b9 _\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_\b5_\b0 _\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_\b0 _\bs_\be_\bn_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b2_\b5_\b1 _\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.26 , page 93)'' is not iso-8859-1 and recipients may not under-
+ (section 7.4.27 , page 94)'' is not iso-8859-1 and recipients may not under-
stand UTF-8, it is advisable to include in the list an appropriate widely used
standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
+
+ The Mutt Next Generation E-Mail Client 149
+
instead of or after iso-8859-1.
- _\b7_\b._\b4_\b._\b2_\b5_\b1 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl
+ _\b7_\b._\b4_\b._\b2_\b5_\b2 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl
Type: path
Default: '/usr/sbin/sendmail -oem -oi'
Specifies the program and arguments used to deliver mail sent by Mutt-ng.
-
- The Mutt Next Generation E-Mail Client 148
-
Mutt-ng expects that the specified program interprets additional arguments as
recipient addresses.
- _\b7_\b._\b4_\b._\b2_\b5_\b2 _\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl_\b__\bw_\ba_\bi_\bt
+ _\b7_\b._\b4_\b._\b2_\b5_\b3 _\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.251 ,
- page 147)'' 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.252 ,
+ page 148)'' process to finish before giving up and putting delivery in the
background.
Mutt-ng interprets the value of this variable as follows:
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_\b3 _\bs_\bh_\be_\bl_\bl
+ _\b7_\b._\b4_\b._\b2_\b5_\b4 _\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_\b4 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by
+ _\b7_\b._\b4_\b._\b2_\b5_\b5 _\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.258 , page 149) is _\bs_\be_\bt, this variable specifies the characters at which to
+ 7.4.259 , page 150) is _\bs_\be_\bt, this variable specifies the characters at which to
+
+ The Mutt Next Generation E-Mail Client 150
+
split a folder name into ``hierarchy items.''
- _\b7_\b._\b4_\b._\b2_\b5_\b5 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bd_\be_\bl_\bi_\bm
+ _\b7_\b._\b4_\b._\b2_\b5_\b6 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bd_\be_\bl_\bi_\bm
Type: string
Default: '|'
This specifies the delimiter between the sidebar (if visible) and other
-
- The Mutt Next Generation E-Mail Client 149
-
screens.
- _\b7_\b._\b4_\b._\b2_\b5_\b6 _\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_\b5_\b7 _\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_\b5_\b7 _\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_\b5_\b8 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bn_\bu_\bm_\bb_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
1) These expandos only have a non-zero value for the current mailbox and will
always be zero otherwise.
- _\b7_\b._\b4_\b._\b2_\b5_\b8 _\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 151
+
+ _\b7_\b._\b4_\b._\b2_\b5_\b9 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by
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.260 , page 150)'' is set to a too low value). For example, if the
-
- The Mutt Next Generation E-Mail Client 150
-
- newsgroup 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.
+ 7.4.261 , page 151)'' 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.254 , page 148) variable.
+ _\bb_\ba_\br_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by (section 7.4.255 , page 149) variable.
- _\b7_\b._\b4_\b._\b2_\b5_\b9 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
+ _\b7_\b._\b4_\b._\b2_\b6_\b0 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bv_\bi_\bs_\bi_\bb_\bl_\be
Type: boolean
This specifies whether or not to show the sidebar (a list of folders specified
with the ``mailboxes'' command).
- _\b7_\b._\b4_\b._\b2_\b6_\b0 _\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bw_\bi_\bd_\bt_\bh
+ _\b7_\b._\b4_\b._\b2_\b6_\b1 _\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_\b1 _\bs_\bi_\bg_\b__\bd_\ba_\bs_\bh_\be_\bs
+ _\b7_\b._\b4_\b._\b2_\b6_\b2 _\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.263 , page 150)''. It is s\bst\btr\bro\bon\bng\bgl\bly\by recommended
+ your ``_\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.264 , page 151)''. 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_\b2 _\bs_\bi_\bg_\b__\bo_\bn_\b__\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b2_\b6_\b3 _\bs_\bi_\bg_\b__\bo_\bn_\b__\bt_\bo_\bp
Type: boolean
Default: no
+ The Mutt Next Generation E-Mail Client 152
+
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_\b3 _\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be
+ _\b7_\b._\b4_\b._\b2_\b6_\b4 _\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be
Type: path
- The Mutt Next Generation E-Mail Client 151
-
Default: '~/.signature'
Specifies the filename of your signature, which is appended to all outgoing
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_\b4 _\bs_\bi_\bg_\bn_\bo_\bf_\bf_\b__\bs_\bt_\br_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b2_\b6_\b5 _\bs_\bi_\bg_\bn_\bo_\bf_\bf_\b__\bs_\bt_\br_\bi_\bn_\bg
Type: string
witty quotes into your mails, better use a signature file instead of the sig-
noff string.
- _\b7_\b._\b4_\b._\b2_\b6_\b5 _\bs_\bi_\bm_\bp_\bl_\be_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b7_\b._\b4_\b._\b2_\b6_\b6 _\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 81)'' for more information on search patterns.
+ ``_\bp_\ba_\bt_\bt_\be_\br_\bn_\bs (section 7.2 , page 82)'' 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_\b6 _\bs_\bl_\be_\be_\bp_\b__\bt_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b2_\b6_\b7 _\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_\b6_\b7 _\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp
+ The Mutt Next Generation E-Mail Client 153
+
+ _\b7_\b._\b4_\b._\b2_\b6_\b8 _\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.125 ,
+ page 119)'' variable.
- The Mutt Next Generation E-Mail Client 152
-
- simply wrapped at the screen edge. Also see the ``_\b$_\bm_\ba_\br_\bk_\be_\br_\bs (section 7.4.124 ,
- page 117)'' variable.
-
- _\b7_\b._\b4_\b._\b2_\b6_\b8 _\bs_\bm_\bi_\bl_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b2_\b6_\b9 _\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.229 , page 142)'', most notably smileys in the
+ ``_\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.230 , page 143)'', most notably smileys in the
beginning of a line
- _\b7_\b._\b4_\b._\b2_\b6_\b9 _\bs_\bm_\bi_\bm_\be_\b__\ba_\bs_\bk_\b__\bc_\be_\br_\bt_\b__\bl_\ba_\bb_\be_\bl
+ _\b7_\b._\b4_\b._\b2_\b7_\b0 _\bs_\bm_\bi_\bm_\be_\b__\ba_\bs_\bk_\b__\bc_\be_\br_\bt_\b__\bl_\ba_\bb_\be_\bl
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_\b0 _\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn
+ _\b7_\b._\b4_\b._\b2_\b7_\b1 _\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_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bc_\be_\br_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\be_\bs
+ _\b7_\b._\b4_\b._\b2_\b7_\b2 _\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_\b2 _\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 154
+
+ _\b7_\b._\b4_\b._\b2_\b7_\b3 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This format string specifies a command which is used to decrypt application/x-
pkcs7-mime attachments.
- The Mutt Next Generation E-Mail Client 153
-
The OpenSSL command formats have their own set of printf(3)-like sequences sim-
ilar to PGP's:
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.274 ,
- page 153)
+ The key-pair specified with _\b$_\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by (section 7.4.275 ,
+ page 154)
%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.270 , page 152) 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.270 , page 152)' or
- '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.270 , page 152)'.
+ 7.4.271 , page 153) points to a directory or file, this expands to
+ '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.271 , page 153)' or
+ '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 7.4.271 , page 153)'.
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_\b3 _\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_\b7_\b4 _\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_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bk_\be_\by
+ _\b7_\b._\b4_\b._\b2_\b7_\b5 _\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 155
+
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_\b5 _\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_\b7_\b6 _\bs_\bm_\bi_\bm_\be_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
- The Mutt Next Generation E-Mail Client 154
-
Default: ''
This command is used to create encrypted S/MIME messages. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b7_\b6 _\bs_\bm_\bi_\bm_\be_\b__\be_\bn_\bc_\br_\by_\bp_\bt_\b__\bw_\bi_\bt_\bh
+ _\b7_\b._\b4_\b._\b2_\b7_\b7 _\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)
- _\b7_\b._\b4_\b._\b2_\b7_\b7 _\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_\b7_\b8 _\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_\b7_\b8 _\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_\b7_\b9 _\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_\b7_\b9 _\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_\b8_\b0 _\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_\b0 _\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 156
+
+ _\b7_\b._\b4_\b._\b2_\b8_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bi_\bm_\bp_\bo_\br_\bt_\b__\bc_\be_\br_\bt_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to import a certificate via smime_keysng. (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b1 _\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt
-
- The Mutt Next Generation E-Mail Client 155
+ _\b7_\b._\b4_\b._\b2_\b8_\b2 _\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.39 , page 96).) (S/MIME only)
+ tion 7.4.40 , page 97).) (S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b2 _\bs_\bm_\bi_\bm_\be_\b__\bk_\be_\by_\bs
+ _\b7_\b._\b4_\b._\b2_\b8_\b3 _\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_\b3 _\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_\b8_\b4 _\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_\b4 _\bs_\bm_\bi_\bm_\be_\b__\bs_\bi_\bg_\bn_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ _\b7_\b._\b4_\b._\b2_\b8_\b5 _\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_\b5 _\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 157
+
+ _\b7_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bs_\bi_\bg_\bn_\b__\bo_\bp_\ba_\bq_\bu_\be_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
pkcs7-signature, which can only be handled by mail clients supporting the
S/MIME extension. (S/MIME only)
- The Mutt Next Generation E-Mail Client 156
-
- _\b7_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bi_\bm_\be_\b__\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b2_\b8_\b7 _\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_\b8_\b7 _\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_\b8_\b8 _\bs_\bm_\bi_\bm_\be_\b__\bv_\be_\br_\bi_\bf_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd
Type: string
This command is used to verify S/MIME signatures of type multipart/signed.
(S/MIME only)
- _\b7_\b._\b4_\b._\b2_\b8_\b8 _\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._\b2_\b8_\b9 _\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_\b8_\b9 _\bs_\bm_\bt_\bp_\b__\be_\bn_\bv_\be_\bl_\bo_\bp_\be
+ _\b7_\b._\b4_\b._\b2_\b9_\b0 _\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_\b0 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+
+ The Mutt Next Generation E-Mail Client 158
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.251 , page 147)'', and any associated variables.
-
- The Mutt Next Generation E-Mail Client 157
+ _\bm_\ba_\bi_\bl (section 7.4.252 , page 148)'', and any associated variables.
- _\b7_\b._\b4_\b._\b2_\b9_\b1 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b2_\b9_\b2 _\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.294 , page 157)'' is set, but this variable is not, you will be prompted
+ 7.4.295 , page 158)'' 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.
- _\b7_\b._\b4_\b._\b2_\b9_\b2 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
+ _\b7_\b._\b4_\b._\b2_\b9_\b3 _\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_\b3 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
+ _\b7_\b._\b4_\b._\b2_\b9_\b4 _\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_\b4 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
+ The Mutt Next Generation E-Mail Client 159
+
+ _\b7_\b._\b4_\b._\b2_\b9_\b5 _\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.
- The Mutt Next Generation E-Mail Client 158
-
- _\b7_\b._\b4_\b._\b2_\b9_\b5 _\bs_\bo_\br_\bt
+ _\b7_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bo_\br_\bt
Type: sort order
You may optionally use the ``reverse-'' prefix to specify reverse sorting order
(example: set sort=reverse-date-sent).
- _\b7_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bo_\br_\bt_\b__\ba_\bl_\bi_\ba_\bs
+ _\b7_\b._\b4_\b._\b2_\b9_\b7 _\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._\b2_\b9_\b7 _\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ _\b7_\b._\b4_\b._\b2_\b9_\b8 _\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
Type: sort order
+ The Mutt Next Generation E-Mail Client 160
+
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.295 , page 157)'' can,
+ This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158)'' 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
siblings by which has the last descendant, using the rest of sort_aux as an
ordering.
- The Mutt Next Generation E-Mail Client 159
-
For instance, set sort_aux=last-date-received would mean that if a new message
is received in a thread, that thread becomes the last one displayed (or the
first, if you have set sort=reverse-threads.)
- N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 7.4.295 , page 157)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
- (section 7.4.297 , page 158) is reversed again (which is not the right thing
+ N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ (section 7.4.298 , page 159) is reversed again (which is not the right thing
to do, but kept to not break any existing configuration setting).
- _\b7_\b._\b4_\b._\b2_\b9_\b8 _\bs_\bo_\br_\bt_\b__\bb_\br_\bo_\bw_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b2_\b9_\b9 _\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._\b2_\b9_\b9 _\bs_\bo_\br_\bt_\b__\br_\be
+ _\b7_\b._\b4_\b._\b3_\b0_\b0 _\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.316 , page 165)'' _\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.299 ,
- page 159) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
+ (section 7.4.317 , page 166)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.300 ,
+ page 160) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
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.235 , page 143)''. With
- _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.299 , page 159) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
+ matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.236 , page 145)''. With
+ _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 7.4.300 , page 160) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
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.235 , page 143)'' parts of both messages are identical.
+ 7.4.236 , page 145)'' parts of both messages are identical.
+
+ The Mutt Next Generation E-Mail Client 161
- _\b7_\b._\b4_\b._\b3_\b0_\b0 _\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br
+ _\b7_\b._\b4_\b._\b3_\b0_\b1 _\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.300 , page 159)'' controls what happens when
+ ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.301 , page 160)'' 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.300 ,
- page 159)'' as a separator.
-
- The Mutt Next Generation E-Mail Client 160
+ match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 7.4.301 ,
+ page 160)'' as a separator.
- _\b7_\b._\b4_\b._\b3_\b0_\b1 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
+ _\b7_\b._\b4_\b._\b3_\b0_\b2 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
Type: path
set this variable to the value of the environment variable $MAIL if it is not
set.
- _\b7_\b._\b4_\b._\b3_\b0_\b2 _\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_\b0_\b3 _\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_\b3 _\bs_\bs_\bl_\b__\bc_\bl_\bi_\be_\bn_\bt_\b__\bc_\be_\br_\bt
+ _\b7_\b._\b4_\b._\b3_\b0_\b4 _\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_\b4 _\bs_\bs_\bl_\b__\bf_\bo_\br_\bc_\be_\b__\bt_\bl_\bs
+ _\b7_\b._\b4_\b._\b3_\b0_\b5 _\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 162
+
abort the connection anyway. This option supersedes ``_\b$_\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs (section
- 7.4.306 , page 160)''.
+ 7.4.307 , page 162)''.
- _\b7_\b._\b4_\b._\b3_\b0_\b5 _\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_\b0_\b6 _\bs_\bs_\bl_\b__\bm_\bi_\bn_\b__\bd_\bh_\b__\bp_\br_\bi_\bm_\be_\b__\bb_\bi_\bt_\bs
Type: number
Availability: GNUTLS
This variable specifies the minimum acceptable prime size (in bits) for use in
-
- The Mutt Next Generation E-Mail Client 161
-
any Diffie-Hellman key exchange. A value of 0 will use the default from the
GNUTLS library.
- _\b7_\b._\b4_\b._\b3_\b0_\b6 _\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs
+ _\b7_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bs_\bl_\b__\bs_\bt_\ba_\br_\bt_\bt_\bl_\bs
Type: quadoption
ing the capability. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will not attempt to use STARTTLS
regardless of the server's capabilities.
- _\b7_\b._\b4_\b._\b3_\b0_\b7 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b2
+ _\b7_\b._\b4_\b._\b3_\b0_\b8 _\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_\b0_\b8 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bs_\bs_\bl_\bv_\b3
+ _\b7_\b._\b4_\b._\b3_\b0_\b9 _\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_\b0_\b9 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bt_\bl_\bs_\bv_\b1
+ _\b7_\b._\b4_\b._\b3_\b1_\b0 _\bs_\bs_\bl_\b__\bu_\bs_\be_\b__\bt_\bl_\bs_\bv_\b1
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 163
+
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_\b0 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
Type: boolean
Default: yes
- The Mutt Next Generation E-Mail Client 162
-
Availability: SSL
If set to _\by_\be_\bs, Mutt-ng will use CA certificates in the system-wide certificate
store when checking if server certificate is signed by a trusted CA.
- _\b7_\b._\b4_\b._\b3_\b1_\b1 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b2 _\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.312 , page 162)''. The first character is used when the mailbox is
+ tion 7.4.313 , page 163)''. 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_\b2 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b3_\b1_\b3 _\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.113 , page 113)'', but has
+ string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.114 , page 114)'', but has
its own set of printf(3)-like sequences:
%b
%d
number of deleted messages *
+ The Mutt Next Generation E-Mail Client 164
+
%f
the full pathname of the current mailbox
%l
size (in bytes) of the current mailbox *
- The Mutt Next Generation E-Mail Client 163
-
%L
size (in bytes) of the messages shown (i.e., which match the cur-
rent 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.311 , page 161)
+ to _\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br_\bs (section 7.4.312 , page 163)
%s
- current sorting mode (_\b$_\bs_\bo_\br_\bt (section 7.4.295 , page 157))
+ current sorting mode (_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158))
%S
- current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 7.4.297 , page
- 158))
+ current aux sorting method (_\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx (section 7.4.298 , page
+ 159))
%t
number of tagged messages *
%v
Mutt-ng version string
+ The Mutt Next Generation E-Mail Client 165
+
%V
currently active limit pattern, if any *
* = can be optionally printed if nonzero
- The Mutt Next Generation E-Mail Client 164
-
Some of the above sequences can be used to optionally print a string if their
value is nonzero. For example, you may only want to see the number of flagged
messages if such messages exist, since zero is not particularly meaningful. To
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_\b3 _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bo_\bn_\b__\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b3_\b1_\b4 _\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_\b4 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\ba_\bi_\bl_\bt_\bo
+ The Mutt Next Generation E-Mail Client 166
+
+ _\b7_\b._\b4_\b._\b3_\b1_\b5 _\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.57 , page 100)'' is unset.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101)'' is unset.
If this variable is _\bs_\be_\bt, mutt-ng is strict and allows anything to be changed.
-
- The Mutt Next Generation E-Mail Client 165
-
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.57 , page 100)'' is set to.
+ ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.58 , page 101)'' is set to.
- _\b7_\b._\b4_\b._\b3_\b1_\b5 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b3_\b1_\b6 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be
Type: boolean
When _\bu_\bn_\bs_\be_\bt, non MIME-compliant messages that doesn't have any charset indica-
tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
messages are often generated by old mailers or buggy mailers like MS Outlook
- Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.12 , page 89).
+ Express). See also _\b$_\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt (section 7.4.13 , page 90).
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_\b6 _\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b7 _\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.295 , page 157)'' by mes-
+ ences:'' header fields when you ``_\b$_\bs_\bo_\br_\bt (section 7.4.296 , page 158)'' 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_\b1_\b7 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs
+ _\b7_\b._\b4_\b._\b3_\b1_\b8 _\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.318 , page 165) when replying. This is
+ matches _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx (section 7.4.319 , page 166) when replying. This is
useful to properly react on subject changes and reduce ``subject noise.'' (esp.
in Usenet)
- _\b7_\b._\b4_\b._\b3_\b1_\b8 _\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs_\b__\br_\be_\bg_\be_\bx
+ The Mutt Next Generation E-Mail Client 167
+
+ _\b7_\b._\b4_\b._\b3_\b1_\b9 _\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.317 , page 165) is _\bs_\be_\bt, mutt-ng
+ When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 7.4.318 , page 166) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
- The Mutt Next Generation E-Mail Client 166
-
- _\b7_\b._\b4_\b._\b3_\b1_\b9 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b3_\b2_\b0 _\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.
- _\b7_\b._\b4_\b._\b3_\b2_\b0 _\bs_\bu_\bs_\bp_\be_\bn_\bd
+ _\b7_\b._\b4_\b._\b3_\b2_\b1 _\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_\b1 _\bt_\be_\bx_\bt_\b__\bf_\bl_\bo_\bw_\be_\bd
+ _\b7_\b._\b4_\b._\b3_\b2_\b2 _\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.112 , page 113) is ignored when this
+ Note that _\b$_\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg (section 7.4.113 , page 114) is ignored when this
option is set.
- _\b7_\b._\b4_\b._\b3_\b2_\b2 _\bt_\bh_\bo_\br_\bo_\bu_\bg_\bh_\b__\bs_\be_\ba_\br_\bc_\bh
+ _\b7_\b._\b4_\b._\b3_\b2_\b3 _\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 81)'' above. If _\bs_\be_\bt, the headers and attachments of messages
+ tion 7.2 , page 82)'' 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_\b3 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
+ The Mutt Next Generation E-Mail Client 168
+
+ _\b7_\b._\b4_\b._\b3_\b2_\b4 _\bt_\bh_\br_\be_\ba_\bd_\b__\br_\be_\bc_\be_\bi_\bv_\be_\bd
Type: boolean
When _\bs_\be_\bt, Mutt-ng uses the date received rather than the date sent to thread
messages by subject.
- The Mutt Next Generation E-Mail Client 167
-
- _\b7_\b._\b4_\b._\b3_\b2_\b4 _\bt_\bi_\bl_\bd_\be
+ _\b7_\b._\b4_\b._\b3_\b2_\b5 _\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 (~).
- _\b7_\b._\b4_\b._\b3_\b2_\b5 _\bt_\bi_\bm_\be_\bo_\bu_\bt
+ _\b7_\b._\b4_\b._\b3_\b2_\b6 _\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_\b6 _\bt_\bm_\bp_\bd_\bi_\br
+ _\b7_\b._\b4_\b._\b3_\b2_\b7 _\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_\b2_\b7 _\bt_\bo_\b__\bc_\bh_\ba_\br_\bs
+ _\b7_\b._\b4_\b._\b3_\b2_\b8 _\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_\b2_\b8 _\bt_\br_\ba_\bs_\bh
+ The Mutt Next Generation E-Mail Client 169
+
+ _\b7_\b._\b4_\b._\b3_\b2_\b9 _\bt_\br_\ba_\bs_\bh
Type: path
If _\bs_\be_\bt, this variable specifies the path of the trash folder where the mails
marked for deletion will be moved, instead of being irremediably purged.
- The Mutt Next Generation E-Mail Client 168
-
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_\b2_\b9 _\bt_\bu_\bn_\bn_\be_\bl
+ _\b7_\b._\b4_\b._\b3_\b3_\b0 _\bt_\bu_\bn_\bn_\be_\bl
Type: string
N\bNo\bot\bte\be:\b: For this example to work you must be able to log in to the remote machine
without having to enter a password.
- _\b7_\b._\b4_\b._\b3_\b3_\b0 _\bu_\bm_\ba_\bs_\bk
+ _\b7_\b._\b4_\b._\b3_\b3_\b1 _\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_\b1 _\bu_\bn_\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be_\b__\bj_\bu_\bm_\bp
+ _\b7_\b._\b4_\b._\b3_\b3_\b2 _\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_\b2 _\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be
+ _\b7_\b._\b4_\b._\b3_\b3_\b3 _\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 170
+
mail.
- When _\bs_\be_\bt, Mutt-ng will either invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.251 , page
- 147)'' 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.252 , page
+ 148)'' 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_\b3 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
+ _\b7_\b._\b4_\b._\b3_\b3_\b4 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
Type: boolean
- The Mutt Next Generation E-Mail Client 169
-
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.92 , page 108)''. If _\bu_\bn_\bs_\be_\bt,
+ tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 7.4.93 , page 109)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
- _\b7_\b._\b4_\b._\b3_\b3_\b4 _\bu_\bs_\be_\b__\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b3_\b3_\b5 _\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.15 , page 35)'' command.
+ explicitly sets one using the ``_\bm_\by_\b__\bh_\bd_\br (section 3.16 , page 36)'' command.
- _\b7_\b._\b4_\b._\b3_\b3_\b5 _\bu_\bs_\be_\b__\bi_\bd_\bn
+ _\b7_\b._\b4_\b._\b3_\b3_\b6 _\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_\b6 _\bu_\bs_\be_\b__\bi_\bp_\bv_\b6
+ _\b7_\b._\b4_\b._\b3_\b3_\b7 _\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_\b3_\b7 _\bu_\bs_\be_\br_\b__\ba_\bg_\be_\bn_\bt
-
- Type: boolean
-
- Default: yes
-
- When _\bs_\be_\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
- cating which version of Mutt-ng was used for composing them.
-
_\b7_\b._\b4_\b._\b3_\b3_\b8 _\bv_\bi_\bs_\bu_\ba_\bl
Type: path
Default: ''
- The Mutt Next Generation E-Mail Client 170
+ The Mutt Next Generation E-Mail Client 171
Specifies the visual editor to invoke when the _\b~_\bv command is given in the
builtin editor.
_\bm_\be_\bs_\bs_\ba_\bg_\be, _\bp_\bi_\bp_\be_\b-_\be_\bn_\bt_\br_\by, _\bp_\br_\bi_\bn_\bt_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be, and _\bp_\br_\bi_\bn_\bt_\b-_\be_\bn_\bt_\br_\by commands.
It is also used when viewing attachments with ``_\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page
- 76)'', provided that the corresponding mailcap entry has a needsterminal flag,
+ 77)'', provided that the corresponding mailcap entry has a needsterminal flag,
and the external program is interactive.
When _\bs_\be_\bt, Mutt-ng will always ask for a key. When _\bu_\bn_\bs_\be_\bt, Mutt-ng will wait for
Default: yes
- The Mutt Next Generation E-Mail Client 171
+ The Mutt Next Generation E-Mail Client 172
Controls whether Mutt-ng writes out the Bcc header when preparing messages to
be sent. Exim users may wish to _\bu_\bn_\bs_\be_\bt this.
indicate progress. If set to 0, only a single message will be displayed before
writing a mailbox.
- Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 7.4.230 , page 142)'' variable.
+ Also see the ``_\b$_\br_\be_\ba_\bd_\b__\bi_\bn_\bc (section 7.4.231 , page 143)'' variable.
_\b7_\b._\b4_\b._\b3_\b4_\b5 _\bx_\bt_\be_\br_\bm_\b__\bi_\bc_\bo_\bn
Default: 'M%?n?AIL&ail?'
Controls the format of the X11 icon title, as long as _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (sec-
- tion 7.4.347 , page 171) 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.312 , page 162)''.
+ tion 7.4.347 , page 172) is _\bs_\be_\bt. This string is identical in formatting to the
+ one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 , page 163)''.
_\b7_\b._\b4_\b._\b3_\b4_\b6 _\bx_\bt_\be_\br_\bm_\b__\bl_\be_\ba_\bv_\be
Default: ''
- If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.347 , page 171) is _\bs_\be_\bt, this string will be
+ If _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.347 , page 172) is _\bs_\be_\bt, this string will be
used to set the title when leaving mutt-ng. For terminal-based programs,
there's no easy and portable way to read the current title so mutt-ng cannot
read it upon startup and restore it when exiting.
Type: string
- The Mutt Next Generation E-Mail Client 172
+ The Mutt Next Generation E-Mail Client 173
Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
Controls the format of the title bar of the xterm provided that
- _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.347 , page 171) 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.312 ,
- page 162)''.
+ _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 7.4.347 , page 172) has been _\bs_\be_\bt. This string is
+ identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.313 ,
+ page 163)''.
_\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.4 , page 24) command.
+ with the _\bb_\bi_\bn_\bd (section 3.5 , page 25) command.
_\b7_\b._\b5_\b._\b1 _\bg_\be_\bn_\be_\br_\bi_\bc
top-page H move to the top of the page
what-key not bound display the keycode for a key press
- The Mutt Next Generation E-Mail Client 173
+ The Mutt Next Generation E-Mail Client 174
_\b7_\b._\b5_\b._\b2 _\bi_\bn_\bd_\be_\bx
- The Mutt Next Generation E-Mail Client 174
+ The Mutt Next Generation E-Mail Client 175
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 175
+ The Mutt Next Generation E-Mail Client 176
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 176
+ The Mutt Next Generation E-Mail Client 177
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 177
+ The Mutt Next Generation E-Mail Client 178
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 178
+ The Mutt Next Generation E-Mail Client 179
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 179
+ The Mutt Next Generation E-Mail Client 180
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 180
+ The Mutt Next Generation E-Mail Client 181
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 181
+ The Mutt Next Generation E-Mail Client 182
_\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 182
+ The Mutt Next Generation E-Mail Client 183
Brandon Long <blong@fiction.net>,
Elimar Riesebieter <riesebie@lxtec.de>
- The Mutt Next Generation E-Mail Client 183
+ The Mutt Next Generation E-Mail Client 184
_\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 184
+ The Mutt Next Generation E-Mail Client 185
CONTENTS
3. Configuration ........................................................ 21
3.1 Locations of Configuration Files ............................... 21
- 3.2 Syntax of Initialization Files ................................. 21
- 3.3 Defining/Using aliases ......................................... 23
- 3.4 Changing the default key bindings .............................. 24
- 3.5 Defining aliases for character sets ........................... 26
+ 3.2 Basic Syntax of Initialization Files ........................... 21
+ 3.3 Variable Expansion ........................................... 23
+ 3.3.1 Commands' Output 23
+ 3.3.2 Environment Variables 23
i
- 3.6 Setting variables based upon mailbox ........................... 26
- 3.7 Keyboard macros ................................................ 27
- 3.8 Using color and mono video attributes .......................... 28
- 3.9 Ignoring (weeding) unwanted message headers .................... 30
- 3.10 Alternative addresses .......................................... 31
- 3.11 Format = Flowed .............................................. 31
- 3.11.1 Introduction 31
- 3.11.2 Receiving: Display Setup 31
- 3.11.3 Sending 32
- 3.11.4 Additional Notes 33
- 3.12 Mailing lists .................................................. 33
- 3.13 Using Multiple spool mailboxes ................................. 34
- 3.14 Defining mailboxes which receive mail .......................... 34
- 3.15 User defined headers ........................................... 35
- 3.16 Defining the order of headers when viewing messages ............ 36
- 3.17 Specify default save filename .................................. 36
- 3.18 Specify default Fcc: mailbox when composing .................... 36
- 3.19 Specify default save filename and default Fcc: mailbox at once . 37
- 3.20 Change settings based upon message recipients .................. 37
- 3.21 Change settings before formatting a message .................... 38
- 3.22 Choosing the cryptographic key of the recipient ................ 38
- 3.23 Adding key sequences to the keyboard buffer .................... 38
- 3.24 Executing functions ............................................ 39
- 3.25 Message Scoring ................................................ 39
- 3.26 Spam detection ................................................. 40
- 3.27 Setting variables .............................................. 42
- 3.28 Reading initialization commands from another file .............. 43
- 3.29 Removing hooks ................................................. 43
- 3.30 Sharing Setups ............................................. 43
- 3.30.1 Character Sets 43
- 3.30.2 Modularization 44
- 3.30.3 Conditional parts 44
- 3.31 Obsolete Variables ............................................. 46
-
- 4. Advanced Usage ....................................................... 46
- 4.1 Regular Expressions ............................................ 46
- 4.2 Patterns ....................................................... 49
- 4.2.1 Complex Patterns 49
- 4.2.2 Patterns and Dates 50
- 4.3 Format Strings ............................................. 50
- 4.3.1 Introduction 50
- 4.3.2 Conditional Expansion 52
- 4.3.3 Modifications and Padding 53
- 4.4 Using Tags ..................................................... 53
- 4.5 Using Hooks .................................................... 54
- 4.5.1 Message Matching in Hooks 55
- 4.6 Using the sidebar .............................................. 55
- 4.7 External Address Queries ....................................... 56
- 4.8 Mailbox Formats ................................................ 57
- 4.9 Mailbox Shortcuts .............................................. 58
- 4.10 Handling Mailing Lists ......................................... 58
- 4.11 Editing threads ................................................ 59
- 4.11.1 Linking threads 60
+ 3.3.3 Configuration Variables 23
+ 3.3.4 Self-Defined Variables 23
+ 3.3.5 Type Conversions 24
+ 3.4 Defining/Using aliases ......................................... 24
+ 3.5 Changing the default key bindings .............................. 25
+ 3.6 Defining aliases for character sets ........................... 27
+ 3.7 Setting variables based upon mailbox ........................... 27
+ 3.8 Keyboard macros ................................................ 28
+ 3.9 Using color and mono video attributes .......................... 29
+ 3.10 Ignoring (weeding) unwanted message headers .................... 31
+ 3.11 Alternative addresses .......................................... 32
+ 3.12 Format = Flowed .............................................. 32
+ 3.12.1 Introduction 32
+ 3.12.2 Receiving: Display Setup 33
+ 3.12.3 Sending 34
+ 3.12.4 Additional Notes 34
+ 3.13 Mailing lists .................................................. 34
+ 3.14 Using Multiple spool mailboxes ................................. 35
+ 3.15 Defining mailboxes which receive mail .......................... 36
+ 3.16 User defined headers ........................................... 36
+ 3.17 Defining the order of headers when viewing messages ............ 37
+ 3.18 Specify default save filename .................................. 37
+ 3.19 Specify default Fcc: mailbox when composing .................... 38
+ 3.20 Specify default save filename and default Fcc: mailbox at once . 38
+ 3.21 Change settings based upon message recipients .................. 38
+ 3.22 Change settings before formatting a message .................... 39
+ 3.23 Choosing the cryptographic key of the recipient ................ 39
+ 3.24 Adding key sequences to the keyboard buffer .................... 40
+ 3.25 Executing functions ............................................ 40
+ 3.26 Message Scoring ................................................ 40
+ 3.27 Spam detection ................................................. 41
+ 3.28 Setting variables .............................................. 43
+ 3.29 Reading initialization commands from another file .............. 44
+ 3.30 Removing hooks ................................................. 44
+ 3.31 Sharing Setups ............................................. 44
+ 3.31.1 Character Sets 45
+ 3.31.2 Modularization 45
+ 3.31.3 Conditional parts 45
+ 3.32 Obsolete Variables ............................................. 47
+
+ 4. Advanced Usage ....................................................... 47
+ 4.1 Regular Expressions ............................................ 47
+ 4.2 Patterns ....................................................... 50
+ 4.2.1 Complex Patterns 50
+ 4.2.2 Patterns and Dates 51
+ 4.3 Format Strings ............................................. 52
+ 4.3.1 Introduction 52
+ 4.3.2 Conditional Expansion 53
+ 4.3.3 Modifications and Padding 54
+ 4.4 Using Tags ..................................................... 55
+ 4.5 Using Hooks .................................................... 55
+ 4.5.1 Message Matching in Hooks 56
+ 4.6 Using the sidebar .............................................. 56
ii
- 4.11.2 Breaking threads 60
- 4.12 Delivery Status Notification (DSN) Support ..................... 60
- 4.13 POP3 Support (OPTIONAL) ........................................ 60
- 4.14 IMAP Support (OPTIONAL) ........................................ 61
- 4.14.1 The Folder Browser 62
- 4.14.2 Authentication 62
- 4.15 NNTP Support (OPTIONAL) ........................................ 63
- 4.15.1 Again: Scoring 63
- 4.16 SMTP Support (OPTIONAL) ........................................ 64
- 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 65
- 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 65
- 4.19 Compressed folders Support (OPTIONAL) .......................... 65
- 4.19.1 Open a compressed mailbox for reading 66
- 4.19.2 Write a compressed mailbox 66
- 4.19.3 Append a message to a compressed mailbox 67
- 4.19.4 Encrypted folders 68
-
- 5. Mutt-ng's MIME Support ............................................... 68
- 5.1 Using MIME in Mutt ............................................. 68
- 5.1.1 Viewing MIME messages in the pager 68
- 5.1.2 The Attachment Menu 69
- 5.1.3 The Compose Menu 69
- 5.2 MIME Type configuration with mime.types ........................ 69
- 5.3 MIME Viewer configuration with mailcap ......................... 70
- 5.3.1 The Basics of the mailcap file 71
- 5.3.2 Secure use of mailcap 72
- 5.3.3 Advanced mailcap Usage 72
- 5.3.4 Example mailcap files 75
- 5.4 MIME Autoview .................................................. 76
- 5.5 MIME Multipart/Alternative ..................................... 77
- 5.6 MIME Lookup .................................................... 77
-
- 6. Security Considerations ............................................ 78
- 6.1 Passwords .................................................. 78
- 6.2 Temporary Files ............................................ 78
- 6.3 Information Leaks ............................................ 78
- 6.3.1 Message-ID: headers 78
- 6.3.2 mailto:-style links 79
- 6.4 External applications ...................................... 79
- 6.4.1 mailcap 79
- 6.4.2 Other 80
-
- 7. Reference ............................................................ 80
- 7.1 Command line options ........................................... 80
- 7.2 Patterns ....................................................... 81
- 7.3 Configuration Commands ......................................... 83
- 7.4 Configuration variables .......................................... 85
- 7.4.1 abort_noattach 86
- 7.4.2 abort_nosubject 87
- 7.4.3 abort_unmodified 87
- 7.4.4 alias_file 87
- 7.4.5 alias_format 87
- 7.4.6 allow_8bit 88
+ 4.7 External Address Queries ....................................... 57
+ 4.8 Mailbox Formats ................................................ 58
+ 4.9 Mailbox Shortcuts .............................................. 59
+ 4.10 Handling Mailing Lists ......................................... 59
+ 4.11 Editing threads ................................................ 61
+ 4.11.1 Linking threads 61
+ 4.11.2 Breaking threads 61
+ 4.12 Delivery Status Notification (DSN) Support ..................... 61
+ 4.13 POP3 Support (OPTIONAL) ........................................ 62
+ 4.14 IMAP Support (OPTIONAL) ........................................ 62
+ 4.14.1 The Folder Browser 63
+ 4.14.2 Authentication 64
+ 4.15 NNTP Support (OPTIONAL) ........................................ 64
+ 4.15.1 Again: Scoring 64
+ 4.16 SMTP Support (OPTIONAL) ........................................ 65
+ 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 66
+ 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 66
+ 4.19 Compressed folders Support (OPTIONAL) .......................... 66
+ 4.19.1 Open a compressed mailbox for reading 67
+ 4.19.2 Write a compressed mailbox 68
+ 4.19.3 Append a message to a compressed mailbox 68
+ 4.19.4 Encrypted folders 69
+
+ 5. Mutt-ng's MIME Support ............................................... 69
+ 5.1 Using MIME in Mutt ............................................. 69
+ 5.1.1 Viewing MIME messages in the pager 69
+ 5.1.2 The Attachment Menu 70
+ 5.1.3 The Compose Menu 70
+ 5.2 MIME Type configuration with mime.types ........................ 71
+ 5.3 MIME Viewer configuration with mailcap ......................... 71
+ 5.3.1 The Basics of the mailcap file 72
+ 5.3.2 Secure use of mailcap 73
+ 5.3.3 Advanced mailcap Usage 73
+ 5.3.4 Example mailcap files 76
+ 5.4 MIME Autoview .................................................. 77
+ 5.5 MIME Multipart/Alternative ..................................... 78
+ 5.6 MIME Lookup .................................................... 78
+
+ 6. Security Considerations ............................................ 79
+ 6.1 Passwords .................................................. 79
+ 6.2 Temporary Files ............................................ 79
+ 6.3 Information Leaks ............................................ 80
+ 6.3.1 Message-ID: headers 80
+ 6.3.2 mailto:-style links 80
+ 6.4 External applications ...................................... 80
+ 6.4.1 mailcap 80
+ 6.4.2 Other 81
+
+ 7. Reference ............................................................ 81
+ 7.1 Command line options ........................................... 81
+ 7.2 Patterns ....................................................... 82
+ 7.3 Configuration Commands ......................................... 84
+ 7.4 Configuration variables .......................................... 86
iii
- 7.4.7 allow_ansi 88
- 7.4.8 arrow_cursor 88
- 7.4.9 ascii_chars 88
- 7.4.10 askbcc 89
- 7.4.11 askcc 89
- 7.4.12 assumed_charset 89
- 7.4.13 attach_format 89
- 7.4.14 attach_remind_regexp 90
- 7.4.15 attach_sep 90
- 7.4.16 attach_split 91
- 7.4.17 attribution 91
- 7.4.18 auto_tag 91
- 7.4.19 autoedit 91
- 7.4.20 beep 92
- 7.4.21 beep_new 92
- 7.4.22 bounce 92
- 7.4.23 bounce_delivered 92
- 7.4.24 braille_friendly 92
- 7.4.25 certificate_file 92
- 7.4.26 charset 93
- 7.4.27 check_new 93
- 7.4.28 collapse_unread 93
- 7.4.29 compose_format 93
- 7.4.30 config_charset 94
- 7.4.31 confirmappend 94
- 7.4.32 confirmcreate 94
- 7.4.33 connect_timeout 94
- 7.4.34 content_type 95
- 7.4.35 copy 95
- 7.4.36 crypt_autoencrypt 95
- 7.4.37 crypt_autopgp 95
- 7.4.38 crypt_autosign 95
- 7.4.39 crypt_autosmime 96
- 7.4.40 crypt_replyencrypt 96
- 7.4.41 crypt_replysign 96
- 7.4.42 crypt_replysignencrypted 96
- 7.4.43 crypt_timestamp 96
- 7.4.44 crypt_use_gpgme 97
- 7.4.45 crypt_verify_sig 97
- 7.4.46 date_format 97
- 7.4.47 default_hook 97
- 7.4.48 delete 98
- 7.4.49 delete_space 98
- 7.4.50 delete_untag 98
- 7.4.51 digest_collapse 98
- 7.4.52 display_filter 98
- 7.4.53 dotlock_program 99
- 7.4.54 dsn_notify 99
- 7.4.55 dsn_return 99
- 7.4.56 duplicate_threads 99
- 7.4.57 edit_headers 100
- 7.4.58 editor 100
- 7.4.59 encode_from 100
+ 7.4.1 abort_noattach 87
+ 7.4.2 abort_nosubject 88
+ 7.4.3 abort_unmodified 88
+ 7.4.4 agent_string 88
+ 7.4.5 alias_file 88
+ 7.4.6 alias_format 88
+ 7.4.7 allow_8bit 89
+ 7.4.8 allow_ansi 89
+ 7.4.9 arrow_cursor 89
+ 7.4.10 ascii_chars 90
+ 7.4.11 askbcc 90
+ 7.4.12 askcc 90
+ 7.4.13 assumed_charset 90
+ 7.4.14 attach_format 90
+ 7.4.15 attach_remind_regexp 91
+ 7.4.16 attach_sep 92
+ 7.4.17 attach_split 92
+ 7.4.18 attribution 92
+ 7.4.19 auto_tag 92
+ 7.4.20 autoedit 92
+ 7.4.21 beep 93
+ 7.4.22 beep_new 93
+ 7.4.23 bounce 93
+ 7.4.24 bounce_delivered 93
+ 7.4.25 braille_friendly 93
+ 7.4.26 certificate_file 94
+ 7.4.27 charset 94
+ 7.4.28 check_new 94
+ 7.4.29 collapse_unread 94
+ 7.4.30 compose_format 95
+ 7.4.31 config_charset 95
+ 7.4.32 confirmappend 95
+ 7.4.33 confirmcreate 95
+ 7.4.34 connect_timeout 95
+ 7.4.35 content_type 96
+ 7.4.36 copy 96
+ 7.4.37 crypt_autoencrypt 96
+ 7.4.38 crypt_autopgp 96
+ 7.4.39 crypt_autosign 97
+ 7.4.40 crypt_autosmime 97
+ 7.4.41 crypt_replyencrypt 97
+ 7.4.42 crypt_replysign 97
+ 7.4.43 crypt_replysignencrypted 97
+ 7.4.44 crypt_timestamp 98
+ 7.4.45 crypt_use_gpgme 98
+ 7.4.46 crypt_verify_sig 98
+ 7.4.47 date_format 98
+ 7.4.48 default_hook 99
+ 7.4.49 delete 99
+ 7.4.50 delete_space 99
+ 7.4.51 delete_untag 99
+ 7.4.52 digest_collapse 99
+ 7.4.53 display_filter 100
iv
- 7.4.60 entropy_file 100
- 7.4.61 envelope_from 101
- 7.4.62 escape 101
- 7.4.63 fast_reply 101
- 7.4.64 fcc_attach 101
- 7.4.65 fcc_clear 101
- 7.4.66 file_charset 101
- 7.4.67 folder 102
- 7.4.68 folder_format 102
- 7.4.69 followup_to 103
- 7.4.70 force_buffy_check 103
- 7.4.71 force_name 103
- 7.4.72 forward_decode 104
- 7.4.73 forward_decrypt 104
- 7.4.74 forward_edit 104
- 7.4.75 forward_format 104
- 7.4.76 forward_quote 104
- 7.4.77 from 105
- 7.4.78 gecos_mask 105
- 7.4.79 hdrs 105
- 7.4.80 header 105
- 7.4.81 header_cache 106
- 7.4.82 header_cache_compress 106
- 7.4.83 help 106
- 7.4.84 hidden_host 106
- 7.4.85 hide_limited 107
- 7.4.86 hide_missing 107
- 7.4.87 hide_thread_subject 107
- 7.4.88 hide_top_limited 107
- 7.4.89 hide_top_missing 107
- 7.4.90 history 107
- 7.4.91 honor_followup_to 108
- 7.4.92 hostname 108
- 7.4.93 ignore_list_reply_to 108
- 7.4.94 imap_authenticators 108
- 7.4.95 imap_check_subscribed 109
- 7.4.96 imap_delim_chars 109
- 7.4.97 imap_headers 109
- 7.4.98 imap_home_namespace 109
- 7.4.99 imap_keepalive 110
- 7.4.100 imap_list_subscribed 110
- 7.4.101 imap_login 110
- 7.4.102 imap_mail_check 110
- 7.4.103 imap_pass 111
- 7.4.104 imap_passive 111
- 7.4.105 imap_peek 111
- 7.4.106 imap_reconnect 111
- 7.4.107 imap_servernoise 112
- 7.4.108 imap_user 112
- 7.4.109 implicit_autoview 112
- 7.4.110 include 112
- 7.4.111 include_onlyfirst 112
- 7.4.112 indent_string 113
+ 7.4.54 dotlock_program 100
+ 7.4.55 dsn_notify 100
+ 7.4.56 dsn_return 100
+ 7.4.57 duplicate_threads 101
+ 7.4.58 edit_headers 101
+ 7.4.59 editor 101
+ 7.4.60 encode_from 101
+ 7.4.61 entropy_file 101
+ 7.4.62 envelope_from 102
+ 7.4.63 escape 102
+ 7.4.64 fast_reply 102
+ 7.4.65 fcc_attach 102
+ 7.4.66 fcc_clear 102
+ 7.4.67 file_charset 103
+ 7.4.68 folder 103
+ 7.4.69 folder_format 103
+ 7.4.70 followup_to 104
+ 7.4.71 force_buffy_check 104
+ 7.4.72 force_name 105
+ 7.4.73 forward_decode 105
+ 7.4.74 forward_decrypt 105
+ 7.4.75 forward_edit 105
+ 7.4.76 forward_format 105
+ 7.4.77 forward_quote 106
+ 7.4.78 from 106
+ 7.4.79 gecos_mask 106
+ 7.4.80 hdrs 106
+ 7.4.81 header 107
+ 7.4.82 header_cache 107
+ 7.4.83 header_cache_compress 107
+ 7.4.84 help 107
+ 7.4.85 hidden_host 108
+ 7.4.86 hide_limited 108
+ 7.4.87 hide_missing 108
+ 7.4.88 hide_thread_subject 108
+ 7.4.89 hide_top_limited 108
+ 7.4.90 hide_top_missing 108
+ 7.4.91 history 109
+ 7.4.92 honor_followup_to 109
+ 7.4.93 hostname 109
+ 7.4.94 ignore_list_reply_to 109
+ 7.4.95 imap_authenticators 109
+ 7.4.96 imap_check_subscribed 110
+ 7.4.97 imap_delim_chars 110
+ 7.4.98 imap_headers 110
+ 7.4.99 imap_home_namespace 111
+ 7.4.100 imap_keepalive 111
+ 7.4.101 imap_list_subscribed 111
+ 7.4.102 imap_login 111
+ 7.4.103 imap_mail_check 112
+ 7.4.104 imap_pass 112
+ 7.4.105 imap_passive 112
+ 7.4.106 imap_peek 112
v
- 7.4.113 index_format 113
- 7.4.114 ispell 115
- 7.4.115 keep_flagged 116
- 7.4.116 list_reply 116
- 7.4.117 locale 116
- 7.4.118 mail_check 116
- 7.4.119 mailcap_path 116
- 7.4.120 mailcap_sanitize 117
- 7.4.121 maildir_header_cache_verify 117
- 7.4.122 maildir_trash 117
- 7.4.123 mark_old 117
- 7.4.124 markers 118
- 7.4.125 mask 118
- 7.4.126 max_display_recips 118
- 7.4.127 max_line_length 118
- 7.4.128 mbox 118
- 7.4.129 mbox_type 118
- 7.4.130 menu_context 119
- 7.4.131 menu_move_off 119
- 7.4.132 menu_scroll 119
- 7.4.133 message_format 119
- 7.4.134 meta_key 119
- 7.4.135 metoo 120
- 7.4.136 mh_purge 120
- 7.4.137 mh_seq_flagged 120
- 7.4.138 mh_seq_replied 120
- 7.4.139 mh_seq_unseen 120
- 7.4.140 mime_forward 120
- 7.4.141 mime_forward_decode 121
- 7.4.142 mime_forward_rest 121
- 7.4.143 mix_entry_format 121
- 7.4.144 mixmaster 122
- 7.4.145 move 122
- 7.4.146 msgid_format 122
- 7.4.147 narrow_tree 123
- 7.4.148 nntp_ask_followup_to 123
- 7.4.149 nntp_ask_x_comment_to 123
- 7.4.150 nntp_cache_dir 124
- 7.4.151 nntp_catchup 124
- 7.4.152 nntp_context 124
- 7.4.153 nntp_followup_to_poster 124
- 7.4.154 nntp_group_index_format 125
- 7.4.155 nntp_host 125
- 7.4.156 nntp_inews 125
- 7.4.157 nntp_load_description 126
- 7.4.158 nntp_mail_check 126
- 7.4.159 nntp_mime_subject 126
- 7.4.160 nntp_newsrc 126
- 7.4.161 nntp_pass 127
- 7.4.162 nntp_post_moderated 127
- 7.4.163 nntp_reconnect 127
- 7.4.164 nntp_save_unsubscribed 127
- 7.4.165 nntp_show_new_news 128
+ 7.4.107 imap_reconnect 113
+ 7.4.108 imap_servernoise 113
+ 7.4.109 imap_user 113
+ 7.4.110 implicit_autoview 113
+ 7.4.111 include 113
+ 7.4.112 include_onlyfirst 114
+ 7.4.113 indent_string 114
+ 7.4.114 index_format 114
+ 7.4.115 ispell 117
+ 7.4.116 keep_flagged 117
+ 7.4.117 list_reply 117
+ 7.4.118 locale 117
+ 7.4.119 mail_check 117
+ 7.4.120 mailcap_path 118
+ 7.4.121 mailcap_sanitize 118
+ 7.4.122 maildir_header_cache_verify 118
+ 7.4.123 maildir_trash 118
+ 7.4.124 mark_old 118
+ 7.4.125 markers 119
+ 7.4.126 mask 119
+ 7.4.127 max_display_recips 119
+ 7.4.128 max_line_length 119
+ 7.4.129 mbox 119
+ 7.4.130 mbox_type 120
+ 7.4.131 menu_context 120
+ 7.4.132 menu_move_off 120
+ 7.4.133 menu_scroll 120
+ 7.4.134 message_format 120
+ 7.4.135 meta_key 121
+ 7.4.136 metoo 121
+ 7.4.137 mh_purge 121
+ 7.4.138 mh_seq_flagged 121
+ 7.4.139 mh_seq_replied 121
+ 7.4.140 mh_seq_unseen 121
+ 7.4.141 mime_forward 122
+ 7.4.142 mime_forward_decode 122
+ 7.4.143 mime_forward_rest 122
+ 7.4.144 mix_entry_format 122
+ 7.4.145 mixmaster 123
+ 7.4.146 move 123
+ 7.4.147 msgid_format 123
+ 7.4.148 narrow_tree 124
+ 7.4.149 nntp_ask_followup_to 124
+ 7.4.150 nntp_ask_x_comment_to 124
+ 7.4.151 nntp_cache_dir 125
+ 7.4.152 nntp_catchup 125
+ 7.4.153 nntp_context 125
+ 7.4.154 nntp_followup_to_poster 125
+ 7.4.155 nntp_group_index_format 126
+ 7.4.156 nntp_host 126
+ 7.4.157 nntp_inews 126
+ 7.4.158 nntp_load_description 127
+ 7.4.159 nntp_mail_check 127
vi
- 7.4.166 nntp_show_only_unread 128
- 7.4.167 nntp_user 128
- 7.4.168 nntp_x_comment_to 128
- 7.4.169 operating_system 128
- 7.4.170 pager 129
- 7.4.171 pager_context 129
- 7.4.172 pager_format 129
- 7.4.173 pager_index_lines 129
- 7.4.174 pager_stop 130
- 7.4.175 pgp_auto_decode 130
- 7.4.176 pgp_autoinline 130
- 7.4.177 pgp_check_exit 130
- 7.4.178 pgp_clearsign_command 131
- 7.4.179 pgp_decode_command 131
- 7.4.180 pgp_decrypt_command 131
- 7.4.181 pgp_encrypt_only_command 132
- 7.4.182 pgp_encrypt_sign_command 132
- 7.4.183 pgp_entry_format 132
- 7.4.184 pgp_export_command 133
- 7.4.185 pgp_getkeys_command 133
- 7.4.186 pgp_good_sign 133
- 7.4.187 pgp_ignore_subkeys 133
- 7.4.188 pgp_import_command 133
- 7.4.189 pgp_list_pubring_command 133
- 7.4.190 pgp_list_secring_command 134
- 7.4.191 pgp_long_ids 134
- 7.4.192 pgp_mime_auto 134
- 7.4.193 pgp_replyinline 134
- 7.4.194 pgp_retainable_sigs 135
- 7.4.195 pgp_show_unusable 135
- 7.4.196 pgp_sign_as 135
- 7.4.197 pgp_sign_command 135
- 7.4.198 pgp_sort_keys 135
- 7.4.199 pgp_strict_enc 136
- 7.4.200 pgp_timeout 136
- 7.4.201 pgp_use_gpg_agent 136
- 7.4.202 pgp_verify_command 136
- 7.4.203 pgp_verify_key_command 137
- 7.4.204 pipe_decode 137
- 7.4.205 pipe_sep 137
- 7.4.206 pipe_split 137
- 7.4.207 pop_auth_try_all 137
- 7.4.208 pop_authenticators 138
- 7.4.209 pop_delete 138
- 7.4.210 pop_host 138
- 7.4.211 pop_last 138
- 7.4.212 pop_mail_check 139
- 7.4.213 pop_pass 139
- 7.4.214 pop_reconnect 139
- 7.4.215 pop_user 139
- 7.4.216 post_indent_string 139
- 7.4.217 postpone 140
- 7.4.218 postponed 140
+ 7.4.160 nntp_mime_subject 127
+ 7.4.161 nntp_newsrc 127
+ 7.4.162 nntp_pass 128
+ 7.4.163 nntp_post_moderated 128
+ 7.4.164 nntp_reconnect 128
+ 7.4.165 nntp_save_unsubscribed 129
+ 7.4.166 nntp_show_new_news 129
+ 7.4.167 nntp_show_only_unread 129
+ 7.4.168 nntp_user 129
+ 7.4.169 nntp_x_comment_to 129
+ 7.4.170 operating_system 130
+ 7.4.171 pager 130
+ 7.4.172 pager_context 130
+ 7.4.173 pager_format 130
+ 7.4.174 pager_index_lines 130
+ 7.4.175 pager_stop 131
+ 7.4.176 pgp_auto_decode 131
+ 7.4.177 pgp_autoinline 131
+ 7.4.178 pgp_check_exit 132
+ 7.4.179 pgp_clearsign_command 132
+ 7.4.180 pgp_decode_command 132
+ 7.4.181 pgp_decrypt_command 132
+ 7.4.182 pgp_encrypt_only_command 133
+ 7.4.183 pgp_encrypt_sign_command 133
+ 7.4.184 pgp_entry_format 133
+ 7.4.185 pgp_export_command 134
+ 7.4.186 pgp_getkeys_command 134
+ 7.4.187 pgp_good_sign 134
+ 7.4.188 pgp_ignore_subkeys 134
+ 7.4.189 pgp_import_command 134
+ 7.4.190 pgp_list_pubring_command 135
+ 7.4.191 pgp_list_secring_command 135
+ 7.4.192 pgp_long_ids 135
+ 7.4.193 pgp_mime_auto 135
+ 7.4.194 pgp_replyinline 135
+ 7.4.195 pgp_retainable_sigs 136
+ 7.4.196 pgp_show_unusable 136
+ 7.4.197 pgp_sign_as 136
+ 7.4.198 pgp_sign_command 136
+ 7.4.199 pgp_sort_keys 137
+ 7.4.200 pgp_strict_enc 137
+ 7.4.201 pgp_timeout 137
+ 7.4.202 pgp_use_gpg_agent 137
+ 7.4.203 pgp_verify_command 138
+ 7.4.204 pgp_verify_key_command 138
+ 7.4.205 pipe_decode 138
+ 7.4.206 pipe_sep 138
+ 7.4.207 pipe_split 138
+ 7.4.208 pop_auth_try_all 138
+ 7.4.209 pop_authenticators 139
+ 7.4.210 pop_delete 139
+ 7.4.211 pop_host 139
+ 7.4.212 pop_last 140
vii
- 7.4.219 preconnect 140
- 7.4.220 print 140
- 7.4.221 print_command 141
- 7.4.222 print_decode 141
- 7.4.223 print_split 141
- 7.4.224 prompt_after 141
- 7.4.225 query_command 141
- 7.4.226 quit 142
- 7.4.227 quote_empty 142
- 7.4.228 quote_quoted 142
- 7.4.229 quote_regexp 142
- 7.4.230 read_inc 142
- 7.4.231 read_only 143
- 7.4.232 realname 143
- 7.4.233 recall 143
- 7.4.234 record 143
- 7.4.235 reply_regexp 144
- 7.4.236 reply_self 144
- 7.4.237 reply_to 144
- 7.4.238 resolve 144
- 7.4.239 reverse_alias 144
- 7.4.240 reverse_name 145
- 7.4.241 reverse_realname 145
- 7.4.242 rfc2047_parameters 145
- 7.4.243 save_address 146
- 7.4.244 save_empty 146
- 7.4.245 save_name 146
- 7.4.246 score 146
- 7.4.247 score_threshold_delete 147
- 7.4.248 score_threshold_flag 147
- 7.4.249 score_threshold_read 147
- 7.4.250 send_charset 147
- 7.4.251 sendmail 147
- 7.4.252 sendmail_wait 148
- 7.4.253 shell 148
- 7.4.254 sidebar_boundary 148
- 7.4.255 sidebar_delim 148
- 7.4.256 sidebar_newmail_only 149
- 7.4.257 sidebar_number_format 149
- 7.4.258 sidebar_shorten_hierarchy 149
- 7.4.259 sidebar_visible 150
- 7.4.260 sidebar_width 150
- 7.4.261 sig_dashes 150
- 7.4.262 sig_on_top 150
- 7.4.263 signature 150
- 7.4.264 signoff_string 151
- 7.4.265 simple_search 151
- 7.4.266 sleep_time 151
- 7.4.267 smart_wrap 151
- 7.4.268 smileys 152
- 7.4.269 smime_ask_cert_label 152
- 7.4.270 smime_ca_location 152
- 7.4.271 smime_certificates 152
+ 7.4.213 pop_mail_check 140
+ 7.4.214 pop_pass 140
+ 7.4.215 pop_reconnect 140
+ 7.4.216 pop_user 140
+ 7.4.217 post_indent_string 141
+ 7.4.218 postpone 141
+ 7.4.219 postponed 141
+ 7.4.220 preconnect 141
+ 7.4.221 print 142
+ 7.4.222 print_command 142
+ 7.4.223 print_decode 142
+ 7.4.224 print_split 142
+ 7.4.225 prompt_after 142
+ 7.4.226 query_command 143
+ 7.4.227 quit 143
+ 7.4.228 quote_empty 143
+ 7.4.229 quote_quoted 143
+ 7.4.230 quote_regexp 143
+ 7.4.231 read_inc 144
+ 7.4.232 read_only 144
+ 7.4.233 realname 144
+ 7.4.234 recall 144
+ 7.4.235 record 144
+ 7.4.236 reply_regexp 145
+ 7.4.237 reply_self 145
+ 7.4.238 reply_to 145
+ 7.4.239 resolve 145
+ 7.4.240 reverse_alias 146
+ 7.4.241 reverse_name 146
+ 7.4.242 reverse_realname 146
+ 7.4.243 rfc2047_parameters 146
+ 7.4.244 save_address 147
+ 7.4.245 save_empty 147
+ 7.4.246 save_name 147
+ 7.4.247 score 148
+ 7.4.248 score_threshold_delete 148
+ 7.4.249 score_threshold_flag 148
+ 7.4.250 score_threshold_read 148
+ 7.4.251 send_charset 148
+ 7.4.252 sendmail 149
+ 7.4.253 sendmail_wait 149
+ 7.4.254 shell 149
+ 7.4.255 sidebar_boundary 149
+ 7.4.256 sidebar_delim 150
+ 7.4.257 sidebar_newmail_only 150
+ 7.4.258 sidebar_number_format 150
+ 7.4.259 sidebar_shorten_hierarchy 151
+ 7.4.260 sidebar_visible 151
+ 7.4.261 sidebar_width 151
+ 7.4.262 sig_dashes 151
+ 7.4.263 sig_on_top 151
+ 7.4.264 signature 152
+ 7.4.265 signoff_string 152
viii
- 7.4.272 smime_decrypt_command 152
- 7.4.273 smime_decrypt_use_default_key 153
- 7.4.274 smime_default_key 153
- 7.4.275 smime_encrypt_command 153
- 7.4.276 smime_encrypt_with 154
- 7.4.277 smime_get_cert_command 154
- 7.4.278 smime_get_cert_email_command 154
- 7.4.279 smime_get_signer_cert_command 154
- 7.4.280 smime_import_cert_command 154
- 7.4.281 smime_is_default 154
- 7.4.282 smime_keys 155
- 7.4.283 smime_pk7out_command 155
- 7.4.284 smime_sign_command 155
- 7.4.285 smime_sign_opaque_command 155
- 7.4.286 smime_timeout 156
- 7.4.287 smime_verify_command 156
- 7.4.288 smime_verify_opaque_command 156
- 7.4.289 smtp_envelope 156
- 7.4.290 smtp_host 156
- 7.4.291 smtp_pass 157
- 7.4.292 smtp_port 157
- 7.4.293 smtp_use_tls 157
- 7.4.294 smtp_user 157
- 7.4.295 sort 158
- 7.4.296 sort_alias 158
- 7.4.297 sort_aux 158
- 7.4.298 sort_browser 159
- 7.4.299 sort_re 159
- 7.4.300 spam_separator 159
- 7.4.301 spoolfile 160
- 7.4.302 ssl_ca_certificates_file 160
- 7.4.303 ssl_client_cert 160
- 7.4.304 ssl_force_tls 160
- 7.4.305 ssl_min_dh_prime_bits 160
- 7.4.306 ssl_starttls 161
- 7.4.307 ssl_use_sslv2 161
- 7.4.308 ssl_use_sslv3 161
- 7.4.309 ssl_use_tlsv1 161
- 7.4.310 ssl_usesystemcerts 161
- 7.4.311 status_chars 162
- 7.4.312 status_format 162
- 7.4.313 status_on_top 164
- 7.4.314 strict_mailto 164
- 7.4.315 strict_mime 165
- 7.4.316 strict_threads 165
- 7.4.317 strip_was 165
- 7.4.318 strip_was_regex 165
- 7.4.319 stuff_quoted 166
- 7.4.320 suspend 166
- 7.4.321 text_flowed 166
- 7.4.322 thorough_search 166
- 7.4.323 thread_received 166
- 7.4.324 tilde 167
+ 7.4.266 simple_search 152
+ 7.4.267 sleep_time 152
+ 7.4.268 smart_wrap 153
+ 7.4.269 smileys 153
+ 7.4.270 smime_ask_cert_label 153
+ 7.4.271 smime_ca_location 153
+ 7.4.272 smime_certificates 153
+ 7.4.273 smime_decrypt_command 154
+ 7.4.274 smime_decrypt_use_default_key 154
+ 7.4.275 smime_default_key 154
+ 7.4.276 smime_encrypt_command 155
+ 7.4.277 smime_encrypt_with 155
+ 7.4.278 smime_get_cert_command 155
+ 7.4.279 smime_get_cert_email_command 155
+ 7.4.280 smime_get_signer_cert_command 155
+ 7.4.281 smime_import_cert_command 156
+ 7.4.282 smime_is_default 156
+ 7.4.283 smime_keys 156
+ 7.4.284 smime_pk7out_command 156
+ 7.4.285 smime_sign_command 156
+ 7.4.286 smime_sign_opaque_command 157
+ 7.4.287 smime_timeout 157
+ 7.4.288 smime_verify_command 157
+ 7.4.289 smime_verify_opaque_command 157
+ 7.4.290 smtp_envelope 157
+ 7.4.291 smtp_host 157
+ 7.4.292 smtp_pass 158
+ 7.4.293 smtp_port 158
+ 7.4.294 smtp_use_tls 158
+ 7.4.295 smtp_user 159
+ 7.4.296 sort 159
+ 7.4.297 sort_alias 159
+ 7.4.298 sort_aux 159
+ 7.4.299 sort_browser 160
+ 7.4.300 sort_re 160
+ 7.4.301 spam_separator 161
+ 7.4.302 spoolfile 161
+ 7.4.303 ssl_ca_certificates_file 161
+ 7.4.304 ssl_client_cert 161
+ 7.4.305 ssl_force_tls 161
+ 7.4.306 ssl_min_dh_prime_bits 162
+ 7.4.307 ssl_starttls 162
+ 7.4.308 ssl_use_sslv2 162
+ 7.4.309 ssl_use_sslv3 162
+ 7.4.310 ssl_use_tlsv1 162
+ 7.4.311 ssl_usesystemcerts 163
+ 7.4.312 status_chars 163
+ 7.4.313 status_format 163
+ 7.4.314 status_on_top 165
+ 7.4.315 strict_mailto 166
+ 7.4.316 strict_mime 166
+ 7.4.317 strict_threads 166
+ 7.4.318 strip_was 166
ix
- 7.4.325 timeout 167
- 7.4.326 tmpdir 167
- 7.4.327 to_chars 167
- 7.4.328 trash 167
- 7.4.329 tunnel 168
- 7.4.330 umask 168
- 7.4.331 uncollapse_jump 168
- 7.4.332 use_8bitmime 168
- 7.4.333 use_domain 168
- 7.4.334 use_from 169
- 7.4.335 use_idn 169
- 7.4.336 use_ipv6 169
- 7.4.337 user_agent 169
- 7.4.338 visual 169
- 7.4.339 wait_key 170
- 7.4.340 weed 170
- 7.4.341 wrap_search 170
- 7.4.342 wrapmargin 170
- 7.4.343 write_bcc 170
- 7.4.344 write_inc 171
- 7.4.345 xterm_icon 171
- 7.4.346 xterm_leave 171
- 7.4.347 xterm_set_titles 171
- 7.4.348 xterm_title 171
- 7.5 Functions ....................................................... 172
- 7.5.1 generic 172
- 7.5.2 index 173
- 7.5.3 pager 175
- 7.5.4 alias 177
- 7.5.5 query 177
- 7.5.6 attach 177
- 7.5.7 compose 178
- 7.5.8 postpone 179
- 7.5.9 browser 179
- 7.5.10 pgp 180
- 7.5.11 editor 180
-
- 8. Miscellany ............................................................ 180
- 8.1 Acknowledgments ................................................. 181
- 8.2 About this document ............................................. 183
+ 7.4.319 strip_was_regex 167
+ 7.4.320 stuff_quoted 167
+ 7.4.321 suspend 167
+ 7.4.322 text_flowed 167
+ 7.4.323 thorough_search 167
+ 7.4.324 thread_received 168
+ 7.4.325 tilde 168
+ 7.4.326 timeout 168
+ 7.4.327 tmpdir 168
+ 7.4.328 to_chars 168
+ 7.4.329 trash 169
+ 7.4.330 tunnel 169
+ 7.4.331 umask 169
+ 7.4.332 uncollapse_jump 169
+ 7.4.333 use_8bitmime 169
+ 7.4.334 use_domain 170
+ 7.4.335 use_from 170
+ 7.4.336 use_idn 170
+ 7.4.337 use_ipv6 170
+ 7.4.338 visual 170
+ 7.4.339 wait_key 171
+ 7.4.340 weed 171
+ 7.4.341 wrap_search 171
+ 7.4.342 wrapmargin 171
+ 7.4.343 write_bcc 171
+ 7.4.344 write_inc 172
+ 7.4.345 xterm_icon 172
+ 7.4.346 xterm_leave 172
+ 7.4.347 xterm_set_titles 172
+ 7.4.348 xterm_title 172
+ 7.5 Functions ....................................................... 173
+ 7.5.1 generic 173
+ 7.5.2 index 174
+ 7.5.3 pager 176
+ 7.5.4 alias 178
+ 7.5.5 query 178
+ 7.5.6 attach 178
+ 7.5.7 compose 179
+ 7.5.8 postpone 180
+ 7.5.9 browser 180
+ 7.5.10 pgp 181
+ 7.5.11 editor 181
+
+ 8. Miscellany ............................................................ 181
+ 8.1 Acknowledgments ................................................. 182
+ 8.2 About this document ............................................. 184
x
#include "buffy.h"
#ifndef _MAKEDOC
-#define DT_MASK 0x0f
-#define DT_BOOL 1 /* boolean option */
-#define DT_NUM 2 /* a number */
-#define DT_STR 3 /* a string */
-#define DT_PATH 4 /* a pathname */
-#define DT_QUAD 5 /* quad-option (yes/no/ask-yes/ask-no) */
-#define DT_SORT 6 /* sorting methods */
-#define DT_RX 7 /* regular expressions */
-#define DT_MAGIC 8 /* mailbox type */
-#define DT_SYN 9 /* synonym for another variable */
-#define DT_ADDR 10 /* e-mail address */
+#define DT_MASK 0x0f
+#define DT_BOOL 1 /* boolean option */
+#define DT_NUM 2 /* a number */
+#define DT_STR 3 /* a string */
+#define DT_PATH 4 /* a pathname */
+#define DT_QUAD 5 /* quad-option (yes/no/ask-yes/ask-no) */
+#define DT_SORT 6 /* sorting methods */
+#define DT_RX 7 /* regular expressions */
+#define DT_MAGIC 8 /* mailbox type */
+#define DT_SYN 9 /* synonym for another variable */
+#define DT_ADDR 10 /* e-mail address */
+#define DT_USER 11 /* user defined viar $user_ */
#define DTYPE(x) ((x) & DT_MASK)
/* subtypes */
-#define DT_SUBTYPE_MASK 0xf0
-#define DT_SORT_ALIAS 0x10
+#define DT_SUBTYPE_MASK 0xf0
+#define DT_SORT_ALIAS 0x10
#define DT_SORT_BROWSER 0x20
-#define DT_SORT_KEYS 0x40
-#define DT_SORT_AUX 0x80
+#define DT_SORT_KEYS 0x40
+#define DT_SORT_AUX 0x80
/* flags to parse_set() */
-#define M_SET_INV (1<<0) /* default is to invert all vars */
-#define M_SET_UNSET (1<<1) /* default is to unset all vars */
-#define M_SET_RESET (1<<2) /* default is to reset all vars to default */
+#define M_SET_INV (1<<0) /* default is to invert all vars */
+#define M_SET_UNSET (1<<1) /* default is to unset all vars */
+#define M_SET_RESET (1<<2) /* default is to reset all vars to default */
/* forced redraw/resort types */
-#define R_NONE 0
-#define R_INDEX (1<<0)
-#define R_PAGER (1<<1)
-#define R_RESORT (1<<2) /* resort the mailbox */
-#define R_RESORT_SUB (1<<3) /* resort subthreads */
-#define R_RESORT_INIT (1<<4) /* resort from scratch */
-#define R_TREE (1<<5) /* redraw the thread tree */
-#define R_BOTH (R_INDEX|R_PAGER)
-#define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB)
+#define R_NONE 0
+#define R_INDEX (1<<0)
+#define R_PAGER (1<<1)
+#define R_RESORT (1<<2) /* resort the mailbox */
+#define R_RESORT_SUB (1<<3) /* resort subthreads */
+#define R_RESORT_INIT (1<<4) /* resort from scratch */
+#define R_TREE (1<<5) /* redraw the thread tree */
+#define R_BOTH (R_INDEX|R_PAGER)
+#define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB)
struct option_t {
char *option;
short type;
short flags;
unsigned long data;
- unsigned long init; /* initial value */
+ char* init;
};
struct feature_t {
struct option_t MuttVars[] = {
/*++*/
- {"abort_noattach", DT_QUAD, R_NONE, OPT_ATTACH, M_NO},
+ {"abort_noattach", DT_QUAD, R_NONE, OPT_ATTACH, "no" },
/*
** .pp
** This variable specifies whether to abort sending if no attachment
** was made but the content references them, i.e. the content
** matches the regular expression given in
- ** $$$attach_remind_regexp. If a match was found and this
+ ** $$attach_remind_regexp. If a match was found and this
** variable is set to \fIyes\fP, message sending will be aborted
** but the mail will be send nevertheless if set to \fIno\fP.
**
** .pp
- ** This variable and $$$attach_remind_regexp are intended to
+ ** This variable and $$attach_remind_regexp are intended to
** remind the user to attach files if the message's text
** references them.
**
** .pp
- ** See also the $$$attach_remind_regexp variable.
+ ** See also the $$attach_remind_regexp variable.
*/
- {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, M_ASKYES},
+ {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, "ask-yes" },
/*
** .pp
** If set to \fIyes\fP, when composing messages and no subject is given
** \fIno\fP, composing messages with no subject given at the subject
** prompt will never be aborted.
*/
- {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, M_YES},
+ {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, "yes" },
/*
** .pp
** If set to \fIyes\fP, composition will automatically abort after
** check only happens after the \fIfirst\fP edit of the file). When set
** to \fIno\fP, composition will never be aborted.
*/
- {"alias_file", DT_PATH, R_NONE, UL &AliasFile, UL "~/.muttngrc"},
+ {"alias_file", DT_PATH, R_NONE, UL &AliasFile, "~/.muttngrc"},
/*
** .pp
** The default file in which to save aliases created by the
** \fBNote:\fP Mutt-ng will not automatically source this file; you must
** explicitly use the ``$source'' command for it to be executed.
*/
- {"alias_format", DT_STR, R_NONE, UL &AliasFmt, UL "%4n %2f %t %-10a %r"},
+ {"alias_format", DT_STR, R_NONE, UL &AliasFmt, "%4n %2f %t %-10a %r"},
/*
** .pp
** Specifies the format of the data displayed for the ``alias'' menu. The
** .dt %t .dd character which indicates if the alias is tagged for inclusion
** .de
*/
- {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, 1},
+ {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, "yes" },
/*
** .pp
** Controls whether 8-bit data is converted to 7-bit using either
** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
*/
- {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, 0},
+ {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, "no" },
/*
** .pp
** Controls whether ANSI color codes in messages (and color tags in
** message could include a line like ``\fT[-- PGP output follows ...\fP" and
** give it the same color as your attachment color.
*/
- {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, 0},
+ {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, "no" },
/*
** .pp
** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
** be redrawn on the screen when moving to the next or previous entries
** in the menu.
*/
- {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, 0},
+ {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
** and attachment trees, instead of the default \fTACS\fP characters.
*/
- {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, 0},
+ {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
** before editing an outgoing message.
*/
- {"askcc", DT_BOOL, R_NONE, OPTASKCC, 0},
+ {"askcc", DT_BOOL, R_NONE, OPTASKCC, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
** editing the body of an outgoing message.
*/
- {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, UL "us-ascii"},
+ {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, "us-ascii"},
/*
** .pp
** This variable is a colon-separated list of character encoding
*/
#ifdef USE_NNTP
{"ask_followup_to", DT_SYN, R_NONE, UL "nntp_ask_followup_to", 0},
- {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, 0},
+ {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, "no" },
/*
** .pp
** Availability: NNTP
** field before editing the body of an outgoing news article.
*/
{"ask_x_comment_to", DT_SYN, R_NONE, UL "nntp_ask_x_comment_to", 0},
- {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, 0},
+ {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, "no" },
/*
** .pp
** Availability: NNTP
** field before editing the body of an outgoing news article.
*/
#endif
- {"attach_format", DT_STR, R_NONE, UL &AttachFormat, UL "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
+ {"attach_format", DT_STR, R_NONE, UL &AttachFormat, "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
/*
** .pp
** This variable describes the format of the ``attachment'' menu. The
** .dt %|X .dd pad to the end of the line with character "X"
** .de
*/
- {"attach_remind_regexp", DT_RX, R_NONE, UL &AttachRemindRegexp, UL "attach"},
+ {"attach_remind_regexp", DT_RX, R_NONE, UL &AttachRemindRegexp, "attach"},
/*
** .pp
** 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 $$$abort_noattach.
+ ** ask for what to do depending on the setting of $$abort_noattach.
** .pp
- ** This variable and $$$abort_noattach are intended to remind the user
+ ** This variable and $$abort_noattach are intended to remind the user
** to attach files if the message's text references them.
*/
- {"attach_sep", DT_STR, R_NONE, UL &AttachSep, UL "\n"},
+ {"attach_sep", DT_STR, R_NONE, UL &AttachSep, "\n"},
/*
** .pp
** The separator to add between attachments when operating (saving,
** printing, piping, etc) on a list of tagged attachments.
*/
- {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, 1},
+ {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, "yes" },
/*
** .pp
** If this variable is \fIunset\fP, when operating (saving, printing, piping,
** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
** Mutt-ng will operate on the attachments one by one.
*/
- {"attribution", DT_STR, R_NONE, UL &Attribution, UL "On %d, %n wrote:"},
+ {"attribution", DT_STR, R_NONE, UL &Attribution, "On %d, %n wrote:"},
/*
** .pp
** This is the string that will precede a message which has been included
** in a reply. For a full listing of defined \fTprintf(3)\fP-like sequences see
** the section on ``$$index_format''.
*/
- {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, 0},
+ {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, "no" },
/*
** .pp
** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
** .pp
** Also see ``$$fast_reply''.
*/
- {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, 0},
+ {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, "no" },
/*
** .pp
** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
** make the next function apply to all tagged messages.
*/
- {"beep", DT_BOOL, R_NONE, OPTBEEP, 1},
+ {"beep", DT_BOOL, R_NONE, OPTBEEP, "yes" },
/*
** .pp
** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
*/
- {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, 0},
+ {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, "no" },
/*
** .pp
** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
** notifying you of new mail. This is independent of the setting of the
** ``$$beep'' variable.
*/
- {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, M_ASKYES},
+ {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, "ask-yes" },
/*
** .pp
** Controls whether you will be asked to confirm bouncing messages.
** message. Setting this variable to \fIno\fP is not generally useful,
** and thus not recommended, because you are unable to bounce messages.
*/
- {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, 1},
+ {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, "yes" },
/*
** .pp
** When this variable is \fIset\fP, Mutt-ng will include
** \fTDelivered-To:\fP header fields when bouncing messages.
** Postfix users may wish to \fIunset\fP this variable.
*/
- { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, 0 },
+ { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, "no" },
/*
** .pp
** When this variable is set, mutt will place the cursor at the beginning
*/
#ifdef USE_NNTP
{"catchup_newsgroup", DT_SYN, R_NONE, UL "nntp_catchup", 0},
- {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, M_ASKYES},
+ {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, "ask-yes" },
/*
** .pp
** Availability: NNTP
** as read when you leaving it.
*/
#endif
- {"charset", DT_STR, R_NONE, UL &Charset, UL 0},
+ {"charset", DT_STR, R_NONE, UL &Charset, "" },
/*
** .pp
** Character set your terminal uses to display and enter textual data.
*/
- {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, 1},
+ {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, "yes" },
/*
** .pp
** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
** checking each file to see if it has already been looked at. If it's
** \fIunset\fP, no check for new mail is performed while the mailbox is open.
*/
- {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, 1},
+ {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, "yes" },
/*
** .pp
** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
** unread messages.
*/
- {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, 0},
+ {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
** when the current thread is \fIun\fPcollapsed.
*/
- {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, UL "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
+ {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
/*
** .pp
** Controls the format of the status line displayed in the ``compose''
** See the text describing the ``$$status_format'' option for more
** information on how to set ``$$compose_format''.
*/
- {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, UL 0},
+ {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, "" },
/*
** .pp
** When defined, Mutt-ng will recode commands in rc files from this
** encoding.
*/
- {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, 1},
+ {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
** an existing mailbox.
*/
- {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, 1},
+ {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
** mailbox which does not yet exist before creating it.
*/
- {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, 30},
+ {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, "30" },
/*
** .pp
** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
** many seconds if the connection is not able to be established. A negative
** value causes Mutt-ng to wait indefinitely for the connection to succeed.
*/
- {"content_type", DT_STR, R_NONE, UL &ContentType, UL "text/plain"},
+ {"content_type", DT_STR, R_NONE, UL &ContentType, "text/plain"},
/*
** .pp
** Sets the default \fTContent-Type:\fP header field for the body
** of newly composed messages.
*/
- {"copy", DT_QUAD, R_NONE, OPT_COPY, M_YES},
+ {"copy", DT_QUAD, R_NONE, OPT_COPY, "yes" },
/*
** .pp
** This variable controls whether or not copies of your outgoing messages
** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
*/
- {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, 0},
+ {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, "no" },
/*
** .pp
** This variable controls the use the GPGME enabled crypto backends.
** file as it won't have any effect when used interactively.
*/
- {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, 1},
+ {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, "yes" },
/*
** .pp
** This variable controls whether or not Mutt-ng may automatically enable
** ``$$crypt_replyencrypt'',
** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
*/
- {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, 1},
+ {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, "yes" },
/*
** .pp
** This variable controls whether or not Mutt-ng may automatically enable
** ``$$crypt_replyencrypt'',
** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
*/
- {"date_format", DT_STR, R_BOTH, UL &DateFmt, UL "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
+ {"date_format", DT_STR, R_BOTH, UL &DateFmt, "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
/*
** .pp
** This variable controls the format of the date printed by the ``\fT%d\fP''
** rest of the string are expanded in the \fIC\fP locale (that is in US
** English).
*/
- {"default_hook", DT_STR, R_NONE, UL &DefaultHook, UL "~f %s !~P | (~P ~C %s)"},
+ {"default_hook", DT_STR, R_NONE, UL &DefaultHook, "~f %s !~P | (~P ~C %s)"},
/*
** .pp
** This variable controls how send-hooks, message-hooks, save-hooks,
** ``alternates'') and is to or cc'ed to a user matching the given
** regular expression.
*/
- {"delete", DT_QUAD, R_NONE, OPT_DELETE, M_ASKYES},
+ {"delete", DT_QUAD, R_NONE, OPT_DELETE, "ask-yes" },
/*
** .pp
** Controls whether or not messages are really deleted when closing or
** deleting will automatically be purged without prompting. If set to
** \fIno\fP, messages marked for deletion will be kept in the mailbox.
*/
- {"delete_space", DT_BOOL, R_NONE, OPTDELSP, 0},
+ {"delete_space", DT_BOOL, R_NONE, OPTDELSP, "no" },
/*
** .pp
** When sending messages with \fTformat=flowed\fP by \fIsetting\fP the
- ** $$$text_flowed variable, this variable specifies whether to also
+ ** $$text_flowed variable, this variable specifies whether to also
** set the \fTDelSp\fP parameter to \fTyes\fP. If this is \fIunset\fP,
** no additional parameter will be send as a value of \fTno\fP already
** is the default behavior.
**
** .pp
** \fBNote:\fP this variable only has an effect on \fIoutgoing\fP messages
- ** (if $$$text_flowed is \fIset\fP) but not on incomming.
+ ** (if $$text_flowed is \fIset\fP) but not on incomming.
*/
- {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, 1},
+ {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, "yes" },
/*
** .pp
** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
** for deletion. This applies when you either explicitly delete a message,
** or when you save it to another folder.
*/
- {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, 1},
+ {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, "yes" },
/*
** .pp
** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
*/
- {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, UL ""},
+ {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, ""},
/*
** .pp
** When \fIset\fP, specifies a command used to filter messages. When a message
** filtered message is read from the standard output.
*/
#if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
- {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, UL BINDIR "/muttng_dotlock"},
+ {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, BINDIR "/muttng_dotlock"},
/*
** .pp
** Availability: Standalone and Dotlock
** Mutt-ng.
*/
#endif
- {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, UL ""},
+ {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, ""},
/*
** .pp
** \fBNote:\fP you should not enable this unless you are using Sendmail
** .pp
** Example: \fTset dsn_notify="failure,delay"\fP
*/
- {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, UL ""},
+ {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, ""},
/*
** .pp
** \fBNote:\fP you should not enable this unless you are using Sendmail
** .pp
** Example: \fTset dsn_return=hdrs\fP
*/
- {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, 1},
+ {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, "yes" },
/*
** .pp
** This variable controls whether Mutt-ng, when sorting by threads, threads
** If it is \fIset\fP, it will indicate that it thinks they are duplicates
** of each other with an equals sign in the thread diagram.
*/
- {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, 0},
+ {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, "no" },
/*
** .pp
** This option allows you to edit the header of your outgoing messages
** along with the body of your message.
*/
- {"editor", DT_PATH, R_NONE, UL &Editor, 0},
+ {"editor", DT_PATH, R_NONE, UL &Editor, "" },
/*
** .pp
** This variable specifies which editor is used by Mutt-ng.
** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
** variable, or to the string "\fTvi\fP" if neither of those are set.
*/
- {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, 0},
+ {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
** you must take care of space-stuffing <tt/From / lines (with a trailing
** space) yourself.
*/
- {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, 0},
+ {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
** or if the sendmail on your machine doesn't support that command
** line switch.
*/
- {"escape", DT_STR, R_NONE, UL &EscChar, UL "~"},
+ {"escape", DT_STR, R_NONE, UL &EscChar, "~"},
/*
** .pp
** Escape character to use for functions in the builtin editor.
*/
- {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, 0},
+ {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, "no" },
/*
** .pp
** When \fIset\fP, the initial prompt for recipients and subject are skipped
** \fBNote:\fP this variable has no effect when the ``$$autoedit''
** variable is \fIset\fP.
*/
- {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, 1},
+ {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, "yes" },
/*
** .pp
** This variable controls whether or not attachments on outgoing messages
** are saved along with the main body of your message.
*/
- {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, 0},
+ {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, "no" },
/*
** .pp
** When this variable is \fIset\fP, FCCs will be stored unencrypted and
** signed.
** (PGP only)
*/
- {"file_charset", DT_STR, R_NONE, UL &FileCharset, UL 0},
+ {"file_charset", DT_STR, R_NONE, UL &FileCharset, "" },
/*
** .pp
** This variable is a colon-separated list of character encoding
** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
** if included.
*/
- {"folder", DT_PATH, R_NONE, UL &Maildir, UL "~/Mail"},
+ {"folder", DT_PATH, R_NONE, UL &Maildir, "~/Mail"},
/*
** .pp
** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
** you use ``+'' or ``='' for any other variables since expansion takes place
** during the ``set'' command.
*/
- {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, UL "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
+ {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
/*
** .pp
** This variable allows you to customize the file browser display to your
** .dt %|X .dd pad to the end of the line with character "X"
** .de
*/
- {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, 1},
+ {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, "yes" },
/*
** .pp
** Controls whether or not the \fTMail-Followup-To:\fP header field is
*/
#ifdef USE_NNTP
{"followup_to_poster", DT_SYN, R_NONE, UL "nntp_followup_to_poster", 0},
- {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, M_ASKYES},
+ {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, "ask-yes" },
/*
** .pp
** Availability: NNTP
** message via mail.
*/
#endif
- {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, 0},
+ {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, "no" },
/*
** .pp
** This variable is similar to ``$$save_name'', except that Mutt-ng will
** .pp
** Also see the ``$$record'' variable.
*/
- {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, 0},
+ {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, "no" },
/*
** .pp
** When \fIset\fP, it causes Mutt-ng to check for new mail when the
** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
** ``$$imap_mail_check''.
*/
- {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, 1},
+ {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, "yes" },
/*
** .pp
** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
** otherwise ``$$mime_forward_decode'' is used instead.
*/
- {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES},
+ {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, "yes" },
/*
** .pp
** This quadoption controls whether or not the user is automatically
** placed in the editor when forwarding messages. For those who always want
** to forward with no modification, use a setting of \fIno\fP.
*/
- {"forward_format", DT_STR, R_NONE, UL &ForwFmt, UL "[%a: %s]"},
+ {"forward_format", DT_STR, R_NONE, UL &ForwFmt, "[%a: %s]"},
/*
** .pp
** This variable controls the default subject when forwarding a message.
** It uses the same format sequences as the ``$$index_format'' variable.
*/
- {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, 0},
+ {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, "no" },
/*
** .pp
** When \fIset\fP forwarded messages included in the main body of the
** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
** ``$$indent_string''.
*/
- {"from", DT_ADDR, R_NONE, UL &From, UL 0},
+ {"from", DT_ADDR, R_NONE, UL &From, "" },
/*
** .pp
** This variable contains a default from address. It
** .pp
** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
*/
- {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, UL "^[^,]*"},
+ {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, "^[^,]*"},
/*
** .pp
** A regular expression used by Mutt-ng to parse the GECOS field of a password
*/
#ifdef USE_NNTP
{"group_index_format", DT_SYN, R_NONE, UL "nntp_group_index_format", 0},
- {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, UL "%4C %M%N %5s %-45.45f %d"},
+ {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, "%4C %M%N %5s %-45.45f %d"},
/*
** .pp
** Availability: NNTP
** .te
*/
#endif
- {"hdrs", DT_BOOL, R_NONE, OPTHDRS, 1},
+ {"hdrs", DT_BOOL, R_NONE, OPTHDRS, "yes" },
/*
** .pp
** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
** composing a new message or replying in order to take effect. If \fIset\fP,
** the user defined header fields are added to every new message.
*/
- {"header", DT_BOOL, R_NONE, OPTHEADER, 0},
+ {"header", DT_BOOL, R_NONE, OPTHEADER, "no" },
/*
** .pp
** When \fIset\fP, this variable causes Mutt-ng to include the header
** of the message you are replying to into the edit buffer.
** The ``$$weed'' setting applies.
*/
- {"help", DT_BOOL, R_BOTH, OPTHELP, 1},
+ {"help", DT_BOOL, R_BOTH, OPTHELP, "yes" },
/*
** .pp
** When \fIset\fP, help lines describing the bindings for the major functions
** running. Since this variable is primarily aimed at new users, neither
** of these should present a major problem.
*/
- {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, 0},
+ {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
** cut-off of first-level domains.
*/
- {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, 0},
+ {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
** by limiting, in the thread tree.
*/
- {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, 1},
+ {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
** thread tree.
*/
- {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, 1},
+ {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
** tree that have the same subject as their parent or closest previously
** displayed sibling.
*/
- {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, 0},
+ {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, "no" },
/*
** .pp
** When \fIset\fP, 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
** $$hide_missing is set, this option will have no effect.
*/
- {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, 1},
+ {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
** top of threads in the thread tree. Note that when $$hide_limited is
** \fIset\fP, this option will have no effect.
*/
- {"history", DT_NUM, R_NONE, UL &HistSize, 10},
+ {"history", DT_NUM, R_NONE, UL &HistSize, "10" },
/*
** .pp
** This variable controls the size (in number of strings remembered) of
** the string history buffer. The buffer is cleared each time the
** variable is changed.
*/
- {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES},
+ {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, "yes" },
/*
** .pp
** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
** honored when group-replying to a message.
*/
- {"hostname", DT_STR, R_NONE, UL &Fqdn, 0},
+ {"hostname", DT_STR, R_NONE, UL &Fqdn, "" },
/*
** .pp
** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
** Please be sure to really know what you are doing when changing this variable
** to configure a custom domain part of Message-IDs.
*/
- {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, 0},
+ {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, "no" },
/*
** .pp
** Affects the behaviour of the \fIreply\fP function when replying to
** list.
*/
#ifdef USE_IMAP
- {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, UL 0},
+ {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, "" },
/*
** .pp
** Availability: IMAP
** the previous methods are unavailable. If a method is available but
** authentication fails, Mutt-ng will not connect to the IMAP server.
*/
- { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, 0 },
+ { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, "no" },
/*
** .pp
** When \fIset\fP, mutt will fetch the set of subscribed folders from
** it polls for new mail. See also the ``$mailboxes'' command.
*/
- {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, UL "/."},
+ {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, "/."},
/*
** .pp
** Availability: IMAP
** as folder separators for displaying IMAP paths. In particular it
** helps in using the '\fT=\fP' shortcut for your $$folder variable.
*/
- {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, UL 0},
+ {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, "" },
/*
** .pp
** Availability: IMAP
** .pp
** \fBNote:\fP This is a space separated list.
*/
- {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, UL 0},
+ {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, "" },
/*
** .pp
** Availability: IMAP
** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
** this variable to the IMAP path to your folders.
*/
- {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, 900},
+ {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, "900" },
/*
** .pp
** Availability: IMAP
** Reduce this number if you find yourself
** getting disconnected from your IMAP server due to inactivity.
*/
- {"imap_login", DT_STR, R_NONE, UL &ImapLogin, 0 },
+ {"imap_login", DT_STR, R_NONE, UL &ImapLogin, "" },
/*
** .pp
** Availability: IMAP
** .pp
** This variable defaults to the value of ``$$imap_user.''
*/
- {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, 0},
+ {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, "no" },
/*
** .pp
** Availability: IMAP
** only subscribed folders or all folders. This can be toggled in the
** IMAP browser with the \fItoggle-subscribed\fP function.
*/
- {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, 300},
+ {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, "300" },
/*
** .pp
** This variable configures how often (in seconds) Mutt-ng should look for
** new mail in IMAP folders. This is split from the ``$mail_check'' variable
** to generate less traffic and get more accurate information for local folders.
*/
- {"imap_pass", DT_STR, R_NONE, UL &ImapPass, UL 0},
+ {"imap_pass", DT_STR, R_NONE, UL &ImapPass, "" },
/*
** .pp
** Availability: IMAP
** fairly secure machine, because the superuser can read your configuration even
** if you are the only one who can read the file.
*/
- {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, 1},
+ {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, "yes" },
/*
** .pp
** Availability: IMAP
** user/password pairs on Mutt-ng invocation, or if opening the connection
** is slow.
*/
- {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, 1},
+ {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, "yes" },
/*
** .pp
** Availability: IMAP
** but can make closing an IMAP folder somewhat slower. This option
** exists to appease speed freaks.
*/
- {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, M_ASKYES},
+ {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, "ask-yes" },
/*
** .pp
** Availability: IMAP
** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
** the connection is lost.
*/
- {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, 1},
+ {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, "yes" },
/*
** .pp
** Availability: IMAP
** server which are out of the users' hands, you may wish to suppress
** them at some point.
*/
- {"imap_user", DT_STR, R_NONE, UL &ImapUser, UL 0},
+ {"imap_user", DT_STR, R_NONE, UL &ImapUser, "" },
/*
** .pp
** Availability: IMAP
** This variable defaults to your user name on the local machine.
*/
#endif
- {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, 0},
+ {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
** use the viewer defined in that entry to convert the body part to text
** form.
*/
- {"include", DT_QUAD, R_NONE, OPT_INCLUDE, M_ASKYES},
+ {"include", DT_QUAD, R_NONE, OPT_INCLUDE, "ask-yes" },
/*
** .pp
** Controls whether or not a copy of the message(s) you are replying to
** is included in your reply.
*/
- {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, 0},
+ {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, "no" },
/*
** .pp
** Controls whether or not Mutt-ng includes only the first attachment
** of the message you are replying.
*/
- {"indent_string", DT_STR, R_NONE, UL &Prefix, UL "> "},
+ {"indent_string", DT_STR, R_NONE, UL &Prefix, "> "},
/*
** .pp
** Specifies the string to prepend to each line of text quoted in a
** message to which you are replying. You are strongly encouraged not to
** change this value, as it tends to agitate the more fanatical netizens.
*/
- {"index_format", DT_STR, R_BOTH, UL &HdrFmt, UL "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
+ {"index_format", DT_STR, R_BOTH, UL &HdrFmt, "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
/*
** .pp
** This variable allows you to customize the message index display to
*/
#ifdef USE_NNTP
{"inews", DT_SYN, R_NONE, UL "nntp_inews", 0},
- {"nntp_inews", DT_PATH, R_NONE, UL &Inews, UL ""},
+ {"nntp_inews", DT_PATH, R_NONE, UL &Inews, ""},
/*
** .pp
** Availability: NNTP
** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
*/
#endif
- {"ispell", DT_PATH, R_NONE, UL &Ispell, UL ISPELL},
+ {"ispell", DT_PATH, R_NONE, UL &Ispell, ISPELL},
/*
** .pp
** How to invoke ispell (GNU's spell-checking software).
*/
- {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, 0},
+ {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, "no" },
/*
** .pp
** If \fIset\fP, read messages marked as flagged will not be moved
** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
** a ``$mbox-hook'' command.
*/
- {"locale", DT_STR, R_BOTH, UL &Locale, UL "C"},
+ {"locale", DT_STR, R_BOTH, UL &Locale, "C"},
/*
** .pp
** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
** the strings your system accepts for the locale variable \fTLC_TIME\fP.
*/
- {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, M_NO},
+ {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, "no" },
/*
** .pp
** When \fIset\fP, address replies to the mailing list the original message came
** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
*/
- {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, 0},
+ {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, "0" },
/*
** .pp
** When set non-zero, this specifies the maximum number of recipient header
** weeding is turned on. In case the number of lines exeeds its value, the
** last line will have 3 dots appended.
*/
- {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, 0},
+ {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, "0" },
/*
** .pp
** When \fIset\fP, 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 $$wrapmargin.
*/
- {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, 5},
+ {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, "5" },
/*
** .pp
** This variable configures how often (in seconds) Mutt-ng should look for
** .pp
** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
*/
- {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, 0},
+ {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, "" },
/*
** .pp
** This variable specifies which files to consult when attempting to
** display MIME bodies not directly supported by Mutt-ng.
*/
- {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, 1},
+ {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, "yes" },
/*
** .pp
** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
*/
#ifdef USE_HCACHE
- {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0},
+ {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "" },
/*
** .pp
** Availability: Header Cache
** be a single global header cache. By default it is \fIunset\fP so no
** header caching will be used.
*/
- {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1},
+ {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, "yes" },
/*
** .pp
** Availability: Header Cache
** message every time the folder is opened.
*/
#if HAVE_GDBM || HAVE_DB4
- {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384"},
+ {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, "16384"},
/*
** .pp
** Availability: Header Cache
*/
#endif /* HAVE_GDBM || HAVE_DB 4 */
#if HAVE_QDBM
- { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 0 },
+ { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, "no" },
/*
** .pp
** If enabled the header cache will be compressed. So only one fifth of the usual
*/
#endif /* HAVE_QDBM */
#endif /* USE_HCACHE */
- {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0},
+ {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, "no" },
/*
** .pp
** If \fIset\fP, messages marked as deleted will be saved with the maildir
** .pp
** It is similiar to the trash option.
*/
- {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1},
+ {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, "yes" },
/*
** .pp
** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
** will show up with an "O" next to them in the ``index'' menu,
** indicating that they are old.
*/
- {"markers", DT_BOOL, R_PAGER, OPTMARKERS, 1},
+ {"markers", DT_BOOL, R_PAGER, OPTMARKERS, "yes" },
/*
** .pp
** Controls the display of wrapped lines in the internal pager. If set, a
** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
** the ``$$smart_wrap'' variable.
*/
- {"mask", DT_RX, R_NONE, UL &Mask, UL "!^\\.[^.]"},
+ {"mask", DT_RX, R_NONE, UL &Mask, "!^\\.[^.]"},
/*
** .pp
** A regular expression used in the file browser, optionally preceded by
** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
** will be shown. The match is always case-sensitive.
*/
- {"mbox", DT_PATH, R_BOTH, UL &Inbox, UL "~/mbox"},
+ {"mbox", DT_PATH, R_BOTH, UL &Inbox, "~/mbox"},
/*
** .pp
** This specifies the folder into which read mail in your ``$$spoolfile''
** folder will be appended.
*/
- {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, 0},
+ {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, "" },
/*
** .pp
** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
** .pp
** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
*/
- {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, UL "." },
+ {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, "." },
/*
** .pp
** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
** variable specifies the characters at which to split a folder name into
** ``hierarchy items.''
*/
- {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, UL "|"},
+ {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, "|"},
/*
** .pp
** This specifies the delimiter between the sidebar (if visible) and
** other screens.
*/
- {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, 0},
+ {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, "no" },
/*
** .pp
** This specifies whether or not to show the sidebar (a list of folders specified
** with the ``mailboxes'' command).
*/
- {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, 0},
+ {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, "0" },
/*
** .pp
** The width of the sidebar.
*/
- {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, 0},
+ {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, "no" },
/*
** .pp
** If \fIset\fP, only folders with new mail will be shown in the sidebar.
*/
- {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, UL "%m%?n?(%n)?%?f?[%f]?"},
+ {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, "%m%?n?(%n)?%?f?[%f]?"},
/*
** .pp
** This variable controls how message counts are printed when the sidebar
** 1) These expandos only have a non-zero value for the current mailbox and
** will always be zero otherwise.
*/
- {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, 0},
+ {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, "no" },
/*
** .pp
** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
** At which characters this compression is done is controled via the
** $$sidebar_boundary variable.
*/
- {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, M_MBOX},
+ {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, "mbox" },
/*
** .pp
** The default mailbox type used when creating new folders. May be any of
** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
*/
- {"metoo", DT_BOOL, R_NONE, OPTMETOO, 0},
+ {"metoo", DT_BOOL, R_NONE, OPTMETOO, "no" },
/*
** .pp
** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
** command) from the list of recipients when replying to a message.
*/
- {"menu_context", DT_NUM, R_NONE, UL &MenuContext, 0},
+ {"menu_context", DT_NUM, R_NONE, UL &MenuContext, "0" },
/*
** .pp
** This variable controls the number of lines of context that are given
** when scrolling through menus. (Similar to ``$$pager_context''.)
*/
- {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, 1},
+ {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, "yes" },
/*
** .pp
** When \fIunset\fP, the bottom entry of menus will never scroll up past
** the bottom of the screen, unless there are less entries than lines.
** When \fIset\fP, the bottom entry may move off the bottom.
*/
- {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, 0},
+ {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, "no" },
/*
** .pp
** When \fIset\fP, menus will be scrolled up or down one line when you
** is cleared and the next or previous page of the menu is displayed
** (useful for slow links to avoid many redraws).
*/
- {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0},
+ {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, "no" },
/*
** .pp
** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
** ``\fTx\fP''.
*/
- {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0},
+ {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" },
/*
** .pp
** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
** them. If the variable is set, the message files will simply be
** deleted.
*/
- {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, UL "flagged"},
+ {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, "flagged"},
/*
** .pp
** The name of the MH sequence used for flagged messages.
*/
- {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, UL "replied"},
+ {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, "replied"},
/*
** .pp
** The name of the MH sequence used to tag replied messages.
*/
- {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, UL "unseen"},
+ {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, "unseen"},
/*
** .pp
** The name of the MH sequence used for unseen messages.
*/
- {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, M_NO},
+ {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, "no" },
/*
** .pp
** When \fIset\fP, the message you are forwarding will be attached as a
** .pp
** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
*/
- {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, 0},
+ {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, "no" },
/*
** .pp
** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
** ``$$forward_decode'' is used instead.
*/
- {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, M_YES},
+ {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, "yes" },
/*
** .pp
** When forwarding multiple attachments of a MIME message from the recvattach
#ifdef USE_NNTP
{"mime_subject", DT_SYN, R_NONE, UL "nntp_mime_subject", 0},
- {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, 1},
+ {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, "yes" },
/*
** .pp
** Availability: NNTP
#endif
#ifdef MIXMASTER
- {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, UL "%4n %c %-16s %a"},
+ {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, "%4n %c %-16s %a"},
/*
** .pp
** Availability: Mixmaster
** .dt %a .dd The remailer's e-mail address.
** .de
*/
- {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, UL MIXMASTER},
+ {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, MIXMASTER},
/*
** .pp
** Availability: Mixmaster
** mixmaster chain.
*/
#endif
- {"move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO},
+ {"move", DT_QUAD, R_NONE, OPT_MOVE, "ask-no" },
/*
** .pp
** Controls whether or not Mutt-ng will move read messages
** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
** a ``$mbox-hook'' command.
*/
- {"message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s"},
+ {"message_format", DT_STR, R_NONE, UL &MsgFmt, "%s"},
/*
** .pp
** This is the string displayed in the ``attachment'' menu for
** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
*/
- {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, UL "%Y%m%d%h%M%s.G%P%p"},
+ {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, "%Y%m%d%h%M%s.G%P%p"},
/*
** .pp
** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
** \fBNote:\fP Please only change this setting if you know what you are doing.
** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
*/
- {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0},
+ {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, "no" },
/*
** .pp
** This variable, when \fIset\fP, makes the thread tree narrower, allowing
*/
#ifdef USE_NNTP
{"news_cache_dir", DT_SYN, R_NONE, UL "nntp_cache_dir", 0},
- {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.muttng"},
+ {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.muttng"},
/*
** .pp
** Availability: NNTP
** As for the header caching in connection with IMAP and/or Maildir,
** this drastically increases speed and lowers traffic.
*/
- {"news_server", DT_SYN, R_NONE, UL "nntp_host", 0},
- {"nntp_host", DT_STR, R_NONE, UL &NewsServer, 0},
+ {"news_server", DT_SYN, R_NONE, UL "nntp_host", 0 },
+ {"nntp_host", DT_STR, R_NONE, UL &NewsServer, "" },
/*
** .pp
** Availability: NNTP
** regardless of the file's permissions.
*/
{"newsrc", DT_SYN, R_NONE, UL "nntp_newsrc", 0},
- {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, UL "~/.newsrc"},
+ {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, "~/.newsrc"},
/*
** .pp
** Availability: NNTP
** %s newsserver name
** .te
*/
- {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, 1000},
+ {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, "1000" },
/*
** .pp
** Availability: NNTP
** If there're more articles than defined with $$nntp_context, all older ones
** will be removed/not shown in the index.
*/
- {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, 1},
+ {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, "yes" },
/*
** .pp
** Availability: NNTP
** This variable controls whether or not descriptions for newsgroups
** are to be loaded when subscribing to a newsgroup.
*/
- {"nntp_user", DT_STR, R_NONE, UL &NntpUser, UL ""},
+ {"nntp_user", DT_STR, R_NONE, UL &NntpUser, ""},
/*
** .pp
** Availability: NNTP
** Your login name on the NNTP server. If \fIunset\fP and the server requires
** authentification, Mutt-ng will prompt you for your account name.
*/
- {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL ""},
+ {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, ""},
/*
** .pp
** Availability: NNTP
** regardless of the file's permissions.
*/
{"nntp_poll", DT_SYN, R_NONE, UL "nntp_mail_check", 0},
- {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, 60},
+ {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, "60" },
/*
** .pp
** Availability: NNTP
** 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.).
*/
- {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES},
+ {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, "ask-yes" },
/*
** .pp
** Availability: NNTP
** was connection lost.
*/
#endif
- {"pager", DT_PATH, R_NONE, UL &Pager, UL "builtin"},
+ {"pager", DT_PATH, R_NONE, UL &Pager, "builtin"},
/*
** .pp
** This variable specifies which pager you would like to use to view
** directly from the pager, and screen resizes cause lines longer than
** the screen width to be badly formatted in the help menu.
*/
- {"pager_context", DT_NUM, R_NONE, UL &PagerContext, 0},
+ {"pager_context", DT_NUM, R_NONE, UL &PagerContext, "0" },
/*
** .pp
** This variable controls the number of lines of context that are given
** default, Mutt-ng will display the line after the last one on the screen
** at the top of the next page (0 lines of context).
*/
- {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s"},
+ {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, "-%Z- %C/%m: %-20.20n %s"},
/*
** .pp
** This variable controls the format of the one-line message ``status''
** pager. The valid sequences are listed in the ``$$index_format''
** section.
*/
- {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, 0},
+ {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, "0" },
/*
** .pp
** Determines the number of lines of a mini-index which is shown when in
** is less than \fIpager_index_lines\fP, then the index will only use as
** many lines as it needs.
*/
- {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, 0},
+ {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, "no" },
/*
** .pp
** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
** when you are at the end of a message and invoke the \fInext-page\fP
** function.
*/
- {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0},
+ {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, "no" },
/*
** .pp
** Setting this variable will cause Mutt-ng to always attempt to
** be overridden by use of the \fIsmime-menu\fP.
** (Crypto only)
*/
- {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0},
+ {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, "no" },
/*
** .pp
** Setting this variable will cause Mutt-ng to always attempt to PGP
** settings can be overridden by use of the \fIsmime-menu\fP.
** (Crypto only)
*/
- {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
+ {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, "yes" },
/*
** .pp
** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
** if you want to play interesting key selection games.
** (PGP only)
*/
- {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1},
+ {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, "yes" },
/*
** .pp
** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
** encrypted.
** (Crypto only)
*/
- {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0},
+ {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, "no" },
/*
** .pp
** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
** (Crypto only)
*/
- {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0},
+ {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, "no" },
/*
** .pp
** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
** to find out whether an encrypted message is also signed.
** (Crypto only)
*/
- {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1},
+ {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, "yes" },
/*
** .pp
** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
** you may \fIunset\fP this setting.
** (Crypto only)
*/
- {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
+ {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
** (PGP only)
*/
- {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES},
+ {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, "yes" },
/*
** .pp
** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
** (Crypto only)
*/
- {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
+ {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, "no" },
/*
** .pp
** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
** (S/MIME only)
*/
- {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1},
+ {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, "yes" },
/*
** .pp
** This flag controls whether you want to be asked to enter a label
** \fIset\fP by default.
** (S/MIME only)
*/
- {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1},
+ {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, "yes" },
/*
** .pp
** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
** to determine the key to use. It will ask you to supply a key, if it can't find one.
** (S/MIME only)
*/
- {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u"},
+ {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, "%4n %t%f %4l/0x%k %-4a %2c %u"},
/*
** .pp
** This variable allows you to customize the PGP key selection menu to
** .pp
** (PGP only)
*/
- {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0},
+ {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, "" },
/*
** .pp
** If you assign a text to this variable, then a PGP signature is only
** even for bad signatures.
** (PGP only)
*/
- {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1},
+ {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, "yes" },
/*
** .pp
** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
** subprocess failed.
** (PGP only)
*/
- {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0},
+ {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, "no" },
/*
** .pp
** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
** (PGP only)
*/
- {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0},
+ {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, "no" },
/*
** .pp
** If \fIset\fP, signed and encrypted messages will consist of nested
** removed, while the inner multipart/signed part is retained.
** (PGP only)
*/
- {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0},
+ {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, "no" },
/*
** .pp
** This option controls whether Mutt-ng generates old-style inline
** \fBdeprecated\fP.
** (PGP only)
*/
- {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, 0},
+ {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" },
/*
** .pp
** Setting this variable will cause Mutt-ng to always attempt to
** (PGP only)
**
*/
- {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1},
+ {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, "yes" },
/*
** .pp
** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
** have been marked as ``disabled'' by the user.
** (PGP only)
*/
- {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, 0},
+ {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, "" },
/*
** .pp
** If you have more than one key pair, this option allows you to specify
** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
** (PGP only)
*/
- {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1},
+ {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, "yes" },
/*
** .pp
** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
** this if you know what you are doing.
** (PGP only)
*/
- {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300},
+ {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, "300" },
/*
** .pp
** The number of seconds after which a cached passphrase will expire if
** not used. Default: 300.
** (PGP only)
*/
- {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS},
+ {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, "address" },
/*
** .pp
** Specifies how the entries in the ``pgp keys'' menu are sorted. The
** ``reverse-''.
** (PGP only)
*/
- {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES},
+ {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, "ask-yes" },
/*
** .pp
** This option controls whether Mutt-ng will prompt you for
** \fBdeprecated\fP.
** (PGP only)
*/
- {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0},
+ {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
/* XXX Default values! */
- {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0},
+ {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, "" },
/*
** .pp
** This format strings specifies a command which is used to decode
** alongside the documentation.
** (PGP only)
*/
- {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0},
+ {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, "" },
/*
** .pp
** This command is invoked whenever Mutt-ng will need public key information.
** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
** (PGP only)
*/
- {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0},
+ {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, "" },
/*
** .pp
** This command is used to verify PGP signatures.
** (PGP only)
*/
- {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0},
+ {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, "" },
/*
** .pp
** This command is used to decrypt a PGP encrypted message.
** (PGP only)
*/
- {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0},
+ {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, "" },
/*
** .pp
** This format is used to create a old-style ``clearsigned'' PGP message.
** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
** (PGP only)
*/
- {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0},
+ {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, "" },
/*
** .pp
** This command is used to create the detached PGP signature for a
** multipart/signed PGP/MIME body part.
** (PGP only)
*/
- {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0},
+ {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, "" },
/*
** .pp
** This command is used to both sign and encrypt a body part.
** (PGP only)
*/
- {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0},
+ {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, "" },
/*
** .pp
** This command is used to encrypt a body part without signing it.
** (PGP only)
*/
- {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0},
+ {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, "" },
/*
** .pp
** This command is used to import a key from a message into
** the user's public key ring.
** (PGP only)
*/
- {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0},
+ {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, "" },
/*
** .pp
** This command is used to export a public key from the user's
** key ring.
** (PGP only)
*/
- {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0},
+ {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, "" },
/*
** .pp
** This command is used to verify key information from the key selection
** menu.
** (PGP only)
*/
- {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0},
+ {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, "" },
/*
** .pp
** This command is used to list the secret key ring's contents. The
** with Mutt-ng.
** (PGP only)
*/
- {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0},
+ {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, "" },
/*
** .pp
** This command is used to list the public key ring's contents. The
** with Mutt-ng.
** (PGP only)
*/
- {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1},
+ {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, "yes" },
/*
** .pp
** Controls the handling of encrypted messages when forwarding a message.
** ``$$mime_forward_decode'' is \fIunset\fP.
** (PGP only)
*/
- {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300},
+ {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, "300" },
/*
** .pp
** The number of seconds after which a cached passphrase will expire if
** not used.
** (S/MIME only)
*/
- {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0},
+ {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, "" },
/*
** .pp
** This sets the algorithm that should be used for encryption.
** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
** (S/MIME only)
*/
- {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0},
+ {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, "" },
/*
** .pp
** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
** edited. This one points to the location of the private keys.
** (S/MIME only)
*/
- {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0},
+ {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, "" },
/*
** .pp
** This variable contains the name of either a directory, or a file which
** contains trusted certificates for use with OpenSSL.
** (S/MIME only)
*/
- {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0},
+ {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, "" },
/*
** .pp
** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
** the location of the certificates.
** (S/MIME only)
*/
- {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0},
+ {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, "" },
/*
** .pp
** This format string specifies a command which is used to decrypt
** alongside the documentation.
** (S/MIME only)
*/
- {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0},
+ {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, "" },
/*
** .pp
** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
** (S/MIME only)
*/
- {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0},
+ {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, "" },
/*
** .pp
** This command is used to verify S/MIME signatures of type
** \fTapplication/x-pkcs7-mime\fP.
** (S/MIME only)
*/
- {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0},
+ {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, "" },
/*
** .pp
** This command is used to created S/MIME signatures of type
** \fTmultipart/signed\fP, which can be read by all mail clients.
** (S/MIME only)
*/
- {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0},
+ {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, "" },
/*
** .pp
** This command is used to created S/MIME signatures of type
** clients supporting the S/MIME extension.
** (S/MIME only)
*/
- {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0},
+ {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, "" },
/*
** .pp
** This command is used to create encrypted S/MIME messages.
** (S/MIME only)
*/
- {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0},
+ {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, "" },
/*
** .pp
** This command is used to extract PKCS7 structures of S/MIME signatures,
** in order to extract the public X509 certificate(s).
** (S/MIME only)
*/
- {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0},
+ {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, "" },
/*
** .pp
** This command is used to extract X509 certificates from a PKCS7 structure.
** (S/MIME only)
*/
- {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0},
+ {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, "" },
/*
** .pp
** This command is used to extract only the signers X509 certificate from a S/MIME
** email's ``\fTFrom:\fP'' header field.
** (S/MIME only)
*/
- {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0},
+ {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, "" },
/*
** .pp
** This command is used to import a certificate via \fTsmime_keysng\fP.
** (S/MIME only)
*/
- {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0},
+ {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, "" },
/*
** .pp
** This command is used to extract the mail address(es) used for storing
** certificate was issued for the sender's mailbox).
** (S/MIME only)
*/
- {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0},
+ {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, "" },
/*
** .pp
** This is the default key-pair to use for signing. This must be set to the
*/
#if defined(USE_LIBESMTP)
{"smtp_auth_username", DT_SYN, R_NONE, UL "smtp_user", 0},
- {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, 0},
+ {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, "" },
/*
** .pp
** Availability: SMTP
** cause Mutt-ng to attempt to use SMTP AUTH when sending.
*/
{"smtp_auth_password", DT_SYN, R_NONE, UL "smtp_pass", 0},
- {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, 0},
+ {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, "" },
/*
** .pp
** Availability: SMTP
** presents a security risk since the superuser of your machine may read it
** regardless of the file's permissions.
*/
- {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, 0},
+ {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, "" },
/*
** .pp
** Availability: SMTP
** as the envelope sender but only a particular one which may not be the same as the
** user's desired \fTFrom:\fP header.
*/
- {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, 0},
+ {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, "" },
/*
** .pp
** Availability: SMTP
** to invoking the sendmail binary. Setting this variable overrides the
** value of ``$$sendmail'', and any associated variables.
*/
- {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, 25},
+ {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, "25" },
/*
** .pp
** Availability: SMTP
** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
** servers will probably desire 587, the mail submission port.
*/
- {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, 0},
+ {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, "" },
/*
** .pp
** Availability: SMTP (and SSL)
#endif
#if defined(USE_SSL) || defined(USE_GNUTLS)
#ifdef USE_SSL
- {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0},
+ {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, "" },
/*
** .pp
** Availability: SSL
** key.
*/
#endif /* USE_SSL */
- {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, 0 },
+ {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, "no" },
/*
** .pp
** If this variable is \fIset\fP, mutt-ng will require that all connections
** since it would otherwise have to abort the connection anyway. This
** option supersedes ``$$ssl_starttls''.
*/
- {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES},
+ {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, "yes" },
/*
** .pp
** Availability: SSL or GNUTLS
** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
** use STARTTLS regardless of the server's capabilities.
*/
- {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates"},
+ {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, "~/.mutt_certificates"},
/*
** .pp
** Availability: SSL or GNUTLS
** Example: \fTset certificate_file=~/.muttng/certificates\fP
*/
# if defined(_MAKEDOC) || !defined (USE_GNUTLS)
- {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1},
+ {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, "yes" },
/*
** .pp
** Availability: SSL
** system-wide certificate store when checking if server certificate
** is signed by a trusted CA.
*/
- {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0},
+ {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, "" },
/*
** .pp
** Availability: SSL
** The file which includes random data that is used to initialize SSL
** library functions.
*/
- {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1},
+ {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, "yes" },
/*
** .pp
** Availability: SSL
** SSL authentication process.
*/
# endif /* _MAKEDOC || !USE_GNUTLS */
- {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1},
+ {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, "yes" },
/*
** .pp
** Availability: SSL or GNUTLS
** This variables specifies whether to attempt to use SSLv3 in the
** SSL authentication process.
*/
- {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1},
+ {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, "yes" },
/*
** .pp
** Availability: SSL or GNUTLS
** SSL authentication process.
*/
# ifdef USE_GNUTLS
- {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0},
+ {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, "0" },
/*
** .pp
** Availability: GNUTLS
** for use in any Diffie-Hellman key exchange. A value of 0 will use
** the default from the GNUTLS library.
*/
- {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0},
+ {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, "" },
/*
** .pp
** This variable specifies a file containing trusted CA certificates.
*/
# endif /* USE_GNUTLS */
# endif /* USE_SSL || USE_GNUTLS */
- {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0},
+ {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, "no" },
/*
** .pp
** Used in connection with the \fIpipe-message\fP command and the ``tag-
** In both cases the messages are piped in the current sorted order,
** and the ``$$pipe_sep'' separator is added after each message.
*/
- {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0},
+ {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, "no" },
/*
** .pp
** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
** will weed headers and will attempt to PGP/MIME decode the messages
** first.
*/
- {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, UL "\n"},
+ {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, "\n"},
/*
** .pp
** The separator to add between messages when piping a list of tagged
** messages to an external Unix command.
*/
#ifdef USE_POP
- {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0},
+ {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, "" },
/*
** .pp
** Availability: POP
** .pp
** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
*/
- {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1},
+ {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, "yes" },
/*
** .pp
** Availability: POP
** fails, Mutt-ng will not connect to the POP server.
*/
{"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
- {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, 60},
+ {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, "60" },
/*
** .pp
** Availability: POP
** This variable configures how often (in seconds) POP should look for
** new mail.
*/
- {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, M_ASKNO},
+ {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, "ask-no" },
/*
** .pp
** Availability: POP
** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
** download messages but also leave them on the POP server.
*/
- {"pop_host", DT_STR, R_NONE, UL &PopHost, UL ""},
+ {"pop_host", DT_STR, R_NONE, UL &PopHost, ""},
/*
** .pp
** Availability: POP
** presents a security risk since the superuser of your machine may read it
** regardless of the file's permissions.
*/
- {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0},
+ {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, "no" },
/*
** .pp
** Availability: POP
** for retrieving only unread messages from the POP server when using
** the ``fetch-mail'' function.
*/
- {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES},
+ {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, "ask-yes" },
/*
** .pp
** Availability: POP
** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
** connection is lost.
*/
- {"pop_user", DT_STR, R_NONE, UL &PopUser, 0},
+ {"pop_user", DT_STR, R_NONE, UL &PopUser, "" },
/*
** .pp
** Availability: POP
** .pp
** This variable defaults to your user name on the local machine.
*/
- {"pop_pass", DT_STR, R_NONE, UL &PopPass, UL ""},
+ {"pop_pass", DT_STR, R_NONE, UL &PopPass, ""},
/*
** .pp
** Availability: POP
** regardless of the file's permissions.
*/
#endif /* USE_POP */
- {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, UL ""},
+ {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, ""},
/*
** .pp
** Similar to the ``$$attribution'' variable, Mutt-ng will append this
*/
#ifdef USE_NNTP
{"post_moderated", DT_SYN, R_NONE, UL "nntp_post_moderated", 0 },
- {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES},
+ {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, "ask-yes" },
/*
** .pp
** Availability: NNTP
** posting will not have any effect.
*/
#endif
- {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES},
+ {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, "ask-yes" },
/*
** .pp
** Controls whether or not messages are saved in the ``$$postponed''
** mailbox when you elect not to send immediately.
*/
- {"postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed"},
+ {"postponed", DT_PATH, R_NONE, UL &Postponed, "~/postponed"},
/*
** .pp
** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
** variable.
*/
#ifdef USE_SOCKET
- {"preconnect", DT_STR, R_NONE, UL &Preconnect, UL 0},
+ {"preconnect", DT_STR, R_NONE, UL &Preconnect, "" },
/*
** .pp
** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
** remote machine without having to enter a password.
*/
#endif /* USE_SOCKET */
- {"print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO},
+ {"print", DT_QUAD, R_NONE, OPT_PRINT, "ask-no" },
/*
** .pp
** Controls whether or not Mutt-ng really prints messages.
** This is set to \fIask-no\fP by default, because some people
** accidentally hit ``p'' often.
*/
- {"print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr"},
+ {"print_command", DT_PATH, R_NONE, UL &PrintCmd, "lpr"},
/*
** .pp
** This specifies the command pipe that should be used to print messages.
*/
- {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1},
+ {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, "yes" },
/*
** .pp
** Used in connection with the print-message command. If this
** some advanced printer filter which is able to properly format
** e-mail messages for printing.
*/
- {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, 0},
+ {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, "no" },
/*
** .pp
** Used in connection with the print-message command. If this option
** Those who use the \fTenscript(1)\fP program's mail-printing mode will
** most likely want to set this option.
*/
- {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, 1},
+ {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, "yes" },
/*
** .pp
** If you use an \fIexternal\fP ``$$pager'', setting this variable will
** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
** index menu when the external pager exits.
*/
- {"query_command", DT_PATH, R_NONE, UL &QueryCmd, UL ""},
+ {"query_command", DT_PATH, R_NONE, UL &QueryCmd, ""},
/*
** .pp
** This specifies the command that Mutt-ng will use to make external address
** with the query string the user types. See ``$query'' for more
** information.
*/
- {"quit", DT_QUAD, R_NONE, OPT_QUIT, M_YES},
+ {"quit", DT_QUAD, R_NONE, OPT_QUIT, "yes" },
/*
** .pp
** This variable controls whether ``quit'' and ``exit'' actually quit
** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
** prompted for confirmation when you try to quit.
*/
- {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, 1},
+ {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, "yes" },
/*
** .pp
** Controls whether or not empty lines will be quoted using
** ``$indent_string''.
*/
- {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, 0},
+ {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, "no" },
/*
** .pp
** Controls how quoted lines will be quoted. If \fIset\fP, one quote
** character will be added to the end of existing prefix. Otherwise,
** quoted lines will be prepended by ``$indent_string''.
*/
- {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, UL "^([ \t]*[|>:}#])+"},
+ {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, "^([ \t]*[|>:}#])+"},
/*
** .pp
** A regular expression used in the internal-pager to determine quoted
** matches \fIexactly\fP the quote characters at the beginning of quoted
** lines.
*/
- {"read_inc", DT_NUM, R_NONE, UL &ReadInc, 10},
+ {"read_inc", DT_NUM, R_NONE, UL &ReadInc, "10" },
/*
** .pp
** If set to a value greater than 0, Mutt-ng will display which message it
** .pp
** Also see the ``$$write_inc'' variable.
*/
- {"read_only", DT_BOOL, R_NONE, OPTREADONLY, 0},
+ {"read_only", DT_BOOL, R_NONE, OPTREADONLY, "no" },
/*
** .pp
** If set, all folders are opened in read-only mode.
*/
- {"realname", DT_STR, R_BOTH, UL &Realname, 0},
+ {"realname", DT_STR, R_BOTH, UL &Realname, "" },
/*
** .pp
** This variable specifies what ``real'' or ``personal'' name should be used
** variable will \fInot\fP be used when the user has set a real name
** in the $$from variable.
*/
- {"recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES},
+ {"recall", DT_QUAD, R_NONE, OPT_RECALL, "ask-yes" },
/*
** .pp
** Controls whether or not Mutt-ng recalls postponed messages
** Setting this variable to \fIyes\fP is not generally useful, and thus not
** recommended.
*/
- {"record", DT_PATH, R_NONE, UL &Outbox, UL ""},
+ {"record", DT_PATH, R_NONE, UL &Outbox, ""},
/*
** .pp
** This specifies the file into which your outgoing messages should be
** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
** ``$$save_name'' variables, and the ``$fcc-hook'' command.
*/
- {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, UL "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
+ {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
/*
** .pp
** A regular expression used to recognize reply messages when threading
** and replying. The default value corresponds to the English ``Re:'' and
** the German ``Aw:''.
*/
- {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, 0},
+ {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, "no" },
/*
** .pp
** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
** assume that you want to reply to the recipients of that message rather
** than to yourself.
*/
- {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES},
+ {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, "ask-yes" },
/*
** .pp
** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
** header field to the list address and you want to send a private
** message to the author of a message.
*/
- {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, 1},
+ {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, "yes" },
/*
** .pp
** When set, the cursor will be automatically advanced to the next
** (possibly undeleted) message whenever a command that modifies the
** current message is executed.
*/
- {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, 0},
+ {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, "no" },
/*
** .pp
** This variable controls whether or not Mutt-ng will display the ``personal''
** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
** address is not human friendly (like CompuServe addresses).
*/
- {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, 0},
+ {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, "no" },
/*
** .pp
** It may sometimes arrive that you receive mail to a certain machine,
** used doesn't match your alternates, the \fTFrom:\fP line will use
** your address on the current machine.
*/
- {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, 1},
+ {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, "yes" },
/*
** .pp
** This variable fine-tunes the behaviour of the $reverse_name feature.
** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
** override any such real names with the setting of the $realname variable.
*/
- {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, 0},
+ {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "no" },
/*
** .pp
** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
** unconditionally use the encoding specified in RFC 2231.
*/
- {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, 0},
+ {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" },
/*
** .pp
** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
** is \fIset\fP too, the selection of the fcc folder will be changed as well.
*/
- {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, 1},
+ {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, "yes" },
/*
** .pp
** When \fIunset\fP, mailboxes which contain no saved messages will be removed
** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
** delete MH and Maildir directories.
*/
- {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, 0},
+ {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, "no" },
/*
** .pp
** This variable controls how copies of outgoing messages are saved.
** .pp
** Also see the ``$$force_name'' variable.
*/
- {"score", DT_BOOL, R_NONE, OPTSCORE, 1},
+ {"score", DT_BOOL, R_NONE, OPTSCORE, "yes" },
/*
** .pp
** When this variable is \fIunset\fP, scoring is turned off. This can
** ``$$score_threshold_delete'' variable and friends are used.
**
*/
- {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, UL -1},
+ {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, "-1" },
/*
** .pp
** Messages which have been assigned a score equal to or lower than the value
** Mutt-ng scores are always greater than or equal to zero, the default setting
** of this variable will never mark a message for deletion.
*/
- {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, 9999},
+ {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, "9999" },
/*
** .pp
** Messages which have been assigned a score greater than or equal to this
** variable's value are automatically marked ``flagged''.
*/
- {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, UL -1},
+ {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, "-1" },
/*
** .pp
** Messages which have been assigned a score equal to or lower than the value
** Mutt-ng scores are always greater than or equal to zero, the default setting
** of this variable will never mark a message read.
*/
- {"send_charset", DT_STR, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8"},
+ {"send_charset", DT_STR, R_NONE, UL &SendCharset, "us-ascii:iso-8859-1:utf-8"},
/*
** .pp
** A list of character sets for outgoing messages. Mutt-ng will use the
** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
** instead of or after \fTiso-8859-1\fP.
*/
- {"sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi"},
+ {"sendmail", DT_PATH, R_NONE, UL &Sendmail, SENDMAIL " -oem -oi"},
/*
** .pp
** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
** Mutt-ng expects that the specified program interprets additional
** arguments as recipient addresses.
*/
- {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0},
+ {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, "0" },
/*
** .pp
** Specifies the number of seconds to wait for the ``$$sendmail'' process
** process will be put in a temporary file. If there is some error, you
** will be informed as to where to find the output.
*/
- {"shell", DT_PATH, R_NONE, UL &Shell, 0},
+ {"shell", DT_PATH, R_NONE, UL &Shell, "" },
/*
** .pp
** Command to use when spawning a subshell. By default, the user's login
*/
#ifdef USE_NNTP
{"save_unsubscribed", DT_SYN, R_NONE, UL "nntp_save_unsubscribed", 0 },
- {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, 0},
+ {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, "no" },
/*
** .pp
** Availability: NNTP
#endif
#ifdef USE_NNTP
{"show_new_news", DT_SYN, R_NONE, UL "nntp_show_new_news", 0 },
- {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, 1},
+ {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, "yes" },
/*
** .pp
** Availability: NNTP
** newsgroups will be checked.
*/
{"show_only_unread", DT_SYN, R_NONE, UL "nntp_show_only_unread", 0 },
- {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, 0},
+ {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, "no" },
/*
** .pp
** Availability: NNTP
** will be displayed in the newsgroup browser.
*/
#endif
- {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1},
+ {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, "yes" },
/*
** .pp
** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
** For example, Mutt-ng has the ability to highlight
** the signature in a different color in the builtin pager.
*/
- {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0},
+ {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, "no" },
/*
** .pp
** If \fIset\fP, the signature will be included before any quoted or forwarded
** unless you really know what you are doing, and are prepared to take
** some heat from netiquette guardians.
*/
- {"signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature"},
+ {"signature", DT_PATH, R_NONE, UL &Signature, "~/.signature"},
/*
** .pp
** Specifies the filename of your signature, which is appended to all
** assumed that filename is a shell command and input should be read from
** its stdout.
*/
- {"signoff_string", DT_STR, R_NONE, UL &SignOffString, UL 0},
+ {"signoff_string", DT_STR, R_NONE, UL &SignOffString, "" },
/*
** .pp
** If \fIset\fP, this string will be inserted before the signature. This is useful
** witty quotes into your mails, better use a signature file instead of
** the signoff string.
*/
- {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s"},
+ {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, "~f %s | ~s %s"},
/*
** .pp
** Specifies how Mutt-ng should expand a simple search into a real search
** .pp
** \fT~f joe | ~s joe\fP
*/
- {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1},
+ {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, "yes" },
/*
** .pp
** Controls the display of lines longer than the screen width in the
** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
** ``$$markers'' variable.
*/
- {"smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])"},
+ {"smileys", DT_RX, R_PAGER, UL &Smileys, "(>From )|(:[-^]?[][)(><}{|/DP])"},
/*
** .pp
** The \fIpager\fP uses this variable to catch some common false
** positives of ``$$quote_regexp'', most notably smileys in the beginning
** of a line
*/
- {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1},
+ {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, "1" },
/*
** .pp
** Specifies time, in seconds, to pause while displaying certain informational
** messages from the current folder. The default is to pause one second, so
** a value of zero for this option suppresses the pause.
*/
- {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, SORT_DATE},
+ {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, "date" },
/*
** .pp
** Specifies how to sort messages in the \fIindex\fP menu. Valid values
** You may optionally use the ``reverse-'' prefix to specify reverse sorting
** order (example: \fTset sort=reverse-date-sent\fP).
*/
- {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, SORT_ALIAS},
+ {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, "alias" },
/*
** .pp
** Specifies how the entries in the ``alias'' menu are sorted. The
** . unsorted (leave in order specified in .muttrc)
** .te
*/
- {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE},
+ {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, "date" },
/*
** .pp
** When sorting by threads, this variable controls how threads are sorted
** (which is not the right thing to do, but kept to not break any existing
** configuration setting).
*/
- {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, SORT_ALPHA},
+ {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, "alpha" },
/*
** .pp
** Specifies how to sort entries in the file browser. By default, the
** You may optionally use the ``reverse-'' prefix to specify reverse sorting
** order (example: \fTset sort_browser=reverse-date\fP).
*/
- {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, 1},
+ {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, "yes" },
/*
** .pp
** This variable is only useful when sorting by threads with
** Mutt-ng will attach the message whether or not this is the case,
** as long as the non-``$$reply_regexp'' parts of both messages are identical.
*/
- {"spam_separator", DT_STR, R_NONE, UL &SpamSep, UL ","},
+ {"spam_separator", DT_STR, R_NONE, UL &SpamSep, ","},
/*
** .pp
** ``$spam_separator'' controls what happens when multiple spam headers
** match will append to the previous, using ``$spam_separator'' as a
** separator.
*/
- {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, 0},
+ {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, "" },
/*
** .pp
** If your spool mailbox is in a non-default place where Mutt-ng cannot find
** automatically set this variable to the value of the environment
** variable $$$MAIL if it is not set.
*/
- {"status_chars", DT_STR, R_BOTH, UL &StChars, UL "-*%A"},
+ {"status_chars", DT_STR, R_BOTH, UL &StChars, "-*%A"},
/*
** .pp
** Controls the characters used by the ``\fT%r\fP'' indicator in
** opened in attach-message mode (Certain operations like composing
** a new mail, replying, forwarding, etc. are not permitted in this mode).
*/
- {"status_format", DT_STR, R_BOTH, UL &Status, UL "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"},
+ {"status_format", DT_STR, R_BOTH, UL &Status, "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"},
/*
** .pp
** Controls the format of the status line displayed in the \fIindex\fP
** will replace any dots in the expansion by underscores. This might be helpful
** with IMAP folders that don't like dots in folder names.
*/
- {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, 0},
+ {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, "no" },
/*
** .pp
** Setting this variable causes the ``status bar'' to be displayed on
** the first line of the screen rather than near the bottom.
*/
- {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, 1},
+ {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, "yes" },
/*
**
** .pp
** ``X-Mailto-'' and the message including headers will be shown in the editor
** regardless of what ``$$edit_headers'' is set to.
**/
- {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, 1},
+ {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "yes" },
/*
** .pp
** When \fIunset\fP, non MIME-compliant messages that doesn't have any
** and *text to a single space to prevent the display of MIME-encoded
** ``\fTSubject:\fP'' header field from being devided into multiple lines.
*/
- {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, 0},
+ {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, "no" },
/*
** .pp
** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
** personal mailbox where you might have several unrelated messages with
** the subject ``hi'' which will get grouped together.
*/
- {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, 0},
+ {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, "no" },
/**
** .pp
** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
** line which matches $$strip_was_regex when replying. This is useful to
** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
**/
- {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, UL "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
+ {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
/**
** .pp
** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
** trailing part of the ``Subject'' line when replying if it won't be empty
** afterwards.
**/
- {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, 0},
+ {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, "no" },
/*
** .pp
** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
** i.e. a space will be inserted between the quote characters and the actual
** text.
*/
- {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, 1},
+ {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, "yes" },
/*
** .pp
** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
*/
- {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, 0},
+ {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
** .pp
** Note that $$indent_string is ignored when this option is set.
*/
- {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0},
+ {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, "no" },
/*
** .pp
** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
** to thread messages by subject.
*/
- {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, 0},
+ {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, "no" },
/*
** .pp
** Affects the \fT~b\fP and \fT~h\fP search operations described in
** messages to be searched are decoded before searching. If \fIunset\fP,
** messages are searched as they appear in the folder.
*/
- {"tilde", DT_BOOL, R_PAGER, OPTTILDE, 0},
+ {"tilde", DT_BOOL, R_PAGER, OPTTILDE, "no" },
/*
** .pp
** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
** screen with a tilde (~).
*/
- {"timeout", DT_NUM, R_NONE, UL &Timeout, 600},
+ {"timeout", DT_NUM, R_NONE, UL &Timeout, "600" },
/*
** .pp
** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
** checking for new mail. A value of zero or less will cause Mutt-ng
** to never time out.
*/
- {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, 0},
+ {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, "" },
/*
** .pp
** This variable allows you to specify where Mutt-ng will place its
** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
*/
- {"to_chars", DT_STR, R_BOTH, UL &Tochars, UL " +TCFL"},
+ {"to_chars", DT_STR, R_BOTH, UL &Tochars, " +TCFL"},
/*
** .pp
** Controls the character used to indicate mail addressed to you. The
** by \fIyou\fP. The sixth character is used to indicate when a mail
** was sent to a mailing-list you're subscribe to (default: L).
*/
- {"trash", DT_PATH, R_NONE, UL &TrashPath, 0},
+ {"trash", DT_PATH, R_NONE, UL &TrashPath, "" },
/*
** .pp
** If \fIset\fP, this variable specifies the path of the trash folder where the
** deleted, so that there is no way to recover mail.
*/
#ifdef USE_SOCKET
- {"tunnel", DT_STR, R_NONE, UL &Tunnel, UL 0},
+ {"tunnel", DT_STR, R_NONE, UL &Tunnel, "" },
/*
** .pp
** Setting this variable will cause Mutt-ng to open a pipe to a command
** machine without having to enter a password.
*/
#endif
- {"umask", DT_NUM, R_NONE, UL &Umask, 0077},
+ {"umask", DT_NUM, R_NONE, UL &Umask, "0077" },
/*
** .pp
** This sets the umask that will be used by Mutt-ng when creating all
** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
*/
- {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, 0},
+ {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, "no" },
/*
** .pp
** \fBWarning:\fP do not set this variable unless you are using a version
** flag when sending 8-bit messages to enable ESMTP negotiation or tell
** libESMTP to do so.
*/
- {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, 1},
+ {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
** addresses will be qualified.
*/
- {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, 1},
+ {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
** command.
*/
#ifdef HAVE_LIBIDN
- {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, 1},
+ {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, "yes" },
/*
** .pp
** Availability: IDN
*/
#endif /* HAVE_LIBIDN */
#ifdef HAVE_GETADDRINFO
- {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, 1},
+ {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
** Normally, the default should work.
*/
#endif /* HAVE_GETADDRINFO */
- {"user_agent", DT_BOOL, R_NONE, OPTXMAILER, 1},
+ {"user_agent", DT_SYN, R_NONE, UL "agent_string", 0 },
+ {"agent_string", DT_BOOL, R_NONE, OPTXMAILER, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
** messages, indicating which version of Mutt-ng was used for composing
** them.
*/
- {"visual", DT_PATH, R_NONE, UL &Visual, 0},
+ {"visual", DT_PATH, R_NONE, UL &Visual, "" },
/*
** .pp
** Specifies the visual editor to invoke when the \fI~v\fP command is
** given in the builtin editor.
*/
- {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, 1},
+ {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, "yes" },
/*
** .pp
** Controls whether Mutt-ng will ask you to press a key after \fIshell-
** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
** for a key only if the external command returned a non-zero status.
*/
- {"weed", DT_BOOL, R_NONE, OPTWEED, 1},
+ {"weed", DT_BOOL, R_NONE, OPTWEED, "yes" },
/*
** .pp
** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
** printing, or replying to messages.
*/
- {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, 1},
+ {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, "yes" },
/*
** .pp
** Controls whether searches wrap around the end of the mailbox.
** When \fIset\fP, searches will wrap around the first (or last) message. When
** \fIunset\fP, searches will not wrap.
*/
- {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, 0},
+ {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, "0" },
/*
** .pp
** Controls the size of the margin remaining at the right side of
** the terminal when Mutt-ng's pager does smart wrapping.
*/
- {"write_inc", DT_NUM, R_NONE, UL &WriteInc, 10},
+ {"write_inc", DT_NUM, R_NONE, UL &WriteInc, "10" },
/*
** .pp
** When writing a mailbox, a message will be printed every
** .pp
** Also see the ``$$read_inc'' variable.
*/
- {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1},
+ {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, "yes" },
/*
** .pp
** Controls whether Mutt-ng writes out the Bcc header when preparing
** messages to be sent. Exim users may wish to \fIunset\fP this.
*/
- {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, UL "M%?n?AIL&ail?"},
+ {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, "M%?n?AIL&ail?"},
/*
** .pp
** Controls the format of the X11 icon title, as long as $$xterm_set_titles
** is \fIset\fP. This string is identical in formatting to the one used by
** ``$$status_format''.
*/
- {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, 0},
+ {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, "no" },
/*
** .pp
** Controls whether Mutt-ng sets the xterm title bar and icon name
** (as long as you're in an appropriate terminal). The default must
** be \fIunset\fP to force in the validity checking.
*/
- {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, UL "" },
+ {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, "" },
/*
** .pp
** If $$xterm_set_titles is \fIset\fP, this string will be used to
** .pp
** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
*/
- {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, UL "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
+ {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
/*
** .pp
** Controls the format of the title bar of the xterm provided that
*/
#ifdef USE_NNTP
{"x_comment_to", DT_SYN, R_NONE, UL "nntp_x_comment_to", 0},
- {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, 0},
+ {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, "no" },
/*
** .pp
** Availability: NNTP