X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.xml.head;h=671402a738aa0b4692321cf73c42d2b5dd77e017;hp=c121d1bec729eb09a8b08a1f453c40c7d184fcda;hb=d6988dab6bd378ccdf0f17aaa16de8aee1ceaf43;hpb=f7f52358a72c7bc02e201dd03bd7f75869681a52 diff --git a/doc/manual.xml.head b/doc/manual.xml.head index c121d1b..671402a 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -1,10 +1,10 @@ - - + + + + + - - - + The Mutt Next Generation E-Mail Client AndreasKrennmair @@ -14,7 +14,7 @@ MichaelElkins me@cs.hmc.edu - version devel-r473 + version @VERSION@ Michael Elinks on mutt, circa 1995: @@ -24,13 +24,13 @@ Sven Guckes on mutt, ca. 2003: ``But it still sucks!'' - + - - Introduction - - - Overview + + Introduction + + + Overview Mutt-ng is a small but very @@ -58,11 +58,11 @@ - - Mutt-ng Home Page + + Mutt-ng Home Page - http://www.muttng.org + @@ -71,8 +71,8 @@ - - Mailing Lists + + Mailing Lists @@ -102,14 +102,12 @@ - - Software Distribution Sites + + Software Distribution Sites So far, there are no official releases of Mutt-ng, but you can - download daily snapshots from http://mutt-ng.berlios.de/snapshots/ + download daily snapshots from @@ -118,8 +116,8 @@ - - IRC + + IRC Visit channel #muttng on - - Weblog + + Weblog If you want to read fresh news about the latest development in @@ -144,8 +142,8 @@ - - Copyright + + Copyright Mutt is Copyright (C) 1996-2000 Michael R. Elkins @@ -169,22 +167,76 @@ You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software - Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - + + + Manual Conventions + + + This manual contains several (hopefully consistent) conventions to + specially layout different items in different fashions. + + + + + + Configuration and environment variables will be printed + in a typewriter font and both prefixed with a dollar sign as + it's common for UNIX-like environments. Configuration + variables are lower-case only while environment variables + are upper-case only. is a configuration variable while + is an environment + variable. + + + Muttng-specific functions are enclosed in + <> and printed in a typewriter font, + too, as in . + + + As common for UNIX-like environments, references to + manual pages are printed with the section enclosed in + braces, as in or . Execute man [section] + [name] to view the manual page. + + + Keys are presented in the following way: ordinary keys + are just given as-is, e.g. + q. Control characters are + prefixed with C- (e.g. the screen can be + redraw by pressing L) and E- for + Escape, e.g. a folder can be opened read-only with + c. + + + + + + + If, while reading this fine manual, you find any inconsistencies + of whatever kind, please contact the developers via + mutt-ng-devel@lists.berlios.de to report it. + + + + - + - - Getting Started + + Getting Started - - Basic Concepts + + Basic Concepts - - Screens and Menus + + Screens and Menus mutt-ng offers different screens of which every has its special @@ -294,8 +346,8 @@ - - Configuration + + Configuration Mutt-ng does not feature an internal @@ -326,8 +378,8 @@ - - Functions + + Functions Mutt-ng offers great flexibility due to the use of functions: @@ -346,8 +398,8 @@ - - Interaction + + Interaction Mutt-ng has two basic concepts of user interaction: @@ -392,8 +444,8 @@ - - Modularization + + Modularization Although mutt-ng has many functionality built-in, many @@ -415,8 +467,8 @@ - - Patterns + + Patterns Mutt-ng has a built-in pattern matching ``language'' which is @@ -440,11 +492,11 @@ - - Screens and Menus + + Screens and Menus - - Index + + Index The index is the screen that you usually see first when you @@ -467,8 +519,8 @@ - - Pager + + Pager The pager is responsible for showing the email content. On the @@ -499,8 +551,8 @@ - - File Browser + + File Browser The file browser is the interface to the local or remote @@ -518,8 +570,8 @@ - - Sidebar + + Sidebar The sidebar comes in handy to manage mails which are spread @@ -538,8 +590,8 @@ - - Help + + Help The help screen is meant to offer a quick help to the user. It @@ -556,8 +608,8 @@ - - Compose Menu + + Compose Menu The compose menu features a split screen containing the @@ -581,8 +633,8 @@ - - Alias Menu + + Alias Menu The alias menu is used to help users finding the recipients @@ -600,8 +652,8 @@ - - Attachment Menu + + Attachment Menu As will be later discussed in detail, mutt-ng features a good @@ -620,8 +672,8 @@ - - Key Menu + + Key Menu FIXME @@ -640,8 +692,8 @@ - - Moving Around in Menus + + Moving Around in Menus Information is presented in menus, very similar to ELM. Here is a @@ -650,8 +702,8 @@ - - Default Menu Movement Keys +
+ Most commonly used movement bindings @@ -662,43 +714,43 @@ - j or Down - next-entry + j or Down + move to the next entry - k or Up - previous-entry + k or Up + move to the previous entry - z or PageDn - page-down + z or PageDn + go to the next page - Z or PageUp - page-up + Z or PageUp + go to the previous page - = or Home - first-entry + = or Home + jump to the first entry - * or End - last-entry + * or End + jump to the last entry - q - quit + q + exit the current menu - ? - help + ? + list all key bindings for the current menu @@ -716,7 +768,7 @@ - Editing Input Fields + Editing Input Fields Mutt-ng has a builtin line editor which is used as the primary way to @@ -728,8 +780,8 @@ -
- Built-In Editor Functions +
+ Line Editor Functions @@ -740,113 +792,113 @@ - ^A or <Home> - bol + A or Home + move to the start of the line - ^B or <Left> - backward-char + B or Left + move back one char - Esc B - backward-word + B + move back one word - ^D or <Delete> - delete-char + D or Delete + delete the char under the cursor - ^E or <End> - eol + E or End + move to the end of the line - ^F or <Right> - forward-char + F or Right + move forward one char - Esc F - forward-word + F + move forward one word - <Tab> - complete + Tab + complete filename or alias - ^T - complete-query + T + complete address with query - ^K - kill-eol + K + delete to the end of the line - ESC d - kill-eow + d + delete to the end of the word - ^W - kill-word + W + kill the word in front of the cursor - ^U - kill-line + U + delete entire line - ^V - quote-char + V + quote the next typed key - <Up> - history-up + Up + recall previous string from history - <Down> - history-down + Down + recall next string from history - <BackSpace> - backspace + BackSpace + kill the char in front of the cursor - Esc u - upcase-word + u + convert word to upper case - Esc l - downcase-word + l + convert word to lower case - Esc c - capitalize-word + c + capitalize the word - ^G - n/a + G + abort - <Return> - n/a + Return + finish editing @@ -856,27 +908,21 @@ - You can remap the editor functions using the - bind - - command. For example, to make the Delete key - delete the character in - front of the cursor rather than under, you could use + You can remap the editor functions using the + command. For example, to make + the Delete key delete the character in front + of the cursor rather than under, you could use bind editor <delete> backspace - - - - - - Reading Mail - The Index and Pager + + Reading Mail - The Index and Pager Similar to many other mail clients, there are two modes in which mail @@ -891,13 +937,13 @@ modes. - - The Message Index + + The Message Index -
- Default Index Menu Bindings +
+ Most commonly used Index Bindings @@ -907,35 +953,151 @@ - c change to a different mailbox - ESC c change to a folder in read-only mode - C copy the current message to another mailbox - ESC C decode a message and copy it to a folder - ESC s decode a message and save it to a folder - D delete messages matching a pattern - d delete the current message - F mark as important - l show messages matching a pattern - N mark message as new - o change the current sort method - O reverse sort the mailbox - q save changes and exit - s save-message - T tag messages matching a pattern - t toggle the tag on a message - ESC t toggle tag on entire message thread - U undelete messages matching a pattern - u undelete-message - v view-attachments - x abort changes and exit - <Return> display-message - <Tab> jump to the next new message - @ show the author's full e-mail address - $ save changes to mailbox - / search - ESC / search-reverse - ^L clear and redraw the screen - ^T untag messages matching a pattern + + c + + change to a different mailbox + + + c + + change to a folder in read-only mode + + + C + + copy the current message to another mailbox + + + C + + decode a message and copy it to a folder + + + s + + decode a message and save it to a folder + + + D + + delete messages matching a pattern + + + d + + delete the current message + + + F + + mark as important + + + l + + show messages matching a pattern + + + N + + mark message as new + + + o + + change the current sort method + + + O + + reverse sort the mailbox + + + q + + save changes and exit + + + s + + save-message + + + T + + tag messages matching a pattern + + + t + + toggle the tag on a message + + + t + + toggle tag on entire message thread + + + U + + undelete messages matching a pattern + + + u + + undelete-message + + + v + + view-attachments + + + x + + abort changes and exit + + + Return + + display-message + + + Tab + + jump to the next new or unread message + + + @ + + show the author's full e-mail address + + + $ + + save changes to mailbox + + + / + + search + + + / + + search-reverse + + + L + + clear and redraw the screen + + + T + + untag messages matching a pattern +
@@ -1074,7 +1236,7 @@ Furthermore, the following flags reflect who the message is addressed to. They can be customized with the - $to_chars variable. + variable. @@ -1123,14 +1285,12 @@ - - - - The Pager + + The Pager By default, Mutt-ng uses its builtin pager to display the body of @@ -1141,8 +1301,8 @@ - - Default Pager Menu Bindings +
+ Most commonly used Pager Bindings @@ -1152,17 +1312,61 @@ - <Return> go down one line - <Space> display the next page (or next message if at the end of a message) - - go back to the previous page - n search for next match - S skip beyond quoted text - T toggle display of quoted text - ? show key bindings - / search for a regular expression (pattern) - ESC / search backwards for a regular expression - \ toggle search pattern coloring - ^ jump to the top of the message + + Return + + go down one line + + + Space + + display the next page (or next message if at the end of a message) + + + - + + go back to the previous page + + + n + + search for next match + + + S + + skip beyond quoted text + + + T + + toggle display of quoted text + + + ? + + show key bindings + + + / + + search for a regular expression (pattern) + + + / + + search backwards for a regular expression + + + \ + + toggle search pattern coloring + + + ^ + + jump to the top of the message +
@@ -1180,19 +1384,17 @@ - Also, the internal pager supports a couple other advanced features. - For - one, it will accept and translate the ``standard'' nroff sequences - forbold 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-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 color - objects to specify a color or mono attribute for them. + Also, the internal pager supports a couple other advanced + features. For one, it will accept and translate the + ``standard'' nroff sequences forbold 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-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 objects to specify a color or mono attribute + for them. @@ -1201,12 +1403,12 @@ linkend="color">color into the correct color and character settings. The sequences Mutt-ng supports are: ESC [ Ps;Ps;Ps;...;Ps m (see table below for possible values for - Ps). + Ps). - +
ANSI Escape Sequences @@ -1216,19 +1418,40 @@ linkend="color">color - 0 All Attributes Off - 1 Bold on - 4 Underline on - 5 Blink on - 7 Reverse video on - 3x Foreground color is x (see table below) - 4x Background color is x (see table below) + + 0 + All Attributes Off + + + 1 + Bold on + + + 4 + Underline on + + + 5 + Blink on + + + 7 + Reverse video on + + + 3x + Foreground color is x (see table below) + + + 4x + Background color is x (see table below) +
- +
ANSI Colors @@ -1238,14 +1461,38 @@ linkend="color">color - 0 black - 1 red - 2 green - 3 yellow - 4 blue - 5 magenta - 6 cyan - 7 white + + 0 + black + + + 1 + red + + + 2 + green + + + 3 + yellow + + + 4 + blue + + + 5 + magenta + + + 6 + cyan + + + 7 + white +
@@ -1256,18 +1503,16 @@ linkend="color">color Mutt-ng uses these attributes for handling text/enriched messages, and they - can also be used by an external autoview + can also be used by an external script for highlighting purposes. Note: If you change the colors for your display, for example by changing the color associated with color2 for your xterm, then that color will be used instead of green. - - Threaded Mode + Threaded Mode When the mailbox is sorted by @@ -1282,8 +1527,8 @@ linkend="color">color - - Default Thread Function Bindings +
+ Most commonly used thread-related bindings @@ -1293,20 +1538,76 @@ linkend="color">color - ^D delete-thread delete all messages in the current thread - ^U undelete-thread undelete all messages in the current thread - ^N next-thread jump to the start of the next thread - ^P previous-thread jump to the start of the previous thread - ^R read-thread mark the current thread as read - ESC d delete-subthread delete all messages in the current subthread - ESC u undelete-subthread undelete all messages in the current subthread - ESC n next-subthread jump to the start of the next subthread - ESC p previous-subthread jump to the start of the previous subthread - ESC r read-subthread mark the current subthread as read - ESC t tag-thread toggle the tag on the current thread - ESC v collapse-thread toggle collapse for the current thread - ESC V collapse-all toggle collapse for all threads - P parent-message jump to parent message in thread + + D + + delete all messages in the current thread + + + U + + undelete all messages in the current thread + + + N + + jump to the start of the next thread + + + P + + jump to the start of the previous thread + + + R + + mark the current thread as read + + + d + + delete all messages in the current subthread + + + u + + undelete all messages in the current subthread + + + n + + jump to the start of the next subthread + + + p + + jump to the start of the previous subthread + + + r + + mark the current subthread as read + + + t + + toggle the tag on the current thread + + + v + + toggle collapse for the current thread + + + V + + toggle collapse for all threads + + + P + + jump to parent message in thread +
@@ -1319,53 +1620,42 @@ linkend="color">color only the first message in the thread and hides the others. This is useful when threads contain so many messages that you can only see a handful of threads - onthe screen. See %M in - index-format - - . + onthe screen. See %M in + . + + + For example, you could use - "%?M?(#%03M)&(%4l)?" in - index-format - + %?M?(#%03M)&(%4l)? in to optionally display the number of hidden messages if the thread is collapsed. - See also: strict-threads. + See also the variable. - - - Miscellaneous Functions + + Miscellaneous Functions - create-alias - (default: a) - + a Creates a new alias based upon the current message (or prompts for a - new one). Once editing is complete, an alias - command is added to the file specified by the - alias-file - + new one). Once editing is complete, an + command is added to the file specified by the variable for future use. Note: - Specifying an alias-file - does not add the aliases specified there-in, you must also - source - + Specifying an + does not add the aliases specified there-in, you must also the file. - check-traditional-pgp - (default: ESC P) - + P @@ -1373,28 +1663,22 @@ linkend="color">color encrypted with PGP the "traditional" way, that is, without proper MIME tagging. Technically, this function will temporarily change the MIME content types of the body parts containing PGP data; this - is similar to the edit-type + is similar to the function's effect. - display-toggle-weed - (default: h) - + h - Toggles the weeding of message header fields specified by - ignore - + Toggles the weeding of message header fields specified by commands. - edit - (default: e) - + e @@ -1406,11 +1690,9 @@ linkend="color">color - edit-type - - (default: ˆE on the attachment menu, and in the pager and index - menus; ˆT on the - compose menu) + + (default: E on the attachment menu, and in the pager and index + menus; T on the compose menu) @@ -1424,17 +1706,13 @@ linkend="color">color - Note that this command is also available on the - compose-menu - + Note that this command is also available on the compose-menu .There, it's used to fine-tune the properties of attachments you are going to send. - enter-command - (default: ``:'') - + : @@ -1442,15 +1720,13 @@ linkend="color">color a configuration file. A common use is to check the settings of variables, or - in conjunction with macro to change + in conjunction with to change settings on the fly. - extract-keys - (default: ˆK) - + K @@ -1459,10 +1735,7 @@ linkend="color">color - forget-passphrase - (default: - ˆF) - + F @@ -1471,20 +1744,16 @@ linkend="color">color - list-reply - (default: L) - + L Reply to the current or tagged message(s) by extracting any addresses which - match the regular expressions given by the - lists - + match the regular expressions given by the commands, but also honor any Mail-Followup-To header(s) if the - honor-followup-to + configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the @@ -1493,28 +1762,21 @@ linkend="color">color - pipe-message - (default: |) - + Asks for an external Unix command and pipes the current or - tagged message(s) to it. The variables - pipe-decode - - ,pipe-split, - pipe-sep - - and wait-key control the exact - behavior of this - function. + tagged message(s) to it. The variables + , + , + and + + control the exact behavior of this function. - resend-message - (default: ESC e) - + e @@ -1525,7 +1787,7 @@ linkend="color">color folders". It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers - included here depends on the value of the weed + included here depends on the value of the variable. @@ -1537,15 +1799,12 @@ linkend="color">color - shell-escape - (default: !) - + ! - Asks for an external Unix command and executes it. The - wait-key - + Asks for an external Unix command and executes it. The + can be used to control whether Mutt-ng will wait for a key to be pressed when the command returns @@ -1554,15 +1813,12 @@ linkend="color">color - toggle-quoted - (default: T) - + T - The pager uses the - quote-regexp - + The pager uses the + variable to detect quoted text when displaying the body of the message. This function toggles the displayof the quoted material in the message. It is particularly @@ -1572,9 +1828,7 @@ linkend="color">color - skip-quoted - (default: S) - + S @@ -1586,14 +1840,13 @@ linkend="color">color - - + - - Sending Mail + + Sending Mail The following bindings are available in the index @@ -1603,8 +1856,8 @@ linkend="color">color - - Default Mail Composition Bindings +
+ Most commonly used Mail Composition Bindings @@ -1614,13 +1867,41 @@ linkend="color">color - m compose compose a new message - r reply reply to sender - g group-reply reply to all recipients - L list-reply reply to mailing list address - f forward forward message - b bounce bounce (remail) message - ESC k mail-key mail a PGP public key to someone + + m + + compose a new message + + + r + + reply to sender + + + g + + reply to all recipients + + + L + + reply to mailing list address + + + f + + forward message + + + b + + bounce (remail) message + + + k + + mail a PGP public key to someone +
@@ -1631,25 +1912,22 @@ linkend="color">color Bouncing a message sends the message as is to the recipient you specify. Forwarding a message allows you to add comments or modify the message you are forwarding. These items are discussed - in greater detail in the next chapter - forwarding-mail - - . + in greater detail in the next chapter forwarding-mail. - - Composing new messages + + Composing new messages - When you want to send an email using mutt-ng, simply press m on + When you want to send an email using mutt-ng, simply press m on your keyboard. Then, mutt-ng asks for the recipient via a prompt in the last line: - -To: + +To: @@ -1671,20 +1949,20 @@ To: - + set editor = "vim +/^$/ -c ':set tw=72'" set editor = "nano" -set editor = "emacs" +set editor = "emacs" If you don't set your preferred editor in your configuration, mutt-ng - first looks whether the environment variable $VISUAL is set, and if + first looks whether the environment variable is set, and if so, it takes its value as editor command. Otherwise, it has a look - at $EDITOR and takes its value if it is set. If no + at and takes its value if it is set. If no editor command - can be found, mutt-ng simply assumes vi to be the + can be found, mutt-ng simply assumes to be the default editor, since it's the most widespread editor in the Unix world and it's pretty @@ -1711,13 +1989,13 @@ set editor = "emacs" - At this point, you can add more attachments, pressing a, you - can edit the recipient addresses, pressing t for + At this point, you can add more attachments, pressing a, you + can edit the recipient addresses, pressing t for the "To:" field, - c for the "Cc:" field, and b + c for the "Cc:" field, and b for the "Bcc: field. You can - also edit the subject the subject by simply pressing s or the - email message that you've entered before by pressing e. You will + also edit the subject the subject by simply pressing s or the + email message that you've entered before by pressing e. You will then again return to the editor. You can even edit the sender, by pressing <esc>f, but this shall only be used with @@ -1732,8 +2010,8 @@ set editor = "emacs" - -set edit_headers + +set edit_headers @@ -1745,8 +2023,8 @@ set edit_headers - - Default Compose Menu Bindings +
+ Most commonly used Compose Menu Bindings @@ -1756,26 +2034,106 @@ set edit_headers - a attach-file attach a file - A attach-message attach message(s) to the message - ESC k attach-key attach a PGP public key - d edit-description edit description on attachment - D detach-file detach a file - t edit-to edit the To field - ESC f edit-from edit the From field - r edit-reply-to edit the Reply-To field - c edit-cc edit the Cc field - b edit-bcc edit the Bcc field - y send-message send the message - s edit-subject edit the Subject - S smime-menu select S/MIME options - f edit-fcc specify an ``Fcc'' mailbox - p pgp-menu select PGP options - P postpone-message postpone this message until later - q quit quit (abort) sending the message - w write-fcc write the message to a folder - i ispell check spelling (if available on your system) - ^F forget-passphrase wipe passphrase(s) from memory + + a + + attach a file + + + A + + attach message(s) to the message + + + k + + attach a PGP public key + + + d + + edit description on attachment + + + D + + detach a file + + + t + + edit the To field + + + f + + edit the From field + + + r + + edit the Reply-To field + + + c + + edit the Cc field + + + b + + edit the Bcc field + + + y + + send the message + + + s + + edit the Subject + + + S + + select S/MIME options + + + f + + specify an ``Fcc'' mailbox + + + p + + select PGP options + + + P + + postpone this message until later + + + q + + quit (abort) sending the message + + + w + + write the message to a folder + + + i + + check spelling (if available on your system) + + + F + + wipe passphrase(s) from memory +
@@ -1789,9 +2147,8 @@ set edit_headers theywill be attached to the message you are sending. Note that certainoperations like composing a new mail, replying, forwarding, etc. are - not permitted when you are in that folder. The %r in - status-format - + not permitted when you are in that folder. The %r + in will change to a 'A' to indicate that you are in attach-message mode. @@ -1800,18 +2157,17 @@ set edit_headers - - - Replying + + Replying - - Simple Replies + + Simple Replies When you want to reply to an email message, select it in the index - menu and then press r. Mutt-ng's behaviour is + menu and then press r. Mutt-ng's behaviour is then similar to the behaviour when you compose a message: first, you will be asked for the recipient, then for the subject, and then, mutt-ng will start @@ -1821,12 +2177,12 @@ set edit_headers - + On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote: > Bill, can you please send last month's progress report to Mr. > Morgan? We also urgently need the cost estimation for the new > production server that we want to set up before our customer's -> project will go live. +> project will go live. @@ -1843,28 +2199,28 @@ On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote: The quote attribution is configurable, by default it is set to - -set attribution = "On %d, %n wrote:" + +set attribution = "On %d, %n wrote:" It can also be set to something more compact, e.g. - -set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" + +set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" The example above results in the following attribution: - + * Michael Svensson <svensson@foobar.com> [05-03-06 17:02]: > Bill, can you please send last month's progress report to Mr. > Morgan? We also urgently need the cost estimation for the new > production server that we want to set up before our customer's -> project will go live. +> project will go live. @@ -1887,18 +2243,17 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" - - - Group Replies + + Group Replies In the situation where a group of people uses email as a discussion, most of the emails will have one or more recipients, and probably several "Cc:" recipients. The group reply - functionalityensures that when you press g - instead of r to do a reply, + functionalityensures that when you press g + instead of r to do a reply, each and every recipient that is contained in the original message will receive a copy of the message, either as normal recipient or as "Cc:" recipient. @@ -1908,11 +2263,10 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" - - - List Replies + + List Replies When you use mailing lists, it's generally better to send your @@ -1922,7 +2276,7 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" - To do a list reply, simply press L. If the email + To do a list reply, simply press L. If the email contains a Mail-Followup-To: header, its value will be used as reply @@ -1935,8 +2289,8 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" - -lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ + +lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ @@ -1955,14 +2309,12 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - - - - Editing the message header + + Editing the message header When editing the header of your outgoing message, there are a couple @@ -1982,12 +2334,10 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ You can also attach files to your message by specifying - - Attach: filename [ - description - - ] - + + +Attach: filename [description] + where filename is the file to attach and description @@ -2002,7 +2352,8 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - Also see edit-headers. + Also see the and + variables @@ -2011,26 +2362,18 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - - Using Mutt-ng with PGP + + Using Mutt-ng with PGP If you want to use PGP, you can specify - - - - Pgp: [ E | - S - - | S<id> ] - - - + +Pgp: [E | S | S id] + ``E'' encrypts, ``S'' signs and - ``S<id>'' signs with the given key, setting - pgp-sign-as - + ``S<id>'' signs with the given key, setting + permanently. @@ -2048,7 +2391,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ In these cases, you are dropped into a menu with a list of keys from which you can select one. When you quit this menu, or mutt can't find any matching keys, you are prompted for a user ID. You can, as - usually, abort this prompt using ˆG. When + usually, abort this prompt using G. When you do so, mutt will return to the compose screen. @@ -2059,21 +2402,19 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - Most fields of the entries in the key selection menu (see also - pgp-entry-format - - ) + Most fields of the entries in the key selection menu (see also + ) have obvious meanings. But some explanations on the capabilities, flags, and validity fields are in order. - The flags sequence (%f) will expand to one of the following + The flags sequence (%f) will expand to one of the following flags: - +
PGP Key Menu Flags @@ -2083,10 +2424,22 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - R The key has been revoked and can't be used. - X The key is expired and can't be used. - d You have marked the key as disabled. - c There are unknown critical self-signature packets. + + R + The key has been revoked and can't be used. + + + X + The key is expired and can't be used. + + + d + You have marked the key as disabled. + + + c + There are unknown critical self-signature packets. +
@@ -2094,7 +2447,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - The capabilities field (%c) expands to a two-character + The capabilities field (%c) expands to a two-character sequencerepresenting a key's capabilities. The first character gives the key's encryption capabilities: A minus sign ( - @@ -2120,7 +2473,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - Finally, the validity field (%t) indicates how well-certified + Finally, the validity field (%t) indicates how well-certified a user-id is. A question mark (?) indicates undefined validity, a minus @@ -2139,8 +2492,8 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - - Sending anonymous messages via mixmaster + + Sending anonymous messages via mixmaster You may also have configured mutt to co-operate with Mixmaster, an @@ -2171,7 +2524,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ and chain-next functions, which are by default bound to the left - and right arrows and to the h and l keys (think vi + and right arrows and to the h and l keys (think vi keyboard bindings). To insert a remailer at the current chain position, use the insert function. To append a remailer behind @@ -2189,9 +2542,9 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ Note that different remailers do have different capabilities, - indicated in the %c entry of the remailer menu lines (see - mix-entry-format). Most - important is + indicated in the %c entry of the remailer menu lines (see + ). + Most important is the ``middleman'' capability, indicated by a capital ``M'': This means that the remailer in question cannot be used as the final element of a chain, but will only forward messages to other @@ -2212,7 +2565,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - Forwarding and Bouncing Mail + Forwarding and Bouncing Mail Often, it is necessary to forward mails to other people. @@ -2222,7 +2575,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ The first one is regular forwarding, as you probably know it from - other mail clients. You simply press f, enter the + other mail clients. You simply press f, enter the recipient email address, the subject of the forwarded email, and then you can edit the message to be forwarded in the editor. The forwarded @@ -2232,18 +2585,18 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ - ------ Forwarded message from Lucas User <luser@example.com> ----- + +----- Forwarded message from Lucas User <luser@example.com> ----- -From: Lucas User <luser@example.com> +From: Lucas User <luser@example.com> Date: Thu, 02 Dec 2004 03:08:34 +0100 -To: Michael Random <mrandom@example.com> +To: Michael Random <mrandom@example.com> Subject: Re: blackmail Pay me EUR 50,000.- cash or your favorite stuffed animal will die a horrible death. ------ End forwarded message ----- +----- End forwarded message ----- @@ -2259,7 +2612,7 @@ a horrible death. another address, it will be sent in practically the same format you send it (except for headers that are created during transporting the - message). To bounce a message, press b and enter the + message). To bounce a message, press b and enter the recipient email address. By default, you are then asked whether you really want to bounce the message to the specified recipient. If you answer @@ -2282,17 +2635,15 @@ a horrible death. - Postponing Mail + Postponing Mail At times it is desirable to delay sending a message that you have already begun to compose. When the postpone-message function is used in the compose menu, the body of your message and attachments - are stored in the mailbox specified by the - postponed - - variable. This means that you can recall the + are stored in the mailbox specified by the + variable. This means that you can recall the message even if you exit Mutt-ng and then restart it at a later time. @@ -2316,7 +2667,7 @@ a horrible death. - See also the postpone quad-option. + See also the quad-option. @@ -2328,14 +2679,17 @@ a horrible death. + + - + + - - Configuration + + Configuration - - Locations of Configuration Files + + Locations of Configuration Files While the default configuration (or ``preferences'') make Mutt-ng @@ -2379,30 +2733,27 @@ a horrible death. - - Basic Syntax of Initialization Files + + Basic Syntax of Initialization Files - An initialization file consists of a series of - commands - - .Each line of the file may contain one or more commands. + An initialization file consists of a series of commands. Each line of the file may contain one or more commands. When multiple commands are used, they must be separated by a semicolon (;). - -set realname='Mutt-ng user' ; ignore x- + +set realname='Mutt-ng user' ; ignore x- The hash mark, or pound sign - (``#''), is used as a ``comment'' character. You can use it to + (``#''), is used as a ``comment'' character. You can use it to annotate your initialization file. All text after the comment character to the end of the line is ignored. For example, - -my_hdr X-Disclaimer: Why are you listening to me? # This is a comment + +my_hdr X-Disclaimer: Why are you listening to me? # This is a comment @@ -2416,52 +2767,52 @@ my_hdr X-Disclaimer: Why are you listening to me? # This is a commentnot for single quotes. - \ quotes the next character, just as in shells such as bash and + \ quotes the next character, just as in shells such as bash and zsh. For example, if want to put quotes ``"'' inside of a string, you can use - ``\'' to force the next character to be a literal instead of + ``\'' to force the next character to be a literal instead of interpreted character. - -set realname="Michael \"MuttDude\" Elkins" + +set realname="Michael \"MuttDude\" Elkins" - ``\\'' means to insert a literal ``\'' into the line. - ``\n'' and ``\r'' have their usual C meanings of linefeed and + ``\\'' means to insert a literal ``\'' into the line. + ``\n'' and ``\r'' have their usual C meanings of linefeed and carriage-return, respectively. - A \ at the end of a line can be used to split commands over + A \ at the end of a line can be used to split commands over multiple lines, provided that the split points don't appear in the middle of command names. Please note that, unlike the various shells, mutt-ng interprets a - ``\'' + ``\'' at the end of a line also in comments. This allows you to disable a command - split over multiple lines with only one ``#''. + split over multiple lines with only one ``#''. - + # folder-hook . \ -set realname="Michael \"MuttDude\" Elkins" +set realname="Michael \"MuttDude\" Elkins" @@ -2471,7 +2822,7 @@ set realname="Michael \"MuttDude\" Elkins" at the end of the commented line extends the current line with the next line - then referred to as a ``continuation line''. As the first line is - commented with a hash (#) all following continuation lines are also + commented with a hash (#) all following continuation lines are also part of a comment and therefore are ignored, too. So take care of comments when continuation lines are involved within your setup files! @@ -2483,17 +2834,17 @@ set realname="Michael \"MuttDude\" Elkins" - + line1\ line2a # line2b\ line3\ line4 -line5 +line5 - line1 ``continues'' until line4. however, the part after the # is a + 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 thus is interpreted again. @@ -2510,16 +2861,16 @@ line5 - - Expansion within variables + + Expansion within variables Besides just assign static content to variables, there's plenty of ways of adding external and more or less dynamic content. - - Commands' Output + + Commands' Output It is possible to substitute the output of a Unix command in an @@ -2529,8 +2880,8 @@ line5 - -my_hdr X-Operating-System: `uname -a` + +my_hdr X-Operating-System: `uname -a` @@ -2543,27 +2894,27 @@ my_hdr X-Operating-System: `uname -a` - - Environment Variables + + Environment Variables UNIX environments can be accessed like the way it is done in shells like sh and bash: Prepend the name of the environment by a - ``$'' sign. For example, + ``$'' sign. For example, - -set record=+sent_on_$HOSTNAME + +set record=+sent_on_$HOSTNAME - sets the record variable to the - string +sent_on_ and appends the + sets the variable to the + string +sent_on_ and appends the value of the evironment - variable $HOSTNAME. + variable . @@ -2574,8 +2925,8 @@ set record=+sent_on_$HOSTNAME - - Configuration Variables + + Configuration Variables As for environment variables, the values of all configuration @@ -2584,28 +2935,23 @@ set record=+sent_on_$HOSTNAME - -set imap_home_namespace = $folder + +set imap_home_namespace = $folder - would set the value of - imap-home-namespace - - to the value to - which folder is currently set - to. + would set the value of + to the value to which + is currently set to. Note: There're no logical links established in such cases so - that the the value for - imap-home-namespace - + that the the value for won't change even - if folder gets changed. + if gets changed. @@ -2617,14 +2963,14 @@ set imap_home_namespace = $folder - - Self-Defined Variables + + Self-Defined Variables Mutt-ng flexibly allows users to define their own variables. To avoid conflicts with the standard set and to prevent misleading error messages, there's a reserved namespace for them: all - user-defined variables must be prefixed with user_ and can be + user-defined variables must be prefixed with user_ and can be used just like any ordinary configuration or environment variable. @@ -2636,9 +2982,9 @@ set imap_home_namespace = $folder - + macro generic <F1> "!less -r /path/to/manual" "Show manual" -macro pager <F1> "!less -r /path/to/manual" "Show manual" +macro pager <F1> "!less -r /path/to/manual" "Show manual" @@ -2652,11 +2998,11 @@ macro pager <F1> "!less -r /path/to/manual" "Show manual" - + set user_manualcmd = "!less -r /path/to_manual" macro generic <F1> "$user_manualcmd<enter>" "Show manual" macro pager <F1> "$user_manualcmd<enter>" "Show manual" -macro index <F1> "$user_manualcmd<enter>" "Show manual" +macro index <F1> "$user_manualcmd<enter>" "Show manual" @@ -2666,8 +3012,8 @@ macro index <F1> "$user_manualcmd<enter>" "Show manual" - -macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" + +macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" @@ -2695,22 +3041,22 @@ macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" - + set user_foo = 42 -set user_foo = 666 +set user_foo = 666 - the variable $user_foo has a current value + the variable $user_foo has a current value of 666 and an initial of 42. The query - -set ?user_foo + +set ?user_foo @@ -2720,8 +3066,8 @@ set ?user_foo - -reset user_foo + +reset user_foo @@ -2732,8 +3078,8 @@ reset user_foo - -unset user_foo + +unset user_foo @@ -2744,14 +3090,14 @@ unset user_foo - - Pre-Defined Variables + + Pre-Defined Variables In order to allow users to share one setup over a number of different machines without having to change its contents, there's a number of pre-defined variables. These are prefixed with - muttng_ and are read-only, i.e. they cannot + muttng_ and are read-only, i.e. they cannot be set, unset or reset. The reference chapter lists all available variables. @@ -2767,8 +3113,8 @@ unset user_foo - -muttng -Q muttng_docdir + +$ muttng -Q muttng_docdir @@ -2780,8 +3126,8 @@ muttng -Q muttng_docdir - -set user_manualcmd = '!less -r /path/to_manual' + +set user_manualcmd = '!less -r /path/to_manual' @@ -2791,8 +3137,8 @@ set user_manualcmd = '!less -r /path/to_manual' - -set user_manualcmd = "!less -r $muttng_docdir/manual.txt" + +set user_manualcmd = "!less -r $muttng_docdir/manual.txt" @@ -2813,8 +3159,8 @@ set user_manualcmd = "!less -r $muttng_docdir/manual.txt" - -folder-hook . "set user_current_folder = $muttng_folder_name" + +folder-hook . "set user_current_folder = $muttng_folder_name" @@ -2825,27 +3171,27 @@ folder-hook . "set user_current_folder = $muttng_folder_name" - -folder-hook . "set user_current_folder = some_folder" + +folder-hook . "set user_current_folder = some_folder" - with some_folder being the name of the + with some_folder being the name of the first folder muttng opens. On the contrary, - -folder-hook . 'set user_current_folder = $muttng_folder_name' + +folder-hook . 'set user_current_folder = $muttng_folder_name' will be executed at runtime because of the single quotes so that - user_current_folder will always have + user_current_folder will always have the value of the currently opened folder. @@ -2856,8 +3202,8 @@ folder-hook . 'set user_current_folder = $muttng_folder_name' - -folder-hook . 'source ~/.mutt/score-$muttng_folder_name' + +folder-hook . 'source ~/.mutt/score-$muttng_folder_name' @@ -2868,8 +3214,8 @@ folder-hook . 'source ~/.mutt/score-$muttng_folder_name' - - Type Conversions + + Type Conversions A note about variable's types during conversion: internally @@ -2882,12 +3228,12 @@ folder-hook . 'source ~/.mutt/score-$muttng_folder_name' - + set read_inc = 100 set folder = $read_inc set read_inc = $folder set user_magic_number = 42 -set folder = $user_magic_number +set folder = $user_magic_number @@ -2895,14 +3241,13 @@ set folder = $user_magic_number - - Defining/Using aliases - + + Defining/Using aliases + - Usage: alias key - address - - [ , address, ... ] + + key address [, address,...] + @@ -2925,17 +3270,16 @@ set folder = $user_magic_number - unalias [ * | key - ... - - ] + + [* | key ... ] + - + alias muttdude me@cs.hmc.edu (Michael Elkins) -alias theguys manny, moe, jack +alias theguys manny, moe, jack @@ -2943,26 +3287,21 @@ alias theguys manny, moe, jack Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a special file. The alias command can appear anywhere in - a configuration file, as long as this file is - source - - .Consequently, you can have multiple alias files, or + a configuration file, as long as this file is . + Consequently, you can have multiple alias files, or you can have all aliases defined in your muttrc. - On the other hand, the create-alias - function can use only one file, the one pointed to by the - alias-file - + On the other hand, the + function can use only one file, the one pointed to by the + variable (which is - ˜/.muttrc by default). This file is not + ~/.muttrc by default). This file is not special either, in the sense that Mutt-ng will happily append aliases to any file, but in - order for the new aliases to take effect you need to explicitly - source - + order for the new aliases to take effect you need to explicitly this file too. @@ -2972,10 +3311,10 @@ alias theguys manny, moe, jack - + source /usr/local/share/Mutt-ng.aliases source ~/.mail_aliases -set alias_file=~/.mail_aliases +set alias_file=~/.mail_aliases @@ -2987,7 +3326,8 @@ set alias_file=~/.mail_aliases prompt. You can also enter aliases in your editor at the appropriate headers if you have the - edit-headers variable set. + + variable set. @@ -3017,13 +3357,13 @@ set alias_file=~/.mail_aliases - - Changing the default key bindings + + Changing the default key bindings - Usage: bind map key - function - + + map key function + @@ -3150,21 +3490,21 @@ set alias_file=~/.mail_aliases key is the key (or key sequence) you wish to bind. To specify a - control character, use the sequence \Cx, + control character, use the sequence \Cx, where x is the letter of the control character (for example, to specify control-A use - ``\Ca''). Note that the case of x as well as - \C is - ignored, so that \CA, \Ca, - \cA + ``\Ca''). Note that the case of x as well as + \C is + ignored, so that \CA, \Ca, + \cA - and \ca are all + and \ca are all equivalent. An alternative form is to specify the key as a three digit - octal number prefixed with a ``\'' (for example - \177 + octal number prefixed with a ``\'' (for example + \177 is - equivalent to \c?). + equivalent to \c?). @@ -3173,7 +3513,7 @@ set alias_file=~/.mail_aliases - +
Alternative Key Names @@ -3183,29 +3523,98 @@ set alias_file=~/.mail_aliases - \t tab - <tab> tab - <backtab> backtab / shift-tab - \r carriage return - \n newline - \e escape - <esc> escape - <up> up arrow - <down> down arrow - <left> left arrow - <right> right arrow - <pageup> Page Up - <pagedown> Page Down - <backspace> Backspace - <delete> Delete - <insert> Insert - <enter> Enter - <return> Return - <home> Home - <end> End - <space> Space bar - <f1> function key 1 - <f10> function key 10 + + \t + tab + + + <tab> + tab + + + <backtab> + backtab / shift-tab + + + \r + carriage return + + + \n + newline + + + \e + escape + + + <esc> + escape + + + <up> + up arrow + + + <down> + down arrow + + + <left> + left arrow + + + <right> + right arrow + + + <pageup> + Page Up + + + <pagedown> + Page Down + + + <backspace> + Backspace + + + <delete> + Delete + + + <insert> + Insert + + + <enter> + Enter + + + <return> + Return + + + <home> + Home + + + <end> + End + + + <space> + Space bar + + + <f1> + function key 1 + + + <f10> + function key 10 +
@@ -3223,10 +3632,8 @@ set alias_file=~/.mail_aliases key is pressed. - For a complete list of functions, see the - functions - - .The special function noop unbinds the specified key + For a complete list of functions, see the functions. + The special function noop unbinds the specified key sequence. @@ -3237,27 +3644,25 @@ set alias_file=~/.mail_aliases - Defining aliases for character sets - + Defining aliases for character sets + + - Usage: charset-hook alias - charset - - - Usage: iconv-hook charset - local-charset - + Usage: alias charset + + + Usage: charset local-charset - The charset-hook command defines an alias for a + The command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to mutt. - The iconv-hook command defines a system-specific + The command defines a system-specific name for a character set. This is helpful when your systems character conversion library insists on using strange, system-specific names @@ -3271,30 +3676,28 @@ set alias_file=~/.mail_aliases - Setting variables based upon mailbox + Setting variables based upon mailbox - Usage: folder-hook [!]regexp - command - + Usage: [!]regexp command It is often desirable to change settings based on which mailbox you are - reading. The folder-hook command provides a method by which you can + reading. The command provides a method by which you can execute any configuration command. regexp is a regular expression specifying in which mailboxes to execute command before loading. If a mailbox - matches multiple folder-hook's, they are executed in the order given in + matches multiple 's, they are executed in the order given in the muttrc. Note: if you use the ``!'' shortcut - for spoolfile at the beginning of the + for at the beginning of the pattern, you must place it inside of double or single quotes in order to distinguish it from the logical not operator for the expression. @@ -3309,8 +3712,8 @@ set alias_file=~/.mail_aliases - -folder-hook mutt set sort=threads + +folder-hook mutt set sort=threads @@ -3323,8 +3726,8 @@ folder-hook mutt set sort=threads - -folder-hook . set sort=date-sent + +folder-hook . set sort=date-sent @@ -3334,14 +3737,13 @@ folder-hook . set sort=date-sent - - Keyboard macros + + Keyboard macros - Usage: macro menu key - sequence - - [ description ] + + menu key sequence [description] + @@ -3366,22 +3768,18 @@ folder-hook . set sort=date-sent - key and sequence are expanded - by the same rules as the bind. There are - some additions however. The - first is that control characters in sequence can - also be specified - as ˆx. In order to get a caret (`ˆ'') - you need to use - ˆˆ. Secondly, to specify a certain key - such as up - or to invoke a function directly, you can use the format + key and sequence are + expanded by the same rules as the . There are some additions however. The first + is that control characters in sequence can + also be specified as ^x. In order to get a + caret (`^'') you need to specify it twice. Secondly, + to specify a certain key such as up or to + invoke a function directly, you can use the format <key name> and <function - name> - - .For a listing of key - names see the section on bind. Functions - are listed in the functions. + name> .For a listing of key names see the + section on . Functions are + listed in the functions. @@ -3411,24 +3809,17 @@ folder-hook . set sort=date-sent - - Using color and mono video attributes - + + Using color and mono video attributes + - Usage: color object - foreground - - background [ regexp - ] - - Usage: color index foreground - background - - pattern - - Usage: uncolor index pattern - [ pattern ... ] - + object foreground background [regexp] + + + index foreground pattern + + + index pattern [pattern ...] @@ -3518,7 +3909,7 @@ folder-hook . set sort=date-sent - quoted (text matching quote-regexp in the body of a message) + quoted (text matching in the body of a message) @@ -3550,7 +3941,7 @@ folder-hook . set sort=date-sent - tilde (the ``˜'' used to pad blank lines in the pager) + tilde (the ``~'' used to pad blank lines in the pager) @@ -3655,16 +4046,16 @@ folder-hook . set sort=date-sent used as a transparent color. The value brightdefault is also valid. If Mutt-ng is linked against the S-Lang library, you also need to set - the COLORFGBG environment variable to the default + the environment variable to the default colors of your terminal for this to work; for example (for Bourne-like shells): - + set COLORFGBG="green;black" -export COLORFGBG +export COLORFGBG @@ -3692,7 +4083,7 @@ export COLORFGBG Mutt-ng also recognizes the keywords color0, color1 - ,…, + ,..., colorN-1 ( N @@ -3711,18 +4102,13 @@ export COLORFGBG - Usage: mono <object> - <attribute> - - [ regexp ] - - Usage: mono index attribute - pattern - - - Usage: unmono index pattern - [ pattern ... ] - + object attribute [regexp] + + + index attribute pattern + + + index pattern [pattern ...] @@ -3773,16 +4159,17 @@ export COLORFGBG - - Ignoring (weeding) unwanted message headers - + + Ignoring (weeding) unwanted message headers + - Usage: [un]ignore pattern [ - pattern - - ... ] + pattern [pattern ...] - + + + pattern [pattern ...] + + Messages often have many header fields added by automatic processing systems, @@ -3814,12 +4201,12 @@ export COLORFGBG For example: - + # Sven's draconian header weeding ignore * unignore from date subject to cc unignore organization organisation x-mailer: x-newsreader: x-mailing-list: -unignore posted-to: +unignore posted-to: @@ -3829,27 +4216,25 @@ unignore posted-to: - - Alternative addresses + + Alternative addresses - Usage: [un]alternates regexp [ - regexp - - ... ] - + regexp [regexp ...] - + + + regexp [regexp ...] + + With various functions, mutt will treat messages differently, 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 - yourself won't make much sense in many cases. (See - reply-to - - .) + the response to the original message's recipients--responding to + yourself won't make much sense in many cases. + (See .) @@ -3898,11 +4283,11 @@ unignore posted-to: - - Format = Flowed + + Format = Flowed - - Introduction + + Introduction Mutt-ng contains support for so-called format=flowed messages. @@ -3920,13 +4305,13 @@ unignore posted-to: For introductory information on format=flowed messages, see - <http://www.joeclark.org/ffaq.html>. + . - - Receiving: Display Setup + + Receiving: Display Setup When you receive emails that are marked as format=flowed @@ -3938,8 +4323,8 @@ unignore posted-to: - -set wrapmargin = 10 + +set wrapmargin = 10 @@ -3955,8 +4340,8 @@ set wrapmargin = 10 - -set max_line_length = 120 + +set max_line_length = 120 @@ -3973,11 +4358,11 @@ set max_line_length = 120 - + >Bill, can you please send last month's progress report to Mr. >Morgan? We also urgently need the cost estimation for the new >production server that we want to set up before our customer's ->project will go live. +>project will go live. @@ -3989,8 +4374,8 @@ set max_line_length = 120 - -set stuff_quoted + +set stuff_quoted @@ -4000,18 +4385,18 @@ set stuff_quoted - + > Bill, can you please send last month's progress report to Mr. > Morgan? We also urgently need the cost estimation for the new > production server that we want to set up before our customer's -> project will go live. +> project will go live. - - Sending + + Sending If you want mutt-ng to send emails with format=flowed set, you @@ -4020,14 +4405,14 @@ set stuff_quoted - -set text_flowed + +set text_flowed Additionally, you have to use an editor which supports writing - format=flowed-conforming emails. For vim, this is + format=flowed-conforming emails. For , this is done by adding w to the formatoptions (see :h formatoptions @@ -4044,7 +4429,7 @@ set text_flowed side, the first space (if any) is removed. As a consequence and in addition to the above simple setting, please keep this in mind when making manual formattings within the editor. Also note that mutt-ng - currently violates the standard (RfC 3676) as it does not + currently violates the standard () as it does not space-stuff lines starting with: @@ -4052,7 +4437,6 @@ set text_flowed - > This is not the quote character but a right @@ -4060,21 +4444,6 @@ set text_flowed - - - - From with a trailing space. - - - - - - - just a space for formatting reasons - - - - @@ -4085,11 +4454,11 @@ set text_flowed - + Additional Notes - For completeness, the delete-space variable provides the mechanism + For completeness, the variable provides the mechanism to generate a DelSp=yes parameter on outgoing @@ -4113,30 +4482,28 @@ set text_flowed - - Mailing lists + + Mailing lists - Usage: [un]lists regexp [ - regexp - - ... ] - - Usage: [un]subscribe regexp [ - regexp - - ... ] + regexp [regexp ...] + + + regexp [regexp ...] + + + regexp [regexp ...] + + + regexp [regexp ...] - Mutt-ng has a few nice features for - using-lists - - .In order to take advantage of them, you must + Mutt-ng has a few nice features for using-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 - list-reply - + lists you are subscribed to. Once you have done this, the + list-reply function will work for all known lists. Additionally, when you send a message to a subscribed list, mutt will add a Mail-Followup-To header to tell other users' mail user agents @@ -4145,9 +4512,8 @@ set text_flowed supported by all mail user agents. Adding it is not bullet-proof against receiving personal CCs of list messages. Also note that the generation - of the Mail-Followup-To header is controlled by the - followup-to - + of the Mail-Followup-To header is controlled by the + configuration variable. @@ -4162,7 +4528,7 @@ set text_flowed You can use regular expressions with both commands. To mark all messages sent to a specific bug report's address on mutt's bug tracking system as list mail, for instance, you could say - ``subscribe [0-9]*@bugs.guug.de''. Often, it's sufficient to just + ``subscribe [0-9]*@bugs.guug.de''. Often, it's sufficient to just give a portion of the list's e-mail address. @@ -4177,8 +4543,8 @@ set text_flowed add ``subscribe mutt-users'' to your initialization file instead. If you also happen to get mail from someone whose address is mutt-users@example.com, you could use ``lists - mutt-users@mutt\\.org'' - or ``subscribe mutt-users@mutt\\.org'' to + mutt-users@mutt\\.org'' + or ``subscribe mutt-users@mutt\\.org'' to match only mail from the actual list. @@ -4200,12 +4566,10 @@ set text_flowed - Using Multiple spool mailboxes + Using Multiple spool mailboxes - Usage: mbox-hook [!]pattern - mailbox - + Usage: [!]pattern mailbox @@ -4234,16 +4598,16 @@ set text_flowed - - Defining mailboxes which receive mail - + + Defining mailboxes which receive mail + - Usage: [un]mailboxes [!] - filename - - [ filename ... ] + [!]filename [filename ... ] - + + [!]filename [filename ... ] + + This command specifies folders which can receive mail and which will be checked for new messages. By default, the @@ -4290,14 +4654,10 @@ set text_flowed mailboxes command are resolved when - the command is executed, so if these names contain - shortcuts - + the command is executed, so if these names contain shortcuts (such as ``='' and ``!''), any variable - definition that affect these characters (like - folder - - and spoolfile) + definition that affect these characters (like + and ) should be executed before the mailboxes command. @@ -4307,22 +4667,18 @@ set text_flowed - - User defined headers + + User defined headers - Usage: - - my_hdr string - - unmy_hdr field [ - field - - ... ] + string + + + field [field ...] - The ``my_hdr'' command allows you to create your own header + The ``my_hdr'' command allows you to create your own header fields which will be added to every message you send. @@ -4333,8 +4689,8 @@ set text_flowed - -my_hdr Organization: A Really Big Company, Anytown, USA + +my_hdr Organization: A Really Big Company, Anytown, USA @@ -4346,13 +4702,13 @@ my_hdr Organization: A Really Big Company, Anytown, USA not allowed between the keyword and - the colon (``:''). The standard for electronic mail (RFC822) says that + the colon (``:''). The standard for electronic mail () says that 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 edit-headers + either set the variable, or use the edit-headers function (default: ``E'') in the send-menu so @@ -4360,15 +4716,15 @@ my_hdr Organization: A Really Big Company, Anytown, USA - To remove user defined header fields, use the ``unmy_hdr'' + To remove user defined header fields, use the ``unmy_hdr'' command. You may specify an asterisk (``*'') to remove all header fields, or the fields to remove. For example, to remove all ``To'' and ``Cc'' header fields, you could use: - -unmy_hdr to cc + +unmy_hdr to cc @@ -4377,21 +4733,24 @@ unmy_hdr to cc - - Defining the order of headers when viewing messages + + Defining the order of headers when viewing messages - Usage: hdr_order header1 - header2 header3 + header header [header ...] - + + + [ * | header header ...] + + With this command, you can specify an order in which mutt will attempt to present headers to you when viewing messages. - ``unhdr_order *'' will clear all previous headers from the order + ``unhdr_order *'' will clear all previous headers from the order list, thus removing the header order effects set by the system-wide startup file. @@ -4399,8 +4758,8 @@ unmy_hdr to cc - -hdr_order From Date: From: To: Cc: Subject: + +hdr_order From Date: From: To: Cc: Subject: @@ -4411,12 +4770,10 @@ hdr_order From Date: From: To: Cc: Subject: - Specify default save filename + Specify default save filename - Usage: save-hook [!]pattern - filename - + Usage: [!]pattern filename @@ -4431,7 +4788,7 @@ hdr_order From Date: From: To: Cc: Subject: - See pattern-hook for information on + See for information on the exact format of pattern. @@ -4441,14 +4798,14 @@ hdr_order From Date: From: To: Cc: Subject: - + save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins -save-hook aol\\.com$ +spam +save-hook aol\\.com$ +spam - Also see the fcc-save-hook + Also see the command. @@ -4459,43 +4816,41 @@ save-hook aol\\.com$ +spam - Specify default Fcc: mailbox when composing + Specify default Fcc: mailbox when composing - Usage: fcc-hook [!]pattern - mailbox - + Usage: [!]pattern mailbox This command is used to save outgoing mail in a mailbox other than - record. Mutt-ng searches the initial + . Mutt-ng searches the initial list of message recipients for the first matching regexp and uses mailbox as the default Fcc: mailbox. If no match is found the message will be saved - to record mailbox. + to mailbox. - See pattern-hook for information on + See for information on the exact format of pattern. - Example: fcc-hook [@.]aol\\.com$ - +spammers - + Example: + + + + +fcc-hook [@.]aol\\.com$ +spammers - The above will save a copy of all messages going to the aol.com domain - to - the `+spammers' mailbox by default. Also see the - fcc-save-hook - - command. + The above will save a copy of all messages going to the aol.com + domain to the `+spammers' mailbox by default. Also see the + command. @@ -4505,19 +4860,15 @@ save-hook aol\\.com$ +spam - Specify default save filename and default Fcc: mailbox at once + Specify default save filename and default Fcc: mailbox at once - Usage: fcc-save-hook [!]pattern - mailbox - + Usage: [!]pattern mailbox - This command is a shortcut, equivalent to doing both a - fcc-hook - - and a save-hook with its arguments. + This command is a shortcut, equivalent to doing both a + and a with its arguments. @@ -4527,20 +4878,18 @@ save-hook aol\\.com$ +spam - Change settings based upon message recipients - + Change settings based upon message recipients + + + - Usage: reply-hook [!]pattern - command - - - Usage: send-hook [!]pattern - command - - - Usage: send2-hook [!]pattern - command - + Usage: [!]pattern command + + + Usage: [!]pattern command + + + Usage: [!]pattern command @@ -4554,75 +4903,68 @@ save-hook aol\\.com$ +spam - reply-hook is matched against the message you are + is matched against the message you are replying to, instead of the message you are sending - .send-hook is + . is matched against all messages, both new and replies .Note: - reply-hooks are matched before the - send-hook - - ,regardless + s are matched before the + , regardless of the order specified in the users's configuration file. - send2-hook is matched every time a message is + is matched every time a message is changed, either by editing it, or by using the compose menu to change its recipients - or subject. send2-hook is executed after - send-hook - + or subject. is executed after ,and - can, e.g., be used to set parameters such as the - sendmail - + can, e.g., be used to set parameters such as the variable depending on the message's sender address. - For each type of send-hook or reply-hook, when multiple matches + For each type of or , when multiple matches occur, commands are executed in the order they are specified in the muttrc (for that type of hook). - See pattern-hook for information on + See for information on the exact format of pattern. - Example: send-hook mutt "set mime_forward + Example: send-hook mutt "set mime_forward signature=''" Another typical use for this command is to change the values of the - attribution, - signature - - and locale + , + and variables in order to change the language of the attributions and signatures based upon the recipients. - Note: the send-hook's are only + Note: the 's are only executed ONCE after getting the initial list of recipients. Adding a recipient after replying or editing the - message will NOT cause any send-hook to be executed. Also note that - my_hdr commands which modify recipient headers, or the message's + message will NOT cause any to be executed. Also note that + my_hdr commands which modify recipient headers, or the message's subject, don't have any effect on the current message when executed - from a send-hook. + from a . @@ -4632,12 +4974,10 @@ save-hook aol\\.com$ +spam - Change settings before formatting a message + Change settings before formatting a message - Usage: message-hook [!]pattern - command - + Usage: [!]pattern command @@ -4651,16 +4991,16 @@ save-hook aol\\.com$ +spam - See pattern-hook for + See for information on the exact format of pattern. Example: - + message-hook ~A 'set pager=builtin' -message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' +message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' @@ -4671,12 +5011,10 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' - Choosing the cryptographic key of the recipient + Choosing the cryptographic key of the recipient - Usage: crypt-hook pattern - keyid - + Usage: pattern keyid @@ -4685,7 +5023,7 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' 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-ng - wouldnormally use. The crypt-hook command provides a method by which + wouldnormally use. The 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. @@ -4703,22 +5041,25 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' - - Adding key sequences to the keyboard buffer + + Adding key sequences to the keyboard buffer - Usage: push string + string - This command adds the named string to the keyboard buffer. The string - may - contain control characters, key names and function names like the - sequence - string in the macro command. You may use - it to - automatically run a sequence of commands at startup, or when entering - certain folders. + + This command adds the named string to the keyboard buffer. The + string may contain control characters, key names and function + names like the sequence string in the command. You may use it to + automatically run a sequence of commands at startup, or when + entering certain folders. For example, the following command + will automatically collapse all threads when entering a folder: + + +folder-hook . 'push <collapse-all>' + @@ -4727,14 +5068,11 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' - - Executing functions + + Executing functions - Usage: exec function [ - function - - ... ] + function [function ... ] @@ -4749,18 +5087,14 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' - - Message Scoring + + Message Scoring - Usage: score pattern - value - - - Usage: unscore pattern [ - pattern - - ... ] + pattern value + + + pattern [pattern ... ] @@ -4783,9 +5117,9 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' - + score "~f nion@muttng\.org" 50 -score "~f @sco\.com" -100 +score "~f @sco\.com" -100 @@ -4797,8 +5131,8 @@ score "~f @sco\.com" -100 - -score "~f santaclaus@northpole\.int" =666 + +score "~f santaclaus@northpole\.int" =666 @@ -4847,17 +5181,16 @@ score "~f santaclaus@northpole\.int" =666 - These three thresholds can be set via the variables - score-threshold-flag - - ,score-threshold-read, - score-threshold-delete - - and. By - default, score-threshold-read and - score-threshold-delete - - are set to + These three thresholds can be set via the variables + , + and + . + + + By default, + and + + are set to -1, which means that in the default threshold configuration no message will ever get marked as read or deleted. @@ -4868,14 +5201,14 @@ score "~f santaclaus@northpole\.int" =666 color command - and the ˜n pattern: + and the pattern: - + color index black yellow "~n 10-" -color index red yellow "~n 100-" +color index red yellow "~n 100-" @@ -4893,15 +5226,14 @@ color index red yellow "~n 100-" - - Spam detection - + + Spam detection + - Usage: spam pattern - format - - - Usage: nospam pattern + pattern format + + + pattern @@ -4915,10 +5247,9 @@ color index red yellow "~n 100-" your mail based on its spam attributes, as determined by the external filter. You also can display the spam attributes in your index - display using the %H selector in the - index-format - - variable. (Tip: try %?H?[%H] ? + display using the %H selector in the + + variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -4936,8 +5267,8 @@ color index red yellow "~n 100-" pattern expression. (A regular expression ``back-reference'' refers to a - sub-expression contained within parentheses.) %1 is replaced with - the first back-reference in the regex, %2 + sub-expression contained within parentheses.) %1 is replaced with + the first back-reference in the regex, %2 with the second, etc. @@ -4946,10 +5277,10 @@ color index red yellow "~n 100-" one spam-related header. You can define spam patterns for each filter you use. If a message matches two or more of these patterns, and - the $spam_separator variable is set to a string, then the + the $spam_separator variable is set to a string, then the message's spam tag will consist of all the format strings joined - together, with the value of $spam_separator separating + together, with the value of $spam_separator separating them. @@ -4957,25 +5288,25 @@ color index red yellow "~n 100-" For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define these spam settings: - + spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1" spam "X-Spam-Status: Yes" "90+/SA" spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM" -set spam_separator=", " +set spam_separator=", " If I then received a message that DCC registered with ``many'' hits under the ``Fuz2'' checksum, and that PureMessage registered with a - 97% probability of being spam, that message's spam tag would + 97% probability of being spam, that message's spam tag would read90+/DCC-Fuz2, 97/PM. (The four characters before ``=many'' in a DCC report indicate the checksum used -- in this case, ``Fuz2''.) - If the $spam_separator variable is unset, then each + If the $spam_separator variable is unset, then each spam pattern match supersedes the previous one. Instead of getting joined format strings, you'll get only the last one to match. @@ -4983,11 +5314,11 @@ set spam_separator=", " The spam tag is what will be displayed in the index when you use - %H in the - $index_format + %H in the + $index_format variable. It's also the - string that the ˜H pattern-matching expression + string that the pattern-matching expression matches against for search and limit functions. And it's what sorting by spam @@ -5043,10 +5374,7 @@ set spam_separator=", " will be removed. This might be the default action if you use spam - and nospam in conjunction with a - folder-hook - - . + and nospam in conjunction with a . @@ -5059,8 +5387,8 @@ set spam_separator=", " - -spam "^From: .*MAILER-DAEMON" "999" + +spam "^From: .*MAILER-DAEMON" "999" @@ -5070,36 +5398,25 @@ spam "^From: .*MAILER-DAEMON" "999" - - Setting variables - + + Setting variables + - Usage: set [no|inv] - variable - - [=value] [ variable ... ] - - Usage: toggle variable [ - variable - - ... ] - - Usage: unset variable [ - variable - - ... ] - - Usage: reset variable [ - variable - - ... ] + [no|inv]variable [=value] [variable...] + + + variable [variable ...] + + + variable [variable ...] + + + variable [variable ...] - This command is used to set (and unset) - variables - - .There are four basic types of variables: + This command is used to set (and unset) variables. + There are four basic types of variables: boolean, number, string and quadoption. boolean variables can be set (true) or unset (false). @@ -5112,8 +5429,8 @@ spam "^From: .*MAILER-DAEMON" "999" printable characters. strings must be enclosed in quotes if they contain spaces or tabs. You - may also use the ``C'' escape sequences \n and - \t + may also use the ``C'' escape sequences \n and + \t for newline and tab, respectively. @@ -5147,7 +5464,7 @@ spam "^From: .*MAILER-DAEMON" "999" the variable name with inv to toggle the value (on or off). This is useful when writing - macros. Example: set invsmart_wrap. + macros. Example: set invsmart_wrap. @@ -5176,8 +5493,8 @@ spam "^From: .*MAILER-DAEMON" "999" - -set ?allow_8bit + +set ?allow_8bit @@ -5207,37 +5524,34 @@ set ?allow_8bit - - Reading initialization commands from another file + + Reading initialization commands from another file - Usage: source filename [ - filename - - ... ] + filename [filename ...] This command allows the inclusion of initialization commands from other files. For example, I place all of my aliases in - ˜/.mail_aliases so that I can make my - ˜/.muttrc readable and keep my aliases + ~/.mail_aliases so that I can make my + ~/.muttrc readable and keep my aliases private. - If the filename begins with a tilde (``˜''), it will be expanded + If the filename begins with a tilde (``~''), it will be expanded to the path of your home directory. - If the filename ends with a vertical bar (|), then + If the filename ends with a vertical bar (|), then filename is considered to be an executable program from which to read input (eg. - source ˜/bin/myscript|). + source ~/bin/myscript|). @@ -5246,18 +5560,18 @@ set ?allow_8bit - - Removing hooks + + Removing hooks - Usage: unhook [ * | hook-type ] + [* | hook-type] This command permits you to flush hooks you have previously defined. You can either remove all hooks by giving the ``*'' character as an argument, or you can remove all hooks of a specific type by saying - something like unhook send-hook. + something like unhook send. @@ -5266,11 +5580,11 @@ set ?allow_8bit - - Sharing Setups + + Sharing Setups - - Character Sets + + Character Sets As users may run mutt-ng on different systems, the configuration @@ -5290,14 +5604,14 @@ set ?allow_8bit - -set config_charset = "..." + +set config_charset = "..." and replacing the dots with the actual character set. To avoid - problems while maintaining the setup, vim user's may want to use + problems while maintaining the setup, user's may want to use modelines as show in: @@ -5310,7 +5624,7 @@ set config_charset = "..." while, again, replacing the dots with the appropriate name. This - tells vim as which character set to read and save the file. + tells as which character set to read and save the file. @@ -5319,8 +5633,8 @@ set config_charset = "..." - - Modularization + + Modularization ``Modularization'' means to divide the setup into several files @@ -5340,8 +5654,8 @@ set config_charset = "..." - - Conditional parts + + Conditional parts When using a configuration on different systems, the user may not @@ -5356,9 +5670,9 @@ set config_charset = "..." - + ifdef <item> <command> -ifndef <item> <command> +ifndef <item> <command> @@ -5406,7 +5720,7 @@ ifndef <item> <command> All available functions, variables and menus are documented elsewhere in this manual but ``features'' is specific to these two commands. To test for one, prefix one of the following - keywords with feature_: ncurses, + keywords 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 @@ -5414,56 +5728,54 @@ ifndef <item> <command> As an example, one can use the following in - ˜/.muttngrc: + ~/.muttngrc: - + ifdef feature_imap 'source ~/.mutt-ng/setup-imap' ifdef feature_pop 'source ~/.mutt-ng/setup-pop' -ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp' +ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp' - ...to only source ˜/.mutt-ng/setup-imap if + ...to only source ~/.mutt-ng/setup-imap if IMAP - support is built in, only source ˜/.mutt-ng/setup-pop + support is built in, only source ~/.mutt-ng/setup-pop if POP support is built in and only source - ˜/.mutt-ng/setup-nntp if NNTP support is + ~/.mutt-ng/setup-nntp if NNTP support is built in. An example for testing for variable names can be used if users use different revisions of mutt-ng whereby the older one may not - have a certain variable. To test for the availability of - imap-mail-check - - , + have a certain variable. To test for the availability of + use: - -ifdef imap_mail_check 'set imap_mail_check = 300' + +ifdef imap_mail_check 'set imap_mail_check = 300' - Provided for completeness is the test for menu names. To set - pager-index-lines - + Provided for completeness is the test for menu names. To set + only if the pager menu is available, use: - -ifdef pager 'set pager_index_lines = 10' + +ifdef pager 'set pager_index_lines = 10' @@ -5477,9 +5789,9 @@ ifdef pager 'set pager_index_lines = 10' - + ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses' -ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang' +ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang' @@ -5489,9 +5801,9 @@ ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang' - + ifdef feature_slang 'source ~/.mutt-ng/setup-slang' -ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' +ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' @@ -5507,8 +5819,8 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - - Obsolete Variables + + Obsolete Variables In the process of ensuring and creating more consistency, many @@ -5528,16 +5840,17 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' + - - Advanced Usage + + Advanced Usage - - Regular Expressions + + Regular Expressions All string patterns in Mutt-ng including those in more complex - patterns must be specified + 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 @@ -5546,9 +5859,9 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' The search is case sensitive if the pattern contains at least one upper - case letter, and case insensitive otherwise. Note that ``\'' + case letter, and case insensitive otherwise. Note that ``\'' must be quoted if used for a regular expression in an initialization - command: ``\\''. + command: ``\\''. @@ -5561,7 +5874,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' 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 muttrc-syntax + character. See muttrc-syntax for more information on " and ' delimiter processing. To match a literal " or ' you must preface it with \ (backslash). @@ -5574,33 +5887,33 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - The period ``.'' matches any single character. The caret ``ˆ'' - andthe dollar sign ``$'' are metacharacters that respectively + The period ``.'' matches any single character. The caret ``^'' + andthe dollar sign ``$'' are metacharacters that respectively match the empty string at the beginning and end of a line. - A list of characters enclosed by ``['' and ``]'' matches any + A list of characters enclosed by ``]'' and ``]'' matches any single character in that list; if the first character of the list - is a caret ``ˆ'' then it matches any character + is a caret ``^'' then it matches any character not in the list. For example, the regular expression - [0123456789] + ]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 - lists. To include a literal ``]'' place it first in the list. - Similarly, to include a literal ``ˆ'' place it anywhere but first. + 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. Certain named classes of characters are predefined. Character classes - consist of ``[:'', a keyword denoting the class, and ``:]''. + consist of ``[:'', a keyword denoting the class, and ``:]''. The following classes are defined by the POSIX standard: @@ -5608,7 +5921,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:alnum:] + [:alnum:] Alphanumeric characters. @@ -5616,7 +5929,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:alpha:] + [:alpha:] Alphabetic characters. @@ -5624,7 +5937,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:blank:] + [:blank:] Space or tab characters. @@ -5632,7 +5945,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:cntrl:] + [:cntrl:] Control characters. @@ -5640,7 +5953,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:digit:] + [:digit:] Numeric characters. @@ -5648,7 +5961,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:graph:] + [:graph:] Characters that are both printable and visible. (A space is @@ -5658,7 +5971,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:lower:] + [:lower:] Lower-case alphabetic characters. @@ -5666,7 +5979,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:print:] + [:print:] Printable characters (characters that are not control @@ -5675,7 +5988,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:punct:] + [:punct:] Punctuation characters (characters that are not letter, digits, @@ -5685,7 +5998,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:space:] + [:space:] Space characters (such as space, tab and formfeed, to name a @@ -5694,7 +6007,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:upper:] + [:upper:] Upper-case alphabetic characters. @@ -5702,7 +6015,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - [:xdigit:] + [:xdigit:] Characters that are hexadecimal digits. @@ -5717,8 +6030,8 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' brackets of a character list. Note that the brackets in these class names are part of the symbolic names, and must be included in addition to the brackets delimiting the bracket list. For - example, [[:digit:]] is equivalent to - [0-9]. + example, [[:digit:]] is equivalent to + [0-9]. @@ -5739,14 +6052,14 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' A collating symbol is a multi-character collating element enclosed in - ``[.'' and ``.]''. For example, if ``ch'' is a + ``[.'' and ``.]''. For example, if ``ch'' is a collating element, then - [[.ch.]] + [[.ch.]] is a regexp that matches this collating element, while - [ch] + [ch] is a regexp that matches either ``c'' or ``h''. @@ -5759,13 +6072,13 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' An equivalence class is a locale-specific name for a list of characters that are equivalent. The name is enclosed in - ``[='' - and ``=]''. For example, the name ``e'' might be used to - represent all of ``è'' ``é'' and ``e''. In this + ``[='' + and ``=]''. For example, the name ``e'' might be used to + represent all of ``è'' ``é'' and ``e''. In this case, - [[=e=]] is + [[=e=]] is a regexp that matches any of - ``è'', ``é'' and ``e''. + ``è'', ``é'' and ``e''. @@ -5805,7 +6118,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - {n} + {n} The preceding item is matched exactly n @@ -5814,7 +6127,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - {n,} + {n,} The preceding item is matched n or more @@ -5823,7 +6136,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - {,m} + {,m} The preceding item is matched at most m @@ -5832,7 +6145,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - {n,m} + {n,m} The preceding item is matched at least n @@ -5852,7 +6165,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' Two regular expressions may be joined by the infix operator - ``|''; + ``|''; the resulting regular expression matches any string matching either subexpression. @@ -5873,7 +6186,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\y + \\y Matches the empty string at either the beginning or the end of @@ -5882,7 +6195,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\B + \\B Matches the empty string within a word. @@ -5890,7 +6203,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\< + \\< Matches the empty string at the beginning of a word. @@ -5898,7 +6211,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\> + \\> Matches the empty string at the end of a word. @@ -5906,7 +6219,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\w + \\w Matches any word-constituent character (letter, digit, or @@ -5915,7 +6228,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\W + \\W Matches any character that is not word-constituent. @@ -5923,7 +6236,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\` + \\` Matches the empty string at the beginning of a buffer (string). @@ -5931,7 +6244,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - \\' + \\' Matches the empty string at the end of a buffer. @@ -5952,27 +6265,27 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - - Patterns + + Patterns 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 patterns in the Reference chapter. + these patterns, please refer to table patterns in the Reference chapter. It must be noted that in this table, EXPR is a regular expression. For ranges, the forms - <[MAX], >>[MIN], - [MIN]- and -[MAX] are + <[MAX], >>[MIN], + [MIN]- and -[MAX] are also possible. - - Complex Patterns + + Complex Patterns It is possible to combine several sub-patterns to a more complex @@ -5983,7 +6296,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' -~s 'SPAM' ~U + 'SPAM' @@ -5993,7 +6306,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - To logical OR patterns, simply use the | + To logical OR patterns, simply use the | operator. This one especially useful when using local groups: @@ -6001,9 +6314,9 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' -~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org") -(~b mutt-ng|~s Mutt-ng) -!~x '@synflood\.at' + ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org") +( mutt-ng| Mutt-ng) +! '@synflood\.at' @@ -6021,8 +6334,8 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - - Patterns and Dates + + Patterns and Dates When using dates in patterns, the dates must be specified in a @@ -6052,9 +6365,9 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' -~d 01/01/2005+1y -~d 18/10/2004-2w -~d 28/12/2004*1d + 01/01/2005+1y + 18/10/2004-2w + 28/12/2004*1d @@ -6075,9 +6388,9 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' -~d >2w # messages older than two weeks -~d <3d # messages newer than 3 days -~d =1m # messages that are exactly one month old + >2w # messages older than two weeks + <3d # messages newer than 3 days + =1m # messages that are exactly one month old @@ -6089,11 +6402,11 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - - Format Strings + + Format Strings - - Introduction + + Introduction The so called Format Strings offer great @@ -6139,27 +6452,27 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' The setting for the status bar of the index is controlled via the - status-format + variable. For the hostname and version string, there's an expando - for $status_format: - %h + for $status_format: + %h expands to the - hostname and %v to the version string. When + hostname and %v to the version string. When just configuring: - -set status_format = "%v on %h: ..." + +set status_format = "%v on %h: ..." - mutt-ng will replace the sequence %v with + mutt-ng will replace the sequence %v with the version string - and %h with the host's name. When you are, + and %h with the host's name. When you are, for example, running mutt-ng version 1.5.9i on host mailhost, you'll see the following when you're in the index: @@ -6212,8 +6525,8 @@ Mutt-ng 1.5.9i on mailhost: ... - -set status_format = "%v on %h: %B: ... + +set status_format = "%v on %h: %B: ... @@ -6246,19 +6559,19 @@ Mutt-ng 1.5.9i on mailhost: Inbox: ... - - Conditional Expansion + + Conditional Expansion To only print the number of messages if there are new messages in the current mailbox, further extend - $status_format to: + $status_format to: - -set status_format = "%v on %h: %B %?n?%n new? ... + +set status_format = "%v on %h: %B %?n?%n new? ... @@ -6273,7 +6586,7 @@ set status_format = "%v on %h: %B %?n?%n new? ... -%?<item>?<string if nonzero>? +%?<item>?<string if nonzero>? @@ -6281,9 +6594,9 @@ set status_format = "%v on %h: %B %?n?%n new? ... which tells mutt-ng to only look at <string if nonzero> - if the value of the %<item%gt; + if the value of the %<item%gt; expando is different from zero. In our example, we used n as - the expando to check for and %n new as the + the expando to check for and %n new as the optional nonzero string. @@ -6299,7 +6612,7 @@ set status_format = "%v on %h: %B %?n?%n new? ... -%?<item>?<string if nonzero>&<string if zero>? +%?<item>?<string if nonzero>&<string if zero>? @@ -6339,8 +6652,8 @@ set status_format = "%v on %h: %B %?n?%n new? ... - -set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ... + +set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ... @@ -6351,8 +6664,8 @@ set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...< - -set status_format = "%v on %h: %B: %?n?%n&no? new messages ... + +set status_format = "%v on %h: %B: %?n?%n&no? new messages ... @@ -6368,8 +6681,8 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - - Modifications and Padding + + Modifications and Padding Besides the information given so far, there're even more features of @@ -6382,9 +6695,9 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - When specifying %_<item> + When specifying %_<item> instead of - just %<item>, mutt-ng will + just %<item>, mutt-ng will convert all characters in the expansion of <item> to @@ -6395,12 +6708,12 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - When specifying %:<item> + When specifying %:<item> instead of just - %<item>, mutt-ng will convert + %<item>, mutt-ng will convert all dots in the expansion of <item> to underscores - (_). + (_). @@ -6412,8 +6725,8 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... Also, there's a feature called Padding supplied by the - following two expandos: %|X and - %>X + following two expandos: %|X and + %>X . @@ -6423,7 +6736,7 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - %|X + %|X @@ -6435,34 +6748,34 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - -set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-" + +set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-" - %>X + %>X Since the previous expando stops at the end of line, there must be a way to fill the gap between - two items via the %>X expando: + two items via the %>X expando: it puts as many characters X in between two items so that the rest of the line will be right-justified. For example, to not put the version string and hostname of our example on the left but on the right and fill the gap with spaces, one might use (note - the space after %>): + the space after %>): - -set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" + +set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" @@ -6482,8 +6795,8 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" - - Using Tags + + Using Tags Sometimes it is desirable to perform an operation on a group of @@ -6493,7 +6806,7 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" 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 patterns for Mutt-ng's + default. See patterns for Mutt-ng's pattern matching syntax. @@ -6506,13 +6819,13 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" operation will be applied to all tagged messages if that operation can be used in that - manner. If the auto-tag + manner. If the variable is set, the next operation applies to the tagged messages automatically, without requiring the ``tag-prefix''. - In macro or push commands, + In or 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-ng will stop "eating" the macro when it encounters the @@ -6528,7 +6841,7 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" - Using Hooks + Using Hooks A hook is a concept borrowed from the EMACS editor @@ -6540,51 +6853,51 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" reading, or to whom you are sending mail. In the Mutt-ng world, a hook - consists of a regexp or - patterns along with a + consists of a regexp or + patterns along with a configuration option/command. See - folder-hook + - send-hook + - message-hook + - save-hook + - mbox-hook + - fcc-hook + - fcc-save-hook + @@ -6600,16 +6913,16 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" effective until the end of the current mutt session. As this is generally not desired, a default hook needs to be added before all other hooks to - restore configuration defaults. Here is an example with send-hook and + restore configuration defaults. Here is an example with and the - my_hdr directive: + my_hdr directive: - + send-hook . 'unmy_hdr From:' -send-hook ~C'^b@b\.b$' my_hdr from: c@c.c +send-hook '~C ^b@b\.b$' my-hdr from: c@c.c @@ -6617,18 +6930,18 @@ send-hook ~C'^b@b\.b$' my_hdr from: c@c.c Message Matching in Hooks - Hooks that act upon messages (send-hook, save-hook, - fcc-hook,message-hook + Hooks that act upon messages (, , + , )are evaluated in a slightly different manner. For the other - types of hooks, a regexp is + types of hooks, a regexp 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. - Mutt-ng allows the use of the patterns + Mutt-ng allows the use of the patterns language for matching messages in hook commands. This works in exactly the same way as it would when limiting orsearching the mailbox, except that you are @@ -6642,8 +6955,8 @@ send-hook ~C'^b@b\.b$' my_hdr from: c@c.c sending mail to a specific address, you could do something like: - -send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>' + +send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Mutt-ng User <user@host>' which would execute the given command when sending mail to me@cs.hmc.edu. @@ -6659,10 +6972,10 @@ send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>' like the other hooks, in which case Mutt-ng will translate your pattern into the full language, using the translation specified by the - default-hook variable. The + variable. The pattern is translated at the time the hook is declared, so the value of - default-hook that is in effect + that is in effect at that time will be used. @@ -6675,7 +6988,7 @@ send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>' - Using the sidebar + Using the sidebar The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox @@ -6686,63 +6999,37 @@ send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>' and highlights the ones with new email Use the following configuration commands: - + set sidebar_visible="yes" -set sidebar_width=25 +set sidebar_width=25 If you want to specify the mailboxes you can do so with: - + set mbox='=INBOX' mailboxes INBOX \ MBOX1 \ MBOX2 \ -... +... You can also specify the colors for mailboxes with new mails by using: - + color sidebar_new red black -color sidebar white black +color sidebar white black - - The available functions are: - - - Default Sidebar Function Bindings - - - - Key - Function - Description - - - - nonesidebar-scroll-up Scrolls the mailbox list up 1 page - nonesidebar-scroll-down Scrolls the mailbox list down 1 page - nonesidebar-next Highlights the next mailbox - nonesidebar-next-new Highlights the next mailbox with new mail - nonesidebar-previous Highlights the previous mailbox - nonesidebar-open Opens the currently highlighted mailbox - - -
- - - Reasonable key bindings look e.g. like this: - + bind index \Cp sidebar-prev bind index \Cn sidebar-next bind index \Cb sidebar-open @@ -6751,7 +7038,7 @@ bind pager \Cn sidebar-next bind pager \Cb sidebar-open macro index B ':toggle sidebar_visible^M' -macro pager B ':toggle sidebar_visible^M' +macro pager B ':toggle sidebar_visible^M' @@ -6767,23 +7054,22 @@ macro pager B ':toggle sidebar_visible^M' - External Address Queries + External Address Queries 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 - query-command - + using a simple interface. Using the + variable, you specify the wrapper command to use. For example: - -set query_command = "mutt_ldap_query.pl '%s'" + +set query_command = "mutt_ldap_query.pl '%s'" @@ -6822,7 +7108,7 @@ roessler@guug.de Thomas Roessler mutt pgp The other mechanism for accessing the query function is for address completion, similar to the alias completion. In any prompt for address - entry, you can use the complete-query function (default: ˆT) to + entry, you can use the complete-query function (default: ^T) to run a query based on the current address you have typed. Like aliases, mutt will look for what you have typed back to the last space or comma. If @@ -6839,16 +7125,15 @@ roessler@guug.de Thomas Roessler mutt pgp - - Mailbox Formats + + 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 - newmailboxes, Mutt-ng uses the default specified with the - mbox-type - + newmailboxes, Mutt-ng uses the default specified with the + variable. @@ -6861,14 +7146,14 @@ roessler@guug.de Thomas Roessler mutt pgp - -From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST + +From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST to denote the start of a new message (this is often referred to as the - ``From_'' line). + ``From_'' line). @@ -6876,7 +7161,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST mbox format. Each message is - surrounded by lines containing ``ˆAˆAˆAˆA'' (four + surrounded by lines containing ``^A^A^A^A'' (four control-A's). @@ -6893,7 +7178,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Mutt detects this type of mailbox by looking for either - .mh_sequences + .mh_sequences or .xmhcache (needed to distinguish normal directories from MH @@ -6922,7 +7207,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - Mailbox Shortcuts + Mailbox Shortcuts There are a number of built in shortcuts which refer to specific @@ -6938,26 +7223,26 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - ! -- refers to your spoolfile + ! -- refers to your (incoming) mailbox - > -- refers to your mbox file + > -- refers to your file - < -- refers to your record file + < -- refers to your file - ˆ -- refers to the current mailbox + ^ -- refers to the current mailbox @@ -6969,22 +7254,20 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - ˜ -- refers to your home directory + ~ -- refers to your home directory - = or + -- refers to your folder + = or + -- refers to your directory - @alias -- refers to the - save-hook - + @alias -- refers to the as determined by the address of the alias @@ -7000,7 +7283,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - Handling Mailing Lists + Handling Mailing Lists Mutt-ng has a few configuration options that make dealing with large @@ -7008,7 +7291,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST 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 often used for), and what lists you are subscribed to. This is - accomplished through the use of the lists + accomplished through the use of the commands in your muttrc. @@ -7018,10 +7301,9 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST through which you received a message (i.e., of a subscribed list) in the index menu display. This is useful to distinguish between - personal and list mail in the same mailbox. In the - index-format - - variable, the escape ``%L'' + personal and list mail in the same mailbox. In the + + variable, the escape ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To'' field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it returns the name of the author). @@ -7043,9 +7325,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Mutt-ng also supports the 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 - followup-to - + subscribed mailing lists, and if the option is set, mutt will generate a Mail-Followup-To header which contains all the recipients to whom you send this message, but not your address. This indicates that @@ -7059,7 +7339,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Conversely, when group-replying or list-replying to a message which has a Mail-Followup-To header, mutt will respect this header if - the honor-followup-to + the configuration variable is set. Using list-reply will in this case also make sure that the reply goes to the mailing list, even if it's not specified @@ -7079,7 +7359,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST 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-ng uses the reply-to + field. Mutt-ng uses the variable to help decide which address to use. If set to ask-yes @@ -7095,11 +7375,11 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages - individually). The index-format - variable's ``%y'' and - ``%Y'' escapes can be used to expand ``X-Label:'' fields in the + individually). The + variable's ``%y'' and + ``%Y'' escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's pattern-matcher can match regular expressions to - ``X-Label:'' fields with the ``˜y'' selector. ``X-Label:'' is + ``X-Label:'' fields with the ``'' selector. ``X-Label:'' is not a standard message header field, but it can easily be inserted by procmailand other mail filtering agents. @@ -7125,8 +7405,8 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - - Editing threads + + Editing threads Mutt-ng has the ability to dynamically restructure threads that are @@ -7136,7 +7416,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST annoyances which make it hard to follow a discussion. - + Linking threads @@ -7156,12 +7436,12 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST You can also connect multiple children at once, tagging them and using the - tag-prefix command (';') or the auto_tag option. + tag-prefix command (';') or the auto_tag option. - + Breaking threads @@ -7170,7 +7450,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST changing the subject to a totally unrelated one. You can fix such threads by using the ``break-thread'' function - (boundby default to #), which will turn the subthread starting + (boundby default to #), which will turn the subthread starting from the current message into a whole different thread. @@ -7184,10 +7464,10 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - Delivery Status Notification (DSN) Support + Delivery Status Notification (DSN) Support - RFC1894 defines a set of MIME content types for relaying information + defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of as ``return receipts.'' @@ -7230,7 +7510,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - dsn-notify is used + is used to request receipts for different results (such as failed message,message delivered, etc.). @@ -7239,7 +7519,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - dsn-return requests + requests how much of your message should be returned with the receipt (headers or full message). @@ -7260,8 +7540,8 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - - POP3 Support (OPTIONAL) + + POP3 Support (OPTIONAL) If Mutt-ng was compiled with POP3 support (by running the @@ -7294,7 +7574,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST reason the frequency at which Mutt-ng will check for mail remotely can be controlled by the - pop-mail-check + variable, which defaults to every 60 seconds. @@ -7312,11 +7592,10 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Another way to access your POP3 mail is the fetch-mail function - (default: G). It allows to connect to - pop-host - + (default: G). It allows to connect to pop-host ,fetch all your new mail and place it in the - local spoolfile. After this + local . After this point, Mutt-ng runs exactly as if the mail had always been local. @@ -7324,8 +7603,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Note: If you only need to fetch all messages to local mailbox you should consider using a specialized program, such as - fetchmail + . @@ -7334,38 +7612,52 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - - IMAP Support (OPTIONAL) + + IMAP Support (OPTIONAL) - If Mutt-ng was compiled with IMAP support (by running the - configure - - script with the --enable-imap flag), it has the - ability to work - with folders located on a remote IMAP server. + If Mutt-ng was compiled with IMAP support (by running the + configure script with the + --enable-imap flag), it has the + ability to work with folders located on a remote IMAP server. - You can access the remote inbox by selecting the folder - imap://imapserver/INBOX, where imapserver is the name of the - IMAP server and INBOX is the special name for your - spool mailbox on - the IMAP server. If you want to access another mail folder at the IMAP - server, you should use imap://imapserver/path/to/folder where - path/to/folder is the path of the folder you want to - access. + You can access the remote inbox by selecting the folder via its + URL: - + - You can select an alternative port by specifying it with the server, - i.e.: - imap://imapserver:port/INBOX. + +imap://imapserver/INBOX + + + + where imapserver is the name of the IMAP + server and INBOX is the special name for your + spool mailbox on the IMAP server. If you want to access another + mail folder at the IMAP server, you should use + + + + +imap://imapserver/path/to/folder + + + + where path/to/folder is the path + of the folder you want to access. You can select an alternative + port by specifying it with the server, i.e.: + + + + +imap://imapserver:port/INBOX - You can also specify different username for each folder, i.e.: - imap://username@imapserver[:port]/INBOX. + You can also specify different username for each folder by + prenpending your username and an @ symbol to the server's name. @@ -7375,14 +7667,9 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST script with the --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 imaps://[username@]imapserver[:port]/path/to/folder as your - folder path. - - - - Pine-compatible notation is also supported, i.e. - {[username@]imapserver[:port][/ssl]}path/to/folder + SSL encrypted connections. To access a folder with IMAP/SSL, you only + need to substitute the initial imap:// by + imaps:// in the above examples. @@ -7396,7 +7683,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST When browsing folders on an IMAP server, you can toggle whether to look at only the folders you are subscribed to, or all folders with the toggle-subscribed command. See also the - imap-list-subscribed + variable. @@ -7404,9 +7691,9 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Polling for new mail on an IMAP server can cause noticeable delays. So, you'll want to carefully tune the - imap-mail-check + and - timeout + variables. @@ -7417,7 +7704,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST selects the same folder. - + The Folder Browser @@ -7470,7 +7757,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - + Authentication @@ -7514,19 +7801,19 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - imap-user - controls + - controls the username under which you request authentication on the IMAP server, for all authenticators. This is overridden by an explicit username in the mailbox path (i.e. by using a mailbox name of the form - {user@host}). + {user@host}). - imap-pass - a + - a password which you may preset, used by all authentication methods where a password is needed. @@ -7535,7 +7822,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - imap-authenticators + - a colon-delimited list of IMAP authentication methods to try, in the order you wish to try them. If @@ -7557,36 +7844,36 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - - NNTP Support (OPTIONAL) + + NNTP Support (OPTIONAL) If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup'' function from the index/pager which is by default - bound to i. + bound to i. - The Default newsserver can be obtained from the - $NNTPSERVER environment variable. Like other + The Default newsserver can be obtained from the + environment variable. Like other news readers, info about subscribed newsgroups is saved in a file as specified by the - nntp-newsrc variable. + variable. Article headers are cached and can be loaded from a file when a newsgroup is entered instead loading from newsserver; currently, this caching mechanism still is different from the header caching for maildir/IMAP. - - Again: Scoring + + Again: Scoring Especially for Usenet, people often ask for advanced filtering and scoring functionality. Of course, mutt-ng has scoring and allows a killfile, too. How to use a killfile has been discussed - in score-command. + in Message Scoring. @@ -7603,8 +7890,8 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - -score ~* =42 + +score ~* =42 @@ -7615,8 +7902,8 @@ score ~* =42 - -score !~* =42 + +score !~* =42 @@ -7631,10 +7918,7 @@ score !~* =42 - Email addresses must be valid according to RFC 2822, see - <ftp://ftp.rfc-editor.org/in-notes/rfc2822.txt> - + Email addresses must be valid according to @@ -7674,45 +7958,37 @@ score !~* =42 - - SMTP Support (OPTIONAL) + + SMTP Support (OPTIONAL) Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP functionality. When configure was called with --with-libesmtp or the output muttng -v contains - +USE_LIBESMTP, this will be or is the case + +USE_LIBESMTP, this will be or is the case already. The SMTP - support includes support for Delivery Status Notification (see - dsn - - section) as well as - handling the 8BITMIME flag controlled via - use-8bitmime - - . + support includes support for Delivery Status Notification + (see dsn section) as well as + handling the 8BITMIME flag controlled via + . To enable sending mail directly via SMTP without an MTA such as - Postfix or SSMTP and the like, simply set the - smtp-host - + Postfix or SSMTP and the like, simply set the variable pointing to your SMTP server. - Authentication mechanisms are available via the - smtp-user - - and smtp-pass variables. + Authentication mechanisms are available via the + and variables. Transport Encryption via the StartTLS command is also available. For this to work, first of all Mutt-ng must be built with SSL or GNUTLS. - Secondly, the smtp-use-tls variable + Secondly, the variable must be either set to ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server supports it: for the second case, the connection will fail @@ -7725,20 +8001,20 @@ score !~* =42 sender, i.e. they allow for only one value which may not be what the user wants to send as the From: header. In this case, the variable - smtp-envelope may be used + may be used to set the envelope different from the From: header. - Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) + Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) If you happen to have accounts on multiple IMAP and/or POP servers, you may find managing all the authentication settings inconvenient and - error-prone. The account-hook command may help. This hook works like - folder-hook but is invoked whenever you access a remote mailbox + error-prone. The command may help. This hook works like + but is invoked whenever you access a remote mailbox (including inside the folder browser), not just when you open the mailbox. @@ -7749,10 +8025,10 @@ score !~* =42 - + account-hook . 'unset imap_user; unset imap_pass; unset tunnel' account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo' -account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' +account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' @@ -7763,7 +8039,7 @@ account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' - Start a WWW Browser on URLs (EXTERNAL) + Start a WWW Browser on URLs (EXTERNAL) If a message contains URLs (unified resource locator = address in the @@ -7771,13 +8047,12 @@ account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' efficient to get a menu with all the URLs and start a WWW browser on one of them. This functionality is provided by the external urlview program which can be - retrieved at ftp://ftp.mutt.org/mutt/contrib/ -> + retrieved at and the configuration commands: - + macro index \cb |urlview\n -macro pager \cb |urlview\n +macro pager \cb |urlview\n @@ -7787,8 +8062,8 @@ macro pager \cb |urlview\n - - Compressed folders Support (OPTIONAL) + + Compressed folders Support (OPTIONAL) If Mutt-ng was compiled with compressed folders support (by running the @@ -7814,10 +8089,8 @@ macro pager \cb |urlview\n - There are three hooks defined (open-hook, - close-hook and - append-hook - + There are three hooks defined (, + and )which define commands to uncompress and compress a folder and to append messages to an existing compressed folder respectively. @@ -7829,25 +8102,19 @@ macro pager \cb |urlview\n - -open-hook \\.gz$ "gzip -cd %f > %t" -close-hook \\.gz$ "gzip -c %t > %f" -append-hook \\.gz$ "gzip -c %t >> %f" + +open-hook \\.gz$ "gzip -cd %f > %t" +close-hook \\.gz$ "gzip -c %t > %f" +append-hook \\.gz$ "gzip -c %t >> %f" - You do not have to specify all of the commands. If you omit - append-hook - + You do not have to specify all of the commands. If you omit ,the folder will be open and - closed again each time you will add to it. If you omit - close-hook - + closed again each time you will add to it. If you omit (or give empty command) , the - folder will be open in the mode. If you specify - append-hook - + folder will be open in the mode. If you specify though you'll be able to append to the folder. @@ -7859,9 +8126,8 @@ append-hook \\.gz$ "gzip -c %t >> %f" supposes it is not compressed. This is important because it allows the use of programs that do not have well defined extensions. Just use "." as a regexp. But this may be surprising if your - compressing script produces empty files. In this situation, unset - save-empty - + compressing script produces empty files. In this situation, unset + ,so that the compressed file will be removed if you delete all of the messages. @@ -7870,8 +8136,7 @@ append-hook \\.gz$ "gzip -c %t >> %f" Open a compressed mailbox for reading - Usage: open-hook regexp - "command" + Usage: regexp "command" @@ -7883,16 +8148,16 @@ append-hook \\.gz$ "gzip -c %t >> %f" The command string is the printf-like format string, and it - should accept two parameters: %f, which is replaced with the - (compressed) folder name, and %t which is replaced with the + should accept two parameters: %f, which is replaced with the + (compressed) folder name, and %t which is replaced with the name of the temporary folder to which to write. - %f and %t can be repeated any number of times in the + %f and %t can be repeated any number of times in the command string, and all of the entries are replaced with the - appropriate folder name. In addition, %% is replaced by - %, as in printf, and any other %anything is left as is. + appropriate folder name. In addition, %% is replaced by + %, as in printf, and any other %anything is left as is. @@ -7908,9 +8173,8 @@ append-hook \\.gz$ "gzip -c %t >> %f" - -open-hook \\.gz$ "gzip -cd %f > %t" - + +open-hook \\.gz$ "gzip -cd %f > %t" @@ -7926,14 +8190,11 @@ open-hook \\.gz$ "gzip -cd %f > %t" Write a compressed mailbox - Usage: close-hook regexp - "command" + Usage: regexp"command" - This is used to close the folder that was open with the - open-hook - + This is used to close the folder that was open with the command after some changes were made to it. @@ -7942,11 +8203,9 @@ open-hook \\.gz$ "gzip -cd %f > %t" used for closing the folders whose names match regexp. It has the same format as in - the open-hook command. Temporary + the command. Temporary folder - in this case is the folder previously produced by the < - open-hook - + in this case is the folder previously produced by the command. @@ -7963,8 +8222,8 @@ open-hook \\.gz$ "gzip -cd %f > %t" - -close-hook \\.gz$ "gzip -c %t > %f" + +close-hook \\.gz$ "gzip -c %t > %f" @@ -7975,7 +8234,7 @@ close-hook \\.gz$ "gzip -c %t > %f" - close-hook is not called when you + is not called when you exit from the folder if the folder was not changed. @@ -7986,8 +8245,7 @@ close-hook \\.gz$ "gzip -c %t > %f" Append a message to a compressed mailbox - Usage: append-hook regexp - "command" + Usage: regexp"command" @@ -7996,7 +8254,7 @@ close-hook \\.gz$ "gzip -c %t > %f" appending to the folders whose names match regexp. It has the same format as in - the open-hook command. + the command. The temporary folder in this case contains the messages that are beingappended. @@ -8014,29 +8272,23 @@ close-hook \\.gz$ "gzip -c %t > %f" - -append-hook \\.gz$ "gzip -c %t >> %f" + +append-hook \\.gz$ "gzip -c %t >> %f" - When append-hook is used, the + When is used, the folder is not opened, which saves time, but this means that we can not find out - what the folder type is. Thus the default ( - mbox-type - + what the folder type is. Thus the default ( )type is always supposed (i.e. this is the format used for the temporary folder). - If the file does not exist when you save to it, - close-hook - - is called, and not append-hook. - append-hook - + If the file does not exist when you save to it, + is called, and not . is only for appending to existing folders. @@ -8045,15 +8297,13 @@ append-hook \\.gz$ "gzip -c %t >> %f" If the command is empty, this operation is disabled for this file type. In this case, the folder will be open and closed again (using - open-hook and - close-hook - + and respectively) each time you will add to it. - + Encrypted folders @@ -8064,16 +8314,15 @@ append-hook \\.gz$ "gzip -c %t >> %f" - -open-hook \\.pgp$ "pgp -f < %f > %t" -close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" - + +open-hook \\.pgp$ "pgp -f < %f > %t" +close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" Please note, that PGP does not support appending to an encrypted - folder, so there is no append-hook defined. + folder, so there is no defined. @@ -8096,9 +8345,10 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" + - - Mutt-ng's MIME Support + + Mutt-ng's MIME Support Quite a bit of effort has been made to make Mutt-ng the premier text-mode @@ -8113,8 +8363,8 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" the external commands to use for handling specific MIME types. - - Using MIME in Mutt + + Using MIME in Mutt There are three areas/menus in Mutt-ng which deal with MIME, they are @@ -8123,7 +8373,7 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" menu. - + Viewing MIME messages in the pager @@ -8186,7 +8436,7 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" Finally, you can apply the usual message-related functions (like - resend-message, and the reply + , and the reply and forward functions) to attachments of type message/rfc822. @@ -8214,8 +8464,8 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" Attachments appear as follows: -1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description> -2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description> +1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description> +2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description> @@ -8225,12 +8475,12 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" toggle-unlink command (default: u). The next field is the MIME content-type, and can be changed with the edit-type command - (default: ˆT). The next field is the encoding for the + (default: ^T). The next field is the encoding for the attachment, which allows a binary message to be encoded for transmission on 7bit links. It can be changed with the edit-encoding command - (default: ˆE). The next field is the size of the attachment, + (default: ^E). The next field is the size of the attachment, rounded to kilobytes or megabytes. The next field is the filename, which can be changed with the rename-file command (default: R). @@ -8247,17 +8497,14 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" - + MIME Type configuration with <literal>mime.types</literal> When you add an attachment to your mail message, Mutt-ng searches your - personal mime.types file at - ${HOME}/.mime.types - - ,and then + personal mime.types file within and then the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types @@ -8289,7 +8536,7 @@ audio/x-aiff aif aifc aiff type that Mutt-ng assigns to an attachment by using the edit-type - command from the compose menu (default: ˆT). The MIME type is + 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 @@ -8313,14 +8560,14 @@ audio/x-aiff aif aifc aiff - + MIME Viewer configuration with <literal>mailcap</literal> - Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix - specific format specified in Appendix A of RFC 1524. This file format + Mutt-ng supports MIME Configuration, in particular the Unix + specific format specified in Appendix A of the RfC. 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 @@ -8336,7 +8583,7 @@ audio/x-aiff aif aifc aiff ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap - where $HOME is your home directory. + where is your home directory. @@ -8346,7 +8593,7 @@ ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/et entries. - + The Basics of the mailcap file @@ -8356,7 +8603,7 @@ ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/et - A comment line consists of a # character followed by anything you + A comment line consists of a # character followed by anything you want. @@ -8374,7 +8621,7 @@ ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/et The content type is specified in the MIME standard type/subtype method. For example, - text/plain, text/html, image/gif, + text/plain, text/html, image/gif, etc. In addition, the mailcap format includes two formats for wildcards, one using the special '*' subtype, the other is the implicit @@ -8391,10 +8638,10 @@ ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/et 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 behavior by using %s as a parameter to your view command. + 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 - file, and then call the view command with the %s replaced by + file, and then call the view command with the %s replaced by the name of the temporary file. In both cases, Mutt-ng will turn over the terminal to the view program until the program quits, at which time @@ -8421,7 +8668,7 @@ text/plain; more %s text/html; lynx %s In this case, lynx does not support viewing a file from stdin, so you - must use the %s syntax. + must use the %s syntax. Note: Some older versions of lynx contain a bug where they will check the mailcap file for a viewer for text/html. They will @@ -8456,7 +8703,7 @@ text/*; more - + Secure use of mailcap @@ -8464,11 +8711,9 @@ text/*; more parameters can lead to security problems in general. Mutt-ng tries to quote parameters - in expansion of %s syntaxes properly, and avoids risky + in expansion of %s syntaxes properly, and avoids risky characters by - substituting them, see the - mailcap-sanitize - + substituting them, see the variable. @@ -8480,7 +8725,7 @@ text/*; more - Keep the %-expandos away from shell quoting. + Keep the %-expandos away from shell quoting. 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 @@ -8491,11 +8736,11 @@ text/*; more - If you have to use the %-expandos' values in context where you + If you have to use the %-expandos' values in context where you need quoting or backtick expansions, put that value into a shell variable and reference the shell variable where necessary, as in the following - example (using $charset inside the backtick + example (using $charset inside the backtick expansion is safe, since it is not itself subject to any further expansion): @@ -8510,10 +8755,10 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ - + Advanced mailcap Usage - + Optional Fields @@ -8556,15 +8801,13 @@ text/html; lynx -dump %s ; copiousoutput needsterminal - Mutt-ng uses this flag when viewing attachments with - auto-view - - ,in order to decide whether it should honor the setting - of the wait-key variable or + Mutt-ng uses this flag when viewing attachments with , + in order to decide whether it should honor the setting + of the variable or not. When an attachment is viewed using an interactive program, and the corresponding mailcap entry has a needsterminal flag, Mutt-ng will use - wait-key and the exit + and the exit statusof the program to decide if it will ask you to press a key after the external program has exited. In all other situations it @@ -8630,7 +8873,7 @@ text/html; lynx -dump %s ; copiousoutput This field specifies the format for the file denoted by - %s in the + %s in the command fields. Certain programs will require a certain file extension, for instance, to correctly view a file. For instance, lynx @@ -8687,7 +8930,7 @@ text/html; lynx %s - + Search Order @@ -8712,9 +8955,7 @@ nametemplate=%s.gif - In addition, you can use this with - auto-view - + In addition, you can use this with to denote two commands for viewing an attachment, one to be viewed automatically, the other to be viewed interactively from the attachment @@ -8727,7 +8968,7 @@ text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s; nametemplate=%s.html text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - For auto-view, Mutt-ng will choose + For , Mutt-ng will choose the third entry because of the copiousoutput tag. For interactive viewing, Mutt @@ -8740,7 +8981,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - + Command Expansion @@ -8755,7 +8996,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - %s + %s As seen in the basic mailcap section, this variable is @@ -8773,10 +9014,10 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - %t + %t - Mutt-ng will expand %t to the text representation of + 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 @@ -8786,7 +9027,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - %{<parameter>} + %{<parameter>} Mutt-ng will expand this to the value of the specified @@ -8795,10 +9036,10 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput instance, if Your mail message contains: - -Content-Type: text/plain; charset=iso-8859-1 + +Content-Type: text/plain; charset=iso-8859-1 - then Mutt-ng will expand %{charset} to + 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 @@ -8807,17 +9048,17 @@ Content-Type: text/plain; charset=iso-8859-1 - \% + \% - This will be replaced by a % + This will be replaced by a % - Mutt-ng does not currently support the %F and %n + Mutt-ng does not currently support the %F and %n keywords - specified in RFC 1524. The main purpose of these parameters is for + specified in . The main purpose of these parameters is for multipart messages, which is handled internally by Mutt-ng. @@ -8825,7 +9066,7 @@ Content-Type: text/plain; charset=iso-8859-1 - + Example mailcap files @@ -8833,8 +9074,8 @@ Content-Type: text/plain; charset=iso-8859-1 > # I'm always running X :) -video/*; xanim %s > /dev/null -image/*; xv %s > /dev/null +video/*; xanim %s > /dev/null +image/*; xv %s > /dev/null # I'm always running netscape (if my computer had more memory, maybe) text/html; netscape -remote 'openURL(%s)' @@ -8850,7 +9091,7 @@ text/html; netscape -remote 'openURL(%s)' # Use xanim to view all videos Xanim produces a header on startup, # send that to /dev/null so I don't see it -video/*; xanim %s > /dev/null +video/*; xanim %s > /dev/null # Send html to a running netscape by remote text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape @@ -8876,8 +9117,8 @@ image/jpeg;xv %s; x-mozilla-flags=internal image/*;xv %s; test=RunningX; edit=xpaint %s # Convert images to text using the netpbm tools -image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm | -pbmtoascii -1x2 ) 2>&1 ; copiousoutput +image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | \ +pgmtopbm | pbmtoascii -1x2 ) 2>&1 ; copiousoutput # Send excel spreadsheets to my NT box application/ms-excel; open.pl %s @@ -8892,9 +9133,17 @@ application/ms-excel; open.pl %s - - MIME Autoview - + + MIME Autoview + + + mime-type [mime-type ...] + + + + mime-type [mime-type ...] + + In addition to explicitly telling Mutt-ng to view an attachment with theMIME viewer defined in the mailcap file, Mutt-ng has support for @@ -8910,17 +9159,17 @@ application/ms-excel; open.pl %s - You then use the auto_view muttrc command to + You then use the auto_view muttrc command to list the content-types that you wish to view automatically. - For instance, if you set auto_view to: + For instance, if you set auto_view to: - + auto_view text/html application/x-gunzip application/postscript -image/gif application/x-tar-gz +image/gif application/x-tar-gz @@ -8938,11 +9187,11 @@ application/postscript; ps2ascii %s; copiousoutput - ``unauto_view'' can be used to remove previous entries from the + ``unauto_view'' can be used to remove previous entries from the autoview list. - This can be used with message-hook to autoview messages based on size, + This can be used with to autoview messages based on size, etc. - ``unauto_view *'' will remove all previous entries. + ``unauto_view *'' will remove all previous entries. @@ -8951,34 +9200,42 @@ application/postscript; ps2ascii %s; copiousoutput - - MIME Multipart/Alternative + + MIME Multipart/Alternative + + + mime-type [mime-type ...] + + + mime-type [mime-type ...] + + 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 - typesis preferred. The alternative_order list consists of a + alternative_order list to determine if one of the available + typesis preferred. The alternative_order list consists of a number of MIME types in order, including support for implicit and explicit wildcards, for example: - - + + alternative_order text/enriched text/plain text -application/postscript image/* +application/postscript image/* Next, mutt will check if any of the types have a defined - auto-view, and use that. Failing + , and use that. Failing that, Mutt-ng will look for any text type. As a last attempt, mutt willlook for any type it knows how to handle. - To remove a MIME type from the alternative_order list, use the - unalternative_order command. + To remove a MIME type from the alternative_order list, use the + unalternative_order command. @@ -8986,17 +9243,146 @@ application/postscript image/* - - - MIME Lookup - + + + Attachment Searching and Counting + - Mutt-ng's mime_lookup list specifies a list of mime-types that + If you ever lose track of attachments in your mailboxes, Mutt's + attachment-counting and -searching support might be for you. You + can make your message index display the number of qualifying + attachments in each message, or search for messages by + attachment count. You also can configure what kinds of + attachments qualify for this feature with the attachments and + unattachments commands. + + + +The syntax is: + + + + + ( {+|-}disposition mime-type | ? ) + + + + + {+|-}disposition mime-type + + + + +Disposition is the attachment's Content-disposition type -- either +"inline" or "attachment". You can abbreviate this to I or A. + + + +Disposition is prefixed by either a + symbolor a - symbol. If it's +a +, you're saying that you want to allow this disposition and MIME +type to qualify. If it's a -, you're saying that this disposition +and MIME type is an exception to previous + rules. There are examples +below of how this is useful. + + + +Mime-type is, unsurprisingly, the MIME type of the attachment you want +to affect. A MIME type is always of the format "major/minor", where +"major" describes the broad category of document you're looking at, and +"minor" describes the specific type within that category. The major +part of mim-type must be literal text (or the special token "*"), but +the minor part may be a regular expression. (Therefore, "*/.*" matches +any MIME type.) + + + +The MIME types you give to the attachments directive are a kind of +pattern. When you use the attachments directive, the patterns you +specify are added to a list. When you use unattachments, the pattern +is removed from the list. The patterns are not expanded and matched +to specific MIME types at this time -- they're just text in a list. +They're only matched when actually evaluating a message. + + + +Some examples might help to illustrate. The examples that are not +commented out define the default configuration of the lists. + + + +## Removing a pattern from a list removes that pattern literally. It +## does not remove any type matching the pattern. +## +## attachments +A */.* +## attachments +A image/jpeg +## unattachments +A */.* +## +## This leaves "attached" image/jpeg files on the allowed attachments +## list. It does not remove all items, as you might expect, because the +## second */.* is not a matching expression at this time. +## +## Remember: "unattachments" only undoes what "attachments" has done! +## It does not trigger any matching on actual messages. + + +## Qualify any MIME part with an "attachment" disposition, EXCEPT for +## text/x-vcard and application/pgp parts. (PGP parts are already known +## to mutt, and can be searched for with ~g, ~G, and ~k.) +## +## I've added x-pkcs7 to this, since it functions (for S/MIME) +## analogously to PGP signature attachments. S/MIME isn't supported +## in a stock mutt build, but we can still treat it specially here. +## +attachments +A */.* +attachments -A text/x-vcard application/pgp.* +attachments -A application/x-pkcs7-.* + +## Discount all MIME parts with an "inline" disposition, unless they're +## text/plain. (Why inline a text/plain part unless it's external to the +## message flow?) +## +attachments +I text/plain + +## These two lines make Mutt qualify MIME containers. (So, for example, +## a message/rfc822 forward will count as an attachment.) The first +## line is unnecessary if you already have "attach-allow */.*", of +## course. These are off by default! The MIME elements contained +## within a message/* or multipart/* are still examined, even if the +## containers themseves don't qualify. +## +#attachments +A message/.* multipart/.* +#attachments +I message/.* multipart/.* + +## You probably don't really care to know about deleted attachments. +attachments -A message/external-body +attachments -I message/external-body + + + +"attachments ?" will list your current settings in Muttrc format, so +that it can be pasted elsewhere. + + + + + + MIME Lookup + + + mime-type [mime-type ...] + + + + mime-type [mime-type ...] + + + + 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 todeal with binary types such as application/octet-stream. When an attachment's - mime-type is listed in mime_lookup, then the extension of the + mime-type is listed in mime_lookup, then the extension of the filename will be compared to the list of extensions in the mime.types file. The mime-type @@ -9004,15 +9390,15 @@ application/postscript image/* attachment according to the rules in the mailcap file and according to any other configuration - options (such as auto_view) specified. Common usage would be: + options (such as auto_view) specified. Common usage would be: - -mime_lookup application/octet-stream application/X-Lotus-Manuscript + +mime_lookup application/octet-stream application/X-Lotus-Manuscript - In addition, the unmime_lookup command may be used to disable + In addition, the unmime_lookup command may be used to disable this feature for any particular mime-type if it had been set, for example, in a global @@ -9030,9 +9416,10 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript + - - Security Considerations + + Security Considerations First of all, mutt-ng contains no security holes included by @@ -9058,8 +9445,8 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript of setup, please read this chapter carefully. - - Passwords + + Passwords Although mutt-ng can be told the various passwords for accounts, @@ -9073,25 +9460,25 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript - - Temporary Files + + Temporary Files Mutt-ng uses many temporary files for viewing messages, verifying - digital signatures, etc. The umask + digital signatures, etc. The variable can be used to change the default permissions of these files. Please only change it if you really know what you are doing. Also, a different location for these files may be desired which can - be changed via the tmpdir variable. + be changed via the variable. - - Information Leaks + + Information Leaks - - Message-ID: headers + + Message-ID: headers In the default configuration, mutt-ng will leak some information @@ -9100,17 +9487,17 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript is increased (and rotated) with every message sent. If you'd like to hide this information probably telling others how many mail you sent in which - time, you at least need to remove the %P + time, you at least need to remove the %P expando from the - default setting of the msgid-format variable. Please make sure that + default setting of the variable. Please make sure that you really know how local parts of these Message-ID: headers are composed. - - mailto:-style links + + mailto:-style links As mutt-ng be can be set up to be the mail client to handle @@ -9119,7 +9506,7 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript will be strict in interpreting them which means that arbitrary header fields can be embedded in these links which could override existing header fields or attach arbitrary files. This may be - problematic if the edit-headers + problematic if the variable is unset, i.e. the user doesn't want to see header fields while editing the message. @@ -9142,9 +9529,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - When unsetting the - strict-mailto - + When unsetting the variable, mutt-ng will @@ -9164,7 +9549,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - turn on the edit-headers + turn on the variable by force to let the user see all the headers (because they still may leak information.) @@ -9180,8 +9565,8 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - - External applications + + External applications Mutt-ng in many places has to rely on external applications or @@ -9189,16 +9574,15 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg applications. - - mailcap + + mailcap One of these is the mailcap mechanism as defined - by RfC - 1524. Mutt-ng can be set up to automatically + by . Mutt-ng can be set up to automatically execute any given utility as listed in one of the mailcap files (see the - mailcap-path + variable for details.) @@ -9242,7 +9626,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - leave the mailcap-sanitize variable in its default + leave the variable in its default state to restrict mailcap expandos to a safe set of characters @@ -9254,8 +9638,8 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - - Other + + Other Besides the mailcap mechanism, mutt-ng uses a number of other @@ -9279,12 +9663,13 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg + - - Reference + + Reference - Command line options + Command line options Running mutt with no arguments will make Mutt-ng @@ -9295,8 +9680,8 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - - Mutt-NG Command Line Options +
+ Reference: Command Line Options @@ -9305,29 +9690,98 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - -A expand an alias - -a attach a file to a message - -b specify a blind carbon-copy (BCC) address - -c specify a carbon-copy (Cc) address - -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 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 - -n do not read the system Muttngrc - -p recall a postponed message - -Q query a configuration variable - -R open mailbox in read-only mode - -s specify a subject (enclose in quotes if it contains spaces) - -t dump the value of all variables to stdout - -T dump the value of all changed variables to stdout - -v show version number and compile-time definitions - -x simulate the mailx(1) compose mode - -y show a menu containing the files specified by the mailboxes command - -z exit immediately if there are no messages in the mailbox - -Z open the first folder with new message,exit immediately if none + + -A + expand an alias + + + -a + attach a file to a message + + + -b + specify a blind carbon-copy (BCC) address + + + -c + specify a carbon-copy (Cc) address + + + -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 + 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 + + + -n + do not read the system Muttngrc + + + -p + recall a postponed message + + + -Q + query a configuration variable + + + -R + open mailbox in read-only mode + + + -s + specify a subject (enclose in quotes if it contains spaces) + + + -t + dump the value of all variables to stdout + + + -T + dump the value of all changed variables to stdout + + + -v + show version number and compile-time definitions + + + -x + simulate the mailx(1) compose mode + + + -y + show a menu containing the files specified by the mailboxes command + + + -z + exit immediately if there are no messages in the mailbox + + + -Z + open the first folder with new message,exit immediately if none +
@@ -9339,10 +9793,10 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - mutt [ -nz ] [ -F muttrc ] [ -m + mutt ] -nz ] ] -F muttrc ] ] -m type - ] [ -f mailbox ] + ] ] -f mailbox ] @@ -9350,16 +9804,16 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - mutt [ -n ] [ -F muttrc ] [ -a + mutt ] -n ] ] -F muttrc ] ] -a file - ] [ -c address ] [ -i + ] ] -c address ] ] -i filename - ] [ -s subject ] address [ + ] ] -s subject ] address ] address - ... ] + ... ] @@ -9369,18 +9823,18 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - mutt -s "data set for run #2" + mutt -s "data set for run #2" professor@bigschool.edu - < ˜/run2.dat + < ~/run2.dat This command will send a message to ``professor@bigschool.edu'' with a subject - of ``data set for run #2''. In the body of the message will be the + of ``data set for run #2''. In the body of the message will be the contents - of the file ``˜/run2.dat''. + of the file ``~/run2.dat''. @@ -9390,12 +9844,12 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - Patterns + Patterns - - Patterns +
+ Reference: Patterns @@ -9405,50 +9859,232 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - ~A all messages - ~b EXPR messages which contain EXPR in the message body - ~B EXPR messages which contain EXPR in the whole message - ~c EXPR messages carbon-copied to EXPR - ~C EXPR message is either to: or cc: EXPR - ~D deleted messages - ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range - ~E expired messages - ~e EXPR message which contains EXPR in the ``Sender'' field - ~F flagged messages - ~f EXPR messages originating from EXPR - ~g cryptographically signed 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 - ~i EXPR 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 - ~m [MIN]-[MAX] message in the range MIN to MAX *) - ~M multipart messages - ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *) - ~N new messages - ~O old messages - ~p message is addressed to you (consults alternates) - ~P message is from you (consults alternates) - ~Q messages which have been replied to - ~R read messages - ~r [MIN]-[MAX] messages with ``date-received'' in a Date range - ~S superseded messages - ~s EXPR messages having EXPR in the ``Subject'' field. - ~T tagged messages - ~t EXPR messages addressed to EXPR - ~U unread messages - ~u message is addressed to a subscribed mailing list - ~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) + + + + all messages + + + + EXPR + messages which contain EXPR in the message body + + + + EXPR + messages which contain EXPR in the whole message + + + + EXPR + messages carbon-copied to EXPR + + + + EXPR + message is either to: or cc: EXPR + + + + + deleted messages + + + + [MIN]-[MAX] + messages with ``date-sent'' in a Date range + + + + + expired messages + + + + EXPR + message which contains EXPR in the ``Sender'' field + + + + + flagged messages + + + + EXPR + messages originating from EXPR + + + + + cryptographically signed messages + + + + + cryptographically encrypted messages + + + + EXPR + messages with a spam attribute matching EXPR + + + + EXPR + messages which contain EXPR in the message header + + + + + message contains PGP key material + + + + EXPR + message which match ID in the ``Message-ID'' field + + + + EXPR + message is either originated or received by EXPR + + + + + message is addressed to a known mailing list + + + + [MIN]-[MAX] + message in the range MIN to MAX *) + + + + + multipart messages + + + + [MIN]-[MAX] + messages with a score in the range MIN to MAX *) + + + + + new messages + + + + + old messages + + + + + message is addressed to you (consults alternates) + + + + + message is from you (consults alternates) + + + + + messages which have been replied to + + + + + read messages + + + + [MIN]-[MAX] + messages with ``date-received'' in a Date range + + + + + superseded messages + + + + EXPR + messages having EXPR in the ``Subject'' field. + + + + + tagged messages + + + + EXPR + messages addressed to EXPR + + + + + unread messages + + + + + message is addressed to a subscribed mailing list + + + + + message is part of a collapsed thread. + + + + + cryptographically verified messages + + + + EXPR + messages which contain EXPR in the `Newsgroups' field (if compiled with NNTP support) + + + + EXPR + messages which contain EXPR in the `References' field + + + + [MIN]-[MAX] + messages with MIN to MAX attachments *) + + + + EXPR + messages which contain EXPR in the `X-Label' field + + + + [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) +
@@ -9456,7 +10092,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg Where EXPR are - regexp. Special attention has to be + regexp. 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 (\), @@ -9467,22 +10103,15 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - *) The forms <[MAX], - >[MIN] - - , - [MIN]- and -[MAX] + *) The forms <[MAX], >[MIN], + [MIN]- and -[MAX] are allowed, too. - - - - - Configuration Commands + Configuration Commands The following are the commands understood by mutt. @@ -9494,521 +10123,326 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - - account-hook - - pattern command + pattern command - - alias - - key address [ , - address - - ,... ] + key address [, address, ... ] - - alias - - [ * | key ... ] + [ * | key ... ] - - alternates - - regexp [ regexp - ... ] + regexp [ regexp ... ] - - alternates - - [ * | regexp ... ] + [ * | regexp ... ] - - alternative-order - - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - - alternative-order - - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - - append-hook - - regexp command + regexp command - - auto-view - - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - - auto-view - - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - - bind - - map key - function - + map key function - - charset-hook - - alias charset + alias charset - - close-hook - - regexp command + regexp command - - color - - object foreground - background - - [ regexp ] + object foreground background [ regexp ] - - color - - index pattern [ - pattern - - ... ] + index pattern [ pattern ... ] - - exec - - function [ function ... ] + function [ function ... ] - - fcc-hook - - pattern mailbox + pattern mailbox - - fcc-save-hook - - pattern mailbox + pattern mailbox - - folder-hook - - pattern command + pattern command - - hdr-order - - header [ header - ... ] + header [ header ... ] - - hdr-order - - header [ header - ... ] + header [ header ... ] - - charset-hook - - charset local-charset + charset local-charset - - ignore - - pattern [ pattern - ... ] + pattern [ pattern ... ] - - ignore - - pattern [ pattern - ... ] + pattern [ pattern ... ] - - lists - - regexp [ regexp - ... ] + regexp [ regexp ... ] - - lists - - regexp [ regexp - ... ] + regexp [ regexp ... ] - - macro - - menu key - sequence - - [ description ] + menu key sequence [ description ] - - mailboxes - - filename [ filename ... ] + filename [ filename ... ] - - mbox-hook - - pattern mailbox + pattern mailbox - - message-hook - - pattern command + pattern command - - mime-lookup - - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - mime-lookup - - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - - color - - object attribute [ regexp ] + object attribute [ regexp ] - - color - - index pattern [ - pattern - - ... ] + index pattern [ pattern ... ] - - my-hdr - - string + string - - my-hdr - - field [ field ... - ] + field [ field ... ] - - open-hook - - regexp command + regexp command - - crypt-hook - - pattern key-id + pattern key-id - - push - - string + string - - set - - variable [variable - ... ] + variable [ variable ... ] - - save-hook - - regexp filename + regexp filename - - score-command - - pattern value + pattern value - - score-command - - pattern [ pattern - ... ] + pattern [ pattern ... ] - - send-hook - - regexp command + regexp command - - reply-hook - - regexp command + regexp command - - set - - [no|inv]variable[= - value - - ] [ variable ... ] + [no|inv]variable[ =value ] [ variable ... ] - - set - - variable [variable - ... ] + variable [ variable ... ] - - source - - filename + filename - - spam - - pattern format + pattern format - - spam - - pattern + pattern - - lists - - regexp [ regexp - ... ] + regexp [ regexp ... ] - - lists - - regexp [ regexp - ... ] + regexp [ regexp ... ] - - set - - variable [variable - ... ] + variable [ variable ... ] - - unhook - - hook-type + hook-type @@ -10031,8 +10465,8 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - - Obsolete Variables +
+ Reference: Obsolete Variables @@ -10041,47 +10475,170 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - edit_hdrsedit_headers - forw_decodeforward_decode - forw_formatforward_format - forw_quoteforward_quote - hdr_formatindex_format - indent_strindent_string - mime_fwdmime_forward - msg_formatmessage_format - pgp_autosigncrypt_autosign - pgp_autoencryptcrypt_autoencrypt - pgp_replyencryptcrypt_replyencrypt - pgp_replysigncrypt_replysign - pgp_replysignencryptedcrypt_replysignencrypted - pgp_verify_sigcrypt_verify_sig - pgp_create_traditionalpgp_autoinline - pgp_auto_traditionalpgp_replyinline - forw_decryptforward_decrypt - smime_sign_assmime_default_key - post_indent_strpost_indent_string - print_cmdprint_command - shorten_hierarchysidebar_shorten_hierarchy - ask_followup_tonntp_ask_followup_to - ask_x_comment_tonntp_ask_x_comment_to - catchup_newsgroupnntp_catchup - followup_to_posternntp_followup_to_poster - group_index_formatnntp_group_index_format - inewsnntp_inews - mime_subjectnntp_mime_subject - news_cache_dirnntp_cache_dir - news_servernntp_host - newsrcnntp_newsrc - nntp_pollnntp_mail_check - pop_checkintervalpop_mail_check - post_moderatednntp_post_moderated - save_unsubscribednntp_save_unsubscribed - show_new_newsnntp_show_new_news - show_only_unreadnntp_show_only_unread - x_comment_tonntp_x_comment_to - smtp_auth_usernamesmtp_user - smtp_auth_passwordsmtp_pass - user_agentagent_string + + edit_hdrs + + + + forw_decode + + + + forw_format + + + + forw_quote + + + + hdr_format + + + + indent_str + + + + mime_fwd + + + + msg_format + + + + pgp_autosign + + + + pgp_autoencrypt + + + + pgp_replyencrypt + + + + pgp_replysign + + + + pgp_replysignencrypted + + + + pgp_verify_sig + + + + pgp_create_traditional + + + + pgp_auto_traditional + + + + forw_decrypt + + + + smime_sign_as + + + + post_indent_str + + + + print_cmd + + + + shorten_hierarchy + + + + ask_followup_to + + + + ask_x_comment_to + + + + catchup_newsgroup + + + + followup_to_poster + + + + group_index_format + + + + inews + + + + mime_subject + + + + news_cache_dir + + + + news_server + + + + newsrc + + + + nntp_poll + + + + pop_checkinterval + + + + post_moderated + + + + save_unsubscribed + + + + show_new_news + + + + show_only_unread + + + + x_comment_to + + + + smtp_auth_username + + + + smtp_auth_password + + + + user_agent + +