<book>
-<bookinfo>
+<bookinfo> <!--{{{-->
<title>The Mutt Next Generation E-Mail Client</title>
<author>
<firstname>Andreas</firstname><surname>Krennmair</surname>
Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
</para>
</abstract>
-</bookinfo>
+</bookinfo> <!--}}}-->
-<chapter> <!--{{{-->
- <title>Introduction </title>
-
- <sect1>
- <title>Overview </title>
+<chapter id="introduction"> <!--{{{-->
+ <title>Introduction</title>
+
+ <sect1 id="overview">
+ <title>Overview</title>
<para>
<emphasis role="bold">Mutt-ng</emphasis> is a small but very
</sect1>
- <sect1>
- <title>Mutt-ng Home Page </title>
+ <sect1 id="homepage">
+ <title>Mutt-ng Home Page</title>
<para>
<ulink url="http://www.muttng.org/">http://www.muttng.org</ulink>
</sect1>
- <sect1>
- <title>Mailing Lists </title>
+ <sect1 id="mailinglists">
+ <title>Mailing Lists</title>
<para>
</sect1>
- <sect1>
- <title>Software Distribution Sites </title>
+ <sect1 id="distrib-sites">
+ <title>Software Distribution Sites</title>
<para>
So far, there are no official releases of Mutt-ng, but you can
</sect1>
- <sect1>
- <title>IRC </title>
+ <sect1 id="irc">
+ <title>IRC</title>
<para>
Visit channel <emphasis>#muttng</emphasis> on <ulink
</sect1>
- <sect1>
- <title>Weblog </title>
+ <sect1 id="weblog">
+ <title>Weblog</title>
<para>
If you want to read fresh news about the latest development in
</sect1>
- <sect1>
- <title>Copyright </title>
+ <sect1 id="copyright">
+ <title>Copyright</title>
<para>
Mutt is Copyright (C) 1996-2000 Michael R. Elkins
</sect1>
</chapter>
- <!--}}}-->
+<!--}}}-->
-<chapter>
- <title>Getting Started </title>
+<chapter id="getting-started"> <!--{{{-->
+ <title>Getting Started</title>
- <sect1> <!--{{{-->
- <title>Basic Concepts </title>
+ <sect1 id="basic-concepts"> <!--{{{-->
+ <title>Basic Concepts</title>
- <sect2> <!--{{{-->
- <title>Screens and Menus </title>
+ <sect2 id="concept-screens-and-menus"> <!--{{{-->
+ <title>Screens and Menus</title>
<para>
mutt-ng offers different screens of which every has its special
</sect2>
<!--}}}-->
- <sect2> <!--{{{-->
- <title>Configuration </title>
+ <sect2 id="concept-configuration"> <!--{{{-->
+ <title>Configuration</title>
<para>
Mutt-ng does <emphasis>not</emphasis> feature an internal
</sect2>
<!--}}}-->
- <sect2> <!--{{{-->
- <title>Functions </title>
+ <sect2 id="concept-functions"> <!--{{{-->
+ <title>Functions</title>
<para>
Mutt-ng offers great flexibility due to the use of functions:
</sect2>
<!--}}}-->
- <sect2> <!--{{{-->
- <title>Interaction </title>
+ <sect2 id="concept-interaction"> <!--{{{-->
+ <title>Interaction</title>
<para>
Mutt-ng has two basic concepts of user interaction:
</sect2>
<!--}}}-->
- <sect2> <!--{{{-->
- <title>Modularization </title>
+ <sect2 id="concept-modularization"> <!--{{{-->
+ <title>Modularization</title>
<para>
Although mutt-ng has many functionality built-in, many
</sect2>
<!--}}}-->
- <sect2> <!--{{{-->
- <title>Patterns </title>
+ <sect2 id="concept-patterns"> <!--{{{-->
+ <title>Patterns</title>
<para>
Mutt-ng has a built-in pattern matching ``language'' which is
<!--}}}-->
- <sect1> <!--{{{-->
- <title>Screens and Menus </title>
+ <sect1 id="screens-and-menus"> <!--{{{-->
+ <title>Screens and Menus</title>
- <sect2>
- <title>Index </title>
+ <sect2 id="intro-index">
+ <title>Index</title>
<para>
The index is the screen that you usually see first when you
</sect2>
- <sect2>
- <title>Pager </title>
+ <sect2 id="intro-pager">
+ <title>Pager</title>
<para>
The pager is responsible for showing the email content. On the
</sect2>
- <sect2>
- <title>File Browser </title>
+ <sect2 id="intro-browser">
+ <title>File Browser</title>
<para>
The file browser is the interface to the local or remote
</sect2>
- <sect2>
- <title>Sidebar </title>
+ <sect2 id="intro-sidebar">
+ <title>Sidebar</title>
<para>
The sidebar comes in handy to manage mails which are spread
</sect2>
- <sect2>
- <title>Help </title>
+ <sect2 id="intro-help">
+ <title>Help</title>
<para>
The help screen is meant to offer a quick help to the user. It
</sect2>
- <sect2>
- <title>Compose Menu </title>
+ <sect2 id="intro-compose">
+ <title>Compose Menu</title>
<para>
The compose menu features a split screen containing the
</sect2>
- <sect2>
- <title>Alias Menu </title>
+ <sect2 id="intro-alias">
+ <title>Alias Menu</title>
<para>
The alias menu is used to help users finding the recipients
</sect2>
- <sect2>
- <title>Attachment Menu </title>
+ <sect2 id="intro-attach">
+ <title>Attachment Menu</title>
<para>
As will be later discussed in detail, mutt-ng features a good
</sect2>
- <sect2>
- <title>Key Menu </title>
+ <sect2 id="intro-keysel">
+ <title>Key Menu</title>
<para>
<literal>FIXME</literal>
</sect1>
<!--}}}-->
- <sect1> <!--{{{-->
- <title>Moving Around in Menus </title>
+ <sect1 id="moving"> <!--{{{-->
+ <title>Moving Around in Menus</title>
<para>
Information is presented in menus, very similar to ELM. Here is a
<!--}}}-->
<sect1 id="editing"> <!--{{{-->
- <title>Editing Input Fields </title>
+ <title>Editing Input Fields</title>
<para>
Mutt-ng has a builtin line editor which is used as the primary way to
</sect1>
<!--}}}-->
- <sect1>
- <title>Reading Mail - The Index and Pager </title> <!--{{{-->
+ <sect1 id="reading"> <!--{{{-->
+ <title>Reading Mail - The Index and Pager</title>
<para>
Similar to many other mail clients, there are two modes in which mail
modes.
</para>
- <sect2>
- <title>The Message Index</title> <!--{{{-->
+ <sect2 id="reading-index">
+ <title>The Message Index</title>
<para>
</variablelist>
</para>
- <!--}}}-->
</sect3>
- <!--}}}-->
</sect2>
- <sect2>
- <title>The Pager</title> <!--{{{-->
+ <sect2 id="reading-pager">
+ <title>The Pager</title>
<para>
By default, Mutt-ng uses its builtin pager to display the body of
your xterm, then that color will be used instead of green.
</para>
- <!--}}}-->
</sect2>
<sect2 id="threads">
- <title>Threaded Mode</title> <!--{{{-->
+ <title>Threaded Mode</title>
<para>
When the mailbox is <link linkend="sort">sorted</link> by <emphasis>
See also: <link linkend="strict-threads">strict-threads</link>.
</para>
- <!--}}}-->
</sect2>
- <sect2>
- <title>Miscellaneous Functions</title> <!--{{{-->
+ <sect2 id="pager-functions">
+ <title>Miscellaneous Functions</title>
<para>
<emphasis role="bold">create-alias</emphasis><anchor id="create-alias"/>
</para>
- <!--}}}-->
</sect2>
- <!--}}}-->
</sect1>
+ <!--}}}-->
- <sect1>
- <title>Sending Mail </title> <!--{{{-->
+ <sect1 id="sending"> <!--{{{-->
+ <title>Sending Mail</title>
<para>
The following bindings are available in the <emphasis>index</emphasis>
.
</para>
- <sect2>
- <title>Composing new messages </title> <!--{{{-->
+ <sect2 id="sending-compose">
+ <title>Composing new messages</title>
<para>
When you want to send an email using mutt-ng, simply press <literal>m</literal> on
</para>
- <!--}}}-->
</sect2>
- <sect2>
- <title>Replying </title> <!--{{{-->
+ <sect2 id="sending-reply">
+ <title>Replying</title>
- <sect3>
- <title>Simple Replies </title> <!--{{{-->
+ <sect3 id="sending-simple-reply">
+ <title>Simple Replies</title>
<para>
When you want to reply to an email message, select it in the index
</para>
- <!--}}}-->
</sect3>
- <sect3>
- <title>Group Replies </title> <!--{{{-->
+ <sect3 id="sending-group-reply">
+ <title>Group Replies</title>
<para>
In the situation where a group of people uses email as a
</para>
- <!--}}}-->
</sect3>
- <sect3>
- <title>List Replies </title> <!--{{{-->
+ <sect3 id="sending-list-reply">
+ <title>List Replies</title>
<para>
When you use mailing lists, it's generally better to send your
</para>
- <!--}}}-->
</sect3>
- <!--}}}-->
</sect2>
- <sect2>
- <title>Editing the message header </title>
+ <sect2 id="sending-edit-header">
+ <title>Editing the message header</title>
<para>
When editing the header of your outgoing message, there are a couple
</sect2>
- <sect2>
- <title>Using Mutt-ng with PGP </title>
+ <sect2 id="sending-crypto">
+ <title>Using Mutt-ng with PGP</title>
<para>
If you want to use PGP, you can specify
</sect2>
- <sect2>
- <title>Sending anonymous messages via mixmaster </title>
+ <sect2 id="sending-mixmaster">
+ <title>Sending anonymous messages via mixmaster</title>
<para>
You may also have configured mutt to co-operate with Mixmaster, an
</sect1>
<sect1 id="forwarding-mail">
- <title>Forwarding and Bouncing Mail </title>
+ <title>Forwarding and Bouncing Mail</title>
<para>
Often, it is necessary to forward mails to other people.
</sect1>
<sect1 id="postponing-mail">
- <title>Postponing Mail </title>
+ <title>Postponing Mail</title>
<para>
At times it is desirable to delay sending a message that you have
</para>
</sect1>
+
+ <!--}}}-->
- </chapter>
+</chapter>
+<!--}}}-->
- <chapter>
- <title>Configuration </title>
+<chapter id="configuration"> <!--{{{-->
+ <title>Configuration</title>
- <sect1>
- <title>Locations of Configuration Files </title>
+ <sect1 id="configuration-files">
+ <title>Locations of Configuration Files</title>
<para>
While the default configuration (or ``preferences'') make Mutt-ng
</sect1>
- <sect1 id="muttrc-syntax">
- <title>Basic Syntax of Initialization Files </title>
+ <sect1 id="configuration-syntax">
+ <title>Basic Syntax of Initialization Files</title>
<para>
An initialization file consists of a series of <link linkend="commands">
</sect1>
- <sect1>
- <title>Expansion within variables </title>
+ <sect1 id="configuration-expansion">
+ <title>Expansion within variables</title>
<para>
Besides just assign static content to variables, there's plenty of
ways of adding external and more or less dynamic content.
</para>
- <sect2>
- <title>Commands' Output </title>
+ <sect2 id="configuration-expansion-commands">
+ <title>Commands' Output</title>
<para>
It is possible to substitute the output of a Unix command in an
</sect2>
- <sect2>
- <title>Environment Variables </title>
+ <sect2 id="configuration-expansion-environment">
+ <title>Environment Variables</title>
<para>
UNIX environments can be accessed like the way it is done in
</sect2>
- <sect2>
- <title>Configuration Variables </title>
+ <sect2 id="configuration-expansion-config">
+ <title>Configuration Variables</title>
<para>
As for environment variables, the values of all configuration
</sect2>
- <sect2>
- <title>Self-Defined Variables </title>
+ <sect2 id="configuration-expansion-self">
+ <title>Self-Defined Variables</title>
<para>
Mutt-ng flexibly allows users to define their own variables. To
</sect2>
- <sect2>
- <title>Pre-Defined Variables </title>
+ <sect2 id="configuration-expansion-predef">
+ <title>Pre-Defined Variables</title>
<para>
In order to allow users to share one setup over a number of
</sect2>
- <sect2>
- <title>Type Conversions </title>
+ <sect2 id="configuration-expansion-typeconv">
+ <title>Type Conversions</title>
<para>
A note about variable's types during conversion: internally
</sect1>
<sect1 id="alias">
- <title>Defining/Using aliases </title>
+ <title>Defining/Using aliases</title>
<para>
<literallayout>
</sect1>
<sect1 id="bind">
- <title>Changing the default key bindings </title>
+ <title>Changing the default key bindings</title>
<para>
<literallayout>
</sect1>
<sect1 id="charset-hook">
- <title>Defining aliases for character sets </title>
+ <title>Defining aliases for character sets</title>
<para>
<literallayout>
</sect1>
<sect1 id="folder-hook">
- <title>Setting variables based upon mailbox </title>
+ <title>Setting variables based upon mailbox</title>
<para>
<literallayout>
</sect1>
<sect1 id="macro">
- <title>Keyboard macros </title>
+ <title>Keyboard macros</title>
<para>
<literallayout>
</sect1>
<sect1 id="color">
- <title>Using color and mono video attributes </title>
+ <title>Using color and mono video attributes</title>
<para>
<literallayout>
</sect1>
<sect1 id="ignore">
- <title>Ignoring (weeding) unwanted message headers </title>
+ <title>Ignoring (weeding) unwanted message headers</title>
<para>
<literallayout>
</sect1>
<sect1 id="alternates">
- <title>Alternative addresses </title>
+ <title>Alternative addresses</title>
<para>
Usage: <literal>[un]alternates</literal> <emphasis>regexp</emphasis> [ <emphasis>
depending on whether you sent them or whether you received them from
someone else. For instance, when replying to a message that you
sent to a different party, mutt will automatically suggest to send
- the response to the original message's recipients -- responding to
+ the response to the original message's recipients--responding to
yourself won't make much sense in many cases. (See <link linkend="reply-to">
reply-to
</link>
</sect1>
- <sect1>
- <title>Format = Flowed </title>
+ <sect1 id="format-flowed">
+ <title>Format = Flowed</title>
- <sect2>
- <title>Introduction </title>
+ <sect2 id="format-flowed-intro">
+ <title>Introduction</title>
<para>
Mutt-ng contains support for so-called <literal>format=flowed</literal> messages.
</sect2>
- <sect2>
- <title>Receiving: Display Setup </title>
+ <sect2 id="format-flowed-display">
+ <title>Receiving: Display Setup</title>
<para>
When you receive emails that are marked as <literal>format=flowed</literal>
</sect2>
- <sect2>
- <title>Sending </title>
+ <sect2 id="format-flowed-send">
+ <title>Sending</title>
<para>
If you want mutt-ng to send emails with <literal>format=flowed</literal> set, you
</sect2>
- <sect2>
+ <sect2 id="format-flowed-notes">
<title>Additional Notes</title>
<para>
</sect1>
<sect1 id="lists">
- <title>Mailing lists </title>
+ <title>Mailing lists</title>
<para>
<literallayout>
</sect1>
<sect1 id="mbox-hook">
- <title>Using Multiple spool mailboxes </title>
+ <title>Using Multiple spool mailboxes</title>
<para>
<literallayout>
</sect1>
<sect1 id="mailboxes">
- <title>Defining mailboxes which receive mail </title>
+ <title>Defining mailboxes which receive mail</title>
<para>
<literallayout>
</sect1>
<sect1 id="my-hdr">
- <title>User defined headers </title>
+ <title>User defined headers</title>
<para>
<literallayout>
</sect1>
<sect1 id="hdr-order">
- <title>Defining the order of headers when viewing messages </title>
+ <title>Defining the order of headers when viewing messages</title>
<para>
<literallayout>
</sect1>
<sect1 id="save-hook">
- <title>Specify default save filename </title>
+ <title>Specify default save filename</title>
<para>
<literallayout>
</sect1>
<sect1 id="fcc-hook">
- <title>Specify default Fcc: mailbox when composing </title>
+ <title>Specify default Fcc: mailbox when composing</title>
<para>
<literallayout>
</sect1>
<sect1 id="fcc-save-hook">
- <title>Specify default save filename and default Fcc: mailbox at once </title>
+ <title>Specify default save filename and default Fcc: mailbox at once</title>
<para>
<literallayout>
</sect1>
<sect1 id="send-hook">
- <title>Change settings based upon message recipients </title>
-
+ <title>Change settings based upon message recipients</title>
+
+ <anchor id="reply-hook"/>
<para>
<literallayout>
Usage: <literal>reply-hook</literal> [!]<emphasis>pattern</emphasis> <emphasis>command</emphasis>
</sect1>
<sect1 id="message-hook">
- <title>Change settings before formatting a message </title>
+ <title>Change settings before formatting a message</title>
<para>
<literallayout>
</sect1>
<sect1 id="crypt-hook">
- <title>Choosing the cryptographic key of the recipient </title>
+ <title>Choosing the cryptographic key of the recipient</title>
<para>
<literallayout>
</sect1>
<sect1 id="push">
- <title>Adding key sequences to the keyboard buffer </title>
+ <title>Adding key sequences to the keyboard buffer</title>
<para>
<literallayout>
</sect1>
<sect1 id="exec">
- <title>Executing functions </title>
+ <title>Executing functions</title>
<para>
<literallayout>
</sect1>
<sect1 id="score-command">
- <title>Message Scoring </title>
+ <title>Message Scoring</title>
<para>
<literallayout>
</sect1>
<sect1 id="spam">
- <title>Spam detection </title>
+ <title>Spam detection</title>
<para>
<literallayout>
</sect1>
<sect1 id="set">
- <title>Setting variables </title>
+ <title>Setting variables</title>
<para>
<literallayout>
</sect1>
<sect1 id="source">
- <title>Reading initialization commands from another file </title>
+ <title>Reading initialization commands from another file</title>
<para>
<literallayout>
</sect1>
<sect1 id="unhook">
- <title>Removing hooks </title>
+ <title>Removing hooks</title>
<para>
<literallayout>
</sect1>
- <sect1 id="sect:sharingsetups">
- <title>Sharing Setups </title>
+ <sect1 id="share">
+ <title>Sharing Setups</title>
- <sect2>
- <title>Character Sets </title>
+ <sect2 id="share-charset">
+ <title>Character Sets</title>
<para>
As users may run mutt-ng on different systems, the configuration
</sect2>
- <sect2>
- <title>Modularization </title>
+ <sect2 id="share-modularization">
+ <title>Modularization</title>
<para>
``Modularization'' means to divide the setup into several files
</sect2>
- <sect2>
- <title>Conditional parts </title>
+ <sect2 id="share-conditional">
+ <title>Conditional parts</title>
<para>
When using a configuration on different systems, the user may not
</sect1>
- <sect1>
- <title>Obsolete Variables </title>
+ <sect1 id="vars-obsolete">
+ <title>Obsolete Variables</title>
<para>
In the process of ensuring and creating more consistency, many
</sect1>
</chapter>
+ <!--}}}-->
- <chapter>
- <title>Advanced Usage </title>
+ <chapter id="advanced-usage"> <!--{{{-->
+ <title>Advanced Usage</title>
- <sect1 id="regexp">
- <title>Regular Expressions </title>
+ <sect1 id="advanced-regexp">
+ <title>Regular Expressions</title>
<para>
All string patterns in Mutt-ng including those in more complex
- <link linkend="patterns">patterns</link> must be specified
+ <link linkend="tab-patterns">patterns</link> 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
Note that the regular expression can be enclosed/delimited by either
"
or ' which is useful if the regular expression includes a white-space
- character. See <link linkend="muttrc-syntax">muttrc-syntax</link>
+ character. See <link linkend="configuration-syntax">muttrc-syntax</link>
for more information on " and ' delimiter processing. To match a
literal " or ' you must preface it with \ (backslash).
</para>
</sect1>
- <sect1>
- <title>Patterns </title>
+ <sect1 id="advanced-patterns">
+ <title>Patterns</title>
<para>
Mutt-ng's pattern language provides a simple yet effective way to
set up rules to match messages, e.g. for operations like tagging and
scoring. A pattern consists of one or more sub-pattern, which can be
logically grouped, ORed, and negated. For a complete listing of
- these patterns, please refer to table <link linkend="patterns">patterns</link> in the Reference chapter.
+ these patterns, please refer to table <link linkend="tab-patterns">patterns</link> in the Reference chapter.
</para>
<para>
It must be noted that in this table, <literal>EXPR</literal> is
a regular expression. For ranges, the forms
<literal><[MAX]</literal>, <literal>>>[MIN]</literal>,
- <literal> [MIN]- </literal> and <literal>-[MAX]</literal> are
+ <literal> [MIN]-</literal> and <literal>-[MAX]</literal> are
also possible.
</para>
- <sect2>
- <title>Complex Patterns </title>
+ <sect2 id="patterns-complex">
+ <title>Complex Patterns</title>
<para>
It is possible to combine several sub-patterns to a more complex
</sect2>
- <sect2>
- <title>Patterns and Dates </title>
+ <sect2 sect="patterns-dates">
+ <title>Patterns and Dates</title>
<para>
When using dates in patterns, the dates must be specified in a
</sect1>
- <sect1>
- <title>Format Strings </title>
+ <sect1 id="formatstrings">
+ <title>Format Strings</title>
- <sect2>
- <title>Introduction </title>
+ <sect2 id="formatstrings-intro">
+ <title>Introduction</title>
<para>
The so called <emphasis>Format Strings</emphasis> offer great
</sect2>
- <sect2>
- <title>Conditional Expansion </title>
+ <sect2 id="formatstrings-conditional">
+ <title>Conditional Expansion</title>
<para>
To only print the number of messages if there are new messages in
</sect2>
- <sect2>
- <title>Modifications and Padding </title>
+ <sect2 id="formatstrings-padding">
+ <title>Modifications and Padding</title>
<para>
Besides the information given so far, there're even more features of
</sect1>
- <sect1>
- <title>Using Tags </title>
+ <sect1 id="using-tags">
+ <title>Using Tags</title>
<para>
Sometimes it is desirable to perform an operation on a group of
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 <link linkend="patterns">patterns</link> for Mutt-ng's
+ default. See <link linkend="tab-patterns">patterns</link> for Mutt-ng's
pattern
matching syntax.
</para>
</sect1>
<sect1 id="hooks">
- <title>Using Hooks </title>
+ <title>Using Hooks</title>
<para>
A <emphasis>hook</emphasis> is a concept borrowed from the EMACS editor
reading, or to whom you are sending mail. In the Mutt-ng world, a <emphasis>
hook
</emphasis>
- consists of a <link linkend="regexp">regexp</link> or
- <link linkend="patterns">patterns</link> along with a
+ consists of a <link linkend="advanced-regexp">regexp</link> or
+ <link linkend="tab-patterns">patterns</link> along with a
configuration option/command. See
<itemizedlist>
fcc-hook,message-hook
</literal>
)are evaluated in a slightly different manner. For the other
- types of hooks, a <link linkend="regexp">regexp</link> is
+ types of hooks, a <link linkend="advanced-regexp">regexp</link> is
sufficient. But in dealing with messages a finer grain of control is
needed for matching since for different purposes you want to match
different criteria.
</para>
<para>
- Mutt-ng allows the use of the <link linkend="patterns">patterns</link>
+ Mutt-ng allows the use of the <link linkend="tab-patterns">patterns</link>
language for matching messages in hook commands. This works in
exactly the same way as it would when <emphasis>limiting</emphasis>
or<emphasis>searching</emphasis> the mailbox, except that you are
</sect1>
<sect1 id="sidebar">
- <title>Using the sidebar </title>
+ <title>Using the sidebar</title>
<para>
The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox
</sect1>
<sect1 id="query">
- <title>External Address Queries </title>
+ <title>External Address Queries</title>
<para>
Mutt-ng supports connecting to external directory databases such as
</sect1>
- <sect1>
- <title>Mailbox Formats </title>
+ <sect1 id="mailbox-formats">
+ <title>Mailbox Formats</title>
<para>
Mutt-ng supports reading and writing of four different mailbox formats:
</sect1>
<sect1 id="shortcuts">
- <title>Mailbox Shortcuts </title>
+ <title>Mailbox Shortcuts</title>
<para>
There are a number of built in shortcuts which refer to specific
</sect1>
<sect1 id="using-lists">
- <title>Handling Mailing Lists </title>
+ <title>Handling Mailing Lists</title>
<para>
Mutt-ng has a few configuration options that make dealing with large
</sect1>
- <sect1>
- <title>Editing threads </title>
+ <sect1 id="editing-threads">
+ <title>Editing threads</title>
<para>
Mutt-ng has the ability to dynamically restructure threads that are
annoyances which make it hard to follow a discussion.
</para>
- <sect2>
+ <sect2 id="editing-threads-link">
<title>Linking threads</title>
<para>
</sect2>
- <sect2>
+ <sect2 id="editing-threads-break">
<title>Breaking threads</title>
<para>
</sect1>
<sect1 id="dsn">
- <title>Delivery Status Notification (DSN) Support </title>
+ <title>Delivery Status Notification (DSN) Support</title>
<para>
RFC1894 defines a set of MIME content types for relaying information
</sect1>
- <sect1>
- <title>POP3 Support (OPTIONAL) </title>
+ <sect1 id="pop3">
+ <title>POP3 Support (OPTIONAL)</title>
<para>
If Mutt-ng was compiled with POP3 support (by running the <emphasis>
</sect1>
- <sect1>
- <title>IMAP Support (OPTIONAL) </title>
+ <sect1 id="imap">
+ <title>IMAP Support (OPTIONAL)</title>
<para>
If Mutt-ng was compiled with IMAP support (by running the <emphasis>
selects the same folder.
</para>
- <sect2>
+ <sect2 id="imap-browser">
<title>The Folder Browser</title>
<para>
</sect2>
- <sect2>
+ <sect2 id="imap-auth">
<title>Authentication</title>
<para>
</sect1>
- <sect1 id="reading-news">
- <title>NNTP Support (OPTIONAL) </title>
+ <sect1 id="nntp">
+ <title>NNTP Support (OPTIONAL)</title>
<para>
If compiled with ``--enable-nntp'' option, Mutt-ng can read news from
maildir/IMAP.
</para>
- <sect2>
- <title>Again: Scoring </title>
+ <sect2 id="nntp-scoring">
+ <title>Again: Scoring</title>
<para>
Especially for Usenet, people often ask for advanced filtering
</sect1>
- <sect1>
- <title>SMTP Support (OPTIONAL) </title>
+ <sect1 id="smtp">
+ <title>SMTP Support (OPTIONAL)</title>
<para>
Mutt-ng can be built using a library called ``libESMTP'' which
</sect1>
<sect1 id="account-hook">
- <title>Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) </title>
+ <title>Managing multiple IMAP/POP/NNTP accounts (OPTIONAL)</title>
<para>
If you happen to have accounts on multiple IMAP and/or POP servers,
</sect1>
<sect1 id="urlview">
- <title>Start a WWW Browser on URLs (EXTERNAL) </title>
+ <title>Start a WWW Browser on URLs (EXTERNAL)</title>
<para>
If a message contains URLs (<emphasis>unified resource locator</emphasis> = address in the
</sect1>
- <sect1>
- <title>Compressed folders Support (OPTIONAL) </title>
+ <sect1 id="compressed-folders">
+ <title>Compressed folders Support (OPTIONAL)</title>
<para>
If Mutt-ng was compiled with compressed folders support (by running the
</sect2>
- <sect2>
+ <sect2 id="encrypted-folders">
<title>Encrypted folders</title>
<para>
</sect1>
</chapter>
+ <!--}}}-->
- <chapter>
- <title>Mutt-ng's MIME Support </title>
+ <chapter id="mime-support"> <!--{{{-->
+ <title>Mutt-ng's MIME Support</title>
<para>
Quite a bit of effort has been made to make Mutt-ng the premier text-mode
the external commands to use for handling specific MIME types.
</para>
- <sect1>
- <title>Using MIME in Mutt </title>
+ <sect1 id="mime">
+ <title>Using MIME in Mutt</title>
<para>
There are three areas/menus in Mutt-ng which deal with MIME, they are
menu.
</para>
- <sect2>
+ <sect2 id="mime-view">
<title>Viewing MIME messages in the pager</title>
<para>
</sect1>
- <sect1>
+ <sect1 id="mime-types">
<title>
MIME Type configuration with <literal>mime.types</literal>
</title>
</sect1>
- <sect1>
+ <sect1 id="mime-mailcap">
<title>
MIME Viewer configuration with <literal>mailcap</literal>
</title>
entries.
</para>
- <sect2>
+ <sect2 id="mime-mailcap-basics">
<title>The Basics of the mailcap file</title>
<para>
The content type is specified in the MIME standard type/subtype
method.
For example,
- <literal>text/plain, text/html, image/gif, </literal>
+ <literal>text/plain, text/html, image/gif,</literal>
etc. In addition, the mailcap format includes two formats for
wildcards, one using the special '*' subtype, the other is the
implicit
</sect2>
- <sect2>
+ <sect2 id="mime-mailcap-security">
<title>Secure use of mailcap</title>
<para>
</sect2>
- <sect2>
+ <sect2 id="mime-mailcap-advanced">
<title>Advanced mailcap Usage</title>
- <sect3>
+ <sect3 id="mime-mailcap-advanced-fields">
<title>Optional Fields</title>
<para>
</sect3>
- <sect3>
+ <sect3 id="mime-mailcap-advanced-searchorder">
<title>Search Order</title>
<para>
</sect3>
- <sect3>
+ <sect3 id="mime-mailcap-advanced-expansion">
<title>Command Expansion</title>
<para>
</sect2>
- <sect2>
+ <sect2 id="mime-mailcap-examples">
<title>Example mailcap files</title>
<para>
</sect1>
<sect1 id="auto-view">
- <title>MIME Autoview </title>
+ <title>MIME Autoview</title>
<para>
In addition to explicitly telling Mutt-ng to view an attachment with
</sect1>
<sect1 id="alternative-order">
- <title>MIME Multipart/Alternative </title>
+ <title>MIME Multipart/Alternative</title>
<para>
Mutt-ng has some heuristics for determining which attachment of a
</sect1>
<sect1 id="mime-lookup">
- <title>MIME Lookup </title>
+ <title>MIME Lookup</title>
<para>
Mutt-ng's mime_lookup list specifies a list of mime-types that
</sect1>
</chapter>
+ <!--}}}-->
- <chapter>
- <title>Security Considerations </title>
+ <chapter id="security"> <!--{{{-->
+ <title>Security Considerations</title>
<para>
First of all, mutt-ng contains no security holes included by
of setup, please read this chapter carefully.
</para>
- <sect1>
- <title>Passwords </title>
+ <sect1 id="security-passwords">
+ <title>Passwords</title>
<para>
Although mutt-ng can be told the various passwords for accounts,
</sect1>
- <sect1>
- <title>Temporary Files </title>
+ <sect1 id="security-tempfiles">
+ <title>Temporary Files</title>
<para>
Mutt-ng uses many temporary files for viewing messages, verifying
</sect1>
- <sect1>
- <title>Information Leaks </title>
+ <sect1 id="security-leaks">
+ <title>Information Leaks</title>
- <sect2>
- <title>Message-ID: headers </title>
+ <sect2 id="security-leaks-mid">
+ <title>Message-ID: headers</title>
<para>
In the default configuration, mutt-ng will leak some information
</sect2>
- <sect2>
- <title>mailto:-style links </title>
+ <sect2 id="security-leaks-mailto">
+ <title>mailto:-style links</title>
<para>
As mutt-ng be can be set up to be the mail client to handle
</sect1>
- <sect1>
- <title>External applications </title>
+ <sect1 id="security-external">
+ <title>External applications</title>
<para>
Mutt-ng in many places has to rely on external applications or
applications.
</para>
- <sect2>
- <title>mailcap </title>
+ <sect2 id="security-external-mailcap">
+ <title>mailcap</title>
<para>
One of these is the <literal>mailcap</literal> mechanism as defined
</sect2>
- <sect2>
- <title>Other </title>
+ <sect2 id="security-external-other">
+ <title>Other</title>
<para>
Besides the mailcap mechanism, mutt-ng uses a number of other
</sect1>
</chapter>
+ <!--}}}-->
- <chapter>
- <title>Reference </title>
+ <chapter id="reference"> <!--{{{-->
+ <title>Reference</title>
<sect1 id="commandline">
- <title>Command line options </title>
+ <title>Command line options</title>
<para>
Running <literal>mutt</literal> with no arguments will make Mutt-ng
</sect1>
<sect1 id="patterns">
- <title>Patterns </title>
+ <title>Patterns</title>
<para>
- <table>
+ <table id="tab-patterns">
<title>Patterns</title>
<tgroup cols="2" align="left" colsep="1" rowsep="1">
<thead>
<para>
Where EXPR are
- <link linkend="regexp">regexp</link>. Special attention has to be
+ <link linkend="advanced-regexp">regexp</link>. Special attention has to be
made when using regular expressions inside of patterns. Specifically,
Mutt-ng's parser for these patterns will strip one level of backslash
(\),
</sect1>
<sect1 id="commands">
- <title>Configuration Commands </title>
+ <title>Configuration Commands</title>
<para>
The following are the commands understood by mutt.