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-
N\bNo\bot\bte\be:\b: Collapsing a thread displays only the first message in the thread and
hides the others. This is useful when threads contain so many messages that you
can only see a handful of threads on the screen. See %M in _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (sec-
- tion 6.4.110 , page 105). For example, you could use "%?M?(#%03M)&(%4l)?" in
- _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 105) to optionally display the number of
+ tion 6.4.110 , page 106). For example, you could use "%?M?(#%03M)&(%4l)?" in
+ _\b$_\bi_\bn_\bd_\be_\bx_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.110 , page 106) to optionally display the number of
- the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 80) variable for
- future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 80) does not
+ the file specified by the _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 81) variable for
+ future use. N\bNo\bot\bte\be:\b: Specifying an _\b$_\ba_\bl_\bi_\ba_\bs_\b__\bf_\bi_\bl_\be (section 6.4.3 , page 81) does not
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
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
- it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.200 , page 129), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
- (section 6.4.202 , page 129), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 6.4.201 , page 129) and
- _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.334 , page 161) control the exact behavior of this
+ it. The variables _\b$_\bp_\bi_\bp_\be_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.200 , page 130), _\b$_\bp_\bi_\bp_\be_\b__\bs_\bp_\bl_\bi_\bt
+ (section 6.4.202 , page 130), _\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp (section 6.4.201 , page 130) and
+ _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 162) control the exact behavior of this
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
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
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)
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)
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
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
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
Note that different remailers do have different capabilities, indicated in the
%c entry of the remailer menu lines (see _\b$_\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.139 ,
Note that different remailers do have different capabilities, indicated in the
%c entry of the remailer menu lines (see _\b$_\bm_\bi_\bx_\b__\be_\bn_\bt_\br_\by_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.139 ,
capital ``M'': This means that the remailer in question cannot be used as the
final element of a chain, but will only forward messages to other mixmaster
remailers. For details on the other capabilities, please have a look at the
capital ``M'': This means that the remailer in question cannot be used as the
final element of a chain, but will only forward messages to other mixmaster
remailers. For details on the other capabilities, please have a look at the
At times it is desirable to delay sending a message that you have already begun
to compose. When the _\bp_\bo_\bs_\bt_\bp_\bo_\bn_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be function is used in the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu,
the body of your message and attachments are stored in the mailbox specified by
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
have multiple alias files, or you can have all aliases defined in your muttrc.
On the other hand, the _\bc_\br_\be_\ba_\bt_\be_\b-_\ba_\bl_\bi_\ba_\bs (section 2.5.4 , page 11) function can use
have multiple alias files, or you can have all aliases defined in your muttrc.
On the other hand, the _\bc_\br_\be_\ba_\bt_\be_\b-_\ba_\bl_\bi_\ba_\bs (section 2.5.4 , page 11) function can use
variable (which is ~/.muttrc by default). This file is not special either, in
the sense that Mutt-ng will happily append aliases to any file, but in order
for the new aliases to take effect you need to explicitly _\bs_\bo_\bu_\br_\bc_\be (section
variable (which is ~/.muttrc by default). This file is not special either, in
the sense that Mutt-ng will happily append aliases to any file, but in order
for the new aliases to take effect you need to explicitly _\bs_\bo_\bu_\br_\bc_\be (section
To use aliases, you merely use the alias at any place in mutt where mutt
prompts for addresses, such as the _\bT_\bo_\b: or _\bC_\bc_\b: prompt. You can also enter
aliases in your editor at the appropriate headers if you have the _\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs
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
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
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
- N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.296 , page
- 151) at the beginning of the pattern, you must place it inside of double or
+ N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page
+ 152) at the beginning of the pattern, you must place it inside of double or
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
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
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
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
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-
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-
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-
N\bNo\bot\bte\be:\b: the filenames in the mailboxes command are resolved when the command is
executed, so if these names contain _\bs_\bh_\bo_\br_\bt_\bc_\bu_\bt _\bc_\bh_\ba_\br_\ba_\bc_\bt_\be_\br_\bs (section 4.9 , page
56) (such as ``='' and ``!''), any variable definition that affect these char-
- acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 94) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
- 6.4.296 , page 151)) should be executed before the mailboxes command.
+ acters (like _\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 , page 95) and _\b$_\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section
+ 6.4.297 , page 152)) should be executed before the mailboxes command.
- _\bt_\bi_\bo_\bn (section 6.4.15 , page 84), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 143) and
- _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 108) variables in order to change the language
+ _\bt_\bi_\bo_\bn (section 6.4.15 , page 85), _\b$_\bs_\bi_\bg_\bn_\ba_\bt_\bu_\br_\be (section 6.4.259 , page 143) and
+ _\b$_\bl_\bo_\bc_\ba_\bl_\be (section 6.4.114 , page 109) variables in order to change the language
- tion 6.4.244 , page 139), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 6.4.245 , page 139),
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 6.4.243 , page 139) and. By default,
- _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 6.4.245 , page 139) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
- (section 6.4.243 , page 139) are set to -1, which means that in the default
+ tion 6.4.244 , page 140), _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 6.4.245 , page 140),
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be (section 6.4.243 , page 140) and. By default,
+ _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\br_\be_\ba_\bd (section 6.4.245 , page 140) and _\b$_\bs_\bc_\bo_\br_\be_\b__\bt_\bh_\br_\be_\bs_\bh_\bo_\bl_\bd_\b__\bd_\be_\bl_\be_\bt_\be
+ (section 6.4.243 , page 140) are set to -1, which means that in the default
ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
operator is used, the n\bne\bex\bxt\bt operation will be applied to all tagged messages if
that operation can be used in that manner. If the _\b$_\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg (section 6.4.16 ,
ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
operator is used, the n\bne\bex\bxt\bt operation will be applied to all tagged messages if
that operation can be used in that manner. If the _\b$_\ba_\bu_\bt_\bo_\b__\bt_\ba_\bg (section 6.4.16 ,
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,
automatically, without requiring the ``tag-prefix''.
In _\bm_\ba_\bc_\br_\bo_\bs (section 3.7 , page 27) or _\bp_\bu_\bs_\bh (section 3.23 , page 37) commands,
searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the
other hooks, in which case Mutt-ng will translate your pattern into the full
language, using the translation specified by the _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section
searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the
other hooks, in which case Mutt-ng will translate your pattern into the full
language, using the translation specified by the _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section
- 6.4.45 , page 90) variable. The pattern is translated at the time the hook is
- declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.4.45 , page 90) that is in
+ 6.4.45 , page 91) variable. The pattern is translated at the time the hook is
+ declared, so the value of _\b$_\bd_\be_\bf_\ba_\bu_\bl_\bt_\b__\bh_\bo_\bo_\bk (section 6.4.45 , page 91) that is in
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
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
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-
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-
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
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
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
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
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
_\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
_\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
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.
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.
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
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
- To support this, there are two variables. _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 6.4.51 , page
- 91) is used to request receipts for different results (such as failed message,
- message delivered, etc.). _\b$_\bd_\bs_\bn_\b__\br_\be_\bt_\bu_\br_\bn (section 6.4.52 , page 92) requests how
- much of your message should be returned with the receipt (headers or full mes-
- sage). Refer to the man page on sendmail for more details on DSN.
+ Users can make use of it in one of the following two ways:
- If Mutt-ng was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script with
+ +\bo The SMTP support via libESMTP supports it, too.
+
+ To support this, there are two variables:
+
+ +\bo _\b$_\bd_\bs_\bn_\b__\bn_\bo_\bt_\bi_\bf_\by (section 6.4.51 , page 92) is used to request receipts for
+ different results (such as failed message, message delivered, etc.).
- It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.206 , page 130), fetch all your
- new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.296 , page 151).
+ It allows to connect to _\bp_\bo_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.206 , page 131), fetch all your
+ new mail and place it in the local _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be (section 6.4.297 , page 152).
INBOX is the special name for your spool mailbox on the IMAP server. If you
want to access another mail folder at the IMAP server, you should use
imap://imapserver/path/to/folder where path/to/folder is the path of the folder
INBOX is the special name for your spool mailbox on the IMAP server. If you
want to access another mail folder at the IMAP server, you should use
imap://imapserver/path/to/folder where path/to/folder is the path of the folder
- the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This
-
- The Mutt Next Generation E-Mail Client 61
-
- naturally requires that the server supports SSL encrypted connections. To
- access a folder with IMAP/SSL, you should use imaps://[user-
+ the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be encrypted. This natu-
+ rally requires that the server supports SSL encrypted connections. To access a
+ folder with IMAP/SSL, you should use imaps://[user-
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
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
- want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.99 , page 103) and
- _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.320 , page 159) variables.
+ want to carefully tune the _\b$_\bi_\bm_\ba_\bp_\b__\bm_\ba_\bi_\bl_\b__\bc_\bh_\be_\bc_\bk (section 6.4.99 , page 104) and
+ _\b$_\bt_\bi_\bm_\be_\bo_\bu_\bt (section 6.4.321 , page 160) variables.
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
available on your host and the server. Using some of these methods (including
DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
available on your host and the server. Using some of these methods (including
DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
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}).
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}).
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).
of IMAP authentication methods to try, in the order you wish to try them.
If specified, this overrides mutt's default (attempt everything, in the
order listed above).
Especially for Usenet, people often ask for advanced filtering and scoring
functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
Especially for Usenet, people often ask for advanced filtering and scoring
functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
- muttng -v contains +USE_LIBESMTP, this will be or is the case already.
+ muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
+ support includes support for Delivery Status Notification (see _\bD_\be_\bl_\bi_\bv_\be_\br_\by _\bS_\bt_\ba_\bt_\bu_\bs
+ _\bN_\bo_\bt_\bi_\bf_\bi_\bc_\ba_\bt_\bi_\bo_\bn (section 4.12 , page 58) section) as well as handling the 8BIT-
+ MIME flag controlled via _\b$_\bu_\bs_\be_\b__\b8_\bb_\bi_\bt_\bm_\bi_\bm_\be (section 6.4.328 , page 161).
- Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 6.4.289 ,
- page 149) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.286 , page 148) variables.
+ The Mutt Next Generation E-Mail Client 64
+
+ Authentication mechanisms are available via the _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section 6.4.290 ,
+ page 150) and _\b$_\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs (section 6.4.287 , page 149) variables.
``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.
``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.
_\b4_\b._\b1_\b7 _\bM_\ba_\bn_\ba_\bg_\bi_\bn_\bg _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bI_\bM_\bA_\bP_\b/_\bP_\bO_\bP_\b/_\bN_\bN_\bT_\bP _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\bs _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
If you happen to have accounts on multiple IMAP and/or POP servers, you may
find managing all the authentication settings inconvenient and error-prone.
_\b4_\b._\b1_\b7 _\bM_\ba_\bn_\ba_\bg_\bi_\bn_\bg _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\be _\bI_\bM_\bA_\bP_\b/_\bP_\bO_\bP_\b/_\bN_\bN_\bT_\bP _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\bs _\b(_\bO_\bP_\bT_\bI_\bO_\bN_\bA_\bL_\b)
If you happen to have accounts on multiple IMAP and/or POP servers, you may
find managing all the authentication settings inconvenient and error-prone.
The account-hook command may help. This hook works like folder-hook but is
invoked whenever you access a remote mailbox (including inside the folder
browser), not just when you open the mailbox.
The account-hook command may help. This hook works like folder-hook but is
invoked whenever you access a remote mailbox (including inside the folder
browser), not just when you open the mailbox.
You do not have to specify all of the commands. If you omit _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (sec-
tion 4.19.3 , page 65), the folder will be open and closed again each time you
will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65) (or give
You do not have to specify all of the commands. If you omit _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (sec-
tion 4.19.3 , page 65), the folder will be open and closed again each time you
will add to it. If you omit _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65) (or give
compressed. This is important because it allows the use of programs that do not
have well defined extensions. Just use '.' as a regexp. But this may be sur-
prising if your compressing script produces empty files. In this situation,
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,
When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65) is used, the folder is not opened,
which saves time, but this means that we can not find out what the folder type
When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65) is used, the folder is not opened,
which saves time, but this means that we can not find out what the folder type
the message to a text representation. Mutt-ng internally supports a number of
MIME types, including text/plain, text/enriched, message/rfc822, and mes-
sage/news. In addition, the export controlled version of Mutt-ng recognizes a
the message to a text representation. Mutt-ng internally supports a number of
MIME types, including text/plain, text/enriched, message/rfc822, and mes-
sage/news. In addition, the export controlled version of Mutt-ng recognizes a
a message. From the attachment menu, you can save, print, pipe, delete, and
view attachments. You can apply these operations to a group of attachments at
once, by tagging the attachments and by using the ``tag-prefix'' operator. You
a message. From the attachment menu, you can save, print, pipe, delete, and
view attachments. You can apply these operations to a group of attachments at
once, by tagging the attachments and by using the ``tag-prefix'' operator. You
or canceling) the message. It can be toggled with the toggle-unlink command
(default: u). The next field is the MIME content-type, and can be changed with
the edit-type command (default: ^T). The next field is the encoding for the
or canceling) the message. It can be toggled with the toggle-unlink command
(default: u). The next field is the MIME content-type, and can be changed with
the edit-type command (default: ^T). The next field is the encoding for the
attachment, which allows a binary message to be encoded for transmission on
7bit links. It can be changed with the edit-encoding command (default: ^E).
The next field is the size of the attachment, rounded to kilobytes or
attachment, which allows a binary message to be encoded for transmission on
7bit links. It can be changed with the edit-encoding command (default: ^E).
The next field is the size of the attachment, rounded to kilobytes or
The content type is specified in the MIME standard type/subtype method. For
example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
mat includes two formats for wildcards, one using the special '*' subtype, the
The content type is specified in the MIME standard type/subtype method. For
example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
mat includes two formats for wildcards, one using the special '*' subtype, the
In this case, lynx does not support viewing a file from stdin, so you must use
the %s syntax. N\bNo\bot\bte\be:\b: _\bS_\bo_\bm_\be _\bo_\bl_\bd_\be_\br _\bv_\be_\br_\bs_\bi_\bo_\bn_\bs _\bo_\bf _\bl_\by_\bn_\bx _\bc_\bo_\bn_\bt_\ba_\bi_\bn _\ba _\bb_\bu_\bg _\bw_\bh_\be_\br_\be _\bt_\bh_\be_\by _\bw_\bi_\bl_\bl
_\bc_\bh_\be_\bc_\bk _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be _\bf_\bo_\br _\ba _\bv_\bi_\be_\bw_\be_\br _\bf_\bo_\br _\bt_\be_\bx_\bt_\b/_\bh_\bt_\bm_\bl_\b. _\bT_\bh_\be_\by _\bw_\bi_\bl_\bl _\bf_\bi_\bn_\bd _\bt_\bh_\be _\bl_\bi_\bn_\be
In this case, lynx does not support viewing a file from stdin, so you must use
the %s syntax. N\bNo\bot\bte\be:\b: _\bS_\bo_\bm_\be _\bo_\bl_\bd_\be_\br _\bv_\be_\br_\bs_\bi_\bo_\bn_\bs _\bo_\bf _\bl_\by_\bn_\bx _\bc_\bo_\bn_\bt_\ba_\bi_\bn _\ba _\bb_\bu_\bg _\bw_\bh_\be_\br_\be _\bt_\bh_\be_\by _\bw_\bi_\bl_\bl
_\bc_\bh_\be_\bc_\bk _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be _\bf_\bo_\br _\ba _\bv_\bi_\be_\bw_\be_\br _\bf_\bo_\br _\bt_\be_\bx_\bt_\b/_\bh_\bt_\bm_\bl_\b. _\bT_\bh_\be_\by _\bw_\bi_\bl_\bl _\bf_\bi_\bn_\bd _\bt_\bh_\be _\bl_\bi_\bn_\be
_\b5_\b._\b3_\b._\b2 _\bS_\be_\bc_\bu_\br_\be _\bu_\bs_\be _\bo_\bf _\bm_\ba_\bi_\bl_\bc_\ba_\bp
The interpretation of shell meta-characters embedded in MIME parameters can
lead to security problems in general. Mutt-ng tries to quote parameters in
expansion of %s syntaxes properly, and avoids risky characters by substituting
_\b5_\b._\b3_\b._\b2 _\bS_\be_\bc_\bu_\br_\be _\bu_\bs_\be _\bo_\bf _\bm_\ba_\bi_\bl_\bc_\ba_\bp
The interpretation of shell meta-characters embedded in MIME parameters can
lead to security problems in general. Mutt-ng tries to quote parameters in
expansion of %s syntaxes properly, and avoids risky characters by substituting
In addition to the required content-type and view command fields, you can add
semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
nizes the following optional fields:
In addition to the required content-type and view command fields, you can add
semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
nizes the following optional fields:
- Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw
-
- The Mutt Next Generation E-Mail Client 72
-
- (section 5.4 , page 74), in order to decide whether it should
- honor the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.334 , page 161)
- variable or not. When an attachment is viewed using an interactive
- program, and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl
- flag, Mutt-ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.334 , page 161) and
- the exit status of the program to decide if it will ask you to
- press a key after the external program has exited. In all other
- situations it will not prompt you for a key.
+ Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
+ tion 5.4 , page 74), in order to decide whether it should honor
+ the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 162) variable
+ or not. When an attachment is viewed using an interactive program,
+ and the corresponding mailcap entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt-
+ ng will use _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.335 , page 162) and the exit
+ status of the program to decide if it will ask you to press a key
+ after the external program has exited. In all other situations it
+ will not prompt you for a key.
In this example, Mutt-ng will run the program RunningX which will
return 0 if the X Window manager is running, and non-zero if it
isn't. If RunningX returns 0, then Mutt-ng will call netscape to
In this example, Mutt-ng will run the program RunningX which will
return 0 if the X Window manager is running, and non-zero if it
isn't. If RunningX returns 0, then Mutt-ng will call netscape to
# 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
# 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
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
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
This command will send a message to ``professor@bigschool.edu'' with a subject
of ``data set for run #2''. In the body of the message will be the contents of
the file ``~/run2.dat''.
_\b6_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
This command will send a message to ``professor@bigschool.edu'' with a subject
of ``data set for run #2''. In the body of the message will be the contents of
the file ``~/run2.dat''.
_\b6_\b._\b2 _\bP_\ba_\bt_\bt_\be_\br_\bn_\bs
Where EXPR, USER, ID, and SUBJECT are _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs (section 4.1 , page
44). Special attention has to be made when using regular expressions inside of
patterns. Specifically, Mutt-ng's parser for these patterns will strip one
Where EXPR, USER, ID, and SUBJECT are _\br_\be_\bg_\bu_\bl_\ba_\br _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn_\bs (section 4.1 , page
44). Special attention has to be made when using regular expressions inside of
patterns. Specifically, Mutt-ng's parser for these patterns will strip one
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
_\b6_\b._\b3 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bC_\bo_\bm_\bm_\ba_\bn_\bd_\bs
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
_\b6_\b._\b3 _\bC_\bo_\bn_\bf_\bi_\bg_\bu_\br_\ba_\bt_\bi_\bo_\bn _\bC_\bo_\bm_\bm_\ba_\bn_\bd_\bs
+\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 35) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 35) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+\bo _\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 35) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+\bo _\bu_\bn_\bh_\bd_\br_\b__\bo_\br_\bd_\be_\br (section 3.16 , page 35) _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+\bo _\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 _\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 _\bu_\bn_\bs_\be_\bt (section 3.27 , page 41) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.28 , page 42) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+\bo _\bu_\bn_\bs_\be_\bt (section 3.27 , page 41) _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+\bo _\bs_\bo_\bu_\br_\bc_\be (section 3.28 , page 42) _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+\bo _\bu_\bn_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be (section 3.12 , page 32) _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
The separator to add between attachments when operating (saving, printing, pip-
ing, etc) on a list of tagged attachments.
The separator to add between attachments when operating (saving, printing, pip-
ing, etc) on a list of tagged attachments.
If this variable is _\bu_\bn_\bs_\be_\bt, when operating (saving, printing, piping, etc) on a
list of tagged attachments, Mutt-ng will concatenate the attachments and will
operate on them as a single attachment. The ``_\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp (section 6.4.13 ,
If this variable is _\bu_\bn_\bs_\be_\bt, when operating (saving, printing, piping, etc) on a
list of tagged attachments, Mutt-ng will concatenate the attachments and will
operate on them as a single attachment. The ``_\b$_\ba_\bt_\bt_\ba_\bc_\bh_\b__\bs_\be_\bp (section 6.4.13 ,
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.
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.
- 136)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 138)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
- 6.4.68 , page 96)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 35)''.
+ 136)'', ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 139)'', ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section
+ 6.4.68 , page 97)'' and ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page 35)''.
- 6.4.34 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 89)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 6.4.39 , page 89)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
+ 6.4.34 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 90)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+ 6.4.39 , page 90)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
- 6.4.34 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 89)'',
- ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 88)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
- 6.4.39 , page 89)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
+ 6.4.34 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\be_\bn_\bc_\br_\by_\bp_\bt (section 6.4.38 , page 90)'',
+ ``_\b$_\bc_\br_\by_\bp_\bt_\b__\ba_\bu_\bt_\bo_\bs_\bi_\bg_\bn (section 6.4.36 , page 89)'', ``_\b$_\bc_\br_\by_\bp_\bt_\b__\br_\be_\bp_\bl_\by_\bs_\bi_\bg_\bn (section
+
+ The Mutt Next Generation E-Mail Client 91
+
+ 6.4.39 , page 90)'' and ``_\b$_\bs_\bm_\bi_\bm_\be_\b__\bi_\bs_\b__\bd_\be_\bf_\ba_\bu_\bl_\bt (section 6.4.277 , page 147)''.
If _\bs_\be_\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
S/MIME output, so spoofing such lines is more difficult. If you are using col-
ors to mark these lines, and rely on these, you may _\bu_\bn_\bs_\be_\bt this setting.
If _\bs_\be_\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
S/MIME output, so spoofing such lines is more difficult. If you are using col-
ors to mark these lines, and rely on these, you may _\bu_\bn_\bs_\be_\bt this setting.
hook is declared. The default value matches if the message is either from a
user matching the regular expression given, or if it is from you (if the from
address matches ``alternates'') and is to or cc'ed to a user matching the given
hook is declared. The default value matches if the message is either from a
user matching the regular expression given, or if it is from you (if the from
address matches ``alternates'') and is to or cc'ed to a user matching the given
When _\bs_\be_\bt, specifies a command used to filter messages. When a message is
viewed it is passed as standard input to _\b$_\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br (section 6.4.49 ,
When _\bs_\be_\bt, specifies a command used to filter messages. When a message is
viewed it is passed as standard input to _\b$_\bd_\bi_\bs_\bp_\bl_\ba_\by_\b__\bf_\bi_\bl_\bt_\be_\br (section 6.4.49 ,
- consists of a comma separated list (no spaces!) of one or more of the follow-
- ing: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notification on
- transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs, to be
- notified of successful transmission.
+ consists of a comma separated list (no spaces!) of one or more of the
+
+ The Mutt Next Generation E-Mail Client 94
+
+ following: _\bn_\be_\bv_\be_\br, to never request notification, _\bf_\ba_\bi_\bl_\bu_\br_\be, to request notifica-
+ tion on transmission failure, _\bd_\be_\bl_\ba_\by, to be notified of message delays, _\bs_\bu_\bc_\bc_\be_\bs_\bs,
+ to be notified of successful transmission.
Controls the decoding of complex MIME messages into text/plain when forwarding
a message. The message header is also RFC2047 decoded. This variable is only
used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 113)'' is _\bu_\bn_\bs_\be_\bt, otherwise
Controls the decoding of complex MIME messages into text/plain when forwarding
a message. The message header is also RFC2047 decoded. This variable is only
used, if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 113)'' is _\bu_\bn_\bs_\be_\bt, otherwise
Controls the handling of encrypted messages when forwarding a message. When
_\bs_\be_\bt, the outer layer of encryption is stripped off. This variable is only used
if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 113)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
Controls the handling of encrypted messages when forwarding a message. When
_\bs_\be_\bt, the outer layer of encryption is stripped off. This variable is only used
if ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd (section 6.4.136 , page 113)'' is _\bs_\be_\bt and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
This quadoption controls whether or not the user is automatically placed in the
editor when forwarding messages. For those who always want to forward with no
modification, use a setting of _\bn_\bo.
This 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.
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''
user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
expression that will match the whole name so Mutt-ng will expand ``Franklin''
Default: no
When _\bs_\be_\bt, 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-
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-
When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages at the top of
threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd (section 6.4.82 ,
When _\bs_\be_\bt, Mutt-ng will not show the presence of missing messages at the top of
threads in the thread tree. Note that when _\b$_\bh_\bi_\bd_\be_\b__\bl_\bi_\bm_\bi_\bt_\be_\bd (section 6.4.82 ,
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
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
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.
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.
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
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
When _\bs_\be_\bt, menus will be scrolled up or down one line when you attempt to move
across a screen boundary. If _\bu_\bn_\bs_\be_\bt, the screen is cleared and the next or pre-
vious page of the menu is displayed (useful for slow links to avoid many
When _\bs_\be_\bt, menus will be scrolled up or down one line when you attempt to move
across a screen boundary. If _\bu_\bn_\bs_\be_\bt, the screen is cleared and the next or pre-
vious page of the menu is displayed (useful for slow links to avoid many
- Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.69 , page 96)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
- _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.137 , page 113)''.
+ Also see ``_\b$_\bf_\bo_\br_\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.69 , page 97)'' and ``_\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\b-
+ _\bw_\ba_\br_\bd_\b__\bd_\be_\bc_\bo_\bd_\be (section 6.4.137 , page 114)''.
This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
threads to fit on the screen.
This variable, when _\bs_\be_\bt, makes the thread tree narrower, allowing deeper
threads to fit on the screen.
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.).
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.).
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
the principal key will inherit the subkeys' capabilities. _\bU_\bn_\bs_\be_\bt this if you
want to play interesting key selection games. (PGP only)
Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
the principal key will inherit the subkeys' capabilities. _\bU_\bn_\bs_\be_\bt this if you
want to play interesting key selection games. (PGP only)
Setting this variable will cause Mutt-ng to always attempt to create an inline
(traditional) message when replying to a message which is PGP encrypted/signed
inline. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when inline is not
Setting this variable will cause Mutt-ng to always attempt to create an inline
(traditional) message when replying to a message which is PGP encrypted/signed
inline. This can be overridden by use of the _\bp_\bg_\bp_\b-_\bm_\be_\bn_\bu, when inline is not
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
Note that Mutt-ng might automatically use PGP/MIME for messages which consist
of more than a single MIME part. Mutt-ng can be configured to ask before send-
ing PGP/MIME messages when inline (traditional) would not work. See also:
If you have more than one key pair, this option allows you to specify which of
your private keys to use. It is recommended that you use the keyid form to
specify your key (e.g., ``0x00112233''). (PGP only)
If you have more than one key pair, this option allows you to specify which of
your private keys to use. It is recommended that you use the keyid form to
specify your key (e.g., ``0x00112233''). (PGP only)
``tag-prefix-cond'' operators. If this variable is _\bu_\bn_\bs_\be_\bt, when piping a list
of tagged messages Mutt-ng will concatenate the messages and will pipe them as
a single folder. When _\bs_\be_\bt, Mutt-ng will pipe the messages one by one. In both
cases the messages are piped in the current sorted order, and the ``_\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp
``tag-prefix-cond'' operators. If this variable is _\bu_\bn_\bs_\be_\bt, when piping a list
of tagged messages Mutt-ng will concatenate the messages and will pipe them as
a single folder. When _\bs_\be_\bt, Mutt-ng will pipe the messages one by one. In both
cases the messages are piped in the current sorted order, and the ``_\b$_\bp_\bi_\bp_\be_\b__\bs_\be_\bp
- If _\bs_\be_\bt, a shell command to be executed if Mutt-ng fails to establish a
-
- The Mutt Next Generation E-Mail Client 134
-
- connection to the server. This is useful for setting up secure connections,
- e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up
- opening the server. Example:
+ If _\bs_\be_\bt, a shell command to be executed if Mutt-ng fails to establish a connec-
+ tion to the server. This is useful for setting up secure connections, e.g. with
+ ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the
+ server. Example:
cessing will be applied to the message when printing it. The latter setting
may be useful if you are using some advanced printer filter which is able to
properly format e-mail messages for printing.
cessing will be applied to the message when printing it. The latter setting
may be useful if you are using some advanced printer filter which is able to
properly format e-mail messages for printing.
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 96)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
- 6.4.241 , page 138)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 97)'' and ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section
+ 6.4.241 , page 139)'' variables, and the ``_\bf_\bc_\bc_\b-_\bh_\bo_\bo_\bk (section 3.18 , page
messages as-is, possibly including eventual real names. When it is _\bu_\bn_\bs_\be_\bt,
Mutt-ng will override any such real names with the setting of the _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
messages as-is, possibly including eventual real names. When it is _\bu_\bn_\bs_\be_\bt,
Mutt-ng will override any such real names with the setting of the _\br_\be_\ba_\bl_\bn_\ba_\bm_\be
- folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 138)'' or
- ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 96)'' is _\bs_\be_\bt too, the selection of the
+ folder for saving a mail. If ``_\b$_\bs_\ba_\bv_\be_\b__\bn_\ba_\bm_\be (section 6.4.241 , page 139)'' or
+ ``_\b$_\bf_\bo_\br_\bc_\be_\b__\bn_\ba_\bm_\be (section 6.4.68 , page 97)'' is _\bs_\be_\bt too, the selection of the
Default: no
This variable controls how copies of outgoing messages are saved. When set, a
check is made to see if a mailbox specified by the recipient address exists
(this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 ,
Default: no
This variable controls how copies of outgoing messages are saved. When set, a
check is made to see if a mailbox specified by the recipient address exists
(this is done by searching for a mailbox in the ``_\b$_\bf_\bo_\bl_\bd_\be_\br (section 6.4.64 ,
mailbox exists, the outgoing message will be saved to that mailbox, otherwise
the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 136)'' mailbox.
mailbox exists, the outgoing message will be saved to that mailbox, otherwise
the message is saved to the ``_\b$_\br_\be_\bc_\bo_\br_\bd (section 6.4.230 , page 136)'' mailbox.
Type: string
Default: 'us-ascii:iso-8859-1:utf-8'
A list of character sets for outgoing messages. Mutt-ng will use the first
character set into which the text can be converted exactly. If your ``_\b$_\bc_\bh_\ba_\br_\bs_\be_\bt
Type: string
Default: 'us-ascii:iso-8859-1:utf-8'
A list of character sets for outgoing messages. Mutt-ng will use the first
character set into which the text can be converted exactly. If your ``_\b$_\bc_\bh_\ba_\br_\bs_\be_\bt
When the sidebar is displayed and _\b$_\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by (section
6.4.254 , page 142) is _\bs_\be_\bt, this variable specifies the characters at which to
When the sidebar is displayed and _\b$_\bs_\bi_\bd_\be_\bb_\ba_\br_\b__\bs_\bh_\bo_\br_\bt_\be_\bn_\b__\bh_\bi_\be_\br_\ba_\br_\bc_\bh_\by (section
6.4.254 , page 142) is _\bs_\be_\bt, this variable specifies the characters at which to
group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
get shortened.
At which characters this compression is done is controled via the _\b$_\bs_\bi_\bd_\be_\b-
group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
get shortened.
At which characters this compression is done is controled via the _\b$_\bs_\bi_\bd_\be_\b-
If _\bs_\be_\bt, the signature will be included before any quoted or forwarded text. It
is s\bst\btr\bro\bon\bng\bgl\bly\by recommended that you do not set this variable unless you really
know what you are doing, and are prepared to take some heat from netiquette
If _\bs_\be_\bt, the signature will be included before any quoted or forwarded text. It
is s\bst\btr\bro\bon\bng\bgl\bly\by recommended that you do not set this variable unless you really
know what you are doing, and are prepared to take some heat from netiquette
Controls the display of lines longer than the screen width in the internal
pager. If _\bs_\be_\bt, long lines are wrapped at a word boundary. If _\bu_\bn_\bs_\be_\bt, lines are
simply wrapped at the screen edge. Also see the ``_\b$_\bm_\ba_\br_\bk_\be_\br_\bs (section 6.4.121 ,
Controls the display of lines longer than the screen width in the internal
pager. If _\bs_\be_\bt, long lines are wrapped at a word boundary. If _\bu_\bn_\bs_\be_\bt, lines are
simply wrapped at the screen edge. Also see the ``_\b$_\bm_\ba_\br_\bk_\be_\br_\bs (section 6.4.121 ,
- 6.4.266 , page 144) points to a directory or file, this expands to
- '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.4.266 , page 144)' or
- '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.4.266 , page 144)'.
+ 6.4.266 , page 145) points to a directory or file, this expands to
+ '-CApath _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.4.266 , page 145)' or
+ '-CAfile _\b$_\bs_\bm_\bi_\bm_\be_\b__\bc_\ba_\b__\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn (section 6.4.266 , page 145)'.
If _\bs_\be_\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
mailbox-address to determine the key to use. It will ask you to supply a key,
If _\bs_\be_\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
mailbox-address to determine the key to use. It will ask you to supply a key,
- The Mutt Next Generation E-Mail Client 150
+ If this variable is non-empty, it'll be used as the envelope sender. If it's
+ empty (the default), the value of the regular From: header will be used.
+
+ This may be necessary as some providers don't allow for arbitrary values as the
+ envelope sender but only a particular one which may not be the same as the
+ user's desired From: header.
+
+ _\b6_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
+
+ The Mutt Next Generation E-Mail Client 151
+
+ Type: string
+
+ Default: ''
+
+ Availability: SMTP
Defines the SMTP host which will be used to deliver mail, as opposed to invok-
ing the sendmail binary. Setting this variable overrides the value of ``_\b$_\bs_\be_\bn_\bd_\b-
_\bm_\ba_\bi_\bl (section 6.4.247 , page 140)'', and any associated variables.
Defines the SMTP host which will be used to deliver mail, as opposed to invok-
ing the sendmail binary. Setting this variable overrides the value of ``_\b$_\bs_\be_\bn_\bd_\b-
_\bm_\ba_\bi_\bl (section 6.4.247 , page 140)'', and any associated variables.
- Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\ba_\bu_\bt_\bh_\b__\bu_\bs_\be_\br_\bn_\ba_\bm_\be (section
- , page )'' is set, but this variable is not, you will be prompted for a pass-
- word when sending.
+ Defines the password to use with SMTP AUTH. If ``_\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br (section
+ 6.4.290 , page 150)'' is set, but this variable is not, you will be prompted
+ for a password when sending.
Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
will probably desire 587, the mail submission port.
Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
will probably desire 587, the mail submission port.
except threads (in that case, Mutt-ng will just use date-sent). You can also
specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
come after reverse-. The last- prefix causes messages to be sorted against its
except threads (in that case, Mutt-ng will just use date-sent). You can also
specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
come after reverse-. The last- prefix causes messages to be sorted against its
- N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 6.4.290 , page 149)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
- (section 6.4.292 , page 150) is reversed again (which is not the right thing
+ N\bNo\bot\bte\be:\b: For reversed ``_\b$_\bs_\bo_\br_\bt (section 6.4.291 , page 150)'' order _\b$_\bs_\bo_\br_\bt_\b__\ba_\bu_\bx
+ (section 6.4.293 , page 151) is reversed again (which is not the right thing
- (section 6.4.311 , page 157)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
- Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.294 ,
- page 151) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
+ (section 6.4.312 , page 158)'' _\bu_\bn_\bs_\be_\bt. In that case, it changes the heuristic
+ Mutt-ng uses to thread messages by subject. With _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.295 ,
+ page 152) _\bs_\be_\bt, Mutt-ng will only attach a message as the child of another mes-
- matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.231 , page 136)''. With
- _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.294 , page 151) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
+ matching the setting of ``_\b$_\br_\be_\bp_\bl_\by_\b__\br_\be_\bg_\be_\bx_\bp (section 6.4.231 , page 137)''. With
+ _\b$_\bs_\bo_\br_\bt_\b__\br_\be (section 6.4.295 , page 152) _\bu_\bn_\bs_\be_\bt, Mutt-ng will attach the message
- ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.295 , page 151)'' controls what happens when
- multiple spam headers are matched: if _\bu_\bn_\bs_\be_\bt, each successive header will
+ ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.296 , page 152)'' controls what happens when
+ multiple spam headers are matched: if _\bu_\bn_\bs_\be_\bt, each successive header will over-
+ write any previous matches value for the spam label. If _\bs_\be_\bt, each successive
+ match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section 6.4.296 ,
+ page 152)'' as a separator.
- The Mutt Next Generation E-Mail Client 153
-
- overwrite any previous matches value for the spam label. If _\bs_\be_\bt, each succes-
- sive match will append to the previous, using ``_\bs_\bp_\ba_\bm_\b__\bs_\be_\bp_\ba_\br_\ba_\bt_\bo_\br (section
- 6.4.295 , page 151)'' as a separator.
-
- _\b6_\b._\b4_\b._\b2_\b9_\b6 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
+ _\b6_\b._\b4_\b._\b2_\b9_\b7 _\bs_\bp_\bo_\bo_\bl_\bf_\bi_\bl_\be
If this variable is _\bs_\be_\bt, mutt-ng will require that all connections to remote
servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
server does not advertise the capability, since it would otherwise have to
If this variable is _\bs_\be_\bt, mutt-ng will require that all connections to remote
servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
server does not advertise the capability, since it would otherwise have to
unchanged. The second is used when the mailbox has been changed, and it needs
to be resynchronized. The third is used if the mailbox is in read-only mode, or
if the mailbox will not be written when exiting that mailbox (You can toggle
unchanged. The second is used when the mailbox has been changed, and it needs
to be resynchronized. The third is used if the mailbox is in read-only mode, or
if the mailbox will not be written when exiting that mailbox (You can toggle
been opened in attach-message mode (Certain operations like composing a new
mail, replying, forwarding, etc. are not permitted in this mode).
been opened in attach-message mode (Certain operations like composing a new
mail, replying, forwarding, etc. are not permitted in this mode).
If this variable is _\bs_\be_\bt, mutt-ng is strict and allows anything to be changed.
If it's _\bu_\bn_\bs_\be_\bt, all headers given will be prefixed with ``X-Mailto-'' and the
message including headers will be shown in the editor regardless of what
If this variable is _\bs_\be_\bt, mutt-ng is strict and allows anything to be changed.
If it's _\bu_\bn_\bs_\be_\bt, all headers given will be prefixed with ``X-Mailto-'' and the
message including headers will be shown in the editor regardless of what
When _\bu_\bn_\bs_\be_\bt, non MIME-compliant messages that doesn't have any charset indica-
tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
messages are often generated by old mailers or buggy mailers like MS Outlook
When _\bu_\bn_\bs_\be_\bt, non MIME-compliant messages that doesn't have any charset indica-
tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
messages are often generated by old mailers or buggy mailers like MS Outlook
This option also replaces linear-white-space between encoded-word and *text to
a single space to prevent the display of MIME-encoded ``Subject:'' header field
from being devided into multiple lines.
This option also replaces linear-white-space between encoded-word and *text to
a single space to prevent the display of MIME-encoded ``Subject:'' header field
from being devided into multiple lines.
sage threads. By default, messages with the same subject are grouped together
in ``pseudo threads.'' This may not always be desirable, such as in a personal
mailbox where you might have several unrelated messages with the subject ``hi''
which will get grouped together.
sage threads. By default, messages with the same subject are grouped together
in ``pseudo threads.'' This may not always be desirable, such as in a personal
mailbox where you might have several unrelated messages with the subject ``hi''
which will get grouped together.
When _\bs_\be_\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
rent thread is _\bu_\bncollapsed.
When _\bs_\be_\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
rent thread is _\bu_\bncollapsed.
- When _\bs_\be_\bt, Mutt-ng will invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page 140)'' with
- the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation.
+ When _\bs_\be_\bt, Mutt-ng will either invoke ``_\b$_\bs_\be_\bn_\bd_\bm_\ba_\bi_\bl (section 6.4.247 , page
+ 140)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
+ negotiation or tell libESMTP to do so.
- tion 6.4.342 , page 163) is _\bs_\be_\bt. This string is identical in formatting to the
- one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.307 , page 154)''.
+ tion 6.4.343 , page 164) is _\bs_\be_\bt. This string is identical in formatting to the
+ one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 , page 155)''.
used to set the title when leaving mutt-ng. For terminal-based programs,
there's no easy and portable way to read the current title so mutt-ng cannot
read it upon startup and restore it when exiting.
used to set the title when leaving mutt-ng. For terminal-based programs,
there's no easy and portable way to read the current title so mutt-ng cannot
read it upon startup and restore it when exiting.
- _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.342 , page 163) has been _\bs_\be_\bt. This string is
- identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.307 ,
- page 154)''.
+ _\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.343 , page 164) has been _\bs_\be_\bt. This string is
+ identical in formatting to the one used by ``_\b$_\bs_\bt_\ba_\bt_\bu_\bs_\b__\bf_\bo_\br_\bm_\ba_\bt (section 6.4.308 ,
+ page 155)''.
4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64
4.19 Compressed folders Support (OPTIONAL) .......................... 64
4.19.1 Open a compressed mailbox for reading 65
4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64
4.19 Compressed folders Support (OPTIONAL) .......................... 64
4.19.1 Open a compressed mailbox for reading 65
5. Mutt-ng's MIME Support ............................................... 67
5.1 Using MIME in Mutt ............................................. 67
5.1.1 Viewing MIME messages in the pager 67
5. Mutt-ng's MIME Support ............................................... 67
5.1 Using MIME in Mutt ............................................. 67
5.1.1 Viewing MIME messages in the pager 67
6. Reference ............................................................ 77
6.1 Command line options ........................................... 77
6.2 Patterns ....................................................... 78
6. Reference ............................................................ 77
6.1 Command line options ........................................... 77
6.2 Patterns ....................................................... 78
- 6.3 Configuration Commands ......................................... 79
- 6.4 Configuration variables .......................................... 81
- 6.4.1 abort_nosubject 81
- 6.4.2 abort_unmodified 81
- 6.4.3 alias_file 81
- 6.4.4 alias_format 81
- 6.4.5 allow_8bit 82
- 6.4.6 allow_ansi 82
- 6.4.7 arrow_cursor 82
+ 6.3 Configuration Commands ......................................... 80
+ 6.4 Configuration variables .......................................... 82
+ 6.4.1 abort_nosubject 82
+ 6.4.2 abort_unmodified 82
+ 6.4.3 alias_file 82
+ 6.4.4 alias_format 82
+ 6.4.5 allow_8bit 83
+ 6.4.6 allow_ansi 83
+ 6.4.7 arrow_cursor 83
- 6.4.22 braille_friendly 86
- 6.4.23 certificate_file 86
- 6.4.24 charset 87
- 6.4.25 check_new 87
- 6.4.26 collapse_unread 87
- 6.4.27 compose_format 87
- 6.4.28 config_charset 88
- 6.4.29 confirmappend 88
- 6.4.30 confirmcreate 88
- 6.4.31 connect_timeout 88
- 6.4.32 content_type 88
+ 6.4.22 braille_friendly 87
+ 6.4.23 certificate_file 87
+ 6.4.24 charset 88
+ 6.4.25 check_new 88
+ 6.4.26 collapse_unread 88
+ 6.4.27 compose_format 88
+ 6.4.28 config_charset 89
+ 6.4.29 confirmappend 89
+ 6.4.30 confirmcreate 89
+ 6.4.31 connect_timeout 89
+ 6.4.32 content_type 89
- 6.4.38 crypt_replyencrypt 90
- 6.4.39 crypt_replysign 90
- 6.4.40 crypt_replysignencrypted 90
- 6.4.41 crypt_timestamp 90
+ 6.4.38 crypt_replyencrypt 91
+ 6.4.39 crypt_replysign 91
+ 6.4.40 crypt_replysignencrypted 91
+ 6.4.41 crypt_timestamp 91
- 6.4.107 include 106
- 6.4.108 include_onlyfirst 106
- 6.4.109 indent_string 106
- 6.4.110 index_format 106
- 6.4.111 ispell 109
- 6.4.112 keep_flagged 109
- 6.4.113 list_reply 109
+ 6.4.107 include 107
+ 6.4.108 include_onlyfirst 107
+ 6.4.109 indent_string 107
+ 6.4.110 index_format 107
+ 6.4.111 ispell 110
+ 6.4.112 keep_flagged 110
+ 6.4.113 list_reply 110
- 6.4.136 mime_forward 114
- 6.4.137 mime_forward_decode 114
- 6.4.138 mime_forward_rest 114
- 6.4.139 mix_entry_format 114
- 6.4.140 mixmaster 115
- 6.4.141 move 115
- 6.4.142 msgid_format 115
- 6.4.143 narrow_tree 116
+ 6.4.136 mime_forward 115
+ 6.4.137 mime_forward_decode 115
+ 6.4.138 mime_forward_rest 115
+ 6.4.139 mix_entry_format 115
+ 6.4.140 mixmaster 116
+ 6.4.141 move 116
+ 6.4.142 msgid_format 116
+ 6.4.143 narrow_tree 117
- 6.4.170 pager_stop 123
- 6.4.171 pgp_auto_decode 123
- 6.4.172 pgp_autoinline 123
- 6.4.173 pgp_check_exit 124
- 6.4.174 pgp_clearsign_command 124
- 6.4.175 pgp_decode_command 124
+ 6.4.170 pager_stop 124
+ 6.4.171 pgp_auto_decode 124
+ 6.4.172 pgp_autoinline 124
+ 6.4.173 pgp_check_exit 125
+ 6.4.174 pgp_clearsign_command 125
+ 6.4.175 pgp_decode_command 125
- 6.4.177 pgp_encrypt_only_command 125
- 6.4.178 pgp_encrypt_sign_command 125
- 6.4.179 pgp_entry_format 125
- 6.4.180 pgp_export_command 126
+ 6.4.177 pgp_encrypt_only_command 126
+ 6.4.178 pgp_encrypt_sign_command 126
+ 6.4.179 pgp_entry_format 126
+ 6.4.180 pgp_export_command 127
- 6.4.185 pgp_list_pubring_command 127
- 6.4.186 pgp_list_secring_command 127
- 6.4.187 pgp_long_ids 127
- 6.4.188 pgp_mime_auto 127
+ 6.4.185 pgp_list_pubring_command 128
+ 6.4.186 pgp_list_secring_command 128
+ 6.4.187 pgp_long_ids 128
+ 6.4.188 pgp_mime_auto 128
- 6.4.212 post_indent_string 133
- 6.4.213 postpone 133
- 6.4.214 postponed 133
- 6.4.215 preconnect 133
- 6.4.216 print 134
- 6.4.217 print_command 134
- 6.4.218 print_decode 134
- 6.4.219 print_split 134
+ 6.4.212 post_indent_string 134
+ 6.4.213 postpone 134
+ 6.4.214 postponed 134
+ 6.4.215 preconnect 134
+ 6.4.216 print 135
+ 6.4.217 print_command 135
+ 6.4.218 print_decode 135
+ 6.4.219 print_split 135
- 6.4.239 save_address 139
- 6.4.240 save_empty 139
- 6.4.241 save_name 139
- 6.4.242 score 140
- 6.4.243 score_threshold_delete 140
- 6.4.244 score_threshold_flag 140
- 6.4.245 score_threshold_read 140
- 6.4.246 send_charset 140
- 6.4.247 sendmail 141
- 6.4.248 sendmail_wait 141
- 6.4.249 shell 141
+ 6.4.239 save_address 140
+ 6.4.240 save_empty 140
+ 6.4.241 save_name 140
+ 6.4.242 score 141
+ 6.4.243 score_threshold_delete 141
+ 6.4.244 score_threshold_flag 141
+ 6.4.245 score_threshold_read 141
+ 6.4.246 send_charset 141
+ 6.4.247 sendmail 142
+ 6.4.248 sendmail_wait 142
+ 6.4.249 shell 142
- 6.4.251 sidebar_delim 142
- 6.4.252 sidebar_newmail_only 142
- 6.4.253 sidebar_number_format 142
- 6.4.254 sidebar_shorten_hierarchy 143
- 6.4.255 sidebar_visible 143
- 6.4.256 sidebar_width 143
- 6.4.257 sig_dashes 143
+ 6.4.251 sidebar_delim 143
+ 6.4.252 sidebar_newmail_only 143
+ 6.4.253 sidebar_number_format 143
+ 6.4.254 sidebar_shorten_hierarchy 144
+ 6.4.255 sidebar_visible 144
+ 6.4.256 sidebar_width 144
+ 6.4.257 sig_dashes 144
- 6.4.263 smart_wrap 145
- 6.4.264 smileys 145
- 6.4.265 smime_ask_cert_label 145
- 6.4.266 smime_ca_location 145
- 6.4.267 smime_certificates 145
- 6.4.268 smime_decrypt_command 146
- 6.4.269 smime_decrypt_use_default_key 146
+ 6.4.263 smart_wrap 146
+ 6.4.264 smileys 146
+ 6.4.265 smime_ask_cert_label 146
+ 6.4.266 smime_ca_location 146
+ 6.4.267 smime_certificates 146
+ 6.4.268 smime_decrypt_command 147
+ 6.4.269 smime_decrypt_use_default_key 147
- 6.4.271 smime_encrypt_command 147
- 6.4.272 smime_encrypt_with 147
- 6.4.273 smime_get_cert_command 147
- 6.4.274 smime_get_cert_email_command 147
- 6.4.275 smime_get_signer_cert_command 147
- 6.4.276 smime_import_cert_command 148
- 6.4.277 smime_is_default 148
- 6.4.278 smime_keys 148
- 6.4.279 smime_pk7out_command 148
+ 6.4.271 smime_encrypt_command 148
+ 6.4.272 smime_encrypt_with 148
+ 6.4.273 smime_get_cert_command 148
+ 6.4.274 smime_get_cert_email_command 148
+ 6.4.275 smime_get_signer_cert_command 148
+ 6.4.276 smime_import_cert_command 149
+ 6.4.277 smime_is_default 149
+ 6.4.278 smime_keys 149
+ 6.4.279 smime_pk7out_command 149
- 6.4.281 smime_sign_opaque_command 149
- 6.4.282 smime_timeout 149
- 6.4.283 smime_verify_command 149
- 6.4.284 smime_verify_opaque_command 149
- 6.4.285 smtp_host 149
- 6.4.286 smtp_pass 150
+ 6.4.281 smime_sign_opaque_command 150
+ 6.4.282 smime_timeout 150
+ 6.4.283 smime_verify_command 150
+ 6.4.284 smime_verify_opaque_command 150
+ 6.4.285 smtp_envelope 150
+ 6.4.286 smtp_host 150
- 6.4.287 smtp_port 150
- 6.4.288 smtp_use_tls 150
- 6.4.289 smtp_user 150
- 6.4.290 sort 151
- 6.4.291 sort_alias 151
- 6.4.292 sort_aux 151
- 6.4.293 sort_browser 152
- 6.4.294 sort_re 152
- 6.4.295 spam_separator 152
- 6.4.296 spoolfile 153
- 6.4.297 ssl_ca_certificates_file 153
- 6.4.298 ssl_client_cert 153
- 6.4.299 ssl_force_tls 153
- 6.4.300 ssl_min_dh_prime_bits 153
- 6.4.301 ssl_starttls 154
- 6.4.302 ssl_use_sslv2 154
- 6.4.303 ssl_use_sslv3 154
- 6.4.304 ssl_use_tlsv1 154
- 6.4.305 ssl_usesystemcerts 154
- 6.4.306 status_chars 155
- 6.4.307 status_format 155
- 6.4.308 status_on_top 157
- 6.4.309 strict_mailto 157
- 6.4.310 strict_mime 158
- 6.4.311 strict_threads 158
- 6.4.312 strip_was 158
- 6.4.313 strip_was_regex 158
- 6.4.314 stuff_quoted 159
- 6.4.315 suspend 159
- 6.4.316 text_flowed 159
- 6.4.317 thorough_search 159
- 6.4.318 thread_received 159
- 6.4.319 tilde 160
- 6.4.320 timeout 160
- 6.4.321 tmpdir 160
- 6.4.322 to_chars 160
- 6.4.323 trash 160
- 6.4.324 tunnel 161
- 6.4.325 umask 161
- 6.4.326 uncollapse_jump 161
- 6.4.327 use_8bitmime 161
- 6.4.328 use_domain 161
- 6.4.329 use_from 162
- 6.4.330 use_idn 162
- 6.4.331 use_ipv6 162
- 6.4.332 user_agent 162
- 6.4.333 visual 162
- 6.4.334 wait_key 163
- 6.4.335 weed 163
- 6.4.336 wrap_search 163
- 6.4.337 wrapmargin 163
- 6.4.338 write_bcc 163
- 6.4.339 write_inc 164
+ 6.4.287 smtp_pass 151
+ 6.4.288 smtp_port 151
+ 6.4.289 smtp_use_tls 151
+ 6.4.290 smtp_user 152
+ 6.4.291 sort 152
+ 6.4.292 sort_alias 152
+ 6.4.293 sort_aux 152
+ 6.4.294 sort_browser 153
+ 6.4.295 sort_re 153
+ 6.4.296 spam_separator 154
+ 6.4.297 spoolfile 154
+ 6.4.298 ssl_ca_certificates_file 154
+ 6.4.299 ssl_client_cert 154
+ 6.4.300 ssl_force_tls 154
+ 6.4.301 ssl_min_dh_prime_bits 155
+ 6.4.302 ssl_starttls 155
+ 6.4.303 ssl_use_sslv2 155
+ 6.4.304 ssl_use_sslv3 155
+ 6.4.305 ssl_use_tlsv1 155
+ 6.4.306 ssl_usesystemcerts 156
+ 6.4.307 status_chars 156
+ 6.4.308 status_format 156
+ 6.4.309 status_on_top 158
+ 6.4.310 strict_mailto 159
+ 6.4.311 strict_mime 159
+ 6.4.312 strict_threads 159
+ 6.4.313 strip_was 159
+ 6.4.314 strip_was_regex 160
+ 6.4.315 stuff_quoted 160
+ 6.4.316 suspend 160
+ 6.4.317 text_flowed 160
+ 6.4.318 thorough_search 160
+ 6.4.319 thread_received 161
+ 6.4.320 tilde 161
+ 6.4.321 timeout 161
+ 6.4.322 tmpdir 161
+ 6.4.323 to_chars 161
+ 6.4.324 trash 162
+ 6.4.325 tunnel 162
+ 6.4.326 umask 162
+ 6.4.327 uncollapse_jump 162
+ 6.4.328 use_8bitmime 162
+ 6.4.329 use_domain 163
+ 6.4.330 use_from 163
+ 6.4.331 use_idn 163
+ 6.4.332 use_ipv6 163
+ 6.4.333 user_agent 163
+ 6.4.334 visual 164
+ 6.4.335 wait_key 164
+ 6.4.336 weed 164
+ 6.4.337 wrap_search 164
+ 6.4.338 wrapmargin 164
+ 6.4.339 write_bcc 165
- 6.4.340 xterm_icon 164
- 6.4.341 xterm_leave 164
- 6.4.342 xterm_set_titles 164
- 6.4.343 xterm_title 164
- 6.5 Functions ....................................................... 165
- 6.5.1 generic 165
- 6.5.2 index 166
- 6.5.3 pager 168
- 6.5.4 alias 170
- 6.5.5 query 170
- 6.5.6 attach 170
- 6.5.7 compose 171
- 6.5.8 postpone 172
- 6.5.9 browser 172
- 6.5.10 pgp 173
- 6.5.11 editor 173
-
- 7. Miscellany ............................................................ 173
- 7.1 Acknowledgments ................................................. 174
- 7.2 About this document ............................................. 176
+ 6.4.340 write_inc 165
+ 6.4.341 xterm_icon 165
+ 6.4.342 xterm_leave 165
+ 6.4.343 xterm_set_titles 165
+ 6.4.344 xterm_title 166
+ 6.5 Functions ....................................................... 166
+ 6.5.1 generic 166
+ 6.5.2 index 167
+ 6.5.3 pager 169
+ 6.5.4 alias 171
+ 6.5.5 query 171
+ 6.5.6 attach 171
+ 6.5.7 compose 172
+ 6.5.8 postpone 173
+ 6.5.9 browser 173
+ 6.5.10 pgp 174
+ 6.5.11 editor 174
+
+ 7. Miscellany ............................................................ 174
+ 7.1 Acknowledgments ................................................. 175
+ 7.2 About this document ............................................. 177
projects / apps / madmutt.git / commitdiff