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-r408
+ version devel
A\bAb\bbs\bst\btr\bra\bac\bct\bt
+\bo c\bcl\ble\bea\bar\br-\b-f\bfl\bla\bag\bg (default: W)
Furthermore, the following flags reflect who the message is addressed to. They
- can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.324 , page 165) variable.
+ can be customized with the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.325 , page 165) variable.
+
message is to you and you only
_\b2_\b._\b5_\b._\b3 _\bT_\bh_\br_\be_\ba_\bd_\be_\bd _\bM_\bo_\bd_\be
- When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.292 , page 155) by _\bt_\bh_\br_\be_\ba_\bd_\bs, there are
+ When the mailbox is _\bs_\bo_\br_\bt_\be_\bd (section 7.4.293 , page 156) 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.110 , page 111). 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.110 , page 111) to optionally display the number of
+ tion 7.4.111 , page 111). 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.111 , page 111) 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.313 , page 163).
+ See also: _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bt_\bh_\br_\be_\ba_\bd_\bs (section 7.4.314 , page 163).
_\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
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 67), 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 68), you can
change any attachment's content type. These changes are not persistent, and get
lost upon changing folders.
Reply to the current or tagged message(s) by extracting any addresses which
match the regular expressions given by the _\bl_\bi_\bs_\bt_\bs _\bo_\br _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 ,
- page 32) commands, but also honor any Mail-Followup-To header(s) if the
- _\b$_\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.88 , page 106) configuration variable is set.
+ 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.89 , page 106) 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.201 , page 134), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
- (section 7.4.203 , page 135), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.202 , page 135) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.336 , page 167) control the exact behavior of this
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.202 , page 135), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 7.4.204 , page 135), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 7.4.203 , page 135) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.337 , page 168) 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.337 , page 168) variable.
+ the value of the _\b$_\bw_\be_\be_\bd (section 7.4.338 , page 168) 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.336 , page 167) can be used to control whether Mutt-ng will wait for a key
+ 7.4.337 , page 168) 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.226 , page 140) 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.227 , page 140) 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.309 , page 160) 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.310 , page 160) 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.54 , page 98).
+ Also see _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.55 , page 98).
_\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.193 , page 133) permanently.
+ _\b$_\bp_\bg_\bp_\b__\bs_\bi_\bg_\bn_\b__\ba_\bs (section 7.4.194 , page 133) 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.180 , page 130)) have obvious meanings. But some explana-
+ _\bm_\ba_\bt (section 7.4.181 , page 130)) 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.140 ,
+ %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.141 ,
page 119)). 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
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.215 , page 138) variable. This means that you can
+ the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\bd (section 7.4.216 , page 138) 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.214 , page 137) quad-option.
+ See also the _\b$_\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be (section 7.4.215 , page 138) quad-option.
_\b3_\b. _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn
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.54 , page 98) variable set.
+ (section 7.4.55 , page 98) variable set.
In addition, at the various address prompts, you can use the tab character to
expand a partial alias to the full alias. If there are multiple matches, mutt
_\bk_\be_\by does not need to be enclosed in quotes unless it contains a space (`` '').
_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn specifies which action to take when _\bk_\be_\by is pressed. For a complete
- list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 169). The special
+ list of functions, see the _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section 7.5 , page 170). The special
function noop unbinds the specified key sequence.
_\b3_\b._\b5 _\bD_\be_\bf_\bi_\bn_\bi_\bn_\bg _\ba_\bl_\bi_\ba_\bs_\be_\bs _\bf_\bo_\br _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br _\bs_\be_\bt_\bs
mailboxes to execute _\bc_\bo_\bm_\bm_\ba_\bn_\bd before loading. If a mailbox matches multiple
folder-hook's, they are executed in the order given in the muttrc.
- N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.298 , page
- 157) 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.299 , page
+ 158) at the beginning of the pattern, you must place it inside of double or
single quotes in order to distinguish it from the logical _\bn_\bo_\bt operator for the
expression.
invoke a function directly, you can use the format _\b<_\bk_\be_\by _\bn_\ba_\bm_\be_\b> and _\b<_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
_\bn_\ba_\bm_\be_\b>. For a listing of key names see the section on _\bk_\be_\by _\bb_\bi_\bn_\bd_\bi_\bn_\bg_\bs (section
3.4 , page 24). Functions are listed in the _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\br_\be_\bf_\be_\br_\be_\bn_\bc_\be (section
- 7.5 , page 169).
+ 7.5 , page 170).
The advantage with using function names directly is that the macros will work
regardless of the current key bindings, so they are not dependent on the user
+\bo normal
- +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.226 , page 140) in the
+ +\bo quoted (text matching _\b$_\bq_\bu_\bo_\bt_\be_\b__\br_\be_\bg_\be_\bx_\bp (section 7.4.227 , page 140) in the
body of a message)
+\bo quoted1, quoted2, ..., quotedN\bN (higher levels of quoting)
instance, when replying to a message that you sent to a different party, mutt
will automatically suggest to send the response to the original message's
recipients -- responding to yourself won't make much sense in many cases. (See
- _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.234 , page 142).)
+ _\b$_\br_\be_\bp_\bl_\by_\b__\bt_\bo (section 7.4.235 , page 142).)
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
_\b3_\b._\b1_\b1 _\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
+
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-
playing them on fixed-size terminals. But times changed, and nowadays hardly
For introductory information on format=flowed messages, see
<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
+
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:
- set wrapmargin = 10
-
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
terminal.
If your terminal is so wide that the lines are embarrassingly long, you can
also set a maximum line length:
- set max_line_length = 120
+ set max_line_length = 120
The example above will give you lines not longer than 120 characters.
When you view at format=flowed messages, you will often see the quoting hierar-
chy like in the following example:
- >Bill, can you please send last month's progress report to Mr.
- >Morgan? We also urgently need the cost estimation for the new
- >production server that we want to set up before our customer's
- >project will go live.
+ >Bill, can you please send last month's progress report to Mr.
+ >Morgan? We also urgently need the cost estimation for the new
+ >production server that we want to set up before our customer's
+ >project will go live.
This obviously doesn't look very nice, and it makes it very hard to differenti-
ate between text and quoting character. The solution is to configure mutt-ng to
"stuff" the quoting:
- set stuff_quoted
+ set stuff_quoted
This will lead to a nicer result that is easier to read:
- > Bill, can you please send last month's progress report to Mr.
- > Morgan? We also urgently need the cost estimation for the new
- > production server that we want to set up before our customer's
- > project will go live.
+ > Bill, can you please send last month's progress report to Mr.
+ > Morgan? We also urgently need the cost estimation for the new
+ > 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
If you want mutt-ng to send emails with format=flowed set, you need to explic-
itly set it:
- set text_flowed
+ 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.
- _\b3_\b._\b1_\b2 _\bM_\ba_\bi_\bl_\bi_\bn_\bg _\bl_\bi_\bs_\bt_\bs
+ Also note that _\bf_\bo_\br_\bm_\ba_\bt_\b=_\bf_\bl_\bo_\bw_\be_\bd knows about ``space-stuffing'', that is, when
+ sending messages, some kinds of lines have to be indented with a single space
+ on the sending side. On the receiving side, the first space (if any) is
+ removed. As a consequence and in addition to the above simple setting, please
+ keep this in mind when making manual formattings within the editor. Also note
+ that mutt-ng currently violates the standard (RfC 3676) as it does not space-
+ stuff lines starting with:
- The Mutt Next Generation E-Mail Client 33
+ +\bo > This is _\bn_\bo_\bt the quote character but a right angle used for other reasons
+
+ +\bo From with a trailing space.
+
+ +\bo just a space for formatting reasons
+
+ 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
+
+ "
+
+ For completeness, the _\b$_\bd_\be_\bl_\be_\bt_\be_\b__\bs_\bp_\ba_\bc_\be (section 7.4.47 , page 96) 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.
+ Because flowed lines usually contain only one space at the end, this parameter
+ would make the receiving client concatenate the last word of the previous with
+ the first of the current line _\bw_\bi_\bt_\bh_\bo_\bu_\bt a space. This makes ordinary text unread-
+ 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
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 57). In order to take advantage of them, you must specify which addresses
+ page 58). In order to take advantage of them, you must specify which addresses
belong to mailing lists, and which mailing lists you are subscribed to. Once
you have done this, the _\bl_\bi_\bs_\bt_\b-_\br_\be_\bp_\bl_\by (section 2.5.4 , page 12) function will
work for all known lists. Additionally, when you send a message to a sub-
the Mail-Followup-To header is a non-standard extension which is not supported
by all mail user agents. Adding it is not bullet-proof against receiving per-
sonal CCs of list messages. Also note that the generation of the Mail-Fol-
- lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.66 , page 101)
+ lowup-To header is controlled by the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.67 , page 101)
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,
regular expression specifying the mailbox to treat as a ``spool'' mailbox and
_\bm_\ba_\bi_\bl_\bb_\bo_\bx specifies where mail should be saved when read.
- The Mutt Next Generation E-Mail Client 34
-
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).
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
- 56) (such as ``='' and ``!''), any variable definition that affect these char-
- acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.64 , page 100) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 7.4.298 , page 157)) should be executed before the mailboxes command.
+ 57) (such as ``='' and ``!''), any variable definition that affect these char-
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.65 , page 100) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 7.4.299 , page 158)) 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
my_hdr Organization: A Really Big Company, Anytown, USA
- The Mutt Next Generation E-Mail Client 35
-
in your .muttrc.
N\bNo\bot\bte\be:\b: space characters are _\bn_\bo_\bt allowed between the keyword and the colon
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.54 , page 98) 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.55 , page 98) 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
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 53) 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 54) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Examples:
save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
- The Mutt Next Generation E-Mail Client 36
-
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 36) command.
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.231 , page 141). Mutt-ng searches the initial list of message
+ (section 7.4.232 , page 142). 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.231 , page 141) mailbox.
+ 7.4.232 , page 142) 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 53) 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 54) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example: fcc-hook [@.]aol\\.com$ +spammers
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 35) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 35) with its arguments.
+ 3.18 , page 36) and a _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 36) 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
and _\br_\be_\bp_\bl_\bi_\be_\bs. N\bNo\bot\bte\be:\b: reply-hooks are matched b\bbe\bef\bfo\bor\bre\be the send-hook, r\bre\beg\bga\bar\brd\bdl\ble\bes\bss\bs of
the order specified in the users's configuration file.
- The Mutt Next Generation E-Mail Client 37
-
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.248 , page 145) variable depending on the message's
+ _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.249 , page 146) variable depending on the message's
sender address.
For each type of send-hook or reply-hook, when multiple matches occur, commands
are executed in the order they are specified in the muttrc (for that type of
hook).
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 53) 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 54) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example: send-hook mutt 'set mime_forward signature='''
- Another typical use for this command is to change the values of the _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\b-
- _\bt_\bi_\bo_\bn (section 7.4.15 , page 89), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.260 , page 148) and
- _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.114 , page 114) variables in order to change the language
- of the attributions and signatures based upon the recipients.
+ Another typical use for this command is to change the values of the
+
+ The Mutt Next Generation E-Mail Client 38
+
+ _\b$_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\bi_\bo_\bn (section 7.4.15 , page 89), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 7.4.261 , page
+ 149) and _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.115 , page 114) variables in order to change the
+ language of the attributions and signatures based upon the recipients.
N\bNo\bot\bte\be:\b: the send-hook's are only executed ONCE after getting the initial list of
recipients. Adding a recipient after replying or editing the message will NOT
tiple matches occur, commands are executed in the order they are specified in
the muttrc.
- See _\bM_\be_\bs_\bs_\ba_\bg_\be _\bM_\ba_\bt_\bc_\bh_\bi_\bn_\bg _\bi_\bn _\bH_\bo_\bo_\bk_\bs (section 4.5.1 , page 53) 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 54) for information on the
exact format of _\bp_\ba_\bt_\bt_\be_\br_\bn.
Example:
Usage: crypt-hook _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\bi_\bd
- When encrypting messages with PGP or OpenSSL, you may want to associate a
-
- The Mutt Next Generation E-Mail Client 38
-
- certain key with a given e-mail address automatically, either because the
- recipient's public key can't be deduced from the destination address, or
- because, for some reasons, you need to override the key Mutt-ng would normally
- use. The 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.
+ When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
+ tain key with a given e-mail address automatically, either because the recipi-
+ ent's public key can't be deduced from the destination address, or because, for
+ some reasons, you need to override the key Mutt-ng would normally use. The
+ 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 meaning of "key id" is to be taken broadly in this context: You can either
put a numerical key ID here, an e-mail address, or even just a real name.
Usage: push _\bs_\bt_\br_\bi_\bn_\bg
- This command adds the named string to the keyboard buffer. The string may con-
- tain control characters, key names and function names like the sequence string
- in the _\bm_\ba_\bc_\br_\bo (section 3.7 , page 27) command. You may use it to automatically
- run a sequence of commands at startup, or when entering certain folders.
+ This command adds the named string to the keyboard buffer. The string may
+
+ The Mutt Next Generation E-Mail Client 39
+
+ 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
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 169). ``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 170). ``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
score "~f nion@muttng\.org" 50
score "~f @sco\.com" -100
- The Mutt Next Generation E-Mail Client 39
-
If the pattern matches, it is also possible to set the score value of the cur-
rent message to a certain value and then stop evaluation:
+\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.245 , page 145), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.246 , page 145),
- _\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.244 , page 144) 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.246 , page 145) 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.244 , page 144) are set to -1, which means that in the default
+ tion 7.4.246 , page 145), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 7.4.247 , page 145),
+ _\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.245 , page 145) 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.247 , page 145) 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.245 , page 145) are set to -1, which means that in the default
threshold configuration no message will ever get marked as read or deleted.
Scoring gets especially interesting when combined with the color command and
your spam patterns with the spam and nospam commands, you can _\bl_\bi_\bm_\bi_\bt, _\bs_\be_\ba_\br_\bc_\bh,
and _\bs_\bo_\br_\bt your mail based on its spam attributes, as determined by the external
filter. You also can display the spam attributes in your index display using
-
- The Mutt Next Generation E-Mail Client 40
-
- the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.110 , page 111) variable.
+ the %H selector in the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111) variable.
(Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
given message.)
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
mutt will sort numerically first, and lexically only when two numbers are equal
in value. (This is like UNIX's sort -n.) A message with no spam attributes at
all -- that is, one that didn't match _\ba_\bn_\by of your spam patterns -- is sorted at
-
- The Mutt Next Generation E-Mail Client 41
-
lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
``z''. Clearly, in general, sorting by spam tags is most effective when you can
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.
if you had answered ``no.'' A value of _\ba_\bs_\bk_\b-_\by_\be_\bs will cause a prompt with a
default answer of ``yes'' and _\ba_\bs_\bk_\b-_\bn_\bo will provide a default answer of ``no.''
- The Mutt Next Generation E-Mail Client 42
-
Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
For _\bb_\bo_\bo_\bl_\be_\ba_\bn variables, you may optionally prefix the variable name with inv to
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-
This command permits you to flush hooks you have previously defined. You can
either remove all hooks by giving the ``*'' character as an argument, or you
can remove all hooks of a specific type by saying something like unhook send-
-
- The Mutt Next Generation E-Mail Client 43
-
hook.
_\b3_\b._\b3_\b0 _\bS_\bh_\ba_\br_\bi_\bn_\bg _\bS_\be_\bt_\bu_\bp_\bs
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 = "..."
To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
for mutt. Its basic syntax is:
- The Mutt Next Generation E-Mail Client 44
-
ifdef <item> <command>
ifndef <item> <command>
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.99 , page 108),
+ test for the availability of _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.100 , page 109),
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.170 , page 127) only if the pager menu is available, use:
+ (section 7.4.171 , page 128) only if the pager menu is available, use:
ifdef pager 'set pager_index_lines = 10'
For completeness, too, the opposite of ifdef is provided: ifndef which only
executes the command if the test fails. For example, the following two examples
-
- The Mutt Next Generation E-Mail Client 45
-
are equivalent:
ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
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
In the process of ensuring and creating more consistency, many variables have
ace it with \ (backslash).
The fundamental building blocks are the regular expressions that match a single
-
- The Mutt Next Generation E-Mail Client 46
-
character. Most characters, including all letters and digits, are regular
expressions that match themselves. Any metacharacter with special meaning may
be quoted by preceding it with a backslash.
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:
[:space:]
Space characters (such as space, tab and formfeed, to name a few).
- The Mutt Next Generation E-Mail Client 47
-
[:upper:]
Upper-case alphabetic characters.
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''.
The preceding item is matched at least _\bn times, but no more than _\bm
times.
- The Mutt Next Generation E-Mail Client 48
-
Two regular expressions may be concatenated; the resulting regular expression
matches any string formed by concatenating two substrings that respectively
match the concatenated subexpressions.
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.
_\bt_\be_\br_\bn_\bs (section 7.2 , page 80) in the Reference chapter.
It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
-
- The Mutt Next Generation E-Mail Client 49
-
expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
possible.
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'
~d 28/12/2004*1d
The first pattern matches all dates between January 1st, 2005 and January 1st
-
- The Mutt Next Generation E-Mail Client 50
-
2006. The second pattern matches all dates between October 18th, 2004 and
October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
_\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.309 , page 160) variable. For the hostname and version
+ _\bm_\ba_\bt (section 7.4.310 , page 160) variable. For the hostname and version
string, there's an expando for $status_format: %h expands to the hostname and
%v to the version string. When just configuring:
In the index, there're more useful information one could want to see:
- The Mutt Next Generation E-Mail Client 51
-
+\bo which mailbox is open
+\bo how man new, flagged or postponed messages
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.
%?<item>?<string if nonzero>&<string if zero>?
- The Mutt Next Generation E-Mail Client 52
-
Using this we can make mutt-ng to do the following:
+\bo make it print ``_\bn new messages'' whereby _\bn is the count but only if there
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.
Since the previous expando stops at the end of line, there must be
a way to fill the gap between two items via the %>X expando: it
puts as many characters X in between two items so that the rest of
- the line will be right-justified. For example, to not put the
-
- The Mutt Next Generation E-Mail Client 53
-
- version string and hostname of our example on the left but on the
+ the line will be right-justified. For example, to not put the ver-
+ sion string and hostname of our example on the left but on the
right and fill the gap with spaces, one might use (note the space
after %>):
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 80) for Mutt-ng's pattern matching
syntax.
page 90) variable is set, the next operation applies to the tagged messages
automatically, without requiring the ``tag-prefix''.
- In _\bm_\ba_\bc_\br_\bo_\bs (section 3.7 , page 27) or _\bp_\bu_\bs_\bh (section 3.23 , page 37) commands,
+ In _\bm_\ba_\bc_\br_\bo_\bs (section 3.7 , page 27) or _\bp_\bu_\bs_\bh (section 3.23 , page 38) 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 44) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 80) along
+ _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 45) or _\bp_\ba_\bt_\bt_\be_\br_\bn (section 7.2 , page 80) 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 _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 36)
+ +\bo _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 3.20 , page 37)
+\bo _\bm_\be_\bs_\bs_\ba_\bg_\be_\b-_\bh_\bo_\bo_\bk (section 3.21 , page 37)
- The Mutt Next Generation E-Mail Client 54
-
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 35)
+ +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 36)
- +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 33)
+ +\bo _\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34)
- +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 35)
+ +\bo _\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 36)
+\bo _\bf_\bc_\bc_\b-_\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.19 , page 36)
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 44) is sufficient. But in dealing with
+ _\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn (section 4.1 , page 45) 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.
_\b4_\b._\b6 _\bU_\bs_\bi_\bn_\bg _\bt_\bh_\be _\bs_\bi_\bd_\be_\bb_\ba_\br
- The Mutt Next Generation E-Mail Client 55
-
The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
which looks very similar to the ones you probably know from GUI mail clients.
The sidebar lists all specified mailboxes, shows the number in each and high-
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
_\b4_\b._\b7 _\bE_\bx_\bt_\be_\br_\bn_\ba_\bl _\bA_\bd_\bd_\br_\be_\bs_\bs _\bQ_\bu_\be_\br_\bi_\be_\bs
- The Mutt Next Generation E-Mail Client 56
-
Mutt-ng supports connecting to external directory databases such as LDAP,
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
- simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.222 , page 139) vari-
+ simple interface. Using the _\b$_\bq_\bu_\be_\br_\by_\b__\bc_\bo_\bm_\bm_\ba_\bn_\bd (section 7.4.223 , page 140) vari-
able, you specify the wrapper command to use. For example:
set query_command = "mutt_ldap_query.pl '%s'"
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.126 , page 116)
+ uses the default specified with the _\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.127 , page 117)
variable.
m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All messages are
From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
- The Mutt Next Generation E-Mail Client 57
-
to denote the start of a new message (this is often referred to as the
``From_'' line).
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.298 , page 157) (incoming)
+ +\bo ! -- refers to your _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.299 , page 158) (incoming)
mailbox
- +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.125 , page 116) file
+ +\bo > -- refers to your _\b$_\bm_\bb_\bo_\bx (section 7.4.126 , page 117) file
- +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.231 , page 141) file
+ +\bo < -- refers to your _\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.232 , page 142) 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.64 , page 100) directory
+ +\bo = or + -- refers to your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.65 , page 100) directory
- +\bo @_\ba_\bl_\bi_\ba_\bs -- refers to the _\bd_\be_\bf_\ba_\bu_\bl_\bt _\bs_\ba_\bv_\be _\bf_\bo_\bl_\bd_\be_\br (section 3.17 , page 35) as
+ +\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
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
mail easier. The first thing you must do is to let Mutt know what addresses
you consider to be mailing lists (technically this does not have to be a mail-
ing list, but that is what it is most often used for), and what lists you are
-
- The Mutt Next Generation E-Mail Client 58
-
subscribed to. This is accomplished through the use of the _\bl_\bi_\bs_\bt_\bs _\ba_\bn_\bd _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be
- (section 3.12 , page 32) commands in your muttrc.
+ (section 3.12 , page 33) 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.110 , page 111) variable, the escape
+ box. In the _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111) variable, the escape
``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
returns the name of the author).
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.66 , page 101) option is set, mutt will
+ and if the _\b$_\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo (section 7.4.67 , page 101) 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.88 , page 106) configuration variable is set. Using list-reply
+ (section 7.4.89 , page 106) 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.234 , page 142) variable to help decide which address to use. If set to
+ 7.4.235 , page 142) 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.110 , page 111) variable's ``%y'' and ``%Y''
-
- The Mutt Next Generation E-Mail Client 59
-
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111) 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.292 , page 155) the mail-
+ Lastly, Mutt-ng has the ability to _\bs_\bo_\br_\bt (section 7.4.293 , page 156) 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-
_\b4_\b._\b1_\b1 _\bE_\bd_\bi_\bt_\bi_\bn_\bg _\bt_\bh_\br_\be_\ba_\bd_\bs
Mutt-ng has the ability to dynamically restructure threads that are broken
+
+ The Mutt Next Generation E-Mail Client 60
+
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.
+\bo Berkeley sendmail 8.8.x currently has some command line options in which
the mail client can make requests as to what type of status messages
-
- The Mutt Next Generation E-Mail Client 60
-
should be returned.
+\bo The SMTP support via libESMTP supports it, too.
To support this, there are two variables:
- +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.51 , page 97) is used to request receipts for
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 7.4.52 , page 97) 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.52 , page 97) requests how much of your message
+ +\bo _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 7.4.53 , page 97) 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.209 , page 136) variable, which defaults
+ by the _\b$_\bp_\bo_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.210 , page 137) 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.207 , page 136), fetch all your
- new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.298 , page 157).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.208 , page 136), fetch all your
+ new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 7.4.299 , page 158).
After this point, Mutt-ng runs exactly as if the mail had always been local.
N\bNo\bot\bte\be:\b: If you only need to fetch all messages to local mailbox you should con-
_\b4_\b._\b1_\b4 _\bI_\bM_\bA_\bP _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
- The Mutt Next Generation E-Mail Client 61
-
If Mutt-ng was compiled with IMAP support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bi_\bm_\ba_\bp flag), it has the ability to work with folders located on a
remote IMAP server.
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.97 , page 108) vari-
+ command. See also the _\b$_\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd (section 7.4.98 , page 108) vari-
able.
Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
- want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.99 , page 108) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.322 , page 164) 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.100 , page 109) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.323 , page 165) variables.
Note that if you are using mbox as the mail store on UW servers prior to
v12.250, the server has been reported to disconnect a client if another client
sages and subfolders. On Cyrus-like servers folders will often contain
both messages and subfolders.
- The Mutt Next Generation E-Mail Client 62
-
+\bo For the case where an entry can contain both messages and subfolders, the
selection key (bound to enter by default) will choose to descend into the
subfolder view. If you wish to view the messages in that folder, you must
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.105 , page 110) - controls the username under
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.106 , page 110) - 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.100 , page 109) - a password which you may pre-
+ +\bo _\b$_\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.101 , page 109) - 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.91 , page 106) - 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.92 , page 107) - a colon-delimited list
of IMAP authentication methods to try, in the order you wish to try them.
If specified, this overrides mutt's default (attempt everything, in the
order listed above).
newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
function from the index/pager which is by default bound to i.
- The Default newsserver can be obtained from the $NNTPSERVER environment
-
- The Mutt Next Generation E-Mail Client 63
-
- variable. Like other news readers, info about subscribed newsgroups is saved in
- a file as specified by the _\b$_\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc (section 7.4.157 , page 124) variable.
+ 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.158 , page 125) 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.
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-
_\b4_\b._\b1_\b6 _\bS_\bM_\bT_\bP _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
-
- The Mutt Next Generation E-Mail Client 64
-
functionality. When configure was called with --with-libesmtp or the output
muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
support includes support for Delivery Status Notification (see _\bD_\be_\bl_\bi_\bv_\be_\br_\by _\bS_\bt_\ba_\bt_\bu_\bs
_\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 59) section) as well as handling the 8BIT-
- MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.329 , page 166).
+ MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 7.4.330 , page 166).
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.287 , page 154)
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 7.4.288 , page 154)
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.291 ,
- page 155) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.288 , page 154) variables.
+ Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 7.4.292 ,
+ page 155) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 7.4.289 , page 155) 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.290 , page 155) variable must be either set to
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 7.4.291 , page 155) 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.286 ,
+ 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.287 ,
page 154) may be used to set the envelope different from the From: header.
_\b4_\b._\b1_\b7 _\bM_\ba_\bn_\ba_\bg_\bi_\bn_\bg _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bI_\bM_\bA_\bP_\b/_\bP_\bO_\bP_\b/_\bN_\bN_\bT_\bP _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\bs _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
macro index \cb |urlview\n
macro pager \cb |urlview\n
- The Mutt Next Generation E-Mail Client 65
-
_\b4_\b._\b1_\b9 _\bC_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs _\bS_\bu_\bp_\bp_\bo_\br_\bt _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
If Mutt-ng was compiled with compressed folders support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\b-
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 65), _\bc_\bl_\bo_\bs_\be_\b-
- _\bh_\bo_\bo_\bk (section 4.19.2 , page 65) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66))
+ _\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 66))
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"
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 66), the folder will be open and closed again each time you
- will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65) (or give
+ 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
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 66) though you'll be able to append to the folder.
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.241 , page 144), so that the compressed file
+ unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 7.4.242 , page 144), so that the compressed file
will be removed if you delete all of the messages.
_\b4_\b._\b1_\b9_\b._\b1 _\bO_\bp_\be_\bn _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\bf_\bo_\br _\br_\be_\ba_\bd_\bi_\bn_\bg
%f and %t can be repeated any number of times in the command string, and all of
the entries are replaced with the appropriate folder name. In addition, %% is
-
- The Mutt Next Generation E-Mail Client 66
-
replaced by %, as in printf, and any other %anything is left as is.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should n\bno\bot\bt remove the original compressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should
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 65) command after some changes were made to it.
+ The Mutt Next Generation E-Mail Client 67
+
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 65) command. Temporary folder in this case is the folder previ-
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 65) is not called when you exit from the
+ _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 66) 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
Example:
- The Mutt Next Generation E-Mail Client 67
-
append-hook \\.gz$ "gzip -c %t >> %f"
When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66) is used, the folder is not opened,
which saves time, but this means that we can not find out what the folder type
- is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.126 , page 116)) type is always
+ is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 7.4.127 , page 117)) type is always
supposed (i.e. this is the format used for the temporary folder).
If the file does not exist when you save to it, _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 ,
- page 65) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66). _\ba_\bp_\bp_\be_\bn_\bd_\b-
+ page 66) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 66). _\ba_\bp_\bp_\be_\bn_\bd_\b-
_\bh_\bo_\bo_\bk (section 4.19.3 , page 66) is only for appending to existing folders.
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type. In this
case, the folder will be open and closed again (using _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.19.1 , page 65) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65)respectively) each
+ 4.19.1 , page 65) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 66)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
There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
(while viewing a message), the attachment menu and the compose menu.
- The Mutt Next Generation E-Mail Client 68
-
_\b5_\b._\b1_\b._\b1 _\bV_\bi_\be_\bw_\bi_\bn_\bg _\bM_\bI_\bM_\bE _\bm_\be_\bs_\bs_\ba_\bg_\be_\bs _\bi_\bn _\bt_\bh_\be _\bp_\ba_\bg_\be_\br
When you select a message from the index and view it in the pager, Mutt decodes
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) --]
- 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
- The Mutt Next Generation E-Mail Client 69
-
The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
or canceling) the message. It can be toggled with the toggle-unlink command
(default: u). The next field is the MIME content-type, and can be changed with
_\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
referred to as the mailcap format. Many MIME compliant programs utilize the
mailcap format, allowing you to specify handling for all MIME types in one
place for all programs. Programs known to use this format include Netscape,
-
- The Mutt Next Generation E-Mail Client 70
-
XMosaic, lynx and metamail.
In order to handle various MIME types that Mutt-ng can not handle internally,
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/plain; more %s
- The Mutt Next Generation E-Mail Client 71
-
Perhaps you would like to use lynx to interactively view a text/html message:
text/html; lynx %s
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.117 , page 115) variable.
+ them, see the _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be (section 7.4.118 , page 115) variable.
Although mutt's procedures to invoke programs with mailcap seem to be safe,
there are other applications parsing mailcap, maybe taking less care of it.
text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
- The Mutt Next Generation E-Mail Client 72
-
_\b5_\b._\b3_\b._\b3 _\bA_\bd_\bv_\ba_\bn_\bc_\be_\bd _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bU_\bs_\ba_\bg_\be
_\b5_\b._\b3_\b._\b3_\b._\b1 _\bO_\bp_\bt_\bi_\bo_\bn_\ba_\bl _\bF_\bi_\be_\bl_\bd_\bs
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 75), in order to decide whether it should honor
- the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.336 , page 167) variable
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.337 , page 168) 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.336 , page 167) and the exit
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 7.4.337 , page 168) and the exit
status of the program to decide if it will ask you to press a key
after the external program has exited. In all other situations it
will not prompt you for a key.
edit=<command>
This flag specifies the command to use to edit a specific MIME
type. Mutt-ng supports this from the compose menu, and also uses
-
- The Mutt Next Generation E-Mail Client 73
-
it to compose new attachments. Mutt-ng will default to the defined
editor for text attachments.
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
can then use the test feature to determine which viewer to use interactively
depending on your environment.
- The Mutt Next Generation E-Mail Client 74
-
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s; nametemplate=%s.html
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
_\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 75
-
# I'm always running X :)
video/*; xanim %s > /dev/null
image/*; xv %s > /dev/null
This mailcap file shows quite a number of examples:
+ The Mutt Next Generation E-Mail Client 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
-
- The Mutt Next Generation E-Mail Client 76
-
- viewing MIME attachments while in the pager.
+ viewer defined in the mailcap file, Mutt-ng has support for automatically view-
+ ing MIME attachments while in the pager.
To work, you must define a viewer in the mailcap file which uses the copi-
ousoutput option to denote that it is non-interactive. Usually, you also use
For instance, if you set auto_view to:
+ The Mutt Next Generation E-Mail Client 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-
_\b5_\b._\b6 _\bM_\bI_\bM_\bE _\bL_\bo_\bo_\bk_\bu_\bp
Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
-
- The Mutt Next Generation E-Mail Client 77
-
treated according to their mailcap entry. This option is designed to deal with
binary types such as application/octet-stream. When an attachment's mime-type
is listed in mime_lookup, then the extension of the filename will be compared
mime_lookup application/octet-stream application/X-Lotus-Manuscript
In addition, the unmime_lookup command may be used to disable this feature for
+
+ The Mutt Next Generation E-Mail Client 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.327 , page 166) variable can be used to
+ natures, etc. The _\b$_\bu_\bm_\ba_\bs_\bk (section 7.4.328 , page 166) 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.323 , page 165)
+ be desired which can be changed via the _\b$_\bt_\bm_\bp_\bd_\bi_\br (section 7.4.324 , page 165)
variable.
- The Mutt Next Generation E-Mail Client 78
-
_\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.143 , page 120) variable. Please make sure
+ of the _\b$_\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.144 , page 120) 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.54 , page 98) 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.55 , page 98) 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.311 , page 162) 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.312 , page 162) 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.54 , page 98) variable by force to
+ +\bo turn on the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.55 , page 98) 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.116 , page 114) variable for
+ cap files (see the _\b$_\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh (section 7.4.117 , page 115) variable for
details.)
- These utilities may have a variety of security vulnerabilities, including
-
- The Mutt Next Generation E-Mail Client 79
-
- overwriting of arbitrary files, information leaks or other exploitable bugs.
- These vulnerabilities may go unnoticed by the user, especially when they are
- called automatically (and without interactive prompting) from the mailcap
- file(s). When using mutt-ng's autoview mechanism in combination with mailcap
- files, please be sure to...
+ These utilities may have a variety of security vulnerabilities, including over-
+ writing of arbitrary files, information leaks or other exploitable bugs. These
+ vulnerabilities may go unnoticed by the user, especially when they are called
+ automatically (and without interactive prompting) from the mailcap file(s).
+ When using mutt-ng's autoview mechanism in combination with mailcap files,
+ please be sure to...
+\bo manually select trustworth applications with a reasonable calling sequence
+\bo periodically check the contents of mailcap files, especially after soft-
ware installations or upgrades
+ The Mutt Next Generation E-Mail Client 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.117 , page 115) 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.118 , page 115) 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 80
-
-A expand an alias
-a attach a file to a message
-b specify a blind carbon-copy (BCC) address
To read messages in a mailbox
+ The Mutt Next Generation E-Mail Client 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 81
+ The Mutt Next Generation E-Mail Client 82
~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
- 44). Special attention has to be made when using regular expressions inside of
+ 45). 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 82
+ The Mutt Next Generation E-Mail Client 83
*) 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 63) _\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 64) _\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 _\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_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65) _\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 66) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\bc_\bo_\bl_\bo_\br (section 3.8 , page 27) _\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 27) _\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 37) _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+ +\bo _\be_\bx_\be_\bc (section 3.24 , page 38) _\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 35) _\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.18 , page 36) _\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 36) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+\bo _\bi_\bg_\bn_\bo_\br_\be (section 3.9 , page 30) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- The Mutt Next Generation E-Mail Client 83
+ The Mutt Next Generation E-Mail Client 84
+\bo _\bu_\bn_\bi_\bg_\bn_\bo_\br_\be (section 3.9 , page 30) _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
- +\bo _\bl_\bi_\bs_\bt_\bs (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\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.12 , page 32) _\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 _\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_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.14 , page 33) _\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.14 , page 34) _\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 33) _\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.13 , page 34) _\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 37) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\bu_\bn_\bm_\bo_\bn_\bo (section 3.8 , page 27) _\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 34) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 35) _\bs_\bt_\br_\bi_\bn_\bg
- +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 34) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ +\bo _\bu_\bn_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 35) _\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 65) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- +\bo _\bc_\br_\by_\bp_\bt_\b-_\bh_\bo_\bo_\bk (section 3.22 , page 37) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
+ +\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 _\bp_\bu_\bs_\bh (section 3.23 , page 37) _\bs_\bt_\br_\bi_\bn_\bg
+ +\bo _\bp_\bu_\bs_\bh (section 3.23 , page 38) _\bs_\bt_\br_\bi_\bn_\bg
+\bo _\br_\be_\bs_\be_\bt (section 3.27 , page 41) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- +\bo _\bs_\ba_\bv_\be_\b-_\bh_\bo_\bo_\bk (section 3.17 , page 35) _\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.17 , page 36) _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+\bo _\bs_\bc_\bo_\br_\be (section 3.25 , page 38) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
+\bo _\bu_\bn_\bs_\bc_\bo_\br_\be (section 3.25 , page 38) _\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 36) _\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.20 , page 37) _\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_\bo_\bu_\br_\bc_\be (section 3.28 , page 42) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- +\bo _\bs_\bp_\ba_\bm (section 3.26 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
+ +\bo _\bs_\bp_\ba_\bm (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bo_\br_\bm_\ba_\bt
- +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.26 , page 39) _\bp_\ba_\bt_\bt_\be_\br_\bn
+ +\bo _\bn_\bo_\bs_\bp_\ba_\bm (section 3.26 , page 40) _\bp_\ba_\bt_\bt_\be_\br_\bn
- The Mutt Next Generation E-Mail Client 84
+ The Mutt Next Generation E-Mail Client 85
- +\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\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.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ +\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 33) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bt_\bo_\bg_\bg_\bl_\be (section 3.27 , page 41) _\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 42) _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
+ +\bo _\bu_\bn_\bh_\bo_\bo_\bk (section 3.29 , page 43) _\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 85
+ The Mutt Next Generation E-Mail Client 86
edit_hdrs edit_headers
forw_decode forward_decode
If set to _\by_\be_\bs, when composing messages and no subject is given at the subject
- The Mutt Next Generation E-Mail Client 86
+ The Mutt Next Generation E-Mail Client 87
prompt, composition will be aborted. If set to _\bn_\bo, composing messages with no
subject given at the subject prompt will never be aborted.
Default: yes
- The Mutt Next Generation E-Mail Client 87
+ The Mutt Next Generation E-Mail Client 88
Controls whether 8-bit data is converted to 7-bit using either quoted-printable
or base64 encoding when sending mail.
If _\bs_\be_\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
the body of an outgoing message.
- The Mutt Next Generation E-Mail Client 88
+ The Mutt Next Generation E-Mail Client 89
_\b7_\b._\b4_\b._\b1_\b1 _\ba_\bs_\bs_\bu_\bm_\be_\bd_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
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.312 , page 162) is unset.
+ is valid only if _\b$_\bs_\bt_\br_\bi_\bc_\bt_\b__\bm_\bi_\bm_\be (section 7.4.313 , page 163) is unset.
_\b7_\b._\b4_\b._\b1_\b2 _\ba_\bt_\bt_\ba_\bc_\bh_\b__\bf_\bo_\br_\bm_\ba_\bt
%M
MIME subtype
- The Mutt Next Generation E-Mail Client 89
+ The Mutt Next Generation E-Mail Client 90
%n
attachment number
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.110 , page 111)''.
+ on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111)''.
_\b7_\b._\b4_\b._\b1_\b6 _\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg
- The Mutt Next Generation E-Mail Client 90
+ The Mutt Next Generation E-Mail Client 91
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.54 , page 98)'', Mutt-ng will
+ When _\bs_\be_\bt along with ``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 7.4.55 , page 98)'', Mutt-ng will
skip the initial send-menu and allow you to immediately begin editing the body
of your message. The send-menu may still be accessed once you have finished
editing the body of your message.
- Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.60 , page 99)''.
+ Also see ``_\b$_\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by (section 7.4.61 , page 99)''.
_\b7_\b._\b4_\b._\b1_\b8 _\bb_\be_\be_\bp
Type: boolean
- The Mutt Next Generation E-Mail Client 91
+ The Mutt Next Generation E-Mail Client 92
Default: yes
When _\bs_\be_\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
Especially with MH mailboxes, this operation can take quite some time since it
- The Mutt Next Generation E-Mail Client 92
+ The Mutt Next Generation E-Mail Client 93
involves scanning the directory and checking each file to see if it has already
been looked at. If it's _\bu_\bn_\bs_\be_\bt, no check for new mail is performed while the
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.309 , page 160)'', but has
+ string is similar to ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.310 , page 160)'', 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.309 , page 160)''
+ See the text describing the ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.310 , page 160)''
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.27 ,
page 92)''.
When _\bs_\be_\bt, Mutt-ng will prompt for confirmation when appending messages to an
- The Mutt Next Generation E-Mail Client 93
+ The Mutt Next Generation E-Mail Client 94
existing mailbox.
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.231 , page
- 141)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.242 , page 144)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
- 7.4.68 , page 101)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 35)''.
+ saved for later references. Also see ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.232 , page
+ 142)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.243 , page 144)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 7.4.69 , page 102)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 36)''.
_\b7_\b._\b4_\b._\b3_\b4 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\be_\bn_\bc_\br_\by_\bp_\bt
going messages. This is probably only useful in connection to the _\bs_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk
command. It can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when encryption is not
required or signing is requested as well. If ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section
- 7.4.278 , page 152)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
+ 7.4.279 , page 153)'' is _\bs_\be_\bt, then OpenSSL is used instead to create S/MIME
messages and settings can be overridden by use of the _\bs_\bm_\bi_\bm_\be_\b-_\bm_\be_\bn_\bu. (Crypto
only)
- The Mutt Next Generation E-Mail Client 94
+ The Mutt Next Generation E-Mail Client 95
_\b7_\b._\b4_\b._\b3_\b5 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bp_\bg_\bp
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.34 , page 93)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.38 , page 94)'',
``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.36 , page 94)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.39 , page 94)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.278 , page 152)''.
+ 7.4.39 , page 94)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.279 , page 153)''.
_\b7_\b._\b4_\b._\b3_\b6 _\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn
Setting this variable will cause Mutt-ng to always attempt to cryptographically
sign outgoing messages. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when
signing is not required or encryption is requested as well. If
- ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.278 , page 152)'' 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.279 , page 153)'' 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)
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.34 , page 93)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 7.4.38 , page 94)'',
``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 7.4.36 , page 94)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 7.4.39 , page 94)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.278 , page 152)''.
+ 7.4.39 , page 94)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 7.4.279 , page 153)''.
_\b7_\b._\b4_\b._\b3_\b8 _\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt
If _\bs_\be_\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
- The Mutt Next Generation E-Mail Client 95
+ The Mutt Next Generation E-Mail Client 96
N\bNo\bot\bte\be:\b: this does not work on messages that are encrypted a\ban\bnd\bd signed! (Crypto
only)
Type: string
- The Mutt Next Generation E-Mail Client 96
+ The Mutt Next Generation E-Mail Client 97
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.110 , page 111)''. This is passed to strftime(3)
+ ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111)''. 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.114 , page 114)''. If the first character in the string
+ ``_\b$_\bl_\bo_\bc_\ba_\bl_\be (section 7.4.115 , page 114)''. 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).
be purged without prompting. If set to _\bn_\bo, messages marked for deletion will
be kept in the mailbox.
- _\b7_\b._\b4_\b._\b4_\b7 _\bd_\be_\bl_\be_\bt_\be_\b__\bu_\bn_\bt_\ba_\bg
+ _\b7_\b._\b4_\b._\b4_\b7 _\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.
+
+ 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.
+
+ _\b7_\b._\b4_\b._\b4_\b8 _\bd_\be_\bl_\be_\bt_\be_\b__\bu_\bn_\bt_\ba_\bg
+
+ The Mutt Next Generation E-Mail Client 98
Type: boolean
tion. This applies when you either explicitly delete a message, or when you
save it to another folder.
- _\b7_\b._\b4_\b._\b4_\b8 _\bd_\bi_\bg_\be_\bs_\bt_\b__\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be
+ _\b7_\b._\b4_\b._\b4_\b9 _\bd_\bi_\bg_\be_\bs_\bt_\b__\bc_\bo_\bl_\bl_\ba_\bp_\bs_\be
Type: boolean
Default: yes
- The Mutt Next Generation E-Mail Client 97
-
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._\b4_\b9 _\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br
+ _\b7_\b._\b4_\b._\b5_\b0 _\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.49 ,
+ 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.50 ,
page 97), and the filtered message is read from the standard output.
- _\b7_\b._\b4_\b._\b5_\b0 _\bd_\bo_\bt_\bl_\bo_\bc_\bk_\b__\bp_\br_\bo_\bg_\br_\ba_\bm
+ _\b7_\b._\b4_\b._\b5_\b1 _\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_\b1 _\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by
+ _\b7_\b._\b4_\b._\b5_\b2 _\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by
Type: string
Example: set dsn_notify='failure,delay'
- _\b7_\b._\b4_\b._\b5_\b2 _\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn
+ The Mutt Next Generation E-Mail Client 99
+
+ _\b7_\b._\b4_\b._\b5_\b3 _\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn
Type: string
It may be set to either _\bh_\bd_\br_\bs to return just the message header, or _\bf_\bu_\bl_\bl to
return the full message.
- The Mutt Next Generation E-Mail Client 98
-
Example: set dsn_return=hdrs
- _\b7_\b._\b4_\b._\b5_\b3 _\bd_\bu_\bp_\bl_\bi_\bc_\ba_\bt_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
+ _\b7_\b._\b4_\b._\b5_\b4 _\bd_\bu_\bp_\bl_\bi_\bc_\ba_\bt_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\bs
Type: boolean
indicate that it thinks they are duplicates of each other with an equals sign
in the thread diagram.
- _\b7_\b._\b4_\b._\b5_\b4 _\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b5_\b5 _\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_\b5 _\be_\bd_\bi_\bt_\bo_\br
+ _\b7_\b._\b4_\b._\b5_\b6 _\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_\b6 _\be_\bn_\bc_\bo_\bd_\be_\b__\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b5_\b7 _\be_\bn_\bc_\bo_\bd_\be_\b__\bf_\br_\bo_\bm
Type: boolean
When _\bs_\be_\bt, Mutt-ng will quoted-printable encode messages when they contain the
string ``From '' (note the trailing space) in the beginning of a line. Useful
to avoid the tampering certain mail delivery and transport agents tend to do
+
+ The Mutt Next Generation E-Mail Client 100
+
with messages.
- _\b7_\b._\b4_\b._\b5_\b7 _\be_\bn_\bt_\br_\bo_\bp_\by_\b__\bf_\bi_\bl_\be
+ N\bNo\bot\bte\be:\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
+ <em/strongly/ advised to _\bs_\be_\bt this option although discouraged by the standard.
+ Alternatively, you must take care of space-stuffing <tt/From / lines (with a
+ trailing space) yourself.
+
+ _\b7_\b._\b4_\b._\b5_\b8 _\be_\bn_\bt_\br_\bo_\bp_\by_\b__\bf_\bi_\bl_\be
Type: path
The file which includes random data that is used to initialize SSL library
functions.
- The Mutt Next Generation E-Mail Client 99
-
- _\b7_\b._\b4_\b._\b5_\b8 _\be_\bn_\bv_\be_\bl_\bo_\bp_\be_\b__\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b5_\b9 _\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.248 , page 145) yourself, or
+ are using that switch in _\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 7.4.249 , page 146) yourself, or
if the sendmail on your machine doesn't support that command line switch.
- _\b7_\b._\b4_\b._\b5_\b9 _\be_\bs_\bc_\ba_\bp_\be
+ _\b7_\b._\b4_\b._\b6_\b0 _\be_\bs_\bc_\ba_\bp_\be
Type: string
Escape character to use for functions in the builtin editor.
- _\b7_\b._\b4_\b._\b6_\b0 _\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by
+ _\b7_\b._\b4_\b._\b6_\b1 _\bf_\ba_\bs_\bt_\b__\br_\be_\bp_\bl_\by
Type: boolean
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.17 , page
90)'' variable is _\bs_\be_\bt.
- _\b7_\b._\b4_\b._\b6_\b1 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
+ _\b7_\b._\b4_\b._\b6_\b2 _\bf_\bc_\bc_\b__\ba_\bt_\bt_\ba_\bc_\bh
Type: boolean
+ The Mutt Next Generation E-Mail Client 101
+
Default: yes
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_\b2 _\bf_\bc_\bc_\b__\bc_\bl_\be_\ba_\br
+ _\b7_\b._\b4_\b._\b6_\b3 _\bf_\bc_\bc_\b__\bc_\bl_\be_\ba_\br
Type: boolean
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_\b3 _\bf_\bi_\bl_\be_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
+ _\b7_\b._\b4_\b._\b6_\b4 _\bf_\bi_\bl_\be_\b__\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
- The Mutt Next Generation E-Mail Client 100
-
Default: ''
This variable is a colon-separated list of character encoding schemes for text
Note: ``iso-2022-*'' must be put at the head of the value as shown above if
included.
- _\b7_\b._\b4_\b._\b6_\b4 _\bf_\bo_\bl_\bd_\be_\br
+ _\b7_\b._\b4_\b._\b6_\b5 _\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_\b5 _\bf_\bo_\bl_\bd_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b6_\b6 _\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.110 , page
+ taste. This string is similar to ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page
111)'', but has its own set of printf(3)-like sequences:
%C
current file number
+ The Mutt Next Generation E-Mail Client 102
+
%d
date/time folder was last modified
%N
N if folder has new mail, blank otherwise
- The Mutt Next Generation E-Mail Client 101
-
%s
size in bytes
%|X
pad to the end of the line with character 'X'
- _\b7_\b._\b4_\b._\b6_\b6 _\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b6_\b7 _\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 32)'' commands or detected by common mailing list headers.
+ 3.12 , page 33)'' 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._\b6_\b7 _\bf_\bo_\br_\bc_\be_\b__\bb_\bu_\bf_\bf_\by_\b__\bc_\bh_\be_\bc_\bk
+ The Mutt Next Generation E-Mail Client 103
+
+ _\b7_\b._\b4_\b._\b6_\b8 _\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.322 , page 164)'',
- ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.115 , page 114)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 7.4.99 , page 108)''.
+ Also see the following variables: ``_\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 7.4.323 , page 165)'',
+ ``_\b$_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.116 , page 114)'' and ``_\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
+ 7.4.100 , page 109)''.
- _\b7_\b._\b4_\b._\b6_\b8 _\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b6_\b9 _\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 102
-
- This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.242 , page 144)'',
+ This variable is similar to ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 7.4.243 , page 144)'',
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.231 , page 141)'' variable.
+ Also see the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 7.4.232 , page 142)'' variable.
- _\b7_\b._\b4_\b._\b6_\b9 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b7_\b0 _\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.137 , page 118)'' 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.138 , page 119)'' is used instead.
+ used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.138 , page 119)'' 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.139 , page 119)'' is used instead.
- _\b7_\b._\b4_\b._\b7_\b0 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\br_\by_\bp_\bt
+ _\b7_\b._\b4_\b._\b7_\b1 _\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.137 , page 118)'' 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.138 , page 119)'' 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.138 , page 119)'' 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.139 , page 119)'' is _\bu_\bn_\bs_\be_\bt. (PGP only)
- _\b7_\b._\b4_\b._\b7_\b1 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
+ _\b7_\b._\b4_\b._\b7_\b2 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\be_\bd_\bi_\bt
Type: quadoption
Default: yes
+ The Mutt Next Generation E-Mail Client 104
+
This quadoption controls whether or not the user is automatically placed in the
editor when forwarding messages. For those who always want to forward with no
modification, use a setting of _\bn_\bo.
- _\b7_\b._\b4_\b._\b7_\b2 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
Default: '[%a: %s]'
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.110 , page
+ the same format sequences as the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page
111)'' variable.
- _\b7_\b._\b4_\b._\b7_\b3 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
+ _\b7_\b._\b4_\b._\b7_\b4 _\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bq_\bu_\bo_\bt_\be
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 103
-
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.137 , page 118)'' 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.109 , page 111)''.
+ ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.138 , page 119)'' 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.110 , page 111)''.
- _\b7_\b._\b4_\b._\b7_\b4 _\bf_\br_\bo_\bm
+ _\b7_\b._\b4_\b._\b7_\b5 _\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.237 , page
- 143)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.331 , page
- 166)'' 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.238 , page
+ 143)''. This variable is ignored if ``_\b$_\bu_\bs_\be_\b__\bf_\br_\bo_\bm (section 7.4.332 , page
+ 167)'' 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_\b5 _\bg_\be_\bc_\bo_\bs_\b__\bm_\ba_\bs_\bk
+ _\b7_\b._\b4_\b._\b7_\b6 _\bg_\be_\bc_\bo_\bs_\b__\bm_\ba_\bs_\bk
Type: regular expression
do: set gecos_mask='.*'.
This can be useful if you see the following behavior: you address a e-mail to
+
+ The Mutt Next Generation E-Mail Client 105
+
user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
expression that will match the whole name so Mutt-ng will expand ``Franklin''
to ``Franklin, Steve''.
- _\b7_\b._\b4_\b._\b7_\b6 _\bh_\bd_\br_\bs
+ _\b7_\b._\b4_\b._\b7_\b7 _\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 34)'' command are not created. This variable _\bm_\bu_\bs_\bt be _\bu_\bn_\bs_\be_\bt before compos-
+ page 35)'' 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._\b7_\b7 _\bh_\be_\ba_\bd_\be_\br
+ _\b7_\b._\b4_\b._\b7_\b8 _\bh_\be_\ba_\bd_\be_\br
Type: boolean
- The Mutt Next Generation E-Mail Client 104
-
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.337 , page
+ are replying to into the edit buffer. The ``_\b$_\bw_\be_\be_\bd (section 7.4.338 , page
168)'' setting applies.
- _\b7_\b._\b4_\b._\b7_\b8 _\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be
+ _\b7_\b._\b4_\b._\b7_\b9 _\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.78 , page 104) variable points to the header
+ The _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.79 , page 104) variable points to the header
cache database.
- If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.78 , page 104) points to a directory it will
+ If _\b$_\bh_\be_\ba_\bd_\be_\br_\b__\bc_\ba_\bc_\bh_\be (section 7.4.79 , page 104) 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.78 , page 104) points to a file that file will be a single global header
+ 7.4.79 , page 104) 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._\b7_\b9 _\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_\b0 _\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_\b0 _\bh_\be_\bl_\bp
+ _\b7_\b._\b4_\b._\b8_\b1 _\bh_\be_\bl_\bp
+
+ The Mutt Next Generation E-Mail Client 106
Type: boolean
is primarily aimed at new users, neither of these should present a major prob-
lem.
- _\b7_\b._\b4_\b._\b8_\b1 _\bh_\bi_\bd_\bd_\be_\bn_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b8_\b2 _\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 105
-
- 7.4.89 , page 106)'' variable when adding the domain part to addresses. This
+ 7.4.90 , page 106)'' 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_\b2 _\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b8_\b3 _\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_\b3 _\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b8_\b4 _\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_\b4 _\bh_\bi_\bd_\be_\b__\bt_\bh_\br_\be_\ba_\bd_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b8_\b5 _\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_\b5 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
+ _\b7_\b._\b4_\b._\b8_\b6 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd
Type: boolean
+ The Mutt Next Generation E-Mail Client 107
+
Default: no
When _\bs_\be_\bt, Mutt-ng will not show the presence of messages that are hidden by
limiting, at the top of threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bm_\bi_\bs_\bs_\b-
- _\bi_\bn_\bg (section 7.4.83 , page 105) is set, this option will have no effect.
+ _\bi_\bn_\bg (section 7.4.84 , page 105) is set, this option will have no effect.
- _\b7_\b._\b4_\b._\b8_\b6 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b8_\b7 _\bh_\bi_\bd_\be_\b__\bt_\bo_\bp_\b__\bm_\bi_\bs_\bs_\bi_\bn_\bg
Type: boolean
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.82 ,
+ threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd (section 7.4.83 ,
page 105) is _\bs_\be_\bt, this option will have no effect.
- _\b7_\b._\b4_\b._\b8_\b7 _\bh_\bi_\bs_\bt_\bo_\br_\by
+ _\b7_\b._\b4_\b._\b8_\b8 _\bh_\bi_\bs_\bt_\bo_\br_\by
Type: number
- The Mutt Next Generation E-Mail Client 106
-
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._\b8_\b8 _\bh_\bo_\bn_\bo_\br_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b8_\b9 _\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._\b8_\b9 _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be
+ _\b7_\b._\b4_\b._\b9_\b0 _\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_\b0 _\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_\b1 _\bi_\bg_\bn_\bo_\br_\be_\b__\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by_\b__\bt_\bo
Type: boolean
Affects the behaviour of the _\br_\be_\bp_\bl_\by function when replying to messages from
mailing lists. When _\bs_\be_\bt, if the ``Reply-To:'' header field is set to the same
+
+ The Mutt Next Generation E-Mail Client 108
+
value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
header field was set by the mailing list to automate responses to the list, and
will ignore this field. To direct a response to the mailing list when this
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_\b1 _\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
+ _\b7_\b._\b4_\b._\b9_\b2 _\bi_\bm_\ba_\bp_\b__\ba_\bu_\bt_\bh_\be_\bn_\bt_\bi_\bc_\ba_\bt_\bo_\br_\bs
Type: string
capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
eter is case-insensitive.
- The Mutt Next Generation E-Mail Client 107
-
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_\b2 _\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_\b3 _\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 33)'' command.
+ also the ``_\bm_\ba_\bi_\bl_\bb_\bo_\bx_\be_\bs (section 3.14 , page 34)'' command.
- _\b7_\b._\b4_\b._\b9_\b3 _\bi_\bm_\ba_\bp_\b__\bd_\be_\bl_\bi_\bm_\b__\bc_\bh_\ba_\br_\bs
+ _\b7_\b._\b4_\b._\b9_\b4 _\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.64 , page 100) variable.
+ shortcut for your _\b$_\bf_\bo_\bl_\bd_\be_\br (section 7.4.65 , page 100) variable.
- _\b7_\b._\b4_\b._\b9_\b4 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b9_\b5 _\bi_\bm_\ba_\bp_\b__\bh_\be_\ba_\bd_\be_\br_\bs
Type: string
+ The Mutt Next Generation E-Mail Client 109
+
Default: ''
Availability: IMAP
N\bNo\bot\bte\be:\b: This is a space separated list.
- _\b7_\b._\b4_\b._\b9_\b5 _\bi_\bm_\ba_\bp_\b__\bh_\bo_\bm_\be_\b__\bn_\ba_\bm_\be_\bs_\bp_\ba_\bc_\be
+ _\b7_\b._\b4_\b._\b9_\b6 _\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 108
-
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_\b6 _\bi_\bm_\ba_\bp_\b__\bk_\be_\be_\bp_\ba_\bl_\bi_\bv_\be
+ _\b7_\b._\b4_\b._\b9_\b7 _\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._\b9_\b7 _\bi_\bm_\ba_\bp_\b__\bl_\bi_\bs_\bt_\b__\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
+ _\b7_\b._\b4_\b._\b9_\b8 _\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._\b9_\b8 _\bi_\bm_\ba_\bp_\b__\bl_\bo_\bg_\bi_\bn
+ The Mutt Next Generation E-Mail Client 110
+
+ _\b7_\b._\b4_\b._\b9_\b9 _\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.105 , page
+ This variable defaults to the value of ``_\b$_\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br (section 7.4.106 , page
110).''
- _\b7_\b._\b4_\b._\b9_\b9 _\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b1_\b0_\b0 _\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 109
-
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.115 ,
+ mail in IMAP folders. This is split from the ``_\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 7.4.116 ,
page 114)'' variable to generate less traffic and get more accurate information
for local folders.
- _\b7_\b._\b4_\b._\b1_\b0_\b0 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b1_\b0_\b1 _\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_\b1 _\bi_\bm_\ba_\bp_\b__\bp_\ba_\bs_\bs_\bi_\bv_\be
+ _\b7_\b._\b4_\b._\b1_\b0_\b2 _\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_\b2 _\bi_\bm_\ba_\bp_\b__\bp_\be_\be_\bk
+ _\b7_\b._\b4_\b._\b1_\b0_\b3 _\bi_\bm_\ba_\bp_\b__\bp_\be_\be_\bk
+
+ The Mutt Next Generation E-Mail Client 111
Type: boolean
closing an IMAP folder somewhat slower. This option exists to appease speed
freaks.
- _\b7_\b._\b4_\b._\b1_\b0_\b3 _\bi_\bm_\ba_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b0_\b4 _\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 110
-
Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
connection is lost.
- _\b7_\b._\b4_\b._\b1_\b0_\b4 _\bi_\bm_\ba_\bp_\b__\bs_\be_\br_\bv_\be_\br_\bn_\bo_\bi_\bs_\be
+ _\b7_\b._\b4_\b._\b1_\b0_\b5 _\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_\b5 _\bi_\bm_\ba_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b0_\b6 _\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_\b6 _\bi_\bm_\bp_\bl_\bi_\bc_\bi_\bt_\b__\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw
+ _\b7_\b._\b4_\b._\b1_\b0_\b7 _\bi_\bm_\bp_\bl_\bi_\bc_\bi_\bt_\b__\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw
Type: boolean
Default: no
If _\bs_\be_\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
+
+ The Mutt Next Generation E-Mail Client 112
+
set for _\be_\bv_\be_\br_\by MIME attachment it doesn't have an internal viewer defined for.
If such an entry is found, Mutt-ng will use the viewer defined in that entry to
convert the body part to text form.
- _\b7_\b._\b4_\b._\b1_\b0_\b7 _\bi_\bn_\bc_\bl_\bu_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b0_\b8 _\bi_\bn_\bc_\bl_\bu_\bd_\be
Type: quadoption
Controls whether or not a copy of the message(s) you are replying to is
included in your reply.
- _\b7_\b._\b4_\b._\b1_\b0_\b8 _\bi_\bn_\bc_\bl_\bu_\bd_\be_\b__\bo_\bn_\bl_\by_\bf_\bi_\br_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b0_\b9 _\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 111
-
Controls whether or not Mutt-ng includes only the first attachment of the mes-
sage you are replying.
- _\b7_\b._\b4_\b._\b1_\b0_\b9 _\bi_\bn_\bd_\be_\bn_\bt_\b__\bs_\bt_\br_\bi_\bn_\bg
+ _\b7_\b._\b4_\b._\b1_\b1_\b0 _\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_\b0 _\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b1_\b1 _\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%b
filename of the original message folder (think mailBox)
+ The Mutt Next Generation E-Mail Client 113
+
%B
the list to which the letter was sent, or else the folder name
(%b).
date and time of the message in the format specified by ``date_for-
mat'' converted to the local time zone
- The Mutt Next Generation E-Mail Client 112
-
%e
current message number in thread
%M
number of hidden messages if the thread is collapsed.
+ The Mutt Next Generation E-Mail Client 114
+
%N
message score
%t
`to:' field (recipients)
- The Mutt Next Generation E-Mail Client 113
-
%T
- the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.324 ,
+ the appropriate character from the _\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.325 ,
page 165) string
%u
zone, and ``fmt'' is expanded by the library function ``strftime'';
a leading bang disables locales
+ The Mutt Next Generation E-Mail Client 115
+
%(fmt)
the local date and time when the message was received. ``fmt'' is
expanded by the library function ``strftime''; a leading bang dis-
%|X
pad to the end of the line with character 'X'
- See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.324 , page 165)''.
-
- _\b7_\b._\b4_\b._\b1_\b1_\b1 _\bi_\bs_\bp_\be_\bl_\bl
+ See also: ``_\b$_\bt_\bo_\b__\bc_\bh_\ba_\br_\bs (section 7.4.325 , page 165)''.
- The Mutt Next Generation E-Mail Client 114
+ _\b7_\b._\b4_\b._\b1_\b1_\b2 _\bi_\bs_\bp_\be_\bl_\bl
Type: path
How to invoke ispell (GNU's spell-checking software).
- _\b7_\b._\b4_\b._\b1_\b1_\b2 _\bk_\be_\be_\bp_\b__\bf_\bl_\ba_\bg_\bg_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b1_\b3 _\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.125 , page 116)'' mailbox, or as a result of
- a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 33)'' command.
+ box to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.126 , page 117)'' mailbox, or as a result of
+ a ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34)'' command.
- _\b7_\b._\b4_\b._\b1_\b1_\b3 _\bl_\bi_\bs_\bt_\b__\br_\be_\bp_\bl_\by
+ _\b7_\b._\b4_\b._\b1_\b1_\b4 _\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_\b4 _\bl_\bo_\bc_\ba_\bl_\be
+ _\b7_\b._\b4_\b._\b1_\b1_\b5 _\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_\b5 _\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ The Mutt Next Generation E-Mail Client 116
+
+ _\b7_\b._\b4_\b._\b1_\b1_\b6 _\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
Type: number
mail.
N\bNo\bot\bte\be:\b: This does not apply to IMAP mailboxes, see _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section
- 7.4.99 , page 108).
+ 7.4.100 , page 109).
- _\b7_\b._\b4_\b._\b1_\b1_\b6 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bp_\ba_\bt_\bh
+ _\b7_\b._\b4_\b._\b1_\b1_\b7 _\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 115
-
bodies not directly supported by Mutt-ng.
- _\b7_\b._\b4_\b._\b1_\b1_\b7 _\bm_\ba_\bi_\bl_\bc_\ba_\bp_\b__\bs_\ba_\bn_\bi_\bt_\bi_\bz_\be
+ _\b7_\b._\b4_\b._\b1_\b1_\b8 _\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_\b1_\b8 _\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_\b1_\b9 _\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_\b1_\b9 _\bm_\ba_\bi_\bl_\bd_\bi_\br_\b__\bt_\br_\ba_\bs_\bh
+ _\b7_\b._\b4_\b._\b1_\b2_\b0 _\bm_\ba_\bi_\bl_\bd_\bi_\br_\b__\bt_\br_\ba_\bs_\bh
Type: boolean
If _\bs_\be_\bt, messages marked as deleted will be saved with the maildir (T)rashed
flag instead of physically deleted.
+ The Mutt Next Generation E-Mail Client 117
+
N\bNO\bOT\bTE\bE:\b: this only applies to maildir-style mailboxes. Setting it will have no
effect on other mailbox types.
It is similiar to the trash option.
- _\b7_\b._\b4_\b._\b1_\b2_\b0 _\bm_\ba_\br_\bk_\b__\bo_\bl_\bd
+ _\b7_\b._\b4_\b._\b1_\b2_\b1 _\bm_\ba_\br_\bk_\b__\bo_\bl_\bd
Type: boolean
up with an 'O' next to them in the ``index'' menu, indicating that they are
old.
- The Mutt Next Generation E-Mail Client 116
-
- _\b7_\b._\b4_\b._\b1_\b2_\b1 _\bm_\ba_\br_\bk_\be_\br_\bs
+ _\b7_\b._\b4_\b._\b1_\b2_\b2 _\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.264 , page 149)'' variable.
+ ``_\b$_\bs_\bm_\ba_\br_\bt_\b__\bw_\br_\ba_\bp (section 7.4.265 , page 150)'' variable.
- _\b7_\b._\b4_\b._\b1_\b2_\b2 _\bm_\ba_\bs_\bk
+ _\b7_\b._\b4_\b._\b1_\b2_\b3 _\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_\b3 _\bm_\ba_\bx_\b__\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\br_\be_\bc_\bi_\bp_\bs
+ _\b7_\b._\b4_\b._\b1_\b2_\b4 _\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_\b4 _\bm_\ba_\bx_\b__\bl_\bi_\bn_\be_\b__\bl_\be_\bn_\bg_\bt_\bh
+ _\b7_\b._\b4_\b._\b1_\b2_\b5 _\bm_\ba_\bx_\b__\bl_\bi_\bn_\be_\b__\bl_\be_\bn_\bg_\bt_\bh
Type: number
Default: 0
+ The Mutt Next Generation E-Mail Client 118
+
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.339 , page 168).
+ (section 7.4.340 , page 168).
- _\b7_\b._\b4_\b._\b1_\b2_\b5 _\bm_\bb_\bo_\bx
+ _\b7_\b._\b4_\b._\b1_\b2_\b6 _\bm_\bb_\bo_\bx
Type: path
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.298 , page 157)'' folder will be appended.
+ 7.4.299 , page 158)'' folder will be appended.
- _\b7_\b._\b4_\b._\b1_\b2_\b6 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
+ _\b7_\b._\b4_\b._\b1_\b2_\b7 _\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be
Type: folder magic
- The Mutt Next Generation E-Mail Client 117
-
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_\b2_\b7 _\bm_\be_\bn_\bu_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b2_\b8 _\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.168 , page
+ scrolling through menus. (Similar to ``_\b$_\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.169 , page
127)''.)
- _\b7_\b._\b4_\b._\b1_\b2_\b8 _\bm_\be_\bn_\bu_\b__\bm_\bo_\bv_\be_\b__\bo_\bf_\bf
+ _\b7_\b._\b4_\b._\b1_\b2_\b9 _\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_\b2_\b9 _\bm_\be_\bn_\bu_\b__\bs_\bc_\br_\bo_\bl_\bl
+ _\b7_\b._\b4_\b._\b1_\b3_\b0 _\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_\b0 _\bm_\be_\bs_\bs_\ba_\bg_\be_\b__\bf_\bo_\br_\bm_\ba_\bt
+ The Mutt Next Generation E-Mail Client 119
+
+ _\b7_\b._\b4_\b._\b1_\b3_\b1 _\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.110 , page 111)''.
+ section on ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111)''.
- _\b7_\b._\b4_\b._\b1_\b3_\b1 _\bm_\be_\bt_\ba_\b__\bk_\be_\by
+ _\b7_\b._\b4_\b._\b1_\b3_\b2 _\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 118
-
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_\b2 _\bm_\be_\bt_\bo_\bo
+ _\b7_\b._\b4_\b._\b1_\b3_\b3 _\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_\b3 _\bm_\bh_\b__\bp_\bu_\br_\bg_\be
+ _\b7_\b._\b4_\b._\b1_\b3_\b4 _\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_\b4 _\bm_\bh_\b__\bs_\be_\bq_\b__\bf_\bl_\ba_\bg_\bg_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b3_\b5 _\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_\b5 _\bm_\bh_\b__\bs_\be_\bq_\b__\br_\be_\bp_\bl_\bi_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b3_\b6 _\bm_\bh_\b__\bs_\be_\bq_\b__\br_\be_\bp_\bl_\bi_\be_\bd
Type: string
+ The Mutt Next Generation E-Mail Client 120
+
Default: 'replied'
The name of the MH sequence used to tag replied messages.
- _\b7_\b._\b4_\b._\b1_\b3_\b6 _\bm_\bh_\b__\bs_\be_\bq_\b__\bu_\bn_\bs_\be_\be_\bn
+ _\b7_\b._\b4_\b._\b1_\b3_\b7 _\bm_\bh_\b__\bs_\be_\bq_\b__\bu_\bn_\bs_\be_\be_\bn
Type: string
The name of the MH sequence used for unseen messages.
- _\b7_\b._\b4_\b._\b1_\b3_\b7 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd
+ _\b7_\b._\b4_\b._\b1_\b3_\b8 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd
Type: quadoption
Default: no
- The Mutt Next Generation E-Mail Client 119
-
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.69 , page 102)'' 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.138 , page 119)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.70 , page 102)'' 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.139 , page 119)''.
- _\b7_\b._\b4_\b._\b1_\b3_\b8 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b3_\b9 _\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.137 , page 118)'' is _\bs_\be_\bt. Other-
- wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.69 , page 102)'' is used instead.
+ a message while ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 7.4.138 , page 119)'' is _\bs_\be_\bt. Other-
+ wise ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 7.4.70 , page 102)'' is used instead.
- _\b7_\b._\b4_\b._\b1_\b3_\b9 _\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\br_\be_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b4_\b0 _\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_\b0 _\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b4_\b1 _\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
Default: '%4n %c %-16s %a'
+ The Mutt Next Generation E-Mail Client 121
+
Availability: Mixmaster
This variable describes the format of a remailer line on the mixmaster chain
%a
The remailer's e-mail address.
- The Mutt Next Generation E-Mail Client 120
-
- _\b7_\b._\b4_\b._\b1_\b4_\b1 _\bm_\bi_\bx_\bm_\ba_\bs_\bt_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b4_\b2 _\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_\b2 _\bm_\bo_\bv_\be
+ _\b7_\b._\b4_\b._\b1_\b4_\b3 _\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.125 , page 116)'' mailbox, or as a result of a
- ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 33)'' command.
+ to your ``_\b$_\bm_\bb_\bo_\bx (section 7.4.126 , page 117)'' mailbox, or as a result of a
+ ``_\bm_\bb_\bo_\bx_\b-_\bh_\bo_\bo_\bk (section 3.13 , page 34)'' command.
- _\b7_\b._\b4_\b._\b1_\b4_\b3 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
+ _\b7_\b._\b4_\b._\b1_\b4_\b4 _\bm_\bs_\bg_\bi_\bd_\b__\bf_\bo_\br_\bm_\ba_\bt
Type: string
%d
the current day of month
+ The Mutt Next Generation E-Mail Client 122
+
%h
the current hour
the current Message-ID prefix (a character rotating with every Mes-
sage-ID being generated)
- The Mutt Next Generation E-Mail Client 121
-
%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_\b4 _\bn_\ba_\br_\br_\bo_\bw_\b__\bt_\br_\be_\be
+ _\b7_\b._\b4_\b._\b1_\b4_\b5 _\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_\b5 _\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_\b6 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bf_\bo_\bl_\bl_\bo_\bw_\bu_\bp_\b__\bt_\bo
+
+ The Mutt Next Generation E-Mail Client 123
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_\b6 _\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_\b4_\b7 _\bn_\bn_\bt_\bp_\b__\ba_\bs_\bk_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
Type: boolean
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 122
-
- _\b7_\b._\b4_\b._\b1_\b4_\b7 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br
+ _\b7_\b._\b4_\b._\b1_\b4_\b8 _\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_\b4_\b8 _\bn_\bn_\bt_\bp_\b__\bc_\ba_\bt_\bc_\bh_\bu_\bp
+ _\b7_\b._\b4_\b._\b1_\b4_\b9 _\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_\b4_\b9 _\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b5_\b0 _\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
Type: number
Availability: NNTP
+ The Mutt Next Generation E-Mail Client 124
+
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.147 , page 121)) and how
+ caching is enabled, see _\b$_\bn_\bn_\bt_\bp_\b__\bc_\ba_\bc_\bh_\be_\b__\bd_\bi_\br (section 7.4.148 , page 122)) 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.149 ,
+ If there're more articles than defined with _\b$_\bn_\bn_\bt_\bp_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt (section 7.4.150 ,
page 122), all older ones will be removed/not shown in the index.
- _\b7_\b._\b4_\b._\b1_\b5_\b0 _\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_\b1 _\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
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 123
-
- _\b7_\b._\b4_\b._\b1_\b5_\b1 _\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_\b2 _\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.110 ,
+ personal taste. This string is similar to ``_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 ,
page 111)'', but has its own set of printf(3)-like sequences:
%C current newsgroup number
%>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_\b2 _\bn_\bn_\bt_\bp_\b__\bh_\bo_\bs_\bt
+ _\b7_\b._\b4_\b._\b1_\b5_\b3 _\bn_\bn_\bt_\bp_\b__\bh_\bo_\bs_\bt
Type: string
This variable specifies the name (or address) of the NNTP server to be used.
It defaults to the value specified via the environment variable $NNTPSERVER or
+
+ The Mutt Next Generation E-Mail Client 125
+
contained in the file /etc/nntpserver.
You can also specify a username and an alternative port for each newsserver,
security risk since the superuser of your machine may read it regardless of the
file's permissions.
- _\b7_\b._\b4_\b._\b1_\b5_\b3 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
+ _\b7_\b._\b4_\b._\b1_\b5_\b4 _\bn_\bn_\bt_\bp_\b__\bi_\bn_\be_\bw_\bs
Type: path
Availability: NNTP
- The Mutt Next Generation E-Mail Client 124
-
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_\b4 _\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_\b5 _\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_\b5 _\bn_\bn_\bt_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk
+ _\b7_\b._\b4_\b._\b1_\b5_\b6 _\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_\b6 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b5_\b7 _\bn_\bn_\bt_\bp_\b__\bm_\bi_\bm_\be_\b__\bs_\bu_\bb_\bj_\be_\bc_\bt
+
+ The Mutt Next Generation E-Mail Client 126
Type: boolean
N\bNo\bot\bte\be:\b: Only change this setting if you know what you are doing.
- _\b7_\b._\b4_\b._\b1_\b5_\b7 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
+ _\b7_\b._\b4_\b._\b1_\b5_\b8 _\bn_\bn_\bt_\bp_\b__\bn_\be_\bw_\bs_\br_\bc
Type: path
Availability: NNTP
- The Mutt Next Generation E-Mail Client 125
-
This file contains information about subscribed newsgroup and articles read so
far.
%s newsserver name
- _\b7_\b._\b4_\b._\b1_\b5_\b8 _\bn_\bn_\bt_\bp_\b__\bp_\ba_\bs_\bs
+ _\b7_\b._\b4_\b._\b1_\b5_\b9 _\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_\b5_\b9 _\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_\b0 _\bn_\bn_\bt_\bp_\b__\bp_\bo_\bs_\bt_\b__\bm_\bo_\bd_\be_\br_\ba_\bt_\be_\bd
Type: quadoption
sions to post (e.g. moderated).
N\bNo\bot\bte\be:\b: if the newsserver does not support posting to that newsgroup or a group
+
+ The Mutt Next Generation E-Mail Client 127
+
is totally read-only, that posting will not have any effect.
- _\b7_\b._\b4_\b._\b1_\b6_\b0 _\bn_\bn_\bt_\bp_\b__\br_\be_\bc_\bo_\bn_\bn_\be_\bc_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b1 _\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_\b1 _\bn_\bn_\bt_\bp_\b__\bs_\ba_\bv_\be_\b__\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd
+ _\b7_\b._\b4_\b._\b1_\b6_\b2 _\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 126
-
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_\b2 _\bn_\bn_\bt_\bp_\b__\bs_\bh_\bo_\bw_\b__\bn_\be_\bw_\b__\bn_\be_\bw_\bs
+ _\b7_\b._\b4_\b._\b1_\b6_\b3 _\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_\b3 _\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_\b4 _\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_\b4 _\bn_\bn_\bt_\bp_\b__\bu_\bs_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b6_\b5 _\bn_\bn_\bt_\bp_\b__\bu_\bs_\be_\br
Type: string
Default: ''
+ The Mutt Next Generation E-Mail Client 128
+
Availability: NNTP
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_\b5 _\bn_\bn_\bt_\bp_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
+ _\b7_\b._\b4_\b._\b1_\b6_\b6 _\bn_\bn_\bt_\bp_\b__\bx_\b__\bc_\bo_\bm_\bm_\be_\bn_\bt_\b__\bt_\bo
Type: boolean
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_\b6 _\bo_\bp_\be_\br_\ba_\bt_\bi_\bn_\bg_\b__\bs_\by_\bs_\bt_\be_\bm
+ _\b7_\b._\b4_\b._\b1_\b6_\b7 _\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 127
-
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_\b6_\b7 _\bp_\ba_\bg_\be_\br
+ _\b7_\b._\b4_\b._\b1_\b6_\b8 _\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_\b6_\b8 _\bp_\ba_\bg_\be_\br_\b__\bc_\bo_\bn_\bt_\be_\bx_\bt
+ _\b7_\b._\b4_\b._\b1_\b6_\b9 _\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_\b6_\b9 _\bp_\ba_\bg_\be_\br_\b__\bf_\bo_\br_\bm_\ba_\bt
+ The Mutt Next Generation E-Mail Client 129
+
+ _\b7_\b._\b4_\b._\b1_\b7_\b0 _\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.110 , page 111)''
+ sequences are listed in the ``_\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 7.4.111 , page 111)''
section.
- _\b7_\b._\b4_\b._\b1_\b7_\b0 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
+ _\b7_\b._\b4_\b._\b1_\b7_\b1 _\bp_\ba_\bg_\be_\br_\b__\bi_\bn_\bd_\be_\bx_\b__\bl_\bi_\bn_\be_\bs
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 128
-
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_\b1 _\bp_\ba_\bg_\be_\br_\b__\bs_\bt_\bo_\bp
+ _\b7_\b._\b4_\b._\b1_\b7_\b2 _\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_\b2 _\bp_\bg_\bp_\b__\ba_\bu_\bt_\bo_\b__\bd_\be_\bc_\bo_\bd_\be
+ _\b7_\b._\b4_\b._\b1_\b7_\b3 _\bp_\bg_\b<
projects / apps / madmutt.git / commitdiff