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-r388
+ version devel-r394
A\bAb\bbs\bst\btr\bra\bac\bct\bt
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 66), 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 67), you can
change any attachment's content type. These changes are not persistent, and get
lost upon changing folders.
from people who they have defined an alias for so that those 2 groups of
messages are excluded from the strict rules.
- _\b4_\b._\b1_\b6 _\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)
+ _\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
+ functionality. When configure was called with --with-libesmtp or the output
+ muttng -v contains +USE_LIBESMTP, this will be or is the case already.
+
+ To enable sending mail directly via SMTP without an MTA such as Postfix or
+ SSMTP and the like, simply set the _\b$_\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt (section 6.4.285 , page 148)
+ variable pointing to your SMTP server.
+
+ 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.
+
+ Transport Encryption via the StartTLS command is also available. For this to
+ work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
+ _\b$_\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs (section 6.4.288 , page 149) 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.
+
+ _\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 Mutt Next Generation E-Mail Client 64
+
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.
account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
- _\b4_\b._\b1_\b7 _\bS_\bt_\ba_\br_\bt _\ba _\bW_\bW_\bW _\bB_\br_\bo_\bw_\bs_\be_\br _\bo_\bn _\bU_\bR_\bL_\bs _\b(_\bE_\bX_\bT_\bE_\bR_\bN_\bA_\bL_\b)
+ _\b4_\b._\b1_\b8 _\bS_\bt_\ba_\br_\bt _\ba _\bW_\bW_\bW _\bB_\br_\bo_\bw_\bs_\be_\br _\bo_\bn _\bU_\bR_\bL_\bs _\b(_\bE_\bX_\bT_\bE_\bR_\bN_\bA_\bL_\b)
If a message contains URLs (_\bu_\bn_\bi_\bf_\bi_\be_\bd _\br_\be_\bs_\bo_\bu_\br_\bc_\be _\bl_\bo_\bc_\ba_\bt_\bo_\br = address in the WWW space
like _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bm_\bu_\bt_\bt_\b._\bo_\br_\bg_\b/), it is efficient to get a menu with all the URLs and
start a WWW browser on one of them. This functionality is provided by the
- external urlview program which can be retrieved at
-
- The Mutt Next Generation E-Mail Client 64
-
- ftp://ftp.mutt.org/mutt/contrib/ and the configuration commands:
+ external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
+ trib/ and the configuration commands:
macro index \cb |urlview\n
macro pager \cb |urlview\n
- _\b4_\b._\b1_\b8 _\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)
+ _\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-
_\bu_\br_\be script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd flag), Mutt can open folders stored in
may be faster than converting the entire folder to the accepted format, append-
ing to it and converting back to the user-defined format.
- There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.18.1 , page 64), _\bc_\bl_\bo_\bs_\be_\b-
- _\bh_\bo_\bo_\bk (section 4.18.2 , page 64) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.18.3 , page 65))
+ There are three hooks defined (_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64), _\bc_\bl_\bo_\bs_\be_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.2 , page 65) and _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65))
which define commands to uncompress and compress a folder and to append mes-
sages to an existing compressed folder respectively.
close-hook \\.gz$ "gzip -c %t > %f"
append-hook \\.gz$ "gzip -c %t >> %f"
+ The Mutt Next Generation E-Mail Client 65
+
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.18.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.18.2 , page 64) (or give
+ 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
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.18.3 , page 65) though you'll be able to append to the folder.
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 65) though you'll be able to append to the folder.
Note that Mutt-ng will only try to use hooks if the file is not in one of the
accepted formats. In particular, if the file is empty, mutt supposes it is not
unset _\b$_\bs_\ba_\bv_\be_\b__\be_\bm_\bp_\bt_\by (section 6.4.240 , page 138), so that the compressed file
will be removed if you delete all of the messages.
- _\b4_\b._\b1_\b8_\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
+ _\b4_\b._\b1_\b9_\b._\b1 _\bO_\bp_\be_\bn _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx _\bf_\bo_\br _\br_\be_\ba_\bd_\bi_\bn_\bg
Usage: open-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd is the command that can be used for opening the folders whose names
-
- The Mutt Next Generation E-Mail Client 65
-
match _\br_\be_\bg_\be_\bx_\bp.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd string is the printf-like format string, and it should accept two
If the _\bc_\bo_\bm_\bm_\ba_\bn_\bd is empty, this operation is disabled for this file type.
- _\b4_\b._\b1_\b8_\b._\b2 _\bW_\br_\bi_\bt_\be _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ _\b4_\b._\b1_\b9_\b._\b2 _\bW_\br_\bi_\bt_\be _\ba _\bc_\bo_\bm_\bp_\br_\be_\bs_\bs_\be_\bd _\bm_\ba_\bi_\bl_\bb_\bo_\bx
Usage: close-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
This is used to close the folder that was open with the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.18.1 , page 64) command after some changes were made to it.
+ 4.19.1 , page 64) command after some changes were made to it.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd string is the command that can be used for closing the folders
whose names match _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section
- 4.18.1 , page 64) command. Temporary folder in this case is the folder previ-
- ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.18.1 , page 64) command.
+ 4.19.1 , page 64) command. Temporary folder in this case is the folder previ-
+ ously produced by the <_\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64) command.
The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should n\bno\bot\bt remove the decompressed file. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd should return
non-zero exit status if it fails, so mutt knows something's wrong.
+ The Mutt Next Generation E-Mail Client 66
+
Example:
close-hook \\.gz$ "gzip -c %t > %f"
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.18.2 , page 64) is not called when you exit from the
+ _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65) is not called when you exit from the
folder if the folder was not changed.
- _\b4_\b._\b1_\b8_\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
+ _\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
Usage: append-hook _\br_\be_\bg_\be_\bx_\bp '_\bc_\bo_\bm_\bm_\ba_\bn_\bd'
This command is used for saving to an existing compressed folder. The _\bc_\bo_\bm_\bm_\ba_\bn_\bd
is the command that can be used for appending to the folders whose names match
-
- The Mutt Next Generation E-Mail Client 66
-
- _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.18.1 , page 64)
+ _\br_\be_\bg_\be_\bx_\bp. It has the same format as in the _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64)
command. The temporary folder in this case contains the messages that are
being appended.
append-hook \\.gz$ "gzip -c %t >> %f"
- When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.18.3 , page 65) is used, the folder is not opened,
+ When _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65) is used, the folder is not opened,
which saves time, but this means that we can not find out what the folder type
is. Thus the default (_\b$_\bm_\bb_\bo_\bx_\b__\bt_\by_\bp_\be (section 6.4.125 , page 111)) 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.18.2 ,
- page 64) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.18.3 , page 65). _\ba_\bp_\bp_\be_\bn_\bd_\b-
- _\bh_\bo_\bo_\bk (section 4.18.3 , page 65) is only for appending to existing folders.
+ If the file does not exist when you save to it, _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 ,
+ page 65) is called, and not _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65). _\ba_\bp_\bp_\be_\bn_\bd_\b-
+ _\bh_\bo_\bo_\bk (section 4.19.3 , page 65) is only for appending to existing folders.
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.18.1 , page 64) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.18.2 , page 64)respectively) each
+ 4.19.1 , page 64) and _\bc_\bl_\bo_\bs_\be_\b-_\bh_\bo_\bo_\bk (section 4.19.2 , page 65)respectively) each
time you will add to it.
- _\b4_\b._\b1_\b8_\b._\b4 _\bE_\bn_\bc_\br_\by_\bp_\bt_\be_\bd _\bf_\bo_\bl_\bd_\be_\br_\bs
+ _\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
you want to encrypt a folder with PGP, you may want to use the following hooks:
open-hook \\.pgp$ "pgp -f < %f > %t"
close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
+ The Mutt Next Generation E-Mail Client 67
+
Please note, that PGP does not support appending to an encrypted folder, so
there is no append-hook defined.
Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
MUA. Every effort has been made to provide the functionality that the discern-
ing MIME user requires, and the conformance to the standards wherever possible.
-
- The Mutt Next Generation E-Mail Client 67
-
When configuring Mutt-ng for MIME, there are two extra types of configuration
files which Mutt-ng uses. One is the mime.types file, which contains the map-
ping of file extensions to IANA MIME types. The other is the mailcap file,
The default binding for view-attachments is `v', which displays the attachment
menu for a message. The attachment menu displays a list of the attachments in
+
+ The Mutt Next Generation E-Mail Client 68
+
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
The compose menu is the menu you see before you send a message. It allows you
to edit the recipient list, the subject, and other aspects of your message. It
-
- The Mutt Next Generation E-Mail Client 68
-
also contains a list of the attachments of your message, including the main
body. From this menu, you can print, copy, filter, pipe, edit, compose,
review, and rename an attachment or a list of tagged attachments. You can also
application/pgp pgp
audio/x-aiff aif aifc aiff
+ The Mutt Next Generation E-Mail Client 69
+
A sample mime.types file comes with the Mutt-ng distribution, and should con-
tain most of the MIME types you are likely to use.
these if the appropriate entry is found in the mime.types file. It also recog-
nises other major mime types, such as the chemical type that is widely used in
the molecular modelling community to pass molecular data in various forms to
-
- The Mutt Next Generation E-Mail Client 69
-
various molecular viewers. Non-recognised mime types should only be used if the
recipient of the message is likely to be expecting such attachments.
optional fields. Each field of a definition line is divided by a semicolon ';'
character.
+ The Mutt Next Generation E-Mail Client 70
+
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
body of the MIME message to a temporary file, and then call the view command
with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
will turn over the terminal to the view program until the program quits, at
-
- The Mutt Next Generation E-Mail Client 70
-
which time Mutt will remove the temporary file if it exists.
So, in the simplest form, you can send a text/plain message to the external
This is the simplest form of a mailcap file.
+ The Mutt Next Generation E-Mail Client 71
+
_\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
double quotes. Mutt-ng does this for you, the right way, as should any other
program which interprets mailcap. Don't put them into backtick expansions. Be
highly careful with eval statements, and avoid them if possible at all. Trying
-
- The Mutt Next Generation E-Mail Client 71
-
to fix broken behaviour with quotes introduces new leaks - there is no alterna-
tive to correct quoting in the first place.
and Mutt-ng will use your standard pager to display the results.
needsterminal
- Mutt-ng uses this flag when viewing attachments with _\ba_\bu_\bt_\bo_\bv_\bi_\be_\bw (sec-
- tion 5.4 , page 74), in order to decide whether it should honor
- the setting of the _\b$_\bw_\ba_\bi_\bt_\b__\bk_\be_\by (section 6.4.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
+
+ 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.
compose=<command>
This flag specifies the command to use to create a new attachment
of a specific MIME type. Mutt-ng supports this from the compose
menu.
- The Mutt Next Generation E-Mail Client 72
-
composetyped=<command>
This flag specifies the command to use to create a new attachment
of a specific MIME type. This command differs from the compose
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s
+ The Mutt Next Generation E-Mail Client 73
+
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
When searching for an entry in the mailcap file, Mutt-ng will search for the
most useful entry for its purpose. For instance, if you are attempting to
print an image/gif, and you have the following entries in your mailcap file,
-
- The Mutt Next Generation E-Mail Client 73
-
Mutt-ng will search for an entry with the print command:
image/*; xv %s
use of this keyword causes Mutt-ng to not pass the body of the mes-
sage to the view/print/edit program on stdin.
+ The Mutt Next Generation E-Mail Client 74
+
%t
Mutt-ng will expand %t to the text representation of the content
type of the message in the same form as the first parameter of the
Content-Type: text/plain; charset=iso-8859-1
- The Mutt Next Generation E-Mail Client 74
-
then Mutt-ng will expand %{charset} to iso-8859-1. The default
metamail mailcap file uses this feature to test the charset to
spawn an xterm using the right charset to view the message.
The following are the commands understood by mutt.
- +\bo _\ba_\bc_\bc_\bo_\bu_\bn_\bt_\b-_\bh_\bo_\bo_\bk (section 4.16 , page 62) _\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 63) _\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 _\bu_\bn_\ba_\bl_\bt_\be_\br_\bn_\ba_\bt_\bi_\bv_\be_\b__\bo_\br_\bd_\be_\br (section 5.5 , page 75) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
- +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.18.3 , page 65) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\ba_\bp_\bp_\be_\bn_\bd_\b-_\bh_\bo_\bo_\bk (section 4.19.3 , page 65) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+\bo _\ba_\bu_\bt_\bo_\b__\bv_\bi_\be_\bw (section 5.4 , page 74) _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+\bo _\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.18.2 , page 64) _\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 65) _\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_\bm_\by_\b__\bh_\bd_\br (section 3.15 , page 34) _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
- +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.18.1 , page 64) _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ +\bo _\bo_\bp_\be_\bn_\b-_\bh_\bo_\bo_\bk (section 4.19.1 , page 64) _\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
This command is used to verify S/MIME signatures of type application/x-
pkcs7-mime. (S/MIME only)
- _\b6_\b._\b4_\b._\b2_\b8_\b5 _\bs_\bm_\bt_\bp_\b__\ba_\bu_\bt_\bh_\b__\bp_\ba_\bs_\bs_\bw_\bo_\br_\bd
+ _\b6_\b._\b4_\b._\b2_\b8_\b5 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
Type: string
The Mutt Next Generation E-Mail Client 150
- 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
- 6.4.286 , page 148)'' is set, but this variable is not, you will be prompted
- for a password when sending.
-
- N\bNo\bot\bte\be:\b: Storing passwords in a configuration file presents a security risk since
- the superuser of your machine may read it regardless of the file's permissions.
+ 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.
- _\b6_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bt_\bp_\b__\ba_\bu_\bt_\bh_\b__\bu_\bs_\be_\br_\bn_\ba_\bm_\be
+ _\b6_\b._\b4_\b._\b2_\b8_\b6 _\bs_\bm_\bt_\bp_\b__\bp_\ba_\bs_\bs
Type: string
Availability: SMTP
- Defines the username to use with SMTP AUTH. Setting this variable will cause
- Mutt-ng to attempt to use SMTP AUTH when sending.
-
- _\b6_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bt_\bp_\b__\bh_\bo_\bs_\bt
-
- Type: string
-
- Default: ''
-
- Availability: SMTP
+ 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 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.
+ 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.
- _\b6_\b._\b4_\b._\b2_\b8_\b8 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
+ _\b6_\b._\b4_\b._\b2_\b8_\b7 _\bs_\bm_\bt_\bp_\b__\bp_\bo_\br_\bt
Type: number
Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
will probably desire 587, the mail submission port.
- _\b6_\b._\b4_\b._\b2_\b8_\b9 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
+ _\b6_\b._\b4_\b._\b2_\b8_\b8 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\b__\bt_\bl_\bs
Type: string
Defines wether to use STARTTLS. If this option is set to ``_\br_\be_\bq_\bu_\bi_\br_\be_\bd'' and the
server does not support STARTTLS or there is an error in the TLS Handshake, the
-
- The Mutt Next Generation E-Mail Client 151
-
connection will fail. Setting this to ``_\be_\bn_\ba_\bb_\bl_\be_\bd'' will try to start TLS and
continue without TLS in case of an error. Muttng still needs to have SSL sup-
port enabled in order to use it.
+ _\b6_\b._\b4_\b._\b2_\b8_\b9 _\bs_\bm_\bt_\bp_\b__\bu_\bs_\be_\br
+
+ Type: string
+
+ Default: ''
+
+ Availability: SMTP
+
+ The Mutt Next Generation E-Mail Client 151
+
+ Defines the username to use with SMTP AUTH. Setting this variable will cause
+ Mutt-ng to attempt to use SMTP AUTH when sending.
+
_\b6_\b._\b4_\b._\b2_\b9_\b0 _\bs_\bo_\br_\bt
Type: sort order
This can be set to any value that ``_\b$_\bs_\bo_\br_\bt (section 6.4.290 , page 149)'' can,
except threads (in that case, Mutt-ng will just use date-sent). You can also
specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
+ come after reverse-. The last- prefix causes messages to be sorted against its
The Mutt Next Generation E-Mail Client 152
- come after reverse-. The last- prefix causes messages to be sorted against its
siblings by which has the last descendant, using the rest of sort_aux as an
ordering.
Default: ','
``_\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
The Mutt Next Generation E-Mail Client 153
- 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.295 ,
- page 151)'' as a separator.
+ 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
Type: number
- The Mutt Next Generation E-Mail Client 154
-
Default: 0
+ The Mutt Next Generation E-Mail Client 154
+
Availability: GNUTLS
This variable specifies the minimum acceptable prime size (in bits) for use in
This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
tion process.
- The Mutt Next Generation E-Mail Client 155
-
_\b6_\b._\b4_\b._\b3_\b0_\b5 _\bs_\bs_\bl_\b__\bu_\bs_\be_\bs_\by_\bs_\bt_\be_\bm_\bc_\be_\br_\bt_\bs
Type: boolean
+ The Mutt Next Generation E-Mail Client 155
+
Default: yes
Availability: SSL
%F
number of flagged messages *
- The Mutt Next Generation E-Mail Client 156
-
%h
local hostname
+ The Mutt Next Generation E-Mail Client 156
+
%l
size (in bytes) of the current mailbox *
%>X
right justify the rest of the string and pad with 'X'
- The Mutt Next Generation E-Mail Client 157
-
%|X
pad to the end of the line with 'X'
+ The Mutt Next Generation E-Mail Client 157
+
* = can be optionally printed if nonzero
Some of the above sequences can be used to optionally print a string if their
Default: yes
- The Mutt Next Generation E-Mail Client 158
-
With mailto: style links, a body as well as arbitrary header information may be
embedded. This may lead to (user) headers being overwriten without note if
``_\b$_\be_\bd_\bi_\bt_\b__\bh_\be_\ba_\bd_\be_\br_\bs (section 6.4.54 , page 92)'' is unset.
+ The Mutt Next Generation E-Mail Client 158
+
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
Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
- The Mutt Next Generation E-Mail Client 159
-
When non-empty and _\b$_\bs_\bt_\br_\bi_\bp_\b__\bw_\ba_\bs (section 6.4.312 , page 157) is _\bs_\be_\bt, mutt-ng
will remove this trailing part of the ``Subject'' line when replying if it
won't be empty afterwards.
+ The Mutt Next Generation E-Mail Client 159
+
_\b6_\b._\b4_\b._\b3_\b1_\b4 _\bs_\bt_\bu_\bf_\bf_\b__\bq_\bu_\bo_\bt_\be_\bd
Type: boolean
Default: no
- The Mutt Next Generation E-Mail Client 160
-
When _\bs_\be_\bt, Mutt-ng uses the date received rather than the date sent to thread
messages by subject.
+ The Mutt Next Generation E-Mail Client 160
+
_\b6_\b._\b4_\b._\b3_\b1_\b9 _\bt_\bi_\bl_\bd_\be
Type: boolean
Default: ''
- The Mutt Next Generation E-Mail Client 161
-
If _\bs_\be_\bt, this variable specifies the path of the trash folder where the mails
marked for deletion will be moved, instead of being irremediably purged.
+ The Mutt Next Generation E-Mail Client 161
+
N\bNo\bot\bte\be: When you delete a message in the trash folder, it is really deleted, so
that there is no way to recover mail.
_\b6_\b._\b4_\b._\b3_\b2_\b8 _\bu_\bs_\be_\b__\bd_\bo_\bm_\ba_\bi_\bn
- The Mutt Next Generation E-Mail Client 162
-
Type: boolean
Default: yes
+ The Mutt Next Generation E-Mail Client 162
+
When _\bs_\be_\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
tion) with the value of ``_\b$_\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be (section 6.4.89 , page 100)''. If _\bu_\bn_\bs_\be_\bt,
no addresses will be qualified.
Type: path
- The Mutt Next Generation E-Mail Client 163
-
Default: ''
Specifies the visual editor to invoke when the _\b~_\bv command is given in the
builtin editor.
+ The Mutt Next Generation E-Mail Client 163
+
_\b6_\b._\b4_\b._\b3_\b3_\b4 _\bw_\ba_\bi_\bt_\b__\bk_\be_\by
Type: boolean
Type: boolean
- The Mutt Next Generation E-Mail Client 164
-
Default: yes
Controls whether Mutt-ng writes out the Bcc header when preparing messages to
be sent. Exim users may wish to _\bu_\bn_\bs_\be_\bt this.
+ The Mutt Next Generation E-Mail Client 164
+
_\b6_\b._\b4_\b._\b3_\b3_\b9 _\bw_\br_\bi_\bt_\be_\b__\bi_\bn_\bc
Type: number
you're in an appropriate terminal). The default must be _\bu_\bn_\bs_\be_\bt to force in the
validity checking.
- The Mutt Next Generation E-Mail Client 165
-
_\b6_\b._\b4_\b._\b3_\b4_\b3 _\bx_\bt_\be_\br_\bm_\b__\bt_\bi_\bt_\bl_\be
Type: string
Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
+ The Mutt Next Generation E-Mail Client 165
+
Controls the format of the title bar of the xterm provided that
_\b$_\bx_\bt_\be_\br_\bm_\b__\bs_\be_\bt_\b__\bt_\bi_\bt_\bl_\be_\bs (section 6.4.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 ,
tings for this menu will affect the default bindings for all menus (except as
noted).
- The Mutt Next Generation E-Mail Client 166
-
bottom-page L move to the bottom of the page
current-bottom not bound move current entry to bottom of page
current-middle not bound move current entry to middle of page
top-page H move to the top of the page
what-key not bound display the keycode for a key press
+ The Mutt Next Generation E-Mail Client 166
+
_\b6_\b._\b5_\b._\b2 _\bi_\bn_\bd_\be_\bx
The Mutt Next Generation E-Mail Client 167
The following people have been very helpful to the development of Mutt-ng:
+ Christian Gall <cg@cgall.de>
+
Iain Lea <iain@bricbrac.de>
Andreas Kneib <akneib@gmx.net>
Elimar Riesebieter <riesebie@lxtec.de>
- _\b7_\b._\b2 _\bA_\bb_\bo_\bu_\bt _\bt_\bh_\bi_\bs _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt
-
The Mutt Next Generation E-Mail Client 176
+ _\b7_\b._\b2 _\bA_\bb_\bo_\bu_\bt _\bt_\bh_\bi_\bs _\bd_\bo_\bc_\bu_\bm_\be_\bn_\bt
+
This document was written in SGML, and then rendered using the sgml-tools pack-
age.
4.14.2 Authentication 61
4.15 NNTP Support (OPTIONAL) ........................................ 62
4.15.1 Again: Scoring 62
- 4.16 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 63
- 4.17 Start a WWW Browser on URLs (EXTERNAL) ......................... 63
- 4.18 Compressed folders Support (OPTIONAL) .......................... 64
- 4.18.1 Open a compressed mailbox for reading 64
- 4.18.2 Write a compressed mailbox 65
- 4.18.3 Append a message to a compressed mailbox 65
- 4.18.4 Encrypted folders 66
-
- 5. Mutt-ng's MIME Support ............................................... 66
+ 4.16 SMTP Support (OPTIONAL) ........................................ 63
+ 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 63
+ 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.19.2 Write a compressed mailbox 65
+ 4.19.3 Append a message to a compressed mailbox 66
+ 4.19.4 Encrypted folders 66
+
+ 5. Mutt-ng's MIME Support ............................................... 67
5.1 Using MIME in Mutt ............................................. 67
5.1.1 Viewing MIME messages in the pager 67
5.1.2 The Attachment Menu 67
- 5.1.3 The Compose Menu 67
+ 5.1.3 The Compose Menu 68
5.2 MIME Type configuration with mime.types ........................ 68
5.3 MIME Viewer configuration with mailcap ......................... 69
5.3.1 The Basics of the mailcap file 69
- 5.3.2 Secure use of mailcap 70
+ 5.3.2 Secure use of mailcap 71
5.3.3 Advanced mailcap Usage 71
5.3.4 Example mailcap files 74
5.4 MIME Autoview .................................................. 75
6.4.19 beep_new 86
6.4.20 bounce 86
6.4.21 bounce_delivered 86
- 6.4.22 braille_friendly 86
iii
+ 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.72 forward_format 98
6.4.73 forward_quote 98
6.4.74 from 98
- 6.4.75 gecos_mask 98
iv
+ 6.4.75 gecos_mask 98
6.4.76 hdrs 99
6.4.77 header 99
6.4.78 header_cache 99
6.4.125 mbox_type 112
6.4.126 menu_context 112
6.4.127 menu_move_off 112
- 6.4.128 menu_scroll 112
v
+ 6.4.128 menu_scroll 112
6.4.129 message_format 113
6.4.130 meta_key 113
6.4.131 metoo 113
6.4.178 pgp_encrypt_sign_command 125
6.4.179 pgp_entry_format 125
6.4.180 pgp_export_command 126
- 6.4.181 pgp_getkeys_command 126
vi
+ 6.4.181 pgp_getkeys_command 126
6.4.182 pgp_good_sign 126
6.4.183 pgp_ignore_subkeys 126
6.4.184 pgp_import_command 127
6.4.231 reply_regexp 137
6.4.232 reply_self 137
6.4.233 reply_to 137
- 6.4.234 resolve 138
vii
+ 6.4.234 resolve 138
6.4.235 reverse_alias 138
6.4.236 reverse_name 138
6.4.237 reverse_realname 138
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_auth_password 149
- 6.4.286 smtp_auth_username 150
- 6.4.287 smtp_host 150
+ 6.4.285 smtp_host 149
+ 6.4.286 smtp_pass 150
viii
- 6.4.288 smtp_port 150
- 6.4.289 smtp_use_tls 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.302 ssl_use_sslv2 154
6.4.303 ssl_use_sslv3 154
6.4.304 ssl_use_tlsv1 154
- 6.4.305 ssl_usesystemcerts 155
+ 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.337 wrapmargin 163
6.4.338 write_bcc 163
6.4.339 write_inc 164
- 6.4.340 xterm_icon 164
ix
+ 6.4.340 xterm_icon 164
6.4.341 xterm_leave 164
6.4.342 xterm_set_titles 164
- 6.4.343 xterm_title 165
+ 6.4.343 xterm_title 164
6.5 Functions ....................................................... 165
6.5.1 generic 165
6.5.2 index 166
7. Miscellany ............................................................ 173
7.1 Acknowledgments ................................................. 174
- 7.2 About this document ............................................. 175
+ 7.2 About this document ............................................. 176
x
projects / apps / madmutt.git / blobdiff