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 27) 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.336 , page 171) 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 30) 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 78) 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.304 , page 161) 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.116 , page 115). 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.116 , page 115) 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.325 , page 168).
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 26) 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 89) 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 89) 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 32) 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 71), 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 71). 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 29) 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 36) 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.94 , page 110) 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.213 , page 140), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.215 , page 141), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.214 , page 140) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.347 , page 173) 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.348 , page 173) 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.347 , page 173) 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.238 , page 146) 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.321 , page 165) 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.59 , page 102).
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.205 , page 139) 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.192 , page 135)) 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.146 ,
951 page 124)). 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.227 , page 143) 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.226 , page 143) 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 82) 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 85) 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 85). 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 85).
1108 The Mutt Next Generation E-Mail Client 23
1110 _
\b3_
\b._
\b3 _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn _
\bw_
\bi_
\bt_
\bh_
\bi_
\bn _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1112 Besides just assign static content to variables, there's plenty of ways of
1113 adding external and more or less dynamic content.
1115 _
\b3_
\b._
\b3_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs_
\b' _
\bO_
\bu_
\bt_
\bp_
\bu_
\bt
1117 It is possible to substitute the output of a Unix command in an initialization
1118 file. This is accomplished by enclosing the command in backquotes (``) as in,
1121 my_hdr X-Operating-System: `uname -a`
1123 The output of the Unix command ``uname -a'' will be substituted before the line
1124 is parsed. Note that since initialization files are line oriented, only the
1125 first line of output from the Unix command will be substituted.
1127 _
\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
1129 UNIX environments can be accessed like the way it is done in shells like sh and
1130 bash: Prepend the name of the environment by a ``$'' sign. For example,
1132 set record=+sent_on_$HOSTNAME
1134 sets the _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.243 , page 147) variable to the string _
\b+_
\bs_
\be_
\bn_
\bt_
\b__
\bo_
\bn_
\b_
1135 and appends the value of the evironment variable $HOSTNAME.
1137 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if an environment variable is not defined. The
1138 result will of the expansion will then be empty.
1140 _
\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
1142 As for environment variables, the values of all configuration variables as
1143 string can be used in the same way, too. For example,
1145 set imap_home_namespace = $folder
1147 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.101 , page 112) to
1148 the value to which _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 104) is _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by set to.
1150 N
\bNo
\bot
\bte
\be:
\b: There're no logical links established in such cases so that the the value
1151 for _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.101 , page 112) won't change even if
1152 _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 104) gets changed.
1154 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if a configuration variable is not defined or is
1155 empty. The result will of the expansion will then be empty.
1157 The Mutt Next Generation E-Mail Client 24
1159 _
\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
1161 Mutt-ng flexibly allows users to define their own variables. To avoid conflicts
1162 with the standard set and to prevent misleading error messages, there's a
1163 reserved namespace for them: all user-defined variables must be prefixed with
1164 user_ and can be used just like any ordinary configuration or environment vari-
1167 For example, to view the manual, users can either define two macros like the
1170 macro generic <F1> "!less -r /path/to/manual" "Show manual"
1171 macro pager <F1> "!less -r /path/to/manual" "Show manual"
1173 for generic, pager and index. The alternative is to define a custom variable
1176 set user_manualcmd = "!less -r /path/to_manual"
1177 macro generic <F1> "$user_manualcmd<enter>" "Show manual"
1178 macro pager <F1> "$user_manualcmd<enter>" "Show manual"
1179 macro index <F1> "$user_manualcmd<enter>" "Show manual"
1181 to re-use the command sequence as in:
1183 macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
1185 Using this feature, arbitrary sequences can be defined once and recalled and
1186 reused where necessary. More advanced scenarios could include to save a vari-
1187 able's value at the beginning of macro sequence and restore it at end.
1189 When the variable is first defined, the first value it gets assigned is also
1190 the initial value to which it can be reset using the reset command.
1192 The complete removal is done via the unset keyword.
1194 After the following sequence:
1199 the variable $user_foo has a current value of 666 and an initial of 42. The
1204 The Mutt Next Generation E-Mail Client 25
1206 will show 666. After doing the reset via
1210 a following query will give 42 as the result. After unsetting it via
1214 any query or operation (except the noted expansion within other statements)
1215 will lead to an error message.
1217 _
\b3_
\b._
\b3_
\b._
\b5 _
\bP_
\br_
\be_
\b-_
\bD_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1219 In order to allow users to share one setup over a number of different machines
1220 without having to change its contents, there's a number of pre-defined vari-
1221 ables. These are prefixed with muttng_ and are read-only, i.e. they cannot be
1222 set, unset or reset. The reference chapter lists all available variables.
1224 _
\bP_
\bl_
\be_
\ba_
\bs_
\be _
\bc_
\bo_
\bn_
\bs_
\bu_
\bl_
\bt _
\bt_
\bh_
\be _
\bl_
\bo_
\bc_
\ba_
\bl _
\bc_
\bo_
\bp_
\by _
\bo_
\bf _
\by_
\bo_
\bu_
\br _
\bm_
\ba_
\bn_
\bu_
\ba_
\bl _
\bf_
\bo_
\br _
\bt_
\bh_
\be_
\bi_
\br _
\bv_
\ba_
\bl_
\bu_
\be_
\bs _
\ba_
\bs _
\bt_
\bh_
\be_
\by _
\bm_
\ba_
\by _
\bd_
\bi_
\bf_
\b-
1225 _
\bf_
\be_
\br _
\bf_
\br_
\bo_
\bm _
\bd_
\bi_
\bf_
\bf_
\be_
\br_
\be_
\bn_
\bt _
\bm_
\ba_
\bn_
\bu_
\ba_
\bl _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bs_
\b. Where the manual is installed in can be
1226 queried (already using such a variable) by running:
1228 muttng -Q muttng_docdir
1230 To extend the example for viewing the manual via self-defined variables, it can
1231 be made more readable and more portable by changing the real path in:
1233 set user_manualcmd = '!less -r /path/to_manual'
1237 set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
1239 which works everywhere if a manual is installed.
1241 _
\bN_
\bo_
\bt_
\be_
\b: _
\bt_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\bd_
\br_
\ba_
\bf_
\bt _
\bf_
\be_
\ba_
\bt_
\bu_
\br_
\be _
\ba_
\bn_
\bd _
\bm_
\ba_
\by_
\bb_
\be _
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt _
\bt_
\bo _
\bc_
\bh_
\ba_
\bn_
\bg_
\be _
\bi_
\bn _
\bt_
\bh_
\be _
\bn_
\be_
\ba_
\br _
\bf_
\bu_
\bt_
\bu_
\br_
\be_
\b.
1243 _
\b3_
\b._
\b3_
\b._
\b6 _
\bT_
\by_
\bp_
\be _
\bC_
\bo_
\bn_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn_
\bs
1245 A note about variable's types during conversion: internally values are stored
1246 in internal types but for any dump/query or set operation they're converted to
1247 and from string. That means that there's no need to worry about types when ref-
1248 erencing any variable. As an example, the following can be used without harm
1249 (besides makeing muttng very likely behave strange):
1251 The Mutt Next Generation E-Mail Client 26
1254 set folder = $read_inc
1255 set read_inc = $folder
1256 set user_magic_number = 42
1257 set folder = $user_magic_number
1259 _
\b3_
\b._
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1261 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1263 It's usually very cumbersome to remember or type out the address of someone you
1264 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1265 short string to a full address.
1267 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1268 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1270 To remove an alias or aliases (``*'' means all aliases):
1272 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1274 alias muttdude me@cs.hmc.edu (Michael Elkins)
1275 alias theguys manny, moe, jack
1277 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1278 cial file. The alias command can appear anywhere in a configuration file, as
1279 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.29 , page 45). Consequently, you can
1280 have multiple alias files, or you can have all aliases defined in your muttrc.
1282 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
1283 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 89)
1284 variable (which is ~/.muttrc by default). This file is not special either, in
1285 the sense that Mutt-ng will happily append aliases to any file, but in order
1286 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1287 3.29 , page 45) this file too.
1291 source /usr/local/share/Mutt-ng.aliases
1292 source ~/.mail_aliases
1293 set alias_file=~/.mail_aliases
1295 To use aliases, you merely use the alias at any place in mutt where mutt
1296 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1297 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
1298 (section 7.4.59 , page 102) variable set.
1300 In addition, at the various address prompts, you can use the tab character to
1301 expand a partial alias to the full alias. If there are multiple matches, mutt
1303 The Mutt Next Generation E-Mail Client 27
1305 will bring up a menu with the matching aliases. In order to be presented with
1306 the full list of aliases, you must hit tab with out a partial alias, such as at
1307 the beginning of the prompt or after a comma denoting multiple addresses.
1309 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1310 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1313 _
\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
1315 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1317 This command allows you to change the default key bindings (operation invoked
1318 when pressing a key).
1320 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be speci-
1321 fied by separating them with commas (no additional whitespace is allowed). The
1322 currently defined maps are:
1325 This is not a real menu, but is used as a fallback for all of the
1326 other menus except for the pager and editor modes. If a key is not
1327 defined in another menu, Mutt-ng will look for a binding to use in
1328 this menu. This allows you to bind a key to a certain function in
1329 multiple menus instead of having multiple bind statements to accom-
1330 plish the same task.
1333 The alias menu is the list of your personal aliases as defined in
1334 your muttrc. It is the mapping from a short alias name to the full
1335 email address(es) of the recipient(s).
1338 The attachment menu is used to access the attachments on received
1342 The browser is used for both browsing the local directory struc-
1343 ture, and for listing all of your incoming mailboxes.
1346 The editor is the line-based editor the user enters text data.
1349 The index is the list of messages contained in a mailbox.
1352 The compose menu is the screen used when sending a new message.
1354 The Mutt Next Generation E-Mail Client 28
1357 The pager is the mode used to display message/attachment data, and
1361 The pgp menu is used to select the OpenPGP keys used for encrypting
1365 The postpone menu is similar to the index menu, except is used when
1366 recalling a message the user was composing, but saved until later.
1368 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1369 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1370 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1371 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
1372 alternative form is to specify the key as a three digit octal number prefixed
1373 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1375 In addition, _
\bk_
\be_
\by may consist of:
1379 <backtab> backtab / shift-tab
1389 <pagedown> Page Down
1390 <backspace> Backspace
1399 <f10> function key 10
1401 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1403 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1404 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 175). The special
1405 function noop unbinds the specified key sequence.
1407 The Mutt Next Generation E-Mail Client 29
1409 _
\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
1411 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1413 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1415 The charset-hook command defines an alias for a character set. This is useful
1416 to properly display messages which are tagged with a character set name not
1419 The iconv-hook command defines a system-specific name for a character set.
1420 This is helpful when your systems character conversion library insists on using
1421 strange, system-specific names for character sets.
1423 _
\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
1425 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1427 It is often desirable to change settings based on which mailbox you are read-
1428 ing. The folder-hook command provides a method by which you can execute any
1429 configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1430 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1431 folder-hook's, they are executed in the order given in the muttrc.
1433 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.310 , page
1434 163) at the beginning of the pattern, you must place it inside of double or
1435 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1438 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1439 ple, a command action to perform is to change the sorting method based upon the
1442 folder-hook mutt set sort=threads
1444 However, the sorting method is not restored to its previous value when reading
1445 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1447 folder-hook . set sort=date-sent
1449 _
\b3_
\b._
\b8 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1451 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 ]
1453 Macros are useful when you would like a single key to perform a series of
1454 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1456 The Mutt Next Generation E-Mail Client 30
1458 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1459 create a macro to execute those commands with a single key.
1461 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.5 , page 27) which the macro will be bound. Multi-
1462 ple maps may be specified by separating multiple menu arguments by commas.
1463 Whitespace may not be used in between the menu arguments and the commas sepa-
1466 _
\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
1467 3.5 , page 27). There are some additions however. The first is that control
1468 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1469 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1470 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
1471 _
\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
1472 3.5 , page 27). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1475 The advantage with using function names directly is that the macros will work
1476 regardless of the current key bindings, so they are not dependent on the user
1477 having particular key definitions. This makes them more robust and portable,
1478 and also facilitates defining of macros in files used by more than one user
1479 (eg. the system Muttngrc).
1481 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1484 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1485 truncated at the screen width, and are not wrapped.
1487 _
\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
1489 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 ]
1491 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
1493 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1495 If your terminal supports color, you can spice up Mutt-ng by creating your own
1496 color scheme. To define the color of an object (type of information), you must
1497 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1498 only specify one or the other).
1500 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1504 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1506 +
\bo bold (highlighting bold patterns in the body of messages)
1508 +
\bo error (error messages printed by Mutt-ng)
1510 The Mutt Next Generation E-Mail Client 31
1512 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1514 +
\bo hdrdefault (default color of the message header in the pager)
1516 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1518 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1520 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1522 +
\bo message (informational messages)
1526 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.238 , page 146) in the
1529 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1531 +
\bo search (highlighting of words in the pager)
1535 +
\bo status (mode lines used to display info about the mailbox or message)
1537 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1539 +
\bo tree (thread tree drawn in the message index and attachment menu)
1541 +
\bo underline (highlighting underlined patterns in the body of messages)
1543 _
\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:
1565 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the
1567 The Mutt Next Generation E-Mail Client 32
1569 foreground color boldfaced (e.g., brightred).
1571 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1572 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1573 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-
1574 ment variable to the default colors of your terminal for this to work; for
1575 example (for Bourne-like shells):
1577 set COLORFGBG="green;black"
1580 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
1581 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1583 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1584 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1585 command for it to be removed. The pattern ``*'' is a special token which means
1586 to clear the color index list of all entries.
1588 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
1589 number of colors supported by your terminal). This is useful when you remap
1590 the colors for your display (for example by changing the color associated with
1591 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1593 If your terminal does not support color, it is still possible change the video
1594 attributes through the use of the ``mono'' command:
1596 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 ]
1598 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1600 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1602 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1614 _
\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
1616 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1618 Messages often have many header fields added by automatic processing systems,
1620 The Mutt Next Generation E-Mail Client 33
1622 or which may not seem useful to display on the screen. This command allows you
1623 to specify header fields which you don't normally want to see.
1625 You do not need to specify the full header field name. For example, ``ignore
1626 content-'' will ignore all header fields that begin with the pattern ``con-
1627 tent-''. ``ignore *'' will ignore all headers.
1629 To remove a previously added token from the list, use the ``unignore'' command.
1630 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1631 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1634 ``unignore *'' will remove all tokens from the ignore list.
1638 # Sven's draconian header weeding
1640 unignore from date subject to cc
1641 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1644 _
\b3_
\b._
\b1_
\b1 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1646 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1648 With various functions, mutt will treat messages differently, depending on
1649 whether you sent them or whether you received them from someone else. For
1650 instance, when replying to a message that you sent to a different party, mutt
1651 will automatically suggest to send the response to the original message's
1652 recipients -- responding to yourself won't make much sense in many cases. (See
1653 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.246 , page 148).)
1655 Many users receive e-mail under a number of different addresses. To fully use
1656 mutt's features here, the program must be able to recognize what e-mail
1657 addresses you receive mail under. That's the purpose of the alternates command:
1658 It takes a list of regular expressions, each of which can identify an address
1659 under which you receive e-mail.
1661 The unalternates command can be used to write exceptions to alternates pat-
1662 terns. If an address matches something in an alternates command, but you none-
1663 theless do not think it is from you, you can list a more precise pattern under
1664 an unalternates command.
1666 To remove a regular expression from the alternates list, use the unalternates
1667 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1668 command matches an entry on the unalternates list, that unalternates entry will
1669 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
1672 The Mutt Next Generation E-Mail Client 34
1674 _
\b3_
\b._
\b1_
\b2 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1676 _
\b3_
\b._
\b1_
\b2_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
1678 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1679 ning of email, each message had a fixed line width, and it was enough for dis-
1680 playing them on fixed-size terminals. But times changed, and nowadays hardly
1681 anybody still uses fixed-size terminals: more people nowaydays use graphical
1682 user interfaces, with dynamically resizable windows. This led to the demand of
1683 a new email format that makes it possible for the email client to make the
1684 email look nice in a resizable window without breaking quoting levels and cre-
1685 ating an incompatible email format that can also be displayed nicely on old
1686 fixed-size terminals.
1688 For introductory information on format=flowed messages, see
1689 <http://www.joeclark.org/ffaq.html>.
1691 _
\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
1693 When you receive emails that are marked as format=flowed messages, and is for-
1694 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1695 your terminal. If you want a fixed margin on the right side of your terminal,
1696 you can set the following:
1700 The code above makes the line break 10 columns before the right side of the
1703 If your terminal is so wide that the lines are embarrassingly long, you can
1704 also set a maximum line length:
1706 set max_line_length = 120
1708 The example above will give you lines not longer than 120 characters.
1710 When you view at format=flowed messages, you will often see the quoting hierar-
1711 chy like in the following example:
1713 >Bill, can you please send last month's progress report to Mr.
1714 >Morgan? We also urgently need the cost estimation for the new
1715 >production server that we want to set up before our customer's
1716 >project will go live.
1718 This obviously doesn't look very nice, and it makes it very hard to
1720 The Mutt Next Generation E-Mail Client 35
1722 differentiate between text and quoting character. The solution is to configure
1723 mutt-ng to "stuff" the quoting:
1727 This will lead to a nicer result that is easier to read:
1729 > Bill, can you please send last month's progress report to Mr.
1730 > Morgan? We also urgently need the cost estimation for the new
1731 > production server that we want to set up before our customer's
1732 > project will go live.
1734 _
\b3_
\b._
\b1_
\b2_
\b._
\b3 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg
1736 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1741 Additionally, you have to use an editor which supports writing format=flowed-
1742 conforming emails. For vim, this is done by adding w to the formatoptions (see
1743 :h formatoptions and :h fo-table) when writing emails.
1745 Also note that _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\b=_
\bf_
\bl_
\bo_
\bw_
\be_
\bd knows about ``space-stuffing'', that is, when
1746 sending messages, some kinds of lines have to be indented with a single space
1747 on the sending side. On the receiving side, the first space (if any) is
1748 removed. As a consequence and in addition to the above simple setting, please
1749 keep this in mind when making manual formattings within the editor. Also note
1750 that mutt-ng currently violates the standard (RfC 3676) as it does not space-
1751 stuff lines starting with:
1753 +
\bo > This is _
\bn_
\bo_
\bt the quote character but a right angle used for other reasons
1755 +
\bo From with a trailing space.
1757 +
\bo just a space for formatting reasons
1759 Please make sure that you manually prepend a space to each of them.
1761 _
\b3_
\b._
\b1_
\b2_
\b._
\b4 _
\bA_
\bd_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bN_
\bo_
\bt_
\be_
\bs
1765 For completeness, the _
\b$_
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.51 , page 100) variable pro-
1766 vides the mechanism to generate a DelSp=yes parameter on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages.
1768 The Mutt Next Generation E-Mail Client 36
1770 According to the standard, clients receiving a format=flowed messages should
1771 delete the last space of a flowed line but still interpret the line as flowed.
1772 Because flowed lines usually contain only one space at the end, this parameter
1773 would make the receiving client concatenate the last word of the previous with
1774 the first of the current line _
\bw_
\bi_
\bt_
\bh_
\bo_
\bu_
\bt a space. This makes ordinary text unread-
1775 able and is intended for languages rarely using spaces. So please use this set-
1776 ting only if you're sure what you're doing.
1778 _
\b3_
\b._
\b1_
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1780 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1782 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1784 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 ,
1785 page 60). In order to take advantage of them, you must specify which addresses
1786 belong to mailing lists, and which mailing lists you are subscribed to. Once
1787 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1788 work for all known lists. Additionally, when you send a message to a sub-
1789 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1790 user agents not to send copies of replies to your personal address. Note that
1791 the Mail-Followup-To header is a non-standard extension which is not supported
1792 by all mail user agents. Adding it is not bullet-proof against receiving per-
1793 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1794 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.72 , page 105)
1795 configuration variable.
1797 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1798 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1799 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1802 You can use regular expressions with both commands. To mark all messages sent
1803 to a specific bug report's address on mutt's bug tracking system as list mail,
1804 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1805 sufficient to just give a portion of the list's e-mail address.
1807 Specify as much of the address as you need to to remove ambiguity. For exam-
1808 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1809 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
1810 list, you could add ``lists mutt-users'' to your initialization file. To tell
1811 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1812 tialization file instead. If you also happen to get mail from someone whose
1813 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-
1814 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1815 from the actual list.
1817 The ``unlists'' command is used to remove a token from the list of known and
1818 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1820 To remove a mailing list from the list of subscribed mailing lists, but keep it
1821 on the list of known mailing lists, use ``unsubscribe''.
1823 The Mutt Next Generation E-Mail Client 37
1825 _
\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
1827 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1829 This command is used to move read messages from a specified mailbox to a dif-
1830 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1831 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1832 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1834 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1835 (it is not possible to save read mail in more than a single mailbox).
1837 _
\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
1839 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1841 This command specifies folders which can receive mail and which will be checked
1842 for new messages. By default, the main menu status bar displays how many of
1843 these folders have new messages.
1845 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1847 Pressing TAB in the directory browser will bring up a menu showing the files
1848 specified by the mailboxes command, and indicate which contain new messages.
1849 Mutt-ng will automatically enter this mode when invoked from the command line
1852 The ``unmailboxes'' command is used to remove a token from the list of folders
1853 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1855 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1856 access time. Utilities like biff or frm or any other program which accesses
1857 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1858 they do not properly reset the access time. Backup tools are another common
1859 reason for updated access times.
1861 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1862 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
1863 60) (such as ``='' and ``!''), any variable definition that affect these char-
1864 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 104) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1865 7.4.310 , page 163)) should be executed before the mailboxes command.
1867 _
\b3_
\b._
\b1_
\b6 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1871 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1873 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1875 The Mutt Next Generation E-Mail Client 38
1877 The ``my_hdr'' command allows you to create your own header fields which will
1878 be added to every message you send.
1880 For example, if you would like to add an ``Organization:'' header field to all
1881 of your outgoing messages, you can put the command
1883 my_hdr Organization: A Really Big Company, Anytown, USA
1887 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1888 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1889 there, so Mutt-ng enforces the rule.
1891 If you would like to add a header field to a single message, you should either
1892 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1893 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1894 header of your message along with the body.
1896 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1897 specify an asterisk (``*'') to remove all header fields, or the fields to
1898 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1903 _
\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
1905 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1907 With this command, you can specify an order in which mutt will attempt to
1908 present headers to you when viewing messages.
1910 ``unhdr_order *'' will clear all previous headers from the order list, thus
1911 removing the header order effects set by the system-wide startup file.
1913 hdr_order From Date: From: To: Cc: Subject:
1915 _
\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
1917 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1919 This command is used to override the default filename used when saving mes-
1920 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:
1922 The Mutt Next Generation E-Mail Client 39
1924 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1925 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1927 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 57) for information on the
1928 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1932 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1933 save-hook aol\\.com$ +spam
1935 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39) command.
1937 _
\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
1939 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1941 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1942 (section 7.4.243 , page 147). Mutt-ng searches the initial list of message
1943 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1944 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1945 7.4.243 , page 147) mailbox.
1947 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 57) for information on the
1948 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1950 Example: fcc-hook [@.]aol\\.com$ +spammers
1952 The above will save a copy of all messages going to the aol.com domain to the
1953 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 ,
1956 _
\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
1958 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1960 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1961 3.19 , page 39) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38) with its arguments.
1963 _
\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
1965 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1967 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1969 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1971 The Mutt Next Generation E-Mail Client 40
1973 These commands can be used to execute arbitrary configuration commands based
1974 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1975 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1978 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1979 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1980 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
1981 the order specified in the users's configuration file.
1983 send2-hook is matched every time a message is changed, either by editing it, or
1984 by using the compose menu to change its recipients or subject. send2-hook is
1985 executed after send-hook, and can, e.g., be used to set parameters such as the
1986 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.260 , page 151) variable depending on the message's
1989 For each type of send-hook or reply-hook, when multiple matches occur, commands
1990 are executed in the order they are specified in the muttrc (for that type of
1993 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 57) for information on the
1994 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1996 Example: send-hook mutt 'set mime_forward signature='''
1998 Another typical use for this command is to change the values of the _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\b-
1999 _
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 93), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.272 , page 154) and
2000 _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.120 , page 119) variables in order to change the language
2001 of the attributions and signatures based upon the recipients.
2003 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
2004 recipients. Adding a recipient after replying or editing the message will NOT
2005 cause any send-hook to be executed. Also note that my_hdr commands which mod-
2006 ify recipient headers, or the message's subject, don't have any effect on the
2007 current message when executed from a send-hook.
2009 _
\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
2011 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
2013 This command can be used to execute arbitrary configuration commands before
2014 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
2015 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
2016 tiple matches occur, commands are executed in the order they are specified in
2019 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 57) for information on the
2020 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
2024 message-hook ~A 'set pager=builtin'
2026 The Mutt Next Generation E-Mail Client 41
2028 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
2030 _
\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
2032 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
2034 When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
2035 tain key with a given e-mail address automatically, either because the recipi-
2036 ent's public key can't be deduced from the destination address, or because, for
2037 some reasons, you need to override the key Mutt-ng would normally use. The
2038 crypt-hook command provides a method by which you can specify the ID of the
2039 public key to be used when encrypting messages to a certain recipient.
2041 The meaning of "key id" is to be taken broadly in this context: You can either
2042 put a numerical key ID here, an e-mail address, or even just a real name.
2044 _
\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
2046 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
2048 This command adds the named string to the keyboard buffer. The string may con-
2049 tain control characters, key names and function names like the sequence string
2050 in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 29) command. You may use it to automatically
2051 run a sequence of commands at startup, or when entering certain folders.
2053 _
\b3_
\b._
\b2_
\b5 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
2055 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
2057 This command can be used to execute any function. Functions are listed in the
2058 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 175). ``exec function'' is equivalent
2059 to ``push <function>''.
2061 _
\b3_
\b._
\b2_
\b6 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
2063 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
2065 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
2067 In situations where you have to cope with a lot of emails, e.g. when you read
2068 many different mailing lists, and take part in discussions, it is always useful
2069 to have the important messages marked and the annoying messages or the ones
2070 that you aren't interested in deleted. For this purpose, mutt-ng features a
2071 mechanism called ``scoring''.
2073 The Mutt Next Generation E-Mail Client 42
2075 When you use scoring, every message has a base score of 0. You can then use the
2076 score command to define patterns and a positive or negative value associated
2077 with it. When a pattern matches a message, the message's score will be raised
2078 or lowered by the amount of the value associated with the pattern.
2080 score "~f nion@muttng\.org" 50
2081 score "~f @sco\.com" -100
2083 If the pattern matches, it is also possible to set the score value of the cur-
2084 rent message to a certain value and then stop evaluation:
2086 score "~f santaclaus@northpole\.int" =666
2088 What is important to note is that negative score values will be rounded up to
2091 To make scoring actually useful, the score must be applied in some way. That's
2092 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:
2094 +
\bo flag threshold: when a message has a score value equal or higher than the
2095 flag threshold, it will be flagged.
2097 +
\bo read threshold: when a message has a score value equal or lower than the
2098 read threshold, it will be marked as read.
2100 +
\bo delete threshold: when a message has a score value equal or lower than the
2101 delete threshold, it will be marked as deleted.
2103 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-
2104 tion 7.4.257 , page 150), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.258 , page 151),
2105 _
\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.256 , page 150) and. By default,
2106 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.258 , page 151) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
2107 (section 7.4.256 , page 150) are set to -1, which means that in the default
2108 threshold configuration no message will ever get marked as read or deleted.
2110 Scoring gets especially interesting when combined with the color command and
2113 color index black yellow "~n 10-"
2114 color index red yellow "~n 100-"
2116 The rules above mark all messages with a score between 10 and 99 with black and
2117 yellow, and messages with a score greater or equal 100 with red and yellow.
2118 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
2119 but it is more flexible, as it visually marks different scores.
2121 The Mutt Next Generation E-Mail Client 43
2123 _
\b3_
\b._
\b2_
\b7 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
2125 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2127 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
2129 Mutt-ng has generalized support for external spam-scoring filters. By defining
2130 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
2131 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
2132 filter. You also can display the spam attributes in your index display using
2133 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115) variable.
2134 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
2137 Your first step is to define your external filter's spam patterns using the
2138 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
2139 mail message. If any message in the mailbox matches this regular expression, it
2140 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
2141 nospam pattern -- see below.) The appearance of this attribute is entirely up
2142 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,
2143 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
2144 expression ``back-reference'' refers to a sub-expression contained within
2145 parentheses.) %1 is replaced with the first back-reference in the regex, %2
2146 with the second, etc.
2148 If you're using multiple spam filters, a message can have more than one spam-
2149 related header. You can define spam patterns for each filter you use. If a mes-
2150 sage matches two or more of these patterns, and the $spam_separator variable is
2151 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2152 strings joined together, with the value of $spam_separator separating them.
2154 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
2155 these spam settings:
2157 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
2158 spam "X-Spam-Status: Yes" "90+/SA"
2159 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
2160 set spam_separator=", "
2162 If I then received a message that DCC registered with ``many'' hits under the
2163 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
2164 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
2165 characters before ``=many'' in a DCC report indicate the checksum used -- in
2166 this case, ``Fuz2''.)
2168 If the $spam_separator variable is unset, then each spam pattern match super-
2169 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
2170 only the last one to match.
2172 The spam tag is what will be displayed in the index when you use %H in the
2173 $index_format variable. It's also the string that the ~H pattern-matching
2174 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2175 ing by spam attribute will use as a sort key.
2177 The Mutt Next Generation E-Mail Client 44
2179 That's a pretty complicated example, and most people's actual environments will
2180 have only one spam filter. The simpler your configuration, the more effective
2181 mutt can be, especially when it comes to sorting.
2183 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2184 ordering strings alphnumerically. However, if a spam tag begins with a number,
2185 mutt will sort numerically first, and lexically only when two numbers are equal
2186 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2187 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2188 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2189 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2190 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2191 coerce your filter to give you a raw number. But in case you can't, mutt can
2192 still do something useful.
2194 The nospam command can be used to write exceptions to spam patterns. If a
2195 header pattern matches something in a spam command, but you nonetheless do not
2196 want it to receive a spam tag, you can list a more precise pattern under a
2199 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-
2200 ing spam list entry, the effect will be to remove the entry from the spam list,
2201 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2202 matches an entry on the nospam list, that nospam entry will be removed. If the
2203 _
\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
2204 might be the default action if you use spam and nospam in conjunction with a
2207 You can have as many spam or nospam commands as you like. You can even do your
2208 own primitive spam detection within mutt -- for example, if you consider all
2209 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2211 spam "^From: .*MAILER-DAEMON" "999"
2213 _
\b3_
\b._
\b2_
\b8 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2215 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 ... ]
2217 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2219 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2221 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2223 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 ,
2224 page 87). There are four basic types of variables: boolean, number, string and
2225 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
2226 variables can be assigned a positive integer value.
2228 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2230 The Mutt Next Generation E-Mail Client 45
2232 be enclosed in quotes if they contain spaces or tabs. You may also use the
2233 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2235 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2236 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2237 action to be carried out automatically as if you had answered yes to the ques-
2238 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2239 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2240 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2242 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2244 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2245 toggle the value (on or off). This is useful when writing macros. Example:
2248 The toggle command automatically prepends the inv prefix to all specified vari-
2251 The unset command automatically prepends the no prefix to all specified vari-
2254 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2255 a variable by prefixing the name of the variable with a question mark:
2259 The question mark is actually only required for boolean and quadoption vari-
2262 The reset command resets all given variables to the compile time defaults
2263 (hopefully mentioned in this manual). If you use the command set and prefix the
2264 variable with ``&'' this has the same behavior as the reset command.
2266 With the reset command there exists the special variable ``all'', which allows
2267 you to reset all variables to their system defaults.
2269 _
\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
2271 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2273 This command allows the inclusion of initialization commands from other files.
2274 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2275 ~/.muttrc readable and keep my aliases private.
2277 If the filename begins with a tilde (``~''), it will be expanded to the path of
2278 your home directory.
2280 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2281 an executable program from which to read input (eg. source ~/bin/myscript|).
2283 The Mutt Next Generation E-Mail Client 46
2285 _
\b3_
\b._
\b3_
\b0 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2287 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2289 This command permits you to flush hooks you have previously defined. You can
2290 either remove all hooks by giving the ``*'' character as an argument, or you
2291 can remove all hooks of a specific type by saying something like unhook send-
2294 _
\b3_
\b._
\b3_
\b1 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2296 _
\b3_
\b._
\b3_
\b1_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2298 As users may run mutt-ng on different systems, the configuration must be main-
2299 tained because it's likely that people want to use the setup everywhere they
2300 use mutt-ng. And mutt-ng tries to help where it can.
2302 To not produce conflicts with different character sets, mutt-ng allows users to
2303 specify in which character set their configuration files are encoded. Please
2304 note that while reading the configuration files, this is only respected after
2305 the corresponding declaration appears. It's advised to put the following at the
2306 very beginning of a users muttngrc:
2308 set config_charset = "..."
2310 and replacing the dots with the actual character set. To avoid problems while
2311 maintaining the setup, vim user's may want to use modelines as show in:
2313 # vim:fileencoding=...:
2315 while, again, replacing the dots with the appropriate name. This tells vim as
2316 which character set to read and save the file.
2318 _
\b3_
\b._
\b3_
\b1_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2320 ``Modularization'' means to divide the setup into several files while sorting
2321 the options or commands by topic. Especially for longer setups (e.g. with many
2322 hooks), this helps maintaining it and solving trouble.
2324 When using separation, setups may be, as a whole or in fractions, shared over
2327 _
\b3_
\b._
\b3_
\b1_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2329 The Mutt Next Generation E-Mail Client 47
2331 When using a configuration on different systems, the user may not always have
2332 influence on how mutt-ng is installed and which features it includes.
2334 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2335 for mutt. Its basic syntax is:
2337 ifdef <item> <command>
2338 ifndef <item> <command>
2340 ...whereby <item> can be one of:
2342 +
\bo a function name
2344 +
\bo a variable name
2350 All available functions, variables and menus are documented elsewhere in this
2351 manual but ``features'' is specific to these two commands. To test for one,
2352 prefix one of the following keywords with feature_:
2354 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2355 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2356 classic_smime, gpgme, header_cache
2358 As an example, one can use the following in ~/.muttngrc:
2360 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2361 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2362 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2364 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2365 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2366 ng/setup-nntp if NNTP support is built in.
2368 An example for testing for variable names can be used if users use different
2369 revisions of mutt-ng whereby the older one may not have a certain variable. To
2370 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.105 , page 113),
2373 ifdef imap_mail_check 'set imap_mail_check = 300'
2375 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
2376 (section 7.4.182 , page 133) only if the pager menu is available, use:
2378 The Mutt Next Generation E-Mail Client 48
2380 ifdef pager 'set pager_index_lines = 10'
2382 For completeness, too, the opposite of ifdef is provided: ifndef which only
2383 executes the command if the test fails. For example, the following two examples
2386 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2387 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2391 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2392 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2394 _
\b3_
\b._
\b3_
\b2 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2396 In the process of ensuring and creating more consistency, many variables have
2397 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2398 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 87) for a complete list.
2400 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2402 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2404 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2405 tion 7.2 , page 83) must be specified using regular expressions (regexp) in
2406 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2407 and GNU awk). For your convenience, we have included below a brief description
2410 The search is case sensitive if the pattern contains at least one upper case
2411 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2412 for a regular expression in an initialization command: ``\\''.
2414 A regular expression is a pattern that describes a set of strings. Regular
2415 expressions are constructed analogously to arithmetic expressions, by using
2416 various operators to combine smaller expressions.
2418 Note that the regular expression can be enclosed/delimited by either ' or '
2419 which is useful if the regular expression includes a white-space character.
2421 The Mutt Next Generation E-Mail Client 49
2423 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-
2424 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2425 ace it with \ (backslash).
2427 The fundamental building blocks are the regular expressions that match a single
2428 character. Most characters, including all letters and digits, are regular
2429 expressions that match themselves. Any metacharacter with special meaning may
2430 be quoted by preceding it with a backslash.
2432 The period ``.'' matches any single character. The caret ``^'' and the dollar
2433 sign ``$'' are metacharacters that respectively match the empty string at the
2434 beginning and end of a line.
2436 A list of characters enclosed by ``['' and ``]'' matches any single character
2437 in that list; if the first character of the list is a caret ``^'' then it
2438 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2439 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2440 specified by giving the first and last characters, separated by a hyphen ``-''.
2441 Most metacharacters lose their special meaning inside lists. To include a lit-
2442 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2443 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2446 Certain named classes of characters are predefined. Character classes consist
2447 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2448 defined by the POSIX standard:
2451 Alphanumeric characters.
2454 Alphabetic characters.
2457 Space or tab characters.
2466 Characters that are both printable and visible. (A space is print-
2467 able, but not visible, while an ``a'' is both.)
2470 Lower-case alphabetic characters.
2473 Printable characters (characters that are not control characters.)
2476 Punctuation characters (characters that are not letter, digits,
2478 The Mutt Next Generation E-Mail Client 50
2480 control characters, or space characters).
2483 Space characters (such as space, tab and formfeed, to name a few).
2486 Upper-case alphabetic characters.
2489 Characters that are hexadecimal digits.
2491 A character class is only valid in a regular expression inside the brackets of
2492 a character list. Note that the brackets in these class names are part of the
2493 symbolic names, and must be included in addition to the brackets delimiting the
2494 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].
2496 Two additional special sequences can appear in character lists. These apply to
2497 non-ASCII character sets, which can have single symbols (called collating ele-
2498 ments) that are represented with more than one character, as well as several
2499 characters that are equivalent for collating or sorting purposes:
2502 A collating symbol is a multi-character collating element enclosed
2503 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2504 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2505 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2508 An equivalence class is a locale-specific name for a list of char-
2509 acters that are equivalent. The name is enclosed in ``[='' and
2510 ``=]''. For example, the name ``e'' might be used to represent all
2511 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2512 matches any of ``'', ``'' and ``e''.
2514 A regular expression matching a single character may be followed by one of sev-
2515 eral repetition operators:
2518 The preceding item is optional and matched at most once.
2521 The preceding item will be matched zero or more times.
2524 The preceding item will be matched one or more times.
2527 The preceding item is matched exactly _
\bn times.
2530 The preceding item is matched _
\bn or more times.
2533 The preceding item is matched at most _
\bm times.
2535 The Mutt Next Generation E-Mail Client 51
2538 The preceding item is matched at least _
\bn times, but no more than _
\bm
2541 Two regular expressions may be concatenated; the resulting regular expression
2542 matches any string formed by concatenating two substrings that respectively
2543 match the concatenated subexpressions.
2545 Two regular expressions may be joined by the infix operator ``|''; the result-
2546 ing regular expression matches any string matching either subexpression.
2548 Repetition takes precedence over concatenation, which in turn takes precedence
2549 over alternation. A whole subexpression may be enclosed in parentheses to
2550 override these precedence rules.
2552 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2553 may also be used in regular expressions:
2556 Matches the empty string at either the beginning or the end of a
2560 Matches the empty string within a word.
2563 Matches the empty string at the beginning of a word.
2566 Matches the empty string at the end of a word.
2569 Matches any word-constituent character (letter, digit, or under-
2573 Matches any character that is not word-constituent.
2576 Matches the empty string at the beginning of a buffer (string).
2579 Matches the empty string at the end of a buffer.
2581 Please note however that these operators are not defined by POSIX, so they may
2582 or may not be available in stock libraries on various systems.
2584 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2586 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2587 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2588 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2590 The Mutt Next Generation E-Mail Client 52
2592 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2593 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83) in the Reference chapter.
2595 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2596 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2599 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2601 It is possible to combine several sub-patterns to a more complex pattern. The
2602 most simple possibility is to logically AND several patterns by stringing them
2607 The pattern above matches all messages that contain ``SPAM'' in the subject and
2610 To logical OR patterns, simply use the | operator. This one especially useful
2611 when using local groups:
2613 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2614 (~b mutt-ng|~s Mutt-ng)
2617 The first pattern matches all messages that were sent by one of the mutt-ng
2618 maintainers, while the seconds pattern matches all messages that contain
2619 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2620 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2621 ences: header, i.e. messages that are not an (indirect) reply to one of my
2622 messages. A pattern can be logicall negated using the ! operator.
2624 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2626 When using dates in patterns, the dates must be specified in a special format,
2627 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2628 rent month or year. When using date ranges, and you specify only the minimum or
2629 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2630 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2632 It is also possible to use so-called ``error margins'' when specifying date
2633 ranges. You simply specify a date, and then the error margin. This margin
2634 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2635 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2636 months, w for weeks and d for days. If you use the special * sign, it means
2637 that the error margin goes to both ``directions'' in time.
2642 The Mutt Next Generation E-Mail Client 53
2646 The first pattern matches all dates between January 1st, 2005 and January 1st
2647 2006. The second pattern matches all dates between October 18th, 2004 and
2648 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2649 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2651 Relative dates are also very important, as they make it possible to specify
2652 date ranges between a fixed number of units and the current date. How this
2653 works can be seen in the following example:
2655 ~d >2w # messages older than two weeks
2656 ~d <3d # messages newer than 3 days
2657 ~d =1m # messages that are exactly one month old
2659 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2661 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2663 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2664 In short, they describe what items to print out how in menus and status mes-
2667 Basically, they work as this: for different menus and bars, there's a variable
2668 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2670 For example, when running mutt-ng on different machines or different versions
2671 for testing purposes, it may be interesting to have the following information
2672 always printed on screen when one is in the index:
2674 +
\bo the current hostname
2676 +
\bo the current mutt-ng version number
2678 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-
2679 _
\bm_
\ba_
\bt (section 7.4.321 , page 165) variable. For the hostname and version
2680 string, there's an expando for $status_format: %h expands to the hostname and
2681 %v to the version string. When just configuring:
2683 set status_format = "%v on %h: ..."
2685 mutt-ng will replace the sequence %v with the version string and %h with the
2686 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2687 mailhost, you'll see the following when you're in the index:
2689 Mutt-ng 1.5.9i on mailhost: ...
2691 The Mutt Next Generation E-Mail Client 54
2693 In the index, there're more useful information one could want to see:
2695 +
\bo which mailbox is open
2697 +
\bo how man new, flagged or postponed messages
2701 To include the mailbox' name is as easy as:
2703 set status_format = "%v on %h: %B: ...
2705 When the currently opened mailbox is Inbox, this will be expanded to:
2707 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2709 For the number of certain types of messages, one more feature of the format
2710 strings is extremely useful. If there aren't messages of a certain type, it may
2711 not be desired to print just that there aren't any but instead only print some-
2712 thing if there are any.
2714 _
\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
2716 To only print the number of messages if there are new messages in the current
2717 mailbox, further extend $status_format to:
2719 set status_format = "%v on %h: %B %?n?%n new? ...
2721 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
2722 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2723 ated if the value of the expando is different from zero. The basic syntax is:
2725 %?<item>?<string if nonzero>?
2727 which tells mutt-ng to only look at <string if nonzero> if the value of the
2728 %<item%gt; expando is different from zero. In our example, we used n as the
2729 expando to check for and %n new as the optional nonzero string.
2731 But this is not all: this feature only offers one alternative: ``print some-
2732 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2733 complete version: ``if zero, print something and else print something else.''
2734 This is achieved by the following syntax for those expandos which may be
2737 The Mutt Next Generation E-Mail Client 55
2739 %?<item>?<string if nonzero>&<string if zero>?
2741 Using this we can make mutt-ng to do the following:
2743 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2746 +
\bo and make it print ``no new messages'' if there aren't any
2748 The corresponding configuration is:
2750 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2752 This doubles the use of the ``new messages'' string because it'll get always
2753 printed. Thus, it can be shortened to:
2755 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2757 As you might see from this rather simple example, one can create very complex
2758 but fancy status messages. Please see the reference chapter for expandos and
2759 those which may be printed nonzero.
2761 _
\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
2763 Besides the information given so far, there're even more features of format
2766 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2767 characters in the expansion of <item> to lowercase.
2769 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2770 dots in the expansion of <item> to underscores (_).
2772 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2776 When this occurs, mutt-ng will fill the rest of the line with the
2777 character X. In our example, filling the rest of the line with
2778 dashes is done by setting:
2780 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2783 Since the previous expando stops at the end of line, there must be
2785 The Mutt Next Generation E-Mail Client 56
2787 a way to fill the gap between two items via the %>X expando: it
2788 puts as many characters X in between two items so that the rest of
2789 the line will be right-justified. For example, to not put the ver-
2790 sion string and hostname of our example on the left but on the
2791 right and fill the gap with spaces, one might use (note the space
2794 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2796 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2798 Sometimes it is desirable to perform an operation on a group of messages all at
2799 once rather than one at a time. An example might be to save messages to a
2800 mailing list to a separate folder, or to delete all messages with a given sub-
2801 ject. To tag all messages matching a pattern, use the tag-pattern function,
2802 which is bound to ``shift-T'' by default. Or you can select individual mes-
2803 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2804 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83) for Mutt-ng's pattern matching
2807 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2808 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2809 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2810 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.19 ,
2811 page 93) variable is set, the next operation applies to the tagged messages
2812 automatically, without requiring the ``tag-prefix''.
2814 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 29) or _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 41) commands,
2815 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2816 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2817 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2818 this operator the rest of the macro will be executed as normal.
2820 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2822 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2823 arbitrary commands before performing some operation. For example, you may wish
2824 to tailor your configuration based upon which mailbox you are reading, or to
2825 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
2826 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 48) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 83) along
2827 with a configuration option/command. See
2829 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 29)
2831 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 39)
2833 The Mutt Next Generation E-Mail Client 57
2835 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 40)
2837 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38)
2839 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37)
2841 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 39)
2843 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39)
2845 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2847 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2848 until the end of the current mutt session. As this is generally not desired, a
2849 default hook needs to be added before all other hooks to restore configuration
2850 defaults. Here is an example with send-hook and the my_hdr directive:
2852 send-hook . 'unmy_hdr From:'
2853 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2855 _
\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
2857 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2858 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2859 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 48) is sufficient. But in dealing with
2860 messages a finer grain of control is needed for matching since for different
2861 purposes you want to match different criteria.
2863 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 83) language
2864 for matching messages in hook commands. This works in exactly the same way as
2865 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
2866 to those operators which match information mutt extracts from the header of the
2867 message (i.e. from, to, cc, date, subject, etc.).
2869 For example, if you wanted to set your return address based upon sending mail
2870 to a specific address, you could do something like:
2872 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2874 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2876 However, it is not required that you write the pattern to match using the full
2877 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
2878 other hooks, in which case Mutt-ng will translate your pattern into the full
2879 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2880 7.4.49 , page 100) variable. The pattern is translated at the time the hook
2881 is declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.49 , page 100) that is
2882 in effect at that time will be used.
2884 The Mutt Next Generation E-Mail Client 58
2886 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2888 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2889 which looks very similar to the ones you probably know from GUI mail clients.
2890 The sidebar lists all specified mailboxes, shows the number in each and high-
2891 lights the ones with new email Use the following configuration commands:
2893 set sidebar_visible="yes"
2894 set sidebar_width=25
2896 If you want to specify the mailboxes you can do so with:
2904 You can also specify the colors for mailboxes with new mails by using:
2906 color sidebar_new red black
2907 color sidebar white black
2909 The available functions are:
2911 sidebar-scroll-up Scrolls the mailbox list up 1 page
2912 sidebar-scroll-down Scrolls the mailbox list down 1 page
2913 sidebar-next Highlights the next mailbox
2914 sidebar-next-new Highlights the next mailbox with new mail
2915 sidebar-previous Highlights the previous mailbox
2916 sidebar-open Opens the currently highlighted mailbox
2918 Reasonable key bindings look e.g. like this:
2920 bind index \Cp sidebar-prev
2921 bind index \Cn sidebar-next
2922 bind index \Cb sidebar-open
2923 bind pager \Cp sidebar-prev
2924 bind pager \Cn sidebar-next
2925 bind pager \Cb sidebar-open
2927 macro index B ':toggle sidebar_visible^M'
2928 macro pager B ':toggle sidebar_visible^M'
2930 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2931 off the sidebar simply by pressing 'B'.
2933 The Mutt Next Generation E-Mail Client 59
2935 _
\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
2937 Mutt-ng supports connecting to external directory databases such as LDAP,
2938 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2939 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.234 , page 145) vari-
2940 able, you specify the wrapper command to use. For example:
2942 set query_command = "mutt_ldap_query.pl '%s'"
2944 The wrapper script should accept the query on the command-line. It should
2945 return a one line message, then each matching response on a single line, each
2946 line containing a tab separated address then name then some other optional
2947 information. On error, or if there are no matching addresses, return a non-
2948 zero exit code and a one line error message.
2950 An example multiple response output:
2952 Searching database ... 20 entries ... 3 matching:
2953 me@cs.hmc.edu Michael Elkins mutt dude
2954 blong@fiction.net Brandon Long mutt and more
2955 roessler@guug.de Thomas Roessler mutt pgp
2957 There are two mechanisms for accessing the query function of mutt. One is to
2958 do a query from the index menu using the query function (default: Q). This
2959 will prompt for a query, then bring up the query menu which will list the
2960 matching responses. From the query menu, you can select addresses to create
2961 aliases, or to mail. You can tag multiple addresses to mail, start a new
2962 query, or have a new query appended to the current responses.
2964 The other mechanism for accessing the query function is for address completion,
2965 similar to the alias completion. In any prompt for address entry, you can use
2966 the complete-query function (default: ^T) to run a query based on the current
2967 address you have typed. Like aliases, mutt will look for what you have typed
2968 back to the last space or comma. If there is a single response for that query,
2969 mutt will expand the address in place. If there are multiple responses, mutt
2970 will activate the query menu. At the query menu, you can select one or more
2971 addresses to be added to the prompt.
2973 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2975 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2976 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2977 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2978 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.132 , page 121)
2981 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2982 stored in a single file. Each message has a line of the form:
2984 The Mutt Next Generation E-Mail Client 60
2986 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2988 to denote the start of a new message (this is often referred to as the
2991 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2992 lines containing ``^A^A^A^A'' (four control-A's).
2994 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2995 and each message is stored in a separate file. The filename indicates the mes-
2996 sage number (however, this is may not correspond to the message number Mutt-ng
2997 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2998 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2999 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
3002 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
3003 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
3004 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
3005 way they are unique, even when two programs are writing the mailbox over NFS,
3006 which means that no file locking is needed.
3008 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
3010 There are a number of built in shortcuts which refer to specific mailboxes.
3011 These shortcuts can be used anywhere you are prompted for a file or mailbox
3014 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.310 , page 163) (incoming)
3017 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.131 , page 121) file
3019 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.243 , page 147) file
3021 +
\bo ^ -- refers to the current mailbox
3023 +
\bo - or !! -- refers to the file you've last visited
3025 +
\bo ~ -- refers to your home directory
3027 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 104) directory
3029 +
\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 38) as
3030 determined by the address of the alias
3032 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
3034 Mutt-ng has a few configuration options that make dealing with large amounts of
3036 The Mutt Next Generation E-Mail Client 61
3038 mail easier. The first thing you must do is to let Mutt know what addresses
3039 you consider to be mailing lists (technically this does not have to be a mail-
3040 ing list, but that is what it is most often used for), and what lists you are
3041 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
3042 (section 3.13 , page 36) commands in your muttrc.
3044 Now that Mutt-ng knows what your mailing lists are, it can do several things,
3045 the first of which is the ability to show the name of a list through which you
3046 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
3047 This is useful to distinguish between personal and list mail in the same mail-
3048 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115) variable, the escape
3049 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
3050 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
3051 returns the name of the author).
3053 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
3054 quite large. Most people do not bother to remove the author of the message they
3055 are reply to from the list, resulting in two or more copies being sent to that
3056 person. The ``list-reply'' function, which by default is bound to ``L'' in the
3057 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
3058 mailing list addresses instead of all recipients (except as specified by Mail-
3059 Followup-To, see below).
3061 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
3062 a list of recipients which includes one or several subscribed mailing lists,
3063 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.72 , page 105) option is set, mutt will
3064 generate a Mail-Followup-To header which contains all the recipients to whom
3065 you send this message, but not your address. This indicates that group-replies
3066 or list-replies (also known as ``followups'') to this message should only be
3067 sent to the original recipients of the message, and not separately to you -
3068 you'll receive your copy through one of the mailing lists you are subscribed
3071 Conversely, when group-replying or list-replying to a message which has a Mail-
3072 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
3073 (section 7.4.94 , page 110) configuration variable is set. Using list-reply
3074 will in this case also make sure that the reply goes to the mailing list, even
3075 if it's not specified in the list of recipients in the Mail-Followup-To.
3077 Note that, when header editing is enabled, you can create a Mail-Followup-To
3078 header manually. Mutt-ng will only auto-generate this header if it doesn't
3079 exist when you send the message.
3081 The other method some mailing list admins use is to generate a ``Reply-To''
3082 field which points back to the mailing list address rather than the author of
3083 the message. This can create problems when trying to reply directly to the
3084 author in private, since most mail clients will automatically reply to the
3085 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
3086 7.4.246 , page 148) variable to help decide which address to use. If set to
3087 _
\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
3088 use the address given in the ``Reply-To'' field, or reply directly to the
3089 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
3090 will be used when present.
3092 The Mutt Next Generation E-Mail Client 62
3094 The ``X-Label:'' header field can be used to further identify mailing lists or
3095 list subject matter (or just to annotate messages individually). The
3096 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115) variable's ``%y'' and ``%Y''
3097 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
3098 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
3099 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
3100 can easily be inserted by procmail and other mail filtering agents.
3102 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.304 , page 161) the mail-
3103 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
3104 which all relate to the same subject. This is usually organized into a tree-
3105 like structure where a message and all of its replies are represented graphi-
3106 cally. If you've ever used a threaded news client, this is the same concept.
3107 It makes dealing with large volume mailing lists easier because you can easily
3108 delete uninteresting threads and quickly find topics of value.
3110 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3112 Mutt-ng has the ability to dynamically restructure threads that are broken
3113 either by misconfigured software or bad behavior from some correspondents. This
3114 allows to clean your mailboxes formats) from these annoyances which make it
3115 hard to follow a discussion.
3117 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3119 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
3120 ences:" headers when replying to a message. This results in broken discussions
3121 because Mutt-ng has not enough information to guess the correct threading. You
3122 can fix this by tagging the reply, then moving to the parent message and using
3123 the ``link-threads'' function (bound to & by default). The reply will then be
3124 connected to this "parent" message.
3126 You can also connect multiple children at once, tagging them and using the tag-
3127 prefix command (';') or the auto_tag option.
3129 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3131 On mailing lists, some people are in the bad habit of starting a new discussion
3132 by hitting "reply" to any message from the list and changing the subject to a
3133 totally unrelated one. You can fix such threads by using the ``break-thread''
3134 function (bound by default to #), which will turn the subthread starting from
3135 the current message into a whole different thread.
3137 _
\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
3139 RFC1894 defines a set of MIME content types for relaying information about the
3140 status of electronic mail messages. These can be thought of as ``return
3143 Users can make use of it in one of the following two ways:
3145 The Mutt Next Generation E-Mail Client 63
3147 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
3148 the mail client can make requests as to what type of status messages
3151 +
\bo The SMTP support via libESMTP supports it, too.
3153 To support this, there are two variables:
3155 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.56 , page 101) is used to request receipts for
3156 different results (such as failed message, message delivered, etc.).
3158 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.57 , page 102) requests how much of your message
3159 should be returned with the receipt (headers or full message).
3161 Please see the reference chapter for possible values.
3163 _
\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)
3165 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3166 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
3167 remote POP3 server and fetch mail for local browsing.
3169 You can access the remote POP3 mailbox by selecting the folder
3172 You can select an alternative port by specifying it with the server, i.e.:
3173 pop://popserver:port/.
3175 You can also specify different username for each folder, i.e.: pop://user-
3176 name@popserver[:port]/.
3178 Polling for new mail is more expensive over POP3 than locally. For this reason
3179 the frequency at which Mutt-ng will check for mail remotely can be controlled
3180 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.221 , page 142) variable, which defaults
3181 to every 60 seconds.
3183 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3184 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3185 rally requires that the server supports SSL encrypted connections. To access a
3186 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3187 name@]popserver[:port]/.
3189 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3190 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.219 , page 142), fetch all your
3191 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.310 , page 163).
3192 After this point, Mutt-ng runs exactly as if the mail had always been local.
3194 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3195 sider using a specialized program, such as fetchmail
3197 The Mutt Next Generation E-Mail Client 64
3199 _
\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)
3201 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3202 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
3205 You can access the remote inbox by selecting the folder
3206 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3207 INBOX is the special name for your spool mailbox on the IMAP server. If you
3208 want to access another mail folder at the IMAP server, you should use
3209 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3212 You can select an alternative port by specifying it with the server, i.e.:
3213 imap://imapserver:port/INBOX.
3215 You can also specify different username for each folder, i.e.: imap://user-
3216 name@imapserver[:port]/INBOX.
3218 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3219 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3220 rally requires that the server supports SSL encrypted connections. To access a
3221 folder with IMAP/SSL, you should use imaps://[user-
3222 name@]imapserver[:port]/path/to/folder as your folder path.
3224 Pine-compatible notation is also supported, i.e. {[user-
3225 name@]imapserver[:port][/ssl]}path/to/folder
3227 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3228 correctly notice which separator is being used by the server and convert paths
3231 When browsing folders on an IMAP server, you can toggle whether to look at only
3232 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
3233 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.103 , page 113)
3236 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3237 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.105 , page 113) and
3238 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.334 , page 170) variables.
3240 Note that if you are using mbox as the mail store on UW servers prior to
3241 v12.250, the server has been reported to disconnect a client if another client
3242 selects the same folder.
3244 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3246 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3247 mostly the same as the local file browser, with the following differences:
3249 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3250 followed by the symbol "+", indicating that the entry contains both mes-
3251 sages and subfolders. On Cyrus-like servers folders will often contain
3252 both messages and subfolders.
3254 The Mutt Next Generation E-Mail Client 65
3256 +
\bo For the case where an entry can contain both messages and subfolders, the
3257 selection key (bound to enter by default) will choose to descend into the
3258 subfolder view. If you wish to view the messages in that folder, you must
3259 use view-file instead (bound to space by default).
3261 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3262 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3263 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3264 mally these are bound to s and u, respectively).
3266 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3268 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3269 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3270 tion for you poor exchange users out there, but it has yet to be integrated
3271 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3272 which allows you to log in to a public IMAP server without having an account.
3273 To use ANONYMOUS, simply make your username blank or "anonymous".
3275 SASL is a special super-authenticator, which selects among several protocols
3276 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3277 available on your host and the server. Using some of these methods (including
3278 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3279 invisible to those teeming network snoops. It is the best option if you have
3280 it. To use it, you must have the Cyrus SASL library installed on your system
3281 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3283 Mutt-ng will try whichever methods are compiled in and available on the server,
3284 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3286 There are a few variables which control authentication:
3288 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.111 , page 114) - controls the username under
3289 which you request authentication on the IMAP server, for all authentica-
3290 tors. This is overridden by an explicit username in the mailbox path (i.e.
3291 by using a mailbox name of the form {user@host}).
3293 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.106 , page 113) - a password which you may pre-
3294 set, used by all authentication methods where a password is needed.
3296 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.97 , page 111) - a colon-delimited list
3297 of IMAP authentication methods to try, in the order you wish to try them.
3298 If specified, this overrides mutt's default (attempt everything, in the
3299 order listed above).
3301 _
\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)
3303 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3304 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3305 function from the index/pager which is by default bound to i.
3307 The Default newsserver can be obtained from the $NNTPSERVER environment
3309 The Mutt Next Generation E-Mail Client 66
3311 variable. Like other news readers, info about subscribed newsgroups is saved in
3312 a file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.169 , page 130) variable.
3313 Article headers are cached and can be loaded from a file when a newsgroup is
3314 entered instead loading from newsserver; currently, this caching mechanism
3315 still is different from the header caching for maildir/IMAP.
3317 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3319 Especially for Usenet, people often ask for advanced filtering and scoring
3320 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3321 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
3324 What has not been discusses in detail is mutt-ng's built-in realname filter.
3325 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3326 there are frequent request for such functionality. The solutions offered often
3327 are complicated regular expressions.
3329 In mutt-ng this is as easy as
3333 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3334 fied a valid realname and a valid email address. Using
3338 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3339 ria which are very strict:
3341 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3342 editor.org/in-notes/rfc2822.txt>
3344 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3345 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3346 ``J. User'' and ``J. A. User'' aren't.
3348 +
\bo it's assumed that users are interested in reading their own mail and mail
3349 from people who they have defined an alias for so that those 2 groups of
3350 messages are excluded from the strict rules.
3352 _
\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)
3354 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3356 The Mutt Next Generation E-Mail Client 67
3358 functionality. When configure was called with --with-libesmtp or the output
3359 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3360 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3361 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 62) section) as well as handling the 8BIT-
3362 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.341 , page 172).
3364 To enable sending mail directly via SMTP without an MTA such as Postfix or
3365 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.299 , page 160)
3366 variable pointing to your SMTP server.
3368 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.303 ,
3369 page 161) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.300 , page 160) variables.
3371 Transport Encryption via the StartTLS command is also available. For this to
3372 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3373 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.302 , page 161) variable must be either set to
3374 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3375 supports it: for the second case, the connection will fail if it doesn't while
3376 switching back to unencrypted communication for the first one.
3378 Some mail providers require user's to set a particular envelope sender, i.e.
3379 they allow for only one value which may not be what the user wants to send as
3380 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.298 ,
3381 page 160) may be used to set the envelope different from the From: header.
3383 _
\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)
3385 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3386 find managing all the authentication settings inconvenient and error-prone.
3387 The account-hook command may help. This hook works like folder-hook but is
3388 invoked whenever you access a remote mailbox (including inside the folder
3389 browser), not just when you open the mailbox.
3393 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3394 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3395 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3397 _
\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)
3399 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
3400 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
3401 start a WWW browser on one of them. This functionality is provided by the
3402 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3403 trib/ and the configuration commands:
3405 macro index \cb |urlview\n
3406 macro pager \cb |urlview\n
3408 The Mutt Next Generation E-Mail Client 68
3410 _
\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)
3412 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3413 _
\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
3414 an arbitrary format, provided that the user has a script to convert from/to
3415 this format to one of the accepted.
3417 The most common use is to open compressed archived folders e.g. with gzip.
3419 In addition, the user can provide a script that gets a folder in an accepted
3420 format and appends its context to the folder in the user-defined format, which
3421 may be faster than converting the entire folder to the accepted format, append-
3422 ing to it and converting back to the user-defined format.
3424 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3425 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69))
3426 which define commands to uncompress and compress a folder and to append mes-
3427 sages to an existing compressed folder respectively.
3431 open-hook \\.gz$ "gzip -cd %f > %t"
3432 close-hook \\.gz$ "gzip -c %t > %f"
3433 append-hook \\.gz$ "gzip -c %t >> %f"
3435 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-
3436 tion 4.19.3 , page 69), the folder will be open and closed again each time you
3437 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) (or give
3438 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3439 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) though you'll be able to append to the folder.
3441 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3442 accepted formats. In particular, if the file is empty, mutt supposes it is not
3443 compressed. This is important because it allows the use of programs that do not
3444 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3445 prising if your compressing script produces empty files. In this situation,
3446 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.253 , page 149), so that the compressed file
3447 will be removed if you delete all of the messages.
3449 _
\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
3451 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3453 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3454 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3456 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3457 parameters: %f, which is replaced with the (compressed) folder name, and %t
3458 which is replaced with the name of the temporary folder to which to write.
3460 %f and %t can be repeated any number of times in the command string, and all of
3461 the entries are replaced with the appropriate folder name. In addition, %% is
3463 The Mutt Next Generation E-Mail Client 69
3465 replaced by %, as in printf, and any other %anything is left as is.
3467 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
3468 return non-zero exit status if it fails, so mutt knows something's wrong.
3472 open-hook \\.gz$ "gzip -cd %f > %t"
3474 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3476 _
\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
3478 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3480 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3481 4.19.1 , page 68) command after some changes were made to it.
3483 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3484 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
3485 4.19.1 , page 68) command. Temporary folder in this case is the folder previ-
3486 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68) command.
3488 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
3489 non-zero exit status if it fails, so mutt knows something's wrong.
3493 close-hook \\.gz$ "gzip -c %t > %f"
3495 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3496 file can only be open in the readonly mode.
3498 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) is not called when you exit from the
3499 folder if the folder was not changed.
3501 _
\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
3503 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3505 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3506 is the command that can be used for appending to the folders whose names match
3507 _
\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 68)
3508 command. The temporary folder in this case contains the messages that are
3511 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
3512 non-zero exit status if it fails, so mutt knows something's wrong.
3516 The Mutt Next Generation E-Mail Client 70
3518 append-hook \\.gz$ "gzip -c %t >> %f"
3520 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) is used, the folder is not opened,
3521 which saves time, but this means that we can not find out what the folder type
3522 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.132 , page 121)) type is always
3523 supposed (i.e. this is the format used for the temporary folder).
3525 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 ,
3526 page 69) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3527 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) is only for appending to existing folders.
3529 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3530 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3531 4.19.1 , page 68) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69)respectively) each
3532 time you will add to it.
3534 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3536 The compressed folders support can also be used to handle encrypted folders. If
3537 you want to encrypt a folder with PGP, you may want to use the following hooks:
3539 open-hook \\.pgp$ "pgp -f < %f > %t"
3540 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3542 Please note, that PGP does not support appending to an encrypted folder, so
3543 there is no append-hook defined.
3545 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3546 can be read by your system administrator. So think about the security aspects
3549 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3551 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3552 MUA. Every effort has been made to provide the functionality that the discern-
3553 ing MIME user requires, and the conformance to the standards wherever possible.
3554 When configuring Mutt-ng for MIME, there are two extra types of configuration
3555 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3556 ping of file extensions to IANA MIME types. The other is the mailcap file,
3557 which specifies the external commands to use for handling specific MIME types.
3559 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3561 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3562 (while viewing a message), the attachment menu and the compose menu.
3564 The Mutt Next Generation E-Mail Client 71
3566 _
\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
3568 When you select a message from the index and view it in the pager, Mutt decodes
3569 the message to a text representation. Mutt-ng internally supports a number of
3570 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3571 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3572 variety of PGP MIME types, including PGP/MIME and application/pgp.
3574 Mutt-ng will denote attachments with a couple lines describing them. These
3575 lines are of the form:
3577 [-- Attachment #1: Description --]
3578 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3580 Where the Description is the description or filename given for the attachment,
3581 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3583 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3585 [-- image/gif is unsupported (use 'v' to view this part) --]
3587 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3589 The default binding for view-attachments is `v', which displays the attachment
3590 menu for a message. The attachment menu displays a list of the attachments in
3591 a message. From the attachment menu, you can save, print, pipe, delete, and
3592 view attachments. You can apply these operations to a group of attachments at
3593 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3594 can also reply to the current message from this menu, and only the current
3595 attachment (or the attachments tagged) will be quoted in your reply. You can
3596 view attachments as text, or view them using the mailcap viewer definition.
3598 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3599 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3600 of type message/rfc822.
3602 See the help on the attachment menu for more information.
3604 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3606 The compose menu is the menu you see before you send a message. It allows you
3607 to edit the recipient list, the subject, and other aspects of your message. It
3608 also contains a list of the attachments of your message, including the main
3609 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3610 review, and rename an attachment or a list of tagged attachments. You can also
3611 modifying the attachment information, notably the type, encoding and descrip-
3614 Attachments appear as follows:
3616 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3617 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3619 The Mutt Next Generation E-Mail Client 72
3621 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3622 or canceling) the message. It can be toggled with the toggle-unlink command
3623 (default: u). The next field is the MIME content-type, and can be changed with
3624 the edit-type command (default: ^T). The next field is the encoding for the
3625 attachment, which allows a binary message to be encoded for transmission on
3626 7bit links. It can be changed with the edit-encoding command (default: ^E).
3627 The next field is the size of the attachment, rounded to kilobytes or
3628 megabytes. The next field is the filename, which can be changed with the
3629 rename-file command (default: R). The final field is the description of the
3630 attachment, and can be changed with the edit-description command (default: d).
3632 _
\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
3634 When you add an attachment to your mail message, Mutt-ng searches your personal
3635 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3636 /usr/local/share/mutt/mime.types or /etc/mime.types
3638 The mime.types file consist of lines containing a MIME type and a space sepa-
3639 rated list of extensions. For example:
3641 application/postscript ps eps
3643 audio/x-aiff aif aifc aiff
3645 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3646 tain most of the MIME types you are likely to use.
3648 If Mutt-ng can not determine the mime type by the extension of the file you
3649 attach, it will look at the file. If the file is free of binary information,
3650 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3651 the file contains binary information, then Mutt-ng will mark it as applica-
3652 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3653 attachment by using the edit-type command from the compose menu (default: ^T).
3654 The MIME type is actually a major mime type followed by the sub-type, separated
3655 by a '/'. 6 major types: application, text, image, video, audio, and model have
3656 been approved after various internet discussions. Mutt-ng recognises all of
3657 these if the appropriate entry is found in the mime.types file. It also recog-
3658 nises other major mime types, such as the chemical type that is widely used in
3659 the molecular modelling community to pass molecular data in various forms to
3660 various molecular viewers. Non-recognised mime types should only be used if the
3661 recipient of the message is likely to be expecting such attachments.
3663 _
\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
3665 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3666 format specified in Appendix A of RFC 1524. This file format is commonly
3667 referred to as the mailcap format. Many MIME compliant programs utilize the
3668 mailcap format, allowing you to specify handling for all MIME types in one
3669 place for all programs. Programs known to use this format include Netscape,
3671 The Mutt Next Generation E-Mail Client 73
3673 XMosaic, lynx and metamail.
3675 In order to handle various MIME types that Mutt-ng can not handle internally,
3676 Mutt-ng parses a series of external configuration files to find an external
3677 handler. The default search string for these files is a colon delimited list
3680 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3682 where $HOME is your home directory.
3684 In particular, the metamail distribution will install a mailcap file, usually
3685 as /usr/local/etc/mailcap, which contains some baseline entries.
3687 _
\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
3689 A mailcap file consists of a series of lines which are comments, blank, or def-
3692 A comment line consists of a # character followed by anything you want.
3694 A blank line is blank.
3696 A definition line consists of a content type, a view command, and any number of
3697 optional fields. Each field of a definition line is divided by a semicolon ';'
3700 The content type is specified in the MIME standard type/subtype method. For
3701 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3702 mat includes two formats for wildcards, one using the special '*' subtype, the
3703 other is the implicit wild, where you only include the major type. For exam-
3704 ple, image/*, or video, will match all image types and video types, respec-
3707 The view command is a Unix command for viewing the type specified. There are
3708 two different types of commands supported. The default is to send the body of
3709 the MIME message to the command on stdin. You can change this behavior by using
3710 %s as a parameter to your view command. This will cause Mutt-ng to save the
3711 body of the MIME message to a temporary file, and then call the view command
3712 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3713 will turn over the terminal to the view program until the program quits, at
3714 which time Mutt will remove the temporary file if it exists.
3716 So, in the simplest form, you can send a text/plain message to the external
3717 pager more on stdin:
3721 Or, you could send the message as a file:
3725 The Mutt Next Generation E-Mail Client 74
3727 Perhaps you would like to use lynx to interactively view a text/html message:
3731 In this case, lynx does not support viewing a file from stdin, so you must use
3732 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
3733 _
\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
3734 _
\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
3735 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3737 On the other hand, maybe you don't want to use lynx interactively, you just
3738 want to have it convert the text/html to text/plain, then you can use:
3740 text/html; lynx -dump %s | more
3742 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3743 text formats, then you would use the following:
3748 This is the simplest form of a mailcap file.
3750 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3752 The interpretation of shell meta-characters embedded in MIME parameters can
3753 lead to security problems in general. Mutt-ng tries to quote parameters in
3754 expansion of %s syntaxes properly, and avoids risky characters by substituting
3755 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.123 , page 119) variable.
3757 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3758 there are other applications parsing mailcap, maybe taking less care of it.
3759 Therefore you should pay attention to the following rules:
3761 _
\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
3762 double quotes. Mutt-ng does this for you, the right way, as should any other
3763 program which interprets mailcap. Don't put them into backtick expansions. Be
3764 highly careful with eval statements, and avoid them if possible at all. Trying
3765 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3766 tive to correct quoting in the first place.
3768 If you have to use the %-expandos' values in context where you need quoting or
3769 backtick expansions, put that value into a shell variable and reference the
3770 shell variable where necessary, as in the following example (using $charset
3771 inside the backtick expansion is safe, since it is not itself subject to any
3774 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3775 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3777 The Mutt Next Generation E-Mail Client 75
3779 _
\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
3781 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3783 In addition to the required content-type and view command fields, you can add
3784 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3785 nizes the following optional fields:
3788 This flag tells Mutt-ng that the command passes possibly large
3789 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3790 (either the internal pager or the external pager defined by the
3791 pager variable) on the output of the view command. Without this
3792 flag, Mutt-ng assumes that the command is interactive. One could
3793 use this to replace the pipe to more in the lynx -dump example in
3796 text/html; lynx -dump %s ; copiousoutput
3798 This will cause lynx to format the text/html output as text/plain
3799 and Mutt-ng will use your standard pager to display the results.
3802 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3803 tion 5.4 , page 78), in order to decide whether it should honor
3804 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.347 , page 173) variable
3805 or not. When an attachment is viewed using an interactive program,
3806 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3807 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.347 , page 173) and the exit
3808 status of the program to decide if it will ask you to press a key
3809 after the external program has exited. In all other situations it
3810 will not prompt you for a key.
3813 This flag specifies the command to use to create a new attachment
3814 of a specific MIME type. Mutt-ng supports this from the compose
3817 composetyped=<command>
3818 This flag specifies the command to use to create a new attachment
3819 of a specific MIME type. This command differs from the compose
3820 command in that mutt will expect standard MIME headers on the data.
3821 This can be used to specify parameters, filename, description, etc.
3822 for a new attachment. Mutt-ng supports this from the compose
3826 This flag specifies the command to use to print a specific MIME
3827 type. Mutt-ng supports this from the attachment and compose menus.
3830 This flag specifies the command to use to edit a specific MIME
3831 type. Mutt-ng supports this from the compose menu, and also uses
3833 The Mutt Next Generation E-Mail Client 76
3835 it to compose new attachments. Mutt-ng will default to the defined
3836 editor for text attachments.
3838 nametemplate=<template>
3839 This field specifies the format for the file denoted by %s in the
3840 command fields. Certain programs will require a certain file
3841 extension, for instance, to correctly view a file. For instance,
3842 lynx will only interpret a file as text/html if the file ends in
3843 .html. So, you would specify lynx as a text/html viewer with a
3844 line in the mailcap file like:
3846 text/html; lynx %s; nametemplate=%s.html
3849 This field specifies a command to run to test whether this mailcap
3850 entry should be used. The command is defined with the command
3851 expansion rules defined in the next section. If the command
3852 returns 0, then the test passed, and Mutt-ng uses this entry. If
3853 the command returns non-zero, then the test failed, and Mutt-ng
3854 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
3855 _
\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:
3857 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3860 In this example, Mutt-ng will run the program RunningX which will
3861 return 0 if the X Window manager is running, and non-zero if it
3862 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3863 display the text/html object. If RunningX doesn't return 0, then
3864 Mutt-ng will go on to the next entry and use lynx to display the
3867 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3869 When searching for an entry in the mailcap file, Mutt-ng will search for the
3870 most useful entry for its purpose. For instance, if you are attempting to
3871 print an image/gif, and you have the following entries in your mailcap file,
3872 Mutt-ng will search for an entry with the print command:
3875 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3878 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3881 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) to denote
3882 two commands for viewing an attachment, one to be viewed automatically, the
3883 other to be viewed interactively from the attachment menu. In addition, you
3884 can then use the test feature to determine which viewer to use interactively
3885 depending on your environment.
3887 The Mutt Next Generation E-Mail Client 77
3889 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3890 text/html; lynx %s; nametemplate=%s.html
3891 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3893 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78), Mutt-ng will choose the third entry
3894 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3895 program RunningX to determine if it should use the first entry. If the program
3896 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3898 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3900 The various commands defined in the mailcap files are passed to the /bin/sh
3901 shell using the system() function. Before the command is passed to /bin/sh -c,
3902 it is parsed to expand various special parameters with information from Mutt-
3903 ng. The keywords Mutt-ng expands are:
3906 As seen in the basic mailcap section, this variable is expanded to
3907 a filename specified by the calling program. This file contains
3908 the body of the message to view/print/edit or where the composing
3909 program should place the results of composition. In addition, the
3910 use of this keyword causes Mutt-ng to not pass the body of the mes-
3911 sage to the view/print/edit program on stdin.
3914 Mutt-ng will expand %t to the text representation of the content
3915 type of the message in the same form as the first parameter of the
3916 mailcap definition line, ie text/html or image/gif.
3919 Mutt-ng will expand this to the value of the specified parameter
3920 from the Content-Type: line of the mail message. For instance, if
3921 Your mail message contains:
3923 Content-Type: text/plain; charset=iso-8859-1
3925 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3926 metamail mailcap file uses this feature to test the charset to
3927 spawn an xterm using the right charset to view the message.
3930 This will be replaced by a %
3932 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3933 1524. The main purpose of these parameters is for multipart messages, which is
3934 handled internally by Mutt-ng.
3936 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3938 This mailcap file is fairly simple and standard:
3940 The Mutt Next Generation E-Mail Client 78
3942 # I'm always running X :)
3943 video/*; xanim %s > /dev/null
3944 image/*; xv %s > /dev/null
3946 # I'm always running netscape (if my computer had more memory, maybe)
3947 text/html; netscape -remote 'openURL(%s)'
3949 This mailcap file shows quite a number of examples:
3951 # Use xanim to view all videos Xanim produces a header on startup,
3952 # send that to /dev/null so I don't see it
3953 video/*; xanim %s > /dev/null
3955 # Send html to a running netscape by remote
3956 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3958 # If I'm not running netscape but I am running X, start netscape on the
3960 text/html; netscape %s; test=RunningX
3962 # Else use lynx to view it as text
3965 # This version would convert the text/html to text/plain
3966 text/html; lynx -dump %s; copiousoutput
3968 # I use enscript to print text in two columns to a page
3969 text/*; more %s; print=enscript -2Gr %s
3971 # Netscape adds a flag to tell itself to view jpegs internally
3972 image/jpeg;xv %s; x-mozilla-flags=internal
3974 # Use xv to view images if I'm running X
3975 # In addition, this uses the \ to extend the line and set my editor
3977 image/*;xv %s; test=RunningX; \
3980 # Convert images to text using the netpbm tools
3981 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3982 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3984 # Send excel spreadsheets to my NT box
3985 application/ms-excel; open.pl %s
3987 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3989 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3990 viewer defined in the mailcap file, Mutt-ng has support for automatically
3992 The Mutt Next Generation E-Mail Client 79
3994 viewing MIME attachments while in the pager.
3996 To work, you must define a viewer in the mailcap file which uses the copi-
3997 ousoutput option to denote that it is non-interactive. Usually, you also use
3998 the entry to convert the attachment to a text representation which you can view
4001 You then use the auto_view muttrc command to list the content-types that you
4002 wish to view automatically.
4004 For instance, if you set auto_view to:
4006 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
4008 Mutt-ng could use the following mailcap entries to automatically view attach-
4009 ments of these types.
4011 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
4012 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
4013 application/x-gunzip; gzcat; copiousoutput
4014 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
4015 application/postscript; ps2ascii %s; copiousoutput
4017 ``unauto_view'' can be used to remove previous entries from the autoview list.
4018 This can be used with message-hook to autoview messages based on size, etc.
4019 ``unauto_view *'' will remove all previous entries.
4021 _
\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
4023 Mutt-ng has some heuristics for determining which attachment of a multi-
4024 part/alternative type to display. First, mutt will check the alternative_order
4025 list to determine if one of the available types is preferred. The alterna-
4026 tive_order list consists of a number of MIME types in order, including support
4027 for implicit and explicit wildcards, for example:
4029 alternative_order text/enriched text/plain text application/postscript image/*
4031 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
4032 5.4 , page 78), and use that. Failing that, Mutt-ng will look for any text
4033 type. As a last attempt, mutt will look for any type it knows how to handle.
4035 To remove a MIME type from the alternative_order list, use the unalterna-
4038 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
4040 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
4042 The Mutt Next Generation E-Mail Client 80
4044 treated according to their mailcap entry. This option is designed to deal with
4045 binary types such as application/octet-stream. When an attachment's mime-type
4046 is listed in mime_lookup, then the extension of the filename will be compared
4047 to the list of extensions in the mime.types file. The mime-type associated
4048 with this extension will then be used to process the attachment according to
4049 the rules in the mailcap file and according to any other configuration options
4050 (such as auto_view) specified. Common usage would be:
4052 mime_lookup application/octet-stream application/X-Lotus-Manuscript
4054 In addition, the unmime_lookup command may be used to disable this feature for
4055 any particular mime-type if it had been set, for example, in a global muttrc.
4057 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4059 First of all, mutt-ng contains no security holes included by intention but may
4060 contain unknown security holes. As a consequence, please run mutt-ng only with
4061 as few permissions as possible.
4063 Please do not run mutt-ng as the super user.
4065 When configuring mutt-ng, there're some points to note about secure setups.
4067 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
4068 mail user agents (in their default configuration) just by changing mutt-ng's
4069 configuration files: it then can execute arbitrary programs and scripts
4070 attached to messages, send out private data on its own, etc. Although this is
4071 not believed to the common type of setup, please read this chapter carefully.
4073 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
4075 Although mutt-ng can be told the various passwords for accounts, please never
4076 store passwords in configuration files. Besides the fact that the system's
4077 operator can always read them, you could forget to replace the actual password
4078 with asterisks when reporting a bug or asking for help via, for example, a
4079 mailing list so that your mail including your password could be archived by
4080 internet search engines, etc. Please never store passwords on disk.
4082 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
4084 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
4085 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.339 , page 171) variable can be used to
4086 change the default permissions of these files. Please only change it if you
4087 really know what you are doing. Also, a different location for these files may
4088 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.335 , page 170)
4091 The Mutt Next Generation E-Mail Client 81
4093 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
4095 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4097 In the default configuration, mutt-ng will leak some information to the outside
4098 world when sending messages: the generation of Message-ID: headers includes a
4099 step counter which is increased (and rotated) with every message sent. If you'd
4100 like to hide this information probably telling others how many mail you sent in
4101 which time, you at least need to remove the %P expando from the default setting
4102 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.149 , page 124) variable. Please make sure
4103 that you really know how local parts of these Message-ID: headers are composed.
4105 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
4107 As mutt-ng be can be set up to be the mail client to handle mailto: style links
4108 in websites, there're security considerations, too. To keep the old behavior by
4109 default, mutt-ng will be strict in interpreting them which means that arbitrary
4110 header fields can be embedded in these links which could override existing
4111 header fields or attach arbitrary files. This may be problematic if the
4112 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
4113 doesn't want to see header fields while editing the message.
4115 For example, following a link like
4117 mailto:joe@host?Attach=~/.gnupg/secring.gpg
4119 will send out the user's private gnupg keyring to joe@host if the user doesn't
4120 follow the information on screen carefully enough.
4122 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.323 , page 168) variable, mutt-
4125 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
4126 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
4128 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable by force
4129 to let the user see all the headers (because they still may leak informa-
4132 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4134 Mutt-ng in many places has to rely on external applications or for convenience
4135 supports mechanisms involving external applications.
4137 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
4139 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
4140 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-
4141 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.122 , page 119) variable for
4144 These utilities may have a variety of security vulnerabilities, including
4146 The Mutt Next Generation E-Mail Client 82
4148 overwriting of arbitrary files, information leaks or other exploitable bugs.
4149 These vulnerabilities may go unnoticed by the user, especially when they are
4150 called automatically (and without interactive prompting) from the mailcap
4151 file(s). When using mutt-ng's autoview mechanism in combination with mailcap
4152 files, please be sure to...
4154 +
\bo manually select trustworth applications with a reasonable calling sequence
4156 +
\bo periodically check the contents of mailcap files, especially after soft-
4157 ware installations or upgrades
4159 +
\bo keep the software packages referenced in the mailcap file up to date
4161 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.123 , page 119) variable in its
4162 default state to restrict mailcap expandos to a safe set of characters
4164 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
4166 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4169 The same security considerations apply for these as for tools involved via
4170 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4171 compressed folders support if the uncompressed mailbox is too large for the
4172 disk it is saved to.)
4174 As already noted, most of these problems are not built in but caused by wrong
4175 configuration, so please check your configuration.
4177 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4179 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4181 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4182 mailbox. However, it is possible to read other mailboxes and to send messages
4183 from the command line as well.
4185 The Mutt Next Generation E-Mail Client 83
4188 -a attach a file to a message
4189 -b specify a blind carbon-copy (BCC) address
4190 -c specify a carbon-copy (Cc) address
4191 -e specify a config command to be run after initialization files are read
4192 -f specify a mailbox to load
4193 -F specify an alternate file to read initialization commands
4194 -h print help on command line options
4195 -H specify a draft file from which to read a header and body
4196 -i specify a file to include in a message composition
4197 -m specify a default mailbox type
4198 -n do not read the system Muttngrc
4199 -p recall a postponed message
4200 -Q query a configuration variable
4201 -R open mailbox in read-only mode
4202 -s specify a subject (enclose in quotes if it contains spaces)
4203 -t dump the value of all variables to stdout
4204 -T dump the value of all changed variables to stdout
4205 -v show version number and compile-time definitions
4206 -x simulate the mailx(1) compose mode
4207 -y show a menu containing the files specified by the mailboxes command
4208 -z exit immediately if there are no messages in the mailbox
4209 -Z open the first folder with new message,exit immediately if none
4211 To read messages in a mailbox
4213 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4215 To compose a new message
4217 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-
4218 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4220 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4221 rect input from the file you wish to send. For example,
4223 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4225 This command will send a message to ``professor@bigschool.edu'' with a subject
4226 of ``data set for run #2''. In the body of the message will be the contents of
4227 the file ``~/run2.dat''.
4229 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4231 The Mutt Next Generation E-Mail Client 84
4234 ~b EXPR messages which contain EXPR in the message body
4235 ~B EXPR messages which contain EXPR in the whole message
4236 ~c USER messages carbon-copied to USER
4237 ~C EXPR message is either to: or cc: EXPR
4239 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4241 ~e EXPR message which contains EXPR in the ``Sender'' field
4243 ~f USER messages originating from USER
4244 ~g cryptographically signed messages
4245 ~G cryptographically encrypted messages
4246 ~H EXPR messages with a spam attribute matching EXPR
4247 ~h EXPR messages which contain EXPR in the message header
4248 ~k message contains PGP key material
4249 ~i ID message which match ID in the ``Message-ID'' field
4250 ~L EXPR message is either originated or received by EXPR
4251 ~l message is addressed to a known mailing list
4252 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4253 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4256 ~p message is addressed to you (consults alternates)
4257 ~P message is from you (consults alternates)
4258 ~Q messages which have been replied to
4260 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4261 ~S superseded messages
4262 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4264 ~t USER messages addressed to USER
4266 ~v message is part of a collapsed thread.
4267 ~V cryptographically verified messages
4268 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4269 (if compiled with NNTP support)
4270 ~x EXPR messages which contain EXPR in the `References' field
4271 ~y EXPR messages which contain EXPR in the `X-Label' field
4272 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4273 ~= duplicated messages (see $duplicate_threads)
4274 ~$ unreferenced messages (requires threaded view)
4275 ~* ``From'' contains realname and (syntactically) valid
4276 address (excluded are addresses matching against
4277 alternates or any alias)
4279 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
4280 48). Special attention has to be made when using regular expressions inside of
4281 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4282 level of backslash (\), which is normally used for quoting. If it is your
4283 intention to use a backslash in the regular expression, you will need to use
4284 two backslashes instead (\\).
4286 The Mutt Next Generation E-Mail Client 85
4288 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4290 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4292 The following are the commands understood by mutt.
4294 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 67) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4296 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 26) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4298 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 26) [ * | _
\bk_
\be_
\by ... ]
4300 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4302 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 33) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4304 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4306 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4308 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4310 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4312 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4314 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 27) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4316 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 29) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4318 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4320 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 30) _
\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 ]
4322 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 30) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4324 +
\bo _
\be_
\bx_
\be_
\bc (section 3.25 , page 41) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4326 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4328 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4330 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 29) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4332 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 38) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4334 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 38) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4336 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 29) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4338 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 32) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4340 The Mutt Next Generation E-Mail Client 86
4342 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 32) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4344 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4346 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4348 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 29) _
\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 ]
4350 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 37) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4352 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4354 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4356 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4358 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4360 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.9 , page 30) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4362 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.9 , page 30) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4364 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4366 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4368 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4370 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.23 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4372 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 41) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4374 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4376 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4378 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4380 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4382 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 39) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4384 +
\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
4386 +
\bo _
\bs_
\be_
\bt (section 3.28 , page 44) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4388 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4390 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 45) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4392 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.27 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4394 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.27 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4396 The Mutt Next Generation E-Mail Client 87
4398 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4400 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4402 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4404 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.30 , page 46) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4406 _
\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
4408 The following list contains all variables which, in the process of providing
4409 more consistency, have been renamed and are partially even removed already. The
4410 left column contains the old synonym variables, the right column the full/new
4413 The Mutt Next Generation E-Mail Client 88
4415 edit_hdrs edit_headers
4416 forw_decode forward_decode
4417 forw_format forward_format
4418 forw_quote forward_quote
4419 hdr_format index_format
4420 indent_str indent_string
4421 mime_fwd mime_forward
4422 msg_format message_format
4423 pgp_autosign crypt_autosign
4424 pgp_autoencrypt crypt_autoencrypt
4425 pgp_replyencrypt crypt_replyencrypt
4426 pgp_replysign crypt_replysign
4427 pgp_replysignencrypted crypt_replysignencrypted
4428 pgp_verify_sig crypt_verify_sig
4429 pgp_create_traditional pgp_autoinline
4430 pgp_auto_traditional pgp_replyinline
4431 forw_decrypt forward_decrypt
4432 smime_sign_as smime_default_key
4433 post_indent_str post_indent_string
4434 print_cmd print_command
4435 shorten_hierarchy sidebar_shorten_hierarchy
4436 ask_followup_to nntp_ask_followup_to
4437 ask_x_comment_to nntp_ask_x_comment_to
4438 catchup_newsgroup nntp_catchup
4439 followup_to_poster nntp_followup_to_poster
4440 group_index_format nntp_group_index_format
4442 mime_subject nntp_mime_subject
4443 news_cache_dir nntp_cache_dir
4444 news_server nntp_host
4446 nntp_poll nntp_mail_check
4447 pop_checkinterval pop_mail_check
4448 post_moderated nntp_post_moderated
4449 save_unsubscribed nntp_save_unsubscribed
4450 show_new_news nntp_show_new_news
4451 show_only_unread nntp_show_only_unread
4452 x_comment_to nntp_x_comment_to
4453 smtp_auth_username smtp_user
4454 smtp_auth_password smtp_pass
4456 The contrib subdirectory contains a script named update-config.pl which eases
4459 A complete list of current variables follows.
4461 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
4467 This variable specifies whether to abort sending if no attachment was made but
4469 The Mutt Next Generation E-Mail Client 89
4471 the content references them, i.e. the content matches the regular expression
4472 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 92). If a match was
4473 found and this variable is set to _
\by_
\be_
\bs, message sending will be aborted but the
4474 mail will be send nevertheless if set to _
\bn_
\bo.
4476 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 92) are
4477 intended to remind the user to attach files if the message's text references
4480 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 92) variable.
4482 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4488 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4489 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4490 subject given at the subject prompt will never be aborted.
4492 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4498 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4499 body if no changes are made to the file (this check only happens after the
4500 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4502 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bg_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4508 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
4509 cating which version of Mutt-ng was used for composing them.
4511 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4515 Default: '~/.muttngrc'
4517 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4518 tion 2.5.4 , page 11)'' function.
4520 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4521 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 45)'' command for it to be executed.
4523 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4525 The Mutt Next Generation E-Mail Client 90
4529 Default: '%4n %2f %t %-10a %r'
4531 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4532 ing printf(3)-style sequences are available:
4538 flags - currently, a 'd' for an alias marked for deletion
4544 address which alias expands to
4547 character which indicates if the alias is tagged for inclusion
4549 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4555 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4556 or base64 encoding when sending mail.
4558 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4564 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4565 sages) are to be interpreted. Messages containing these codes are rare, but if
4566 this option is set, their text will be colored accordingly. Note that this may
4567 override your color choices, and even present a security problem, since a mes-
4568 sage could include a line like ``[-- PGP output follows ...' and give it the
4569 same color as your attachment color.
4571 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4577 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4578 instead of highlighting the whole line. On slow network or modem links this
4579 will make response faster because there is less that has to be redrawn on the
4580 screen when moving to the next or previous entries in the menu.
4582 The Mutt Next Generation E-Mail Client 91
4584 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4590 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4591 attachment trees, instead of the default ACS characters.
4593 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4599 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4600 editing an outgoing message.
4602 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bs_
\bk_
\bc_
\bc
4608 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4609 the body of an outgoing message.
4611 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4617 This variable is a colon-separated list of character encoding schemes for mes-
4618 sages without character encoding indication. Header field values and message
4619 body content without character encoding indication would be assumed that they
4620 are written in one of this list. By default, all the header fields and message
4621 body without any charset indication are assumed to be in us-ascii.
4623 For example, Japanese users might prefer this:
4625 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4627 However, only the first content is valid for the message body. This variable
4628 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.324 , page 168) is unset.
4630 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4634 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4636 This variable describes the format of the ``attachment'' menu. The following
4637 printf(3)-style sequences are understood:
4639 The Mutt Next Generation E-Mail Client 92
4645 requires charset conversion (n or c)
4654 MIME Content-Transfer-Encoding: header field
4660 MIME Content-Disposition: header field (I=inline, A=attachment)
4678 graphic tree characters
4681 unlink (=to delete) flag
4684 right justify the rest of the string and pad with character 'X'
4687 pad to the end of the line with character 'X'
4689 _
\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
4691 Type: regular expression
4695 The Mutt Next Generation E-Mail Client 93
4697 If this variable is non-empty, muttng will scan a message's contents before
4698 sending for this regular expression. If it is found, it will ask for what to do
4699 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 88).
4701 This variable and _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 88) are intended to
4702 remind the user to attach files if the message's text references them.
4704 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4710 The separator to add between attachments when operating (saving, printing, pip-
4711 ing, etc) on a list of tagged attachments.
4713 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4719 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4720 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4721 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.16 ,
4722 page 93)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4723 operate on the attachments one by one.
4725 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4729 Default: 'On %d, %n wrote:'
4731 This is the string that will precede a message which has been included in a
4732 reply. For a full listing of defined printf(3)-like sequences see the section
4733 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115)''.
4735 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4741 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4742 all tagged messages (if there are any). When unset, you must first use the
4743 ``tag-prefix'' function (default: ';') to make the next function apply to all
4746 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4752 The Mutt Next Generation E-Mail Client 94
4754 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'', Mutt-ng
4755 will skip the initial send-menu and allow you to immediately begin editing the
4756 body of your message. The send-menu may still be accessed once you have fin-
4757 ished editing the body of your message.
4759 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.66 , page 104)''.
4761 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\be_
\be_
\bp
4767 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4769 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4775 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4776 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4777 tion 7.4.21 , page 94)'' variable.
4779 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4785 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4786 you don't get asked if you want to bounce a message. Setting this variable to
4787 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4790 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4796 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4797 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4799 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4805 When this variable is set, mutt will place the cursor at the beginning of the
4806 current line in menus, even when the arrow_cursor variable is unset, making it
4807 easier for blind persons using Braille displays to follow these menus. The
4809 The Mutt Next Generation E-Mail Client 95
4811 option is disabled by default because many visual terminals don't permit making
4812 the cursor invisible.
4814 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4818 Default: '~/.mutt_certificates'
4820 Availability: SSL or GNUTLS
4822 This variable specifies the file where the certificates you trust are saved.
4823 When an unknown certificate is encountered, you are asked if you accept it or
4824 not. If you accept it, the certificate can also be saved in this file and fur-
4825 ther connections are automatically accepted.
4827 You can also manually add CA certificates in this file. Any server certificate
4828 that is signed with one of these CA certificates are also automatically
4831 Example: set certificate_file=~/.muttng/certificates
4833 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4839 Character set your terminal uses to display and enter textual data.
4841 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4847 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4849 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4850 Especially with MH mailboxes, this operation can take quite some time since it
4851 involves scanning the directory and checking each file to see if it has already
4852 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4855 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4861 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4864 The Mutt Next Generation E-Mail Client 96
4866 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4870 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4872 Controls the format of the status line displayed in the ``compose'' menu. This
4873 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.321 , page 165)'', but has
4874 its own set of printf(3)-like sequences:
4877 total number of attachments
4883 approximate size (in bytes) of the current message
4886 Mutt-ng version string
4888 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.321 , page 165)''
4889 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 ,
4892 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4898 When defined, Mutt-ng will recode commands in rc files from this encoding.
4900 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4906 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4909 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4915 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4916 box which does not yet exist before creating it.
4918 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4920 The Mutt Next Generation E-Mail Client 97
4926 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4927 many seconds if the connection is not able to be established. A negative value
4928 causes Mutt-ng to wait indefinitely for the connection to succeed.
4930 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4934 Default: 'text/plain'
4936 Sets the default Content-Type: header field for the body of newly composed mes-
4939 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\bo_
\bp_
\by
4945 This variable controls whether or not copies of your outgoing messages will be
4946 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.243 , page
4947 147)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.254 , page 150)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4948 7.4.74 , page 106)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 39)''.
4950 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4956 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4957 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4958 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4959 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
4960 7.4.290 , page 158)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4961 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4964 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4970 This variable controls whether or not Mutt-ng may automatically enable PGP
4971 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
4972 7.4.37 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 98)'',
4973 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4974 7.4.42 , page 98)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.290 , page 158)''.
4976 The Mutt Next Generation E-Mail Client 98
4978 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4984 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4985 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4986 signing is not required or encryption is requested as well. If
4987 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.290 , page 158)'' is _
\bs_
\be_
\bt, then OpenSSL is
4988 used instead to create S/MIME messages and settings can be overridden by use of
4989 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4991 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4997 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4998 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
4999 7.4.37 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 98)'',
5000 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
5001 7.4.42 , page 98)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.290 , page 158)''.
5003 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
5009 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
5010 encrypted. (Crypto only)
5012 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
5018 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
5020 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
5023 _
\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
5029 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
5030 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
5031 7.4.41 , page 98)'', because it allows you to sign all messages which are
5033 The Mutt Next Generation E-Mail Client 99
5035 automatically encrypted. This works around the problem noted in
5036 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.42 , page 98)'', that Mutt-ng is not able to
5037 find out whether an encrypted message is also signed. (Crypto only)
5039 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
5045 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
5046 S/MIME output, so spoofing such lines is more difficult. If you are using col-
5047 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
5050 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
5056 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
5057 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
5058 will be used instead of the classic code.
5060 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
5061 won't have any effect when used interactively.
5063 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
5069 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
5070 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
5071 cryptographic signatures. (Crypto only)
5073 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5077 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
5079 This variable controls the format of the date printed by the ``%d'' sequence in
5080 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115)''. This is passed to strftime(3)
5081 to process the date.
5083 Unless the first character in the string is a bang (``!''), the month and week
5084 day names are expanded according to the locale specified in the variable
5085 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.120 , page 119)''. If the first character in the string
5086 is a bang, the bang is discarded, and the month and week day names in the rest
5087 of the string are expanded in the _
\bC locale (that is in US English).
5089 The Mutt Next Generation E-Mail Client 100
5091 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\be_
\bb_
\bu_
\bg_
\b__
\bl_
\be_
\bv_
\be_
\bl
5099 This variable specifies the current debug level and may be used to increase or
5100 decrease the verbosity level during runtime. It overrides the level given with
5101 the -d command line option.
5103 Currently, this number must be >= 0 and <= 5 and muttng must be started with -d
5104 to enable debugging at all; enabling at runtime is not possible.
5106 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
5110 Default: '~f %s !~P | (~P ~C %s)'
5112 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
5113 will be interpreted if they are specified with only a simple regexp, instead of
5114 a matching pattern. The hooks are expanded when they are declared, so a hook
5115 will be interpreted according to the value of this variable at the time the
5116 hook is declared. The default value matches if the message is either from a
5117 user matching the regular expression given, or if it is from you (if the from
5118 address matches ``alternates'') and is to or cc'ed to a user matching the given
5121 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\be_
\bl_
\be_
\bt_
\be
5127 Controls whether or not messages are really deleted when closing or synchroniz-
5128 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
5129 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
5130 be kept in the mailbox.
5132 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be
5138 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
5139 7.4.330 , page 169) variable, this variable specifies whether to also set the
5140 DelSp parameter to yes. If this is _
\bu_
\bn_
\bs_
\be_
\bt, no additional parameter will be send
5141 as a value of no already is the default behavior.
5143 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
5144 (section 7.4.330 , page 169) is _
\bs_
\be_
\bt) but not on incomming.
5146 The Mutt Next Generation E-Mail Client 101
5148 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
5154 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
5155 tion. This applies when you either explicitly delete a message, or when you
5156 save it to another folder.
5158 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
5164 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
5165 subparts of individual messages in a multipart/digest. To see these subparts,
5166 press 'v' on that menu.
5168 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
5174 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
5175 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.54 ,
5176 page 101), and the filtered message is read from the standard output.
5178 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
5182 Default: '$muttng_bindir/muttng_dotlock'
5184 Availability: Standalone and Dotlock
5186 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
5188 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
5194 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5195 or in connection with the SMTP support via libESMTP.
5197 This variable sets the request for when notification is returned. The string
5198 consists of a comma separated list (no spaces!) of one or more of the follow-
5199 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
5200 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
5201 notified of successful transmission.
5203 The Mutt Next Generation E-Mail Client 102
5205 Example: set dsn_notify='failure,delay'
5207 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
5213 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5214 or in connection with the SMTP support via libESMTP.
5216 This variable controls how much of your message is returned in DSN messages.
5217 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
5218 return the full message.
5220 Example: set dsn_return=hdrs
5222 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
5228 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
5229 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
5230 indicate that it thinks they are duplicates of each other with an equals sign
5231 in the thread diagram.
5233 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5239 This option allows you to edit the header of your outgoing messages along with
5240 the body of your message.
5242 Which empty header fields to show is controlled by the _
\b$_
\be_
\bd_
\bi_
\bt_
\bo_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section
5243 7.4.61 , page 102) option.
5245 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5251 This variable specifies which editor is used by Mutt-ng. It defaults to the
5252 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5253 if neither of those are set.
5255 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5259 The Mutt Next Generation E-Mail Client 103
5261 Default: 'From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To: X-Com-
5264 If _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) is _
\bs_
\be_
\bt, this space-separated list
5265 specifies which _
\bn_
\bo_
\bn_
\b-_
\be_
\bm_
\bp_
\bt_
\by header fields to edit in addition to user-defined
5268 Note: if _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) had to be turned on by
5269 force because _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo (section 7.4.323 , page 168) is _
\bu_
\bn_
\bs_
\be_
\bt, this
5270 option has no effect.
5272 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5278 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5279 string ``From '' (note the trailing space) in the beginning of a line. Useful
5280 to avoid the tampering certain mail delivery and transport agents tend to do
5283 N
\bNo
\bot
\bte
\be:
\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
5284 <em/strongly/ advised to _
\bs_
\be_
\bt this option although discouraged by the standard.
5285 Alternatively, you must take care of space-stuffing <tt/From / lines (with a
5286 trailing space) yourself.
5288 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5296 The file which includes random data that is used to initialize SSL library
5299 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5305 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5306 ``From:'' header field. Note that this information is passed to the sendmail
5307 command using the ``-f' command line switch, so don't set this option if you
5308 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.260 , page 151) yourself, or
5309 if the sendmail on your machine doesn't support that command line switch.
5311 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5315 The Mutt Next Generation E-Mail Client 104
5319 Escape character to use for functions in the builtin editor.
5321 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5327 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5328 ing to messages, and the initial prompt for subject is skipped when forwarding
5331 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
5332 93)'' variable is _
\bs_
\be_
\bt.
5334 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5340 This variable controls whether or not attachments on outgoing messages are
5341 saved along with the main body of your message.
5343 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5349 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5350 when the actual message is encrypted and/or signed. (PGP only)
5352 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5358 This variable is a colon-separated list of character encoding schemes for text
5359 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.27 , page 95) value will
5360 be used instead. For example, the following configuration would work for
5361 Japanese text handling:
5363 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5365 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5368 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5372 The Mutt Next Generation E-Mail Client 105
5376 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5377 beginning of a pathname will be expanded to the value of this variable. Note
5378 that if you change this variable from the default value you need to make sure
5379 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5380 ables since expansion takes place during the ``set'' command.
5382 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5386 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5388 This variable allows you to customize the file browser display to your personal
5389 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page
5390 115)'', but has its own set of printf(3)-like sequences:
5396 date/time folder was last modified
5405 group name (or numeric gid, if missing)
5408 number of hard links
5411 N if folder has new mail, blank otherwise
5417 * if the file is tagged, blank otherwise
5420 owner name (or numeric uid, if missing)
5423 right justify the rest of the string and pad with character 'X'
5426 pad to the end of the line with character 'X'
5428 The Mutt Next Generation E-Mail Client 106
5430 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5436 Controls whether or not the Mail-Followup-To: header field is generated when
5437 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5438 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5439 3.13 , page 36)'' commands or detected by common mailing list headers.
5441 This field has two purposes. First, preventing you from receiving duplicate
5442 copies of replies to messages which you send to mailing lists. Second, ensuring
5443 that you do get a reply separately for any messages sent to known lists to
5444 which you are not subscribed. The header will contain only the list's address
5445 for subscribed lists, and both the list address and your own email address for
5446 unsubscribed lists. Without this header, a group reply to your message sent to
5447 a subscribed list will be sent to both the list and your address, resulting in
5448 two copies of the same email for you.
5450 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5456 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
5457 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
5458 already known to have new mail.
5460 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.334 , page 170)'',
5461 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.121 , page 119)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5462 7.4.105 , page 113)''.
5464 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5470 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.254 , page 150)'',
5471 except that Mutt-ng will store a copy of your outgoing message by the username
5472 of the address you are sending to even if that mailbox does not exist.
5474 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.243 , page 147)'' variable.
5476 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5482 Controls the decoding of complex MIME messages into text/plain when forwarding
5483 a message. The message header is also RFC2047 decoded. This variable is only
5485 The Mutt Next Generation E-Mail Client 107
5487 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5488 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.144 , page 123)'' is used instead.
5490 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5496 Controls the handling of encrypted messages when forwarding a message. When
5497 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5498 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 123)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5499 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.144 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5501 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5507 This quadoption controls whether or not the user is automatically placed in the
5508 editor when forwarding messages. For those who always want to forward with no
5509 modification, use a setting of _
\bn_
\bo.
5511 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5517 This variable controls the default subject when forwarding a message. It uses
5518 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page
5521 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5527 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5528 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5529 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.115 , page 115)''.
5531 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bf_
\br_
\bo_
\bm
5533 Type: e-mail address
5537 This variable contains a default from address. It can be overridden using
5538 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.249 , page
5539 148)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.343 , page
5542 The Mutt Next Generation E-Mail Client 108
5544 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5545 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5546 takes this email address.
5548 Defaults to the contents of the environment variable $EMAIL.
5550 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5552 Type: regular expression
5556 A regular expression used by Mutt-ng to parse the GECOS field of a password
5557 entry when expanding the alias. By default the regular expression is set to
5558 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5559 the GECOS field contains a string like 'lastname, firstname' then you should
5560 do: set gecos_mask='.*'.
5562 This can be useful if you see the following behavior: you address a e-mail to
5563 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5564 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5565 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5566 to ``Franklin, Steve''.
5568 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\bd_
\br_
\bs
5574 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 ,
5575 page 37)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5576 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5577 defined header fields are added to every new message.
5579 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5585 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5586 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.348 , page
5587 173)'' setting applies.
5589 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5595 Availability: Header Cache
5597 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.84 , page 108) variable points to the header
5599 The Mutt Next Generation E-Mail Client 109
5603 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.84 , page 108) points to a directory it will
5604 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5605 7.4.84 , page 108) points to a file that file will be a single global header
5606 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5608 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5614 If enabled the header cache will be compressed. So only one fifth of the usual
5615 diskspace is used, but the uncompression can result in a slower open of the
5618 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\be_
\bl_
\bp
5624 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5625 by each menu are displayed on the first line of the screen.
5627 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5628 sequence rather than a single keystroke. Also, the help line may not be
5629 updated if a binding is changed while Mutt-ng is running. Since this variable
5630 is primarily aimed at new users, neither of these should present a major prob-
5633 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5639 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5640 7.4.95 , page 110)'' variable when adding the domain part to addresses. This
5641 variable does not affect the generation of Message-ID: header fields, and it
5642 will not lead to the cut-off of first-level domains.
5644 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5650 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5651 limiting, in the thread tree.
5653 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5655 The Mutt Next Generation E-Mail Client 110
5661 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5664 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5670 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5671 have the same subject as their parent or closest previously displayed sibling.
5673 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5679 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5680 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5681 _
\bi_
\bn_
\bg (section 7.4.89 , page 109) is set, this option will have no effect.
5683 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5689 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5690 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.88 ,
5691 page 109) is _
\bs_
\be_
\bt, this option will have no effect.
5693 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5699 This variable controls the size (in number of strings remembered) of the string
5700 history buffer. The buffer is cleared each time the variable is changed.
5702 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5708 This variable controls whether or not a Mail-Followup-To: header field is hon-
5709 ored when group-replying to a message.
5711 The Mutt Next Generation E-Mail Client 111
5713 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5719 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5720 during generation of Message-Id: headers.
5722 Please be sure to really know what you are doing when changing this variable to
5723 configure a custom domain part of Message-IDs.
5725 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5731 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5732 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5733 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5734 header field was set by the mailing list to automate responses to the list, and
5735 will ignore this field. To direct a response to the mailing list when this
5736 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
5737 sender and the list.
5739 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5747 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5748 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5749 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5750 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5751 eter is case-insensitive.
5753 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5754 ods, in order from most-secure to least-secure.
5756 Example: set imap_authenticators='gssapi:cram-md5:login'
5758 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5759 ous methods are unavailable. If a method is available but authentication fails,
5760 Mutt-ng will not connect to the IMAP server.
5762 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5768 The Mutt Next Generation E-Mail Client 112
5770 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5771 connection, and add them to the set of mailboxes it polls for new mail. See
5772 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 37)'' command.
5774 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5782 This contains the list of characters which you would like to treat as folder
5783 separators for displaying IMAP paths. In particular it helps in using the '='
5784 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 104) variable.
5786 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5794 Mutt-ng requests these header fields in addition to the default headers (``DATE
5795 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5796 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5797 ``index'' menu. You may want to add more headers for spam detection.
5799 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5801 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5809 You normally want to see your personal folders alongside your INBOX in the IMAP
5810 browser. If you see something else, you may set this variable to the IMAP path
5813 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5821 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5822 wait before polling open IMAP connections, to prevent the server from closing
5823 them before Mutt-ng has finished with them.
5825 The Mutt Next Generation E-Mail Client 113
5827 The default is well within the RFC-specified minimum amount of time (30 min-
5828 utes) before a server is allowed to do this, but in practice the RFC does get
5829 violated every now and then.
5831 Reduce this number if you find yourself getting disconnected from your IMAP
5832 server due to inactivity.
5834 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5842 This variable configures whether IMAP folder browsing will look for only sub-
5843 scribed folders or all folders. This can be toggled in the IMAP browser with
5844 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5846 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5854 Your login name on the IMAP server.
5856 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.111 , page
5859 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5865 This variable configures how often (in seconds) Mutt-ng should look for new
5866 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.121 ,
5867 page 119)'' variable to generate less traffic and get more accurate information
5870 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5878 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5879 you for your password when you invoke the fetch-mail function.
5881 The Mutt Next Generation E-Mail Client 114
5883 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5884 machine, because the superuser can read your configuration even if you are the
5885 only one who can read the file.
5887 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5895 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5896 Mutt-ng will only check for new mail over existing IMAP connections. This is
5897 useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
5898 cation, or if opening the connection is slow.
5900 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5908 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5909 fetch a message from the server. This is generally a good thing, but can make
5910 closing an IMAP folder somewhat slower. This option exists to appease speed
5913 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5921 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5924 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5932 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5933 messages. Since these messages are often harmless, or generated due to configu-
5934 ration problems on the server which are out of the users' hands, you may wish
5935 to suppress them at some point.
5937 The Mutt Next Generation E-Mail Client 115
5939 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5947 The name of the user whose mail you intend to access on the IMAP server.
5949 This variable defaults to your user name on the local machine.
5951 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5957 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5958 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5959 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5960 convert the body part to text form.
5962 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5968 Controls whether or not a copy of the message(s) you are replying to is
5969 included in your reply.
5971 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5977 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5978 sage you are replying.
5980 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5986 Specifies the string to prepend to each line of text quoted in a message to
5987 which you are replying. You are strongly encouraged not to change this value,
5988 as it tends to agitate the more fanatical netizens.
5990 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5994 The Mutt Next Generation E-Mail Client 116
5996 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5998 This variable allows you to customize the message index display to your per-
6001 ``Format strings'' are similar to the strings used in the ``C'' function
6002 printf(3) to format output (see the man page for more detail). The following
6003 sequences are defined in Mutt-ng:
6006 address of the author
6009 reply-to address (if present; otherwise: address of author)
6012 filename of the original message folder (think mailBox)
6015 the list to which the letter was sent, or else the folder name
6019 number of characters (bytes) in the message
6022 current message number
6025 date and time of the message in the format specified by ``date_for-
6026 mat'' converted to sender's time zone
6029 date and time of the message in the format specified by ``date_for-
6030 mat'' converted to the local time zone
6033 current message number in thread
6036 number of messages in current thread
6039 entire From: line (address + real name)
6042 author name, or recipient name if the message is from you
6045 spam attribute(s) of this message
6048 newsgroup name (if compiled with nntp support)
6050 The Mutt Next Generation E-Mail Client 117
6053 message-id of the current message
6056 number of lines in the message (does not work with maildir, mh, and
6057 possibly IMAP folders)
6060 If an address in the To or CC header field matches an address
6061 defined by the users ``subscribe'' command, this displays 'To
6062 <list-name>', otherwise the same as %F.
6065 total number of message in the mailbox
6068 number of hidden messages if the thread is collapsed.
6074 author's real name (or address if missing)
6077 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
6078 the message: list name or recipient name if no list
6081 subject of the message
6084 status of the message (N/D/d/!/r/*)
6087 `to:' field (recipients)
6090 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.336 ,
6094 user (login) name of the author
6097 first name of the author, or the recipient if the message is from
6101 name of organization of author (`organization:' field)
6104 `x-label:' field, if present
6106 The Mutt Next Generation E-Mail Client 118
6109 `x-label' field, if present, and (1) not at part of a thread tree,
6110 (2) at the top of a thread, or (3) `x-label' is different from pre-
6111 ceding message's `x-label'.
6114 message status flags
6117 the date and time of the message is converted to sender's time
6118 zone, and ``fmt'' is expanded by the library function ``strftime'';
6119 a leading bang disables locales
6122 the date and time of the message is converted to the local time
6123 zone, and ``fmt'' is expanded by the library function ``strftime'';
6124 a leading bang disables locales
6127 the local date and time when the message was received. ``fmt'' is
6128 expanded by the library function ``strftime''; a leading bang dis-
6132 the current local time. ``fmt'' is expanded by the library function
6133 ``strftime''; a leading bang disables locales.
6136 right justify the rest of the string and pad with character 'X'
6139 pad to the end of the line with character 'X'
6141 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.336 , page 171)''.
6143 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
6149 How to invoke ispell (GNU's spell-checking software).
6151 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6157 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
6158 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.131 , page 121)'' mailbox, or as a result of
6159 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37)'' command.
6161 The Mutt Next Generation E-Mail Client 119
6163 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
6169 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
6170 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
6171 will ask if you really intended to reply to the author only.
6173 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
6179 The locale used by strftime(3) to format dates. Legal values are the strings
6180 your system accepts for the locale variable LC_TIME.
6182 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6188 This variable configures how often (in seconds) Mutt-ng should look for new
6191 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
6192 7.4.105 , page 113).
6194 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
6200 This variable specifies which files to consult when attempting to display MIME
6201 bodies not directly supported by Mutt-ng.
6203 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
6209 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
6210 well-defined set of safe characters. This is the safe setting, but we are not
6211 sure it doesn't break some more advanced MIME stuff.
6213 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!
6215 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\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
6217 The Mutt Next Generation E-Mail Client 120
6223 Availability: Header Cache
6225 Check for Maildir unaware programs other than Mutt-ng having modified maildir
6226 files when the header cache is in use. This incurs one stat(2) per message
6227 every time the folder is opened.
6229 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
6235 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
6236 flag instead of physically deleted.
6238 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
6239 effect on other mailbox types.
6241 It is similiar to the trash option.
6243 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
6249 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
6250 mailbox without reading them.
6252 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
6253 up with an 'O' next to them in the ``index'' menu, indicating that they are
6256 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
6262 Controls the display of wrapped lines in the internal pager. If set, a ``+''
6263 marker is displayed at the beginning of wrapped lines. Also see the
6264 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.276 , page 155)'' variable.
6266 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\ba_
\bs_
\bk
6268 Type: regular expression
6272 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6274 The Mutt Next Generation E-Mail Client 121
6276 operator ``!''. Only files whose names match this mask will be shown. The
6277 match is always case-sensitive.
6279 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6285 When set non-zero, this specifies the maximum number of recipient header lines
6286 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6287 case the number of lines exeeds its value, the last line will have 3 dots
6290 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6296 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6297 is limited to this length. A value of 0 (which is also the default) means that
6298 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6299 (section 7.4.350 , page 174).
6301 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\bb_
\bo_
\bx
6307 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6308 7.4.310 , page 163)'' folder will be appended.
6310 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6316 The default mailbox type used when creating new folders. May be any of mbox,
6317 MMDF, MH and Maildir.
6319 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6325 This variable controls the number of lines of context that are given when
6326 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.180 , page
6329 The Mutt Next Generation E-Mail Client 122
6331 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6337 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6338 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6339 entry may move off the bottom.
6341 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6347 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6348 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6349 vious page of the menu is displayed (useful for slow links to avoid many
6352 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6358 This is the string displayed in the ``attachment'' menu for attachments of type
6359 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6360 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115)''.
6362 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6368 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6369 if the user had pressed the ESC key and whatever key remains after having the
6370 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6371 then this is treated as if the user had pressed ESC then ``x''. This is
6372 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6373 the ASCII character ``x''.
6375 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\be_
\bt_
\bo_
\bo
6381 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6382 from the list of recipients when replying to a message.
6384 The Mutt Next Generation E-Mail Client 123
6386 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6392 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6393 _
\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-
6394 able is set, the message files will simply be deleted.
6396 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6402 The name of the MH sequence used for flagged messages.
6404 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6410 The name of the MH sequence used to tag replied messages.
6412 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6418 The name of the MH sequence used for unseen messages.
6420 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6426 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6427 part instead of included in the main body of the message.
6429 This is useful for forwarding MIME messages so the receiver can properly view
6430 the message as it was delivered to you. If you like to switch between MIME and
6431 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6433 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.75 , page 106)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6434 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.144 , page 123)''.
6436 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6440 The Mutt Next Generation E-Mail Client 124
6444 Controls the decoding of complex MIME messages into text/plain when forwarding
6445 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 123)'' is _
\bs_
\be_
\bt. Other-
6446 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.75 , page 106)'' is used instead.
6448 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6454 When forwarding multiple attachments of a MIME message from the recvattach
6455 menu, attachments which cannot be decoded in a reasonable manner will be
6456 attached to the newly composed message if this option is set.
6458 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6462 Default: '%4n %c %-16s %a'
6464 Availability: Mixmaster
6466 This variable describes the format of a remailer line on the mixmaster chain
6467 selection screen. The following printf(3)-like sequences are supported:
6470 The running number on the menu.
6473 Remailer capabilities.
6476 The remailer's short name.
6479 The remailer's e-mail address.
6481 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6485 Default: 'mixmaster'
6487 Availability: Mixmaster
6489 This variable contains the path to the Mixmaster binary on your system. It is
6490 used with various sets of parameters to gather the list of known remailers, and
6491 to finally send a message through the mixmaster chain.
6493 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bm_
\bo_
\bv_
\be
6497 The Mutt Next Generation E-Mail Client 125
6501 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6502 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.131 , page 121)'' mailbox, or as a result of a
6503 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37)'' command.
6505 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6509 Default: '%Y%m%d%h%M%s.G%P%p'
6511 This is the format for the ``local part'' of the Message-Id: header field gen-
6512 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6513 generated. The '%' character marks that certain data will be added to the
6514 string, similar to printf(3). The following characters are allowed:
6517 the current day of month
6529 the current UNIX timestamp (octal)
6535 the current Message-ID prefix (a character rotating with every Mes-
6536 sage-ID being generated)
6539 a random integer value (decimal)
6542 a random integer value (hexadecimal)
6548 the current UNIX timestamp (decimal)
6551 the current UNIX timestamp (hexadecimal)
6553 The Mutt Next Generation E-Mail Client 126
6556 the current year (Y2K compliant)
6561 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6562 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6564 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bb_
\bi_
\bn_
\bd_
\bi_
\br
6566 Type: system property
6568 Value: /opt/freebsd4/mutt-ng/bin
6570 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be
6571 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bb_
\bi_
\bn_
\ba_
\br_
\by_
\b.
6573 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bd_
\bo_
\bc_
\bd_
\bi_
\br
6575 Type: system property
6577 Value: /opt/freebsd4/mutt-ng/doc/muttng
6579 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be
6580 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt_
\ba_
\bt_
\bi_
\bo_
\bn_
\b.
6582 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bh_
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bb_
\ba_
\bc_
\bk_
\be_
\bn_
\bd
6584 Type: system property
6588 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br _
\bc_
\bh_
\ba_
\bc_
\bh_
\bi_
\bn_
\bg_
\b'_
\bs _
\bd_
\ba_
\bt_
\ba_
\b-
6589 _
\bb_
\ba_
\bs_
\be _
\bb_
\ba_
\bc_
\bk_
\be_
\bn_
\bd_
\b.
6591 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\br_
\be_
\bv_
\bi_
\bs_
\bi_
\bo_
\bn
6593 Type: system property
6597 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b'_
\bs _
\bs_
\bu_
\bb_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn _
\br_
\be_
\bv_
\bi_
\bs_
\bi_
\bo_
\bn
6598 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\b.
6600 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bc_
\bo_
\bn_
\bf_
\bd_
\bi_
\br
6602 Type: system property
6604 Value: /opt/freebsd4/mutt-ng/etc
6606 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be
6607 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\b-_
\bw_
\bi_
\bd_
\be _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\b.
6609 The Mutt Next Generation E-Mail Client 127
6611 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn
6613 Type: system property
6617 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b'_
\bs _
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\b.
6619 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6625 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6626 threads to fit on the screen.
6628 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6636 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6637 ing the body of an outgoing news article.
6639 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6647 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6648 ing the body of an outgoing news article.
6650 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6654 Default: '~/.muttng'
6658 This variable points to directory where Mutt-ng will cache news article head-
6659 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6660 when you enter a newsgroup.
6662 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6663 cally increases speed and lowers traffic.
6665 The Mutt Next Generation E-Mail Client 128
6667 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6675 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6676 when you leaving it.
6678 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6686 This variable controls how many news articles to cache per newsgroup (if
6687 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.159 , page 127)) and how
6688 many news articles to show in the ``index'' menu.
6690 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.161 ,
6691 page 128), all older ones will be removed/not shown in the index.
6693 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6701 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6702 header field, a follow-up to the newsgroup is not permitted. The message will
6703 be mailed to the submitter of the message via mail.
6705 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6709 Default: '%4C %M%N %5s %-45.45f %d'
6713 This variable allows you to customize the newsgroup browser display to your
6714 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 ,
6715 page 115)'', but has its own set of printf(3)-like sequences:
6717 The Mutt Next Generation E-Mail Client 129
6719 %C current newsgroup number
6720 %d description of newsgroup (retrieved from server)
6722 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6723 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6724 %n number of new articles in newsgroup
6725 %s number of unread articles in newsgroup
6726 %>X right justify the rest of the string and pad with character "X"
6727 %|X pad to the end of the line with character "X"
6729 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6737 This variable specifies the name (or address) of the NNTP server to be used.
6739 It defaults to the value specified via the environment variable $NNTPSERVER or
6740 contained in the file /etc/nntpserver.
6742 You can also specify a username and an alternative port for each newsserver,
6745 [nntp[s]://][username[:password]@]newsserver[:port]
6747 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6748 security risk since the superuser of your machine may read it regardless of the
6751 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6759 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6760 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6761 lowing printf(3)-style sequence is understood:
6765 Example: set inews='/usr/local/bin/inews -hS'
6767 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6771 The Mutt Next Generation E-Mail Client 130
6777 This variable controls whether or not descriptions for newsgroups are to be
6778 loaded when subscribing to a newsgroup.
6780 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6788 The time in seconds until any operations on a newsgroup except posting a new
6789 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6790 each operation in index (stepping, read article, etc.).
6792 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6800 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6801 encoded according to RFC2047.
6803 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6805 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6809 Default: '~/.newsrc'
6813 This file contains information about subscribed newsgroup and articles read so
6816 To ease the use of multiple news servers, the following printf(3)-style
6817 sequence is understood:
6821 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6825 The Mutt Next Generation E-Mail Client 131
6831 Your password for NNTP account.
6833 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6834 the superuser of your machine may read it regardless of the file's permissions.
6836 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6844 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6845 sions to post (e.g. moderated).
6847 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6848 is totally read-only, that posting will not have any effect.
6850 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6858 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6859 was connection lost.
6861 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6869 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6870 file and into the news cache.
6872 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6880 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6882 The Mutt Next Generation E-Mail Client 132
6884 browser. Otherwise, it will be done only once for a newsserver. Also controls
6885 whether or not the number of new articles of subscribed newsgroups will be
6888 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6896 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6897 played in the newsgroup browser.
6899 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6907 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6908 tification, Mutt-ng will prompt you for your account name.
6910 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6918 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6919 name of the original article author) to articles that you followup to.
6921 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6927 This specifies the operating system name for the User-Agent: header field. If
6928 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6929 returns. If uname(2) fails, ``UNIX'' will be used.
6931 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6933 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\ba_
\bg_
\be_
\br
6939 The Mutt Next Generation E-Mail Client 133
6941 This variable specifies which pager you would like to use to view messages.
6942 ``builtin'' means to use the builtin pager, otherwise this variable should
6943 specify the pathname of the external pager you would like to use.
6945 Using an external pager may have some disadvantages: Additional keystrokes are
6946 necessary because you can't call Mutt-ng functions directly from the pager, and
6947 screen resizes cause lines longer than the screen width to be badly formatted
6950 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6956 This variable controls the number of lines of context that are given when dis-
6957 playing the next or previous page in the internal pager. By default, Mutt-ng
6958 will display the line after the last one on the screen at the top of the next
6959 page (0 lines of context).
6961 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6965 Default: '-%Z- %C/%m: %-20.20n %s'
6967 This variable controls the format of the one-line message ``status'' displayed
6968 before each message in either the internal or an external pager. The valid
6969 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115)''
6972 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6978 Determines the number of lines of a mini-index which is shown when in the
6979 pager. The current message, unless near the top or bottom of the folder, will
6980 be roughly one third of the way down this mini-index, giving the reader the
6981 context of a few messages before and after the message. This is useful, for
6982 example, to determine how many messages remain to be read in the current
6983 thread. One of the lines is reserved for the status bar from the index, so a
6984 _
\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
6985 0 results in no index being shown. If the number of messages in the current
6986 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
6989 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6995 The Mutt Next Generation E-Mail Client 134
6997 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6998 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
7000 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7006 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
7007 whenever the user performs an operation which ordinarily would result in the
7008 contents of the message being operated on. For example, if the user displays a
7009 pgp-traditional message which has not been manually checked with the check-tra-
7010 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
7013 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7019 This option controls whether Mutt-ng generates old-style inline (traditional)
7020 PGP encrypted or signed messages under certain circumstances. This can be
7021 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
7023 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7024 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7025 ing PGP/MIME messages when inline (traditional) would not work. See also:
7026 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.201 , page 138)''.
7028 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.
7031 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
7037 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
7038 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
7040 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7046 This format is used to create a old-style ``clearsigned'' PGP message.
7048 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)
7050 The Mutt Next Generation E-Mail Client 135
7052 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7058 This format strings specifies a command which is used to decode application/pgp
7061 The PGP command formats have their own set of printf(3)-like sequences:
7064 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
7065 string otherwise. Note: This may be used with a %? construct.
7068 Expands to the name of a file containing a message.
7071 Expands to the name of a file containing the signature part of a
7072 multipart/signed attachment when verifying it.
7075 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.205 , page 139).
7078 One or more key IDs.
7080 For examples on how to configure these formats for the various versions of PGP
7081 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
7082 subdirectory which has been installed on your system alongside the documenta-
7085 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7091 This command is used to decrypt a PGP encrypted message. (PGP only)
7093 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7099 This command is used to encrypt a body part without signing it. (PGP only)
7101 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7107 The Mutt Next Generation E-Mail Client 136
7109 This command is used to both sign and encrypt a body part. (PGP only)
7111 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7115 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
7117 This variable allows you to customize the PGP key selection menu to your per-
7118 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page
7119 115)'', but has its own set of printf(3)-like sequences:
7143 trust/validity of the key-uid association
7146 date of the key where <s> is an strftime(3) expression
7150 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7156 This command is used to export a public key from the user's key ring. (PGP
7159 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7163 The Mutt Next Generation E-Mail Client 137
7167 This command is invoked whenever Mutt-ng will need public key information. %r
7168 is the only printf(3)-like sequence used with this format. (PGP only)
7170 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
7172 Type: regular expression
7176 If you assign a text to this variable, then a PGP signature is only considered
7177 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.211 , page 140)
7178 contains the text. Use this variable if the exit code from the command is 0
7179 even for bad signatures. (PGP only)
7181 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
7187 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
7188 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
7189 want to play interesting key selection games. (PGP only)
7191 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7197 This command is used to import a key from a message into the user's public key
7200 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7206 This command is used to list the public key ring's contents. The output format
7207 must be analogous to the one used by gpg --list-keys --with-colons.
7209 This format is also generated by the pgpring utility which comes with Mutt-ng.
7212 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7218 This command is used to list the secret key ring's contents. The output format
7220 The Mutt Next Generation E-Mail Client 138
7222 must be analogous to the one used by gpg --list-keys --with-colons.
7224 This format is also generated by the pgpring utility which comes with Mutt-ng.
7227 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
7233 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
7236 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
7242 This option controls whether Mutt-ng will prompt you for automatically sending
7243 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
7246 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.
7249 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7255 Setting this variable will cause Mutt-ng to always attempt to create an inline
7256 (traditional) message when replying to a message which is PGP encrypted/signed
7257 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
7258 required. This option does not automatically detect if the (replied-to) mes-
7259 sage is inline; instead it relies on Mutt-ng internals for previously
7260 checked/flagged messages.
7262 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7263 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7264 ing PGP/MIME messages when inline (traditional) would not work. See also:
7265 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.201 , page 138)''.
7267 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.
7270 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
7276 The Mutt Next Generation E-Mail Client 139
7278 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
7279 and multipart/encrypted body parts.
7281 This is useful for applications like encrypted and signed mailing lists, where
7282 the outer layer (multipart/encrypted) can be easily removed, while the inner
7283 multipart/signed part is retained. (PGP only)
7285 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
7291 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
7292 This includes keys which have been revoked, have expired, or have been marked
7293 as ``disabled'' by the user. (PGP only)
7295 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
7301 If you have more than one key pair, this option allows you to specify which of
7302 your private keys to use. It is recommended that you use the keyid form to
7303 specify your key (e.g., ``0x00112233''). (PGP only)
7305 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7311 This command is used to create the detached PGP signature for a multi-
7312 part/signed PGP/MIME body part. (PGP only)
7314 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
7320 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7324 sort alphabetically by user id
7327 sort alphabetically by key id
7330 sort by key creation date
7332 The Mutt Next Generation E-Mail Client 140
7335 sort by the trust of the key
7337 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7340 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7346 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7347 printable. Please note that unsetting this variable may lead to problems with
7348 non-verifyable PGP signatures, so only change this if you know what you are
7351 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7357 The number of seconds after which a cached passphrase will expire if not used.
7358 Default: 300. (PGP only)
7360 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7366 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7368 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7374 This command is used to verify PGP signatures. (PGP only)
7376 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7382 This command is used to verify key information from the key selection menu.
7385 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7389 The Mutt Next Generation E-Mail Client 141
7393 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
7394 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7395 ers and will attempt to PGP/MIME decode the messages first.
7397 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7403 The separator to add between messages when piping a list of tagged messages to
7404 an external Unix command.
7406 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7412 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7413 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7414 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7415 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7416 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7417 (section 7.4.214 , page 140)'' separator is added after each message.
7419 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7427 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7428 fall back to other authentication methods if the previous methods are unavail-
7429 able. If a method is available but authentication fails, Mutt-ng will not con-
7430 nect to the POP server.
7432 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7440 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7441 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7442 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7443 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7445 The Mutt Next Generation E-Mail Client 142
7447 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7448 Mutt-ng will try all available methods, in order from most-secure to least-
7451 Example: set pop_authenticators='digest-md5:apop:user'
7453 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7461 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7462 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7463 load messages but also leave them on the POP server.
7465 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7473 The name of your POP server for the ``fetch-mail'' function. You can also
7474 specify an alternative port, username and password, i.e.:
7476 [pop[s]://][username[:password]@]popserver[:port]
7478 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7479 the superuser of your machine may read it regardless of the file's permissions.
7481 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7489 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7490 retrieving only unread messages from the POP server when using the ``fetch-
7493 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7501 The Mutt Next Generation E-Mail Client 143
7503 This variable configures how often (in seconds) POP should look for new mail.
7505 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7513 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7514 for your password when you open POP mailbox.
7516 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7517 the superuser of your machine may read it regardless of the file's permissions.
7519 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7527 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7530 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7538 Your login name on the POP server.
7540 This variable defaults to your user name on the local machine.
7542 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7548 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 93)'' variable, Mutt-ng
7549 will append this string after the inclusion of a message which is being replied
7552 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7558 The Mutt Next Generation E-Mail Client 144
7560 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7561 7.4.227 , page 143)'' mailbox when you elect not to send immediately.
7563 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7567 Default: '~/postponed'
7569 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.226 , page 143)
7570 sending a message'' which you are editing. When you choose to postpone a mes-
7571 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7572 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.226 , page 143)'' variable.
7574 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7580 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a connec-
7581 tion to the server. This is useful for setting up secure connections, e.g. with
7582 ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the
7585 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7586 /dev/null > /dev/null'
7588 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7590 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7591 machine without having to enter a password.
7593 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\bp_
\br_
\bi_
\bn_
\bt
7599 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7600 by default, because some people accidentally hit ``p'' often.
7602 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7608 This specifies the command pipe that should be used to print messages.
7610 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7614 The Mutt Next Generation E-Mail Client 145
7618 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7619 message is decoded before it is passed to the external command specified by
7620 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.230 , page 144). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7621 cessing will be applied to the message when printing it. The latter setting
7622 may be useful if you are using some advanced printer filter which is able to
7623 properly format e-mail messages for printing.
7625 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7631 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7632 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.230 , page 144) is executed
7633 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7634 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.230 , page 144) is executed
7635 only once, and all the messages are concatenated, with a form feed as the mes-
7638 Those who use the enscript(1) program's mail-printing mode will most likely
7639 want to set this option.
7641 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7647 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.179 , page 132)'', setting this
7648 variable will cause Mutt-ng to prompt you for a command when the pager exits
7649 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7650 index menu when the external pager exits.
7652 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7658 This specifies the command that Mutt-ng will use to make external address
7659 queries. The string should contain a %s, which will be substituted with the
7660 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 58)'' for more
7663 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\bq_
\bu_
\bi_
\bt
7669 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7671 The Mutt Next Generation E-Mail Client 146
7673 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7674 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
7677 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7683 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7684 tion 7.4.115 , page 115)''.
7686 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7692 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7693 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7694 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.115 , page 115)''.
7696 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7698 Type: regular expression
7700 Default: '^([ \t]*[|>:}#])+'
7702 A regular expression used in the internal-pager to determine quoted sections of
7703 text in the body of a message.
7705 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
7706 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7707 the beginning of quoted lines.
7709 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7715 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7716 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7717 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7718 reads message 25, and then again when it gets to message 50). This variable is
7719 meant to indicate progress when reading large mailboxes which may take some
7720 time. When set to 0, only a single message will appear before the reading the
7723 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.352 , page 174)'' variable.
7725 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7727 The Mutt Next Generation E-Mail Client 147
7733 If set, all folders are opened in read-only mode.
7735 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7741 This variable specifies what ``real'' or ``personal'' name should be used when
7744 By default, this is the GECOS field from /etc/passwd.
7746 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7747 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.80 , page 107) variable.
7749 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7755 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7756 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.227 , page 143)''.
7758 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7760 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7766 This specifies the file into which your outgoing messages should be appended.
7767 (This is meant as the primary method for saving a copy of your messages, but
7768 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37)'' com-
7769 mand to create a Bcc: header field with your email address in it.)
7771 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b7_
\b) is overridden by the
7772 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.74 , page 106)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7773 7.4.254 , page 150)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page
7776 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7778 Type: regular expression
7780 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7782 A regular expression used to recognize reply messages when threading and
7784 The Mutt Next Generation E-Mail Client 148
7786 replying. The default value corresponds to the English ``Re:'' and the German
7789 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7795 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7796 that you want to reply to the recipients of that message rather than to your-
7799 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7805 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7806 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7807 use the address in the ``From:'' header field instead.
7809 This option is useful for reading a mailing list that sets the ``Reply-To:''
7810 header field to the list address and you want to send a private message to the
7811 author of a message.
7813 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7819 When set, the cursor will be automatically advanced to the next (possibly
7820 undeleted) message whenever a command that modifies the current message is exe-
7823 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7829 This variable controls whether or not Mutt-ng will display the ``personal''
7830 name from your aliases in the index menu if it finds an alias that matches the
7831 message's sender. For example, if you have the following alias:
7833 alias juser abd30425@somewhere.net (Joe User)
7835 and then you receive mail which contains the following header:
7837 From: abd30425@somewhere.net
7839 It would be displayed in the index menu as ``Joe User'' instead of
7841 The Mutt Next Generation E-Mail Client 149
7843 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7844 not human friendly (like CompuServe addresses).
7846 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7852 It may sometimes arrive that you receive mail to a certain machine, move the
7853 messages to another machine, and reply to some the messages from there. If
7854 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7855 using the address where you received the messages you are replying to i
\bif
\bf that
7856 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7857 would be used doesn't match your alternates, the From: line will use your
7858 address on the current machine.
7860 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7866 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.249 ,
7867 page 148) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7868 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7869 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7870 (section 7.4.241 , page 146) variable.
7872 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7878 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7879 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7880 ments to files named like this:
7882 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7884 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7885 effect before you have changed folders.
7887 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7888 standard, but nevertheless encountered in the wild.
7890 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7891 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7892 encoding specified in RFC 2231.
7894 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7898 The Mutt Next Generation E-Mail Client 150
7902 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7903 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.254 , page 150)'' or
7904 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.74 , page 106)'' is _
\bs_
\be_
\bt too, the selection of the
7905 fcc folder will be changed as well.
7907 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7913 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7914 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.310 , page 163)'' which is
7915 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7917 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7918 and Maildir directories.
7920 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7926 This variable controls how copies of outgoing messages are saved. When set, a
7927 check is made to see if a mailbox specified by the recipient address exists
7928 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 ,
7929 page 104)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7930 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7931 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.243 , page 147)'' mailbox.
7933 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.74 , page 106)'' variable.
7935 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\bc_
\bo_
\br_
\be
7941 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7942 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
7943 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.256 , page 150)'' variable and friends are used.
7945 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7951 Messages which have been assigned a score equal to or lower than the value of
7952 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7953 scores are always greater than or equal to zero, the default setting of this
7955 The Mutt Next Generation E-Mail Client 151
7957 variable will never mark a message for deletion.
7959 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7965 Messages which have been assigned a score greater than or equal to this vari-
7966 able's value are automatically marked ``flagged''.
7968 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7974 Messages which have been assigned a score equal to or lower than the value of
7975 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7976 scores are always greater than or equal to zero, the default setting of this
7977 variable will never mark a message read.
7979 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7983 Default: 'us-ascii:iso-8859-1:utf-8'
7985 A list of character sets for outgoing messages. Mutt-ng will use the first
7986 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7987 (section 7.4.27 , page 95)'' is not iso-8859-1 and recipients may not under-
7988 stand UTF-8, it is advisable to include in the list an appropriate widely used
7989 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7990 instead of or after iso-8859-1.
7992 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7996 Default: '/usr/sbin/sendmail -oem -oi'
7998 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7999 Mutt-ng expects that the specified program interprets additional arguments as
8000 recipient addresses.
8002 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
8008 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.260 ,
8009 page 151)'' process to finish before giving up and putting delivery in the
8012 The Mutt Next Generation E-Mail Client 152
8014 Mutt-ng interprets the value of this variable as follows:
8017 number of seconds to wait for sendmail to finish before continuing
8020 wait forever for sendmail to finish
8023 always put sendmail in the background without waiting
8025 Note that if you specify a value other than 0, the output of the child process
8026 will be put in a temporary file. If there is some error, you will be informed
8027 as to where to find the output.
8029 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bh_
\be_
\bl_
\bl
8035 Command to use when spawning a subshell. By default, the user's login shell
8036 from /etc/passwd is used.
8038 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
8044 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
8045 7.4.267 , page 153) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
8046 split a folder name into ``hierarchy items.''
8048 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
8054 This specifies the delimiter between the sidebar (if visible) and other
8057 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
8063 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
8065 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8069 The Mutt Next Generation E-Mail Client 153
8071 Default: '%m%?n?(%n)?%?f?[%f]?'
8073 This variable controls how message counts are printed when the sidebar is
8074 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
8075 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
8076 mbox-style mailboxes.)
8078 The following printf(3)-like sequences are supported all of which may be
8082 Number of deleted messages. 1)
8085 Number of flagged messages.
8088 Total number of messages.
8091 Total number of messages shown, i.e. not hidden by a limit. 1)
8094 Number of new messages.
8097 Number of tagged messages. 1)
8099 1) These expandos only have a non-zero value for the current mailbox and will
8100 always be zero otherwise.
8102 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\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
8108 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
8109 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
8110 7.4.269 , page 153)'' is set to a too low value). For example, if the news-
8111 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
8112 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
8115 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
8116 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.263 , page 152) variable.
8118 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
8124 This specifies whether or not to show the sidebar (a list of folders specified
8126 The Mutt Next Generation E-Mail Client 154
8128 with the ``mailboxes'' command).
8130 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
8136 The width of the sidebar.
8138 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
8144 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
8145 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.272 , page 154)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
8146 that you not unset this variable unless your ``signature'' contains just your
8147 name. The reason for this is because many software packages use ``-- \n'' to
8148 detect your signature.
8150 For example, Mutt-ng has the ability to highlight the signature in a different
8151 color in the builtin pager.
8153 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8159 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
8160 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
8161 know what you are doing, and are prepared to take some heat from netiquette
8164 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
8168 Default: '~/.signature'
8170 Specifies the filename of your signature, which is appended to all outgoing
8171 messages. If the filename ends with a pipe (``|''), it is assumed that file-
8172 name is a shell command and input should be read from its stdout.
8174 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
8180 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
8181 people that want to sign off every message they send with their name.
8183 The Mutt Next Generation E-Mail Client 155
8185 If you want to insert your website's URL, additional contact information or
8186 witty quotes into your mails, better use a signature file instead of the sig-
8189 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8193 Default: '~f %s | ~s %s'
8195 Specifies how Mutt-ng should expand a simple search into a real search pattern.
8196 A simple search is one that does not contain any of the ~ operators. See
8197 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83)'' for more information on search patterns.
8199 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
8200 will automatically expand it to the value specified by this variable. For the
8201 default value it would be:
8205 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
8211 Specifies time, in seconds, to pause while displaying certain informational
8212 messages, while moving from folder to folder and after expunging messages from
8213 the current folder. The default is to pause one second, so a value of zero for
8214 this option suppresses the pause.
8216 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
8222 Controls the display of lines longer than the screen width in the internal
8223 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
8224 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.127 ,
8225 page 120)'' variable.
8227 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
8229 Type: regular expression
8231 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
8233 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
8234 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.238 , page 146)'', most notably smileys in the
8237 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
8239 The Mutt Next Generation E-Mail Client 156
8245 This flag controls whether you want to be asked to enter a label for a certifi-
8246 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
8249 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
8255 This variable contains the name of either a directory, or a file which contains
8256 trusted certificates for use with OpenSSL. (S/MIME only)
8258 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
8264 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
8265 and retrieval of keys by itself. This is very basic right now, and keys and
8266 certificates are stored 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 pairs, and which can be manually edited. This one points to the
8269 location of the certificates. (S/MIME only)
8271 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8277 This format string specifies a command which is used to decrypt application/x-
8278 pkcs7-mime attachments.
8280 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
8284 Expands to the name of a file containing a message.
8287 Expands to the name of a file containing the signature part of a
8288 multipart/signed attachment when verifying it.
8291 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.283 ,
8294 The Mutt Next Generation E-Mail Client 157
8297 One or more certificate IDs.
8300 The algorithm used for encryption.
8303 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
8304 7.4.279 , page 156) points to a directory or file, this expands to
8305 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.279 , page 156)' or
8306 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.279 , page 156)'.
8308 For examples on how to configure these formats, see the smime.rc in the sam-
8309 ples/ subdirectory which has been installed on your system alongside the docu-
8310 mentation. (S/MIME only)
8312 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\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
8318 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
8319 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8320 mailbox-address to determine the key to use. It will ask you to supply a key,
8321 if it can't find one. (S/MIME only)
8323 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8329 This is the default key-pair to use for signing. This must be set to the keyid
8330 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8332 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8338 This command is used to create encrypted S/MIME messages. (S/MIME only)
8340 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8346 This sets the algorithm that should be used for encryption. Valid choices are
8347 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8349 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8351 The Mutt Next Generation E-Mail Client 158
8353 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8359 This command is used to extract X509 certificates from a PKCS7 structure.
8362 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\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
8368 This command is used to extract the mail address(es) used for storing X509 cer-
8369 tificates, and for verification purposes (to check whether the certificate was
8370 issued for the sender's mailbox). (S/MIME only)
8372 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\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
8378 This command is used to extract only the signers X509 certificate from a S/MIME
8379 signature, so that the certificate's owner may get compared to the email's
8380 ``From:'' header field. (S/MIME only)
8382 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\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
8388 This command is used to import a certificate via smime_keysng. (S/MIME only)
8390 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8396 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8397 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8399 However, this has no effect while replying, since Mutt-ng will automatically
8400 select the same application that was used to sign/encrypt the original message.
8402 (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-
8403 tion 7.4.40 , page 98).) (S/MIME only)
8405 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8407 The Mutt Next Generation E-Mail Client 159
8413 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8414 retrieval of keys/certs by itself. This is very basic right now, and stores
8415 keys and certificates in two different directories, both named as the hash-
8416 value retrieved from OpenSSL. There is an index file which contains mailbox-
8417 address keyid pair, and which can be manually edited. This one points to the
8418 location of the private keys. (S/MIME only)
8420 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8426 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8427 to extract the public X509 certificate(s). (S/MIME only)
8429 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8435 This command is used to created S/MIME signatures of type multipart/signed,
8436 which can be read by all mail clients. (S/MIME only)
8438 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\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
8444 This command is used to created S/MIME signatures of type application/x-
8445 pkcs7-signature, which can only be handled by mail clients supporting the
8446 S/MIME extension. (S/MIME only)
8448 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8454 The number of seconds after which a cached passphrase will expire if not used.
8457 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8463 The Mutt Next Generation E-Mail Client 160
8465 This command is used to verify S/MIME signatures of type multipart/signed.
8468 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\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
8474 This command is used to verify S/MIME signatures of type application/x-
8475 pkcs7-mime. (S/MIME only)
8477 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8485 If this variable is non-empty, it'll be used as the envelope sender. If it's
8486 empty (the default), the value of the regular From: header will be used.
8488 This may be necessary as some providers don't allow for arbitrary values as the
8489 envelope sender but only a particular one which may not be the same as the
8490 user's desired From: header.
8492 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8500 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8501 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8502 _
\bm_
\ba_
\bi_
\bl (section 7.4.260 , page 151)'', and any associated variables.
8504 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8512 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8513 7.4.303 , page 161)'' is set, but this variable is not, you will be prompted
8514 for a password when sending.
8516 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8517 the superuser of your machine may read it regardless of the file's permissions.
8519 The Mutt Next Generation E-Mail Client 161
8521 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8529 Defines the port that the SMTP host is listening on for mail delivery. Must be
8530 specified as a number.
8532 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8533 will probably desire 587, the mail submission port.
8535 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8541 Availability: SMTP (and SSL)
8543 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8544 server does not support STARTTLS or there is an error in the TLS Handshake, the
8545 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8546 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8547 port enabled in order to use it.
8549 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8557 Defines the username to use with SMTP AUTH. Setting this variable will cause
8558 Mutt-ng to attempt to use SMTP AUTH when sending.
8560 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bo_
\br_
\bt
8566 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8568 The Mutt Next Generation E-Mail Client 162
8573 mailbox-order (unsorted)
8581 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8582 (example: set sort=reverse-date-sent).
8584 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8590 Specifies how the entries in the ``alias'' menu are sorted. The following are
8593 address (sort alphabetically by email address)
8594 alias (sort alphabetically by alias name)
8595 unsorted (leave in order specified in .muttrc)
8597 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8603 When sorting by threads, this variable controls how threads are sorted in rela-
8604 tion to other threads, and how the branches of the thread trees are sorted.
8605 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.304 , page 161)'' can,
8606 except threads (in that case, Mutt-ng will just use date-sent). You can also
8607 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8608 come after reverse-. The last- prefix causes messages to be sorted against its
8609 siblings by which has the last descendant, using the rest of sort_aux as an
8612 For instance, set sort_aux=last-date-received would mean that if a new message
8613 is received in a thread, that thread becomes the last one displayed (or the
8614 first, if you have set sort=reverse-threads.)
8616 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.304 , page 161)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8617 (section 7.4.306 , page 162) is reversed again (which is not the right thing
8618 to do, but kept to not break any existing configuration setting).
8620 The Mutt Next Generation E-Mail Client 163
8622 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8628 Specifies how to sort entries in the file browser. By default, the entries are
8629 sorted alphabetically. Valid values:
8631 alpha (alphabetically)
8636 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8637 (example: set sort_browser=reverse-date).
8639 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8645 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
8646 (section 7.4.325 , page 168)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8647 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.308 ,
8648 page 163) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8649 sage by subject if the subject of the child message starts with a substring
8650 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.244 , page 147)''. With
8651 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.308 , page 163) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8652 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
8653 7.4.244 , page 147)'' parts of both messages are identical.
8655 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8661 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.309 , page 163)'' controls what happens when
8662 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8663 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8664 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.309 ,
8665 page 163)'' as a separator.
8667 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8673 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8675 The Mutt Next Generation E-Mail Client 164
8677 you can specify its location with this variable. Mutt-ng will automatically
8678 set this variable to the value of the environment variable $MAIL if it is not
8681 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8687 This variable specifies a file containing trusted CA certificates. Any server
8688 certificate that is signed with one of these CA certificates are also automati-
8691 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8693 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8701 The file containing a client certificate and its associated private key.
8703 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8709 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8710 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8711 server does not advertise the capability, since it would otherwise have to
8712 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8713 7.4.315 , page 164)''.
8715 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8721 Availability: GNUTLS
8723 This variable specifies the minimum acceptable prime size (in bits) for use in
8724 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8727 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8731 The Mutt Next Generation E-Mail Client 165
8735 Availability: SSL or GNUTLS
8737 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8738 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8739 regardless of the server's capabilities.
8741 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8749 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8752 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8758 Availability: SSL or GNUTLS
8760 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8763 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8769 Availability: SSL or GNUTLS
8771 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8774 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8782 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8783 store when checking if server certificate is signed by a trusted CA.
8785 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8787 The Mutt Next Generation E-Mail Client 166
8793 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8794 tion 7.4.321 , page 165)''. The first character is used when the mailbox is
8795 unchanged. The second is used when the mailbox has been changed, and it needs
8796 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8797 if the mailbox will not be written when exiting that mailbox (You can toggle
8798 whether to write changes to a mailbox with the toggle-write operation, bound by
8799 default to ``%''). The fourth is used to indicate that the current folder has
8800 been opened in attach-message mode (Certain operations like composing a new
8801 mail, replying, forwarding, etc. are not permitted in this mode).
8803 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8807 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8808 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8809 %l?]---(%s/%S)-%>-(%P)---'
8811 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8812 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 115)'', but has
8813 its own set of printf(3)-like sequences:
8816 number of mailboxes with new mail *
8819 the short pathname of the current mailbox
8822 number of deleted messages *
8825 the full pathname of the current mailbox
8828 number of flagged messages *
8834 size (in bytes) of the current mailbox *
8837 size (in bytes) of the messages shown (i.e., which match the cur-
8841 the number of messages in the mailbox *
8843 The Mutt Next Generation E-Mail Client 167
8846 the number of messages shown (i.e., which match the current limit)
8850 number of new messages in the mailbox *
8853 number of old unread messages *
8856 number of postponed messages *
8859 percentage of the way through the index
8862 modified/read-only/won't-write/attach-message indicator, according
8863 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.320 , page 165)
8866 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.304 , page 161))
8869 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.306 , page
8873 number of tagged messages *
8876 number of unread messages *
8879 Mutt-ng version string
8882 currently active limit pattern, if any *
8885 right justify the rest of the string and pad with 'X'
8888 pad to the end of the line with 'X'
8890 * = can be optionally printed if nonzero
8892 Some of the above sequences can be used to optionally print a string if their
8893 value is nonzero. For example, you may only want to see the number of flagged
8894 messages if such messages exist, since zero is not particularly meaningful. To
8895 optionally print a string based upon one of the above sequences, the following
8898 %?<sequence_char>?<optional_string>?
8900 The Mutt Next Generation E-Mail Client 168
8902 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
8903 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
8904 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8907 Here is an example illustrating how to optionally print the number of new mes-
8910 %?n?%n new messages.?
8912 Additionally you can switch between two strings, the first one, if a value is
8913 zero, the second one, if the value is nonzero, by using the following con-
8916 %?<sequence_char>?<if_string>&<else_string>?
8918 You can additionally force the result of any printf(3)-like sequence to be low-
8919 ercase by prefixing the sequence character with an underscore (_) sign. For
8920 example, if you want to display the local hostname in lowercase, you would use:
8924 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8925 replace any dots in the expansion by underscores. This might be helpful with
8926 IMAP folders that don't like dots in folder names.
8928 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8934 Setting this variable causes the ``status bar'' to be displayed on the first
8935 line of the screen rather than near the bottom.
8937 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8943 With mailto: style links, a body as well as arbitrary header information may be
8944 embedded. This may lead to (user) headers being overwriten without note if
8945 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'' is unset.
8947 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8948 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8949 message including headers will be shown in the editor regardless of what
8950 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'' is set to.
8952 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8956 The Mutt Next Generation E-Mail Client 169
8960 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8961 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8962 messages are often generated by old mailers or buggy mailers like MS Outlook
8963 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.13 , page 91).
8965 This option also replaces linear-white-space between encoded-word and *text to
8966 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8967 from being devided into multiple lines.
8969 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8975 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8976 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.304 , page 161)'' by mes-
8977 sage threads. By default, messages with the same subject are grouped together
8978 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8979 mailbox where you might have several unrelated messages with the subject ``hi''
8980 which will get grouped together.
8982 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8988 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8989 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.327 , page 169) when replying. This is
8990 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8993 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8995 Type: regular expression
8997 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8999 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.326 , page 169) is _
\bs_
\be_
\bt, mutt-ng
9000 will remove this trailing part of the ``Subject'' line when replying if it
9001 won't be empty afterwards.
9003 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
9009 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
9010 i.e. a space will be inserted between the quote characters and the actual text.
9012 The Mutt Next Generation E-Mail Client 170
9014 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
9020 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
9021 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
9022 mand like ``xterm -e muttng.''
9024 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
9030 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
9031 format is easier to handle for some mailing software, and generally just looks
9032 like ordinary text. To actually make use of this format's features, you'll
9033 need support in your editor.
9035 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.115 , page 115) is ignored when this
9038 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9044 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
9045 tion 7.2 , page 83)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
9046 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
9047 as they appear in the folder.
9049 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
9055 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
9056 messages by subject.
9058 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bt_
\bi_
\bl_
\bd_
\be
9064 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
9067 The Mutt Next Generation E-Mail Client 171
9069 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
9075 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
9076 pressed in the main menu before timing out and checking for new mail. A value
9077 of zero or less will cause Mutt-ng to never time out.
9079 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
9085 This variable allows you to specify where Mutt-ng will place its temporary
9086 files needed for displaying and composing messages. If this variable is not
9087 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
9090 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
9096 Controls the character used to indicate mail addressed to you. The first char-
9097 acter is the one used when the mail is NOT addressed to your address (default:
9098 space). The second is used when you are the only recipient of the message
9099 (default: +). The third is when your address appears in the ``To:'' header
9100 field, but you are not the only recipient of the message (default: T). The
9101 fourth character is used when your address is specified in the ``Cc:'' header
9102 field, but you are not the only recipient. The fifth character is used to
9103 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
9104 when a mail was sent to a mailing-list you're subscribe to (default: L).
9106 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bt_
\br_
\ba_
\bs_
\bh
9112 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
9113 marked for deletion will be moved, instead of being irremediably purged.
9115 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
9116 that there is no way to recover mail.
9118 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
9124 The Mutt Next Generation E-Mail Client 172
9126 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
9127 a raw socket. You may be able to use this to set up preauthenticated connec-
9128 tions to your IMAP/POP3 server. Example:
9130 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
9132 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
9133 without having to enter a password.
9135 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bu_
\bm_
\ba_
\bs_
\bk
9141 This sets the umask that will be used by Mutt-ng when creating all kinds of
9142 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
9144 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
9150 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
9151 rent thread is _
\bu_
\bncollapsed.
9153 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
9159 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
9160 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
9161 with the SMTP support via libESMTP. Otherwise you may not be able to send
9164 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.260 , page
9165 151)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
9166 negotiation or tell libESMTP to do so.
9168 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
9174 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
9175 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.95 , page 110)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
9176 no addresses will be qualified.
9178 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
9180 The Mutt Next Generation E-Mail Client 173
9186 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
9187 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
9188 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37)'' command.
9190 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
9198 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
9200 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
9203 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
9209 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
9210 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
9211 mally, the default should work.
9213 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b6 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
9219 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
9222 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b7 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
9228 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-
9229 _
\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.
9231 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
9232 78)'', provided that the corresponding mailcap entry has a needsterminal flag,
9233 and the external program is interactive.
9235 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
9237 The Mutt Next Generation E-Mail Client 174
9239 a key only if the external command returned a non-zero status.
9241 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b8 _
\bw_
\be_
\be_
\bd
9247 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
9248 replying to messages.
9250 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b9 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9256 Controls whether searches wrap around the end of the mailbox.
9258 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
9259 searches will not wrap.
9261 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b0 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
9267 Controls the size of the margin remaining at the right side of the terminal
9268 when Mutt-ng's pager does smart wrapping.
9270 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b1 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
9276 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
9277 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
9279 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b2 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
9285 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
9286 indicate progress. If set to 0, only a single message will be displayed before
9289 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.239 , page 146)'' variable.
9291 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b3 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
9293 The Mutt Next Generation E-Mail Client 175
9297 Default: 'M%?n?AIL&ail?'
9299 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-
9300 tion 7.4.355 , page 175) is _
\bs_
\be_
\bt. This string is identical in formatting to the
9301 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.321 , page 165)''.
9303 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b4 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
9309 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.355 , page 175) is _
\bs_
\be_
\bt, this string will be
9310 used to set the title when leaving mutt-ng. For terminal-based programs,
9311 there's no easy and portable way to read the current title so mutt-ng cannot
9312 read it upon startup and restore it when exiting.
9314 Based on the xterm FAQ, the following might work:
9316 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9319 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b5 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9325 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9326 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9329 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b6 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9333 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9335 Controls the format of the title bar of the xterm provided that
9336 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.355 , page 175) has been _
\bs_
\be_
\bt. This string is
9337 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.321 ,
9340 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9342 The following is the list of available functions listed by the mapping in which
9343 they are available. The default key setting is given, and an explanation of
9344 what the function does. The key bindings of these functions can be changed
9345 with the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 27) command.
9347 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9349 The Mutt Next Generation E-Mail Client 176
9351 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9352 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9353 tings for this menu will affect the default bindings for all menus (except as
9356 bottom-page L move to the bottom of the page
9357 current-bottom not bound move current entry to bottom of page
9358 current-middle not bound move current entry to middle of page
9359 current-top not bound move current entry to top of page
9360 enter-command : enter a muttngrc command
9361 exit q exit this menu
9362 first-entry = move to the first entry
9363 half-down ] scroll down 1/2 page
9364 half-up [ scroll up 1/2 page
9366 jump number jump to an index number
9367 last-entry * move to the last entry
9368 middle-page M move to the middle of the page
9369 next-entry j move to the next entry
9370 next-line > scroll down one line
9371 next-page z move to the next page
9372 previous-entry k move to the previous entry
9373 previous-line < scroll up one line
9374 previous-page Z move to the previous page
9375 refresh ^L clear and redraw the screen
9376 search / search for a regular expression
9377 search-next n search for next match
9378 search-opposite not bound search for next match in opposite direction
9379 search-reverse ESC / search backwards for a regular expression
9380 select-entry RET select the current entry
9381 shell-escape ! run a program in a subshell
9382 tag-entry t toggle the tag on the current entry
9383 tag-prefix ; apply next command to tagged entries
9384 tag-prefix-cond not bound apply next function ONLY to tagged messages
9385 top-page H move to the top of the page
9386 what-key not bound display the keycode for a key press
9388 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9390 The Mutt Next Generation E-Mail Client 177
9392 bounce-message b remail a message to another user
9393 change-folder c open a different folder
9394 change-folder-readonly ESC c open a different folder in read only mode
9395 check-traditional-pgp ESC P check for classic pgp
9396 clear-flag W clear a status flag from a message
9397 copy-message C copy a message to a file/mailbox
9398 create-alias a create an alias from a message sender
9399 decode-copy ESC C decode a message and copy it to a file/mailbox
9400 decode-save ESC s decode a message and save it to a file/mailbox
9401 delete-message d delete the current entry
9402 delete-pattern D delete messages matching a pattern
9403 delete-subthread ESC d delete all messages in subthread
9404 delete-thread ^D delete all messages in thread
9405 display-address @ display full address of sender
9406 display-toggle-weed h display message and toggle header weeding
9407 display-message RET display a message
9408 edit e edit the current message
9409 edit-type ^E edit the current message's Content-Type
9410 exit x exit without saving changes
9411 extract-keys ^K extract PGP public keys
9412 fetch-mail G retrieve mail from POP server
9413 flag-message F toggle a message's 'important' flag
9414 forget-passphrase ^F wipe PGP passphrase from memory
9415 forward-message f forward a message with comments
9416 group-reply g reply to all recipients
9417 limit l show only messages matching a pattern
9418 list-reply L reply to specified mailing list
9419 mail m compose a new mail message
9420 mail-key ESC k mail a PGP public key
9421 next-new TAB jump to the next new message
9422 next-subthread ESC n jump to the next subthread
9423 next-thread ^N jump to the next thread
9424 next-undeleted j move to the next undeleted message
9425 next-unread not bound jump to the next unread message
9426 parent-message P jump to parent message in thread
9427 pipe-message | pipe message/attachment to a shell command
9428 previous-new ESC TAB jump to the previous new message
9429 previous-page Z move to the previous page
9430 previous-subthread ESC p jump to previous subthread
9431 previous-thread ^P jump to previous thread
9432 previous-undeleted k move to the last undelete message
9433 previous-unread not bound jump to the previous unread message
9434 print-message p print the current entry
9435 query Q query external program for addresses
9436 quit q save changes to mailbox and quit
9437 read-subthread ESC r mark the current subthread as read
9438 read-thread ^R mark the current thread as read
9439 recall-message R recall a postponed message
9440 reply r reply to a message
9441 resend-message ESC e resend message and preserve MIME structure
9442 save-message s save message/attachment to a file
9443 set-flag w set a status flag on a message
9444 show-version V show the Mutt-ng version number and date
9445 show-limit ESC l show currently active limit pattern, if any
9447 The Mutt Next Generation E-Mail Client 178
9449 sort-mailbox o sort messages
9450 sort-reverse O sort messages in reverse order
9451 sync-mailbox $ save changes to mailbox
9452 tag-pattern T tag messages matching a pattern
9453 tag-thread ESC t tag/untag all messages in the current thread
9454 toggle-new N toggle a message's 'new' flag
9455 toggle-write % toggle whether the mailbox will be rewritten
9456 undelete-message u undelete the current entry
9457 undelete-pattern U undelete messages matching a pattern
9458 undelete-subthread ESC u undelete all messages in subthread
9459 undelete-thread ^U undelete all messages in thread
9460 untag-pattern ^T untag messages matching a pattern
9461 view-attachments v show MIME attachments
9463 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9465 The Mutt Next Generation E-Mail Client 179
9467 bottom not bound jump to the bottom of the message
9468 bounce-message b remail a message to another user
9469 change-folder c open a different folder
9470 change-folder-readonly ESC c open a different folder in read only mode
9471 check-traditional-pgp ESC P check for classic pgp
9472 copy-message C copy a message to a file/mailbox
9473 create-alias a create an alias from a message sender
9474 decode-copy ESC C decode a message and copy it to a file/mailbox
9475 decode-save ESC s decode a message and save it to a file/mailbox
9476 delete-message d delete the current entry
9477 delete-subthread ESC d delete all messages in subthread
9478 delete-thread ^D delete all messages in thread
9479 display-address @ display full address of sender
9480 display-toggle-weed h display message and toggle header weeding
9481 edit e edit the current message
9482 edit-type ^E edit the current message's Content-Type
9483 enter-command : enter a muttngrc command
9484 exit i return to the main-menu
9485 extract-keys ^K extract PGP public keys
9486 flag-message F toggle a message's 'important' flag
9487 forget-passphrase ^F wipe PGP passphrase from memory
9488 forward-message f forward a message with comments
9489 group-reply g reply to all recipients
9490 half-up not bound move up one-half page
9491 half-down not bound move down one-half page
9493 list-reply L reply to specified mailing list
9494 mail m compose a new mail message
9495 mail-key ESC k mail a PGP public key
9496 mark-as-new N toggle a message's 'new' flag
9497 next-line RET scroll down one line
9498 next-entry J move to the next entry
9499 next-new TAB jump to the next new message
9500 next-page move to the next page
9501 next-subthread ESC n jump to the next subthread
9502 next-thread ^N jump to the next thread
9503 next-undeleted j move to the next undeleted message
9504 next-unread not bound jump to the next unread message
9505 parent-message P jump to parent message in thread
9506 pipe-message | pipe message/attachment to a shell command
9507 previous-line BackSpace scroll up one line
9508 previous-entry K move to the previous entry
9509 previous-new not bound jump to the previous new message
9510 previous-page - move to the previous page
9511 previous-subthread ESC p jump to previous subthread
9512 previous-thread ^P jump to previous thread
9513 previous-undeleted k move to the last undelete message
9514 previous-unread not bound jump to the previous unread message
9515 print-message p print the current entry
9516 quit Q save changes to mailbox and quit
9517 read-subthread ESC r mark the current subthread as read
9518 read-thread ^R mark the current thread as read
9519 recall-message R recall a postponed message
9520 redraw-screen ^L clear and redraw the screen
9522 The Mutt Next Generation E-Mail Client 180
9524 reply r reply to a message
9525 save-message s save message/attachment to a file
9526 search / search for a regular expression
9527 search-next n search for next match
9528 search-opposite not bound search for next match in opposite direction
9529 search-reverse ESC / search backwards for a regular expression
9530 search-toggle \ toggle search pattern coloring
9531 shell-escape ! invoke a command in a subshell
9532 show-version V show the Mutt-ng version number and date
9533 skip-quoted S skip beyond quoted text
9534 sync-mailbox $ save changes to mailbox
9535 tag-message t tag a message
9536 toggle-quoted T toggle display of quoted text
9537 top ^ jump to the top of the message
9538 undelete-message u undelete the current entry
9539 undelete-subthread ESC u undelete all messages in subthread
9540 undelete-thread ^U undelete all messages in thread
9541 view-attachments v show MIME attachments
9543 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9545 search / search for a regular expression
9546 search-next n search for next match
9547 search-reverse ESC / search backwards for a regular expression
9549 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9551 create-alias a create an alias from a message sender
9552 mail m compose a new mail message
9553 query Q query external program for addresses
9554 query-append A append new query results to current results
9555 search / search for a regular expression
9556 search-next n search for next match
9557 search-opposite not bound search for next match in opposite direction
9558 search-reverse ESC / search backwards for a regular expression
9560 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9562 The Mutt Next Generation E-Mail Client 181
9564 bounce-message b remail a message to another user
9565 collapse-parts v toggle display of subparts
9566 delete-entry d delete the current entry
9567 display-toggle-weed h display message and toggle header weeding
9568 edit-type ^E edit the current entry's Content-Type
9569 extract-keys ^K extract PGP public keys
9570 forward-message f forward a message with comments
9571 group-reply g reply to all recipients
9572 list-reply L reply to specified mailing list
9573 pipe-entry | pipe message/attachment to a shell command
9574 print-entry p print the current entry
9575 reply r reply to a message
9576 resend-message ESC e resend message and preserve MIME structure
9577 save-entry s save message/attachment to a file
9578 undelete-entry u undelete the current entry
9579 view-attach RET view attachment using mailcap entry if necessary
9580 view-mailcap m force viewing of attachment using mailcap
9581 view-text T view attachment as text
9583 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9585 The Mutt Next Generation E-Mail Client 182
9587 attach-file a attach a file(s) to this message
9588 attach-message A attach message(s) to this message
9589 attach-key ESC k attach a PGP public key
9590 copy-file C save message/attachment to a file
9591 detach-file D delete the current entry
9592 display-toggle-weed h display message and toggle header weeding
9593 edit-bcc b edit the BCC list
9594 edit-cc c edit the CC list
9595 edit-description d edit attachment description
9596 edit-encoding ^E edit attachment transfer-encoding
9597 edit-fcc f enter a file to save a copy of this message in
9598 edit-from ESC f edit the from: field
9599 edit-file ^X e edit the file to be attached
9600 edit-headers E edit the message with headers
9601 edit e edit the message
9602 edit-mime m edit attachment using mailcap entry
9603 edit-reply-to r edit the Reply-To field
9604 edit-subject s edit the subject of this message
9605 edit-to t edit the TO list
9606 edit-type ^T edit attachment type
9607 filter-entry F filter attachment through a shell command
9608 forget-passphrase ^F wipe PGP passphrase from memory
9609 ispell i run ispell on the message
9610 new-mime n compose new attachment using mailcap entry
9611 pgp-menu p show PGP options
9612 pipe-entry | pipe message/attachment to a shell command
9613 postpone-message P save this message to send later
9614 print-entry l print the current entry
9615 rename-file R rename/move an attached file
9616 send-message y send the message
9617 toggle-unlink u toggle whether to delete file after sending it
9618 view-attach RET view attachment using mailcap entry if necessary
9619 write-fcc w write the message to a folder
9621 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9623 delete-entry d delete the current entry
9624 undelete-entry u undelete the current entry
9626 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9628 The Mutt Next Generation E-Mail Client 183
9630 change-dir c change directories
9631 check-new TAB check mailboxes for new mail
9632 enter-mask m enter a file mask
9633 search / search for a regular expression
9634 search-next n search for next match
9635 search-reverse ESC / search backwards for a regular expression
9636 select-new N select a new file in this directory
9637 sort o sort messages
9638 sort-reverse O sort messages in reverse order
9639 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9640 view-file SPACE view file
9641 subscribe s subscribe to current mailbox (IMAP Only)
9642 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9643 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9645 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9647 view-name % view the key's user id
9648 verify-key c verify a PGP public key
9650 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9652 backspace BackSpace delete the char in front of the cursor
9653 backward-char ^B move the cursor one character to the left
9654 backward-word ESC b move the cursor to the previous word
9655 bol ^A jump to the beginning of the line
9656 buffy-cycle Space cycle among incoming mailboxes
9657 capitalize-word ESC c uppercase the first character in the word
9658 complete TAB complete filename or alias
9659 complete-query ^T complete address with query
9660 delete-char ^D delete the char under the cursor
9661 downcase-word ESC l lowercase all characters in current word
9662 eol ^E jump to the end of the line
9663 forward-char ^F move the cursor one character to the right
9664 forward-word ESC f move the cursor to the next word
9665 history-down not bound scroll down through the history list
9666 history-up not bound scroll up through the history list
9667 kill-eol ^K delete chars from cursor to end of line
9668 kill-eow ESC d delete chars from cursor to end of word
9669 kill-line ^U delete all chars on the line
9670 kill-word ^W delete the word in front of the cursor
9671 quote-char ^V quote the next typed key
9672 transpose-chars not bound transpose character under cursor with previous
9673 upcase-word ESC u uppercase all characters in current word
9675 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9677 The Mutt Next Generation E-Mail Client 184
9679 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9681 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9682 back in the ELM-ME days.
9684 The following people have been very helpful to the development of Mutt:
9686 Vikas Agnihotri <vikasa@writeme.com>,
9688 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9690 Aric Blumer <aric@fore.com>,
9692 John Capo <jc@irbs.com>,
9694 David Champion <dgc@uchicago.edu,
9696 Brendan Cully <brendan@kublai.com>,
9698 Liviu Daia <daia@stoilow.imar.ro>,
9700 Thomas E. Dickey <dickey@herndon4.his.com>,
9702 David DeSimone <fox@convex.hp.com>,
9704 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9706 Ruslan Ermilov <ru@freebsd.org>,
9708 Edmund Grimley Evans <edmundo@rano.org,
9710 Michael Finken <finken@conware.de>,
9712 Sven Guckes <guckes@math.fu-berlin.de>,
9714 Lars Hecking <lhecking@nmrc.ie>,
9716 Mark Holloman <holloman@nando.net>,
9718 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9720 Marco d'Itri <md@linux.it>,
9722 Bjrn Jacke <bjacke@suse.com>,
9724 Byrial Jensen <byrial@image.dk>,
9726 David Jeske <jeske@igcom.net>,
9728 Christophe Kalt <kalt@hugo.int-evry.fr>,
9730 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9732 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9734 The Mutt Next Generation E-Mail Client 185
9736 Brandon Long <blong@fiction.net>,
9738 Jimmy Mkel <jmy@flashback.net>,
9740 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9742 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9744 Andrew W. Nosenko <awn@bcs.zp.ua>,
9746 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9748 Clint Olsen <olsenc@ichips.intel.com>,
9750 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9752 Thomas Parmelan <tom@ankh.fr.eu.org>,
9754 Ollivier Robert <roberto@keltia.freenix.fr>,
9756 Thomas Roessler <roessler@does-not-exist.org>,
9758 Roland Rosenfeld <roland@spinnaker.de>,
9760 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9762 Allain Thivillon <Allain.Thivillon@alma.fr>,
9764 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9766 Vsevolod Volkov <vvv@lucky.net>,
9768 Ken Weinert <kenw@ihs.com>
9770 Mutt-ng is developed by the following people:
9772 Andreas Krennmair <ak@synflood.at>
9774 Nico Golde <nico@ngolde.de>
9776 Rocco Rutte <pdmef@cs.tu-berlin.de>
9778 The following people have been very helpful to the development of Mutt-ng:
9780 Christian Gall <cg@cgall.de>
9782 Iain Lea <iain@bricbrac.de>
9784 Andreas Kneib <akneib@gmx.net>
9786 Carsten Schoelzki <cjs@weisshuhn.de>
9788 Elimar Riesebieter <riesebie@lxtec.de>
9790 The Mutt Next Generation E-Mail Client 186
9792 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9794 This document was written in SGML, and then rendered using the sgml-tools pack-
9797 The Mutt Next Generation E-Mail Client 187
9801 1. Introduction .......................................................... 1
9802 1.1 Overview ........................................................ 1
9803 1.2 Mutt-ng Home Page ............................................... 1
9804 1.3 Mailing Lists ................................................... 1
9805 1.4 Software Distribution Sites ..................................... 2
9806 1.5 IRC ............................................................. 2
9807 1.6 Weblog .......................................................... 2
9808 1.7 Copyright ....................................................... 2
9810 2. Getting Started ..................................................... 2
9811 2.1 Basic Concepts .............................................. 2
9812 2.1.1 Screens and Menus 3
9813 2.1.2 Configuration 3
9816 2.1.5 Modularization 4
9818 2.2 Screens and Menus ........................................... 4
9821 2.2.3 File Browser 5
9824 2.2.6 Compose Menu 6
9826 2.2.8 Attachment Menu 6
9828 2.3 Moving Around in Menus .......................................... 6
9829 2.4 Editing Input Fields ............................................ 7
9830 2.5 Reading Mail - The Index and Pager .............................. 8
9831 2.5.1 The Message Index 8
9833 2.5.3 Threaded Mode 11
9834 2.5.4 Miscellaneous Functions 11
9835 2.6 Sending Mail ................................................... 14
9836 2.6.1 Composing new messages 14
9838 2.6.3 Editing the message header 17
9839 2.6.4 Using Mutt-ng with PGP 18
9840 2.6.5 Sending anonymous messages via mixmaster 19
9841 2.7 Forwarding and Bouncing Mail ................................... 19
9842 2.8 Postponing Mail ................................................ 20
9844 3. Configuration ........................................................ 21
9845 3.1 Locations of Configuration Files ............................... 21
9846 3.2 Basic Syntax of Initialization Files ........................... 21
9847 3.3 Expansion within variables ................................... 23
9848 3.3.1 Commands' Output 23
9849 3.3.2 Environment Variables 23
9853 3.3.3 Configuration Variables 23
9854 3.3.4 Self-Defined Variables 24
9855 3.3.5 Pre-Defined Variables 25
9856 3.3.6 Type Conversions 25
9857 3.4 Defining/Using aliases ......................................... 26
9858 3.5 Changing the default key bindings .............................. 27
9859 3.6 Defining aliases for character sets ........................... 29
9860 3.7 Setting variables based upon mailbox ........................... 29
9861 3.8 Keyboard macros ................................................ 29
9862 3.9 Using color and mono video attributes .......................... 30
9863 3.10 Ignoring (weeding) unwanted message headers .................... 32
9864 3.11 Alternative addresses .......................................... 33
9865 3.12 Format = Flowed .............................................. 34
9866 3.12.1 Introduction 34
9867 3.12.2 Receiving: Display Setup 34
9869 3.12.4 Additional Notes 35
9870 3.13 Mailing lists .................................................. 36
9871 3.14 Using Multiple spool mailboxes ................................. 37
9872 3.15 Defining mailboxes which receive mail .......................... 37
9873 3.16 User defined headers ........................................... 37
9874 3.17 Defining the order of headers when viewing messages ............ 38
9875 3.18 Specify default save filename .................................. 38
9876 3.19 Specify default Fcc: mailbox when composing .................... 39
9877 3.20 Specify default save filename and default Fcc: mailbox at once . 39
9878 3.21 Change settings based upon message recipients .................. 39
9879 3.22 Change settings before formatting a message .................... 40
9880 3.23 Choosing the cryptographic key of the recipient ................ 41
9881 3.24 Adding key sequences to the keyboard buffer .................... 41
9882 3.25 Executing functions ............................................ 41
9883 3.26 Message Scoring ................................................ 41
9884 3.27 Spam detection ................................................. 43
9885 3.28 Setting variables .............................................. 44
9886 3.29 Reading initialization commands from another file .............. 45
9887 3.30 Removing hooks ................................................. 46
9888 3.31 Sharing Setups ............................................. 46
9889 3.31.1 Character Sets 46
9890 3.31.2 Modularization 46
9891 3.31.3 Conditional parts 46
9892 3.32 Obsolete Variables ............................................. 48
9894 4. Advanced Usage ....................................................... 48
9895 4.1 Regular Expressions ............................................ 48
9896 4.2 Patterns ....................................................... 51
9897 4.2.1 Complex Patterns 52
9898 4.2.2 Patterns and Dates 52
9899 4.3 Format Strings ............................................. 53
9900 4.3.1 Introduction 53
9901 4.3.2 Conditional Expansion 54
9902 4.3.3 Modifications and Padding 55
9903 4.4 Using Tags ..................................................... 56
9904 4.5 Using Hooks .................................................... 56
9905 4.5.1 Message Matching in Hooks 57
9909 4.6 Using the sidebar .............................................. 58
9910 4.7 External Address Queries ....................................... 59
9911 4.8 Mailbox Formats ................................................ 59
9912 4.9 Mailbox Shortcuts .............................................. 60
9913 4.10 Handling Mailing Lists ......................................... 60
9914 4.11 Editing threads ................................................ 62
9915 4.11.1 Linking threads 62
9916 4.11.2 Breaking threads 62
9917 4.12 Delivery Status Notification (DSN) Support ..................... 62
9918 4.13 POP3 Support (OPTIONAL) ........................................ 63
9919 4.14 IMAP Support (OPTIONAL) ........................................ 64
9920 4.14.1 The Folder Browser 64
9921 4.14.2 Authentication 65
9922 4.15 NNTP Support (OPTIONAL) ........................................ 65
9923 4.15.1 Again: Scoring 66
9924 4.16 SMTP Support (OPTIONAL) ........................................ 66
9925 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 67
9926 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 67
9927 4.19 Compressed folders Support (OPTIONAL) .......................... 68
9928 4.19.1 Open a compressed mailbox for reading 68
9929 4.19.2 Write a compressed mailbox 69
9930 4.19.3 Append a message to a compressed mailbox 69
9931 4.19.4 Encrypted folders 70
9933 5. Mutt-ng's MIME Support ............................................... 70
9934 5.1 Using MIME in Mutt ............................................. 70
9935 5.1.1 Viewing MIME messages in the pager 71
9936 5.1.2 The Attachment Menu 71
9937 5.1.3 The Compose Menu 71
9938 5.2 MIME Type configuration with mime.types ........................ 72
9939 5.3 MIME Viewer configuration with mailcap ......................... 72
9940 5.3.1 The Basics of the mailcap file 73
9941 5.3.2 Secure use of mailcap 74
9942 5.3.3 Advanced mailcap Usage 75
9943 5.3.4 Example mailcap files 77
9944 5.4 MIME Autoview .................................................. 78
9945 5.5 MIME Multipart/Alternative ..................................... 79
9946 5.6 MIME Lookup .................................................... 79
9948 6. Security Considerations ............................................ 80
9949 6.1 Passwords .................................................. 80
9950 6.2 Temporary Files ............................................ 80
9951 6.3 Information Leaks ............................................ 81
9952 6.3.1 Message-ID: headers 81
9953 6.3.2 mailto:-style links 81
9954 6.4 External applications ...................................... 81
9958 7. Reference ............................................................ 82
9959 7.1 Command line options ........................................... 82
9960 7.2 Patterns ....................................................... 83
9961 7.3 Configuration Commands ......................................... 85
9965 7.4 Configuration variables .......................................... 87
9966 7.4.1 abort_noattach 88
9967 7.4.2 abort_nosubject 89
9968 7.4.3 abort_unmodified 89
9969 7.4.4 agent_string 89
9971 7.4.6 alias_format 89
9974 7.4.9 arrow_cursor 90
9975 7.4.10 ascii_chars 91
9978 7.4.13 assumed_charset 91
9979 7.4.14 attach_format 91
9980 7.4.15 attach_remind_regexp 92
9981 7.4.16 attach_sep 93
9982 7.4.17 attach_split 93
9983 7.4.18 attribution 93
9989 7.4.24 bounce_delivered 94
9990 7.4.25 braille_friendly 94
9991 7.4.26 certificate_file 95
9994 7.4.29 collapse_unread 95
9995 7.4.30 compose_format 96
9996 7.4.31 config_charset 96
9997 7.4.32 confirmappend 96
9998 7.4.33 confirmcreate 96
9999 7.4.34 connect_timeout 96
10000 7.4.35 content_type 97
10002 7.4.37 crypt_autoencrypt 97
10003 7.4.38 crypt_autopgp 97
10004 7.4.39 crypt_autosign 98
10005 7.4.40 crypt_autosmime 98
10006 7.4.41 crypt_replyencrypt 98
10007 7.4.42 crypt_replysign 98
10008 7.4.43 crypt_replysignencrypted 98
10009 7.4.44 crypt_timestamp 99
10010 7.4.45 crypt_use_gpgme 99
10011 7.4.46 crypt_verify_sig 99
10012 7.4.47 date_format 99
10013 7.4.48 debug_level 100
10014 7.4.49 default_hook 100
10016 7.4.51 delete_space 100
10017 7.4.52 delete_untag 101
10021 7.4.53 digest_collapse 101
10022 7.4.54 display_filter 101
10023 7.4.55 dotlock_program 101
10024 7.4.56 dsn_notify 101
10025 7.4.57 dsn_return 102
10026 7.4.58 duplicate_threads 102
10027 7.4.59 edit_headers 102
10029 7.4.61 editor_headers 102
10030 7.4.62 encode_from 103
10031 7.4.63 entropy_file 103
10032 7.4.64 envelope_from 103
10034 7.4.66 fast_reply 104
10035 7.4.67 fcc_attach 104
10036 7.4.68 fcc_clear 104
10037 7.4.69 file_charset 104
10039 7.4.71 folder_format 105
10040 7.4.72 followup_to 106
10041 7.4.73 force_buffy_check 106
10042 7.4.74 force_name 106
10043 7.4.75 forward_decode 106
10044 7.4.76 forward_decrypt 107
10045 7.4.77 forward_edit 107
10046 7.4.78 forward_format 107
10047 7.4.79 forward_quote 107
10049 7.4.81 gecos_mask 108
10052 7.4.84 header_cache 108
10053 7.4.85 header_cache_compress 109
10055 7.4.87 hidden_host 109
10056 7.4.88 hide_limited 109
10057 7.4.89 hide_missing 109
10058 7.4.90 hide_thread_subject 110
10059 7.4.91 hide_top_limited 110
10060 7.4.92 hide_top_missing 110
10062 7.4.94 honor_followup_to 110
10063 7.4.95 hostname 111
10064 7.4.96 ignore_list_reply_to 111
10065 7.4.97 imap_authenticators 111
10066 7.4.98 imap_check_subscribed 111
10067 7.4.99 imap_delim_chars 112
10068 7.4.100 imap_headers 112
10069 7.4.101 imap_home_namespace 112
10070 7.4.102 imap_keepalive 112
10071 7.4.103 imap_list_subscribed 113
10072 7.4.104 imap_login 113
10073 7.4.105 imap_mail_check 113
10077 7.4.106 imap_pass 113
10078 7.4.107 imap_passive 114
10079 7.4.108 imap_peek 114
10080 7.4.109 imap_reconnect 114
10081 7.4.110 imap_servernoise 114
10082 7.4.111 imap_user 115
10083 7.4.112 implicit_autoview 115
10084 7.4.113 include 115
10085 7.4.114 include_onlyfirst 115
10086 7.4.115 indent_string 115
10087 7.4.116 index_format 115
10089 7.4.118 keep_flagged 118
10090 7.4.119 list_reply 119
10092 7.4.121 mail_check 119
10093 7.4.122 mailcap_path 119
10094 7.4.123 mailcap_sanitize 119
10095 7.4.124 maildir_header_cache_verify 119
10096 7.4.125 maildir_trash 120
10097 7.4.126 mark_old 120
10098 7.4.127 markers 120
10100 7.4.129 max_display_recips 121
10101 7.4.130 max_line_length 121
10103 7.4.132 mbox_type 121
10104 7.4.133 menu_context 121
10105 7.4.134 menu_move_off 122
10106 7.4.135 menu_scroll 122
10107 7.4.136 message_format 122
10108 7.4.137 meta_key 122
10110 7.4.139 mh_purge 123
10111 7.4.140 mh_seq_flagged 123
10112 7.4.141 mh_seq_replied 123
10113 7.4.142 mh_seq_unseen 123
10114 7.4.143 mime_forward 123
10115 7.4.144 mime_forward_decode 123
10116 7.4.145 mime_forward_rest 124
10117 7.4.146 mix_entry_format 124
10118 7.4.147 mixmaster 124
10120 7.4.149 msgid_format 125
10121 7.4.150 muttng_bindir 126
10122 7.4.151 muttng_docdir 126
10123 7.4.152 muttng_hcache_backend 126
10124 7.4.153 muttng_revision 126
10125 7.4.154 muttng_sysconfdir 126
10126 7.4.155 muttng_version 127
10127 7.4.156 narrow_tree 127
10128 7.4.157 nntp_ask_followup_to 127
10129 7.4.158 nntp_ask_x_comment_to 127
10133 7.4.159 nntp_cache_dir 127
10134 7.4.160 nntp_catchup 128
10135 7.4.161 nntp_context 128
10136 7.4.162 nntp_followup_to_poster 128
10137 7.4.163 nntp_group_index_format 128
10138 7.4.164 nntp_host 129
10139 7.4.165 nntp_inews 129
10140 7.4.166 nntp_load_description 129
10141 7.4.167 nntp_mail_check 130
10142 7.4.168 nntp_mime_subject 130
10143 7.4.169 nntp_newsrc 130
10144 7.4.170 nntp_pass 130
10145 7.4.171 nntp_post_moderated 131
10146 7.4.172 nntp_reconnect 131
10147 7.4.173 nntp_save_unsubscribed 131
10148 7.4.174 nntp_show_new_news 131
10149 7.4.175 nntp_show_only_unread 132
10150 7.4.176 nntp_user 132
10151 7.4.177 nntp_x_comment_to 132
10152 7.4.178 operating_system 132
10154 7.4.180 pager_context 133
10155 7.4.181 pager_format 133
10156 7.4.182 pager_index_lines 133
10157 7.4.183 pager_stop 133
10158 7.4.184 pgp_auto_decode 134
10159 7.4.185 pgp_autoinline 134
10160 7.4.186 pgp_check_exit 134
10161 7.4.187 pgp_clearsign_command 134
10162 7.4.188 pgp_decode_command 135
10163 7.4.189 pgp_decrypt_command 135
10164 7.4.190 pgp_encrypt_only_command 135
10165 7.4.191 pgp_encrypt_sign_command 135
10166 7.4.192 pgp_entry_format 136
10167 7.4.193 pgp_export_command 136
10168 7.4.194 pgp_getkeys_command 136
10169 7.4.195 pgp_good_sign 137
10170 7.4.196 pgp_ignore_subkeys 137
10171 7.4.197 pgp_import_command 137
10172 7.4.198 pgp_list_pubring_command 137
10173 7.4.199 pgp_list_secring_command 137
10174 7.4.200 pgp_long_ids 138
10175 7.4.201 pgp_mime_auto 138
10176 7.4.202 pgp_replyinline 138
10177 7.4.203 pgp_retainable_sigs 138
10178 7.4.204 pgp_show_unusable 139
10179 7.4.205 pgp_sign_as 139
10180 7.4.206 pgp_sign_command 139
10181 7.4.207 pgp_sort_keys 139
10182 7.4.208 pgp_strict_enc 140
10183 7.4.209 pgp_timeout 140
10184 7.4.210 pgp_use_gpg_agent 140
10185 7.4.211 pgp_verify_command 140
10189 7.4.212 pgp_verify_key_command 140
10190 7.4.213 pipe_decode 140
10191 7.4.214 pipe_sep 141
10192 7.4.215 pipe_split 141
10193 7.4.216 pop_auth_try_all 141
10194 7.4.217 pop_authenticators 141
10195 7.4.218 pop_delete 142
10196 7.4.219 pop_host 142
10197 7.4.220 pop_last 142
10198 7.4.221 pop_mail_check 142
10199 7.4.222 pop_pass 143
10200 7.4.223 pop_reconnect 143
10201 7.4.224 pop_user 143
10202 7.4.225 post_indent_string 143
10203 7.4.226 postpone 143
10204 7.4.227 postponed 144
10205 7.4.228 preconnect 144
10207 7.4.230 print_command 144
10208 7.4.231 print_decode 144
10209 7.4.232 print_split 145
10210 7.4.233 prompt_after 145
10211 7.4.234 query_command 145
10213 7.4.236 quote_empty 146
10214 7.4.237 quote_quoted 146
10215 7.4.238 quote_regexp 146
10216 7.4.239 read_inc 146
10217 7.4.240 read_only 146
10218 7.4.241 realname 147
10221 7.4.244 reply_regexp 147
10222 7.4.245 reply_self 148
10223 7.4.246 reply_to 148
10224 7.4.247 resolve 148
10225 7.4.248 reverse_alias 148
10226 7.4.249 reverse_name 149
10227 7.4.250 reverse_realname 149
10228 7.4.251 rfc2047_parameters 149
10229 7.4.252 save_address 149
10230 7.4.253 save_empty 150
10231 7.4.254 save_name 150
10233 7.4.256 score_threshold_delete 150
10234 7.4.257 score_threshold_flag 151
10235 7.4.258 score_threshold_read 151
10236 7.4.259 send_charset 151
10237 7.4.260 sendmail 151
10238 7.4.261 sendmail_wait 151
10240 7.4.263 sidebar_boundary 152
10241 7.4.264 sidebar_delim 152
10245 7.4.265 sidebar_newmail_only 152
10246 7.4.266 sidebar_number_format 152
10247 7.4.267 sidebar_shorten_hierarchy 153
10248 7.4.268 sidebar_visible 153
10249 7.4.269 sidebar_width 154
10250 7.4.270 sig_dashes 154
10251 7.4.271 sig_on_top 154
10252 7.4.272 signature 154
10253 7.4.273 signoff_string 154
10254 7.4.274 simple_search 155
10255 7.4.275 sleep_time 155
10256 7.4.276 smart_wrap 155
10257 7.4.277 smileys 155
10258 7.4.278 smime_ask_cert_label 155
10259 7.4.279 smime_ca_location 156
10260 7.4.280 smime_certificates 156
10261 7.4.281 smime_decrypt_command 156
10262 7.4.282 smime_decrypt_use_default_key 157
10263 7.4.283 smime_default_key 157
10264 7.4.284 smime_encrypt_command 157
10265 7.4.285 smime_encrypt_with 157
10266 7.4.286 smime_get_cert_command 158
10267 7.4.287 smime_get_cert_email_command 158
10268 7.4.288 smime_get_signer_cert_command 158
10269 7.4.289 smime_import_cert_command 158
10270 7.4.290 smime_is_default 158
10271 7.4.291 smime_keys 158
10272 7.4.292 smime_pk7out_command 159
10273 7.4.293 smime_sign_command 159
10274 7.4.294 smime_sign_opaque_command 159
10275 7.4.295 smime_timeout 159
10276 7.4.296 smime_verify_command 159
10277 7.4.297 smime_verify_opaque_command 160
10278 7.4.298 smtp_envelope 160
10279 7.4.299 smtp_host 160
10280 7.4.300 smtp_pass 160
10281 7.4.301 smtp_port 161
10282 7.4.302 smtp_use_tls 161
10283 7.4.303 smtp_user 161
10285 7.4.305 sort_alias 162
10286 7.4.306 sort_aux 162
10287 7.4.307 sort_browser 163
10288 7.4.308 sort_re 163
10289 7.4.309 spam_separator 163
10290 7.4.310 spoolfile 163
10291 7.4.311 ssl_ca_certificates_file 164
10292 7.4.312 ssl_client_cert 164
10293 7.4.313 ssl_force_tls 164
10294 7.4.314 ssl_min_dh_prime_bits 164
10295 7.4.315 ssl_starttls 164
10296 7.4.316 ssl_use_sslv2 165
10297 7.4.317 ssl_use_sslv3 165
10301 7.4.318 ssl_use_tlsv1 165
10302 7.4.319 ssl_usesystemcerts 165
10303 7.4.320 status_chars 165
10304 7.4.321 status_format 166
10305 7.4.322 status_on_top 168
10306 7.4.323 strict_mailto 168
10307 7.4.324 strict_mime 168
10308 7.4.325 strict_threads 169
10309 7.4.326 strip_was 169
10310 7.4.327 strip_was_regex 169
10311 7.4.328 stuff_quoted 169
10312 7.4.329 suspend 170
10313 7.4.330 text_flowed 170
10314 7.4.331 thorough_search 170
10315 7.4.332 thread_received 170
10317 7.4.334 timeout 171
10319 7.4.336 to_chars 171
10323 7.4.340 uncollapse_jump 172
10324 7.4.341 use_8bitmime 172
10325 7.4.342 use_domain 172
10326 7.4.343 use_from 172
10327 7.4.344 use_idn 173
10328 7.4.345 use_ipv6 173
10330 7.4.347 wait_key 173
10332 7.4.349 wrap_search 174
10333 7.4.350 wrapmargin 174
10334 7.4.351 write_bcc 174
10335 7.4.352 write_inc 174
10336 7.4.353 xterm_icon 174
10337 7.4.354 xterm_leave 175
10338 7.4.355 xterm_set_titles 175
10339 7.4.356 xterm_title 175
10340 7.5 Functions ....................................................... 175
10353 8. Miscellany ............................................................ 183
10357 8.1 Acknowledgments ................................................. 184
10358 8.2 About this document ............................................. 186