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.4 , page 24) 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.324 , page 165) 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.8 , page 27) 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 75) 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.292 , page 155) 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.110 , page 111). 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.110 , page 111) 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.313 , page 163).
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.3 , page 23) command is added to
534 the file specified by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.3 , page 86) 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.3 , page 86) does not
536 add the aliases specified there-in, you must also _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , 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.9 , page 30) 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 67), 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 68). 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.7 , page 27) 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.12 ,
607 page 32) 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.88 , page 106) 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.201 , page 134), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.203 , page 135), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.202 , page 135) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.336 , page 167) 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.337 , page 168) 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.336 , page 167) 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.226 , page 140) 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.309 , page 160) 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.54 , page 98).
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.193 , page 133) 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.180 , page 130)) 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.140 ,
951 page 119)). 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.215 , page 138) 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.214 , page 137) 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 79) 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 82) to configure Mutt-ng.
1042 _
\b3_
\b._
\b2 _
\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 82). 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 It is also possible to substitute the output of a Unix command in an initial-
1106 ization file. This is accomplished by enclosing the command in backquotes
1109 The Mutt Next Generation E-Mail Client 23
1111 my_hdr X-Operating-System: `uname -a`
1113 The output of the Unix command ``uname -a'' will be substituted before the line
1114 is parsed. Note that since initialization files are line oriented, only the
1115 first line of output from the Unix command will be substituted.
1117 UNIX environments can be accessed like the way it is done in shells like sh and
1118 bash: Prepend the name of the environment by a ``$''. For example,
1120 set record=+sent_on_$HOSTNAME
1122 The commands understood by mutt are explained in the next paragraphs. For a
1123 complete list, see the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.3 , page 82).
1125 _
\b3_
\b._
\b3 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1127 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1129 It's usually very cumbersome to remember or type out the address of someone you
1130 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1131 short string to a full address.
1133 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1134 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1136 To remove an alias or aliases (``*'' means all aliases):
1138 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1140 alias muttdude me@cs.hmc.edu (Michael Elkins)
1141 alias theguys manny, moe, jack
1143 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1144 cial file. The alias command can appear anywhere in a configuration file, as
1145 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.28 , page 42). Consequently, you can
1146 have multiple alias files, or you can have all aliases defined in your muttrc.
1148 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
1149 only one file, the one pointed to by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.3 , page 86)
1150 variable (which is ~/.muttrc by default). This file is not special either, in
1151 the sense that Mutt-ng will happily append aliases to any file, but in order
1152 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1153 3.28 , page 42) this file too.
1157 The Mutt Next Generation E-Mail Client 24
1159 source /usr/local/share/Mutt-ng.aliases
1160 source ~/.mail_aliases
1161 set alias_file=~/.mail_aliases
1163 To use aliases, you merely use the alias at any place in mutt where mutt
1164 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1165 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
1166 (section 7.4.54 , page 98) variable set.
1168 In addition, at the various address prompts, you can use the tab character to
1169 expand a partial alias to the full alias. If there are multiple matches, mutt
1170 will bring up a menu with the matching aliases. In order to be presented with
1171 the full list of aliases, you must hit tab with out a partial alias, such as at
1172 the beginning of the prompt or after a comma denoting multiple addresses.
1174 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1175 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1178 _
\b3_
\b._
\b4 _
\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
1180 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1182 This command allows you to change the default key bindings (operation invoked
1183 when pressing a key).
1185 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be speci-
1186 fied by separating them with commas (no additional whitespace is allowed). The
1187 currently defined maps are:
1190 This is not a real menu, but is used as a fallback for all of the
1191 other menus except for the pager and editor modes. If a key is not
1192 defined in another menu, Mutt-ng will look for a binding to use in
1193 this menu. This allows you to bind a key to a certain function in
1194 multiple menus instead of having multiple bind statements to accom-
1195 plish the same task.
1198 The alias menu is the list of your personal aliases as defined in
1199 your muttrc. It is the mapping from a short alias name to the full
1200 email address(es) of the recipient(s).
1203 The attachment menu is used to access the attachments on received
1207 The browser is used for both browsing the local directory
1209 The Mutt Next Generation E-Mail Client 25
1211 structure, and for listing all of your incoming mailboxes.
1214 The editor is the line-based editor the user enters text data.
1217 The index is the list of messages contained in a mailbox.
1220 The compose menu is the screen used when sending a new message.
1223 The pager is the mode used to display message/attachment data, and
1227 The pgp menu is used to select the OpenPGP keys used for encrypting
1231 The postpone menu is similar to the index menu, except is used when
1232 recalling a message the user was composing, but saved until later.
1234 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1235 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1236 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1237 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
1238 alternative form is to specify the key as a three digit octal number prefixed
1239 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1241 In addition, _
\bk_
\be_
\by may consist of:
1243 The Mutt Next Generation E-Mail Client 26
1247 <backtab> backtab / shift-tab
1257 <pagedown> Page Down
1258 <backspace> Backspace
1267 <f10> function key 10
1269 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1271 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1272 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 169). The special
1273 function noop unbinds the specified key sequence.
1275 _
\b3_
\b._
\b5 _
\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
1277 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1279 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1281 The charset-hook command defines an alias for a character set. This is useful
1282 to properly display messages which are tagged with a character set name not
1285 The iconv-hook command defines a system-specific name for a character set.
1286 This is helpful when your systems character conversion library insists on using
1287 strange, system-specific names for character sets.
1289 _
\b3_
\b._
\b6 _
\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
1291 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1293 It is often desirable to change settings based on which mailbox you are
1295 The Mutt Next Generation E-Mail Client 27
1297 reading. The folder-hook command provides a method by which you can execute
1298 any configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1299 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1300 folder-hook's, they are executed in the order given in the muttrc.
1302 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.298 , page
1303 157) at the beginning of the pattern, you must place it inside of double or
1304 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1307 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1308 ple, a command action to perform is to change the sorting method based upon the
1311 folder-hook mutt set sort=threads
1313 However, the sorting method is not restored to its previous value when reading
1314 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1316 folder-hook . set sort=date-sent
1318 _
\b3_
\b._
\b7 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1320 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 ]
1322 Macros are useful when you would like a single key to perform a series of
1323 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1324 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1325 create a macro to execute those commands with a single key.
1327 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.4 , page 24) which the macro will be bound. Multi-
1328 ple maps may be specified by separating multiple menu arguments by commas.
1329 Whitespace may not be used in between the menu arguments and the commas sepa-
1332 _
\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
1333 3.4 , page 24). There are some additions however. The first is that control
1334 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1335 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1336 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
1337 _
\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
1338 3.4 , page 24). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1341 The advantage with using function names directly is that the macros will work
1342 regardless of the current key bindings, so they are not dependent on the user
1343 having particular key definitions. This makes them more robust and portable,
1344 and also facilitates defining of macros in files used by more than one user
1346 The Mutt Next Generation E-Mail Client 28
1348 (eg. the system Muttngrc).
1350 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1353 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1354 truncated at the screen width, and are not wrapped.
1356 _
\b3_
\b._
\b8 _
\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
1358 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 ]
1360 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
1362 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1364 If your terminal supports color, you can spice up Mutt-ng by creating your own
1365 color scheme. To define the color of an object (type of information), you must
1366 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1367 only specify one or the other).
1369 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1373 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1375 +
\bo bold (highlighting bold patterns in the body of messages)
1377 +
\bo error (error messages printed by Mutt-ng)
1379 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1381 +
\bo hdrdefault (default color of the message header in the pager)
1383 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1385 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1387 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1389 +
\bo message (informational messages)
1393 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.226 , page 140) in the
1396 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1398 +
\bo search (highlighting of words in the pager)
1400 The Mutt Next Generation E-Mail Client 29
1404 +
\bo status (mode lines used to display info about the mailbox or message)
1406 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1408 +
\bo tree (thread tree drawn in the message index and attachment menu)
1410 +
\bo underline (highlighting underlined patterns in the body of messages)
1412 _
\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:
1434 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the fore-
1435 ground color boldfaced (e.g., brightred).
1437 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1438 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1439 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-
1440 ment variable to the default colors of your terminal for this to work; for
1441 example (for Bourne-like shells):
1443 set COLORFGBG="green;black"
1446 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
1447 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1449 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1450 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1451 command for it to be removed. The pattern ``*'' is a special token which means
1452 to clear the color index list of all entries.
1454 The Mutt Next Generation E-Mail Client 30
1456 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
1457 number of colors supported by your terminal). This is useful when you remap
1458 the colors for your display (for example by changing the color associated with
1459 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1461 If your terminal does not support color, it is still possible change the video
1462 attributes through the use of the ``mono'' command:
1464 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 ]
1466 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1468 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1470 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1482 _
\b3_
\b._
\b9 _
\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
1484 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1486 Messages often have many header fields added by automatic processing systems,
1487 or which may not seem useful to display on the screen. This command allows you
1488 to specify header fields which you don't normally want to see.
1490 You do not need to specify the full header field name. For example, ``ignore
1491 content-'' will ignore all header fields that begin with the pattern ``con-
1492 tent-''. ``ignore *'' will ignore all headers.
1494 To remove a previously added token from the list, use the ``unignore'' command.
1495 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1496 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1499 ``unignore *'' will remove all tokens from the ignore list.
1503 # Sven's draconian header weeding
1505 unignore from date subject to cc
1506 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1509 The Mutt Next Generation E-Mail Client 31
1511 _
\b3_
\b._
\b1_
\b0 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1513 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1515 With various functions, mutt will treat messages differently, depending on
1516 whether you sent them or whether you received them from someone else. For
1517 instance, when replying to a message that you sent to a different party, mutt
1518 will automatically suggest to send the response to the original message's
1519 recipients -- responding to yourself won't make much sense in many cases. (See
1520 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.234 , page 142).)
1522 Many users receive e-mail under a number of different addresses. To fully use
1523 mutt's features here, the program must be able to recognize what e-mail
1524 addresses you receive mail under. That's the purpose of the alternates command:
1525 It takes a list of regular expressions, each of which can identify an address
1526 under which you receive e-mail.
1528 The unalternates command can be used to write exceptions to alternates pat-
1529 terns. If an address matches something in an alternates command, but you none-
1530 theless do not think it is from you, you can list a more precise pattern under
1531 an unalternates command.
1533 To remove a regular expression from the alternates list, use the unalternates
1534 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1535 command matches an entry on the unalternates list, that unalternates entry will
1536 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
1539 _
\b3_
\b._
\b1_
\b1 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1541 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1542 ning of email, each message had a fixed line width, and it was enough for dis-
1543 playing them on fixed-size terminals. But times changed, and nowadays hardly
1544 anybody still uses fixed-size terminals: more people nowaydays use graphical
1545 user interfaces, with dynamically resizable windows. This led to the demand of
1546 a new email format that makes it possible for the email client to make the
1547 email look nice in a resizable window without breaking quoting levels and cre-
1548 ating an incompatible email format that can also be displayed nicely on old
1549 fixed-size terminals.
1551 For introductory information on format=flowed messages, see
1552 <http://www.joeclark.org/ffaq.html>.
1554 When you receive emails that are marked as format=flowed messages, and is for-
1555 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1556 your terminal. If you want a fixed margin on the right side of your terminal,
1557 you can set the following:
1561 The Mutt Next Generation E-Mail Client 32
1563 The code above makes the line break 10 columns before the right side of the
1566 If your terminal is so wide that the lines are embarrassingly long, you can
1567 also set a maximum line length:
1569 set max_line_length = 120
1571 The example above will give you lines not longer than 120 characters.
1573 When you view at format=flowed messages, you will often see the quoting hierar-
1574 chy like in the following example:
1576 >Bill, can you please send last month's progress report to Mr.
1577 >Morgan? We also urgently need the cost estimation for the new
1578 >production server that we want to set up before our customer's
1579 >project will go live.
1581 This obviously doesn't look very nice, and it makes it very hard to differenti-
1582 ate between text and quoting character. The solution is to configure mutt-ng to
1583 "stuff" the quoting:
1587 This will lead to a nicer result that is easier to read:
1589 > Bill, can you please send last month's progress report to Mr.
1590 > Morgan? We also urgently need the cost estimation for the new
1591 > production server that we want to set up before our customer's
1592 > project will go live.
1594 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1599 Additionally, you have to use an editor which supports writing format=flowed-
1600 conforming emails. For vim, this is done by adding w to the formatoptions (see
1601 :h formatoptions and :h fo-table) when writing emails.
1603 _
\b3_
\b._
\b1_
\b2 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1605 The Mutt Next Generation E-Mail Client 33
1607 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1609 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1611 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 ,
1612 page 57). In order to take advantage of them, you must specify which addresses
1613 belong to mailing lists, and which mailing lists you are subscribed to. Once
1614 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1615 work for all known lists. Additionally, when you send a message to a sub-
1616 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1617 user agents not to send copies of replies to your personal address. Note that
1618 the Mail-Followup-To header is a non-standard extension which is not supported
1619 by all mail user agents. Adding it is not bullet-proof against receiving per-
1620 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1621 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.66 , page 101)
1622 configuration variable.
1624 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1625 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1626 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1629 You can use regular expressions with both commands. To mark all messages sent
1630 to a specific bug report's address on mutt's bug tracking system as list mail,
1631 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1632 sufficient to just give a portion of the list's e-mail address.
1634 Specify as much of the address as you need to to remove ambiguity. For exam-
1635 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1636 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
1637 list, you could add ``lists mutt-users'' to your initialization file. To tell
1638 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1639 tialization file instead. If you also happen to get mail from someone whose
1640 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-
1641 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1642 from the actual list.
1644 The ``unlists'' command is used to remove a token from the list of known and
1645 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1647 To remove a mailing list from the list of subscribed mailing lists, but keep it
1648 on the list of known mailing lists, use ``unsubscribe''.
1650 _
\b3_
\b._
\b1_
\b3 _
\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
1652 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1654 This command is used to move read messages from a specified mailbox to a dif-
1655 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1656 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1657 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1659 The Mutt Next Generation E-Mail Client 34
1661 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1662 (it is not possible to save read mail in more than a single mailbox).
1664 _
\b3_
\b._
\b1_
\b4 _
\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
1666 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1668 This command specifies folders which can receive mail and which will be checked
1669 for new messages. By default, the main menu status bar displays how many of
1670 these folders have new messages.
1672 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1674 Pressing TAB in the directory browser will bring up a menu showing the files
1675 specified by the mailboxes command, and indicate which contain new messages.
1676 Mutt-ng will automatically enter this mode when invoked from the command line
1679 The ``unmailboxes'' command is used to remove a token from the list of folders
1680 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1682 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1683 access time. Utilities like biff or frm or any other program which accesses
1684 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1685 they do not properly reset the access time. Backup tools are another common
1686 reason for updated access times.
1688 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1689 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
1690 56) (such as ``='' and ``!''), any variable definition that affect these char-
1691 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.64 , page 100) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1692 7.4.298 , page 157)) should be executed before the mailboxes command.
1694 _
\b3_
\b._
\b1_
\b5 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1698 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1700 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1702 The ``my_hdr'' command allows you to create your own header fields which will
1703 be added to every message you send.
1705 For example, if you would like to add an ``Organization:'' header field to all
1706 of your outgoing messages, you can put the command
1708 my_hdr Organization: A Really Big Company, Anytown, USA
1710 The Mutt Next Generation E-Mail Client 35
1714 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1715 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1716 there, so Mutt-ng enforces the rule.
1718 If you would like to add a header field to a single message, you should either
1719 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.54 , page 98) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1720 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1721 header of your message along with the body.
1723 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1724 specify an asterisk (``*'') to remove all header fields, or the fields to
1725 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1730 _
\b3_
\b._
\b1_
\b6 _
\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
1732 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1734 With this command, you can specify an order in which mutt will attempt to
1735 present headers to you when viewing messages.
1737 ``unhdr_order *'' will clear all previous headers from the order list, thus
1738 removing the header order effects set by the system-wide startup file.
1740 hdr_order From Date: From: To: Cc: Subject:
1742 _
\b3_
\b._
\b1_
\b7 _
\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
1744 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1746 This command is used to override the default filename used when saving mes-
1747 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:
1748 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1749 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1751 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 53) for information on the
1752 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1756 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1758 The Mutt Next Generation E-Mail Client 36
1760 save-hook aol\\.com$ +spam
1762 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36) command.
1764 _
\b3_
\b._
\b1_
\b8 _
\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
1766 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1768 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1769 (section 7.4.231 , page 141). Mutt-ng searches the initial list of message
1770 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1771 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1772 7.4.231 , page 141) mailbox.
1774 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 53) for information on the
1775 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1777 Example: fcc-hook [@.]aol\\.com$ +spammers
1779 The above will save a copy of all messages going to the aol.com domain to the
1780 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 ,
1783 _
\b3_
\b._
\b1_
\b9 _
\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
1785 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1787 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1788 3.18 , page 35) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 35) with its arguments.
1790 _
\b3_
\b._
\b2_
\b0 _
\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
1792 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1794 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1796 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1798 These commands can be used to execute arbitrary configuration commands based
1799 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1800 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1803 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1804 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1805 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
1806 the order specified in the users's configuration file.
1808 The Mutt Next Generation E-Mail Client 37
1810 send2-hook is matched every time a message is changed, either by editing it, or
1811 by using the compose menu to change its recipients or subject. send2-hook is
1812 executed after send-hook, and can, e.g., be used to set parameters such as the
1813 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.248 , page 145) variable depending on the message's
1816 For each type of send-hook or reply-hook, when multiple matches occur, commands
1817 are executed in the order they are specified in the muttrc (for that type of
1820 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 53) for information on the
1821 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1823 Example: send-hook mutt 'set mime_forward signature='''
1825 Another typical use for this command is to change the values of the _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\b-
1826 _
\bt_
\bi_
\bo_
\bn (section 7.4.15 , page 89), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.260 , page 148) and
1827 _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.114 , page 114) variables in order to change the language
1828 of the attributions and signatures based upon the recipients.
1830 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
1831 recipients. Adding a recipient after replying or editing the message will NOT
1832 cause any send-hook to be executed. Also note that my_hdr commands which mod-
1833 ify recipient headers, or the message's subject, don't have any effect on the
1834 current message when executed from a send-hook.
1836 _
\b3_
\b._
\b2_
\b1 _
\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
1838 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1840 This command can be used to execute arbitrary configuration commands before
1841 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
1842 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
1843 tiple matches occur, commands are executed in the order they are specified in
1846 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 53) for information on the
1847 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1851 message-hook ~A 'set pager=builtin'
1852 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1854 _
\b3_
\b._
\b2_
\b2 _
\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
1856 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
1858 When encrypting messages with PGP or OpenSSL, you may want to associate a
1860 The Mutt Next Generation E-Mail Client 38
1862 certain key with a given e-mail address automatically, either because the
1863 recipient's public key can't be deduced from the destination address, or
1864 because, for some reasons, you need to override the key Mutt-ng would normally
1865 use. The crypt-hook command provides a method by which you can specify the ID
1866 of the public key to be used when encrypting messages to a certain recipient.
1868 The meaning of "key id" is to be taken broadly in this context: You can either
1869 put a numerical key ID here, an e-mail address, or even just a real name.
1871 _
\b3_
\b._
\b2_
\b3 _
\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
1873 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1875 This command adds the named string to the keyboard buffer. The string may con-
1876 tain control characters, key names and function names like the sequence string
1877 in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.7 , page 27) command. You may use it to automatically
1878 run a sequence of commands at startup, or when entering certain folders.
1880 _
\b3_
\b._
\b2_
\b4 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
1882 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
1884 This command can be used to execute any function. Functions are listed in the
1885 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 169). ``exec function'' is equivalent
1886 to ``push <function>''.
1888 _
\b3_
\b._
\b2_
\b5 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
1890 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
1892 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1894 In situations where you have to cope with a lot of emails, e.g. when you read
1895 many different mailing lists, and take part in discussions, it is always useful
1896 to have the important messages marked and the annoying messages or the ones
1897 that you aren't interested in deleted. For this purpose, mutt-ng features a
1898 mechanism called ``scoring''.
1900 When you use scoring, every message has a base score of 0. You can then use the
1901 score command to define patterns and a positive or negative value associated
1902 with it. When a pattern matches a message, the message's score will be raised
1903 or lowered by the amount of the value associated with the pattern.
1905 score "~f nion@muttng\.org" 50
1906 score "~f @sco\.com" -100
1908 The Mutt Next Generation E-Mail Client 39
1910 If the pattern matches, it is also possible to set the score value of the cur-
1911 rent message to a certain value and then stop evaluation:
1913 score "~f santaclaus@northpole\.int" =666
1915 What is important to note is that negative score values will be rounded up to
1918 To make scoring actually useful, the score must be applied in some way. That's
1919 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:
1921 +
\bo flag threshold: when a message has a score value equal or higher than the
1922 flag threshold, it will be flagged.
1924 +
\bo read threshold: when a message has a score value equal or lower than the
1925 read threshold, it will be marked as read.
1927 +
\bo delete threshold: when a message has a score value equal or lower than the
1928 delete threshold, it will be marked as deleted.
1930 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-
1931 tion 7.4.245 , page 145), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.246 , page 145),
1932 _
\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.244 , page 144) and. By default,
1933 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.246 , page 145) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
1934 (section 7.4.244 , page 144) are set to -1, which means that in the default
1935 threshold configuration no message will ever get marked as read or deleted.
1937 Scoring gets especially interesting when combined with the color command and
1940 color black yellow "~n 10-"
1941 color red yellow "~n 100-"
1943 The rules above mark all messages with a score between 10 and 99 with black and
1944 yellow, and messages with a score greater or equal 100 with red and yellow.
1945 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
1946 but it is more flexible, as it visually marks different scores.
1948 _
\b3_
\b._
\b2_
\b6 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
1950 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
1952 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1954 Mutt-ng has generalized support for external spam-scoring filters. By defining
1955 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
1956 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
1957 filter. You also can display the spam attributes in your index display using
1959 The Mutt Next Generation E-Mail Client 40
1961 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111) variable.
1962 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
1965 Your first step is to define your external filter's spam patterns using the
1966 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
1967 mail message. If any message in the mailbox matches this regular expression, it
1968 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
1969 nospam pattern -- see below.) The appearance of this attribute is entirely up
1970 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,
1971 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
1972 expression ``back-reference'' refers to a sub-expression contained within
1973 parentheses.) %1 is replaced with the first back-reference in the regex, %2
1974 with the second, etc.
1976 If you're using multiple spam filters, a message can have more than one spam-
1977 related header. You can define spam patterns for each filter you use. If a mes-
1978 sage matches two or more of these patterns, and the $spam_separator variable is
1979 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
1980 strings joined together, with the value of $spam_separator separating them.
1982 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
1983 these spam settings:
1985 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
1986 spam "X-Spam-Status: Yes" "90+/SA"
1987 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
1988 set spam_separator=", "
1990 If I then received a message that DCC registered with ``many'' hits under the
1991 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
1992 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
1993 characters before ``=many'' in a DCC report indicate the checksum used -- in
1994 this case, ``Fuz2''.)
1996 If the $spam_separator variable is unset, then each spam pattern match super-
1997 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
1998 only the last one to match.
2000 The spam tag is what will be displayed in the index when you use %H in the
2001 $index_format variable. It's also the string that the ~H pattern-matching
2002 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2003 ing by spam attribute will use as a sort key.
2005 That's a pretty complicated example, and most people's actual environments will
2006 have only one spam filter. The simpler your configuration, the more effective
2007 mutt can be, especially when it comes to sorting.
2009 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2010 ordering strings alphnumerically. However, if a spam tag begins with a number,
2011 mutt will sort numerically first, and lexically only when two numbers are equal
2012 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2013 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2015 The Mutt Next Generation E-Mail Client 41
2017 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2018 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2019 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2020 coerce your filter to give you a raw number. But in case you can't, mutt can
2021 still do something useful.
2023 The nospam command can be used to write exceptions to spam patterns. If a
2024 header pattern matches something in a spam command, but you nonetheless do not
2025 want it to receive a spam tag, you can list a more precise pattern under a
2028 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-
2029 ing spam list entry, the effect will be to remove the entry from the spam list,
2030 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2031 matches an entry on the nospam list, that nospam entry will be removed. If the
2032 _
\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
2033 might be the default action if you use spam and nospam in conjunction with a
2036 You can have as many spam or nospam commands as you like. You can even do your
2037 own primitive spam detection within mutt -- for example, if you consider all
2038 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2040 spam "^From: .*MAILER-DAEMON" "999"
2042 _
\b3_
\b._
\b2_
\b7 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2044 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 ... ]
2046 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2048 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2050 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2052 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 ,
2053 page 84). There are four basic types of variables: boolean, number, string and
2054 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
2055 variables can be assigned a positive integer value.
2057 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2058 be enclosed in quotes if they contain spaces or tabs. You may also use the
2059 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2061 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2062 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2063 action to be carried out automatically as if you had answered yes to the ques-
2064 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2065 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2066 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2068 The Mutt Next Generation E-Mail Client 42
2070 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2072 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2073 toggle the value (on or off). This is useful when writing macros. Example:
2076 The toggle command automatically prepends the inv prefix to all specified vari-
2079 The unset command automatically prepends the no prefix to all specified vari-
2082 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2083 a variable by prefixing the name of the variable with a question mark:
2087 The question mark is actually only required for boolean and quadoption vari-
2090 The reset command resets all given variables to the compile time defaults
2091 (hopefully mentioned in this manual). If you use the command set and prefix the
2092 variable with ``&'' this has the same behavior as the reset command.
2094 With the reset command there exists the special variable ``all'', which allows
2095 you to reset all variables to their system defaults.
2097 _
\b3_
\b._
\b2_
\b8 _
\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
2099 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2101 This command allows the inclusion of initialization commands from other files.
2102 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2103 ~/.muttrc readable and keep my aliases private.
2105 If the filename begins with a tilde (``~''), it will be expanded to the path of
2106 your home directory.
2108 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2109 an executable program from which to read input (eg. source ~/bin/myscript|).
2111 _
\b3_
\b._
\b2_
\b9 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2113 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2115 This command permits you to flush hooks you have previously defined. You can
2116 either remove all hooks by giving the ``*'' character as an argument, or you
2117 can remove all hooks of a specific type by saying something like unhook send-
2119 The Mutt Next Generation E-Mail Client 43
2123 _
\b3_
\b._
\b3_
\b0 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2125 _
\b3_
\b._
\b3_
\b0_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2127 As users may run mutt-ng on different systems, the configuration must be main-
2128 tained because it's likely that people want to use the setup everywhere they
2129 use mutt-ng. And mutt-ng tries to help where it can.
2131 To not produce conflicts with different character sets, mutt-ng allows users to
2132 specify in which character set their configuration files are encoded. Please
2133 note that while reading the configuration files, this is only respected after
2134 the corresponding declaration appears. It's advised to put the following at the
2135 very beginning of a users muttngrc:
2137 set config_charset = "..."
2139 and replacing the dots with the actual character set. To avoid problems while
2140 maintaining the setup, vim user's may want to use modelines as show in:
2142 # vim:fileencoding=...:
2144 while, again, replacing the dots with the appropriate name. This tells vim as
2145 which character set to read and save the file.
2147 _
\b3_
\b._
\b3_
\b0_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2149 ``Modularization'' means to divide the setup into several files while sorting
2150 the options or commands by topic. Especially for longer setups (e.g. with many
2151 hooks), this helps maintaining it and solving trouble.
2153 When using separation, setups may be, as a whole or in fractions, shared over
2156 _
\b3_
\b._
\b3_
\b0_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2158 When using a configuration on different systems, the user may not always have
2159 influence on how mutt-ng is installed and which features it includes.
2161 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2162 for mutt. Its basic syntax is:
2164 The Mutt Next Generation E-Mail Client 44
2166 ifdef <item> <command>
2167 ifndef <item> <command>
2169 ...whereby <item> can be one of:
2171 +
\bo a function name
2173 +
\bo a variable name
2179 All available functions, variables and menus are documented elsewhere in this
2180 manual but ``features'' is specific to these two commands. To test for one,
2181 prefix one of the following keywords with feature_:
2183 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2184 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2185 classic_smime, gpgme, header_cache
2187 As an example, one can use the following in ~/.muttngrc:
2189 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2190 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2191 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2193 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2194 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2195 ng/setup-nntp if NNTP support is built in.
2197 An example for testing for variable names can be used if users use different
2198 revisions of mutt-ng whereby the older one may not have a certain variable. To
2199 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.99 , page 108),
2202 ifdef imap_mail_check 'set imap_mail_check = 300'
2204 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
2205 (section 7.4.170 , page 127) only if the pager menu is available, use:
2207 ifdef pager 'set pager_index_lines = 10'
2209 For completeness, too, the opposite of ifdef is provided: ifndef which only
2210 executes the command if the test fails. For example, the following two examples
2212 The Mutt Next Generation E-Mail Client 45
2216 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2217 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2221 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2222 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2224 _
\b3_
\b._
\b3_
\b1 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2226 In the process of ensuring and creating more consistency, many variables have
2227 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2228 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 84) for a complete list.
2230 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2232 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2234 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2235 tion 7.2 , page 80) must be specified using regular expressions (regexp) in
2236 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2237 and GNU awk). For your convenience, we have included below a brief description
2240 The search is case sensitive if the pattern contains at least one upper case
2241 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2242 for a regular expression in an initialization command: ``\\''.
2244 A regular expression is a pattern that describes a set of strings. Regular
2245 expressions are constructed analogously to arithmetic expressions, by using
2246 various operators to combine smaller expressions.
2248 Note that the regular expression can be enclosed/delimited by either ' or '
2249 which is useful if the regular expression includes a white-space character.
2250 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-
2251 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2252 ace it with \ (backslash).
2254 The fundamental building blocks are the regular expressions that match a single
2256 The Mutt Next Generation E-Mail Client 46
2258 character. Most characters, including all letters and digits, are regular
2259 expressions that match themselves. Any metacharacter with special meaning may
2260 be quoted by preceding it with a backslash.
2262 The period ``.'' matches any single character. The caret ``^'' and the dollar
2263 sign ``$'' are metacharacters that respectively match the empty string at the
2264 beginning and end of a line.
2266 A list of characters enclosed by ``['' and ``]'' matches any single character
2267 in that list; if the first character of the list is a caret ``^'' then it
2268 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2269 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2270 specified by giving the first and last characters, separated by a hyphen ``-''.
2271 Most metacharacters lose their special meaning inside lists. To include a lit-
2272 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2273 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2276 Certain named classes of characters are predefined. Character classes consist
2277 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2278 defined by the POSIX standard:
2281 Alphanumeric characters.
2284 Alphabetic characters.
2287 Space or tab characters.
2296 Characters that are both printable and visible. (A space is print-
2297 able, but not visible, while an ``a'' is both.)
2300 Lower-case alphabetic characters.
2303 Printable characters (characters that are not control characters.)
2306 Punctuation characters (characters that are not letter, digits,
2307 control characters, or space characters).
2310 Space characters (such as space, tab and formfeed, to name a few).
2312 The Mutt Next Generation E-Mail Client 47
2315 Upper-case alphabetic characters.
2318 Characters that are hexadecimal digits.
2320 A character class is only valid in a regular expression inside the brackets of
2321 a character list. Note that the brackets in these class names are part of the
2322 symbolic names, and must be included in addition to the brackets delimiting the
2323 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].
2325 Two additional special sequences can appear in character lists. These apply to
2326 non-ASCII character sets, which can have single symbols (called collating ele-
2327 ments) that are represented with more than one character, as well as several
2328 characters that are equivalent for collating or sorting purposes:
2331 A collating symbol is a multi-character collating element enclosed
2332 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2333 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2334 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2337 An equivalence class is a locale-specific name for a list of char-
2338 acters that are equivalent. The name is enclosed in ``[='' and
2339 ``=]''. For example, the name ``e'' might be used to represent all
2340 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2341 matches any of ``'', ``'' and ``e''.
2343 A regular expression matching a single character may be followed by one of sev-
2344 eral repetition operators:
2347 The preceding item is optional and matched at most once.
2350 The preceding item will be matched zero or more times.
2353 The preceding item will be matched one or more times.
2356 The preceding item is matched exactly _
\bn times.
2359 The preceding item is matched _
\bn or more times.
2362 The preceding item is matched at most _
\bm times.
2365 The preceding item is matched at least _
\bn times, but no more than _
\bm
2368 The Mutt Next Generation E-Mail Client 48
2370 Two regular expressions may be concatenated; the resulting regular expression
2371 matches any string formed by concatenating two substrings that respectively
2372 match the concatenated subexpressions.
2374 Two regular expressions may be joined by the infix operator ``|''; the result-
2375 ing regular expression matches any string matching either subexpression.
2377 Repetition takes precedence over concatenation, which in turn takes precedence
2378 over alternation. A whole subexpression may be enclosed in parentheses to
2379 override these precedence rules.
2381 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2382 may also be used in regular expressions:
2385 Matches the empty string at either the beginning or the end of a
2389 Matches the empty string within a word.
2392 Matches the empty string at the beginning of a word.
2395 Matches the empty string at the end of a word.
2398 Matches any word-constituent character (letter, digit, or under-
2402 Matches any character that is not word-constituent.
2405 Matches the empty string at the beginning of a buffer (string).
2408 Matches the empty string at the end of a buffer.
2410 Please note however that these operators are not defined by POSIX, so they may
2411 or may not be available in stock libraries on various systems.
2413 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2415 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2416 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2417 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2418 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2419 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 80) in the Reference chapter.
2421 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2423 The Mutt Next Generation E-Mail Client 49
2425 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2428 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2430 It is possible to combine several sub-patterns to a more complex pattern. The
2431 most simple possibility is to logically AND several patterns by stringing them
2436 The pattern above matches all messages that contain ``SPAM'' in the subject and
2439 To logical OR patterns, simply use the | operator. This one especially useful
2440 when using local groups:
2442 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2443 (~b mutt-ng|~s Mutt-ng)
2446 The first pattern matches all messages that were sent by one of the mutt-ng
2447 maintainers, while the seconds pattern matches all messages that contain
2448 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2449 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2450 ences: header, i.e. messages that are not an (indirect) reply to one of my
2451 messages. A pattern can be logicall negated using the ! operator.
2453 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2455 When using dates in patterns, the dates must be specified in a special format,
2456 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2457 rent month or year. When using date ranges, and you specify only the minimum or
2458 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2459 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2461 It is also possible to use so-called ``error margins'' when specifying date
2462 ranges. You simply specify a date, and then the error margin. This margin
2463 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2464 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2465 months, w for weeks and d for days. If you use the special * sign, it means
2466 that the error margin goes to both ``directions'' in time.
2472 The first pattern matches all dates between January 1st, 2005 and January 1st
2474 The Mutt Next Generation E-Mail Client 50
2476 2006. The second pattern matches all dates between October 18th, 2004 and
2477 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2478 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2480 Relative dates are also very important, as they make it possible to specify
2481 date ranges between a fixed number of units and the current date. How this
2482 works can be seen in the following example:
2484 ~d >2w # messages older than two weeks
2485 ~d <3d # messages newer than 3 days
2486 ~d =1m # messages that are exactly one month old
2488 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2490 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2492 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2493 In short, they describe what items to print out how in menus and status mes-
2496 Basically, they work as this: for different menus and bars, there's a variable
2497 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2499 For example, when running mutt-ng on different machines or different versions
2500 for testing purposes, it may be interesting to have the following information
2501 always printed on screen when one is in the index:
2503 +
\bo the current hostname
2505 +
\bo the current mutt-ng version number
2507 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-
2508 _
\bm_
\ba_
\bt (section 7.4.309 , page 160) variable. For the hostname and version
2509 string, there's an expando for $status_format: %h expands to the hostname and
2510 %v to the version string. When just configuring:
2512 set status_format = "%v on %h: ..."
2514 mutt-ng will replace the sequence %v with the version string and %h with the
2515 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2516 mailhost, you'll see the following when you're in the index:
2518 Mutt-ng 1.5.9i on mailhost: ...
2520 In the index, there're more useful information one could want to see:
2522 The Mutt Next Generation E-Mail Client 51
2524 +
\bo which mailbox is open
2526 +
\bo how man new, flagged or postponed messages
2530 To include the mailbox' name is as easy as:
2532 set status_format = "%v on %h: %B: ...
2534 When the currently opened mailbox is Inbox, this will be expanded to:
2536 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2538 For the number of certain types of messages, one more feature of the format
2539 strings is extremely useful. If there aren't messages of a certain type, it may
2540 not be desired to print just that there aren't any but instead only print some-
2541 thing if there are any.
2543 _
\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
2545 To only print the number of messages if there are new messages in the current
2546 mailbox, further extend $status_format to:
2548 set status_format = "%v on %h: %B %?n?%n new? ...
2550 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
2551 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2552 ated if the value of the expando is different from zero. The basic syntax is:
2554 %?<item>?<string if nonzero>?
2556 which tells mutt-ng to only look at <string if nonzero> if the value of the
2557 %<item%gt; expando is different from zero. In our example, we used n as the
2558 expando to check for and %n new as the optional nonzero string.
2560 But this is not all: this feature only offers one alternative: ``print some-
2561 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2562 complete version: ``if zero, print something and else print something else.''
2563 This is achieved by the following syntax for those expandos which may be
2566 %?<item>?<string if nonzero>&<string if zero>?
2568 The Mutt Next Generation E-Mail Client 52
2570 Using this we can make mutt-ng to do the following:
2572 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2575 +
\bo and make it print ``no new messages'' if there aren't any
2577 The corresponding configuration is:
2579 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2581 This doubles the use of the ``new messages'' string because it'll get always
2582 printed. Thus, it can be shortened to:
2584 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2586 As you might see from this rather simple example, one can create very complex
2587 but fancy status messages. Please see the reference chapter for expandos and
2588 those which may be printed nonzero.
2590 _
\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
2592 Besides the information given so far, there're even more features of format
2595 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2596 characters in the expansion of <item> to lowercase.
2598 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2599 dots in the expansion of <item> to underscores (_).
2601 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2605 When this occurs, mutt-ng will fill the rest of the line with the
2606 character X. In our example, filling the rest of the line with
2607 dashes is done by setting:
2609 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2612 Since the previous expando stops at the end of line, there must be
2613 a way to fill the gap between two items via the %>X expando: it
2614 puts as many characters X in between two items so that the rest of
2615 the line will be right-justified. For example, to not put the
2617 The Mutt Next Generation E-Mail Client 53
2619 version string and hostname of our example on the left but on the
2620 right and fill the gap with spaces, one might use (note the space
2623 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2625 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2627 Sometimes it is desirable to perform an operation on a group of messages all at
2628 once rather than one at a time. An example might be to save messages to a
2629 mailing list to a separate folder, or to delete all messages with a given sub-
2630 ject. To tag all messages matching a pattern, use the tag-pattern function,
2631 which is bound to ``shift-T'' by default. Or you can select individual mes-
2632 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2633 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 80) for Mutt-ng's pattern matching
2636 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2637 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2638 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2639 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.16 ,
2640 page 90) variable is set, the next operation applies to the tagged messages
2641 automatically, without requiring the ``tag-prefix''.
2643 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.7 , page 27) or _
\bp_
\bu_
\bs_
\bh (section 3.23 , page 37) commands,
2644 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2645 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2646 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2647 this operator the rest of the macro will be executed as normal.
2649 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2651 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2652 arbitrary commands before performing some operation. For example, you may wish
2653 to tailor your configuration based upon which mailbox you are reading, or to
2654 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
2655 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 44) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 80) along
2656 with a configuration option/command. See
2658 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 26)
2660 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 36)
2662 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 37)
2664 The Mutt Next Generation E-Mail Client 54
2666 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 35)
2668 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33)
2670 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 35)
2672 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36)
2674 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2676 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2677 until the end of the current mutt session. As this is generally not desired, a
2678 default hook needs to be added before all other hooks to restore configuration
2679 defaults. Here is an example with send-hook and the my_hdr directive:
2681 send-hook . 'unmy_hdr From:'
2682 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2684 _
\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
2686 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2687 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2688 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 44) is sufficient. But in dealing with
2689 messages a finer grain of control is needed for matching since for different
2690 purposes you want to match different criteria.
2692 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 80) language
2693 for matching messages in hook commands. This works in exactly the same way as
2694 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
2695 to those operators which match information mutt extracts from the header of the
2696 message (i.e. from, to, cc, date, subject, etc.).
2698 For example, if you wanted to set your return address based upon sending mail
2699 to a specific address, you could do something like:
2701 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2703 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2705 However, it is not required that you write the pattern to match using the full
2706 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
2707 other hooks, in which case Mutt-ng will translate your pattern into the full
2708 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2709 7.4.45 , page 96) variable. The pattern is translated at the time the hook is
2710 declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.45 , page 96) that is in
2711 effect at that time will be used.
2713 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2715 The Mutt Next Generation E-Mail Client 55
2717 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2718 which looks very similar to the ones you probably know from GUI mail clients.
2719 The sidebar lists all specified mailboxes, shows the number in each and high-
2720 lights the ones with new email Use the following configuration commands:
2722 set sidebar_visible="yes"
2723 set sidebar_width=25
2725 If you want to specify the mailboxes you can do so with:
2733 You can also specify the colors for mailboxes with new mails by using:
2735 color sidebar_new red black
2736 color sidebar white black
2738 The available functions are:
2740 sidebar-scroll-up Scrolls the mailbox list up 1 page
2741 sidebar-scroll-down Scrolls the mailbox list down 1 page
2742 sidebar-next Highlights the next mailbox
2743 sidebar-next-new Highlights the next mailbox with new mail
2744 sidebar-previous Highlights the previous mailbox
2745 sidebar-open Opens the currently highlighted mailbox
2747 Reasonable key bindings look e.g. like this:
2749 bind index \Cp sidebar-prev
2750 bind index \Cn sidebar-next
2751 bind index \Cb sidebar-open
2752 bind pager \Cp sidebar-prev
2753 bind pager \Cn sidebar-next
2754 bind pager \Cb sidebar-open
2756 macro index B ':toggle sidebar_visible^M'
2757 macro pager B ':toggle sidebar_visible^M'
2759 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2760 off the sidebar simply by pressing 'B'.
2762 _
\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
2764 The Mutt Next Generation E-Mail Client 56
2766 Mutt-ng supports connecting to external directory databases such as LDAP,
2767 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2768 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.222 , page 139) vari-
2769 able, you specify the wrapper command to use. For example:
2771 set query_command = "mutt_ldap_query.pl '%s'"
2773 The wrapper script should accept the query on the command-line. It should
2774 return a one line message, then each matching response on a single line, each
2775 line containing a tab separated address then name then some other optional
2776 information. On error, or if there are no matching addresses, return a non-
2777 zero exit code and a one line error message.
2779 An example multiple response output:
2781 Searching database ... 20 entries ... 3 matching:
2782 me@cs.hmc.edu Michael Elkins mutt dude
2783 blong@fiction.net Brandon Long mutt and more
2784 roessler@guug.de Thomas Roessler mutt pgp
2786 There are two mechanisms for accessing the query function of mutt. One is to
2787 do a query from the index menu using the query function (default: Q). This
2788 will prompt for a query, then bring up the query menu which will list the
2789 matching responses. From the query menu, you can select addresses to create
2790 aliases, or to mail. You can tag multiple addresses to mail, start a new
2791 query, or have a new query appended to the current responses.
2793 The other mechanism for accessing the query function is for address completion,
2794 similar to the alias completion. In any prompt for address entry, you can use
2795 the complete-query function (default: ^T) to run a query based on the current
2796 address you have typed. Like aliases, mutt will look for what you have typed
2797 back to the last space or comma. If there is a single response for that query,
2798 mutt will expand the address in place. If there are multiple responses, mutt
2799 will activate the query menu. At the query menu, you can select one or more
2800 addresses to be added to the prompt.
2802 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2804 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2805 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2806 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2807 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.126 , page 116)
2810 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2811 stored in a single file. Each message has a line of the form:
2813 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2815 The Mutt Next Generation E-Mail Client 57
2817 to denote the start of a new message (this is often referred to as the
2820 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2821 lines containing ``^A^A^A^A'' (four control-A's).
2823 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2824 and each message is stored in a separate file. The filename indicates the mes-
2825 sage number (however, this is may not correspond to the message number Mutt-ng
2826 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2827 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2828 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
2831 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
2832 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
2833 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
2834 way they are unique, even when two programs are writing the mailbox over NFS,
2835 which means that no file locking is needed.
2837 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
2839 There are a number of built in shortcuts which refer to specific mailboxes.
2840 These shortcuts can be used anywhere you are prompted for a file or mailbox
2843 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.298 , page 157) (incoming)
2846 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.125 , page 116) file
2848 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.231 , page 141) file
2850 +
\bo ^ -- refers to the current mailbox
2852 +
\bo - or !! -- refers to the file you've last visited
2854 +
\bo ~ -- refers to your home directory
2856 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.64 , page 100) directory
2858 +
\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.17 , page 35) as
2859 determined by the address of the alias
2861 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
2863 Mutt-ng has a few configuration options that make dealing with large amounts of
2864 mail easier. The first thing you must do is to let Mutt know what addresses
2865 you consider to be mailing lists (technically this does not have to be a mail-
2866 ing list, but that is what it is most often used for), and what lists you are
2868 The Mutt Next Generation E-Mail Client 58
2870 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
2871 (section 3.12 , page 32) commands in your muttrc.
2873 Now that Mutt-ng knows what your mailing lists are, it can do several things,
2874 the first of which is the ability to show the name of a list through which you
2875 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
2876 This is useful to distinguish between personal and list mail in the same mail-
2877 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111) variable, the escape
2878 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
2879 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
2880 returns the name of the author).
2882 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
2883 quite large. Most people do not bother to remove the author of the message they
2884 are reply to from the list, resulting in two or more copies being sent to that
2885 person. The ``list-reply'' function, which by default is bound to ``L'' in the
2886 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
2887 mailing list addresses instead of all recipients (except as specified by Mail-
2888 Followup-To, see below).
2890 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
2891 a list of recipients which includes one or several subscribed mailing lists,
2892 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.66 , page 101) option is set, mutt will
2893 generate a Mail-Followup-To header which contains all the recipients to whom
2894 you send this message, but not your address. This indicates that group-replies
2895 or list-replies (also known as ``followups'') to this message should only be
2896 sent to the original recipients of the message, and not separately to you -
2897 you'll receive your copy through one of the mailing lists you are subscribed
2900 Conversely, when group-replying or list-replying to a message which has a Mail-
2901 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
2902 (section 7.4.88 , page 106) configuration variable is set. Using list-reply
2903 will in this case also make sure that the reply goes to the mailing list, even
2904 if it's not specified in the list of recipients in the Mail-Followup-To.
2906 Note that, when header editing is enabled, you can create a Mail-Followup-To
2907 header manually. Mutt-ng will only auto-generate this header if it doesn't
2908 exist when you send the message.
2910 The other method some mailing list admins use is to generate a ``Reply-To''
2911 field which points back to the mailing list address rather than the author of
2912 the message. This can create problems when trying to reply directly to the
2913 author in private, since most mail clients will automatically reply to the
2914 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
2915 7.4.234 , page 142) variable to help decide which address to use. If set to
2916 _
\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
2917 use the address given in the ``Reply-To'' field, or reply directly to the
2918 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
2919 will be used when present.
2921 The ``X-Label:'' header field can be used to further identify mailing lists or
2922 list subject matter (or just to annotate messages individually). The
2923 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111) variable's ``%y'' and ``%Y''
2925 The Mutt Next Generation E-Mail Client 59
2927 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
2928 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
2929 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
2930 can easily be inserted by procmail and other mail filtering agents.
2932 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.292 , page 155) the mail-
2933 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
2934 which all relate to the same subject. This is usually organized into a tree-
2935 like structure where a message and all of its replies are represented graphi-
2936 cally. If you've ever used a threaded news client, this is the same concept.
2937 It makes dealing with large volume mailing lists easier because you can easily
2938 delete uninteresting threads and quickly find topics of value.
2940 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2942 Mutt-ng has the ability to dynamically restructure threads that are broken
2943 either by misconfigured software or bad behavior from some correspondents. This
2944 allows to clean your mailboxes formats) from these annoyances which make it
2945 hard to follow a discussion.
2947 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2949 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
2950 ences:" headers when replying to a message. This results in broken discussions
2951 because Mutt-ng has not enough information to guess the correct threading. You
2952 can fix this by tagging the reply, then moving to the parent message and using
2953 the ``link-threads'' function (bound to & by default). The reply will then be
2954 connected to this "parent" message.
2956 You can also connect multiple children at once, tagging them and using the tag-
2957 prefix command (';') or the auto_tag option.
2959 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2961 On mailing lists, some people are in the bad habit of starting a new discussion
2962 by hitting "reply" to any message from the list and changing the subject to a
2963 totally unrelated one. You can fix such threads by using the ``break-thread''
2964 function (bound by default to #), which will turn the subthread starting from
2965 the current message into a whole different thread.
2967 _
\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
2969 RFC1894 defines a set of MIME content types for relaying information about the
2970 status of electronic mail messages. These can be thought of as ``return
2973 Users can make use of it in one of the following two ways:
2975 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
2976 the mail client can make requests as to what type of status messages
2978 The Mutt Next Generation E-Mail Client 60
2982 +
\bo The SMTP support via libESMTP supports it, too.
2984 To support this, there are two variables:
2986 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.51 , page 97) is used to request receipts for
2987 different results (such as failed message, message delivered, etc.).
2989 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.52 , page 97) requests how much of your message
2990 should be returned with the receipt (headers or full message).
2992 Please see the reference chapter for possible values.
2994 _
\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)
2996 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
2997 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
2998 remote POP3 server and fetch mail for local browsing.
3000 You can access the remote POP3 mailbox by selecting the folder
3003 You can select an alternative port by specifying it with the server, i.e.:
3004 pop://popserver:port/.
3006 You can also specify different username for each folder, i.e.: pop://user-
3007 name@popserver[:port]/.
3009 Polling for new mail is more expensive over POP3 than locally. For this reason
3010 the frequency at which Mutt-ng will check for mail remotely can be controlled
3011 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.209 , page 136) variable, which defaults
3012 to every 60 seconds.
3014 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3015 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3016 rally requires that the server supports SSL encrypted connections. To access a
3017 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3018 name@]popserver[:port]/.
3020 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3021 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.207 , page 136), fetch all your
3022 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.298 , page 157).
3023 After this point, Mutt-ng runs exactly as if the mail had always been local.
3025 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3026 sider using a specialized program, such as fetchmail
3028 _
\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)
3030 The Mutt Next Generation E-Mail Client 61
3032 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3033 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
3036 You can access the remote inbox by selecting the folder
3037 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3038 INBOX is the special name for your spool mailbox on the IMAP server. If you
3039 want to access another mail folder at the IMAP server, you should use
3040 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3043 You can select an alternative port by specifying it with the server, i.e.:
3044 imap://imapserver:port/INBOX.
3046 You can also specify different username for each folder, i.e.: imap://user-
3047 name@imapserver[:port]/INBOX.
3049 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3050 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3051 rally requires that the server supports SSL encrypted connections. To access a
3052 folder with IMAP/SSL, you should use imaps://[user-
3053 name@]imapserver[:port]/path/to/folder as your folder path.
3055 Pine-compatible notation is also supported, i.e. {[user-
3056 name@]imapserver[:port][/ssl]}path/to/folder
3058 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3059 correctly notice which separator is being used by the server and convert paths
3062 When browsing folders on an IMAP server, you can toggle whether to look at only
3063 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
3064 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.97 , page 108) vari-
3067 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3068 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.99 , page 108) and
3069 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.322 , page 164) variables.
3071 Note that if you are using mbox as the mail store on UW servers prior to
3072 v12.250, the server has been reported to disconnect a client if another client
3073 selects the same folder.
3075 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3077 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3078 mostly the same as the local file browser, with the following differences:
3080 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3081 followed by the symbol "+", indicating that the entry contains both mes-
3082 sages and subfolders. On Cyrus-like servers folders will often contain
3083 both messages and subfolders.
3085 The Mutt Next Generation E-Mail Client 62
3087 +
\bo For the case where an entry can contain both messages and subfolders, the
3088 selection key (bound to enter by default) will choose to descend into the
3089 subfolder view. If you wish to view the messages in that folder, you must
3090 use view-file instead (bound to space by default).
3092 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3093 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3094 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3095 mally these are bound to s and u, respectively).
3097 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3099 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3100 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3101 tion for you poor exchange users out there, but it has yet to be integrated
3102 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3103 which allows you to log in to a public IMAP server without having an account.
3104 To use ANONYMOUS, simply make your username blank or "anonymous".
3106 SASL is a special super-authenticator, which selects among several protocols
3107 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3108 available on your host and the server. Using some of these methods (including
3109 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3110 invisible to those teeming network snoops. It is the best option if you have
3111 it. To use it, you must have the Cyrus SASL library installed on your system
3112 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3114 Mutt-ng will try whichever methods are compiled in and available on the server,
3115 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3117 There are a few variables which control authentication:
3119 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.105 , page 110) - controls the username under
3120 which you request authentication on the IMAP server, for all authentica-
3121 tors. This is overridden by an explicit username in the mailbox path (i.e.
3122 by using a mailbox name of the form {user@host}).
3124 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.100 , page 109) - a password which you may pre-
3125 set, used by all authentication methods where a password is needed.
3127 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.91 , page 106) - a colon-delimited list
3128 of IMAP authentication methods to try, in the order you wish to try them.
3129 If specified, this overrides mutt's default (attempt everything, in the
3130 order listed above).
3132 _
\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)
3134 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3135 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3136 function from the index/pager which is by default bound to i.
3138 The Default newsserver can be obtained from the $NNTPSERVER environment
3140 The Mutt Next Generation E-Mail Client 63
3142 variable. Like other news readers, info about subscribed newsgroups is saved in
3143 a file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.157 , page 124) variable.
3144 Article headers are cached and can be loaded from a file when a newsgroup is
3145 entered instead loading from newsserver; currently, this caching mechanism
3146 still is different from the header caching for maildir/IMAP.
3148 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3150 Especially for Usenet, people often ask for advanced filtering and scoring
3151 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3152 to use a killfile has been discussed in _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bs_
\bc_
\bo_
\br_
\bi_
\bn_
\bg (section 3.25 , page
3155 What has not been discusses in detail is mutt-ng's built-in realname filter.
3156 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3157 there are frequent request for such functionality. The solutions offered often
3158 are complicated regular expressions.
3160 In mutt-ng this is as easy as
3164 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3165 fied a valid realname and a valid email address. Using
3169 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3170 ria which are very strict:
3172 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3173 editor.org/in-notes/rfc2822.txt>
3175 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3176 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3177 ``J. User'' and ``J. A. User'' aren't.
3179 +
\bo it's assumed that users are interested in reading their own mail and mail
3180 from people who they have defined an alias for so that those 2 groups of
3181 messages are excluded from the strict rules.
3183 _
\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)
3185 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3187 The Mutt Next Generation E-Mail Client 64
3189 functionality. When configure was called with --with-libesmtp or the output
3190 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3191 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3192 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 59) section) as well as handling the 8BIT-
3193 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.329 , page 166).
3195 To enable sending mail directly via SMTP without an MTA such as Postfix or
3196 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.287 , page 154)
3197 variable pointing to your SMTP server.
3199 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.291 ,
3200 page 155) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.288 , page 154) variables.
3202 Transport Encryption via the StartTLS command is also available. For this to
3203 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3204 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.290 , page 155) variable must be either set to
3205 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3206 supports it: for the second case, the connection will fail if it doesn't while
3207 switching back to unencrypted communication for the first one.
3209 Some mail providers require user's to set a particular envelope sender, i.e.
3210 they allow for only one value which may not be what the user wants to send as
3211 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.286 ,
3212 page 154) may be used to set the envelope different from the From: header.
3214 _
\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)
3216 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3217 find managing all the authentication settings inconvenient and error-prone.
3218 The account-hook command may help. This hook works like folder-hook but is
3219 invoked whenever you access a remote mailbox (including inside the folder
3220 browser), not just when you open the mailbox.
3224 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3225 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3226 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3228 _
\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)
3230 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
3231 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
3232 start a WWW browser on one of them. This functionality is provided by the
3233 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3234 trib/ and the configuration commands:
3236 macro index \cb |urlview\n
3237 macro pager \cb |urlview\n
3239 The Mutt Next Generation E-Mail Client 65
3241 _
\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)
3243 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3244 _
\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
3245 an arbitrary format, provided that the user has a script to convert from/to
3246 this format to one of the accepted.
3248 The most common use is to open compressed archived folders e.g. with gzip.
3250 In addition, the user can provide a script that gets a folder in an accepted
3251 format and appends its context to the folder in the user-defined format, which
3252 may be faster than converting the entire folder to the accepted format, append-
3253 ing to it and converting back to the user-defined format.
3255 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3256 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66))
3257 which define commands to uncompress and compress a folder and to append mes-
3258 sages to an existing compressed folder respectively.
3262 open-hook \\.gz$ "gzip -cd %f > %t"
3263 close-hook \\.gz$ "gzip -c %t > %f"
3264 append-hook \\.gz$ "gzip -c %t >> %f"
3266 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-
3267 tion 4.19.3 , page 66), the folder will be open and closed again each time you
3268 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) (or give
3269 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3270 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) though you'll be able to append to the folder.
3272 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3273 accepted formats. In particular, if the file is empty, mutt supposes it is not
3274 compressed. This is important because it allows the use of programs that do not
3275 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3276 prising if your compressing script produces empty files. In this situation,
3277 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.241 , page 144), so that the compressed file
3278 will be removed if you delete all of the messages.
3280 _
\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
3282 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3284 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3285 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3287 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3288 parameters: %f, which is replaced with the (compressed) folder name, and %t
3289 which is replaced with the name of the temporary folder to which to write.
3291 %f and %t can be repeated any number of times in the command string, and all of
3292 the entries are replaced with the appropriate folder name. In addition, %% is
3294 The Mutt Next Generation E-Mail Client 66
3296 replaced by %, as in printf, and any other %anything is left as is.
3298 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
3299 return non-zero exit status if it fails, so mutt knows something's wrong.
3303 open-hook \\.gz$ "gzip -cd %f > %t"
3305 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3307 _
\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
3309 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3311 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3312 4.19.1 , page 65) command after some changes were made to it.
3314 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3315 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
3316 4.19.1 , page 65) command. Temporary folder in this case is the folder previ-
3317 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65) command.
3319 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
3320 non-zero exit status if it fails, so mutt knows something's wrong.
3324 close-hook \\.gz$ "gzip -c %t > %f"
3326 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3327 file can only be open in the readonly mode.
3329 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) is not called when you exit from the
3330 folder if the folder was not changed.
3332 _
\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
3334 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3336 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3337 is the command that can be used for appending to the folders whose names match
3338 _
\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 65)
3339 command. The temporary folder in this case contains the messages that are
3342 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
3343 non-zero exit status if it fails, so mutt knows something's wrong.
3347 The Mutt Next Generation E-Mail Client 67
3349 append-hook \\.gz$ "gzip -c %t >> %f"
3351 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) is used, the folder is not opened,
3352 which saves time, but this means that we can not find out what the folder type
3353 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.126 , page 116)) type is always
3354 supposed (i.e. this is the format used for the temporary folder).
3356 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 ,
3357 page 65) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3358 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) is only for appending to existing folders.
3360 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3361 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3362 4.19.1 , page 65) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65)respectively) each
3363 time you will add to it.
3365 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3367 The compressed folders support can also be used to handle encrypted folders. If
3368 you want to encrypt a folder with PGP, you may want to use the following hooks:
3370 open-hook \\.pgp$ "pgp -f < %f > %t"
3371 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3373 Please note, that PGP does not support appending to an encrypted folder, so
3374 there is no append-hook defined.
3376 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3377 can be read by your system administrator. So think about the security aspects
3380 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3382 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3383 MUA. Every effort has been made to provide the functionality that the discern-
3384 ing MIME user requires, and the conformance to the standards wherever possible.
3385 When configuring Mutt-ng for MIME, there are two extra types of configuration
3386 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3387 ping of file extensions to IANA MIME types. The other is the mailcap file,
3388 which specifies the external commands to use for handling specific MIME types.
3390 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3392 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3393 (while viewing a message), the attachment menu and the compose menu.
3395 The Mutt Next Generation E-Mail Client 68
3397 _
\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
3399 When you select a message from the index and view it in the pager, Mutt decodes
3400 the message to a text representation. Mutt-ng internally supports a number of
3401 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3402 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3403 variety of PGP MIME types, including PGP/MIME and application/pgp.
3405 Mutt-ng will denote attachments with a couple lines describing them. These
3406 lines are of the form:
3408 [-- Attachment #1: Description --]
3409 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3411 Where the Description is the description or filename given for the attachment,
3412 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3414 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3416 [-- image/gif is unsupported (use 'v' to view this part) --]
3418 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3420 The default binding for view-attachments is `v', which displays the attachment
3421 menu for a message. The attachment menu displays a list of the attachments in
3422 a message. From the attachment menu, you can save, print, pipe, delete, and
3423 view attachments. You can apply these operations to a group of attachments at
3424 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3425 can also reply to the current message from this menu, and only the current
3426 attachment (or the attachments tagged) will be quoted in your reply. You can
3427 view attachments as text, or view them using the mailcap viewer definition.
3429 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3430 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3431 of type message/rfc822.
3433 See the help on the attachment menu for more information.
3435 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3437 The compose menu is the menu you see before you send a message. It allows you
3438 to edit the recipient list, the subject, and other aspects of your message. It
3439 also contains a list of the attachments of your message, including the main
3440 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3441 review, and rename an attachment or a list of tagged attachments. You can also
3442 modifying the attachment information, notably the type, encoding and descrip-
3445 Attachments appear as follows:
3447 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3448 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3450 The Mutt Next Generation E-Mail Client 69
3452 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3453 or canceling) the message. It can be toggled with the toggle-unlink command
3454 (default: u). The next field is the MIME content-type, and can be changed with
3455 the edit-type command (default: ^T). The next field is the encoding for the
3456 attachment, which allows a binary message to be encoded for transmission on
3457 7bit links. It can be changed with the edit-encoding command (default: ^E).
3458 The next field is the size of the attachment, rounded to kilobytes or
3459 megabytes. The next field is the filename, which can be changed with the
3460 rename-file command (default: R). The final field is the description of the
3461 attachment, and can be changed with the edit-description command (default: d).
3463 _
\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
3465 When you add an attachment to your mail message, Mutt-ng searches your personal
3466 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3467 /usr/local/share/mutt/mime.types or /etc/mime.types
3469 The mime.types file consist of lines containing a MIME type and a space sepa-
3470 rated list of extensions. For example:
3472 application/postscript ps eps
3474 audio/x-aiff aif aifc aiff
3476 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3477 tain most of the MIME types you are likely to use.
3479 If Mutt-ng can not determine the mime type by the extension of the file you
3480 attach, it will look at the file. If the file is free of binary information,
3481 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3482 the file contains binary information, then Mutt-ng will mark it as applica-
3483 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3484 attachment by using the edit-type command from the compose menu (default: ^T).
3485 The MIME type is actually a major mime type followed by the sub-type, separated
3486 by a '/'. 6 major types: application, text, image, video, audio, and model have
3487 been approved after various internet discussions. Mutt-ng recognises all of
3488 these if the appropriate entry is found in the mime.types file. It also recog-
3489 nises other major mime types, such as the chemical type that is widely used in
3490 the molecular modelling community to pass molecular data in various forms to
3491 various molecular viewers. Non-recognised mime types should only be used if the
3492 recipient of the message is likely to be expecting such attachments.
3494 _
\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
3496 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3497 format specified in Appendix A of RFC 1524. This file format is commonly
3498 referred to as the mailcap format. Many MIME compliant programs utilize the
3499 mailcap format, allowing you to specify handling for all MIME types in one
3500 place for all programs. Programs known to use this format include Netscape,
3502 The Mutt Next Generation E-Mail Client 70
3504 XMosaic, lynx and metamail.
3506 In order to handle various MIME types that Mutt-ng can not handle internally,
3507 Mutt-ng parses a series of external configuration files to find an external
3508 handler. The default search string for these files is a colon delimited list
3511 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3513 where $HOME is your home directory.
3515 In particular, the metamail distribution will install a mailcap file, usually
3516 as /usr/local/etc/mailcap, which contains some baseline entries.
3518 _
\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
3520 A mailcap file consists of a series of lines which are comments, blank, or def-
3523 A comment line consists of a # character followed by anything you want.
3525 A blank line is blank.
3527 A definition line consists of a content type, a view command, and any number of
3528 optional fields. Each field of a definition line is divided by a semicolon ';'
3531 The content type is specified in the MIME standard type/subtype method. For
3532 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3533 mat includes two formats for wildcards, one using the special '*' subtype, the
3534 other is the implicit wild, where you only include the major type. For exam-
3535 ple, image/*, or video, will match all image types and video types, respec-
3538 The view command is a Unix command for viewing the type specified. There are
3539 two different types of commands supported. The default is to send the body of
3540 the MIME message to the command on stdin. You can change this behavior by using
3541 %s as a parameter to your view command. This will cause Mutt-ng to save the
3542 body of the MIME message to a temporary file, and then call the view command
3543 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3544 will turn over the terminal to the view program until the program quits, at
3545 which time Mutt will remove the temporary file if it exists.
3547 So, in the simplest form, you can send a text/plain message to the external
3548 pager more on stdin:
3552 Or, you could send the message as a file:
3556 The Mutt Next Generation E-Mail Client 71
3558 Perhaps you would like to use lynx to interactively view a text/html message:
3562 In this case, lynx does not support viewing a file from stdin, so you must use
3563 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
3564 _
\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
3565 _
\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
3566 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3568 On the other hand, maybe you don't want to use lynx interactively, you just
3569 want to have it convert the text/html to text/plain, then you can use:
3571 text/html; lynx -dump %s | more
3573 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3574 text formats, then you would use the following:
3579 This is the simplest form of a mailcap file.
3581 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3583 The interpretation of shell meta-characters embedded in MIME parameters can
3584 lead to security problems in general. Mutt-ng tries to quote parameters in
3585 expansion of %s syntaxes properly, and avoids risky characters by substituting
3586 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.117 , page 115) variable.
3588 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3589 there are other applications parsing mailcap, maybe taking less care of it.
3590 Therefore you should pay attention to the following rules:
3592 _
\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
3593 double quotes. Mutt-ng does this for you, the right way, as should any other
3594 program which interprets mailcap. Don't put them into backtick expansions. Be
3595 highly careful with eval statements, and avoid them if possible at all. Trying
3596 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3597 tive to correct quoting in the first place.
3599 If you have to use the %-expandos' values in context where you need quoting or
3600 backtick expansions, put that value into a shell variable and reference the
3601 shell variable where necessary, as in the following example (using $charset
3602 inside the backtick expansion is safe, since it is not itself subject to any
3605 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3606 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3608 The Mutt Next Generation E-Mail Client 72
3610 _
\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
3612 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3614 In addition to the required content-type and view command fields, you can add
3615 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3616 nizes the following optional fields:
3619 This flag tells Mutt-ng that the command passes possibly large
3620 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3621 (either the internal pager or the external pager defined by the
3622 pager variable) on the output of the view command. Without this
3623 flag, Mutt-ng assumes that the command is interactive. One could
3624 use this to replace the pipe to more in the lynx -dump example in
3627 text/html; lynx -dump %s ; copiousoutput
3629 This will cause lynx to format the text/html output as text/plain
3630 and Mutt-ng will use your standard pager to display the results.
3633 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3634 tion 5.4 , page 75), in order to decide whether it should honor
3635 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.336 , page 167) variable
3636 or not. When an attachment is viewed using an interactive program,
3637 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3638 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.336 , page 167) and the exit
3639 status of the program to decide if it will ask you to press a key
3640 after the external program has exited. In all other situations it
3641 will not prompt you for a key.
3644 This flag specifies the command to use to create a new attachment
3645 of a specific MIME type. Mutt-ng supports this from the compose
3648 composetyped=<command>
3649 This flag specifies the command to use to create a new attachment
3650 of a specific MIME type. This command differs from the compose
3651 command in that mutt will expect standard MIME headers on the data.
3652 This can be used to specify parameters, filename, description, etc.
3653 for a new attachment. Mutt-ng supports this from the compose
3657 This flag specifies the command to use to print a specific MIME
3658 type. Mutt-ng supports this from the attachment and compose menus.
3661 This flag specifies the command to use to edit a specific MIME
3662 type. Mutt-ng supports this from the compose menu, and also uses
3664 The Mutt Next Generation E-Mail Client 73
3666 it to compose new attachments. Mutt-ng will default to the defined
3667 editor for text attachments.
3669 nametemplate=<template>
3670 This field specifies the format for the file denoted by %s in the
3671 command fields. Certain programs will require a certain file
3672 extension, for instance, to correctly view a file. For instance,
3673 lynx will only interpret a file as text/html if the file ends in
3674 .html. So, you would specify lynx as a text/html viewer with a
3675 line in the mailcap file like:
3677 text/html; lynx %s; nametemplate=%s.html
3680 This field specifies a command to run to test whether this mailcap
3681 entry should be used. The command is defined with the command
3682 expansion rules defined in the next section. If the command
3683 returns 0, then the test passed, and Mutt-ng uses this entry. If
3684 the command returns non-zero, then the test failed, and Mutt-ng
3685 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
3686 _
\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:
3688 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3691 In this example, Mutt-ng will run the program RunningX which will
3692 return 0 if the X Window manager is running, and non-zero if it
3693 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3694 display the text/html object. If RunningX doesn't return 0, then
3695 Mutt-ng will go on to the next entry and use lynx to display the
3698 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3700 When searching for an entry in the mailcap file, Mutt-ng will search for the
3701 most useful entry for its purpose. For instance, if you are attempting to
3702 print an image/gif, and you have the following entries in your mailcap file,
3703 Mutt-ng will search for an entry with the print command:
3706 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3709 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3712 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) to denote
3713 two commands for viewing an attachment, one to be viewed automatically, the
3714 other to be viewed interactively from the attachment menu. In addition, you
3715 can then use the test feature to determine which viewer to use interactively
3716 depending on your environment.
3718 The Mutt Next Generation E-Mail Client 74
3720 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3721 text/html; lynx %s; nametemplate=%s.html
3722 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3724 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 75), Mutt-ng will choose the third entry
3725 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3726 program RunningX to determine if it should use the first entry. If the program
3727 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3729 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3731 The various commands defined in the mailcap files are passed to the /bin/sh
3732 shell using the system() function. Before the command is passed to /bin/sh -c,
3733 it is parsed to expand various special parameters with information from Mutt-
3734 ng. The keywords Mutt-ng expands are:
3737 As seen in the basic mailcap section, this variable is expanded to
3738 a filename specified by the calling program. This file contains
3739 the body of the message to view/print/edit or where the composing
3740 program should place the results of composition. In addition, the
3741 use of this keyword causes Mutt-ng to not pass the body of the mes-
3742 sage to the view/print/edit program on stdin.
3745 Mutt-ng will expand %t to the text representation of the content
3746 type of the message in the same form as the first parameter of the
3747 mailcap definition line, ie text/html or image/gif.
3750 Mutt-ng will expand this to the value of the specified parameter
3751 from the Content-Type: line of the mail message. For instance, if
3752 Your mail message contains:
3754 Content-Type: text/plain; charset=iso-8859-1
3756 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3757 metamail mailcap file uses this feature to test the charset to
3758 spawn an xterm using the right charset to view the message.
3761 This will be replaced by a %
3763 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3764 1524. The main purpose of these parameters is for multipart messages, which is
3765 handled internally by Mutt-ng.
3767 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3769 This mailcap file is fairly simple and standard:
3771 The Mutt Next Generation E-Mail Client 75
3773 # I'm always running X :)
3774 video/*; xanim %s > /dev/null
3775 image/*; xv %s > /dev/null
3777 # I'm always running netscape (if my computer had more memory, maybe)
3778 text/html; netscape -remote 'openURL(%s)'
3780 This mailcap file shows quite a number of examples:
3782 # Use xanim to view all videos Xanim produces a header on startup,
3783 # send that to /dev/null so I don't see it
3784 video/*; xanim %s > /dev/null
3786 # Send html to a running netscape by remote
3787 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3789 # If I'm not running netscape but I am running X, start netscape on the
3791 text/html; netscape %s; test=RunningX
3793 # Else use lynx to view it as text
3796 # This version would convert the text/html to text/plain
3797 text/html; lynx -dump %s; copiousoutput
3799 # I use enscript to print text in two columns to a page
3800 text/*; more %s; print=enscript -2Gr %s
3802 # Netscape adds a flag to tell itself to view jpegs internally
3803 image/jpeg;xv %s; x-mozilla-flags=internal
3805 # Use xv to view images if I'm running X
3806 # In addition, this uses the \ to extend the line and set my editor
3808 image/*;xv %s; test=RunningX; \
3811 # Convert images to text using the netpbm tools
3812 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3813 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3815 # Send excel spreadsheets to my NT box
3816 application/ms-excel; open.pl %s
3818 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3820 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3821 viewer defined in the mailcap file, Mutt-ng has support for automatically
3823 The Mutt Next Generation E-Mail Client 76
3825 viewing MIME attachments while in the pager.
3827 To work, you must define a viewer in the mailcap file which uses the copi-
3828 ousoutput option to denote that it is non-interactive. Usually, you also use
3829 the entry to convert the attachment to a text representation which you can view
3832 You then use the auto_view muttrc command to list the content-types that you
3833 wish to view automatically.
3835 For instance, if you set auto_view to:
3837 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3839 Mutt-ng could use the following mailcap entries to automatically view attach-
3840 ments of these types.
3842 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3843 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3844 application/x-gunzip; gzcat; copiousoutput
3845 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3846 application/postscript; ps2ascii %s; copiousoutput
3848 ``unauto_view'' can be used to remove previous entries from the autoview list.
3849 This can be used with message-hook to autoview messages based on size, etc.
3850 ``unauto_view *'' will remove all previous entries.
3852 _
\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
3854 Mutt-ng has some heuristics for determining which attachment of a multi-
3855 part/alternative type to display. First, mutt will check the alternative_order
3856 list to determine if one of the available types is preferred. The alterna-
3857 tive_order list consists of a number of MIME types in order, including support
3858 for implicit and explicit wildcards, for example:
3860 alternative_order text/enriched text/plain text application/postscript image/*
3862 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
3863 5.4 , page 75), and use that. Failing that, Mutt-ng will look for any text
3864 type. As a last attempt, mutt will look for any type it knows how to handle.
3866 To remove a MIME type from the alternative_order list, use the unalterna-
3869 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
3871 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
3873 The Mutt Next Generation E-Mail Client 77
3875 treated according to their mailcap entry. This option is designed to deal with
3876 binary types such as application/octet-stream. When an attachment's mime-type
3877 is listed in mime_lookup, then the extension of the filename will be compared
3878 to the list of extensions in the mime.types file. The mime-type associated
3879 with this extension will then be used to process the attachment according to
3880 the rules in the mailcap file and according to any other configuration options
3881 (such as auto_view) specified. Common usage would be:
3883 mime_lookup application/octet-stream application/X-Lotus-Manuscript
3885 In addition, the unmime_lookup command may be used to disable this feature for
3886 any particular mime-type if it had been set, for example, in a global muttrc.
3888 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
3890 First of all, mutt-ng contains no security holes included by intention but may
3891 contain unknown security holes. As a consequence, please run mutt-ng only with
3892 as few permissions as possible.
3894 Please do not run mutt-ng as the super user.
3896 When configuring mutt-ng, there're some points to note about secure setups.
3898 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
3899 mail user agents (in their default configuration) just by changing mutt-ng's
3900 configuration files: it then can execute arbitrary programs and scripts
3901 attached to messages, send out private data on its own, etc. Although this is
3902 not believed to the common type of setup, please read this chapter carefully.
3904 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
3906 Although mutt-ng can be told the various passwords for accounts, please never
3907 store passwords in configuration files. Besides the fact that the system's
3908 operator can always read them, you could forget to replace the actual password
3909 with asterisks when reporting a bug or asking for help via, for example, a
3910 mailing list so that your mail including your password could be archived by
3911 internet search engines, etc. Please never store passwords on disk.
3913 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
3915 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
3916 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.327 , page 166) variable can be used to
3917 change the default permissions of these files. Please only change it if you
3918 really know what you are doing. Also, a different location for these files may
3919 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.323 , page 165)
3922 The Mutt Next Generation E-Mail Client 78
3924 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
3926 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
3928 In the default configuration, mutt-ng will leak some information to the outside
3929 world when sending messages: the generation of Message-ID: headers includes a
3930 step counter which is increased (and rotated) with every message sent. If you'd
3931 like to hide this information probably telling others how many mail you sent in
3932 which time, you at least need to remove the %P expando from the default setting
3933 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.143 , page 120) variable. Please make sure
3934 that you really know how local parts of these Message-ID: headers are composed.
3936 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
3938 As mutt-ng be can be set up to be the mail client to handle mailto: style links
3939 in websites, there're security considerations, too. To keep the old behavior by
3940 default, mutt-ng will be strict in interpreting them which means that arbitrary
3941 header fields can be embedded in these links which could override existing
3942 header fields or attach arbitrary files. This may be problematic if the
3943 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.54 , page 98) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
3944 doesn't want to see header fields while editing the message.
3946 For example, following a link like
3948 mailto:joe@host?Attach=~/.gnupg/secring.gpg
3950 will send out the user's private gnupg keyring to joe@host if the user doesn't
3951 follow the information on screen carefully enough.
3953 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.311 , page 162) variable, mutt-
3956 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
3957 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
3959 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.54 , page 98) variable by force to
3960 let the user see all the headers (because they still may leak informa-
3963 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
3965 Mutt-ng in many places has to rely on external applications or for convenience
3966 supports mechanisms involving external applications.
3968 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3970 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
3971 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-
3972 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.116 , page 114) variable for
3975 These utilities may have a variety of security vulnerabilities, including
3977 The Mutt Next Generation E-Mail Client 79
3979 overwriting of arbitrary files, information leaks or other exploitable bugs.
3980 These vulnerabilities may go unnoticed by the user, especially when they are
3981 called automatically (and without interactive prompting) from the mailcap
3982 file(s). When using mutt-ng's autoview mechanism in combination with mailcap
3983 files, please be sure to...
3985 +
\bo manually select trustworth applications with a reasonable calling sequence
3987 +
\bo periodically check the contents of mailcap files, especially after soft-
3988 ware installations or upgrades
3990 +
\bo keep the software packages referenced in the mailcap file up to date
3992 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.117 , page 115) variable in its
3993 default state to restrict mailcap expandos to a safe set of characters
3995 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
3997 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4000 The same security considerations apply for these as for tools involved via
4001 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4002 compressed folders support if the uncompressed mailbox is too large for the
4003 disk it is saved to.)
4005 As already noted, most of these problems are not built in but caused by wrong
4006 configuration, so please check your configuration.
4008 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4010 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4012 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4013 mailbox. However, it is possible to read other mailboxes and to send messages
4014 from the command line as well.
4016 The Mutt Next Generation E-Mail Client 80
4019 -a attach a file to a message
4020 -b specify a blind carbon-copy (BCC) address
4021 -c specify a carbon-copy (Cc) address
4022 -D print the value of all variables on stdout
4023 -e specify a config command to be run after initialization files are read
4024 -f specify a mailbox to load
4025 -F specify an alternate file to read initialization commands
4026 -h print help on command line options
4027 -H specify a draft file from which to read a header and body
4028 -i specify a file to include in a message composition
4029 -m specify a default mailbox type
4030 -n do not read the system Muttngrc
4031 -p recall a postponed message
4032 -Q query a configuration variable
4033 -R open mailbox in read-only mode
4034 -s specify a subject (enclose in quotes if it contains spaces)
4035 -v show version number and compile-time definitions
4036 -x simulate the mailx(1) compose mode
4037 -y show a menu containing the files specified by the mailboxes command
4038 -z exit immediately if there are no messages in the mailbox
4039 -Z open the first folder with new message,exit immediately if none
4041 To read messages in a mailbox
4043 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4045 To compose a new message
4047 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-
4048 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4050 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4051 rect input from the file you wish to send. For example,
4053 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4055 This command will send a message to ``professor@bigschool.edu'' with a subject
4056 of ``data set for run #2''. In the body of the message will be the contents of
4057 the file ``~/run2.dat''.
4059 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4061 The Mutt Next Generation E-Mail Client 81
4064 ~b EXPR messages which contain EXPR in the message body
4065 ~B EXPR messages which contain EXPR in the whole message
4066 ~c USER messages carbon-copied to USER
4067 ~C EXPR message is either to: or cc: EXPR
4069 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4071 ~e EXPR message which contains EXPR in the ``Sender'' field
4073 ~f USER messages originating from USER
4074 ~g cryptographically signed messages
4075 ~G cryptographically encrypted messages
4076 ~H EXPR messages with a spam attribute matching EXPR
4077 ~h EXPR messages which contain EXPR in the message header
4078 ~k message contains PGP key material
4079 ~i ID message which match ID in the ``Message-ID'' field
4080 ~L EXPR message is either originated or received by EXPR
4081 ~l message is addressed to a known mailing list
4082 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4083 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4086 ~p message is addressed to you (consults alternates)
4087 ~P message is from you (consults alternates)
4088 ~Q messages which have been replied to
4090 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4091 ~S superseded messages
4092 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4094 ~t USER messages addressed to USER
4096 ~v message is part of a collapsed thread.
4097 ~V cryptographically verified messages
4098 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4099 (if compiled with NNTP support)
4100 ~x EXPR messages which contain EXPR in the `References' field
4101 ~y EXPR messages which contain EXPR in the `X-Label' field
4102 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4103 ~= duplicated messages (see $duplicate_threads)
4104 ~$ unreferenced messages (requires threaded view)
4105 ~* ``From'' contains realname and (syntactically) valid
4106 address (excluded are addresses matching against
4107 alternates or any alias)
4109 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
4110 44). Special attention has to be made when using regular expressions inside of
4111 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4112 level of backslash (\), which is normally used for quoting. If it is your
4113 intention to use a backslash in the regular expression, you will need to use
4114 two backslashes instead (\\).
4116 The Mutt Next Generation E-Mail Client 82
4118 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4120 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4122 The following are the commands understood by mutt.
4124 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 63) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4126 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.3 , page 23) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4128 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.3 , page 23) [ * | _
\bk_
\be_
\by ... ]
4130 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.10 , page 30) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4132 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.10 , page 30) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4134 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4136 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4138 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4140 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4142 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4144 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4146 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.5 , page 26) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4148 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4150 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.8 , page 27) _
\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 ]
4152 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.8 , page 27) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4154 +
\bo _
\be_
\bx_
\be_
\bc (section 3.24 , page 37) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4156 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 35) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4158 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4160 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 26) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4162 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.16 , page 35) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4164 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.16 , page 35) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4166 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.5 , page 26) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4168 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.9 , page 30) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4170 The Mutt Next Generation E-Mail Client 83
4172 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.9 , page 30) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4174 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4176 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4178 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.7 , page 27) _
\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 ]
4180 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.14 , page 33) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4182 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4184 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 37) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4186 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4188 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4190 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.8 , page 27) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4192 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.8 , page 27) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4194 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4196 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4198 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4200 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 37) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4202 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.23 , page 37) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4204 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.27 , page 41) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4206 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4208 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.25 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4210 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.25 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4212 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4214 +
\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
4216 +
\bo _
\bs_
\be_
\bt (section 3.27 , page 41) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4218 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.27 , page 41) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4220 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page 42) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4222 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.26 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4224 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.26 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4226 The Mutt Next Generation E-Mail Client 84
4228 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4230 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4232 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.27 , page 41) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4234 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.29 , page 42) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4236 _
\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
4238 The following list contains all variables which, in the process of providing
4239 more consistency, have been renamed and are partially even removed already. The
4240 left column contains the old synonym variables, the right column the full/new
4243 The Mutt Next Generation E-Mail Client 85
4245 edit_hdrs edit_headers
4246 forw_decode forward_decode
4247 forw_format forward_format
4248 forw_quote forward_quote
4249 hdr_format index_format
4250 indent_str indent_string
4251 mime_fwd mime_forward
4252 msg_format message_format
4253 pgp_autosign crypt_autosign
4254 pgp_autoencrypt crypt_autoencrypt
4255 pgp_replyencrypt crypt_replyencrypt
4256 pgp_replysign crypt_replysign
4257 pgp_replysignencrypted crypt_replysignencrypted
4258 pgp_verify_sig crypt_verify_sig
4259 pgp_create_traditional pgp_autoinline
4260 pgp_auto_traditional pgp_replyinline
4261 forw_decrypt forward_decrypt
4262 smime_sign_as smime_default_key
4263 post_indent_str post_indent_string
4264 print_cmd print_command
4265 shorten_hierarchy sidebar_shorten_hierarchy
4266 ask_followup_to nntp_ask_followup_to
4267 ask_x_comment_to nntp_ask_x_comment_to
4268 catchup_newsgroup nntp_catchup
4269 followup_to_poster nntp_followup_to_poster
4270 group_index_format nntp_group_index_format
4272 mime_subject nntp_mime_subject
4273 news_cache_dir nntp_cache_dir
4274 news_server nntp_host
4276 nntp_poll nntp_mail_check
4277 pop_checkinterval pop_mail_check
4278 post_moderated nntp_post_moderated
4279 save_unsubscribed nntp_save_unsubscribed
4280 show_new_news nntp_show_new_news
4281 show_only_unread nntp_show_only_unread
4282 x_comment_to nntp_x_comment_to
4283 smtp_auth_username smtp_user
4284 smtp_auth_password smtp_pass
4286 The contrib subdirectory contains a script named update-config.pl which eases
4289 A complete list of current variables follows.
4291 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4297 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4299 The Mutt Next Generation E-Mail Client 86
4301 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4302 subject given at the subject prompt will never be aborted.
4304 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4310 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4311 body if no changes are made to the file (this check only happens after the
4312 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4314 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4318 Default: '~/.muttngrc'
4320 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4321 tion 2.5.4 , page 11)'' function.
4323 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4324 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page 42)'' command for it to be executed.
4326 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4330 Default: '%4n %2f %t %-10a %r'
4332 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4333 ing printf(3)-style sequences are available:
4339 flags - currently, a 'd' for an alias marked for deletion
4345 address which alias expands to
4348 character which indicates if the alias is tagged for inclusion
4350 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4356 The Mutt Next Generation E-Mail Client 87
4358 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4359 or base64 encoding when sending mail.
4361 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4367 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4368 sages) are to be interpreted. Messages containing these codes are rare, but if
4369 this option is set, their text will be colored accordingly. Note that this may
4370 override your color choices, and even present a security problem, since a mes-
4371 sage could include a line like ``[-- PGP output follows ...' and give it the
4372 same color as your attachment color.
4374 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4380 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4381 instead of highlighting the whole line. On slow network or modem links this
4382 will make response faster because there is less that has to be redrawn on the
4383 screen when moving to the next or previous entries in the menu.
4385 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4391 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4392 attachment trees, instead of the default ACS characters.
4394 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4400 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4401 editing an outgoing message.
4403 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bk_
\bc_
\bc
4409 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4410 the body of an outgoing message.
4412 The Mutt Next Generation E-Mail Client 88
4414 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4420 This variable is a colon-separated list of character encoding schemes for mes-
4421 sages without character encoding indication. Header field values and message
4422 body content without character encoding indication would be assumed that they
4423 are written in one of this list. By default, all the header fields and message
4424 body without any charset indication are assumed to be in us-ascii.
4426 For example, Japanese users might prefer this:
4428 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4430 However, only the first content is valid for the message body. This variable
4431 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.312 , page 162) is unset.
4433 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4437 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4439 This variable describes the format of the ``attachment'' menu. The following
4440 printf(3)-style sequences are understood:
4446 requires charset conversion (n or c)
4455 MIME Content-Transfer-Encoding: header field
4461 MIME Content-Disposition: header field (I=inline, A=attachment)
4469 The Mutt Next Generation E-Mail Client 89
4481 graphic tree characters
4484 unlink (=to delete) flag
4487 right justify the rest of the string and pad with character 'X'
4490 pad to the end of the line with character 'X'
4492 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4498 The separator to add between attachments when operating (saving, printing, pip-
4499 ing, etc) on a list of tagged attachments.
4501 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4507 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4508 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4509 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.13 ,
4510 page 89)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4511 operate on the attachments one by one.
4513 _
\b7_
\b._
\b4_
\b._
\b1_
\b5 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4517 Default: 'On %d, %n wrote:'
4519 This is the string that will precede a message which has been included in a
4520 reply. For a full listing of defined printf(3)-like sequences see the section
4521 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111)''.
4523 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4525 The Mutt Next Generation E-Mail Client 90
4531 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4532 all tagged messages (if there are any). When unset, you must first use the
4533 ``tag-prefix'' function (default: ';') to make the next function apply to all
4536 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4542 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.54 , page 98)'', Mutt-ng will
4543 skip the initial send-menu and allow you to immediately begin editing the body
4544 of your message. The send-menu may still be accessed once you have finished
4545 editing the body of your message.
4547 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.60 , page 99)''.
4549 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\bb_
\be_
\be_
\bp
4555 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4557 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4563 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4564 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4565 tion 7.4.18 , page 90)'' variable.
4567 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4573 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4574 you don't get asked if you want to bounce a message. Setting this variable to
4575 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4578 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4582 The Mutt Next Generation E-Mail Client 91
4586 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4587 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4589 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4595 When this variable is set, mutt will place the cursor at the beginning of the
4596 current line in menus, even when the arrow_cursor variable is unset, making it
4597 easier for blind persons using Braille displays to follow these menus. The
4598 option is disabled by default because many visual terminals don't permit making
4599 the cursor invisible.
4601 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4605 Default: '~/.mutt_certificates'
4607 Availability: SSL or GNUTLS
4609 This variable specifies the file where the certificates you trust are saved.
4610 When an unknown certificate is encountered, you are asked if you accept it or
4611 not. If you accept it, the certificate can also be saved in this file and fur-
4612 ther connections are automatically accepted.
4614 You can also manually add CA certificates in this file. Any server certificate
4615 that is signed with one of these CA certificates are also automatically
4618 Example: set certificate_file=~/.muttng/certificates
4620 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4626 Character set your terminal uses to display and enter textual data.
4628 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4634 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4636 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4637 Especially with MH mailboxes, this operation can take quite some time since it
4639 The Mutt Next Generation E-Mail Client 92
4641 involves scanning the directory and checking each file to see if it has already
4642 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4645 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4651 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4654 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4658 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4660 Controls the format of the status line displayed in the ``compose'' menu. This
4661 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.309 , page 160)'', but has
4662 its own set of printf(3)-like sequences:
4665 total number of attachments
4671 approximate size (in bytes) of the current message
4674 Mutt-ng version string
4676 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.309 , page 160)''
4677 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.27 ,
4680 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4686 When defined, Mutt-ng will recode commands in rc files from this encoding.
4688 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4694 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4696 The Mutt Next Generation E-Mail Client 93
4700 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4706 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4707 box which does not yet exist before creating it.
4709 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4715 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4716 many seconds if the connection is not able to be established. A negative value
4717 causes Mutt-ng to wait indefinitely for the connection to succeed.
4719 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4723 Default: 'text/plain'
4725 Sets the default Content-Type: header field for the body of newly composed mes-
4728 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bp_
\by
4734 This variable controls whether or not copies of your outgoing messages will be
4735 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.231 , page
4736 141)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 , page 144)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4737 7.4.68 , page 101)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 35)''.
4739 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4745 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4746 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4747 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4748 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
4749 7.4.278 , page 152)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4750 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4753 The Mutt Next Generation E-Mail Client 94
4755 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4761 This variable controls whether or not Mutt-ng may automatically enable PGP
4762 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
4763 7.4.34 , page 93)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.38 , page 94)'',
4764 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.36 , page 94)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4765 7.4.39 , page 94)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.278 , page 152)''.
4767 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4773 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4774 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4775 signing is not required or encryption is requested as well. If
4776 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.278 , page 152)'' is _
\bs_
\be_
\bt, then OpenSSL is
4777 used instead to create S/MIME messages and settings can be overridden by use of
4778 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4780 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4786 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4787 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
4788 7.4.34 , page 93)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.38 , page 94)'',
4789 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.36 , page 94)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4790 7.4.39 , page 94)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.278 , page 152)''.
4792 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4798 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
4799 encrypted. (Crypto only)
4801 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
4807 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
4809 The Mutt Next Generation E-Mail Client 95
4811 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
4814 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd
4820 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
4821 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
4822 7.4.38 , page 94)'', because it allows you to sign all messages which are
4823 automatically encrypted. This works around the problem noted in
4824 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 94)'', that Mutt-ng is not able to
4825 find out whether an encrypted message is also signed. (Crypto only)
4827 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
4833 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
4834 S/MIME output, so spoofing such lines is more difficult. If you are using col-
4835 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
4838 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
4844 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
4845 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
4846 will be used instead of the classic code.
4848 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
4849 won't have any effect when used interactively.
4851 _
\b7_
\b._
\b4_
\b._
\b4_
\b3 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
4857 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
4858 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
4859 cryptographic signatures. (Crypto only)
4861 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4865 The Mutt Next Generation E-Mail Client 96
4867 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
4869 This variable controls the format of the date printed by the ``%d'' sequence in
4870 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111)''. This is passed to strftime(3)
4871 to process the date.
4873 Unless the first character in the string is a bang (``!''), the month and week
4874 day names are expanded according to the locale specified in the variable
4875 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.114 , page 114)''. If the first character in the string
4876 is a bang, the bang is discarded, and the month and week day names in the rest
4877 of the string are expanded in the _
\bC locale (that is in US English).
4879 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
4883 Default: '~f %s !~P | (~P ~C %s)'
4885 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
4886 will be interpreted if they are specified with only a simple regexp, instead of
4887 a matching pattern. The hooks are expanded when they are declared, so a hook
4888 will be interpreted according to the value of this variable at the time the
4889 hook is declared. The default value matches if the message is either from a
4890 user matching the regular expression given, or if it is from you (if the from
4891 address matches ``alternates'') and is to or cc'ed to a user matching the given
4894 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bd_
\be_
\bl_
\be_
\bt_
\be
4900 Controls whether or not messages are really deleted when closing or synchroniz-
4901 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
4902 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
4903 be kept in the mailbox.
4905 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
4911 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
4912 tion. This applies when you either explicitly delete a message, or when you
4913 save it to another folder.
4915 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
4921 The Mutt Next Generation E-Mail Client 97
4923 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
4924 subparts of individual messages in a multipart/digest. To see these subparts,
4925 press 'v' on that menu.
4927 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
4933 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
4934 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.49 ,
4935 page 97), and the filtered message is read from the standard output.
4937 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
4941 Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
4943 Availability: Standalone and Dotlock
4945 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
4947 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
4953 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
4954 or in connection with the SMTP support via libESMTP.
4956 This variable sets the request for when notification is returned. The string
4957 consists of a comma separated list (no spaces!) of one or more of the follow-
4958 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
4959 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
4960 notified of successful transmission.
4962 Example: set dsn_notify='failure,delay'
4964 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
4970 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
4971 or in connection with the SMTP support via libESMTP.
4973 This variable controls how much of your message is returned in DSN messages.
4974 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
4975 return the full message.
4977 The Mutt Next Generation E-Mail Client 98
4979 Example: set dsn_return=hdrs
4981 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
4987 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
4988 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
4989 indicate that it thinks they are duplicates of each other with an equals sign
4990 in the thread diagram.
4992 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4998 This option allows you to edit the header of your outgoing messages along with
4999 the body of your message.
5001 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5007 This variable specifies which editor is used by Mutt-ng. It defaults to the
5008 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5009 if neither of those are set.
5011 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5017 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5018 string ``From '' (note the trailing space) in the beginning of a line. Useful
5019 to avoid the tampering certain mail delivery and transport agents tend to do
5022 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5030 The file which includes random data that is used to initialize SSL library
5033 The Mutt Next Generation E-Mail Client 99
5035 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5041 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5042 ``From:'' header field. Note that this information is passed to the sendmail
5043 command using the ``-f' command line switch, so don't set this option if you
5044 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.248 , page 145) yourself, or
5045 if the sendmail on your machine doesn't support that command line switch.
5047 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5053 Escape character to use for functions in the builtin editor.
5055 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5061 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5062 ing to messages, and the initial prompt for subject is skipped when forwarding
5065 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.17 , page
5066 90)'' variable is _
\bs_
\be_
\bt.
5068 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5074 This variable controls whether or not attachments on outgoing messages are
5075 saved along with the main body of your message.
5077 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5083 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5084 when the actual message is encrypted and/or signed. (PGP only)
5086 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5090 The Mutt Next Generation E-Mail Client 100
5094 This variable is a colon-separated list of character encoding schemes for text
5095 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.24 , page 91) value will
5096 be used instead. For example, the following configuration would work for
5097 Japanese text handling:
5099 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5101 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5104 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5110 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5111 beginning of a pathname will be expanded to the value of this variable. Note
5112 that if you change this variable from the default value you need to make sure
5113 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5114 ables since expansion takes place during the ``set'' command.
5116 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5120 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5122 This variable allows you to customize the file browser display to your personal
5123 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page
5124 111)'', but has its own set of printf(3)-like sequences:
5130 date/time folder was last modified
5139 group name (or numeric gid, if missing)
5142 number of hard links
5145 N if folder has new mail, blank otherwise
5147 The Mutt Next Generation E-Mail Client 101
5153 * if the file is tagged, blank otherwise
5156 owner name (or numeric uid, if missing)
5159 right justify the rest of the string and pad with character 'X'
5162 pad to the end of the line with character 'X'
5164 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5170 Controls whether or not the Mail-Followup-To: header field is generated when
5171 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5172 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5173 3.12 , page 32)'' commands or detected by common mailing list headers.
5175 This field has two purposes. First, preventing you from receiving duplicate
5176 copies of replies to messages which you send to mailing lists. Second, ensuring
5177 that you do get a reply separately for any messages sent to known lists to
5178 which you are not subscribed. The header will contain only the list's address
5179 for subscribed lists, and both the list address and your own email address for
5180 unsubscribed lists. Without this header, a group reply to your message sent to
5181 a subscribed list will be sent to both the list and your address, resulting in
5182 two copies of the same email for you.
5184 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5190 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
5191 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
5192 already known to have new mail.
5194 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.322 , page 164)'',
5195 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.115 , page 114)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5196 7.4.99 , page 108)''.
5198 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5204 The Mutt Next Generation E-Mail Client 102
5206 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 , page 144)'',
5207 except that Mutt-ng will store a copy of your outgoing message by the username
5208 of the address you are sending to even if that mailbox does not exist.
5210 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.231 , page 141)'' variable.
5212 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5218 Controls the decoding of complex MIME messages into text/plain when forwarding
5219 a message. The message header is also RFC2047 decoded. This variable is only
5220 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.137 , page 118)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5221 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.138 , page 119)'' is used instead.
5223 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5229 Controls the handling of encrypted messages when forwarding a message. When
5230 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5231 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.137 , page 118)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5232 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.138 , page 119)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5234 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5240 This quadoption controls whether or not the user is automatically placed in the
5241 editor when forwarding messages. For those who always want to forward with no
5242 modification, use a setting of _
\bn_
\bo.
5244 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5250 This variable controls the default subject when forwarding a message. It uses
5251 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page
5254 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5260 The Mutt Next Generation E-Mail Client 103
5262 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5263 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.137 , page 118)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5264 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.109 , page 111)''.
5266 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\br_
\bo_
\bm
5268 Type: e-mail address
5272 This variable contains a default from address. It can be overridden using
5273 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.237 , page
5274 143)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.331 , page
5277 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5278 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5279 takes this email address.
5281 Defaults to the contents of the environment variable $EMAIL.
5283 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5285 Type: regular expression
5289 A regular expression used by Mutt-ng to parse the GECOS field of a password
5290 entry when expanding the alias. By default the regular expression is set to
5291 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5292 the GECOS field contains a string like 'lastname, firstname' then you should
5293 do: set gecos_mask='.*'.
5295 This can be useful if you see the following behavior: you address a e-mail to
5296 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5297 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5298 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5299 to ``Franklin, Steve''.
5301 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bh_
\bd_
\br_
\bs
5307 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 ,
5308 page 34)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5309 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5310 defined header fields are added to every new message.
5312 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5316 The Mutt Next Generation E-Mail Client 104
5320 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5321 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.337 , page
5322 168)'' setting applies.
5324 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5330 Availability: Header Cache
5332 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.78 , page 104) variable points to the header
5335 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.78 , page 104) points to a directory it will
5336 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5337 7.4.78 , page 104) points to a file that file will be a single global header
5338 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5340 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5346 If enabled the header cache will be compressed. So only one fifth of the usual
5347 diskspace is used, but the uncompression can result in a slower open of the
5350 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bh_
\be_
\bl_
\bp
5356 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5357 by each menu are displayed on the first line of the screen.
5359 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5360 sequence rather than a single keystroke. Also, the help line may not be
5361 updated if a binding is changed while Mutt-ng is running. Since this variable
5362 is primarily aimed at new users, neither of these should present a major prob-
5365 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5371 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5373 The Mutt Next Generation E-Mail Client 105
5375 7.4.89 , page 106)'' variable when adding the domain part to addresses. This
5376 variable does not affect the generation of Message-ID: header fields, and it
5377 will not lead to the cut-off of first-level domains.
5379 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5385 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5386 limiting, in the thread tree.
5388 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5394 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5397 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5403 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5404 have the same subject as their parent or closest previously displayed sibling.
5406 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5412 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5413 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5414 _
\bi_
\bn_
\bg (section 7.4.83 , page 105) is set, this option will have no effect.
5416 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5422 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5423 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.82 ,
5424 page 105) is _
\bs_
\be_
\bt, this option will have no effect.
5426 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5430 The Mutt Next Generation E-Mail Client 106
5434 This variable controls the size (in number of strings remembered) of the string
5435 history buffer. The buffer is cleared each time the variable is changed.
5437 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5443 This variable controls whether or not a Mail-Followup-To: header field is hon-
5444 ored when group-replying to a message.
5446 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5452 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5453 during generation of Message-Id: headers.
5455 Please be sure to really know what you are doing when changing this variable to
5456 configure a custom domain part of Message-IDs.
5458 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5464 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5465 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5466 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5467 header field was set by the mailing list to automate responses to the list, and
5468 will ignore this field. To direct a response to the mailing list when this
5469 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
5470 sender and the list.
5472 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5480 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5481 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5482 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5483 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5484 eter is case-insensitive.
5486 The Mutt Next Generation E-Mail Client 107
5488 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5489 ods, in order from most-secure to least-secure.
5491 Example: set imap_authenticators='gssapi:cram-md5:login'
5493 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5494 ous methods are unavailable. If a method is available but authentication fails,
5495 Mutt-ng will not connect to the IMAP server.
5497 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5503 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5504 connection, and add them to the set of mailboxes it polls for new mail. See
5505 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.14 , page 33)'' command.
5507 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5515 This contains the list of characters which you would like to treat as folder
5516 separators for displaying IMAP paths. In particular it helps in using the '='
5517 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.64 , page 100) variable.
5519 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5527 Mutt-ng requests these header fields in addition to the default headers (``DATE
5528 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5529 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5530 ``index'' menu. You may want to add more headers for spam detection.
5532 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5534 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5542 The Mutt Next Generation E-Mail Client 108
5544 You normally want to see your personal folders alongside your INBOX in the IMAP
5545 browser. If you see something else, you may set this variable to the IMAP path
5548 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5556 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5557 wait before polling open IMAP connections, to prevent the server from closing
5558 them before Mutt-ng has finished with them.
5560 The default is well within the RFC-specified minimum amount of time (30 min-
5561 utes) before a server is allowed to do this, but in practice the RFC does get
5562 violated every now and then.
5564 Reduce this number if you find yourself getting disconnected from your IMAP
5565 server due to inactivity.
5567 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5575 This variable configures whether IMAP folder browsing will look for only sub-
5576 scribed folders or all folders. This can be toggled in the IMAP browser with
5577 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5579 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5587 Your login name on the IMAP server.
5589 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.105 , page
5592 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5598 The Mutt Next Generation E-Mail Client 109
5600 This variable configures how often (in seconds) Mutt-ng should look for new
5601 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.115 ,
5602 page 114)'' variable to generate less traffic and get more accurate information
5605 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5613 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5614 you for your password when you invoke the fetch-mail function.
5616 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5617 machine, because the superuser can read your configuration even if you are the
5618 only one who can read the file.
5620 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5628 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5629 Mutt-ng will only check for new mail over existing IMAP connections. This is
5630 useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
5631 cation, or if opening the connection is slow.
5633 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5641 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5642 fetch a message from the server. This is generally a good thing, but can make
5643 closing an IMAP folder somewhat slower. This option exists to appease speed
5646 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5654 The Mutt Next Generation E-Mail Client 110
5656 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5659 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5667 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5668 messages. Since these messages are often harmless, or generated due to configu-
5669 ration problems on the server which are out of the users' hands, you may wish
5670 to suppress them at some point.
5672 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5680 The name of the user whose mail you intend to access on the IMAP server.
5682 This variable defaults to your user name on the local machine.
5684 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5690 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5691 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5692 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5693 convert the body part to text form.
5695 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5701 Controls whether or not a copy of the message(s) you are replying to is
5702 included in your reply.
5704 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5710 The Mutt Next Generation E-Mail Client 111
5712 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5713 sage you are replying.
5715 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5721 Specifies the string to prepend to each line of text quoted in a message to
5722 which you are replying. You are strongly encouraged not to change this value,
5723 as it tends to agitate the more fanatical netizens.
5725 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5729 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5731 This variable allows you to customize the message index display to your per-
5734 ``Format strings'' are similar to the strings used in the ``C'' function
5735 printf(3) to format output (see the man page for more detail). The following
5736 sequences are defined in Mutt-ng:
5739 address of the author
5742 reply-to address (if present; otherwise: address of author)
5745 filename of the original message folder (think mailBox)
5748 the list to which the letter was sent, or else the folder name
5752 number of characters (bytes) in the message
5755 current message number
5758 date and time of the message in the format specified by ``date_for-
5759 mat'' converted to sender's time zone
5762 date and time of the message in the format specified by ``date_for-
5763 mat'' converted to the local time zone
5765 The Mutt Next Generation E-Mail Client 112
5768 current message number in thread
5771 number of messages in current thread
5774 entire From: line (address + real name)
5777 author name, or recipient name if the message is from you
5780 spam attribute(s) of this message
5783 newsgroup name (if compiled with nntp support)
5786 message-id of the current message
5789 number of lines in the message (does not work with maildir, mh, and
5790 possibly IMAP folders)
5793 If an address in the To or CC header field matches an address
5794 defined by the users ``subscribe'' command, this displays 'To
5795 <list-name>', otherwise the same as %F.
5798 total number of message in the mailbox
5801 number of hidden messages if the thread is collapsed.
5807 author's real name (or address if missing)
5810 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
5811 the message: list name or recipient name if no list
5814 subject of the message
5817 status of the message (N/D/d/!/r/*)
5820 `to:' field (recipients)
5822 The Mutt Next Generation E-Mail Client 113
5825 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.324 ,
5829 user (login) name of the author
5832 first name of the author, or the recipient if the message is from
5836 name of organization of author (`organization:' field)
5839 `x-label:' field, if present
5842 `x-label' field, if present, and (1) not at part of a thread tree,
5843 (2) at the top of a thread, or (3) `x-label' is different from pre-
5844 ceding message's `x-label'.
5847 message status flags
5850 the date and time of the message is converted to sender's time
5851 zone, and ``fmt'' is expanded by the library function ``strftime'';
5852 a leading bang disables locales
5855 the date and time of the message is converted to the local time
5856 zone, and ``fmt'' is expanded by the library function ``strftime'';
5857 a leading bang disables locales
5860 the local date and time when the message was received. ``fmt'' is
5861 expanded by the library function ``strftime''; a leading bang dis-
5865 the current local time. ``fmt'' is expanded by the library function
5866 ``strftime''; a leading bang disables locales.
5869 right justify the rest of the string and pad with character 'X'
5872 pad to the end of the line with character 'X'
5874 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.324 , page 165)''.
5876 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
5878 The Mutt Next Generation E-Mail Client 114
5884 How to invoke ispell (GNU's spell-checking software).
5886 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
5892 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
5893 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.125 , page 116)'' mailbox, or as a result of
5894 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33)'' command.
5896 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5902 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
5903 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
5904 will ask if you really intended to reply to the author only.
5906 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
5912 The locale used by strftime(3) to format dates. Legal values are the strings
5913 your system accepts for the locale variable LC_TIME.
5915 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5921 This variable configures how often (in seconds) Mutt-ng should look for new
5924 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
5927 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
5933 This variable specifies which files to consult when attempting to display MIME
5935 The Mutt Next Generation E-Mail Client 115
5937 bodies not directly supported by Mutt-ng.
5939 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
5945 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
5946 well-defined set of safe characters. This is the safe setting, but we are not
5947 sure it doesn't break some more advanced MIME stuff.
5949 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!
5951 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\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
5957 Availability: Header Cache
5959 Check for Maildir unaware programs other than Mutt-ng having modified maildir
5960 files when the header cache is in use. This incurs one stat(2) per message
5961 every time the folder is opened.
5963 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
5969 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
5970 flag instead of physically deleted.
5972 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
5973 effect on other mailbox types.
5975 It is similiar to the trash option.
5977 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
5983 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
5984 mailbox without reading them.
5986 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
5987 up with an 'O' next to them in the ``index'' menu, indicating that they are
5990 The Mutt Next Generation E-Mail Client 116
5992 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
5998 Controls the display of wrapped lines in the internal pager. If set, a ``+''
5999 marker is displayed at the beginning of wrapped lines. Also see the
6000 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.264 , page 149)'' variable.
6002 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bs_
\bk
6004 Type: regular expression
6008 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6009 operator ``!''. Only files whose names match this mask will be shown. The
6010 match is always case-sensitive.
6012 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6018 When set non-zero, this specifies the maximum number of recipient header lines
6019 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6020 case the number of lines exeeds its value, the last line will have 3 dots
6023 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6029 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6030 is limited to this length. A value of 0 (which is also the default) means that
6031 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6032 (section 7.4.339 , page 168).
6034 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\bb_
\bo_
\bx
6040 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6041 7.4.298 , page 157)'' folder will be appended.
6043 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6047 The Mutt Next Generation E-Mail Client 117
6051 The default mailbox type used when creating new folders. May be any of mbox,
6052 MMDF, MH and Maildir.
6054 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6060 This variable controls the number of lines of context that are given when
6061 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.168 , page
6064 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6070 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6071 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6072 entry may move off the bottom.
6074 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6080 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6081 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6082 vious page of the menu is displayed (useful for slow links to avoid many
6085 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6091 This is the string displayed in the ``attachment'' menu for attachments of type
6092 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6093 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111)''.
6095 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6101 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6102 if the user had pressed the ESC key and whatever key remains after having the
6104 The Mutt Next Generation E-Mail Client 118
6106 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6107 then this is treated as if the user had pressed ESC then ``x''. This is
6108 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6109 the ASCII character ``x''.
6111 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\be_
\bt_
\bo_
\bo
6117 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6118 from the list of recipients when replying to a message.
6120 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6126 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6127 _
\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-
6128 able is set, the message files will simply be deleted.
6130 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6136 The name of the MH sequence used for flagged messages.
6138 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6144 The name of the MH sequence used to tag replied messages.
6146 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6152 The name of the MH sequence used for unseen messages.
6154 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6160 The Mutt Next Generation E-Mail Client 119
6162 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6163 part instead of included in the main body of the message.
6165 This is useful for forwarding MIME messages so the receiver can properly view
6166 the message as it was delivered to you. If you like to switch between MIME and
6167 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6169 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.69 , page 102)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6170 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.138 , page 119)''.
6172 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6178 Controls the decoding of complex MIME messages into text/plain when forwarding
6179 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.137 , page 118)'' is _
\bs_
\be_
\bt. Other-
6180 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.69 , page 102)'' is used instead.
6182 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6188 When forwarding multiple attachments of a MIME message from the recvattach
6189 menu, attachments which cannot be decoded in a reasonable manner will be
6190 attached to the newly composed message if this option is set.
6192 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6196 Default: '%4n %c %-16s %a'
6198 Availability: Mixmaster
6200 This variable describes the format of a remailer line on the mixmaster chain
6201 selection screen. The following printf(3)-like sequences are supported:
6204 The running number on the menu.
6207 Remailer capabilities.
6210 The remailer's short name.
6213 The remailer's e-mail address.
6215 The Mutt Next Generation E-Mail Client 120
6217 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6221 Default: 'mixmaster'
6223 Availability: Mixmaster
6225 This variable contains the path to the Mixmaster binary on your system. It is
6226 used with various sets of parameters to gather the list of known remailers, and
6227 to finally send a message through the mixmaster chain.
6229 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bo_
\bv_
\be
6235 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6236 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.125 , page 116)'' mailbox, or as a result of a
6237 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33)'' command.
6239 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6243 Default: '%Y%m%d%h%M%s.G%P%p'
6245 This is the format for the ``local part'' of the Message-Id: header field gen-
6246 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6247 generated. The '%' character marks that certain data will be added to the
6248 string, similar to printf(3). The following characters are allowed:
6251 the current day of month
6263 the current UNIX timestamp (octal)
6269 the current Message-ID prefix (a character rotating with every Mes-
6270 sage-ID being generated)
6272 The Mutt Next Generation E-Mail Client 121
6275 a random integer value (decimal)
6278 a random integer value (hexadecimal)
6284 the current UNIX timestamp (decimal)
6287 the current UNIX timestamp (hexadecimal)
6290 the current year (Y2K compliant)
6295 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6296 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6298 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6304 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6305 threads to fit on the screen.
6307 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6315 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6316 ing the body of an outgoing news article.
6318 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6326 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6327 ing the body of an outgoing news article.
6329 The Mutt Next Generation E-Mail Client 122
6331 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6335 Default: '~/.muttng'
6339 This variable points to directory where Mutt-ng will cache news article head-
6340 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6341 when you enter a newsgroup.
6343 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6344 cally increases speed and lowers traffic.
6346 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6354 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6355 when you leaving it.
6357 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6365 This variable controls how many news articles to cache per newsgroup (if
6366 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.147 , page 121)) and how
6367 many news articles to show in the ``index'' menu.
6369 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.149 ,
6370 page 122), all older ones will be removed/not shown in the index.
6372 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6380 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6381 header field, a follow-up to the newsgroup is not permitted. The message will
6382 be mailed to the submitter of the message via mail.
6384 The Mutt Next Generation E-Mail Client 123
6386 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6390 Default: '%4C %M%N %5s %-45.45f %d'
6394 This variable allows you to customize the newsgroup browser display to your
6395 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 ,
6396 page 111)'', but has its own set of printf(3)-like sequences:
6398 %C current newsgroup number
6399 %d description of newsgroup (retrieved from server)
6401 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6402 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6403 %n number of new articles in newsgroup
6404 %s number of unread articles in newsgroup
6405 %>X right justify the rest of the string and pad with character "X"
6406 %|X pad to the end of the line with character "X"
6408 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6416 This variable specifies the name (or address) of the NNTP server to be used.
6418 It defaults to the value specified via the environment variable $NNTPSERVER or
6419 contained in the file /etc/nntpserver.
6421 You can also specify a username and an alternative port for each newsserver,
6424 [nntp[s]://][username[:password]@]newsserver[:port]
6426 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6427 security risk since the superuser of your machine may read it regardless of the
6430 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6438 The Mutt Next Generation E-Mail Client 124
6440 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6441 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6442 lowing printf(3)-style sequence is understood:
6446 Example: set inews='/usr/local/bin/inews -hS'
6448 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6456 This variable controls whether or not descriptions for newsgroups are to be
6457 loaded when subscribing to a newsgroup.
6459 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6467 The time in seconds until any operations on a newsgroup except posting a new
6468 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6469 each operation in index (stepping, read article, etc.).
6471 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6479 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6480 encoded according to RFC2047.
6482 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6484 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6488 Default: '~/.newsrc'
6492 The Mutt Next Generation E-Mail Client 125
6494 This file contains information about subscribed newsgroup and articles read so
6497 To ease the use of multiple news servers, the following printf(3)-style
6498 sequence is understood:
6502 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6510 Your password for NNTP account.
6512 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6513 the superuser of your machine may read it regardless of the file's permissions.
6515 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6523 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6524 sions to post (e.g. moderated).
6526 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6527 is totally read-only, that posting will not have any effect.
6529 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6537 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6538 was connection lost.
6540 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6546 The Mutt Next Generation E-Mail Client 126
6550 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6551 file and into the news cache.
6553 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6561 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6562 browser. Otherwise, it will be done only once for a newsserver. Also controls
6563 whether or not the number of new articles of subscribed newsgroups will be
6566 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6574 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6575 played in the newsgroup browser.
6577 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6585 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6586 tification, Mutt-ng will prompt you for your account name.
6588 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6596 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6597 name of the original article author) to articles that you followup to.
6599 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6603 The Mutt Next Generation E-Mail Client 127
6607 This specifies the operating system name for the User-Agent: header field. If
6608 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6609 returns. If uname(2) fails, ``UNIX'' will be used.
6611 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6613 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bp_
\ba_
\bg_
\be_
\br
6619 This variable specifies which pager you would like to use to view messages.
6620 ``builtin'' means to use the builtin pager, otherwise this variable should
6621 specify the pathname of the external pager you would like to use.
6623 Using an external pager may have some disadvantages: Additional keystrokes are
6624 necessary because you can't call Mutt-ng functions directly from the pager, and
6625 screen resizes cause lines longer than the screen width to be badly formatted
6628 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6634 This variable controls the number of lines of context that are given when dis-
6635 playing the next or previous page in the internal pager. By default, Mutt-ng
6636 will display the line after the last one on the screen at the top of the next
6637 page (0 lines of context).
6639 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6643 Default: '-%Z- %C/%m: %-20.20n %s'
6645 This variable controls the format of the one-line message ``status'' displayed
6646 before each message in either the internal or an external pager. The valid
6647 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111)''
6650 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6656 Determines the number of lines of a mini-index which is shown when in the
6657 pager. The current message, unless near the top or bottom of the folder, will
6658 be roughly one third of the way down this mini-index, giving the reader the
6660 The Mutt Next Generation E-Mail Client 128
6662 context of a few messages before and after the message. This is useful, for
6663 example, to determine how many messages remain to be read in the current
6664 thread. One of the lines is reserved for the status bar from the index, so a
6665 _
\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
6666 0 results in no index being shown. If the number of messages in the current
6667 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
6670 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6676 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6677 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
6679 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6685 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
6686 whenever the user performs an operation which ordinarily would result in the
6687 contents of the message being operated on. For example, if the user displays a
6688 pgp-traditional message which has not been manually checked with the check-tra-
6689 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
6692 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6698 This option controls whether Mutt-ng generates old-style inline (traditional)
6699 PGP encrypted or signed messages under certain circumstances. This can be
6700 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
6702 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6703 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6704 ing PGP/MIME messages when inline (traditional) would not work. See also:
6705 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.189 , page 132)''.
6707 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.
6710 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
6716 The Mutt Next Generation E-Mail Client 129
6718 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
6719 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
6721 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6727 This format is used to create a old-style ``clearsigned'' PGP message.
6729 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)
6731 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6737 This format strings specifies a command which is used to decode application/pgp
6740 The PGP command formats have their own set of printf(3)-like sequences:
6743 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
6744 string otherwise. Note: This may be used with a %? construct.
6747 Expands to the name of a file containing a message.
6750 Expands to the name of a file containing the signature part of a
6751 multipart/signed attachment when verifying it.
6754 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.193 , page 133).
6757 One or more key IDs.
6759 For examples on how to configure these formats for the various versions of PGP
6760 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
6761 subdirectory which has been installed on your system alongside the documenta-
6764 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6770 This command is used to decrypt a PGP encrypted message. (PGP only)
6772 The Mutt Next Generation E-Mail Client 130
6774 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6780 This command is used to encrypt a body part without signing it. (PGP only)
6782 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6788 This command is used to both sign and encrypt a body part. (PGP only)
6790 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6794 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
6796 This variable allows you to customize the PGP key selection menu to your per-
6797 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page
6798 111)'', but has its own set of printf(3)-like sequences:
6822 trust/validity of the key-uid association
6825 date of the key where <s> is an strftime(3) expression
6829 The Mutt Next Generation E-Mail Client 131
6831 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6837 This command is used to export a public key from the user's key ring. (PGP
6840 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6846 This command is invoked whenever Mutt-ng will need public key information. %r
6847 is the only printf(3)-like sequence used with this format. (PGP only)
6849 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
6851 Type: regular expression
6855 If you assign a text to this variable, then a PGP signature is only considered
6856 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.199 , page 134)
6857 contains the text. Use this variable if the exit code from the command is 0
6858 even for bad signatures. (PGP only)
6860 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
6866 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
6867 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
6868 want to play interesting key selection games. (PGP only)
6870 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6876 This command is used to import a key from a message into the user's public key
6879 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6885 The Mutt Next Generation E-Mail Client 132
6887 This command is used to list the public key ring's contents. The output format
6888 must be analogous to the one used by gpg --list-keys --with-colons.
6890 This format is also generated by the pgpring utility which comes with Mutt-ng.
6893 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6899 This command is used to list the secret key ring's contents. The output format
6900 must be analogous to the one used by gpg --list-keys --with-colons.
6902 This format is also generated by the pgpring utility which comes with Mutt-ng.
6905 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
6911 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
6914 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
6920 This option controls whether Mutt-ng will prompt you for automatically sending
6921 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
6924 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.
6927 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6933 Setting this variable will cause Mutt-ng to always attempt to create an inline
6934 (traditional) message when replying to a message which is PGP encrypted/signed
6935 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
6936 required. This option does not automatically detect if the (replied-to) mes-
6937 sage is inline; instead it relies on Mutt-ng internals for previously
6938 checked/flagged messages.
6940 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6942 The Mutt Next Generation E-Mail Client 133
6944 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6945 ing PGP/MIME messages when inline (traditional) would not work. See also:
6946 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.189 , page 132)''.
6948 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.
6951 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
6957 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
6958 and multipart/encrypted body parts.
6960 This is useful for applications like encrypted and signed mailing lists, where
6961 the outer layer (multipart/encrypted) can be easily removed, while the inner
6962 multipart/signed part is retained. (PGP only)
6964 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
6970 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
6971 This includes keys which have been revoked, have expired, or have been marked
6972 as ``disabled'' by the user. (PGP only)
6974 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
6980 If you have more than one key pair, this option allows you to specify which of
6981 your private keys to use. It is recommended that you use the keyid form to
6982 specify your key (e.g., ``0x00112233''). (PGP only)
6984 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6990 This command is used to create the detached PGP signature for a multi-
6991 part/signed PGP/MIME body part. (PGP only)
6993 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
6999 The Mutt Next Generation E-Mail Client 134
7001 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7005 sort alphabetically by user id
7008 sort alphabetically by key id
7011 sort by key creation date
7014 sort by the trust of the key
7016 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7019 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7025 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7026 printable. Please note that unsetting this variable may lead to problems with
7027 non-verifyable PGP signatures, so only change this if you know what you are
7030 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7036 The number of seconds after which a cached passphrase will expire if not used.
7037 Default: 300. (PGP only)
7039 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7045 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7047 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7053 This command is used to verify PGP signatures. (PGP only)
7055 The Mutt Next Generation E-Mail Client 135
7057 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7063 This command is used to verify key information from the key selection menu.
7066 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7072 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
7073 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7074 ers and will attempt to PGP/MIME decode the messages first.
7076 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7082 The separator to add between messages when piping a list of tagged messages to
7083 an external Unix command.
7085 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7091 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7092 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7093 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7094 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7095 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7096 (section 7.4.202 , page 135)'' separator is added after each message.
7098 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7106 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7107 fall back to other authentication methods if the previous methods are unavail-
7108 able. If a method is available but authentication fails, Mutt-ng will not con-
7109 nect to the POP server.
7111 The Mutt Next Generation E-Mail Client 136
7113 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7121 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7122 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7123 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7124 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7126 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7127 Mutt-ng will try all available methods, in order from most-secure to least-
7130 Example: set pop_authenticators='digest-md5:apop:user'
7132 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7140 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7141 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7142 load messages but also leave them on the POP server.
7144 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7152 The name of your POP server for the ``fetch-mail'' function. You can also
7153 specify an alternative port, username and password, i.e.:
7155 [pop[s]://][username[:password]@]popserver[:port]
7157 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7158 the superuser of your machine may read it regardless of the file's permissions.
7160 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7168 The Mutt Next Generation E-Mail Client 137
7170 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7171 retrieving only unread messages from the POP server when using the ``fetch-
7174 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7182 This variable configures how often (in seconds) POP should look for new mail.
7184 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7192 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7193 for your password when you open POP mailbox.
7195 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7196 the superuser of your machine may read it regardless of the file's permissions.
7198 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7206 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7209 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7217 Your login name on the POP server.
7219 This variable defaults to your user name on the local machine.
7221 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7225 The Mutt Next Generation E-Mail Client 138
7229 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.15 , page 89)'' variable, Mutt-ng
7230 will append this string after the inclusion of a message which is being replied
7233 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7239 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7240 7.4.215 , page 138)'' mailbox when you elect not to send immediately.
7242 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7246 Default: '~/postponed'
7248 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.214 , page 137)
7249 sending a message'' which you are editing. When you choose to postpone a mes-
7250 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7251 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.214 , page 137)'' variable.
7253 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7259 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a connec-
7260 tion to the server. This is useful for setting up secure connections, e.g. with
7261 ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the
7264 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7265 /dev/null > /dev/null'
7267 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7269 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7270 machine without having to enter a password.
7272 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\br_
\bi_
\bn_
\bt
7278 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7279 by default, because some people accidentally hit ``p'' often.
7281 The Mutt Next Generation E-Mail Client 139
7283 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7289 This specifies the command pipe that should be used to print messages.
7291 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7297 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7298 message is decoded before it is passed to the external command specified by
7299 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.218 , page 138). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7300 cessing will be applied to the message when printing it. The latter setting
7301 may be useful if you are using some advanced printer filter which is able to
7302 properly format e-mail messages for printing.
7304 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7310 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7311 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.218 , page 138) is executed
7312 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7313 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.218 , page 138) is executed
7314 only once, and all the messages are concatenated, with a form feed as the mes-
7317 Those who use the enscript(1) program's mail-printing mode will most likely
7318 want to set this option.
7320 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7326 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.167 , page 127)'', setting this
7327 variable will cause Mutt-ng to prompt you for a command when the pager exits
7328 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7329 index menu when the external pager exits.
7331 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7337 The Mutt Next Generation E-Mail Client 140
7339 This specifies the command that Mutt-ng will use to make external address
7340 queries. The string should contain a %s, which will be substituted with the
7341 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 55)'' for more
7344 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bq_
\bu_
\bi_
\bt
7350 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7351 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7352 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
7355 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7361 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7362 tion 7.4.109 , page 111)''.
7364 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7370 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7371 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7372 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.109 , page 111)''.
7374 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7376 Type: regular expression
7378 Default: '^([ \t]*[|>:}#])+'
7380 A regular expression used in the internal-pager to determine quoted sections of
7381 text in the body of a message.
7383 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
7384 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7385 the beginning of quoted lines.
7387 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7393 The Mutt Next Generation E-Mail Client 141
7395 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7396 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7397 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7398 reads message 25, and then again when it gets to message 50). This variable is
7399 meant to indicate progress when reading large mailboxes which may take some
7400 time. When set to 0, only a single message will appear before the reading the
7403 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.341 , page 168)'' variable.
7405 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7411 If set, all folders are opened in read-only mode.
7413 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7419 This variable specifies what ``real'' or ``personal'' name should be used when
7422 By default, this is the GECOS field from /etc/passwd.
7424 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7425 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.74 , page 103) variable.
7427 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7433 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7434 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.215 , page 138)''.
7436 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7438 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7444 This specifies the file into which your outgoing messages should be appended.
7445 (This is meant as the primary method for saving a copy of your messages, but
7446 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34)'' com-
7447 mand to create a Bcc: header field with your email address in it.)
7449 The Mutt Next Generation E-Mail Client 142
7451 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b1_
\b) is overridden by the
7452 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.68 , page 101)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7453 7.4.242 , page 144)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page
7456 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7458 Type: regular expression
7460 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7462 A regular expression used to recognize reply messages when threading and reply-
7463 ing. The default value corresponds to the English ``Re:'' and the German
7466 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7472 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7473 that you want to reply to the recipients of that message rather than to your-
7476 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7482 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7483 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7484 use the address in the ``From:'' header field instead.
7486 This option is useful for reading a mailing list that sets the ``Reply-To:''
7487 header field to the list address and you want to send a private message to the
7488 author of a message.
7490 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7496 When set, the cursor will be automatically advanced to the next (possibly
7497 undeleted) message whenever a command that modifies the current message is exe-
7500 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7506 The Mutt Next Generation E-Mail Client 143
7508 This variable controls whether or not Mutt-ng will display the ``personal''
7509 name from your aliases in the index menu if it finds an alias that matches the
7510 message's sender. For example, if you have the following alias:
7512 alias juser abd30425@somewhere.net (Joe User)
7514 and then you receive mail which contains the following header:
7516 From: abd30425@somewhere.net
7518 It would be displayed in the index menu as ``Joe User'' instead of
7519 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7520 not human friendly (like CompuServe addresses).
7522 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7528 It may sometimes arrive that you receive mail to a certain machine, move the
7529 messages to another machine, and reply to some the messages from there. If
7530 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7531 using the address where you received the messages you are replying to i
\bif
\bf that
7532 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7533 would be used doesn't match your alternates, the From: line will use your
7534 address on the current machine.
7536 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7542 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.237 ,
7543 page 143) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7544 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7545 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7546 (section 7.4.229 , page 141) variable.
7548 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7554 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7555 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7556 ments to files named like this:
7558 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7560 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7561 effect before you have changed folders.
7563 The Mutt Next Generation E-Mail Client 144
7565 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7566 standard, but nevertheless encountered in the wild.
7568 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7569 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7570 encoding specified in RFC 2231.
7572 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7578 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7579 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 , page 144)'' or
7580 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.68 , page 101)'' is _
\bs_
\be_
\bt too, the selection of the
7581 fcc folder will be changed as well.
7583 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7589 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7590 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.298 , page 157)'' which is
7591 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7593 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7594 and Maildir directories.
7596 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7602 This variable controls how copies of outgoing messages are saved. When set, a
7603 check is made to see if a mailbox specified by the recipient address exists
7604 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.64 ,
7605 page 100)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7606 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7607 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.231 , page 141)'' mailbox.
7609 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.68 , page 101)'' variable.
7611 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\bs_
\bc_
\bo_
\br_
\be
7617 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7618 selectively disable scoring for certain folders when the
7620 The Mutt Next Generation E-Mail Client 145
7622 ``_
\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.244 , page 144)'' variable and friends
7625 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7631 Messages which have been assigned a score equal to or lower than the value of
7632 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7633 scores are always greater than or equal to zero, the default setting of this
7634 variable will never mark a message for deletion.
7636 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7642 Messages which have been assigned a score greater than or equal to this vari-
7643 able's value are automatically marked ``flagged''.
7645 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7651 Messages which have been assigned a score equal to or lower than the value of
7652 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7653 scores are always greater than or equal to zero, the default setting of this
7654 variable will never mark a message read.
7656 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7660 Default: 'us-ascii:iso-8859-1:utf-8'
7662 A list of character sets for outgoing messages. Mutt-ng will use the first
7663 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7664 (section 7.4.24 , page 91)'' is not iso-8859-1 and recipients may not under-
7665 stand UTF-8, it is advisable to include in the list an appropriate widely used
7666 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7667 instead of or after iso-8859-1.
7669 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7673 Default: '/usr/sbin/sendmail -oem -oi'
7675 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7677 The Mutt Next Generation E-Mail Client 146
7679 Mutt-ng expects that the specified program interprets additional arguments as
7680 recipient addresses.
7682 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
7688 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.248 ,
7689 page 145)'' process to finish before giving up and putting delivery in the
7692 Mutt-ng interprets the value of this variable as follows:
7695 number of seconds to wait for sendmail to finish before continuing
7698 wait forever for sendmail to finish
7701 always put sendmail in the background without waiting
7703 Note that if you specify a value other than 0, the output of the child process
7704 will be put in a temporary file. If there is some error, you will be informed
7705 as to where to find the output.
7707 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\bs_
\bh_
\be_
\bl_
\bl
7713 Command to use when spawning a subshell. By default, the user's login shell
7714 from /etc/passwd is used.
7716 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
7722 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
7723 7.4.255 , page 147) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
7724 split a folder name into ``hierarchy items.''
7726 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
7732 This specifies the delimiter between the sidebar (if visible) and other
7734 The Mutt Next Generation E-Mail Client 147
7738 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
7744 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
7746 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7750 Default: '%m%?n?(%n)?%?f?[%f]?'
7752 This variable controls how message counts are printed when the sidebar is
7753 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
7754 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
7755 mbox-style mailboxes.)
7757 The following printf(3)-like sequences are supported all of which may be
7761 Number of deleted messages. 1)
7764 Number of flagged messages.
7767 Total number of messages.
7770 Total number of messages shown, i.e. not hidden by a limit. 1)
7773 Number of new messages.
7776 Number of tagged messages. 1)
7778 1) These expandos only have a non-zero value for the current mailbox and will
7779 always be zero otherwise.
7781 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\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
7787 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
7788 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
7789 7.4.257 , page 148)'' is set to a too low value). For example, if the
7791 The Mutt Next Generation E-Mail Client 148
7793 newsgroup name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll
7794 get shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will
7797 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
7798 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.251 , page 146) variable.
7800 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
7806 This specifies whether or not to show the sidebar (a list of folders specified
7807 with the ``mailboxes'' command).
7809 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
7815 The width of the sidebar.
7817 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
7823 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
7824 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.260 , page 148)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
7825 that you not unset this variable unless your ``signature'' contains just your
7826 name. The reason for this is because many software packages use ``-- \n'' to
7827 detect your signature.
7829 For example, Mutt-ng has the ability to highlight the signature in a different
7830 color in the builtin pager.
7832 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
7838 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
7839 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
7840 know what you are doing, and are prepared to take some heat from netiquette
7843 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
7847 The Mutt Next Generation E-Mail Client 149
7849 Default: '~/.signature'
7851 Specifies the filename of your signature, which is appended to all outgoing
7852 messages. If the filename ends with a pipe (``|''), it is assumed that file-
7853 name is a shell command and input should be read from its stdout.
7855 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7861 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
7862 people that want to sign off every message they send with their name.
7864 If you want to insert your website's URL, additional contact information or
7865 witty quotes into your mails, better use a signature file instead of the sig-
7868 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
7872 Default: '~f %s | ~s %s'
7874 Specifies how Mutt-ng should expand a simple search into a real search pattern.
7875 A simple search is one that does not contain any of the ~ operators. See
7876 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 80)'' for more information on search patterns.
7878 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
7879 will automatically expand it to the value specified by this variable. For the
7880 default value it would be:
7884 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
7890 Specifies time, in seconds, to pause while displaying certain informational
7891 messages, while moving from folder to folder and after expunging messages from
7892 the current folder. The default is to pause one second, so a value of zero for
7893 this option suppresses the pause.
7895 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
7901 Controls the display of lines longer than the screen width in the internal
7902 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
7904 The Mutt Next Generation E-Mail Client 150
7906 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.121 ,
7907 page 115)'' variable.
7909 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
7911 Type: regular expression
7913 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
7915 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
7916 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.226 , page 140)'', most notably smileys in the
7919 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
7925 This flag controls whether you want to be asked to enter a label for a certifi-
7926 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
7929 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
7935 This variable contains the name of either a directory, or a file which contains
7936 trusted certificates for use with OpenSSL. (S/MIME only)
7938 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
7944 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
7945 and retrieval of keys by itself. This is very basic right now, and keys and
7946 certificates are stored in two different directories, both named as the hash-
7947 value retrieved from OpenSSL. There is an index file which contains mailbox-
7948 address keyid pairs, and which can be manually edited. This one points to the
7949 location of the certificates. (S/MIME only)
7951 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7957 This format string specifies a command which is used to decrypt application/x-
7958 pkcs7-mime attachments.
7960 The Mutt Next Generation E-Mail Client 151
7962 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
7966 Expands to the name of a file containing a message.
7969 Expands to the name of a file containing the signature part of a
7970 multipart/signed attachment when verifying it.
7973 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.271 ,
7977 One or more certificate IDs.
7980 The algorithm used for encryption.
7983 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
7984 7.4.267 , page 150) points to a directory or file, this expands to
7985 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.267 , page 150)' or
7986 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.267 , page 150)'.
7988 For examples on how to configure these formats, see the smime.rc in the sam-
7989 ples/ subdirectory which has been installed on your system alongside the docu-
7990 mentation. (S/MIME only)
7992 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\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
7998 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
7999 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8000 mailbox-address to determine the key to use. It will ask you to supply a key,
8001 if it can't find one. (S/MIME only)
8003 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8009 This is the default key-pair to use for signing. This must be set to the keyid
8010 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8012 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8016 The Mutt Next Generation E-Mail Client 152
8020 This command is used to create encrypted S/MIME messages. (S/MIME only)
8022 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8028 This sets the algorithm that should be used for encryption. Valid choices are
8029 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8031 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8033 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8039 This command is used to extract X509 certificates from a PKCS7 structure.
8042 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\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
8048 This command is used to extract the mail address(es) used for storing X509 cer-
8049 tificates, and for verification purposes (to check whether the certificate was
8050 issued for the sender's mailbox). (S/MIME only)
8052 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\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
8058 This command is used to extract only the signers X509 certificate from a S/MIME
8059 signature, so that the certificate's owner may get compared to the email's
8060 ``From:'' header field. (S/MIME only)
8062 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\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
8068 This command is used to import a certificate via smime_keysng. (S/MIME only)
8070 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8072 The Mutt Next Generation E-Mail Client 153
8078 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8079 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8081 However, this has no effect while replying, since Mutt-ng will automatically
8082 select the same application that was used to sign/encrypt the original message.
8084 (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-
8085 tion 7.4.37 , page 94).) (S/MIME only)
8087 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8093 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8094 retrieval of keys/certs by itself. This is very basic right now, and stores
8095 keys and certificates in two different directories, both named as the hash-
8096 value retrieved from OpenSSL. There is an index file which contains mailbox-
8097 address keyid pair, and which can be manually edited. This one points to the
8098 location of the private keys. (S/MIME only)
8100 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8106 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8107 to extract the public X509 certificate(s). (S/MIME only)
8109 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8115 This command is used to created S/MIME signatures of type multipart/signed,
8116 which can be read by all mail clients. (S/MIME only)
8118 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\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
8124 This command is used to created S/MIME signatures of type application/x-
8125 pkcs7-signature, which can only be handled by mail clients supporting the
8126 S/MIME extension. (S/MIME only)
8128 The Mutt Next Generation E-Mail Client 154
8130 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8136 The number of seconds after which a cached passphrase will expire if not used.
8139 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8145 This command is used to verify S/MIME signatures of type multipart/signed.
8148 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\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
8154 This command is used to verify S/MIME signatures of type application/x-
8155 pkcs7-mime. (S/MIME only)
8157 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8165 If this variable is non-empty, it'll be used as the envelope sender. If it's
8166 empty (the default), the value of the regular From: header will be used.
8168 This may be necessary as some providers don't allow for arbitrary values as the
8169 envelope sender but only a particular one which may not be the same as the
8170 user's desired From: header.
8172 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8180 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8181 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8182 _
\bm_
\ba_
\bi_
\bl (section 7.4.248 , page 145)'', and any associated variables.
8184 The Mutt Next Generation E-Mail Client 155
8186 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8194 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8195 7.4.291 , page 155)'' is set, but this variable is not, you will be prompted
8196 for a password when sending.
8198 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8199 the superuser of your machine may read it regardless of the file's permissions.
8201 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8209 Defines the port that the SMTP host is listening on for mail delivery. Must be
8210 specified as a number.
8212 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8213 will probably desire 587, the mail submission port.
8215 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8221 Availability: SMTP (and SSL)
8223 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8224 server does not support STARTTLS or there is an error in the TLS Handshake, the
8225 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8226 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8227 port enabled in order to use it.
8229 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8237 Defines the username to use with SMTP AUTH. Setting this variable will cause
8238 Mutt-ng to attempt to use SMTP AUTH when sending.
8240 The Mutt Next Generation E-Mail Client 156
8242 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bo_
\br_
\bt
8248 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8253 mailbox-order (unsorted)
8261 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8262 (example: set sort=reverse-date-sent).
8264 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8270 Specifies how the entries in the ``alias'' menu are sorted. The following are
8273 address (sort alphabetically by email address)
8274 alias (sort alphabetically by alias name)
8275 unsorted (leave in order specified in .muttrc)
8277 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8283 When sorting by threads, this variable controls how threads are sorted in rela-
8284 tion to other threads, and how the branches of the thread trees are sorted.
8285 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.292 , page 155)'' can,
8286 except threads (in that case, Mutt-ng will just use date-sent). You can also
8287 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8288 come after reverse-. The last- prefix causes messages to be sorted against its
8289 siblings by which has the last descendant, using the rest of sort_aux as an
8292 The Mutt Next Generation E-Mail Client 157
8294 For instance, set sort_aux=last-date-received would mean that if a new message
8295 is received in a thread, that thread becomes the last one displayed (or the
8296 first, if you have set sort=reverse-threads.)
8298 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.292 , page 155)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8299 (section 7.4.294 , page 156) is reversed again (which is not the right thing
8300 to do, but kept to not break any existing configuration setting).
8302 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8308 Specifies how to sort entries in the file browser. By default, the entries are
8309 sorted alphabetically. Valid values:
8311 alpha (alphabetically)
8316 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8317 (example: set sort_browser=reverse-date).
8319 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8325 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
8326 (section 7.4.313 , page 163)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8327 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.296 ,
8328 page 157) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8329 sage by subject if the subject of the child message starts with a substring
8330 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.232 , page 141)''. With
8331 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.296 , page 157) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8332 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
8333 7.4.232 , page 141)'' parts of both messages are identical.
8335 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8341 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.297 , page 157)'' controls what happens when
8342 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8343 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8344 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.297 ,
8345 page 157)'' as a separator.
8347 The Mutt Next Generation E-Mail Client 158
8349 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8355 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8356 you can specify its location with this variable. Mutt-ng will automatically
8357 set this variable to the value of the environment variable $MAIL if it is not
8360 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8366 This variable specifies a file containing trusted CA certificates. Any server
8367 certificate that is signed with one of these CA certificates are also automati-
8370 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8372 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8380 The file containing a client certificate and its associated private key.
8382 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8388 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8389 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8390 server does not advertise the capability, since it would otherwise have to
8391 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8392 7.4.303 , page 158)''.
8394 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8400 Availability: GNUTLS
8402 This variable specifies the minimum acceptable prime size (in bits) for use in
8404 The Mutt Next Generation E-Mail Client 159
8406 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8409 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8415 Availability: SSL or GNUTLS
8417 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8418 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8419 regardless of the server's capabilities.
8421 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8429 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8432 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8438 Availability: SSL or GNUTLS
8440 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8443 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8449 Availability: SSL or GNUTLS
8451 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8454 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8460 The Mutt Next Generation E-Mail Client 160
8464 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8465 store when checking if server certificate is signed by a trusted CA.
8467 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8473 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8474 tion 7.4.309 , page 160)''. The first character is used when the mailbox is
8475 unchanged. The second is used when the mailbox has been changed, and it needs
8476 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8477 if the mailbox will not be written when exiting that mailbox (You can toggle
8478 whether to write changes to a mailbox with the toggle-write operation, bound by
8479 default to ``%''). The fourth is used to indicate that the current folder has
8480 been opened in attach-message mode (Certain operations like composing a new
8481 mail, replying, forwarding, etc. are not permitted in this mode).
8483 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8487 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8488 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8489 %l?]---(%s/%S)-%>-(%P)---'
8491 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8492 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.110 , page 111)'', but has
8493 its own set of printf(3)-like sequences:
8496 number of mailboxes with new mail *
8499 the short pathname of the current mailbox
8502 number of deleted messages *
8505 the full pathname of the current mailbox
8508 number of flagged messages *
8514 size (in bytes) of the current mailbox *
8516 The Mutt Next Generation E-Mail Client 161
8519 size (in bytes) of the messages shown (i.e., which match the cur-
8523 the number of messages in the mailbox *
8526 the number of messages shown (i.e., which match the current limit)
8530 number of new messages in the mailbox *
8533 number of old unread messages *
8536 number of postponed messages *
8539 percentage of the way through the index
8542 modified/read-only/won't-write/attach-message indicator, according
8543 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.308 , page 159)
8546 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.292 , page 155))
8549 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.294 , page
8553 number of tagged messages *
8556 number of unread messages *
8559 Mutt-ng version string
8562 currently active limit pattern, if any *
8565 right justify the rest of the string and pad with 'X'
8568 pad to the end of the line with 'X'
8570 * = can be optionally printed if nonzero
8572 The Mutt Next Generation E-Mail Client 162
8574 Some of the above sequences can be used to optionally print a string if their
8575 value is nonzero. For example, you may only want to see the number of flagged
8576 messages if such messages exist, since zero is not particularly meaningful. To
8577 optionally print a string based upon one of the above sequences, the following
8580 %?<sequence_char>?<optional_string>?
8582 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
8583 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
8584 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8587 Here is an example illustrating how to optionally print the number of new mes-
8590 %?n?%n new messages.?
8592 Additionally you can switch between two strings, the first one, if a value is
8593 zero, the second one, if the value is nonzero, by using the following con-
8596 %?<sequence_char>?<if_string>&<else_string>?
8598 You can additionally force the result of any printf(3)-like sequence to be low-
8599 ercase by prefixing the sequence character with an underscore (_) sign. For
8600 example, if you want to display the local hostname in lowercase, you would use:
8604 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8605 replace any dots in the expansion by underscores. This might be helpful with
8606 IMAP folders that don't like dots in folder names.
8608 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8614 Setting this variable causes the ``status bar'' to be displayed on the first
8615 line of the screen rather than near the bottom.
8617 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8623 With mailto: style links, a body as well as arbitrary header information may be
8624 embedded. This may lead to (user) headers being overwriten without note if
8625 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.54 , page 98)'' is unset.
8627 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8629 The Mutt Next Generation E-Mail Client 163
8631 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8632 message including headers will be shown in the editor regardless of what
8633 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.54 , page 98)'' is set to.
8635 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8641 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8642 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8643 messages are often generated by old mailers or buggy mailers like MS Outlook
8644 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.11 , page 88).
8646 This option also replaces linear-white-space between encoded-word and *text to
8647 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8648 from being devided into multiple lines.
8650 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8656 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8657 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.292 , page 155)'' by mes-
8658 sage threads. By default, messages with the same subject are grouped together
8659 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8660 mailbox where you might have several unrelated messages with the subject ``hi''
8661 which will get grouped together.
8663 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8669 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8670 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.315 , page 163) when replying. This is
8671 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8674 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8676 Type: regular expression
8678 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8680 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.314 , page 163) is _
\bs_
\be_
\bt, mutt-ng
8681 will remove this trailing part of the ``Subject'' line when replying if it
8682 won't be empty afterwards.
8684 The Mutt Next Generation E-Mail Client 164
8686 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
8692 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
8693 i.e. a space will be inserted between the quote characters and the actual text.
8695 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
8701 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
8702 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
8703 mand like ``xterm -e muttng.''
8705 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
8711 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
8712 format is easier to handle for some mailing software, and generally just looks
8713 like ordinary text. To actually make use of this format's features, you'll
8714 need support in your editor.
8716 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.109 , page 111) is ignored when this
8719 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8725 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
8726 tion 7.2 , page 80)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
8727 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
8728 as they appear in the folder.
8730 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
8736 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
8737 messages by subject.
8739 The Mutt Next Generation E-Mail Client 165
8741 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bt_
\bi_
\bl_
\bd_
\be
8747 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
8750 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8756 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
8757 pressed in the main menu before timing out and checking for new mail. A value
8758 of zero or less will cause Mutt-ng to never time out.
8760 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
8766 This variable allows you to specify where Mutt-ng will place its temporary
8767 files needed for displaying and composing messages. If this variable is not
8768 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
8771 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8777 Controls the character used to indicate mail addressed to you. The first char-
8778 acter is the one used when the mail is NOT addressed to your address (default:
8779 space). The second is used when you are the only recipient of the message
8780 (default: +). The third is when your address appears in the ``To:'' header
8781 field, but you are not the only recipient of the message (default: T). The
8782 fourth character is used when your address is specified in the ``Cc:'' header
8783 field, but you are not the only recipient. The fifth character is used to
8784 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
8785 when a mail was sent to a mailing-list you're subscribe to (default: L).
8787 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bt_
\br_
\ba_
\bs_
\bh
8793 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
8794 marked for deletion will be moved, instead of being irremediably purged.
8796 The Mutt Next Generation E-Mail Client 166
8798 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
8799 that there is no way to recover mail.
8801 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
8807 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
8808 a raw socket. You may be able to use this to set up preauthenticated connec-
8809 tions to your IMAP/POP3 server. Example:
8811 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
8813 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
8814 without having to enter a password.
8816 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bu_
\bm_
\ba_
\bs_
\bk
8822 This sets the umask that will be used by Mutt-ng when creating all kinds of
8823 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
8825 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
8831 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
8832 rent thread is _
\bu_
\bncollapsed.
8834 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
8840 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
8841 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
8842 with the SMTP support via libESMTP. Otherwise you may not be able to send
8845 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.248 , page
8846 145)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
8847 negotiation or tell libESMTP to do so.
8849 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
8853 The Mutt Next Generation E-Mail Client 167
8857 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
8858 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.89 , page 106)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
8859 no addresses will be qualified.
8861 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
8867 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
8868 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
8869 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34)'' command.
8871 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
8879 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
8881 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
8884 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
8890 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
8891 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
8892 mally, the default should work.
8894 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bu_
\bs_
\be_
\br_
\b__
\ba_
\bg_
\be_
\bn_
\bt
8900 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
8901 cating which version of Mutt-ng was used for composing them.
8903 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
8909 The Mutt Next Generation E-Mail Client 168
8911 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
8914 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
8920 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-
8921 _
\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.
8923 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
8924 75)'', provided that the corresponding mailcap entry has a needsterminal flag,
8925 and the external program is interactive.
8927 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
8928 a key only if the external command returned a non-zero status.
8930 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bw_
\be_
\be_
\bd
8936 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
8937 replying to messages.
8939 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8945 Controls whether searches wrap around the end of the mailbox.
8947 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
8948 searches will not wrap.
8950 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
8956 Controls the size of the margin remaining at the right side of the terminal
8957 when Mutt-ng's pager does smart wrapping.
8959 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
8965 The Mutt Next Generation E-Mail Client 169
8967 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
8968 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
8970 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
8976 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
8977 indicate progress. If set to 0, only a single message will be displayed before
8980 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.227 , page 140)'' variable.
8982 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
8986 Default: 'M%?n?AIL&ail?'
8988 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-
8989 tion 7.4.344 , page 169) is _
\bs_
\be_
\bt. This string is identical in formatting to the
8990 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.309 , page 160)''.
8992 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
8998 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.344 , page 169) is _
\bs_
\be_
\bt, this string will be
8999 used to set the title when leaving mutt-ng. For terminal-based programs,
9000 there's no easy and portable way to read the current title so mutt-ng cannot
9001 read it upon startup and restore it when exiting.
9003 Based on the xterm FAQ, the following might work:
9005 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9008 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9014 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9015 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9018 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9022 The Mutt Next Generation E-Mail Client 170
9024 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9026 Controls the format of the title bar of the xterm provided that
9027 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.344 , page 169) has been _
\bs_
\be_
\bt. This string is
9028 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.309 ,
9031 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9033 The following is the list of available functions listed by the mapping in which
9034 they are available. The default key setting is given, and an explanation of
9035 what the function does. The key bindings of these functions can be changed
9036 with the _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) command.
9038 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9040 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9041 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9042 tings for this menu will affect the default bindings for all menus (except as
9045 bottom-page L move to the bottom of the page
9046 current-bottom not bound move current entry to bottom of page
9047 current-middle not bound move current entry to middle of page
9048 current-top not bound move current entry to top of page
9049 enter-command : enter a muttngrc command
9050 exit q exit this menu
9051 first-entry = move to the first entry
9052 half-down ] scroll down 1/2 page
9053 half-up [ scroll up 1/2 page
9055 jump number jump to an index number
9056 last-entry * move to the last entry
9057 middle-page M move to the middle of the page
9058 next-entry j move to the next entry
9059 next-line > scroll down one line
9060 next-page z move to the next page
9061 previous-entry k move to the previous entry
9062 previous-line < scroll up one line
9063 previous-page Z move to the previous page
9064 refresh ^L clear and redraw the screen
9065 search / search for a regular expression
9066 search-next n search for next match
9067 search-opposite not bound search for next match in opposite direction
9068 search-reverse ESC / search backwards for a regular expression
9069 select-entry RET select the current entry
9070 shell-escape ! run a program in a subshell
9071 tag-entry t toggle the tag on the current entry
9072 tag-prefix ; apply next command to tagged entries
9073 tag-prefix-cond not bound apply next function ONLY to tagged messages
9074 top-page H move to the top of the page
9075 what-key not bound display the keycode for a key press
9077 The Mutt Next Generation E-Mail Client 171
9079 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9081 The Mutt Next Generation E-Mail Client 172
9083 bounce-message b remail a message to another user
9084 change-folder c open a different folder
9085 change-folder-readonly ESC c open a different folder in read only mode
9086 check-traditional-pgp ESC P check for classic pgp
9087 clear-flag W clear a status flag from a message
9088 copy-message C copy a message to a file/mailbox
9089 create-alias a create an alias from a message sender
9090 decode-copy ESC C decode a message and copy it to a file/mailbox
9091 decode-save ESC s decode a message and save it to a file/mailbox
9092 delete-message d delete the current entry
9093 delete-pattern D delete messages matching a pattern
9094 delete-subthread ESC d delete all messages in subthread
9095 delete-thread ^D delete all messages in thread
9096 display-address @ display full address of sender
9097 display-toggle-weed h display message and toggle header weeding
9098 display-message RET display a message
9099 edit e edit the current message
9100 edit-type ^E edit the current message's Content-Type
9101 exit x exit without saving changes
9102 extract-keys ^K extract PGP public keys
9103 fetch-mail G retrieve mail from POP server
9104 flag-message F toggle a message's 'important' flag
9105 forget-passphrase ^F wipe PGP passphrase from memory
9106 forward-message f forward a message with comments
9107 group-reply g reply to all recipients
9108 limit l show only messages matching a pattern
9109 list-reply L reply to specified mailing list
9110 mail m compose a new mail message
9111 mail-key ESC k mail a PGP public key
9112 next-new TAB jump to the next new message
9113 next-subthread ESC n jump to the next subthread
9114 next-thread ^N jump to the next thread
9115 next-undeleted j move to the next undeleted message
9116 next-unread not bound jump to the next unread message
9117 parent-message P jump to parent message in thread
9118 pipe-message | pipe message/attachment to a shell command
9119 previous-new ESC TAB jump to the previous new message
9120 previous-page Z move to the previous page
9121 previous-subthread ESC p jump to previous subthread
9122 previous-thread ^P jump to previous thread
9123 previous-undeleted k move to the last undelete message
9124 previous-unread not bound jump to the previous unread message
9125 print-message p print the current entry
9126 query Q query external program for addresses
9127 quit q save changes to mailbox and quit
9128 read-subthread ESC r mark the current subthread as read
9129 read-thread ^R mark the current thread as read
9130 recall-message R recall a postponed message
9131 reply r reply to a message
9132 resend-message ESC e resend message and preserve MIME structure
9133 save-message s save message/attachment to a file
9134 set-flag w set a status flag on a message
9135 show-version V show the Mutt-ng version number and date
9136 show-limit ESC l show currently active limit pattern, if any
9138 The Mutt Next Generation E-Mail Client 173
9140 sort-mailbox o sort messages
9141 sort-reverse O sort messages in reverse order
9142 sync-mailbox $ save changes to mailbox
9143 tag-pattern T tag messages matching a pattern
9144 tag-thread ESC t tag/untag all messages in the current thread
9145 toggle-new N toggle a message's 'new' flag
9146 toggle-write % toggle whether the mailbox will be rewritten
9147 undelete-message u undelete the current entry
9148 undelete-pattern U undelete messages matching a pattern
9149 undelete-subthread ESC u undelete all messages in subthread
9150 undelete-thread ^U undelete all messages in thread
9151 untag-pattern ^T untag messages matching a pattern
9152 view-attachments v show MIME attachments
9154 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9156 The Mutt Next Generation E-Mail Client 174
9158 bottom not bound jump to the bottom of the message
9159 bounce-message b remail a message to another user
9160 change-folder c open a different folder
9161 change-folder-readonly ESC c open a different folder in read only mode
9162 check-traditional-pgp ESC P check for classic pgp
9163 copy-message C copy a message to a file/mailbox
9164 create-alias a create an alias from a message sender
9165 decode-copy ESC C decode a message and copy it to a file/mailbox
9166 decode-save ESC s decode a message and save it to a file/mailbox
9167 delete-message d delete the current entry
9168 delete-subthread ESC d delete all messages in subthread
9169 delete-thread ^D delete all messages in thread
9170 display-address @ display full address of sender
9171 display-toggle-weed h display message and toggle header weeding
9172 edit e edit the current message
9173 edit-type ^E edit the current message's Content-Type
9174 enter-command : enter a muttngrc command
9175 exit i return to the main-menu
9176 extract-keys ^K extract PGP public keys
9177 flag-message F toggle a message's 'important' flag
9178 forget-passphrase ^F wipe PGP passphrase from memory
9179 forward-message f forward a message with comments
9180 group-reply g reply to all recipients
9181 half-up not bound move up one-half page
9182 half-down not bound move down one-half page
9184 list-reply L reply to specified mailing list
9185 mail m compose a new mail message
9186 mail-key ESC k mail a PGP public key
9187 mark-as-new N toggle a message's 'new' flag
9188 next-line RET scroll down one line
9189 next-entry J move to the next entry
9190 next-new TAB jump to the next new message
9191 next-page move to the next page
9192 next-subthread ESC n jump to the next subthread
9193 next-thread ^N jump to the next thread
9194 next-undeleted j move to the next undeleted message
9195 next-unread not bound jump to the next unread message
9196 parent-message P jump to parent message in thread
9197 pipe-message | pipe message/attachment to a shell command
9198 previous-line BackSpace scroll up one line
9199 previous-entry K move to the previous entry
9200 previous-new not bound jump to the previous new message
9201 previous-page - move to the previous page
9202 previous-subthread ESC p jump to previous subthread
9203 previous-thread ^P jump to previous thread
9204 previous-undeleted k move to the last undelete message
9205 previous-unread not bound jump to the previous unread message
9206 print-message p print the current entry
9207 quit Q save changes to mailbox and quit
9208 read-subthread ESC r mark the current subthread as read
9209 read-thread ^R mark the current thread as read
9210 recall-message R recall a postponed message
9211 redraw-screen ^L clear and redraw the screen
9213 The Mutt Next Generation E-Mail Client 175
9215 reply r reply to a message
9216 save-message s save message/attachment to a file
9217 search / search for a regular expression
9218 search-next n search for next match
9219 search-opposite not bound search for next match in opposite direction
9220 search-reverse ESC / search backwards for a regular expression
9221 search-toggle \ toggle search pattern coloring
9222 shell-escape ! invoke a command in a subshell
9223 show-version V show the Mutt-ng version number and date
9224 skip-quoted S skip beyond quoted text
9225 sync-mailbox $ save changes to mailbox
9226 tag-message t tag a message
9227 toggle-quoted T toggle display of quoted text
9228 top ^ jump to the top of the message
9229 undelete-message u undelete the current entry
9230 undelete-subthread ESC u undelete all messages in subthread
9231 undelete-thread ^U undelete all messages in thread
9232 view-attachments v show MIME attachments
9234 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9236 search / search for a regular expression
9237 search-next n search for next match
9238 search-reverse ESC / search backwards for a regular expression
9240 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9242 create-alias a create an alias from a message sender
9243 mail m compose a new mail message
9244 query Q query external program for addresses
9245 query-append A append new query results to current results
9246 search / search for a regular expression
9247 search-next n search for next match
9248 search-opposite not bound search for next match in opposite direction
9249 search-reverse ESC / search backwards for a regular expression
9251 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9253 The Mutt Next Generation E-Mail Client 176
9255 bounce-message b remail a message to another user
9256 collapse-parts v toggle display of subparts
9257 delete-entry d delete the current entry
9258 display-toggle-weed h display message and toggle header weeding
9259 edit-type ^E edit the current entry's Content-Type
9260 extract-keys ^K extract PGP public keys
9261 forward-message f forward a message with comments
9262 group-reply g reply to all recipients
9263 list-reply L reply to specified mailing list
9264 pipe-entry | pipe message/attachment to a shell command
9265 print-entry p print the current entry
9266 reply r reply to a message
9267 resend-message ESC e resend message and preserve MIME structure
9268 save-entry s save message/attachment to a file
9269 undelete-entry u undelete the current entry
9270 view-attach RET view attachment using mailcap entry if necessary
9271 view-mailcap m force viewing of attachment using mailcap
9272 view-text T view attachment as text
9274 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9276 The Mutt Next Generation E-Mail Client 177
9278 attach-file a attach a file(s) to this message
9279 attach-message A attach message(s) to this message
9280 attach-key ESC k attach a PGP public key
9281 copy-file C save message/attachment to a file
9282 detach-file D delete the current entry
9283 display-toggle-weed h display message and toggle header weeding
9284 edit-bcc b edit the BCC list
9285 edit-cc c edit the CC list
9286 edit-description d edit attachment description
9287 edit-encoding ^E edit attachment transfer-encoding
9288 edit-fcc f enter a file to save a copy of this message in
9289 edit-from ESC f edit the from: field
9290 edit-file ^X e edit the file to be attached
9291 edit-headers E edit the message with headers
9292 edit e edit the message
9293 edit-mime m edit attachment using mailcap entry
9294 edit-reply-to r edit the Reply-To field
9295 edit-subject s edit the subject of this message
9296 edit-to t edit the TO list
9297 edit-type ^T edit attachment type
9298 filter-entry F filter attachment through a shell command
9299 forget-passphrase ^F wipe PGP passphrase from memory
9300 ispell i run ispell on the message
9301 new-mime n compose new attachment using mailcap entry
9302 pgp-menu p show PGP options
9303 pipe-entry | pipe message/attachment to a shell command
9304 postpone-message P save this message to send later
9305 print-entry l print the current entry
9306 rename-file R rename/move an attached file
9307 send-message y send the message
9308 toggle-unlink u toggle whether to delete file after sending it
9309 view-attach RET view attachment using mailcap entry if necessary
9310 write-fcc w write the message to a folder
9312 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9314 delete-entry d delete the current entry
9315 undelete-entry u undelete the current entry
9317 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9319 The Mutt Next Generation E-Mail Client 178
9321 change-dir c change directories
9322 check-new TAB check mailboxes for new mail
9323 enter-mask m enter a file mask
9324 search / search for a regular expression
9325 search-next n search for next match
9326 search-reverse ESC / search backwards for a regular expression
9327 select-new N select a new file in this directory
9328 sort o sort messages
9329 sort-reverse O sort messages in reverse order
9330 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9331 view-file SPACE view file
9332 subscribe s subscribe to current mailbox (IMAP Only)
9333 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9334 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9336 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9338 view-name % view the key's user id
9339 verify-key c verify a PGP public key
9341 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9343 backspace BackSpace delete the char in front of the cursor
9344 backward-char ^B move the cursor one character to the left
9345 backward-word ESC b move the cursor to the previous word
9346 bol ^A jump to the beginning of the line
9347 buffy-cycle Space cycle among incoming mailboxes
9348 capitalize-word ESC c uppercase the first character in the word
9349 complete TAB complete filename or alias
9350 complete-query ^T complete address with query
9351 delete-char ^D delete the char under the cursor
9352 downcase-word ESC l lowercase all characters in current word
9353 eol ^E jump to the end of the line
9354 forward-char ^F move the cursor one character to the right
9355 forward-word ESC f move the cursor to the next word
9356 history-down not bound scroll down through the history list
9357 history-up not bound scroll up through the history list
9358 kill-eol ^K delete chars from cursor to end of line
9359 kill-eow ESC d delete chars from cursor to end of word
9360 kill-line ^U delete all chars on the line
9361 kill-word ^W delete the word in front of the cursor
9362 quote-char ^V quote the next typed key
9363 transpose-chars not bound transpose character under cursor with previous
9364 upcase-word ESC u uppercase all characters in current word
9366 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9368 The Mutt Next Generation E-Mail Client 179
9370 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9372 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9373 back in the ELM-ME days.
9375 The following people have been very helpful to the development of Mutt:
9377 Vikas Agnihotri <vikasa@writeme.com>,
9379 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9381 Aric Blumer <aric@fore.com>,
9383 John Capo <jc@irbs.com>,
9385 David Champion <dgc@uchicago.edu,
9387 Brendan Cully <brendan@kublai.com>,
9389 Liviu Daia <daia@stoilow.imar.ro>,
9391 Thomas E. Dickey <dickey@herndon4.his.com>,
9393 David DeSimone <fox@convex.hp.com>,
9395 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9397 Ruslan Ermilov <ru@freebsd.org>,
9399 Edmund Grimley Evans <edmundo@rano.org,
9401 Michael Finken <finken@conware.de>,
9403 Sven Guckes <guckes@math.fu-berlin.de>,
9405 Lars Hecking <lhecking@nmrc.ie>,
9407 Mark Holloman <holloman@nando.net>,
9409 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9411 Marco d'Itri <md@linux.it>,
9413 Bjrn Jacke <bjacke@suse.com>,
9415 Byrial Jensen <byrial@image.dk>,
9417 David Jeske <jeske@igcom.net>,
9419 Christophe Kalt <kalt@hugo.int-evry.fr>,
9421 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9423 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9425 The Mutt Next Generation E-Mail Client 180
9427 Brandon Long <blong@fiction.net>,
9429 Jimmy Mkel <jmy@flashback.net>,
9431 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9433 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9435 Andrew W. Nosenko <awn@bcs.zp.ua>,
9437 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9439 Clint Olsen <olsenc@ichips.intel.com>,
9441 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9443 Thomas Parmelan <tom@ankh.fr.eu.org>,
9445 Ollivier Robert <roberto@keltia.freenix.fr>,
9447 Thomas Roessler <roessler@does-not-exist.org>,
9449 Roland Rosenfeld <roland@spinnaker.de>,
9451 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9453 Allain Thivillon <Allain.Thivillon@alma.fr>,
9455 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9457 Vsevolod Volkov <vvv@lucky.net>,
9459 Ken Weinert <kenw@ihs.com>
9461 Mutt-ng is developed by the following people:
9463 Andreas Krennmair <ak@synflood.at>
9465 Nico Golde <nico@ngolde.de>
9467 Rocco Rutte <pdmef@cs.tu-berlin.de>
9469 The following people have been very helpful to the development of Mutt-ng:
9471 Christian Gall <cg@cgall.de>
9473 Iain Lea <iain@bricbrac.de>
9475 Andreas Kneib <akneib@gmx.net>
9477 Carsten Schoelzki <cjs@weisshuhn.de>
9479 Elimar Riesebieter <riesebie@lxtec.de>
9481 The Mutt Next Generation E-Mail Client 181
9483 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9485 This document was written in SGML, and then rendered using the sgml-tools pack-
9488 The Mutt Next Generation E-Mail Client 182
9492 1. Introduction .......................................................... 1
9493 1.1 Overview ........................................................ 1
9494 1.2 Mutt-ng Home Page ............................................... 1
9495 1.3 Mailing Lists ................................................... 1
9496 1.4 Software Distribution Sites ..................................... 2
9497 1.5 IRC ............................................................. 2
9498 1.6 Weblog .......................................................... 2
9499 1.7 Copyright ....................................................... 2
9501 2. Getting Started ..................................................... 2
9502 2.1 Basic Concepts .............................................. 2
9503 2.1.1 Screens and Menus 3
9504 2.1.2 Configuration 3
9507 2.1.5 Modularization 4
9509 2.2 Screens and Menus ........................................... 4
9512 2.2.3 File Browser 5
9515 2.2.6 Compose Menu 6
9517 2.2.8 Attachment Menu 6
9519 2.3 Moving Around in Menus .......................................... 6
9520 2.4 Editing Input Fields ............................................ 7
9521 2.5 Reading Mail - The Index and Pager .............................. 8
9522 2.5.1 The Message Index 8
9524 2.5.3 Threaded Mode 11
9525 2.5.4 Miscellaneous Functions 11
9526 2.6 Sending Mail ................................................... 14
9527 2.6.1 Composing new messages 14
9529 2.6.3 Editing the message header 17
9530 2.6.4 Using Mutt-ng with PGP 18
9531 2.6.5 Sending anonymous messages via mixmaster 19
9532 2.7 Forwarding and Bouncing Mail ................................... 19
9533 2.8 Postponing Mail ................................................ 20
9535 3. Configuration ........................................................ 21
9536 3.1 Locations of Configuration Files ............................... 21
9537 3.2 Syntax of Initialization Files ................................. 21
9538 3.3 Defining/Using aliases ......................................... 23
9539 3.4 Changing the default key bindings .............................. 24
9540 3.5 Defining aliases for character sets ........................... 26
9544 3.6 Setting variables based upon mailbox ........................... 26
9545 3.7 Keyboard macros ................................................ 27
9546 3.8 Using color and mono video attributes .......................... 28
9547 3.9 Ignoring (weeding) unwanted message headers .................... 30
9548 3.10 Alternative addresses .......................................... 31
9549 3.11 Format = Flowed ................................................ 31
9550 3.12 Mailing lists .................................................. 32
9551 3.13 Using Multiple spool mailboxes ................................. 33
9552 3.14 Defining mailboxes which receive mail .......................... 34
9553 3.15 User defined headers ........................................... 34
9554 3.16 Defining the order of headers when viewing messages ............ 35
9555 3.17 Specify default save filename .................................. 35
9556 3.18 Specify default Fcc: mailbox when composing .................... 36
9557 3.19 Specify default save filename and default Fcc: mailbox at once . 36
9558 3.20 Change settings based upon message recipients .................. 36
9559 3.21 Change settings before formatting a message .................... 37
9560 3.22 Choosing the cryptographic key of the recipient ................ 37
9561 3.23 Adding key sequences to the keyboard buffer .................... 38
9562 3.24 Executing functions ............................................ 38
9563 3.25 Message Scoring ................................................ 38
9564 3.26 Spam detection ................................................. 39
9565 3.27 Setting variables .............................................. 41
9566 3.28 Reading initialization commands from another file .............. 42
9567 3.29 Removing hooks ................................................. 42
9568 3.30 Sharing Setups ............................................. 43
9569 3.30.1 Character Sets 43
9570 3.30.2 Modularization 43
9571 3.30.3 Conditional parts 43
9572 3.31 Obsolete Variables ............................................. 45
9574 4. Advanced Usage ....................................................... 45
9575 4.1 Regular Expressions ............................................ 45
9576 4.2 Patterns ....................................................... 48
9577 4.2.1 Complex Patterns 49
9578 4.2.2 Patterns and Dates 49
9579 4.3 Format Strings ............................................. 50
9580 4.3.1 Introduction 50
9581 4.3.2 Conditional Expansion 51
9582 4.3.3 Modifications and Padding 52
9583 4.4 Using Tags ..................................................... 53
9584 4.5 Using Hooks .................................................... 53
9585 4.5.1 Message Matching in Hooks 54
9586 4.6 Using the sidebar .............................................. 54
9587 4.7 External Address Queries ....................................... 55
9588 4.8 Mailbox Formats ................................................ 56
9589 4.9 Mailbox Shortcuts .............................................. 57
9590 4.10 Handling Mailing Lists ......................................... 57
9591 4.11 Editing threads ................................................ 59
9592 4.11.1 Linking threads 59
9593 4.11.2 Breaking threads 59
9594 4.12 Delivery Status Notification (DSN) Support ..................... 59
9595 4.13 POP3 Support (OPTIONAL) ........................................ 60
9596 4.14 IMAP Support (OPTIONAL) ........................................ 60
9600 4.14.1 The Folder Browser 61
9601 4.14.2 Authentication 62
9602 4.15 NNTP Support (OPTIONAL) ........................................ 62
9603 4.15.1 Again: Scoring 63
9604 4.16 SMTP Support (OPTIONAL) ........................................ 63
9605 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 64
9606 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64
9607 4.19 Compressed folders Support (OPTIONAL) .......................... 65
9608 4.19.1 Open a compressed mailbox for reading 65
9609 4.19.2 Write a compressed mailbox 66
9610 4.19.3 Append a message to a compressed mailbox 66
9611 4.19.4 Encrypted folders 67
9613 5. Mutt-ng's MIME Support ............................................... 67
9614 5.1 Using MIME in Mutt ............................................. 67
9615 5.1.1 Viewing MIME messages in the pager 68
9616 5.1.2 The Attachment Menu 68
9617 5.1.3 The Compose Menu 68
9618 5.2 MIME Type configuration with mime.types ........................ 69
9619 5.3 MIME Viewer configuration with mailcap ......................... 69
9620 5.3.1 The Basics of the mailcap file 70
9621 5.3.2 Secure use of mailcap 71
9622 5.3.3 Advanced mailcap Usage 72
9623 5.3.4 Example mailcap files 74
9624 5.4 MIME Autoview .................................................. 75
9625 5.5 MIME Multipart/Alternative ..................................... 76
9626 5.6 MIME Lookup .................................................... 76
9628 6. Security Considerations ............................................ 77
9629 6.1 Passwords .................................................. 77
9630 6.2 Temporary Files ............................................ 77
9631 6.3 Information Leaks ............................................ 78
9632 6.3.1 Message-ID: headers 78
9633 6.3.2 mailto:-style links 78
9634 6.4 External applications ...................................... 78
9638 7. Reference ............................................................ 79
9639 7.1 Command line options ........................................... 79
9640 7.2 Patterns ....................................................... 80
9641 7.3 Configuration Commands ......................................... 82
9642 7.4 Configuration variables .......................................... 84
9643 7.4.1 abort_nosubject 85
9644 7.4.2 abort_unmodified 86
9646 7.4.4 alias_format 86
9649 7.4.7 arrow_cursor 87
9650 7.4.8 ascii_chars 87
9656 7.4.11 assumed_charset 88
9657 7.4.12 attach_format 88
9658 7.4.13 attach_sep 89
9659 7.4.14 attach_split 89
9660 7.4.15 attribution 89
9666 7.4.21 bounce_delivered 90
9667 7.4.22 braille_friendly 91
9668 7.4.23 certificate_file 91
9671 7.4.26 collapse_unread 92
9672 7.4.27 compose_format 92
9673 7.4.28 config_charset 92
9674 7.4.29 confirmappend 92
9675 7.4.30 confirmcreate 93
9676 7.4.31 connect_timeout 93
9677 7.4.32 content_type 93
9679 7.4.34 crypt_autoencrypt 93
9680 7.4.35 crypt_autopgp 94
9681 7.4.36 crypt_autosign 94
9682 7.4.37 crypt_autosmime 94
9683 7.4.38 crypt_replyencrypt 94
9684 7.4.39 crypt_replysign 94
9685 7.4.40 crypt_replysignencrypted 95
9686 7.4.41 crypt_timestamp 95
9687 7.4.42 crypt_use_gpgme 95
9688 7.4.43 crypt_verify_sig 95
9689 7.4.44 date_format 95
9690 7.4.45 default_hook 96
9692 7.4.47 delete_untag 96
9693 7.4.48 digest_collapse 96
9694 7.4.49 display_filter 97
9695 7.4.50 dotlock_program 97
9696 7.4.51 dsn_notify 97
9697 7.4.52 dsn_return 97
9698 7.4.53 duplicate_threads 98
9699 7.4.54 edit_headers 98
9701 7.4.56 encode_from 98
9702 7.4.57 entropy_file 98
9703 7.4.58 envelope_from 99
9705 7.4.60 fast_reply 99
9706 7.4.61 fcc_attach 99
9708 7.4.63 file_charset 99
9713 7.4.65 folder_format 100
9714 7.4.66 followup_to 101
9715 7.4.67 force_buffy_check 101
9716 7.4.68 force_name 101
9717 7.4.69 forward_decode 102
9718 7.4.70 forward_decrypt 102
9719 7.4.71 forward_edit 102
9720 7.4.72 forward_format 102
9721 7.4.73 forward_quote 102
9723 7.4.75 gecos_mask 103
9726 7.4.78 header_cache 104
9727 7.4.79 header_cache_compress 104
9729 7.4.81 hidden_host 104
9730 7.4.82 hide_limited 105
9731 7.4.83 hide_missing 105
9732 7.4.84 hide_thread_subject 105
9733 7.4.85 hide_top_limited 105
9734 7.4.86 hide_top_missing 105
9736 7.4.88 honor_followup_to 106
9738 7.4.90 ignore_list_reply_to 106
9739 7.4.91 imap_authenticators 106
9740 7.4.92 imap_check_subscribed 107
9741 7.4.93 imap_delim_chars 107
9742 7.4.94 imap_headers 107
9743 7.4.95 imap_home_namespace 107
9744 7.4.96 imap_keepalive 108
9745 7.4.97 imap_list_subscribed 108
9746 7.4.98 imap_login 108
9747 7.4.99 imap_mail_check 108
9748 7.4.100 imap_pass 109
9749 7.4.101 imap_passive 109
9750 7.4.102 imap_peek 109
9751 7.4.103 imap_reconnect 109
9752 7.4.104 imap_servernoise 110
9753 7.4.105 imap_user 110
9754 7.4.106 implicit_autoview 110
9756 7.4.108 include_onlyfirst 110
9757 7.4.109 indent_string 111
9758 7.4.110 index_format 111
9760 7.4.112 keep_flagged 114
9761 7.4.113 list_reply 114
9763 7.4.115 mail_check 114
9764 7.4.116 mailcap_path 114
9768 7.4.117 mailcap_sanitize 115
9769 7.4.118 maildir_header_cache_verify 115
9770 7.4.119 maildir_trash 115
9771 7.4.120 mark_old 115
9774 7.4.123 max_display_recips 116
9775 7.4.124 max_line_length 116
9777 7.4.126 mbox_type 116
9778 7.4.127 menu_context 117
9779 7.4.128 menu_move_off 117
9780 7.4.129 menu_scroll 117
9781 7.4.130 message_format 117
9782 7.4.131 meta_key 117
9784 7.4.133 mh_purge 118
9785 7.4.134 mh_seq_flagged 118
9786 7.4.135 mh_seq_replied 118
9787 7.4.136 mh_seq_unseen 118
9788 7.4.137 mime_forward 118
9789 7.4.138 mime_forward_decode 119
9790 7.4.139 mime_forward_rest 119
9791 7.4.140 mix_entry_format 119
9792 7.4.141 mixmaster 120
9794 7.4.143 msgid_format 120
9795 7.4.144 narrow_tree 121
9796 7.4.145 nntp_ask_followup_to 121
9797 7.4.146 nntp_ask_x_comment_to 121
9798 7.4.147 nntp_cache_dir 122
9799 7.4.148 nntp_catchup 122
9800 7.4.149 nntp_context 122
9801 7.4.150 nntp_followup_to_poster 122
9802 7.4.151 nntp_group_index_format 123
9803 7.4.152 nntp_host 123
9804 7.4.153 nntp_inews 123
9805 7.4.154 nntp_load_description 124
9806 7.4.155 nntp_mail_check 124
9807 7.4.156 nntp_mime_subject 124
9808 7.4.157 nntp_newsrc 124
9809 7.4.158 nntp_pass 125
9810 7.4.159 nntp_post_moderated 125
9811 7.4.160 nntp_reconnect 125
9812 7.4.161 nntp_save_unsubscribed 125
9813 7.4.162 nntp_show_new_news 126
9814 7.4.163 nntp_show_only_unread 126
9815 7.4.164 nntp_user 126
9816 7.4.165 nntp_x_comment_to 126
9817 7.4.166 operating_system 126
9819 7.4.168 pager_context 127
9820 7.4.169 pager_format 127
9824 7.4.170 pager_index_lines 127
9825 7.4.171 pager_stop 128
9826 7.4.172 pgp_auto_decode 128
9827 7.4.173 pgp_autoinline 128
9828 7.4.174 pgp_check_exit 128
9829 7.4.175 pgp_clearsign_command 129
9830 7.4.176 pgp_decode_command 129
9831 7.4.177 pgp_decrypt_command 129
9832 7.4.178 pgp_encrypt_only_command 130
9833 7.4.179 pgp_encrypt_sign_command 130
9834 7.4.180 pgp_entry_format 130
9835 7.4.181 pgp_export_command 131
9836 7.4.182 pgp_getkeys_command 131
9837 7.4.183 pgp_good_sign 131
9838 7.4.184 pgp_ignore_subkeys 131
9839 7.4.185 pgp_import_command 131
9840 7.4.186 pgp_list_pubring_command 131
9841 7.4.187 pgp_list_secring_command 132
9842 7.4.188 pgp_long_ids 132
9843 7.4.189 pgp_mime_auto 132
9844 7.4.190 pgp_replyinline 132
9845 7.4.191 pgp_retainable_sigs 133
9846 7.4.192 pgp_show_unusable 133
9847 7.4.193 pgp_sign_as 133
9848 7.4.194 pgp_sign_command 133
9849 7.4.195 pgp_sort_keys 133
9850 7.4.196 pgp_strict_enc 134
9851 7.4.197 pgp_timeout 134
9852 7.4.198 pgp_use_gpg_agent 134
9853 7.4.199 pgp_verify_command 134
9854 7.4.200 pgp_verify_key_command 135
9855 7.4.201 pipe_decode 135
9856 7.4.202 pipe_sep 135
9857 7.4.203 pipe_split 135
9858 7.4.204 pop_auth_try_all 135
9859 7.4.205 pop_authenticators 136
9860 7.4.206 pop_delete 136
9861 7.4.207 pop_host 136
9862 7.4.208 pop_last 136
9863 7.4.209 pop_mail_check 137
9864 7.4.210 pop_pass 137
9865 7.4.211 pop_reconnect 137
9866 7.4.212 pop_user 137
9867 7.4.213 post_indent_string 137
9868 7.4.214 postpone 138
9869 7.4.215 postponed 138
9870 7.4.216 preconnect 138
9872 7.4.218 print_command 139
9873 7.4.219 print_decode 139
9874 7.4.220 print_split 139
9875 7.4.221 prompt_after 139
9876 7.4.222 query_command 139
9881 7.4.224 quote_empty 140
9882 7.4.225 quote_quoted 140
9883 7.4.226 quote_regexp 140
9884 7.4.227 read_inc 140
9885 7.4.228 read_only 141
9886 7.4.229 realname 141
9889 7.4.232 reply_regexp 142
9890 7.4.233 reply_self 142
9891 7.4.234 reply_to 142
9893 7.4.236 reverse_alias 142
9894 7.4.237 reverse_name 143
9895 7.4.238 reverse_realname 143
9896 7.4.239 rfc2047_parameters 143
9897 7.4.240 save_address 144
9898 7.4.241 save_empty 144
9899 7.4.242 save_name 144
9901 7.4.244 score_threshold_delete 145
9902 7.4.245 score_threshold_flag 145
9903 7.4.246 score_threshold_read 145
9904 7.4.247 send_charset 145
9905 7.4.248 sendmail 145
9906 7.4.249 sendmail_wait 146
9908 7.4.251 sidebar_boundary 146
9909 7.4.252 sidebar_delim 146
9910 7.4.253 sidebar_newmail_only 147
9911 7.4.254 sidebar_number_format 147
9912 7.4.255 sidebar_shorten_hierarchy 147
9913 7.4.256 sidebar_visible 148
9914 7.4.257 sidebar_width 148
9915 7.4.258 sig_dashes 148
9916 7.4.259 sig_on_top 148
9917 7.4.260 signature 148
9918 7.4.261 signoff_string 149
9919 7.4.262 simple_search 149
9920 7.4.263 sleep_time 149
9921 7.4.264 smart_wrap 149
9923 7.4.266 smime_ask_cert_label 150
9924 7.4.267 smime_ca_location 150
9925 7.4.268 smime_certificates 150
9926 7.4.269 smime_decrypt_command 150
9927 7.4.270 smime_decrypt_use_default_key 151
9928 7.4.271 smime_default_key 151
9929 7.4.272 smime_encrypt_command 151
9930 7.4.273 smime_encrypt_with 152
9931 7.4.274 smime_get_cert_command 152
9932 7.4.275 smime_get_cert_email_command 152
9936 7.4.276 smime_get_signer_cert_command 152
9937 7.4.277 smime_import_cert_command 152
9938 7.4.278 smime_is_default 152
9939 7.4.279 smime_keys 153
9940 7.4.280 smime_pk7out_command 153
9941 7.4.281 smime_sign_command 153
9942 7.4.282 smime_sign_opaque_command 153
9943 7.4.283 smime_timeout 154
9944 7.4.284 smime_verify_command 154
9945 7.4.285 smime_verify_opaque_command 154
9946 7.4.286 smtp_envelope 154
9947 7.4.287 smtp_host 154
9948 7.4.288 smtp_pass 155
9949 7.4.289 smtp_port 155
9950 7.4.290 smtp_use_tls 155
9951 7.4.291 smtp_user 155
9953 7.4.293 sort_alias 156
9954 7.4.294 sort_aux 156
9955 7.4.295 sort_browser 157
9957 7.4.297 spam_separator 157
9958 7.4.298 spoolfile 158
9959 7.4.299 ssl_ca_certificates_file 158
9960 7.4.300 ssl_client_cert 158
9961 7.4.301 ssl_force_tls 158
9962 7.4.302 ssl_min_dh_prime_bits 158
9963 7.4.303 ssl_starttls 159
9964 7.4.304 ssl_use_sslv2 159
9965 7.4.305 ssl_use_sslv3 159
9966 7.4.306 ssl_use_tlsv1 159
9967 7.4.307 ssl_usesystemcerts 159
9968 7.4.308 status_chars 160
9969 7.4.309 status_format 160
9970 7.4.310 status_on_top 162
9971 7.4.311 strict_mailto 162
9972 7.4.312 strict_mime 163
9973 7.4.313 strict_threads 163
9974 7.4.314 strip_was 163
9975 7.4.315 strip_was_regex 163
9976 7.4.316 stuff_quoted 164
9978 7.4.318 text_flowed 164
9979 7.4.319 thorough_search 164
9980 7.4.320 thread_received 164
9984 7.4.324 to_chars 165
9988 7.4.328 uncollapse_jump 166
9992 7.4.329 use_8bitmime 166
9993 7.4.330 use_domain 166
9994 7.4.331 use_from 167
9996 7.4.333 use_ipv6 167
9997 7.4.334 user_agent 167
9999 7.4.336 wait_key 168
10001 7.4.338 wrap_search 168
10002 7.4.339 wrapmargin 168
10003 7.4.340 write_bcc 168
10004 7.4.341 write_inc 169
10005 7.4.342 xterm_icon 169
10006 7.4.343 xterm_leave 169
10007 7.4.344 xterm_set_titles 169
10008 7.4.345 xterm_title 169
10009 7.5 Functions ....................................................... 170
10022 8. Miscellany ............................................................ 178
10023 8.1 Acknowledgments ................................................. 179
10024 8.2 About this document ............................................. 181
projects / apps / madmutt.git / blob