2 T
\bTh
\bhe
\be M
\bMu
\but
\btt
\bt N
\bNe
\bex
\bxt
\bt G
\bGe
\ben
\bne
\ber
\bra
\bat
\bti
\bio
\bon
\bn E
\bE-
\b-M
\bMa
\bai
\bil
\bl C
\bCl
\bli
\bie
\ben
\bnt
\bt
4 by Andreas Krennmair <ak@synflood.at> and others
5 originally based on _
\bm_
\bu_
\bt_
\bt by Michael Elkins <me@cs.hmc.edu> and others
9 A
\bAb
\bbs
\bst
\btr
\bra
\bac
\bct
\bt
11 Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
12 sucks less.'' - Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
14 _
\b1_
\b. _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
16 _
\b1_
\b._
\b1 _
\bO_
\bv_
\be_
\br_
\bv_
\bi_
\be_
\bw
18 M
\bMu
\but
\btt
\bt-
\b-n
\bng
\bg is a small but very powerful text-based MIME mail client. Mutt-ng is
19 highly configurable, and is well suited to the mail power user with advanced
20 features like key bindings, keyboard macros, mail threading, regular expression
21 searches and a powerful pattern matching language for selecting groups of mes-
24 This documentation additionally contains documentation to M
\bMu
\but
\btt
\bt-
\b-N
\bNG
\bG, a fork from
25 Mutt with the goal to fix all the little annoyances of Mutt, to integrate all
26 the Mutt patches that are floating around in the web, and to add other new fea-
27 tures. Features specific to Mutt-ng will be discussed in an extra section.
28 Don't be confused when most of the documentation talk about Mutt and not Mutt-
29 ng, Mutt-ng contains all Mutt features, plus many more.
31 _
\b1_
\b._
\b2 _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bH_
\bo_
\bm_
\be _
\bP_
\ba_
\bg_
\be
35 _
\b1_
\b._
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
37 +
\bo mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user support
40 The Mutt Next Generation E-Mail Client 1
42 The Mutt Next Generation E-Mail Client 2
44 +
\bo mutt-ng-devel@lists.berlios.de -- The development mailing list for mutt-ng
46 _
\b1_
\b._
\b4 _
\bS_
\bo_
\bf_
\bt_
\bw_
\ba_
\br_
\be _
\bD_
\bi_
\bs_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn _
\bS_
\bi_
\bt_
\be_
\bs
48 So far, there are no official releases of Mutt-ng, but you can download daily
49 snapshots from http://mutt-ng.berlios.de/snapshots/
51 _
\b1_
\b._
\b5 _
\bI_
\bR_
\bC
53 Visit channel _
\b#_
\bm_
\bu_
\bt_
\bt_
\bn_
\bg on irc.freenode.net (www.freenode.net) to chat with other
54 people interested in Mutt-ng.
56 _
\b1_
\b._
\b6 _
\bW_
\be_
\bb_
\bl_
\bo_
\bg
58 If you want to read fresh news about the latest development in Mutt-ng, and get
59 informed about stuff like interesting, Mutt-ng-related articles and packages
60 for your favorite distribution, you can read and/or subscribe to our Mutt-ng
63 _
\b1_
\b._
\b7 _
\bC_
\bo_
\bp_
\by_
\br_
\bi_
\bg_
\bh_
\bt
65 Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and others
67 This program is free software; you can redistribute it and/or modify it under
68 the terms of the GNU General Public License as published by the Free Software
69 Foundation; either version 2 of the License, or (at your option) any later ver-
72 This program is distributed in the hope that it will be useful, but WITHOUT ANY
73 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
74 PARTICULAR PURPOSE. See the GNU General Public License for more details.
76 You should have received a copy of the GNU General Public License along with
77 this program; if not, write to the Free Software Foundation, Inc., 59 Temple
78 Place - Suite 330, Boston, MA 02111, USA.
80 _
\b2_
\b. _
\bG_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bS_
\bt_
\ba_
\br_
\bt_
\be_
\bd
82 _
\b2_
\b._
\b1 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bC_
\bo_
\bn_
\bc_
\be_
\bp_
\bt_
\bs
84 The Mutt Next Generation E-Mail Client 3
86 _
\b2_
\b._
\b1_
\b._
\b1 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
88 mutt-ng offers different screens of which every has its special purpose:
90 +
\bo The _
\bi_
\bn_
\bd_
\be_
\bx displays the contents of the currently opened mailbox.
92 +
\bo The _
\bp_
\ba_
\bg_
\be_
\br is responsible for displaying messages, that is, the header, the
93 body and all attached parts.
95 +
\bo The _
\bf_
\bi_
\bl_
\be _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br offers operations on and displays information of all
96 folders mutt-ng should watch for mail.
98 +
\bo The _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br offers a permanent view of which mailboxes contain how many
99 total, new and/or flagged mails.
101 +
\bo The _
\bh_
\be_
\bl_
\bp _
\bs_
\bc_
\br_
\be_
\be_
\bn lists for all currently available commands how to invoke
102 them as well as a short description.
104 +
\bo The _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu is a comfortable interface take last actions before send-
105 ing mail: change subjects, attach files, remove attachements, etc.
107 +
\bo The _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\be_
\bm_
\be_
\bn_
\bt menu gives a summary and the tree structure of the
108 attachements of the current message.
110 +
\bo The _
\ba_
\bl_
\bi_
\ba_
\bs menu lists all or a fraction of the aliases a user has defined.
112 +
\bo The _
\bk_
\be_
\by menu used in connection with encryption lets users choose the
113 right key to encrypt with.
115 When mutt-ng is started without any further options, it'll open the users
116 default mailbox and display the index.
118 _
\b2_
\b._
\b1_
\b._
\b2 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
120 Mutt-ng does _
\bn_
\bo_
\bt feature an internal configuration interface or menu due to the
121 simple fact that this would be too complex to handle (currently there are sev-
122 eral _
\bh_
\bu_
\bn_
\bd_
\br_
\be_
\bd variables which fine-tune the behaviour.)
124 Mutt-ng is configured using configuration files which allow users to add com-
125 ments or manage them via version control systems to ease maintenance.
127 Also, mutt-ng comes with a shell script named grml-muttng kindly contributed by
128 users which really helps and eases the creation of a user's configuration file.
129 When downloading the source code via a snapshot or via subversion, it can be
130 found in the contrib directory.
132 _
\b2_
\b._
\b1_
\b._
\b3 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
134 Mutt-ng offers great flexibility due to the use of functions: internally, every
135 action a user can make mutt-ng perform is named ``function.'' Those functions
137 The Mutt Next Generation E-Mail Client 4
139 are assigned to keys (or even key sequences) and may be completely adjusted to
140 user's needs. The basic idea is that the impatient users get a very intuitive
141 interface to start off with and advanced users virtually get no limits to
144 _
\b2_
\b._
\b1_
\b._
\b4 _
\bI_
\bn_
\bt_
\be_
\br_
\ba_
\bc_
\bt_
\bi_
\bo_
\bn
146 Mutt-ng has two basic concepts of user interaction:
148 1. There is one dedicated line on the screen used to query the user for
149 input, issue any command, query variables and display error and informa-
150 tional messages. As for every type of user input, this requires manual
151 action leading to the need of input.
153 2. The automatized interface for interaction are the so called _
\bh_
\bo_
\bo_
\bk_
\bs. Hooks
154 specify actions the user wants to be performed at well-defined situa-
155 tions: what to do when entering which folder, what to do when displaying
156 or replying to what kind of message, etc. These are optional, i.e. a user
157 doesn't need to specify them but can do so.
159 _
\b2_
\b._
\b1_
\b._
\b5 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
161 Although mutt-ng has many functionality built-in, many features can be dele-
162 gated to external tools to increase flexibility: users can define programs to
163 filter a message through before displaying, users can use any program they want
164 for displaying a message, message types (such as PDF or PostScript) for which
165 mutt-ng doesn't have a built-in filter can be rendered by arbitrary tools and
166 so forth. Although mutt-ng has an alias mechanism built-in, it features using
167 external tools to query for nearly every type of addresses from sources like
168 LDAP, databases or just the list of locally known users.
170 _
\b2_
\b._
\b1_
\b._
\b6 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
172 Mutt-ng has a built-in pattern matching ``language'' which is as widely used as
173 possible to present a consistent interface to users. The same ``pattern terms''
174 can be used for searching, scoring, message selection and much more.
176 _
\b2_
\b._
\b2 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
178 _
\b2_
\b._
\b2_
\b._
\b1 _
\bI_
\bn_
\bd_
\be_
\bx
180 The index is the screen that you usually see first when you start mutt-ng. It
181 gives an overview over your emails in the currently opened mailbox. By default,
182 this is your system mailbox. The information you see in the index is a list of
184 The Mutt Next Generation E-Mail Client 5
186 emails, each with its number on the left, its flags (new email, important
187 email, email that has been forwarded or replied to, tagged email, ...), the
188 date when email was sent, its sender, the email size, and the subject. Addi-
189 tionally, the index also shows thread hierarchies: when you reply to an email,
190 and the other person replies back, you can see the other's person email in a
191 "sub-tree" below. This is especially useful for personal email between a group
192 of people or when you've subscribed to mailing lists.
194 _
\b2_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bg_
\be_
\br
196 The pager is responsible for showing the email content. On the top of the pager
197 you have an overview over the most important email headers like the sender, the
198 recipient, the subject, and much more information. How much information you
199 actually see depends on your configuration, which we'll describe below.
201 Below the headers, you see the email body which usually contains the message.
202 If the email contains any attachments, you will see more information about them
203 below the email body, or, if the attachments are text files, you can view them
204 directly in the pager.
206 To give the user a good overview, it is possible to configure mutt-ng to show
207 different things in the pager with different colors. Virtually everything that
208 can be described with a regular expression can be colored, e.g. URLs, email
209 addresses or smileys.
211 _
\b2_
\b._
\b2_
\b._
\b3 _
\bF_
\bi_
\bl_
\be _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
213 The file browser is the interface to the local or remote file system. When
214 selecting a mailbox to open, the browser allows custom sorting of items, limit-
215 ing the items shown by a regular expression and a freely adjustable format of
216 what to display in which way. It also allows for easy navigation through the
217 file system when selecting file(s) to attach to a message, select multiple
218 files to attach and many more.
220 _
\b2_
\b._
\b2_
\b._
\b4 _
\bS_
\bi_
\bd_
\be_
\bb_
\ba_
\br
222 The sidebar comes in handy to manage mails which are spread over different
223 folders. All folders users setup mutt-ng to watch for new mail will be listed.
224 The listing includes not only the name but also the number of total messages,
225 the number of new and flagged messages. Items with new mail may be colored dif-
226 ferent from those with flagged mail, items may be shortened or compress if
227 they're they to long to be printed in full form so that by abbreviated names,
228 user still now what the name stands for.
230 _
\b2_
\b._
\b2_
\b._
\b5 _
\bH_
\be_
\bl_
\bp
232 The Mutt Next Generation E-Mail Client 6
234 The help screen is meant to offer a quick help to the user. It lists the cur-
235 rent configuration of key bindings and their associated commands including a
236 short description, and currently unbound functions that still need to be asso-
237 ciated with a key binding (or alternatively, they can be called via the mutt-ng
240 _
\b2_
\b._
\b2_
\b._
\b6 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
242 The compose menu features a split screen containing the information which
243 really matter before actually sending a message by mail or posting an article
244 to a newsgroup: who gets the message as what (recipient, newsgroup, who gets
245 what kind of copy). Additionally, users may set security options like deciding
246 whether to sign, encrypt or sign and encrypt a message with/for what keys.
248 Also, it's used to attach messages, news articles or files to a message, to re-
249 edit any attachment including the message itself.
251 _
\b2_
\b._
\b2_
\b._
\b7 _
\bA_
\bl_
\bi_
\ba_
\bs _
\bM_
\be_
\bn_
\bu
253 The alias menu is used to help users finding the recipients of messages. For
254 users who need to contact many people, there's no need to remember addresses or
255 names completely because it allows for searching, too. The alias mechanism and
256 thus the alias menu also features grouping several addresses by a shorter nick-
257 name, the actual alias, so that users don't have to select each single recipi-
260 _
\b2_
\b._
\b2_
\b._
\b8 _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
262 As will be later discussed in detail, mutt-ng features a good and stable MIME
263 implementation, that is, is greatly supports sending and receiving messages of
264 arbitrary type. The attachment menu displays a message's structure in detail:
265 what content parts are attached to which parent part (which gives a true tree
266 structure), which type is of what type and what size. Single parts may saved,
267 deleted or modified to offer great and easy access to message's internals.
269 _
\b2_
\b._
\b2_
\b._
\b9 _
\bK_
\be_
\by _
\bM_
\be_
\bn_
\bu
273 _
\b2_
\b._
\b3 _
\bM_
\bo_
\bv_
\bi_
\bn_
\bg _
\bA_
\br_
\bo_
\bu_
\bn_
\bd _
\bi_
\bn _
\bM_
\be_
\bn_
\bu_
\bs
275 Information is presented in menus, very similar to ELM. Here is a table
277 The Mutt Next Generation E-Mail Client 7
279 showing the common keys used to navigate menus in Mutt-ng.
281 j or Down next-entry move to the next entry
282 k or Up previous-entry move to the previous entry
283 z or PageDn page-down go to the next page
284 Z or PageUp page-up go to the previous page
285 = or Home first-entry jump to the first entry
286 * or End last-entry jump to the last entry
287 q quit exit the current menu
288 ? help list all key bindings for the current menu
290 _
\b2_
\b._
\b4 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bI_
\bn_
\bp_
\bu_
\bt _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
292 Mutt-ng has a builtin line editor which is used as the primary way to input
293 textual data such as email addresses or filenames. The keys used to move
294 around while editing are very similar to those of Emacs.
296 ^A or <Home> bol move to the start of the line
297 ^B or <Left> backward-char move back one char
298 Esc B backward-word move back one word
299 ^D or <Delete> delete-char delete the char under the cursor
300 ^E or <End> eol move to the end of the line
301 ^F or <Right> forward-char move forward one char
302 Esc F forward-word move forward one word
303 <Tab> complete complete filename or alias
304 ^T complete-query complete address with query
305 ^K kill-eol delete to the end of the line
306 ESC d kill-eow delete to the end of the word
307 ^W kill-word kill the word in front of the cursor
308 ^U kill-line delete entire line
309 ^V quote-char quote the next typed key
310 <Up> history-up recall previous string from history
311 <Down> history-down recall next string from history
312 <BackSpace> backspace kill the char in front of the cursor
313 Esc u upcase-word convert word to upper case
314 Esc l downcase-word convert word to lower case
315 Esc c capitalize-word capitalize the word
317 <Return> n/a finish editing
319 You can remap the _
\be_
\bd_
\bi_
\bt_
\bo_
\br functions using the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 26) 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.329 , page 169) variable.
419 message is to you and you only
422 message is to you, but also to or cc'ed to others
425 message is cc'ed to you
431 message is sent to a subscribed mailing list
433 _
\b2_
\b._
\b5_
\b._
\b2 _
\bT_
\bh_
\be _
\bP_
\ba_
\bg_
\be_
\br
435 By default, Mutt-ng uses its builtin pager to display the body of messages.
437 The Mutt Next Generation E-Mail Client 10
439 The pager is very similar to the Unix program _
\bl_
\be_
\bs_
\bs though not nearly as fea-
442 <Return> go down one line
443 <Space> display the next page (or next message if at the end of a message)
444 - go back to the previous page
445 n search for next match
446 S skip beyond quoted text
447 T toggle display of quoted text
449 / search for a regular expression (pattern)
450 ESC / search backwards for a regular expression
451 \ toggle search pattern coloring
452 ^ jump to the top of the message
454 In addition, many of the functions from the _
\bi_
\bn_
\bd_
\be_
\bx are available in the pager,
455 such as _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be or _
\bc_
\bo_
\bp_
\by_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be (this is one advantage over using an
456 external pager to view messages).
458 Also, the internal pager supports a couple other advanced features. For one, it
459 will accept and translate the ``standard'' nroff sequences for bold and under-
460 line. These sequences are a series of either the letter, backspace (^H), the
461 letter again for bold or the letter, backspace, ``_'' for denoting underline.
462 Mutt-ng will attempt to display these in bold and underline respectively if
463 your terminal supports them. If not, you can use the bold and underline _
\bc_
\bo_
\bl_
\bo_
\br
464 (section 3.9 , page 30) objects to specify a color or mono attribute for them.
466 Additionally, the internal pager supports the ANSI escape sequences for charac-
467 ter attributes. Mutt-ng translates them into the correct color and character
468 settings. The sequences Mutt-ng supports are:
470 ESC [ Ps;Ps;Ps;...;Ps m
477 3x Foreground color is x
478 4x Background color is x
490 The Mutt Next Generation E-Mail Client 11
492 Mutt-ng uses these attributes for handling text/enriched messages, and they can
493 also be used by an external _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) script for high-
494 lighting purposes. N
\bNo
\bot
\bte
\be:
\b: If you change the colors for your display, for exam-
495 ple by changing the color associated with color2 for your xterm, then that
496 color will be used instead of green.
498 _
\b2_
\b._
\b5_
\b._
\b3 _
\bT_
\bh_
\br_
\be_
\ba_
\bd_
\be_
\bd _
\bM_
\bo_
\bd_
\be
500 When the mailbox is _
\bs_
\bo_
\br_
\bt_
\be_
\bd (section 7.4.297 , page 160) 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.115 , page 115). For example, you could use "%?M?(#%03M)&(%4l)?" in
522 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) to optionally display the number of
523 hidden messages if the thread is collapsed.
525 See also: _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 7.4.318 , page 167).
527 _
\b2_
\b._
\b5_
\b._
\b4 _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\be_
\bo_
\bu_
\bs _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
529 c
\bcr
\bre
\bea
\bat
\bte
\be-
\b-a
\bal
\bli
\bia
\bas
\bs
532 Creates a new alias based upon the current message (or prompts for a new one).
533 Once editing is complete, an _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 25) command is added to
534 the file specified by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 89) variable for
535 future use. N
\bNo
\bot
\bte
\be:
\b: Specifying an _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 89) does not
536 add the aliases specified there-in, you must also _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page
539 c
\bch
\bhe
\bec
\bck
\bk-
\b-t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl-
\b-p
\bpg
\bgp
\bp
542 This function will search the current message for content signed or encrypted
543 with PGP the "traditional" way, that is, without proper MIME tagging.
545 The Mutt Next Generation E-Mail Client 12
547 Technically, this function will temporarily change the MIME content types of
548 the body parts containing PGP data; this is similar to the _
\be_
\bd_
\bi_
\bt_
\b-_
\bt_
\by_
\bp_
\be (section
549 2.5.4 , page 12) function's effect.
551 d
\bdi
\bis
\bsp
\bpl
\bla
\bay
\by-
\b-t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-w
\bwe
\bee
\bed
\bd
554 Toggles the weeding of message header fields specified by _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section
555 3.10 , page 32) commands.
560 This command (available in the ``index'' and ``pager'') allows you to edit the
561 raw current message as it's present in the mail folder. After you have fin-
562 ished editing, the changed message will be appended to the current folder, and
563 the original message will be marked for deletion.
565 e
\bed
\bdi
\bit
\bt-
\b-t
\bty
\byp
\bpe
\be
567 (default: ^E on the attachment menu, and in the pager and index menus; ^T on
570 This command is used to temporarily edit an attachment's content type to fix,
571 for instance, bogus character set parameters. When invoked from the index or
572 from the pager, you'll have the opportunity to edit the top-level attachment's
573 content type. On the _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bm_
\be_
\bn_
\bu (section 5.1.2 , page 70), you can
574 change any attachment's content type. These changes are not persistent, and get
575 lost upon changing folders.
577 Note that this command is also available on the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bm_
\be_
\bn_
\bu (section 5.1.3 ,
578 page 71). There, it's used to fine-tune the properties of attachments you are
581 e
\ben
\bnt
\bte
\ber
\br-
\b-c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
584 This command is used to execute any command you would normally put in a config-
585 uration file. A common use is to check the settings of variables, or in con-
586 junction with _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 29) to change settings on the fly.
588 e
\bex
\bxt
\btr
\bra
\bac
\bct
\bt-
\b-k
\bke
\bey
\bys
\bs
591 This command extracts PGP public keys from the current or tagged message(s) and
592 adds them to your PGP public key ring.
594 f
\bfo
\bor
\brg
\bge
\bet
\bt-
\b-p
\bpa
\bas
\bss
\bsp
\bph
\bhr
\bra
\bas
\bse
\be
597 This command wipes the passphrase(s) from memory. It is useful, if you mis-
598 spelled the passphrase.
600 The Mutt Next Generation E-Mail Client 13
602 l
\bli
\bis
\bst
\bt-
\b-r
\bre
\bep
\bpl
\bly
\by
605 Reply to the current or tagged message(s) by extracting any addresses which
606 match the regular expressions given by the _
\bl_
\bi_
\bs_
\bt_
\bs _
\bo_
\br _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 ,
607 page 35) 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.93 , page 110) configuration variable is set.
609 Using this when replying to messages posted to mailing lists helps avoid dupli-
610 cate copies being sent to the author of the message you are replying to.
612 p
\bpi
\bip
\bpe
\be-
\b-m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
615 Asks for an external Unix command and pipes the current or tagged message(s) to
616 it. The variables _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.206 , page 139), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.208 , page 139), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.207 , page 139) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.340 , page 172) 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.341 , page 172) 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.340 , page 172) 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.231 , page 144) 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.314 , page 164) will change to a
759 'A' to indicate that you are in attach-message mode.
761 The Mutt Next Generation E-Mail Client 16
763 _
\b2_
\b._
\b6_
\b._
\b2 _
\bR_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg
765 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b1 _
\bS_
\bi_
\bm_
\bp_
\bl_
\be _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
767 When you want to reply to an email message, select it in the index menu and
768 then press r. Mutt-ng's behaviour is then similar to the behaviour when you
769 compose a message: first, you will be asked for the recipient, then for the
770 subject, and then, mutt-ng will start the editor with the quote attribution and
771 the quoted message. This can e.g. look like the example below.
773 On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote:
774 > Bill, can you please send last month's progress report to Mr.
775 > Morgan? We also urgently need the cost estimation for the new
776 > production server that we want to set up before our customer's
777 > project will go live.
779 You can start editing the email message. It is strongly recommended to put your
780 answer _
\bb_
\be_
\bl_
\bo_
\bw the quoted text and to only quote what is really necessary and
781 that you refer to. Putting your answer on top of the quoted message, is,
782 although very widespread, very often not considered to be a polite way to
785 The quote attribution is configurable, by default it is set to
787 set attribution = "On %d, %n wrote:"
789 It can also be set to something more compact, e.g.
791 set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
793 The example above results in the following attribution:
795 * Michael Svensson <svensson@foobar.com> [05-03-06 17:02]:
796 > Bill, can you please send last month's progress report to Mr.
797 > Morgan? We also urgently need the cost estimation for the new
798 > production server that we want to set up before our customer's
799 > project will go live.
801 Generally, try to keep your attribution short yet information-rich. It is _
\bn_
\bo_
\bt
802 the right place for witty quotes, long "attribution" novels or anything like
803 that: the right place for such things is - if at all - the email signature at
804 the very bottom of the message.
806 When you're done with writing your message, save and quit the editor. As
807 before, you will return to the compose menu, which is used in the same way as
809 The Mutt Next Generation E-Mail Client 17
813 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b2 _
\bG_
\br_
\bo_
\bu_
\bp _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
815 In the situation where a group of people uses email as a discussion, most of
816 the emails will have one or more recipients, and probably several "Cc:" recipi-
817 ents. The group reply functionality ensures that when you press g instead of r
818 to do a reply, each and every recipient that is contained in the original mes-
819 sage will receive a copy of the message, either as normal recipient or as "Cc:"
822 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b3 _
\bL_
\bi_
\bs_
\bt _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
824 When you use mailing lists, it's generally better to send your reply to a mes-
825 sage only to the list instead of the list and the original author. To make this
826 easy to use, mutt-ng features list replies.
828 To do a list reply, simply press L. If the email contains a Mail-Followup-To:
829 header, its value will be used as reply address. Otherwise, mutt-ng searches
830 through all mail addresses in the original message and tries to match them a
831 list of regular expressions which can be specified using the lists command. If
832 any of the regular expression matches, a mailing list address has been found,
833 and it will be used as reply address.
835 lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
837 Nowadays, most mailing list software like GNU Mailman adds a Mail-Followup-To:
838 header to their emails anyway, so setting lists is hardly ever necessary in
841 _
\b2_
\b._
\b6_
\b._
\b3 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br
843 When editing the header of your outgoing message, there are a couple of special
848 Fcc: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
850 Mutt-ng will pick up _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be just as if you had used the _
\be_
\bd_
\bi_
\bt_
\b-_
\bf_
\bc_
\bc function in
851 the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu.
853 You can also attach files to your message by specifying
855 The Mutt Next Generation E-Mail Client 18
857 Attach: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
859 where _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is the file to attach and _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn is an optional string to
860 use as the description of the attached file.
862 When replying to messages, if you remove the _
\bI_
\bn_
\b-_
\bR_
\be_
\bp_
\bl_
\by_
\b-_
\bT_
\bo_
\b: field from the header
863 field, Mutt-ng will not generate a _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be_
\bs_
\b: field, which allows you to cre-
864 ate a new message thread.
866 Also see _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102).
868 _
\b2_
\b._
\b6_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bw_
\bi_
\bt_
\bh _
\bP_
\bG_
\bP
870 If you want to use PGP, you can specify
872 Pgp: [ E | S | S_
\b<_
\bi_
\bd_
\b> ]
874 ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
875 _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.198 , page 137) 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.185 , page 134)) 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.145 ,
951 page 123)). 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.220 , page 142) 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.219 , page 142) quad-option.
1024 _
\b3_
\b. _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
1026 _
\b3_
\b._
\b1 _
\bL_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs _
\bo_
\bf _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1028 While the default configuration (or ``preferences'') make Mutt-ng usable right
1029 out of the box, it is often desirable to tailor Mutt-ng to suit your own
1030 tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
1031 configuration file (defaults set by your local system administrator), unless
1032 the ``-n'' _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be (section 7.1 , page 82) option is specified. This
1033 file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
1034 users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
1035 Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
1036 will look for .muttngrc. If this file does not exist and your home directory
1037 has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
1039 .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
1040 your _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page 85) to configure Mutt-ng.
1042 _
\b3_
\b._
\b2 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bS_
\by_
\bn_
\bt_
\ba_
\bx _
\bo_
\bf _
\bI_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1044 An initialization file consists of a series of _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page
1045 85). Each line of the file may contain one or more commands. When multiple
1046 commands are used, they must be separated by a semicolon (;).
1048 set realname='Mutt-ng user' ; ignore x-
1050 The hash mark, or pound sign (``#''), is used as a ``comment'' character. You
1051 can use it to annotate your initialization file. All text after the comment
1052 character to the end of the line is ignored. For example,
1054 my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
1056 Single quotes (') and double quotes (') can be used to quote strings which
1058 The Mutt Next Generation E-Mail Client 22
1060 contain spaces or other special characters. The difference between the two
1061 types of quotes is similar to that of many popular shell programs, namely that
1062 a single quote is used to specify a literal string (one that is not interpreted
1063 for shell variables or quoting with a backslash [see next paragraph]), while
1064 double quotes indicate a string for which should be evaluated. For example,
1065 backtics are evaluated inside of double quotes, but n
\bno
\bot
\bt for single quotes.
1067 \ quotes the next character, just as in shells such as bash and zsh. For exam-
1068 ple, if want to put quotes ``''' inside of a string, you can use ``\'' to force
1069 the next character to be a literal instead of interpreted character.
1071 set realname="Michael \"MuttDude\" Elkins"
1073 ``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r'' have
1074 their usual C meanings of linefeed and carriage-return, respectively.
1076 A \ at the end of a line can be used to split commands over multiple lines,
1077 provided that the split points don't appear in the middle of command names.
1079 Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the
1080 end of a line also in comments. This allows you to disable a command split over
1081 multiple lines with only one ``#''.
1084 set realname="Michael \"MuttDude\" Elkins"
1086 When testing your config files, beware the following caveat. The backslash at
1087 the end of the commented line extends the current line with the next line -
1088 then referred to as a ``continuation line''. As the first line is commented
1089 with a hash (#) all following continuation lines are also part of a comment and
1090 therefore are ignored, too. So take care of comments when continuation lines
1091 are involved within your setup files!
1101 line1 ``continues'' until line4. however, the part after the # is a comment
1102 which includes line3 and line4. line5 is a new line of its own and thus is
1105 The commands understood by mutt are explained in the next paragraphs. For a
1106 complete list, see the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.3 , page 85).
1108 The Mutt Next Generation E-Mail Client 23
1110 _
\b3_
\b._
\b3 _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
1112 _
\b3_
\b._
\b3_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs_
\b' _
\bO_
\bu_
\bt_
\bp_
\bu_
\bt
1114 It is possible to substitute the output of a Unix command in an initialization
1115 file. This is accomplished by enclosing the command in backquotes (``) as in,
1118 my_hdr X-Operating-System: `uname -a`
1120 The output of the Unix command ``uname -a'' will be substituted before the line
1121 is parsed. Note that since initialization files are line oriented, only the
1122 first line of output from the Unix command will be substituted.
1124 _
\b3_
\b._
\b3_
\b._
\b2 _
\bE_
\bn_
\bv_
\bi_
\br_
\bo_
\bn_
\bm_
\be_
\bn_
\bt _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1126 UNIX environments can be accessed like the way it is done in shells like sh and
1127 bash: Prepend the name of the environment by a ``$'' sign. For example,
1129 set record=+sent_on_$HOSTNAME
1131 sets the _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146) variable to the string _
\b+_
\bs_
\be_
\bn_
\bt_
\b__
\bo_
\bn_
\b_
1132 and appends the value of the evironment variable $HOSTNAME.
1134 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if an environment variable is not defined. The
1135 result will of the expansion will then be empty.
1137 _
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1139 As for environment variables, the values of all configuration variables as
1140 string can be used in the same way, too. For example,
1142 set imap_home_namespace = $folder
1144 would set the value of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.100 , page 112) to
1145 the value to which _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) is _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by set to.
1147 N
\bNo
\bot
\bte
\be:
\b: There're no logical links established in such cases so that the the value
1148 for _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.100 , page 112) won't change even if
1149 _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) gets changed.
1151 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if a configuration variable is not defined or is
1152 empty. The result will of the expansion will then be empty.
1154 _
\b3_
\b._
\b3_
\b._
\b4 _
\bS_
\be_
\bl_
\bf_
\b-_
\bD_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1156 Mutt-ng flexibly allows users to define their own variables. To avoid conflicts
1157 with the standard set and to prevent misleading error messages, there's a
1159 The Mutt Next Generation E-Mail Client 24
1161 reserved namespace for them: all user-defined variables must be prefixed with
1162 user_ and can be used just like any ordinary configuration or environment vari-
1165 For example, to view the manual, users can either define two macros like the
1168 macro generic <F1> "!less -r /path/to/manual" "Show manual"
1169 macro pager <F1> "!less -r /path/to/manual" "Show manual"
1171 for generic, pager and index. The alternative is to define a custom variable
1174 set user_manualcmd = '!less -r /path/to_manual'
1175 macro generic <F1> "$user_manualcmd<enter>" "Show manual"
1176 macro pager <F1> "$user_manualcmd<enter>" "Show manual"
1177 macro index <F1> "$user_manualcmd<enter>" "Show manual"
1179 to re-use the command sequence as in:
1181 macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
1183 Using this feature, arbitrary sequences can be defined once and recalled and
1184 reused where necessary. More advanced scenarios could include to save a vari-
1185 able's value at the beginning of macro sequence and restore it at end.
1187 When the variable is first defined, the first value it gets assigned is also
1188 the initial value to which it can be reset using the reset command.
1190 The complete removal is done via the unset keyword.
1192 After the following sequence:
1197 the variable $user_foo has a current value of 666 and an initial of 42. The
1202 will show 666. After doing the reset via
1204 The Mutt Next Generation E-Mail Client 25
1208 a following query will give 42 as the result. After unsetting it via
1212 any query or operation (except the noted expansion within other statements)
1213 will lead to an error message.
1215 _
\b3_
\b._
\b3_
\b._
\b5 _
\bT_
\by_
\bp_
\be _
\bC_
\bo_
\bn_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn_
\bs
1217 A note about variable's types during conversion: internally values are stored
1218 in internal types but for any dump/query or set operation they're converted to
1219 and from string. That means that there's no need to worry about types when ref-
1220 erencing any variable. As an example, the following can be used without harm
1221 (besides makeing muttng very likely behave strange):
1224 set folder = $read_inc
1225 set read_inc = $folder
1226 set user_magic_number = 42
1227 set folder = $user_magic_number
1229 _
\b3_
\b._
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1231 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1233 It's usually very cumbersome to remember or type out the address of someone you
1234 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1235 short string to a full address.
1237 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1238 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1240 To remove an alias or aliases (``*'' means all aliases):
1242 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1244 alias muttdude me@cs.hmc.edu (Michael Elkins)
1245 alias theguys manny, moe, jack
1247 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1248 cial file. The alias command can appear anywhere in a configuration file, as
1249 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.29 , page 45). Consequently, you can
1250 have multiple alias files, or you can have all aliases defined in your muttrc.
1252 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
1254 The Mutt Next Generation E-Mail Client 26
1256 only one file, the one pointed to by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 89)
1257 variable (which is ~/.muttrc by default). This file is not special either, in
1258 the sense that Mutt-ng will happily append aliases to any file, but in order
1259 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1260 3.29 , page 45) this file too.
1264 source /usr/local/share/Mutt-ng.aliases
1265 source ~/.mail_aliases
1266 set alias_file=~/.mail_aliases
1268 To use aliases, you merely use the alias at any place in mutt where mutt
1269 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1270 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
1271 (section 7.4.59 , page 102) variable set.
1273 In addition, at the various address prompts, you can use the tab character to
1274 expand a partial alias to the full alias. If there are multiple matches, mutt
1275 will bring up a menu with the matching aliases. In order to be presented with
1276 the full list of aliases, you must hit tab with out a partial alias, such as at
1277 the beginning of the prompt or after a comma denoting multiple addresses.
1279 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1280 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1283 _
\b3_
\b._
\b5 _
\bC_
\bh_
\ba_
\bn_
\bg_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs
1285 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1287 This command allows you to change the default key bindings (operation invoked
1288 when pressing a key).
1290 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be speci-
1291 fied by separating them with commas (no additional whitespace is allowed). The
1292 currently defined maps are:
1295 This is not a real menu, but is used as a fallback for all of the
1296 other menus except for the pager and editor modes. If a key is not
1297 defined in another menu, Mutt-ng will look for a binding to use in
1298 this menu. This allows you to bind a key to a certain function in
1299 multiple menus instead of having multiple bind statements to accom-
1300 plish the same task.
1303 The alias menu is the list of your personal aliases as defined in
1305 The Mutt Next Generation E-Mail Client 27
1307 your muttrc. It is the mapping from a short alias name to the full
1308 email address(es) of the recipient(s).
1311 The attachment menu is used to access the attachments on received
1315 The browser is used for both browsing the local directory struc-
1316 ture, and for listing all of your incoming mailboxes.
1319 The editor is the line-based editor the user enters text data.
1322 The index is the list of messages contained in a mailbox.
1325 The compose menu is the screen used when sending a new message.
1328 The pager is the mode used to display message/attachment data, and
1332 The pgp menu is used to select the OpenPGP keys used for encrypting
1336 The postpone menu is similar to the index menu, except is used when
1337 recalling a message the user was composing, but saved until later.
1339 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1340 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1341 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1342 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
1343 alternative form is to specify the key as a three digit octal number prefixed
1344 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1346 In addition, _
\bk_
\be_
\by may consist of:
1348 The Mutt Next Generation E-Mail Client 28
1352 <backtab> backtab / shift-tab
1362 <pagedown> Page Down
1363 <backspace> Backspace
1372 <f10> function key 10
1374 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1376 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1377 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 174). The special
1378 function noop unbinds the specified key sequence.
1380 _
\b3_
\b._
\b6 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs _
\bf_
\bo_
\br _
\bc_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bs_
\be_
\bt_
\bs
1382 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1384 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1386 The charset-hook command defines an alias for a character set. This is useful
1387 to properly display messages which are tagged with a character set name not
1390 The iconv-hook command defines a system-specific name for a character set.
1391 This is helpful when your systems character conversion library insists on using
1392 strange, system-specific names for character sets.
1394 _
\b3_
\b._
\b7 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1396 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1398 It is often desirable to change settings based on which mailbox you are
1400 The Mutt Next Generation E-Mail Client 29
1402 reading. The folder-hook command provides a method by which you can execute
1403 any configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1404 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1405 folder-hook's, they are executed in the order given in the muttrc.
1407 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.303 , page
1408 162) at the beginning of the pattern, you must place it inside of double or
1409 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1412 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1413 ple, a command action to perform is to change the sorting method based upon the
1416 folder-hook mutt set sort=threads
1418 However, the sorting method is not restored to its previous value when reading
1419 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1421 folder-hook . set sort=date-sent
1423 _
\b3_
\b._
\b8 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1425 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 ]
1427 Macros are useful when you would like a single key to perform a series of
1428 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1429 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1430 create a macro to execute those commands with a single key.
1432 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.5 , page 26) which the macro will be bound. Multi-
1433 ple maps may be specified by separating multiple menu arguments by commas.
1434 Whitespace may not be used in between the menu arguments and the commas sepa-
1437 _
\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
1438 3.5 , page 26). There are some additions however. The first is that control
1439 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1440 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1441 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
1442 _
\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
1443 3.5 , page 26). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1446 The advantage with using function names directly is that the macros will work
1447 regardless of the current key bindings, so they are not dependent on the user
1448 having particular key definitions. This makes them more robust and portable,
1449 and also facilitates defining of macros in files used by more than one user
1451 The Mutt Next Generation E-Mail Client 30
1453 (eg. the system Muttngrc).
1455 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1458 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1459 truncated at the screen width, and are not wrapped.
1461 _
\b3_
\b._
\b9 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bc_
\bo_
\bl_
\bo_
\br _
\ba_
\bn_
\bd _
\bm_
\bo_
\bn_
\bo _
\bv_
\bi_
\bd_
\be_
\bo _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be_
\bs
1463 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 ]
1465 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
1467 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1469 If your terminal supports color, you can spice up Mutt-ng by creating your own
1470 color scheme. To define the color of an object (type of information), you must
1471 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1472 only specify one or the other).
1474 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1478 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1480 +
\bo bold (highlighting bold patterns in the body of messages)
1482 +
\bo error (error messages printed by Mutt-ng)
1484 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1486 +
\bo hdrdefault (default color of the message header in the pager)
1488 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1490 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1492 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1494 +
\bo message (informational messages)
1498 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.231 , page 144) in the
1501 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1503 +
\bo search (highlighting of words in the pager)
1505 The Mutt Next Generation E-Mail Client 31
1509 +
\bo status (mode lines used to display info about the mailbox or message)
1511 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1513 +
\bo tree (thread tree drawn in the message index and attachment menu)
1515 +
\bo underline (highlighting underlined patterns in the body of messages)
1517 _
\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:
1539 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the fore-
1540 ground color boldfaced (e.g., brightred).
1542 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1543 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1544 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-
1545 ment variable to the default colors of your terminal for this to work; for
1546 example (for Bourne-like shells):
1548 set COLORFGBG="green;black"
1551 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
1552 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1554 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1555 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1556 command for it to be removed. The pattern ``*'' is a special token which means
1557 to clear the color index list of all entries.
1559 The Mutt Next Generation E-Mail Client 32
1561 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
1562 number of colors supported by your terminal). This is useful when you remap
1563 the colors for your display (for example by changing the color associated with
1564 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1566 If your terminal does not support color, it is still possible change the video
1567 attributes through the use of the ``mono'' command:
1569 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 ]
1571 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1573 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1575 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1587 _
\b3_
\b._
\b1_
\b0 _
\bI_
\bg_
\bn_
\bo_
\br_
\bi_
\bn_
\bg _
\b(_
\bw_
\be_
\be_
\bd_
\bi_
\bn_
\bg_
\b) _
\bu_
\bn_
\bw_
\ba_
\bn_
\bt_
\be_
\bd _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1589 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1591 Messages often have many header fields added by automatic processing systems,
1592 or which may not seem useful to display on the screen. This command allows you
1593 to specify header fields which you don't normally want to see.
1595 You do not need to specify the full header field name. For example, ``ignore
1596 content-'' will ignore all header fields that begin with the pattern ``con-
1597 tent-''. ``ignore *'' will ignore all headers.
1599 To remove a previously added token from the list, use the ``unignore'' command.
1600 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1601 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1604 ``unignore *'' will remove all tokens from the ignore list.
1608 # Sven's draconian header weeding
1610 unignore from date subject to cc
1611 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1614 The Mutt Next Generation E-Mail Client 33
1616 _
\b3_
\b._
\b1_
\b1 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1618 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1620 With various functions, mutt will treat messages differently, depending on
1621 whether you sent them or whether you received them from someone else. For
1622 instance, when replying to a message that you sent to a different party, mutt
1623 will automatically suggest to send the response to the original message's
1624 recipients -- responding to yourself won't make much sense in many cases. (See
1625 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.239 , page 146).)
1627 Many users receive e-mail under a number of different addresses. To fully use
1628 mutt's features here, the program must be able to recognize what e-mail
1629 addresses you receive mail under. That's the purpose of the alternates command:
1630 It takes a list of regular expressions, each of which can identify an address
1631 under which you receive e-mail.
1633 The unalternates command can be used to write exceptions to alternates pat-
1634 terns. If an address matches something in an alternates command, but you none-
1635 theless do not think it is from you, you can list a more precise pattern under
1636 an unalternates command.
1638 To remove a regular expression from the alternates list, use the unalternates
1639 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1640 command matches an entry on the unalternates list, that unalternates entry will
1641 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
1644 _
\b3_
\b._
\b1_
\b2 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1646 _
\b3_
\b._
\b1_
\b2_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
1648 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1649 ning of email, each message had a fixed line width, and it was enough for dis-
1650 playing them on fixed-size terminals. But times changed, and nowadays hardly
1651 anybody still uses fixed-size terminals: more people nowaydays use graphical
1652 user interfaces, with dynamically resizable windows. This led to the demand of
1653 a new email format that makes it possible for the email client to make the
1654 email look nice in a resizable window without breaking quoting levels and cre-
1655 ating an incompatible email format that can also be displayed nicely on old
1656 fixed-size terminals.
1658 For introductory information on format=flowed messages, see
1659 <http://www.joeclark.org/ffaq.html>.
1661 _
\b3_
\b._
\b1_
\b2_
\b._
\b2 _
\bR_
\be_
\bc_
\be_
\bi_
\bv_
\bi_
\bn_
\bg_
\b: _
\bD_
\bi_
\bs_
\bp_
\bl_
\ba_
\by _
\bS_
\be_
\bt_
\bu_
\bp
1663 When you receive emails that are marked as format=flowed messages, and is for-
1664 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1665 your terminal. If you want a fixed margin on the right side of your terminal,
1666 you can set the following:
1668 The Mutt Next Generation E-Mail Client 34
1672 The code above makes the line break 10 columns before the right side of the
1675 If your terminal is so wide that the lines are embarrassingly long, you can
1676 also set a maximum line length:
1678 set max_line_length = 120
1680 The example above will give you lines not longer than 120 characters.
1682 When you view at format=flowed messages, you will often see the quoting hierar-
1683 chy like in the following example:
1685 >Bill, can you please send last month's progress report to Mr.
1686 >Morgan? We also urgently need the cost estimation for the new
1687 >production server that we want to set up before our customer's
1688 >project will go live.
1690 This obviously doesn't look very nice, and it makes it very hard to differenti-
1691 ate between text and quoting character. The solution is to configure mutt-ng to
1692 "stuff" the quoting:
1696 This will lead to a nicer result that is easier to read:
1698 > Bill, can you please send last month's progress report to Mr.
1699 > Morgan? We also urgently need the cost estimation for the new
1700 > production server that we want to set up before our customer's
1701 > project will go live.
1703 _
\b3_
\b._
\b1_
\b2_
\b._
\b3 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg
1705 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1710 The Mutt Next Generation E-Mail Client 35
1712 Additionally, you have to use an editor which supports writing format=flowed-
1713 conforming emails. For vim, this is done by adding w to the formatoptions (see
1714 :h formatoptions and :h fo-table) when writing emails.
1716 Also note that _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\b=_
\bf_
\bl_
\bo_
\bw_
\be_
\bd knows about ``space-stuffing'', that is, when
1717 sending messages, some kinds of lines have to be indented with a single space
1718 on the sending side. On the receiving side, the first space (if any) is
1719 removed. As a consequence and in addition to the above simple setting, please
1720 keep this in mind when making manual formattings within the editor. Also note
1721 that mutt-ng currently violates the standard (RfC 3676) as it does not space-
1722 stuff lines starting with:
1724 +
\bo > This is _
\bn_
\bo_
\bt the quote character but a right angle used for other reasons
1726 +
\bo From with a trailing space.
1728 +
\bo just a space for formatting reasons
1730 Please make sure that you manually prepend a space to each of them.
1732 _
\b3_
\b._
\b1_
\b2_
\b._
\b4 _
\bA_
\bd_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bN_
\bo_
\bt_
\be_
\bs
1736 For completeness, the _
\b$_
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.51 , page 100) variable pro-
1737 vides the mechanism to generate a DelSp=yes parameter on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages.
1738 According to the standard, clients receiving a format=flowed messages should
1739 delete the last space of a flowed line but still interpret the line as flowed.
1740 Because flowed lines usually contain only one space at the end, this parameter
1741 would make the receiving client concatenate the last word of the previous with
1742 the first of the current line _
\bw_
\bi_
\bt_
\bh_
\bo_
\bu_
\bt a space. This makes ordinary text unread-
1743 able and is intended for languages rarely using spaces. So please use this set-
1744 ting only if you're sure what you're doing.
1746 _
\b3_
\b._
\b1_
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1748 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1750 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1752 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 ,
1753 page 60). In order to take advantage of them, you must specify which addresses
1754 belong to mailing lists, and which mailing lists you are subscribed to. Once
1755 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1756 work for all known lists. Additionally, when you send a message to a sub-
1757 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1758 user agents not to send copies of replies to your personal address. Note that
1759 the Mail-Followup-To header is a non-standard extension which is not supported
1760 by all mail user agents. Adding it is not bullet-proof against receiving per-
1761 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1762 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.71 , page 105)
1763 configuration variable.
1765 The Mutt Next Generation E-Mail Client 36
1767 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1768 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1769 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1772 You can use regular expressions with both commands. To mark all messages sent
1773 to a specific bug report's address on mutt's bug tracking system as list mail,
1774 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1775 sufficient to just give a portion of the list's e-mail address.
1777 Specify as much of the address as you need to to remove ambiguity. For exam-
1778 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1779 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
1780 list, you could add ``lists mutt-users'' to your initialization file. To tell
1781 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1782 tialization file instead. If you also happen to get mail from someone whose
1783 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-
1784 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1785 from the actual list.
1787 The ``unlists'' command is used to remove a token from the list of known and
1788 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1790 To remove a mailing list from the list of subscribed mailing lists, but keep it
1791 on the list of known mailing lists, use ``unsubscribe''.
1793 _
\b3_
\b._
\b1_
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bl_
\bt_
\bi_
\bp_
\bl_
\be _
\bs_
\bp_
\bo_
\bo_
\bl _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs
1795 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1797 This command is used to move read messages from a specified mailbox to a dif-
1798 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1799 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1800 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1802 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1803 (it is not possible to save read mail in more than a single mailbox).
1805 _
\b3_
\b._
\b1_
\b5 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs _
\bw_
\bh_
\bi_
\bc_
\bh _
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be _
\bm_
\ba_
\bi_
\bl
1807 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1809 This command specifies folders which can receive mail and which will be checked
1810 for new messages. By default, the main menu status bar displays how many of
1811 these folders have new messages.
1813 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1815 Pressing TAB in the directory browser will bring up a menu showing the files
1816 specified by the mailboxes command, and indicate which contain new messages.
1818 The Mutt Next Generation E-Mail Client 37
1820 Mutt-ng will automatically enter this mode when invoked from the command line
1823 The ``unmailboxes'' command is used to remove a token from the list of folders
1824 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1826 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1827 access time. Utilities like biff or frm or any other program which accesses
1828 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1829 they do not properly reset the access time. Backup tools are another common
1830 reason for updated access times.
1832 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1833 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
1834 60) (such as ``='' and ``!''), any variable definition that affect these char-
1835 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1836 7.4.303 , page 162)) should be executed before the mailboxes command.
1838 _
\b3_
\b._
\b1_
\b6 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1842 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1844 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1846 The ``my_hdr'' command allows you to create your own header fields which will
1847 be added to every message you send.
1849 For example, if you would like to add an ``Organization:'' header field to all
1850 of your outgoing messages, you can put the command
1852 my_hdr Organization: A Really Big Company, Anytown, USA
1856 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1857 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1858 there, so Mutt-ng enforces the rule.
1860 If you would like to add a header field to a single message, you should either
1861 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1862 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1863 header of your message along with the body.
1865 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1866 specify an asterisk (``*'') to remove all header fields, or the fields to
1867 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1870 The Mutt Next Generation E-Mail Client 38
1874 _
\b3_
\b._
\b1_
\b7 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bo_
\br_
\bd_
\be_
\br _
\bo_
\bf _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs _
\bw_
\bh_
\be_
\bn _
\bv_
\bi_
\be_
\bw_
\bi_
\bn_
\bg _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
1876 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1878 With this command, you can specify an order in which mutt will attempt to
1879 present headers to you when viewing messages.
1881 ``unhdr_order *'' will clear all previous headers from the order list, thus
1882 removing the header order effects set by the system-wide startup file.
1884 hdr_order From Date: From: To: Cc: Subject:
1886 _
\b3_
\b._
\b1_
\b8 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1888 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1890 This command is used to override the default filename used when saving mes-
1891 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:
1892 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1893 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1895 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1896 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1900 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1901 save-hook aol\\.com$ +spam
1903 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39) command.
1905 _
\b3_
\b._
\b1_
\b9 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bw_
\bh_
\be_
\bn _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg
1907 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1909 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1910 (section 7.4.236 , page 146). Mutt-ng searches the initial list of message
1911 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1912 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1913 7.4.236 , page 146) mailbox.
1915 The Mutt Next Generation E-Mail Client 39
1917 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1918 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1920 Example: fcc-hook [@.]aol\\.com$ +spammers
1922 The above will save a copy of all messages going to the aol.com domain to the
1923 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 ,
1926 _
\b3_
\b._
\b2_
\b0 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be _
\ba_
\bn_
\bd _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\ba_
\bt _
\bo_
\bn_
\bc_
\be
1928 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1930 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1931 3.19 , page 38) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38) with its arguments.
1933 _
\b3_
\b._
\b2_
\b1 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt_
\bs
1935 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1937 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1939 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1941 These commands can be used to execute arbitrary configuration commands based
1942 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1943 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1946 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1947 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1948 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
1949 the order specified in the users's configuration file.
1951 send2-hook is matched every time a message is changed, either by editing it, or
1952 by using the compose menu to change its recipients or subject. send2-hook is
1953 executed after send-hook, and can, e.g., be used to set parameters such as the
1954 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page 150) variable depending on the message's
1957 For each type of send-hook or reply-hook, when multiple matches occur, commands
1958 are executed in the order they are specified in the muttrc (for that type of
1961 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1962 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1964 Example: send-hook mutt 'set mime_forward signature='''
1966 Another typical use for this command is to change the values of the
1968 The Mutt Next Generation E-Mail Client 40
1970 _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 93), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.265 , page
1971 153) and _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.119 , page 118) variables in order to change the
1972 language of the attributions and signatures based upon the recipients.
1974 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
1975 recipients. Adding a recipient after replying or editing the message will NOT
1976 cause any send-hook to be executed. Also note that my_hdr commands which mod-
1977 ify recipient headers, or the message's subject, don't have any effect on the
1978 current message when executed from a send-hook.
1980 _
\b3_
\b._
\b2_
\b2 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\be_
\bf_
\bo_
\br_
\be _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bt_
\bi_
\bn_
\bg _
\ba _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
1982 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1984 This command can be used to execute arbitrary configuration commands before
1985 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
1986 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
1987 tiple matches occur, commands are executed in the order they are specified in
1990 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1991 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1995 message-hook ~A 'set pager=builtin'
1996 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1998 _
\b3_
\b._
\b2_
\b3 _
\bC_
\bh_
\bo_
\bo_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bc_
\br_
\by_
\bp_
\bt_
\bo_
\bg_
\br_
\ba_
\bp_
\bh_
\bi_
\bc _
\bk_
\be_
\by _
\bo_
\bf _
\bt_
\bh_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt
2000 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
2002 When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
2003 tain key with a given e-mail address automatically, either because the recipi-
2004 ent's public key can't be deduced from the destination address, or because, for
2005 some reasons, you need to override the key Mutt-ng would normally use. The
2006 crypt-hook command provides a method by which you can specify the ID of the
2007 public key to be used when encrypting messages to a certain recipient.
2009 The meaning of "key id" is to be taken broadly in this context: You can either
2010 put a numerical key ID here, an e-mail address, or even just a real name.
2012 _
\b3_
\b._
\b2_
\b4 _
\bA_
\bd_
\bd_
\bi_
\bn_
\bg _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be_
\bs _
\bt_
\bo _
\bt_
\bh_
\be _
\bk_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bb_
\bu_
\bf_
\bf_
\be_
\br
2014 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
2016 This command adds the named string to the keyboard buffer. The string may
2018 The Mutt Next Generation E-Mail Client 41
2020 contain control characters, key names and function names like the sequence
2021 string in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 29) command. You may use it to auto-
2022 matically run a sequence of commands at startup, or when entering certain fold-
2025 _
\b3_
\b._
\b2_
\b5 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
2027 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
2029 This command can be used to execute any function. Functions are listed in the
2030 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 174). ``exec function'' is equivalent
2031 to ``push <function>''.
2033 _
\b3_
\b._
\b2_
\b6 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
2035 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
2037 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
2039 In situations where you have to cope with a lot of emails, e.g. when you read
2040 many different mailing lists, and take part in discussions, it is always useful
2041 to have the important messages marked and the annoying messages or the ones
2042 that you aren't interested in deleted. For this purpose, mutt-ng features a
2043 mechanism called ``scoring''.
2045 When you use scoring, every message has a base score of 0. You can then use the
2046 score command to define patterns and a positive or negative value associated
2047 with it. When a pattern matches a message, the message's score will be raised
2048 or lowered by the amount of the value associated with the pattern.
2050 score "~f nion@muttng\.org" 50
2051 score "~f @sco\.com" -100
2053 If the pattern matches, it is also possible to set the score value of the cur-
2054 rent message to a certain value and then stop evaluation:
2056 score "~f santaclaus@northpole\.int" =666
2058 What is important to note is that negative score values will be rounded up to
2061 To make scoring actually useful, the score must be applied in some way. That's
2062 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:
2064 +
\bo flag threshold: when a message has a score value equal or higher than the
2065 flag threshold, it will be flagged.
2067 The Mutt Next Generation E-Mail Client 42
2069 +
\bo read threshold: when a message has a score value equal or lower than the
2070 read threshold, it will be marked as read.
2072 +
\bo delete threshold: when a message has a score value equal or lower than the
2073 delete threshold, it will be marked as deleted.
2075 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-
2076 tion 7.4.250 , page 149), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.251 , page 149),
2077 _
\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.249 , page 149) and. By default,
2078 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.251 , page 149) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
2079 (section 7.4.249 , page 149) are set to -1, which means that in the default
2080 threshold configuration no message will ever get marked as read or deleted.
2082 Scoring gets especially interesting when combined with the color command and
2085 color index black yellow "~n 10-"
2086 color index red yellow "~n 100-"
2088 The rules above mark all messages with a score between 10 and 99 with black and
2089 yellow, and messages with a score greater or equal 100 with red and yellow.
2090 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
2091 but it is more flexible, as it visually marks different scores.
2093 _
\b3_
\b._
\b2_
\b7 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
2095 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2097 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
2099 Mutt-ng has generalized support for external spam-scoring filters. By defining
2100 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
2101 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
2102 filter. You also can display the spam attributes in your index display using
2103 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) variable.
2104 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
2107 Your first step is to define your external filter's spam patterns using the
2108 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
2109 mail message. If any message in the mailbox matches this regular expression, it
2110 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
2111 nospam pattern -- see below.) The appearance of this attribute is entirely up
2112 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,
2113 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
2114 expression ``back-reference'' refers to a sub-expression contained within
2115 parentheses.) %1 is replaced with the first back-reference in the regex, %2
2116 with the second, etc.
2118 If you're using multiple spam filters, a message can have more than one spam-
2120 The Mutt Next Generation E-Mail Client 43
2122 related header. You can define spam patterns for each filter you use. If a mes-
2123 sage matches two or more of these patterns, and the $spam_separator variable is
2124 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2125 strings joined together, with the value of $spam_separator separating them.
2127 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
2128 these spam settings:
2130 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
2131 spam "X-Spam-Status: Yes" "90+/SA"
2132 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
2133 set spam_separator=", "
2135 If I then received a message that DCC registered with ``many'' hits under the
2136 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
2137 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
2138 characters before ``=many'' in a DCC report indicate the checksum used -- in
2139 this case, ``Fuz2''.)
2141 If the $spam_separator variable is unset, then each spam pattern match super-
2142 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
2143 only the last one to match.
2145 The spam tag is what will be displayed in the index when you use %H in the
2146 $index_format variable. It's also the string that the ~H pattern-matching
2147 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2148 ing by spam attribute will use as a sort key.
2150 That's a pretty complicated example, and most people's actual environments will
2151 have only one spam filter. The simpler your configuration, the more effective
2152 mutt can be, especially when it comes to sorting.
2154 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2155 ordering strings alphnumerically. However, if a spam tag begins with a number,
2156 mutt will sort numerically first, and lexically only when two numbers are equal
2157 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2158 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2159 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2160 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2161 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2162 coerce your filter to give you a raw number. But in case you can't, mutt can
2163 still do something useful.
2165 The nospam command can be used to write exceptions to spam patterns. If a
2166 header pattern matches something in a spam command, but you nonetheless do not
2167 want it to receive a spam tag, you can list a more precise pattern under a
2170 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-
2171 ing spam list entry, the effect will be to remove the entry from the spam list,
2172 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2173 matches an entry on the nospam list, that nospam entry will be removed. If the
2174 _
\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
2176 The Mutt Next Generation E-Mail Client 44
2178 might be the default action if you use spam and nospam in conjunction with a
2181 You can have as many spam or nospam commands as you like. You can even do your
2182 own primitive spam detection within mutt -- for example, if you consider all
2183 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2185 spam "^From: .*MAILER-DAEMON" "999"
2187 _
\b3_
\b._
\b2_
\b8 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2189 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 ... ]
2191 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2193 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2195 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2197 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 ,
2198 page 87). There are four basic types of variables: boolean, number, string and
2199 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
2200 variables can be assigned a positive integer value.
2202 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2203 be enclosed in quotes if they contain spaces or tabs. You may also use the
2204 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2206 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2207 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2208 action to be carried out automatically as if you had answered yes to the ques-
2209 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2210 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2211 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2213 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2215 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2216 toggle the value (on or off). This is useful when writing macros. Example:
2219 The toggle command automatically prepends the inv prefix to all specified vari-
2222 The unset command automatically prepends the no prefix to all specified vari-
2225 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2226 a variable by prefixing the name of the variable with a question mark:
2228 The Mutt Next Generation E-Mail Client 45
2232 The question mark is actually only required for boolean and quadoption vari-
2235 The reset command resets all given variables to the compile time defaults
2236 (hopefully mentioned in this manual). If you use the command set and prefix the
2237 variable with ``&'' this has the same behavior as the reset command.
2239 With the reset command there exists the special variable ``all'', which allows
2240 you to reset all variables to their system defaults.
2242 _
\b3_
\b._
\b2_
\b9 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bi_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs _
\bf_
\br_
\bo_
\bm _
\ba_
\bn_
\bo_
\bt_
\bh_
\be_
\br _
\bf_
\bi_
\bl_
\be
2244 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2246 This command allows the inclusion of initialization commands from other files.
2247 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2248 ~/.muttrc readable and keep my aliases private.
2250 If the filename begins with a tilde (``~''), it will be expanded to the path of
2251 your home directory.
2253 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2254 an executable program from which to read input (eg. source ~/bin/myscript|).
2256 _
\b3_
\b._
\b3_
\b0 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2258 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2260 This command permits you to flush hooks you have previously defined. You can
2261 either remove all hooks by giving the ``*'' character as an argument, or you
2262 can remove all hooks of a specific type by saying something like unhook send-
2265 _
\b3_
\b._
\b3_
\b1 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2267 _
\b3_
\b._
\b3_
\b1_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2269 As users may run mutt-ng on different systems, the configuration must be main-
2270 tained because it's likely that people want to use the setup everywhere they
2271 use mutt-ng. And mutt-ng tries to help where it can.
2273 To not produce conflicts with different character sets, mutt-ng allows users to
2274 specify in which character set their configuration files are encoded. Please
2275 note that while reading the configuration files, this is only respected after
2276 the corresponding declaration appears. It's advised to put the following at the
2278 The Mutt Next Generation E-Mail Client 46
2280 very beginning of a users muttngrc:
2282 set config_charset = "..."
2284 and replacing the dots with the actual character set. To avoid problems while
2285 maintaining the setup, vim user's may want to use modelines as show in:
2287 # vim:fileencoding=...:
2289 while, again, replacing the dots with the appropriate name. This tells vim as
2290 which character set to read and save the file.
2292 _
\b3_
\b._
\b3_
\b1_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2294 ``Modularization'' means to divide the setup into several files while sorting
2295 the options or commands by topic. Especially for longer setups (e.g. with many
2296 hooks), this helps maintaining it and solving trouble.
2298 When using separation, setups may be, as a whole or in fractions, shared over
2301 _
\b3_
\b._
\b3_
\b1_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2303 When using a configuration on different systems, the user may not always have
2304 influence on how mutt-ng is installed and which features it includes.
2306 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2307 for mutt. Its basic syntax is:
2309 ifdef <item> <command>
2310 ifndef <item> <command>
2312 ...whereby <item> can be one of:
2314 +
\bo a function name
2316 +
\bo a variable name
2322 All available functions, variables and menus are documented elsewhere in this
2323 manual but ``features'' is specific to these two commands. To test for one,
2325 The Mutt Next Generation E-Mail Client 47
2327 prefix one of the following keywords with feature_:
2329 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2330 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2331 classic_smime, gpgme, header_cache
2333 As an example, one can use the following in ~/.muttngrc:
2335 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2336 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2337 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2339 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2340 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2341 ng/setup-nntp if NNTP support is built in.
2343 An example for testing for variable names can be used if users use different
2344 revisions of mutt-ng whereby the older one may not have a certain variable. To
2345 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.104 , page 113),
2348 ifdef imap_mail_check 'set imap_mail_check = 300'
2350 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
2351 (section 7.4.175 , page 132) only if the pager menu is available, use:
2353 ifdef pager 'set pager_index_lines = 10'
2355 For completeness, too, the opposite of ifdef is provided: ifndef which only
2356 executes the command if the test fails. For example, the following two examples
2359 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2360 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2364 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2365 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2367 The Mutt Next Generation E-Mail Client 48
2369 _
\b3_
\b._
\b3_
\b2 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2371 In the process of ensuring and creating more consistency, many variables have
2372 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2373 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 87) for a complete list.
2375 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2377 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2379 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2380 tion 7.2 , page 83) must be specified using regular expressions (regexp) in
2381 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2382 and GNU awk). For your convenience, we have included below a brief description
2385 The search is case sensitive if the pattern contains at least one upper case
2386 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2387 for a regular expression in an initialization command: ``\\''.
2389 A regular expression is a pattern that describes a set of strings. Regular
2390 expressions are constructed analogously to arithmetic expressions, by using
2391 various operators to combine smaller expressions.
2393 Note that the regular expression can be enclosed/delimited by either ' or '
2394 which is useful if the regular expression includes a white-space character.
2395 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-
2396 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2397 ace it with \ (backslash).
2399 The fundamental building blocks are the regular expressions that match a single
2400 character. Most characters, including all letters and digits, are regular
2401 expressions that match themselves. Any metacharacter with special meaning may
2402 be quoted by preceding it with a backslash.
2404 The period ``.'' matches any single character. The caret ``^'' and the dollar
2405 sign ``$'' are metacharacters that respectively match the empty string at the
2406 beginning and end of a line.
2408 A list of characters enclosed by ``['' and ``]'' matches any single character
2409 in that list; if the first character of the list is a caret ``^'' then it
2410 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2411 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2412 specified by giving the first and last characters, separated by a hyphen ``-''.
2413 Most metacharacters lose their special meaning inside lists. To include a lit-
2414 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2415 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2418 The Mutt Next Generation E-Mail Client 49
2420 Certain named classes of characters are predefined. Character classes consist
2421 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2422 defined by the POSIX standard:
2425 Alphanumeric characters.
2428 Alphabetic characters.
2431 Space or tab characters.
2440 Characters that are both printable and visible. (A space is print-
2441 able, but not visible, while an ``a'' is both.)
2444 Lower-case alphabetic characters.
2447 Printable characters (characters that are not control characters.)
2450 Punctuation characters (characters that are not letter, digits,
2451 control characters, or space characters).
2454 Space characters (such as space, tab and formfeed, to name a few).
2457 Upper-case alphabetic characters.
2460 Characters that are hexadecimal digits.
2462 A character class is only valid in a regular expression inside the brackets of
2463 a character list. Note that the brackets in these class names are part of the
2464 symbolic names, and must be included in addition to the brackets delimiting the
2465 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].
2467 Two additional special sequences can appear in character lists. These apply to
2468 non-ASCII character sets, which can have single symbols (called collating ele-
2469 ments) that are represented with more than one character, as well as several
2470 characters that are equivalent for collating or sorting purposes:
2473 A collating symbol is a multi-character collating element enclosed
2475 The Mutt Next Generation E-Mail Client 50
2477 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2478 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2479 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2482 An equivalence class is a locale-specific name for a list of char-
2483 acters that are equivalent. The name is enclosed in ``[='' and
2484 ``=]''. For example, the name ``e'' might be used to represent all
2485 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2486 matches any of ``'', ``'' and ``e''.
2488 A regular expression matching a single character may be followed by one of sev-
2489 eral repetition operators:
2492 The preceding item is optional and matched at most once.
2495 The preceding item will be matched zero or more times.
2498 The preceding item will be matched one or more times.
2501 The preceding item is matched exactly _
\bn times.
2504 The preceding item is matched _
\bn or more times.
2507 The preceding item is matched at most _
\bm times.
2510 The preceding item is matched at least _
\bn times, but no more than _
\bm
2513 Two regular expressions may be concatenated; the resulting regular expression
2514 matches any string formed by concatenating two substrings that respectively
2515 match the concatenated subexpressions.
2517 Two regular expressions may be joined by the infix operator ``|''; the result-
2518 ing regular expression matches any string matching either subexpression.
2520 Repetition takes precedence over concatenation, which in turn takes precedence
2521 over alternation. A whole subexpression may be enclosed in parentheses to
2522 override these precedence rules.
2524 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2525 may also be used in regular expressions:
2528 Matches the empty string at either the beginning or the end of a
2531 The Mutt Next Generation E-Mail Client 51
2534 Matches the empty string within a word.
2537 Matches the empty string at the beginning of a word.
2540 Matches the empty string at the end of a word.
2543 Matches any word-constituent character (letter, digit, or under-
2547 Matches any character that is not word-constituent.
2550 Matches the empty string at the beginning of a buffer (string).
2553 Matches the empty string at the end of a buffer.
2555 Please note however that these operators are not defined by POSIX, so they may
2556 or may not be available in stock libraries on various systems.
2558 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2560 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2561 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2562 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2563 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2564 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83) in the Reference chapter.
2566 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2567 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2570 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2572 It is possible to combine several sub-patterns to a more complex pattern. The
2573 most simple possibility is to logically AND several patterns by stringing them
2578 The pattern above matches all messages that contain ``SPAM'' in the subject and
2581 To logical OR patterns, simply use the | operator. This one especially useful
2582 when using local groups:
2584 The Mutt Next Generation E-Mail Client 52
2586 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2587 (~b mutt-ng|~s Mutt-ng)
2590 The first pattern matches all messages that were sent by one of the mutt-ng
2591 maintainers, while the seconds pattern matches all messages that contain
2592 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2593 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2594 ences: header, i.e. messages that are not an (indirect) reply to one of my
2595 messages. A pattern can be logicall negated using the ! operator.
2597 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2599 When using dates in patterns, the dates must be specified in a special format,
2600 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2601 rent month or year. When using date ranges, and you specify only the minimum or
2602 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2603 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2605 It is also possible to use so-called ``error margins'' when specifying date
2606 ranges. You simply specify a date, and then the error margin. This margin
2607 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2608 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2609 months, w for weeks and d for days. If you use the special * sign, it means
2610 that the error margin goes to both ``directions'' in time.
2616 The first pattern matches all dates between January 1st, 2005 and January 1st
2617 2006. The second pattern matches all dates between October 18th, 2004 and
2618 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2619 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2621 Relative dates are also very important, as they make it possible to specify
2622 date ranges between a fixed number of units and the current date. How this
2623 works can be seen in the following example:
2625 ~d >2w # messages older than two weeks
2626 ~d <3d # messages newer than 3 days
2627 ~d =1m # messages that are exactly one month old
2629 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2631 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2633 The Mutt Next Generation E-Mail Client 53
2635 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2636 In short, they describe what items to print out how in menus and status mes-
2639 Basically, they work as this: for different menus and bars, there's a variable
2640 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2642 For example, when running mutt-ng on different machines or different versions
2643 for testing purposes, it may be interesting to have the following information
2644 always printed on screen when one is in the index:
2646 +
\bo the current hostname
2648 +
\bo the current mutt-ng version number
2650 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-
2651 _
\bm_
\ba_
\bt (section 7.4.314 , page 164) variable. For the hostname and version
2652 string, there's an expando for $status_format: %h expands to the hostname and
2653 %v to the version string. When just configuring:
2655 set status_format = "%v on %h: ..."
2657 mutt-ng will replace the sequence %v with the version string and %h with the
2658 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2659 mailhost, you'll see the following when you're in the index:
2661 Mutt-ng 1.5.9i on mailhost: ...
2663 In the index, there're more useful information one could want to see:
2665 +
\bo which mailbox is open
2667 +
\bo how man new, flagged or postponed messages
2671 To include the mailbox' name is as easy as:
2673 set status_format = "%v on %h: %B: ...
2675 When the currently opened mailbox is Inbox, this will be expanded to:
2677 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2679 For the number of certain types of messages, one more feature of the format
2680 strings is extremely useful. If there aren't messages of a certain type, it may
2682 The Mutt Next Generation E-Mail Client 54
2684 not be desired to print just that there aren't any but instead only print some-
2685 thing if there are any.
2687 _
\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
2689 To only print the number of messages if there are new messages in the current
2690 mailbox, further extend $status_format to:
2692 set status_format = "%v on %h: %B %?n?%n new? ...
2694 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
2695 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2696 ated if the value of the expando is different from zero. The basic syntax is:
2698 %?<item>?<string if nonzero>?
2700 which tells mutt-ng to only look at <string if nonzero> if the value of the
2701 %<item%gt; expando is different from zero. In our example, we used n as the
2702 expando to check for and %n new as the optional nonzero string.
2704 But this is not all: this feature only offers one alternative: ``print some-
2705 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2706 complete version: ``if zero, print something and else print something else.''
2707 This is achieved by the following syntax for those expandos which may be
2710 %?<item>?<string if nonzero>&<string if zero>?
2712 Using this we can make mutt-ng to do the following:
2714 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2717 +
\bo and make it print ``no new messages'' if there aren't any
2719 The corresponding configuration is:
2721 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2723 This doubles the use of the ``new messages'' string because it'll get always
2724 printed. Thus, it can be shortened to:
2726 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2728 The Mutt Next Generation E-Mail Client 55
2730 As you might see from this rather simple example, one can create very complex
2731 but fancy status messages. Please see the reference chapter for expandos and
2732 those which may be printed nonzero.
2734 _
\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
2736 Besides the information given so far, there're even more features of format
2739 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2740 characters in the expansion of <item> to lowercase.
2742 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2743 dots in the expansion of <item> to underscores (_).
2745 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2749 When this occurs, mutt-ng will fill the rest of the line with the
2750 character X. In our example, filling the rest of the line with
2751 dashes is done by setting:
2753 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2756 Since the previous expando stops at the end of line, there must be
2757 a way to fill the gap between two items via the %>X expando: it
2758 puts as many characters X in between two items so that the rest of
2759 the line will be right-justified. For example, to not put the ver-
2760 sion string and hostname of our example on the left but on the
2761 right and fill the gap with spaces, one might use (note the space
2764 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2766 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2768 Sometimes it is desirable to perform an operation on a group of messages all at
2769 once rather than one at a time. An example might be to save messages to a
2770 mailing list to a separate folder, or to delete all messages with a given sub-
2771 ject. To tag all messages matching a pattern, use the tag-pattern function,
2772 which is bound to ``shift-T'' by default. Or you can select individual mes-
2773 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2775 The Mutt Next Generation E-Mail Client 56
2777 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83) for Mutt-ng's pattern matching
2780 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2781 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2782 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2783 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.19 ,
2784 page 93) variable is set, the next operation applies to the tagged messages
2785 automatically, without requiring the ``tag-prefix''.
2787 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 29) or _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 40) commands,
2788 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2789 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2790 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2791 this operator the rest of the macro will be executed as normal.
2793 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2795 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2796 arbitrary commands before performing some operation. For example, you may wish
2797 to tailor your configuration based upon which mailbox you are reading, or to
2798 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
2799 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 48) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 83) along
2800 with a configuration option/command. See
2802 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 28)
2804 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 39)
2806 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 40)
2808 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38)
2810 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36)
2812 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38)
2814 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39)
2816 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2818 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2819 until the end of the current mutt session. As this is generally not desired, a
2820 default hook needs to be added before all other hooks to restore configuration
2821 defaults. Here is an example with send-hook and the my_hdr directive:
2823 send-hook . 'unmy_hdr From:'
2824 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2826 The Mutt Next Generation E-Mail Client 57
2828 _
\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
2830 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2831 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2832 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 48) is sufficient. But in dealing with
2833 messages a finer grain of control is needed for matching since for different
2834 purposes you want to match different criteria.
2836 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 83) language
2837 for matching messages in hook commands. This works in exactly the same way as
2838 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
2839 to those operators which match information mutt extracts from the header of the
2840 message (i.e. from, to, cc, date, subject, etc.).
2842 For example, if you wanted to set your return address based upon sending mail
2843 to a specific address, you could do something like:
2845 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2847 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2849 However, it is not required that you write the pattern to match using the full
2850 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
2851 other hooks, in which case Mutt-ng will translate your pattern into the full
2852 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2853 7.4.49 , page 100) variable. The pattern is translated at the time the hook
2854 is declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.49 , page 100) that is
2855 in effect at that time will be used.
2857 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2859 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2860 which looks very similar to the ones you probably know from GUI mail clients.
2861 The sidebar lists all specified mailboxes, shows the number in each and high-
2862 lights the ones with new email Use the following configuration commands:
2864 set sidebar_visible="yes"
2865 set sidebar_width=25
2867 If you want to specify the mailboxes you can do so with:
2875 You can also specify the colors for mailboxes with new mails by using:
2877 The Mutt Next Generation E-Mail Client 58
2879 color sidebar_new red black
2880 color sidebar white black
2882 The available functions are:
2884 sidebar-scroll-up Scrolls the mailbox list up 1 page
2885 sidebar-scroll-down Scrolls the mailbox list down 1 page
2886 sidebar-next Highlights the next mailbox
2887 sidebar-next-new Highlights the next mailbox with new mail
2888 sidebar-previous Highlights the previous mailbox
2889 sidebar-open Opens the currently highlighted mailbox
2891 Reasonable key bindings look e.g. like this:
2893 bind index \Cp sidebar-prev
2894 bind index \Cn sidebar-next
2895 bind index \Cb sidebar-open
2896 bind pager \Cp sidebar-prev
2897 bind pager \Cn sidebar-next
2898 bind pager \Cb sidebar-open
2900 macro index B ':toggle sidebar_visible^M'
2901 macro pager B ':toggle sidebar_visible^M'
2903 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2904 off the sidebar simply by pressing 'B'.
2906 _
\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
2908 Mutt-ng supports connecting to external directory databases such as LDAP,
2909 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2910 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.227 , page 144) vari-
2911 able, you specify the wrapper command to use. For example:
2913 set query_command = "mutt_ldap_query.pl '%s'"
2915 The wrapper script should accept the query on the command-line. It should
2916 return a one line message, then each matching response on a single line, each
2917 line containing a tab separated address then name then some other optional
2918 information. On error, or if there are no matching addresses, return a non-
2919 zero exit code and a one line error message.
2921 An example multiple response output:
2923 Searching database ... 20 entries ... 3 matching:
2924 me@cs.hmc.edu Michael Elkins mutt dude
2925 blong@fiction.net Brandon Long mutt and more
2927 The Mutt Next Generation E-Mail Client 59
2929 roessler@guug.de Thomas Roessler mutt pgp
2931 There are two mechanisms for accessing the query function of mutt. One is to
2932 do a query from the index menu using the query function (default: Q). This
2933 will prompt for a query, then bring up the query menu which will list the
2934 matching responses. From the query menu, you can select addresses to create
2935 aliases, or to mail. You can tag multiple addresses to mail, start a new
2936 query, or have a new query appended to the current responses.
2938 The other mechanism for accessing the query function is for address completion,
2939 similar to the alias completion. In any prompt for address entry, you can use
2940 the complete-query function (default: ^T) to run a query based on the current
2941 address you have typed. Like aliases, mutt will look for what you have typed
2942 back to the last space or comma. If there is a single response for that query,
2943 mutt will expand the address in place. If there are multiple responses, mutt
2944 will activate the query menu. At the query menu, you can select one or more
2945 addresses to be added to the prompt.
2947 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2949 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2950 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2951 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2952 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.131 , page 121)
2955 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2956 stored in a single file. Each message has a line of the form:
2958 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2960 to denote the start of a new message (this is often referred to as the
2963 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2964 lines containing ``^A^A^A^A'' (four control-A's).
2966 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2967 and each message is stored in a separate file. The filename indicates the mes-
2968 sage number (however, this is may not correspond to the message number Mutt-ng
2969 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2970 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2971 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
2974 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
2975 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
2976 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
2977 way they are unique, even when two programs are writing the mailbox over NFS,
2979 The Mutt Next Generation E-Mail Client 60
2981 which means that no file locking is needed.
2983 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
2985 There are a number of built in shortcuts which refer to specific mailboxes.
2986 These shortcuts can be used anywhere you are prompted for a file or mailbox
2989 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page 162) (incoming)
2992 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.130 , page 121) file
2994 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146) file
2996 +
\bo ^ -- refers to the current mailbox
2998 +
\bo - or !! -- refers to the file you've last visited
3000 +
\bo ~ -- refers to your home directory
3002 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) directory
3004 +
\bo @_
\ba_
\bl_
\bi_
\ba_
\bs -- refers to the _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 3.18 , page 38) as
3005 determined by the address of the alias
3007 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
3009 Mutt-ng has a few configuration options that make dealing with large amounts of
3010 mail easier. The first thing you must do is to let Mutt know what addresses
3011 you consider to be mailing lists (technically this does not have to be a mail-
3012 ing list, but that is what it is most often used for), and what lists you are
3013 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
3014 (section 3.13 , page 35) commands in your muttrc.
3016 Now that Mutt-ng knows what your mailing lists are, it can do several things,
3017 the first of which is the ability to show the name of a list through which you
3018 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
3019 This is useful to distinguish between personal and list mail in the same mail-
3020 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) variable, the escape
3021 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
3022 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
3023 returns the name of the author).
3025 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
3026 quite large. Most people do not bother to remove the author of the message they
3027 are reply to from the list, resulting in two or more copies being sent to that
3028 person. The ``list-reply'' function, which by default is bound to ``L'' in the
3029 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
3030 mailing list addresses instead of all recipients (except as specified by Mail-
3032 The Mutt Next Generation E-Mail Client 61
3034 Followup-To, see below).
3036 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
3037 a list of recipients which includes one or several subscribed mailing lists,
3038 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.71 , page 105) option is set, mutt will
3039 generate a Mail-Followup-To header which contains all the recipients to whom
3040 you send this message, but not your address. This indicates that group-replies
3041 or list-replies (also known as ``followups'') to this message should only be
3042 sent to the original recipients of the message, and not separately to you -
3043 you'll receive your copy through one of the mailing lists you are subscribed
3046 Conversely, when group-replying or list-replying to a message which has a Mail-
3047 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
3048 (section 7.4.93 , page 110) configuration variable is set. Using list-reply
3049 will in this case also make sure that the reply goes to the mailing list, even
3050 if it's not specified in the list of recipients in the Mail-Followup-To.
3052 Note that, when header editing is enabled, you can create a Mail-Followup-To
3053 header manually. Mutt-ng will only auto-generate this header if it doesn't
3054 exist when you send the message.
3056 The other method some mailing list admins use is to generate a ``Reply-To''
3057 field which points back to the mailing list address rather than the author of
3058 the message. This can create problems when trying to reply directly to the
3059 author in private, since most mail clients will automatically reply to the
3060 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
3061 7.4.239 , page 146) variable to help decide which address to use. If set to
3062 _
\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
3063 use the address given in the ``Reply-To'' field, or reply directly to the
3064 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
3065 will be used when present.
3067 The ``X-Label:'' header field can be used to further identify mailing lists or
3068 list subject matter (or just to annotate messages individually). The
3069 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) variable's ``%y'' and ``%Y''
3070 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
3071 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
3072 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
3073 can easily be inserted by procmail and other mail filtering agents.
3075 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160) the mail-
3076 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
3077 which all relate to the same subject. This is usually organized into a tree-
3078 like structure where a message and all of its replies are represented graphi-
3079 cally. If you've ever used a threaded news client, this is the same concept.
3080 It makes dealing with large volume mailing lists easier because you can easily
3081 delete uninteresting threads and quickly find topics of value.
3083 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3085 Mutt-ng has the ability to dynamically restructure threads that are broken
3087 The Mutt Next Generation E-Mail Client 62
3089 either by misconfigured software or bad behavior from some correspondents. This
3090 allows to clean your mailboxes formats) from these annoyances which make it
3091 hard to follow a discussion.
3093 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3095 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
3096 ences:" headers when replying to a message. This results in broken discussions
3097 because Mutt-ng has not enough information to guess the correct threading. You
3098 can fix this by tagging the reply, then moving to the parent message and using
3099 the ``link-threads'' function (bound to & by default). The reply will then be
3100 connected to this "parent" message.
3102 You can also connect multiple children at once, tagging them and using the tag-
3103 prefix command (';') or the auto_tag option.
3105 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3107 On mailing lists, some people are in the bad habit of starting a new discussion
3108 by hitting "reply" to any message from the list and changing the subject to a
3109 totally unrelated one. You can fix such threads by using the ``break-thread''
3110 function (bound by default to #), which will turn the subthread starting from
3111 the current message into a whole different thread.
3113 _
\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
3115 RFC1894 defines a set of MIME content types for relaying information about the
3116 status of electronic mail messages. These can be thought of as ``return
3119 Users can make use of it in one of the following two ways:
3121 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
3122 the mail client can make requests as to what type of status messages
3125 +
\bo The SMTP support via libESMTP supports it, too.
3127 To support this, there are two variables:
3129 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.56 , page 101) is used to request receipts for
3130 different results (such as failed message, message delivered, etc.).
3132 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.57 , page 102) requests how much of your message
3133 should be returned with the receipt (headers or full message).
3135 Please see the reference chapter for possible values.
3137 _
\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)
3139 The Mutt Next Generation E-Mail Client 63
3141 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3142 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
3143 remote POP3 server and fetch mail for local browsing.
3145 You can access the remote POP3 mailbox by selecting the folder
3148 You can select an alternative port by specifying it with the server, i.e.:
3149 pop://popserver:port/.
3151 You can also specify different username for each folder, i.e.: pop://user-
3152 name@popserver[:port]/.
3154 Polling for new mail is more expensive over POP3 than locally. For this reason
3155 the frequency at which Mutt-ng will check for mail remotely can be controlled
3156 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.214 , page 141) variable, which defaults
3157 to every 60 seconds.
3159 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3160 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3161 rally requires that the server supports SSL encrypted connections. To access a
3162 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3163 name@]popserver[:port]/.
3165 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3166 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.212 , page 140), fetch all your
3167 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page 162).
3168 After this point, Mutt-ng runs exactly as if the mail had always been local.
3170 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3171 sider using a specialized program, such as fetchmail
3173 _
\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)
3175 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3176 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
3179 You can access the remote inbox by selecting the folder
3180 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3181 INBOX is the special name for your spool mailbox on the IMAP server. If you
3182 want to access another mail folder at the IMAP server, you should use
3183 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3186 You can select an alternative port by specifying it with the server, i.e.:
3187 imap://imapserver:port/INBOX.
3189 You can also specify different username for each folder, i.e.: imap://user-
3190 name@imapserver[:port]/INBOX.
3192 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3194 The Mutt Next Generation E-Mail Client 64
3196 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3197 rally requires that the server supports SSL encrypted connections. To access a
3198 folder with IMAP/SSL, you should use imaps://[user-
3199 name@]imapserver[:port]/path/to/folder as your folder path.
3201 Pine-compatible notation is also supported, i.e. {[user-
3202 name@]imapserver[:port][/ssl]}path/to/folder
3204 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3205 correctly notice which separator is being used by the server and convert paths
3208 When browsing folders on an IMAP server, you can toggle whether to look at only
3209 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
3210 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.102 , page 112)
3213 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3214 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.104 , page 113) and
3215 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.327 , page 169) variables.
3217 Note that if you are using mbox as the mail store on UW servers prior to
3218 v12.250, the server has been reported to disconnect a client if another client
3219 selects the same folder.
3221 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3223 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3224 mostly the same as the local file browser, with the following differences:
3226 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3227 followed by the symbol "+", indicating that the entry contains both mes-
3228 sages and subfolders. On Cyrus-like servers folders will often contain
3229 both messages and subfolders.
3231 +
\bo For the case where an entry can contain both messages and subfolders, the
3232 selection key (bound to enter by default) will choose to descend into the
3233 subfolder view. If you wish to view the messages in that folder, you must
3234 use view-file instead (bound to space by default).
3236 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3237 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3238 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3239 mally these are bound to s and u, respectively).
3241 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3243 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3244 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3245 tion for you poor exchange users out there, but it has yet to be integrated
3246 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3247 which allows you to log in to a public IMAP server without having an account.
3248 To use ANONYMOUS, simply make your username blank or "anonymous".
3250 The Mutt Next Generation E-Mail Client 65
3252 SASL is a special super-authenticator, which selects among several protocols
3253 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3254 available on your host and the server. Using some of these methods (including
3255 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3256 invisible to those teeming network snoops. It is the best option if you have
3257 it. To use it, you must have the Cyrus SASL library installed on your system
3258 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3260 Mutt-ng will try whichever methods are compiled in and available on the server,
3261 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3263 There are a few variables which control authentication:
3265 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.110 , page 114) - controls the username under
3266 which you request authentication on the IMAP server, for all authentica-
3267 tors. This is overridden by an explicit username in the mailbox path (i.e.
3268 by using a mailbox name of the form {user@host}).
3270 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.105 , page 113) - a password which you may pre-
3271 set, used by all authentication methods where a password is needed.
3273 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.96 , page 111) - a colon-delimited list
3274 of IMAP authentication methods to try, in the order you wish to try them.
3275 If specified, this overrides mutt's default (attempt everything, in the
3276 order listed above).
3278 _
\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)
3280 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3281 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3282 function from the index/pager which is by default bound to i.
3284 The Default newsserver can be obtained from the $NNTPSERVER environment vari-
3285 able. Like other news readers, info about subscribed newsgroups is saved in a
3286 file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.162 , page 129) variable.
3287 Article headers are cached and can be loaded from a file when a newsgroup is
3288 entered instead loading from newsserver; currently, this caching mechanism
3289 still is different from the header caching for maildir/IMAP.
3291 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3293 Especially for Usenet, people often ask for advanced filtering and scoring
3294 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3295 to use a killfile has been discussed in _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bs_
\bc_
\bo_
\br_
\bi_
\bn_
\bg (section 3.26 , page
3298 What has not been discusses in detail is mutt-ng's built-in realname filter.
3299 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3300 there are frequent request for such functionality. The solutions offered often
3301 are complicated regular expressions.
3303 In mutt-ng this is as easy as
3305 The Mutt Next Generation E-Mail Client 66
3309 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3310 fied a valid realname and a valid email address. Using
3314 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3315 ria which are very strict:
3317 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3318 editor.org/in-notes/rfc2822.txt>
3320 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3321 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3322 ``J. User'' and ``J. A. User'' aren't.
3324 +
\bo it's assumed that users are interested in reading their own mail and mail
3325 from people who they have defined an alias for so that those 2 groups of
3326 messages are excluded from the strict rules.
3328 _
\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)
3330 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3331 functionality. When configure was called with --with-libesmtp or the output
3332 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3333 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3334 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 62) section) as well as handling the 8BIT-
3335 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.334 , page 170).
3337 To enable sending mail directly via SMTP without an MTA such as Postfix or
3338 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.292 , page 158)
3339 variable pointing to your SMTP server.
3341 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.296 ,
3342 page 159) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.293 , page 159) variables.
3344 Transport Encryption via the StartTLS command is also available. For this to
3345 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3346 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.295 , page 159) variable must be either set to
3347 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3348 supports it: for the second case, the connection will fail if it doesn't while
3349 switching back to unencrypted communication for the first one.
3351 Some mail providers require user's to set a particular envelope sender, i.e.
3353 The Mutt Next Generation E-Mail Client 67
3355 they allow for only one value which may not be what the user wants to send as
3356 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.291 ,
3357 page 158) may be used to set the envelope different from the From: header.
3359 _
\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)
3361 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3362 find managing all the authentication settings inconvenient and error-prone.
3363 The account-hook command may help. This hook works like folder-hook but is
3364 invoked whenever you access a remote mailbox (including inside the folder
3365 browser), not just when you open the mailbox.
3369 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3370 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3371 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3373 _
\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)
3375 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
3376 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
3377 start a WWW browser on one of them. This functionality is provided by the
3378 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3379 trib/ and the configuration commands:
3381 macro index \cb |urlview\n
3382 macro pager \cb |urlview\n
3384 _
\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)
3386 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3387 _
\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
3388 an arbitrary format, provided that the user has a script to convert from/to
3389 this format to one of the accepted.
3391 The most common use is to open compressed archived folders e.g. with gzip.
3393 In addition, the user can provide a script that gets a folder in an accepted
3394 format and appends its context to the folder in the user-defined format, which
3395 may be faster than converting the entire folder to the accepted format, append-
3396 ing to it and converting back to the user-defined format.
3398 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3399 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69))
3400 which define commands to uncompress and compress a folder and to append mes-
3401 sages to an existing compressed folder respectively.
3403 The Mutt Next Generation E-Mail Client 68
3407 open-hook \\.gz$ "gzip -cd %f > %t"
3408 close-hook \\.gz$ "gzip -c %t > %f"
3409 append-hook \\.gz$ "gzip -c %t >> %f"
3411 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-
3412 tion 4.19.3 , page 69), the folder will be open and closed again each time you
3413 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) (or give
3414 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3415 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) though you'll be able to append to the folder.
3417 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3418 accepted formats. In particular, if the file is empty, mutt supposes it is not
3419 compressed. This is important because it allows the use of programs that do not
3420 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3421 prising if your compressing script produces empty files. In this situation,
3422 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.246 , page 148), so that the compressed file
3423 will be removed if you delete all of the messages.
3425 _
\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
3427 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3429 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3430 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3432 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3433 parameters: %f, which is replaced with the (compressed) folder name, and %t
3434 which is replaced with the name of the temporary folder to which to write.
3436 %f and %t can be repeated any number of times in the command string, and all of
3437 the entries are replaced with the appropriate folder name. In addition, %% is
3438 replaced by %, as in printf, and any other %anything is left as is.
3440 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
3441 return non-zero exit status if it fails, so mutt knows something's wrong.
3445 open-hook \\.gz$ "gzip -cd %f > %t"
3447 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3449 _
\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
3451 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3453 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3454 4.19.1 , page 68) command after some changes were made to it.
3456 The Mutt Next Generation E-Mail Client 69
3458 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3459 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
3460 4.19.1 , page 68) command. Temporary folder in this case is the folder previ-
3461 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68) command.
3463 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
3464 non-zero exit status if it fails, so mutt knows something's wrong.
3468 close-hook \\.gz$ "gzip -c %t > %f"
3470 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3471 file can only be open in the readonly mode.
3473 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) is not called when you exit from the
3474 folder if the folder was not changed.
3476 _
\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
3478 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3480 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3481 is the command that can be used for appending to the folders whose names match
3482 _
\br_
\be_
\bg_
\be_
\bx_
\bp. It has the same format as in the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68)
3483 command. The temporary folder in this case contains the messages that are
3486 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
3487 non-zero exit status if it fails, so mutt knows something's wrong.
3491 append-hook \\.gz$ "gzip -c %t >> %f"
3493 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) is used, the folder is not opened,
3494 which saves time, but this means that we can not find out what the folder type
3495 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.131 , page 121)) type is always
3496 supposed (i.e. this is the format used for the temporary folder).
3498 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 ,
3499 page 68) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3500 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) is only for appending to existing folders.
3502 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3503 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3504 4.19.1 , page 68) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68)respectively) each
3505 time you will add to it.
3507 The Mutt Next Generation E-Mail Client 70
3509 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3511 The compressed folders support can also be used to handle encrypted folders. If
3512 you want to encrypt a folder with PGP, you may want to use the following hooks:
3514 open-hook \\.pgp$ "pgp -f < %f > %t"
3515 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3517 Please note, that PGP does not support appending to an encrypted folder, so
3518 there is no append-hook defined.
3520 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3521 can be read by your system administrator. So think about the security aspects
3524 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3526 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3527 MUA. Every effort has been made to provide the functionality that the discern-
3528 ing MIME user requires, and the conformance to the standards wherever possible.
3529 When configuring Mutt-ng for MIME, there are two extra types of configuration
3530 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3531 ping of file extensions to IANA MIME types. The other is the mailcap file,
3532 which specifies the external commands to use for handling specific MIME types.
3534 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3536 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3537 (while viewing a message), the attachment menu and the compose menu.
3539 _
\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
3541 When you select a message from the index and view it in the pager, Mutt decodes
3542 the message to a text representation. Mutt-ng internally supports a number of
3543 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3544 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3545 variety of PGP MIME types, including PGP/MIME and application/pgp.
3547 Mutt-ng will denote attachments with a couple lines describing them. These
3548 lines are of the form:
3550 [-- Attachment #1: Description --]
3551 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3553 Where the Description is the description or filename given for the attachment,
3554 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3556 The Mutt Next Generation E-Mail Client 71
3558 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3560 [-- image/gif is unsupported (use 'v' to view this part) --]
3562 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3564 The default binding for view-attachments is `v', which displays the attachment
3565 menu for a message. The attachment menu displays a list of the attachments in
3566 a message. From the attachment menu, you can save, print, pipe, delete, and
3567 view attachments. You can apply these operations to a group of attachments at
3568 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3569 can also reply to the current message from this menu, and only the current
3570 attachment (or the attachments tagged) will be quoted in your reply. You can
3571 view attachments as text, or view them using the mailcap viewer definition.
3573 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3574 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3575 of type message/rfc822.
3577 See the help on the attachment menu for more information.
3579 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3581 The compose menu is the menu you see before you send a message. It allows you
3582 to edit the recipient list, the subject, and other aspects of your message. It
3583 also contains a list of the attachments of your message, including the main
3584 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3585 review, and rename an attachment or a list of tagged attachments. You can also
3586 modifying the attachment information, notably the type, encoding and descrip-
3589 Attachments appear as follows:
3591 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3592 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3594 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3595 or canceling) the message. It can be toggled with the toggle-unlink command
3596 (default: u). The next field is the MIME content-type, and can be changed with
3597 the edit-type command (default: ^T). The next field is the encoding for the
3598 attachment, which allows a binary message to be encoded for transmission on
3599 7bit links. It can be changed with the edit-encoding command (default: ^E).
3600 The next field is the size of the attachment, rounded to kilobytes or
3601 megabytes. The next field is the filename, which can be changed with the
3602 rename-file command (default: R). The final field is the description of the
3603 attachment, and can be changed with the edit-description command (default: d).
3605 _
\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
3607 When you add an attachment to your mail message, Mutt-ng searches your personal
3609 The Mutt Next Generation E-Mail Client 72
3611 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3612 /usr/local/share/mutt/mime.types or /etc/mime.types
3614 The mime.types file consist of lines containing a MIME type and a space sepa-
3615 rated list of extensions. For example:
3617 application/postscript ps eps
3619 audio/x-aiff aif aifc aiff
3621 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3622 tain most of the MIME types you are likely to use.
3624 If Mutt-ng can not determine the mime type by the extension of the file you
3625 attach, it will look at the file. If the file is free of binary information,
3626 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3627 the file contains binary information, then Mutt-ng will mark it as applica-
3628 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3629 attachment by using the edit-type command from the compose menu (default: ^T).
3630 The MIME type is actually a major mime type followed by the sub-type, separated
3631 by a '/'. 6 major types: application, text, image, video, audio, and model have
3632 been approved after various internet discussions. Mutt-ng recognises all of
3633 these if the appropriate entry is found in the mime.types file. It also recog-
3634 nises other major mime types, such as the chemical type that is widely used in
3635 the molecular modelling community to pass molecular data in various forms to
3636 various molecular viewers. Non-recognised mime types should only be used if the
3637 recipient of the message is likely to be expecting such attachments.
3639 _
\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
3641 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3642 format specified in Appendix A of RFC 1524. This file format is commonly
3643 referred to as the mailcap format. Many MIME compliant programs utilize the
3644 mailcap format, allowing you to specify handling for all MIME types in one
3645 place for all programs. Programs known to use this format include Netscape,
3646 XMosaic, lynx and metamail.
3648 In order to handle various MIME types that Mutt-ng can not handle internally,
3649 Mutt-ng parses a series of external configuration files to find an external
3650 handler. The default search string for these files is a colon delimited list
3653 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3655 where $HOME is your home directory.
3657 In particular, the metamail distribution will install a mailcap file, usually
3658 as /usr/local/etc/mailcap, which contains some baseline entries.
3660 The Mutt Next Generation E-Mail Client 73
3662 _
\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
3664 A mailcap file consists of a series of lines which are comments, blank, or def-
3667 A comment line consists of a # character followed by anything you want.
3669 A blank line is blank.
3671 A definition line consists of a content type, a view command, and any number of
3672 optional fields. Each field of a definition line is divided by a semicolon ';'
3675 The content type is specified in the MIME standard type/subtype method. For
3676 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3677 mat includes two formats for wildcards, one using the special '*' subtype, the
3678 other is the implicit wild, where you only include the major type. For exam-
3679 ple, image/*, or video, will match all image types and video types, respec-
3682 The view command is a Unix command for viewing the type specified. There are
3683 two different types of commands supported. The default is to send the body of
3684 the MIME message to the command on stdin. You can change this behavior by using
3685 %s as a parameter to your view command. This will cause Mutt-ng to save the
3686 body of the MIME message to a temporary file, and then call the view command
3687 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3688 will turn over the terminal to the view program until the program quits, at
3689 which time Mutt will remove the temporary file if it exists.
3691 So, in the simplest form, you can send a text/plain message to the external
3692 pager more on stdin:
3696 Or, you could send the message as a file:
3700 Perhaps you would like to use lynx to interactively view a text/html message:
3704 In this case, lynx does not support viewing a file from stdin, so you must use
3705 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
3706 _
\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
3707 _
\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
3708 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3710 On the other hand, maybe you don't want to use lynx interactively, you just
3711 want to have it convert the text/html to text/plain, then you can use:
3713 The Mutt Next Generation E-Mail Client 74
3715 text/html; lynx -dump %s | more
3717 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3718 text formats, then you would use the following:
3723 This is the simplest form of a mailcap file.
3725 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3727 The interpretation of shell meta-characters embedded in MIME parameters can
3728 lead to security problems in general. Mutt-ng tries to quote parameters in
3729 expansion of %s syntaxes properly, and avoids risky characters by substituting
3730 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.122 , page 119) variable.
3732 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3733 there are other applications parsing mailcap, maybe taking less care of it.
3734 Therefore you should pay attention to the following rules:
3736 _
\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
3737 double quotes. Mutt-ng does this for you, the right way, as should any other
3738 program which interprets mailcap. Don't put them into backtick expansions. Be
3739 highly careful with eval statements, and avoid them if possible at all. Trying
3740 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3741 tive to correct quoting in the first place.
3743 If you have to use the %-expandos' values in context where you need quoting or
3744 backtick expansions, put that value into a shell variable and reference the
3745 shell variable where necessary, as in the following example (using $charset
3746 inside the backtick expansion is safe, since it is not itself subject to any
3749 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3750 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3752 _
\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
3754 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3756 In addition to the required content-type and view command fields, you can add
3757 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3758 nizes the following optional fields:
3761 This flag tells Mutt-ng that the command passes possibly large
3762 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3763 (either the internal pager or the external pager defined by the
3764 pager variable) on the output of the view command. Without this
3766 The Mutt Next Generation E-Mail Client 75
3768 flag, Mutt-ng assumes that the command is interactive. One could
3769 use this to replace the pipe to more in the lynx -dump example in
3772 text/html; lynx -dump %s ; copiousoutput
3774 This will cause lynx to format the text/html output as text/plain
3775 and Mutt-ng will use your standard pager to display the results.
3778 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3779 tion 5.4 , page 78), in order to decide whether it should honor
3780 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.340 , page 172) variable
3781 or not. When an attachment is viewed using an interactive program,
3782 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3783 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.340 , page 172) and the exit
3784 status of the program to decide if it will ask you to press a key
3785 after the external program has exited. In all other situations it
3786 will not prompt you for a key.
3789 This flag specifies the command to use to create a new attachment
3790 of a specific MIME type. Mutt-ng supports this from the compose
3793 composetyped=<command>
3794 This flag specifies the command to use to create a new attachment
3795 of a specific MIME type. This command differs from the compose
3796 command in that mutt will expect standard MIME headers on the data.
3797 This can be used to specify parameters, filename, description, etc.
3798 for a new attachment. Mutt-ng supports this from the compose
3802 This flag specifies the command to use to print a specific MIME
3803 type. Mutt-ng supports this from the attachment and compose menus.
3806 This flag specifies the command to use to edit a specific MIME
3807 type. Mutt-ng supports this from the compose menu, and also uses
3808 it to compose new attachments. Mutt-ng will default to the defined
3809 editor for text attachments.
3811 nametemplate=<template>
3812 This field specifies the format for the file denoted by %s in the
3813 command fields. Certain programs will require a certain file
3814 extension, for instance, to correctly view a file. For instance,
3815 lynx will only interpret a file as text/html if the file ends in
3816 .html. So, you would specify lynx as a text/html viewer with a
3817 line in the mailcap file like:
3819 text/html; lynx %s; nametemplate=%s.html
3821 The Mutt Next Generation E-Mail Client 76
3824 This field specifies a command to run to test whether this mailcap
3825 entry should be used. The command is defined with the command
3826 expansion rules defined in the next section. If the command
3827 returns 0, then the test passed, and Mutt-ng uses this entry. If
3828 the command returns non-zero, then the test failed, and Mutt-ng
3829 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
3830 _
\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:
3832 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3835 In this example, Mutt-ng will run the program RunningX which will
3836 return 0 if the X Window manager is running, and non-zero if it
3837 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3838 display the text/html object. If RunningX doesn't return 0, then
3839 Mutt-ng will go on to the next entry and use lynx to display the
3842 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3844 When searching for an entry in the mailcap file, Mutt-ng will search for the
3845 most useful entry for its purpose. For instance, if you are attempting to
3846 print an image/gif, and you have the following entries in your mailcap file,
3847 Mutt-ng will search for an entry with the print command:
3850 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3853 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3856 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) to denote
3857 two commands for viewing an attachment, one to be viewed automatically, the
3858 other to be viewed interactively from the attachment menu. In addition, you
3859 can then use the test feature to determine which viewer to use interactively
3860 depending on your environment.
3862 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3863 text/html; lynx %s; nametemplate=%s.html
3864 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3866 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78), Mutt-ng will choose the third entry
3867 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3868 program RunningX to determine if it should use the first entry. If the program
3869 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3871 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3873 The various commands defined in the mailcap files are passed to the /bin/sh
3875 The Mutt Next Generation E-Mail Client 77
3877 shell using the system() function. Before the command is passed to /bin/sh -c,
3878 it is parsed to expand various special parameters with information from Mutt-
3879 ng. The keywords Mutt-ng expands are:
3882 As seen in the basic mailcap section, this variable is expanded to
3883 a filename specified by the calling program. This file contains
3884 the body of the message to view/print/edit or where the composing
3885 program should place the results of composition. In addition, the
3886 use of this keyword causes Mutt-ng to not pass the body of the mes-
3887 sage to the view/print/edit program on stdin.
3890 Mutt-ng will expand %t to the text representation of the content
3891 type of the message in the same form as the first parameter of the
3892 mailcap definition line, ie text/html or image/gif.
3895 Mutt-ng will expand this to the value of the specified parameter
3896 from the Content-Type: line of the mail message. For instance, if
3897 Your mail message contains:
3899 Content-Type: text/plain; charset=iso-8859-1
3901 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3902 metamail mailcap file uses this feature to test the charset to
3903 spawn an xterm using the right charset to view the message.
3906 This will be replaced by a %
3908 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3909 1524. The main purpose of these parameters is for multipart messages, which is
3910 handled internally by Mutt-ng.
3912 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3914 This mailcap file is fairly simple and standard:
3916 # I'm always running X :)
3917 video/*; xanim %s > /dev/null
3918 image/*; xv %s > /dev/null
3920 # I'm always running netscape (if my computer had more memory, maybe)
3921 text/html; netscape -remote 'openURL(%s)'
3923 This mailcap file shows quite a number of examples:
3925 The Mutt Next Generation E-Mail Client 78
3927 # Use xanim to view all videos Xanim produces a header on startup,
3928 # send that to /dev/null so I don't see it
3929 video/*; xanim %s > /dev/null
3931 # Send html to a running netscape by remote
3932 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3934 # If I'm not running netscape but I am running X, start netscape on the
3936 text/html; netscape %s; test=RunningX
3938 # Else use lynx to view it as text
3941 # This version would convert the text/html to text/plain
3942 text/html; lynx -dump %s; copiousoutput
3944 # I use enscript to print text in two columns to a page
3945 text/*; more %s; print=enscript -2Gr %s
3947 # Netscape adds a flag to tell itself to view jpegs internally
3948 image/jpeg;xv %s; x-mozilla-flags=internal
3950 # Use xv to view images if I'm running X
3951 # In addition, this uses the \ to extend the line and set my editor
3953 image/*;xv %s; test=RunningX; \
3956 # Convert images to text using the netpbm tools
3957 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3958 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3960 # Send excel spreadsheets to my NT box
3961 application/ms-excel; open.pl %s
3963 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3965 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3966 viewer defined in the mailcap file, Mutt-ng has support for automatically view-
3967 ing MIME attachments while in the pager.
3969 To work, you must define a viewer in the mailcap file which uses the copi-
3970 ousoutput option to denote that it is non-interactive. Usually, you also use
3971 the entry to convert the attachment to a text representation which you can view
3974 You then use the auto_view muttrc command to list the content-types that you
3975 wish to view automatically.
3977 For instance, if you set auto_view to:
3979 The Mutt Next Generation E-Mail Client 79
3981 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3983 Mutt-ng could use the following mailcap entries to automatically view attach-
3984 ments of these types.
3986 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3987 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3988 application/x-gunzip; gzcat; copiousoutput
3989 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3990 application/postscript; ps2ascii %s; copiousoutput
3992 ``unauto_view'' can be used to remove previous entries from the autoview list.
3993 This can be used with message-hook to autoview messages based on size, etc.
3994 ``unauto_view *'' will remove all previous entries.
3996 _
\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
3998 Mutt-ng has some heuristics for determining which attachment of a multi-
3999 part/alternative type to display. First, mutt will check the alternative_order
4000 list to determine if one of the available types is preferred. The alterna-
4001 tive_order list consists of a number of MIME types in order, including support
4002 for implicit and explicit wildcards, for example:
4004 alternative_order text/enriched text/plain text application/postscript image/*
4006 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
4007 5.4 , page 78), and use that. Failing that, Mutt-ng will look for any text
4008 type. As a last attempt, mutt will look for any type it knows how to handle.
4010 To remove a MIME type from the alternative_order list, use the unalterna-
4013 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
4015 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
4016 treated according to their mailcap entry. This option is designed to deal with
4017 binary types such as application/octet-stream. When an attachment's mime-type
4018 is listed in mime_lookup, then the extension of the filename will be compared
4019 to the list of extensions in the mime.types file. The mime-type associated
4020 with this extension will then be used to process the attachment according to
4021 the rules in the mailcap file and according to any other configuration options
4022 (such as auto_view) specified. Common usage would be:
4024 mime_lookup application/octet-stream application/X-Lotus-Manuscript
4026 In addition, the unmime_lookup command may be used to disable this feature for
4028 The Mutt Next Generation E-Mail Client 80
4030 any particular mime-type if it had been set, for example, in a global muttrc.
4032 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4034 First of all, mutt-ng contains no security holes included by intention but may
4035 contain unknown security holes. As a consequence, please run mutt-ng only with
4036 as few permissions as possible.
4038 Please do not run mutt-ng as the super user.
4040 When configuring mutt-ng, there're some points to note about secure setups.
4042 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
4043 mail user agents (in their default configuration) just by changing mutt-ng's
4044 configuration files: it then can execute arbitrary programs and scripts
4045 attached to messages, send out private data on its own, etc. Although this is
4046 not believed to the common type of setup, please read this chapter carefully.
4048 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
4050 Although mutt-ng can be told the various passwords for accounts, please never
4051 store passwords in configuration files. Besides the fact that the system's
4052 operator can always read them, you could forget to replace the actual password
4053 with asterisks when reporting a bug or asking for help via, for example, a
4054 mailing list so that your mail including your password could be archived by
4055 internet search engines, etc. Please never store passwords on disk.
4057 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
4059 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
4060 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.332 , page 170) variable can be used to
4061 change the default permissions of these files. Please only change it if you
4062 really know what you are doing. Also, a different location for these files may
4063 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.328 , page 169)
4066 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
4068 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4070 In the default configuration, mutt-ng will leak some information to the outside
4071 world when sending messages: the generation of Message-ID: headers includes a
4072 step counter which is increased (and rotated) with every message sent. If you'd
4073 like to hide this information probably telling others how many mail you sent in
4074 which time, you at least need to remove the %P expando from the default setting
4075 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.148 , page 124) variable. Please make sure
4076 that you really know how local parts of these Message-ID: headers are composed.
4078 The Mutt Next Generation E-Mail Client 81
4080 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
4082 As mutt-ng be can be set up to be the mail client to handle mailto: style links
4083 in websites, there're security considerations, too. To keep the old behavior by
4084 default, mutt-ng will be strict in interpreting them which means that arbitrary
4085 header fields can be embedded in these links which could override existing
4086 header fields or attach arbitrary files. This may be problematic if the
4087 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
4088 doesn't want to see header fields while editing the message.
4090 For example, following a link like
4092 mailto:joe@host?Attach=~/.gnupg/secring.gpg
4094 will send out the user's private gnupg keyring to joe@host if the user doesn't
4095 follow the information on screen carefully enough.
4097 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.316 , page 166) variable, mutt-
4100 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
4101 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
4103 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable by force
4104 to let the user see all the headers (because they still may leak informa-
4107 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4109 Mutt-ng in many places has to rely on external applications or for convenience
4110 supports mechanisms involving external applications.
4112 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
4114 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
4115 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-
4116 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.121 , page 119) variable for
4119 These utilities may have a variety of security vulnerabilities, including over-
4120 writing of arbitrary files, information leaks or other exploitable bugs. These
4121 vulnerabilities may go unnoticed by the user, especially when they are called
4122 automatically (and without interactive prompting) from the mailcap file(s).
4123 When using mutt-ng's autoview mechanism in combination with mailcap files,
4124 please be sure to...
4126 +
\bo manually select trustworth applications with a reasonable calling sequence
4128 +
\bo periodically check the contents of mailcap files, especially after soft-
4129 ware installations or upgrades
4131 The Mutt Next Generation E-Mail Client 82
4133 +
\bo keep the software packages referenced in the mailcap file up to date
4135 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.122 , page 119) variable in its
4136 default state to restrict mailcap expandos to a safe set of characters
4138 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
4140 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4143 The same security considerations apply for these as for tools involved via
4144 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4145 compressed folders support if the uncompressed mailbox is too large for the
4146 disk it is saved to.)
4148 As already noted, most of these problems are not built in but caused by wrong
4149 configuration, so please check your configuration.
4151 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4153 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4155 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4156 mailbox. However, it is possible to read other mailboxes and to send messages
4157 from the command line as well.
4160 -a attach a file to a message
4161 -b specify a blind carbon-copy (BCC) address
4162 -c specify a carbon-copy (Cc) address
4163 -e specify a config command to be run after initialization files are read
4164 -f specify a mailbox to load
4165 -F specify an alternate file to read initialization commands
4166 -h print help on command line options
4167 -H specify a draft file from which to read a header and body
4168 -i specify a file to include in a message composition
4169 -m specify a default mailbox type
4170 -n do not read the system Muttngrc
4171 -p recall a postponed message
4172 -Q query a configuration variable
4173 -R open mailbox in read-only mode
4174 -s specify a subject (enclose in quotes if it contains spaces)
4175 -t dump the value of all variables to stdout
4176 -T dump the value of all changed variables to stdout
4177 -v show version number and compile-time definitions
4178 -x simulate the mailx(1) compose mode
4179 -y show a menu containing the files specified by the mailboxes command
4180 -z exit immediately if there are no messages in the mailbox
4181 -Z open the first folder with new message,exit immediately if none
4183 To read messages in a mailbox
4185 The Mutt Next Generation E-Mail Client 83
4187 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4189 To compose a new message
4191 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-
4192 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4194 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4195 rect input from the file you wish to send. For example,
4197 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4199 This command will send a message to ``professor@bigschool.edu'' with a subject
4200 of ``data set for run #2''. In the body of the message will be the contents of
4201 the file ``~/run2.dat''.
4203 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4205 The Mutt Next Generation E-Mail Client 84
4208 ~b EXPR messages which contain EXPR in the message body
4209 ~B EXPR messages which contain EXPR in the whole message
4210 ~c USER messages carbon-copied to USER
4211 ~C EXPR message is either to: or cc: EXPR
4213 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4215 ~e EXPR message which contains EXPR in the ``Sender'' field
4217 ~f USER messages originating from USER
4218 ~g cryptographically signed messages
4219 ~G cryptographically encrypted messages
4220 ~H EXPR messages with a spam attribute matching EXPR
4221 ~h EXPR messages which contain EXPR in the message header
4222 ~k message contains PGP key material
4223 ~i ID message which match ID in the ``Message-ID'' field
4224 ~L EXPR message is either originated or received by EXPR
4225 ~l message is addressed to a known mailing list
4226 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4227 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4230 ~p message is addressed to you (consults alternates)
4231 ~P message is from you (consults alternates)
4232 ~Q messages which have been replied to
4234 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4235 ~S superseded messages
4236 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4238 ~t USER messages addressed to USER
4240 ~v message is part of a collapsed thread.
4241 ~V cryptographically verified messages
4242 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4243 (if compiled with NNTP support)
4244 ~x EXPR messages which contain EXPR in the `References' field
4245 ~y EXPR messages which contain EXPR in the `X-Label' field
4246 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4247 ~= duplicated messages (see $duplicate_threads)
4248 ~$ unreferenced messages (requires threaded view)
4249 ~* ``From'' contains realname and (syntactically) valid
4250 address (excluded are addresses matching against
4251 alternates or any alias)
4253 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
4254 48). Special attention has to be made when using regular expressions inside of
4255 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4256 level of backslash (\), which is normally used for quoting. If it is your
4257 intention to use a backslash in the regular expression, you will need to use
4258 two backslashes instead (\\).
4260 The Mutt Next Generation E-Mail Client 85
4262 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4264 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4266 The following are the commands understood by mutt.
4268 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 66) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4270 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 25) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4272 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 25) [ * | _
\bk_
\be_
\by ... ]
4274 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4276 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 33) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4278 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4280 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4282 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4284 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4286 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4288 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 26) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4290 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 28) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4292 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4294 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 30) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4296 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 30) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4298 +
\bo _
\be_
\bx_
\be_
\bc (section 3.25 , page 41) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4300 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4302 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4304 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 28) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4306 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 38) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4308 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 38) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4310 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 28) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4312 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 32) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4314 The Mutt Next Generation E-Mail Client 86
4316 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 32) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4318 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4320 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4322 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 29) _
\bm_
\be_
\bn_
\bu _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
4324 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 36) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4326 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4328 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4330 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4332 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4334 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.9 , page 30) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4336 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.9 , page 30) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4338 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4340 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4342 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4344 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.23 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4346 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 40) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4348 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4350 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4352 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4354 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4356 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 39) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4358 +
\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
4360 +
\bo _
\bs_
\be_
\bt (section 3.28 , page 44) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4362 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4364 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 45) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4366 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.27 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4368 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.27 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4370 The Mutt Next Generation E-Mail Client 87
4372 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4374 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4376 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4378 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.30 , page 45) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4380 _
\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
4382 The following list contains all variables which, in the process of providing
4383 more consistency, have been renamed and are partially even removed already. The
4384 left column contains the old synonym variables, the right column the full/new
4387 The Mutt Next Generation E-Mail Client 88
4389 edit_hdrs edit_headers
4390 forw_decode forward_decode
4391 forw_format forward_format
4392 forw_quote forward_quote
4393 hdr_format index_format
4394 indent_str indent_string
4395 mime_fwd mime_forward
4396 msg_format message_format
4397 pgp_autosign crypt_autosign
4398 pgp_autoencrypt crypt_autoencrypt
4399 pgp_replyencrypt crypt_replyencrypt
4400 pgp_replysign crypt_replysign
4401 pgp_replysignencrypted crypt_replysignencrypted
4402 pgp_verify_sig crypt_verify_sig
4403 pgp_create_traditional pgp_autoinline
4404 pgp_auto_traditional pgp_replyinline
4405 forw_decrypt forward_decrypt
4406 smime_sign_as smime_default_key
4407 post_indent_str post_indent_string
4408 print_cmd print_command
4409 shorten_hierarchy sidebar_shorten_hierarchy
4410 ask_followup_to nntp_ask_followup_to
4411 ask_x_comment_to nntp_ask_x_comment_to
4412 catchup_newsgroup nntp_catchup
4413 followup_to_poster nntp_followup_to_poster
4414 group_index_format nntp_group_index_format
4416 mime_subject nntp_mime_subject
4417 news_cache_dir nntp_cache_dir
4418 news_server nntp_host
4420 nntp_poll nntp_mail_check
4421 pop_checkinterval pop_mail_check
4422 post_moderated nntp_post_moderated
4423 save_unsubscribed nntp_save_unsubscribed
4424 show_new_news nntp_show_new_news
4425 show_only_unread nntp_show_only_unread
4426 x_comment_to nntp_x_comment_to
4427 smtp_auth_username smtp_user
4428 smtp_auth_password smtp_pass
4430 The contrib subdirectory contains a script named update-config.pl which eases
4433 A complete list of current variables follows.
4435 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
4441 This variable specifies whether to abort sending if no attachment was made but
4443 The Mutt Next Generation E-Mail Client 89
4445 the content references them, i.e. the content matches the regular expression
4446 given in _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 92). If a match was
4447 found and this variable is set to _
\by_
\be_
\bs, message sending will be aborted but the
4448 mail will be send nevertheless if set to _
\bn_
\bo.
4450 This variable and _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 92) are
4451 intended to remind the user to attach files if the message's text references
4454 See also the _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 92) variable.
4456 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4462 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4463 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4464 subject given at the subject prompt will never be aborted.
4466 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4472 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4473 body if no changes are made to the file (this check only happens after the
4474 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4476 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bg_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4482 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
4483 cating which version of Mutt-ng was used for composing them.
4485 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4489 Default: '~/.muttngrc'
4491 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4492 tion 2.5.4 , page 11)'' function.
4494 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4495 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 45)'' command for it to be executed.
4497 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4499 The Mutt Next Generation E-Mail Client 90
4503 Default: '%4n %2f %t %-10a %r'
4505 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4506 ing printf(3)-style sequences are available:
4512 flags - currently, a 'd' for an alias marked for deletion
4518 address which alias expands to
4521 character which indicates if the alias is tagged for inclusion
4523 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4529 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4530 or base64 encoding when sending mail.
4532 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4538 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4539 sages) are to be interpreted. Messages containing these codes are rare, but if
4540 this option is set, their text will be colored accordingly. Note that this may
4541 override your color choices, and even present a security problem, since a mes-
4542 sage could include a line like ``[-- PGP output follows ...' and give it the
4543 same color as your attachment color.
4545 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4551 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4552 instead of highlighting the whole line. On slow network or modem links this
4553 will make response faster because there is less that has to be redrawn on the
4554 screen when moving to the next or previous entries in the menu.
4556 The Mutt Next Generation E-Mail Client 91
4558 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4564 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4565 attachment trees, instead of the default ACS characters.
4567 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4573 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4574 editing an outgoing message.
4576 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bs_
\bk_
\bc_
\bc
4582 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4583 the body of an outgoing message.
4585 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4591 This variable is a colon-separated list of character encoding schemes for mes-
4592 sages without character encoding indication. Header field values and message
4593 body content without character encoding indication would be assumed that they
4594 are written in one of this list. By default, all the header fields and message
4595 body without any charset indication are assumed to be in us-ascii.
4597 For example, Japanese users might prefer this:
4599 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4601 However, only the first content is valid for the message body. This variable
4602 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.317 , page 167) is unset.
4604 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4608 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4610 This variable describes the format of the ``attachment'' menu. The following
4611 printf(3)-style sequences are understood:
4613 The Mutt Next Generation E-Mail Client 92
4619 requires charset conversion (n or c)
4628 MIME Content-Transfer-Encoding: header field
4634 MIME Content-Disposition: header field (I=inline, A=attachment)
4652 graphic tree characters
4655 unlink (=to delete) flag
4658 right justify the rest of the string and pad with character 'X'
4661 pad to the end of the line with character 'X'
4663 _
\b7_
\b._
\b4_
\b._
\b1_
\b5 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
4665 Type: regular expression
4669 The Mutt Next Generation E-Mail Client 93
4671 If this variable is non-empty, muttng will scan a message's contents before
4672 sending for this regular expression. If it is found, it will ask for what to do
4673 depending on the setting of _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 88).
4675 This variable and _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 88) are intended to
4676 remind the user to attach files if the message's text references them.
4678 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4684 The separator to add between attachments when operating (saving, printing, pip-
4685 ing, etc) on a list of tagged attachments.
4687 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4693 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4694 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4695 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.16 ,
4696 page 93)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4697 operate on the attachments one by one.
4699 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4703 Default: 'On %d, %n wrote:'
4705 This is the string that will precede a message which has been included in a
4706 reply. For a full listing of defined printf(3)-like sequences see the section
4707 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''.
4709 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4715 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4716 all tagged messages (if there are any). When unset, you must first use the
4717 ``tag-prefix'' function (default: ';') to make the next function apply to all
4720 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4726 The Mutt Next Generation E-Mail Client 94
4728 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'', Mutt-ng
4729 will skip the initial send-menu and allow you to immediately begin editing the
4730 body of your message. The send-menu may still be accessed once you have fin-
4731 ished editing the body of your message.
4733 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.65 , page 103)''.
4735 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\be_
\be_
\bp
4741 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4743 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4749 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4750 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4751 tion 7.4.21 , page 94)'' variable.
4753 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4759 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4760 you don't get asked if you want to bounce a message. Setting this variable to
4761 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4764 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4770 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4771 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4773 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4779 When this variable is set, mutt will place the cursor at the beginning of the
4780 current line in menus, even when the arrow_cursor variable is unset, making it
4781 easier for blind persons using Braille displays to follow these menus. The
4783 The Mutt Next Generation E-Mail Client 95
4785 option is disabled by default because many visual terminals don't permit making
4786 the cursor invisible.
4788 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4792 Default: '~/.mutt_certificates'
4794 Availability: SSL or GNUTLS
4796 This variable specifies the file where the certificates you trust are saved.
4797 When an unknown certificate is encountered, you are asked if you accept it or
4798 not. If you accept it, the certificate can also be saved in this file and fur-
4799 ther connections are automatically accepted.
4801 You can also manually add CA certificates in this file. Any server certificate
4802 that is signed with one of these CA certificates are also automatically
4805 Example: set certificate_file=~/.muttng/certificates
4807 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4813 Character set your terminal uses to display and enter textual data.
4815 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4821 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4823 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4824 Especially with MH mailboxes, this operation can take quite some time since it
4825 involves scanning the directory and checking each file to see if it has already
4826 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4829 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4835 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4838 The Mutt Next Generation E-Mail Client 96
4840 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4844 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4846 Controls the format of the status line displayed in the ``compose'' menu. This
4847 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164)'', but has
4848 its own set of printf(3)-like sequences:
4851 total number of attachments
4857 approximate size (in bytes) of the current message
4860 Mutt-ng version string
4862 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164)''
4863 option for more information on how to set ``_
\b$_
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.30 ,
4866 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4872 When defined, Mutt-ng will recode commands in rc files from this encoding.
4874 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4880 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4883 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4889 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4890 box which does not yet exist before creating it.
4892 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4894 The Mutt Next Generation E-Mail Client 97
4900 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4901 many seconds if the connection is not able to be established. A negative value
4902 causes Mutt-ng to wait indefinitely for the connection to succeed.
4904 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4908 Default: 'text/plain'
4910 Sets the default Content-Type: header field for the body of newly composed mes-
4913 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\bo_
\bp_
\by
4919 This variable controls whether or not copies of your outgoing messages will be
4920 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page
4921 146)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.247 , page 148)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4922 7.4.73 , page 106)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38)''.
4924 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4930 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4931 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4932 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4933 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
4934 7.4.283 , page 157)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4935 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4938 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4944 This variable controls whether or not Mutt-ng may automatically enable PGP
4945 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
4946 7.4.37 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 98)'',
4947 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4948 7.4.42 , page 98)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.283 , page 157)''.
4950 The Mutt Next Generation E-Mail Client 98
4952 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4958 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4959 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4960 signing is not required or encryption is requested as well. If
4961 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.283 , page 157)'' is _
\bs_
\be_
\bt, then OpenSSL is
4962 used instead to create S/MIME messages and settings can be overridden by use of
4963 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4965 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4971 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4972 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
4973 7.4.37 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 98)'',
4974 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4975 7.4.42 , page 98)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.283 , page 157)''.
4977 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4983 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
4984 encrypted. (Crypto only)
4986 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
4992 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
4994 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
4997 _
\b7_
\b._
\b4_
\b._
\b4_
\b3 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd
5003 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
5004 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
5005 7.4.41 , page 98)'', because it allows you to sign all messages which are
5007 The Mutt Next Generation E-Mail Client 99
5009 automatically encrypted. This works around the problem noted in
5010 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.42 , page 98)'', that Mutt-ng is not able to
5011 find out whether an encrypted message is also signed. (Crypto only)
5013 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
5019 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
5020 S/MIME output, so spoofing such lines is more difficult. If you are using col-
5021 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
5024 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
5030 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
5031 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
5032 will be used instead of the classic code.
5034 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
5035 won't have any effect when used interactively.
5037 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
5043 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
5044 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
5045 cryptographic signatures. (Crypto only)
5047 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5051 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
5053 This variable controls the format of the date printed by the ``%d'' sequence in
5054 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''. This is passed to strftime(3)
5055 to process the date.
5057 Unless the first character in the string is a bang (``!''), the month and week
5058 day names are expanded according to the locale specified in the variable
5059 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.119 , page 118)''. If the first character in the string
5060 is a bang, the bang is discarded, and the month and week day names in the rest
5061 of the string are expanded in the _
\bC locale (that is in US English).
5063 The Mutt Next Generation E-Mail Client 100
5065 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\be_
\bb_
\bu_
\bg_
\b__
\bl_
\be_
\bv_
\be_
\bl
5073 This variable specifies the current debug level and may be used to increase or
5074 decrease the verbosity level during runtime. It overrides the level given with
5075 the -d command line option.
5077 Currently, this number must be >= 0 and <= 5 and muttng must be started with -d
5078 to enable debugging at all; enabling at runtime is not possible.
5080 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
5084 Default: '~f %s !~P | (~P ~C %s)'
5086 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
5087 will be interpreted if they are specified with only a simple regexp, instead of
5088 a matching pattern. The hooks are expanded when they are declared, so a hook
5089 will be interpreted according to the value of this variable at the time the
5090 hook is declared. The default value matches if the message is either from a
5091 user matching the regular expression given, or if it is from you (if the from
5092 address matches ``alternates'') and is to or cc'ed to a user matching the given
5095 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\be_
\bl_
\be_
\bt_
\be
5101 Controls whether or not messages are really deleted when closing or synchroniz-
5102 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
5103 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
5104 be kept in the mailbox.
5106 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be
5112 When sending messages with format=flowed by _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg the _
\b$_
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd (section
5113 7.4.323 , page 168) variable, this variable specifies whether to also set the
5114 DelSp parameter to yes. If this is _
\bu_
\bn_
\bs_
\be_
\bt, no additional parameter will be send
5115 as a value of no already is the default behavior.
5117 N
\bNo
\bot
\bte
\be:
\b: this variable only has an effect on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages (if _
\b$_
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
5118 (section 7.4.323 , page 168) is _
\bs_
\be_
\bt) but not on incomming.
5120 The Mutt Next Generation E-Mail Client 101
5122 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
5128 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
5129 tion. This applies when you either explicitly delete a message, or when you
5130 save it to another folder.
5132 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
5138 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
5139 subparts of individual messages in a multipart/digest. To see these subparts,
5140 press 'v' on that menu.
5142 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
5148 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
5149 viewed it is passed as standard input to _
\b$_
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br (section 7.4.54 ,
5150 page 101), and the filtered message is read from the standard output.
5152 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
5156 Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
5158 Availability: Standalone and Dotlock
5160 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
5162 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
5168 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5169 or in connection with the SMTP support via libESMTP.
5171 This variable sets the request for when notification is returned. The string
5172 consists of a comma separated list (no spaces!) of one or more of the follow-
5173 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
5174 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
5175 notified of successful transmission.
5177 The Mutt Next Generation E-Mail Client 102
5179 Example: set dsn_notify='failure,delay'
5181 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
5187 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5188 or in connection with the SMTP support via libESMTP.
5190 This variable controls how much of your message is returned in DSN messages.
5191 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
5192 return the full message.
5194 Example: set dsn_return=hdrs
5196 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
5202 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
5203 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
5204 indicate that it thinks they are duplicates of each other with an equals sign
5205 in the thread diagram.
5207 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5213 This option allows you to edit the header of your outgoing messages along with
5214 the body of your message.
5216 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5222 This variable specifies which editor is used by Mutt-ng. It defaults to the
5223 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5224 if neither of those are set.
5226 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5232 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5234 The Mutt Next Generation E-Mail Client 103
5236 string ``From '' (note the trailing space) in the beginning of a line. Useful
5237 to avoid the tampering certain mail delivery and transport agents tend to do
5240 N
\bNo
\bot
\bte
\be:
\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
5241 <em/strongly/ advised to _
\bs_
\be_
\bt this option although discouraged by the standard.
5242 Alternatively, you must take care of space-stuffing <tt/From / lines (with a
5243 trailing space) yourself.
5245 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5253 The file which includes random data that is used to initialize SSL library
5256 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5262 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5263 ``From:'' header field. Note that this information is passed to the sendmail
5264 command using the ``-f' command line switch, so don't set this option if you
5265 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page 150) yourself, or
5266 if the sendmail on your machine doesn't support that command line switch.
5268 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5274 Escape character to use for functions in the builtin editor.
5276 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5282 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5283 ing to messages, and the initial prompt for subject is skipped when forwarding
5286 N
\bNo
\bot
\bte
\be:
\b: this variable has no effect when the ``_
\b$_
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt (section 7.4.20 , page
5287 93)'' variable is _
\bs_
\be_
\bt.
5289 The Mutt Next Generation E-Mail Client 104
5291 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5297 This variable controls whether or not attachments on outgoing messages are
5298 saved along with the main body of your message.
5300 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5306 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5307 when the actual message is encrypted and/or signed. (PGP only)
5309 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5315 This variable is a colon-separated list of character encoding schemes for text
5316 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.27 , page 95) value will
5317 be used instead. For example, the following configuration would work for
5318 Japanese text handling:
5320 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5322 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5325 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5331 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5332 beginning of a pathname will be expanded to the value of this variable. Note
5333 that if you change this variable from the default value you need to make sure
5334 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5335 ables since expansion takes place during the ``set'' command.
5337 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5341 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5343 This variable allows you to customize the file browser display to your personal
5344 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page
5346 The Mutt Next Generation E-Mail Client 105
5348 115)'', but has its own set of printf(3)-like sequences:
5354 date/time folder was last modified
5363 group name (or numeric gid, if missing)
5366 number of hard links
5369 N if folder has new mail, blank otherwise
5375 * if the file is tagged, blank otherwise
5378 owner name (or numeric uid, if missing)
5381 right justify the rest of the string and pad with character 'X'
5384 pad to the end of the line with character 'X'
5386 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5392 Controls whether or not the Mail-Followup-To: header field is generated when
5393 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5394 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5395 3.13 , page 35)'' commands or detected by common mailing list headers.
5397 This field has two purposes. First, preventing you from receiving duplicate
5398 copies of replies to messages which you send to mailing lists. Second, ensuring
5399 that you do get a reply separately for any messages sent to known lists to
5400 which you are not subscribed. The header will contain only the list's address
5401 for subscribed lists, and both the list address and your own email address for
5403 The Mutt Next Generation E-Mail Client 106
5405 unsubscribed lists. Without this header, a group reply to your message sent to
5406 a subscribed list will be sent to both the list and your address, resulting in
5407 two copies of the same email for you.
5409 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5415 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
5416 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
5417 already known to have new mail.
5419 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.327 , page 169)'',
5420 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.120 , page 118)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5421 7.4.104 , page 113)''.
5423 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5429 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.247 , page 148)'',
5430 except that Mutt-ng will store a copy of your outgoing message by the username
5431 of the address you are sending to even if that mailbox does not exist.
5433 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146)'' variable.
5435 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5441 Controls the decoding of complex MIME messages into text/plain when forwarding
5442 a message. The message header is also RFC2047 decoded. This variable is only
5443 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5444 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.143 , page 123)'' is used instead.
5446 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5452 Controls the handling of encrypted messages when forwarding a message. When
5453 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5454 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5455 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.143 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5457 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5459 The Mutt Next Generation E-Mail Client 107
5465 This quadoption controls whether or not the user is automatically placed in the
5466 editor when forwarding messages. For those who always want to forward with no
5467 modification, use a setting of _
\bn_
\bo.
5469 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5475 This variable controls the default subject when forwarding a message. It uses
5476 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page
5479 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5485 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5486 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5487 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.114 , page 115)''.
5489 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bf_
\br_
\bo_
\bm
5491 Type: e-mail address
5495 This variable contains a default from address. It can be overridden using
5496 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 , page
5497 147)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.336 , page
5500 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5501 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5502 takes this email address.
5504 Defaults to the contents of the environment variable $EMAIL.
5506 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5508 Type: regular expression
5512 A regular expression used by Mutt-ng to parse the GECOS field of a password
5513 entry when expanding the alias. By default the regular expression is set to
5514 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5516 The Mutt Next Generation E-Mail Client 108
5518 the GECOS field contains a string like 'lastname, firstname' then you should
5519 do: set gecos_mask='.*'.
5521 This can be useful if you see the following behavior: you address a e-mail to
5522 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5523 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5524 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5525 to ``Franklin, Steve''.
5527 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bh_
\bd_
\br_
\bs
5533 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 ,
5534 page 37)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5535 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5536 defined header fields are added to every new message.
5538 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5544 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5545 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.341 , page
5546 172)'' setting applies.
5548 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5554 Availability: Header Cache
5556 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.83 , page 108) variable points to the header
5559 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.83 , page 108) points to a directory it will
5560 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5561 7.4.83 , page 108) points to a file that file will be a single global header
5562 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5564 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5570 If enabled the header cache will be compressed. So only one fifth of the usual
5571 diskspace is used, but the uncompression can result in a slower open of the
5573 The Mutt Next Generation E-Mail Client 109
5577 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\be_
\bl_
\bp
5583 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5584 by each menu are displayed on the first line of the screen.
5586 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5587 sequence rather than a single keystroke. Also, the help line may not be
5588 updated if a binding is changed while Mutt-ng is running. Since this variable
5589 is primarily aimed at new users, neither of these should present a major prob-
5592 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5598 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5599 7.4.94 , page 110)'' variable when adding the domain part to addresses. This
5600 variable does not affect the generation of Message-ID: header fields, and it
5601 will not lead to the cut-off of first-level domains.
5603 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5609 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5610 limiting, in the thread tree.
5612 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5618 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5621 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5627 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5628 have the same subject as their parent or closest previously displayed sibling.
5630 The Mutt Next Generation E-Mail Client 110
5632 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5638 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5639 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5640 _
\bi_
\bn_
\bg (section 7.4.88 , page 109) is set, this option will have no effect.
5642 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5648 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5649 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.87 ,
5650 page 109) is _
\bs_
\be_
\bt, this option will have no effect.
5652 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5658 This variable controls the size (in number of strings remembered) of the string
5659 history buffer. The buffer is cleared each time the variable is changed.
5661 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5667 This variable controls whether or not a Mail-Followup-To: header field is hon-
5668 ored when group-replying to a message.
5670 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5676 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5677 during generation of Message-Id: headers.
5679 Please be sure to really know what you are doing when changing this variable to
5680 configure a custom domain part of Message-IDs.
5682 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5686 The Mutt Next Generation E-Mail Client 111
5690 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5691 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5692 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5693 header field was set by the mailing list to automate responses to the list, and
5694 will ignore this field. To direct a response to the mailing list when this
5695 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
5696 sender and the list.
5698 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5706 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5707 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5708 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5709 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5710 eter is case-insensitive.
5712 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5713 ods, in order from most-secure to least-secure.
5715 Example: set imap_authenticators='gssapi:cram-md5:login'
5717 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5718 ous methods are unavailable. If a method is available but authentication fails,
5719 Mutt-ng will not connect to the IMAP server.
5721 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5727 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5728 connection, and add them to the set of mailboxes it polls for new mail. See
5729 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 36)'' command.
5731 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5739 This contains the list of characters which you would like to treat as folder
5740 separators for displaying IMAP paths. In particular it helps in using the '='
5741 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) variable.
5743 The Mutt Next Generation E-Mail Client 112
5745 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5753 Mutt-ng requests these header fields in addition to the default headers (``DATE
5754 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5755 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5756 ``index'' menu. You may want to add more headers for spam detection.
5758 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5760 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5768 You normally want to see your personal folders alongside your INBOX in the IMAP
5769 browser. If you see something else, you may set this variable to the IMAP path
5772 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5780 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5781 wait before polling open IMAP connections, to prevent the server from closing
5782 them before Mutt-ng has finished with them.
5784 The default is well within the RFC-specified minimum amount of time (30 min-
5785 utes) before a server is allowed to do this, but in practice the RFC does get
5786 violated every now and then.
5788 Reduce this number if you find yourself getting disconnected from your IMAP
5789 server due to inactivity.
5791 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5799 The Mutt Next Generation E-Mail Client 113
5801 This variable configures whether IMAP folder browsing will look for only sub-
5802 scribed folders or all folders. This can be toggled in the IMAP browser with
5803 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5805 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5813 Your login name on the IMAP server.
5815 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.110 , page
5818 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5824 This variable configures how often (in seconds) Mutt-ng should look for new
5825 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.120 ,
5826 page 118)'' variable to generate less traffic and get more accurate information
5829 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5837 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5838 you for your password when you invoke the fetch-mail function.
5840 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5841 machine, because the superuser can read your configuration even if you are the
5842 only one who can read the file.
5844 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5852 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5853 Mutt-ng will only check for new mail over existing IMAP connections. This is
5854 useful if you don't want to be prompted to user/password pairs on Mutt-ng
5856 The Mutt Next Generation E-Mail Client 114
5858 invocation, or if opening the connection is slow.
5860 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5868 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5869 fetch a message from the server. This is generally a good thing, but can make
5870 closing an IMAP folder somewhat slower. This option exists to appease speed
5873 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5881 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5884 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5892 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5893 messages. Since these messages are often harmless, or generated due to configu-
5894 ration problems on the server which are out of the users' hands, you may wish
5895 to suppress them at some point.
5897 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5905 The name of the user whose mail you intend to access on the IMAP server.
5907 This variable defaults to your user name on the local machine.
5909 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5913 The Mutt Next Generation E-Mail Client 115
5917 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5918 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5919 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5920 convert the body part to text form.
5922 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5928 Controls whether or not a copy of the message(s) you are replying to is
5929 included in your reply.
5931 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5937 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5938 sage you are replying.
5940 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5946 Specifies the string to prepend to each line of text quoted in a message to
5947 which you are replying. You are strongly encouraged not to change this value,
5948 as it tends to agitate the more fanatical netizens.
5950 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5954 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5956 This variable allows you to customize the message index display to your per-
5959 ``Format strings'' are similar to the strings used in the ``C'' function
5960 printf(3) to format output (see the man page for more detail). The following
5961 sequences are defined in Mutt-ng:
5964 address of the author
5967 reply-to address (if present; otherwise: address of author)
5969 The Mutt Next Generation E-Mail Client 116
5972 filename of the original message folder (think mailBox)
5975 the list to which the letter was sent, or else the folder name
5979 number of characters (bytes) in the message
5982 current message number
5985 date and time of the message in the format specified by ``date_for-
5986 mat'' converted to sender's time zone
5989 date and time of the message in the format specified by ``date_for-
5990 mat'' converted to the local time zone
5993 current message number in thread
5996 number of messages in current thread
5999 entire From: line (address + real name)
6002 author name, or recipient name if the message is from you
6005 spam attribute(s) of this message
6008 newsgroup name (if compiled with nntp support)
6011 message-id of the current message
6014 number of lines in the message (does not work with maildir, mh, and
6015 possibly IMAP folders)
6018 If an address in the To or CC header field matches an address
6019 defined by the users ``subscribe'' command, this displays 'To
6020 <list-name>', otherwise the same as %F.
6023 total number of message in the mailbox
6025 The Mutt Next Generation E-Mail Client 117
6028 number of hidden messages if the thread is collapsed.
6034 author's real name (or address if missing)
6037 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
6038 the message: list name or recipient name if no list
6041 subject of the message
6044 status of the message (N/D/d/!/r/*)
6047 `to:' field (recipients)
6050 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.329 ,
6054 user (login) name of the author
6057 first name of the author, or the recipient if the message is from
6061 name of organization of author (`organization:' field)
6064 `x-label:' field, if present
6067 `x-label' field, if present, and (1) not at part of a thread tree,
6068 (2) at the top of a thread, or (3) `x-label' is different from pre-
6069 ceding message's `x-label'.
6072 message status flags
6075 the date and time of the message is converted to sender's time
6076 zone, and ``fmt'' is expanded by the library function ``strftime'';
6077 a leading bang disables locales
6080 the date and time of the message is converted to the local time
6082 The Mutt Next Generation E-Mail Client 118
6084 zone, and ``fmt'' is expanded by the library function ``strftime'';
6085 a leading bang disables locales
6088 the local date and time when the message was received. ``fmt'' is
6089 expanded by the library function ``strftime''; a leading bang dis-
6093 the current local time. ``fmt'' is expanded by the library function
6094 ``strftime''; a leading bang disables locales.
6097 right justify the rest of the string and pad with character 'X'
6100 pad to the end of the line with character 'X'
6102 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.329 , page 169)''.
6104 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
6110 How to invoke ispell (GNU's spell-checking software).
6112 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6118 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
6119 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.130 , page 121)'' mailbox, or as a result of
6120 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36)'' command.
6122 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
6128 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
6129 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
6130 will ask if you really intended to reply to the author only.
6132 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
6138 The Mutt Next Generation E-Mail Client 119
6140 The locale used by strftime(3) to format dates. Legal values are the strings
6141 your system accepts for the locale variable LC_TIME.
6143 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6149 This variable configures how often (in seconds) Mutt-ng should look for new
6152 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
6153 7.4.104 , page 113).
6155 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
6161 This variable specifies which files to consult when attempting to display MIME
6162 bodies not directly supported by Mutt-ng.
6164 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
6170 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
6171 well-defined set of safe characters. This is the safe setting, but we are not
6172 sure it doesn't break some more advanced MIME stuff.
6174 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!
6176 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\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
6182 Availability: Header Cache
6184 Check for Maildir unaware programs other than Mutt-ng having modified maildir
6185 files when the header cache is in use. This incurs one stat(2) per message
6186 every time the folder is opened.
6188 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
6194 The Mutt Next Generation E-Mail Client 120
6196 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
6197 flag instead of physically deleted.
6199 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
6200 effect on other mailbox types.
6202 It is similiar to the trash option.
6204 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
6210 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
6211 mailbox without reading them.
6213 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
6214 up with an 'O' next to them in the ``index'' menu, indicating that they are
6217 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
6223 Controls the display of wrapped lines in the internal pager. If set, a ``+''
6224 marker is displayed at the beginning of wrapped lines. Also see the
6225 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.269 , page 154)'' variable.
6227 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\ba_
\bs_
\bk
6229 Type: regular expression
6233 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6234 operator ``!''. Only files whose names match this mask will be shown. The
6235 match is always case-sensitive.
6237 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6243 When set non-zero, this specifies the maximum number of recipient header lines
6244 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6245 case the number of lines exeeds its value, the last line will have 3 dots
6248 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6250 The Mutt Next Generation E-Mail Client 121
6256 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6257 is limited to this length. A value of 0 (which is also the default) means that
6258 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6259 (section 7.4.343 , page 172).
6261 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\bb_
\bo_
\bx
6267 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6268 7.4.303 , page 162)'' folder will be appended.
6270 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6276 The default mailbox type used when creating new folders. May be any of mbox,
6277 MMDF, MH and Maildir.
6279 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6285 This variable controls the number of lines of context that are given when
6286 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.173 , page
6289 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6295 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6296 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6297 entry may move off the bottom.
6299 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6305 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6307 The Mutt Next Generation E-Mail Client 122
6309 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6310 vious page of the menu is displayed (useful for slow links to avoid many
6313 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6319 This is the string displayed in the ``attachment'' menu for attachments of type
6320 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6321 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''.
6323 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6329 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6330 if the user had pressed the ESC key and whatever key remains after having the
6331 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6332 then this is treated as if the user had pressed ESC then ``x''. This is
6333 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6334 the ASCII character ``x''.
6336 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\be_
\bt_
\bo_
\bo
6342 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6343 from the list of recipients when replying to a message.
6345 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6351 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6352 _
\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-
6353 able is set, the message files will simply be deleted.
6355 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6361 The name of the MH sequence used for flagged messages.
6363 The Mutt Next Generation E-Mail Client 123
6365 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6371 The name of the MH sequence used to tag replied messages.
6373 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6379 The name of the MH sequence used for unseen messages.
6381 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6387 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6388 part instead of included in the main body of the message.
6390 This is useful for forwarding MIME messages so the receiver can properly view
6391 the message as it was delivered to you. If you like to switch between MIME and
6392 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6394 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.74 , page 106)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6395 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.143 , page 123)''.
6397 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6403 Controls the decoding of complex MIME messages into text/plain when forwarding
6404 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bs_
\be_
\bt. Other-
6405 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.74 , page 106)'' is used instead.
6407 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6413 When forwarding multiple attachments of a MIME message from the recvattach
6414 menu, attachments which cannot be decoded in a reasonable manner will be
6415 attached to the newly composed message if this option is set.
6417 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6419 The Mutt Next Generation E-Mail Client 124
6423 Default: '%4n %c %-16s %a'
6425 Availability: Mixmaster
6427 This variable describes the format of a remailer line on the mixmaster chain
6428 selection screen. The following printf(3)-like sequences are supported:
6431 The running number on the menu.
6434 Remailer capabilities.
6437 The remailer's short name.
6440 The remailer's e-mail address.
6442 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6446 Default: 'mixmaster'
6448 Availability: Mixmaster
6450 This variable contains the path to the Mixmaster binary on your system. It is
6451 used with various sets of parameters to gather the list of known remailers, and
6452 to finally send a message through the mixmaster chain.
6454 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bm_
\bo_
\bv_
\be
6460 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6461 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.130 , page 121)'' mailbox, or as a result of a
6462 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36)'' command.
6464 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6468 Default: '%Y%m%d%h%M%s.G%P%p'
6470 This is the format for the ``local part'' of the Message-Id: header field gen-
6471 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6472 generated. The '%' character marks that certain data will be added to the
6473 string, similar to printf(3). The following characters are allowed:
6475 The Mutt Next Generation E-Mail Client 125
6478 the current day of month
6490 the current UNIX timestamp (octal)
6496 the current Message-ID prefix (a character rotating with every Mes-
6497 sage-ID being generated)
6500 a random integer value (decimal)
6503 a random integer value (hexadecimal)
6509 the current UNIX timestamp (decimal)
6512 the current UNIX timestamp (hexadecimal)
6515 the current year (Y2K compliant)
6520 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6521 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6523 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6529 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6530 threads to fit on the screen.
6532 The Mutt Next Generation E-Mail Client 126
6534 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6542 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6543 ing the body of an outgoing news article.
6545 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6553 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6554 ing the body of an outgoing news article.
6556 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6560 Default: '~/.muttng'
6564 This variable points to directory where Mutt-ng will cache news article head-
6565 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6566 when you enter a newsgroup.
6568 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6569 cally increases speed and lowers traffic.
6571 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6579 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6580 when you leaving it.
6582 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6588 The Mutt Next Generation E-Mail Client 127
6592 This variable controls how many news articles to cache per newsgroup (if
6593 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.152 , page 126)) and how
6594 many news articles to show in the ``index'' menu.
6596 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.154 ,
6597 page 126), all older ones will be removed/not shown in the index.
6599 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6607 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6608 header field, a follow-up to the newsgroup is not permitted. The message will
6609 be mailed to the submitter of the message via mail.
6611 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6615 Default: '%4C %M%N %5s %-45.45f %d'
6619 This variable allows you to customize the newsgroup browser display to your
6620 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 ,
6621 page 115)'', but has its own set of printf(3)-like sequences:
6623 %C current newsgroup number
6624 %d description of newsgroup (retrieved from server)
6626 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6627 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6628 %n number of new articles in newsgroup
6629 %s number of unread articles in newsgroup
6630 %>X right justify the rest of the string and pad with character "X"
6631 %|X pad to the end of the line with character "X"
6633 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6641 This variable specifies the name (or address) of the NNTP server to be used.
6643 The Mutt Next Generation E-Mail Client 128
6645 It defaults to the value specified via the environment variable $NNTPSERVER or
6646 contained in the file /etc/nntpserver.
6648 You can also specify a username and an alternative port for each newsserver,
6651 [nntp[s]://][username[:password]@]newsserver[:port]
6653 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6654 security risk since the superuser of your machine may read it regardless of the
6657 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6665 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6666 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6667 lowing printf(3)-style sequence is understood:
6671 Example: set inews='/usr/local/bin/inews -hS'
6673 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6681 This variable controls whether or not descriptions for newsgroups are to be
6682 loaded when subscribing to a newsgroup.
6684 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6692 The time in seconds until any operations on a newsgroup except posting a new
6693 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6694 each operation in index (stepping, read article, etc.).
6696 The Mutt Next Generation E-Mail Client 129
6698 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6706 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6707 encoded according to RFC2047.
6709 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6711 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6715 Default: '~/.newsrc'
6719 This file contains information about subscribed newsgroup and articles read so
6722 To ease the use of multiple news servers, the following printf(3)-style
6723 sequence is understood:
6727 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6735 Your password for NNTP account.
6737 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6738 the superuser of your machine may read it regardless of the file's permissions.
6740 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6748 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6749 sions to post (e.g. moderated).
6751 The Mutt Next Generation E-Mail Client 130
6753 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6754 is totally read-only, that posting will not have any effect.
6756 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6764 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6765 was connection lost.
6767 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6775 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6776 file and into the news cache.
6778 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6786 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6787 browser. Otherwise, it will be done only once for a newsserver. Also controls
6788 whether or not the number of new articles of subscribed newsgroups will be
6791 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6799 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6800 played in the newsgroup browser.
6802 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6808 The Mutt Next Generation E-Mail Client 131
6812 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6813 tification, Mutt-ng will prompt you for your account name.
6815 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6823 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6824 name of the original article author) to articles that you followup to.
6826 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6832 This specifies the operating system name for the User-Agent: header field. If
6833 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6834 returns. If uname(2) fails, ``UNIX'' will be used.
6836 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6838 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bp_
\ba_
\bg_
\be_
\br
6844 This variable specifies which pager you would like to use to view messages.
6845 ``builtin'' means to use the builtin pager, otherwise this variable should
6846 specify the pathname of the external pager you would like to use.
6848 Using an external pager may have some disadvantages: Additional keystrokes are
6849 necessary because you can't call Mutt-ng functions directly from the pager, and
6850 screen resizes cause lines longer than the screen width to be badly formatted
6853 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6859 This variable controls the number of lines of context that are given when dis-
6860 playing the next or previous page in the internal pager. By default, Mutt-ng
6861 will display the line after the last one on the screen at the top of the next
6862 page (0 lines of context).
6864 The Mutt Next Generation E-Mail Client 132
6866 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6870 Default: '-%Z- %C/%m: %-20.20n %s'
6872 This variable controls the format of the one-line message ``status'' displayed
6873 before each message in either the internal or an external pager. The valid
6874 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''
6877 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6883 Determines the number of lines of a mini-index which is shown when in the
6884 pager. The current message, unless near the top or bottom of the folder, will
6885 be roughly one third of the way down this mini-index, giving the reader the
6886 context of a few messages before and after the message. This is useful, for
6887 example, to determine how many messages remain to be read in the current
6888 thread. One of the lines is reserved for the status bar from the index, so a
6889 _
\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
6890 0 results in no index being shown. If the number of messages in the current
6891 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
6894 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6900 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6901 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
6903 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6909 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
6910 whenever the user performs an operation which ordinarily would result in the
6911 contents of the message being operated on. For example, if the user displays a
6912 pgp-traditional message which has not been manually checked with the check-tra-
6913 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
6916 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6920 The Mutt Next Generation E-Mail Client 133
6924 This option controls whether Mutt-ng generates old-style inline (traditional)
6925 PGP encrypted or signed messages under certain circumstances. This can be
6926 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
6928 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6929 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6930 ing PGP/MIME messages when inline (traditional) would not work. See also:
6931 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.194 , page 136)''.
6933 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.
6936 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
6942 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
6943 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
6945 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6951 This format is used to create a old-style ``clearsigned'' PGP message.
6953 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)
6955 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6961 This format strings specifies a command which is used to decode application/pgp
6964 The PGP command formats have their own set of printf(3)-like sequences:
6967 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
6968 string otherwise. Note: This may be used with a %? construct.
6971 Expands to the name of a file containing a message.
6974 Expands to the name of a file containing the signature part of a
6975 multipart/signed attachment when verifying it.
6977 The Mutt Next Generation E-Mail Client 134
6980 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.198 , page 137).
6983 One or more key IDs.
6985 For examples on how to configure these formats for the various versions of PGP
6986 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
6987 subdirectory which has been installed on your system alongside the documenta-
6990 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6996 This command is used to decrypt a PGP encrypted message. (PGP only)
6998 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7004 This command is used to encrypt a body part without signing it. (PGP only)
7006 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7012 This command is used to both sign and encrypt a body part. (PGP only)
7014 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7018 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
7020 This variable allows you to customize the PGP key selection menu to your per-
7021 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page
7022 115)'', but has its own set of printf(3)-like sequences:
7033 The Mutt Next Generation E-Mail Client 135
7048 trust/validity of the key-uid association
7051 date of the key where <s> is an strftime(3) expression
7055 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7061 This command is used to export a public key from the user's key ring. (PGP
7064 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7070 This command is invoked whenever Mutt-ng will need public key information. %r
7071 is the only printf(3)-like sequence used with this format. (PGP only)
7073 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
7075 Type: regular expression
7079 If you assign a text to this variable, then a PGP signature is only considered
7080 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.204 , page 139)
7081 contains the text. Use this variable if the exit code from the command is 0
7082 even for bad signatures. (PGP only)
7084 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
7090 The Mutt Next Generation E-Mail Client 136
7092 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
7093 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
7094 want to play interesting key selection games. (PGP only)
7096 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7102 This command is used to import a key from a message into the user's public key
7105 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7111 This command is used to list the public key ring's contents. The output format
7112 must be analogous to the one used by gpg --list-keys --with-colons.
7114 This format is also generated by the pgpring utility which comes with Mutt-ng.
7117 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7123 This command is used to list the secret key ring's contents. The output format
7124 must be analogous to the one used by gpg --list-keys --with-colons.
7126 This format is also generated by the pgpring utility which comes with Mutt-ng.
7129 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
7135 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
7138 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
7144 This option controls whether Mutt-ng will prompt you for automatically sending
7145 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
7147 The Mutt Next Generation E-Mail Client 137
7151 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.
7154 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7160 Setting this variable will cause Mutt-ng to always attempt to create an inline
7161 (traditional) message when replying to a message which is PGP encrypted/signed
7162 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
7163 required. This option does not automatically detect if the (replied-to) mes-
7164 sage is inline; instead it relies on Mutt-ng internals for previously
7165 checked/flagged messages.
7167 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7168 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7169 ing PGP/MIME messages when inline (traditional) would not work. See also:
7170 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.194 , page 136)''.
7172 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.
7175 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
7181 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
7182 and multipart/encrypted body parts.
7184 This is useful for applications like encrypted and signed mailing lists, where
7185 the outer layer (multipart/encrypted) can be easily removed, while the inner
7186 multipart/signed part is retained. (PGP only)
7188 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
7194 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
7195 This includes keys which have been revoked, have expired, or have been marked
7196 as ``disabled'' by the user. (PGP only)
7198 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
7204 The Mutt Next Generation E-Mail Client 138
7206 If you have more than one key pair, this option allows you to specify which of
7207 your private keys to use. It is recommended that you use the keyid form to
7208 specify your key (e.g., ``0x00112233''). (PGP only)
7210 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7216 This command is used to create the detached PGP signature for a multi-
7217 part/signed PGP/MIME body part. (PGP only)
7219 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
7225 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7229 sort alphabetically by user id
7232 sort alphabetically by key id
7235 sort by key creation date
7238 sort by the trust of the key
7240 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7243 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7249 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7250 printable. Please note that unsetting this variable may lead to problems with
7251 non-verifyable PGP signatures, so only change this if you know what you are
7254 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7260 The Mutt Next Generation E-Mail Client 139
7262 The number of seconds after which a cached passphrase will expire if not used.
7263 Default: 300. (PGP only)
7265 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7271 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7273 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7279 This command is used to verify PGP signatures. (PGP only)
7281 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7287 This command is used to verify key information from the key selection menu.
7290 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7296 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
7297 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7298 ers and will attempt to PGP/MIME decode the messages first.
7300 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7306 The separator to add between messages when piping a list of tagged messages to
7307 an external Unix command.
7309 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7315 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7317 The Mutt Next Generation E-Mail Client 140
7319 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7320 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7321 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7322 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7323 (section 7.4.207 , page 139)'' separator is added after each message.
7325 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7333 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7334 fall back to other authentication methods if the previous methods are unavail-
7335 able. If a method is available but authentication fails, Mutt-ng will not con-
7336 nect to the POP server.
7338 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7346 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7347 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7348 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7349 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7351 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7352 Mutt-ng will try all available methods, in order from most-secure to least-
7355 Example: set pop_authenticators='digest-md5:apop:user'
7357 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7365 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7366 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7367 load messages but also leave them on the POP server.
7369 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7373 The Mutt Next Generation E-Mail Client 141
7379 The name of your POP server for the ``fetch-mail'' function. You can also
7380 specify an alternative port, username and password, i.e.:
7382 [pop[s]://][username[:password]@]popserver[:port]
7384 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7385 the superuser of your machine may read it regardless of the file's permissions.
7387 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7395 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7396 retrieving only unread messages from the POP server when using the ``fetch-
7399 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7407 This variable configures how often (in seconds) POP should look for new mail.
7409 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7417 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7418 for your password when you open POP mailbox.
7420 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7421 the superuser of your machine may read it regardless of the file's permissions.
7423 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7429 The Mutt Next Generation E-Mail Client 142
7433 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7436 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7444 Your login name on the POP server.
7446 This variable defaults to your user name on the local machine.
7448 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7454 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 93)'' variable, Mutt-ng
7455 will append this string after the inclusion of a message which is being replied
7458 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7464 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7465 7.4.220 , page 142)'' mailbox when you elect not to send immediately.
7467 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7471 Default: '~/postponed'
7473 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.219 , page 142)
7474 sending a message'' which you are editing. When you choose to postpone a mes-
7475 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7476 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.219 , page 142)'' variable.
7478 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7484 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a
7486 The Mutt Next Generation E-Mail Client 143
7488 connection to the server. This is useful for setting up secure connections,
7489 e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up
7490 opening the server. Example:
7492 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7493 /dev/null > /dev/null'
7495 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7497 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7498 machine without having to enter a password.
7500 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bp_
\br_
\bi_
\bn_
\bt
7506 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7507 by default, because some people accidentally hit ``p'' often.
7509 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7515 This specifies the command pipe that should be used to print messages.
7517 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7523 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7524 message is decoded before it is passed to the external command specified by
7525 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 143). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7526 cessing will be applied to the message when printing it. The latter setting
7527 may be useful if you are using some advanced printer filter which is able to
7528 properly format e-mail messages for printing.
7530 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7536 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7537 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 143) is executed
7538 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7539 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 143) is executed
7540 only once, and all the messages are concatenated, with a form feed as the mes-
7543 The Mutt Next Generation E-Mail Client 144
7545 Those who use the enscript(1) program's mail-printing mode will most likely
7546 want to set this option.
7548 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7554 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.172 , page 131)'', setting this
7555 variable will cause Mutt-ng to prompt you for a command when the pager exits
7556 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7557 index menu when the external pager exits.
7559 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7565 This specifies the command that Mutt-ng will use to make external address
7566 queries. The string should contain a %s, which will be substituted with the
7567 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 58)'' for more
7570 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\bq_
\bu_
\bi_
\bt
7576 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7577 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7578 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
7581 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7587 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7588 tion 7.4.114 , page 115)''.
7590 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7596 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7597 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7598 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.114 , page 115)''.
7600 The Mutt Next Generation E-Mail Client 145
7602 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7604 Type: regular expression
7606 Default: '^([ \t]*[|>:}#])+'
7608 A regular expression used in the internal-pager to determine quoted sections of
7609 text in the body of a message.
7611 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
7612 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7613 the beginning of quoted lines.
7615 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7621 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7622 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7623 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7624 reads message 25, and then again when it gets to message 50). This variable is
7625 meant to indicate progress when reading large mailboxes which may take some
7626 time. When set to 0, only a single message will appear before the reading the
7629 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.345 , page 173)'' variable.
7631 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7637 If set, all folders are opened in read-only mode.
7639 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7645 This variable specifies what ``real'' or ``personal'' name should be used when
7648 By default, this is the GECOS field from /etc/passwd.
7650 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7651 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.79 , page 107) variable.
7653 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7657 The Mutt Next Generation E-Mail Client 146
7661 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7662 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.220 , page 142)''.
7664 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7666 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7672 This specifies the file into which your outgoing messages should be appended.
7673 (This is meant as the primary method for saving a copy of your messages, but
7674 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37)'' com-
7675 mand to create a Bcc: header field with your email address in it.)
7677 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b6_
\b) is overridden by the
7678 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.73 , page 106)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7679 7.4.247 , page 148)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page
7682 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7684 Type: regular expression
7686 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7688 A regular expression used to recognize reply messages when threading and reply-
7689 ing. The default value corresponds to the English ``Re:'' and the German
7692 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7698 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7699 that you want to reply to the recipients of that message rather than to your-
7702 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7708 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7709 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7710 use the address in the ``From:'' header field instead.
7712 This option is useful for reading a mailing list that sets the ``Reply-To:''
7714 The Mutt Next Generation E-Mail Client 147
7716 header field to the list address and you want to send a private message to the
7717 author of a message.
7719 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7725 When set, the cursor will be automatically advanced to the next (possibly
7726 undeleted) message whenever a command that modifies the current message is exe-
7729 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7735 This variable controls whether or not Mutt-ng will display the ``personal''
7736 name from your aliases in the index menu if it finds an alias that matches the
7737 message's sender. For example, if you have the following alias:
7739 alias juser abd30425@somewhere.net (Joe User)
7741 and then you receive mail which contains the following header:
7743 From: abd30425@somewhere.net
7745 It would be displayed in the index menu as ``Joe User'' instead of
7746 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7747 not human friendly (like CompuServe addresses).
7749 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7755 It may sometimes arrive that you receive mail to a certain machine, move the
7756 messages to another machine, and reply to some the messages from there. If
7757 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7758 using the address where you received the messages you are replying to i
\bif
\bf that
7759 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7760 would be used doesn't match your alternates, the From: line will use your
7761 address on the current machine.
7763 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7769 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 ,
7771 The Mutt Next Generation E-Mail Client 148
7773 page 147) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7774 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7775 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7776 (section 7.4.234 , page 145) variable.
7778 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7784 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7785 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7786 ments to files named like this:
7788 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7790 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7791 effect before you have changed folders.
7793 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7794 standard, but nevertheless encountered in the wild.
7796 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7797 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7798 encoding specified in RFC 2231.
7800 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7806 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7807 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.247 , page 148)'' or
7808 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.73 , page 106)'' is _
\bs_
\be_
\bt too, the selection of the
7809 fcc folder will be changed as well.
7811 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7817 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7818 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page 162)'' which is
7819 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7821 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7822 and Maildir directories.
7824 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7828 The Mutt Next Generation E-Mail Client 149
7832 This variable controls how copies of outgoing messages are saved. When set, a
7833 check is made to see if a mailbox specified by the recipient address exists
7834 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 ,
7835 page 104)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7836 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7837 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146)'' mailbox.
7839 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.73 , page 106)'' variable.
7841 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\bs_
\bc_
\bo_
\br_
\be
7847 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7848 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
7849 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.249 , page 149)'' variable and friends are used.
7851 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7857 Messages which have been assigned a score equal to or lower than the value of
7858 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7859 scores are always greater than or equal to zero, the default setting of this
7860 variable will never mark a message for deletion.
7862 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7868 Messages which have been assigned a score greater than or equal to this vari-
7869 able's value are automatically marked ``flagged''.
7871 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7877 Messages which have been assigned a score equal to or lower than the value of
7878 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7879 scores are always greater than or equal to zero, the default setting of this
7880 variable will never mark a message read.
7882 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7884 The Mutt Next Generation E-Mail Client 150
7888 Default: 'us-ascii:iso-8859-1:utf-8'
7890 A list of character sets for outgoing messages. Mutt-ng will use the first
7891 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7892 (section 7.4.27 , page 95)'' is not iso-8859-1 and recipients may not under-
7893 stand UTF-8, it is advisable to include in the list an appropriate widely used
7894 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7895 instead of or after iso-8859-1.
7897 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7901 Default: '/usr/sbin/sendmail -oem -oi'
7903 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7904 Mutt-ng expects that the specified program interprets additional arguments as
7905 recipient addresses.
7907 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
7913 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 ,
7914 page 150)'' process to finish before giving up and putting delivery in the
7917 Mutt-ng interprets the value of this variable as follows:
7920 number of seconds to wait for sendmail to finish before continuing
7923 wait forever for sendmail to finish
7926 always put sendmail in the background without waiting
7928 Note that if you specify a value other than 0, the output of the child process
7929 will be put in a temporary file. If there is some error, you will be informed
7930 as to where to find the output.
7932 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\bh_
\be_
\bl_
\bl
7938 Command to use when spawning a subshell. By default, the user's login shell
7939 from /etc/passwd is used.
7941 The Mutt Next Generation E-Mail Client 151
7943 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
7949 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
7950 7.4.260 , page 152) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
7951 split a folder name into ``hierarchy items.''
7953 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
7959 This specifies the delimiter between the sidebar (if visible) and other
7962 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
7968 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
7970 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7974 Default: '%m%?n?(%n)?%?f?[%f]?'
7976 This variable controls how message counts are printed when the sidebar is
7977 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
7978 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
7979 mbox-style mailboxes.)
7981 The following printf(3)-like sequences are supported all of which may be
7985 Number of deleted messages. 1)
7988 Number of flagged messages.
7991 Total number of messages.
7994 Total number of messages shown, i.e. not hidden by a limit. 1)
7996 The Mutt Next Generation E-Mail Client 152
7999 Number of new messages.
8002 Number of tagged messages. 1)
8004 1) These expandos only have a non-zero value for the current mailbox and will
8005 always be zero otherwise.
8007 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\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
8013 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
8014 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
8015 7.4.262 , page 152)'' is set to a too low value). For example, if the news-
8016 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
8017 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
8020 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
8021 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.256 , page 150) variable.
8023 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
8029 This specifies whether or not to show the sidebar (a list of folders specified
8030 with the ``mailboxes'' command).
8032 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
8038 The width of the sidebar.
8040 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
8046 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
8047 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.265 , page 153)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
8048 that you not unset this variable unless your ``signature'' contains just your
8049 name. The reason for this is because many software packages use ``-- \n'' to
8050 detect your signature.
8052 The Mutt Next Generation E-Mail Client 153
8054 For example, Mutt-ng has the ability to highlight the signature in a different
8055 color in the builtin pager.
8057 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8063 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
8064 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
8065 know what you are doing, and are prepared to take some heat from netiquette
8068 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
8072 Default: '~/.signature'
8074 Specifies the filename of your signature, which is appended to all outgoing
8075 messages. If the filename ends with a pipe (``|''), it is assumed that file-
8076 name is a shell command and input should be read from its stdout.
8078 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
8084 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
8085 people that want to sign off every message they send with their name.
8087 If you want to insert your website's URL, additional contact information or
8088 witty quotes into your mails, better use a signature file instead of the sig-
8091 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8095 Default: '~f %s | ~s %s'
8097 Specifies how Mutt-ng should expand a simple search into a real search pattern.
8098 A simple search is one that does not contain any of the ~ operators. See
8099 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83)'' for more information on search patterns.
8101 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
8102 will automatically expand it to the value specified by this variable. For the
8103 default value it would be:
8107 The Mutt Next Generation E-Mail Client 154
8109 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
8115 Specifies time, in seconds, to pause while displaying certain informational
8116 messages, while moving from folder to folder and after expunging messages from
8117 the current folder. The default is to pause one second, so a value of zero for
8118 this option suppresses the pause.
8120 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
8126 Controls the display of lines longer than the screen width in the internal
8127 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
8128 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.126 ,
8129 page 120)'' variable.
8131 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
8133 Type: regular expression
8135 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
8137 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
8138 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.231 , page 144)'', most notably smileys in the
8141 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
8147 This flag controls whether you want to be asked to enter a label for a certifi-
8148 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
8151 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
8157 This variable contains the name of either a directory, or a file which contains
8158 trusted certificates for use with OpenSSL. (S/MIME only)
8160 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
8164 The Mutt Next Generation E-Mail Client 155
8168 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
8169 and retrieval of keys by itself. This is very basic right now, and keys and
8170 certificates are stored in two different directories, both named as the hash-
8171 value retrieved from OpenSSL. There is an index file which contains mailbox-
8172 address keyid pairs, and which can be manually edited. This one points to the
8173 location of the certificates. (S/MIME only)
8175 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8181 This format string specifies a command which is used to decrypt application/x-
8182 pkcs7-mime attachments.
8184 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
8188 Expands to the name of a file containing a message.
8191 Expands to the name of a file containing the signature part of a
8192 multipart/signed attachment when verifying it.
8195 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.276 ,
8199 One or more certificate IDs.
8202 The algorithm used for encryption.
8205 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
8206 7.4.272 , page 154) points to a directory or file, this expands to
8207 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.272 , page 154)' or
8208 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.272 , page 154)'.
8210 For examples on how to configure these formats, see the smime.rc in the sam-
8211 ples/ subdirectory which has been installed on your system alongside the docu-
8212 mentation. (S/MIME only)
8214 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\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
8220 The Mutt Next Generation E-Mail Client 156
8222 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
8223 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8224 mailbox-address to determine the key to use. It will ask you to supply a key,
8225 if it can't find one. (S/MIME only)
8227 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8233 This is the default key-pair to use for signing. This must be set to the keyid
8234 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8236 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8242 This command is used to create encrypted S/MIME messages. (S/MIME only)
8244 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8250 This sets the algorithm that should be used for encryption. Valid choices are
8251 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8253 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8255 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8261 This command is used to extract X509 certificates from a PKCS7 structure.
8264 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\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
8270 This command is used to extract the mail address(es) used for storing X509 cer-
8271 tificates, and for verification purposes (to check whether the certificate was
8272 issued for the sender's mailbox). (S/MIME only)
8274 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\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
8276 The Mutt Next Generation E-Mail Client 157
8282 This command is used to extract only the signers X509 certificate from a S/MIME
8283 signature, so that the certificate's owner may get compared to the email's
8284 ``From:'' header field. (S/MIME only)
8286 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\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
8292 This command is used to import a certificate via smime_keysng. (S/MIME only)
8294 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8300 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8301 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8303 However, this has no effect while replying, since Mutt-ng will automatically
8304 select the same application that was used to sign/encrypt the original message.
8306 (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-
8307 tion 7.4.40 , page 98).) (S/MIME only)
8309 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8315 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8316 retrieval of keys/certs by itself. This is very basic right now, and stores
8317 keys and certificates in two different directories, both named as the hash-
8318 value retrieved from OpenSSL. There is an index file which contains mailbox-
8319 address keyid pair, and which can be manually edited. This one points to the
8320 location of the private keys. (S/MIME only)
8322 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8328 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8329 to extract the public X509 certificate(s). (S/MIME only)
8331 The Mutt Next Generation E-Mail Client 158
8333 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8339 This command is used to created S/MIME signatures of type multipart/signed,
8340 which can be read by all mail clients. (S/MIME only)
8342 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\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
8348 This command is used to created S/MIME signatures of type application/x-
8349 pkcs7-signature, which can only be handled by mail clients supporting the
8350 S/MIME extension. (S/MIME only)
8352 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8358 The number of seconds after which a cached passphrase will expire if not used.
8361 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8367 This command is used to verify S/MIME signatures of type multipart/signed.
8370 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\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
8376 This command is used to verify S/MIME signatures of type application/x-
8377 pkcs7-mime. (S/MIME only)
8379 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8387 The Mutt Next Generation E-Mail Client 159
8389 If this variable is non-empty, it'll be used as the envelope sender. If it's
8390 empty (the default), the value of the regular From: header will be used.
8392 This may be necessary as some providers don't allow for arbitrary values as the
8393 envelope sender but only a particular one which may not be the same as the
8394 user's desired From: header.
8396 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8404 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8405 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8406 _
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page 150)'', and any associated variables.
8408 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8416 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8417 7.4.296 , page 159)'' is set, but this variable is not, you will be prompted
8418 for a password when sending.
8420 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8421 the superuser of your machine may read it regardless of the file's permissions.
8423 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8431 Defines the port that the SMTP host is listening on for mail delivery. Must be
8432 specified as a number.
8434 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8435 will probably desire 587, the mail submission port.
8437 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8443 The Mutt Next Generation E-Mail Client 160
8445 Availability: SMTP (and SSL)
8447 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8448 server does not support STARTTLS or there is an error in the TLS Handshake, the
8449 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8450 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8451 port enabled in order to use it.
8453 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8461 Defines the username to use with SMTP AUTH. Setting this variable will cause
8462 Mutt-ng to attempt to use SMTP AUTH when sending.
8464 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\bs_
\bo_
\br_
\bt
8470 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8475 mailbox-order (unsorted)
8483 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8484 (example: set sort=reverse-date-sent).
8486 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8492 Specifies how the entries in the ``alias'' menu are sorted. The following are
8495 The Mutt Next Generation E-Mail Client 161
8497 address (sort alphabetically by email address)
8498 alias (sort alphabetically by alias name)
8499 unsorted (leave in order specified in .muttrc)
8501 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8507 When sorting by threads, this variable controls how threads are sorted in rela-
8508 tion to other threads, and how the branches of the thread trees are sorted.
8509 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160)'' can,
8510 except threads (in that case, Mutt-ng will just use date-sent). You can also
8511 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8512 come after reverse-. The last- prefix causes messages to be sorted against its
8513 siblings by which has the last descendant, using the rest of sort_aux as an
8516 For instance, set sort_aux=last-date-received would mean that if a new message
8517 is received in a thread, that thread becomes the last one displayed (or the
8518 first, if you have set sort=reverse-threads.)
8520 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8521 (section 7.4.299 , page 160) is reversed again (which is not the right thing
8522 to do, but kept to not break any existing configuration setting).
8524 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8530 Specifies how to sort entries in the file browser. By default, the entries are
8531 sorted alphabetically. Valid values:
8533 alpha (alphabetically)
8538 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8539 (example: set sort_browser=reverse-date).
8541 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8547 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
8549 The Mutt Next Generation E-Mail Client 162
8551 (section 7.4.318 , page 167)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8552 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.301 ,
8553 page 161) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8554 sage by subject if the subject of the child message starts with a substring
8555 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.237 , page 146)''. With
8556 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.301 , page 161) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8557 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
8558 7.4.237 , page 146)'' parts of both messages are identical.
8560 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8566 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.302 , page 161)'' controls what happens when
8567 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8568 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8569 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.302 ,
8570 page 161)'' as a separator.
8572 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8578 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8579 you can specify its location with this variable. Mutt-ng will automatically
8580 set this variable to the value of the environment variable $MAIL if it is not
8583 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8589 This variable specifies a file containing trusted CA certificates. Any server
8590 certificate that is signed with one of these CA certificates are also automati-
8593 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8595 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8603 The file containing a client certificate and its associated private key.
8605 The Mutt Next Generation E-Mail Client 163
8607 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8613 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8614 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8615 server does not advertise the capability, since it would otherwise have to
8616 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8617 7.4.308 , page 163)''.
8619 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8625 Availability: GNUTLS
8627 This variable specifies the minimum acceptable prime size (in bits) for use in
8628 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8631 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8637 Availability: SSL or GNUTLS
8639 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8640 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8641 regardless of the server's capabilities.
8643 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8651 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8654 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8660 Availability: SSL or GNUTLS
8662 The Mutt Next Generation E-Mail Client 164
8664 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8667 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8673 Availability: SSL or GNUTLS
8675 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8678 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8686 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8687 store when checking if server certificate is signed by a trusted CA.
8689 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8695 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8696 tion 7.4.314 , page 164)''. The first character is used when the mailbox is
8697 unchanged. The second is used when the mailbox has been changed, and it needs
8698 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8699 if the mailbox will not be written when exiting that mailbox (You can toggle
8700 whether to write changes to a mailbox with the toggle-write operation, bound by
8701 default to ``%''). The fourth is used to indicate that the current folder has
8702 been opened in attach-message mode (Certain operations like composing a new
8703 mail, replying, forwarding, etc. are not permitted in this mode).
8705 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8709 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8710 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8711 %l?]---(%s/%S)-%>-(%P)---'
8713 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8714 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)'', but has
8715 its own set of printf(3)-like sequences:
8717 The Mutt Next Generation E-Mail Client 165
8720 number of mailboxes with new mail *
8723 the short pathname of the current mailbox
8726 number of deleted messages *
8729 the full pathname of the current mailbox
8732 number of flagged messages *
8738 size (in bytes) of the current mailbox *
8741 size (in bytes) of the messages shown (i.e., which match the cur-
8745 the number of messages in the mailbox *
8748 the number of messages shown (i.e., which match the current limit)
8752 number of new messages in the mailbox *
8755 number of old unread messages *
8758 number of postponed messages *
8761 percentage of the way through the index
8764 modified/read-only/won't-write/attach-message indicator, according
8765 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.313 , page 164)
8768 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160))
8771 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.299 , page
8774 The Mutt Next Generation E-Mail Client 166
8777 number of tagged messages *
8780 number of unread messages *
8783 Mutt-ng version string
8786 currently active limit pattern, if any *
8789 right justify the rest of the string and pad with 'X'
8792 pad to the end of the line with 'X'
8794 * = can be optionally printed if nonzero
8796 Some of the above sequences can be used to optionally print a string if their
8797 value is nonzero. For example, you may only want to see the number of flagged
8798 messages if such messages exist, since zero is not particularly meaningful. To
8799 optionally print a string based upon one of the above sequences, the following
8802 %?<sequence_char>?<optional_string>?
8804 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
8805 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
8806 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8809 Here is an example illustrating how to optionally print the number of new mes-
8812 %?n?%n new messages.?
8814 Additionally you can switch between two strings, the first one, if a value is
8815 zero, the second one, if the value is nonzero, by using the following con-
8818 %?<sequence_char>?<if_string>&<else_string>?
8820 You can additionally force the result of any printf(3)-like sequence to be low-
8821 ercase by prefixing the sequence character with an underscore (_) sign. For
8822 example, if you want to display the local hostname in lowercase, you would use:
8826 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8827 replace any dots in the expansion by underscores. This might be helpful with
8828 IMAP folders that don't like dots in folder names.
8830 The Mutt Next Generation E-Mail Client 167
8832 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8838 Setting this variable causes the ``status bar'' to be displayed on the first
8839 line of the screen rather than near the bottom.
8841 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8847 With mailto: style links, a body as well as arbitrary header information may be
8848 embedded. This may lead to (user) headers being overwriten without note if
8849 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'' is unset.
8851 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8852 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8853 message including headers will be shown in the editor regardless of what
8854 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'' is set to.
8856 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8862 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8863 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8864 messages are often generated by old mailers or buggy mailers like MS Outlook
8865 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.13 , page 91).
8867 This option also replaces linear-white-space between encoded-word and *text to
8868 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8869 from being devided into multiple lines.
8871 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8877 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8878 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160)'' by mes-
8879 sage threads. By default, messages with the same subject are grouped together
8880 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8881 mailbox where you might have several unrelated messages with the subject ``hi''
8882 which will get grouped together.
8884 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8886 The Mutt Next Generation E-Mail Client 168
8892 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8893 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.320 , page 167) when replying. This is
8894 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8897 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8899 Type: regular expression
8901 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8903 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.319 , page 167) is _
\bs_
\be_
\bt, mutt-ng
8904 will remove this trailing part of the ``Subject'' line when replying if it
8905 won't be empty afterwards.
8907 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
8913 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
8914 i.e. a space will be inserted between the quote characters and the actual text.
8916 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
8922 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
8923 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
8924 mand like ``xterm -e muttng.''
8926 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
8932 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
8933 format is easier to handle for some mailing software, and generally just looks
8934 like ordinary text. To actually make use of this format's features, you'll
8935 need support in your editor.
8937 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.114 , page 115) is ignored when this
8940 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8942 The Mutt Next Generation E-Mail Client 169
8948 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
8949 tion 7.2 , page 83)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
8950 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
8951 as they appear in the folder.
8953 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
8959 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
8960 messages by subject.
8962 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bt_
\bi_
\bl_
\bd_
\be
8968 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
8971 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8977 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
8978 pressed in the main menu before timing out and checking for new mail. A value
8979 of zero or less will cause Mutt-ng to never time out.
8981 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
8987 This variable allows you to specify where Mutt-ng will place its temporary
8988 files needed for displaying and composing messages. If this variable is not
8989 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
8992 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8998 The Mutt Next Generation E-Mail Client 170
9000 Controls the character used to indicate mail addressed to you. The first char-
9001 acter is the one used when the mail is NOT addressed to your address (default:
9002 space). The second is used when you are the only recipient of the message
9003 (default: +). The third is when your address appears in the ``To:'' header
9004 field, but you are not the only recipient of the message (default: T). The
9005 fourth character is used when your address is specified in the ``Cc:'' header
9006 field, but you are not the only recipient. The fifth character is used to
9007 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
9008 when a mail was sent to a mailing-list you're subscribe to (default: L).
9010 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bt_
\br_
\ba_
\bs_
\bh
9016 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
9017 marked for deletion will be moved, instead of being irremediably purged.
9019 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
9020 that there is no way to recover mail.
9022 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
9028 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
9029 a raw socket. You may be able to use this to set up preauthenticated connec-
9030 tions to your IMAP/POP3 server. Example:
9032 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
9034 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
9035 without having to enter a password.
9037 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bu_
\bm_
\ba_
\bs_
\bk
9043 This sets the umask that will be used by Mutt-ng when creating all kinds of
9044 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
9046 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
9052 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
9053 rent thread is _
\bu_
\bncollapsed.
9055 The Mutt Next Generation E-Mail Client 171
9057 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
9063 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
9064 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
9065 with the SMTP support via libESMTP. Otherwise you may not be able to send
9068 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page
9069 150)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
9070 negotiation or tell libESMTP to do so.
9072 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
9078 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
9079 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.94 , page 110)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
9080 no addresses will be qualified.
9082 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
9088 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
9089 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
9090 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37)'' command.
9092 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
9100 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
9102 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
9105 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
9111 The Mutt Next Generation E-Mail Client 172
9113 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
9114 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
9115 mally, the default should work.
9117 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
9123 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
9126 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
9132 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-
9133 _
\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.
9135 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
9136 78)'', provided that the corresponding mailcap entry has a needsterminal flag,
9137 and the external program is interactive.
9139 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
9140 a key only if the external command returned a non-zero status.
9142 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bw_
\be_
\be_
\bd
9148 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
9149 replying to messages.
9151 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9157 Controls whether searches wrap around the end of the mailbox.
9159 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
9160 searches will not wrap.
9162 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
9168 The Mutt Next Generation E-Mail Client 173
9170 Controls the size of the margin remaining at the right side of the terminal
9171 when Mutt-ng's pager does smart wrapping.
9173 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
9179 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
9180 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
9182 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
9188 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
9189 indicate progress. If set to 0, only a single message will be displayed before
9192 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.232 , page 145)'' variable.
9194 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b6 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
9198 Default: 'M%?n?AIL&ail?'
9200 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-
9201 tion 7.4.348 , page 173) is _
\bs_
\be_
\bt. This string is identical in formatting to the
9202 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164)''.
9204 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b7 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
9210 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.348 , page 173) is _
\bs_
\be_
\bt, this string will be
9211 used to set the title when leaving mutt-ng. For terminal-based programs,
9212 there's no easy and portable way to read the current title so mutt-ng cannot
9213 read it upon startup and restore it when exiting.
9215 Based on the xterm FAQ, the following might work:
9217 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9220 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b8 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9224 The Mutt Next Generation E-Mail Client 174
9228 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9229 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9232 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b9 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9236 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9238 Controls the format of the title bar of the xterm provided that
9239 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.348 , page 173) has been _
\bs_
\be_
\bt. This string is
9240 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.314 ,
9243 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9245 The following is the list of available functions listed by the mapping in which
9246 they are available. The default key setting is given, and an explanation of
9247 what the function does. The key bindings of these functions can be changed
9248 with the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 26) command.
9250 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9252 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9253 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9254 tings for this menu will affect the default bindings for all menus (except as
9257 The Mutt Next Generation E-Mail Client 175
9259 bottom-page L move to the bottom of the page
9260 current-bottom not bound move current entry to bottom of page
9261 current-middle not bound move current entry to middle of page
9262 current-top not bound move current entry to top of page
9263 enter-command : enter a muttngrc command
9264 exit q exit this menu
9265 first-entry = move to the first entry
9266 half-down ] scroll down 1/2 page
9267 half-up [ scroll up 1/2 page
9269 jump number jump to an index number
9270 last-entry * move to the last entry
9271 middle-page M move to the middle of the page
9272 next-entry j move to the next entry
9273 next-line > scroll down one line
9274 next-page z move to the next page
9275 previous-entry k move to the previous entry
9276 previous-line < scroll up one line
9277 previous-page Z move to the previous page
9278 refresh ^L clear and redraw the screen
9279 search / search for a regular expression
9280 search-next n search for next match
9281 search-opposite not bound search for next match in opposite direction
9282 search-reverse ESC / search backwards for a regular expression
9283 select-entry RET select the current entry
9284 shell-escape ! run a program in a subshell
9285 tag-entry t toggle the tag on the current entry
9286 tag-prefix ; apply next command to tagged entries
9287 tag-prefix-cond not bound apply next function ONLY to tagged messages
9288 top-page H move to the top of the page
9289 what-key not bound display the keycode for a key press
9291 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9293 The Mutt Next Generation E-Mail Client 176
9295 bounce-message b remail a message to another user
9296 change-folder c open a different folder
9297 change-folder-readonly ESC c open a different folder in read only mode
9298 check-traditional-pgp ESC P check for classic pgp
9299 clear-flag W clear a status flag from a message
9300 copy-message C copy a message to a file/mailbox
9301 create-alias a create an alias from a message sender
9302 decode-copy ESC C decode a message and copy it to a file/mailbox
9303 decode-save ESC s decode a message and save it to a file/mailbox
9304 delete-message d delete the current entry
9305 delete-pattern D delete messages matching a pattern
9306 delete-subthread ESC d delete all messages in subthread
9307 delete-thread ^D delete all messages in thread
9308 display-address @ display full address of sender
9309 display-toggle-weed h display message and toggle header weeding
9310 display-message RET display a message
9311 edit e edit the current message
9312 edit-type ^E edit the current message's Content-Type
9313 exit x exit without saving changes
9314 extract-keys ^K extract PGP public keys
9315 fetch-mail G retrieve mail from POP server
9316 flag-message F toggle a message's 'important' flag
9317 forget-passphrase ^F wipe PGP passphrase from memory
9318 forward-message f forward a message with comments
9319 group-reply g reply to all recipients
9320 limit l show only messages matching a pattern
9321 list-reply L reply to specified mailing list
9322 mail m compose a new mail message
9323 mail-key ESC k mail a PGP public key
9324 next-new TAB jump to the next new message
9325 next-subthread ESC n jump to the next subthread
9326 next-thread ^N jump to the next thread
9327 next-undeleted j move to the next undeleted message
9328 next-unread not bound jump to the next unread message
9329 parent-message P jump to parent message in thread
9330 pipe-message | pipe message/attachment to a shell command
9331 previous-new ESC TAB jump to the previous new message
9332 previous-page Z move to the previous page
9333 previous-subthread ESC p jump to previous subthread
9334 previous-thread ^P jump to previous thread
9335 previous-undeleted k move to the last undelete message
9336 previous-unread not bound jump to the previous unread message
9337 print-message p print the current entry
9338 query Q query external program for addresses
9339 quit q save changes to mailbox and quit
9340 read-subthread ESC r mark the current subthread as read
9341 read-thread ^R mark the current thread as read
9342 recall-message R recall a postponed message
9343 reply r reply to a message
9344 resend-message ESC e resend message and preserve MIME structure
9345 save-message s save message/attachment to a file
9346 set-flag w set a status flag on a message
9347 show-version V show the Mutt-ng version number and date
9348 show-limit ESC l show currently active limit pattern, if any
9350 The Mutt Next Generation E-Mail Client 177
9352 sort-mailbox o sort messages
9353 sort-reverse O sort messages in reverse order
9354 sync-mailbox $ save changes to mailbox
9355 tag-pattern T tag messages matching a pattern
9356 tag-thread ESC t tag/untag all messages in the current thread
9357 toggle-new N toggle a message's 'new' flag
9358 toggle-write % toggle whether the mailbox will be rewritten
9359 undelete-message u undelete the current entry
9360 undelete-pattern U undelete messages matching a pattern
9361 undelete-subthread ESC u undelete all messages in subthread
9362 undelete-thread ^U undelete all messages in thread
9363 untag-pattern ^T untag messages matching a pattern
9364 view-attachments v show MIME attachments
9366 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9368 The Mutt Next Generation E-Mail Client 178
9370 bottom not bound jump to the bottom of the message
9371 bounce-message b remail a message to another user
9372 change-folder c open a different folder
9373 change-folder-readonly ESC c open a different folder in read only mode
9374 check-traditional-pgp ESC P check for classic pgp
9375 copy-message C copy a message to a file/mailbox
9376 create-alias a create an alias from a message sender
9377 decode-copy ESC C decode a message and copy it to a file/mailbox
9378 decode-save ESC s decode a message and save it to a file/mailbox
9379 delete-message d delete the current entry
9380 delete-subthread ESC d delete all messages in subthread
9381 delete-thread ^D delete all messages in thread
9382 display-address @ display full address of sender
9383 display-toggle-weed h display message and toggle header weeding
9384 edit e edit the current message
9385 edit-type ^E edit the current message's Content-Type
9386 enter-command : enter a muttngrc command
9387 exit i return to the main-menu
9388 extract-keys ^K extract PGP public keys
9389 flag-message F toggle a message's 'important' flag
9390 forget-passphrase ^F wipe PGP passphrase from memory
9391 forward-message f forward a message with comments
9392 group-reply g reply to all recipients
9393 half-up not bound move up one-half page
9394 half-down not bound move down one-half page
9396 list-reply L reply to specified mailing list
9397 mail m compose a new mail message
9398 mail-key ESC k mail a PGP public key
9399 mark-as-new N toggle a message's 'new' flag
9400 next-line RET scroll down one line
9401 next-entry J move to the next entry
9402 next-new TAB jump to the next new message
9403 next-page move to the next page
9404 next-subthread ESC n jump to the next subthread
9405 next-thread ^N jump to the next thread
9406 next-undeleted j move to the next undeleted message
9407 next-unread not bound jump to the next unread message
9408 parent-message P jump to parent message in thread
9409 pipe-message | pipe message/attachment to a shell command
9410 previous-line BackSpace scroll up one line
9411 previous-entry K move to the previous entry
9412 previous-new not bound jump to the previous new message
9413 previous-page - move to the previous page
9414 previous-subthread ESC p jump to previous subthread
9415 previous-thread ^P jump to previous thread
9416 previous-undeleted k move to the last undelete message
9417 previous-unread not bound jump to the previous unread message
9418 print-message p print the current entry
9419 quit Q save changes to mailbox and quit
9420 read-subthread ESC r mark the current subthread as read
9421 read-thread ^R mark the current thread as read
9422 recall-message R recall a postponed message
9423 redraw-screen ^L clear and redraw the screen
9425 The Mutt Next Generation E-Mail Client 179
9427 reply r reply to a message
9428 save-message s save message/attachment to a file
9429 search / search for a regular expression
9430 search-next n search for next match
9431 search-opposite not bound search for next match in opposite direction
9432 search-reverse ESC / search backwards for a regular expression
9433 search-toggle \ toggle search pattern coloring
9434 shell-escape ! invoke a command in a subshell
9435 show-version V show the Mutt-ng version number and date
9436 skip-quoted S skip beyond quoted text
9437 sync-mailbox $ save changes to mailbox
9438 tag-message t tag a message
9439 toggle-quoted T toggle display of quoted text
9440 top ^ jump to the top of the message
9441 undelete-message u undelete the current entry
9442 undelete-subthread ESC u undelete all messages in subthread
9443 undelete-thread ^U undelete all messages in thread
9444 view-attachments v show MIME attachments
9446 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9448 search / search for a regular expression
9449 search-next n search for next match
9450 search-reverse ESC / search backwards for a regular expression
9452 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9454 create-alias a create an alias from a message sender
9455 mail m compose a new mail message
9456 query Q query external program for addresses
9457 query-append A append new query results to current results
9458 search / search for a regular expression
9459 search-next n search for next match
9460 search-opposite not bound search for next match in opposite direction
9461 search-reverse ESC / search backwards for a regular expression
9463 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9465 The Mutt Next Generation E-Mail Client 180
9467 bounce-message b remail a message to another user
9468 collapse-parts v toggle display of subparts
9469 delete-entry d delete the current entry
9470 display-toggle-weed h display message and toggle header weeding
9471 edit-type ^E edit the current entry's Content-Type
9472 extract-keys ^K extract PGP public keys
9473 forward-message f forward a message with comments
9474 group-reply g reply to all recipients
9475 list-reply L reply to specified mailing list
9476 pipe-entry | pipe message/attachment to a shell command
9477 print-entry p print the current entry
9478 reply r reply to a message
9479 resend-message ESC e resend message and preserve MIME structure
9480 save-entry s save message/attachment to a file
9481 undelete-entry u undelete the current entry
9482 view-attach RET view attachment using mailcap entry if necessary
9483 view-mailcap m force viewing of attachment using mailcap
9484 view-text T view attachment as text
9486 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9488 The Mutt Next Generation E-Mail Client 181
9490 attach-file a attach a file(s) to this message
9491 attach-message A attach message(s) to this message
9492 attach-key ESC k attach a PGP public key
9493 copy-file C save message/attachment to a file
9494 detach-file D delete the current entry
9495 display-toggle-weed h display message and toggle header weeding
9496 edit-bcc b edit the BCC list
9497 edit-cc c edit the CC list
9498 edit-description d edit attachment description
9499 edit-encoding ^E edit attachment transfer-encoding
9500 edit-fcc f enter a file to save a copy of this message in
9501 edit-from ESC f edit the from: field
9502 edit-file ^X e edit the file to be attached
9503 edit-headers E edit the message with headers
9504 edit e edit the message
9505 edit-mime m edit attachment using mailcap entry
9506 edit-reply-to r edit the Reply-To field
9507 edit-subject s edit the subject of this message
9508 edit-to t edit the TO list
9509 edit-type ^T edit attachment type
9510 filter-entry F filter attachment through a shell command
9511 forget-passphrase ^F wipe PGP passphrase from memory
9512 ispell i run ispell on the message
9513 new-mime n compose new attachment using mailcap entry
9514 pgp-menu p show PGP options
9515 pipe-entry | pipe message/attachment to a shell command
9516 postpone-message P save this message to send later
9517 print-entry l print the current entry
9518 rename-file R rename/move an attached file
9519 send-message y send the message
9520 toggle-unlink u toggle whether to delete file after sending it
9521 view-attach RET view attachment using mailcap entry if necessary
9522 write-fcc w write the message to a folder
9524 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9526 delete-entry d delete the current entry
9527 undelete-entry u undelete the current entry
9529 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9531 The Mutt Next Generation E-Mail Client 182
9533 change-dir c change directories
9534 check-new TAB check mailboxes for new mail
9535 enter-mask m enter a file mask
9536 search / search for a regular expression
9537 search-next n search for next match
9538 search-reverse ESC / search backwards for a regular expression
9539 select-new N select a new file in this directory
9540 sort o sort messages
9541 sort-reverse O sort messages in reverse order
9542 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9543 view-file SPACE view file
9544 subscribe s subscribe to current mailbox (IMAP Only)
9545 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9546 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9548 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9550 view-name % view the key's user id
9551 verify-key c verify a PGP public key
9553 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9555 backspace BackSpace delete the char in front of the cursor
9556 backward-char ^B move the cursor one character to the left
9557 backward-word ESC b move the cursor to the previous word
9558 bol ^A jump to the beginning of the line
9559 buffy-cycle Space cycle among incoming mailboxes
9560 capitalize-word ESC c uppercase the first character in the word
9561 complete TAB complete filename or alias
9562 complete-query ^T complete address with query
9563 delete-char ^D delete the char under the cursor
9564 downcase-word ESC l lowercase all characters in current word
9565 eol ^E jump to the end of the line
9566 forward-char ^F move the cursor one character to the right
9567 forward-word ESC f move the cursor to the next word
9568 history-down not bound scroll down through the history list
9569 history-up not bound scroll up through the history list
9570 kill-eol ^K delete chars from cursor to end of line
9571 kill-eow ESC d delete chars from cursor to end of word
9572 kill-line ^U delete all chars on the line
9573 kill-word ^W delete the word in front of the cursor
9574 quote-char ^V quote the next typed key
9575 transpose-chars not bound transpose character under cursor with previous
9576 upcase-word ESC u uppercase all characters in current word
9578 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9580 The Mutt Next Generation E-Mail Client 183
9582 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9584 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9585 back in the ELM-ME days.
9587 The following people have been very helpful to the development of Mutt:
9589 Vikas Agnihotri <vikasa@writeme.com>,
9591 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9593 Aric Blumer <aric@fore.com>,
9595 John Capo <jc@irbs.com>,
9597 David Champion <dgc@uchicago.edu,
9599 Brendan Cully <brendan@kublai.com>,
9601 Liviu Daia <daia@stoilow.imar.ro>,
9603 Thomas E. Dickey <dickey@herndon4.his.com>,
9605 David DeSimone <fox@convex.hp.com>,
9607 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9609 Ruslan Ermilov <ru@freebsd.org>,
9611 Edmund Grimley Evans <edmundo@rano.org,
9613 Michael Finken <finken@conware.de>,
9615 Sven Guckes <guckes@math.fu-berlin.de>,
9617 Lars Hecking <lhecking@nmrc.ie>,
9619 Mark Holloman <holloman@nando.net>,
9621 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9623 Marco d'Itri <md@linux.it>,
9625 Bjrn Jacke <bjacke@suse.com>,
9627 Byrial Jensen <byrial@image.dk>,
9629 David Jeske <jeske@igcom.net>,
9631 Christophe Kalt <kalt@hugo.int-evry.fr>,
9633 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9635 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9637 The Mutt Next Generation E-Mail Client 184
9639 Brandon Long <blong@fiction.net>,
9641 Jimmy Mkel <jmy@flashback.net>,
9643 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9645 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9647 Andrew W. Nosenko <awn@bcs.zp.ua>,
9649 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9651 Clint Olsen <olsenc@ichips.intel.com>,
9653 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9655 Thomas Parmelan <tom@ankh.fr.eu.org>,
9657 Ollivier Robert <roberto@keltia.freenix.fr>,
9659 Thomas Roessler <roessler@does-not-exist.org>,
9661 Roland Rosenfeld <roland@spinnaker.de>,
9663 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9665 Allain Thivillon <Allain.Thivillon@alma.fr>,
9667 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9669 Vsevolod Volkov <vvv@lucky.net>,
9671 Ken Weinert <kenw@ihs.com>
9673 Mutt-ng is developed by the following people:
9675 Andreas Krennmair <ak@synflood.at>
9677 Nico Golde <nico@ngolde.de>
9679 Rocco Rutte <pdmef@cs.tu-berlin.de>
9681 The following people have been very helpful to the development of Mutt-ng:
9683 Christian Gall <cg@cgall.de>
9685 Iain Lea <iain@bricbrac.de>
9687 Andreas Kneib <akneib@gmx.net>
9689 Carsten Schoelzki <cjs@weisshuhn.de>
9691 Elimar Riesebieter <riesebie@lxtec.de>
9693 The Mutt Next Generation E-Mail Client 185
9695 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9697 This document was written in SGML, and then rendered using the sgml-tools pack-
9700 The Mutt Next Generation E-Mail Client 186
9704 1. Introduction .......................................................... 1
9705 1.1 Overview ........................................................ 1
9706 1.2 Mutt-ng Home Page ............................................... 1
9707 1.3 Mailing Lists ................................................... 1
9708 1.4 Software Distribution Sites ..................................... 2
9709 1.5 IRC ............................................................. 2
9710 1.6 Weblog .......................................................... 2
9711 1.7 Copyright ....................................................... 2
9713 2. Getting Started ..................................................... 2
9714 2.1 Basic Concepts .............................................. 2
9715 2.1.1 Screens and Menus 3
9716 2.1.2 Configuration 3
9719 2.1.5 Modularization 4
9721 2.2 Screens and Menus ........................................... 4
9724 2.2.3 File Browser 5
9727 2.2.6 Compose Menu 6
9729 2.2.8 Attachment Menu 6
9731 2.3 Moving Around in Menus .......................................... 6
9732 2.4 Editing Input Fields ............................................ 7
9733 2.5 Reading Mail - The Index and Pager .............................. 8
9734 2.5.1 The Message Index 8
9736 2.5.3 Threaded Mode 11
9737 2.5.4 Miscellaneous Functions 11
9738 2.6 Sending Mail ................................................... 14
9739 2.6.1 Composing new messages 14
9741 2.6.3 Editing the message header 17
9742 2.6.4 Using Mutt-ng with PGP 18
9743 2.6.5 Sending anonymous messages via mixmaster 19
9744 2.7 Forwarding and Bouncing Mail ................................... 19
9745 2.8 Postponing Mail ................................................ 20
9747 3. Configuration ........................................................ 21
9748 3.1 Locations of Configuration Files ............................... 21
9749 3.2 Basic Syntax of Initialization Files ........................... 21
9750 3.3 Variable Expansion ........................................... 23
9751 3.3.1 Commands' Output 23
9752 3.3.2 Environment Variables 23
9756 3.3.3 Configuration Variables 23
9757 3.3.4 Self-Defined Variables 23
9758 3.3.5 Type Conversions 25
9759 3.4 Defining/Using aliases ......................................... 25
9760 3.5 Changing the default key bindings .............................. 26
9761 3.6 Defining aliases for character sets ........................... 28
9762 3.7 Setting variables based upon mailbox ........................... 28
9763 3.8 Keyboard macros ................................................ 29
9764 3.9 Using color and mono video attributes .......................... 30
9765 3.10 Ignoring (weeding) unwanted message headers .................... 32
9766 3.11 Alternative addresses .......................................... 33
9767 3.12 Format = Flowed .............................................. 33
9768 3.12.1 Introduction 33
9769 3.12.2 Receiving: Display Setup 33
9771 3.12.4 Additional Notes 35
9772 3.13 Mailing lists .................................................. 35
9773 3.14 Using Multiple spool mailboxes ................................. 36
9774 3.15 Defining mailboxes which receive mail .......................... 36
9775 3.16 User defined headers ........................................... 37
9776 3.17 Defining the order of headers when viewing messages ............ 38
9777 3.18 Specify default save filename .................................. 38
9778 3.19 Specify default Fcc: mailbox when composing .................... 38
9779 3.20 Specify default save filename and default Fcc: mailbox at once . 39
9780 3.21 Change settings based upon message recipients .................. 39
9781 3.22 Change settings before formatting a message .................... 40
9782 3.23 Choosing the cryptographic key of the recipient ................ 40
9783 3.24 Adding key sequences to the keyboard buffer .................... 40
9784 3.25 Executing functions ............................................ 41
9785 3.26 Message Scoring ................................................ 41
9786 3.27 Spam detection ................................................. 42
9787 3.28 Setting variables .............................................. 44
9788 3.29 Reading initialization commands from another file .............. 45
9789 3.30 Removing hooks ................................................. 45
9790 3.31 Sharing Setups ............................................. 45
9791 3.31.1 Character Sets 45
9792 3.31.2 Modularization 46
9793 3.31.3 Conditional parts 46
9794 3.32 Obsolete Variables ............................................. 48
9796 4. Advanced Usage ....................................................... 48
9797 4.1 Regular Expressions ............................................ 48
9798 4.2 Patterns ....................................................... 51
9799 4.2.1 Complex Patterns 51
9800 4.2.2 Patterns and Dates 52
9801 4.3 Format Strings ............................................. 52
9802 4.3.1 Introduction 52
9803 4.3.2 Conditional Expansion 54
9804 4.3.3 Modifications and Padding 55
9805 4.4 Using Tags ..................................................... 55
9806 4.5 Using Hooks .................................................... 56
9807 4.5.1 Message Matching in Hooks 57
9808 4.6 Using the sidebar .............................................. 57
9812 4.7 External Address Queries ....................................... 58
9813 4.8 Mailbox Formats ................................................ 59
9814 4.9 Mailbox Shortcuts .............................................. 60
9815 4.10 Handling Mailing Lists ......................................... 60
9816 4.11 Editing threads ................................................ 61
9817 4.11.1 Linking threads 62
9818 4.11.2 Breaking threads 62
9819 4.12 Delivery Status Notification (DSN) Support ..................... 62
9820 4.13 POP3 Support (OPTIONAL) ........................................ 62
9821 4.14 IMAP Support (OPTIONAL) ........................................ 63
9822 4.14.1 The Folder Browser 64
9823 4.14.2 Authentication 64
9824 4.15 NNTP Support (OPTIONAL) ........................................ 65
9825 4.15.1 Again: Scoring 65
9826 4.16 SMTP Support (OPTIONAL) ........................................ 66
9827 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 67
9828 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 67
9829 4.19 Compressed folders Support (OPTIONAL) .......................... 67
9830 4.19.1 Open a compressed mailbox for reading 68
9831 4.19.2 Write a compressed mailbox 68
9832 4.19.3 Append a message to a compressed mailbox 69
9833 4.19.4 Encrypted folders 70
9835 5. Mutt-ng's MIME Support ............................................... 70
9836 5.1 Using MIME in Mutt ............................................. 70
9837 5.1.1 Viewing MIME messages in the pager 70
9838 5.1.2 The Attachment Menu 71
9839 5.1.3 The Compose Menu 71
9840 5.2 MIME Type configuration with mime.types ........................ 71
9841 5.3 MIME Viewer configuration with mailcap ......................... 72
9842 5.3.1 The Basics of the mailcap file 73
9843 5.3.2 Secure use of mailcap 74
9844 5.3.3 Advanced mailcap Usage 74
9845 5.3.4 Example mailcap files 77
9846 5.4 MIME Autoview .................................................. 78
9847 5.5 MIME Multipart/Alternative ..................................... 79
9848 5.6 MIME Lookup .................................................... 79
9850 6. Security Considerations ............................................ 80
9851 6.1 Passwords .................................................. 80
9852 6.2 Temporary Files ............................................ 80
9853 6.3 Information Leaks ............................................ 80
9854 6.3.1 Message-ID: headers 80
9855 6.3.2 mailto:-style links 81
9856 6.4 External applications ...................................... 81
9860 7. Reference ............................................................ 82
9861 7.1 Command line options ........................................... 82
9862 7.2 Patterns ....................................................... 83
9863 7.3 Configuration Commands ......................................... 85
9864 7.4 Configuration variables .......................................... 87
9868 7.4.1 abort_noattach 88
9869 7.4.2 abort_nosubject 89
9870 7.4.3 abort_unmodified 89
9871 7.4.4 agent_string 89
9873 7.4.6 alias_format 89
9876 7.4.9 arrow_cursor 90
9877 7.4.10 ascii_chars 91
9880 7.4.13 assumed_charset 91
9881 7.4.14 attach_format 91
9882 7.4.15 attach_remind_regexp 92
9883 7.4.16 attach_sep 93
9884 7.4.17 attach_split 93
9885 7.4.18 attribution 93
9891 7.4.24 bounce_delivered 94
9892 7.4.25 braille_friendly 94
9893 7.4.26 certificate_file 95
9896 7.4.29 collapse_unread 95
9897 7.4.30 compose_format 96
9898 7.4.31 config_charset 96
9899 7.4.32 confirmappend 96
9900 7.4.33 confirmcreate 96
9901 7.4.34 connect_timeout 96
9902 7.4.35 content_type 97
9904 7.4.37 crypt_autoencrypt 97
9905 7.4.38 crypt_autopgp 97
9906 7.4.39 crypt_autosign 98
9907 7.4.40 crypt_autosmime 98
9908 7.4.41 crypt_replyencrypt 98
9909 7.4.42 crypt_replysign 98
9910 7.4.43 crypt_replysignencrypted 98
9911 7.4.44 crypt_timestamp 99
9912 7.4.45 crypt_use_gpgme 99
9913 7.4.46 crypt_verify_sig 99
9914 7.4.47 date_format 99
9915 7.4.48 debug_level 100
9916 7.4.49 default_hook 100
9918 7.4.51 delete_space 100
9919 7.4.52 delete_untag 101
9920 7.4.53 digest_collapse 101
9924 7.4.54 display_filter 101
9925 7.4.55 dotlock_program 101
9926 7.4.56 dsn_notify 101
9927 7.4.57 dsn_return 102
9928 7.4.58 duplicate_threads 102
9929 7.4.59 edit_headers 102
9931 7.4.61 encode_from 102
9932 7.4.62 entropy_file 103
9933 7.4.63 envelope_from 103
9935 7.4.65 fast_reply 103
9936 7.4.66 fcc_attach 104
9937 7.4.67 fcc_clear 104
9938 7.4.68 file_charset 104
9940 7.4.70 folder_format 104
9941 7.4.71 followup_to 105
9942 7.4.72 force_buffy_check 106
9943 7.4.73 force_name 106
9944 7.4.74 forward_decode 106
9945 7.4.75 forward_decrypt 106
9946 7.4.76 forward_edit 106
9947 7.4.77 forward_format 107
9948 7.4.78 forward_quote 107
9950 7.4.80 gecos_mask 107
9953 7.4.83 header_cache 108
9954 7.4.84 header_cache_compress 108
9956 7.4.86 hidden_host 109
9957 7.4.87 hide_limited 109
9958 7.4.88 hide_missing 109
9959 7.4.89 hide_thread_subject 109
9960 7.4.90 hide_top_limited 110
9961 7.4.91 hide_top_missing 110
9963 7.4.93 honor_followup_to 110
9965 7.4.95 ignore_list_reply_to 110
9966 7.4.96 imap_authenticators 111
9967 7.4.97 imap_check_subscribed 111
9968 7.4.98 imap_delim_chars 111
9969 7.4.99 imap_headers 112
9970 7.4.100 imap_home_namespace 112
9971 7.4.101 imap_keepalive 112
9972 7.4.102 imap_list_subscribed 112
9973 7.4.103 imap_login 113
9974 7.4.104 imap_mail_check 113
9975 7.4.105 imap_pass 113
9976 7.4.106 imap_passive 113
9980 7.4.107 imap_peek 114
9981 7.4.108 imap_reconnect 114
9982 7.4.109 imap_servernoise 114
9983 7.4.110 imap_user 114
9984 7.4.111 implicit_autoview 114
9986 7.4.113 include_onlyfirst 115
9987 7.4.114 indent_string 115
9988 7.4.115 index_format 115
9990 7.4.117 keep_flagged 118
9991 7.4.118 list_reply 118
9993 7.4.120 mail_check 119
9994 7.4.121 mailcap_path 119
9995 7.4.122 mailcap_sanitize 119
9996 7.4.123 maildir_header_cache_verify 119
9997 7.4.124 maildir_trash 119
9998 7.4.125 mark_old 120
10001 7.4.128 max_display_recips 120
10002 7.4.129 max_line_length 120
10004 7.4.131 mbox_type 121
10005 7.4.132 menu_context 121
10006 7.4.133 menu_move_off 121
10007 7.4.134 menu_scroll 121
10008 7.4.135 message_format 122
10009 7.4.136 meta_key 122
10011 7.4.138 mh_purge 122
10012 7.4.139 mh_seq_flagged 122
10013 7.4.140 mh_seq_replied 123
10014 7.4.141 mh_seq_unseen 123
10015 7.4.142 mime_forward 123
10016 7.4.143 mime_forward_decode 123
10017 7.4.144 mime_forward_rest 123
10018 7.4.145 mix_entry_format 123
10019 7.4.146 mixmaster 124
10021 7.4.148 msgid_format 124
10022 7.4.149 narrow_tree 125
10023 7.4.150 nntp_ask_followup_to 126
10024 7.4.151 nntp_ask_x_comment_to 126
10025 7.4.152 nntp_cache_dir 126
10026 7.4.153 nntp_catchup 126
10027 7.4.154 nntp_context 126
10028 7.4.155 nntp_followup_to_poster 127
10029 7.4.156 nntp_group_index_format 127
10030 7.4.157 nntp_host 127
10031 7.4.158 nntp_inews 128
10032 7.4.159 nntp_load_description 128
10036 7.4.160 nntp_mail_check 128
10037 7.4.161 nntp_mime_subject 129
10038 7.4.162 nntp_newsrc 129
10039 7.4.163 nntp_pass 129
10040 7.4.164 nntp_post_moderated 129
10041 7.4.165 nntp_reconnect 130
10042 7.4.166 nntp_save_unsubscribed 130
10043 7.4.167 nntp_show_new_news 130
10044 7.4.168 nntp_show_only_unread 130
10045 7.4.169 nntp_user 130
10046 7.4.170 nntp_x_comment_to 131
10047 7.4.171 operating_system 131
10049 7.4.173 pager_context 131
10050 7.4.174 pager_format 132
10051 7.4.175 pager_index_lines 132
10052 7.4.176 pager_stop 132
10053 7.4.177 pgp_auto_decode 132
10054 7.4.178 pgp_autoinline 132
10055 7.4.179 pgp_check_exit 133
10056 7.4.180 pgp_clearsign_command 133
10057 7.4.181 pgp_decode_command 133
10058 7.4.182 pgp_decrypt_command 134
10059 7.4.183 pgp_encrypt_only_command 134
10060 7.4.184 pgp_encrypt_sign_command 134
10061 7.4.185 pgp_entry_format 134
10062 7.4.186 pgp_export_command 135
10063 7.4.187 pgp_getkeys_command 135
10064 7.4.188 pgp_good_sign 135
10065 7.4.189 pgp_ignore_subkeys 135
10066 7.4.190 pgp_import_command 136
10067 7.4.191 pgp_list_pubring_command 136
10068 7.4.192 pgp_list_secring_command 136
10069 7.4.193 pgp_long_ids 136
10070 7.4.194 pgp_mime_auto 136
10071 7.4.195 pgp_replyinline 137
10072 7.4.196 pgp_retainable_sigs 137
10073 7.4.197 pgp_show_unusable 137
10074 7.4.198 pgp_sign_as 137
10075 7.4.199 pgp_sign_command 138
10076 7.4.200 pgp_sort_keys 138
10077 7.4.201 pgp_strict_enc 138
10078 7.4.202 pgp_timeout 138
10079 7.4.203 pgp_use_gpg_agent 139
10080 7.4.204 pgp_verify_command 139
10081 7.4.205 pgp_verify_key_command 139
10082 7.4.206 pipe_decode 139
10083 7.4.207 pipe_sep 139
10084 7.4.208 pipe_split 139
10085 7.4.209 pop_auth_try_all 140
10086 7.4.210 pop_authenticators 140
10087 7.4.211 pop_delete 140
10088 7.4.212 pop_host 140
10092 7.4.213 pop_last 141
10093 7.4.214 pop_mail_check 141
10094 7.4.215 pop_pass 141
10095 7.4.216 pop_reconnect 141
10096 7.4.217 pop_user 142
10097 7.4.218 post_indent_string 142
10098 7.4.219 postpone 142
10099 7.4.220 postponed 142
10100 7.4.221 preconnect 142
10102 7.4.223 print_command 143
10103 7.4.224 print_decode 143
10104 7.4.225 print_split 143
10105 7.4.226 prompt_after 144
10106 7.4.227 query_command 144
10108 7.4.229 quote_empty 144
10109 7.4.230 quote_quoted 144
10110 7.4.231 quote_regexp 145
10111 7.4.232 read_inc 145
10112 7.4.233 read_only 145
10113 7.4.234 realname 145
10116 7.4.237 reply_regexp 146
10117 7.4.238 reply_self 146
10118 7.4.239 reply_to 146
10119 7.4.240 resolve 147
10120 7.4.241 reverse_alias 147
10121 7.4.242 reverse_name 147
10122 7.4.243 reverse_realname 147
10123 7.4.244 rfc2047_parameters 148
10124 7.4.245 save_address 148
10125 7.4.246 save_empty 148
10126 7.4.247 save_name 148
10128 7.4.249 score_threshold_delete 149
10129 7.4.250 score_threshold_flag 149
10130 7.4.251 score_threshold_read 149
10131 7.4.252 send_charset 149
10132 7.4.253 sendmail 150
10133 7.4.254 sendmail_wait 150
10135 7.4.256 sidebar_boundary 151
10136 7.4.257 sidebar_delim 151
10137 7.4.258 sidebar_newmail_only 151
10138 7.4.259 sidebar_number_format 151
10139 7.4.260 sidebar_shorten_hierarchy 152
10140 7.4.261 sidebar_visible 152
10141 7.4.262 sidebar_width 152
10142 7.4.263 sig_dashes 152
10143 7.4.264 sig_on_top 153
10144 7.4.265 signature 153
10148 7.4.266 signoff_string 153
10149 7.4.267 simple_search 153
10150 7.4.268 sleep_time 154
10151 7.4.269 smart_wrap 154
10152 7.4.270 smileys 154
10153 7.4.271 smime_ask_cert_label 154
10154 7.4.272 smime_ca_location 154
10155 7.4.273 smime_certificates 154
10156 7.4.274 smime_decrypt_command 155
10157 7.4.275 smime_decrypt_use_default_key 155
10158 7.4.276 smime_default_key 156
10159 7.4.277 smime_encrypt_command 156
10160 7.4.278 smime_encrypt_with 156
10161 7.4.279 smime_get_cert_command 156
10162 7.4.280 smime_get_cert_email_command 156
10163 7.4.281 smime_get_signer_cert_command 156
10164 7.4.282 smime_import_cert_command 157
10165 7.4.283 smime_is_default 157
10166 7.4.284 smime_keys 157
10167 7.4.285 smime_pk7out_command 157
10168 7.4.286 smime_sign_command 158
10169 7.4.287 smime_sign_opaque_command 158
10170 7.4.288 smime_timeout 158
10171 7.4.289 smime_verify_command 158
10172 7.4.290 smime_verify_opaque_command 158
10173 7.4.291 smtp_envelope 158
10174 7.4.292 smtp_host 159
10175 7.4.293 smtp_pass 159
10176 7.4.294 smtp_port 159
10177 7.4.295 smtp_use_tls 159
10178 7.4.296 smtp_user 160
10180 7.4.298 sort_alias 160
10181 7.4.299 sort_aux 161
10182 7.4.300 sort_browser 161
10183 7.4.301 sort_re 161
10184 7.4.302 spam_separator 162
10185 7.4.303 spoolfile 162
10186 7.4.304 ssl_ca_certificates_file 162
10187 7.4.305 ssl_client_cert 162
10188 7.4.306 ssl_force_tls 163
10189 7.4.307 ssl_min_dh_prime_bits 163
10190 7.4.308 ssl_starttls 163
10191 7.4.309 ssl_use_sslv2 163
10192 7.4.310 ssl_use_sslv3 163
10193 7.4.311 ssl_use_tlsv1 164
10194 7.4.312 ssl_usesystemcerts 164
10195 7.4.313 status_chars 164
10196 7.4.314 status_format 164
10197 7.4.315 status_on_top 167
10198 7.4.316 strict_mailto 167
10199 7.4.317 strict_mime 167
10200 7.4.318 strict_threads 167
10204 7.4.319 strip_was 167
10205 7.4.320 strip_was_regex 168
10206 7.4.321 stuff_quoted 168
10207 7.4.322 suspend 168
10208 7.4.323 text_flowed 168
10209 7.4.324 thorough_search 168
10210 7.4.325 thread_received 169
10212 7.4.327 timeout 169
10214 7.4.329 to_chars 169
10218 7.4.333 uncollapse_jump 170
10219 7.4.334 use_8bitmime 171
10220 7.4.335 use_domain 171
10221 7.4.336 use_from 171
10222 7.4.337 use_idn 171
10223 7.4.338 use_ipv6 171
10225 7.4.340 wait_key 172
10227 7.4.342 wrap_search 172
10228 7.4.343 wrapmargin 172
10229 7.4.344 write_bcc 173
10230 7.4.345 write_inc 173
10231 7.4.346 xterm_icon 173
10232 7.4.347 xterm_leave 173
10233 7.4.348 xterm_set_titles 173
10234 7.4.349 xterm_title 174
10235 7.5 Functions ....................................................... 174
10248 8. Miscellany ............................................................ 182
10249 8.1 Acknowledgments ................................................. 183
10250 8.2 About this document ............................................. 185