2 T
\bTh
\bhe
\be M
\bMu
\but
\btt
\bt N
\bNe
\bex
\bxt
\bt G
\bGe
\ben
\bne
\ber
\bra
\bat
\bti
\bio
\bon
\bn E
\bE-
\b-M
\bMa
\bai
\bil
\bl C
\bCl
\bli
\bie
\ben
\bnt
\bt
4 by Andreas Krennmair <ak@synflood.at> and others
5 originally based on _
\bm_
\bu_
\bt_
\bt by Michael Elkins <me@cs.hmc.edu> and others
9 A
\bAb
\bbs
\bst
\btr
\bra
\bac
\bct
\bt
11 Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
12 sucks less.'' - Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
14 _
\b1_
\b. _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
16 _
\b1_
\b._
\b1 _
\bO_
\bv_
\be_
\br_
\bv_
\bi_
\be_
\bw
18 M
\bMu
\but
\btt
\bt-
\b-n
\bng
\bg is a small but very powerful text-based MIME mail client. Mutt-ng is
19 highly configurable, and is well suited to the mail power user with advanced
20 features like key bindings, keyboard macros, mail threading, regular expression
21 searches and a powerful pattern matching language for selecting groups of mes-
24 This documentation additionally contains documentation to M
\bMu
\but
\btt
\bt-
\b-N
\bNG
\bG, a fork from
25 Mutt with the goal to fix all the little annoyances of Mutt, to integrate all
26 the Mutt patches that are floating around in the web, and to add other new fea-
27 tures. Features specific to Mutt-ng will be discussed in an extra section.
28 Don't be confused when most of the documentation talk about Mutt and not Mutt-
29 ng, Mutt-ng contains all Mutt features, plus many more.
31 _
\b1_
\b._
\b2 _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bH_
\bo_
\bm_
\be _
\bP_
\ba_
\bg_
\be
35 _
\b1_
\b._
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
37 +
\bo mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user support
40 The Mutt Next Generation E-Mail Client 1
42 The Mutt Next Generation E-Mail Client 2
44 +
\bo mutt-ng-devel@lists.berlios.de -- The development mailing list for mutt-ng
46 _
\b1_
\b._
\b4 _
\bS_
\bo_
\bf_
\bt_
\bw_
\ba_
\br_
\be _
\bD_
\bi_
\bs_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn _
\bS_
\bi_
\bt_
\be_
\bs
48 So far, there are no official releases of Mutt-ng, but you can download daily
49 snapshots from http://mutt-ng.berlios.de/snapshots/
51 _
\b1_
\b._
\b5 _
\bI_
\bR_
\bC
53 Visit channel _
\b#_
\bm_
\bu_
\bt_
\bt_
\bn_
\bg on irc.freenode.net (www.freenode.net) to chat with other
54 people interested in Mutt-ng.
56 _
\b1_
\b._
\b6 _
\bW_
\be_
\bb_
\bl_
\bo_
\bg
58 If you want to read fresh news about the latest development in Mutt-ng, and get
59 informed about stuff like interesting, Mutt-ng-related articles and packages
60 for your favorite distribution, you can read and/or subscribe to our Mutt-ng
63 _
\b1_
\b._
\b7 _
\bC_
\bo_
\bp_
\by_
\br_
\bi_
\bg_
\bh_
\bt
65 Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and others
67 This program is free software; you can redistribute it and/or modify it under
68 the terms of the GNU General Public License as published by the Free Software
69 Foundation; either version 2 of the License, or (at your option) any later ver-
72 This program is distributed in the hope that it will be useful, but WITHOUT ANY
73 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
74 PARTICULAR PURPOSE. See the GNU General Public License for more details.
76 You should have received a copy of the GNU General Public License along with
77 this program; if not, write to the Free Software Foundation, Inc., 59 Temple
78 Place - Suite 330, Boston, MA 02111, USA.
80 _
\b2_
\b. _
\bG_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bS_
\bt_
\ba_
\br_
\bt_
\be_
\bd
82 _
\b2_
\b._
\b1 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bC_
\bo_
\bn_
\bc_
\be_
\bp_
\bt_
\bs
84 The Mutt Next Generation E-Mail Client 3
86 _
\b2_
\b._
\b1_
\b._
\b1 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
88 mutt-ng offers different screens of which every has its special purpose:
90 +
\bo The _
\bi_
\bn_
\bd_
\be_
\bx displays the contents of the currently opened mailbox.
92 +
\bo The _
\bp_
\ba_
\bg_
\be_
\br is responsible for displaying messages, that is, the header, the
93 body and all attached parts.
95 +
\bo The _
\bf_
\bi_
\bl_
\be _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br offers operations on and displays information of all
96 folders mutt-ng should watch for mail.
98 +
\bo The _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br offers a permanent view of which mailboxes contain how many
99 total, new and/or flagged mails.
101 +
\bo The _
\bh_
\be_
\bl_
\bp _
\bs_
\bc_
\br_
\be_
\be_
\bn lists for all currently available commands how to invoke
102 them as well as a short description.
104 +
\bo The _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu is a comfortable interface take last actions before send-
105 ing mail: change subjects, attach files, remove attachements, etc.
107 +
\bo The _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\be_
\bm_
\be_
\bn_
\bt menu gives a summary and the tree structure of the
108 attachements of the current message.
110 +
\bo The _
\ba_
\bl_
\bi_
\ba_
\bs menu lists all or a fraction of the aliases a user has defined.
112 +
\bo The _
\bk_
\be_
\by menu used in connection with encryption lets users choose the
113 right key to encrypt with.
115 When mutt-ng is started without any further options, it'll open the users
116 default mailbox and display the index.
118 _
\b2_
\b._
\b1_
\b._
\b2 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
120 Mutt-ng does _
\bn_
\bo_
\bt feature an internal configuration interface or menu due to the
121 simple fact that this would be too complex to handle (currently there are sev-
122 eral _
\bh_
\bu_
\bn_
\bd_
\br_
\be_
\bd variables which fine-tune the behaviour.)
124 Mutt-ng is configured using configuration files which allow users to add com-
125 ments or manage them via version control systems to ease maintenance.
127 Also, mutt-ng comes with a shell script named grml-muttng kindly contributed by
128 users which really helps and eases the creation of a user's configuration file.
129 When downloading the source code via a snapshot or via subversion, it can be
130 found in the contrib directory.
132 _
\b2_
\b._
\b1_
\b._
\b3 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
134 Mutt-ng offers great flexibility due to the use of functions: internally, every
135 action a user can make mutt-ng perform is named ``function.'' Those functions
137 The Mutt Next Generation E-Mail Client 4
139 are assigned to keys (or even key sequences) and may be completely adjusted to
140 user's needs. The basic idea is that the impatient users get a very intuitive
141 interface to start off with and advanced users virtually get no limits to
144 _
\b2_
\b._
\b1_
\b._
\b4 _
\bI_
\bn_
\bt_
\be_
\br_
\ba_
\bc_
\bt_
\bi_
\bo_
\bn
146 Mutt-ng has two basic concepts of user interaction:
148 1. There is one dedicated line on the screen used to query the user for
149 input, issue any command, query variables and display error and informa-
150 tional messages. As for every type of user input, this requires manual
151 action leading to the need of input.
153 2. The automatized interface for interaction are the so called _
\bh_
\bo_
\bo_
\bk_
\bs. Hooks
154 specify actions the user wants to be performed at well-defined situa-
155 tions: what to do when entering which folder, what to do when displaying
156 or replying to what kind of message, etc. These are optional, i.e. a user
157 doesn't need to specify them but can do so.
159 _
\b2_
\b._
\b1_
\b._
\b5 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
161 Although mutt-ng has many functionality built-in, many features can be dele-
162 gated to external tools to increase flexibility: users can define programs to
163 filter a message through before displaying, users can use any program they want
164 for displaying a message, message types (such as PDF or PostScript) for which
165 mutt-ng doesn't have a built-in filter can be rendered by arbitrary tools and
166 so forth. Although mutt-ng has an alias mechanism built-in, it features using
167 external tools to query for nearly every type of addresses from sources like
168 LDAP, databases or just the list of locally known users.
170 _
\b2_
\b._
\b1_
\b._
\b6 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
172 Mutt-ng has a built-in pattern matching ``language'' which is as widely used as
173 possible to present a consistent interface to users. The same ``pattern terms''
174 can be used for searching, scoring, message selection and much more.
176 _
\b2_
\b._
\b2 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
178 _
\b2_
\b._
\b2_
\b._
\b1 _
\bI_
\bn_
\bd_
\be_
\bx
180 The index is the screen that you usually see first when you start mutt-ng. It
181 gives an overview over your emails in the currently opened mailbox. By default,
182 this is your system mailbox. The information you see in the index is a list of
184 The Mutt Next Generation E-Mail Client 5
186 emails, each with its number on the left, its flags (new email, important
187 email, email that has been forwarded or replied to, tagged email, ...), the
188 date when email was sent, its sender, the email size, and the subject. Addi-
189 tionally, the index also shows thread hierarchies: when you reply to an email,
190 and the other person replies back, you can see the other's person email in a
191 "sub-tree" below. This is especially useful for personal email between a group
192 of people or when you've subscribed to mailing lists.
194 _
\b2_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bg_
\be_
\br
196 The pager is responsible for showing the email content. On the top of the pager
197 you have an overview over the most important email headers like the sender, the
198 recipient, the subject, and much more information. How much information you
199 actually see depends on your configuration, which we'll describe below.
201 Below the headers, you see the email body which usually contains the message.
202 If the email contains any attachments, you will see more information about them
203 below the email body, or, if the attachments are text files, you can view them
204 directly in the pager.
206 To give the user a good overview, it is possible to configure mutt-ng to show
207 different things in the pager with different colors. Virtually everything that
208 can be described with a regular expression can be colored, e.g. URLs, email
209 addresses or smileys.
211 _
\b2_
\b._
\b2_
\b._
\b3 _
\bF_
\bi_
\bl_
\be _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
213 The file browser is the interface to the local or remote file system. When
214 selecting a mailbox to open, the browser allows custom sorting of items, limit-
215 ing the items shown by a regular expression and a freely adjustable format of
216 what to display in which way. It also allows for easy navigation through the
217 file system when selecting file(s) to attach to a message, select multiple
218 files to attach and many more.
220 _
\b2_
\b._
\b2_
\b._
\b4 _
\bS_
\bi_
\bd_
\be_
\bb_
\ba_
\br
222 The sidebar comes in handy to manage mails which are spread over different
223 folders. All folders users setup mutt-ng to watch for new mail will be listed.
224 The listing includes not only the name but also the number of total messages,
225 the number of new and flagged messages. Items with new mail may be colored dif-
226 ferent from those with flagged mail, items may be shortened or compress if
227 they're they to long to be printed in full form so that by abbreviated names,
228 user still now what the name stands for.
230 _
\b2_
\b._
\b2_
\b._
\b5 _
\bH_
\be_
\bl_
\bp
232 The Mutt Next Generation E-Mail Client 6
234 The help screen is meant to offer a quick help to the user. It lists the cur-
235 rent configuration of key bindings and their associated commands including a
236 short description, and currently unbound functions that still need to be asso-
237 ciated with a key binding (or alternatively, they can be called via the mutt-ng
240 _
\b2_
\b._
\b2_
\b._
\b6 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
242 The compose menu features a split screen containing the information which
243 really matter before actually sending a message by mail or posting an article
244 to a newsgroup: who gets the message as what (recipient, newsgroup, who gets
245 what kind of copy). Additionally, users may set security options like deciding
246 whether to sign, encrypt or sign and encrypt a message with/for what keys.
248 Also, it's used to attach messages, news articles or files to a message, to re-
249 edit any attachment including the message itself.
251 _
\b2_
\b._
\b2_
\b._
\b7 _
\bA_
\bl_
\bi_
\ba_
\bs _
\bM_
\be_
\bn_
\bu
253 The alias menu is used to help users finding the recipients of messages. For
254 users who need to contact many people, there's no need to remember addresses or
255 names completely because it allows for searching, too. The alias mechanism and
256 thus the alias menu also features grouping several addresses by a shorter nick-
257 name, the actual alias, so that users don't have to select each single recipi-
260 _
\b2_
\b._
\b2_
\b._
\b8 _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
262 As will be later discussed in detail, mutt-ng features a good and stable MIME
263 implementation, that is, is greatly supports sending and receiving messages of
264 arbitrary type. The attachment menu displays a message's structure in detail:
265 what content parts are attached to which parent part (which gives a true tree
266 structure), which type is of what type and what size. Single parts may saved,
267 deleted or modified to offer great and easy access to message's internals.
269 _
\b2_
\b._
\b2_
\b._
\b9 _
\bK_
\be_
\by _
\bM_
\be_
\bn_
\bu
273 _
\b2_
\b._
\b3 _
\bM_
\bo_
\bv_
\bi_
\bn_
\bg _
\bA_
\br_
\bo_
\bu_
\bn_
\bd _
\bi_
\bn _
\bM_
\be_
\bn_
\bu_
\bs
275 Information is presented in menus, very similar to ELM. Here is a table
277 The Mutt Next Generation E-Mail Client 7
279 showing the common keys used to navigate menus in Mutt-ng.
281 j or Down next-entry move to the next entry
282 k or Up previous-entry move to the previous entry
283 z or PageDn page-down go to the next page
284 Z or PageUp page-up go to the previous page
285 = or Home first-entry jump to the first entry
286 * or End last-entry jump to the last entry
287 q quit exit the current menu
288 ? help list all key bindings for the current menu
290 _
\b2_
\b._
\b4 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bI_
\bn_
\bp_
\bu_
\bt _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
292 Mutt-ng has a builtin line editor which is used as the primary way to input
293 textual data such as email addresses or filenames. The keys used to move
294 around while editing are very similar to those of Emacs.
296 ^A or <Home> bol move to the start of the line
297 ^B or <Left> backward-char move back one char
298 Esc B backward-word move back one word
299 ^D or <Delete> delete-char delete the char under the cursor
300 ^E or <End> eol move to the end of the line
301 ^F or <Right> forward-char move forward one char
302 Esc F forward-word move forward one word
303 <Tab> complete complete filename or alias
304 ^T complete-query complete address with query
305 ^K kill-eol delete to the end of the line
306 ESC d kill-eow delete to the end of the word
307 ^W kill-word kill the word in front of the cursor
308 ^U kill-line delete entire line
309 ^V quote-char quote the next typed key
310 <Up> history-up recall previous string from history
311 <Down> history-down recall next string from history
312 <BackSpace> backspace kill the char in front of the cursor
313 Esc u upcase-word convert word to upper case
314 Esc l downcase-word convert word to lower case
315 Esc c capitalize-word capitalize the word
317 <Return> n/a finish editing
319 You can remap the _
\be_
\bd_
\bi_
\bt_
\bo_
\br functions using the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 25) com-
320 mand. For example, to make the _
\bD_
\be_
\bl_
\be_
\bt_
\be key delete the character in front of the
321 cursor rather than under, you could use
323 bind editor <delete> backspace
325 The Mutt Next Generation E-Mail Client 8
327 _
\b2_
\b._
\b5 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl _
\b- _
\bT_
\bh_
\be _
\bI_
\bn_
\bd_
\be_
\bx _
\ba_
\bn_
\bd _
\bP_
\ba_
\bg_
\be_
\br
329 Similar to many other mail clients, there are two modes in which mail is read
330 in Mutt-ng. The first is the index of messages in the mailbox, which is called
331 the ``index'' in Mutt-ng. The second mode is the display of the message con-
332 tents. This is called the ``pager.''
334 The next few sections describe the functions provided in each of these modes.
336 _
\b2_
\b._
\b5_
\b._
\b1 _
\bT_
\bh_
\be _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bI_
\bn_
\bd_
\be_
\bx
338 c change to a different mailbox
339 ESC c change to a folder in read-only mode
340 C copy the current message to another mailbox
341 ESC C decode a message and copy it to a folder
342 ESC s decode a message and save it to a folder
343 D delete messages matching a pattern
344 d delete the current message
346 l show messages matching a pattern
347 N mark message as new
348 o change the current sort method
349 O reverse sort the mailbox
350 q save changes and exit
352 T tag messages matching a pattern
353 t toggle the tag on a message
354 ESC t toggle tag on entire message thread
355 U undelete messages matching a pattern
358 x abort changes and exit
359 <Return> display-message
360 <Tab> jump to the next new message
361 @ show the author's full e-mail address
362 $ save changes to mailbox
365 ^L clear and redraw the screen
366 ^T untag messages matching a pattern
368 _
\b2_
\b._
\b5_
\b._
\b1_
\b._
\b1 _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs _
\bF_
\bl_
\ba_
\bg_
\bs
370 In addition to who sent the message and the subject, a short summary of the
371 disposition of each message is printed beside the message number. Zero or more
372 of the following ``flags'' may appear, which mean:
375 message is deleted (is marked for deletion)
378 message have attachments marked for deletion
380 The Mutt Next Generation E-Mail Client 9
383 contains a PGP public key
392 message is PGP encrypted
395 message has been replied to
398 message is signed, and the signature is succesfully verified
409 Some of the status flags can be turned on or off using
411 +
\bo s
\bse
\bet
\bt-
\b-f
\bfl
\bla
\bag
\bg (default: w)
413 +
\bo c
\bcl
\ble
\bea
\bar
\br-
\b-f
\bfl
\bla
\bag
\bg (default: W)
415 Furthermore, the following flags reflect who the message is addressed to. They
416 can be customized with the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.328 , page 168) variable.
419 message is to you and you only
422 message is to you, but also to or cc'ed to others
425 message is cc'ed to you
431 message is sent to a subscribed mailing list
433 _
\b2_
\b._
\b5_
\b._
\b2 _
\bT_
\bh_
\be _
\bP_
\ba_
\bg_
\be_
\br
435 By default, Mutt-ng uses its builtin pager to display the body of messages.
437 The Mutt Next Generation E-Mail Client 10
439 The pager is very similar to the Unix program _
\bl_
\be_
\bs_
\bs though not nearly as fea-
442 <Return> go down one line
443 <Space> display the next page (or next message if at the end of a message)
444 - go back to the previous page
445 n search for next match
446 S skip beyond quoted text
447 T toggle display of quoted text
449 / search for a regular expression (pattern)
450 ESC / search backwards for a regular expression
451 \ toggle search pattern coloring
452 ^ jump to the top of the message
454 In addition, many of the functions from the _
\bi_
\bn_
\bd_
\be_
\bx are available in the pager,
455 such as _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be or _
\bc_
\bo_
\bp_
\by_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be (this is one advantage over using an
456 external pager to view messages).
458 Also, the internal pager supports a couple other advanced features. For one, it
459 will accept and translate the ``standard'' nroff sequences for bold and under-
460 line. These sequences are a series of either the letter, backspace (^H), the
461 letter again for bold or the letter, backspace, ``_'' for denoting underline.
462 Mutt-ng will attempt to display these in bold and underline respectively if
463 your terminal supports them. If not, you can use the bold and underline _
\bc_
\bo_
\bl_
\bo_
\br
464 (section 3.9 , page 29) objects to specify a color or mono attribute for them.
466 Additionally, the internal pager supports the ANSI escape sequences for charac-
467 ter attributes. Mutt-ng translates them into the correct color and character
468 settings. The sequences Mutt-ng supports are:
470 ESC [ Ps;Ps;Ps;...;Ps m
477 3x Foreground color is x
478 4x Background color is x
490 The Mutt Next Generation E-Mail Client 11
492 Mutt-ng uses these attributes for handling text/enriched messages, and they can
493 also be used by an external _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 77) script for high-
494 lighting purposes. N
\bNo
\bot
\bte
\be:
\b: If you change the colors for your display, for exam-
495 ple by changing the color associated with color2 for your xterm, then that
496 color will be used instead of green.
498 _
\b2_
\b._
\b5_
\b._
\b3 _
\bT_
\bh_
\br_
\be_
\ba_
\bd_
\be_
\bd _
\bM_
\bo_
\bd_
\be
500 When the mailbox is _
\bs_
\bo_
\br_
\bt_
\be_
\bd (section 7.4.296 , page 158) by _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs, there are
501 a few additional functions available in the _
\bi_
\bn_
\bd_
\be_
\bx and _
\bp_
\ba_
\bg_
\be_
\br modes.
503 ^D delete-thread delete all messages in the current thread
504 ^U undelete-thread undelete all messages in the current thread
505 ^N next-thread jump to the start of the next thread
506 ^P previous-thread jump to the start of the previous thread
507 ^R read-thread mark the current thread as read
508 ESC d delete-subthread delete all messages in the current subthread
509 ESC u undelete-subthread undelete all messages in the current subthread
510 ESC n next-subthread jump to the start of the next subthread
511 ESC p previous-subthread jump to the start of the previous subthread
512 ESC r read-subthread mark the current subthread as read
513 ESC t tag-thread toggle the tag on the current thread
514 ESC v collapse-thread toggle collapse for the current thread
515 ESC V collapse-all toggle collapse for all threads
516 P parent-message jump to parent message in thread
518 N
\bNo
\bot
\bte
\be:
\b: Collapsing a thread displays only the first message in the thread and
519 hides the others. This is useful when threads contain so many messages that you
520 can only see a handful of threads on the screen. See %M in _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
521 tion 7.4.114 , page 114). For example, you could use "%?M?(#%03M)&(%4l)?" in
522 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114) to optionally display the number of
523 hidden messages if the thread is collapsed.
525 See also: _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 7.4.317 , page 166).
527 _
\b2_
\b._
\b5_
\b._
\b4 _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\be_
\bo_
\bu_
\bs _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
529 c
\bcr
\bre
\bea
\bat
\bte
\be-
\b-a
\bal
\bli
\bia
\bas
\bs
532 Creates a new alias based upon the current message (or prompts for a new one).
533 Once editing is complete, an _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 24) command is added to
534 the file specified by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 88) variable for
535 future use. N
\bNo
\bot
\bte
\be:
\b: Specifying an _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 88) does not
536 add the aliases specified there-in, you must also _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page
539 c
\bch
\bhe
\bec
\bck
\bk-
\b-t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl-
\b-p
\bpg
\bgp
\bp
542 This function will search the current message for content signed or encrypted
543 with PGP the "traditional" way, that is, without proper MIME tagging.
545 The Mutt Next Generation E-Mail Client 12
547 Technically, this function will temporarily change the MIME content types of
548 the body parts containing PGP data; this is similar to the _
\be_
\bd_
\bi_
\bt_
\b-_
\bt_
\by_
\bp_
\be (section
549 2.5.4 , page 12) function's effect.
551 d
\bdi
\bis
\bsp
\bpl
\bla
\bay
\by-
\b-t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-w
\bwe
\bee
\bed
\bd
554 Toggles the weeding of message header fields specified by _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section
555 3.10 , page 31) commands.
560 This command (available in the ``index'' and ``pager'') allows you to edit the
561 raw current message as it's present in the mail folder. After you have fin-
562 ished editing, the changed message will be appended to the current folder, and
563 the original message will be marked for deletion.
565 e
\bed
\bdi
\bit
\bt-
\b-t
\bty
\byp
\bpe
\be
567 (default: ^E on the attachment menu, and in the pager and index menus; ^T on
570 This command is used to temporarily edit an attachment's content type to fix,
571 for instance, bogus character set parameters. When invoked from the index or
572 from the pager, you'll have the opportunity to edit the top-level attachment's
573 content type. On the _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bm_
\be_
\bn_
\bu (section 5.1.2 , page 69), you can
574 change any attachment's content type. These changes are not persistent, and get
575 lost upon changing folders.
577 Note that this command is also available on the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bm_
\be_
\bn_
\bu (section 5.1.3 ,
578 page 70). There, it's used to fine-tune the properties of attachments you are
581 e
\ben
\bnt
\bte
\ber
\br-
\b-c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
584 This command is used to execute any command you would normally put in a config-
585 uration file. A common use is to check the settings of variables, or in con-
586 junction with _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 28) to change settings on the fly.
588 e
\bex
\bxt
\btr
\bra
\bac
\bct
\bt-
\b-k
\bke
\bey
\bys
\bs
591 This command extracts PGP public keys from the current or tagged message(s) and
592 adds them to your PGP public key ring.
594 f
\bfo
\bor
\brg
\bge
\bet
\bt-
\b-p
\bpa
\bas
\bss
\bsp
\bph
\bhr
\bra
\bas
\bse
\be
597 This command wipes the passphrase(s) from memory. It is useful, if you mis-
598 spelled the passphrase.
600 The Mutt Next Generation E-Mail Client 13
602 l
\bli
\bis
\bst
\bt-
\b-r
\bre
\bep
\bpl
\bly
\by
605 Reply to the current or tagged message(s) by extracting any addresses which
606 match the regular expressions given by the _
\bl_
\bi_
\bs_
\bt_
\bs _
\bo_
\br _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 ,
607 page 34) commands, but also honor any Mail-Followup-To header(s) if the
608 _
\b$_
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.92 , page 109) configuration variable is set.
609 Using this when replying to messages posted to mailing lists helps avoid dupli-
610 cate copies being sent to the author of the message you are replying to.
612 p
\bpi
\bip
\bpe
\be-
\b-m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
615 Asks for an external Unix command and pipes the current or tagged message(s) to
616 it. The variables _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.205 , page 138), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.207 , page 138), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.206 , page 138) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.339 , page 170) control the exact behavior of this
621 r
\bre
\bes
\bse
\ben
\bnd
\bd-
\b-m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
624 With resend-message, mutt takes the current message as a template for a new
625 message. This function is best described as "recall from arbitrary folders".
626 It can conveniently be used to forward MIME messages while preserving the orig-
627 inal mail structure. Note that the amount of headers included here depends on
628 the value of the _
\b$_
\bw_
\be_
\be_
\bd (section 7.4.340 , page 171) variable.
630 This function is also available from the attachment menu. You can use this to
631 easily resend a message which was included with a bounce message as a mes-
632 sage/rfc822 body part.
634 s
\bsh
\bhe
\bel
\bll
\bl-
\b-e
\bes
\bsc
\bca
\bap
\bpe
\be
637 Asks for an external Unix command and executes it. The _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section
638 7.4.339 , page 170) can be used to control whether Mutt-ng will wait for a key
639 to be pressed when the command returns (presumably to let the user read the
640 output of the command), based on the return status of the named command.
642 t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd
645 The _
\bp_
\ba_
\bg_
\be_
\br uses the _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.230 , page 143) variable to
646 detect quoted text when displaying the body of the message. This function tog-
647 gles the display of the quoted material in the message. It is particularly
648 useful when are interested in just the response and there is a large amount of
649 quoted text in the way.
651 s
\bsk
\bki
\bip
\bp-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd
654 This function will go to the next line of non-quoted text which come after a
655 line of quoted text in the internal pager.
657 The Mutt Next Generation E-Mail Client 14
659 _
\b2_
\b._
\b6 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
661 The following bindings are available in the _
\bi_
\bn_
\bd_
\be_
\bx for sending messages.
663 m compose compose a new message
664 r reply reply to sender
665 g group-reply reply to all recipients
666 L list-reply reply to mailing list address
667 f forward forward message
668 b bounce bounce (remail) message
669 ESC k mail-key mail a PGP public key to someone
671 Bouncing a message sends the message as is to the recipient you specify. For-
672 warding a message allows you to add comments or modify the message you are for-
673 warding. These items are discussed in greater detail in the next chapter
674 _
\b`_
\b`_
\bF_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bd _
\bB_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\b'_
\b' (section 2.7 , page 20).
676 _
\b2_
\b._
\b6_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg _
\bn_
\be_
\bw _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
678 When you want to send an email using mutt-ng, simply press m on your keyboard.
679 Then, mutt-ng asks for the recipient via a prompt in the last line:
683 After you've finished entering the recipient(s), press return. If you want to
684 send an email to more than one recipient, separate the email addresses using
685 the comma ",". Mutt-ng then asks you for the email subject. Again, press return
686 after you've entered it. After that, mutt-ng got the most important information
687 from you, and starts up an editor where you can then enter your email.
689 The editor that is called is selected in the following way: you can e.g. set it
690 in the mutt-ng configuration:
692 set editor = "vim +/^$/ -c ':set tw=72'"
696 If you don't set your preferred editor in your configuration, mutt-ng first
697 looks whether the environment variable $VISUAL is set, and if so, it takes its
698 value as editor command. Otherwise, it has a look at $EDITOR and takes its
699 value if it is set. If no editor command can be found, mutt-ng simply assumes
700 vi to be the default editor, since it's the most widespread editor in the Unix
701 world and it's pretty safe to assume that it is installed and available.
703 When you've finished entering your message, save it and quit your editor. Mutt-
704 ng will then present you with a summary screen, the compose menu. On the top,
705 you see a summary of the most important available key commands. Below that,
706 you see the sender, the recipient(s), Cc and/or Bcc recipient(s), the subject,
708 The Mutt Next Generation E-Mail Client 15
710 the reply-to address, and optionally information where the sent email will be
711 stored and whether it should be digitally signed and/or encrypted.
713 Below that, you see a list of "attachments". The mail you've just entered
714 before is also an attachment, but due to its special type (it's plain text), it
715 will be displayed as the normal message on the receiver's side.
717 At this point, you can add more attachments, pressing a, you can edit the
718 recipient addresses, pressing t for the "To:" field, c for the "Cc:" field, and
719 b for the "Bcc: field. You can also edit the subject the subject by simply
720 pressing s or the email message that you've entered before by pressing e. You
721 will then again return to the editor. You can even edit the sender, by pressing
722 <esc>f, but this shall only be used with caution.
724 Alternatively, you can configure mutt-ng in a way that most of the above set-
725 tings can be edited using the editor. Therefore, you only need to add the fol-
726 lowing to your configuration:
730 Once you have finished editing the body of your mail message, you are returned
731 to the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu. The following options are available:
733 a attach-file attach a file
734 A attach-message attach message(s) to the message
735 ESC k attach-key attach a PGP public key
736 d edit-description edit description on attachment
737 D detach-file detach a file
738 t edit-to edit the To field
739 ESC f edit-from edit the From field
740 r edit-reply-to edit the Reply-To field
741 c edit-cc edit the Cc field
742 b edit-bcc edit the Bcc field
743 y send-message send the message
744 s edit-subject edit the Subject
745 S smime-menu select S/MIME options
746 f edit-fcc specify an ``Fcc'' mailbox
747 p pgp-menu select PGP options
748 P postpone-message postpone this message until later
749 q quit quit (abort) sending the message
750 w write-fcc write the message to a folder
751 i ispell check spelling (if available on your system)
752 ^F forget-passphrase wipe passphrase(s) from memory
754 N
\bNo
\bot
\bte
\be:
\b: The attach-message function will prompt you for a folder to attach mes-
755 sages from. You can now tag messages in that folder and they will be attached
756 to the message you are sending. Note that certain operations like composing a
757 new mail, replying, forwarding, etc. are not permitted when you are in that
758 folder. The %r in _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.313 , page 163) will change to a
759 'A' to indicate that you are in attach-message mode.
761 The Mutt Next Generation E-Mail Client 16
763 _
\b2_
\b._
\b6_
\b._
\b2 _
\bR_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg
765 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b1 _
\bS_
\bi_
\bm_
\bp_
\bl_
\be _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
767 When you want to reply to an email message, select it in the index menu and
768 then press r. Mutt-ng's behaviour is then similar to the behaviour when you
769 compose a message: first, you will be asked for the recipient, then for the
770 subject, and then, mutt-ng will start the editor with the quote attribution and
771 the quoted message. This can e.g. look like the example below.
773 On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote:
774 > Bill, can you please send last month's progress report to Mr.
775 > Morgan? We also urgently need the cost estimation for the new
776 > production server that we want to set up before our customer's
777 > project will go live.
779 You can start editing the email message. It is strongly recommended to put your
780 answer _
\bb_
\be_
\bl_
\bo_
\bw the quoted text and to only quote what is really necessary and
781 that you refer to. Putting your answer on top of the quoted message, is,
782 although very widespread, very often not considered to be a polite way to
785 The quote attribution is configurable, by default it is set to
787 set attribution = "On %d, %n wrote:"
789 It can also be set to something more compact, e.g.
791 set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
793 The example above results in the following attribution:
795 * Michael Svensson <svensson@foobar.com> [05-03-06 17:02]:
796 > Bill, can you please send last month's progress report to Mr.
797 > Morgan? We also urgently need the cost estimation for the new
798 > production server that we want to set up before our customer's
799 > project will go live.
801 Generally, try to keep your attribution short yet information-rich. It is _
\bn_
\bo_
\bt
802 the right place for witty quotes, long "attribution" novels or anything like
803 that: the right place for such things is - if at all - the email signature at
804 the very bottom of the message.
806 When you're done with writing your message, save and quit the editor. As
807 before, you will return to the compose menu, which is used in the same way as
809 The Mutt Next Generation E-Mail Client 17
813 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b2 _
\bG_
\br_
\bo_
\bu_
\bp _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
815 In the situation where a group of people uses email as a discussion, most of
816 the emails will have one or more recipients, and probably several "Cc:" recipi-
817 ents. The group reply functionality ensures that when you press g instead of r
818 to do a reply, each and every recipient that is contained in the original mes-
819 sage will receive a copy of the message, either as normal recipient or as "Cc:"
822 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b3 _
\bL_
\bi_
\bs_
\bt _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
824 When you use mailing lists, it's generally better to send your reply to a mes-
825 sage only to the list instead of the list and the original author. To make this
826 easy to use, mutt-ng features list replies.
828 To do a list reply, simply press L. If the email contains a Mail-Followup-To:
829 header, its value will be used as reply address. Otherwise, mutt-ng searches
830 through all mail addresses in the original message and tries to match them a
831 list of regular expressions which can be specified using the lists command. If
832 any of the regular expression matches, a mailing list address has been found,
833 and it will be used as reply address.
835 lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
837 Nowadays, most mailing list software like GNU Mailman adds a Mail-Followup-To:
838 header to their emails anyway, so setting lists is hardly ever necessary in
841 _
\b2_
\b._
\b6_
\b._
\b3 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br
843 When editing the header of your outgoing message, there are a couple of special
848 Fcc: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
850 Mutt-ng will pick up _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be just as if you had used the _
\be_
\bd_
\bi_
\bt_
\b-_
\bf_
\bc_
\bc function in
851 the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu.
853 You can also attach files to your message by specifying
855 The Mutt Next Generation E-Mail Client 18
857 Attach: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
859 where _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is the file to attach and _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn is an optional string to
860 use as the description of the attached file.
862 When replying to messages, if you remove the _
\bI_
\bn_
\b-_
\bR_
\be_
\bp_
\bl_
\by_
\b-_
\bT_
\bo_
\b: field from the header
863 field, Mutt-ng will not generate a _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be_
\bs_
\b: field, which allows you to cre-
864 ate a new message thread.
866 Also see _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101).
868 _
\b2_
\b._
\b6_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bw_
\bi_
\bt_
\bh _
\bP_
\bG_
\bP
870 If you want to use PGP, you can specify
872 Pgp: [ E | S | S_
\b<_
\bi_
\bd_
\b> ]
874 ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
875 _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.197 , page 136) permanently.
877 If you have told mutt to PGP encrypt a message, it will guide you through a key
878 selection process when you try to send the message. Mutt-ng will not ask you
879 any questions about keys which have a certified user ID matching one of the
880 message recipients' mail addresses. However, there may be situations in which
881 there are several keys, weakly certified user ID fields, or where no matching
884 In these cases, you are dropped into a menu with a list of keys from which you
885 can select one. When you quit this menu, or mutt can't find any matching keys,
886 you are prompted for a user ID. You can, as usually, abort this prompt using
887 ^G. When you do so, mutt will return to the compose screen.
889 Once you have successfully finished the key selection, the message will be
890 encrypted using the selected public keys, and sent out.
892 Most fields of the entries in the key selection menu (see also _
\b$_
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\b-
893 _
\bm_
\ba_
\bt (section 7.4.184 , page 133)) have obvious meanings. But some explana-
894 tions on the capabilities, flags, and validity fields are in order.
896 The flags sequence (%f) will expand to one of the following flags:
898 R The key has been revoked and can't be used.
899 X The key is expired and can't be used.
900 d You have marked the key as disabled.
901 c There are unknown critical self-signature
904 The capabilities field (%c) expands to a two-character sequence representing a
905 key's capabilities. The first character gives the key's encryption capabili-
906 ties: A minus sign (-
\b-) means that the key cannot be used for encryption. A dot
907 (.
\b.) means that it's marked as a signature key in one of the user IDs, but may
909 The Mutt Next Generation E-Mail Client 19
911 also be used for encryption. The letter e
\be indicates that this key can be used
914 The second character indicates the key's signing capabilities. Once again, a
915 ``-
\b-'' implies ``not for signing'', ``.
\b.'' implies that the key is marked as an
916 encryption key in one of the user-ids, and ``s
\bs'' denotes a key which can be
919 Finally, the validity field (%t) indicates how well-certified a user-id is. A
920 question mark (?
\b?) indicates undefined validity, a minus character (-
\b-) marks an
921 untrusted association, a space character means a partially trusted association,
922 and a plus character (+
\b+) indicates complete validity.
924 _
\b2_
\b._
\b6_
\b._
\b5 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bo_
\bn_
\by_
\bm_
\bo_
\bu_
\bs _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs _
\bv_
\bi_
\ba _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
926 You may also have configured mutt to co-operate with Mixmaster, an anonymous
927 remailer. Mixmaster permits you to send your messages anonymously using a
928 chain of remailers. Mixmaster support in mutt is for mixmaster version 2.04
929 (beta 45 appears to be the latest) and 2.03. It does not support earlier ver-
930 sions or the later so-called version 3 betas, of which the latest appears to be
933 To use it, you'll have to obey certain restrictions. Most important, you can-
934 not use the Cc and Bcc headers. To tell Mutt-ng to use mixmaster, you have to
935 select a remailer chain, using the mix function on the compose menu.
937 The chain selection screen is divided into two parts. In the (larger) upper
938 part, you get a list of remailers you may use. In the lower part, you see the
939 currently selected chain of remailers.
941 You can navigate in the chain using the chain-prev and chain-next functions,
942 which are by default bound to the left and right arrows and to the h and l keys
943 (think vi keyboard bindings). To insert a remailer at the current chain posi-
944 tion, use the insert function. To append a remailer behind the current chain
945 position, use select-entry or append. You can also delete entries from the
946 chain, using the corresponding function. Finally, to abandon your changes,
947 leave the menu, or accept them pressing (by default) the Return key.
949 Note that different remailers do have different capabilities, indicated in the
950 %c entry of the remailer menu lines (see _
\b$_
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.144 ,
951 page 122)). Most important is the ``middleman'' capability, indicated by a
952 capital ``M'': This means that the remailer in question cannot be used as the
953 final element of a chain, but will only forward messages to other mixmaster
954 remailers. For details on the other capabilities, please have a look at the
955 mixmaster documentation.
957 _
\b2_
\b._
\b7 _
\bF_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bd _
\bB_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
959 The Mutt Next Generation E-Mail Client 20
961 Often, it is necessary to forward mails to other people. Therefore, mutt-ng
962 supports forwarding messages in two different ways.
964 The first one is regular forwarding, as you probably know it from other mail
965 clients. You simply press f, enter the recipient email address, the subject of
966 the forwarded email, and then you can edit the message to be forwarded in the
967 editor. The forwarded message is separated from the rest of the message via the
968 two following markers:
970 ----- Forwarded message from Lucas User <luser@example.com> -----
972 From: Lucas User <luser@example.com>
973 Date: Thu, 02 Dec 2004 03:08:34 +0100
974 To: Michael Random <mrandom@example.com>
975 Subject: Re: blackmail
977 Pay me EUR 50,000.- cash or your favorite stuffed animal will die
980 ----- End forwarded message -----
982 When you're done with editing the mail, save and quit the editor, and you will
983 return to the compose menu, the same menu you also encounter when composing or
986 The second mode of forwarding emails with mutt-ng is the so-called _
\bb_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg:
987 when you bounce an email to another address, it will be sent in practically the
988 same format you send it (except for headers that are created during transport-
989 ing the message). To bounce a message, press b and enter the recipient email
990 address. By default, you are then asked whether you really want to bounce the
991 message to the specified recipient. If you answer with yes, the message will
994 To the recipient, the bounced email will look as if he got it like a regular
995 email where he was Bcc: recipient. The only possibility to find out whether it
996 was a bounced email is to carefully study the email headers and to find out
997 which host really sent the email.
999 _
\b2_
\b._
\b8 _
\bP_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
1001 At times it is desirable to delay sending a message that you have already begun
1002 to compose. When the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be function is used in the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu,
1003 the body of your message and attachments are stored in the mailbox specified by
1004 the _
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.219 , page 141) variable. This means that you can
1005 recall the message even if you exit Mutt-ng and then restart it at a later
1008 Once a message is postponed, there are several ways to resume it. From the
1009 command line you can use the ``-p'' option, or if you _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be a new message
1011 The Mutt Next Generation E-Mail Client 21
1013 from the _
\bi_
\bn_
\bd_
\be_
\bx or _
\bp_
\ba_
\bg_
\be_
\br you will be prompted if postponed messages exist. If
1014 multiple messages are currently postponed, the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd menu will pop up and
1015 you can select which message you would like to resume.
1017 N
\bNo
\bot
\bte
\be:
\b: If you postpone a reply to a message, the reply setting of the message is
1018 only updated when you actually finish the message and send it. Also, you must
1019 be in the same folder with the message you replied to for the status of the
1020 message to be updated.
1022 See also the _
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.218 , page 141) quad-option.
1024 _
\b3_
\b. _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
1026 _
\b3_
\b._
\b1 _
\bL_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs _
\bo_
\bf _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1028 While the default configuration (or ``preferences'') make Mutt-ng usable right
1029 out of the box, it is often desirable to tailor Mutt-ng to suit your own
1030 tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
1031 configuration file (defaults set by your local system administrator), unless
1032 the ``-n'' _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be (section 7.1 , page 81) option is specified. This
1033 file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
1034 users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
1035 Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
1036 will look for .muttngrc. If this file does not exist and your home directory
1037 has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
1039 .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
1040 your _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page 84) to configure Mutt-ng.
1042 _
\b3_
\b._
\b2 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bS_
\by_
\bn_
\bt_
\ba_
\bx _
\bo_
\bf _
\bI_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1044 An initialization file consists of a series of _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page
1045 84). Each line of the file may contain one or more commands. When multiple
1046 commands are used, they must be separated by a semicolon (;).
1048 set realname='Mutt-ng user' ; ignore x-
1050 The hash mark, or pound sign (``#''), is used as a ``comment'' character. You
1051 can use it to annotate your initialization file. All text after the comment
1052 character to the end of the line is ignored. For example,
1054 my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
1056 Single quotes (') and double quotes (') can be used to quote strings which
1058 The Mutt Next Generation E-Mail Client 22
1060 contain spaces or other special characters. The difference between the two
1061 types of quotes is similar to that of many popular shell programs, namely that
1062 a single quote is used to specify a literal string (one that is not interpreted
1063 for shell variables or quoting with a backslash [see next paragraph]), while
1064 double quotes indicate a string for which should be evaluated. For example,
1065 backtics are evaluated inside of double quotes, but n
\bno
\bot
\bt for single quotes.
1067 \ quotes the next character, just as in shells such as bash and zsh. For exam-
1068 ple, if want to put quotes ``''' inside of a string, you can use ``\'' to force
1069 the next character to be a literal instead of interpreted character.
1071 set realname="Michael \"MuttDude\" Elkins"
1073 ``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r'' have
1074 their usual C meanings of linefeed and carriage-return, respectively.
1076 A \ at the end of a line can be used to split commands over multiple lines,
1077 provided that the split points don't appear in the middle of command names.
1079 Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the
1080 end of a line also in comments. This allows you to disable a command split over
1081 multiple lines with only one ``#''.
1084 set realname="Michael \"MuttDude\" Elkins"
1086 When testing your config files, beware the following caveat. The backslash at
1087 the end of the commented line extends the current line with the next line -
1088 then referred to as a ``continuation line''. As the first line is commented
1089 with a hash (#) all following continuation lines are also part of a comment and
1090 therefore are ignored, too. So take care of comments when continuation lines
1091 are involved within your setup files!
1101 line1 ``continues'' until line4. however, the part after the # is a comment
1102 which includes line3 and line4. line5 is a new line of its own and thus is
1105 The commands understood by mutt are explained in the next paragraphs. For a
1106 complete list, see the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.3 , page 84).
1108 The Mutt Next Generation E-Mail Client 23
1110 _
\b3_
\b._
\b3 _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
1112 _
\b3_
\b._
\b3_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs_
\b' _
\bO_
\bu_
\bt_
\bp_
\bu_
\bt
1114 It is possible to substitute the output of a Unix command in an initialization
1115 file. This is accomplished by enclosing the command in backquotes (``) as in,
1118 my_hdr X-Operating-System: `uname -a`
1120 The output of the Unix command ``uname -a'' will be substituted before the line
1121 is parsed. Note that since initialization files are line oriented, only the
1122 first line of output from the Unix command will be substituted.
1124 _
\b3_
\b._
\b3_
\b._
\b2 _
\bE_
\bn_
\bv_
\bi_
\br_
\bo_
\bn_
\bm_
\be_
\bn_
\bt _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1126 UNIX environments can be accessed like the way it is done in shells like sh and
1127 bash: Prepend the name of the environment by a ``$'' sign. For example,
1129 set record=+sent_on_$HOSTNAME
1131 sets the _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.235 , page 144) variable to the string _
\b+_
\bs_
\be_
\bn_
\bt_
\b__
\bo_
\bn_
\b_
1132 and appends the value of the evironment variable $HOSTNAME.
1134 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if an environment variable is not defined. The
1135 result will of the expansion will then be empty.
1137 _
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1139 As for environment variables, the values of all configuration variables as
1140 string can be used in the same way, too. For example,
1142 set imap_home_namespace = $folder
1144 would set the value of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.99 , page 110) to the
1145 value to which _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.68 , page 103) is _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by set to.
1147 N
\bNo
\bot
\bte
\be:
\b: There're no logical links established in such cases so that the the value
1148 for _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.99 , page 110) won't change even if
1149 _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.68 , page 103) gets changed.
1151 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if a configuration variable is not defined or is
1152 empty. The result will of the expansion will then be empty.
1154 _
\b3_
\b._
\b3_
\b._
\b4 _
\bS_
\be_
\bl_
\bf_
\b-_
\bD_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1156 Mutt-ng flexibly allows users to define their own variables. To avoid conflicts
1157 with the standard set and to prevent misleading error messages, there's a
1159 The Mutt Next Generation E-Mail Client 24
1161 reserved namespace for them. All user-defined variables must be prefixed with
1162 user_ and can be used just like any ordinary configuration or environment vari-
1165 For example, to view the manual, users can either define three macros like the
1168 macro generic <F1> "!less -r /path/to/manual" "Show manual"
1169 macro pager <F1> "!less -r /path/to/manual" "Show manual"
1170 macro index <F1> "!less -r /path/to/manual" "Show manual"
1172 for generic, pager and index. The alternative is to define a custom variable
1175 set user_manualcmd = '!less -r /path/to_manual"
1176 macro generic <F1> "$user_manualcmd<enter>" "Show manual"
1177 macro pager <F1> "$user_manualcmd<enter>" "Show manual"
1178 macro index <F1> "$user_manualcmd<enter>" "Show manual"
1180 Using this feature, arbitrary sequences can be defined once and recalled and
1181 reused where necessary. More advanced scenarios could include to save a vari-
1182 able's value at the beginning of macro sequence and restore it at end.
1184 _
\b3_
\b._
\b3_
\b._
\b5 _
\bT_
\by_
\bp_
\be _
\bC_
\bo_
\bn_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn_
\bs
1186 A note about variable's types during conversion: internally values are stored
1187 in internal types but for any dump/query or set operation they're converted to
1188 and from string. That means that there's no need to worry about types when ref-
1189 erencing any variable. As an example, the following can be used without harm
1190 (besides makeing muttng very likely behave strange):
1193 set folder = $read_inc
1194 set $read_inc = $folder
1195 set user_magic_number = 42
1196 set folder = $user_magic_number
1198 _
\b3_
\b._
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1200 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1202 It's usually very cumbersome to remember or type out the address of someone you
1203 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1204 short string to a full address.
1206 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1207 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1209 The Mutt Next Generation E-Mail Client 25
1211 To remove an alias or aliases (``*'' means all aliases):
1213 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1215 alias muttdude me@cs.hmc.edu (Michael Elkins)
1216 alias theguys manny, moe, jack
1218 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1219 cial file. The alias command can appear anywhere in a configuration file, as
1220 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.29 , page 44). Consequently, you can
1221 have multiple alias files, or you can have all aliases defined in your muttrc.
1223 On the other hand, the _
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (section 2.5.4 , page 11) function can use
1224 only one file, the one pointed to by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 88)
1225 variable (which is ~/.muttrc by default). This file is not special either, in
1226 the sense that Mutt-ng will happily append aliases to any file, but in order
1227 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1228 3.29 , page 44) this file too.
1232 source /usr/local/share/Mutt-ng.aliases
1233 source ~/.mail_aliases
1234 set alias_file=~/.mail_aliases
1236 To use aliases, you merely use the alias at any place in mutt where mutt
1237 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1238 aliases in your editor at the appropriate headers if you have the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1239 (section 7.4.58 , page 101) variable set.
1241 In addition, at the various address prompts, you can use the tab character to
1242 expand a partial alias to the full alias. If there are multiple matches, mutt
1243 will bring up a menu with the matching aliases. In order to be presented with
1244 the full list of aliases, you must hit tab with out a partial alias, such as at
1245 the beginning of the prompt or after a comma denoting multiple addresses.
1247 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1248 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1251 _
\b3_
\b._
\b5 _
\bC_
\bh_
\ba_
\bn_
\bg_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs
1253 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1255 This command allows you to change the default key bindings (operation invoked
1256 when pressing a key).
1258 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be
1260 The Mutt Next Generation E-Mail Client 26
1262 specified by separating them with commas (no additional whitespace is allowed).
1263 The currently defined maps are:
1266 This is not a real menu, but is used as a fallback for all of the
1267 other menus except for the pager and editor modes. If a key is not
1268 defined in another menu, Mutt-ng will look for a binding to use in
1269 this menu. This allows you to bind a key to a certain function in
1270 multiple menus instead of having multiple bind statements to accom-
1271 plish the same task.
1274 The alias menu is the list of your personal aliases as defined in
1275 your muttrc. It is the mapping from a short alias name to the full
1276 email address(es) of the recipient(s).
1279 The attachment menu is used to access the attachments on received
1283 The browser is used for both browsing the local directory struc-
1284 ture, and for listing all of your incoming mailboxes.
1287 The editor is the line-based editor the user enters text data.
1290 The index is the list of messages contained in a mailbox.
1293 The compose menu is the screen used when sending a new message.
1296 The pager is the mode used to display message/attachment data, and
1300 The pgp menu is used to select the OpenPGP keys used for encrypting
1304 The postpone menu is similar to the index menu, except is used when
1305 recalling a message the user was composing, but saved until later.
1307 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1308 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1309 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1310 well as _
\b\_
\bC is ignored, so that _
\b\_
\bC_
\bA, _
\b\_
\bC_
\ba, _
\b\_
\bc_
\bA and _
\b\_
\bc_
\ba are all equivalent. An
1311 alternative form is to specify the key as a three digit octal number prefixed
1312 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1314 The Mutt Next Generation E-Mail Client 27
1316 In addition, _
\bk_
\be_
\by may consist of:
1320 <backtab> backtab / shift-tab
1330 <pagedown> Page Down
1331 <backspace> Backspace
1340 <f10> function key 10
1342 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1344 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1345 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 172). The special
1346 function noop unbinds the specified key sequence.
1348 _
\b3_
\b._
\b6 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs _
\bf_
\bo_
\br _
\bc_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bs_
\be_
\bt_
\bs
1350 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1352 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1354 The charset-hook command defines an alias for a character set. This is useful
1355 to properly display messages which are tagged with a character set name not
1358 The iconv-hook command defines a system-specific name for a character set.
1359 This is helpful when your systems character conversion library insists on using
1360 strange, system-specific names for character sets.
1362 _
\b3_
\b._
\b7 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1364 The Mutt Next Generation E-Mail Client 28
1366 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1368 It is often desirable to change settings based on which mailbox you are read-
1369 ing. The folder-hook command provides a method by which you can execute any
1370 configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1371 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1372 folder-hook's, they are executed in the order given in the muttrc.
1374 N
\bNo
\bot
\bte
\be:
\b: if you use the ``!'' shortcut for _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.302 , page
1375 160) at the beginning of the pattern, you must place it inside of double or
1376 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1379 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1380 ple, a command action to perform is to change the sorting method based upon the
1383 folder-hook mutt set sort=threads
1385 However, the sorting method is not restored to its previous value when reading
1386 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1388 folder-hook . set sort=date-sent
1390 _
\b3_
\b._
\b8 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1392 Usage: macro _
\bm_
\be_
\bn_
\bu _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
1394 Macros are useful when you would like a single key to perform a series of
1395 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1396 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1397 create a macro to execute those commands with a single key.
1399 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.5 , page 26) which the macro will be bound. Multi-
1400 ple maps may be specified by separating multiple menu arguments by commas.
1401 Whitespace may not be used in between the menu arguments and the commas sepa-
1404 _
\bk_
\be_
\by and _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be are expanded by the same rules as the _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs (section
1405 3.5 , page 25). There are some additions however. The first is that control
1406 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1407 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1408 invoke a function directly, you can use the format _
\b<_
\bk_
\be_
\by _
\bn_
\ba_
\bm_
\be_
\b> and _
\b<_
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1409 _
\bn_
\ba_
\bm_
\be_
\b>. For a listing of key names see the section on _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs (section
1410 3.5 , page 25). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1413 The advantage with using function names directly is that the macros will work
1415 The Mutt Next Generation E-Mail Client 29
1417 regardless of the current key bindings, so they are not dependent on the user
1418 having particular key definitions. This makes them more robust and portable,
1419 and also facilitates defining of macros in files used by more than one user
1420 (eg. the system Muttngrc).
1422 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1425 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1426 truncated at the screen width, and are not wrapped.
1428 _
\b3_
\b._
\b9 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bc_
\bo_
\bl_
\bo_
\br _
\ba_
\bn_
\bd _
\bm_
\bo_
\bn_
\bo _
\bv_
\bi_
\bd_
\be_
\bo _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be_
\bs
1430 Usage: color _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
1432 Usage: color index _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1434 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1436 If your terminal supports color, you can spice up Mutt-ng by creating your own
1437 color scheme. To define the color of an object (type of information), you must
1438 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1439 only specify one or the other).
1441 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1445 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1447 +
\bo bold (highlighting bold patterns in the body of messages)
1449 +
\bo error (error messages printed by Mutt-ng)
1451 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1453 +
\bo hdrdefault (default color of the message header in the pager)
1455 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1457 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1459 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1461 +
\bo message (informational messages)
1465 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.230 , page 143) in the
1468 The Mutt Next Generation E-Mail Client 30
1470 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1472 +
\bo search (highlighting of words in the pager)
1476 +
\bo status (mode lines used to display info about the mailbox or message)
1478 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1480 +
\bo tree (thread tree drawn in the message index and attachment menu)
1482 +
\bo underline (highlighting underlined patterns in the body of messages)
1484 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd and _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can be one of the following:
1506 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the fore-
1507 ground color boldfaced (e.g., brightred).
1509 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1510 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1511 linked against the _
\bS_
\b-_
\bL_
\ba_
\bn_
\bg library, you also need to set the _
\bC_
\bO_
\bL_
\bO_
\bR_
\bF_
\bG_
\bB_
\bG environ-
1512 ment variable to the default colors of your terminal for this to work; for
1513 example (for Bourne-like shells):
1515 set COLORFGBG="green;black"
1518 N
\bNo
\bot
\bte
\be:
\b: The _
\bS_
\b-_
\bL_
\ba_
\bn_
\bg library requires you to use the _
\bl_
\bi_
\bg_
\bh_
\bt_
\bg_
\br_
\ba_
\by and _
\bb_
\br_
\bo_
\bw_
\bn keywords
1519 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1521 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1523 The Mutt Next Generation E-Mail Client 31
1525 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1526 command for it to be removed. The pattern ``*'' is a special token which means
1527 to clear the color index list of all entries.
1529 Mutt-ng also recognizes the keywords _
\bc_
\bo_
\bl_
\bo_
\br_
\b0, _
\bc_
\bo_
\bl_
\bo_
\br_
\b1, ..., _
\bc_
\bo_
\bl_
\bo_
\brN
\bN-
\b-1
\b1 (N
\bN being the
1530 number of colors supported by your terminal). This is useful when you remap
1531 the colors for your display (for example by changing the color associated with
1532 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1534 If your terminal does not support color, it is still possible change the video
1535 attributes through the use of the ``mono'' command:
1537 Usage: mono _
\b<_
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b> _
\b<_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be_
\b> [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
1539 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1541 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1543 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1555 _
\b3_
\b._
\b1_
\b0 _
\bI_
\bg_
\bn_
\bo_
\br_
\bi_
\bn_
\bg _
\b(_
\bw_
\be_
\be_
\bd_
\bi_
\bn_
\bg_
\b) _
\bu_
\bn_
\bw_
\ba_
\bn_
\bt_
\be_
\bd _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1557 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1559 Messages often have many header fields added by automatic processing systems,
1560 or which may not seem useful to display on the screen. This command allows you
1561 to specify header fields which you don't normally want to see.
1563 You do not need to specify the full header field name. For example, ``ignore
1564 content-'' will ignore all header fields that begin with the pattern ``con-
1565 tent-''. ``ignore *'' will ignore all headers.
1567 To remove a previously added token from the list, use the ``unignore'' command.
1568 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1569 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1572 ``unignore *'' will remove all tokens from the ignore list.
1576 The Mutt Next Generation E-Mail Client 32
1578 # Sven's draconian header weeding
1580 unignore from date subject to cc
1581 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1584 _
\b3_
\b._
\b1_
\b1 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1586 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1588 With various functions, mutt will treat messages differently, depending on
1589 whether you sent them or whether you received them from someone else. For
1590 instance, when replying to a message that you sent to a different party, mutt
1591 will automatically suggest to send the response to the original message's
1592 recipients -- responding to yourself won't make much sense in many cases. (See
1593 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.238 , page 145).)
1595 Many users receive e-mail under a number of different addresses. To fully use
1596 mutt's features here, the program must be able to recognize what e-mail
1597 addresses you receive mail under. That's the purpose of the alternates command:
1598 It takes a list of regular expressions, each of which can identify an address
1599 under which you receive e-mail.
1601 The unalternates command can be used to write exceptions to alternates pat-
1602 terns. If an address matches something in an alternates command, but you none-
1603 theless do not think it is from you, you can list a more precise pattern under
1604 an unalternates command.
1606 To remove a regular expression from the alternates list, use the unalternates
1607 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1608 command matches an entry on the unalternates list, that unalternates entry will
1609 be removed. If the _
\br_
\be_
\bg_
\be_
\bx_
\bp for unalternates is ``*'', _
\ba_
\bl_
\bl _
\be_
\bn_
\bt_
\br_
\bi_
\be_
\bs on alternates
1612 _
\b3_
\b._
\b1_
\b2 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1614 _
\b3_
\b._
\b1_
\b2_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
1616 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1617 ning of email, each message had a fixed line width, and it was enough for dis-
1618 playing them on fixed-size terminals. But times changed, and nowadays hardly
1619 anybody still uses fixed-size terminals: more people nowaydays use graphical
1620 user interfaces, with dynamically resizable windows. This led to the demand of
1621 a new email format that makes it possible for the email client to make the
1622 email look nice in a resizable window without breaking quoting levels and cre-
1623 ating an incompatible email format that can also be displayed nicely on old
1624 fixed-size terminals.
1626 For introductory information on format=flowed messages, see
1628 The Mutt Next Generation E-Mail Client 33
1630 <http://www.joeclark.org/ffaq.html>.
1632 _
\b3_
\b._
\b1_
\b2_
\b._
\b2 _
\bR_
\be_
\bc_
\be_
\bi_
\bv_
\bi_
\bn_
\bg_
\b: _
\bD_
\bi_
\bs_
\bp_
\bl_
\ba_
\by _
\bS_
\be_
\bt_
\bu_
\bp
1634 When you receive emails that are marked as format=flowed messages, and is for-
1635 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1636 your terminal. If you want a fixed margin on the right side of your terminal,
1637 you can set the following:
1641 The code above makes the line break 10 columns before the right side of the
1644 If your terminal is so wide that the lines are embarrassingly long, you can
1645 also set a maximum line length:
1647 set max_line_length = 120
1649 The example above will give you lines not longer than 120 characters.
1651 When you view at format=flowed messages, you will often see the quoting hierar-
1652 chy like in the following example:
1654 >Bill, can you please send last month's progress report to Mr.
1655 >Morgan? We also urgently need the cost estimation for the new
1656 >production server that we want to set up before our customer's
1657 >project will go live.
1659 This obviously doesn't look very nice, and it makes it very hard to differenti-
1660 ate between text and quoting character. The solution is to configure mutt-ng to
1661 "stuff" the quoting:
1665 This will lead to a nicer result that is easier to read:
1667 > Bill, can you please send last month's progress report to Mr.
1668 > Morgan? We also urgently need the cost estimation for the new
1669 > production server that we want to set up before our customer's
1670 > project will go live.
1672 The Mutt Next Generation E-Mail Client 34
1674 _
\b3_
\b._
\b1_
\b2_
\b._
\b3 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg
1676 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1681 Additionally, you have to use an editor which supports writing format=flowed-
1682 conforming emails. For vim, this is done by adding w to the formatoptions (see
1683 :h formatoptions and :h fo-table) when writing emails.
1685 Also note that _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\b=_
\bf_
\bl_
\bo_
\bw_
\be_
\bd knows about ``space-stuffing'', that is, when
1686 sending messages, some kinds of lines have to be indented with a single space
1687 on the sending side. On the receiving side, the first space (if any) is
1688 removed. As a consequence and in addition to the above simple setting, please
1689 keep this in mind when making manual formattings within the editor. Also note
1690 that mutt-ng currently violates the standard (RfC 3676) as it does not space-
1691 stuff lines starting with:
1693 +
\bo > This is _
\bn_
\bo_
\bt the quote character but a right angle used for other reasons
1695 +
\bo From with a trailing space.
1697 +
\bo just a space for formatting reasons
1699 Please make sure that you manually prepend a space to each of them.
1701 _
\b3_
\b._
\b1_
\b2_
\b._
\b4 _
\bA_
\bd_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bN_
\bo_
\bt_
\be_
\bs
1705 For completeness, the _
\b$_
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.50 , page 99) variable pro-
1706 vides the mechanism to generate a DelSp=yes parameter on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages.
1707 According to the standard, clients receiving a format=flowed messages should
1708 delete the last space of a flowed line but still interpret the line as flowed.
1709 Because flowed lines usually contain only one space at the end, this parameter
1710 would make the receiving client concatenate the last word of the previous with
1711 the first of the current line _
\bw_
\bi_
\bt_
\bh_
\bo_
\bu_
\bt a space. This makes ordinary text unread-
1712 able and is intended for languages rarely using spaces. So please use this set-
1713 ting only if you're sure what you're doing.
1715 _
\b3_
\b._
\b1_
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1717 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1719 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1721 Mutt-ng has a few nice features for _
\bh_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bm_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs (section 4.10 ,
1722 page 59). In order to take advantage of them, you must specify which addresses
1724 The Mutt Next Generation E-Mail Client 35
1726 belong to mailing lists, and which mailing lists you are subscribed to. Once
1727 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1728 work for all known lists. Additionally, when you send a message to a sub-
1729 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1730 user agents not to send copies of replies to your personal address. Note that
1731 the Mail-Followup-To header is a non-standard extension which is not supported
1732 by all mail user agents. Adding it is not bullet-proof against receiving per-
1733 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1734 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.70 , page 104)
1735 configuration variable.
1737 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1738 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1739 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1742 You can use regular expressions with both commands. To mark all messages sent
1743 to a specific bug report's address on mutt's bug tracking system as list mail,
1744 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1745 sufficient to just give a portion of the list's e-mail address.
1747 Specify as much of the address as you need to to remove ambiguity. For exam-
1748 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1749 addressed to _
\bm_
\bu_
\bt_
\bt_
\b-_
\bu_
\bs_
\be_
\br_
\bs_
\b@_
\bm_
\bu_
\bt_
\bt_
\b._
\bo_
\br_
\bg. So, to tell Mutt-ng that this is a mailing
1750 list, you could add ``lists mutt-users'' to your initialization file. To tell
1751 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1752 tialization file instead. If you also happen to get mail from someone whose
1753 address is _
\bm_
\bu_
\bt_
\bt_
\b-_
\bu_
\bs_
\be_
\br_
\bs_
\b@_
\be_
\bx_
\ba_
\bm_
\bp_
\bl_
\be_
\b._
\bc_
\bo_
\bm, you could use ``lists mutt-
1754 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1755 from the actual list.
1757 The ``unlists'' command is used to remove a token from the list of known and
1758 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1760 To remove a mailing list from the list of subscribed mailing lists, but keep it
1761 on the list of known mailing lists, use ``unsubscribe''.
1763 _
\b3_
\b._
\b1_
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bl_
\bt_
\bi_
\bp_
\bl_
\be _
\bs_
\bp_
\bo_
\bo_
\bl _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs
1765 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1767 This command is used to move read messages from a specified mailbox to a dif-
1768 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1769 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1770 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1772 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1773 (it is not possible to save read mail in more than a single mailbox).
1775 The Mutt Next Generation E-Mail Client 36
1777 _
\b3_
\b._
\b1_
\b5 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs _
\bw_
\bh_
\bi_
\bc_
\bh _
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be _
\bm_
\ba_
\bi_
\bl
1779 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1781 This command specifies folders which can receive mail and which will be checked
1782 for new messages. By default, the main menu status bar displays how many of
1783 these folders have new messages.
1785 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1787 Pressing TAB in the directory browser will bring up a menu showing the files
1788 specified by the mailboxes command, and indicate which contain new messages.
1789 Mutt-ng will automatically enter this mode when invoked from the command line
1792 The ``unmailboxes'' command is used to remove a token from the list of folders
1793 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1795 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1796 access time. Utilities like biff or frm or any other program which accesses
1797 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1798 they do not properly reset the access time. Backup tools are another common
1799 reason for updated access times.
1801 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1802 executed, so if these names contain _
\bs_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt _
\bc_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br_
\bs (section 4.9 , page
1803 59) (such as ``='' and ``!''), any variable definition that affect these char-
1804 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.68 , page 103) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1805 7.4.302 , page 160)) should be executed before the mailboxes command.
1807 _
\b3_
\b._
\b1_
\b6 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1811 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1813 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1815 The ``my_hdr'' command allows you to create your own header fields which will
1816 be added to every message you send.
1818 For example, if you would like to add an ``Organization:'' header field to all
1819 of your outgoing messages, you can put the command
1821 my_hdr Organization: A Really Big Company, Anytown, USA
1825 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1826 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1828 The Mutt Next Generation E-Mail Client 37
1830 there, so Mutt-ng enforces the rule.
1832 If you would like to add a header field to a single message, you should either
1833 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1834 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1835 header of your message along with the body.
1837 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1838 specify an asterisk (``*'') to remove all header fields, or the fields to
1839 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1844 _
\b3_
\b._
\b1_
\b7 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bo_
\br_
\bd_
\be_
\br _
\bo_
\bf _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs _
\bw_
\bh_
\be_
\bn _
\bv_
\bi_
\be_
\bw_
\bi_
\bn_
\bg _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
1846 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1848 With this command, you can specify an order in which mutt will attempt to
1849 present headers to you when viewing messages.
1851 ``unhdr_order *'' will clear all previous headers from the order list, thus
1852 removing the header order effects set by the system-wide startup file.
1854 hdr_order From Date: From: To: Cc: Subject:
1856 _
\b3_
\b._
\b1_
\b8 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1858 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1860 This command is used to override the default filename used when saving mes-
1861 sages. _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be will be used as the default filename if the message is _
\bF_
\br_
\bo_
\bm_
\b:
1862 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1863 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1865 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 56) for information on the
1866 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1870 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1871 save-hook aol\\.com$ +spam
1873 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 38) command.
1875 The Mutt Next Generation E-Mail Client 38
1877 _
\b3_
\b._
\b1_
\b9 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bw_
\bh_
\be_
\bn _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg
1879 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1881 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1882 (section 7.4.235 , page 144). Mutt-ng searches the initial list of message
1883 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1884 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1885 7.4.235 , page 144) mailbox.
1887 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 56) for information on the
1888 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1890 Example: fcc-hook [@.]aol\\.com$ +spammers
1892 The above will save a copy of all messages going to the aol.com domain to the
1893 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 ,
1896 _
\b3_
\b._
\b2_
\b0 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be _
\ba_
\bn_
\bd _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\ba_
\bt _
\bo_
\bn_
\bc_
\be
1898 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1900 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1901 3.19 , page 38) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 37) with its arguments.
1903 _
\b3_
\b._
\b2_
\b1 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt_
\bs
1905 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1907 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1909 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1911 These commands can be used to execute arbitrary configuration commands based
1912 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1913 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1916 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1917 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1918 and _
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bs. N
\bNo
\bot
\bte
\be:
\b: reply-hooks are matched b
\bbe
\bef
\bfo
\bor
\bre
\be the send-hook, r
\bre
\beg
\bga
\bar
\brd
\bdl
\ble
\bes
\bss
\bs of
1919 the order specified in the users's configuration file.
1921 send2-hook is matched every time a message is changed, either by editing it, or
1922 by using the compose menu to change its recipients or subject. send2-hook is
1923 executed after send-hook, and can, e.g., be used to set parameters such as the
1924 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.252 , page 148) variable depending on the message's
1927 The Mutt Next Generation E-Mail Client 39
1929 For each type of send-hook or reply-hook, when multiple matches occur, commands
1930 are executed in the order they are specified in the muttrc (for that type of
1933 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 56) for information on the
1934 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1936 Example: send-hook mutt 'set mime_forward signature='''
1938 Another typical use for this command is to change the values of the _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\b-
1939 _
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 92), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.264 , page 151) and
1940 _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.118 , page 117) variables in order to change the language
1941 of the attributions and signatures based upon the recipients.
1943 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
1944 recipients. Adding a recipient after replying or editing the message will NOT
1945 cause any send-hook to be executed. Also note that my_hdr commands which mod-
1946 ify recipient headers, or the message's subject, don't have any effect on the
1947 current message when executed from a send-hook.
1949 _
\b3_
\b._
\b2_
\b2 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\be_
\bf_
\bo_
\br_
\be _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bt_
\bi_
\bn_
\bg _
\ba _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
1951 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1953 This command can be used to execute arbitrary configuration commands before
1954 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
1955 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
1956 tiple matches occur, commands are executed in the order they are specified in
1959 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 56) for information on the
1960 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1964 message-hook ~A 'set pager=builtin'
1965 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1967 _
\b3_
\b._
\b2_
\b3 _
\bC_
\bh_
\bo_
\bo_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bc_
\br_
\by_
\bp_
\bt_
\bo_
\bg_
\br_
\ba_
\bp_
\bh_
\bi_
\bc _
\bk_
\be_
\by _
\bo_
\bf _
\bt_
\bh_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt
1969 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
1971 When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
1972 tain key with a given e-mail address automatically, either because the recipi-
1973 ent's public key can't be deduced from the destination address, or because, for
1974 some reasons, you need to override the key Mutt-ng would normally use. The
1975 crypt-hook command provides a method by which you can specify the ID of the
1976 public key to be used when encrypting messages to a certain recipient.
1978 The Mutt Next Generation E-Mail Client 40
1980 The meaning of "key id" is to be taken broadly in this context: You can either
1981 put a numerical key ID here, an e-mail address, or even just a real name.
1983 _
\b3_
\b._
\b2_
\b4 _
\bA_
\bd_
\bd_
\bi_
\bn_
\bg _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be_
\bs _
\bt_
\bo _
\bt_
\bh_
\be _
\bk_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bb_
\bu_
\bf_
\bf_
\be_
\br
1985 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1987 This command adds the named string to the keyboard buffer. The string may con-
1988 tain control characters, key names and function names like the sequence string
1989 in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 28) command. You may use it to automatically
1990 run a sequence of commands at startup, or when entering certain folders.
1992 _
\b3_
\b._
\b2_
\b5 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
1994 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
1996 This command can be used to execute any function. Functions are listed in the
1997 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 172). ``exec function'' is equivalent
1998 to ``push <function>''.
2000 _
\b3_
\b._
\b2_
\b6 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
2002 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
2004 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
2006 In situations where you have to cope with a lot of emails, e.g. when you read
2007 many different mailing lists, and take part in discussions, it is always useful
2008 to have the important messages marked and the annoying messages or the ones
2009 that you aren't interested in deleted. For this purpose, mutt-ng features a
2010 mechanism called ``scoring''.
2012 When you use scoring, every message has a base score of 0. You can then use the
2013 score command to define patterns and a positive or negative value associated
2014 with it. When a pattern matches a message, the message's score will be raised
2015 or lowered by the amount of the value associated with the pattern.
2017 score "~f nion@muttng\.org" 50
2018 score "~f @sco\.com" -100
2020 If the pattern matches, it is also possible to set the score value of the cur-
2021 rent message to a certain value and then stop evaluation:
2023 score "~f santaclaus@northpole\.int" =666
2025 The Mutt Next Generation E-Mail Client 41
2027 What is important to note is that negative score values will be rounded up to
2030 To make scoring actually useful, the score must be applied in some way. That's
2031 what the _
\bs_
\bc_
\bo_
\br_
\be _
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\bs are for. Currently, there are three score thresholds:
2033 +
\bo flag threshold: when a message has a score value equal or higher than the
2034 flag threshold, it will be flagged.
2036 +
\bo read threshold: when a message has a score value equal or lower than the
2037 read threshold, it will be marked as read.
2039 +
\bo delete threshold: when a message has a score value equal or lower than the
2040 delete threshold, it will be marked as deleted.
2042 These three thresholds can be set via the variables _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg (sec-
2043 tion 7.4.249 , page 148), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.250 , page 148),
2044 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.248 , page 148) and. By default,
2045 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.250 , page 148) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
2046 (section 7.4.248 , page 148) are set to -1, which means that in the default
2047 threshold configuration no message will ever get marked as read or deleted.
2049 Scoring gets especially interesting when combined with the color command and
2052 color black yellow "~n 10-"
2053 color red yellow "~n 100-"
2055 The rules above mark all messages with a score between 10 and 99 with black and
2056 yellow, and messages with a score greater or equal 100 with red and yellow.
2057 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
2058 but it is more flexible, as it visually marks different scores.
2060 _
\b3_
\b._
\b2_
\b7 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
2062 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2064 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
2066 Mutt-ng has generalized support for external spam-scoring filters. By defining
2067 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
2068 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
2069 filter. You also can display the spam attributes in your index display using
2070 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114) variable.
2071 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
2074 Your first step is to define your external filter's spam patterns using the
2075 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
2076 mail message. If any message in the mailbox matches this regular expression, it
2078 The Mutt Next Generation E-Mail Client 42
2080 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
2081 nospam pattern -- see below.) The appearance of this attribute is entirely up
2082 to you, and is governed by the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt parameter. _
\bf_
\bo_
\br_
\bm_
\ba_
\bt can be any static text,
2083 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
2084 expression ``back-reference'' refers to a sub-expression contained within
2085 parentheses.) %1 is replaced with the first back-reference in the regex, %2
2086 with the second, etc.
2088 If you're using multiple spam filters, a message can have more than one spam-
2089 related header. You can define spam patterns for each filter you use. If a mes-
2090 sage matches two or more of these patterns, and the $spam_separator variable is
2091 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2092 strings joined together, with the value of $spam_separator separating them.
2094 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
2095 these spam settings:
2097 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
2098 spam "X-Spam-Status: Yes" "90+/SA"
2099 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
2100 set spam_separator=", "
2102 If I then received a message that DCC registered with ``many'' hits under the
2103 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
2104 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
2105 characters before ``=many'' in a DCC report indicate the checksum used -- in
2106 this case, ``Fuz2''.)
2108 If the $spam_separator variable is unset, then each spam pattern match super-
2109 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
2110 only the last one to match.
2112 The spam tag is what will be displayed in the index when you use %H in the
2113 $index_format variable. It's also the string that the ~H pattern-matching
2114 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2115 ing by spam attribute will use as a sort key.
2117 That's a pretty complicated example, and most people's actual environments will
2118 have only one spam filter. The simpler your configuration, the more effective
2119 mutt can be, especially when it comes to sorting.
2121 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2122 ordering strings alphnumerically. However, if a spam tag begins with a number,
2123 mutt will sort numerically first, and lexically only when two numbers are equal
2124 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2125 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2126 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2127 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2128 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2129 coerce your filter to give you a raw number. But in case you can't, mutt can
2130 still do something useful.
2132 The nospam command can be used to write exceptions to spam patterns. If a
2134 The Mutt Next Generation E-Mail Client 43
2136 header pattern matches something in a spam command, but you nonetheless do not
2137 want it to receive a spam tag, you can list a more precise pattern under a
2140 If the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn given to nospam is exactly the same as the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn on an exist-
2141 ing spam list entry, the effect will be to remove the entry from the spam list,
2142 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2143 matches an entry on the nospam list, that nospam entry will be removed. If the
2144 _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for nospam is ``*'', _
\ba_
\bl_
\bl _
\be_
\bn_
\bt_
\br_
\bi_
\be_
\bs _
\bo_
\bn _
\bb_
\bo_
\bt_
\bh _
\bl_
\bi_
\bs_
\bt_
\bs will be removed. This
2145 might be the default action if you use spam and nospam in conjunction with a
2148 You can have as many spam or nospam commands as you like. You can even do your
2149 own primitive spam detection within mutt -- for example, if you consider all
2150 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2152 spam "^From: .*MAILER-DAEMON" "999"
2154 _
\b3_
\b._
\b2_
\b8 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2156 Usage: set [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2158 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2160 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2162 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2164 This command is used to set (and unset) _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 ,
2165 page 86). There are four basic types of variables: boolean, number, string and
2166 quadoption. _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables can be _
\bs_
\be_
\bt (true) or _
\bu_
\bn_
\bs_
\be_
\bt (false). _
\bn_
\bu_
\bm_
\bb_
\be_
\br
2167 variables can be assigned a positive integer value.
2169 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2170 be enclosed in quotes if they contain spaces or tabs. You may also use the
2171 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2173 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2174 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2175 action to be carried out automatically as if you had answered yes to the ques-
2176 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2177 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2178 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2180 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2182 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2183 toggle the value (on or off). This is useful when writing macros. Example:
2186 The Mutt Next Generation E-Mail Client 44
2188 The toggle command automatically prepends the inv prefix to all specified vari-
2191 The unset command automatically prepends the no prefix to all specified vari-
2194 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2195 a variable by prefixing the name of the variable with a question mark:
2199 The question mark is actually only required for boolean and quadoption vari-
2202 The reset command resets all given variables to the compile time defaults
2203 (hopefully mentioned in this manual). If you use the command set and prefix the
2204 variable with ``&'' this has the same behavior as the reset command.
2206 With the reset command there exists the special variable ``all'', which allows
2207 you to reset all variables to their system defaults.
2209 _
\b3_
\b._
\b2_
\b9 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bi_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs _
\bf_
\br_
\bo_
\bm _
\ba_
\bn_
\bo_
\bt_
\bh_
\be_
\br _
\bf_
\bi_
\bl_
\be
2211 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2213 This command allows the inclusion of initialization commands from other files.
2214 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2215 ~/.muttrc readable and keep my aliases private.
2217 If the filename begins with a tilde (``~''), it will be expanded to the path of
2218 your home directory.
2220 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2221 an executable program from which to read input (eg. source ~/bin/myscript|).
2223 _
\b3_
\b._
\b3_
\b0 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2225 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2227 This command permits you to flush hooks you have previously defined. You can
2228 either remove all hooks by giving the ``*'' character as an argument, or you
2229 can remove all hooks of a specific type by saying something like unhook send-
2232 _
\b3_
\b._
\b3_
\b1 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2234 The Mutt Next Generation E-Mail Client 45
2236 _
\b3_
\b._
\b3_
\b1_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2238 As users may run mutt-ng on different systems, the configuration must be main-
2239 tained because it's likely that people want to use the setup everywhere they
2240 use mutt-ng. And mutt-ng tries to help where it can.
2242 To not produce conflicts with different character sets, mutt-ng allows users to
2243 specify in which character set their configuration files are encoded. Please
2244 note that while reading the configuration files, this is only respected after
2245 the corresponding declaration appears. It's advised to put the following at the
2246 very beginning of a users muttngrc:
2248 set config_charset = "..."
2250 and replacing the dots with the actual character set. To avoid problems while
2251 maintaining the setup, vim user's may want to use modelines as show in:
2253 # vim:fileencoding=...:
2255 while, again, replacing the dots with the appropriate name. This tells vim as
2256 which character set to read and save the file.
2258 _
\b3_
\b._
\b3_
\b1_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2260 ``Modularization'' means to divide the setup into several files while sorting
2261 the options or commands by topic. Especially for longer setups (e.g. with many
2262 hooks), this helps maintaining it and solving trouble.
2264 When using separation, setups may be, as a whole or in fractions, shared over
2267 _
\b3_
\b._
\b3_
\b1_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2269 When using a configuration on different systems, the user may not always have
2270 influence on how mutt-ng is installed and which features it includes.
2272 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2273 for mutt. Its basic syntax is:
2275 ifdef <item> <command>
2276 ifndef <item> <command>
2278 ...whereby <item> can be one of:
2280 The Mutt Next Generation E-Mail Client 46
2282 +
\bo a function name
2284 +
\bo a variable name
2290 All available functions, variables and menus are documented elsewhere in this
2291 manual but ``features'' is specific to these two commands. To test for one,
2292 prefix one of the following keywords with feature_:
2294 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2295 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2296 classic_smime, gpgme, header_cache
2298 As an example, one can use the following in ~/.muttngrc:
2300 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2301 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2302 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2304 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2305 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2306 ng/setup-nntp if NNTP support is built in.
2308 An example for testing for variable names can be used if users use different
2309 revisions of mutt-ng whereby the older one may not have a certain variable. To
2310 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.103 , page 111),
2313 ifdef imap_mail_check 'set imap_mail_check = 300'
2315 Provided for completeness is the test for menu names. To set _
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
2316 (section 7.4.174 , page 130) only if the pager menu is available, use:
2318 ifdef pager 'set pager_index_lines = 10'
2320 For completeness, too, the opposite of ifdef is provided: ifndef which only
2321 executes the command if the test fails. For example, the following two examples
2324 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2325 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2327 The Mutt Next Generation E-Mail Client 47
2331 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2332 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2334 _
\b3_
\b._
\b3_
\b2 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2336 In the process of ensuring and creating more consistency, many variables have
2337 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2338 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 86) for a complete list.
2340 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2342 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2344 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2345 tion 7.2 , page 82) must be specified using regular expressions (regexp) in
2346 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2347 and GNU awk). For your convenience, we have included below a brief description
2350 The search is case sensitive if the pattern contains at least one upper case
2351 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2352 for a regular expression in an initialization command: ``\\''.
2354 A regular expression is a pattern that describes a set of strings. Regular
2355 expressions are constructed analogously to arithmetic expressions, by using
2356 various operators to combine smaller expressions.
2358 Note that the regular expression can be enclosed/delimited by either ' or '
2359 which is useful if the regular expression includes a white-space character.
2360 See _
\bS_
\by_
\bn_
\bt_
\ba_
\bx _
\bo_
\bf _
\bI_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs (section 3.2 , page 21) for more informa-
2361 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2362 ace it with \ (backslash).
2364 The fundamental building blocks are the regular expressions that match a single
2365 character. Most characters, including all letters and digits, are regular
2366 expressions that match themselves. Any metacharacter with special meaning may
2367 be quoted by preceding it with a backslash.
2369 The period ``.'' matches any single character. The caret ``^'' and the dollar
2370 sign ``$'' are metacharacters that respectively match the empty string at the
2371 beginning and end of a line.
2373 The Mutt Next Generation E-Mail Client 48
2375 A list of characters enclosed by ``['' and ``]'' matches any single character
2376 in that list; if the first character of the list is a caret ``^'' then it
2377 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2378 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2379 specified by giving the first and last characters, separated by a hyphen ``-''.
2380 Most metacharacters lose their special meaning inside lists. To include a lit-
2381 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2382 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2385 Certain named classes of characters are predefined. Character classes consist
2386 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2387 defined by the POSIX standard:
2390 Alphanumeric characters.
2393 Alphabetic characters.
2396 Space or tab characters.
2405 Characters that are both printable and visible. (A space is print-
2406 able, but not visible, while an ``a'' is both.)
2409 Lower-case alphabetic characters.
2412 Printable characters (characters that are not control characters.)
2415 Punctuation characters (characters that are not letter, digits,
2416 control characters, or space characters).
2419 Space characters (such as space, tab and formfeed, to name a few).
2422 Upper-case alphabetic characters.
2425 Characters that are hexadecimal digits.
2427 A character class is only valid in a regular expression inside the brackets of
2428 a character list. Note that the brackets in these class names are part of the
2430 The Mutt Next Generation E-Mail Client 49
2432 symbolic names, and must be included in addition to the brackets delimiting the
2433 bracket list. For example, [
\b[[
\b[:
\b:d
\bdi
\big
\bgi
\bit
\bt:
\b:]
\b]]
\b] is equivalent to [
\b[0
\b0-
\b-9
\b9]
\b].
2435 Two additional special sequences can appear in character lists. These apply to
2436 non-ASCII character sets, which can have single symbols (called collating ele-
2437 ments) that are represented with more than one character, as well as several
2438 characters that are equivalent for collating or sorting purposes:
2441 A collating symbol is a multi-character collating element enclosed
2442 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2443 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2444 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2447 An equivalence class is a locale-specific name for a list of char-
2448 acters that are equivalent. The name is enclosed in ``[='' and
2449 ``=]''. For example, the name ``e'' might be used to represent all
2450 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2451 matches any of ``'', ``'' and ``e''.
2453 A regular expression matching a single character may be followed by one of sev-
2454 eral repetition operators:
2457 The preceding item is optional and matched at most once.
2460 The preceding item will be matched zero or more times.
2463 The preceding item will be matched one or more times.
2466 The preceding item is matched exactly _
\bn times.
2469 The preceding item is matched _
\bn or more times.
2472 The preceding item is matched at most _
\bm times.
2475 The preceding item is matched at least _
\bn times, but no more than _
\bm
2478 Two regular expressions may be concatenated; the resulting regular expression
2479 matches any string formed by concatenating two substrings that respectively
2480 match the concatenated subexpressions.
2482 Two regular expressions may be joined by the infix operator ``|''; the result-
2483 ing regular expression matches any string matching either subexpression.
2485 Repetition takes precedence over concatenation, which in turn takes precedence
2487 The Mutt Next Generation E-Mail Client 50
2489 over alternation. A whole subexpression may be enclosed in parentheses to
2490 override these precedence rules.
2492 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2493 may also be used in regular expressions:
2496 Matches the empty string at either the beginning or the end of a
2500 Matches the empty string within a word.
2503 Matches the empty string at the beginning of a word.
2506 Matches the empty string at the end of a word.
2509 Matches any word-constituent character (letter, digit, or under-
2513 Matches any character that is not word-constituent.
2516 Matches the empty string at the beginning of a buffer (string).
2519 Matches the empty string at the end of a buffer.
2521 Please note however that these operators are not defined by POSIX, so they may
2522 or may not be available in stock libraries on various systems.
2524 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2526 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2527 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2528 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2529 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2530 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 82) in the Reference chapter.
2532 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2533 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2536 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2538 It is possible to combine several sub-patterns to a more complex pattern. The
2539 most simple possibility is to logically AND several patterns by stringing them
2542 The Mutt Next Generation E-Mail Client 51
2546 The pattern above matches all messages that contain ``SPAM'' in the subject and
2549 To logical OR patterns, simply use the | operator. This one especially useful
2550 when using local groups:
2552 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2553 (~b mutt-ng|~s Mutt-ng)
2556 The first pattern matches all messages that were sent by one of the mutt-ng
2557 maintainers, while the seconds pattern matches all messages that contain
2558 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2559 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2560 ences: header, i.e. messages that are not an (indirect) reply to one of my
2561 messages. A pattern can be logicall negated using the ! operator.
2563 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2565 When using dates in patterns, the dates must be specified in a special format,
2566 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2567 rent month or year. When using date ranges, and you specify only the minimum or
2568 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2569 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2571 It is also possible to use so-called ``error margins'' when specifying date
2572 ranges. You simply specify a date, and then the error margin. This margin
2573 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2574 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2575 months, w for weeks and d for days. If you use the special * sign, it means
2576 that the error margin goes to both ``directions'' in time.
2582 The first pattern matches all dates between January 1st, 2005 and January 1st
2583 2006. The second pattern matches all dates between October 18th, 2004 and
2584 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2585 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2587 Relative dates are also very important, as they make it possible to specify
2588 date ranges between a fixed number of units and the current date. How this
2589 works can be seen in the following example:
2591 The Mutt Next Generation E-Mail Client 52
2593 ~d >2w # messages older than two weeks
2594 ~d <3d # messages newer than 3 days
2595 ~d =1m # messages that are exactly one month old
2597 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2599 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2601 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2602 In short, they describe what items to print out how in menus and status mes-
2605 Basically, they work as this: for different menus and bars, there's a variable
2606 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2608 For example, when running mutt-ng on different machines or different versions
2609 for testing purposes, it may be interesting to have the following information
2610 always printed on screen when one is in the index:
2612 +
\bo the current hostname
2614 +
\bo the current mutt-ng version number
2616 The setting for the status bar of the index is controlled via the _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\b-
2617 _
\bm_
\ba_
\bt (section 7.4.313 , page 163) variable. For the hostname and version
2618 string, there's an expando for $status_format: %h expands to the hostname and
2619 %v to the version string. When just configuring:
2621 set status_format = "%v on %h: ..."
2623 mutt-ng will replace the sequence %v with the version string and %h with the
2624 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2625 mailhost, you'll see the following when you're in the index:
2627 Mutt-ng 1.5.9i on mailhost: ...
2629 In the index, there're more useful information one could want to see:
2631 +
\bo which mailbox is open
2633 +
\bo how man new, flagged or postponed messages
2637 To include the mailbox' name is as easy as:
2639 The Mutt Next Generation E-Mail Client 53
2641 set status_format = "%v on %h: %B: ...
2643 When the currently opened mailbox is Inbox, this will be expanded to:
2645 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2647 For the number of certain types of messages, one more feature of the format
2648 strings is extremely useful. If there aren't messages of a certain type, it may
2649 not be desired to print just that there aren't any but instead only print some-
2650 thing if there are any.
2652 _
\b4_
\b._
\b3_
\b._
\b2 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
2654 To only print the number of messages if there are new messages in the current
2655 mailbox, further extend $status_format to:
2657 set status_format = "%v on %h: %B %?n?%n new? ...
2659 This feature is called _
\bn_
\bo_
\bn_
\bz_
\be_
\br_
\bo_
\b-_
\bp_
\br_
\bi_
\bn_
\bt_
\bi_
\bn_
\bg and works as this: some expandos may be
2660 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2661 ated if the value of the expando is different from zero. The basic syntax is:
2663 %?<item>?<string if nonzero>?
2665 which tells mutt-ng to only look at <string if nonzero> if the value of the
2666 %<item%gt; expando is different from zero. In our example, we used n as the
2667 expando to check for and %n new as the optional nonzero string.
2669 But this is not all: this feature only offers one alternative: ``print some-
2670 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2671 complete version: ``if zero, print something and else print something else.''
2672 This is achieved by the following syntax for those expandos which may be
2675 %?<item>?<string if nonzero>&<string if zero>?
2677 Using this we can make mutt-ng to do the following:
2679 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2682 +
\bo and make it print ``no new messages'' if there aren't any
2684 The Mutt Next Generation E-Mail Client 54
2686 The corresponding configuration is:
2688 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2690 This doubles the use of the ``new messages'' string because it'll get always
2691 printed. Thus, it can be shortened to:
2693 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2695 As you might see from this rather simple example, one can create very complex
2696 but fancy status messages. Please see the reference chapter for expandos and
2697 those which may be printed nonzero.
2699 _
\b4_
\b._
\b3_
\b._
\b3 _
\bM_
\bo_
\bd_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs _
\ba_
\bn_
\bd _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg
2701 Besides the information given so far, there're even more features of format
2704 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2705 characters in the expansion of <item> to lowercase.
2707 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2708 dots in the expansion of <item> to underscores (_).
2710 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2714 When this occurs, mutt-ng will fill the rest of the line with the
2715 character X. In our example, filling the rest of the line with
2716 dashes is done by setting:
2718 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2721 Since the previous expando stops at the end of line, there must be
2722 a way to fill the gap between two items via the %>X expando: it
2723 puts as many characters X in between two items so that the rest of
2724 the line will be right-justified. For example, to not put the ver-
2725 sion string and hostname of our example on the left but on the
2726 right and fill the gap with spaces, one might use (note the space
2729 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2731 The Mutt Next Generation E-Mail Client 55
2733 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2735 Sometimes it is desirable to perform an operation on a group of messages all at
2736 once rather than one at a time. An example might be to save messages to a
2737 mailing list to a separate folder, or to delete all messages with a given sub-
2738 ject. To tag all messages matching a pattern, use the tag-pattern function,
2739 which is bound to ``shift-T'' by default. Or you can select individual mes-
2740 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2741 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 82) for Mutt-ng's pattern matching
2744 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2745 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2746 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2747 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.19 ,
2748 page 92) variable is set, the next operation applies to the tagged messages
2749 automatically, without requiring the ``tag-prefix''.
2751 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 28) or _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 40) commands,
2752 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2753 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2754 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2755 this operator the rest of the macro will be executed as normal.
2757 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2759 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2760 arbitrary commands before performing some operation. For example, you may wish
2761 to tailor your configuration based upon which mailbox you are reading, or to
2762 whom you are sending mail. In the Mutt-ng world, a _
\bh_
\bo_
\bo_
\bk consists of a _
\br_
\be_
\bg_
\bu_
\bl_
\ba_
\br
2763 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 47) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 82) along
2764 with a configuration option/command. See
2766 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 28)
2768 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 38)
2770 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 39)
2772 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 37)
2774 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 35)
2776 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38)
2778 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 38)
2780 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2782 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2783 until the end of the current mutt session. As this is generally not desired, a
2784 default hook needs to be added before all other hooks to restore configuration
2786 The Mutt Next Generation E-Mail Client 56
2788 defaults. Here is an example with send-hook and the my_hdr directive:
2790 send-hook . 'unmy_hdr From:'
2791 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2793 _
\b4_
\b._
\b5_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs
2795 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2796 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2797 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 47) is sufficient. But in dealing with
2798 messages a finer grain of control is needed for matching since for different
2799 purposes you want to match different criteria.
2801 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 82) language
2802 for matching messages in hook commands. This works in exactly the same way as
2803 it would when _
\bl_
\bi_
\bm_
\bi_
\bt_
\bi_
\bn_
\bg or _
\bs_
\be_
\ba_
\br_
\bc_
\bh_
\bi_
\bn_
\bg the mailbox, except that you are restricted
2804 to those operators which match information mutt extracts from the header of the
2805 message (i.e. from, to, cc, date, subject, etc.).
2807 For example, if you wanted to set your return address based upon sending mail
2808 to a specific address, you could do something like:
2810 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2812 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2814 However, it is not required that you write the pattern to match using the full
2815 searching language. You can still specify a simple _
\br_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn like the
2816 other hooks, in which case Mutt-ng will translate your pattern into the full
2817 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2818 7.4.48 , page 98) variable. The pattern is translated at the time the hook is
2819 declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.48 , page 98) that is in
2820 effect at that time will be used.
2822 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2824 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2825 which looks very similar to the ones you probably know from GUI mail clients.
2826 The sidebar lists all specified mailboxes, shows the number in each and high-
2827 lights the ones with new email Use the following configuration commands:
2829 set sidebar_visible="yes"
2830 set sidebar_width=25
2832 If you want to specify the mailboxes you can do so with:
2834 The Mutt Next Generation E-Mail Client 57
2842 You can also specify the colors for mailboxes with new mails by using:
2844 color sidebar_new red black
2845 color sidebar white black
2847 The available functions are:
2849 sidebar-scroll-up Scrolls the mailbox list up 1 page
2850 sidebar-scroll-down Scrolls the mailbox list down 1 page
2851 sidebar-next Highlights the next mailbox
2852 sidebar-next-new Highlights the next mailbox with new mail
2853 sidebar-previous Highlights the previous mailbox
2854 sidebar-open Opens the currently highlighted mailbox
2856 Reasonable key bindings look e.g. like this:
2858 bind index \Cp sidebar-prev
2859 bind index \Cn sidebar-next
2860 bind index \Cb sidebar-open
2861 bind pager \Cp sidebar-prev
2862 bind pager \Cn sidebar-next
2863 bind pager \Cb sidebar-open
2865 macro index B ':toggle sidebar_visible^M'
2866 macro pager B ':toggle sidebar_visible^M'
2868 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2869 off the sidebar simply by pressing 'B'.
2871 _
\b4_
\b._
\b7 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\bA_
\bd_
\bd_
\br_
\be_
\bs_
\bs _
\bQ_
\bu_
\be_
\br_
\bi_
\be_
\bs
2873 Mutt-ng supports connecting to external directory databases such as LDAP,
2874 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2875 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.226 , page 142) vari-
2876 able, you specify the wrapper command to use. For example:
2878 set query_command = "mutt_ldap_query.pl '%s'"
2880 The wrapper script should accept the query on the command-line. It should
2881 return a one line message, then each matching response on a single line, each
2883 The Mutt Next Generation E-Mail Client 58
2885 line containing a tab separated address then name then some other optional
2886 information. On error, or if there are no matching addresses, return a non-
2887 zero exit code and a one line error message.
2889 An example multiple response output:
2891 Searching database ... 20 entries ... 3 matching:
2892 me@cs.hmc.edu Michael Elkins mutt dude
2893 blong@fiction.net Brandon Long mutt and more
2894 roessler@guug.de Thomas Roessler mutt pgp
2896 There are two mechanisms for accessing the query function of mutt. One is to
2897 do a query from the index menu using the query function (default: Q). This
2898 will prompt for a query, then bring up the query menu which will list the
2899 matching responses. From the query menu, you can select addresses to create
2900 aliases, or to mail. You can tag multiple addresses to mail, start a new
2901 query, or have a new query appended to the current responses.
2903 The other mechanism for accessing the query function is for address completion,
2904 similar to the alias completion. In any prompt for address entry, you can use
2905 the complete-query function (default: ^T) to run a query based on the current
2906 address you have typed. Like aliases, mutt will look for what you have typed
2907 back to the last space or comma. If there is a single response for that query,
2908 mutt will expand the address in place. If there are multiple responses, mutt
2909 will activate the query menu. At the query menu, you can select one or more
2910 addresses to be added to the prompt.
2912 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2914 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2915 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2916 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2917 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.130 , page 119)
2920 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2921 stored in a single file. Each message has a line of the form:
2923 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2925 to denote the start of a new message (this is often referred to as the
2928 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2929 lines containing ``^A^A^A^A'' (four control-A's).
2931 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2932 and each message is stored in a separate file. The filename indicates the mes-
2933 sage number (however, this is may not correspond to the message number Mutt-ng
2935 The Mutt Next Generation E-Mail Client 59
2937 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2938 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2939 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
2942 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
2943 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
2944 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
2945 way they are unique, even when two programs are writing the mailbox over NFS,
2946 which means that no file locking is needed.
2948 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
2950 There are a number of built in shortcuts which refer to specific mailboxes.
2951 These shortcuts can be used anywhere you are prompted for a file or mailbox
2954 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.302 , page 160) (incoming)
2957 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.129 , page 119) file
2959 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.235 , page 144) file
2961 +
\bo ^ -- refers to the current mailbox
2963 +
\bo - or !! -- refers to the file you've last visited
2965 +
\bo ~ -- refers to your home directory
2967 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.68 , page 103) directory
2969 +
\bo @_
\ba_
\bl_
\bi_
\ba_
\bs -- refers to the _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 3.18 , page 37) as
2970 determined by the address of the alias
2972 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
2974 Mutt-ng has a few configuration options that make dealing with large amounts of
2975 mail easier. The first thing you must do is to let Mutt know what addresses
2976 you consider to be mailing lists (technically this does not have to be a mail-
2977 ing list, but that is what it is most often used for), and what lists you are
2978 subscribed to. This is accomplished through the use of the _
\bl_
\bi_
\bs_
\bt_
\bs _
\ba_
\bn_
\bd _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be
2979 (section 3.13 , page 34) commands in your muttrc.
2981 Now that Mutt-ng knows what your mailing lists are, it can do several things,
2982 the first of which is the ability to show the name of a list through which you
2983 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
2984 This is useful to distinguish between personal and list mail in the same mail-
2985 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114) variable, the escape
2986 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
2988 The Mutt Next Generation E-Mail Client 60
2990 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
2991 returns the name of the author).
2993 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
2994 quite large. Most people do not bother to remove the author of the message they
2995 are reply to from the list, resulting in two or more copies being sent to that
2996 person. The ``list-reply'' function, which by default is bound to ``L'' in the
2997 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
2998 mailing list addresses instead of all recipients (except as specified by Mail-
2999 Followup-To, see below).
3001 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
3002 a list of recipients which includes one or several subscribed mailing lists,
3003 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.70 , page 104) option is set, mutt will
3004 generate a Mail-Followup-To header which contains all the recipients to whom
3005 you send this message, but not your address. This indicates that group-replies
3006 or list-replies (also known as ``followups'') to this message should only be
3007 sent to the original recipients of the message, and not separately to you -
3008 you'll receive your copy through one of the mailing lists you are subscribed
3011 Conversely, when group-replying or list-replying to a message which has a Mail-
3012 Followup-To header, mutt will respect this header if the _
\b$_
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
3013 (section 7.4.92 , page 109) configuration variable is set. Using list-reply
3014 will in this case also make sure that the reply goes to the mailing list, even
3015 if it's not specified in the list of recipients in the Mail-Followup-To.
3017 Note that, when header editing is enabled, you can create a Mail-Followup-To
3018 header manually. Mutt-ng will only auto-generate this header if it doesn't
3019 exist when you send the message.
3021 The other method some mailing list admins use is to generate a ``Reply-To''
3022 field which points back to the mailing list address rather than the author of
3023 the message. This can create problems when trying to reply directly to the
3024 author in private, since most mail clients will automatically reply to the
3025 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
3026 7.4.238 , page 145) variable to help decide which address to use. If set to
3027 _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs or _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo, you will be prompted as to whether or not you would like to
3028 use the address given in the ``Reply-To'' field, or reply directly to the
3029 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
3030 will be used when present.
3032 The ``X-Label:'' header field can be used to further identify mailing lists or
3033 list subject matter (or just to annotate messages individually). The
3034 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114) variable's ``%y'' and ``%Y''
3035 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
3036 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
3037 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
3038 can easily be inserted by procmail and other mail filtering agents.
3040 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.296 , page 158) the mail-
3041 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
3042 which all relate to the same subject. This is usually organized into a tree-
3043 like structure where a message and all of its replies are represented
3045 The Mutt Next Generation E-Mail Client 61
3047 graphically. If you've ever used a threaded news client, this is the same con-
3048 cept. It makes dealing with large volume mailing lists easier because you can
3049 easily delete uninteresting threads and quickly find topics of value.
3051 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3053 Mutt-ng has the ability to dynamically restructure threads that are broken
3054 either by misconfigured software or bad behavior from some correspondents. This
3055 allows to clean your mailboxes formats) from these annoyances which make it
3056 hard to follow a discussion.
3058 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3060 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
3061 ences:" headers when replying to a message. This results in broken discussions
3062 because Mutt-ng has not enough information to guess the correct threading. You
3063 can fix this by tagging the reply, then moving to the parent message and using
3064 the ``link-threads'' function (bound to & by default). The reply will then be
3065 connected to this "parent" message.
3067 You can also connect multiple children at once, tagging them and using the tag-
3068 prefix command (';') or the auto_tag option.
3070 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3072 On mailing lists, some people are in the bad habit of starting a new discussion
3073 by hitting "reply" to any message from the list and changing the subject to a
3074 totally unrelated one. You can fix such threads by using the ``break-thread''
3075 function (bound by default to #), which will turn the subthread starting from
3076 the current message into a whole different thread.
3078 _
\b4_
\b._
\b1_
\b2 _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn _
\b(_
\bD_
\bS_
\bN_
\b) _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3080 RFC1894 defines a set of MIME content types for relaying information about the
3081 status of electronic mail messages. These can be thought of as ``return
3084 Users can make use of it in one of the following two ways:
3086 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
3087 the mail client can make requests as to what type of status messages
3090 +
\bo The SMTP support via libESMTP supports it, too.
3092 To support this, there are two variables:
3094 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.55 , page 100) is used to request receipts for
3095 different results (such as failed message, message delivered, etc.).
3097 The Mutt Next Generation E-Mail Client 62
3099 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.56 , page 100) requests how much of your message
3100 should be returned with the receipt (headers or full message).
3102 Please see the reference chapter for possible values.
3104 _
\b4_
\b._
\b1_
\b3 _
\bP_
\bO_
\bP_
\b3 _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt _
\b(_
\bO_
\bP_
\bT_
\bI_
\bO_
\bN_
\bA_
\bL_
\b)
3106 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3107 the _
\b-_
\b-_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\b-_
\bp_
\bo_
\bp flag), it has the ability to work with mailboxes located on a
3108 remote POP3 server and fetch mail for local browsing.
3110 You can access the remote POP3 mailbox by selecting the folder
3113 You can select an alternative port by specifying it with the server, i.e.:
3114 pop://popserver:port/.
3116 You can also specify different username for each folder, i.e.: pop://user-
3117 name@popserver[:port]/.
3119 Polling for new mail is more expensive over POP3 than locally. For this reason
3120 the frequency at which Mutt-ng will check for mail remotely can be controlled
3121 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.213 , page 140) variable, which defaults
3122 to every 60 seconds.
3124 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3125 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3126 rally requires that the server supports SSL encrypted connections. To access a
3127 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3128 name@]popserver[:port]/.
3130 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3131 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.211 , page 139), fetch all your
3132 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.302 , page 160).
3133 After this point, Mutt-ng runs exactly as if the mail had always been local.
3135 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3136 sider using a specialized program, such as fetchmail
3138 _
\b4_
\b._
\b1_
\b4 _
\bI_
\bM_
\bA_
\bP _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt _
\b(_
\bO_
\bP_
\bT_
\bI_
\bO_
\bN_
\bA_
\bL_
\b)
3140 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3141 the _
\b-_
\b-_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\b-_
\bi_
\bm_
\ba_
\bp flag), it has the ability to work with folders located on a
3144 You can access the remote inbox by selecting the folder
3145 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3146 INBOX is the special name for your spool mailbox on the IMAP server. If you
3147 want to access another mail folder at the IMAP server, you should use
3148 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3150 The Mutt Next Generation E-Mail Client 63
3154 You can select an alternative port by specifying it with the server, i.e.:
3155 imap://imapserver:port/INBOX.
3157 You can also specify different username for each folder, i.e.: imap://user-
3158 name@imapserver[:port]/INBOX.
3160 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3161 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3162 rally requires that the server supports SSL encrypted connections. To access a
3163 folder with IMAP/SSL, you should use imaps://[user-
3164 name@]imapserver[:port]/path/to/folder as your folder path.
3166 Pine-compatible notation is also supported, i.e. {[user-
3167 name@]imapserver[:port][/ssl]}path/to/folder
3169 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3170 correctly notice which separator is being used by the server and convert paths
3173 When browsing folders on an IMAP server, you can toggle whether to look at only
3174 the folders you are subscribed to, or all folders with the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
3175 command. See also the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd (section 7.4.101 , page 111)
3178 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3179 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.103 , page 111) and
3180 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.326 , page 168) variables.
3182 Note that if you are using mbox as the mail store on UW servers prior to
3183 v12.250, the server has been reported to disconnect a client if another client
3184 selects the same folder.
3186 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3188 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3189 mostly the same as the local file browser, with the following differences:
3191 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3192 followed by the symbol "+", indicating that the entry contains both mes-
3193 sages and subfolders. On Cyrus-like servers folders will often contain
3194 both messages and subfolders.
3196 +
\bo For the case where an entry can contain both messages and subfolders, the
3197 selection key (bound to enter by default) will choose to descend into the
3198 subfolder view. If you wish to view the messages in that folder, you must
3199 use view-file instead (bound to space by default).
3201 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3202 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3203 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3204 mally these are bound to s and u, respectively).
3206 The Mutt Next Generation E-Mail Client 64
3208 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3210 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3211 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3212 tion for you poor exchange users out there, but it has yet to be integrated
3213 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3214 which allows you to log in to a public IMAP server without having an account.
3215 To use ANONYMOUS, simply make your username blank or "anonymous".
3217 SASL is a special super-authenticator, which selects among several protocols
3218 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3219 available on your host and the server. Using some of these methods (including
3220 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3221 invisible to those teeming network snoops. It is the best option if you have
3222 it. To use it, you must have the Cyrus SASL library installed on your system
3223 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3225 Mutt-ng will try whichever methods are compiled in and available on the server,
3226 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3228 There are a few variables which control authentication:
3230 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.109 , page 113) - controls the username under
3231 which you request authentication on the IMAP server, for all authentica-
3232 tors. This is overridden by an explicit username in the mailbox path (i.e.
3233 by using a mailbox name of the form {user@host}).
3235 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.104 , page 112) - a password which you may pre-
3236 set, used by all authentication methods where a password is needed.
3238 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.95 , page 109) - a colon-delimited list
3239 of IMAP authentication methods to try, in the order you wish to try them.
3240 If specified, this overrides mutt's default (attempt everything, in the
3241 order listed above).
3243 _
\b4_
\b._
\b1_
\b5 _
\bN_
\bN_
\bT_
\bP _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt _
\b(_
\bO_
\bP_
\bT_
\bI_
\bO_
\bN_
\bA_
\bL_
\b)
3245 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3246 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3247 function from the index/pager which is by default bound to i.
3249 The Default newsserver can be obtained from the $NNTPSERVER environment vari-
3250 able. Like other news readers, info about subscribed newsgroups is saved in a
3251 file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.161 , page 127) variable.
3252 Article headers are cached and can be loaded from a file when a newsgroup is
3253 entered instead loading from newsserver; currently, this caching mechanism
3254 still is different from the header caching for maildir/IMAP.
3256 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3258 Especially for Usenet, people often ask for advanced filtering and scoring
3259 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3261 The Mutt Next Generation E-Mail Client 65
3263 to use a killfile has been discussed in _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bs_
\bc_
\bo_
\br_
\bi_
\bn_
\bg (section 3.26 , page
3266 What has not been discusses in detail is mutt-ng's built-in realname filter.
3267 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3268 there are frequent request for such functionality. The solutions offered often
3269 are complicated regular expressions.
3271 In mutt-ng this is as easy as
3275 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3276 fied a valid realname and a valid email address. Using
3280 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3281 ria which are very strict:
3283 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3284 editor.org/in-notes/rfc2822.txt>
3286 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3287 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3288 ``J. User'' and ``J. A. User'' aren't.
3290 +
\bo it's assumed that users are interested in reading their own mail and mail
3291 from people who they have defined an alias for so that those 2 groups of
3292 messages are excluded from the strict rules.
3294 _
\b4_
\b._
\b1_
\b6 _
\bS_
\bM_
\bT_
\bP _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt _
\b(_
\bO_
\bP_
\bT_
\bI_
\bO_
\bN_
\bA_
\bL_
\b)
3296 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3297 functionality. When configure was called with --with-libesmtp or the output
3298 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3299 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3300 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 61) section) as well as handling the 8BIT-
3301 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.333 , page 169).
3303 To enable sending mail directly via SMTP without an MTA such as Postfix or
3304 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.291 , page 157)
3305 variable pointing to your SMTP server.
3307 The Mutt Next Generation E-Mail Client 66
3309 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.295 ,
3310 page 158) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.292 , page 157) variables.
3312 Transport Encryption via the StartTLS command is also available. For this to
3313 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3314 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.294 , page 158) variable must be either set to
3315 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3316 supports it: for the second case, the connection will fail if it doesn't while
3317 switching back to unencrypted communication for the first one.
3319 Some mail providers require user's to set a particular envelope sender, i.e.
3320 they allow for only one value which may not be what the user wants to send as
3321 the From: header. In this case, the variable _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be (section 7.4.290 ,
3322 page 157) may be used to set the envelope different from the From: header.
3324 _
\b4_
\b._
\b1_
\b7 _
\bM_
\ba_
\bn_
\ba_
\bg_
\bi_
\bn_
\bg _
\bm_
\bu_
\bl_
\bt_
\bi_
\bp_
\bl_
\be _
\bI_
\bM_
\bA_
\bP_
\b/_
\bP_
\bO_
\bP_
\b/_
\bN_
\bN_
\bT_
\bP _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\bs _
\b(_
\bO_
\bP_
\bT_
\bI_
\bO_
\bN_
\bA_
\bL_
\b)
3326 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3327 find managing all the authentication settings inconvenient and error-prone.
3328 The account-hook command may help. This hook works like folder-hook but is
3329 invoked whenever you access a remote mailbox (including inside the folder
3330 browser), not just when you open the mailbox.
3334 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3335 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3336 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3338 _
\b4_
\b._
\b1_
\b8 _
\bS_
\bt_
\ba_
\br_
\bt _
\ba _
\bW_
\bW_
\bW _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br _
\bo_
\bn _
\bU_
\bR_
\bL_
\bs _
\b(_
\bE_
\bX_
\bT_
\bE_
\bR_
\bN_
\bA_
\bL_
\b)
3340 If a message contains URLs (_
\bu_
\bn_
\bi_
\bf_
\bi_
\be_
\bd _
\br_
\be_
\bs_
\bo_
\bu_
\br_
\bc_
\be _
\bl_
\bo_
\bc_
\ba_
\bt_
\bo_
\br = address in the WWW space
3341 like _
\bh_
\bt_
\bt_
\bp_
\b:_
\b/_
\b/_
\bw_
\bw_
\bw_
\b._
\bm_
\bu_
\bt_
\bt_
\b._
\bo_
\br_
\bg_
\b/), it is efficient to get a menu with all the URLs and
3342 start a WWW browser on one of them. This functionality is provided by the
3343 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3344 trib/ and the configuration commands:
3346 macro index \cb |urlview\n
3347 macro pager \cb |urlview\n
3349 _
\b4_
\b._
\b1_
\b9 _
\bC_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt _
\b(_
\bO_
\bP_
\bT_
\bI_
\bO_
\bN_
\bA_
\bL_
\b)
3351 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3352 _
\bu_
\br_
\be script with the _
\b-_
\b-_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\b-_
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs_
\be_
\bd flag), Mutt can open folders stored in
3353 an arbitrary format, provided that the user has a script to convert from/to
3354 this format to one of the accepted.
3356 The Mutt Next Generation E-Mail Client 67
3358 The most common use is to open compressed archived folders e.g. with gzip.
3360 In addition, the user can provide a script that gets a folder in an accepted
3361 format and appends its context to the folder in the user-defined format, which
3362 may be faster than converting the entire folder to the accepted format, append-
3363 ing to it and converting back to the user-defined format.
3365 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 67), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3366 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 67) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 68))
3367 which define commands to uncompress and compress a folder and to append mes-
3368 sages to an existing compressed folder respectively.
3372 open-hook \\.gz$ "gzip -cd %f > %t"
3373 close-hook \\.gz$ "gzip -c %t > %f"
3374 append-hook \\.gz$ "gzip -c %t >> %f"
3376 You do not have to specify all of the commands. If you omit _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (sec-
3377 tion 4.19.3 , page 68), the folder will be open and closed again each time you
3378 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 67) (or give
3379 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3380 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 68) though you'll be able to append to the folder.
3382 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3383 accepted formats. In particular, if the file is empty, mutt supposes it is not
3384 compressed. This is important because it allows the use of programs that do not
3385 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3386 prising if your compressing script produces empty files. In this situation,
3387 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.245 , page 147), so that the compressed file
3388 will be removed if you delete all of the messages.
3390 _
\b4_
\b._
\b1_
\b9_
\b._
\b1 _
\bO_
\bp_
\be_
\bn _
\ba _
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs_
\be_
\bd _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bf_
\bo_
\br _
\br_
\be_
\ba_
\bd_
\bi_
\bn_
\bg
3392 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3394 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3395 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3397 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3398 parameters: %f, which is replaced with the (compressed) folder name, and %t
3399 which is replaced with the name of the temporary folder to which to write.
3401 %f and %t can be repeated any number of times in the command string, and all of
3402 the entries are replaced with the appropriate folder name. In addition, %% is
3403 replaced by %, as in printf, and any other %anything is left as is.
3405 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should n
\bno
\bot
\bt remove the original compressed file. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should
3406 return non-zero exit status if it fails, so mutt knows something's wrong.
3410 The Mutt Next Generation E-Mail Client 68
3412 open-hook \\.gz$ "gzip -cd %f > %t"
3414 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3416 _
\b4_
\b._
\b1_
\b9_
\b._
\b2 _
\bW_
\br_
\bi_
\bt_
\be _
\ba _
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs_
\be_
\bd _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
3418 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3420 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3421 4.19.1 , page 67) command after some changes were made to it.
3423 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3424 whose names match _
\br_
\be_
\bg_
\be_
\bx_
\bp. It has the same format as in the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3425 4.19.1 , page 67) command. Temporary folder in this case is the folder previ-
3426 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 67) command.
3428 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should n
\bno
\bot
\bt remove the decompressed file. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should return
3429 non-zero exit status if it fails, so mutt knows something's wrong.
3433 close-hook \\.gz$ "gzip -c %t > %f"
3435 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3436 file can only be open in the readonly mode.
3438 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 67) is not called when you exit from the
3439 folder if the folder was not changed.
3441 _
\b4_
\b._
\b1_
\b9_
\b._
\b3 _
\bA_
\bp_
\bp_
\be_
\bn_
\bd _
\ba _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bt_
\bo _
\ba _
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs_
\be_
\bd _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
3443 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3445 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3446 is the command that can be used for appending to the folders whose names match
3447 _
\br_
\be_
\bg_
\be_
\bx_
\bp. It has the same format as in the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 67)
3448 command. The temporary folder in this case contains the messages that are
3451 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should n
\bno
\bot
\bt remove the decompressed file. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should return
3452 non-zero exit status if it fails, so mutt knows something's wrong.
3456 append-hook \\.gz$ "gzip -c %t >> %f"
3458 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 68) is used, the folder is not opened,
3459 which saves time, but this means that we can not find out what the folder type
3460 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.130 , page 119)) type is always
3462 The Mutt Next Generation E-Mail Client 69
3464 supposed (i.e. this is the format used for the temporary folder).
3466 If the file does not exist when you save to it, _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 ,
3467 page 67) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 68). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3468 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 68) is only for appending to existing folders.
3470 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3471 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3472 4.19.1 , page 67) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 67)respectively) each
3473 time you will add to it.
3475 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3477 The compressed folders support can also be used to handle encrypted folders. If
3478 you want to encrypt a folder with PGP, you may want to use the following hooks:
3480 open-hook \\.pgp$ "pgp -f < %f > %t"
3481 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3483 Please note, that PGP does not support appending to an encrypted folder, so
3484 there is no append-hook defined.
3486 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3487 can be read by your system administrator. So think about the security aspects
3490 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3492 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3493 MUA. Every effort has been made to provide the functionality that the discern-
3494 ing MIME user requires, and the conformance to the standards wherever possible.
3495 When configuring Mutt-ng for MIME, there are two extra types of configuration
3496 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3497 ping of file extensions to IANA MIME types. The other is the mailcap file,
3498 which specifies the external commands to use for handling specific MIME types.
3500 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3502 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3503 (while viewing a message), the attachment menu and the compose menu.
3505 _
\b5_
\b._
\b1_
\b._
\b1 _
\bV_
\bi_
\be_
\bw_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs _
\bi_
\bn _
\bt_
\bh_
\be _
\bp_
\ba_
\bg_
\be_
\br
3507 When you select a message from the index and view it in the pager, Mutt decodes
3508 the message to a text representation. Mutt-ng internally supports a number of
3509 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3510 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3512 The Mutt Next Generation E-Mail Client 70
3514 variety of PGP MIME types, including PGP/MIME and application/pgp.
3516 Mutt-ng will denote attachments with a couple lines describing them. These
3517 lines are of the form:
3519 [-- Attachment #1: Description --]
3520 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3522 Where the Description is the description or filename given for the attachment,
3523 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3525 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3527 [-- image/gif is unsupported (use 'v' to view this part) --]
3529 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3531 The default binding for view-attachments is `v', which displays the attachment
3532 menu for a message. The attachment menu displays a list of the attachments in
3533 a message. From the attachment menu, you can save, print, pipe, delete, and
3534 view attachments. You can apply these operations to a group of attachments at
3535 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3536 can also reply to the current message from this menu, and only the current
3537 attachment (or the attachments tagged) will be quoted in your reply. You can
3538 view attachments as text, or view them using the mailcap viewer definition.
3540 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3541 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3542 of type message/rfc822.
3544 See the help on the attachment menu for more information.
3546 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3548 The compose menu is the menu you see before you send a message. It allows you
3549 to edit the recipient list, the subject, and other aspects of your message. It
3550 also contains a list of the attachments of your message, including the main
3551 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3552 review, and rename an attachment or a list of tagged attachments. You can also
3553 modifying the attachment information, notably the type, encoding and descrip-
3556 Attachments appear as follows:
3558 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3559 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3561 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3562 or canceling) the message. It can be toggled with the toggle-unlink command
3563 (default: u). The next field is the MIME content-type, and can be changed with
3564 the edit-type command (default: ^T). The next field is the encoding for the
3566 The Mutt Next Generation E-Mail Client 71
3568 attachment, which allows a binary message to be encoded for transmission on
3569 7bit links. It can be changed with the edit-encoding command (default: ^E).
3570 The next field is the size of the attachment, rounded to kilobytes or
3571 megabytes. The next field is the filename, which can be changed with the
3572 rename-file command (default: R). The final field is the description of the
3573 attachment, and can be changed with the edit-description command (default: d).
3575 _
\b5_
\b._
\b2 _
\bM_
\bI_
\bM_
\bE _
\bT_
\by_
\bp_
\be _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bw_
\bi_
\bt_
\bh _
\bm_
\bi_
\bm_
\be_
\b._
\bt_
\by_
\bp_
\be_
\bs
3577 When you add an attachment to your mail message, Mutt-ng searches your personal
3578 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3579 /usr/local/share/mutt/mime.types or /etc/mime.types
3581 The mime.types file consist of lines containing a MIME type and a space sepa-
3582 rated list of extensions. For example:
3584 application/postscript ps eps
3586 audio/x-aiff aif aifc aiff
3588 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3589 tain most of the MIME types you are likely to use.
3591 If Mutt-ng can not determine the mime type by the extension of the file you
3592 attach, it will look at the file. If the file is free of binary information,
3593 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3594 the file contains binary information, then Mutt-ng will mark it as applica-
3595 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3596 attachment by using the edit-type command from the compose menu (default: ^T).
3597 The MIME type is actually a major mime type followed by the sub-type, separated
3598 by a '/'. 6 major types: application, text, image, video, audio, and model have
3599 been approved after various internet discussions. Mutt-ng recognises all of
3600 these if the appropriate entry is found in the mime.types file. It also recog-
3601 nises other major mime types, such as the chemical type that is widely used in
3602 the molecular modelling community to pass molecular data in various forms to
3603 various molecular viewers. Non-recognised mime types should only be used if the
3604 recipient of the message is likely to be expecting such attachments.
3606 _
\b5_
\b._
\b3 _
\bM_
\bI_
\bM_
\bE _
\bV_
\bi_
\be_
\bw_
\be_
\br _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bw_
\bi_
\bt_
\bh _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3608 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3609 format specified in Appendix A of RFC 1524. This file format is commonly
3610 referred to as the mailcap format. Many MIME compliant programs utilize the
3611 mailcap format, allowing you to specify handling for all MIME types in one
3612 place for all programs. Programs known to use this format include Netscape,
3613 XMosaic, lynx and metamail.
3615 In order to handle various MIME types that Mutt-ng can not handle internally,
3616 Mutt-ng parses a series of external configuration files to find an external
3618 The Mutt Next Generation E-Mail Client 72
3620 handler. The default search string for these files is a colon delimited list
3623 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3625 where $HOME is your home directory.
3627 In particular, the metamail distribution will install a mailcap file, usually
3628 as /usr/local/etc/mailcap, which contains some baseline entries.
3630 _
\b5_
\b._
\b3_
\b._
\b1 _
\bT_
\bh_
\be _
\bB_
\ba_
\bs_
\bi_
\bc_
\bs _
\bo_
\bf _
\bt_
\bh_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be
3632 A mailcap file consists of a series of lines which are comments, blank, or def-
3635 A comment line consists of a # character followed by anything you want.
3637 A blank line is blank.
3639 A definition line consists of a content type, a view command, and any number of
3640 optional fields. Each field of a definition line is divided by a semicolon ';'
3643 The content type is specified in the MIME standard type/subtype method. For
3644 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3645 mat includes two formats for wildcards, one using the special '*' subtype, the
3646 other is the implicit wild, where you only include the major type. For exam-
3647 ple, image/*, or video, will match all image types and video types, respec-
3650 The view command is a Unix command for viewing the type specified. There are
3651 two different types of commands supported. The default is to send the body of
3652 the MIME message to the command on stdin. You can change this behavior by using
3653 %s as a parameter to your view command. This will cause Mutt-ng to save the
3654 body of the MIME message to a temporary file, and then call the view command
3655 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3656 will turn over the terminal to the view program until the program quits, at
3657 which time Mutt will remove the temporary file if it exists.
3659 So, in the simplest form, you can send a text/plain message to the external
3660 pager more on stdin:
3664 Or, you could send the message as a file:
3668 Perhaps you would like to use lynx to interactively view a text/html message:
3672 The Mutt Next Generation E-Mail Client 73
3674 In this case, lynx does not support viewing a file from stdin, so you must use
3675 the %s syntax. N
\bNo
\bot
\bte
\be:
\b: _
\bS_
\bo_
\bm_
\be _
\bo_
\bl_
\bd_
\be_
\br _
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn_
\bs _
\bo_
\bf _
\bl_
\by_
\bn_
\bx _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn _
\ba _
\bb_
\bu_
\bg _
\bw_
\bh_
\be_
\br_
\be _
\bt_
\bh_
\be_
\by _
\bw_
\bi_
\bl_
\bl
3676 _
\bc_
\bh_
\be_
\bc_
\bk _
\bt_
\bh_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be _
\bf_
\bo_
\br _
\ba _
\bv_
\bi_
\be_
\bw_
\be_
\br _
\bf_
\bo_
\br _
\bt_
\be_
\bx_
\bt_
\b/_
\bh_
\bt_
\bm_
\bl_
\b. _
\bT_
\bh_
\be_
\by _
\bw_
\bi_
\bl_
\bl _
\bf_
\bi_
\bn_
\bd _
\bt_
\bh_
\be _
\bl_
\bi_
\bn_
\be
3677 _
\bw_
\bh_
\bi_
\bc_
\bh _
\bc_
\ba_
\bl_
\bl_
\bs _
\bl_
\by_
\bn_
\bx_
\b, _
\ba_
\bn_
\bd _
\br_
\bu_
\bn _
\bi_
\bt_
\b. _
\bT_
\bh_
\bi_
\bs _
\bc_
\ba_
\bu_
\bs_
\be_
\bs _
\bl_
\by_
\bn_
\bx _
\bt_
\bo _
\bc_
\bo_
\bn_
\bt_
\bi_
\bn_
\bu_
\bo_
\bu_
\bs_
\bl_
\by _
\bs_
\bp_
\ba_
\bw_
\bn _
\bi_
\bt_
\bs_
\be_
\bl_
\bf _
\bt_
\bo
3678 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3680 On the other hand, maybe you don't want to use lynx interactively, you just
3681 want to have it convert the text/html to text/plain, then you can use:
3683 text/html; lynx -dump %s | more
3685 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3686 text formats, then you would use the following:
3691 This is the simplest form of a mailcap file.
3693 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3695 The interpretation of shell meta-characters embedded in MIME parameters can
3696 lead to security problems in general. Mutt-ng tries to quote parameters in
3697 expansion of %s syntaxes properly, and avoids risky characters by substituting
3698 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.121 , page 118) variable.
3700 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3701 there are other applications parsing mailcap, maybe taking less care of it.
3702 Therefore you should pay attention to the following rules:
3704 _
\bK_
\be_
\be_
\bp _
\bt_
\bh_
\be _
\b%_
\b-_
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo_
\bs _
\ba_
\bw_
\ba_
\by _
\bf_
\br_
\bo_
\bm _
\bs_
\bh_
\be_
\bl_
\bl _
\bq_
\bu_
\bo_
\bt_
\bi_
\bn_
\bg_
\b. Don't quote them with single or
3705 double quotes. Mutt-ng does this for you, the right way, as should any other
3706 program which interprets mailcap. Don't put them into backtick expansions. Be
3707 highly careful with eval statements, and avoid them if possible at all. Trying
3708 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3709 tive to correct quoting in the first place.
3711 If you have to use the %-expandos' values in context where you need quoting or
3712 backtick expansions, put that value into a shell variable and reference the
3713 shell variable where necessary, as in the following example (using $charset
3714 inside the backtick expansion is safe, since it is not itself subject to any
3717 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3718 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3720 _
\b5_
\b._
\b3_
\b._
\b3 _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bU_
\bs_
\ba_
\bg_
\be
3722 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3724 The Mutt Next Generation E-Mail Client 74
3726 In addition to the required content-type and view command fields, you can add
3727 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3728 nizes the following optional fields:
3731 This flag tells Mutt-ng that the command passes possibly large
3732 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3733 (either the internal pager or the external pager defined by the
3734 pager variable) on the output of the view command. Without this
3735 flag, Mutt-ng assumes that the command is interactive. One could
3736 use this to replace the pipe to more in the lynx -dump example in
3739 text/html; lynx -dump %s ; copiousoutput
3741 This will cause lynx to format the text/html output as text/plain
3742 and Mutt-ng will use your standard pager to display the results.
3745 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3746 tion 5.4 , page 77), in order to decide whether it should honor
3747 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.339 , page 170) variable
3748 or not. When an attachment is viewed using an interactive program,
3749 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3750 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.339 , page 170) and the exit
3751 status of the program to decide if it will ask you to press a key
3752 after the external program has exited. In all other situations it
3753 will not prompt you for a key.
3756 This flag specifies the command to use to create a new attachment
3757 of a specific MIME type. Mutt-ng supports this from the compose
3760 composetyped=<command>
3761 This flag specifies the command to use to create a new attachment
3762 of a specific MIME type. This command differs from the compose
3763 command in that mutt will expect standard MIME headers on the data.
3764 This can be used to specify parameters, filename, description, etc.
3765 for a new attachment. Mutt-ng supports this from the compose
3769 This flag specifies the command to use to print a specific MIME
3770 type. Mutt-ng supports this from the attachment and compose menus.
3773 This flag specifies the command to use to edit a specific MIME
3774 type. Mutt-ng supports this from the compose menu, and also uses
3775 it to compose new attachments. Mutt-ng will default to the defined
3776 editor for text attachments.
3778 The Mutt Next Generation E-Mail Client 75
3780 nametemplate=<template>
3781 This field specifies the format for the file denoted by %s in the
3782 command fields. Certain programs will require a certain file
3783 extension, for instance, to correctly view a file. For instance,
3784 lynx will only interpret a file as text/html if the file ends in
3785 .html. So, you would specify lynx as a text/html viewer with a
3786 line in the mailcap file like:
3788 text/html; lynx %s; nametemplate=%s.html
3791 This field specifies a command to run to test whether this mailcap
3792 entry should be used. The command is defined with the command
3793 expansion rules defined in the next section. If the command
3794 returns 0, then the test passed, and Mutt-ng uses this entry. If
3795 the command returns non-zero, then the test failed, and Mutt-ng
3796 continues searching for the right entry. N
\bNo
\bot
\bte
\be:
\b: _
\bt_
\bh_
\be _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b-_
\bt_
\by_
\bp_
\be
3797 _
\bm_
\bu_
\bs_
\bt _
\bm_
\ba_
\bt_
\bc_
\bh _
\bb_
\be_
\bf_
\bo_
\br_
\be _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bp_
\be_
\br_
\bf_
\bo_
\br_
\bm_
\bs _
\bt_
\bh_
\be _
\bt_
\be_
\bs_
\bt_
\b. For example:
3799 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3802 In this example, Mutt-ng will run the program RunningX which will
3803 return 0 if the X Window manager is running, and non-zero if it
3804 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3805 display the text/html object. If RunningX doesn't return 0, then
3806 Mutt-ng will go on to the next entry and use lynx to display the
3809 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3811 When searching for an entry in the mailcap file, Mutt-ng will search for the
3812 most useful entry for its purpose. For instance, if you are attempting to
3813 print an image/gif, and you have the following entries in your mailcap file,
3814 Mutt-ng will search for an entry with the print command:
3817 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3820 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3823 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 77) to denote
3824 two commands for viewing an attachment, one to be viewed automatically, the
3825 other to be viewed interactively from the attachment menu. In addition, you
3826 can then use the test feature to determine which viewer to use interactively
3827 depending on your environment.
3829 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3830 text/html; lynx %s; nametemplate=%s.html
3832 The Mutt Next Generation E-Mail Client 76
3834 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3836 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 77), Mutt-ng will choose the third entry
3837 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3838 program RunningX to determine if it should use the first entry. If the program
3839 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3841 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3843 The various commands defined in the mailcap files are passed to the /bin/sh
3844 shell using the system() function. Before the command is passed to /bin/sh -c,
3845 it is parsed to expand various special parameters with information from Mutt-
3846 ng. The keywords Mutt-ng expands are:
3849 As seen in the basic mailcap section, this variable is expanded to
3850 a filename specified by the calling program. This file contains
3851 the body of the message to view/print/edit or where the composing
3852 program should place the results of composition. In addition, the
3853 use of this keyword causes Mutt-ng to not pass the body of the mes-
3854 sage to the view/print/edit program on stdin.
3857 Mutt-ng will expand %t to the text representation of the content
3858 type of the message in the same form as the first parameter of the
3859 mailcap definition line, ie text/html or image/gif.
3862 Mutt-ng will expand this to the value of the specified parameter
3863 from the Content-Type: line of the mail message. For instance, if
3864 Your mail message contains:
3866 Content-Type: text/plain; charset=iso-8859-1
3868 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3869 metamail mailcap file uses this feature to test the charset to
3870 spawn an xterm using the right charset to view the message.
3873 This will be replaced by a %
3875 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3876 1524. The main purpose of these parameters is for multipart messages, which is
3877 handled internally by Mutt-ng.
3879 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3881 This mailcap file is fairly simple and standard:
3883 The Mutt Next Generation E-Mail Client 77
3885 # I'm always running X :)
3886 video/*; xanim %s > /dev/null
3887 image/*; xv %s > /dev/null
3889 # I'm always running netscape (if my computer had more memory, maybe)
3890 text/html; netscape -remote 'openURL(%s)'
3892 This mailcap file shows quite a number of examples:
3894 # Use xanim to view all videos Xanim produces a header on startup,
3895 # send that to /dev/null so I don't see it
3896 video/*; xanim %s > /dev/null
3898 # Send html to a running netscape by remote
3899 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3901 # If I'm not running netscape but I am running X, start netscape on the
3903 text/html; netscape %s; test=RunningX
3905 # Else use lynx to view it as text
3908 # This version would convert the text/html to text/plain
3909 text/html; lynx -dump %s; copiousoutput
3911 # I use enscript to print text in two columns to a page
3912 text/*; more %s; print=enscript -2Gr %s
3914 # Netscape adds a flag to tell itself to view jpegs internally
3915 image/jpeg;xv %s; x-mozilla-flags=internal
3917 # Use xv to view images if I'm running X
3918 # In addition, this uses the \ to extend the line and set my editor
3920 image/*;xv %s; test=RunningX; \
3923 # Convert images to text using the netpbm tools
3924 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3925 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3927 # Send excel spreadsheets to my NT box
3928 application/ms-excel; open.pl %s
3930 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3932 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3933 viewer defined in the mailcap file, Mutt-ng has support for automatically
3935 The Mutt Next Generation E-Mail Client 78
3937 viewing MIME attachments while in the pager.
3939 To work, you must define a viewer in the mailcap file which uses the copi-
3940 ousoutput option to denote that it is non-interactive. Usually, you also use
3941 the entry to convert the attachment to a text representation which you can view
3944 You then use the auto_view muttrc command to list the content-types that you
3945 wish to view automatically.
3947 For instance, if you set auto_view to:
3949 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3951 Mutt-ng could use the following mailcap entries to automatically view attach-
3952 ments of these types.
3954 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3955 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3956 application/x-gunzip; gzcat; copiousoutput
3957 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3958 application/postscript; ps2ascii %s; copiousoutput
3960 ``unauto_view'' can be used to remove previous entries from the autoview list.
3961 This can be used with message-hook to autoview messages based on size, etc.
3962 ``unauto_view *'' will remove all previous entries.
3964 _
\b5_
\b._
\b5 _
\bM_
\bI_
\bM_
\bE _
\bM_
\bu_
\bl_
\bt_
\bi_
\bp_
\ba_
\br_
\bt_
\b/_
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be
3966 Mutt-ng has some heuristics for determining which attachment of a multi-
3967 part/alternative type to display. First, mutt will check the alternative_order
3968 list to determine if one of the available types is preferred. The alterna-
3969 tive_order list consists of a number of MIME types in order, including support
3970 for implicit and explicit wildcards, for example:
3972 alternative_order text/enriched text/plain text application/postscript image/*
3974 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
3975 5.4 , page 77), and use that. Failing that, Mutt-ng will look for any text
3976 type. As a last attempt, mutt will look for any type it knows how to handle.
3978 To remove a MIME type from the alternative_order list, use the unalterna-
3981 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
3983 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
3985 The Mutt Next Generation E-Mail Client 79
3987 treated according to their mailcap entry. This option is designed to deal with
3988 binary types such as application/octet-stream. When an attachment's mime-type
3989 is listed in mime_lookup, then the extension of the filename will be compared
3990 to the list of extensions in the mime.types file. The mime-type associated
3991 with this extension will then be used to process the attachment according to
3992 the rules in the mailcap file and according to any other configuration options
3993 (such as auto_view) specified. Common usage would be:
3995 mime_lookup application/octet-stream application/X-Lotus-Manuscript
3997 In addition, the unmime_lookup command may be used to disable this feature for
3998 any particular mime-type if it had been set, for example, in a global muttrc.
4000 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4002 First of all, mutt-ng contains no security holes included by intention but may
4003 contain unknown security holes. As a consequence, please run mutt-ng only with
4004 as few permissions as possible.
4006 Please do not run mutt-ng as the super user.
4008 When configuring mutt-ng, there're some points to note about secure setups.
4010 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
4011 mail user agents (in their default configuration) just by changing mutt-ng's
4012 configuration files: it then can execute arbitrary programs and scripts
4013 attached to messages, send out private data on its own, etc. Although this is
4014 not believed to the common type of setup, please read this chapter carefully.
4016 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
4018 Although mutt-ng can be told the various passwords for accounts, please never
4019 store passwords in configuration files. Besides the fact that the system's
4020 operator can always read them, you could forget to replace the actual password
4021 with asterisks when reporting a bug or asking for help via, for example, a
4022 mailing list so that your mail including your password could be archived by
4023 internet search engines, etc. Please never store passwords on disk.
4025 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
4027 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
4028 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.331 , page 169) variable can be used to
4029 change the default permissions of these files. Please only change it if you
4030 really know what you are doing. Also, a different location for these files may
4031 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.327 , page 168)
4034 The Mutt Next Generation E-Mail Client 80
4036 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
4038 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4040 In the default configuration, mutt-ng will leak some information to the outside
4041 world when sending messages: the generation of Message-ID: headers includes a
4042 step counter which is increased (and rotated) with every message sent. If you'd
4043 like to hide this information probably telling others how many mail you sent in
4044 which time, you at least need to remove the %P expando from the default setting
4045 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.147 , page 123) variable. Please make sure
4046 that you really know how local parts of these Message-ID: headers are composed.
4048 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
4050 As mutt-ng be can be set up to be the mail client to handle mailto: style links
4051 in websites, there're security considerations, too. To keep the old behavior by
4052 default, mutt-ng will be strict in interpreting them which means that arbitrary
4053 header fields can be embedded in these links which could override existing
4054 header fields or attach arbitrary files. This may be problematic if the
4055 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
4056 doesn't want to see header fields while editing the message.
4058 For example, following a link like
4060 mailto:joe@host?Attach=~/.gnupg/secring.gpg
4062 will send out the user's private gnupg keyring to joe@host if the user doesn't
4063 follow the information on screen carefully enough.
4065 When _
\bu_
\bn_
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg the _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo (section 7.4.315 , page 165) variable, mutt-
4068 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
4069 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
4071 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101) variable by force
4072 to let the user see all the headers (because they still may leak informa-
4075 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4077 Mutt-ng in many places has to rely on external applications or for convenience
4078 supports mechanisms involving external applications.
4080 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
4082 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
4083 set up to _
\ba_
\bu_
\bt_
\bo_
\bm_
\ba_
\bt_
\bi_
\bc_
\ba_
\bl_
\bl_
\by execute any given utility as listed in one of the mail-
4084 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.120 , page 117) variable for
4087 These utilities may have a variety of security vulnerabilities, including
4089 The Mutt Next Generation E-Mail Client 81
4091 overwriting of arbitrary files, information leaks or other exploitable bugs.
4092 These vulnerabilities may go unnoticed by the user, especially when they are
4093 called automatically (and without interactive prompting) from the mailcap
4094 file(s). When using mutt-ng's autoview mechanism in combination with mailcap
4095 files, please be sure to...
4097 +
\bo manually select trustworth applications with a reasonable calling sequence
4099 +
\bo periodically check the contents of mailcap files, especially after soft-
4100 ware installations or upgrades
4102 +
\bo keep the software packages referenced in the mailcap file up to date
4104 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.121 , page 118) variable in its
4105 default state to restrict mailcap expandos to a safe set of characters
4107 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
4109 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4112 The same security considerations apply for these as for tools involved via
4113 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4114 compressed folders support if the uncompressed mailbox is too large for the
4115 disk it is saved to.)
4117 As already noted, most of these problems are not built in but caused by wrong
4118 configuration, so please check your configuration.
4120 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4122 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4124 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4125 mailbox. However, it is possible to read other mailboxes and to send messages
4126 from the command line as well.
4128 The Mutt Next Generation E-Mail Client 82
4131 -a attach a file to a message
4132 -b specify a blind carbon-copy (BCC) address
4133 -c specify a carbon-copy (Cc) address
4134 -e specify a config command to be run after initialization files are read
4135 -f specify a mailbox to load
4136 -F specify an alternate file to read initialization commands
4137 -h print help on command line options
4138 -H specify a draft file from which to read a header and body
4139 -i specify a file to include in a message composition
4140 -m specify a default mailbox type
4141 -n do not read the system Muttngrc
4142 -p recall a postponed message
4143 -Q query a configuration variable
4144 -R open mailbox in read-only mode
4145 -s specify a subject (enclose in quotes if it contains spaces)
4146 -t dump the value of all variables to stdout
4147 -T dump the value of all changed variables to stdout
4148 -v show version number and compile-time definitions
4149 -x simulate the mailx(1) compose mode
4150 -y show a menu containing the files specified by the mailboxes command
4151 -z exit immediately if there are no messages in the mailbox
4152 -Z open the first folder with new message,exit immediately if none
4154 To read messages in a mailbox
4156 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4158 To compose a new message
4160 mutt [ -n ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -a _
\bf_
\bi_
\bl_
\be ] [ -c _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ] [ -i _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ] [ -s _
\bs_
\bu_
\bb_
\b-
4161 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4163 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4164 rect input from the file you wish to send. For example,
4166 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4168 This command will send a message to ``professor@bigschool.edu'' with a subject
4169 of ``data set for run #2''. In the body of the message will be the contents of
4170 the file ``~/run2.dat''.
4172 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4174 The Mutt Next Generation E-Mail Client 83
4177 ~b EXPR messages which contain EXPR in the message body
4178 ~B EXPR messages which contain EXPR in the whole message
4179 ~c USER messages carbon-copied to USER
4180 ~C EXPR message is either to: or cc: EXPR
4182 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4184 ~e EXPR message which contains EXPR in the ``Sender'' field
4186 ~f USER messages originating from USER
4187 ~g cryptographically signed messages
4188 ~G cryptographically encrypted messages
4189 ~H EXPR messages with a spam attribute matching EXPR
4190 ~h EXPR messages which contain EXPR in the message header
4191 ~k message contains PGP key material
4192 ~i ID message which match ID in the ``Message-ID'' field
4193 ~L EXPR message is either originated or received by EXPR
4194 ~l message is addressed to a known mailing list
4195 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4196 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4199 ~p message is addressed to you (consults alternates)
4200 ~P message is from you (consults alternates)
4201 ~Q messages which have been replied to
4203 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4204 ~S superseded messages
4205 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4207 ~t USER messages addressed to USER
4209 ~v message is part of a collapsed thread.
4210 ~V cryptographically verified messages
4211 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4212 (if compiled with NNTP support)
4213 ~x EXPR messages which contain EXPR in the `References' field
4214 ~y EXPR messages which contain EXPR in the `X-Label' field
4215 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4216 ~= duplicated messages (see $duplicate_threads)
4217 ~$ unreferenced messages (requires threaded view)
4218 ~* ``From'' contains realname and (syntactically) valid
4219 address (excluded are addresses matching against
4220 alternates or any alias)
4222 Where EXPR, USER, ID, and SUBJECT are _
\br_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs (section 4.1 , page
4223 47). Special attention has to be made when using regular expressions inside of
4224 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4225 level of backslash (\), which is normally used for quoting. If it is your
4226 intention to use a backslash in the regular expression, you will need to use
4227 two backslashes instead (\\).
4229 The Mutt Next Generation E-Mail Client 84
4231 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4233 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4235 The following are the commands understood by mutt.
4237 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 65) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4239 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 24) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4241 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 24) [ * | _
\bk_
\be_
\by ... ]
4243 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4245 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 32) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4247 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4249 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4251 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 68) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4253 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 77) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4255 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 77) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4257 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 25) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4259 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 27) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4261 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 67) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4263 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 29) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4265 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 29) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4267 +
\bo _
\be_
\bx_
\be_
\bc (section 3.25 , page 40) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4269 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4271 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4273 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 28) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4275 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 37) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4277 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 37) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4279 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 27) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4281 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 31) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4283 The Mutt Next Generation E-Mail Client 85
4285 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 31) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4287 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 34) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4289 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 34) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4291 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 28) _
\bm_
\be_
\bn_
\bu _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
4293 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 36) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4295 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 35) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4297 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4299 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4301 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4303 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.9 , page 29) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4305 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.9 , page 29) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4307 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 36) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4309 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 36) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4311 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 67) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4313 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.23 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4315 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 40) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4317 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.28 , page 43) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4319 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 37) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4321 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4323 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4325 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 38) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4327 +
\bo _
\br_
\be_
\bp_
\bl_
\by_
\b-_
\bh_
\bo_
\bo_
\bk (section , page ) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4329 +
\bo _
\bs_
\be_
\bt (section 3.28 , page 43) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4331 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.28 , page 43) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4333 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 44) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4335 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.27 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4337 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.27 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4339 The Mutt Next Generation E-Mail Client 86
4341 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 34) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4343 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 34) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4345 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.28 , page 43) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4347 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.30 , page 44) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4349 _
\b7_
\b._
\b4 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
4351 The following list contains all variables which, in the process of providing
4352 more consistency, have been renamed and are partially even removed already. The
4353 left column contains the old synonym variables, the right column the full/new
4356 The Mutt Next Generation E-Mail Client 87
4358 edit_hdrs edit_headers
4359 forw_decode forward_decode
4360 forw_format forward_format
4361 forw_quote forward_quote
4362 hdr_format index_format
4363 indent_str indent_string
4364 mime_fwd mime_forward
4365 msg_format message_format
4366 pgp_autosign crypt_autosign
4367 pgp_autoencrypt crypt_autoencrypt
4368 pgp_replyencrypt crypt_replyencrypt
4369 pgp_replysign crypt_replysign
4370 pgp_replysignencrypted crypt_replysignencrypted
4371 pgp_verify_sig crypt_verify_sig
4372 pgp_create_traditional pgp_autoinline
4373 pgp_auto_traditional pgp_replyinline
4374 forw_decrypt forward_decrypt
4375 smime_sign_as smime_default_key
4376 post_indent_str post_indent_string
4377 print_cmd print_command
4378 shorten_hierarchy sidebar_shorten_hierarchy
4379 ask_followup_to nntp_ask_followup_to
4380 ask_x_comment_to nntp_ask_x_comment_to
4381 catchup_newsgroup nntp_catchup
4382 followup_to_poster nntp_followup_to_poster
4383 group_index_format nntp_group_index_format
4385 mime_subject nntp_mime_subject
4386 news_cache_dir nntp_cache_dir
4387 news_server nntp_host
4389 nntp_poll nntp_mail_check
4390 pop_checkinterval pop_mail_check
4391 post_moderated nntp_post_moderated
4392 save_unsubscribed nntp_save_unsubscribed
4393 show_new_news nntp_show_new_news
4394 show_only_unread nntp_show_only_unread
4395 x_comment_to nntp_x_comment_to
4396 smtp_auth_username smtp_user
4397 smtp_auth_password smtp_pass
4399 The contrib subdirectory contains a script named update-config.pl which eases
4402 A complete list of current variables follows.
4404 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
4410 This variable specifies whether to abort sending if no attachment was made but
4412 The Mutt Next Generation E-Mail Client 88
4414 the content references them, i.e. the content matches the regular expression
4415 given in _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 91). If a match was
4416 found and this variable is set to _
\by_
\be_
\bs, message sending will be aborted but the
4417 mail will be send nevertheless if set to _
\bn_
\bo.
4419 This variable and _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 91) are
4420 intended to remind the user to attach files if the message's text references
4423 See also the _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 91) variable.
4425 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4431 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4432 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4433 subject given at the subject prompt will never be aborted.
4435 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4441 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4442 body if no changes are made to the file (this check only happens after the
4443 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4445 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bg_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4451 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
4452 cating which version of Mutt-ng was used for composing them.
4454 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4458 Default: '~/.muttngrc'
4460 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4461 tion 2.5.4 , page 11)'' function.
4463 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4464 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 44)'' command for it to be executed.
4466 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4468 The Mutt Next Generation E-Mail Client 89
4472 Default: '%4n %2f %t %-10a %r'
4474 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4475 ing printf(3)-style sequences are available:
4481 flags - currently, a 'd' for an alias marked for deletion
4487 address which alias expands to
4490 character which indicates if the alias is tagged for inclusion
4492 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4498 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4499 or base64 encoding when sending mail.
4501 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4507 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4508 sages) are to be interpreted. Messages containing these codes are rare, but if
4509 this option is set, their text will be colored accordingly. Note that this may
4510 override your color choices, and even present a security problem, since a mes-
4511 sage could include a line like ``[-- PGP output follows ...' and give it the
4512 same color as your attachment color.
4514 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4520 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4521 instead of highlighting the whole line. On slow network or modem links this
4522 will make response faster because there is less that has to be redrawn on the
4523 screen when moving to the next or previous entries in the menu.
4525 The Mutt Next Generation E-Mail Client 90
4527 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4533 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4534 attachment trees, instead of the default ACS characters.
4536 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4542 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4543 editing an outgoing message.
4545 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bs_
\bk_
\bc_
\bc
4551 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4552 the body of an outgoing message.
4554 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4560 This variable is a colon-separated list of character encoding schemes for mes-
4561 sages without character encoding indication. Header field values and message
4562 body content without character encoding indication would be assumed that they
4563 are written in one of this list. By default, all the header fields and message
4564 body without any charset indication are assumed to be in us-ascii.
4566 For example, Japanese users might prefer this:
4568 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4570 However, only the first content is valid for the message body. This variable
4571 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.316 , page 166) is unset.
4573 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4577 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4579 This variable describes the format of the ``attachment'' menu. The following
4580 printf(3)-style sequences are understood:
4582 The Mutt Next Generation E-Mail Client 91
4588 requires charset conversion (n or c)
4597 MIME Content-Transfer-Encoding: header field
4603 MIME Content-Disposition: header field (I=inline, A=attachment)
4621 graphic tree characters
4624 unlink (=to delete) flag
4627 right justify the rest of the string and pad with character 'X'
4630 pad to the end of the line with character 'X'
4632 _
\b7_
\b._
\b4_
\b._
\b1_
\b5 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
4634 Type: regular expression
4638 The Mutt Next Generation E-Mail Client 92
4640 If this variable is non-empty, muttng will scan a message's contents before
4641 sending for this regular expression. If it is found, it will ask for what to do
4642 depending on the setting of _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 87).
4644 This variable and _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 87) are intended to
4645 remind the user to attach files if the message's text references them.
4647 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4653 The separator to add between attachments when operating (saving, printing, pip-
4654 ing, etc) on a list of tagged attachments.
4656 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4662 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4663 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4664 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.16 ,
4665 page 92)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4666 operate on the attachments one by one.
4668 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4672 Default: 'On %d, %n wrote:'
4674 This is the string that will precede a message which has been included in a
4675 reply. For a full listing of defined printf(3)-like sequences see the section
4676 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114)''.
4678 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4684 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4685 all tagged messages (if there are any). When unset, you must first use the
4686 ``tag-prefix'' function (default: ';') to make the next function apply to all
4689 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4695 The Mutt Next Generation E-Mail Client 93
4697 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101)'', Mutt-ng
4698 will skip the initial send-menu and allow you to immediately begin editing the
4699 body of your message. The send-menu may still be accessed once you have fin-
4700 ished editing the body of your message.
4702 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.64 , page 102)''.
4704 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\be_
\be_
\bp
4710 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4712 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4718 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4719 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4720 tion 7.4.21 , page 93)'' variable.
4722 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4728 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4729 you don't get asked if you want to bounce a message. Setting this variable to
4730 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4733 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4739 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4740 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4742 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4748 When this variable is set, mutt will place the cursor at the beginning of the
4749 current line in menus, even when the arrow_cursor variable is unset, making it
4750 easier for blind persons using Braille displays to follow these menus. The
4752 The Mutt Next Generation E-Mail Client 94
4754 option is disabled by default because many visual terminals don't permit making
4755 the cursor invisible.
4757 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4761 Default: '~/.mutt_certificates'
4763 Availability: SSL or GNUTLS
4765 This variable specifies the file where the certificates you trust are saved.
4766 When an unknown certificate is encountered, you are asked if you accept it or
4767 not. If you accept it, the certificate can also be saved in this file and fur-
4768 ther connections are automatically accepted.
4770 You can also manually add CA certificates in this file. Any server certificate
4771 that is signed with one of these CA certificates are also automatically
4774 Example: set certificate_file=~/.muttng/certificates
4776 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4782 Character set your terminal uses to display and enter textual data.
4784 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4790 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4792 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4793 Especially with MH mailboxes, this operation can take quite some time since it
4794 involves scanning the directory and checking each file to see if it has already
4795 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4798 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4804 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4807 The Mutt Next Generation E-Mail Client 95
4809 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4813 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4815 Controls the format of the status line displayed in the ``compose'' menu. This
4816 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.313 , page 163)'', but has
4817 its own set of printf(3)-like sequences:
4820 total number of attachments
4826 approximate size (in bytes) of the current message
4829 Mutt-ng version string
4831 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.313 , page 163)''
4832 option for more information on how to set ``_
\b$_
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.30 ,
4835 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4841 When defined, Mutt-ng will recode commands in rc files from this encoding.
4843 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4849 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4852 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4858 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4859 box which does not yet exist before creating it.
4861 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4863 The Mutt Next Generation E-Mail Client 96
4869 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4870 many seconds if the connection is not able to be established. A negative value
4871 causes Mutt-ng to wait indefinitely for the connection to succeed.
4873 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4877 Default: 'text/plain'
4879 Sets the default Content-Type: header field for the body of newly composed mes-
4882 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\bo_
\bp_
\by
4888 This variable controls whether or not copies of your outgoing messages will be
4889 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.235 , page
4890 144)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.246 , page 147)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4891 7.4.72 , page 105)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38)''.
4893 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4899 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4900 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4901 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4902 required or signing is requested as well. If ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section
4903 7.4.282 , page 155)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4904 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4907 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4913 This variable controls whether or not Mutt-ng may automatically enable PGP
4914 encryption/signing for messages. See also ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section
4915 7.4.37 , page 96)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 97)'',
4916 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 96)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4917 7.4.42 , page 97)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.282 , page 155)''.
4919 The Mutt Next Generation E-Mail Client 97
4921 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4927 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4928 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4929 signing is not required or encryption is requested as well. If
4930 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.282 , page 155)'' is _
\bs_
\be_
\bt, then OpenSSL is
4931 used instead to create S/MIME messages and settings can be overridden by use of
4932 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4934 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4940 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4941 encryption/signing for messages. See also ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section
4942 7.4.37 , page 96)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 97)'',
4943 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 96)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4944 7.4.42 , page 97)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.282 , page 155)''.
4946 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4952 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
4953 encrypted. (Crypto only)
4955 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
4961 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
4963 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
4966 _
\b7_
\b._
\b4_
\b._
\b4_
\b3 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd
4972 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
4973 encrypted. This makes sense in combination with ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section
4974 7.4.41 , page 97)'', because it allows you to sign all messages which are
4976 The Mutt Next Generation E-Mail Client 98
4978 automatically encrypted. This works around the problem noted in
4979 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.42 , page 97)'', that Mutt-ng is not able to
4980 find out whether an encrypted message is also signed. (Crypto only)
4982 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
4988 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
4989 S/MIME output, so spoofing such lines is more difficult. If you are using col-
4990 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
4993 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
4999 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
5000 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
5001 will be used instead of the classic code.
5003 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
5004 won't have any effect when used interactively.
5006 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
5012 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
5013 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
5014 cryptographic signatures. (Crypto only)
5016 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5020 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
5022 This variable controls the format of the date printed by the ``%d'' sequence in
5023 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114)''. This is passed to strftime(3)
5024 to process the date.
5026 Unless the first character in the string is a bang (``!''), the month and week
5027 day names are expanded according to the locale specified in the variable
5028 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.118 , page 117)''. If the first character in the string
5029 is a bang, the bang is discarded, and the month and week day names in the rest
5030 of the string are expanded in the _
\bC locale (that is in US English).
5032 The Mutt Next Generation E-Mail Client 99
5034 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
5038 Default: '~f %s !~P | (~P ~C %s)'
5040 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
5041 will be interpreted if they are specified with only a simple regexp, instead of
5042 a matching pattern. The hooks are expanded when they are declared, so a hook
5043 will be interpreted according to the value of this variable at the time the
5044 hook is declared. The default value matches if the message is either from a
5045 user matching the regular expression given, or if it is from you (if the from
5046 address matches ``alternates'') and is to or cc'ed to a user matching the given
5049 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\be_
\bl_
\be_
\bt_
\be
5055 Controls whether or not messages are really deleted when closing or synchroniz-
5056 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
5057 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
5058 be kept in the mailbox.
5060 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be
5066 When sending messages with format=flowed by _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg the _
\b$_
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd (section
5067 7.4.322 , page 167) variable, this variable specifies whether to also set the
5068 DelSp parameter to yes. If this is _
\bu_
\bn_
\bs_
\be_
\bt, no additional parameter will be send
5069 as a value of no already is the default behavior.
5071 N
\bNo
\bot
\bte
\be:
\b: this variable only has an effect on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages (if _
\b$_
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
5072 (section 7.4.322 , page 167) is _
\bs_
\be_
\bt) but not on incomming.
5074 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
5080 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
5081 tion. This applies when you either explicitly delete a message, or when you
5082 save it to another folder.
5084 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
5088 The Mutt Next Generation E-Mail Client 100
5092 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
5093 subparts of individual messages in a multipart/digest. To see these subparts,
5094 press 'v' on that menu.
5096 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
5102 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
5103 viewed it is passed as standard input to _
\b$_
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br (section 7.4.53 ,
5104 page 100), and the filtered message is read from the standard output.
5106 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
5110 Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
5112 Availability: Standalone and Dotlock
5114 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
5116 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
5122 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5123 or in connection with the SMTP support via libESMTP.
5125 This variable sets the request for when notification is returned. The string
5126 consists of a comma separated list (no spaces!) of one or more of the follow-
5127 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
5128 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
5129 notified of successful transmission.
5131 Example: set dsn_notify='failure,delay'
5133 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
5139 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5140 or in connection with the SMTP support via libESMTP.
5142 This variable controls how much of your message is returned in DSN messages.
5143 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
5145 The Mutt Next Generation E-Mail Client 101
5147 return the full message.
5149 Example: set dsn_return=hdrs
5151 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
5157 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
5158 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
5159 indicate that it thinks they are duplicates of each other with an equals sign
5160 in the thread diagram.
5162 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5168 This option allows you to edit the header of your outgoing messages along with
5169 the body of your message.
5171 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5177 This variable specifies which editor is used by Mutt-ng. It defaults to the
5178 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5179 if neither of those are set.
5181 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5187 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5188 string ``From '' (note the trailing space) in the beginning of a line. Useful
5189 to avoid the tampering certain mail delivery and transport agents tend to do
5192 N
\bNo
\bot
\bte
\be:
\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
5193 <em/strongly/ advised to _
\bs_
\be_
\bt this option although discouraged by the standard.
5194 Alternatively, you must take care of space-stuffing <tt/From / lines (with a
5195 trailing space) yourself.
5197 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5201 The Mutt Next Generation E-Mail Client 102
5207 The file which includes random data that is used to initialize SSL library
5210 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5216 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5217 ``From:'' header field. Note that this information is passed to the sendmail
5218 command using the ``-f' command line switch, so don't set this option if you
5219 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.252 , page 148) yourself, or
5220 if the sendmail on your machine doesn't support that command line switch.
5222 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5228 Escape character to use for functions in the builtin editor.
5230 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5236 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5237 ing to messages, and the initial prompt for subject is skipped when forwarding
5240 N
\bNo
\bot
\bte
\be:
\b: this variable has no effect when the ``_
\b$_
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt (section 7.4.20 , page
5241 92)'' variable is _
\bs_
\be_
\bt.
5243 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5249 This variable controls whether or not attachments on outgoing messages are
5250 saved along with the main body of your message.
5252 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5258 The Mutt Next Generation E-Mail Client 103
5260 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5261 when the actual message is encrypted and/or signed. (PGP only)
5263 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5269 This variable is a colon-separated list of character encoding schemes for text
5270 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.27 , page 94) value will
5271 be used instead. For example, the following configuration would work for
5272 Japanese text handling:
5274 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5276 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5279 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5285 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5286 beginning of a pathname will be expanded to the value of this variable. Note
5287 that if you change this variable from the default value you need to make sure
5288 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5289 ables since expansion takes place during the ``set'' command.
5291 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5295 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5297 This variable allows you to customize the file browser display to your personal
5298 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page
5299 114)'', but has its own set of printf(3)-like sequences:
5305 date/time folder was last modified
5313 The Mutt Next Generation E-Mail Client 104
5316 group name (or numeric gid, if missing)
5319 number of hard links
5322 N if folder has new mail, blank otherwise
5328 * if the file is tagged, blank otherwise
5331 owner name (or numeric uid, if missing)
5334 right justify the rest of the string and pad with character 'X'
5337 pad to the end of the line with character 'X'
5339 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5345 Controls whether or not the Mail-Followup-To: header field is generated when
5346 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5347 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5348 3.13 , page 34)'' commands or detected by common mailing list headers.
5350 This field has two purposes. First, preventing you from receiving duplicate
5351 copies of replies to messages which you send to mailing lists. Second, ensuring
5352 that you do get a reply separately for any messages sent to known lists to
5353 which you are not subscribed. The header will contain only the list's address
5354 for subscribed lists, and both the list address and your own email address for
5355 unsubscribed lists. Without this header, a group reply to your message sent to
5356 a subscribed list will be sent to both the list and your address, resulting in
5357 two copies of the same email for you.
5359 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5365 When _
\bs_
\be_
\bt, it causes Mutt-ng to check for new mail when the _
\bb_
\bu_
\bf_
\bf_
\by_
\b-_
\bl_
\bi_
\bs_
\bt command
5366 is invoked. When _
\bu_
\bn_
\bs_
\be_
\bt, _
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bl_
\bi_
\bs_
\bt will just list all mailboxes which are
5367 already known to have new mail.
5369 The Mutt Next Generation E-Mail Client 105
5371 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.326 , page 168)'',
5372 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.119 , page 117)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5373 7.4.103 , page 111)''.
5375 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5381 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.246 , page 147)'',
5382 except that Mutt-ng will store a copy of your outgoing message by the username
5383 of the address you are sending to even if that mailbox does not exist.
5385 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.235 , page 144)'' variable.
5387 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5393 Controls the decoding of complex MIME messages into text/plain when forwarding
5394 a message. The message header is also RFC2047 decoded. This variable is only
5395 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.141 , page 121)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5396 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.142 , page 122)'' is used instead.
5398 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5404 Controls the handling of encrypted messages when forwarding a message. When
5405 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5406 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.141 , page 121)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5407 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.142 , page 122)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5409 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5415 This quadoption controls whether or not the user is automatically placed in the
5416 editor when forwarding messages. For those who always want to forward with no
5417 modification, use a setting of _
\bn_
\bo.
5419 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5425 The Mutt Next Generation E-Mail Client 106
5427 This variable controls the default subject when forwarding a message. It uses
5428 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page
5431 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5437 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5438 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.141 , page 121)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5439 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.113 , page 114)''.
5441 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bf_
\br_
\bo_
\bm
5443 Type: e-mail address
5447 This variable contains a default from address. It can be overridden using
5448 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.241 , page
5449 146)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.335 , page
5452 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5453 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5454 takes this email address.
5456 Defaults to the contents of the environment variable $EMAIL.
5458 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5460 Type: regular expression
5464 A regular expression used by Mutt-ng to parse the GECOS field of a password
5465 entry when expanding the alias. By default the regular expression is set to
5466 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5467 the GECOS field contains a string like 'lastname, firstname' then you should
5468 do: set gecos_mask='.*'.
5470 This can be useful if you see the following behavior: you address a e-mail to
5471 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5472 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5473 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5474 to ``Franklin, Steve''.
5476 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bh_
\bd_
\br_
\bs
5482 The Mutt Next Generation E-Mail Client 107
5484 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 ,
5485 page 36)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5486 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5487 defined header fields are added to every new message.
5489 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5495 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5496 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.340 , page
5497 171)'' setting applies.
5499 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5505 Availability: Header Cache
5507 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.82 , page 107) variable points to the header
5510 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.82 , page 107) points to a directory it will
5511 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5512 7.4.82 , page 107) points to a file that file will be a single global header
5513 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5515 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5521 If enabled the header cache will be compressed. So only one fifth of the usual
5522 diskspace is used, but the uncompression can result in a slower open of the
5525 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\be_
\bl_
\bp
5531 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5532 by each menu are displayed on the first line of the screen.
5534 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5535 sequence rather than a single keystroke. Also, the help line may not be
5536 updated if a binding is changed while Mutt-ng is running. Since this variable
5537 is primarily aimed at new users, neither of these should present a major
5539 The Mutt Next Generation E-Mail Client 108
5543 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5549 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5550 7.4.93 , page 109)'' variable when adding the domain part to addresses. This
5551 variable does not affect the generation of Message-ID: header fields, and it
5552 will not lead to the cut-off of first-level domains.
5554 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5560 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5561 limiting, in the thread tree.
5563 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5569 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5572 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5578 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5579 have the same subject as their parent or closest previously displayed sibling.
5581 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5587 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5588 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5589 _
\bi_
\bn_
\bg (section 7.4.87 , page 108) is set, this option will have no effect.
5591 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5595 The Mutt Next Generation E-Mail Client 109
5599 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5600 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.86 ,
5601 page 108) is _
\bs_
\be_
\bt, this option will have no effect.
5603 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5609 This variable controls the size (in number of strings remembered) of the string
5610 history buffer. The buffer is cleared each time the variable is changed.
5612 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5618 This variable controls whether or not a Mail-Followup-To: header field is hon-
5619 ored when group-replying to a message.
5621 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5627 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5628 during generation of Message-Id: headers.
5630 Please be sure to really know what you are doing when changing this variable to
5631 configure a custom domain part of Message-IDs.
5633 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5639 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5640 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5641 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5642 header field was set by the mailing list to automate responses to the list, and
5643 will ignore this field. To direct a response to the mailing list when this
5644 option is set, use the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by function; _
\bg_
\br_
\bo_
\bu_
\bp_
\b-_
\br_
\be_
\bp_
\bl_
\by will reply to both the
5645 sender and the list.
5647 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5651 The Mutt Next Generation E-Mail Client 110
5657 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5658 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5659 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5660 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5661 eter is case-insensitive.
5663 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5664 ods, in order from most-secure to least-secure.
5666 Example: set imap_authenticators='gssapi:cram-md5:login'
5668 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5669 ous methods are unavailable. If a method is available but authentication fails,
5670 Mutt-ng will not connect to the IMAP server.
5672 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5678 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5679 connection, and add them to the set of mailboxes it polls for new mail. See
5680 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 36)'' command.
5682 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5690 This contains the list of characters which you would like to treat as folder
5691 separators for displaying IMAP paths. In particular it helps in using the '='
5692 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.68 , page 103) variable.
5694 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5702 Mutt-ng requests these header fields in addition to the default headers (``DATE
5703 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5704 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5705 ``index'' menu. You may want to add more headers for spam detection.
5707 The Mutt Next Generation E-Mail Client 111
5709 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5711 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5719 You normally want to see your personal folders alongside your INBOX in the IMAP
5720 browser. If you see something else, you may set this variable to the IMAP path
5723 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5731 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5732 wait before polling open IMAP connections, to prevent the server from closing
5733 them before Mutt-ng has finished with them.
5735 The default is well within the RFC-specified minimum amount of time (30 min-
5736 utes) before a server is allowed to do this, but in practice the RFC does get
5737 violated every now and then.
5739 Reduce this number if you find yourself getting disconnected from your IMAP
5740 server due to inactivity.
5742 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5750 This variable configures whether IMAP folder browsing will look for only sub-
5751 scribed folders or all folders. This can be toggled in the IMAP browser with
5752 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5754 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5762 Your login name on the IMAP server.
5764 The Mutt Next Generation E-Mail Client 112
5766 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.109 , page
5769 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5775 This variable configures how often (in seconds) Mutt-ng should look for new
5776 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.119 ,
5777 page 117)'' variable to generate less traffic and get more accurate information
5780 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5788 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5789 you for your password when you invoke the fetch-mail function.
5791 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5792 machine, because the superuser can read your configuration even if you are the
5793 only one who can read the file.
5795 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5803 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5804 Mutt-ng will only check for new mail over existing IMAP connections. This is
5805 useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
5806 cation, or if opening the connection is slow.
5808 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5816 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5817 fetch a message from the server. This is generally a good thing, but can make
5818 closing an IMAP folder somewhat slower. This option exists to appease speed
5821 The Mutt Next Generation E-Mail Client 113
5823 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5831 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5834 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5842 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5843 messages. Since these messages are often harmless, or generated due to configu-
5844 ration problems on the server which are out of the users' hands, you may wish
5845 to suppress them at some point.
5847 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5855 The name of the user whose mail you intend to access on the IMAP server.
5857 This variable defaults to your user name on the local machine.
5859 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5865 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5866 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5867 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5868 convert the body part to text form.
5870 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5876 Controls whether or not a copy of the message(s) you are replying to is
5878 The Mutt Next Generation E-Mail Client 114
5880 included in your reply.
5882 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5888 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5889 sage you are replying.
5891 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5897 Specifies the string to prepend to each line of text quoted in a message to
5898 which you are replying. You are strongly encouraged not to change this value,
5899 as it tends to agitate the more fanatical netizens.
5901 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5905 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5907 This variable allows you to customize the message index display to your per-
5910 ``Format strings'' are similar to the strings used in the ``C'' function
5911 printf(3) to format output (see the man page for more detail). The following
5912 sequences are defined in Mutt-ng:
5915 address of the author
5918 reply-to address (if present; otherwise: address of author)
5921 filename of the original message folder (think mailBox)
5924 the list to which the letter was sent, or else the folder name
5928 number of characters (bytes) in the message
5931 current message number
5933 The Mutt Next Generation E-Mail Client 115
5936 date and time of the message in the format specified by ``date_for-
5937 mat'' converted to sender's time zone
5940 date and time of the message in the format specified by ``date_for-
5941 mat'' converted to the local time zone
5944 current message number in thread
5947 number of messages in current thread
5950 entire From: line (address + real name)
5953 author name, or recipient name if the message is from you
5956 spam attribute(s) of this message
5959 newsgroup name (if compiled with nntp support)
5962 message-id of the current message
5965 number of lines in the message (does not work with maildir, mh, and
5966 possibly IMAP folders)
5969 If an address in the To or CC header field matches an address
5970 defined by the users ``subscribe'' command, this displays 'To
5971 <list-name>', otherwise the same as %F.
5974 total number of message in the mailbox
5977 number of hidden messages if the thread is collapsed.
5983 author's real name (or address if missing)
5986 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
5987 the message: list name or recipient name if no list
5989 The Mutt Next Generation E-Mail Client 116
5992 subject of the message
5995 status of the message (N/D/d/!/r/*)
5998 `to:' field (recipients)
6001 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.328 ,
6005 user (login) name of the author
6008 first name of the author, or the recipient if the message is from
6012 name of organization of author (`organization:' field)
6015 `x-label:' field, if present
6018 `x-label' field, if present, and (1) not at part of a thread tree,
6019 (2) at the top of a thread, or (3) `x-label' is different from pre-
6020 ceding message's `x-label'.
6023 message status flags
6026 the date and time of the message is converted to sender's time
6027 zone, and ``fmt'' is expanded by the library function ``strftime'';
6028 a leading bang disables locales
6031 the date and time of the message is converted to the local time
6032 zone, and ``fmt'' is expanded by the library function ``strftime'';
6033 a leading bang disables locales
6036 the local date and time when the message was received. ``fmt'' is
6037 expanded by the library function ``strftime''; a leading bang dis-
6041 the current local time. ``fmt'' is expanded by the library function
6042 ``strftime''; a leading bang disables locales.
6044 The Mutt Next Generation E-Mail Client 117
6047 right justify the rest of the string and pad with character 'X'
6050 pad to the end of the line with character 'X'
6052 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.328 , page 168)''.
6054 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
6060 How to invoke ispell (GNU's spell-checking software).
6062 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6068 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
6069 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.129 , page 119)'' mailbox, or as a result of
6070 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 35)'' command.
6072 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
6078 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
6079 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
6080 will ask if you really intended to reply to the author only.
6082 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
6088 The locale used by strftime(3) to format dates. Legal values are the strings
6089 your system accepts for the locale variable LC_TIME.
6091 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6097 This variable configures how often (in seconds) Mutt-ng should look for new
6100 The Mutt Next Generation E-Mail Client 118
6102 N
\bNo
\bot
\bte
\be:
\b: This does not apply to IMAP mailboxes, see _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
6103 7.4.103 , page 111).
6105 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
6111 This variable specifies which files to consult when attempting to display MIME
6112 bodies not directly supported by Mutt-ng.
6114 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
6120 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
6121 well-defined set of safe characters. This is the safe setting, but we are not
6122 sure it doesn't break some more advanced MIME stuff.
6124 D
\bDO
\bON
\bN'
\b'T
\bT C
\bCH
\bHA
\bAN
\bNG
\bGE
\bE T
\bTH
\bHI
\bIS
\bS S
\bSE
\bET
\bTT
\bTI
\bIN
\bNG
\bG U
\bUN
\bNL
\bLE
\bES
\bSS
\bS Y
\bYO
\bOU
\bU A
\bAR
\bRE
\bE R
\bRE
\bEA
\bAL
\bLL
\bLY
\bY S
\bSU
\bUR
\bRE
\bE W
\bWH
\bHA
\bAT
\bT Y
\bYO
\bOU
\bU A
\bAR
\bRE
\bE D
\bDO
\bOI
\bIN
\bNG
\bG!
\b!
6126 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by
6132 Availability: Header Cache
6134 Check for Maildir unaware programs other than Mutt-ng having modified maildir
6135 files when the header cache is in use. This incurs one stat(2) per message
6136 every time the folder is opened.
6138 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
6144 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
6145 flag instead of physically deleted.
6147 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
6148 effect on other mailbox types.
6150 It is similiar to the trash option.
6152 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
6156 The Mutt Next Generation E-Mail Client 119
6160 Controls whether or not Mutt-ng marks _
\bn_
\be_
\bw u
\bun
\bnr
\bre
\bea
\bad
\bd messages as _
\bo_
\bl_
\bd if you exit a
6161 mailbox without reading them.
6163 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
6164 up with an 'O' next to them in the ``index'' menu, indicating that they are
6167 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
6173 Controls the display of wrapped lines in the internal pager. If set, a ``+''
6174 marker is displayed at the beginning of wrapped lines. Also see the
6175 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.268 , page 152)'' variable.
6177 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\ba_
\bs_
\bk
6179 Type: regular expression
6183 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6184 operator ``!''. Only files whose names match this mask will be shown. The
6185 match is always case-sensitive.
6187 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6193 When set non-zero, this specifies the maximum number of recipient header lines
6194 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6195 case the number of lines exeeds its value, the last line will have 3 dots
6198 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6204 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6205 is limited to this length. A value of 0 (which is also the default) means that
6206 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6207 (section 7.4.342 , page 171).
6209 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\bb_
\bo_
\bx
6213 The Mutt Next Generation E-Mail Client 120
6217 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6218 7.4.302 , page 160)'' folder will be appended.
6220 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6226 The default mailbox type used when creating new folders. May be any of mbox,
6227 MMDF, MH and Maildir.
6229 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6235 This variable controls the number of lines of context that are given when
6236 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.172 , page
6239 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6245 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6246 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6247 entry may move off the bottom.
6249 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6255 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6256 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6257 vious page of the menu is displayed (useful for slow links to avoid many
6260 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6266 This is the string displayed in the ``attachment'' menu for attachments of type
6267 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6268 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114)''.
6270 The Mutt Next Generation E-Mail Client 121
6272 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6278 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6279 if the user had pressed the ESC key and whatever key remains after having the
6280 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6281 then this is treated as if the user had pressed ESC then ``x''. This is
6282 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6283 the ASCII character ``x''.
6285 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\be_
\bt_
\bo_
\bo
6291 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6292 from the list of recipients when replying to a message.
6294 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6300 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6301 _
\b,_
\b<_
\bo_
\bl_
\bd _
\bf_
\bi_
\bl_
\be _
\bn_
\ba_
\bm_
\be_
\b> in mh folders instead of really deleting them. If the vari-
6302 able is set, the message files will simply be deleted.
6304 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6310 The name of the MH sequence used for flagged messages.
6312 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6318 The name of the MH sequence used to tag replied messages.
6320 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6326 The Mutt Next Generation E-Mail Client 122
6328 The name of the MH sequence used for unseen messages.
6330 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6336 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6337 part instead of included in the main body of the message.
6339 This is useful for forwarding MIME messages so the receiver can properly view
6340 the message as it was delivered to you. If you like to switch between MIME and
6341 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6343 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.73 , page 105)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6344 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.142 , page 122)''.
6346 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6352 Controls the decoding of complex MIME messages into text/plain when forwarding
6353 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.141 , page 121)'' is _
\bs_
\be_
\bt. Other-
6354 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.73 , page 105)'' is used instead.
6356 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6362 When forwarding multiple attachments of a MIME message from the recvattach
6363 menu, attachments which cannot be decoded in a reasonable manner will be
6364 attached to the newly composed message if this option is set.
6366 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6370 Default: '%4n %c %-16s %a'
6372 Availability: Mixmaster
6374 This variable describes the format of a remailer line on the mixmaster chain
6375 selection screen. The following printf(3)-like sequences are supported:
6378 The running number on the menu.
6381 Remailer capabilities.
6383 The Mutt Next Generation E-Mail Client 123
6386 The remailer's short name.
6389 The remailer's e-mail address.
6391 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6395 Default: 'mixmaster'
6397 Availability: Mixmaster
6399 This variable contains the path to the Mixmaster binary on your system. It is
6400 used with various sets of parameters to gather the list of known remailers, and
6401 to finally send a message through the mixmaster chain.
6403 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bm_
\bo_
\bv_
\be
6409 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6410 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.129 , page 119)'' mailbox, or as a result of a
6411 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 35)'' command.
6413 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6417 Default: '%Y%m%d%h%M%s.G%P%p'
6419 This is the format for the ``local part'' of the Message-Id: header field gen-
6420 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6421 generated. The '%' character marks that certain data will be added to the
6422 string, similar to printf(3). The following characters are allowed:
6425 the current day of month
6437 the current UNIX timestamp (octal)
6439 The Mutt Next Generation E-Mail Client 124
6445 the current Message-ID prefix (a character rotating with every Mes-
6446 sage-ID being generated)
6449 a random integer value (decimal)
6452 a random integer value (hexadecimal)
6458 the current UNIX timestamp (decimal)
6461 the current UNIX timestamp (hexadecimal)
6464 the current year (Y2K compliant)
6469 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6470 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6472 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6478 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6479 threads to fit on the screen.
6481 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6489 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6490 ing the body of an outgoing news article.
6492 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6496 The Mutt Next Generation E-Mail Client 125
6502 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6503 ing the body of an outgoing news article.
6505 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6509 Default: '~/.muttng'
6513 This variable points to directory where Mutt-ng will cache news article head-
6514 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6515 when you enter a newsgroup.
6517 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6518 cally increases speed and lowers traffic.
6520 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6528 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6529 when you leaving it.
6531 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6539 This variable controls how many news articles to cache per newsgroup (if
6540 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.151 , page 125)) and how
6541 many news articles to show in the ``index'' menu.
6543 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.153 ,
6544 page 125), all older ones will be removed/not shown in the index.
6546 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6552 The Mutt Next Generation E-Mail Client 126
6556 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6557 header field, a follow-up to the newsgroup is not permitted. The message will
6558 be mailed to the submitter of the message via mail.
6560 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6564 Default: '%4C %M%N %5s %-45.45f %d'
6568 This variable allows you to customize the newsgroup browser display to your
6569 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 ,
6570 page 114)'', but has its own set of printf(3)-like sequences:
6572 %C current newsgroup number
6573 %d description of newsgroup (retrieved from server)
6575 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6576 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6577 %n number of new articles in newsgroup
6578 %s number of unread articles in newsgroup
6579 %>X right justify the rest of the string and pad with character "X"
6580 %|X pad to the end of the line with character "X"
6582 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6590 This variable specifies the name (or address) of the NNTP server to be used.
6592 It defaults to the value specified via the environment variable $NNTPSERVER or
6593 contained in the file /etc/nntpserver.
6595 You can also specify a username and an alternative port for each newsserver,
6598 [nntp[s]://][username[:password]@]newsserver[:port]
6600 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6601 security risk since the superuser of your machine may read it regardless of the
6604 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6606 The Mutt Next Generation E-Mail Client 127
6614 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6615 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6616 lowing printf(3)-style sequence is understood:
6620 Example: set inews='/usr/local/bin/inews -hS'
6622 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6630 This variable controls whether or not descriptions for newsgroups are to be
6631 loaded when subscribing to a newsgroup.
6633 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6641 The time in seconds until any operations on a newsgroup except posting a new
6642 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6643 each operation in index (stepping, read article, etc.).
6645 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6653 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6654 encoded according to RFC2047.
6656 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6658 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6660 The Mutt Next Generation E-Mail Client 128
6664 Default: '~/.newsrc'
6668 This file contains information about subscribed newsgroup and articles read so
6671 To ease the use of multiple news servers, the following printf(3)-style
6672 sequence is understood:
6676 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6684 Your password for NNTP account.
6686 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6687 the superuser of your machine may read it regardless of the file's permissions.
6689 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6697 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6698 sions to post (e.g. moderated).
6700 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6701 is totally read-only, that posting will not have any effect.
6703 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6711 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6712 was connection lost.
6714 The Mutt Next Generation E-Mail Client 129
6716 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6724 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6725 file and into the news cache.
6727 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6735 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6736 browser. Otherwise, it will be done only once for a newsserver. Also controls
6737 whether or not the number of new articles of subscribed newsgroups will be
6740 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6748 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6749 played in the newsgroup browser.
6751 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6759 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6760 tification, Mutt-ng will prompt you for your account name.
6762 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6770 The Mutt Next Generation E-Mail Client 130
6772 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6773 name of the original article author) to articles that you followup to.
6775 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6781 This specifies the operating system name for the User-Agent: header field. If
6782 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6783 returns. If uname(2) fails, ``UNIX'' will be used.
6785 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6787 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bp_
\ba_
\bg_
\be_
\br
6793 This variable specifies which pager you would like to use to view messages.
6794 ``builtin'' means to use the builtin pager, otherwise this variable should
6795 specify the pathname of the external pager you would like to use.
6797 Using an external pager may have some disadvantages: Additional keystrokes are
6798 necessary because you can't call Mutt-ng functions directly from the pager, and
6799 screen resizes cause lines longer than the screen width to be badly formatted
6802 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6808 This variable controls the number of lines of context that are given when dis-
6809 playing the next or previous page in the internal pager. By default, Mutt-ng
6810 will display the line after the last one on the screen at the top of the next
6811 page (0 lines of context).
6813 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6817 Default: '-%Z- %C/%m: %-20.20n %s'
6819 This variable controls the format of the one-line message ``status'' displayed
6820 before each message in either the internal or an external pager. The valid
6821 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114)''
6824 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6826 The Mutt Next Generation E-Mail Client 131
6832 Determines the number of lines of a mini-index which is shown when in the
6833 pager. The current message, unless near the top or bottom of the folder, will
6834 be roughly one third of the way down this mini-index, giving the reader the
6835 context of a few messages before and after the message. This is useful, for
6836 example, to determine how many messages remain to be read in the current
6837 thread. One of the lines is reserved for the status bar from the index, so a
6838 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs of 6 will only show 5 lines of the actual index. A value of
6839 0 results in no index being shown. If the number of messages in the current
6840 folder is less than _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs, then the index will only use as many
6843 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6849 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6850 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
6852 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6858 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
6859 whenever the user performs an operation which ordinarily would result in the
6860 contents of the message being operated on. For example, if the user displays a
6861 pgp-traditional message which has not been manually checked with the check-tra-
6862 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
6865 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6871 This option controls whether Mutt-ng generates old-style inline (traditional)
6872 PGP encrypted or signed messages under certain circumstances. This can be
6873 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
6875 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6876 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6877 ing PGP/MIME messages when inline (traditional) would not work. See also:
6878 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.193 , page 135)''.
6880 Also note that using the old-style PGP message format is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by d
\bde
\bep
\bpr
\bre
\bec
\bca
\bat
\bte
\bed
\bd.
6883 The Mutt Next Generation E-Mail Client 132
6885 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
6891 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
6892 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
6894 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6900 This format is used to create a old-style ``clearsigned'' PGP message.
6902 Note that the use of this format is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by d
\bde
\bep
\bpr
\bre
\bec
\bca
\bat
\bte
\bed
\bd. (PGP only)
6904 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6910 This format strings specifies a command which is used to decode application/pgp
6913 The PGP command formats have their own set of printf(3)-like sequences:
6916 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
6917 string otherwise. Note: This may be used with a %? construct.
6920 Expands to the name of a file containing a message.
6923 Expands to the name of a file containing the signature part of a
6924 multipart/signed attachment when verifying it.
6927 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.197 , page 136).
6930 One or more key IDs.
6932 For examples on how to configure these formats for the various versions of PGP
6933 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
6934 subdirectory which has been installed on your system alongside the documenta-
6937 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6939 The Mutt Next Generation E-Mail Client 133
6945 This command is used to decrypt a PGP encrypted message. (PGP only)
6947 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6953 This command is used to encrypt a body part without signing it. (PGP only)
6955 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6961 This command is used to both sign and encrypt a body part. (PGP only)
6963 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6967 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
6969 This variable allows you to customize the PGP key selection menu to your per-
6970 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page
6971 114)'', but has its own set of printf(3)-like sequences:
6994 The Mutt Next Generation E-Mail Client 134
6997 trust/validity of the key-uid association
7000 date of the key where <s> is an strftime(3) expression
7004 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7010 This command is used to export a public key from the user's key ring. (PGP
7013 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7019 This command is invoked whenever Mutt-ng will need public key information. %r
7020 is the only printf(3)-like sequence used with this format. (PGP only)
7022 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
7024 Type: regular expression
7028 If you assign a text to this variable, then a PGP signature is only considered
7029 verified if the output from _
\b$_
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.203 , page 137)
7030 contains the text. Use this variable if the exit code from the command is 0
7031 even for bad signatures. (PGP only)
7033 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
7039 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
7040 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
7041 want to play interesting key selection games. (PGP only)
7043 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7049 This command is used to import a key from a message into the user's public key
7051 The Mutt Next Generation E-Mail Client 135
7055 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7061 This command is used to list the public key ring's contents. The output format
7062 must be analogous to the one used by gpg --list-keys --with-colons.
7064 This format is also generated by the pgpring utility which comes with Mutt-ng.
7067 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7073 This command is used to list the secret key ring's contents. The output format
7074 must be analogous to the one used by gpg --list-keys --with-colons.
7076 This format is also generated by the pgpring utility which comes with Mutt-ng.
7079 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
7085 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
7088 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
7094 This option controls whether Mutt-ng will prompt you for automatically sending
7095 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
7098 Also note that using the old-style PGP message format is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by d
\bde
\bep
\bpr
\bre
\bec
\bca
\bat
\bte
\bed
\bd.
7101 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7107 The Mutt Next Generation E-Mail Client 136
7109 Setting this variable will cause Mutt-ng to always attempt to create an inline
7110 (traditional) message when replying to a message which is PGP encrypted/signed
7111 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
7112 required. This option does not automatically detect if the (replied-to) mes-
7113 sage is inline; instead it relies on Mutt-ng internals for previously
7114 checked/flagged messages.
7116 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7117 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7118 ing PGP/MIME messages when inline (traditional) would not work. See also:
7119 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.193 , page 135)''.
7121 Also note that using the old-style PGP message format is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by d
\bde
\bep
\bpr
\bre
\bec
\bca
\bat
\bte
\bed
\bd.
7124 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
7130 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
7131 and multipart/encrypted body parts.
7133 This is useful for applications like encrypted and signed mailing lists, where
7134 the outer layer (multipart/encrypted) can be easily removed, while the inner
7135 multipart/signed part is retained. (PGP only)
7137 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
7143 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
7144 This includes keys which have been revoked, have expired, or have been marked
7145 as ``disabled'' by the user. (PGP only)
7147 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
7153 If you have more than one key pair, this option allows you to specify which of
7154 your private keys to use. It is recommended that you use the keyid form to
7155 specify your key (e.g., ``0x00112233''). (PGP only)
7157 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7163 The Mutt Next Generation E-Mail Client 137
7165 This command is used to create the detached PGP signature for a multi-
7166 part/signed PGP/MIME body part. (PGP only)
7168 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
7174 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7178 sort alphabetically by user id
7181 sort alphabetically by key id
7184 sort by key creation date
7187 sort by the trust of the key
7189 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7192 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7198 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7199 printable. Please note that unsetting this variable may lead to problems with
7200 non-verifyable PGP signatures, so only change this if you know what you are
7203 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7209 The number of seconds after which a cached passphrase will expire if not used.
7210 Default: 300. (PGP only)
7212 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7218 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7220 The Mutt Next Generation E-Mail Client 138
7222 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7228 This command is used to verify PGP signatures. (PGP only)
7230 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7236 This command is used to verify key information from the key selection menu.
7239 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7245 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will
7246 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7247 ers and will attempt to PGP/MIME decode the messages first.
7249 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7255 The separator to add between messages when piping a list of tagged messages to
7256 an external Unix command.
7258 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7264 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7265 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7266 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7267 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7268 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7269 (section 7.4.206 , page 138)'' separator is added after each message.
7271 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7277 The Mutt Next Generation E-Mail Client 139
7281 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7282 fall back to other authentication methods if the previous methods are unavail-
7283 able. If a method is available but authentication fails, Mutt-ng will not con-
7284 nect to the POP server.
7286 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7294 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7295 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7296 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7297 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7299 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7300 Mutt-ng will try all available methods, in order from most-secure to least-
7303 Example: set pop_authenticators='digest-md5:apop:user'
7305 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7313 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7314 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7315 load messages but also leave them on the POP server.
7317 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7325 The name of your POP server for the ``fetch-mail'' function. You can also
7326 specify an alternative port, username and password, i.e.:
7328 [pop[s]://][username[:password]@]popserver[:port]
7330 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7331 the superuser of your machine may read it regardless of the file's permissions.
7333 The Mutt Next Generation E-Mail Client 140
7335 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7343 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7344 retrieving only unread messages from the POP server when using the ``fetch-
7347 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7355 This variable configures how often (in seconds) POP should look for new mail.
7357 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7365 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7366 for your password when you open POP mailbox.
7368 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7369 the superuser of your machine may read it regardless of the file's permissions.
7371 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7379 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7382 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7390 The Mutt Next Generation E-Mail Client 141
7392 Your login name on the POP server.
7394 This variable defaults to your user name on the local machine.
7396 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7402 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 92)'' variable, Mutt-ng
7403 will append this string after the inclusion of a message which is being replied
7406 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7412 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7413 7.4.219 , page 141)'' mailbox when you elect not to send immediately.
7415 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7419 Default: '~/postponed'
7421 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.218 , page 141)
7422 sending a message'' which you are editing. When you choose to postpone a mes-
7423 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7424 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.218 , page 141)'' variable.
7426 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7432 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a connec-
7433 tion to the server. This is useful for setting up secure connections, e.g. with
7434 ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the
7437 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7438 /dev/null > /dev/null'
7440 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7442 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7443 machine without having to enter a password.
7445 The Mutt Next Generation E-Mail Client 142
7447 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\br_
\bi_
\bn_
\bt
7453 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7454 by default, because some people accidentally hit ``p'' often.
7456 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7462 This specifies the command pipe that should be used to print messages.
7464 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7470 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7471 message is decoded before it is passed to the external command specified by
7472 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.222 , page 142). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7473 cessing will be applied to the message when printing it. The latter setting
7474 may be useful if you are using some advanced printer filter which is able to
7475 properly format e-mail messages for printing.
7477 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7483 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7484 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.222 , page 142) is executed
7485 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7486 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.222 , page 142) is executed
7487 only once, and all the messages are concatenated, with a form feed as the mes-
7490 Those who use the enscript(1) program's mail-printing mode will most likely
7491 want to set this option.
7493 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7499 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.171 , page 130)'', setting this
7500 variable will cause Mutt-ng to prompt you for a command when the pager exits
7502 The Mutt Next Generation E-Mail Client 143
7504 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7505 index menu when the external pager exits.
7507 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7513 This specifies the command that Mutt-ng will use to make external address
7514 queries. The string should contain a %s, which will be substituted with the
7515 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 57)'' for more
7518 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\bq_
\bu_
\bi_
\bt
7524 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7525 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7526 and if it is set to _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs or _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo, you are prompted for confirmation when
7529 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7535 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7536 tion 7.4.113 , page 114)''.
7538 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7544 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7545 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7546 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.113 , page 114)''.
7548 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7550 Type: regular expression
7552 Default: '^([ \t]*[|>:}#])+'
7554 A regular expression used in the internal-pager to determine quoted sections of
7555 text in the body of a message.
7557 N
\bNo
\bot
\bte
\be:
\b: In order to use the _
\bq_
\bu_
\bo_
\bt_
\be_
\bdx
\bx patterns in the internal pager, you need to
7559 The Mutt Next Generation E-Mail Client 144
7561 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7562 the beginning of quoted lines.
7564 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7570 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7571 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7572 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7573 reads message 25, and then again when it gets to message 50). This variable is
7574 meant to indicate progress when reading large mailboxes which may take some
7575 time. When set to 0, only a single message will appear before the reading the
7578 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.344 , page 171)'' variable.
7580 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7586 If set, all folders are opened in read-only mode.
7588 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7594 This variable specifies what ``real'' or ``personal'' name should be used when
7597 By default, this is the GECOS field from /etc/passwd.
7599 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7600 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.78 , page 106) variable.
7602 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7608 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7609 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.219 , page 141)''.
7611 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7613 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7615 The Mutt Next Generation E-Mail Client 145
7621 This specifies the file into which your outgoing messages should be appended.
7622 (This is meant as the primary method for saving a copy of your messages, but
7623 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 36)'' com-
7624 mand to create a Bcc: header field with your email address in it.)
7626 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b4_
\b) is overridden by the
7627 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.72 , page 105)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7628 7.4.246 , page 147)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page
7631 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7633 Type: regular expression
7635 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7637 A regular expression used to recognize reply messages when threading and reply-
7638 ing. The default value corresponds to the English ``Re:'' and the German
7641 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7647 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7648 that you want to reply to the recipients of that message rather than to your-
7651 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7657 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7658 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7659 use the address in the ``From:'' header field instead.
7661 This option is useful for reading a mailing list that sets the ``Reply-To:''
7662 header field to the list address and you want to send a private message to the
7663 author of a message.
7665 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7671 The Mutt Next Generation E-Mail Client 146
7673 When set, the cursor will be automatically advanced to the next (possibly
7674 undeleted) message whenever a command that modifies the current message is exe-
7677 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7683 This variable controls whether or not Mutt-ng will display the ``personal''
7684 name from your aliases in the index menu if it finds an alias that matches the
7685 message's sender. For example, if you have the following alias:
7687 alias juser abd30425@somewhere.net (Joe User)
7689 and then you receive mail which contains the following header:
7691 From: abd30425@somewhere.net
7693 It would be displayed in the index menu as ``Joe User'' instead of
7694 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7695 not human friendly (like CompuServe addresses).
7697 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7703 It may sometimes arrive that you receive mail to a certain machine, move the
7704 messages to another machine, and reply to some the messages from there. If
7705 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7706 using the address where you received the messages you are replying to i
\bif
\bf that
7707 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7708 would be used doesn't match your alternates, the From: line will use your
7709 address on the current machine.
7711 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7717 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.241 ,
7718 page 146) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7719 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7720 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7721 (section 7.4.233 , page 144) variable.
7723 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7727 The Mutt Next Generation E-Mail Client 147
7731 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7732 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7733 ments to files named like this:
7735 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7737 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7738 effect before you have changed folders.
7740 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7741 standard, but nevertheless encountered in the wild.
7743 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7744 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7745 encoding specified in RFC 2231.
7747 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7753 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7754 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.246 , page 147)'' or
7755 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.72 , page 105)'' is _
\bs_
\be_
\bt too, the selection of the
7756 fcc folder will be changed as well.
7758 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7764 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7765 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.302 , page 160)'' which is
7766 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7768 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7769 and Maildir directories.
7771 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7777 This variable controls how copies of outgoing messages are saved. When set, a
7778 check is made to see if a mailbox specified by the recipient address exists
7779 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.68 ,
7780 page 103)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7781 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7782 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.235 , page 144)'' mailbox.
7784 The Mutt Next Generation E-Mail Client 148
7786 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.72 , page 105)'' variable.
7788 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\bs_
\bc_
\bo_
\br_
\be
7794 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7795 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
7796 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.248 , page 148)'' variable and friends are used.
7798 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7804 Messages which have been assigned a score equal to or lower than the value of
7805 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7806 scores are always greater than or equal to zero, the default setting of this
7807 variable will never mark a message for deletion.
7809 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7815 Messages which have been assigned a score greater than or equal to this vari-
7816 able's value are automatically marked ``flagged''.
7818 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7824 Messages which have been assigned a score equal to or lower than the value of
7825 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7826 scores are always greater than or equal to zero, the default setting of this
7827 variable will never mark a message read.
7829 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7833 Default: 'us-ascii:iso-8859-1:utf-8'
7835 A list of character sets for outgoing messages. Mutt-ng will use the first
7836 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7837 (section 7.4.27 , page 94)'' is not iso-8859-1 and recipients may not under-
7838 stand UTF-8, it is advisable to include in the list an appropriate widely used
7839 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7841 The Mutt Next Generation E-Mail Client 149
7843 instead of or after iso-8859-1.
7845 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7849 Default: '/usr/sbin/sendmail -oem -oi'
7851 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7852 Mutt-ng expects that the specified program interprets additional arguments as
7853 recipient addresses.
7855 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
7861 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.252 ,
7862 page 148)'' process to finish before giving up and putting delivery in the
7865 Mutt-ng interprets the value of this variable as follows:
7868 number of seconds to wait for sendmail to finish before continuing
7871 wait forever for sendmail to finish
7874 always put sendmail in the background without waiting
7876 Note that if you specify a value other than 0, the output of the child process
7877 will be put in a temporary file. If there is some error, you will be informed
7878 as to where to find the output.
7880 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\bs_
\bh_
\be_
\bl_
\bl
7886 Command to use when spawning a subshell. By default, the user's login shell
7887 from /etc/passwd is used.
7889 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
7895 When the sidebar is displayed and _
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bs_
\bh_
\bo_
\br_
\bt_
\be_
\bn_
\b__
\bh_
\bi_
\be_
\br_
\ba_
\br_
\bc_
\bh_
\by (section
7896 7.4.259 , page 150) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
7898 The Mutt Next Generation E-Mail Client 150
7900 split a folder name into ``hierarchy items.''
7902 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
7908 This specifies the delimiter between the sidebar (if visible) and other
7911 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
7917 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
7919 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7923 Default: '%m%?n?(%n)?%?f?[%f]?'
7925 This variable controls how message counts are printed when the sidebar is
7926 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
7927 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
7928 mbox-style mailboxes.)
7930 The following printf(3)-like sequences are supported all of which may be
7934 Number of deleted messages. 1)
7937 Number of flagged messages.
7940 Total number of messages.
7943 Total number of messages shown, i.e. not hidden by a limit. 1)
7946 Number of new messages.
7949 Number of tagged messages. 1)
7951 1) These expandos only have a non-zero value for the current mailbox and will
7952 always be zero otherwise.
7954 The Mutt Next Generation E-Mail Client 151
7956 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bs_
\bh_
\bo_
\br_
\bt_
\be_
\bn_
\b__
\bh_
\bi_
\be_
\br_
\ba_
\br_
\bc_
\bh_
\by
7962 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
7963 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
7964 7.4.261 , page 151)'' is set to a too low value). For example, if the news-
7965 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
7966 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
7969 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
7970 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.255 , page 149) variable.
7972 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
7978 This specifies whether or not to show the sidebar (a list of folders specified
7979 with the ``mailboxes'' command).
7981 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
7987 The width of the sidebar.
7989 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
7995 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
7996 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.264 , page 151)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
7997 that you not unset this variable unless your ``signature'' contains just your
7998 name. The reason for this is because many software packages use ``-- \n'' to
7999 detect your signature.
8001 For example, Mutt-ng has the ability to highlight the signature in a different
8002 color in the builtin pager.
8004 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8010 The Mutt Next Generation E-Mail Client 152
8012 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
8013 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
8014 know what you are doing, and are prepared to take some heat from netiquette
8017 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
8021 Default: '~/.signature'
8023 Specifies the filename of your signature, which is appended to all outgoing
8024 messages. If the filename ends with a pipe (``|''), it is assumed that file-
8025 name is a shell command and input should be read from its stdout.
8027 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
8033 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
8034 people that want to sign off every message they send with their name.
8036 If you want to insert your website's URL, additional contact information or
8037 witty quotes into your mails, better use a signature file instead of the sig-
8040 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8044 Default: '~f %s | ~s %s'
8046 Specifies how Mutt-ng should expand a simple search into a real search pattern.
8047 A simple search is one that does not contain any of the ~ operators. See
8048 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 82)'' for more information on search patterns.
8050 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
8051 will automatically expand it to the value specified by this variable. For the
8052 default value it would be:
8056 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
8062 Specifies time, in seconds, to pause while displaying certain informational
8063 messages, while moving from folder to folder and after expunging messages from
8064 the current folder. The default is to pause one second, so a value of zero for
8065 this option suppresses the pause.
8067 The Mutt Next Generation E-Mail Client 153
8069 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
8075 Controls the display of lines longer than the screen width in the internal
8076 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
8077 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.125 ,
8078 page 119)'' variable.
8080 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
8082 Type: regular expression
8084 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
8086 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
8087 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.230 , page 143)'', most notably smileys in the
8090 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
8096 This flag controls whether you want to be asked to enter a label for a certifi-
8097 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
8100 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
8106 This variable contains the name of either a directory, or a file which contains
8107 trusted certificates for use with OpenSSL. (S/MIME only)
8109 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
8115 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
8116 and retrieval of keys by itself. This is very basic right now, and keys and
8117 certificates are stored in two different directories, both named as the hash-
8118 value retrieved from OpenSSL. There is an index file which contains mailbox-
8119 address keyid pairs, and which can be manually edited. This one points to the
8120 location of the certificates. (S/MIME only)
8122 The Mutt Next Generation E-Mail Client 154
8124 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8130 This format string specifies a command which is used to decrypt application/x-
8131 pkcs7-mime attachments.
8133 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
8137 Expands to the name of a file containing a message.
8140 Expands to the name of a file containing the signature part of a
8141 multipart/signed attachment when verifying it.
8144 The key-pair specified with _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by (section 7.4.275 ,
8148 One or more certificate IDs.
8151 The algorithm used for encryption.
8154 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
8155 7.4.271 , page 153) points to a directory or file, this expands to
8156 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.271 , page 153)' or
8157 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.271 , page 153)'.
8159 For examples on how to configure these formats, see the smime.rc in the sam-
8160 ples/ subdirectory which has been installed on your system alongside the docu-
8161 mentation. (S/MIME only)
8163 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8169 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
8170 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8171 mailbox-address to determine the key to use. It will ask you to supply a key,
8172 if it can't find one. (S/MIME only)
8174 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8178 The Mutt Next Generation E-Mail Client 155
8182 This is the default key-pair to use for signing. This must be set to the keyid
8183 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8185 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8191 This command is used to create encrypted S/MIME messages. (S/MIME only)
8193 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8199 This sets the algorithm that should be used for encryption. Valid choices are
8200 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8202 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8204 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8210 This command is used to extract X509 certificates from a PKCS7 structure.
8213 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\be_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8219 This command is used to extract the mail address(es) used for storing X509 cer-
8220 tificates, and for verification purposes (to check whether the certificate was
8221 issued for the sender's mailbox). (S/MIME only)
8223 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\be_
\br_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8229 This command is used to extract only the signers X509 certificate from a S/MIME
8230 signature, so that the certificate's owner may get compared to the email's
8231 ``From:'' header field. (S/MIME only)
8233 The Mutt Next Generation E-Mail Client 156
8235 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8241 This command is used to import a certificate via smime_keysng. (S/MIME only)
8243 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8249 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8250 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8252 However, this has no effect while replying, since Mutt-ng will automatically
8253 select the same application that was used to sign/encrypt the original message.
8255 (Note that this variable can be overridden by unsetting _
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be (sec-
8256 tion 7.4.40 , page 97).) (S/MIME only)
8258 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8264 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8265 retrieval of keys/certs by itself. This is very basic right now, and stores
8266 keys and certificates in two different directories, both named as the hash-
8267 value retrieved from OpenSSL. There is an index file which contains mailbox-
8268 address keyid pair, and which can be manually edited. This one points to the
8269 location of the private keys. (S/MIME only)
8271 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8277 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8278 to extract the public X509 certificate(s). (S/MIME only)
8280 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8286 This command is used to created S/MIME signatures of type multipart/signed,
8287 which can be read by all mail clients. (S/MIME only)
8289 The Mutt Next Generation E-Mail Client 157
8291 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bo_
\bp_
\ba_
\bq_
\bu_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8297 This command is used to created S/MIME signatures of type application/x-
8298 pkcs7-signature, which can only be handled by mail clients supporting the
8299 S/MIME extension. (S/MIME only)
8301 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8307 The number of seconds after which a cached passphrase will expire if not used.
8310 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8316 This command is used to verify S/MIME signatures of type multipart/signed.
8319 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bo_
\bp_
\ba_
\bq_
\bu_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8325 This command is used to verify S/MIME signatures of type application/x-
8326 pkcs7-mime. (S/MIME only)
8328 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8336 If this variable is non-empty, it'll be used as the envelope sender. If it's
8337 empty (the default), the value of the regular From: header will be used.
8339 This may be necessary as some providers don't allow for arbitrary values as the
8340 envelope sender but only a particular one which may not be the same as the
8341 user's desired From: header.
8343 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8345 The Mutt Next Generation E-Mail Client 158
8353 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8354 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8355 _
\bm_
\ba_
\bi_
\bl (section 7.4.252 , page 148)'', and any associated variables.
8357 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8365 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8366 7.4.295 , page 158)'' is set, but this variable is not, you will be prompted
8367 for a password when sending.
8369 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8370 the superuser of your machine may read it regardless of the file's permissions.
8372 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8380 Defines the port that the SMTP host is listening on for mail delivery. Must be
8381 specified as a number.
8383 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8384 will probably desire 587, the mail submission port.
8386 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8392 Availability: SMTP (and SSL)
8394 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8395 server does not support STARTTLS or there is an error in the TLS Handshake, the
8396 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8397 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8398 port enabled in order to use it.
8400 The Mutt Next Generation E-Mail Client 159
8402 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8410 Defines the username to use with SMTP AUTH. Setting this variable will cause
8411 Mutt-ng to attempt to use SMTP AUTH when sending.
8413 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bo_
\br_
\bt
8419 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8424 mailbox-order (unsorted)
8432 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8433 (example: set sort=reverse-date-sent).
8435 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8441 Specifies how the entries in the ``alias'' menu are sorted. The following are
8444 address (sort alphabetically by email address)
8445 alias (sort alphabetically by alias name)
8446 unsorted (leave in order specified in .muttrc)
8448 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8452 The Mutt Next Generation E-Mail Client 160
8456 When sorting by threads, this variable controls how threads are sorted in rela-
8457 tion to other threads, and how the branches of the thread trees are sorted.
8458 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.296 , page 158)'' can,
8459 except threads (in that case, Mutt-ng will just use date-sent). You can also
8460 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8461 come after reverse-. The last- prefix causes messages to be sorted against its
8462 siblings by which has the last descendant, using the rest of sort_aux as an
8465 For instance, set sort_aux=last-date-received would mean that if a new message
8466 is received in a thread, that thread becomes the last one displayed (or the
8467 first, if you have set sort=reverse-threads.)
8469 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.296 , page 158)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8470 (section 7.4.298 , page 159) is reversed again (which is not the right thing
8471 to do, but kept to not break any existing configuration setting).
8473 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8479 Specifies how to sort entries in the file browser. By default, the entries are
8480 sorted alphabetically. Valid values:
8482 alpha (alphabetically)
8487 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8488 (example: set sort_browser=reverse-date).
8490 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8496 This variable is only useful when sorting by threads with ``_
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8497 (section 7.4.317 , page 166)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8498 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.300 ,
8499 page 160) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8500 sage by subject if the subject of the child message starts with a substring
8501 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.236 , page 145)''. With
8502 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.300 , page 160) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8503 whether or not this is the case, as long as the non-``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section
8504 7.4.236 , page 145)'' parts of both messages are identical.
8506 The Mutt Next Generation E-Mail Client 161
8508 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8514 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.301 , page 160)'' controls what happens when
8515 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8516 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8517 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.301 ,
8518 page 160)'' as a separator.
8520 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8526 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8527 you can specify its location with this variable. Mutt-ng will automatically
8528 set this variable to the value of the environment variable $MAIL if it is not
8531 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8537 This variable specifies a file containing trusted CA certificates. Any server
8538 certificate that is signed with one of these CA certificates are also automati-
8541 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8543 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8551 The file containing a client certificate and its associated private key.
8553 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8559 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8560 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8561 server does not advertise the capability, since it would otherwise have to
8563 The Mutt Next Generation E-Mail Client 162
8565 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8566 7.4.307 , page 162)''.
8568 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8574 Availability: GNUTLS
8576 This variable specifies the minimum acceptable prime size (in bits) for use in
8577 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8580 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8586 Availability: SSL or GNUTLS
8588 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8589 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8590 regardless of the server's capabilities.
8592 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8600 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8603 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8609 Availability: SSL or GNUTLS
8611 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8614 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8620 The Mutt Next Generation E-Mail Client 163
8622 Availability: SSL or GNUTLS
8624 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8627 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8635 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8636 store when checking if server certificate is signed by a trusted CA.
8638 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8644 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8645 tion 7.4.313 , page 163)''. The first character is used when the mailbox is
8646 unchanged. The second is used when the mailbox has been changed, and it needs
8647 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8648 if the mailbox will not be written when exiting that mailbox (You can toggle
8649 whether to write changes to a mailbox with the toggle-write operation, bound by
8650 default to ``%''). The fourth is used to indicate that the current folder has
8651 been opened in attach-message mode (Certain operations like composing a new
8652 mail, replying, forwarding, etc. are not permitted in this mode).
8654 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8658 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8659 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8660 %l?]---(%s/%S)-%>-(%P)---'
8662 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8663 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.114 , page 114)'', but has
8664 its own set of printf(3)-like sequences:
8667 number of mailboxes with new mail *
8670 the short pathname of the current mailbox
8673 number of deleted messages *
8675 The Mutt Next Generation E-Mail Client 164
8678 the full pathname of the current mailbox
8681 number of flagged messages *
8687 size (in bytes) of the current mailbox *
8690 size (in bytes) of the messages shown (i.e., which match the cur-
8694 the number of messages in the mailbox *
8697 the number of messages shown (i.e., which match the current limit)
8701 number of new messages in the mailbox *
8704 number of old unread messages *
8707 number of postponed messages *
8710 percentage of the way through the index
8713 modified/read-only/won't-write/attach-message indicator, according
8714 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.312 , page 163)
8717 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.296 , page 158))
8720 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.298 , page
8724 number of tagged messages *
8727 number of unread messages *
8730 Mutt-ng version string
8732 The Mutt Next Generation E-Mail Client 165
8735 currently active limit pattern, if any *
8738 right justify the rest of the string and pad with 'X'
8741 pad to the end of the line with 'X'
8743 * = can be optionally printed if nonzero
8745 Some of the above sequences can be used to optionally print a string if their
8746 value is nonzero. For example, you may only want to see the number of flagged
8747 messages if such messages exist, since zero is not particularly meaningful. To
8748 optionally print a string based upon one of the above sequences, the following
8751 %?<sequence_char>?<optional_string>?
8753 where _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be_
\b__
\bc_
\bh_
\ba_
\br is a character from the table above, and _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg is
8754 the string you would like printed if _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be_
\b__
\bc_
\bh_
\ba_
\br is nonzero. _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
8755 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8758 Here is an example illustrating how to optionally print the number of new mes-
8761 %?n?%n new messages.?
8763 Additionally you can switch between two strings, the first one, if a value is
8764 zero, the second one, if the value is nonzero, by using the following con-
8767 %?<sequence_char>?<if_string>&<else_string>?
8769 You can additionally force the result of any printf(3)-like sequence to be low-
8770 ercase by prefixing the sequence character with an underscore (_) sign. For
8771 example, if you want to display the local hostname in lowercase, you would use:
8775 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8776 replace any dots in the expansion by underscores. This might be helpful with
8777 IMAP folders that don't like dots in folder names.
8779 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8785 Setting this variable causes the ``status bar'' to be displayed on the first
8786 line of the screen rather than near the bottom.
8788 The Mutt Next Generation E-Mail Client 166
8790 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8796 With mailto: style links, a body as well as arbitrary header information may be
8797 embedded. This may lead to (user) headers being overwriten without note if
8798 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101)'' is unset.
8800 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8801 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8802 message including headers will be shown in the editor regardless of what
8803 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.58 , page 101)'' is set to.
8805 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8811 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8812 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8813 messages are often generated by old mailers or buggy mailers like MS Outlook
8814 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.13 , page 90).
8816 This option also replaces linear-white-space between encoded-word and *text to
8817 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8818 from being devided into multiple lines.
8820 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8826 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8827 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.296 , page 158)'' by mes-
8828 sage threads. By default, messages with the same subject are grouped together
8829 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8830 mailbox where you might have several unrelated messages with the subject ``hi''
8831 which will get grouped together.
8833 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8839 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8840 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.319 , page 166) when replying. This is
8841 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8844 The Mutt Next Generation E-Mail Client 167
8846 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8848 Type: regular expression
8850 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8852 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.318 , page 166) is _
\bs_
\be_
\bt, mutt-ng
8853 will remove this trailing part of the ``Subject'' line when replying if it
8854 won't be empty afterwards.
8856 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
8862 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
8863 i.e. a space will be inserted between the quote characters and the actual text.
8865 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
8871 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
8872 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
8873 mand like ``xterm -e muttng.''
8875 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
8881 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
8882 format is easier to handle for some mailing software, and generally just looks
8883 like ordinary text. To actually make use of this format's features, you'll
8884 need support in your editor.
8886 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.113 , page 114) is ignored when this
8889 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8895 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
8896 tion 7.2 , page 82)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
8897 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
8898 as they appear in the folder.
8900 The Mutt Next Generation E-Mail Client 168
8902 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
8908 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
8909 messages by subject.
8911 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bt_
\bi_
\bl_
\bd_
\be
8917 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
8920 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8926 This variable controls the _
\bn_
\bu_
\bm_
\bb_
\be_
\br _
\bo_
\bf _
\bs_
\be_
\bc_
\bo_
\bn_
\bd_
\bs Mutt-ng will wait for a key to be
8927 pressed in the main menu before timing out and checking for new mail. A value
8928 of zero or less will cause Mutt-ng to never time out.
8930 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
8936 This variable allows you to specify where Mutt-ng will place its temporary
8937 files needed for displaying and composing messages. If this variable is not
8938 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
8941 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8947 Controls the character used to indicate mail addressed to you. The first char-
8948 acter is the one used when the mail is NOT addressed to your address (default:
8949 space). The second is used when you are the only recipient of the message
8950 (default: +). The third is when your address appears in the ``To:'' header
8951 field, but you are not the only recipient of the message (default: T). The
8952 fourth character is used when your address is specified in the ``Cc:'' header
8953 field, but you are not the only recipient. The fifth character is used to
8954 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
8955 when a mail was sent to a mailing-list you're subscribe to (default: L).
8957 The Mutt Next Generation E-Mail Client 169
8959 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bt_
\br_
\ba_
\bs_
\bh
8965 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
8966 marked for deletion will be moved, instead of being irremediably purged.
8968 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
8969 that there is no way to recover mail.
8971 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
8977 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
8978 a raw socket. You may be able to use this to set up preauthenticated connec-
8979 tions to your IMAP/POP3 server. Example:
8981 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
8983 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
8984 without having to enter a password.
8986 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bu_
\bm_
\ba_
\bs_
\bk
8992 This sets the umask that will be used by Mutt-ng when creating all kinds of
8993 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
8995 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
9001 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
9002 rent thread is _
\bu_
\bncollapsed.
9004 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
9010 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
9011 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
9012 with the SMTP support via libESMTP. Otherwise you may not be able to send
9014 The Mutt Next Generation E-Mail Client 170
9018 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.252 , page
9019 148)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
9020 negotiation or tell libESMTP to do so.
9022 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
9028 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
9029 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.93 , page 109)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
9030 no addresses will be qualified.
9032 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
9038 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
9039 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
9040 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 36)'' command.
9042 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
9050 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
9052 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
9055 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
9061 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
9062 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
9063 mally, the default should work.
9065 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
9071 The Mutt Next Generation E-Mail Client 171
9073 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
9076 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
9082 Controls whether Mutt-ng will ask you to press a key after _
\bs_
\bh_
\be_
\bl_
\bl_
\b- _
\be_
\bs_
\bc_
\ba_
\bp_
\be, _
\bp_
\bi_
\bp_
\be_
\b-
9083 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be, _
\bp_
\bi_
\bp_
\be_
\b-_
\be_
\bn_
\bt_
\br_
\by, _
\bp_
\br_
\bi_
\bn_
\bt_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be, and _
\bp_
\br_
\bi_
\bn_
\bt_
\b-_
\be_
\bn_
\bt_
\br_
\by commands.
9085 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
9086 77)'', provided that the corresponding mailcap entry has a needsterminal flag,
9087 and the external program is interactive.
9089 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
9090 a key only if the external command returned a non-zero status.
9092 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bw_
\be_
\be_
\bd
9098 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
9099 replying to messages.
9101 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9107 Controls whether searches wrap around the end of the mailbox.
9109 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
9110 searches will not wrap.
9112 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
9118 Controls the size of the margin remaining at the right side of the terminal
9119 when Mutt-ng's pager does smart wrapping.
9121 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
9127 The Mutt Next Generation E-Mail Client 172
9129 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
9130 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
9132 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
9138 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
9139 indicate progress. If set to 0, only a single message will be displayed before
9142 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.231 , page 143)'' variable.
9144 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
9148 Default: 'M%?n?AIL&ail?'
9150 Controls the format of the X11 icon title, as long as _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (sec-
9151 tion 7.4.347 , page 172) is _
\bs_
\be_
\bt. This string is identical in formatting to the
9152 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.313 , page 163)''.
9154 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b6 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
9160 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.347 , page 172) is _
\bs_
\be_
\bt, this string will be
9161 used to set the title when leaving mutt-ng. For terminal-based programs,
9162 there's no easy and portable way to read the current title so mutt-ng cannot
9163 read it upon startup and restore it when exiting.
9165 Based on the xterm FAQ, the following might work:
9167 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9170 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b7 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9176 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9177 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9180 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b8 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9184 The Mutt Next Generation E-Mail Client 173
9186 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9188 Controls the format of the title bar of the xterm provided that
9189 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.347 , page 172) has been _
\bs_
\be_
\bt. This string is
9190 identical in formatting to the one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.313 ,
9193 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9195 The following is the list of available functions listed by the mapping in which
9196 they are available. The default key setting is given, and an explanation of
9197 what the function does. The key bindings of these functions can be changed
9198 with the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 25) command.
9200 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9202 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9203 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9204 tings for this menu will affect the default bindings for all menus (except as
9207 bottom-page L move to the bottom of the page
9208 current-bottom not bound move current entry to bottom of page
9209 current-middle not bound move current entry to middle of page
9210 current-top not bound move current entry to top of page
9211 enter-command : enter a muttngrc command
9212 exit q exit this menu
9213 first-entry = move to the first entry
9214 half-down ] scroll down 1/2 page
9215 half-up [ scroll up 1/2 page
9217 jump number jump to an index number
9218 last-entry * move to the last entry
9219 middle-page M move to the middle of the page
9220 next-entry j move to the next entry
9221 next-line > scroll down one line
9222 next-page z move to the next page
9223 previous-entry k move to the previous entry
9224 previous-line < scroll up one line
9225 previous-page Z move to the previous page
9226 refresh ^L clear and redraw the screen
9227 search / search for a regular expression
9228 search-next n search for next match
9229 search-opposite not bound search for next match in opposite direction
9230 search-reverse ESC / search backwards for a regular expression
9231 select-entry RET select the current entry
9232 shell-escape ! run a program in a subshell
9233 tag-entry t toggle the tag on the current entry
9234 tag-prefix ; apply next command to tagged entries
9235 tag-prefix-cond not bound apply next function ONLY to tagged messages
9236 top-page H move to the top of the page
9237 what-key not bound display the keycode for a key press
9239 The Mutt Next Generation E-Mail Client 174
9241 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9243 The Mutt Next Generation E-Mail Client 175
9245 bounce-message b remail a message to another user
9246 change-folder c open a different folder
9247 change-folder-readonly ESC c open a different folder in read only mode
9248 check-traditional-pgp ESC P check for classic pgp
9249 clear-flag W clear a status flag from a message
9250 copy-message C copy a message to a file/mailbox
9251 create-alias a create an alias from a message sender
9252 decode-copy ESC C decode a message and copy it to a file/mailbox
9253 decode-save ESC s decode a message and save it to a file/mailbox
9254 delete-message d delete the current entry
9255 delete-pattern D delete messages matching a pattern
9256 delete-subthread ESC d delete all messages in subthread
9257 delete-thread ^D delete all messages in thread
9258 display-address @ display full address of sender
9259 display-toggle-weed h display message and toggle header weeding
9260 display-message RET display a message
9261 edit e edit the current message
9262 edit-type ^E edit the current message's Content-Type
9263 exit x exit without saving changes
9264 extract-keys ^K extract PGP public keys
9265 fetch-mail G retrieve mail from POP server
9266 flag-message F toggle a message's 'important' flag
9267 forget-passphrase ^F wipe PGP passphrase from memory
9268 forward-message f forward a message with comments
9269 group-reply g reply to all recipients
9270 limit l show only messages matching a pattern
9271 list-reply L reply to specified mailing list
9272 mail m compose a new mail message
9273 mail-key ESC k mail a PGP public key
9274 next-new TAB jump to the next new message
9275 next-subthread ESC n jump to the next subthread
9276 next-thread ^N jump to the next thread
9277 next-undeleted j move to the next undeleted message
9278 next-unread not bound jump to the next unread message
9279 parent-message P jump to parent message in thread
9280 pipe-message | pipe message/attachment to a shell command
9281 previous-new ESC TAB jump to the previous new message
9282 previous-page Z move to the previous page
9283 previous-subthread ESC p jump to previous subthread
9284 previous-thread ^P jump to previous thread
9285 previous-undeleted k move to the last undelete message
9286 previous-unread not bound jump to the previous unread message
9287 print-message p print the current entry
9288 query Q query external program for addresses
9289 quit q save changes to mailbox and quit
9290 read-subthread ESC r mark the current subthread as read
9291 read-thread ^R mark the current thread as read
9292 recall-message R recall a postponed message
9293 reply r reply to a message
9294 resend-message ESC e resend message and preserve MIME structure
9295 save-message s save message/attachment to a file
9296 set-flag w set a status flag on a message
9297 show-version V show the Mutt-ng version number and date
9298 show-limit ESC l show currently active limit pattern, if any
9300 The Mutt Next Generation E-Mail Client 176
9302 sort-mailbox o sort messages
9303 sort-reverse O sort messages in reverse order
9304 sync-mailbox $ save changes to mailbox
9305 tag-pattern T tag messages matching a pattern
9306 tag-thread ESC t tag/untag all messages in the current thread
9307 toggle-new N toggle a message's 'new' flag
9308 toggle-write % toggle whether the mailbox will be rewritten
9309 undelete-message u undelete the current entry
9310 undelete-pattern U undelete messages matching a pattern
9311 undelete-subthread ESC u undelete all messages in subthread
9312 undelete-thread ^U undelete all messages in thread
9313 untag-pattern ^T untag messages matching a pattern
9314 view-attachments v show MIME attachments
9316 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9318 The Mutt Next Generation E-Mail Client 177
9320 bottom not bound jump to the bottom of the message
9321 bounce-message b remail a message to another user
9322 change-folder c open a different folder
9323 change-folder-readonly ESC c open a different folder in read only mode
9324 check-traditional-pgp ESC P check for classic pgp
9325 copy-message C copy a message to a file/mailbox
9326 create-alias a create an alias from a message sender
9327 decode-copy ESC C decode a message and copy it to a file/mailbox
9328 decode-save ESC s decode a message and save it to a file/mailbox
9329 delete-message d delete the current entry
9330 delete-subthread ESC d delete all messages in subthread
9331 delete-thread ^D delete all messages in thread
9332 display-address @ display full address of sender
9333 display-toggle-weed h display message and toggle header weeding
9334 edit e edit the current message
9335 edit-type ^E edit the current message's Content-Type
9336 enter-command : enter a muttngrc command
9337 exit i return to the main-menu
9338 extract-keys ^K extract PGP public keys
9339 flag-message F toggle a message's 'important' flag
9340 forget-passphrase ^F wipe PGP passphrase from memory
9341 forward-message f forward a message with comments
9342 group-reply g reply to all recipients
9343 half-up not bound move up one-half page
9344 half-down not bound move down one-half page
9346 list-reply L reply to specified mailing list
9347 mail m compose a new mail message
9348 mail-key ESC k mail a PGP public key
9349 mark-as-new N toggle a message's 'new' flag
9350 next-line RET scroll down one line
9351 next-entry J move to the next entry
9352 next-new TAB jump to the next new message
9353 next-page move to the next page
9354 next-subthread ESC n jump to the next subthread
9355 next-thread ^N jump to the next thread
9356 next-undeleted j move to the next undeleted message
9357 next-unread not bound jump to the next unread message
9358 parent-message P jump to parent message in thread
9359 pipe-message | pipe message/attachment to a shell command
9360 previous-line BackSpace scroll up one line
9361 previous-entry K move to the previous entry
9362 previous-new not bound jump to the previous new message
9363 previous-page - move to the previous page
9364 previous-subthread ESC p jump to previous subthread
9365 previous-thread ^P jump to previous thread
9366 previous-undeleted k move to the last undelete message
9367 previous-unread not bound jump to the previous unread message
9368 print-message p print the current entry
9369 quit Q save changes to mailbox and quit
9370 read-subthread ESC r mark the current subthread as read
9371 read-thread ^R mark the current thread as read
9372 recall-message R recall a postponed message
9373 redraw-screen ^L clear and redraw the screen
9375 The Mutt Next Generation E-Mail Client 178
9377 reply r reply to a message
9378 save-message s save message/attachment to a file
9379 search / search for a regular expression
9380 search-next n search for next match
9381 search-opposite not bound search for next match in opposite direction
9382 search-reverse ESC / search backwards for a regular expression
9383 search-toggle \ toggle search pattern coloring
9384 shell-escape ! invoke a command in a subshell
9385 show-version V show the Mutt-ng version number and date
9386 skip-quoted S skip beyond quoted text
9387 sync-mailbox $ save changes to mailbox
9388 tag-message t tag a message
9389 toggle-quoted T toggle display of quoted text
9390 top ^ jump to the top of the message
9391 undelete-message u undelete the current entry
9392 undelete-subthread ESC u undelete all messages in subthread
9393 undelete-thread ^U undelete all messages in thread
9394 view-attachments v show MIME attachments
9396 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9398 search / search for a regular expression
9399 search-next n search for next match
9400 search-reverse ESC / search backwards for a regular expression
9402 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9404 create-alias a create an alias from a message sender
9405 mail m compose a new mail message
9406 query Q query external program for addresses
9407 query-append A append new query results to current results
9408 search / search for a regular expression
9409 search-next n search for next match
9410 search-opposite not bound search for next match in opposite direction
9411 search-reverse ESC / search backwards for a regular expression
9413 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9415 The Mutt Next Generation E-Mail Client 179
9417 bounce-message b remail a message to another user
9418 collapse-parts v toggle display of subparts
9419 delete-entry d delete the current entry
9420 display-toggle-weed h display message and toggle header weeding
9421 edit-type ^E edit the current entry's Content-Type
9422 extract-keys ^K extract PGP public keys
9423 forward-message f forward a message with comments
9424 group-reply g reply to all recipients
9425 list-reply L reply to specified mailing list
9426 pipe-entry | pipe message/attachment to a shell command
9427 print-entry p print the current entry
9428 reply r reply to a message
9429 resend-message ESC e resend message and preserve MIME structure
9430 save-entry s save message/attachment to a file
9431 undelete-entry u undelete the current entry
9432 view-attach RET view attachment using mailcap entry if necessary
9433 view-mailcap m force viewing of attachment using mailcap
9434 view-text T view attachment as text
9436 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9438 The Mutt Next Generation E-Mail Client 180
9440 attach-file a attach a file(s) to this message
9441 attach-message A attach message(s) to this message
9442 attach-key ESC k attach a PGP public key
9443 copy-file C save message/attachment to a file
9444 detach-file D delete the current entry
9445 display-toggle-weed h display message and toggle header weeding
9446 edit-bcc b edit the BCC list
9447 edit-cc c edit the CC list
9448 edit-description d edit attachment description
9449 edit-encoding ^E edit attachment transfer-encoding
9450 edit-fcc f enter a file to save a copy of this message in
9451 edit-from ESC f edit the from: field
9452 edit-file ^X e edit the file to be attached
9453 edit-headers E edit the message with headers
9454 edit e edit the message
9455 edit-mime m edit attachment using mailcap entry
9456 edit-reply-to r edit the Reply-To field
9457 edit-subject s edit the subject of this message
9458 edit-to t edit the TO list
9459 edit-type ^T edit attachment type
9460 filter-entry F filter attachment through a shell command
9461 forget-passphrase ^F wipe PGP passphrase from memory
9462 ispell i run ispell on the message
9463 new-mime n compose new attachment using mailcap entry
9464 pgp-menu p show PGP options
9465 pipe-entry | pipe message/attachment to a shell command
9466 postpone-message P save this message to send later
9467 print-entry l print the current entry
9468 rename-file R rename/move an attached file
9469 send-message y send the message
9470 toggle-unlink u toggle whether to delete file after sending it
9471 view-attach RET view attachment using mailcap entry if necessary
9472 write-fcc w write the message to a folder
9474 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9476 delete-entry d delete the current entry
9477 undelete-entry u undelete the current entry
9479 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9481 The Mutt Next Generation E-Mail Client 181
9483 change-dir c change directories
9484 check-new TAB check mailboxes for new mail
9485 enter-mask m enter a file mask
9486 search / search for a regular expression
9487 search-next n search for next match
9488 search-reverse ESC / search backwards for a regular expression
9489 select-new N select a new file in this directory
9490 sort o sort messages
9491 sort-reverse O sort messages in reverse order
9492 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9493 view-file SPACE view file
9494 subscribe s subscribe to current mailbox (IMAP Only)
9495 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9496 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9498 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9500 view-name % view the key's user id
9501 verify-key c verify a PGP public key
9503 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9505 backspace BackSpace delete the char in front of the cursor
9506 backward-char ^B move the cursor one character to the left
9507 backward-word ESC b move the cursor to the previous word
9508 bol ^A jump to the beginning of the line
9509 buffy-cycle Space cycle among incoming mailboxes
9510 capitalize-word ESC c uppercase the first character in the word
9511 complete TAB complete filename or alias
9512 complete-query ^T complete address with query
9513 delete-char ^D delete the char under the cursor
9514 downcase-word ESC l lowercase all characters in current word
9515 eol ^E jump to the end of the line
9516 forward-char ^F move the cursor one character to the right
9517 forward-word ESC f move the cursor to the next word
9518 history-down not bound scroll down through the history list
9519 history-up not bound scroll up through the history list
9520 kill-eol ^K delete chars from cursor to end of line
9521 kill-eow ESC d delete chars from cursor to end of word
9522 kill-line ^U delete all chars on the line
9523 kill-word ^W delete the word in front of the cursor
9524 quote-char ^V quote the next typed key
9525 transpose-chars not bound transpose character under cursor with previous
9526 upcase-word ESC u uppercase all characters in current word
9528 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9530 The Mutt Next Generation E-Mail Client 182
9532 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9534 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9535 back in the ELM-ME days.
9537 The following people have been very helpful to the development of Mutt:
9539 Vikas Agnihotri <vikasa@writeme.com>,
9541 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9543 Aric Blumer <aric@fore.com>,
9545 John Capo <jc@irbs.com>,
9547 David Champion <dgc@uchicago.edu,
9549 Brendan Cully <brendan@kublai.com>,
9551 Liviu Daia <daia@stoilow.imar.ro>,
9553 Thomas E. Dickey <dickey@herndon4.his.com>,
9555 David DeSimone <fox@convex.hp.com>,
9557 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9559 Ruslan Ermilov <ru@freebsd.org>,
9561 Edmund Grimley Evans <edmundo@rano.org,
9563 Michael Finken <finken@conware.de>,
9565 Sven Guckes <guckes@math.fu-berlin.de>,
9567 Lars Hecking <lhecking@nmrc.ie>,
9569 Mark Holloman <holloman@nando.net>,
9571 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9573 Marco d'Itri <md@linux.it>,
9575 Bjrn Jacke <bjacke@suse.com>,
9577 Byrial Jensen <byrial@image.dk>,
9579 David Jeske <jeske@igcom.net>,
9581 Christophe Kalt <kalt@hugo.int-evry.fr>,
9583 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9585 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9587 The Mutt Next Generation E-Mail Client 183
9589 Brandon Long <blong@fiction.net>,
9591 Jimmy Mkel <jmy@flashback.net>,
9593 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9595 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9597 Andrew W. Nosenko <awn@bcs.zp.ua>,
9599 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9601 Clint Olsen <olsenc@ichips.intel.com>,
9603 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9605 Thomas Parmelan <tom@ankh.fr.eu.org>,
9607 Ollivier Robert <roberto@keltia.freenix.fr>,
9609 Thomas Roessler <roessler@does-not-exist.org>,
9611 Roland Rosenfeld <roland@spinnaker.de>,
9613 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9615 Allain Thivillon <Allain.Thivillon@alma.fr>,
9617 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9619 Vsevolod Volkov <vvv@lucky.net>,
9621 Ken Weinert <kenw@ihs.com>
9623 Mutt-ng is developed by the following people:
9625 Andreas Krennmair <ak@synflood.at>
9627 Nico Golde <nico@ngolde.de>
9629 Rocco Rutte <pdmef@cs.tu-berlin.de>
9631 The following people have been very helpful to the development of Mutt-ng:
9633 Christian Gall <cg@cgall.de>
9635 Iain Lea <iain@bricbrac.de>
9637 Andreas Kneib <akneib@gmx.net>
9639 Carsten Schoelzki <cjs@weisshuhn.de>
9641 Elimar Riesebieter <riesebie@lxtec.de>
9643 The Mutt Next Generation E-Mail Client 184
9645 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9647 This document was written in SGML, and then rendered using the sgml-tools pack-
9650 The Mutt Next Generation E-Mail Client 185
9654 1. Introduction .......................................................... 1
9655 1.1 Overview ........................................................ 1
9656 1.2 Mutt-ng Home Page ............................................... 1
9657 1.3 Mailing Lists ................................................... 1
9658 1.4 Software Distribution Sites ..................................... 2
9659 1.5 IRC ............................................................. 2
9660 1.6 Weblog .......................................................... 2
9661 1.7 Copyright ....................................................... 2
9663 2. Getting Started ..................................................... 2
9664 2.1 Basic Concepts .............................................. 2
9665 2.1.1 Screens and Menus 3
9666 2.1.2 Configuration 3
9669 2.1.5 Modularization 4
9671 2.2 Screens and Menus ........................................... 4
9674 2.2.3 File Browser 5
9677 2.2.6 Compose Menu 6
9679 2.2.8 Attachment Menu 6
9681 2.3 Moving Around in Menus .......................................... 6
9682 2.4 Editing Input Fields ............................................ 7
9683 2.5 Reading Mail - The Index and Pager .............................. 8
9684 2.5.1 The Message Index 8
9686 2.5.3 Threaded Mode 11
9687 2.5.4 Miscellaneous Functions 11
9688 2.6 Sending Mail ................................................... 14
9689 2.6.1 Composing new messages 14
9691 2.6.3 Editing the message header 17
9692 2.6.4 Using Mutt-ng with PGP 18
9693 2.6.5 Sending anonymous messages via mixmaster 19
9694 2.7 Forwarding and Bouncing Mail ................................... 19
9695 2.8 Postponing Mail ................................................ 20
9697 3. Configuration ........................................................ 21
9698 3.1 Locations of Configuration Files ............................... 21
9699 3.2 Basic Syntax of Initialization Files ........................... 21
9700 3.3 Variable Expansion ........................................... 23
9701 3.3.1 Commands' Output 23
9702 3.3.2 Environment Variables 23
9706 3.3.3 Configuration Variables 23
9707 3.3.4 Self-Defined Variables 23
9708 3.3.5 Type Conversions 24
9709 3.4 Defining/Using aliases ......................................... 24
9710 3.5 Changing the default key bindings .............................. 25
9711 3.6 Defining aliases for character sets ........................... 27
9712 3.7 Setting variables based upon mailbox ........................... 27
9713 3.8 Keyboard macros ................................................ 28
9714 3.9 Using color and mono video attributes .......................... 29
9715 3.10 Ignoring (weeding) unwanted message headers .................... 31
9716 3.11 Alternative addresses .......................................... 32
9717 3.12 Format = Flowed .............................................. 32
9718 3.12.1 Introduction 32
9719 3.12.2 Receiving: Display Setup 33
9721 3.12.4 Additional Notes 34
9722 3.13 Mailing lists .................................................. 34
9723 3.14 Using Multiple spool mailboxes ................................. 35
9724 3.15 Defining mailboxes which receive mail .......................... 36
9725 3.16 User defined headers ........................................... 36
9726 3.17 Defining the order of headers when viewing messages ............ 37
9727 3.18 Specify default save filename .................................. 37
9728 3.19 Specify default Fcc: mailbox when composing .................... 38
9729 3.20 Specify default save filename and default Fcc: mailbox at once . 38
9730 3.21 Change settings based upon message recipients .................. 38
9731 3.22 Change settings before formatting a message .................... 39
9732 3.23 Choosing the cryptographic key of the recipient ................ 39
9733 3.24 Adding key sequences to the keyboard buffer .................... 40
9734 3.25 Executing functions ............................................ 40
9735 3.26 Message Scoring ................................................ 40
9736 3.27 Spam detection ................................................. 41
9737 3.28 Setting variables .............................................. 43
9738 3.29 Reading initialization commands from another file .............. 44
9739 3.30 Removing hooks ................................................. 44
9740 3.31 Sharing Setups ............................................. 44
9741 3.31.1 Character Sets 45
9742 3.31.2 Modularization 45
9743 3.31.3 Conditional parts 45
9744 3.32 Obsolete Variables ............................................. 47
9746 4. Advanced Usage ....................................................... 47
9747 4.1 Regular Expressions ............................................ 47
9748 4.2 Patterns ....................................................... 50
9749 4.2.1 Complex Patterns 50
9750 4.2.2 Patterns and Dates 51
9751 4.3 Format Strings ............................................. 52
9752 4.3.1 Introduction 52
9753 4.3.2 Conditional Expansion 53
9754 4.3.3 Modifications and Padding 54
9755 4.4 Using Tags ..................................................... 55
9756 4.5 Using Hooks .................................................... 55
9757 4.5.1 Message Matching in Hooks 56
9758 4.6 Using the sidebar .............................................. 56
9762 4.7 External Address Queries ....................................... 57
9763 4.8 Mailbox Formats ................................................ 58
9764 4.9 Mailbox Shortcuts .............................................. 59
9765 4.10 Handling Mailing Lists ......................................... 59
9766 4.11 Editing threads ................................................ 61
9767 4.11.1 Linking threads 61
9768 4.11.2 Breaking threads 61
9769 4.12 Delivery Status Notification (DSN) Support ..................... 61
9770 4.13 POP3 Support (OPTIONAL) ........................................ 62
9771 4.14 IMAP Support (OPTIONAL) ........................................ 62
9772 4.14.1 The Folder Browser 63
9773 4.14.2 Authentication 64
9774 4.15 NNTP Support (OPTIONAL) ........................................ 64
9775 4.15.1 Again: Scoring 64
9776 4.16 SMTP Support (OPTIONAL) ........................................ 65
9777 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 66
9778 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 66
9779 4.19 Compressed folders Support (OPTIONAL) .......................... 66
9780 4.19.1 Open a compressed mailbox for reading 67
9781 4.19.2 Write a compressed mailbox 68
9782 4.19.3 Append a message to a compressed mailbox 68
9783 4.19.4 Encrypted folders 69
9785 5. Mutt-ng's MIME Support ............................................... 69
9786 5.1 Using MIME in Mutt ............................................. 69
9787 5.1.1 Viewing MIME messages in the pager 69
9788 5.1.2 The Attachment Menu 70
9789 5.1.3 The Compose Menu 70
9790 5.2 MIME Type configuration with mime.types ........................ 71
9791 5.3 MIME Viewer configuration with mailcap ......................... 71
9792 5.3.1 The Basics of the mailcap file 72
9793 5.3.2 Secure use of mailcap 73
9794 5.3.3 Advanced mailcap Usage 73
9795 5.3.4 Example mailcap files 76
9796 5.4 MIME Autoview .................................................. 77
9797 5.5 MIME Multipart/Alternative ..................................... 78
9798 5.6 MIME Lookup .................................................... 78
9800 6. Security Considerations ............................................ 79
9801 6.1 Passwords .................................................. 79
9802 6.2 Temporary Files ............................................ 79
9803 6.3 Information Leaks ............................................ 80
9804 6.3.1 Message-ID: headers 80
9805 6.3.2 mailto:-style links 80
9806 6.4 External applications ...................................... 80
9810 7. Reference ............................................................ 81
9811 7.1 Command line options ........................................... 81
9812 7.2 Patterns ....................................................... 82
9813 7.3 Configuration Commands ......................................... 84
9814 7.4 Configuration variables .......................................... 86
9818 7.4.1 abort_noattach 87
9819 7.4.2 abort_nosubject 88
9820 7.4.3 abort_unmodified 88
9821 7.4.4 agent_string 88
9823 7.4.6 alias_format 88
9826 7.4.9 arrow_cursor 89
9827 7.4.10 ascii_chars 90
9830 7.4.13 assumed_charset 90
9831 7.4.14 attach_format 90
9832 7.4.15 attach_remind_regexp 91
9833 7.4.16 attach_sep 92
9834 7.4.17 attach_split 92
9835 7.4.18 attribution 92
9841 7.4.24 bounce_delivered 93
9842 7.4.25 braille_friendly 93
9843 7.4.26 certificate_file 94
9846 7.4.29 collapse_unread 94
9847 7.4.30 compose_format 95
9848 7.4.31 config_charset 95
9849 7.4.32 confirmappend 95
9850 7.4.33 confirmcreate 95
9851 7.4.34 connect_timeout 95
9852 7.4.35 content_type 96
9854 7.4.37 crypt_autoencrypt 96
9855 7.4.38 crypt_autopgp 96
9856 7.4.39 crypt_autosign 97
9857 7.4.40 crypt_autosmime 97
9858 7.4.41 crypt_replyencrypt 97
9859 7.4.42 crypt_replysign 97
9860 7.4.43 crypt_replysignencrypted 97
9861 7.4.44 crypt_timestamp 98
9862 7.4.45 crypt_use_gpgme 98
9863 7.4.46 crypt_verify_sig 98
9864 7.4.47 date_format 98
9865 7.4.48 default_hook 99
9867 7.4.50 delete_space 99
9868 7.4.51 delete_untag 99
9869 7.4.52 digest_collapse 99
9870 7.4.53 display_filter 100
9874 7.4.54 dotlock_program 100
9875 7.4.55 dsn_notify 100
9876 7.4.56 dsn_return 100
9877 7.4.57 duplicate_threads 101
9878 7.4.58 edit_headers 101
9880 7.4.60 encode_from 101
9881 7.4.61 entropy_file 101
9882 7.4.62 envelope_from 102
9884 7.4.64 fast_reply 102
9885 7.4.65 fcc_attach 102
9886 7.4.66 fcc_clear 102
9887 7.4.67 file_charset 103
9889 7.4.69 folder_format 103
9890 7.4.70 followup_to 104
9891 7.4.71 force_buffy_check 104
9892 7.4.72 force_name 105
9893 7.4.73 forward_decode 105
9894 7.4.74 forward_decrypt 105
9895 7.4.75 forward_edit 105
9896 7.4.76 forward_format 105
9897 7.4.77 forward_quote 106
9899 7.4.79 gecos_mask 106
9902 7.4.82 header_cache 107
9903 7.4.83 header_cache_compress 107
9905 7.4.85 hidden_host 108
9906 7.4.86 hide_limited 108
9907 7.4.87 hide_missing 108
9908 7.4.88 hide_thread_subject 108
9909 7.4.89 hide_top_limited 108
9910 7.4.90 hide_top_missing 108
9912 7.4.92 honor_followup_to 109
9914 7.4.94 ignore_list_reply_to 109
9915 7.4.95 imap_authenticators 109
9916 7.4.96 imap_check_subscribed 110
9917 7.4.97 imap_delim_chars 110
9918 7.4.98 imap_headers 110
9919 7.4.99 imap_home_namespace 111
9920 7.4.100 imap_keepalive 111
9921 7.4.101 imap_list_subscribed 111
9922 7.4.102 imap_login 111
9923 7.4.103 imap_mail_check 112
9924 7.4.104 imap_pass 112
9925 7.4.105 imap_passive 112
9926 7.4.106 imap_peek 112
9930 7.4.107 imap_reconnect 113
9931 7.4.108 imap_servernoise 113
9932 7.4.109 imap_user 113
9933 7.4.110 implicit_autoview 113
9935 7.4.112 include_onlyfirst 114
9936 7.4.113 indent_string 114
9937 7.4.114 index_format 114
9939 7.4.116 keep_flagged 117
9940 7.4.117 list_reply 117
9942 7.4.119 mail_check 117
9943 7.4.120 mailcap_path 118
9944 7.4.121 mailcap_sanitize 118
9945 7.4.122 maildir_header_cache_verify 118
9946 7.4.123 maildir_trash 118
9947 7.4.124 mark_old 118
9950 7.4.127 max_display_recips 119
9951 7.4.128 max_line_length 119
9953 7.4.130 mbox_type 120
9954 7.4.131 menu_context 120
9955 7.4.132 menu_move_off 120
9956 7.4.133 menu_scroll 120
9957 7.4.134 message_format 120
9958 7.4.135 meta_key 121
9960 7.4.137 mh_purge 121
9961 7.4.138 mh_seq_flagged 121
9962 7.4.139 mh_seq_replied 121
9963 7.4.140 mh_seq_unseen 121
9964 7.4.141 mime_forward 122
9965 7.4.142 mime_forward_decode 122
9966 7.4.143 mime_forward_rest 122
9967 7.4.144 mix_entry_format 122
9968 7.4.145 mixmaster 123
9970 7.4.147 msgid_format 123
9971 7.4.148 narrow_tree 124
9972 7.4.149 nntp_ask_followup_to 124
9973 7.4.150 nntp_ask_x_comment_to 124
9974 7.4.151 nntp_cache_dir 125
9975 7.4.152 nntp_catchup 125
9976 7.4.153 nntp_context 125
9977 7.4.154 nntp_followup_to_poster 125
9978 7.4.155 nntp_group_index_format 126
9979 7.4.156 nntp_host 126
9980 7.4.157 nntp_inews 126
9981 7.4.158 nntp_load_description 127
9982 7.4.159 nntp_mail_check 127
9986 7.4.160 nntp_mime_subject 127
9987 7.4.161 nntp_newsrc 127
9988 7.4.162 nntp_pass 128
9989 7.4.163 nntp_post_moderated 128
9990 7.4.164 nntp_reconnect 128
9991 7.4.165 nntp_save_unsubscribed 129
9992 7.4.166 nntp_show_new_news 129
9993 7.4.167 nntp_show_only_unread 129
9994 7.4.168 nntp_user 129
9995 7.4.169 nntp_x_comment_to 129
9996 7.4.170 operating_system 130
9998 7.4.172 pager_context 130
9999 7.4.173 pager_format 130
10000 7.4.174 pager_index_lines 130
10001 7.4.175 pager_stop 131
10002 7.4.176 pgp_auto_decode 131
10003 7.4.177 pgp_autoinline 131
10004 7.4.178 pgp_check_exit 132
10005 7.4.179 pgp_clearsign_command 132
10006 7.4.180 pgp_decode_command 132
10007 7.4.181 pgp_decrypt_command 132
10008 7.4.182 pgp_encrypt_only_command 133
10009 7.4.183 pgp_encrypt_sign_command 133
10010 7.4.184 pgp_entry_format 133
10011 7.4.185 pgp_export_command 134
10012 7.4.186 pgp_getkeys_command 134
10013 7.4.187 pgp_good_sign 134
10014 7.4.188 pgp_ignore_subkeys 134
10015 7.4.189 pgp_import_command 134
10016 7.4.190 pgp_list_pubring_command 135
10017 7.4.191 pgp_list_secring_command 135
10018 7.4.192 pgp_long_ids 135
10019 7.4.193 pgp_mime_auto 135
10020 7.4.194 pgp_replyinline 135
10021 7.4.195 pgp_retainable_sigs 136
10022 7.4.196 pgp_show_unusable 136
10023 7.4.197 pgp_sign_as 136
10024 7.4.198 pgp_sign_command 136
10025 7.4.199 pgp_sort_keys 137
10026 7.4.200 pgp_strict_enc 137
10027 7.4.201 pgp_timeout 137
10028 7.4.202 pgp_use_gpg_agent 137
10029 7.4.203 pgp_verify_command 138
10030 7.4.204 pgp_verify_key_command 138
10031 7.4.205 pipe_decode 138
10032 7.4.206 pipe_sep 138
10033 7.4.207 pipe_split 138
10034 7.4.208 pop_auth_try_all 138
10035 7.4.209 pop_authenticators 139
10036 7.4.210 pop_delete 139
10037 7.4.211 pop_host 139
10038 7.4.212 pop_last 140
10042 7.4.213 pop_mail_check 140
10043 7.4.214 pop_pass 140
10044 7.4.215 pop_reconnect 140
10045 7.4.216 pop_user 140
10046 7.4.217 post_indent_string 141
10047 7.4.218 postpone 141
10048 7.4.219 postponed 141
10049 7.4.220 preconnect 141
10051 7.4.222 print_command 142
10052 7.4.223 print_decode 142
10053 7.4.224 print_split 142
10054 7.4.225 prompt_after 142
10055 7.4.226 query_command 143
10057 7.4.228 quote_empty 143
10058 7.4.229 quote_quoted 143
10059 7.4.230 quote_regexp 143
10060 7.4.231 read_inc 144
10061 7.4.232 read_only 144
10062 7.4.233 realname 144
10065 7.4.236 reply_regexp 145
10066 7.4.237 reply_self 145
10067 7.4.238 reply_to 145
10068 7.4.239 resolve 145
10069 7.4.240 reverse_alias 146
10070 7.4.241 reverse_name 146
10071 7.4.242 reverse_realname 146
10072 7.4.243 rfc2047_parameters 146
10073 7.4.244 save_address 147
10074 7.4.245 save_empty 147
10075 7.4.246 save_name 147
10077 7.4.248 score_threshold_delete 148
10078 7.4.249 score_threshold_flag 148
10079 7.4.250 score_threshold_read 148
10080 7.4.251 send_charset 148
10081 7.4.252 sendmail 149
10082 7.4.253 sendmail_wait 149
10084 7.4.255 sidebar_boundary 149
10085 7.4.256 sidebar_delim 150
10086 7.4.257 sidebar_newmail_only 150
10087 7.4.258 sidebar_number_format 150
10088 7.4.259 sidebar_shorten_hierarchy 151
10089 7.4.260 sidebar_visible 151
10090 7.4.261 sidebar_width 151
10091 7.4.262 sig_dashes 151
10092 7.4.263 sig_on_top 151
10093 7.4.264 signature 152
10094 7.4.265 signoff_string 152
10098 7.4.266 simple_search 152
10099 7.4.267 sleep_time 152
10100 7.4.268 smart_wrap 153
10101 7.4.269 smileys 153
10102 7.4.270 smime_ask_cert_label 153
10103 7.4.271 smime_ca_location 153
10104 7.4.272 smime_certificates 153
10105 7.4.273 smime_decrypt_command 154
10106 7.4.274 smime_decrypt_use_default_key 154
10107 7.4.275 smime_default_key 154
10108 7.4.276 smime_encrypt_command 155
10109 7.4.277 smime_encrypt_with 155
10110 7.4.278 smime_get_cert_command 155
10111 7.4.279 smime_get_cert_email_command 155
10112 7.4.280 smime_get_signer_cert_command 155
10113 7.4.281 smime_import_cert_command 156
10114 7.4.282 smime_is_default 156
10115 7.4.283 smime_keys 156
10116 7.4.284 smime_pk7out_command 156
10117 7.4.285 smime_sign_command 156
10118 7.4.286 smime_sign_opaque_command 157
10119 7.4.287 smime_timeout 157
10120 7.4.288 smime_verify_command 157
10121 7.4.289 smime_verify_opaque_command 157
10122 7.4.290 smtp_envelope 157
10123 7.4.291 smtp_host 157
10124 7.4.292 smtp_pass 158
10125 7.4.293 smtp_port 158
10126 7.4.294 smtp_use_tls 158
10127 7.4.295 smtp_user 159
10129 7.4.297 sort_alias 159
10130 7.4.298 sort_aux 159
10131 7.4.299 sort_browser 160
10132 7.4.300 sort_re 160
10133 7.4.301 spam_separator 161
10134 7.4.302 spoolfile 161
10135 7.4.303 ssl_ca_certificates_file 161
10136 7.4.304 ssl_client_cert 161
10137 7.4.305 ssl_force_tls 161
10138 7.4.306 ssl_min_dh_prime_bits 162
10139 7.4.307 ssl_starttls 162
10140 7.4.308 ssl_use_sslv2 162
10141 7.4.309 ssl_use_sslv3 162
10142 7.4.310 ssl_use_tlsv1 162
10143 7.4.311 ssl_usesystemcerts 163
10144 7.4.312 status_chars 163
10145 7.4.313 status_format 163
10146 7.4.314 status_on_top 165
10147 7.4.315 strict_mailto 166
10148 7.4.316 strict_mime 166
10149 7.4.317 strict_threads 166
10150 7.4.318 strip_was 166
10154 7.4.319 strip_was_regex 167
10155 7.4.320 stuff_quoted 167
10156 7.4.321 suspend 167
10157 7.4.322 text_flowed 167
10158 7.4.323 thorough_search 167
10159 7.4.324 thread_received 168
10161 7.4.326 timeout 168
10163 7.4.328 to_chars 168
10167 7.4.332 uncollapse_jump 169
10168 7.4.333 use_8bitmime 169
10169 7.4.334 use_domain 170
10170 7.4.335 use_from 170
10171 7.4.336 use_idn 170
10172 7.4.337 use_ipv6 170
10174 7.4.339 wait_key 171
10176 7.4.341 wrap_search 171
10177 7.4.342 wrapmargin 171
10178 7.4.343 write_bcc 171
10179 7.4.344 write_inc 172
10180 7.4.345 xterm_icon 172
10181 7.4.346 xterm_leave 172
10182 7.4.347 xterm_set_titles 172
10183 7.4.348 xterm_title 172
10184 7.5 Functions ....................................................... 173
10197 8. Miscellany ............................................................ 181
10198 8.1 Acknowledgments ................................................. 182
10199 8.2 About this document ............................................. 184