-<title>The Mutt E-Mail Client
-<author>by Michael Elkins <htmlurl url="mailto:me@cs.hmc.edu" name="<me@cs.hmc.edu>">
+<title>The Mutt-ng E-Mail Client
+<author>by Michael Elkins <htmlurl url="mailto:me@cs.hmc.edu" name="<me@cs.hmc.edu>"> and others.
fork from Mutt with the goal to fix all the little annoyances of Mutt, to
integrate all the Mutt patches that are floating around in the web, and to
add other new features. Features specific to Mutt-ng will be discussed in
an extra section. Don't be confused when most of the documentation talk about
fork from Mutt with the goal to fix all the little annoyances of Mutt, to
integrate all the Mutt patches that are floating around in the web, and to
add other new features. Features specific to Mutt-ng will be discussed in
an extra section. Don't be confused when most of the documentation talk about
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
+This section is intended as a brief overview of how to use Mutt-ng. There are
+many other features which are described elsewhere in the manual.
+<--
+There
is even more information available in the Mutt FAQ and various web
pages. See the <htmlurl url="http://www.mutt.org/mutt/"
name="Mutt Page"> for more details.
is even more information available in the Mutt FAQ and various web
pages. See the <htmlurl url="http://www.mutt.org/mutt/"
name="Mutt Page"> for more details.
Your local system administrator may have altered the defaults for your site.
You can always type ``?'' in any menu to display the current bindings.
Your local system administrator may have altered the defaults for your site.
You can always type ``?'' in any menu to display the current bindings.
-either the mutt man page or the <ref id="commandline" name="reference">.
+either the muttng man page or the <ref id="commandline" name="reference">.
+
+If you have used mutt in the past the easiest thing to have a proper
+configuration file is to source ~/.muttrc in ~/.muttngrc.
<sect1>Moving Around in Menus
<p>
Information is presented in menus, very similar to ELM. Here is a table
<sect1>Moving Around in Menus
<p>
Information is presented in menus, very similar to ELM. Here is a table
= or Home first-entry jump to the first entry
* or End last-entry jump to the last entry
q quit exit the current menu
= or Home first-entry jump to the first entry
* or End last-entry jump to the last entry
q quit exit the current menu
textual data such as email addresses or filenames. The keys used to move
around while editing are very similar to those of Emacs.
textual data such as email addresses or filenames. The keys used to move
around while editing are very similar to those of Emacs.
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the ``index'' in Mutt. The second mode is the display of the
+read in Mutt-ng. The first is the index of messages in the mailbox, which is
+called the ``index'' in Mutt-ng. The second mode is the display of the
message contents. This is called the ``pager.''
The next few sections describe the functions provided in each of these
message contents. This is called the ``pager.''
The next few sections describe the functions provided in each of these
/ search for a regular expression (pattern)
ESC / search backwards for a regular expression
\ toggle search pattern coloring
/ search for a regular expression (pattern)
ESC / search backwards for a regular expression
\ toggle search pattern coloring
one, it will accept and translate the ``standard'' nroff sequences for
bold and underline. These sequences are a series of either the letter,
backspace (^H), the letter again for bold or the letter, backspace,
one, it will accept and translate the ``standard'' nroff sequences for
bold and underline. These sequences are a series of either the letter,
backspace (^H), the letter again for bold or the letter, backspace,
in bold and underline respectively if your terminal supports them. If
not, you can use the bold and underline <ref id="color" name="color">
objects to specify a color or mono attribute for them.
Additionally, the internal pager supports the ANSI escape sequences for
in bold and underline respectively if your terminal supports them. If
not, you can use the bold and underline <ref id="color" name="color">
objects to specify a color or mono attribute for them.
Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
+character attributes. Mutt-ng translates them into the correct color and
+character settings. The sequences Mutt-ng supports are:
can also be used by an external <ref id="auto_view" name="autoview">
script for highlighting purposes. <bf/Note:/ If you change the colors for your
display, for example by changing the color associated with color2 for
can also be used by an external <ref id="auto_view" name="autoview">
script for highlighting purposes. <bf/Note:/ If you change the colors for your
display, for example by changing the color associated with color2 for
name="$pipe_decode">, <ref id="pipe_split"
name="$pipe_split">, <ref id="pipe_sep"
name="$pipe_sep"> and <ref id="wait_key"
name="$pipe_decode">, <ref id="pipe_split"
name="$pipe_split">, <ref id="pipe_sep"
name="$pipe_sep"> and <ref id="wait_key"
Asks for an external Unix command and executes it. The <ref
id="wait_key" name="$wait_key"> can be used to control
Asks for an external Unix command and executes it. The <ref
id="wait_key" name="$wait_key"> can be used to control
(presumably to let the user read the output of the command), based on
the return status of the named command.
(presumably to let the user read the output of the command), based on
the return status of the named command.
in greater detail in the next chapter <ref id="forwarding_mail"
name="``Forwarding and Bouncing Mail''">.
in greater detail in the next chapter <ref id="forwarding_mail"
name="``Forwarding and Bouncing Mail''">.
recipients to place on the ``To:'' header field. Next, it will ask
you for the ``Subject:'' field for the message, providing a default if
you are replying to or forwarding a message. See also <ref id="askcc"
name="$askcc">, <ref id="askbcc" name="$askbcc">, <ref
id="autoedit" name="$autoedit">, <ref id="bounce"
name="$bounce">, and <ref id="fast_reply"
recipients to place on the ``To:'' header field. Next, it will ask
you for the ``Subject:'' field for the message, providing a default if
you are replying to or forwarding a message. See also <ref id="askcc"
name="$askcc">, <ref id="askbcc" name="$askbcc">, <ref
id="autoedit" name="$autoedit">, <ref id="bounce"
name="$bounce">, and <ref id="fast_reply"
name="$editor"> on the message body. If the <ref id="edit_headers"
name="$edit_headers"> variable is set, the headers will be at
the top of the message in your editor. Any messages you are replying
name="$editor"> on the message body. If the <ref id="edit_headers"
name="$edit_headers"> variable is set, the headers will be at
the top of the message in your editor. Any messages you are replying
just as if you had used the <em/edit-fcc/ function in the <em/compose/ menu.
You can also attach files to your message by specifying<newline>
just as if you had used the <em/edit-fcc/ function in the <em/compose/ menu.
You can also attach files to your message by specifying<newline>
optional string to use as the description of the attached file.
When replying to messages, if you remove the <em/In-Reply-To:/ field from
optional string to use as the description of the attached file.
When replying to messages, if you remove the <em/In-Reply-To:/ field from
allows you to create a new message thread.
Also see <ref id="edit_headers" name="edit_headers">.
allows you to create a new message thread.
Also see <ref id="edit_headers" name="edit_headers">.
If you have told mutt to PGP encrypt a message, it will guide you
through a key selection process when you try to send the message.
If you have told mutt to PGP encrypt a message, it will guide you
through a key selection process when you try to send the message.
certified user ID matching one of the message recipients' mail
addresses. However, there may be situations in which there are
several keys, weakly certified user ID fields, or where no matching
certified user ID matching one of the message recipients' mail
addresses. However, there may be situations in which there are
several keys, weakly certified user ID fields, or where no matching
To use it, you'll have to obey certain restrictions. Most
important, you cannot use the <tt/Cc/ and <tt/Bcc/ headers. To tell
To use it, you'll have to obey certain restrictions. Most
important, you cannot use the <tt/Cc/ and <tt/Bcc/ headers. To tell
used in the <em/compose/ menu, the body of your message and attachments
are stored in the mailbox specified by the <ref id="postponed"
name="$postponed"> variable. This means that you can recall the
used in the <em/compose/ menu, the body of your message and attachments
are stored in the mailbox specified by the <ref id="postponed"
name="$postponed"> variable. This means that you can recall the
Once a message is postponed, there are several ways to resume it. From the
command line you can use the ``-p'' option, or if you <em/compose/ a new
Once a message is postponed, there are several ways to resume it. From the
command line you can use the ``-p'' option, or if you <em/compose/ a new
via NNTP. You can open a newsgroup with function ``change-newsgroup''
(default: i). Default newsserver can be obtained from <em/NNTPSERVER/
environment variable. Like other news readers, info about subscribed
via NNTP. You can open a newsgroup with function ``change-newsgroup''
(default: i). Default newsserver can be obtained from <em/NNTPSERVER/
environment variable. Like other news readers, info about subscribed
Mutt-ng is first invoked, it will attempt to read the ``system'' configuration
file (defaults set by your local system administrator), unless the ``-n'' <ref
id="commandline" name="command line"> option is specified. This file is
Mutt-ng is first invoked, it will attempt to read the ``system'' configuration
file (defaults set by your local system administrator), unless the ``-n'' <ref
id="commandline" name="command line"> option is specified. This file is
mutt try to load a file named <tt>.muttng/muttngrc</tt>.
<tt>.muttrc</tt> (or <tt>.muttngrc</tt> for Mutt-ng) is the file where you will
mutt try to load a file named <tt>.muttng/muttngrc</tt>.
<tt>.muttrc</tt> (or <tt>.muttngrc</tt> for Mutt-ng) is the file where you will
In addition, mutt supports version specific configuration files that are
parsed instead of the default files as explained above. For instance, if
your system has a <tt/Muttrc-0.88/ file in the system configuration
directory, and you are running version 0.88 of mutt, this file will be
In addition, mutt supports version specific configuration files that are
parsed instead of the default files as explained above. For instance, if
your system has a <tt/Muttrc-0.88/ file in the system configuration
directory, and you are running version 0.88 of mutt, this file will be
configuration file, if you have a file <tt/.muttrc-0.88.6/ in your home
directory, when you run mutt version 0.88.6, it will source this file
instead of the default <tt/.muttrc/ file. The version number is the
configuration file, if you have a file <tt/.muttrc-0.88.6/ in your home
directory, when you run mutt version 0.88.6, it will source this file
instead of the default <tt/.muttrc/ file. The version number is the
name="commands">. Each line of the file may contain one or more commands.
When multiple commands are used, they must be separated by a semicolon (;).
<tscreen><verb>
name="commands">. Each line of the file may contain one or more commands.
When multiple commands are used, they must be separated by a semicolon (;).
<tscreen><verb>
</verb></tscreen>
The hash mark, or pound sign
(``#''), is used as a ``comment'' character. You can use it to
</verb></tscreen>
The hash mark, or pound sign
(``#''), is used as a ``comment'' character. You can use it to
at the end of a line also in comments. This allows you to disable a command
split over multiple lines with only one ``#''.
<tscreen><verb>
# folder-hook . \
set realname="Michael \"MuttDude\" Elkins"
at the end of a line also in comments. This allows you to disable a command
split over multiple lines with only one ``#''.
<tscreen><verb>
# folder-hook . \
set realname="Michael \"MuttDude\" Elkins"
When testing your config files, beware the following caveat. The backslash
at the end of the commented line extends the current line with the next line
When testing your config files, beware the following caveat. The backslash
at the end of the commented line extends the current line with the next line
line1 ``continues'' until line4. however, the part after the # is a
comment which includes line3 and line4. line5 is a new line of its own and
line1 ``continues'' until line4. however, the part after the # is a
comment which includes line3 and line4. line5 is a new line of its own and
Usage: <tt/alias/ <em/key/ <em/address/ [ , <em/address/, ... ]
It's usually very cumbersome to remember or type out the address of someone
Usage: <tt/alias/ <em/key/ <em/address/ [ , <em/address/, ... ]
It's usually very cumbersome to remember or type out the address of someone
a short string to a full address.
<bf/Note:/ if you want to create an alias for a group (by specifying more than
a short string to a full address.
<bf/Note:/ if you want to create an alias for a group (by specifying more than
in a special file. The <tt/alias/ command can appear anywhere in
a configuration file, as long as this file is <ref id="source"
name="sourced">. Consequently, you can have multiple alias files, or
in a special file. The <tt/alias/ command can appear anywhere in
a configuration file, as long as this file is <ref id="source"
name="sourced">. Consequently, you can have multiple alias files, or
function can use only one file, the one pointed to by the <ref
id="alias_file" name="$alias_file"> variable (which is
<tt>˜/.muttrc</tt> by default). This file is not special either,
function can use only one file, the one pointed to by the <ref
id="alias_file" name="$alias_file"> variable (which is
<tt>˜/.muttrc</tt> by default). This file is not special either,
order for the new aliases to take effect you need to explicitly <ref
id="source" name="source"> this file too.
For example:
<tscreen><verb>
order for the new aliases to take effect you need to explicitly <ref
id="source" name="source"> this file too.
For example:
<tscreen><verb>
<tag/generic/
This is not a real menu, but is used as a fallback for all of the other
menus except for the pager and editor modes. If a key is not defined in
<tag/generic/
This is not a real menu, but is used as a fallback for all of the other
menus except for the pager and editor modes. If a key is not defined in
you to bind a key to a certain function in multiple menus instead of having
multiple bind statements to accomplish the same task.
<tag/alias/
you to bind a key to a certain function in multiple menus instead of having
multiple bind statements to accomplish the same task.
<tag/alias/
Usage: <tt/macro/ <em/menu/ <em/key/ <em/sequence/ [ <em/description/ ]
Macros are useful when you would like a single key to perform a series of
Usage: <tt/macro/ <em/menu/ <em/key/ <em/sequence/ [ <em/description/ ]
Macros are useful when you would like a single key to perform a series of
you had typed <em/sequence/. So if you have a common sequence of commands
you type, you can create a macro to execute those commands with a single
key.
you had typed <em/sequence/. So if you have a common sequence of commands
you type, you can create a macro to execute those commands with a single
key.
work regardless of the current key bindings, so they are not dependent on
the user having particular key definitions. This makes them more robust
and portable, and also facilitates defining of macros in files used by more
work regardless of the current key bindings, so they are not dependent on
the user having particular key definitions. This makes them more robust
and portable, and also facilitates defining of macros in files used by more
Optionally you can specify a descriptive text after <em/sequence/,
which is shown in the help screens.
Optionally you can specify a descriptive text after <em/sequence/,
which is shown in the help screens.
Usage: <tt/color/ index <em/foreground/ <em/background/ <em/pattern/<newline>
Usage: <tt/uncolor/ index <em/pattern/ [ <em/pattern/ ... ]<newline>
Usage: <tt/color/ index <em/foreground/ <em/background/ <em/pattern/<newline>
Usage: <tt/uncolor/ index <em/pattern/ [ <em/pattern/ ... ]<newline>
color scheme. To define the color of an object (type of information), you
must specify both a foreground color <bf/and/ a background color (it is not
possible to only specify one or the other).
color scheme. To define the color of an object (type of information), you
must specify both a foreground color <bf/and/ a background color (it is not
possible to only specify one or the other).
-<item>bold (hiliting bold patterns in the body of messages)
-<item>error (error messages printed by Mutt)
+<item>bold (highlighting bold patterns in the body of messages)
+<item>error (error messages printed by Mutt-ng)
<item>header (match <em/regexp/ in the message header)
<item>hdrdefault (default color of the message header in the pager)
<item>index (match <em/pattern/ in the message index)
<item>header (match <em/regexp/ in the message header)
<item>hdrdefault (default color of the message header in the pager)
<item>index (match <em/pattern/ in the message index)
<item>quoted (text matching <ref id="quote_regexp"
name="$quote_regexp"> in the body of a message)
<item>quoted1, quoted2, ..., quoted<bf/N/ (higher levels of quoting)
<item>quoted (text matching <ref id="quote_regexp"
name="$quote_regexp"> in the body of a message)
<item>quoted1, quoted2, ..., quoted<bf/N/ (higher levels of quoting)
<item>signature
<item>status (mode lines used to display info about the mailbox or message)
<item>tilde (the ``˜'' used to pad blank lines in the pager)
<item>tree (thread tree drawn in the message index and attachment menu)
<item>signature
<item>status (mode lines used to display info about the mailbox or message)
<item>tilde (the ``˜'' used to pad blank lines in the pager)
<item>tree (thread tree drawn in the message index and attachment menu)
If your terminal supports it, the special keyword <em/default/ can be
used as a transparent color. The value <em/brightdefault/ is also valid.
If your terminal supports it, the special keyword <em/default/ can be
used as a transparent color. The value <em/brightdefault/ is also valid.
the <em/COLORFGBG/ environment variable to the default colors of your
terminal for this to work; for example (for Bourne-like shells):
the <em/COLORFGBG/ environment variable to the default colors of your
terminal for this to work; for example (for Bourne-like shells):
specified in the color command for it to be removed. The pattern ``*'' is
a special token which means to clear the color index list of all entries.
specified in the color command for it to be removed. The pattern ``*'' is
a special token which means to clear the color index list of all entries.
-Mutt also recognizes the keywords <em/color0/, <em/color1/, …,
+Mutt-ng also recognizes the keywords <em/color0/, <em/color1/, …,
<em/color/<bf/N-1/ (<bf/N/ being the number of colors supported
by your terminal). This is useful when you remap the colors for your
display (for example by changing the color associated with <em/color2/
<em/color/<bf/N-1/ (<bf/N/ being the number of colors supported
by your terminal). This is useful when you remap the colors for your
display (for example by changing the color associated with <em/color2/
``content-''. ``ignore *'' will ignore all headers.
To remove a previously added token from the list, use the ``unignore'' command.
``content-''. ``ignore *'' will ignore all headers.
To remove a previously added token from the list, use the ``unignore'' command.
For example, if you do ``ignore x-'' it is possible to ``unignore x-mailer''.
``unignore *'' will remove all tokens from the ignore list.
For example, if you do ``ignore x-'' it is possible to ``unignore x-mailer''.
``unignore *'' will remove all tokens from the ignore list.
Usage: <tt/[un]lists/ <em/regexp/ [ <em/regexp/ ... ]<newline>
Usage: <tt/[un]subscribe/ <em/regexp/ [ <em/regexp/ ... ]
Usage: <tt/[un]lists/ <em/regexp/ [ <em/regexp/ ... ]<newline>
Usage: <tt/[un]subscribe/ <em/regexp/ [ <em/regexp/ ... ]
mailing lists">. In order to take advantage of them, you must
specify which addresses belong to mailing lists, and which mailing
lists you are subscribed to. Once you have done this, the <ref
mailing lists">. In order to take advantage of them, you must
specify which addresses belong to mailing lists, and which mailing
lists you are subscribed to. Once you have done this, the <ref
of the Mail-Followup-To header is controlled by the <ref id="followup_to"
name="$followup_to"> configuration variable.
of the Mail-Followup-To header is controlled by the <ref id="followup_to"
name="$followup_to"> configuration variable.
of known and subscribed mailing lists. Every subscribed mailing
list is known. To mark a mailing list as known, use the ``lists''
command. To mark it as subscribed, use ``subscribe''.
of known and subscribed mailing lists. Every subscribed mailing
list is known. To mark a mailing list as known, use the ``lists''
command. To mark it as subscribed, use ``subscribe''.
give a portion of the list's e-mail address.
Specify as much of the address as you need to to remove ambiguity. For
give a portion of the list's e-mail address.
Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addresssed to <em/mutt-users@mutt.org/. So, to tell Mutt that this is a
+example, if you've subscribed to the Mutt-ng mailing list, you will receive mail
+addressed to <em/mutt-users@mutt.org/. So, to tell Mutt-ng that this is a
mailing list, you could add ``lists mutt-users'' to your
initialization file. To tell mutt that you are subscribed to it,
add ``subscribe mutt-users'' to your initialization file instead.
mailing list, you could add ``lists mutt-users'' to your
initialization file. To tell mutt that you are subscribed to it,
add ``subscribe mutt-users'' to your initialization file instead.
<p>
Pressing TAB in the directory browser will bring up a menu showing the files
specified by the <tt/mailboxes/ command, and indicate which contain new
<p>
Pressing TAB in the directory browser will bring up a menu showing the files
specified by the <tt/mailboxes/ command, and indicate which contain new
command line with the <tt/-y/ option.
The ``unmailboxes'' command is used to remove a token from the list
command line with the <tt/-y/ option.
The ``unmailboxes'' command is used to remove a token from the list
<p>
<bf/Note:/ new mail is detected by comparing the last modification time to
the last access time. Utilities like <tt/biff/ or <tt/frm/ or any other
<p>
<bf/Note:/ new mail is detected by comparing the last modification time to
the last access time. Utilities like <tt/biff/ or <tt/frm/ or any other
for that mailbox if they do not properly reset the access time. Backup
tools are another common reason for updated access times.
<p>
for that mailbox if they do not properly reset the access time. Backup
tools are another common reason for updated access times.
<p>
<bf/Note:/ space characters are <em/not/ allowed between the keyword and
the colon (``:''). The standard for electronic mail (RFC822) says that
<bf/Note:/ space characters are <em/not/ allowed between the keyword and
the colon (``:''). The standard for electronic mail (RFC822) says that
If you would like to add a header field to a single message, you should
either set the <ref id="edit_headers" name="edit_headers"> variable,
If you would like to add a header field to a single message, you should
either set the <ref id="edit_headers" name="edit_headers"> variable,
Usage: <tt/fcc-hook/ [!]<em/pattern/ <em/mailbox/
This command is used to save outgoing mail in a mailbox other than
Usage: <tt/fcc-hook/ [!]<em/pattern/ <em/mailbox/
This command is used to save outgoing mail in a mailbox other than
message recipients for the first matching <em/regexp/ and uses <em/mailbox/
as the default Fcc: mailbox. If no match is found the message will be saved
to <ref id="record" name="$record"> mailbox.
message recipients for the first matching <em/regexp/ and uses <em/mailbox/
as the default Fcc: mailbox. If no match is found the message will be saved
to <ref id="record" name="$record"> mailbox.
When encrypting messages with PGP or OpenSSL, you may want to associate a certain
key with a given e-mail address automatically, either because the
recipient's public key can't be deduced from the destination address,
When encrypting messages with PGP or OpenSSL, you may want to associate a certain
key with a given e-mail address automatically, either because the
recipient's public key can't be deduced from the destination address,
normally use. The crypt-hook command provides a method by which you can
specify the ID of the public key to be used when encrypting messages to
a certain recipient.
normally use. The crypt-hook command provides a method by which you can
specify the ID of the public key to be used when encrypting messages to
a certain recipient.
By defining your spam patterns with the <tt/spam/ and <tt/nospam/
commands, you can <em/limit/, <em/search/, and <em/sort/ your
mail based on its spam attributes, as determined by the external
By defining your spam patterns with the <tt/spam/ and <tt/nospam/
commands, you can <em/limit/, <em/search/, and <em/sort/ your
mail based on its spam attributes, as determined by the external
DCC report indicate the checksum used -- in this case, ``Fuz2''.)
If the $spam_separator variable is unset, then each
DCC report indicate the checksum used -- in this case, ``Fuz2''.)
If the $spam_separator variable is unset, then each
joined <em/format/ strings, you'll get only the last one to match.
The spam tag is what will be displayed in the index when you use
joined <em/format/ strings, you'll get only the last one to match.
The spam tag is what will be displayed in the index when you use
considered to be an executable program from which to read input (eg.
<tt>source ~/bin/myscript|</tt>).
considered to be an executable program from which to read input (eg.
<tt>source ~/bin/myscript|</tt>).
To only set the <ref id="imap_mail_check"
name="<$imap_mail_check"> when the system's SVN
is recent enough to have it:
<tscreen><verb>
ifdef imap_mail_check 'set imap_mail_check=300'
To only set the <ref id="imap_mail_check"
name="<$imap_mail_check"> when the system's SVN
is recent enough to have it:
<tscreen><verb>
ifdef imap_mail_check 'set imap_mail_check=300'
<ref id="patterns" name="patterns"> must be specified
using regular expressions (regexp) in the ``POSIX extended'' syntax (which
is more or less the syntax used by egrep and GNU awk). For your
<ref id="patterns" name="patterns"> must be specified
using regular expressions (regexp) in the ``POSIX extended'' syntax (which
is more or less the syntax used by egrep and GNU awk). For your
precedence over alternation. A whole subexpression may be enclosed in
parentheses to override these precedence rules.
precedence over alternation. A whole subexpression may be enclosed in
parentheses to override these precedence rules.
(limit, tag-pattern, delete-pattern, etc.). There are several ways to select
messages:
(limit, tag-pattern, delete-pattern, etc.). There are several ways to select
messages:
~G cryptographically encrypted messages
~H EXPR messages with a spam attribute matching EXPR
~h EXPR messages which contain EXPR in the message header
~G cryptographically encrypted messages
~H EXPR messages with a spam attribute matching EXPR
~h EXPR messages which contain EXPR in the message header
~i ID message which match ID in the ``Message-ID'' field
~L EXPR message is either originated or received by EXPR
~l message is addressed to a known mailing list
~i ID message which match ID in the ``Message-ID'' field
~L EXPR message is either originated or received by EXPR
~l message is addressed to a known mailing list
-~v message is part of a collapsed thread.
-~V cryptographically verified messages
+~v message is part of a collapsed thread.
+~V cryptographically verified messages
+~w EXPR messages which contain EXPR in the `Newsgroups' field
+ (if compiled with NNTP support)
~x EXPR messages which contain EXPR in the `References' field
~y EXPR messages which contain EXPR in the `X-Label' field
~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
~x EXPR messages which contain EXPR in the `References' field
~y EXPR messages which contain EXPR in the `X-Label' field
~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
-~= duplicated messages (see $duplicate_threads)
-~$ unreferenced messages (requires threaded view)
-~* ``From'' contains realname and (syntactically) valid
- address (excluded are addresses matching against
- alternates or any alias)
+~= duplicated messages (see $duplicate_threads)
+~$ unreferenced messages (requires threaded view)
+~* ``From'' contains realname and (syntactically) valid
+ address (excluded are addresses matching against
+ alternates or any alias)
</verb></tscreen>
Where EXPR, USER, ID, and SUBJECT are
<ref id="regexp" name="regular expressions">. Special attention has to be
made when using regular expressions inside of patterns. Specifically,
</verb></tscreen>
Where EXPR, USER, ID, and SUBJECT are
<ref id="regexp" name="regular expressions">. Special attention has to be
made when using regular expressions inside of patterns. Specifically,
which is normally used for quoting. If it is your intention to use a
backslash in the regular expression, you will need to use two backslashes
instead (\\).
which is normally used for quoting. If it is your intention to use a
backslash in the regular expression, you will need to use two backslashes
instead (\\).
Note that if a regular expression contains parenthesis, or a veritical bar
("|"), you <bf/must/ enclose the expression in double or single quotes since
Note that if a regular expression contains parenthesis, or a veritical bar
("|"), you <bf/must/ enclose the expression in double or single quotes since
<bf/Absolute/. Dates <bf/must/ be in DD/MM/YY format (month and year are
optional, defaulting to the current month and year). An example of a valid
<bf/Absolute/. Dates <bf/must/ be in DD/MM/YY format (month and year are
optional, defaulting to the current month and year). An example of a valid
matching a pattern, use the tag-pattern function, which is bound to
``shift-T'' by default. Or you can select individual messages by
hand using the ``tag-message'' function, which is bound to ``t'' by
matching a pattern, use the tag-pattern function, which is bound to
``shift-T'' by default. Or you can select individual messages by
hand using the ``tag-message'' function, which is bound to ``t'' by
In <ref id="macro" name="macros"> or <ref id="push" name="push"> commands,
you can use the ``tag-prefix-cond'' operator. If there are no tagged
messages, mutt will "eat" the rest of the macro to abort it's execution.
In <ref id="macro" name="macros"> or <ref id="push" name="push"> commands,
you can use the ``tag-prefix-cond'' operator. If there are no tagged
messages, mutt will "eat" the rest of the macro to abort it's execution.
A <em/hook/ is a concept borrowed from the EMACS editor which allows you to
execute arbitrary commands before performing some operation. For example,
you may wish to tailor your configuration based upon which mailbox you are
A <em/hook/ is a concept borrowed from the EMACS editor which allows you to
execute arbitrary commands before performing some operation. For example,
you may wish to tailor your configuration based upon which mailbox you are
consists of a <ref id="regexp" name="regular expression"> or
<ref id="patterns" name="pattern"> along with a
configuration option/command. See
consists of a <ref id="regexp" name="regular expression"> or
<ref id="patterns" name="pattern"> along with a
configuration option/command. See
language for matching messages in hook commands. This works in
exactly the same way as it would when <em/limiting/ or
<em/searching/ the mailbox, except that you are restricted to those
language for matching messages in hook commands. This works in
exactly the same way as it would when <em/limiting/ or
<em/searching/ the mailbox, except that you are restricted to those
For example, if you wanted to set your return address based upon sending
mail to a specific address, you could do something like:
<tscreen><verb>
For example, if you wanted to set your return address based upon sending
mail to a specific address, you could do something like:
<tscreen><verb>
</verb></tscreen>
which would execute the given command when sending mail to
<em/me@cs.hmc.edu/.
However, it is not required that you write the pattern to match using the
full searching language. You can still specify a simple <em/regular
</verb></tscreen>
which would execute the given command when sending mail to
<em/me@cs.hmc.edu/.
However, it is not required that you write the pattern to match using the
full searching language. You can still specify a simple <em/regular
pattern into the full language, using the translation specified by the
<ref id="default_hook" name="$default_hook"> variable. The
pattern is translated at the time the hook is declared, so the value of
pattern into the full language, using the translation specified by the
<ref id="default_hook" name="$default_hook"> variable. The
pattern is translated at the time the hook is declared, so the value of
<tscreen><verb>
sidebar-scroll-up Scrolls the mailbox list up 1 page
sidebar-scroll-down Scrolls the mailbox list down 1 page
<tscreen><verb>
sidebar-scroll-up Scrolls the mailbox list up 1 page
sidebar-scroll-down Scrolls the mailbox list down 1 page
-sidebar-next Hilights the next mailbox
-sidebar-next-new Hilights the next mailbox with new mail
-sidebar-previous Hilights the previous mailbox
-sidebar-open Opens the currently hilighted mailbox
+sidebar-next Highlights the next mailbox
+sidebar-next-new Highlights the next mailbox with new mail
+sidebar-previous Highlights the previous mailbox
+sidebar-open Opens the currently highlighted mailbox
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
using a simple interface. Using the <ref id="query_command"
name="$query_command"> variable, you specify the wrapper
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
using a simple interface. Using the <ref id="query_command"
name="$query_command"> variable, you specify the wrapper
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
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
name="$mbox_type"> variable.
<bf/mbox/. This is the most widely used mailbox format for UNIX. All
name="$mbox_type"> variable.
<bf/mbox/. This is the most widely used mailbox format for UNIX. All
<bf/MH/. A radical departure from <em/mbox/ and <em/MMDF/, a mailbox
consists of a directory and each message is stored in a separate file.
The filename indicates the message number (however, this is may not
<bf/MH/. A radical departure from <em/mbox/ and <em/MMDF/, a mailbox
consists of a directory and each message is stored in a separate file.
The filename indicates the message number (however, this is may not
renamed with a comma (,) prepended to the filename. <bf/Note:/ Mutt
detects this type of mailbox by looking for either <tt/.mh_sequences/
or <tt/.xmhcache/ (needed to distinguish normal directories from MH
renamed with a comma (,) prepended to the filename. <bf/Note:/ Mutt
detects this type of mailbox by looking for either <tt/.mh_sequences/
or <tt/.xmhcache/ (needed to distinguish normal directories from MH
<item>! -- refers to your <ref id="spoolfile" name="$spoolfile"> (incoming) mailbox
<item>> -- refers to your <ref id="mbox" name="$mbox"> file
<item>< -- refers to your <ref id="record" name="$record"> file
<item>! -- refers to your <ref id="spoolfile" name="$spoolfile"> (incoming) mailbox
<item>> -- refers to your <ref id="mbox" name="$mbox"> file
<item>< -- refers to your <ref id="record" name="$record"> file
<item>- or !! -- refers to the file you've last visited
<item>˜ -- refers to your home directory
<item>= or + -- refers to your <ref id="folder" name="$folder"> directory
<item>- or !! -- refers to the file you've last visited
<item>˜ -- refers to your home directory
<item>= or + -- refers to your <ref id="folder" name="$folder"> directory
amounts of mail easier. The first thing you must do is to let Mutt
know what addresses you consider to be mailing lists (technically
this does not have to be a mailing list, but that is what it is most
amounts of mail easier. The first thing you must do is to let Mutt
know what addresses you consider to be mailing lists (technically
this does not have to be a mailing list, but that is what it is most
accomplished through the use of the <ref id="lists"
name="lists and subscribe"> commands in your muttrc.
accomplished through the use of the <ref id="lists"
name="lists and subscribe"> commands in your muttrc.
things, the first of which is the ability to show the name of a list
through which you received a message (i.e., of a subscribed list) in
the <em/index/ menu display. This is useful to distinguish between
things, the first of which is the ability to show the name of a list
through which you received a message (i.e., of a subscribed list) in
the <em/index/ menu display. This is useful to distinguish between
known mailing list addresses instead of all recipients (except as
specified by <tt/Mail-Followup-To/, see below).
known mailing list addresses instead of all recipients (except as
specified by <tt/Mail-Followup-To/, see below).
a message to a list of recipients which includes one or several
subscribed mailing lists, and if the <ref id="followup_to"
name="$followup_to"> option is set, mutt will generate
a message to a list of recipients which includes one or several
subscribed mailing lists, and if the <ref id="followup_to"
name="$followup_to"> option is set, mutt will generate
in the list of recipients in the <tt/Mail-Followup-To/.
Note that, when header editing is enabled, you can create a
in the list of recipients in the <tt/Mail-Followup-To/.
Note that, when header editing is enabled, you can create a
than the author of 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''
than the author of 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''
variable to help decide which address to use. If set to <em/ask-yes/ or
<em/ask-no/, you will be
prompted as to whether or not you would like to use the address given in
variable to help decide which address to use. If set to <em/ask-yes/ or
<em/ask-no/, you will be
prompted as to whether or not you would like to use the address given in
individually). The <ref id="index_format"
name="$index_format"> variable's ``%y'' and
``%Y'' escapes can be used to expand ``X-Label:'' fields in the
individually). The <ref id="index_format"
name="$index_format"> variable's ``%y'' and
``%Y'' escapes can be used to expand ``X-Label:'' fields in the
``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.
``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.
<ref id="threads" name="threads">. 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 graphically. If you've ever
<ref id="threads" name="threads">. 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 graphically. If you've ever
-Mutt has the ability to dynamically restructure threads that are broken
-either by misconfigured software or bad behaviour from some
+Mutt-ng has the ability to dynamically restructure threads that are broken
+either by misconfigured software or bad behavior from some
correspondents. This allows to clean your mailboxes formats) from these
annoyances which make it hard to follow a discussion.
correspondents. This allows to clean your mailboxes formats) from these
annoyances which make it hard to follow a discussion.
Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
"References:" headers when replying to a message. This results in broken
Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
"References:" headers when replying to a message. This results in broken
threading.
You can fix this by tagging the reply, then moving to the parent message
and using the ``link-threads'' function (bound to & by default). The
reply will then be connected to this "parent" message.
threading.
You can fix this by tagging the reply, then moving to the parent message
and using the ``link-threads'' function (bound to & by default). The
reply will then be connected to this "parent" message.
script with the <em/--enable-pop/ flag), it has the ability to work
with mailboxes located on a remote POP3 server and fetch mail for local
browsing.
script with the <em/--enable-pop/ flag), it has the ability to work
with mailboxes located on a remote POP3 server and fetch mail for local
browsing.
<tt>pop://username@popserver[:port]/</tt>.
Polling for new mail is more expensive over POP3 than locally. For this
<tt>pop://username@popserver[:port]/</tt>.
Polling for new mail is more expensive over POP3 than locally. For this
controlled by the
<ref id="pop_checkinterval" name="$pop_checkinterval">
variable, which defaults to every 60 seconds.
controlled by the
<ref id="pop_checkinterval" name="$pop_checkinterval">
variable, which defaults to every 60 seconds.
script with the <em/--with-ssl/ flag), connections to POP3 servers
can be encrypted. This naturally requires that the server supports
SSL encrypted connections. To access a folder with POP3/SSL, you should
script with the <em/--with-ssl/ flag), connections to POP3 servers
can be encrypted. This naturally requires that the server supports
SSL encrypted connections. To access a folder with POP3/SSL, you should
(default: G). It allows to connect to <ref id="pop_host"
name="pop_host">, fetch all your new mail and place it in the
local <ref id="spoolfile" name="spoolfile">. After this
(default: G). It allows to connect to <ref id="pop_host"
name="pop_host">, fetch all your new mail and place it in the
local <ref id="spoolfile" name="spoolfile">. After this
<bf/Note:/ If you only need to fetch all messages to local mailbox
you should consider using a specialized program, such as <htmlurl
<bf/Note:/ If you only need to fetch all messages to local mailbox
you should consider using a specialized program, such as <htmlurl
script with the <em/--enable-imap/ flag), it has the ability to work
with folders located on a remote IMAP server.
script with the <em/--enable-imap/ flag), it has the ability to work
with folders located on a remote IMAP server.
server, you should use <tt>imap://imapserver/path/to/folder</tt> where
<tt>path/to/folder</tt> is the path of the folder you want to access.
server, you should use <tt>imap://imapserver/path/to/folder</tt> where
<tt>path/to/folder</tt> is the path of the folder you want to access.
script with the <em/--with-ssl/ flag), connections to IMAP servers
can be encrypted. This naturally requires that the server supports
SSL encrypted connections. To access a folder with IMAP/SSL, you should
use <tt>imaps://[username@]imapserver[:port]/path/to/folder</tt> as your
folder path.
script with the <em/--with-ssl/ flag), connections to IMAP servers
can be encrypted. This naturally requires that the server supports
SSL encrypted connections. To access a folder with IMAP/SSL, you should
use <tt>imaps://[username@]imapserver[:port]/path/to/folder</tt> as your
folder path.
GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
NTLM authentication for you poor exchange users out there, but it has
yet to be integrated into the main tree). There is also support for
GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
NTLM authentication for you poor exchange users out there, but it has
yet to be integrated into the main tree). There is also support for
option if you have it. To use it, you must have the Cyrus SASL library
installed on your system and compile mutt with the <em/--with-sasl/ flag.
<p>
option if you have it. To use it, you must have the Cyrus SASL library
installed on your system and compile mutt with the <em/--with-sasl/ flag.
<p>
in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
There are a few variables which control authentication:
in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
There are a few variables which control authentication:
<item><ref id="imap_user" name="$imap_user"> - controls
the username under which you request authentication on the IMAP server,
for all authenticators. This is overridden by an explicit username in
<item><ref id="imap_user" name="$imap_user"> - controls
the username under which you request authentication on the IMAP server,
for all authenticators. This is overridden by an explicit username in
<tt/{user@host}/).
<item><ref id="imap_pass" name="$imap_pass"> - a
password which you may preset, used by all authentication methods where
<tt/{user@host}/).
<item><ref id="imap_pass" name="$imap_pass"> - a
password which you may preset, used by all authentication methods where
<em/configure/ script with the <em/--enable-compressed/ flag), Mutt
can open folders stored in an arbitrary format, provided that the user
has a script to convert from/to this format to one of the accepted.
<em/configure/ script with the <em/--enable-compressed/ flag), Mutt
can open folders stored in an arbitrary format, provided that the user
has a script to convert from/to this format to one of the accepted.
the accepted formats. In particular, if the file is empty, mutt
supposes it is not compressed. This is important because it allows the
use of programs that do not have well defined extensions. Just use
the accepted formats. In particular, if the file is empty, mutt
supposes it is not compressed. This is important because it allows the
use of programs that do not have well defined extensions. Just use
directory, where it can be read by your system administrator. So think
about the security aspects of this.
directory, where it can be read by your system administrator. So think
about the security aspects of this.
MIME MUA. Every effort has been made to provide the functionality that
the discerning MIME user requires, and the conformance to the standards
MIME MUA. Every effort has been made to provide the functionality that
the discerning MIME user requires, and the conformance to the standards
-wherever possible. When configuring Mutt for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
+wherever possible. When configuring Mutt-ng for MIME, there are two extra
+types of configuration files which Mutt-ng uses. One is the
<tt/mime.types/ file, which contains the mapping of file extensions to
IANA MIME types. The other is the <tt/mailcap/ file, which specifies
the external commands to use for handling specific MIME types.
<sect1>Using MIME in Mutt
<p>
<tt/mime.types/ file, which contains the mapping of file extensions to
IANA MIME types. The other is the <tt/mailcap/ file, which specifies
the external commands to use for handling specific MIME types.
<sect1>Using MIME in Mutt
<p>
pager (while viewing a message), the attachment menu and the compose
menu.
<sect2>Viewing MIME messages in the pager
<p>
When you select a message from the index and view it in the pager, Mutt
pager (while viewing a message), the attachment menu and the compose
menu.
<sect2>Viewing MIME messages in the pager
<p>
When you select a message from the index and view it in the pager, Mutt
a number of MIME types, including <tt>text/plain, text/enriched,
message/rfc822, and message/news</tt>. In addition, the export
a number of MIME types, including <tt>text/plain, text/enriched,
message/rfc822, and message/news</tt>. In addition, the export
attachment, and the <tt/Encoding/ is one of
<tt>7bit/8bit/quoted-printable/base64/binary</tt>.
attachment, and the <tt/Encoding/ is one of
<tt>7bit/8bit/quoted-printable/base64/binary</tt>.
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or cancelling) the message. It can be toggled with the
+The '-' denotes that Mutt-ng will delete the file after sending (or
+postponing, or canceling) the message. It can be toggled with the
<tt/toggle-unlink/ command (default: u). The next field is the MIME
content-type, and can be changed with the <tt/edit-type/ command
(default: ^T). The next field is the encoding for the attachment,
<tt/toggle-unlink/ command (default: u). The next field is the MIME
content-type, and can be changed with the <tt/edit-type/ command
(default: ^T). The next field is the encoding for the attachment,
personal mime.types file at <tt>${HOME}/.mime.types</tt>, and then
the system mime.types file at <tt>/usr/local/share/mutt/mime.types</tt> or
<tt>/etc/mime.types</tt>
personal mime.types file at <tt>${HOME}/.mime.types</tt>, and then
the system mime.types file at <tt>/usr/local/share/mutt/mime.types</tt> or
<tt>/etc/mime.types</tt>
-information, Mutt will assume that the file is plain text, and mark it
-as <tt>text/plain</tt>. If the file contains binary information, then Mutt will
+information, Mutt-ng will assume that the file is plain text, and mark it
+as <tt>text/plain</tt>. If the file contains binary information, then Mutt-ng will
command from the compose menu (default: ^T). The MIME type is actually a
major mime type followed by the sub-type, separated by a '/'. 6 major
types: application, text, image, video, audio, and model have been approved
command from the compose menu (default: ^T). The MIME type is actually a
major mime type followed by the sub-type, separated by a '/'. 6 major
types: application, text, image, video, audio, and model have been approved
appropriate entry is found in the mime.types file. It also recognises 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
appropriate entry is found in the mime.types file. It also recognises 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
specific format specified in Appendix A of RFC 1524. This file format
is commonly referred to as the mailcap format. Many MIME compliant
programs utilize the mailcap format, allowing you to specify handling
for all MIME types in one place for all programs. Programs known to
use this format include Netscape, XMosaic, lynx and metamail.
specific format specified in Appendix A of RFC 1524. This file format
is commonly referred to as the mailcap format. Many MIME compliant
programs utilize the mailcap format, allowing you to specify handling
for all MIME types in one place for all programs. Programs known to
use this format include Netscape, XMosaic, lynx and metamail.
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
+In order to handle various MIME types that Mutt-ng can not handle
+internally, Mutt-ng parses a series of external configuration files to
The view command is a Unix command for viewing the type specified. There
are two different types of commands supported. The default is to send
the body of the MIME message to the command on stdin. You can change
The view command is a Unix command for viewing the type specified. There
are two different types of commands supported. The default is to send
the body of the MIME message to the command on stdin. You can change
-this behaviour by using %s as a parameter to your view command.
-This will cause Mutt to save the body of the MIME message to a temporary
+this behavior by using %s as a parameter to your view command.
+This will cause Mutt-ng to save the body of the MIME message to a temporary
terminal to the view program until the program quits, at which time Mutt
will remove the temporary file if it exists.
terminal to the view program until the program quits, at which time Mutt
will remove the temporary file if it exists.
-The interpretion of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
+The interpretation of shell meta-characters embedded in MIME parameters
+can lead to security problems in general. Mutt-ng tries to quote parameters
in expansion of %s syntaxes properly, and avoids risky characters by
substituting them, see the <ref id="mailcap_sanitize"
name="mailcap_sanitize"> variable.
in expansion of %s syntaxes properly, and avoids risky characters by
substituting them, see the <ref id="mailcap_sanitize"
name="mailcap_sanitize"> variable.
of it. Therefore you should pay attention to the following rules:
<em/Keep the %-expandos away from shell quoting./
of it. Therefore you should pay attention to the following rules:
<em/Keep the %-expandos away from shell quoting./
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 to fix
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 to fix
<p>
In addition to the required content-type and view command fields, you
can add semi-colon ';' separated fields to set flags and other options.
<p>
In addition to the required content-type and view command fields, you
can add semi-colon ';' separated fields to set flags and other options.
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt to invoke a pager (either the internal
+This flag tells Mutt-ng that the command passes possibly large amounts of
+text on stdout. This causes Mutt-ng to invoke a pager (either the internal
is interactive. One could use this to replace the pipe to <tt>more</tt>
in the <tt>lynx -dump</tt> example in the Basic section:
<tscreen><verb>
text/html; lynx -dump %s ; copiousoutput
</verb></tscreen>
This will cause lynx to format the text/html output as text/plain
is interactive. One could use this to replace the pipe to <tt>more</tt>
in the <tt>lynx -dump</tt> example in the Basic section:
<tscreen><verb>
text/html; lynx -dump %s ; copiousoutput
</verb></tscreen>
This will cause lynx to format the text/html output as text/plain
name="autoview">, in order to decide whether it should honor the setting
of the <ref id="wait_key" name="$wait_key"> variable or
not. When an attachment is viewed using an interactive program, and the
name="autoview">, in order to decide whether it should honor the setting
of the <ref id="wait_key" name="$wait_key"> variable or
not. When an attachment is viewed using an interactive program, and the
<ref id="wait_key" name="$wait_key"> 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.
<tag>compose=<command></tag>
This flag specifies the command to use to create a new attachment of a
<ref id="wait_key" name="$wait_key"> 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.
<tag>compose=<command></tag>
This flag specifies the command to use to create a new attachment of a
<tag>composetyped=<command></tag>
This flag specifies the command to use to create a new attachment of a
specific MIME type. This command differs from the compose command in
that mutt will expect standard MIME headers on the data. This can be
used to specify parameters, filename, description, etc. for a new
<tag>composetyped=<command></tag>
This flag specifies the command to use to create a new attachment of a
specific MIME type. This command differs from the compose command in
that mutt will expect standard MIME headers on the data. This can be
used to specify parameters, filename, description, etc. for a new
<tag>print=<command></tag>
This flag specifies the command to use to print a specific MIME type.
<tag>print=<command></tag>
This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
+Mutt-ng supports this from the compose menu, and also uses it to compose
+new attachments. Mutt-ng will default to the defined editor for text
attachments.
<tag>nametemplate=<template></tag>
This field specifies the format for the file denoted by %s in the
attachments.
<tag>nametemplate=<template></tag>
This field specifies the format for the file denoted by %s in the
This field specifies a command to run to test whether this mailcap
entry should be used. The command is defined with the command expansion
rules defined in the next section. If the command returns 0, then the
This field specifies a command to run to test whether this mailcap
entry should be used. The command is defined with the command expansion
rules defined in the next section. If the command returns 0, then the
-test passed, and Mutt uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-<bf/Note:/ <em>the content-type must match before Mutt performs the test.</em>
+test passed, and Mutt-ng uses this entry. If the command returns non-zero,
+then the test failed, and Mutt-ng continues searching for the right entry.
+<bf/Note:/ <em>the content-type must match before Mutt-ng performs the test.</em>
-RunningX returns 0, then Mutt will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
+RunningX returns 0, then Mutt-ng will call netscape to display the
+text/html object. If RunningX doesn't return 0, then Mutt-ng will go on
the most useful entry for its purpose. For instance, if you are
attempting to print an <tt>image/gif</tt>, and you have the following
the most useful entry for its purpose. For instance, if you are
attempting to print an <tt>image/gif</tt>, and you have the following
entry with the print command.
In addition, you can use this with <ref id="auto_view" name="Autoview">
entry with the print command.
In addition, you can use this with <ref id="auto_view" name="Autoview">
text/html; lynx %s; nametemplate=%s.html
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
</verb></tscreen>
text/html; lynx %s; nametemplate=%s.html
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
</verb></tscreen>
entry because of the copiousoutput tag. For interactive viewing, Mutt
will run the program RunningX to determine if it should use the first
entry because of the copiousoutput tag. For interactive viewing, Mutt
will run the program RunningX to determine if it should use the first
The various commands defined in the mailcap files are passed to the
<tt>/bin/sh</tt> shell using the system() function. Before the
command is passed to <tt>/bin/sh -c</tt>, it is parsed to expand
The various commands defined in the mailcap files are passed to the
<tt>/bin/sh</tt> shell using the system() function. Before the
command is passed to <tt>/bin/sh -c</tt>, it is parsed to expand
<descrip>
<tag/%s/
As seen in the basic mailcap section, this variable is expanded
to a filename specified by the calling program. This file contains
the body of the message to view/print/edit or where the composing
program should place the results of composition. In addition, the
<descrip>
<tag/%s/
As seen in the basic mailcap section, this variable is expanded
to a filename specified by the calling program. This file contains
the body of the message to view/print/edit or where the composing
program should place the results of composition. In addition, the
type of the message in the same form as the first parameter of the
mailcap definition line, ie <tt>text/html</tt> or
<tt>image/gif</tt>.
<tag>%{<parameter>}</tag>
type of the message in the same form as the first parameter of the
mailcap definition line, ie <tt>text/html</tt> or
<tt>image/gif</tt>.
<tag>%{<parameter>}</tag>
from the Content-Type: line of the mail message. For instance, if
Your mail message contains:
<tscreen><verb>
Content-Type: text/plain; charset=iso-8859-1
</verb></tscreen>
from the Content-Type: line of the mail message. For instance, if
Your mail message contains:
<tscreen><verb>
Content-Type: text/plain; charset=iso-8859-1
</verb></tscreen>
mailcap file uses this feature to test the charset to spawn an xterm
using the right charset to view the message.
<tag>\%</tag>
This will be replaced by a %
</descrip>
mailcap file uses this feature to test the charset to spawn an xterm
using the right charset to view the message.
<tag>\%</tag>
This will be replaced by a %
</descrip>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
+In addition to explicitly telling Mutt-ng to view an attachment with the
+MIME viewer defined in the mailcap file, Mutt-ng has support for
automatically viewing MIME attachments while in the pager.
To work, you must define a viewer in the mailcap file which uses the
automatically viewing MIME attachments while in the pager.
To work, you must define a viewer in the mailcap file which uses the
multipart/alternative type to display. First, mutt will check the
alternative_order list to determine if one of the available types
is preferred. The alternative_order list consists of a number of
multipart/alternative type to display. First, mutt will check the
alternative_order list to determine if one of the available types
is preferred. The alternative_order list consists of a number of
Next, mutt will check if any of the types have a defined
<ref id="auto_view" name="auto_view">, and use that. Failing
Next, mutt will check if any of the types have a defined
<ref id="auto_view" name="auto_view">, and use that. Failing
look for any type it knows how to handle.
To remove a MIME type from the <tt/alternative_order/ list, use the
look for any type it knows how to handle.
To remove a MIME type from the <tt/alternative_order/ list, use the
be 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 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
mailbox. However, it is possible to read other mailboxes and
to send messages from the command line as well.
mailbox. However, it is possible to read other mailboxes and
to send messages from the command line as well.
-a attach a file to a message
-b specify a blind carbon-copy (BCC) address
-c specify a carbon-copy (Cc) address
-a attach a file to a message
-b specify a blind carbon-copy (BCC) address
-c specify a carbon-copy (Cc) address
-f specify a mailbox to load
-F specify an alternate file to read initialization commands
-h print help on command line options
-H specify a draft file from which to read a header and body
-i specify a file to include in a message composition
-m specify a default mailbox type
-f specify a mailbox to load
-F specify an alternate file to read initialization commands
-h print help on command line options
-H specify a draft file from which to read a header and body
-i specify a file to include in a message composition
-m specify a default mailbox type
-p recall a postponed message
-Q query a configuration variable
-R open mailbox in read-only mode
-p recall a postponed message
-Q query a configuration variable
-R open mailbox in read-only mode
input from the file you wish to send. For example,
<tt>mutt -s &dquot;data set for run #2&dquot; professor@bigschool.edu
input from the file you wish to send. For example,
<tt>mutt -s &dquot;data set for run #2&dquot; professor@bigschool.edu