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
-Mutt and not Mutt-ng, Mutt-ng contains all Mutt-ng features, plus many more.
+Mutt and not Mutt-ng, Mutt-ng contains all Mutt features, plus many more.
<sect1>Mutt-ng Home Page
<sect>Getting Started
<p>
-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.
+-->
The key bindings described in this section are the defaults as distributed.
Your local system administrator may have altered the defaults for your site.
You can always type ``?'' in any menu to display the current bindings.
-The first thing you need to do is invoke mutt, simply by typing mutt
+The first thing you need to do is invoke mutt-ng simply by typing muttng
at the command line. There are various command-line options, see
-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
-showing the common keys used to navigate menus in Mutt.
+showing the common keys used to navigate menus in Mutt-ng.
<tscreen><verb>
j or Down next-entry move to the next entry
<sect1>Editing Input Fields<label id="editing">
<p>
-Mutt has a builtin line editor which is used as the primary way to input
+Mutt-ng has a builtin line editor which is used as the primary way to input
textual data such as email addresses or filenames. The keys used to move
around while editing are very similar to those of Emacs.
<p>
Similar to many other mail clients, there are two modes in which mail is
-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
<sect2>The Pager
<p>
-By default, Mutt uses its builtin pager to display the body of messages.
+By default, Mutt-ng uses its builtin pager to display the body of messages.
The pager is very similar to the Unix program <em/less/ though not nearly as
featureful.
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,
-``_'' for denoting underline. Mutt will attempt to display these
+``_'' for denoting underline. Mutt-ng will attempt to display these
in bold and underline respectively if your terminal supports them. If
not, you can use the bold and underline <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:
<p>
<tscreen><verb>
name="$askcc">, <ref id="askbcc" name="$askbcc">, <ref
id="autoedit" name="$autoedit">, <ref id="bounce"
name="$bounce">, and <ref id="fast_reply"
-name="$fast_reply"> for changing how Mutt asks these
+name="$fast_reply"> for changing how Mutt-ng asks these
questions.
-Mutt will then automatically start your <ref id="editor"
+Mutt-ng will then automatically start your <ref id="editor"
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
If you specify<newline>
<tt/Fcc:/ <em/filename/<newline>
-Mutt will pick up <em/filename/
+Mutt-ng will pick up <em/filename/
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
-the header field, Mutt will not generate a <em/References:/ field, which
+the header field, Mutt-ng will not generate a <em/References:/ field, which
allows you to create a new message thread.
Also see <ref id="edit_headers" name="edit_headers">.
-<sect2>Using Mutt with PGP
+<sect2>Using Mutt-ng with PGP
<p>
If you want to use PGP, you can specify
If you have told mutt to PGP encrypt a message, it will guide you
through a key selection process when you try to send the message.
-Mutt will not ask you any questions about keys which have a
+Mutt-ng will not ask you any questions about keys which have a
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
-Mutt to use mixmaster, you have to select a remailer chain, using
+Mutt-ng to use mixmaster, you have to select a remailer chain, using
the mix function on the compose menu.
The chain selection screen is divided into two parts. In 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
-message even if you exit Mutt and then restart it at a later time.
+message even if you exit Mutt-ng and then restart it at a later time.
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
<sect1>Reading news via NNTP<label id="reading_news">
<p>
-If compiled with ``--enable-nntp'' option, Mutt can read news from newsserver
-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
-newsgroups is saved in file by <ref id="newsrc" name="$newsrc">
-variable. Article headers are cached and can be loaded from file when
+If compiled with ``--enable-nntp'' option, Mutt-ng can read news from
+newsserver 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 newsgroups is saved in file by <ref
+id="nntp_newsrc" name="$nntp_newsrc"> variable. Article
+headers are cached and can be loaded from file when
newsgroup entered instead loading from newsserver.
<sect>Configuration
<p>
While the default configuration (or ``preferences'') make Mutt-ng usable right out
-of the box, it is often desirable to tailor Mutt to suit your own tastes. When
+of the box, it is often desirable to tailor Mutt-ng to suit your own tastes. When
Mutt-ng is first invoked, it will attempt to read the ``system'' configuration
file (defaults set by your local system administrator), unless the ``-n'' <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
-usually place your <ref id="commands" name="commands"> to configure Mutt.
+usually place your <ref id="commands" name="commands"> to configure Mutt-ng.
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
-sourced instead of the <tt/Muttrc/ file. The same is true of the user
+sourced instead of the <tt/Muttngrc/ file. The same is true of the user
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>
-set realname='Mutt user' ; ignore x-
+set realname='Mutt-ng user' ; ignore x-
</verb></tscreen>
The hash mark, or pound sign
(``#''), is used as a ``comment'' character. You can use it to
Usage: <tt/alias/ <em/key/ <em/address/ [ , <em/address/, ... ]
It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create ``aliases'' which map
+you are communicating with. Mutt-ng allows you to create ``aliases'' which map
a short string to a full address.
<bf/Note:/ if you want to create an alias for a group (by specifying more than
alias theguys manny, moe, jack
</verb></tscreen>
-Unlike other mailers, Mutt doesn't require aliases to be defined
+Unlike other mailers, Mutt-ng doesn't require aliases to be defined
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,
-in the sense that Mutt will happily append aliases to any file, but in
+in the sense that Mutt-ng will happily append aliases to any file, but in
order for the new aliases to take effect you need to explicitly <ref
id="source" name="source"> this file too.
For example:
<tscreen><verb>
-source /usr/local/share/Mutt.aliases
+source /usr/local/share/Mutt-ng.aliases
source ~/.mail_aliases
set alias_file=~/.mail_aliases
</verb></tscreen>
<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
-another menu, Mutt will look for a binding to use in this menu. This allows
+another menu, Mutt-ng will look for a binding to use in this menu. This allows
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
-actions. When you press <em/key/ in menu <em/menu/, Mutt will behave as if
+actions. When you press <em/key/ in menu <em/menu/, Mutt-ng will behave as if
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
-than one user (eg. the system Muttrc).
+than one user (eg. the system Muttngrc).
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>
-If your terminal supports color, you can spice up Mutt by creating your own
+If your terminal supports color, you can spice up Mutt-ng by creating your own
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>attachment
<item>body (match <em/regexp/ in the body of messages)
<item>bold (highlighting bold patterns in the body of messages)
-<item>error (error messages printed by Mutt)
+<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)
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 Mutt is linked against the <em/S-Lang/ library, you also need to set
+If Mutt-ng is linked against the <em/S-Lang/ library, you also need to set
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.
-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/
``content-''. ``ignore *'' will ignore all headers.
To remove a previously added token from the list, use the ``unignore'' command.
-The ``unignore'' command will make Mutt display headers with the given pattern.
+The ``unignore'' command will make Mutt-ng display headers with the given pattern.
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/ ... ]
-Mutt has a few nice features for <ref id="using_lists" name="handling
+Mutt-ng has a few nice features for <ref id="using_lists" name="handling
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.
-More precisely, Mutt maintains lists of patterns for the addresses
+More precisely, Mutt-ng maintains lists of patterns for the addresses
of known and subscribed mailing lists. Every subscribed mailing
list is known. To mark a mailing list as known, use the ``lists''
command. To mark it as subscribed, 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
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed 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.
<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
-messages. Mutt will automatically enter this mode when invoked from the
+messages. Mutt-ng will automatically enter this mode when invoked from the
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
-program which accesses the mailbox might cause Mutt to never detect new mail
+program which accesses the mailbox might cause Mutt-ng to never detect new mail
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
-space is illegal there, so Mutt enforces the rule.
+space is illegal there, so Mutt-ng enforces the rule.
If you would like to add a header field to a single message, you should
either set the <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
-<ref id="record" name="$record">. Mutt searches the initial list of
+<ref id="record" name="$record">. Mutt-ng searches the initial list of
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,
-or because, for some reasons, you need to override the key Mutt would
+or because, for some reasons, you need to override the key Mutt-ng would
normally use. The crypt-hook command provides a method by which you can
specify the ID of the public key to be used when encrypting messages to
a certain recipient.
Usage: <tt/spam/ <em/pattern/ <em/format/<newline>
Usage: <tt/nospam/ <em/pattern/
-Mutt has generalized support for external spam-scoring filters.
+Mutt-ng has generalized support for external spam-scoring filters.
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
<sect1>Configuring features conditionally<label id="ifdef">
<p>
-Usage: <tt/ifdef/ <em/item/ <em/command/
+Usage: <tt/ifdef/ <em/item/ <em/command/<newline>
Usage: <tt/ifndef/ <em/item/ <em/command/
-These command allows to test if a variable, function or certain feature
-is available or not respectively, before actually executing the command.
-<tt/ifdef/ (short for ``if defined) handles commands if upon
+<p>
+These commands allow testing for a variable, function or certain feature
+being available or not respectively, before actually executing the
+command given.
+
+<p>
+<tt/ifdef/ (short for ``if defined'') only executes the command upon
availability while <tt/ifndef/ (short for ``if not defined'') does if
not. The <em/command/ may be any valid fraction of a configuration file.
-All names of variables and functions may be tested. Additionally, the
-following compile-features may be tested when prefixed with 'feature_':
-ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
-gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
-classic_smime, gpgme, header_cache.
+<p>
+All names of variables, functions and menus may be tested. Additionally, the
+following compile-features may be tested when prefixed with
+'<tt/feature_/':
+<tt/ncurses/, <tt/slang/, <tt/iconv/, <tt/idn/, <tt/dotlock/,
+<tt/standalone/, <tt/pop/, <tt/nntp/, <tt/imap/, <tt/ssl/, <tt/gnutls/,
+<tt/sasl/, <tt/sasl2/, <tt/libesmtp/, <tt/compressed/, <tt/color/,
+<tt/classic_pgp/, <tt/classic_smime/, <tt/gpgme/, <tt/header_cache/,
+<tt/gdbm/, <tt/qdbm/ and <tt/db4/.
+<p>
Examples follow.
-To only source a file with IMAP related settings only if IMAP support is
+<p>
+To only source a file with IMAP related settings if IMAP support is
compiled in, use:
<tscreen><verb>
ifdef feature_imap 'source ~/.mutt-ng/imap_setup'
# ...
</verb></tscreen>
+<p>
To exit mutt-ng directly if no NNTP support is compiled in:
<tscreen><verb>
ifndef feature_nntp 'push q'
# ...
</verb></tscreen>
-To only set the <ref id="imap_mail_check"
-name="<$imap_mail_check"> when the system's SVN
-is recent enough to have it:
+<p>
+To only set the <ref id="imap_mail_check"
+name="$imap_mail_check"> variable if
+the system's mutt-ng is aware of it, use:
<tscreen><verb>
-ifdef imap_mail_check 'set imap_mail_check=300'
+ifdef imap_mail_check 'set imap_mail_check=500'
</verb></tscreen>
<sect1>Removing hooks<label id="unhook">
<sect1>Regular Expressions<label id="regexp">
<p>
-All string patterns in Mutt including those in more complex
+All string patterns in Mutt-ng including those in more complex
<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
list. For example, the regular expression <bf/[0123456789]/
matches any single digit. A range of ASCII characters may be specified
by giving the first and last characters, separated by a hyphen
-``‐''. Most metacharacters lose their special meaning inside
+``-''. Most metacharacters lose their special meaning inside
lists. To include a literal ``]'' place it first in the list.
Similarly, to include a literal ``ˆ'' place it anywhere but first.
-Finally, to include a literal hyphen ``‐'' place it last.
+Finally, to include a literal hyphen ``-'' place it last.
Certain named classes of characters are predefined. Character classes
consist of ``[:'', a keyword denoting the class, and ``:]''.
precedence over alternation. A whole subexpression may be enclosed in
parentheses to override these precedence rules.
-<bf/Note:/ If you compile Mutt with the GNU <em/rx/ package, the
+<bf/Note:/ If you compile Mutt-ng with the GNU <em/rx/ package, the
following operators may also be used in regular expressions:
<descrip>
<sect1>Patterns<label id="patterns">
<p>
-Many of Mutt's commands allow you to specify a pattern to match
+Many of Mutt-ng's commands allow you to specify a pattern to match
(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
-~k message contains PGP key material
+~k message contains PGP key material
~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
~T tagged messages
~t USER messages addressed to USER
~U unread messages
-~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 *)
-~= 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,
-Mutt's parser for these patterns will strip one level of backslash (\),
+Mutt-ng's parser for these patterns will strip one level of backslash (\),
which is normally used for quoting. If it is your intention to use a
backslash in the regular expression, you will need to use two backslashes
instead (\\).
recipients <bf/and/ that have the word ``elkins'' in the ``From'' header
field.
-Mutt also recognizes the following operators to create more complex search
+Mutt-ng also recognizes the following operators to create more complex search
patterns:
<itemize>
'~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
</verb></tscreen>
-Note that if a regular expression contains parenthesis, or a veritical bar
+Note that if a regular expression contains parenthesis, or a vertical bar
("|"), you <bf/must/ enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
+those characters are also used to separate different parts of Mutt-ng's
pattern language. For example,
<tscreen><verb>
<sect2>Searching by Date
<p>
-Mutt supports two types of dates, <em/absolute/ and <em/relative/.
+Mutt-ng supports two types of dates, <em/absolute/ and <em/relative/.
<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
-default. See <ref id="patterns" name="patterns"> for Mutt's pattern
+default. See <ref id="patterns" name="patterns"> for Mutt-ng's pattern
matching syntax.
Once you have tagged the desired messages, you can use the
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.
-Mutt will stop "eating" the macro when it encounters the ``end-cond''
+Mutt-ng will stop "eating" the macro when it encounters the ``end-cond''
operator; after this operator the rest of the macro will be executed as
normal.
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
-reading, or to whom you are sending mail. In the Mutt world, a <em/hook/
+reading, or to whom you are sending mail. In the Mutt-ng world, a <em/hook/
consists of a <ref id="regexp" name="regular expression"> or
<ref id="patterns" name="pattern"> along with a
configuration option/command. See
needed for matching since for different purposes you want to match
different criteria.
-Mutt allows the use of the <ref id="patterns" name="search pattern">
+Mutt-ng allows the use of the <ref id="patterns" name="search pattern">
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>
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
+send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
</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
-expression/ like the other hooks, in which case Mutt will translate your
+expression/ like the other hooks, in which case Mutt-ng will translate your
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
<sect1>External Address Queries<label id="query">
<p>
-Mutt supports connecting to external directory databases such as LDAP,
+Mutt-ng supports connecting to external directory databases such as LDAP,
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
using a simple interface. Using the <ref id="query_command"
name="$query_command"> variable, you specify the wrapper
<sect1>Mailbox Formats
<p>
-Mutt supports reading and writing of four different mailbox formats:
+Mutt-ng supports reading and writing of four different mailbox formats:
mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there
is no need to use a flag for different mailbox types. When creating new
-mailboxes, Mutt uses the default specified with the <ref id="mbox_type"
+mailboxes, Mutt-ng uses the default specified with the <ref id="mbox_type"
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
-correspond to the message number Mutt displays). Deleted messages are
+correspond to the message number Mutt-ng displays). Deleted messages are
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
<sect1>Handling Mailing Lists<label id="using_lists">
<p>
-Mutt has a few configuration options that make dealing with large
+Mutt-ng has a few configuration options that make dealing with large
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.
-Now that Mutt knows what your mailing lists are, it can do several
+Now that Mutt-ng knows what your mailing lists are, it can do several
things, the first of which is the ability to show the name of a list
through which you received a message (i.e., of a subscribed list) in
the <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).
-Mutt also supports the <tt/Mail-Followup-To/ header. When you send
+Mutt-ng also supports the <tt/Mail-Followup-To/ header. When you send
a message to a list of recipients which includes one or several
subscribed mailing lists, and if the <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
-<tt/Mail-Followup-To/ header manually. Mutt will only auto-generate
+<tt/Mail-Followup-To/ header manually. Mutt-ng will only auto-generate
this header if it doesn't exist when you send the message.
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''
-field. Mutt uses the <ref id="reply_to" name="$reply_to">
+field. Mutt-ng uses the <ref id="reply_to" name="$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
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
-index, and Mutt's pattern-matcher can match regular expressions to
+index, and Mutt-ng's pattern-matcher can match regular expressions to
``X-Label:'' fields with the ``~y'' selector. ``X-Label:'' is not a
standard message header field, but it can easily be inserted by procmail
and other mail filtering agents.
-Lastly, Mutt has the ability to <ref id="sort" name="sort"> the mailbox into
+Lastly, Mutt-ng has the ability to <ref id="sort" name="sort"> the mailbox into
<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
<sect1>Editing threads
<p>
-Mutt has the ability to dynamically restructure threads that are broken
+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.
Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
"References:" headers when replying to a message. This results in broken
-discussions because Mutt has not enough information to guess the correct
+discussions because Mutt-ng has not enough information to guess the correct
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
<sect1>POP3 Support (OPTIONAL)
<p>
-If Mutt was compiled with POP3 support (by running the <em/configure/
+If Mutt-ng was compiled with POP3 support (by running the <em/configure/
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
-reason the frequency at which Mutt will check for mail remotely can be
+reason the frequency at which Mutt-ng will check for mail remotely can be
controlled by the
-<ref id="pop_checkinterval" name="$pop_checkinterval">
+<ref id="pop_mail_check" name="$pop_mail_check">
variable, which defaults to every 60 seconds.
-If Mutt was compiled with SSL support (by running the <em/configure/
+If Mutt-ng was compiled with SSL support (by running the <em/configure/
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
-point, Mutt runs exactly as if the mail had always been local.
+point, Mutt-ng runs exactly as if the mail had always been local.
<bf/Note:/ If you only need to fetch all messages to local mailbox
you should consider using a specialized program, such as <htmlurl
<sect1>IMAP Support (OPTIONAL)
<p>
-If Mutt was compiled with IMAP support (by running the <em/configure/
+If Mutt-ng was compiled with IMAP support (by running the <em/configure/
script with the <em/--enable-imap/ flag), it has the ability to work
with folders located on a remote IMAP server.
You can also specify different username for each folder, i.e.:
<tt>imap://username@imapserver[:port]/INBOX</tt>.
-If Mutt was compiled with SSL support (by running the <em/configure/
+If Mutt-ng was compiled with SSL support (by running the <em/configure/
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
Pine-compatible notation is also supported, i.e.
<tt>{[username@]imapserver[:port][/ssl]}path/to/folder</tt>
-Note that not all servers use / as the hierarchy separator. Mutt should
+Note that not all servers use / as the hierarchy separator. Mutt-ng should
correctly notice which separator is being used by the server and convert
paths accordingly.
<sect2>Authentication
<p>
-Mutt supports four authentication methods with IMAP servers: SASL,
+Mutt-ng supports four authentication methods with IMAP servers: SASL,
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>
-Mutt will try whichever methods are compiled in and available on the server,
+Mutt-ng will try whichever methods are compiled in and available on the server,
in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
There are a few variables which control authentication:
<sect1>Compressed folders Support (OPTIONAL)
<p>
-If Mutt was compiled with compressed folders support (by running the
+If Mutt-ng was compiled with compressed folders support (by running the
<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.
id="append-hook" name="append-hook"> though you'll be able to append
to the folder.
-Note that Mutt will only try to use hooks if the file is not in one of
+Note that Mutt-ng will only try to use hooks if the file is not in one of
the accepted formats. In particular, if the file is empty, mutt
supposes it is not compressed. This is important because it allows the
use of programs that do not have well defined extensions. Just use
directory, where it can be read by your system administrator. So think
about the security aspects of this.
-<sect>Mutt's MIME Support
+<sect>Mutt-ng's MIME Support
<p>
-Quite a bit of effort has been made to make Mutt the premier text-mode
+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 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>
-There are three areas/menus in Mutt which deal with MIME, they are the
+There are three areas/menus in Mutt-ng which deal with MIME, they are the
pager (while viewing a message), the attachment menu and the compose
menu.
<sect2>Viewing MIME messages in the pager
<p>
When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
+decodes the message to a text representation. Mutt-ng internally supports
a number of MIME types, including <tt>text/plain, text/enriched,
message/rfc822, and message/news</tt>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
+controlled version of Mutt-ng recognizes a variety of PGP MIME types,
including PGP/MIME and application/pgp.
-Mutt will denote attachments with a couple lines describing them.
+Mutt-ng will denote attachments with a couple lines describing them.
These lines are of the form:
<tscreen><verb>
[-- Attachment #1: Description --]
attachment, and the <tt/Encoding/ is one of
<tt>7bit/8bit/quoted-printable/base64/binary</tt>.
-If Mutt cannot deal with a MIME type, it will display a message like:
+If Mutt-ng cannot deal with a MIME type, it will display a message like:
<tscreen><verb>
[-- image/gif is unsupported (use 'v' to view this part) --]
</verb></tscreen>
2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
</verb>
-The '-' denotes that Mutt will delete the file after sending (or
+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
<sect1>MIME Type configuration with <tt/mime.types/
<p>
-When you add an attachment to your mail message, Mutt searches your
+When you add an attachment to your mail message, Mutt-ng searches your
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>
application/pgp pgp
audio/x-aiff aif aifc aiff
</verb></tscreen>
-A sample <tt/mime.types/ file comes with the Mutt distribution, and
+A sample <tt/mime.types/ file comes with the Mutt-ng distribution, and
should contain most of the MIME types you are likely to use.
-If Mutt can not determine the mime type by the extension of the file you
+If Mutt-ng can not determine the mime type by the extension of the file you
attach, it will look at the file. If the file is free of binary
-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
mark it as <tt>application/octet-stream</tt>. You can change the MIME
-type that Mutt assigns to an attachment by using the <tt/edit-type/
+type that Mutt-ng assigns to an attachment by using the <tt/edit-type/
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
-after various internet discussions. Mutt recognises all of these if the
+after various internet discussions. Mutt-ng recognises all of these if the
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
<sect1>MIME Viewer configuration with <tt/mailcap/
<p>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
+Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix
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
find an external handler. The default search string for these files
is a colon delimited list set to
<tscreen><verb>
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 behavior 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 will cause Mutt-ng to save 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 will turn over the
+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 which time Mutt
will remove the temporary file if it exists.
<sect2>Secure use of mailcap
<p>
The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote 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.
of it. Therefore you should pay attention to the following rules:
<em/Keep the %-expandos away from shell quoting./
-Don't quote them with single or double quotes. Mutt does this for
+Don't quote them with single or 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 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.
-Mutt recognizes the following optional fields:
+Mutt-ng recognizes the following optional fields:
<descrip>
<tag/copiousoutput/
-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
pager or the external pager defined by the pager variable) on the output
-of the view command. Without this flag, Mutt assumes that the command
+of the view command. Without this flag, Mutt-ng assumes that the command
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
-and Mutt will use your standard pager to display the results.
+and Mutt-ng will use your standard pager to display the results.
<tag/needsterminal/
-Mutt uses this flag when viewing attachments with <ref id="auto_view"
+Mutt-ng uses this flag when viewing attachments with <ref id="auto_view"
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
-corresponding mailcap entry has a <em/needsterminal/ flag, Mutt will use
+corresponding mailcap entry has a <em/needsterminal/ flag, Mutt-ng will use
<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
-specific MIME type. Mutt supports this from the compose menu.
+specific MIME type. Mutt-ng supports this from the compose menu.
<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
-attachment. Mutt supports this from the compose menu.
+attachment. Mutt-ng supports this from the compose menu.
<tag>print=<command></tag>
This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
+Mutt-ng supports this from the attachment and compose menus.
<tag>edit=<command></tag>
This flag specifies the command to use to edit 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
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>
For example:
<tscreen><verb>
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
text/html; lynx %s
</verb></tscreen>
-In this example, Mutt will run the program RunningX which will return 0
+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 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
to the next entry and use lynx to display the text/html object.
</descrip>
<sect3>Search Order
<p>
-When searching for an entry in the mailcap file, Mutt will search for
+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 <tt>image/gif</tt>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
+entries in your mailcap file, Mutt-ng will search for an entry with the
print command:
<tscreen><verb>
image/*; xv %s
image/gif; ; print= anytopnm %s | pnmtops | lpr; \
nametemplate=%s.gif
</verb></tscreen>
-Mutt will skip the <tt>image/*</tt> entry and use the <tt>image/gif</tt>
+Mutt-ng will skip the <tt>image/*</tt> entry and use the <tt>image/gif</tt>
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>
-For <ref id="auto_view" name="Autoview">, Mutt will choose the third
+For <ref id="auto_view" name="Autoview">, Mutt-ng will choose the third
entry because of the copiousoutput tag. For interactive viewing, Mutt
will run the program RunningX to determine if it should use the first
-entry. If the program returns non-zero, Mutt will use the second entry
+entry. If the program returns non-zero, Mutt-ng will use the second entry
for interactive viewing.
<sect3>Command Expansion
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
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
+various special parameters with information from Mutt-ng. The keywords
+Mutt-ng expands are:
<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
-use of this keyword causes Mutt to not pass the body of the message
+use of this keyword causes Mutt-ng to not pass the body of the message
to the view/print/edit program on stdin.
<tag/%t/
-Mutt will expand %t to the text representation of the content
+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
mailcap definition line, ie <tt>text/html</tt> or
<tt>image/gif</tt>.
<tag>%{<parameter>}</tag>
-Mutt will expand this to the value of the specified parameter
+Mutt-ng will expand this to the value of the specified parameter
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>
-then Mutt will expand %{charset} to iso-8859-1. The default metamail
+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.
<tag>\%</tag>
This will be replaced by a %
</descrip>
-Mutt does not currently support the %F and %n keywords
+Mutt-ng does not currently support the %F and %n keywords
specified in RFC 1524. The main purpose of these parameters is for
-multipart messages, which is handled internally by Mutt.
+multipart messages, which is handled internally by Mutt-ng.
<sect2>Example mailcap files
<p>
<sect1>MIME Autoview<label id="auto_view">
<p>
-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
auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
</verb></tscreen>
-Mutt could use the following mailcap entries to automatically view
+Mutt-ng could use the following mailcap entries to automatically view
attachments of these types.
<tscreen><verb>
text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
<sect1>MIME Multipart/Alternative<label id="alternative_order">
<p>
-Mutt has some heuristics for determining which attachment of a
+Mutt-ng has some heuristics for determining which attachment of a
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
-that, Mutt will look for any text type. As a last attempt, mutt will
+that, Mutt-ng will look for any text type. As a last attempt, mutt will
look for any type it knows how to handle.
To remove a MIME type from the <tt/alternative_order/ list, use the
<sect1>MIME Lookup<label id="mime_lookup">
<p>
-Mutt's mime_lookup list specifies a list of mime-types that should not
+Mutt-ng's mime_lookup list specifies a list of mime-types that should not
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
<sect>Reference
<sect1>Command line options<label id="commandline">
<p>
-Running <tt/mutt/ with no arguments will make Mutt attempt to read your spool
+Running <tt/mutt/ with no arguments will make Mutt-ng attempt to read your spool
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
+-D print the value of all variables on stdout
-e specify a config command to be run after initialization files are read
-f specify a mailbox to load
-F specify an alternate file to read initialization commands
-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
--n do not read the system Muttrc
+-n do not read the system Muttngrc
-p recall a postponed message
-Q query a configuration variable
-R open mailbox in read-only mode
<tt/mutt/ [ -n ] [ -F <em/muttrc/ ] [ -a <em/file/ ] [ -c <em/address/ ] [ -i <em/filename/ ] [ -s <em/subject/ ] <em/address/ [ <em/address/ ... ]
-Mutt also supports a ``batch'' mode to send prepared messages. Simply redirect
+Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redirect
input from the file you wish to send. For example,
<tt>mutt -s &dquot;data set for run #2&dquot; professor@bigschool.edu
projects / apps / madmutt.git / blobdiff