2 T
\bTh
\bhe
\be M
\bMu
\but
\btt
\bt N
\bNe
\bex
\bxt
\bt G
\bGe
\ben
\bne
\ber
\bra
\bat
\bti
\bio
\bon
\bn E
\bE-
\b-M
\bMa
\bai
\bil
\bl C
\bCl
\bli
\bie
\ben
\bnt
\bt
4 by Andreas Krennmair <ak@synflood.at> and others
5 originally based on _
\bm_
\bu_
\bt_
\bt by Michael Elkins <me@cs.hmc.edu> and others
9 A
\bAb
\bbs
\bst
\btr
\bra
\bac
\bct
\bt
11 Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
12 sucks less.'' - Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
14 _
\b1_
\b. _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
16 _
\b1_
\b._
\b1 _
\bO_
\bv_
\be_
\br_
\bv_
\bi_
\be_
\bw
18 M
\bMu
\but
\btt
\bt-
\b-n
\bng
\bg is a small but very powerful text-based MIME mail client. Mutt-ng is
19 highly configurable, and is well suited to the mail power user with advanced
20 features like key bindings, keyboard macros, mail threading, regular expression
21 searches and a powerful pattern matching language for selecting groups of mes-
24 This documentation additionally contains documentation to M
\bMu
\but
\btt
\bt-
\b-N
\bNG
\bG, a fork from
25 Mutt with the goal to fix all the little annoyances of Mutt, to integrate all
26 the Mutt patches that are floating around in the web, and to add other new fea-
27 tures. Features specific to Mutt-ng will be discussed in an extra section.
28 Don't be confused when most of the documentation talk about Mutt and not Mutt-
29 ng, Mutt-ng contains all Mutt features, plus many more.
31 _
\b1_
\b._
\b2 _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bH_
\bo_
\bm_
\be _
\bP_
\ba_
\bg_
\be
35 _
\b1_
\b._
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
37 +
\bo mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user support
40 The Mutt Next Generation E-Mail Client 1
42 The Mutt Next Generation E-Mail Client 2
44 +
\bo mutt-ng-devel@lists.berlios.de -- The development mailing list for mutt-ng
46 _
\b1_
\b._
\b4 _
\bS_
\bo_
\bf_
\bt_
\bw_
\ba_
\br_
\be _
\bD_
\bi_
\bs_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn _
\bS_
\bi_
\bt_
\be_
\bs
48 So far, there are no official releases of Mutt-ng, but you can download daily
49 snapshots from http://mutt-ng.berlios.de/snapshots/
51 _
\b1_
\b._
\b5 _
\bI_
\bR_
\bC
53 Visit channel _
\b#_
\bm_
\bu_
\bt_
\bt_
\bn_
\bg on irc.freenode.net (www.freenode.net) to chat with other
54 people interested in Mutt-ng.
56 _
\b1_
\b._
\b6 _
\bW_
\be_
\bb_
\bl_
\bo_
\bg
58 If you want to read fresh news about the latest development in Mutt-ng, and get
59 informed about stuff like interesting, Mutt-ng-related articles and packages
60 for your favorite distribution, you can read and/or subscribe to our Mutt-ng
63 _
\b1_
\b._
\b7 _
\bC_
\bo_
\bp_
\by_
\br_
\bi_
\bg_
\bh_
\bt
65 Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and others
67 This program is free software; you can redistribute it and/or modify it under
68 the terms of the GNU General Public License as published by the Free Software
69 Foundation; either version 2 of the License, or (at your option) any later ver-
72 This program is distributed in the hope that it will be useful, but WITHOUT ANY
73 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
74 PARTICULAR PURPOSE. See the GNU General Public License for more details.
76 You should have received a copy of the GNU General Public License along with
77 this program; if not, write to the Free Software Foundation, Inc., 59 Temple
78 Place - Suite 330, Boston, MA 02111, USA.
80 _
\b2_
\b. _
\bG_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bS_
\bt_
\ba_
\br_
\bt_
\be_
\bd
82 _
\b2_
\b._
\b1 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bC_
\bo_
\bn_
\bc_
\be_
\bp_
\bt_
\bs
84 The Mutt Next Generation E-Mail Client 3
86 _
\b2_
\b._
\b1_
\b._
\b1 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
88 mutt-ng offers different screens of which every has its special purpose:
90 +
\bo The _
\bi_
\bn_
\bd_
\be_
\bx displays the contents of the currently opened mailbox.
92 +
\bo The _
\bp_
\ba_
\bg_
\be_
\br is responsible for displaying messages, that is, the header, the
93 body and all attached parts.
95 +
\bo The _
\bf_
\bi_
\bl_
\be _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br offers operations on and displays information of all
96 folders mutt-ng should watch for mail.
98 +
\bo The _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br offers a permanent view of which mailboxes contain how many
99 total, new and/or flagged mails.
101 +
\bo The _
\bh_
\be_
\bl_
\bp _
\bs_
\bc_
\br_
\be_
\be_
\bn lists for all currently available commands how to invoke
102 them as well as a short description.
104 +
\bo The _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu is a comfortable interface take last actions before send-
105 ing mail: change subjects, attach files, remove attachements, etc.
107 +
\bo The _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\be_
\bm_
\be_
\bn_
\bt menu gives a summary and the tree structure of the
108 attachements of the current message.
110 +
\bo The _
\ba_
\bl_
\bi_
\ba_
\bs menu lists all or a fraction of the aliases a user has defined.
112 +
\bo The _
\bk_
\be_
\by menu used in connection with encryption lets users choose the
113 right key to encrypt with.
115 When mutt-ng is started without any further options, it'll open the users
116 default mailbox and display the index.
118 _
\b2_
\b._
\b1_
\b._
\b2 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
120 Mutt-ng does _
\bn_
\bo_
\bt feature an internal configuration interface or menu due to the
121 simple fact that this would be too complex to handle (currently there are sev-
122 eral _
\bh_
\bu_
\bn_
\bd_
\br_
\be_
\bd variables which fine-tune the behaviour.)
124 Mutt-ng is configured using configuration files which allow users to add com-
125 ments or manage them via version control systems to ease maintenance.
127 Also, mutt-ng comes with a shell script named grml-muttng kindly contributed by
128 users which really helps and eases the creation of a user's configuration file.
129 When downloading the source code via a snapshot or via subversion, it can be
130 found in the contrib directory.
132 _
\b2_
\b._
\b1_
\b._
\b3 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
134 Mutt-ng offers great flexibility due to the use of functions: internally, every
135 action a user can make mutt-ng perform is named ``function.'' Those functions
137 The Mutt Next Generation E-Mail Client 4
139 are assigned to keys (or even key sequences) and may be completely adjusted to
140 user's needs. The basic idea is that the impatient users get a very intuitive
141 interface to start off with and advanced users virtually get no limits to
144 _
\b2_
\b._
\b1_
\b._
\b4 _
\bI_
\bn_
\bt_
\be_
\br_
\ba_
\bc_
\bt_
\bi_
\bo_
\bn
146 Mutt-ng has two basic concepts of user interaction:
148 1. There is one dedicated line on the screen used to query the user for
149 input, issue any command, query variables and display error and informa-
150 tional messages. As for every type of user input, this requires manual
151 action leading to the need of input.
153 2. The automatized interface for interaction are the so called _
\bh_
\bo_
\bo_
\bk_
\bs. Hooks
154 specify actions the user wants to be performed at well-defined situa-
155 tions: what to do when entering which folder, what to do when displaying
156 or replying to what kind of message, etc. These are optional, i.e. a user
157 doesn't need to specify them but can do so.
159 _
\b2_
\b._
\b1_
\b._
\b5 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
161 Although mutt-ng has many functionality built-in, many features can be dele-
162 gated to external tools to increase flexibility: users can define programs to
163 filter a message through before displaying, users can use any program they want
164 for displaying a message, message types (such as PDF or PostScript) for which
165 mutt-ng doesn't have a built-in filter can be rendered by arbitrary tools and
166 so forth. Although mutt-ng has an alias mechanism built-in, it features using
167 external tools to query for nearly every type of addresses from sources like
168 LDAP, databases or just the list of locally known users.
170 _
\b2_
\b._
\b1_
\b._
\b6 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
172 Mutt-ng has a built-in pattern matching ``language'' which is as widely used as
173 possible to present a consistent interface to users. The same ``pattern terms''
174 can be used for searching, scoring, message selection and much more.
176 _
\b2_
\b._
\b2 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
178 _
\b2_
\b._
\b2_
\b._
\b1 _
\bI_
\bn_
\bd_
\be_
\bx
180 The index is the screen that you usually see first when you start mutt-ng. It
181 gives an overview over your emails in the currently opened mailbox. By default,
182 this is your system mailbox. The information you see in the index is a list of
184 The Mutt Next Generation E-Mail Client 5
186 emails, each with its number on the left, its flags (new email, important
187 email, email that has been forwarded or replied to, tagged email, ...), the
188 date when email was sent, its sender, the email size, and the subject. Addi-
189 tionally, the index also shows thread hierarchies: when you reply to an email,
190 and the other person replies back, you can see the other's person email in a
191 "sub-tree" below. This is especially useful for personal email between a group
192 of people or when you've subscribed to mailing lists.
194 _
\b2_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bg_
\be_
\br
196 The pager is responsible for showing the email content. On the top of the pager
197 you have an overview over the most important email headers like the sender, the
198 recipient, the subject, and much more information. How much information you
199 actually see depends on your configuration, which we'll describe below.
201 Below the headers, you see the email body which usually contains the message.
202 If the email contains any attachments, you will see more information about them
203 below the email body, or, if the attachments are text files, you can view them
204 directly in the pager.
206 To give the user a good overview, it is possible to configure mutt-ng to show
207 different things in the pager with different colors. Virtually everything that
208 can be described with a regular expression can be colored, e.g. URLs, email
209 addresses or smileys.
211 _
\b2_
\b._
\b2_
\b._
\b3 _
\bF_
\bi_
\bl_
\be _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
213 The file browser is the interface to the local or remote file system. When
214 selecting a mailbox to open, the browser allows custom sorting of items, limit-
215 ing the items shown by a regular expression and a freely adjustable format of
216 what to display in which way. It also allows for easy navigation through the
217 file system when selecting file(s) to attach to a message, select multiple
218 files to attach and many more.
220 _
\b2_
\b._
\b2_
\b._
\b4 _
\bS_
\bi_
\bd_
\be_
\bb_
\ba_
\br
222 The sidebar comes in handy to manage mails which are spread over different
223 folders. All folders users setup mutt-ng to watch for new mail will be listed.
224 The listing includes not only the name but also the number of total messages,
225 the number of new and flagged messages. Items with new mail may be colored dif-
226 ferent from those with flagged mail, items may be shortened or compress if
227 they're they to long to be printed in full form so that by abbreviated names,
228 user still now what the name stands for.
230 _
\b2_
\b._
\b2_
\b._
\b5 _
\bH_
\be_
\bl_
\bp
232 The Mutt Next Generation E-Mail Client 6
234 The help screen is meant to offer a quick help to the user. It lists the cur-
235 rent configuration of key bindings and their associated commands including a
236 short description, and currently unbound functions that still need to be asso-
237 ciated with a key binding (or alternatively, they can be called via the mutt-ng
240 _
\b2_
\b._
\b2_
\b._
\b6 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
242 The compose menu features a split screen containing the information which
243 really matter before actually sending a message by mail or posting an article
244 to a newsgroup: who gets the message as what (recipient, newsgroup, who gets
245 what kind of copy). Additionally, users may set security options like deciding
246 whether to sign, encrypt or sign and encrypt a message with/for what keys.
248 Also, it's used to attach messages, news articles or files to a message, to re-
249 edit any attachment including the message itself.
251 _
\b2_
\b._
\b2_
\b._
\b7 _
\bA_
\bl_
\bi_
\ba_
\bs _
\bM_
\be_
\bn_
\bu
253 The alias menu is used to help users finding the recipients of messages. For
254 users who need to contact many people, there's no need to remember addresses or
255 names completely because it allows for searching, too. The alias mechanism and
256 thus the alias menu also features grouping several addresses by a shorter nick-
257 name, the actual alias, so that users don't have to select each single recipi-
260 _
\b2_
\b._
\b2_
\b._
\b8 _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
262 As will be later discussed in detail, mutt-ng features a good and stable MIME
263 implementation, that is, is greatly supports sending and receiving messages of
264 arbitrary type. The attachment menu displays a message's structure in detail:
265 what content parts are attached to which parent part (which gives a true tree
266 structure), which type is of what type and what size. Single parts may saved,
267 deleted or modified to offer great and easy access to message's internals.
269 _
\b2_
\b._
\b2_
\b._
\b9 _
\bK_
\be_
\by _
\bM_
\be_
\bn_
\bu
273 _
\b2_
\b._
\b3 _
\bM_
\bo_
\bv_
\bi_
\bn_
\bg _
\bA_
\br_
\bo_
\bu_
\bn_
\bd _
\bi_
\bn _
\bM_
\be_
\bn_
\bu_
\bs
275 Information is presented in menus, very similar to ELM. Here is a table
277 The Mutt Next Generation E-Mail Client 7
279 showing the common keys used to navigate menus in Mutt-ng.
281 j or Down next-entry move to the next entry
282 k or Up previous-entry move to the previous entry
283 z or PageDn page-down go to the next page
284 Z or PageUp page-up go to the previous page
285 = or Home first-entry jump to the first entry
286 * or End last-entry jump to the last entry
287 q quit exit the current menu
288 ? help list all key bindings for the current menu
290 _
\b2_
\b._
\b4 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bI_
\bn_
\bp_
\bu_
\bt _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
292 Mutt-ng has a builtin line editor which is used as the primary way to input
293 textual data such as email addresses or filenames. The keys used to move
294 around while editing are very similar to those of Emacs.
296 ^A or <Home> bol move to the start of the line
297 ^B or <Left> backward-char move back one char
298 Esc B backward-word move back one word
299 ^D or <Delete> delete-char delete the char under the cursor
300 ^E or <End> eol move to the end of the line
301 ^F or <Right> forward-char move forward one char
302 Esc F forward-word move forward one word
303 <Tab> complete complete filename or alias
304 ^T complete-query complete address with query
305 ^K kill-eol delete to the end of the line
306 ESC d kill-eow delete to the end of the word
307 ^W kill-word kill the word in front of the cursor
308 ^U kill-line delete entire line
309 ^V quote-char quote the next typed key
310 <Up> history-up recall previous string from history
311 <Down> history-down recall next string from history
312 <BackSpace> backspace kill the char in front of the cursor
313 Esc u upcase-word convert word to upper case
314 Esc l downcase-word convert word to lower case
315 Esc c capitalize-word capitalize the word
317 <Return> n/a finish editing
319 You can remap the _
\be_
\bd_
\bi_
\bt_
\bo_
\br functions using the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 27) com-
320 mand. For example, to make the _
\bD_
\be_
\bl_
\be_
\bt_
\be key delete the character in front of the
321 cursor rather than under, you could use
323 bind editor <delete> backspace
325 The Mutt Next Generation E-Mail Client 8
327 _
\b2_
\b._
\b5 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl _
\b- _
\bT_
\bh_
\be _
\bI_
\bn_
\bd_
\be_
\bx _
\ba_
\bn_
\bd _
\bP_
\ba_
\bg_
\be_
\br
329 Similar to many other mail clients, there are two modes in which mail is read
330 in Mutt-ng. The first is the index of messages in the mailbox, which is called
331 the ``index'' in Mutt-ng. The second mode is the display of the message con-
332 tents. This is called the ``pager.''
334 The next few sections describe the functions provided in each of these modes.
336 _
\b2_
\b._
\b5_
\b._
\b1 _
\bT_
\bh_
\be _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bI_
\bn_
\bd_
\be_
\bx
338 c change to a different mailbox
339 ESC c change to a folder in read-only mode
340 C copy the current message to another mailbox
341 ESC C decode a message and copy it to a folder
342 ESC s decode a message and save it to a folder
343 D delete messages matching a pattern
344 d delete the current message
346 l show messages matching a pattern
347 N mark message as new
348 o change the current sort method
349 O reverse sort the mailbox
350 q save changes and exit
352 T tag messages matching a pattern
353 t toggle the tag on a message
354 ESC t toggle tag on entire message thread
355 U undelete messages matching a pattern
358 x abort changes and exit
359 <Return> display-message
360 <Tab> jump to the next new message
361 @ show the author's full e-mail address
362 $ save changes to mailbox
365 ^L clear and redraw the screen
366 ^T untag messages matching a pattern
368 _
\b2_
\b._
\b5_
\b._
\b1_
\b._
\b1 _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs _
\bF_
\bl_
\ba_
\bg_
\bs
370 In addition to who sent the message and the subject, a short summary of the
371 disposition of each message is printed beside the message number. Zero or more
372 of the following ``flags'' may appear, which mean:
375 message is deleted (is marked for deletion)
378 message have attachments marked for deletion
380 The Mutt Next Generation E-Mail Client 9
383 contains a PGP public key
392 message is PGP encrypted
395 message has been replied to
398 message is signed, and the signature is succesfully verified
409 Some of the status flags can be turned on or off using
411 +
\bo s
\bse
\bet
\bt-
\b-f
\bfl
\bla
\bag
\bg (default: w)
413 +
\bo c
\bcl
\ble
\bea
\bar
\br-
\b-f
\bfl
\bla
\bag
\bg (default: W)
415 Furthermore, the following flags reflect who the message is addressed to. They
416 can be customized with the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.339 , page 172) 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 31) 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 79) 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.307 , page 163) by _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs, there are
501 a few additional functions available in the _
\bi_
\bn_
\bd_
\be_
\bx and _
\bp_
\ba_
\bg_
\be_
\br modes.
503 ^D delete-thread delete all messages in the current thread
504 ^U undelete-thread undelete all messages in the current thread
505 ^N next-thread jump to the start of the next thread
506 ^P previous-thread jump to the start of the previous thread
507 ^R read-thread mark the current thread as read
508 ESC d delete-subthread delete all messages in the current subthread
509 ESC u undelete-subthread undelete all messages in the current subthread
510 ESC n next-subthread jump to the start of the next subthread
511 ESC p previous-subthread jump to the start of the previous subthread
512 ESC r read-subthread mark the current subthread as read
513 ESC t tag-thread toggle the tag on the current thread
514 ESC v collapse-thread toggle collapse for the current thread
515 ESC V collapse-all toggle collapse for all threads
516 P parent-message jump to parent message in thread
518 N
\bNo
\bot
\bte
\be:
\b: Collapsing a thread displays only the first message in the thread and
519 hides the others. This is useful when threads contain so many messages that you
520 can only see a handful of threads on the screen. See %M in _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
521 tion 7.4.116 , page 116). For example, you could use "%?M?(#%03M)&(%4l)?" in
522 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116) 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.328 , page 170).
527 _
\b2_
\b._
\b5_
\b._
\b4 _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\be_
\bo_
\bu_
\bs _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
529 c
\bcr
\bre
\bea
\bat
\bte
\be-
\b-a
\bal
\bli
\bia
\bas
\bs
532 Creates a new alias based upon the current message (or prompts for a new one).
533 Once editing is complete, an _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 26) command is added to
534 the file specified by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 90) 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 90) 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 33) commands.
560 This command (available in the ``index'' and ``pager'') allows you to edit the
561 raw current message as it's present in the mail folder. After you have fin-
562 ished editing, the changed message will be appended to the current folder, and
563 the original message will be marked for deletion.
565 e
\bed
\bdi
\bit
\bt-
\b-t
\bty
\byp
\bpe
\be
567 (default: ^E on the attachment menu, and in the pager and index menus; ^T on
570 This command is used to temporarily edit an attachment's content type to fix,
571 for instance, bogus character set parameters. When invoked from the index or
572 from the pager, you'll have the opportunity to edit the top-level attachment's
573 content type. On the _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bm_
\be_
\bn_
\bu (section 5.1.2 , page 71), you can
574 change any attachment's content type. These changes are not persistent, and get
575 lost upon changing folders.
577 Note that this command is also available on the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bm_
\be_
\bn_
\bu (section 5.1.3 ,
578 page 72). 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 30) to change settings on the fly.
588 e
\bex
\bxt
\btr
\bra
\bac
\bct
\bt-
\b-k
\bke
\bey
\bys
\bs
591 This command extracts PGP public keys from the current or tagged message(s) and
592 adds them to your PGP public key ring.
594 f
\bfo
\bor
\brg
\bge
\bet
\bt-
\b-p
\bpa
\bas
\bss
\bsp
\bph
\bhr
\bra
\bas
\bse
\be
597 This command wipes the passphrase(s) from memory. It is useful, if you mis-
598 spelled the passphrase.
600 The Mutt Next Generation E-Mail Client 13
602 l
\bli
\bis
\bst
\bt-
\b-r
\bre
\bep
\bpl
\bly
\by
605 Reply to the current or tagged message(s) by extracting any addresses which
606 match the regular expressions given by the _
\bl_
\bi_
\bs_
\bt_
\bs _
\bo_
\br _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 ,
607 page 36) commands, but also honor any Mail-Followup-To header(s) if the
608 _
\b$_
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.94 , page 111) 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.216 , page 142), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.218 , page 142), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.217 , page 142) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.350 , page 174) 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.351 , page 175) 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.350 , page 174) 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.241 , page 147) 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.324 , page 167) 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 103).
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.208 , page 140) 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.195 , page 137)) have obvious meanings. But some explana-
894 tions on the capabilities, flags, and validity fields are in order.
896 The flags sequence (%f) will expand to one of the following flags:
898 R The key has been revoked and can't be used.
899 X The key is expired and can't be used.
900 d You have marked the key as disabled.
901 c There are unknown critical self-signature
904 The capabilities field (%c) expands to a two-character sequence representing a
905 key's capabilities. The first character gives the key's encryption capabili-
906 ties: A minus sign (-
\b-) means that the key cannot be used for encryption. A dot
907 (.
\b.) means that it's marked as a signature key in one of the user IDs, but may
909 The Mutt Next Generation E-Mail Client 19
911 also be used for encryption. The letter e
\be indicates that this key can be used
914 The second character indicates the key's signing capabilities. Once again, a
915 ``-
\b-'' implies ``not for signing'', ``.
\b.'' implies that the key is marked as an
916 encryption key in one of the user-ids, and ``s
\bs'' denotes a key which can be
919 Finally, the validity field (%t) indicates how well-certified a user-id is. A
920 question mark (?
\b?) indicates undefined validity, a minus character (-
\b-) marks an
921 untrusted association, a space character means a partially trusted association,
922 and a plus character (+
\b+) indicates complete validity.
924 _
\b2_
\b._
\b6_
\b._
\b5 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bo_
\bn_
\by_
\bm_
\bo_
\bu_
\bs _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs _
\bv_
\bi_
\ba _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
926 You may also have configured mutt to co-operate with Mixmaster, an anonymous
927 remailer. Mixmaster permits you to send your messages anonymously using a
928 chain of remailers. Mixmaster support in mutt is for mixmaster version 2.04
929 (beta 45 appears to be the latest) and 2.03. It does not support earlier ver-
930 sions or the later so-called version 3 betas, of which the latest appears to be
933 To use it, you'll have to obey certain restrictions. Most important, you can-
934 not use the Cc and Bcc headers. To tell Mutt-ng to use mixmaster, you have to
935 select a remailer chain, using the mix function on the compose menu.
937 The chain selection screen is divided into two parts. In the (larger) upper
938 part, you get a list of remailers you may use. In the lower part, you see the
939 currently selected chain of remailers.
941 You can navigate in the chain using the chain-prev and chain-next functions,
942 which are by default bound to the left and right arrows and to the h and l keys
943 (think vi keyboard bindings). To insert a remailer at the current chain posi-
944 tion, use the insert function. To append a remailer behind the current chain
945 position, use select-entry or append. You can also delete entries from the
946 chain, using the corresponding function. Finally, to abandon your changes,
947 leave the menu, or accept them pressing (by default) the Return key.
949 Note that different remailers do have different capabilities, indicated in the
950 %c entry of the remailer menu lines (see _
\b$_
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.146 ,
951 page 125)). 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.230 , page 145) 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.229 , page 145) 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 83) 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 86) 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 86). 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 86).
1108 The Mutt Next Generation E-Mail Client 23
1110 _
\b3_
\b._
\b3 _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn _
\bw_
\bi_
\bt_
\bh_
\bi_
\bn _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1112 Besides just assign static content to variables, there's plenty of ways of
1113 adding external and more or less dynamic content.
1115 _
\b3_
\b._
\b3_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs_
\b' _
\bO_
\bu_
\bt_
\bp_
\bu_
\bt
1117 It is possible to substitute the output of a Unix command in an initialization
1118 file. This is accomplished by enclosing the command in backquotes (``) as in,
1121 my_hdr X-Operating-System: `uname -a`
1123 The output of the Unix command ``uname -a'' will be substituted before the line
1124 is parsed. Note that since initialization files are line oriented, only the
1125 first line of output from the Unix command will be substituted.
1127 _
\b3_
\b._
\b3_
\b._
\b2 _
\bE_
\bn_
\bv_
\bi_
\br_
\bo_
\bn_
\bm_
\be_
\bn_
\bt _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1129 UNIX environments can be accessed like the way it is done in shells like sh and
1130 bash: Prepend the name of the environment by a ``$'' sign. For example,
1132 set record=+sent_on_$HOSTNAME
1134 sets the _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.246 , page 148) variable to the string _
\b+_
\bs_
\be_
\bn_
\bt_
\b__
\bo_
\bn_
\b_
1135 and appends the value of the evironment variable $HOSTNAME.
1137 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if an environment variable is not defined. The
1138 result will of the expansion will then be empty.
1140 _
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1142 As for environment variables, the values of all configuration variables as
1143 string can be used in the same way, too. For example,
1145 set imap_home_namespace = $folder
1147 would set the value of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.101 , page 113) to
1148 the value to which _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 105) is _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by set to.
1150 N
\bNo
\bot
\bte
\be:
\b: There're no logical links established in such cases so that the the value
1151 for _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.101 , page 113) won't change even if
1152 _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 105) gets changed.
1154 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if a configuration variable is not defined or is
1155 empty. The result will of the expansion will then be empty.
1157 The Mutt Next Generation E-Mail Client 24
1159 _
\b3_
\b._
\b3_
\b._
\b4 _
\bS_
\be_
\bl_
\bf_
\b-_
\bD_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1161 Mutt-ng flexibly allows users to define their own variables. To avoid conflicts
1162 with the standard set and to prevent misleading error messages, there's a
1163 reserved namespace for them: all user-defined variables must be prefixed with
1164 user_ and can be used just like any ordinary configuration or environment vari-
1167 For example, to view the manual, users can either define two macros like the
1170 macro generic <F1> "!less -r /path/to/manual" "Show manual"
1171 macro pager <F1> "!less -r /path/to/manual" "Show manual"
1173 for generic, pager and index. The alternative is to define a custom variable
1176 set user_manualcmd = "!less -r /path/to_manual"
1177 macro generic <F1> "$user_manualcmd<enter>" "Show manual"
1178 macro pager <F1> "$user_manualcmd<enter>" "Show manual"
1179 macro index <F1> "$user_manualcmd<enter>" "Show manual"
1181 to re-use the command sequence as in:
1183 macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns"
1185 Using this feature, arbitrary sequences can be defined once and recalled and
1186 reused where necessary. More advanced scenarios could include to save a vari-
1187 able's value at the beginning of macro sequence and restore it at end.
1189 When the variable is first defined, the first value it gets assigned is also
1190 the initial value to which it can be reset using the reset command.
1192 The complete removal is done via the unset keyword.
1194 After the following sequence:
1199 the variable $user_foo has a current value of 666 and an initial of 42. The
1204 The Mutt Next Generation E-Mail Client 25
1206 will show 666. After doing the reset via
1210 a following query will give 42 as the result. After unsetting it via
1214 any query or operation (except the noted expansion within other statements)
1215 will lead to an error message.
1217 _
\b3_
\b._
\b3_
\b._
\b5 _
\bP_
\br_
\be_
\b-_
\bD_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1219 In order to allow users to share one setup over a number of different machines
1220 without having to change its contents, there's a number of pre-defined vari-
1221 ables. These are prefixed with muttng_ and are read-only, i.e. they cannot be
1222 set, unset or reset. The reference chapter lists all available variables.
1224 _
\bP_
\bl_
\be_
\ba_
\bs_
\be _
\bc_
\bo_
\bn_
\bs_
\bu_
\bl_
\bt _
\bt_
\bh_
\be _
\bl_
\bo_
\bc_
\ba_
\bl _
\bc_
\bo_
\bp_
\by _
\bo_
\bf _
\by_
\bo_
\bu_
\br _
\bm_
\ba_
\bn_
\bu_
\ba_
\bl _
\bf_
\bo_
\br _
\bt_
\bh_
\be_
\bi_
\br _
\bv_
\ba_
\bl_
\bu_
\be_
\bs _
\ba_
\bs _
\bt_
\bh_
\be_
\by _
\bm_
\ba_
\by _
\bd_
\bi_
\bf_
\b-
1225 _
\bf_
\be_
\br _
\bf_
\br_
\bo_
\bm _
\bd_
\bi_
\bf_
\bf_
\be_
\br_
\be_
\bn_
\bt _
\bm_
\ba_
\bn_
\bu_
\ba_
\bl _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bs_
\b. Where the manual is installed in can be
1226 queried (already using such a variable) by running:
1228 muttng -Q muttng_docdir
1230 To extend the example for viewing the manual via self-defined variables, it can
1231 be made more readable and more portable by changing the real path in:
1233 set user_manualcmd = '!less -r /path/to_manual'
1237 set user_manualcmd = "!less -r $muttng_docdir/manual.txt"
1239 which works everywhere if a manual is installed.
1241 Please note that by the type of quoting, muttng determines when to expand these
1242 values: when it finds double quotes, the value will be expanded during reading
1243 the setup files but when it finds single quotes, it'll expand it at runtime as
1246 For example, the statement
1248 folder-hook . "set user_current_folder = $muttng_folder_name"
1250 The Mutt Next Generation E-Mail Client 26
1252 will be already be translated to the following when reading the startup files:
1254 folder-hook . "set user_current_folder = some_folder"
1256 with some_folder being the name of the first folder muttng opens. On the con-
1259 folder-hook . 'set user_current_folder = $muttng_folder_name'
1261 will be executed at runtime because of the single quotes so that user_cur-
1262 rent_folder will always have the value of the currently opened folder.
1264 A more practical example is:
1266 folder-hook . 'source ~/.mutt/score-$muttng_folder_name'
1268 which can be used to source files containing score commands depending on the
1269 folder the user enters.
1271 _
\b3_
\b._
\b3_
\b._
\b6 _
\bT_
\by_
\bp_
\be _
\bC_
\bo_
\bn_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn_
\bs
1273 A note about variable's types during conversion: internally values are stored
1274 in internal types but for any dump/query or set operation they're converted to
1275 and from string. That means that there's no need to worry about types when ref-
1276 erencing any variable. As an example, the following can be used without harm
1277 (besides makeing muttng very likely behave strange):
1280 set folder = $read_inc
1281 set read_inc = $folder
1282 set user_magic_number = 42
1283 set folder = $user_magic_number
1285 _
\b3_
\b._
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1287 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1289 It's usually very cumbersome to remember or type out the address of someone you
1290 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1291 short string to a full address.
1293 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1294 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1296 To remove an alias or aliases (``*'' means all aliases):
1298 The Mutt Next Generation E-Mail Client 27
1300 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1302 alias muttdude me@cs.hmc.edu (Michael Elkins)
1303 alias theguys manny, moe, jack
1305 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1306 cial file. The alias command can appear anywhere in a configuration file, as
1307 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.29 , page 46). Consequently, you can
1308 have multiple alias files, or you can have all aliases defined in your muttrc.
1310 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
1311 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 90)
1312 variable (which is ~/.muttrc by default). This file is not special either, in
1313 the sense that Mutt-ng will happily append aliases to any file, but in order
1314 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1315 3.29 , page 46) this file too.
1319 source /usr/local/share/Mutt-ng.aliases
1320 source ~/.mail_aliases
1321 set alias_file=~/.mail_aliases
1323 To use aliases, you merely use the alias at any place in mutt where mutt
1324 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1325 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
1326 (section 7.4.59 , page 103) variable set.
1328 In addition, at the various address prompts, you can use the tab character to
1329 expand a partial alias to the full alias. If there are multiple matches, mutt
1330 will bring up a menu with the matching aliases. In order to be presented with
1331 the full list of aliases, you must hit tab with out a partial alias, such as at
1332 the beginning of the prompt or after a comma denoting multiple addresses.
1334 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1335 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1338 _
\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
1340 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1342 This command allows you to change the default key bindings (operation invoked
1343 when pressing a key).
1345 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be speci-
1346 fied by separating them with commas (no additional whitespace is allowed). The
1347 currently defined maps are:
1349 The Mutt Next Generation E-Mail Client 28
1352 This is not a real menu, but is used as a fallback for all of the
1353 other menus except for the pager and editor modes. If a key is not
1354 defined in another menu, Mutt-ng will look for a binding to use in
1355 this menu. This allows you to bind a key to a certain function in
1356 multiple menus instead of having multiple bind statements to accom-
1357 plish the same task.
1360 The alias menu is the list of your personal aliases as defined in
1361 your muttrc. It is the mapping from a short alias name to the full
1362 email address(es) of the recipient(s).
1365 The attachment menu is used to access the attachments on received
1369 The browser is used for both browsing the local directory struc-
1370 ture, and for listing all of your incoming mailboxes.
1373 The editor is the line-based editor the user enters text data.
1376 The index is the list of messages contained in a mailbox.
1379 The compose menu is the screen used when sending a new message.
1382 The pager is the mode used to display message/attachment data, and
1386 The pgp menu is used to select the OpenPGP keys used for encrypting
1390 The postpone menu is similar to the index menu, except is used when
1391 recalling a message the user was composing, but saved until later.
1393 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1394 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1395 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1396 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
1397 alternative form is to specify the key as a three digit octal number prefixed
1398 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1400 In addition, _
\bk_
\be_
\by may consist of:
1402 The Mutt Next Generation E-Mail Client 29
1406 <backtab> backtab / shift-tab
1416 <pagedown> Page Down
1417 <backspace> Backspace
1426 <f10> function key 10
1428 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1430 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1431 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 177). The special
1432 function noop unbinds the specified key sequence.
1434 _
\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
1436 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1438 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1440 The charset-hook command defines an alias for a character set. This is useful
1441 to properly display messages which are tagged with a character set name not
1444 The iconv-hook command defines a system-specific name for a character set.
1445 This is helpful when your systems character conversion library insists on using
1446 strange, system-specific names for character sets.
1448 _
\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
1450 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1452 It is often desirable to change settings based on which mailbox you are
1454 The Mutt Next Generation E-Mail Client 30
1456 reading. The folder-hook command provides a method by which you can execute
1457 any configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1458 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1459 folder-hook's, they are executed in the order given in the muttrc.
1461 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.313 , page
1462 165) at the beginning of the pattern, you must place it inside of double or
1463 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1466 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1467 ple, a command action to perform is to change the sorting method based upon the
1470 folder-hook mutt set sort=threads
1472 However, the sorting method is not restored to its previous value when reading
1473 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1475 folder-hook . set sort=date-sent
1477 _
\b3_
\b._
\b8 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1479 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 ]
1481 Macros are useful when you would like a single key to perform a series of
1482 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1483 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1484 create a macro to execute those commands with a single key.
1486 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.5 , page 28) which the macro will be bound. Multi-
1487 ple maps may be specified by separating multiple menu arguments by commas.
1488 Whitespace may not be used in between the menu arguments and the commas sepa-
1491 _
\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
1492 3.5 , page 27). There are some additions however. The first is that control
1493 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1494 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1495 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
1496 _
\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
1497 3.5 , page 27). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1500 The advantage with using function names directly is that the macros will work
1501 regardless of the current key bindings, so they are not dependent on the user
1502 having particular key definitions. This makes them more robust and portable,
1503 and also facilitates defining of macros in files used by more than one user
1505 The Mutt Next Generation E-Mail Client 31
1507 (eg. the system Muttngrc).
1509 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1512 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1513 truncated at the screen width, and are not wrapped.
1515 _
\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
1517 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 ]
1519 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
1521 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1523 If your terminal supports color, you can spice up Mutt-ng by creating your own
1524 color scheme. To define the color of an object (type of information), you must
1525 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1526 only specify one or the other).
1528 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1532 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1534 +
\bo bold (highlighting bold patterns in the body of messages)
1536 +
\bo error (error messages printed by Mutt-ng)
1538 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1540 +
\bo hdrdefault (default color of the message header in the pager)
1542 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1544 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1546 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1548 +
\bo message (informational messages)
1552 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.241 , page 147) in the
1555 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1557 +
\bo search (highlighting of words in the pager)
1559 The Mutt Next Generation E-Mail Client 32
1563 +
\bo status (mode lines used to display info about the mailbox or message)
1565 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1567 +
\bo tree (thread tree drawn in the message index and attachment menu)
1569 +
\bo underline (highlighting underlined patterns in the body of messages)
1571 _
\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:
1593 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the fore-
1594 ground color boldfaced (e.g., brightred).
1596 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1597 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1598 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-
1599 ment variable to the default colors of your terminal for this to work; for
1600 example (for Bourne-like shells):
1602 set COLORFGBG="green;black"
1605 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
1606 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1608 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1609 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1610 command for it to be removed. The pattern ``*'' is a special token which means
1611 to clear the color index list of all entries.
1613 The Mutt Next Generation E-Mail Client 33
1615 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
1616 number of colors supported by your terminal). This is useful when you remap
1617 the colors for your display (for example by changing the color associated with
1618 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1620 If your terminal does not support color, it is still possible change the video
1621 attributes through the use of the ``mono'' command:
1623 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 ]
1625 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1627 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1629 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1641 _
\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
1643 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1645 Messages often have many header fields added by automatic processing systems,
1646 or which may not seem useful to display on the screen. This command allows you
1647 to specify header fields which you don't normally want to see.
1649 You do not need to specify the full header field name. For example, ``ignore
1650 content-'' will ignore all header fields that begin with the pattern ``con-
1651 tent-''. ``ignore *'' will ignore all headers.
1653 To remove a previously added token from the list, use the ``unignore'' command.
1654 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1655 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1658 ``unignore *'' will remove all tokens from the ignore list.
1662 # Sven's draconian header weeding
1664 unignore from date subject to cc
1665 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1668 The Mutt Next Generation E-Mail Client 34
1670 _
\b3_
\b._
\b1_
\b1 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1672 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1674 With various functions, mutt will treat messages differently, depending on
1675 whether you sent them or whether you received them from someone else. For
1676 instance, when replying to a message that you sent to a different party, mutt
1677 will automatically suggest to send the response to the original message's
1678 recipients -- responding to yourself won't make much sense in many cases. (See
1679 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.249 , page 149).)
1681 Many users receive e-mail under a number of different addresses. To fully use
1682 mutt's features here, the program must be able to recognize what e-mail
1683 addresses you receive mail under. That's the purpose of the alternates command:
1684 It takes a list of regular expressions, each of which can identify an address
1685 under which you receive e-mail.
1687 The unalternates command can be used to write exceptions to alternates pat-
1688 terns. If an address matches something in an alternates command, but you none-
1689 theless do not think it is from you, you can list a more precise pattern under
1690 an unalternates command.
1692 To remove a regular expression from the alternates list, use the unalternates
1693 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1694 command matches an entry on the unalternates list, that unalternates entry will
1695 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
1698 _
\b3_
\b._
\b1_
\b2 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1700 _
\b3_
\b._
\b1_
\b2_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
1702 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1703 ning of email, each message had a fixed line width, and it was enough for dis-
1704 playing them on fixed-size terminals. But times changed, and nowadays hardly
1705 anybody still uses fixed-size terminals: more people nowaydays use graphical
1706 user interfaces, with dynamically resizable windows. This led to the demand of
1707 a new email format that makes it possible for the email client to make the
1708 email look nice in a resizable window without breaking quoting levels and cre-
1709 ating an incompatible email format that can also be displayed nicely on old
1710 fixed-size terminals.
1712 For introductory information on format=flowed messages, see
1713 <http://www.joeclark.org/ffaq.html>.
1715 _
\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
1717 When you receive emails that are marked as format=flowed messages, and is for-
1718 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1719 your terminal. If you want a fixed margin on the right side of your terminal,
1720 you can set the following:
1722 The Mutt Next Generation E-Mail Client 35
1726 The code above makes the line break 10 columns before the right side of the
1729 If your terminal is so wide that the lines are embarrassingly long, you can
1730 also set a maximum line length:
1732 set max_line_length = 120
1734 The example above will give you lines not longer than 120 characters.
1736 When you view at format=flowed messages, you will often see the quoting hierar-
1737 chy like in the following example:
1739 >Bill, can you please send last month's progress report to Mr.
1740 >Morgan? We also urgently need the cost estimation for the new
1741 >production server that we want to set up before our customer's
1742 >project will go live.
1744 This obviously doesn't look very nice, and it makes it very hard to differenti-
1745 ate between text and quoting character. The solution is to configure mutt-ng to
1746 "stuff" the quoting:
1750 This will lead to a nicer result that is easier to read:
1752 > Bill, can you please send last month's progress report to Mr.
1753 > Morgan? We also urgently need the cost estimation for the new
1754 > production server that we want to set up before our customer's
1755 > project will go live.
1757 _
\b3_
\b._
\b1_
\b2_
\b._
\b3 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg
1759 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1764 The Mutt Next Generation E-Mail Client 36
1766 Additionally, you have to use an editor which supports writing format=flowed-
1767 conforming emails. For vim, this is done by adding w to the formatoptions (see
1768 :h formatoptions and :h fo-table) when writing emails.
1770 Also note that _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\b=_
\bf_
\bl_
\bo_
\bw_
\be_
\bd knows about ``space-stuffing'', that is, when
1771 sending messages, some kinds of lines have to be indented with a single space
1772 on the sending side. On the receiving side, the first space (if any) is
1773 removed. As a consequence and in addition to the above simple setting, please
1774 keep this in mind when making manual formattings within the editor. Also note
1775 that mutt-ng currently violates the standard (RfC 3676) as it does not space-
1776 stuff lines starting with:
1778 +
\bo > This is _
\bn_
\bo_
\bt the quote character but a right angle used for other reasons
1780 +
\bo From with a trailing space.
1782 +
\bo just a space for formatting reasons
1784 Please make sure that you manually prepend a space to each of them.
1786 _
\b3_
\b._
\b1_
\b2_
\b._
\b4 _
\bA_
\bd_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bN_
\bo_
\bt_
\be_
\bs
1790 For completeness, the _
\b$_
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.51 , page 101) variable pro-
1791 vides the mechanism to generate a DelSp=yes parameter on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages.
1792 According to the standard, clients receiving a format=flowed messages should
1793 delete the last space of a flowed line but still interpret the line as flowed.
1794 Because flowed lines usually contain only one space at the end, this parameter
1795 would make the receiving client concatenate the last word of the previous with
1796 the first of the current line _
\bw_
\bi_
\bt_
\bh_
\bo_
\bu_
\bt a space. This makes ordinary text unread-
1797 able and is intended for languages rarely using spaces. So please use this set-
1798 ting only if you're sure what you're doing.
1800 _
\b3_
\b._
\b1_
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1802 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1804 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1806 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 ,
1807 page 61). In order to take advantage of them, you must specify which addresses
1808 belong to mailing lists, and which mailing lists you are subscribed to. Once
1809 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1810 work for all known lists. Additionally, when you send a message to a sub-
1811 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1812 user agents not to send copies of replies to your personal address. Note that
1813 the Mail-Followup-To header is a non-standard extension which is not supported
1814 by all mail user agents. Adding it is not bullet-proof against receiving per-
1815 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1816 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.72 , page 106)
1817 configuration variable.
1819 The Mutt Next Generation E-Mail Client 37
1821 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1822 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1823 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1826 You can use regular expressions with both commands. To mark all messages sent
1827 to a specific bug report's address on mutt's bug tracking system as list mail,
1828 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1829 sufficient to just give a portion of the list's e-mail address.
1831 Specify as much of the address as you need to to remove ambiguity. For exam-
1832 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1833 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
1834 list, you could add ``lists mutt-users'' to your initialization file. To tell
1835 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1836 tialization file instead. If you also happen to get mail from someone whose
1837 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-
1838 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1839 from the actual list.
1841 The ``unlists'' command is used to remove a token from the list of known and
1842 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1844 To remove a mailing list from the list of subscribed mailing lists, but keep it
1845 on the list of known mailing lists, use ``unsubscribe''.
1847 _
\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
1849 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1851 This command is used to move read messages from a specified mailbox to a dif-
1852 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1853 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1854 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1856 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1857 (it is not possible to save read mail in more than a single mailbox).
1859 _
\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
1861 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1863 This command specifies folders which can receive mail and which will be checked
1864 for new messages. By default, the main menu status bar displays how many of
1865 these folders have new messages.
1867 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1869 Pressing TAB in the directory browser will bring up a menu showing the files
1870 specified by the mailboxes command, and indicate which contain new messages.
1872 The Mutt Next Generation E-Mail Client 38
1874 Mutt-ng will automatically enter this mode when invoked from the command line
1877 The ``unmailboxes'' command is used to remove a token from the list of folders
1878 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1880 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1881 access time. Utilities like biff or frm or any other program which accesses
1882 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1883 they do not properly reset the access time. Backup tools are another common
1884 reason for updated access times.
1886 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1887 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
1888 61) (such as ``='' and ``!''), any variable definition that affect these char-
1889 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 105) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1890 7.4.313 , page 165)) should be executed before the mailboxes command.
1892 _
\b3_
\b._
\b1_
\b6 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1896 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1898 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1900 The ``my_hdr'' command allows you to create your own header fields which will
1901 be added to every message you send.
1903 For example, if you would like to add an ``Organization:'' header field to all
1904 of your outgoing messages, you can put the command
1906 my_hdr Organization: A Really Big Company, Anytown, USA
1910 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1911 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1912 there, so Mutt-ng enforces the rule.
1914 If you would like to add a header field to a single message, you should either
1915 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1916 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1917 header of your message along with the body.
1919 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1920 specify an asterisk (``*'') to remove all header fields, or the fields to
1921 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1924 The Mutt Next Generation E-Mail Client 39
1928 _
\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
1930 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1932 With this command, you can specify an order in which mutt will attempt to
1933 present headers to you when viewing messages.
1935 ``unhdr_order *'' will clear all previous headers from the order list, thus
1936 removing the header order effects set by the system-wide startup file.
1938 hdr_order From Date: From: To: Cc: Subject:
1940 _
\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
1942 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1944 This command is used to override the default filename used when saving mes-
1945 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:
1946 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1947 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1949 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 58) for information on the
1950 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1954 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1955 save-hook aol\\.com$ +spam
1957 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 40) command.
1959 _
\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
1961 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1963 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1964 (section 7.4.246 , page 148). Mutt-ng searches the initial list of message
1965 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1966 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1967 7.4.246 , page 148) mailbox.
1969 The Mutt Next Generation E-Mail Client 40
1971 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 58) for information on the
1972 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1974 Example: fcc-hook [@.]aol\\.com$ +spammers
1976 The above will save a copy of all messages going to the aol.com domain to the
1977 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 ,
1980 _
\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
1982 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1984 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1985 3.19 , page 39) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 39) with its arguments.
1987 _
\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
1989 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1991 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1993 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1995 These commands can be used to execute arbitrary configuration commands based
1996 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1997 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
2000 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
2001 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
2002 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
2003 the order specified in the users's configuration file.
2005 send2-hook is matched every time a message is changed, either by editing it, or
2006 by using the compose menu to change its recipients or subject. send2-hook is
2007 executed after send-hook, and can, e.g., be used to set parameters such as the
2008 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.263 , page 152) variable depending on the message's
2011 For each type of send-hook or reply-hook, when multiple matches occur, commands
2012 are executed in the order they are specified in the muttrc (for that type of
2015 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 58) for information on the
2016 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
2018 Example: send-hook mutt 'set mime_forward signature='''
2020 Another typical use for this command is to change the values of the
2022 The Mutt Next Generation E-Mail Client 41
2024 _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 94), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.275 , page
2025 155) and _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.120 , page 120) variables in order to change the
2026 language of the attributions and signatures based upon the recipients.
2028 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
2029 recipients. Adding a recipient after replying or editing the message will NOT
2030 cause any send-hook to be executed. Also note that my_hdr commands which mod-
2031 ify recipient headers, or the message's subject, don't have any effect on the
2032 current message when executed from a send-hook.
2034 _
\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
2036 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
2038 This command can be used to execute arbitrary configuration commands before
2039 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
2040 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
2041 tiple matches occur, commands are executed in the order they are specified in
2044 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 58) for information on the
2045 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
2049 message-hook ~A 'set pager=builtin'
2050 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
2052 _
\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
2054 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
2056 When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
2057 tain key with a given e-mail address automatically, either because the recipi-
2058 ent's public key can't be deduced from the destination address, or because, for
2059 some reasons, you need to override the key Mutt-ng would normally use. The
2060 crypt-hook command provides a method by which you can specify the ID of the
2061 public key to be used when encrypting messages to a certain recipient.
2063 The meaning of "key id" is to be taken broadly in this context: You can either
2064 put a numerical key ID here, an e-mail address, or even just a real name.
2066 _
\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
2068 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
2070 This command adds the named string to the keyboard buffer. The string may
2072 The Mutt Next Generation E-Mail Client 42
2074 contain control characters, key names and function names like the sequence
2075 string in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 30) command. You may use it to auto-
2076 matically run a sequence of commands at startup, or when entering certain fold-
2079 _
\b3_
\b._
\b2_
\b5 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
2081 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
2083 This command can be used to execute any function. Functions are listed in the
2084 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 177). ``exec function'' is equivalent
2085 to ``push <function>''.
2087 _
\b3_
\b._
\b2_
\b6 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
2089 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
2091 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
2093 In situations where you have to cope with a lot of emails, e.g. when you read
2094 many different mailing lists, and take part in discussions, it is always useful
2095 to have the important messages marked and the annoying messages or the ones
2096 that you aren't interested in deleted. For this purpose, mutt-ng features a
2097 mechanism called ``scoring''.
2099 When you use scoring, every message has a base score of 0. You can then use the
2100 score command to define patterns and a positive or negative value associated
2101 with it. When a pattern matches a message, the message's score will be raised
2102 or lowered by the amount of the value associated with the pattern.
2104 score "~f nion@muttng\.org" 50
2105 score "~f @sco\.com" -100
2107 If the pattern matches, it is also possible to set the score value of the cur-
2108 rent message to a certain value and then stop evaluation:
2110 score "~f santaclaus@northpole\.int" =666
2112 What is important to note is that negative score values will be rounded up to
2115 To make scoring actually useful, the score must be applied in some way. That's
2116 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:
2118 +
\bo flag threshold: when a message has a score value equal or higher than the
2119 flag threshold, it will be flagged.
2121 The Mutt Next Generation E-Mail Client 43
2123 +
\bo read threshold: when a message has a score value equal or lower than the
2124 read threshold, it will be marked as read.
2126 +
\bo delete threshold: when a message has a score value equal or lower than the
2127 delete threshold, it will be marked as deleted.
2129 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-
2130 tion 7.4.260 , page 152), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.261 , page 152),
2131 _
\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.259 , page 152) and. By default,
2132 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.261 , page 152) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
2133 (section 7.4.259 , page 152) are set to -1, which means that in the default
2134 threshold configuration no message will ever get marked as read or deleted.
2136 Scoring gets especially interesting when combined with the color command and
2139 color index black yellow "~n 10-"
2140 color index red yellow "~n 100-"
2142 The rules above mark all messages with a score between 10 and 99 with black and
2143 yellow, and messages with a score greater or equal 100 with red and yellow.
2144 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
2145 but it is more flexible, as it visually marks different scores.
2147 _
\b3_
\b._
\b2_
\b7 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
2149 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2151 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
2153 Mutt-ng has generalized support for external spam-scoring filters. By defining
2154 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
2155 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
2156 filter. You also can display the spam attributes in your index display using
2157 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116) variable.
2158 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
2161 Your first step is to define your external filter's spam patterns using the
2162 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
2163 mail message. If any message in the mailbox matches this regular expression, it
2164 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
2165 nospam pattern -- see below.) The appearance of this attribute is entirely up
2166 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,
2167 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
2168 expression ``back-reference'' refers to a sub-expression contained within
2169 parentheses.) %1 is replaced with the first back-reference in the regex, %2
2170 with the second, etc.
2172 If you're using multiple spam filters, a message can have more than one spam-
2174 The Mutt Next Generation E-Mail Client 44
2176 related header. You can define spam patterns for each filter you use. If a mes-
2177 sage matches two or more of these patterns, and the $spam_separator variable is
2178 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2179 strings joined together, with the value of $spam_separator separating them.
2181 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
2182 these spam settings:
2184 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
2185 spam "X-Spam-Status: Yes" "90+/SA"
2186 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
2187 set spam_separator=", "
2189 If I then received a message that DCC registered with ``many'' hits under the
2190 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
2191 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
2192 characters before ``=many'' in a DCC report indicate the checksum used -- in
2193 this case, ``Fuz2''.)
2195 If the $spam_separator variable is unset, then each spam pattern match super-
2196 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
2197 only the last one to match.
2199 The spam tag is what will be displayed in the index when you use %H in the
2200 $index_format variable. It's also the string that the ~H pattern-matching
2201 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2202 ing by spam attribute will use as a sort key.
2204 That's a pretty complicated example, and most people's actual environments will
2205 have only one spam filter. The simpler your configuration, the more effective
2206 mutt can be, especially when it comes to sorting.
2208 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2209 ordering strings alphnumerically. However, if a spam tag begins with a number,
2210 mutt will sort numerically first, and lexically only when two numbers are equal
2211 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2212 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2213 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2214 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2215 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2216 coerce your filter to give you a raw number. But in case you can't, mutt can
2217 still do something useful.
2219 The nospam command can be used to write exceptions to spam patterns. If a
2220 header pattern matches something in a spam command, but you nonetheless do not
2221 want it to receive a spam tag, you can list a more precise pattern under a
2224 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-
2225 ing spam list entry, the effect will be to remove the entry from the spam list,
2226 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2227 matches an entry on the nospam list, that nospam entry will be removed. If the
2228 _
\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
2230 The Mutt Next Generation E-Mail Client 45
2232 might be the default action if you use spam and nospam in conjunction with a
2235 You can have as many spam or nospam commands as you like. You can even do your
2236 own primitive spam detection within mutt -- for example, if you consider all
2237 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2239 spam "^From: .*MAILER-DAEMON" "999"
2241 _
\b3_
\b._
\b2_
\b8 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2243 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 ... ]
2245 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2247 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2249 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2251 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 ,
2252 page 88). There are four basic types of variables: boolean, number, string and
2253 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
2254 variables can be assigned a positive integer value.
2256 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2257 be enclosed in quotes if they contain spaces or tabs. You may also use the
2258 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2260 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2261 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2262 action to be carried out automatically as if you had answered yes to the ques-
2263 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2264 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2265 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2267 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2269 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2270 toggle the value (on or off). This is useful when writing macros. Example:
2273 The toggle command automatically prepends the inv prefix to all specified vari-
2276 The unset command automatically prepends the no prefix to all specified vari-
2279 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2280 a variable by prefixing the name of the variable with a question mark:
2282 The Mutt Next Generation E-Mail Client 46
2286 The question mark is actually only required for boolean and quadoption vari-
2289 The reset command resets all given variables to the compile time defaults
2290 (hopefully mentioned in this manual). If you use the command set and prefix the
2291 variable with ``&'' this has the same behavior as the reset command.
2293 With the reset command there exists the special variable ``all'', which allows
2294 you to reset all variables to their system defaults.
2296 _
\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
2298 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2300 This command allows the inclusion of initialization commands from other files.
2301 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2302 ~/.muttrc readable and keep my aliases private.
2304 If the filename begins with a tilde (``~''), it will be expanded to the path of
2305 your home directory.
2307 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2308 an executable program from which to read input (eg. source ~/bin/myscript|).
2310 _
\b3_
\b._
\b3_
\b0 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2312 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2314 This command permits you to flush hooks you have previously defined. You can
2315 either remove all hooks by giving the ``*'' character as an argument, or you
2316 can remove all hooks of a specific type by saying something like unhook send-
2319 _
\b3_
\b._
\b3_
\b1 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2321 _
\b3_
\b._
\b3_
\b1_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2323 As users may run mutt-ng on different systems, the configuration must be main-
2324 tained because it's likely that people want to use the setup everywhere they
2325 use mutt-ng. And mutt-ng tries to help where it can.
2327 To not produce conflicts with different character sets, mutt-ng allows users to
2328 specify in which character set their configuration files are encoded. Please
2329 note that while reading the configuration files, this is only respected after
2330 the corresponding declaration appears. It's advised to put the following at the
2332 The Mutt Next Generation E-Mail Client 47
2334 very beginning of a users muttngrc:
2336 set config_charset = "..."
2338 and replacing the dots with the actual character set. To avoid problems while
2339 maintaining the setup, vim user's may want to use modelines as show in:
2341 # vim:fileencoding=...:
2343 while, again, replacing the dots with the appropriate name. This tells vim as
2344 which character set to read and save the file.
2346 _
\b3_
\b._
\b3_
\b1_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2348 ``Modularization'' means to divide the setup into several files while sorting
2349 the options or commands by topic. Especially for longer setups (e.g. with many
2350 hooks), this helps maintaining it and solving trouble.
2352 When using separation, setups may be, as a whole or in fractions, shared over
2355 _
\b3_
\b._
\b3_
\b1_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2357 When using a configuration on different systems, the user may not always have
2358 influence on how mutt-ng is installed and which features it includes.
2360 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2361 for mutt. Its basic syntax is:
2363 ifdef <item> <command>
2364 ifndef <item> <command>
2366 ...whereby <item> can be one of:
2368 +
\bo a function name
2370 +
\bo a variable name
2376 All available functions, variables and menus are documented elsewhere in this
2377 manual but ``features'' is specific to these two commands. To test for one,
2379 The Mutt Next Generation E-Mail Client 48
2381 prefix one of the following keywords with feature_:
2383 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2384 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2385 classic_smime, gpgme, header_cache
2387 As an example, one can use the following in ~/.muttngrc:
2389 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2390 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2391 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2393 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2394 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2395 ng/setup-nntp if NNTP support is built in.
2397 An example for testing for variable names can be used if users use different
2398 revisions of mutt-ng whereby the older one may not have a certain variable. To
2399 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.105 , page 114),
2402 ifdef imap_mail_check 'set imap_mail_check = 300'
2404 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
2405 (section 7.4.185 , page 134) only if the pager menu is available, use:
2407 ifdef pager 'set pager_index_lines = 10'
2409 For completeness, too, the opposite of ifdef is provided: ifndef which only
2410 executes the command if the test fails. For example, the following two examples
2413 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2414 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2418 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2419 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2421 The Mutt Next Generation E-Mail Client 49
2423 _
\b3_
\b._
\b3_
\b2 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2425 In the process of ensuring and creating more consistency, many variables have
2426 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2427 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 88) for a complete list.
2429 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2431 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2433 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2434 tion 7.2 , page 84) must be specified using regular expressions (regexp) in
2435 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2436 and GNU awk). For your convenience, we have included below a brief description
2439 The search is case sensitive if the pattern contains at least one upper case
2440 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2441 for a regular expression in an initialization command: ``\\''.
2443 A regular expression is a pattern that describes a set of strings. Regular
2444 expressions are constructed analogously to arithmetic expressions, by using
2445 various operators to combine smaller expressions.
2447 Note that the regular expression can be enclosed/delimited by either ' or '
2448 which is useful if the regular expression includes a white-space character.
2449 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-
2450 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2451 ace it with \ (backslash).
2453 The fundamental building blocks are the regular expressions that match a single
2454 character. Most characters, including all letters and digits, are regular
2455 expressions that match themselves. Any metacharacter with special meaning may
2456 be quoted by preceding it with a backslash.
2458 The period ``.'' matches any single character. The caret ``^'' and the dollar
2459 sign ``$'' are metacharacters that respectively match the empty string at the
2460 beginning and end of a line.
2462 A list of characters enclosed by ``['' and ``]'' matches any single character
2463 in that list; if the first character of the list is a caret ``^'' then it
2464 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2465 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2466 specified by giving the first and last characters, separated by a hyphen ``-''.
2467 Most metacharacters lose their special meaning inside lists. To include a lit-
2468 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2469 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2472 The Mutt Next Generation E-Mail Client 50
2474 Certain named classes of characters are predefined. Character classes consist
2475 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2476 defined by the POSIX standard:
2479 Alphanumeric characters.
2482 Alphabetic characters.
2485 Space or tab characters.
2494 Characters that are both printable and visible. (A space is print-
2495 able, but not visible, while an ``a'' is both.)
2498 Lower-case alphabetic characters.
2501 Printable characters (characters that are not control characters.)
2504 Punctuation characters (characters that are not letter, digits,
2505 control characters, or space characters).
2508 Space characters (such as space, tab and formfeed, to name a few).
2511 Upper-case alphabetic characters.
2514 Characters that are hexadecimal digits.
2516 A character class is only valid in a regular expression inside the brackets of
2517 a character list. Note that the brackets in these class names are part of the
2518 symbolic names, and must be included in addition to the brackets delimiting the
2519 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].
2521 Two additional special sequences can appear in character lists. These apply to
2522 non-ASCII character sets, which can have single symbols (called collating ele-
2523 ments) that are represented with more than one character, as well as several
2524 characters that are equivalent for collating or sorting purposes:
2527 A collating symbol is a multi-character collating element enclosed
2529 The Mutt Next Generation E-Mail Client 51
2531 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2532 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2533 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2536 An equivalence class is a locale-specific name for a list of char-
2537 acters that are equivalent. The name is enclosed in ``[='' and
2538 ``=]''. For example, the name ``e'' might be used to represent all
2539 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2540 matches any of ``'', ``'' and ``e''.
2542 A regular expression matching a single character may be followed by one of sev-
2543 eral repetition operators:
2546 The preceding item is optional and matched at most once.
2549 The preceding item will be matched zero or more times.
2552 The preceding item will be matched one or more times.
2555 The preceding item is matched exactly _
\bn times.
2558 The preceding item is matched _
\bn or more times.
2561 The preceding item is matched at most _
\bm times.
2564 The preceding item is matched at least _
\bn times, but no more than _
\bm
2567 Two regular expressions may be concatenated; the resulting regular expression
2568 matches any string formed by concatenating two substrings that respectively
2569 match the concatenated subexpressions.
2571 Two regular expressions may be joined by the infix operator ``|''; the result-
2572 ing regular expression matches any string matching either subexpression.
2574 Repetition takes precedence over concatenation, which in turn takes precedence
2575 over alternation. A whole subexpression may be enclosed in parentheses to
2576 override these precedence rules.
2578 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2579 may also be used in regular expressions:
2582 Matches the empty string at either the beginning or the end of a
2585 The Mutt Next Generation E-Mail Client 52
2588 Matches the empty string within a word.
2591 Matches the empty string at the beginning of a word.
2594 Matches the empty string at the end of a word.
2597 Matches any word-constituent character (letter, digit, or under-
2601 Matches any character that is not word-constituent.
2604 Matches the empty string at the beginning of a buffer (string).
2607 Matches the empty string at the end of a buffer.
2609 Please note however that these operators are not defined by POSIX, so they may
2610 or may not be available in stock libraries on various systems.
2612 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2614 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2615 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2616 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2617 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2618 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 84) in the Reference chapter.
2620 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2621 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2624 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2626 It is possible to combine several sub-patterns to a more complex pattern. The
2627 most simple possibility is to logically AND several patterns by stringing them
2632 The pattern above matches all messages that contain ``SPAM'' in the subject and
2635 To logical OR patterns, simply use the | operator. This one especially useful
2636 when using local groups:
2638 The Mutt Next Generation E-Mail Client 53
2640 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2641 (~b mutt-ng|~s Mutt-ng)
2644 The first pattern matches all messages that were sent by one of the mutt-ng
2645 maintainers, while the seconds pattern matches all messages that contain
2646 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2647 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2648 ences: header, i.e. messages that are not an (indirect) reply to one of my
2649 messages. A pattern can be logicall negated using the ! operator.
2651 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2653 When using dates in patterns, the dates must be specified in a special format,
2654 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2655 rent month or year. When using date ranges, and you specify only the minimum or
2656 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2657 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2659 It is also possible to use so-called ``error margins'' when specifying date
2660 ranges. You simply specify a date, and then the error margin. This margin
2661 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2662 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2663 months, w for weeks and d for days. If you use the special * sign, it means
2664 that the error margin goes to both ``directions'' in time.
2670 The first pattern matches all dates between January 1st, 2005 and January 1st
2671 2006. The second pattern matches all dates between October 18th, 2004 and
2672 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2673 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2675 Relative dates are also very important, as they make it possible to specify
2676 date ranges between a fixed number of units and the current date. How this
2677 works can be seen in the following example:
2679 ~d >2w # messages older than two weeks
2680 ~d <3d # messages newer than 3 days
2681 ~d =1m # messages that are exactly one month old
2683 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2685 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2687 The Mutt Next Generation E-Mail Client 54
2689 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2690 In short, they describe what items to print out how in menus and status mes-
2693 Basically, they work as this: for different menus and bars, there's a variable
2694 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2696 For example, when running mutt-ng on different machines or different versions
2697 for testing purposes, it may be interesting to have the following information
2698 always printed on screen when one is in the index:
2700 +
\bo the current hostname
2702 +
\bo the current mutt-ng version number
2704 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-
2705 _
\bm_
\ba_
\bt (section 7.4.324 , page 167) variable. For the hostname and version
2706 string, there's an expando for $status_format: %h expands to the hostname and
2707 %v to the version string. When just configuring:
2709 set status_format = "%v on %h: ..."
2711 mutt-ng will replace the sequence %v with the version string and %h with the
2712 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2713 mailhost, you'll see the following when you're in the index:
2715 Mutt-ng 1.5.9i on mailhost: ...
2717 In the index, there're more useful information one could want to see:
2719 +
\bo which mailbox is open
2721 +
\bo how man new, flagged or postponed messages
2725 To include the mailbox' name is as easy as:
2727 set status_format = "%v on %h: %B: ...
2729 When the currently opened mailbox is Inbox, this will be expanded to:
2731 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2733 For the number of certain types of messages, one more feature of the format
2734 strings is extremely useful. If there aren't messages of a certain type, it may
2736 The Mutt Next Generation E-Mail Client 55
2738 not be desired to print just that there aren't any but instead only print some-
2739 thing if there are any.
2741 _
\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
2743 To only print the number of messages if there are new messages in the current
2744 mailbox, further extend $status_format to:
2746 set status_format = "%v on %h: %B %?n?%n new? ...
2748 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
2749 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2750 ated if the value of the expando is different from zero. The basic syntax is:
2752 %?<item>?<string if nonzero>?
2754 which tells mutt-ng to only look at <string if nonzero> if the value of the
2755 %<item%gt; expando is different from zero. In our example, we used n as the
2756 expando to check for and %n new as the optional nonzero string.
2758 But this is not all: this feature only offers one alternative: ``print some-
2759 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2760 complete version: ``if zero, print something and else print something else.''
2761 This is achieved by the following syntax for those expandos which may be
2764 %?<item>?<string if nonzero>&<string if zero>?
2766 Using this we can make mutt-ng to do the following:
2768 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2771 +
\bo and make it print ``no new messages'' if there aren't any
2773 The corresponding configuration is:
2775 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2777 This doubles the use of the ``new messages'' string because it'll get always
2778 printed. Thus, it can be shortened to:
2780 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2782 The Mutt Next Generation E-Mail Client 56
2784 As you might see from this rather simple example, one can create very complex
2785 but fancy status messages. Please see the reference chapter for expandos and
2786 those which may be printed nonzero.
2788 _
\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
2790 Besides the information given so far, there're even more features of format
2793 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2794 characters in the expansion of <item> to lowercase.
2796 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2797 dots in the expansion of <item> to underscores (_).
2799 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2803 When this occurs, mutt-ng will fill the rest of the line with the
2804 character X. In our example, filling the rest of the line with
2805 dashes is done by setting:
2807 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2810 Since the previous expando stops at the end of line, there must be
2811 a way to fill the gap between two items via the %>X expando: it
2812 puts as many characters X in between two items so that the rest of
2813 the line will be right-justified. For example, to not put the ver-
2814 sion string and hostname of our example on the left but on the
2815 right and fill the gap with spaces, one might use (note the space
2818 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2820 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2822 Sometimes it is desirable to perform an operation on a group of messages all at
2823 once rather than one at a time. An example might be to save messages to a
2824 mailing list to a separate folder, or to delete all messages with a given sub-
2825 ject. To tag all messages matching a pattern, use the tag-pattern function,
2826 which is bound to ``shift-T'' by default. Or you can select individual mes-
2827 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2829 The Mutt Next Generation E-Mail Client 57
2831 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 84) for Mutt-ng's pattern matching
2834 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2835 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2836 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2837 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.19 ,
2838 page 94) variable is set, the next operation applies to the tagged messages
2839 automatically, without requiring the ``tag-prefix''.
2841 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 30) or _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 41) commands,
2842 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2843 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2844 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2845 this operator the rest of the macro will be executed as normal.
2847 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2849 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2850 arbitrary commands before performing some operation. For example, you may wish
2851 to tailor your configuration based upon which mailbox you are reading, or to
2852 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
2853 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 49) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 84) along
2854 with a configuration option/command. See
2856 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 29)
2858 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 40)
2860 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 41)
2862 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 39)
2864 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37)
2866 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 39)
2868 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 40)
2870 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2872 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2873 until the end of the current mutt session. As this is generally not desired, a
2874 default hook needs to be added before all other hooks to restore configuration
2875 defaults. Here is an example with send-hook and the my_hdr directive:
2877 send-hook . 'unmy_hdr From:'
2878 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2880 The Mutt Next Generation E-Mail Client 58
2882 _
\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
2884 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2885 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2886 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 49) is sufficient. But in dealing with
2887 messages a finer grain of control is needed for matching since for different
2888 purposes you want to match different criteria.
2890 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 84) language
2891 for matching messages in hook commands. This works in exactly the same way as
2892 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
2893 to those operators which match information mutt extracts from the header of the
2894 message (i.e. from, to, cc, date, subject, etc.).
2896 For example, if you wanted to set your return address based upon sending mail
2897 to a specific address, you could do something like:
2899 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2901 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2903 However, it is not required that you write the pattern to match using the full
2904 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
2905 other hooks, in which case Mutt-ng will translate your pattern into the full
2906 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2907 7.4.49 , page 101) variable. The pattern is translated at the time the hook
2908 is declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.49 , page 101) that is
2909 in effect at that time will be used.
2911 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2913 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2914 which looks very similar to the ones you probably know from GUI mail clients.
2915 The sidebar lists all specified mailboxes, shows the number in each and high-
2916 lights the ones with new email Use the following configuration commands:
2918 set sidebar_visible="yes"
2919 set sidebar_width=25
2921 If you want to specify the mailboxes you can do so with:
2929 You can also specify the colors for mailboxes with new mails by using:
2931 The Mutt Next Generation E-Mail Client 59
2933 color sidebar_new red black
2934 color sidebar white black
2936 The available functions are:
2938 sidebar-scroll-up Scrolls the mailbox list up 1 page
2939 sidebar-scroll-down Scrolls the mailbox list down 1 page
2940 sidebar-next Highlights the next mailbox
2941 sidebar-next-new Highlights the next mailbox with new mail
2942 sidebar-previous Highlights the previous mailbox
2943 sidebar-open Opens the currently highlighted mailbox
2945 Reasonable key bindings look e.g. like this:
2947 bind index \Cp sidebar-prev
2948 bind index \Cn sidebar-next
2949 bind index \Cb sidebar-open
2950 bind pager \Cp sidebar-prev
2951 bind pager \Cn sidebar-next
2952 bind pager \Cb sidebar-open
2954 macro index B ':toggle sidebar_visible^M'
2955 macro pager B ':toggle sidebar_visible^M'
2957 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2958 off the sidebar simply by pressing 'B'.
2960 _
\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
2962 Mutt-ng supports connecting to external directory databases such as LDAP,
2963 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2964 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.237 , page 146) vari-
2965 able, you specify the wrapper command to use. For example:
2967 set query_command = "mutt_ldap_query.pl '%s'"
2969 The wrapper script should accept the query on the command-line. It should
2970 return a one line message, then each matching response on a single line, each
2971 line containing a tab separated address then name then some other optional
2972 information. On error, or if there are no matching addresses, return a non-
2973 zero exit code and a one line error message.
2975 An example multiple response output:
2977 Searching database ... 20 entries ... 3 matching:
2978 me@cs.hmc.edu Michael Elkins mutt dude
2979 blong@fiction.net Brandon Long mutt and more
2981 The Mutt Next Generation E-Mail Client 60
2983 roessler@guug.de Thomas Roessler mutt pgp
2985 There are two mechanisms for accessing the query function of mutt. One is to
2986 do a query from the index menu using the query function (default: Q). This
2987 will prompt for a query, then bring up the query menu which will list the
2988 matching responses. From the query menu, you can select addresses to create
2989 aliases, or to mail. You can tag multiple addresses to mail, start a new
2990 query, or have a new query appended to the current responses.
2992 The other mechanism for accessing the query function is for address completion,
2993 similar to the alias completion. In any prompt for address entry, you can use
2994 the complete-query function (default: ^T) to run a query based on the current
2995 address you have typed. Like aliases, mutt will look for what you have typed
2996 back to the last space or comma. If there is a single response for that query,
2997 mutt will expand the address in place. If there are multiple responses, mutt
2998 will activate the query menu. At the query menu, you can select one or more
2999 addresses to be added to the prompt.
3001 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
3003 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
3004 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
3005 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
3006 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.132 , page 122)
3009 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
3010 stored in a single file. Each message has a line of the form:
3012 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
3014 to denote the start of a new message (this is often referred to as the
3017 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
3018 lines containing ``^A^A^A^A'' (four control-A's).
3020 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
3021 and each message is stored in a separate file. The filename indicates the mes-
3022 sage number (however, this is may not correspond to the message number Mutt-ng
3023 displays). Deleted messages are renamed with a comma (,) prepended to the file-
3024 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
3025 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
3028 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
3029 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
3030 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
3031 way they are unique, even when two programs are writing the mailbox over NFS,
3033 The Mutt Next Generation E-Mail Client 61
3035 which means that no file locking is needed.
3037 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
3039 There are a number of built in shortcuts which refer to specific mailboxes.
3040 These shortcuts can be used anywhere you are prompted for a file or mailbox
3043 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.313 , page 165) (incoming)
3046 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.131 , page 122) file
3048 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.246 , page 148) file
3050 +
\bo ^ -- refers to the current mailbox
3052 +
\bo - or !! -- refers to the file you've last visited
3054 +
\bo ~ -- refers to your home directory
3056 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 105) directory
3058 +
\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 39) as
3059 determined by the address of the alias
3061 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
3063 Mutt-ng has a few configuration options that make dealing with large amounts of
3064 mail easier. The first thing you must do is to let Mutt know what addresses
3065 you consider to be mailing lists (technically this does not have to be a mail-
3066 ing list, but that is what it is most often used for), and what lists you are
3067 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
3068 (section 3.13 , page 36) commands in your muttrc.
3070 Now that Mutt-ng knows what your mailing lists are, it can do several things,
3071 the first of which is the ability to show the name of a list through which you
3072 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
3073 This is useful to distinguish between personal and list mail in the same mail-
3074 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116) variable, the escape
3075 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
3076 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
3077 returns the name of the author).
3079 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
3080 quite large. Most people do not bother to remove the author of the message they
3081 are reply to from the list, resulting in two or more copies being sent to that
3082 person. The ``list-reply'' function, which by default is bound to ``L'' in the
3083 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
3084 mailing list addresses instead of all recipients (except as specified by Mail-
3086 The Mutt Next Generation E-Mail Client 62
3088 Followup-To, see below).
3090 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
3091 a list of recipients which includes one or several subscribed mailing lists,
3092 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.72 , page 106) option is set, mutt will
3093 generate a Mail-Followup-To header which contains all the recipients to whom
3094 you send this message, but not your address. This indicates that group-replies
3095 or list-replies (also known as ``followups'') to this message should only be
3096 sent to the original recipients of the message, and not separately to you -
3097 you'll receive your copy through one of the mailing lists you are subscribed
3100 Conversely, when group-replying or list-replying to a message which has a Mail-
3101 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
3102 (section 7.4.94 , page 111) configuration variable is set. Using list-reply
3103 will in this case also make sure that the reply goes to the mailing list, even
3104 if it's not specified in the list of recipients in the Mail-Followup-To.
3106 Note that, when header editing is enabled, you can create a Mail-Followup-To
3107 header manually. Mutt-ng will only auto-generate this header if it doesn't
3108 exist when you send the message.
3110 The other method some mailing list admins use is to generate a ``Reply-To''
3111 field which points back to the mailing list address rather than the author of
3112 the message. This can create problems when trying to reply directly to the
3113 author in private, since most mail clients will automatically reply to the
3114 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
3115 7.4.249 , page 149) variable to help decide which address to use. If set to
3116 _
\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
3117 use the address given in the ``Reply-To'' field, or reply directly to the
3118 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
3119 will be used when present.
3121 The ``X-Label:'' header field can be used to further identify mailing lists or
3122 list subject matter (or just to annotate messages individually). The
3123 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116) variable's ``%y'' and ``%Y''
3124 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
3125 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
3126 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
3127 can easily be inserted by procmail and other mail filtering agents.
3129 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.307 , page 163) the mail-
3130 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
3131 which all relate to the same subject. This is usually organized into a tree-
3132 like structure where a message and all of its replies are represented graphi-
3133 cally. If you've ever used a threaded news client, this is the same concept.
3134 It makes dealing with large volume mailing lists easier because you can easily
3135 delete uninteresting threads and quickly find topics of value.
3137 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3139 Mutt-ng has the ability to dynamically restructure threads that are broken
3141 The Mutt Next Generation E-Mail Client 63
3143 either by misconfigured software or bad behavior from some correspondents. This
3144 allows to clean your mailboxes formats) from these annoyances which make it
3145 hard to follow a discussion.
3147 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3149 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
3150 ences:" headers when replying to a message. This results in broken discussions
3151 because Mutt-ng has not enough information to guess the correct threading. You
3152 can fix this by tagging the reply, then moving to the parent message and using
3153 the ``link-threads'' function (bound to & by default). The reply will then be
3154 connected to this "parent" message.
3156 You can also connect multiple children at once, tagging them and using the tag-
3157 prefix command (';') or the auto_tag option.
3159 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3161 On mailing lists, some people are in the bad habit of starting a new discussion
3162 by hitting "reply" to any message from the list and changing the subject to a
3163 totally unrelated one. You can fix such threads by using the ``break-thread''
3164 function (bound by default to #), which will turn the subthread starting from
3165 the current message into a whole different thread.
3167 _
\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
3169 RFC1894 defines a set of MIME content types for relaying information about the
3170 status of electronic mail messages. These can be thought of as ``return
3173 Users can make use of it in one of the following two ways:
3175 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
3176 the mail client can make requests as to what type of status messages
3179 +
\bo The SMTP support via libESMTP supports it, too.
3181 To support this, there are two variables:
3183 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.56 , page 102) is used to request receipts for
3184 different results (such as failed message, message delivered, etc.).
3186 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.57 , page 103) requests how much of your message
3187 should be returned with the receipt (headers or full message).
3189 Please see the reference chapter for possible values.
3191 _
\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)
3193 The Mutt Next Generation E-Mail Client 64
3195 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3196 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
3197 remote POP3 server and fetch mail for local browsing.
3199 You can access the remote POP3 mailbox by selecting the folder
3202 You can select an alternative port by specifying it with the server, i.e.:
3203 pop://popserver:port/.
3205 You can also specify different username for each folder, i.e.: pop://user-
3206 name@popserver[:port]/.
3208 Polling for new mail is more expensive over POP3 than locally. For this reason
3209 the frequency at which Mutt-ng will check for mail remotely can be controlled
3210 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.224 , page 144) variable, which defaults
3211 to every 60 seconds.
3213 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3214 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3215 rally requires that the server supports SSL encrypted connections. To access a
3216 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3217 name@]popserver[:port]/.
3219 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3220 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.222 , page 143), fetch all your
3221 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.313 , page 165).
3222 After this point, Mutt-ng runs exactly as if the mail had always been local.
3224 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3225 sider using a specialized program, such as fetchmail
3227 _
\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)
3229 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3230 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
3233 You can access the remote inbox by selecting the folder
3234 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3235 INBOX is the special name for your spool mailbox on the IMAP server. If you
3236 want to access another mail folder at the IMAP server, you should use
3237 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3240 You can select an alternative port by specifying it with the server, i.e.:
3241 imap://imapserver:port/INBOX.
3243 You can also specify different username for each folder, i.e.: imap://user-
3244 name@imapserver[:port]/INBOX.
3246 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3248 The Mutt Next Generation E-Mail Client 65
3250 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3251 rally requires that the server supports SSL encrypted connections. To access a
3252 folder with IMAP/SSL, you should use imaps://[user-
3253 name@]imapserver[:port]/path/to/folder as your folder path.
3255 Pine-compatible notation is also supported, i.e. {[user-
3256 name@]imapserver[:port][/ssl]}path/to/folder
3258 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3259 correctly notice which separator is being used by the server and convert paths
3262 When browsing folders on an IMAP server, you can toggle whether to look at only
3263 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
3264 command. See also the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd (section 7.4.103 , page 114)
3267 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3268 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.105 , page 114) and
3269 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.337 , page 172) variables.
3271 Note that if you are using mbox as the mail store on UW servers prior to
3272 v12.250, the server has been reported to disconnect a client if another client
3273 selects the same folder.
3275 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3277 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3278 mostly the same as the local file browser, with the following differences:
3280 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3281 followed by the symbol "+", indicating that the entry contains both mes-
3282 sages and subfolders. On Cyrus-like servers folders will often contain
3283 both messages and subfolders.
3285 +
\bo For the case where an entry can contain both messages and subfolders, the
3286 selection key (bound to enter by default) will choose to descend into the
3287 subfolder view. If you wish to view the messages in that folder, you must
3288 use view-file instead (bound to space by default).
3290 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3291 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3292 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3293 mally these are bound to s and u, respectively).
3295 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3297 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3298 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3299 tion for you poor exchange users out there, but it has yet to be integrated
3300 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3301 which allows you to log in to a public IMAP server without having an account.
3302 To use ANONYMOUS, simply make your username blank or "anonymous".
3304 The Mutt Next Generation E-Mail Client 66
3306 SASL is a special super-authenticator, which selects among several protocols
3307 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3308 available on your host and the server. Using some of these methods (including
3309 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3310 invisible to those teeming network snoops. It is the best option if you have
3311 it. To use it, you must have the Cyrus SASL library installed on your system
3312 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3314 Mutt-ng will try whichever methods are compiled in and available on the server,
3315 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3317 There are a few variables which control authentication:
3319 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.111 , page 115) - controls the username under
3320 which you request authentication on the IMAP server, for all authentica-
3321 tors. This is overridden by an explicit username in the mailbox path (i.e.
3322 by using a mailbox name of the form {user@host}).
3324 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.106 , page 114) - a password which you may pre-
3325 set, used by all authentication methods where a password is needed.
3327 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.97 , page 112) - a colon-delimited list
3328 of IMAP authentication methods to try, in the order you wish to try them.
3329 If specified, this overrides mutt's default (attempt everything, in the
3330 order listed above).
3332 _
\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)
3334 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3335 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3336 function from the index/pager which is by default bound to i.
3338 The Default newsserver can be obtained from the $NNTPSERVER environment vari-
3339 able. Like other news readers, info about subscribed newsgroups is saved in a
3340 file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.172 , page 131) variable.
3341 Article headers are cached and can be loaded from a file when a newsgroup is
3342 entered instead loading from newsserver; currently, this caching mechanism
3343 still is different from the header caching for maildir/IMAP.
3345 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3347 Especially for Usenet, people often ask for advanced filtering and scoring
3348 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3349 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
3352 What has not been discusses in detail is mutt-ng's built-in realname filter.
3353 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3354 there are frequent request for such functionality. The solutions offered often
3355 are complicated regular expressions.
3357 In mutt-ng this is as easy as
3359 The Mutt Next Generation E-Mail Client 67
3363 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3364 fied a valid realname and a valid email address. Using
3368 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3369 ria which are very strict:
3371 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3372 editor.org/in-notes/rfc2822.txt>
3374 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3375 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3376 ``J. User'' and ``J. A. User'' aren't.
3378 +
\bo it's assumed that users are interested in reading their own mail and mail
3379 from people who they have defined an alias for so that those 2 groups of
3380 messages are excluded from the strict rules.
3382 _
\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)
3384 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3385 functionality. When configure was called with --with-libesmtp or the output
3386 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3387 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3388 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 63) section) as well as handling the 8BIT-
3389 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.344 , page 173).
3391 To enable sending mail directly via SMTP without an MTA such as Postfix or
3392 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.302 , page 161)
3393 variable pointing to your SMTP server.
3395 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.306 ,
3396 page 162) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.303 , page 162) variables.
3398 Transport Encryption via the StartTLS command is also available. For this to
3399 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3400 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.305 , page 162) variable must be either set to
3401 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3402 supports it: for the second case, the connection will fail if it doesn't while
3403 switching back to unencrypted communication for the first one.
3405 Some mail providers require user's to set a particular envelope sender, i.e.
3407 The Mutt Next Generation E-Mail Client 68
3409 they allow for only one value which may not be what the user wants to send as
3410 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.301 ,
3411 page 161) may be used to set the envelope different from the From: header.
3413 _
\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)
3415 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3416 find managing all the authentication settings inconvenient and error-prone.
3417 The account-hook command may help. This hook works like folder-hook but is
3418 invoked whenever you access a remote mailbox (including inside the folder
3419 browser), not just when you open the mailbox.
3423 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3424 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3425 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3427 _
\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)
3429 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
3430 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
3431 start a WWW browser on one of them. This functionality is provided by the
3432 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3433 trib/ and the configuration commands:
3435 macro index \cb |urlview\n
3436 macro pager \cb |urlview\n
3438 _
\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)
3440 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3441 _
\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
3442 an arbitrary format, provided that the user has a script to convert from/to
3443 this format to one of the accepted.
3445 The most common use is to open compressed archived folders e.g. with gzip.
3447 In addition, the user can provide a script that gets a folder in an accepted
3448 format and appends its context to the folder in the user-defined format, which
3449 may be faster than converting the entire folder to the accepted format, append-
3450 ing to it and converting back to the user-defined format.
3452 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 69), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3453 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 70))
3454 which define commands to uncompress and compress a folder and to append mes-
3455 sages to an existing compressed folder respectively.
3457 The Mutt Next Generation E-Mail Client 69
3461 open-hook \\.gz$ "gzip -cd %f > %t"
3462 close-hook \\.gz$ "gzip -c %t > %f"
3463 append-hook \\.gz$ "gzip -c %t >> %f"
3465 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-
3466 tion 4.19.3 , page 70), the folder will be open and closed again each time you
3467 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) (or give
3468 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3469 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 70) though you'll be able to append to the folder.
3471 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3472 accepted formats. In particular, if the file is empty, mutt supposes it is not
3473 compressed. This is important because it allows the use of programs that do not
3474 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3475 prising if your compressing script produces empty files. In this situation,
3476 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.256 , page 151), so that the compressed file
3477 will be removed if you delete all of the messages.
3479 _
\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
3481 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3483 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3484 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3486 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3487 parameters: %f, which is replaced with the (compressed) folder name, and %t
3488 which is replaced with the name of the temporary folder to which to write.
3490 %f and %t can be repeated any number of times in the command string, and all of
3491 the entries are replaced with the appropriate folder name. In addition, %% is
3492 replaced by %, as in printf, and any other %anything is left as is.
3494 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
3495 return non-zero exit status if it fails, so mutt knows something's wrong.
3499 open-hook \\.gz$ "gzip -cd %f > %t"
3501 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3503 _
\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
3505 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3507 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3508 4.19.1 , page 69) command after some changes were made to it.
3510 The Mutt Next Generation E-Mail Client 70
3512 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3513 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
3514 4.19.1 , page 69) command. Temporary folder in this case is the folder previ-
3515 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 69) command.
3517 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
3518 non-zero exit status if it fails, so mutt knows something's wrong.
3522 close-hook \\.gz$ "gzip -c %t > %f"
3524 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3525 file can only be open in the readonly mode.
3527 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) is not called when you exit from the
3528 folder if the folder was not changed.
3530 _
\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
3532 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3534 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3535 is the command that can be used for appending to the folders whose names match
3536 _
\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 69)
3537 command. The temporary folder in this case contains the messages that are
3540 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
3541 non-zero exit status if it fails, so mutt knows something's wrong.
3545 append-hook \\.gz$ "gzip -c %t >> %f"
3547 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 70) is used, the folder is not opened,
3548 which saves time, but this means that we can not find out what the folder type
3549 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.132 , page 122)) type is always
3550 supposed (i.e. this is the format used for the temporary folder).
3552 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 ,
3553 page 69) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 70). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3554 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 70) is only for appending to existing folders.
3556 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3557 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3558 4.19.1 , page 69) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69)respectively) each
3559 time you will add to it.
3561 The Mutt Next Generation E-Mail Client 71
3563 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3565 The compressed folders support can also be used to handle encrypted folders. If
3566 you want to encrypt a folder with PGP, you may want to use the following hooks:
3568 open-hook \\.pgp$ "pgp -f < %f > %t"
3569 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3571 Please note, that PGP does not support appending to an encrypted folder, so
3572 there is no append-hook defined.
3574 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3575 can be read by your system administrator. So think about the security aspects
3578 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3580 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3581 MUA. Every effort has been made to provide the functionality that the discern-
3582 ing MIME user requires, and the conformance to the standards wherever possible.
3583 When configuring Mutt-ng for MIME, there are two extra types of configuration
3584 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3585 ping of file extensions to IANA MIME types. The other is the mailcap file,
3586 which specifies the external commands to use for handling specific MIME types.
3588 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3590 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3591 (while viewing a message), the attachment menu and the compose menu.
3593 _
\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
3595 When you select a message from the index and view it in the pager, Mutt decodes
3596 the message to a text representation. Mutt-ng internally supports a number of
3597 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3598 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3599 variety of PGP MIME types, including PGP/MIME and application/pgp.
3601 Mutt-ng will denote attachments with a couple lines describing them. These
3602 lines are of the form:
3604 [-- Attachment #1: Description --]
3605 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3607 Where the Description is the description or filename given for the attachment,
3608 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3610 The Mutt Next Generation E-Mail Client 72
3612 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3614 [-- image/gif is unsupported (use 'v' to view this part) --]
3616 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3618 The default binding for view-attachments is `v', which displays the attachment
3619 menu for a message. The attachment menu displays a list of the attachments in
3620 a message. From the attachment menu, you can save, print, pipe, delete, and
3621 view attachments. You can apply these operations to a group of attachments at
3622 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3623 can also reply to the current message from this menu, and only the current
3624 attachment (or the attachments tagged) will be quoted in your reply. You can
3625 view attachments as text, or view them using the mailcap viewer definition.
3627 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3628 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3629 of type message/rfc822.
3631 See the help on the attachment menu for more information.
3633 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3635 The compose menu is the menu you see before you send a message. It allows you
3636 to edit the recipient list, the subject, and other aspects of your message. It
3637 also contains a list of the attachments of your message, including the main
3638 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3639 review, and rename an attachment or a list of tagged attachments. You can also
3640 modifying the attachment information, notably the type, encoding and descrip-
3643 Attachments appear as follows:
3645 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3646 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3648 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3649 or canceling) the message. It can be toggled with the toggle-unlink command
3650 (default: u). The next field is the MIME content-type, and can be changed with
3651 the edit-type command (default: ^T). The next field is the encoding for the
3652 attachment, which allows a binary message to be encoded for transmission on
3653 7bit links. It can be changed with the edit-encoding command (default: ^E).
3654 The next field is the size of the attachment, rounded to kilobytes or
3655 megabytes. The next field is the filename, which can be changed with the
3656 rename-file command (default: R). The final field is the description of the
3657 attachment, and can be changed with the edit-description command (default: d).
3659 _
\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
3661 When you add an attachment to your mail message, Mutt-ng searches your personal
3663 The Mutt Next Generation E-Mail Client 73
3665 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3666 /usr/local/share/mutt/mime.types or /etc/mime.types
3668 The mime.types file consist of lines containing a MIME type and a space sepa-
3669 rated list of extensions. For example:
3671 application/postscript ps eps
3673 audio/x-aiff aif aifc aiff
3675 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3676 tain most of the MIME types you are likely to use.
3678 If Mutt-ng can not determine the mime type by the extension of the file you
3679 attach, it will look at the file. If the file is free of binary information,
3680 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3681 the file contains binary information, then Mutt-ng will mark it as applica-
3682 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3683 attachment by using the edit-type command from the compose menu (default: ^T).
3684 The MIME type is actually a major mime type followed by the sub-type, separated
3685 by a '/'. 6 major types: application, text, image, video, audio, and model have
3686 been approved after various internet discussions. Mutt-ng recognises all of
3687 these if the appropriate entry is found in the mime.types file. It also recog-
3688 nises other major mime types, such as the chemical type that is widely used in
3689 the molecular modelling community to pass molecular data in various forms to
3690 various molecular viewers. Non-recognised mime types should only be used if the
3691 recipient of the message is likely to be expecting such attachments.
3693 _
\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
3695 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3696 format specified in Appendix A of RFC 1524. This file format is commonly
3697 referred to as the mailcap format. Many MIME compliant programs utilize the
3698 mailcap format, allowing you to specify handling for all MIME types in one
3699 place for all programs. Programs known to use this format include Netscape,
3700 XMosaic, lynx and metamail.
3702 In order to handle various MIME types that Mutt-ng can not handle internally,
3703 Mutt-ng parses a series of external configuration files to find an external
3704 handler. The default search string for these files is a colon delimited list
3707 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3709 where $HOME is your home directory.
3711 In particular, the metamail distribution will install a mailcap file, usually
3712 as /usr/local/etc/mailcap, which contains some baseline entries.
3714 The Mutt Next Generation E-Mail Client 74
3716 _
\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
3718 A mailcap file consists of a series of lines which are comments, blank, or def-
3721 A comment line consists of a # character followed by anything you want.
3723 A blank line is blank.
3725 A definition line consists of a content type, a view command, and any number of
3726 optional fields. Each field of a definition line is divided by a semicolon ';'
3729 The content type is specified in the MIME standard type/subtype method. For
3730 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3731 mat includes two formats for wildcards, one using the special '*' subtype, the
3732 other is the implicit wild, where you only include the major type. For exam-
3733 ple, image/*, or video, will match all image types and video types, respec-
3736 The view command is a Unix command for viewing the type specified. There are
3737 two different types of commands supported. The default is to send the body of
3738 the MIME message to the command on stdin. You can change this behavior by using
3739 %s as a parameter to your view command. This will cause Mutt-ng to save the
3740 body of the MIME message to a temporary file, and then call the view command
3741 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3742 will turn over the terminal to the view program until the program quits, at
3743 which time Mutt will remove the temporary file if it exists.
3745 So, in the simplest form, you can send a text/plain message to the external
3746 pager more on stdin:
3750 Or, you could send the message as a file:
3754 Perhaps you would like to use lynx to interactively view a text/html message:
3758 In this case, lynx does not support viewing a file from stdin, so you must use
3759 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
3760 _
\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
3761 _
\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
3762 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3764 On the other hand, maybe you don't want to use lynx interactively, you just
3765 want to have it convert the text/html to text/plain, then you can use:
3767 The Mutt Next Generation E-Mail Client 75
3769 text/html; lynx -dump %s | more
3771 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3772 text formats, then you would use the following:
3777 This is the simplest form of a mailcap file.
3779 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3781 The interpretation of shell meta-characters embedded in MIME parameters can
3782 lead to security problems in general. Mutt-ng tries to quote parameters in
3783 expansion of %s syntaxes properly, and avoids risky characters by substituting
3784 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.123 , page 120) variable.
3786 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3787 there are other applications parsing mailcap, maybe taking less care of it.
3788 Therefore you should pay attention to the following rules:
3790 _
\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
3791 double quotes. Mutt-ng does this for you, the right way, as should any other
3792 program which interprets mailcap. Don't put them into backtick expansions. Be
3793 highly careful with eval statements, and avoid them if possible at all. Trying
3794 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3795 tive to correct quoting in the first place.
3797 If you have to use the %-expandos' values in context where you need quoting or
3798 backtick expansions, put that value into a shell variable and reference the
3799 shell variable where necessary, as in the following example (using $charset
3800 inside the backtick expansion is safe, since it is not itself subject to any
3803 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3804 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3806 _
\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
3808 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3810 In addition to the required content-type and view command fields, you can add
3811 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3812 nizes the following optional fields:
3815 This flag tells Mutt-ng that the command passes possibly large
3816 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3817 (either the internal pager or the external pager defined by the
3818 pager variable) on the output of the view command. Without this
3820 The Mutt Next Generation E-Mail Client 76
3822 flag, Mutt-ng assumes that the command is interactive. One could
3823 use this to replace the pipe to more in the lynx -dump example in
3826 text/html; lynx -dump %s ; copiousoutput
3828 This will cause lynx to format the text/html output as text/plain
3829 and Mutt-ng will use your standard pager to display the results.
3832 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3833 tion 5.4 , page 79), in order to decide whether it should honor
3834 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.350 , page 174) variable
3835 or not. When an attachment is viewed using an interactive program,
3836 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3837 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.350 , page 174) and the exit
3838 status of the program to decide if it will ask you to press a key
3839 after the external program has exited. In all other situations it
3840 will not prompt you for a key.
3843 This flag specifies the command to use to create a new attachment
3844 of a specific MIME type. Mutt-ng supports this from the compose
3847 composetyped=<command>
3848 This flag specifies the command to use to create a new attachment
3849 of a specific MIME type. This command differs from the compose
3850 command in that mutt will expect standard MIME headers on the data.
3851 This can be used to specify parameters, filename, description, etc.
3852 for a new attachment. Mutt-ng supports this from the compose
3856 This flag specifies the command to use to print a specific MIME
3857 type. Mutt-ng supports this from the attachment and compose menus.
3860 This flag specifies the command to use to edit a specific MIME
3861 type. Mutt-ng supports this from the compose menu, and also uses
3862 it to compose new attachments. Mutt-ng will default to the defined
3863 editor for text attachments.
3865 nametemplate=<template>
3866 This field specifies the format for the file denoted by %s in the
3867 command fields. Certain programs will require a certain file
3868 extension, for instance, to correctly view a file. For instance,
3869 lynx will only interpret a file as text/html if the file ends in
3870 .html. So, you would specify lynx as a text/html viewer with a
3871 line in the mailcap file like:
3873 text/html; lynx %s; nametemplate=%s.html
3875 The Mutt Next Generation E-Mail Client 77
3878 This field specifies a command to run to test whether this mailcap
3879 entry should be used. The command is defined with the command
3880 expansion rules defined in the next section. If the command
3881 returns 0, then the test passed, and Mutt-ng uses this entry. If
3882 the command returns non-zero, then the test failed, and Mutt-ng
3883 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
3884 _
\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:
3886 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3889 In this example, Mutt-ng will run the program RunningX which will
3890 return 0 if the X Window manager is running, and non-zero if it
3891 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3892 display the text/html object. If RunningX doesn't return 0, then
3893 Mutt-ng will go on to the next entry and use lynx to display the
3896 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3898 When searching for an entry in the mailcap file, Mutt-ng will search for the
3899 most useful entry for its purpose. For instance, if you are attempting to
3900 print an image/gif, and you have the following entries in your mailcap file,
3901 Mutt-ng will search for an entry with the print command:
3904 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3907 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3910 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 79) to denote
3911 two commands for viewing an attachment, one to be viewed automatically, the
3912 other to be viewed interactively from the attachment menu. In addition, you
3913 can then use the test feature to determine which viewer to use interactively
3914 depending on your environment.
3916 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3917 text/html; lynx %s; nametemplate=%s.html
3918 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3920 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 79), Mutt-ng will choose the third entry
3921 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3922 program RunningX to determine if it should use the first entry. If the program
3923 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3925 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3927 The various commands defined in the mailcap files are passed to the /bin/sh
3929 The Mutt Next Generation E-Mail Client 78
3931 shell using the system() function. Before the command is passed to /bin/sh -c,
3932 it is parsed to expand various special parameters with information from Mutt-
3933 ng. The keywords Mutt-ng expands are:
3936 As seen in the basic mailcap section, this variable is expanded to
3937 a filename specified by the calling program. This file contains
3938 the body of the message to view/print/edit or where the composing
3939 program should place the results of composition. In addition, the
3940 use of this keyword causes Mutt-ng to not pass the body of the mes-
3941 sage to the view/print/edit program on stdin.
3944 Mutt-ng will expand %t to the text representation of the content
3945 type of the message in the same form as the first parameter of the
3946 mailcap definition line, ie text/html or image/gif.
3949 Mutt-ng will expand this to the value of the specified parameter
3950 from the Content-Type: line of the mail message. For instance, if
3951 Your mail message contains:
3953 Content-Type: text/plain; charset=iso-8859-1
3955 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3956 metamail mailcap file uses this feature to test the charset to
3957 spawn an xterm using the right charset to view the message.
3960 This will be replaced by a %
3962 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3963 1524. The main purpose of these parameters is for multipart messages, which is
3964 handled internally by Mutt-ng.
3966 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3968 This mailcap file is fairly simple and standard:
3970 # I'm always running X :)
3971 video/*; xanim %s > /dev/null
3972 image/*; xv %s > /dev/null
3974 # I'm always running netscape (if my computer had more memory, maybe)
3975 text/html; netscape -remote 'openURL(%s)'
3977 This mailcap file shows quite a number of examples:
3979 The Mutt Next Generation E-Mail Client 79
3981 # Use xanim to view all videos Xanim produces a header on startup,
3982 # send that to /dev/null so I don't see it
3983 video/*; xanim %s > /dev/null
3985 # Send html to a running netscape by remote
3986 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3988 # If I'm not running netscape but I am running X, start netscape on the
3990 text/html; netscape %s; test=RunningX
3992 # Else use lynx to view it as text
3995 # This version would convert the text/html to text/plain
3996 text/html; lynx -dump %s; copiousoutput
3998 # I use enscript to print text in two columns to a page
3999 text/*; more %s; print=enscript -2Gr %s
4001 # Netscape adds a flag to tell itself to view jpegs internally
4002 image/jpeg;xv %s; x-mozilla-flags=internal
4004 # Use xv to view images if I'm running X
4005 # In addition, this uses the \ to extend the line and set my editor
4007 image/*;xv %s; test=RunningX; \
4010 # Convert images to text using the netpbm tools
4011 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
4012 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
4014 # Send excel spreadsheets to my NT box
4015 application/ms-excel; open.pl %s
4017 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
4019 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
4020 viewer defined in the mailcap file, Mutt-ng has support for automatically view-
4021 ing MIME attachments while in the pager.
4023 To work, you must define a viewer in the mailcap file which uses the copi-
4024 ousoutput option to denote that it is non-interactive. Usually, you also use
4025 the entry to convert the attachment to a text representation which you can view
4028 You then use the auto_view muttrc command to list the content-types that you
4029 wish to view automatically.
4031 For instance, if you set auto_view to:
4033 The Mutt Next Generation E-Mail Client 80
4035 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
4037 Mutt-ng could use the following mailcap entries to automatically view attach-
4038 ments of these types.
4040 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
4041 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
4042 application/x-gunzip; gzcat; copiousoutput
4043 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
4044 application/postscript; ps2ascii %s; copiousoutput
4046 ``unauto_view'' can be used to remove previous entries from the autoview list.
4047 This can be used with message-hook to autoview messages based on size, etc.
4048 ``unauto_view *'' will remove all previous entries.
4050 _
\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
4052 Mutt-ng has some heuristics for determining which attachment of a multi-
4053 part/alternative type to display. First, mutt will check the alternative_order
4054 list to determine if one of the available types is preferred. The alterna-
4055 tive_order list consists of a number of MIME types in order, including support
4056 for implicit and explicit wildcards, for example:
4058 alternative_order text/enriched text/plain text application/postscript image/*
4060 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
4061 5.4 , page 79), and use that. Failing that, Mutt-ng will look for any text
4062 type. As a last attempt, mutt will look for any type it knows how to handle.
4064 To remove a MIME type from the alternative_order list, use the unalterna-
4067 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
4069 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
4070 treated according to their mailcap entry. This option is designed to deal with
4071 binary types such as application/octet-stream. When an attachment's mime-type
4072 is listed in mime_lookup, then the extension of the filename will be compared
4073 to the list of extensions in the mime.types file. The mime-type associated
4074 with this extension will then be used to process the attachment according to
4075 the rules in the mailcap file and according to any other configuration options
4076 (such as auto_view) specified. Common usage would be:
4078 mime_lookup application/octet-stream application/X-Lotus-Manuscript
4080 In addition, the unmime_lookup command may be used to disable this feature for
4082 The Mutt Next Generation E-Mail Client 81
4084 any particular mime-type if it had been set, for example, in a global muttrc.
4086 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4088 First of all, mutt-ng contains no security holes included by intention but may
4089 contain unknown security holes. As a consequence, please run mutt-ng only with
4090 as few permissions as possible.
4092 Please do not run mutt-ng as the super user.
4094 When configuring mutt-ng, there're some points to note about secure setups.
4096 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
4097 mail user agents (in their default configuration) just by changing mutt-ng's
4098 configuration files: it then can execute arbitrary programs and scripts
4099 attached to messages, send out private data on its own, etc. Although this is
4100 not believed to the common type of setup, please read this chapter carefully.
4102 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
4104 Although mutt-ng can be told the various passwords for accounts, please never
4105 store passwords in configuration files. Besides the fact that the system's
4106 operator can always read them, you could forget to replace the actual password
4107 with asterisks when reporting a bug or asking for help via, for example, a
4108 mailing list so that your mail including your password could be archived by
4109 internet search engines, etc. Please never store passwords on disk.
4111 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
4113 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
4114 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.342 , page 173) variable can be used to
4115 change the default permissions of these files. Please only change it if you
4116 really know what you are doing. Also, a different location for these files may
4117 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.338 , page 172)
4120 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
4122 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4124 In the default configuration, mutt-ng will leak some information to the outside
4125 world when sending messages: the generation of Message-ID: headers includes a
4126 step counter which is increased (and rotated) with every message sent. If you'd
4127 like to hide this information probably telling others how many mail you sent in
4128 which time, you at least need to remove the %P expando from the default setting
4129 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.149 , page 125) variable. Please make sure
4130 that you really know how local parts of these Message-ID: headers are composed.
4132 The Mutt Next Generation E-Mail Client 82
4134 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
4136 As mutt-ng be can be set up to be the mail client to handle mailto: style links
4137 in websites, there're security considerations, too. To keep the old behavior by
4138 default, mutt-ng will be strict in interpreting them which means that arbitrary
4139 header fields can be embedded in these links which could override existing
4140 header fields or attach arbitrary files. This may be problematic if the
4141 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
4142 doesn't want to see header fields while editing the message.
4144 For example, following a link like
4146 mailto:joe@host?Attach=~/.gnupg/secring.gpg
4148 will send out the user's private gnupg keyring to joe@host if the user doesn't
4149 follow the information on screen carefully enough.
4151 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.326 , page 169) variable, mutt-
4154 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
4155 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
4157 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103) variable by force
4158 to let the user see all the headers (because they still may leak informa-
4161 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4163 Mutt-ng in many places has to rely on external applications or for convenience
4164 supports mechanisms involving external applications.
4166 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
4168 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
4169 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-
4170 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.122 , page 120) variable for
4173 These utilities may have a variety of security vulnerabilities, including over-
4174 writing of arbitrary files, information leaks or other exploitable bugs. These
4175 vulnerabilities may go unnoticed by the user, especially when they are called
4176 automatically (and without interactive prompting) from the mailcap file(s).
4177 When using mutt-ng's autoview mechanism in combination with mailcap files,
4178 please be sure to...
4180 +
\bo manually select trustworth applications with a reasonable calling sequence
4182 +
\bo periodically check the contents of mailcap files, especially after soft-
4183 ware installations or upgrades
4185 The Mutt Next Generation E-Mail Client 83
4187 +
\bo keep the software packages referenced in the mailcap file up to date
4189 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.123 , page 120) variable in its
4190 default state to restrict mailcap expandos to a safe set of characters
4192 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
4194 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4197 The same security considerations apply for these as for tools involved via
4198 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4199 compressed folders support if the uncompressed mailbox is too large for the
4200 disk it is saved to.)
4202 As already noted, most of these problems are not built in but caused by wrong
4203 configuration, so please check your configuration.
4205 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4207 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4209 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4210 mailbox. However, it is possible to read other mailboxes and to send messages
4211 from the command line as well.
4214 -a attach a file to a message
4215 -b specify a blind carbon-copy (BCC) address
4216 -c specify a carbon-copy (Cc) address
4217 -e specify a config command to be run after initialization files are read
4218 -f specify a mailbox to load
4219 -F specify an alternate file to read initialization commands
4220 -h print help on command line options
4221 -H specify a draft file from which to read a header and body
4222 -i specify a file to include in a message composition
4223 -m specify a default mailbox type
4224 -n do not read the system Muttngrc
4225 -p recall a postponed message
4226 -Q query a configuration variable
4227 -R open mailbox in read-only mode
4228 -s specify a subject (enclose in quotes if it contains spaces)
4229 -t dump the value of all variables to stdout
4230 -T dump the value of all changed variables to stdout
4231 -v show version number and compile-time definitions
4232 -x simulate the mailx(1) compose mode
4233 -y show a menu containing the files specified by the mailboxes command
4234 -z exit immediately if there are no messages in the mailbox
4235 -Z open the first folder with new message,exit immediately if none
4237 To read messages in a mailbox
4239 The Mutt Next Generation E-Mail Client 84
4241 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4243 To compose a new message
4245 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-
4246 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4248 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4249 rect input from the file you wish to send. For example,
4251 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4253 This command will send a message to ``professor@bigschool.edu'' with a subject
4254 of ``data set for run #2''. In the body of the message will be the contents of
4255 the file ``~/run2.dat''.
4257 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4259 The Mutt Next Generation E-Mail Client 85
4262 ~b EXPR messages which contain EXPR in the message body
4263 ~B EXPR messages which contain EXPR in the whole message
4264 ~c USER messages carbon-copied to USER
4265 ~C EXPR message is either to: or cc: EXPR
4267 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4269 ~e EXPR message which contains EXPR in the ``Sender'' field
4271 ~f USER messages originating from USER
4272 ~g cryptographically signed messages
4273 ~G cryptographically encrypted messages
4274 ~H EXPR messages with a spam attribute matching EXPR
4275 ~h EXPR messages which contain EXPR in the message header
4276 ~k message contains PGP key material
4277 ~i ID message which match ID in the ``Message-ID'' field
4278 ~L EXPR message is either originated or received by EXPR
4279 ~l message is addressed to a known mailing list
4280 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4281 ~M multipart messages
4282 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4285 ~p message is addressed to you (consults alternates)
4286 ~P message is from you (consults alternates)
4287 ~Q messages which have been replied to
4289 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4290 ~S superseded messages
4291 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4293 ~t USER messages addressed to USER
4295 ~v message is part of a collapsed thread.
4296 ~V cryptographically verified messages
4297 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4298 (if compiled with NNTP support)
4299 ~x EXPR messages which contain EXPR in the `References' field
4300 ~y EXPR messages which contain EXPR in the `X-Label' field
4301 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4302 ~= duplicated messages (see $duplicate_threads)
4303 ~$ unreferenced messages (requires threaded view)
4304 ~* ``From'' contains realname and (syntactically) valid
4305 address (excluded are addresses matching against
4306 alternates or any alias)
4308 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
4309 49). Special attention has to be made when using regular expressions inside of
4310 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4311 level of backslash (\), which is normally used for quoting. If it is your
4312 intention to use a backslash in the regular expression, you will need to use
4313 two backslashes instead (\\).
4315 The Mutt Next Generation E-Mail Client 86
4317 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4319 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4321 The following are the commands understood by mutt.
4323 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 67) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4325 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 26) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4327 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 26) [ * | _
\bk_
\be_
\by ... ]
4329 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 34) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4331 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 34) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4333 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 80) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4335 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 80) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4337 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 70) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4339 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4341 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4343 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 27) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4345 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 29) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4347 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 69) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4349 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 31) _
\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 ]
4351 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 31) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4353 +
\bo _
\be_
\bx_
\be_
\bc (section 3.25 , page 42) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4355 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4357 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4359 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 29) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4361 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 39) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4363 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 39) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4365 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 29) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4367 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 33) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4369 The Mutt Next Generation E-Mail Client 87
4371 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 33) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4373 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4375 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4377 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 30) _
\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 ]
4379 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 37) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4381 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4383 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4385 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 80) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4387 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 80) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4389 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.9 , page 31) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4391 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.9 , page 31) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4393 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 38) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4395 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 38) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4397 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 69) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4399 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.23 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4401 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 41) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4403 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.28 , page 45) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4405 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 39) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4407 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4409 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4411 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 40) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4413 +
\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
4415 +
\bo _
\bs_
\be_
\bt (section 3.28 , page 45) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4417 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.28 , page 45) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4419 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 46) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4421 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.27 , page 43) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4423 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.27 , page 43) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4425 The Mutt Next Generation E-Mail Client 88
4427 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4429 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4431 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.28 , page 45) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4433 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.30 , page 46) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4435 _
\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
4437 The following list contains all variables which, in the process of providing
4438 more consistency, have been renamed and are partially even removed already. The
4439 left column contains the old synonym variables, the right column the full/new
4442 The Mutt Next Generation E-Mail Client 89
4444 edit_hdrs edit_headers
4445 forw_decode forward_decode
4446 forw_format forward_format
4447 forw_quote forward_quote
4448 hdr_format index_format
4449 indent_str indent_string
4450 mime_fwd mime_forward
4451 msg_format message_format
4452 pgp_autosign crypt_autosign
4453 pgp_autoencrypt crypt_autoencrypt
4454 pgp_replyencrypt crypt_replyencrypt
4455 pgp_replysign crypt_replysign
4456 pgp_replysignencrypted crypt_replysignencrypted
4457 pgp_verify_sig crypt_verify_sig
4458 pgp_create_traditional pgp_autoinline
4459 pgp_auto_traditional pgp_replyinline
4460 forw_decrypt forward_decrypt
4461 smime_sign_as smime_default_key
4462 post_indent_str post_indent_string
4463 print_cmd print_command
4464 shorten_hierarchy sidebar_shorten_hierarchy
4465 ask_followup_to nntp_ask_followup_to
4466 ask_x_comment_to nntp_ask_x_comment_to
4467 catchup_newsgroup nntp_catchup
4468 followup_to_poster nntp_followup_to_poster
4469 group_index_format nntp_group_index_format
4471 mime_subject nntp_mime_subject
4472 news_cache_dir nntp_cache_dir
4473 news_server nntp_host
4475 nntp_poll nntp_mail_check
4476 pop_checkinterval pop_mail_check
4477 post_moderated nntp_post_moderated
4478 save_unsubscribed nntp_save_unsubscribed
4479 show_new_news nntp_show_new_news
4480 show_only_unread nntp_show_only_unread
4481 x_comment_to nntp_x_comment_to
4482 smtp_auth_username smtp_user
4483 smtp_auth_password smtp_pass
4485 The contrib subdirectory contains a script named update-config.pl which eases
4488 A complete list of current variables follows.
4490 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
4496 This variable specifies whether to abort sending if no attachment was made but
4498 The Mutt Next Generation E-Mail Client 90
4500 the content references them, i.e. the content matches the regular expression
4501 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 93). If a match was
4502 found and this variable is set to _
\by_
\be_
\bs, message sending will be aborted but the
4503 mail will be send nevertheless if set to _
\bn_
\bo.
4505 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 93) are
4506 intended to remind the user to attach files if the message's text references
4509 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 93) variable.
4511 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4517 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4518 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4519 subject given at the subject prompt will never be aborted.
4521 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4527 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4528 body if no changes are made to the file (this check only happens after the
4529 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4531 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bg_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4537 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
4538 cating which version of Mutt-ng was used for composing them.
4540 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4544 Default: '~/.muttngrc'
4546 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4547 tion 2.5.4 , page 11)'' function.
4549 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4550 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 46)'' command for it to be executed.
4552 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4554 The Mutt Next Generation E-Mail Client 91
4558 Default: '%4n %2f %t %-10a %r'
4560 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4561 ing printf(3)-style sequences are available:
4567 flags - currently, a 'd' for an alias marked for deletion
4573 address which alias expands to
4576 character which indicates if the alias is tagged for inclusion
4578 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4584 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4585 or base64 encoding when sending mail.
4587 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4593 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4594 sages) are to be interpreted. Messages containing these codes are rare, but if
4595 this option is set, their text will be colored accordingly. Note that this may
4596 override your color choices, and even present a security problem, since a mes-
4597 sage could include a line like ``[-- PGP output follows ...' and give it the
4598 same color as your attachment color.
4600 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4606 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4607 instead of highlighting the whole line. On slow network or modem links this
4608 will make response faster because there is less that has to be redrawn on the
4609 screen when moving to the next or previous entries in the menu.
4611 The Mutt Next Generation E-Mail Client 92
4613 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4619 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4620 attachment trees, instead of the default ACS characters.
4622 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4628 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4629 editing an outgoing message.
4631 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bs_
\bk_
\bc_
\bc
4637 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4638 the body of an outgoing message.
4640 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4646 This variable is a colon-separated list of character encoding schemes for mes-
4647 sages without character encoding indication. Header field values and message
4648 body content without character encoding indication would be assumed that they
4649 are written in one of this list. By default, all the header fields and message
4650 body without any charset indication are assumed to be in us-ascii.
4652 For example, Japanese users might prefer this:
4654 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4656 However, only the first content is valid for the message body. This variable
4657 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.327 , page 170) is unset.
4659 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4663 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4665 This variable describes the format of the ``attachment'' menu. The following
4666 printf(3)-style sequences are understood:
4668 The Mutt Next Generation E-Mail Client 93
4674 requires charset conversion (n or c)
4683 MIME Content-Transfer-Encoding: header field
4689 MIME Content-Disposition: header field (I=inline, A=attachment)
4707 graphic tree characters
4710 unlink (=to delete) flag
4713 right justify the rest of the string and pad with character 'X'
4716 pad to the end of the line with character 'X'
4718 _
\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
4720 Type: regular expression
4724 The Mutt Next Generation E-Mail Client 94
4726 If this variable is non-empty, muttng will scan a message's contents before
4727 sending for this regular expression. If it is found, it will ask for what to do
4728 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 89).
4730 This variable and _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 89) are intended to
4731 remind the user to attach files if the message's text references them.
4733 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4739 The separator to add between attachments when operating (saving, printing, pip-
4740 ing, etc) on a list of tagged attachments.
4742 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4748 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4749 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4750 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.16 ,
4751 page 94)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4752 operate on the attachments one by one.
4754 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4758 Default: 'On %d, %n wrote:'
4760 This is the string that will precede a message which has been included in a
4761 reply. For a full listing of defined printf(3)-like sequences see the section
4762 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116)''.
4764 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4770 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4771 all tagged messages (if there are any). When unset, you must first use the
4772 ``tag-prefix'' function (default: ';') to make the next function apply to all
4775 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4781 The Mutt Next Generation E-Mail Client 95
4783 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103)'', Mutt-ng
4784 will skip the initial send-menu and allow you to immediately begin editing the
4785 body of your message. The send-menu may still be accessed once you have fin-
4786 ished editing the body of your message.
4788 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.66 , page 105)''.
4790 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\be_
\be_
\bp
4796 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4798 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4804 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4805 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4806 tion 7.4.21 , page 95)'' variable.
4808 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4814 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4815 you don't get asked if you want to bounce a message. Setting this variable to
4816 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4819 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4825 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4826 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4828 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4834 When this variable is set, mutt will place the cursor at the beginning of the
4835 current line in menus, even when the arrow_cursor variable is unset, making it
4836 easier for blind persons using Braille displays to follow these menus. The
4838 The Mutt Next Generation E-Mail Client 96
4840 option is disabled by default because many visual terminals don't permit making
4841 the cursor invisible.
4843 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4847 Default: '~/.mutt_certificates'
4849 Availability: SSL or GNUTLS
4851 This variable specifies the file where the certificates you trust are saved.
4852 When an unknown certificate is encountered, you are asked if you accept it or
4853 not. If you accept it, the certificate can also be saved in this file and fur-
4854 ther connections are automatically accepted.
4856 You can also manually add CA certificates in this file. Any server certificate
4857 that is signed with one of these CA certificates are also automatically
4860 Example: set certificate_file=~/.muttng/certificates
4862 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4868 Character set your terminal uses to display and enter textual data.
4870 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4876 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4878 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4879 Especially with MH mailboxes, this operation can take quite some time since it
4880 involves scanning the directory and checking each file to see if it has already
4881 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4884 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4890 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4893 The Mutt Next Generation E-Mail Client 97
4895 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4899 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4901 Controls the format of the status line displayed in the ``compose'' menu. This
4902 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.324 , page 167)'', but has
4903 its own set of printf(3)-like sequences:
4906 total number of attachments
4912 approximate size (in bytes) of the current message
4915 Mutt-ng version string
4917 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.324 , page 167)''
4918 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 ,
4921 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4927 When defined, Mutt-ng will recode commands in rc files from this encoding.
4929 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4935 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4938 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4944 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4945 box which does not yet exist before creating it.
4947 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4949 The Mutt Next Generation E-Mail Client 98
4955 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4956 many seconds if the connection is not able to be established. A negative value
4957 causes Mutt-ng to wait indefinitely for the connection to succeed.
4959 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4963 Default: 'text/plain'
4965 Sets the default Content-Type: header field for the body of newly composed mes-
4968 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\bo_
\bp_
\by
4974 This variable controls whether or not copies of your outgoing messages will be
4975 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.246 , page
4976 148)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.257 , page 151)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4977 7.4.74 , page 107)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 39)''.
4979 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4985 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4986 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4987 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4988 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
4989 7.4.293 , page 159)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4990 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4993 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4999 This variable controls whether or not Mutt-ng may automatically enable PGP
5000 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
5001 7.4.37 , page 98)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 99)'',
5002 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 98)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
5003 7.4.42 , page 99)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.293 , page 159)''.
5005 The Mutt Next Generation E-Mail Client 99
5007 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
5013 Setting this variable will cause Mutt-ng to always attempt to cryptographically
5014 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
5015 signing is not required or encryption is requested as well. If
5016 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.293 , page 159)'' is _
\bs_
\be_
\bt, then OpenSSL is
5017 used instead to create S/MIME messages and settings can be overridden by use of
5018 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
5020 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
5026 This variable controls whether or not Mutt-ng may automatically enable S/MIME
5027 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
5028 7.4.37 , page 98)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 99)'',
5029 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 98)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
5030 7.4.42 , page 99)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.293 , page 159)''.
5032 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
5038 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
5039 encrypted. (Crypto only)
5041 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
5047 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
5049 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
5052 _
\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
5058 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
5059 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
5060 7.4.41 , page 99)'', because it allows you to sign all messages which are
5062 The Mutt Next Generation E-Mail Client 100
5064 automatically encrypted. This works around the problem noted in
5065 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.42 , page 99)'', that Mutt-ng is not able to
5066 find out whether an encrypted message is also signed. (Crypto only)
5068 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
5074 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
5075 S/MIME output, so spoofing such lines is more difficult. If you are using col-
5076 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
5079 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
5085 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
5086 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
5087 will be used instead of the classic code.
5089 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
5090 won't have any effect when used interactively.
5092 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
5098 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
5099 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
5100 cryptographic signatures. (Crypto only)
5102 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5106 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
5108 This variable controls the format of the date printed by the ``%d'' sequence in
5109 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116)''. This is passed to strftime(3)
5110 to process the date.
5112 Unless the first character in the string is a bang (``!''), the month and week
5113 day names are expanded according to the locale specified in the variable
5114 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.120 , page 120)''. If the first character in the string
5115 is a bang, the bang is discarded, and the month and week day names in the rest
5116 of the string are expanded in the _
\bC locale (that is in US English).
5118 The Mutt Next Generation E-Mail Client 101
5120 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\be_
\bb_
\bu_
\bg_
\b__
\bl_
\be_
\bv_
\be_
\bl
5128 This variable specifies the current debug level and may be used to increase or
5129 decrease the verbosity level during runtime. It overrides the level given with
5130 the -d command line option.
5132 Currently, this number must be >= 0 and <= 5 and muttng must be started with -d
5133 to enable debugging at all; enabling at runtime is not possible.
5135 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
5139 Default: '~f %s !~P | (~P ~C %s)'
5141 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
5142 will be interpreted if they are specified with only a simple regexp, instead of
5143 a matching pattern. The hooks are expanded when they are declared, so a hook
5144 will be interpreted according to the value of this variable at the time the
5145 hook is declared. The default value matches if the message is either from a
5146 user matching the regular expression given, or if it is from you (if the from
5147 address matches ``alternates'') and is to or cc'ed to a user matching the given
5150 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\be_
\bl_
\be_
\bt_
\be
5156 Controls whether or not messages are really deleted when closing or synchroniz-
5157 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
5158 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
5159 be kept in the mailbox.
5161 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be
5167 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
5168 7.4.333 , page 171) variable, this variable specifies whether to also set the
5169 DelSp parameter to yes. If this is _
\bu_
\bn_
\bs_
\be_
\bt, no additional parameter will be send
5170 as a value of no already is the default behavior.
5172 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
5173 (section 7.4.333 , page 171) is _
\bs_
\be_
\bt) but not on incomming.
5175 The Mutt Next Generation E-Mail Client 102
5177 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
5183 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
5184 tion. This applies when you either explicitly delete a message, or when you
5185 save it to another folder.
5187 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
5193 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
5194 subparts of individual messages in a multipart/digest. To see these subparts,
5195 press 'v' on that menu.
5197 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
5203 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
5204 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 ,
5205 page 102), and the filtered message is read from the standard output.
5207 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
5211 Default: '$muttng_bindir/muttng_dotlock'
5213 Availability: Standalone and Dotlock
5215 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
5217 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
5223 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5224 or in connection with the SMTP support via libESMTP.
5226 This variable sets the request for when notification is returned. The string
5227 consists of a comma separated list (no spaces!) of one or more of the follow-
5228 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
5229 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
5230 notified of successful transmission.
5232 The Mutt Next Generation E-Mail Client 103
5234 Example: set dsn_notify='failure,delay'
5236 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
5242 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5243 or in connection with the SMTP support via libESMTP.
5245 This variable controls how much of your message is returned in DSN messages.
5246 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
5247 return the full message.
5249 Example: set dsn_return=hdrs
5251 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
5257 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
5258 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
5259 indicate that it thinks they are duplicates of each other with an equals sign
5260 in the thread diagram.
5262 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5268 This option allows you to edit the header of your outgoing messages along with
5269 the body of your message.
5271 Which empty header fields to show is controlled by the _
\b$_
\be_
\bd_
\bi_
\bt_
\bo_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section
5272 7.4.61 , page 103) option.
5274 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5280 This variable specifies which editor is used by Mutt-ng. It defaults to the
5281 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5282 if neither of those are set.
5284 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5288 The Mutt Next Generation E-Mail Client 104
5290 Default: 'From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To: X-Com-
5293 If _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103) is _
\bs_
\be_
\bt, this space-separated list
5294 specifies which _
\bn_
\bo_
\bn_
\b-_
\be_
\bm_
\bp_
\bt_
\by header fields to edit in addition to user-defined
5297 Note: if _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103) had to be turned on by
5298 force because _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo (section 7.4.326 , page 169) is _
\bu_
\bn_
\bs_
\be_
\bt, this
5299 option has no effect.
5301 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5307 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5308 string ``From '' (note the trailing space) in the beginning of a line. Useful
5309 to avoid the tampering certain mail delivery and transport agents tend to do
5312 N
\bNo
\bot
\bte
\be:
\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
5313 <em/strongly/ advised to _
\bs_
\be_
\bt this option although discouraged by the standard.
5314 Alternatively, you must take care of space-stuffing <tt/From / lines (with a
5315 trailing space) yourself.
5317 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5325 The file which includes random data that is used to initialize SSL library
5328 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5334 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5335 ``From:'' header field. Note that this information is passed to the sendmail
5336 command using the ``-f' command line switch, so don't set this option if you
5337 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.263 , page 152) yourself, or
5338 if the sendmail on your machine doesn't support that command line switch.
5340 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5344 The Mutt Next Generation E-Mail Client 105
5348 Escape character to use for functions in the builtin editor.
5350 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5356 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5357 ing to messages, and the initial prompt for subject is skipped when forwarding
5360 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
5361 94)'' variable is _
\bs_
\be_
\bt.
5363 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5369 This variable controls whether or not attachments on outgoing messages are
5370 saved along with the main body of your message.
5372 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5378 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5379 when the actual message is encrypted and/or signed. (PGP only)
5381 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5387 This variable is a colon-separated list of character encoding schemes for text
5388 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.27 , page 96) value will
5389 be used instead. For example, the following configuration would work for
5390 Japanese text handling:
5392 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5394 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5397 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5401 The Mutt Next Generation E-Mail Client 106
5405 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5406 beginning of a pathname will be expanded to the value of this variable. Note
5407 that if you change this variable from the default value you need to make sure
5408 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5409 ables since expansion takes place during the ``set'' command.
5411 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5415 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5417 This variable allows you to customize the file browser display to your personal
5418 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page
5419 116)'', but has its own set of printf(3)-like sequences:
5425 date/time folder was last modified
5434 group name (or numeric gid, if missing)
5437 number of hard links
5440 N if folder has new mail, blank otherwise
5446 * if the file is tagged, blank otherwise
5449 owner name (or numeric uid, if missing)
5452 right justify the rest of the string and pad with character 'X'
5455 pad to the end of the line with character 'X'
5457 The Mutt Next Generation E-Mail Client 107
5459 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5465 Controls whether or not the Mail-Followup-To: header field is generated when
5466 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5467 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5468 3.13 , page 36)'' commands or detected by common mailing list headers.
5470 This field has two purposes. First, preventing you from receiving duplicate
5471 copies of replies to messages which you send to mailing lists. Second, ensuring
5472 that you do get a reply separately for any messages sent to known lists to
5473 which you are not subscribed. The header will contain only the list's address
5474 for subscribed lists, and both the list address and your own email address for
5475 unsubscribed lists. Without this header, a group reply to your message sent to
5476 a subscribed list will be sent to both the list and your address, resulting in
5477 two copies of the same email for you.
5479 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5485 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
5486 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
5487 already known to have new mail.
5489 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.337 , page 172)'',
5490 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.121 , page 120)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5491 7.4.105 , page 114)''.
5493 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5499 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.257 , page 151)'',
5500 except that Mutt-ng will store a copy of your outgoing message by the username
5501 of the address you are sending to even if that mailbox does not exist.
5503 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.246 , page 148)'' variable.
5505 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5511 Controls the decoding of complex MIME messages into text/plain when forwarding
5512 a message. The message header is also RFC2047 decoded. This variable is only
5514 The Mutt Next Generation E-Mail Client 108
5516 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 124)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5517 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.144 , page 124)'' is used instead.
5519 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5525 Controls the handling of encrypted messages when forwarding a message. When
5526 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5527 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 124)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5528 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.144 , page 124)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5530 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5536 This quadoption controls whether or not the user is automatically placed in the
5537 editor when forwarding messages. For those who always want to forward with no
5538 modification, use a setting of _
\bn_
\bo.
5540 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5546 This variable controls the default subject when forwarding a message. It uses
5547 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page
5550 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5556 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5557 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 124)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5558 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.115 , page 116)''.
5560 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bf_
\br_
\bo_
\bm
5562 Type: e-mail address
5566 This variable contains a default from address. It can be overridden using
5567 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.252 , page
5568 150)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.346 , page
5571 The Mutt Next Generation E-Mail Client 109
5573 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5574 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5575 takes this email address.
5577 Defaults to the contents of the environment variable $EMAIL.
5579 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5581 Type: regular expression
5585 A regular expression used by Mutt-ng to parse the GECOS field of a password
5586 entry when expanding the alias. By default the regular expression is set to
5587 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5588 the GECOS field contains a string like 'lastname, firstname' then you should
5589 do: set gecos_mask='.*'.
5591 This can be useful if you see the following behavior: you address a e-mail to
5592 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5593 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5594 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5595 to ``Franklin, Steve''.
5597 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\bd_
\br_
\bs
5603 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 ,
5604 page 38)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5605 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5606 defined header fields are added to every new message.
5608 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5614 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5615 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.351 , page
5616 175)'' setting applies.
5618 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5624 Availability: Header Cache
5626 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.84 , page 109) variable points to the header
5628 The Mutt Next Generation E-Mail Client 110
5632 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.84 , page 109) points to a directory it will
5633 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5634 7.4.84 , page 109) points to a file that file will be a single global header
5635 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5637 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5643 If enabled the header cache will be compressed. So only one fifth of the usual
5644 diskspace is used, but the uncompression can result in a slower open of the
5647 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\be_
\bl_
\bp
5653 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5654 by each menu are displayed on the first line of the screen.
5656 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5657 sequence rather than a single keystroke. Also, the help line may not be
5658 updated if a binding is changed while Mutt-ng is running. Since this variable
5659 is primarily aimed at new users, neither of these should present a major prob-
5662 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5668 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5669 7.4.95 , page 111)'' variable when adding the domain part to addresses. This
5670 variable does not affect the generation of Message-ID: header fields, and it
5671 will not lead to the cut-off of first-level domains.
5673 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5679 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5680 limiting, in the thread tree.
5682 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5684 The Mutt Next Generation E-Mail Client 111
5690 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5693 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5699 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5700 have the same subject as their parent or closest previously displayed sibling.
5702 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5708 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5709 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5710 _
\bi_
\bn_
\bg (section 7.4.89 , page 110) is set, this option will have no effect.
5712 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5718 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5719 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.88 ,
5720 page 110) is _
\bs_
\be_
\bt, this option will have no effect.
5722 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5728 This variable controls the size (in number of strings remembered) of the string
5729 history buffer. The buffer is cleared each time the variable is changed.
5731 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5737 This variable controls whether or not a Mail-Followup-To: header field is hon-
5738 ored when group-replying to a message.
5740 The Mutt Next Generation E-Mail Client 112
5742 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5748 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5749 during generation of Message-Id: headers.
5751 Please be sure to really know what you are doing when changing this variable to
5752 configure a custom domain part of Message-IDs.
5754 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5760 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5761 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5762 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5763 header field was set by the mailing list to automate responses to the list, and
5764 will ignore this field. To direct a response to the mailing list when this
5765 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
5766 sender and the list.
5768 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5776 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5777 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5778 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5779 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5780 eter is case-insensitive.
5782 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5783 ods, in order from most-secure to least-secure.
5785 Example: set imap_authenticators='gssapi:cram-md5:login'
5787 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5788 ous methods are unavailable. If a method is available but authentication fails,
5789 Mutt-ng will not connect to the IMAP server.
5791 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5797 The Mutt Next Generation E-Mail Client 113
5799 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5800 connection, and add them to the set of mailboxes it polls for new mail. See
5801 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 37)'' command.
5803 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5811 This contains the list of characters which you would like to treat as folder
5812 separators for displaying IMAP paths. In particular it helps in using the '='
5813 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 , page 105) variable.
5815 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5823 Mutt-ng requests these header fields in addition to the default headers (``DATE
5824 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5825 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5826 ``index'' menu. You may want to add more headers for spam detection.
5828 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5830 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5838 You normally want to see your personal folders alongside your INBOX in the IMAP
5839 browser. If you see something else, you may set this variable to the IMAP path
5842 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5850 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5851 wait before polling open IMAP connections, to prevent the server from closing
5852 them before Mutt-ng has finished with them.
5854 The Mutt Next Generation E-Mail Client 114
5856 The default is well within the RFC-specified minimum amount of time (30 min-
5857 utes) before a server is allowed to do this, but in practice the RFC does get
5858 violated every now and then.
5860 Reduce this number if you find yourself getting disconnected from your IMAP
5861 server due to inactivity.
5863 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5871 This variable configures whether IMAP folder browsing will look for only sub-
5872 scribed folders or all folders. This can be toggled in the IMAP browser with
5873 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5875 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5883 Your login name on the IMAP server.
5885 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.111 , page
5888 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5894 This variable configures how often (in seconds) Mutt-ng should look for new
5895 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.121 ,
5896 page 120)'' variable to generate less traffic and get more accurate information
5899 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5907 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5908 you for your password when you invoke the fetch-mail function.
5910 The Mutt Next Generation E-Mail Client 115
5912 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5913 machine, because the superuser can read your configuration even if you are the
5914 only one who can read the file.
5916 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5924 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5925 Mutt-ng will only check for new mail over existing IMAP connections. This is
5926 useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
5927 cation, or if opening the connection is slow.
5929 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5937 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5938 fetch a message from the server. This is generally a good thing, but can make
5939 closing an IMAP folder somewhat slower. This option exists to appease speed
5942 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5950 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5953 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5961 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5962 messages. Since these messages are often harmless, or generated due to configu-
5963 ration problems on the server which are out of the users' hands, you may wish
5964 to suppress them at some point.
5966 The Mutt Next Generation E-Mail Client 116
5968 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5976 The name of the user whose mail you intend to access on the IMAP server.
5978 This variable defaults to your user name on the local machine.
5980 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5986 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5987 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5988 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5989 convert the body part to text form.
5991 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5997 Controls whether or not a copy of the message(s) you are replying to is
5998 included in your reply.
6000 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
6006 Controls whether or not Mutt-ng includes only the first attachment of the mes-
6007 sage you are replying.
6009 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
6015 Specifies the string to prepend to each line of text quoted in a message to
6016 which you are replying. You are strongly encouraged not to change this value,
6017 as it tends to agitate the more fanatical netizens.
6019 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6023 The Mutt Next Generation E-Mail Client 117
6025 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
6027 This variable allows you to customize the message index display to your per-
6030 ``Format strings'' are similar to the strings used in the ``C'' function
6031 printf(3) to format output (see the man page for more detail). The following
6032 sequences are defined in Mutt-ng:
6035 address of the author
6038 reply-to address (if present; otherwise: address of author)
6041 filename of the original message folder (think mailBox)
6044 the list to which the letter was sent, or else the folder name
6048 number of characters (bytes) in the message
6051 current message number
6054 date and time of the message in the format specified by ``date_for-
6055 mat'' converted to sender's time zone
6058 date and time of the message in the format specified by ``date_for-
6059 mat'' converted to the local time zone
6062 current message number in thread
6065 number of messages in current thread
6068 entire From: line (address + real name)
6071 author name, or recipient name if the message is from you
6074 spam attribute(s) of this message
6077 newsgroup name (if compiled with nntp support)
6079 The Mutt Next Generation E-Mail Client 118
6082 message-id of the current message
6085 number of lines in the message (does not work with maildir, mh, and
6086 possibly IMAP folders)
6089 If an address in the To or CC header field matches an address
6090 defined by the users ``subscribe'' command, this displays 'To
6091 <list-name>', otherwise the same as %F.
6094 total number of message in the mailbox
6097 number of hidden messages if the thread is collapsed.
6103 author's real name (or address if missing)
6106 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
6107 the message: list name or recipient name if no list
6110 subject of the message
6113 status of the message (N/D/d/!/r/*)
6116 `to:' field (recipients)
6119 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.339 ,
6123 user (login) name of the author
6126 first name of the author, or the recipient if the message is from
6130 name of organization of author (`organization:' field)
6133 `x-label:' field, if present
6135 The Mutt Next Generation E-Mail Client 119
6138 `x-label' field, if present, and (1) not at part of a thread tree,
6139 (2) at the top of a thread, or (3) `x-label' is different from pre-
6140 ceding message's `x-label'.
6143 message status flags
6146 the date and time of the message is converted to sender's time
6147 zone, and ``fmt'' is expanded by the library function ``strftime'';
6148 a leading bang disables locales
6151 the date and time of the message is converted to the local time
6152 zone, and ``fmt'' is expanded by the library function ``strftime'';
6153 a leading bang disables locales
6156 the local date and time when the message was received. ``fmt'' is
6157 expanded by the library function ``strftime''; a leading bang dis-
6161 the current local time. ``fmt'' is expanded by the library function
6162 ``strftime''; a leading bang disables locales.
6165 right justify the rest of the string and pad with character 'X'
6168 pad to the end of the line with character 'X'
6170 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.339 , page 172)''.
6172 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
6178 How to invoke ispell (GNU's spell-checking software).
6180 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6186 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
6187 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.131 , page 122)'' mailbox, or as a result of
6188 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37)'' command.
6190 The Mutt Next Generation E-Mail Client 120
6192 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
6198 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
6199 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
6200 will ask if you really intended to reply to the author only.
6202 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
6208 The locale used by strftime(3) to format dates. Legal values are the strings
6209 your system accepts for the locale variable LC_TIME.
6211 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6217 This variable configures how often (in seconds) Mutt-ng should look for new
6220 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
6221 7.4.105 , page 114).
6223 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
6229 This variable specifies which files to consult when attempting to display MIME
6230 bodies not directly supported by Mutt-ng.
6232 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
6238 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
6239 well-defined set of safe characters. This is the safe setting, but we are not
6240 sure it doesn't break some more advanced MIME stuff.
6242 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!
6244 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by
6246 The Mutt Next Generation E-Mail Client 121
6252 Availability: Header Cache
6254 Check for Maildir unaware programs other than Mutt-ng having modified maildir
6255 files when the header cache is in use. This incurs one stat(2) per message
6256 every time the folder is opened.
6258 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
6264 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
6265 flag instead of physically deleted.
6267 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
6268 effect on other mailbox types.
6270 It is similiar to the trash option.
6272 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
6278 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
6279 mailbox without reading them.
6281 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
6282 up with an 'O' next to them in the ``index'' menu, indicating that they are
6285 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
6291 Controls the display of wrapped lines in the internal pager. If set, a ``+''
6292 marker is displayed at the beginning of wrapped lines. Also see the
6293 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.279 , page 156)'' variable.
6295 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\ba_
\bs_
\bk
6297 Type: regular expression
6301 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6303 The Mutt Next Generation E-Mail Client 122
6305 operator ``!''. Only files whose names match this mask will be shown. The
6306 match is always case-sensitive.
6308 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6314 When set non-zero, this specifies the maximum number of recipient header lines
6315 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6316 case the number of lines exeeds its value, the last line will have 3 dots
6319 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6325 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6326 is limited to this length. A value of 0 (which is also the default) means that
6327 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6328 (section 7.4.353 , page 175).
6330 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\bb_
\bo_
\bx
6336 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6337 7.4.313 , page 165)'' folder will be appended.
6339 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6345 The default mailbox type used when creating new folders. May be any of mbox,
6346 MMDF, MH and Maildir.
6348 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6354 This variable controls the number of lines of context that are given when
6355 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.183 , page
6358 The Mutt Next Generation E-Mail Client 123
6360 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6366 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6367 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6368 entry may move off the bottom.
6370 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6376 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6377 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6378 vious page of the menu is displayed (useful for slow links to avoid many
6381 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6387 This is the string displayed in the ``attachment'' menu for attachments of type
6388 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6389 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116)''.
6391 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6397 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6398 if the user had pressed the ESC key and whatever key remains after having the
6399 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6400 then this is treated as if the user had pressed ESC then ``x''. This is
6401 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6402 the ASCII character ``x''.
6404 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\be_
\bt_
\bo_
\bo
6410 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6411 from the list of recipients when replying to a message.
6413 The Mutt Next Generation E-Mail Client 124
6415 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6421 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6422 _
\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-
6423 able is set, the message files will simply be deleted.
6425 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6431 The name of the MH sequence used for flagged messages.
6433 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6439 The name of the MH sequence used to tag replied messages.
6441 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6447 The name of the MH sequence used for unseen messages.
6449 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6455 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6456 part instead of included in the main body of the message.
6458 This is useful for forwarding MIME messages so the receiver can properly view
6459 the message as it was delivered to you. If you like to switch between MIME and
6460 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6462 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.75 , page 107)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6463 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.144 , page 124)''.
6465 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6469 The Mutt Next Generation E-Mail Client 125
6473 Controls the decoding of complex MIME messages into text/plain when forwarding
6474 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.143 , page 124)'' is _
\bs_
\be_
\bt. Other-
6475 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.75 , page 107)'' is used instead.
6477 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6483 When forwarding multiple attachments of a MIME message from the recvattach
6484 menu, attachments which cannot be decoded in a reasonable manner will be
6485 attached to the newly composed message if this option is set.
6487 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6491 Default: '%4n %c %-16s %a'
6493 Availability: Mixmaster
6495 This variable describes the format of a remailer line on the mixmaster chain
6496 selection screen. The following printf(3)-like sequences are supported:
6499 The running number on the menu.
6502 Remailer capabilities.
6505 The remailer's short name.
6508 The remailer's e-mail address.
6510 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6514 Default: 'mixmaster'
6516 Availability: Mixmaster
6518 This variable contains the path to the Mixmaster binary on your system. It is
6519 used with various sets of parameters to gather the list of known remailers, and
6520 to finally send a message through the mixmaster chain.
6522 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bm_
\bo_
\bv_
\be
6526 The Mutt Next Generation E-Mail Client 126
6530 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6531 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.131 , page 122)'' mailbox, or as a result of a
6532 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 37)'' command.
6534 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6538 Default: '%Y%m%d%h%M%s.G%P%p'
6540 This is the format for the ``local part'' of the Message-Id: header field gen-
6541 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6542 generated. The '%' character marks that certain data will be added to the
6543 string, similar to printf(3). The following characters are allowed:
6546 the current day of month
6558 the current UNIX timestamp (octal)
6564 the current Message-ID prefix (a character rotating with every Mes-
6565 sage-ID being generated)
6568 a random integer value (decimal)
6571 a random integer value (hexadecimal)
6577 the current UNIX timestamp (decimal)
6580 the current UNIX timestamp (hexadecimal)
6582 The Mutt Next Generation E-Mail Client 127
6585 the current year (Y2K compliant)
6590 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6591 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6593 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bb_
\bi_
\bn_
\bd_
\bi_
\br
6595 Type: system property
6597 Value: /opt/freebsd4/mutt-ng/bin
6599 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be
6600 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bb_
\bi_
\bn_
\ba_
\br_
\by_
\b.
6602 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bd_
\bo_
\bc_
\bd_
\bi_
\br
6604 Type: system property
6606 Value: /opt/freebsd4/mutt-ng/doc/muttng
6608 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be
6609 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt_
\ba_
\bt_
\bi_
\bo_
\bn_
\b.
6611 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bn_
\ba_
\bm_
\be
6613 Type: system property
6617 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd_
\b, _
\ba_
\bt _
\br_
\bu_
\bn_
\bt_
\bi_
\bm_
\be_
\b, _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bl_
\ba_
\bs_
\bt _
\bp_
\ba_
\br_
\bt _
\bo_
\bf
6618 _
\bt_
\bh_
\be _
\bf_
\bu_
\bl_
\bl _
\bp_
\ba_
\bt_
\bh _
\bo_
\br _
\bU_
\bR_
\bI _
\bo_
\bf _
\bt_
\bh_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by _
\bo_
\bp_
\be_
\bn _
\b(_
\bi_
\bf _
\ba_
\bn_
\by_
\b)_
\b, _
\bi_
\b._
\be_
\b. _
\be_
\bv_
\be_
\br_
\by_
\bt_
\bh_
\bi_
\bn_
\bg
6619 _
\ba_
\bf_
\bt_
\be_
\br _
\bt_
\bh_
\be _
\bl_
\ba_
\bs_
\bt _
\b`_
\b`_
\b/_
\b'_
\b'_
\b.
6621 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bp_
\ba_
\bt_
\bh
6623 Type: system property
6627 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd_
\b, _
\ba_
\bt _
\br_
\bu_
\bn_
\bt_
\bi_
\bm_
\be_
\b, _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bf_
\bu_
\bl_
\bl _
\bp_
\ba_
\bt_
\bh _
\bo_
\br
6628 _
\bU_
\bR_
\bI _
\bo_
\bf _
\bt_
\bh_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by _
\bo_
\bp_
\be_
\bn _
\b(_
\bi_
\bf _
\ba_
\bn_
\by_
\b)_
\b.
6630 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bh_
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bb_
\ba_
\bc_
\bk_
\be_
\bn_
\bd
6632 Type: system property
6636 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br _
\bc_
\bh_
\ba_
\bc_
\bh_
\bi_
\bn_
\bg_
\b'_
\bs _
\bd_
\ba_
\bt_
\ba_
\b-
6637 _
\bb_
\ba_
\bs_
\be _
\bb_
\ba_
\bc_
\bk_
\be_
\bn_
\bd_
\b.
6639 The Mutt Next Generation E-Mail Client 128
6641 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bp_
\bw_
\bd
6643 Type: system property
6647 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd_
\b, _
\ba_
\bt _
\br_
\bu_
\bn_
\bt_
\bi_
\bm_
\be_
\b, _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt
6648 _
\bw_
\bo_
\br_
\bk_
\bi_
\bn_
\bg _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bo_
\bf _
\bt_
\bh_
\be _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bb_
\bi_
\bn_
\ba_
\br_
\by_
\b.
6650 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\br_
\be_
\bv_
\bi_
\bs_
\bi_
\bo_
\bn
6652 Type: system property
6656 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b'_
\bs _
\bs_
\bu_
\bb_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn _
\br_
\be_
\bv_
\bi_
\bs_
\bi_
\bo_
\bn
6657 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\b.
6659 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bc_
\bo_
\bn_
\bf_
\bd_
\bi_
\br
6661 Type: system property
6663 Value: /opt/freebsd4/mutt-ng/etc
6665 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bt_
\bh_
\be _
\bd_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by _
\bc_
\bo_
\bn_
\bt_
\ba_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be
6666 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg _
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\b-_
\bw_
\bi_
\bd_
\be _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\b.
6668 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b__
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn
6670 Type: system property
6674 _
\bT_
\bh_
\bi_
\bs _
\bi_
\bs _
\ba _
\br_
\be_
\ba_
\bd_
\b-_
\bo_
\bn_
\bl_
\by _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bp_
\br_
\bo_
\bp_
\be_
\br_
\bt_
\by _
\ba_
\bn_
\bd _
\bs_
\bp_
\be_
\bc_
\bi_
\bf_
\bi_
\be_
\bs _
\bm_
\bu_
\bt_
\bt_
\bn_
\bg_
\b'_
\bs _
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\b.
6676 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6682 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6683 threads to fit on the screen.
6685 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6693 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6694 ing the body of an outgoing news article.
6696 The Mutt Next Generation E-Mail Client 129
6698 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6706 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6707 ing the body of an outgoing news article.
6709 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6713 Default: '~/.muttng'
6717 This variable points to directory where Mutt-ng will cache news article head-
6718 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6719 when you enter a newsgroup.
6721 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6722 cally increases speed and lowers traffic.
6724 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6732 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6733 when you leaving it.
6735 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6743 This variable controls how many news articles to cache per newsgroup (if
6744 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.162 , page 129)) and how
6745 many news articles to show in the ``index'' menu.
6747 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.164 ,
6748 page 129), all older ones will be removed/not shown in the index.
6750 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6752 The Mutt Next Generation E-Mail Client 130
6760 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6761 header field, a follow-up to the newsgroup is not permitted. The message will
6762 be mailed to the submitter of the message via mail.
6764 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6768 Default: '%4C %M%N %5s %-45.45f %d'
6772 This variable allows you to customize the newsgroup browser display to your
6773 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 ,
6774 page 116)'', but has its own set of printf(3)-like sequences:
6776 %C current newsgroup number
6777 %d description of newsgroup (retrieved from server)
6779 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6780 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6781 %n number of new articles in newsgroup
6782 %s number of unread articles in newsgroup
6783 %>X right justify the rest of the string and pad with character "X"
6784 %|X pad to the end of the line with character "X"
6786 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6794 This variable specifies the name (or address) of the NNTP server to be used.
6796 It defaults to the value specified via the environment variable $NNTPSERVER or
6797 contained in the file /etc/nntpserver.
6799 You can also specify a username and an alternative port for each newsserver,
6802 [nntp[s]://][username[:password]@]newsserver[:port]
6804 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6805 security risk since the superuser of your machine may read it regardless of the
6807 The Mutt Next Generation E-Mail Client 131
6811 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6819 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6820 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6821 lowing printf(3)-style sequence is understood:
6825 Example: set inews='/usr/local/bin/inews -hS'
6827 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6835 This variable controls whether or not descriptions for newsgroups are to be
6836 loaded when subscribing to a newsgroup.
6838 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6846 The time in seconds until any operations on a newsgroup except posting a new
6847 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6848 each operation in index (stepping, read article, etc.).
6850 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6858 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6859 encoded according to RFC2047.
6861 The Mutt Next Generation E-Mail Client 132
6863 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6865 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6869 Default: '~/.newsrc'
6873 This file contains information about subscribed newsgroup and articles read so
6876 To ease the use of multiple news servers, the following printf(3)-style
6877 sequence is understood:
6881 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6889 Your password for NNTP account.
6891 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6892 the superuser of your machine may read it regardless of the file's permissions.
6894 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6902 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6903 sions to post (e.g. moderated).
6905 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6906 is totally read-only, that posting will not have any effect.
6908 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6916 The Mutt Next Generation E-Mail Client 133
6918 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6919 was connection lost.
6921 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6929 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6930 file and into the news cache.
6932 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6940 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6941 browser. Otherwise, it will be done only once for a newsserver. Also controls
6942 whether or not the number of new articles of subscribed newsgroups will be
6945 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6953 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6954 played in the newsgroup browser.
6956 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6964 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6965 tification, Mutt-ng will prompt you for your account name.
6967 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6973 The Mutt Next Generation E-Mail Client 134
6977 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6978 name of the original article author) to articles that you followup to.
6980 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6986 This specifies the operating system name for the User-Agent: header field. If
6987 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6988 returns. If uname(2) fails, ``UNIX'' will be used.
6990 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6992 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\ba_
\bg_
\be_
\br
6998 This variable specifies which pager you would like to use to view messages.
6999 ``builtin'' means to use the builtin pager, otherwise this variable should
7000 specify the pathname of the external pager you would like to use.
7002 Using an external pager may have some disadvantages: Additional keystrokes are
7003 necessary because you can't call Mutt-ng functions directly from the pager, and
7004 screen resizes cause lines longer than the screen width to be badly formatted
7007 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
7013 This variable controls the number of lines of context that are given when dis-
7014 playing the next or previous page in the internal pager. By default, Mutt-ng
7015 will display the line after the last one on the screen at the top of the next
7016 page (0 lines of context).
7018 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7022 Default: '-%Z- %C/%m: %-20.20n %s'
7024 This variable controls the format of the one-line message ``status'' displayed
7025 before each message in either the internal or an external pager. The valid
7026 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116)''
7029 The Mutt Next Generation E-Mail Client 135
7031 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
7037 Determines the number of lines of a mini-index which is shown when in the
7038 pager. The current message, unless near the top or bottom of the folder, will
7039 be roughly one third of the way down this mini-index, giving the reader the
7040 context of a few messages before and after the message. This is useful, for
7041 example, to determine how many messages remain to be read in the current
7042 thread. One of the lines is reserved for the status bar from the index, so a
7043 _
\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
7044 0 results in no index being shown. If the number of messages in the current
7045 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
7048 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
7054 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
7055 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
7057 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7063 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
7064 whenever the user performs an operation which ordinarily would result in the
7065 contents of the message being operated on. For example, if the user displays a
7066 pgp-traditional message which has not been manually checked with the check-tra-
7067 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
7070 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7076 This option controls whether Mutt-ng generates old-style inline (traditional)
7077 PGP encrypted or signed messages under certain circumstances. This can be
7078 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
7080 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7081 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7082 ing PGP/MIME messages when inline (traditional) would not work. See also:
7083 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.204 , page 139)''.
7085 The Mutt Next Generation E-Mail Client 136
7087 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.
7090 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
7096 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
7097 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
7099 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7105 This format is used to create a old-style ``clearsigned'' PGP message.
7107 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)
7109 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7115 This format strings specifies a command which is used to decode application/pgp
7118 The PGP command formats have their own set of printf(3)-like sequences:
7121 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
7122 string otherwise. Note: This may be used with a %? construct.
7125 Expands to the name of a file containing a message.
7128 Expands to the name of a file containing the signature part of a
7129 multipart/signed attachment when verifying it.
7132 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.208 , page 140).
7135 One or more key IDs.
7137 For examples on how to configure these formats for the various versions of PGP
7138 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
7139 subdirectory which has been installed on your system alongside the documenta-
7142 The Mutt Next Generation E-Mail Client 137
7144 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7150 This command is used to decrypt a PGP encrypted message. (PGP only)
7152 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\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
7158 This command is used to encrypt a body part without signing it. (PGP only)
7160 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\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
7166 This command is used to both sign and encrypt a body part. (PGP only)
7168 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7172 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
7174 This variable allows you to customize the PGP key selection menu to your per-
7175 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page
7176 116)'', but has its own set of printf(3)-like sequences:
7199 The Mutt Next Generation E-Mail Client 138
7202 trust/validity of the key-uid association
7205 date of the key where <s> is an strftime(3) expression
7209 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7215 This command is used to export a public key from the user's key ring. (PGP
7218 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7224 This command is invoked whenever Mutt-ng will need public key information. %r
7225 is the only printf(3)-like sequence used with this format. (PGP only)
7227 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
7229 Type: regular expression
7233 If you assign a text to this variable, then a PGP signature is only considered
7234 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.214 , page 141)
7235 contains the text. Use this variable if the exit code from the command is 0
7236 even for bad signatures. (PGP only)
7238 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
7244 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
7245 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
7246 want to play interesting key selection games. (PGP only)
7248 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7254 This command is used to import a key from a message into the user's public key
7256 The Mutt Next Generation E-Mail Client 139
7260 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\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
7266 This command is used to list the public key ring's contents. The output format
7267 must be analogous to the one used by gpg --list-keys --with-colons.
7269 This format is also generated by the pgpring utility which comes with Mutt-ng.
7272 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\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
7278 This command is used to list the secret key ring's contents. The output format
7279 must be analogous to the one used by gpg --list-keys --with-colons.
7281 This format is also generated by the pgpring utility which comes with Mutt-ng.
7284 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
7290 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
7293 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
7299 This option controls whether Mutt-ng will prompt you for automatically sending
7300 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
7303 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.
7306 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7312 The Mutt Next Generation E-Mail Client 140
7314 Setting this variable will cause Mutt-ng to always attempt to create an inline
7315 (traditional) message when replying to a message which is PGP encrypted/signed
7316 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
7317 required. This option does not automatically detect if the (replied-to) mes-
7318 sage is inline; instead it relies on Mutt-ng internals for previously
7319 checked/flagged messages.
7321 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7322 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7323 ing PGP/MIME messages when inline (traditional) would not work. See also:
7324 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.204 , page 139)''.
7326 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.
7329 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
7335 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
7336 and multipart/encrypted body parts.
7338 This is useful for applications like encrypted and signed mailing lists, where
7339 the outer layer (multipart/encrypted) can be easily removed, while the inner
7340 multipart/signed part is retained. (PGP only)
7342 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
7348 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
7349 This includes keys which have been revoked, have expired, or have been marked
7350 as ``disabled'' by the user. (PGP only)
7352 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
7358 If you have more than one key pair, this option allows you to specify which of
7359 your private keys to use. It is recommended that you use the keyid form to
7360 specify your key (e.g., ``0x00112233''). (PGP only)
7362 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7368 The Mutt Next Generation E-Mail Client 141
7370 This command is used to create the detached PGP signature for a multi-
7371 part/signed PGP/MIME body part. (PGP only)
7373 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
7379 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7383 sort alphabetically by user id
7386 sort alphabetically by key id
7389 sort by key creation date
7392 sort by the trust of the key
7394 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7397 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7403 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7404 printable. Please note that unsetting this variable may lead to problems with
7405 non-verifyable PGP signatures, so only change this if you know what you are
7408 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7414 The number of seconds after which a cached passphrase will expire if not used.
7415 Default: 300. (PGP only)
7417 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7423 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7425 The Mutt Next Generation E-Mail Client 142
7427 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7433 This command is used to verify PGP signatures. (PGP only)
7435 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7441 This command is used to verify key information from the key selection menu.
7444 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7450 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
7451 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7452 ers and will attempt to PGP/MIME decode the messages first.
7454 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7460 The separator to add between messages when piping a list of tagged messages to
7461 an external Unix command.
7463 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7469 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7470 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7471 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7472 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7473 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7474 (section 7.4.217 , page 142)'' separator is added after each message.
7476 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7482 The Mutt Next Generation E-Mail Client 143
7486 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7487 fall back to other authentication methods if the previous methods are unavail-
7488 able. If a method is available but authentication fails, Mutt-ng will not con-
7489 nect to the POP server.
7491 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7499 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7500 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7501 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7502 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7504 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7505 Mutt-ng will try all available methods, in order from most-secure to least-
7508 Example: set pop_authenticators='digest-md5:apop:user'
7510 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7518 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7519 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7520 load messages but also leave them on the POP server.
7522 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7530 The name of your POP server for the ``fetch-mail'' function. You can also
7531 specify an alternative port, username and password, i.e.:
7533 [pop[s]://][username[:password]@]popserver[:port]
7535 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7536 the superuser of your machine may read it regardless of the file's permissions.
7538 The Mutt Next Generation E-Mail Client 144
7540 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7548 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7549 retrieving only unread messages from the POP server when using the ``fetch-
7552 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7560 This variable configures how often (in seconds) POP should look for new mail.
7562 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7570 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7571 for your password when you open POP mailbox.
7573 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7574 the superuser of your machine may read it regardless of the file's permissions.
7576 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7584 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7587 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7595 The Mutt Next Generation E-Mail Client 145
7597 Your login name on the POP server.
7599 This variable defaults to your user name on the local machine.
7601 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7607 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 94)'' variable, Mutt-ng
7608 will append this string after the inclusion of a message which is being replied
7611 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7617 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7618 7.4.230 , page 145)'' mailbox when you elect not to send immediately.
7620 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7624 Default: '~/postponed'
7626 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.229 , page 145)
7627 sending a message'' which you are editing. When you choose to postpone a mes-
7628 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7629 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.229 , page 145)'' variable.
7631 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7637 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a connec-
7638 tion to the server. This is useful for setting up secure connections, e.g. with
7639 ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the
7642 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7643 /dev/null > /dev/null'
7645 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7647 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7648 machine without having to enter a password.
7650 The Mutt Next Generation E-Mail Client 146
7652 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\bp_
\br_
\bi_
\bn_
\bt
7658 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7659 by default, because some people accidentally hit ``p'' often.
7661 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7667 This specifies the command pipe that should be used to print messages.
7669 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7675 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7676 message is decoded before it is passed to the external command specified by
7677 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.233 , page 146). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7678 cessing will be applied to the message when printing it. The latter setting
7679 may be useful if you are using some advanced printer filter which is able to
7680 properly format e-mail messages for printing.
7682 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7688 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7689 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.233 , page 146) is executed
7690 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7691 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.233 , page 146) is executed
7692 only once, and all the messages are concatenated, with a form feed as the mes-
7695 Those who use the enscript(1) program's mail-printing mode will most likely
7696 want to set this option.
7698 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7704 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.182 , page 134)'', setting this
7705 variable will cause Mutt-ng to prompt you for a command when the pager exits
7707 The Mutt Next Generation E-Mail Client 147
7709 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7710 index menu when the external pager exits.
7712 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7718 This specifies the command that Mutt-ng will use to make external address
7719 queries. The string should contain a %s, which will be substituted with the
7720 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 59)'' for more
7723 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\bq_
\bu_
\bi_
\bt
7729 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7730 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7731 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
7734 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7740 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7741 tion 7.4.115 , page 116)''.
7743 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7749 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7750 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7751 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.115 , page 116)''.
7753 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7755 Type: regular expression
7757 Default: '^([ \t]*[|>:}#])+'
7759 A regular expression used in the internal-pager to determine quoted sections of
7760 text in the body of a message.
7762 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
7764 The Mutt Next Generation E-Mail Client 148
7766 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7767 the beginning of quoted lines.
7769 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7775 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7776 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7777 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7778 reads message 25, and then again when it gets to message 50). This variable is
7779 meant to indicate progress when reading large mailboxes which may take some
7780 time. When set to 0, only a single message will appear before the reading the
7783 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.355 , page 175)'' variable.
7785 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7791 If set, all folders are opened in read-only mode.
7793 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7799 This variable specifies what ``real'' or ``personal'' name should be used when
7802 By default, this is the GECOS field from /etc/passwd.
7804 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7805 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.80 , page 108) variable.
7807 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7813 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7814 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.230 , page 145)''.
7816 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7818 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7820 The Mutt Next Generation E-Mail Client 149
7826 This specifies the file into which your outgoing messages should be appended.
7827 (This is meant as the primary method for saving a copy of your messages, but
7828 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 38)'' com-
7829 mand to create a Bcc: header field with your email address in it.)
7831 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b8_
\b) is overridden by the
7832 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.74 , page 107)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7833 7.4.257 , page 151)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page
7836 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7838 Type: regular expression
7840 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7842 A regular expression used to recognize reply messages when threading and reply-
7843 ing. The default value corresponds to the English ``Re:'' and the German
7846 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7852 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7853 that you want to reply to the recipients of that message rather than to your-
7856 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7862 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7863 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7864 use the address in the ``From:'' header field instead.
7866 This option is useful for reading a mailing list that sets the ``Reply-To:''
7867 header field to the list address and you want to send a private message to the
7868 author of a message.
7870 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7876 The Mutt Next Generation E-Mail Client 150
7878 When set, the cursor will be automatically advanced to the next (possibly
7879 undeleted) message whenever a command that modifies the current message is exe-
7882 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7888 This variable controls whether or not Mutt-ng will display the ``personal''
7889 name from your aliases in the index menu if it finds an alias that matches the
7890 message's sender. For example, if you have the following alias:
7892 alias juser abd30425@somewhere.net (Joe User)
7894 and then you receive mail which contains the following header:
7896 From: abd30425@somewhere.net
7898 It would be displayed in the index menu as ``Joe User'' instead of
7899 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7900 not human friendly (like CompuServe addresses).
7902 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7908 It may sometimes arrive that you receive mail to a certain machine, move the
7909 messages to another machine, and reply to some the messages from there. If
7910 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7911 using the address where you received the messages you are replying to i
\bif
\bf that
7912 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7913 would be used doesn't match your alternates, the From: line will use your
7914 address on the current machine.
7916 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7922 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.252 ,
7923 page 150) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7924 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7925 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7926 (section 7.4.244 , page 148) variable.
7928 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7932 The Mutt Next Generation E-Mail Client 151
7936 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7937 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7938 ments to files named like this:
7940 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7942 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7943 effect before you have changed folders.
7945 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7946 standard, but nevertheless encountered in the wild.
7948 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7949 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7950 encoding specified in RFC 2231.
7952 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7958 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7959 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.257 , page 151)'' or
7960 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.74 , page 107)'' is _
\bs_
\be_
\bt too, the selection of the
7961 fcc folder will be changed as well.
7963 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7969 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7970 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.313 , page 165)'' which is
7971 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7973 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7974 and Maildir directories.
7976 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7982 This variable controls how copies of outgoing messages are saved. When set, a
7983 check is made to see if a mailbox specified by the recipient address exists
7984 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.70 ,
7985 page 105)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7986 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7987 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.246 , page 148)'' mailbox.
7989 The Mutt Next Generation E-Mail Client 152
7991 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.74 , page 107)'' variable.
7993 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bc_
\bo_
\br_
\be
7999 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
8000 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
8001 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.259 , page 152)'' variable and friends are used.
8003 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
8009 Messages which have been assigned a score equal to or lower than the value of
8010 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
8011 scores are always greater than or equal to zero, the default setting of this
8012 variable will never mark a message for deletion.
8014 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
8020 Messages which have been assigned a score greater than or equal to this vari-
8021 able's value are automatically marked ``flagged''.
8023 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
8029 Messages which have been assigned a score equal to or lower than the value of
8030 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
8031 scores are always greater than or equal to zero, the default setting of this
8032 variable will never mark a message read.
8034 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
8038 Default: 'us-ascii:iso-8859-1:utf-8'
8040 A list of character sets for outgoing messages. Mutt-ng will use the first
8041 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
8042 (section 7.4.27 , page 96)'' is not iso-8859-1 and recipients may not under-
8043 stand UTF-8, it is advisable to include in the list an appropriate widely used
8044 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
8046 The Mutt Next Generation E-Mail Client 153
8048 instead of or after iso-8859-1.
8050 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
8054 Default: '/usr/sbin/sendmail -oem -oi'
8056 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
8057 Mutt-ng expects that the specified program interprets additional arguments as
8058 recipient addresses.
8060 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
8066 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.263 ,
8067 page 152)'' process to finish before giving up and putting delivery in the
8070 Mutt-ng interprets the value of this variable as follows:
8073 number of seconds to wait for sendmail to finish before continuing
8076 wait forever for sendmail to finish
8079 always put sendmail in the background without waiting
8081 Note that if you specify a value other than 0, the output of the child process
8082 will be put in a temporary file. If there is some error, you will be informed
8083 as to where to find the output.
8085 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bh_
\be_
\bl_
\bl
8091 Command to use when spawning a subshell. By default, the user's login shell
8092 from /etc/passwd is used.
8094 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
8100 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
8101 7.4.270 , page 154) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
8103 The Mutt Next Generation E-Mail Client 154
8105 split a folder name into ``hierarchy items.''
8107 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
8113 This specifies the delimiter between the sidebar (if visible) and other
8116 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
8122 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
8124 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8128 Default: '%m%?n?(%n)?%?f?[%f]?'
8130 This variable controls how message counts are printed when the sidebar is
8131 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
8132 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
8133 mbox-style mailboxes.)
8135 The following printf(3)-like sequences are supported all of which may be
8139 Number of deleted messages. 1)
8142 Number of flagged messages.
8145 Total number of messages.
8148 Total number of messages shown, i.e. not hidden by a limit. 1)
8151 Number of new messages.
8154 Number of tagged messages. 1)
8156 1) These expandos only have a non-zero value for the current mailbox and will
8157 always be zero otherwise.
8159 The Mutt Next Generation E-Mail Client 155
8161 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\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
8167 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
8168 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
8169 7.4.272 , page 155)'' is set to a too low value). For example, if the news-
8170 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
8171 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
8174 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
8175 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.266 , page 153) variable.
8177 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
8183 This specifies whether or not to show the sidebar (a list of folders specified
8184 with the ``mailboxes'' command).
8186 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
8192 The width of the sidebar.
8194 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
8200 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
8201 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.275 , page 155)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
8202 that you not unset this variable unless your ``signature'' contains just your
8203 name. The reason for this is because many software packages use ``-- \n'' to
8204 detect your signature.
8206 For example, Mutt-ng has the ability to highlight the signature in a different
8207 color in the builtin pager.
8209 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8215 The Mutt Next Generation E-Mail Client 156
8217 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
8218 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
8219 know what you are doing, and are prepared to take some heat from netiquette
8222 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
8226 Default: '~/.signature'
8228 Specifies the filename of your signature, which is appended to all outgoing
8229 messages. If the filename ends with a pipe (``|''), it is assumed that file-
8230 name is a shell command and input should be read from its stdout.
8232 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
8238 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
8239 people that want to sign off every message they send with their name.
8241 If you want to insert your website's URL, additional contact information or
8242 witty quotes into your mails, better use a signature file instead of the sig-
8245 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8249 Default: '~f %s | ~s %s'
8251 Specifies how Mutt-ng should expand a simple search into a real search pattern.
8252 A simple search is one that does not contain any of the ~ operators. See
8253 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 84)'' for more information on search patterns.
8255 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
8256 will automatically expand it to the value specified by this variable. For the
8257 default value it would be:
8261 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
8267 Specifies time, in seconds, to pause while displaying certain informational
8268 messages, while moving from folder to folder and after expunging messages from
8269 the current folder. The default is to pause one second, so a value of zero for
8270 this option suppresses the pause.
8272 The Mutt Next Generation E-Mail Client 157
8274 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
8280 Controls the display of lines longer than the screen width in the internal
8281 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
8282 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.127 ,
8283 page 121)'' variable.
8285 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
8287 Type: regular expression
8289 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
8291 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
8292 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.241 , page 147)'', most notably smileys in the
8295 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
8301 This flag controls whether you want to be asked to enter a label for a certifi-
8302 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
8305 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
8311 This variable contains the name of either a directory, or a file which contains
8312 trusted certificates for use with OpenSSL. (S/MIME only)
8314 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
8320 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
8321 and retrieval of keys by itself. This is very basic right now, and keys and
8322 certificates are stored in two different directories, both named as the hash-
8323 value retrieved from OpenSSL. There is an index file which contains mailbox-
8324 address keyid pairs, and which can be manually edited. This one points to the
8325 location of the certificates. (S/MIME only)
8327 The Mutt Next Generation E-Mail Client 158
8329 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8335 This format string specifies a command which is used to decrypt application/x-
8336 pkcs7-mime attachments.
8338 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
8342 Expands to the name of a file containing a message.
8345 Expands to the name of a file containing the signature part of a
8346 multipart/signed attachment when verifying it.
8349 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.286 ,
8353 One or more certificate IDs.
8356 The algorithm used for encryption.
8359 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
8360 7.4.282 , page 157) points to a directory or file, this expands to
8361 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.282 , page 157)' or
8362 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.282 , page 157)'.
8364 For examples on how to configure these formats, see the smime.rc in the sam-
8365 ples/ subdirectory which has been installed on your system alongside the docu-
8366 mentation. (S/MIME only)
8368 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\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
8374 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
8375 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8376 mailbox-address to determine the key to use. It will ask you to supply a key,
8377 if it can't find one. (S/MIME only)
8379 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8383 The Mutt Next Generation E-Mail Client 159
8387 This is the default key-pair to use for signing. This must be set to the keyid
8388 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8390 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8396 This command is used to create encrypted S/MIME messages. (S/MIME only)
8398 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8404 This sets the algorithm that should be used for encryption. Valid choices are
8405 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8407 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8409 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8415 This command is used to extract X509 certificates from a PKCS7 structure.
8418 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\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
8424 This command is used to extract the mail address(es) used for storing X509 cer-
8425 tificates, and for verification purposes (to check whether the certificate was
8426 issued for the sender's mailbox). (S/MIME only)
8428 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\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
8434 This command is used to extract only the signers X509 certificate from a S/MIME
8435 signature, so that the certificate's owner may get compared to the email's
8436 ``From:'' header field. (S/MIME only)
8438 The Mutt Next Generation E-Mail Client 160
8440 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\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
8446 This command is used to import a certificate via smime_keysng. (S/MIME only)
8448 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8454 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8455 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8457 However, this has no effect while replying, since Mutt-ng will automatically
8458 select the same application that was used to sign/encrypt the original message.
8460 (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-
8461 tion 7.4.40 , page 99).) (S/MIME only)
8463 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8469 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8470 retrieval of keys/certs by itself. This is very basic right now, and stores
8471 keys and certificates in two different directories, both named as the hash-
8472 value retrieved from OpenSSL. There is an index file which contains mailbox-
8473 address keyid pair, and which can be manually edited. This one points to the
8474 location of the private keys. (S/MIME only)
8476 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8482 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8483 to extract the public X509 certificate(s). (S/MIME only)
8485 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8491 This command is used to created S/MIME signatures of type multipart/signed,
8492 which can be read by all mail clients. (S/MIME only)
8494 The Mutt Next Generation E-Mail Client 161
8496 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\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
8502 This command is used to created S/MIME signatures of type application/x-
8503 pkcs7-signature, which can only be handled by mail clients supporting the
8504 S/MIME extension. (S/MIME only)
8506 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8512 The number of seconds after which a cached passphrase will expire if not used.
8515 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8521 This command is used to verify S/MIME signatures of type multipart/signed.
8524 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\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
8530 This command is used to verify S/MIME signatures of type application/x-
8531 pkcs7-mime. (S/MIME only)
8533 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8541 If this variable is non-empty, it'll be used as the envelope sender. If it's
8542 empty (the default), the value of the regular From: header will be used.
8544 This may be necessary as some providers don't allow for arbitrary values as the
8545 envelope sender but only a particular one which may not be the same as the
8546 user's desired From: header.
8548 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8550 The Mutt Next Generation E-Mail Client 162
8558 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8559 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8560 _
\bm_
\ba_
\bi_
\bl (section 7.4.263 , page 152)'', and any associated variables.
8562 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8570 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8571 7.4.306 , page 162)'' is set, but this variable is not, you will be prompted
8572 for a password when sending.
8574 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8575 the superuser of your machine may read it regardless of the file's permissions.
8577 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8585 Defines the port that the SMTP host is listening on for mail delivery. Must be
8586 specified as a number.
8588 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8589 will probably desire 587, the mail submission port.
8591 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8597 Availability: SMTP (and SSL)
8599 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8600 server does not support STARTTLS or there is an error in the TLS Handshake, the
8601 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8602 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8603 port enabled in order to use it.
8605 The Mutt Next Generation E-Mail Client 163
8607 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8615 Defines the username to use with SMTP AUTH. Setting this variable will cause
8616 Mutt-ng to attempt to use SMTP AUTH when sending.
8618 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bo_
\br_
\bt
8624 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8629 mailbox-order (unsorted)
8637 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8638 (example: set sort=reverse-date-sent).
8640 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8646 Specifies how the entries in the ``alias'' menu are sorted. The following are
8649 address (sort alphabetically by email address)
8650 alias (sort alphabetically by alias name)
8651 unsorted (leave in order specified in .muttrc)
8653 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8657 The Mutt Next Generation E-Mail Client 164
8661 When sorting by threads, this variable controls how threads are sorted in rela-
8662 tion to other threads, and how the branches of the thread trees are sorted.
8663 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.307 , page 163)'' can,
8664 except threads (in that case, Mutt-ng will just use date-sent). You can also
8665 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8666 come after reverse-. The last- prefix causes messages to be sorted against its
8667 siblings by which has the last descendant, using the rest of sort_aux as an
8670 For instance, set sort_aux=last-date-received would mean that if a new message
8671 is received in a thread, that thread becomes the last one displayed (or the
8672 first, if you have set sort=reverse-threads.)
8674 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.307 , page 163)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8675 (section 7.4.309 , page 163) is reversed again (which is not the right thing
8676 to do, but kept to not break any existing configuration setting).
8678 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8684 Specifies how to sort entries in the file browser. By default, the entries are
8685 sorted alphabetically. Valid values:
8687 alpha (alphabetically)
8692 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8693 (example: set sort_browser=reverse-date).
8695 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8701 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
8702 (section 7.4.328 , page 170)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8703 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.311 ,
8704 page 164) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8705 sage by subject if the subject of the child message starts with a substring
8706 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.247 , page 149)''. With
8707 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.311 , page 164) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8708 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
8709 7.4.247 , page 149)'' parts of both messages are identical.
8711 The Mutt Next Generation E-Mail Client 165
8713 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8719 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.312 , page 164)'' controls what happens when
8720 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8721 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8722 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.312 ,
8723 page 164)'' as a separator.
8725 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8731 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8732 you can specify its location with this variable. Mutt-ng will automatically
8733 set this variable to the value of the environment variable $MAIL if it is not
8736 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\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
8742 This variable specifies a file containing trusted CA certificates. Any server
8743 certificate that is signed with one of these CA certificates are also automati-
8746 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8748 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8756 The file containing a client certificate and its associated private key.
8758 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8764 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8765 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8766 server does not advertise the capability, since it would otherwise have to
8768 The Mutt Next Generation E-Mail Client 166
8770 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8771 7.4.318 , page 166)''.
8773 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8779 Availability: GNUTLS
8781 This variable specifies the minimum acceptable prime size (in bits) for use in
8782 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8785 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8791 Availability: SSL or GNUTLS
8793 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8794 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8795 regardless of the server's capabilities.
8797 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8805 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8808 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8814 Availability: SSL or GNUTLS
8816 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8819 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8825 The Mutt Next Generation E-Mail Client 167
8827 Availability: SSL or GNUTLS
8829 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8832 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8840 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8841 store when checking if server certificate is signed by a trusted CA.
8843 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8849 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8850 tion 7.4.324 , page 167)''. The first character is used when the mailbox is
8851 unchanged. The second is used when the mailbox has been changed, and it needs
8852 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8853 if the mailbox will not be written when exiting that mailbox (You can toggle
8854 whether to write changes to a mailbox with the toggle-write operation, bound by
8855 default to ``%''). The fourth is used to indicate that the current folder has
8856 been opened in attach-message mode (Certain operations like composing a new
8857 mail, replying, forwarding, etc. are not permitted in this mode).
8859 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8863 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8864 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8865 %l?]---(%s/%S)-%>-(%P)---'
8867 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8868 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.116 , page 116)'', but has
8869 its own set of printf(3)-like sequences:
8872 number of mailboxes with new mail *
8875 the short pathname of the current mailbox
8878 number of deleted messages *
8880 The Mutt Next Generation E-Mail Client 168
8883 the full pathname of the current mailbox
8886 number of flagged messages *
8892 size (in bytes) of the current mailbox *
8895 size (in bytes) of the messages shown (i.e., which match the cur-
8899 the number of messages in the mailbox *
8902 the number of messages shown (i.e., which match the current limit)
8906 number of new messages in the mailbox *
8909 number of old unread messages *
8912 number of postponed messages *
8915 percentage of the way through the index
8918 modified/read-only/won't-write/attach-message indicator, according
8919 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.323 , page 167)
8922 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.307 , page 163))
8925 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.309 , page
8929 number of tagged messages *
8932 number of unread messages *
8935 Mutt-ng version string
8937 The Mutt Next Generation E-Mail Client 169
8940 currently active limit pattern, if any *
8943 right justify the rest of the string and pad with 'X'
8946 pad to the end of the line with 'X'
8948 * = can be optionally printed if nonzero
8950 Some of the above sequences can be used to optionally print a string if their
8951 value is nonzero. For example, you may only want to see the number of flagged
8952 messages if such messages exist, since zero is not particularly meaningful. To
8953 optionally print a string based upon one of the above sequences, the following
8956 %?<sequence_char>?<optional_string>?
8958 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
8959 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
8960 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8963 Here is an example illustrating how to optionally print the number of new mes-
8966 %?n?%n new messages.?
8968 Additionally you can switch between two strings, the first one, if a value is
8969 zero, the second one, if the value is nonzero, by using the following con-
8972 %?<sequence_char>?<if_string>&<else_string>?
8974 You can additionally force the result of any printf(3)-like sequence to be low-
8975 ercase by prefixing the sequence character with an underscore (_) sign. For
8976 example, if you want to display the local hostname in lowercase, you would use:
8980 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8981 replace any dots in the expansion by underscores. This might be helpful with
8982 IMAP folders that don't like dots in folder names.
8984 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8990 Setting this variable causes the ``status bar'' to be displayed on the first
8991 line of the screen rather than near the bottom.
8993 The Mutt Next Generation E-Mail Client 170
8995 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
9001 With mailto: style links, a body as well as arbitrary header information may be
9002 embedded. This may lead to (user) headers being overwriten without note if
9003 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103)'' is unset.
9005 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
9006 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
9007 message including headers will be shown in the editor regardless of what
9008 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 103)'' is set to.
9010 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
9016 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
9017 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
9018 messages are often generated by old mailers or buggy mailers like MS Outlook
9019 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.13 , page 92).
9021 This option also replaces linear-white-space between encoded-word and *text to
9022 a single space to prevent the display of MIME-encoded ``Subject:'' header field
9023 from being devided into multiple lines.
9025 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
9031 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
9032 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.307 , page 163)'' by mes-
9033 sage threads. By default, messages with the same subject are grouped together
9034 in ``pseudo threads.'' This may not always be desirable, such as in a personal
9035 mailbox where you might have several unrelated messages with the subject ``hi''
9036 which will get grouped together.
9038 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
9044 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
9045 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.330 , page 170) when replying. This is
9046 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
9049 The Mutt Next Generation E-Mail Client 171
9051 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
9053 Type: regular expression
9055 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
9057 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.329 , page 170) is _
\bs_
\be_
\bt, mutt-ng
9058 will remove this trailing part of the ``Subject'' line when replying if it
9059 won't be empty afterwards.
9061 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
9067 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
9068 i.e. a space will be inserted between the quote characters and the actual text.
9070 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
9076 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
9077 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
9078 mand like ``xterm -e muttng.''
9080 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
9086 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
9087 format is easier to handle for some mailing software, and generally just looks
9088 like ordinary text. To actually make use of this format's features, you'll
9089 need support in your editor.
9091 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.115 , page 116) is ignored when this
9094 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9100 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
9101 tion 7.2 , page 84)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
9102 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
9103 as they appear in the folder.
9105 The Mutt Next Generation E-Mail Client 172
9107 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
9113 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
9114 messages by subject.
9116 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bt_
\bi_
\bl_
\bd_
\be
9122 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
9125 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
9131 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
9132 pressed in the main menu before timing out and checking for new mail. A value
9133 of zero or less will cause Mutt-ng to never time out.
9135 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
9141 This variable allows you to specify where Mutt-ng will place its temporary
9142 files needed for displaying and composing messages. If this variable is not
9143 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
9146 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
9152 Controls the character used to indicate mail addressed to you. The first char-
9153 acter is the one used when the mail is NOT addressed to your address (default:
9154 space). The second is used when you are the only recipient of the message
9155 (default: +). The third is when your address appears in the ``To:'' header
9156 field, but you are not the only recipient of the message (default: T). The
9157 fourth character is used when your address is specified in the ``Cc:'' header
9158 field, but you are not the only recipient. The fifth character is used to
9159 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
9160 when a mail was sent to a mailing-list you're subscribe to (default: L).
9162 The Mutt Next Generation E-Mail Client 173
9164 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bt_
\br_
\ba_
\bs_
\bh
9170 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
9171 marked for deletion will be moved, instead of being irremediably purged.
9173 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
9174 that there is no way to recover mail.
9176 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
9182 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
9183 a raw socket. You may be able to use this to set up preauthenticated connec-
9184 tions to your IMAP/POP3 server. Example:
9186 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
9188 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
9189 without having to enter a password.
9191 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bu_
\bm_
\ba_
\bs_
\bk
9197 This sets the umask that will be used by Mutt-ng when creating all kinds of
9198 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
9200 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
9206 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
9207 rent thread is _
\bu_
\bncollapsed.
9209 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
9215 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
9216 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
9217 with the SMTP support via libESMTP. Otherwise you may not be able to send
9219 The Mutt Next Generation E-Mail Client 174
9223 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.263 , page
9224 152)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
9225 negotiation or tell libESMTP to do so.
9227 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
9233 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
9234 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.95 , page 111)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
9235 no addresses will be qualified.
9237 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b6 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
9243 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
9244 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
9245 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 38)'' command.
9247 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b7 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
9255 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
9257 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
9260 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b8 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
9266 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
9267 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
9268 mally, the default should work.
9270 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b9 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
9276 The Mutt Next Generation E-Mail Client 175
9278 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
9281 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b0 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
9287 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-
9288 _
\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.
9290 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
9291 79)'', provided that the corresponding mailcap entry has a needsterminal flag,
9292 and the external program is interactive.
9294 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
9295 a key only if the external command returned a non-zero status.
9297 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b1 _
\bw_
\be_
\be_
\bd
9303 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
9304 replying to messages.
9306 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b2 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9312 Controls whether searches wrap around the end of the mailbox.
9314 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
9315 searches will not wrap.
9317 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b3 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
9323 Controls the size of the margin remaining at the right side of the terminal
9324 when Mutt-ng's pager does smart wrapping.
9326 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b4 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
9332 The Mutt Next Generation E-Mail Client 176
9334 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
9335 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
9337 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b5 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
9343 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
9344 indicate progress. If set to 0, only a single message will be displayed before
9347 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.242 , page 147)'' variable.
9349 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b6 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
9353 Default: 'M%?n?AIL&ail?'
9355 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-
9356 tion 7.4.358 , page 176) is _
\bs_
\be_
\bt. This string is identical in formatting to the
9357 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.324 , page 167)''.
9359 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b7 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
9365 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.358 , page 176) is _
\bs_
\be_
\bt, this string will be
9366 used to set the title when leaving mutt-ng. For terminal-based programs,
9367 there's no easy and portable way to read the current title so mutt-ng cannot
9368 read it upon startup and restore it when exiting.
9370 Based on the xterm FAQ, the following might work:
9372 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9375 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b8 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9381 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9382 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9385 _
\b7_
\b._
\b4_
\b._
\b3_
\b5_
\b9 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9389 The Mutt Next Generation E-Mail Client 177
9391 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9393 Controls the format of the title bar of the xterm provided that
9394 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.358 , page 176) has been _
\bs_
\be_
\bt. This string is
9395 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.324 ,
9398 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9400 The following is the list of available functions listed by the mapping in which
9401 they are available. The default key setting is given, and an explanation of
9402 what the function does. The key bindings of these functions can be changed
9403 with the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 27) command.
9405 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9407 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9408 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9409 tings for this menu will affect the default bindings for all menus (except as
9412 bottom-page L move to the bottom of the page
9413 current-bottom not bound move current entry to bottom of page
9414 current-middle not bound move current entry to middle of page
9415 current-top not bound move current entry to top of page
9416 enter-command : enter a muttngrc command
9417 exit q exit this menu
9418 first-entry = move to the first entry
9419 half-down ] scroll down 1/2 page
9420 half-up [ scroll up 1/2 page
9422 jump number jump to an index number
9423 last-entry * move to the last entry
9424 middle-page M move to the middle of the page
9425 next-entry j move to the next entry
9426 next-line > scroll down one line
9427 next-page z move to the next page
9428 previous-entry k move to the previous entry
9429 previous-line < scroll up one line
9430 previous-page Z move to the previous page
9431 refresh ^L clear and redraw the screen
9432 search / search for a regular expression
9433 search-next n search for next match
9434 search-opposite not bound search for next match in opposite direction
9435 search-reverse ESC / search backwards for a regular expression
9436 select-entry RET select the current entry
9437 shell-escape ! run a program in a subshell
9438 tag-entry t toggle the tag on the current entry
9439 tag-prefix ; apply next command to tagged entries
9440 tag-prefix-cond not bound apply next function ONLY to tagged messages
9441 top-page H move to the top of the page
9442 what-key not bound display the keycode for a key press
9444 The Mutt Next Generation E-Mail Client 178
9446 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9448 The Mutt Next Generation E-Mail Client 179
9450 bounce-message b remail a message to another user
9451 change-folder c open a different folder
9452 change-folder-readonly ESC c open a different folder in read only mode
9453 check-traditional-pgp ESC P check for classic pgp
9454 clear-flag W clear a status flag from a message
9455 copy-message C copy a message to a file/mailbox
9456 create-alias a create an alias from a message sender
9457 decode-copy ESC C decode a message and copy it to a file/mailbox
9458 decode-save ESC s decode a message and save it to a file/mailbox
9459 delete-message d delete the current entry
9460 delete-pattern D delete messages matching a pattern
9461 delete-subthread ESC d delete all messages in subthread
9462 delete-thread ^D delete all messages in thread
9463 display-address @ display full address of sender
9464 display-toggle-weed h display message and toggle header weeding
9465 display-message RET display a message
9466 edit e edit the current message
9467 edit-type ^E edit the current message's Content-Type
9468 exit x exit without saving changes
9469 extract-keys ^K extract PGP public keys
9470 fetch-mail G retrieve mail from POP server
9471 flag-message F toggle a message's 'important' flag
9472 forget-passphrase ^F wipe PGP passphrase from memory
9473 forward-message f forward a message with comments
9474 group-reply g reply to all recipients
9475 limit l show only messages matching a pattern
9476 list-reply L reply to specified mailing list
9477 mail m compose a new mail message
9478 mail-key ESC k mail a PGP public key
9479 next-new TAB jump to the next new message
9480 next-subthread ESC n jump to the next subthread
9481 next-thread ^N jump to the next thread
9482 next-undeleted j move to the next undeleted message
9483 next-unread not bound jump to the next unread message
9484 parent-message P jump to parent message in thread
9485 pipe-message | pipe message/attachment to a shell command
9486 previous-new ESC TAB jump to the previous new message
9487 previous-page Z move to the previous page
9488 previous-subthread ESC p jump to previous subthread
9489 previous-thread ^P jump to previous thread
9490 previous-undeleted k move to the last undelete message
9491 previous-unread not bound jump to the previous unread message
9492 print-message p print the current entry
9493 query Q query external program for addresses
9494 quit q save changes to mailbox and quit
9495 read-subthread ESC r mark the current subthread as read
9496 read-thread ^R mark the current thread as read
9497 recall-message R recall a postponed message
9498 reply r reply to a message
9499 resend-message ESC e resend message and preserve MIME structure
9500 save-message s save message/attachment to a file
9501 set-flag w set a status flag on a message
9502 show-version V show the Mutt-ng version number and date
9503 show-limit ESC l show currently active limit pattern, if any
9505 The Mutt Next Generation E-Mail Client 180
9507 sort-mailbox o sort messages
9508 sort-reverse O sort messages in reverse order
9509 sync-mailbox $ save changes to mailbox
9510 tag-pattern T tag messages matching a pattern
9511 tag-thread ESC t tag/untag all messages in the current thread
9512 toggle-new N toggle a message's 'new' flag
9513 toggle-write % toggle whether the mailbox will be rewritten
9514 undelete-message u undelete the current entry
9515 undelete-pattern U undelete messages matching a pattern
9516 undelete-subthread ESC u undelete all messages in subthread
9517 undelete-thread ^U undelete all messages in thread
9518 untag-pattern ^T untag messages matching a pattern
9519 view-attachments v show MIME attachments
9521 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9523 The Mutt Next Generation E-Mail Client 181
9525 bottom not bound jump to the bottom of the message
9526 bounce-message b remail a message to another user
9527 change-folder c open a different folder
9528 change-folder-readonly ESC c open a different folder in read only mode
9529 check-traditional-pgp ESC P check for classic pgp
9530 copy-message C copy a message to a file/mailbox
9531 create-alias a create an alias from a message sender
9532 decode-copy ESC C decode a message and copy it to a file/mailbox
9533 decode-save ESC s decode a message and save it to a file/mailbox
9534 delete-message d delete the current entry
9535 delete-subthread ESC d delete all messages in subthread
9536 delete-thread ^D delete all messages in thread
9537 display-address @ display full address of sender
9538 display-toggle-weed h display message and toggle header weeding
9539 edit e edit the current message
9540 edit-type ^E edit the current message's Content-Type
9541 enter-command : enter a muttngrc command
9542 exit i return to the main-menu
9543 extract-keys ^K extract PGP public keys
9544 flag-message F toggle a message's 'important' flag
9545 forget-passphrase ^F wipe PGP passphrase from memory
9546 forward-message f forward a message with comments
9547 group-reply g reply to all recipients
9548 half-up not bound move up one-half page
9549 half-down not bound move down one-half page
9551 list-reply L reply to specified mailing list
9552 mail m compose a new mail message
9553 mail-key ESC k mail a PGP public key
9554 mark-as-new N toggle a message's 'new' flag
9555 next-line RET scroll down one line
9556 next-entry J move to the next entry
9557 next-new TAB jump to the next new message
9558 next-page move to the next page
9559 next-subthread ESC n jump to the next subthread
9560 next-thread ^N jump to the next thread
9561 next-undeleted j move to the next undeleted message
9562 next-unread not bound jump to the next unread message
9563 parent-message P jump to parent message in thread
9564 pipe-message | pipe message/attachment to a shell command
9565 previous-line BackSpace scroll up one line
9566 previous-entry K move to the previous entry
9567 previous-new not bound jump to the previous new message
9568 previous-page - move to the previous page
9569 previous-subthread ESC p jump to previous subthread
9570 previous-thread ^P jump to previous thread
9571 previous-undeleted k move to the last undelete message
9572 previous-unread not bound jump to the previous unread message
9573 print-message p print the current entry
9574 quit Q save changes to mailbox and quit
9575 read-subthread ESC r mark the current subthread as read
9576 read-thread ^R mark the current thread as read
9577 recall-message R recall a postponed message
9578 redraw-screen ^L clear and redraw the screen
9580 The Mutt Next Generation E-Mail Client 182
9582 reply r reply to a message
9583 save-message s save message/attachment to a file
9584 search / search for a regular expression
9585 search-next n search for next match
9586 search-opposite not bound search for next match in opposite direction
9587 search-reverse ESC / search backwards for a regular expression
9588 search-toggle \ toggle search pattern coloring
9589 shell-escape ! invoke a command in a subshell
9590 show-version V show the Mutt-ng version number and date
9591 skip-quoted S skip beyond quoted text
9592 sync-mailbox $ save changes to mailbox
9593 tag-message t tag a message
9594 toggle-quoted T toggle display of quoted text
9595 top ^ jump to the top of the message
9596 undelete-message u undelete the current entry
9597 undelete-subthread ESC u undelete all messages in subthread
9598 undelete-thread ^U undelete all messages in thread
9599 view-attachments v show MIME attachments
9601 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9603 search / search for a regular expression
9604 search-next n search for next match
9605 search-reverse ESC / search backwards for a regular expression
9607 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9609 create-alias a create an alias from a message sender
9610 mail m compose a new mail message
9611 query Q query external program for addresses
9612 query-append A append new query results to current results
9613 search / search for a regular expression
9614 search-next n search for next match
9615 search-opposite not bound search for next match in opposite direction
9616 search-reverse ESC / search backwards for a regular expression
9618 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9620 The Mutt Next Generation E-Mail Client 183
9622 bounce-message b remail a message to another user
9623 collapse-parts v toggle display of subparts
9624 delete-entry d delete the current entry
9625 display-toggle-weed h display message and toggle header weeding
9626 edit-type ^E edit the current entry's Content-Type
9627 extract-keys ^K extract PGP public keys
9628 forward-message f forward a message with comments
9629 group-reply g reply to all recipients
9630 list-reply L reply to specified mailing list
9631 pipe-entry | pipe message/attachment to a shell command
9632 print-entry p print the current entry
9633 reply r reply to a message
9634 resend-message ESC e resend message and preserve MIME structure
9635 save-entry s save message/attachment to a file
9636 undelete-entry u undelete the current entry
9637 view-attach RET view attachment using mailcap entry if necessary
9638 view-mailcap m force viewing of attachment using mailcap
9639 view-text T view attachment as text
9641 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9643 The Mutt Next Generation E-Mail Client 184
9645 attach-file a attach a file(s) to this message
9646 attach-message A attach message(s) to this message
9647 attach-key ESC k attach a PGP public key
9648 copy-file C save message/attachment to a file
9649 detach-file D delete the current entry
9650 display-toggle-weed h display message and toggle header weeding
9651 edit-bcc b edit the BCC list
9652 edit-cc c edit the CC list
9653 edit-description d edit attachment description
9654 edit-encoding ^E edit attachment transfer-encoding
9655 edit-fcc f enter a file to save a copy of this message in
9656 edit-from ESC f edit the from: field
9657 edit-file ^X e edit the file to be attached
9658 edit-headers E edit the message with headers
9659 edit e edit the message
9660 edit-mime m edit attachment using mailcap entry
9661 edit-reply-to r edit the Reply-To field
9662 edit-subject s edit the subject of this message
9663 edit-to t edit the TO list
9664 edit-type ^T edit attachment type
9665 filter-entry F filter attachment through a shell command
9666 forget-passphrase ^F wipe PGP passphrase from memory
9667 ispell i run ispell on the message
9668 new-mime n compose new attachment using mailcap entry
9669 pgp-menu p show PGP options
9670 pipe-entry | pipe message/attachment to a shell command
9671 postpone-message P save this message to send later
9672 print-entry l print the current entry
9673 rename-file R rename/move an attached file
9674 send-message y send the message
9675 toggle-unlink u toggle whether to delete file after sending it
9676 view-attach RET view attachment using mailcap entry if necessary
9677 write-fcc w write the message to a folder
9679 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9681 delete-entry d delete the current entry
9682 undelete-entry u undelete the current entry
9684 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9686 The Mutt Next Generation E-Mail Client 185
9688 change-dir c change directories
9689 check-new TAB check mailboxes for new mail
9690 enter-mask m enter a file mask
9691 search / search for a regular expression
9692 search-next n search for next match
9693 search-reverse ESC / search backwards for a regular expression
9694 select-new N select a new file in this directory
9695 sort o sort messages
9696 sort-reverse O sort messages in reverse order
9697 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9698 view-file SPACE view file
9699 subscribe s subscribe to current mailbox (IMAP Only)
9700 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9701 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9703 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9705 view-name % view the key's user id
9706 verify-key c verify a PGP public key
9708 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9710 backspace BackSpace delete the char in front of the cursor
9711 backward-char ^B move the cursor one character to the left
9712 backward-word ESC b move the cursor to the previous word
9713 bol ^A jump to the beginning of the line
9714 buffy-cycle Space cycle among incoming mailboxes
9715 capitalize-word ESC c uppercase the first character in the word
9716 complete TAB complete filename or alias
9717 complete-query ^T complete address with query
9718 delete-char ^D delete the char under the cursor
9719 downcase-word ESC l lowercase all characters in current word
9720 eol ^E jump to the end of the line
9721 forward-char ^F move the cursor one character to the right
9722 forward-word ESC f move the cursor to the next word
9723 history-down not bound scroll down through the history list
9724 history-up not bound scroll up through the history list
9725 kill-eol ^K delete chars from cursor to end of line
9726 kill-eow ESC d delete chars from cursor to end of word
9727 kill-line ^U delete all chars on the line
9728 kill-word ^W delete the word in front of the cursor
9729 quote-char ^V quote the next typed key
9730 transpose-chars not bound transpose character under cursor with previous
9731 upcase-word ESC u uppercase all characters in current word
9733 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9735 The Mutt Next Generation E-Mail Client 186
9737 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9739 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9740 back in the ELM-ME days.
9742 The following people have been very helpful to the development of Mutt:
9744 Vikas Agnihotri <vikasa@writeme.com>,
9746 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9748 Aric Blumer <aric@fore.com>,
9750 John Capo <jc@irbs.com>,
9752 David Champion <dgc@uchicago.edu,
9754 Brendan Cully <brendan@kublai.com>,
9756 Liviu Daia <daia@stoilow.imar.ro>,
9758 Thomas E. Dickey <dickey@herndon4.his.com>,
9760 David DeSimone <fox@convex.hp.com>,
9762 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9764 Ruslan Ermilov <ru@freebsd.org>,
9766 Edmund Grimley Evans <edmundo@rano.org,
9768 Michael Finken <finken@conware.de>,
9770 Sven Guckes <guckes@math.fu-berlin.de>,
9772 Lars Hecking <lhecking@nmrc.ie>,
9774 Mark Holloman <holloman@nando.net>,
9776 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9778 Marco d'Itri <md@linux.it>,
9780 Bjrn Jacke <bjacke@suse.com>,
9782 Byrial Jensen <byrial@image.dk>,
9784 David Jeske <jeske@igcom.net>,
9786 Christophe Kalt <kalt@hugo.int-evry.fr>,
9788 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9790 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9792 The Mutt Next Generation E-Mail Client 187
9794 Brandon Long <blong@fiction.net>,
9796 Jimmy Mkel <jmy@flashback.net>,
9798 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9800 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9802 Andrew W. Nosenko <awn@bcs.zp.ua>,
9804 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9806 Clint Olsen <olsenc@ichips.intel.com>,
9808 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9810 Thomas Parmelan <tom@ankh.fr.eu.org>,
9812 Ollivier Robert <roberto@keltia.freenix.fr>,
9814 Thomas Roessler <roessler@does-not-exist.org>,
9816 Roland Rosenfeld <roland@spinnaker.de>,
9818 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9820 Allain Thivillon <Allain.Thivillon@alma.fr>,
9822 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9824 Vsevolod Volkov <vvv@lucky.net>,
9826 Ken Weinert <kenw@ihs.com>
9828 Mutt-ng is developed by the following people:
9830 Andreas Krennmair <ak@synflood.at>
9832 Nico Golde <nico@ngolde.de>
9834 Rocco Rutte <pdmef@cs.tu-berlin.de>
9836 The following people have been very helpful to the development of Mutt-ng:
9838 Christian Gall <cg@cgall.de>
9840 Iain Lea <iain@bricbrac.de>
9842 Andreas Kneib <akneib@gmx.net>
9844 Carsten Schoelzki <cjs@weisshuhn.de>
9846 Elimar Riesebieter <riesebie@lxtec.de>
9848 The Mutt Next Generation E-Mail Client 188
9850 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9852 This document was written in SGML, and then rendered using the sgml-tools pack-
9855 The Mutt Next Generation E-Mail Client 189
9859 1. Introduction .......................................................... 1
9860 1.1 Overview ........................................................ 1
9861 1.2 Mutt-ng Home Page ............................................... 1
9862 1.3 Mailing Lists ................................................... 1
9863 1.4 Software Distribution Sites ..................................... 2
9864 1.5 IRC ............................................................. 2
9865 1.6 Weblog .......................................................... 2
9866 1.7 Copyright ....................................................... 2
9868 2. Getting Started ..................................................... 2
9869 2.1 Basic Concepts .............................................. 2
9870 2.1.1 Screens and Menus 3
9871 2.1.2 Configuration 3
9874 2.1.5 Modularization 4
9876 2.2 Screens and Menus ........................................... 4
9879 2.2.3 File Browser 5
9882 2.2.6 Compose Menu 6
9884 2.2.8 Attachment Menu 6
9886 2.3 Moving Around in Menus .......................................... 6
9887 2.4 Editing Input Fields ............................................ 7
9888 2.5 Reading Mail - The Index and Pager .............................. 8
9889 2.5.1 The Message Index 8
9891 2.5.3 Threaded Mode 11
9892 2.5.4 Miscellaneous Functions 11
9893 2.6 Sending Mail ................................................... 14
9894 2.6.1 Composing new messages 14
9896 2.6.3 Editing the message header 17
9897 2.6.4 Using Mutt-ng with PGP 18
9898 2.6.5 Sending anonymous messages via mixmaster 19
9899 2.7 Forwarding and Bouncing Mail ................................... 19
9900 2.8 Postponing Mail ................................................ 20
9902 3. Configuration ........................................................ 21
9903 3.1 Locations of Configuration Files ............................... 21
9904 3.2 Basic Syntax of Initialization Files ........................... 21
9905 3.3 Expansion within variables ................................... 23
9906 3.3.1 Commands' Output 23
9907 3.3.2 Environment Variables 23
9911 3.3.3 Configuration Variables 23
9912 3.3.4 Self-Defined Variables 24
9913 3.3.5 Pre-Defined Variables 25
9914 3.3.6 Type Conversions 26
9915 3.4 Defining/Using aliases ......................................... 26
9916 3.5 Changing the default key bindings .............................. 27
9917 3.6 Defining aliases for character sets ........................... 29
9918 3.7 Setting variables based upon mailbox ........................... 29
9919 3.8 Keyboard macros ................................................ 30
9920 3.9 Using color and mono video attributes .......................... 31
9921 3.10 Ignoring (weeding) unwanted message headers .................... 33
9922 3.11 Alternative addresses .......................................... 34
9923 3.12 Format = Flowed .............................................. 34
9924 3.12.1 Introduction 34
9925 3.12.2 Receiving: Display Setup 34
9927 3.12.4 Additional Notes 36
9928 3.13 Mailing lists .................................................. 36
9929 3.14 Using Multiple spool mailboxes ................................. 37
9930 3.15 Defining mailboxes which receive mail .......................... 37
9931 3.16 User defined headers ........................................... 38
9932 3.17 Defining the order of headers when viewing messages ............ 39
9933 3.18 Specify default save filename .................................. 39
9934 3.19 Specify default Fcc: mailbox when composing .................... 39
9935 3.20 Specify default save filename and default Fcc: mailbox at once . 40
9936 3.21 Change settings based upon message recipients .................. 40
9937 3.22 Change settings before formatting a message .................... 41
9938 3.23 Choosing the cryptographic key of the recipient ................ 41
9939 3.24 Adding key sequences to the keyboard buffer .................... 41
9940 3.25 Executing functions ............................................ 42
9941 3.26 Message Scoring ................................................ 42
9942 3.27 Spam detection ................................................. 43
9943 3.28 Setting variables .............................................. 45
9944 3.29 Reading initialization commands from another file .............. 46
9945 3.30 Removing hooks ................................................. 46
9946 3.31 Sharing Setups ............................................. 46
9947 3.31.1 Character Sets 46
9948 3.31.2 Modularization 47
9949 3.31.3 Conditional parts 47
9950 3.32 Obsolete Variables ............................................. 49
9952 4. Advanced Usage ....................................................... 49
9953 4.1 Regular Expressions ............................................ 49
9954 4.2 Patterns ....................................................... 52
9955 4.2.1 Complex Patterns 52
9956 4.2.2 Patterns and Dates 53
9957 4.3 Format Strings ............................................. 53
9958 4.3.1 Introduction 53
9959 4.3.2 Conditional Expansion 55
9960 4.3.3 Modifications and Padding 56
9961 4.4 Using Tags ..................................................... 56
9962 4.5 Using Hooks .................................................... 57
9963 4.5.1 Message Matching in Hooks 58
9967 4.6 Using the sidebar .............................................. 58
9968 4.7 External Address Queries ....................................... 59
9969 4.8 Mailbox Formats ................................................ 60
9970 4.9 Mailbox Shortcuts .............................................. 61
9971 4.10 Handling Mailing Lists ......................................... 61
9972 4.11 Editing threads ................................................ 62
9973 4.11.1 Linking threads 63
9974 4.11.2 Breaking threads 63
9975 4.12 Delivery Status Notification (DSN) Support ..................... 63
9976 4.13 POP3 Support (OPTIONAL) ........................................ 63
9977 4.14 IMAP Support (OPTIONAL) ........................................ 64
9978 4.14.1 The Folder Browser 65
9979 4.14.2 Authentication 65
9980 4.15 NNTP Support (OPTIONAL) ........................................ 66
9981 4.15.1 Again: Scoring 66
9982 4.16 SMTP Support (OPTIONAL) ........................................ 67
9983 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 68
9984 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 68
9985 4.19 Compressed folders Support (OPTIONAL) .......................... 68
9986 4.19.1 Open a compressed mailbox for reading 69
9987 4.19.2 Write a compressed mailbox 69
9988 4.19.3 Append a message to a compressed mailbox 70
9989 4.19.4 Encrypted folders 71
9991 5. Mutt-ng's MIME Support ............................................... 71
9992 5.1 Using MIME in Mutt ............................................. 71
9993 5.1.1 Viewing MIME messages in the pager 71
9994 5.1.2 The Attachment Menu 72
9995 5.1.3 The Compose Menu 72
9996 5.2 MIME Type configuration with mime.types ........................ 72
9997 5.3 MIME Viewer configuration with mailcap ......................... 73
9998 5.3.1 The Basics of the mailcap file 74
9999 5.3.2 Secure use of mailcap 75
10000 5.3.3 Advanced mailcap Usage 75
10001 5.3.4 Example mailcap files 78
10002 5.4 MIME Autoview .................................................. 79
10003 5.5 MIME Multipart/Alternative ..................................... 80
10004 5.6 MIME Lookup .................................................... 80
10006 6. Security Considerations ............................................ 81
10007 6.1 Passwords .................................................. 81
10008 6.2 Temporary Files ............................................ 81
10009 6.3 Information Leaks ............................................ 81
10010 6.3.1 Message-ID: headers 81
10011 6.3.2 mailto:-style links 82
10012 6.4 External applications ...................................... 82
10016 7. Reference ............................................................ 83
10017 7.1 Command line options ........................................... 83
10018 7.2 Patterns ....................................................... 84
10019 7.3 Configuration Commands ......................................... 86
10023 7.4 Configuration variables .......................................... 88
10024 7.4.1 abort_noattach 89
10025 7.4.2 abort_nosubject 90
10026 7.4.3 abort_unmodified 90
10027 7.4.4 agent_string 90
10028 7.4.5 alias_file 90
10029 7.4.6 alias_format 90
10030 7.4.7 allow_8bit 91
10031 7.4.8 allow_ansi 91
10032 7.4.9 arrow_cursor 91
10033 7.4.10 ascii_chars 92
10036 7.4.13 assumed_charset 92
10037 7.4.14 attach_format 92
10038 7.4.15 attach_remind_regexp 93
10039 7.4.16 attach_sep 94
10040 7.4.17 attach_split 94
10041 7.4.18 attribution 94
10047 7.4.24 bounce_delivered 95
10048 7.4.25 braille_friendly 95
10049 7.4.26 certificate_file 96
10051 7.4.28 check_new 96
10052 7.4.29 collapse_unread 96
10053 7.4.30 compose_format 97
10054 7.4.31 config_charset 97
10055 7.4.32 confirmappend 97
10056 7.4.33 confirmcreate 97
10057 7.4.34 connect_timeout 97
10058 7.4.35 content_type 98
10060 7.4.37 crypt_autoencrypt 98
10061 7.4.38 crypt_autopgp 98
10062 7.4.39 crypt_autosign 99
10063 7.4.40 crypt_autosmime 99
10064 7.4.41 crypt_replyencrypt 99
10065 7.4.42 crypt_replysign 99
10066 7.4.43 crypt_replysignencrypted 99
10067 7.4.44 crypt_timestamp 100
10068 7.4.45 crypt_use_gpgme 100
10069 7.4.46 crypt_verify_sig 100
10070 7.4.47 date_format 100
10071 7.4.48 debug_level 101
10072 7.4.49 default_hook 101
10074 7.4.51 delete_space 101
10075 7.4.52 delete_untag 102
10079 7.4.53 digest_collapse 102
10080 7.4.54 display_filter 102
10081 7.4.55 dotlock_program 102
10082 7.4.56 dsn_notify 102
10083 7.4.57 dsn_return 103
10084 7.4.58 duplicate_threads 103
10085 7.4.59 edit_headers 103
10087 7.4.61 editor_headers 103
10088 7.4.62 encode_from 104
10089 7.4.63 entropy_file 104
10090 7.4.64 envelope_from 104
10092 7.4.66 fast_reply 105
10093 7.4.67 fcc_attach 105
10094 7.4.68 fcc_clear 105
10095 7.4.69 file_charset 105
10097 7.4.71 folder_format 106
10098 7.4.72 followup_to 107
10099 7.4.73 force_buffy_check 107
10100 7.4.74 force_name 107
10101 7.4.75 forward_decode 107
10102 7.4.76 forward_decrypt 108
10103 7.4.77 forward_edit 108
10104 7.4.78 forward_format 108
10105 7.4.79 forward_quote 108
10107 7.4.81 gecos_mask 109
10110 7.4.84 header_cache 109
10111 7.4.85 header_cache_compress 110
10113 7.4.87 hidden_host 110
10114 7.4.88 hide_limited 110
10115 7.4.89 hide_missing 110
10116 7.4.90 hide_thread_subject 111
10117 7.4.91 hide_top_limited 111
10118 7.4.92 hide_top_missing 111
10120 7.4.94 honor_followup_to 111
10121 7.4.95 hostname 112
10122 7.4.96 ignore_list_reply_to 112
10123 7.4.97 imap_authenticators 112
10124 7.4.98 imap_check_subscribed 112
10125 7.4.99 imap_delim_chars 113
10126 7.4.100 imap_headers 113
10127 7.4.101 imap_home_namespace 113
10128 7.4.102 imap_keepalive 113
10129 7.4.103 imap_list_subscribed 114
10130 7.4.104 imap_login 114
10131 7.4.105 imap_mail_check 114
10135 7.4.106 imap_pass 114
10136 7.4.107 imap_passive 115
10137 7.4.108 imap_peek 115
10138 7.4.109 imap_reconnect 115
10139 7.4.110 imap_servernoise 115
10140 7.4.111 imap_user 116
10141 7.4.112 implicit_autoview 116
10142 7.4.113 include 116
10143 7.4.114 include_onlyfirst 116
10144 7.4.115 indent_string 116
10145 7.4.116 index_format 116
10147 7.4.118 keep_flagged 119
10148 7.4.119 list_reply 120
10150 7.4.121 mail_check 120
10151 7.4.122 mailcap_path 120
10152 7.4.123 mailcap_sanitize 120
10153 7.4.124 maildir_header_cache_verify 120
10154 7.4.125 maildir_trash 121
10155 7.4.126 mark_old 121
10156 7.4.127 markers 121
10158 7.4.129 max_display_recips 122
10159 7.4.130 max_line_length 122
10161 7.4.132 mbox_type 122
10162 7.4.133 menu_context 122
10163 7.4.134 menu_move_off 123
10164 7.4.135 menu_scroll 123
10165 7.4.136 message_format 123
10166 7.4.137 meta_key 123
10168 7.4.139 mh_purge 124
10169 7.4.140 mh_seq_flagged 124
10170 7.4.141 mh_seq_replied 124
10171 7.4.142 mh_seq_unseen 124
10172 7.4.143 mime_forward 124
10173 7.4.144 mime_forward_decode 124
10174 7.4.145 mime_forward_rest 125
10175 7.4.146 mix_entry_format 125
10176 7.4.147 mixmaster 125
10178 7.4.149 msgid_format 126
10179 7.4.150 muttng_bindir 127
10180 7.4.151 muttng_docdir 127
10181 7.4.152 muttng_folder_name 127
10182 7.4.153 muttng_folder_path 127
10183 7.4.154 muttng_hcache_backend 127
10184 7.4.155 muttng_pwd 128
10185 7.4.156 muttng_revision 128
10186 7.4.157 muttng_sysconfdir 128
10187 7.4.158 muttng_version 128
10191 7.4.159 narrow_tree 128
10192 7.4.160 nntp_ask_followup_to 128
10193 7.4.161 nntp_ask_x_comment_to 129
10194 7.4.162 nntp_cache_dir 129
10195 7.4.163 nntp_catchup 129
10196 7.4.164 nntp_context 129
10197 7.4.165 nntp_followup_to_poster 129
10198 7.4.166 nntp_group_index_format 130
10199 7.4.167 nntp_host 130
10200 7.4.168 nntp_inews 131
10201 7.4.169 nntp_load_description 131
10202 7.4.170 nntp_mail_check 131
10203 7.4.171 nntp_mime_subject 131
10204 7.4.172 nntp_newsrc 132
10205 7.4.173 nntp_pass 132
10206 7.4.174 nntp_post_moderated 132
10207 7.4.175 nntp_reconnect 132
10208 7.4.176 nntp_save_unsubscribed 133
10209 7.4.177 nntp_show_new_news 133
10210 7.4.178 nntp_show_only_unread 133
10211 7.4.179 nntp_user 133
10212 7.4.180 nntp_x_comment_to 133
10213 7.4.181 operating_system 134
10215 7.4.183 pager_context 134
10216 7.4.184 pager_format 134
10217 7.4.185 pager_index_lines 135
10218 7.4.186 pager_stop 135
10219 7.4.187 pgp_auto_decode 135
10220 7.4.188 pgp_autoinline 135
10221 7.4.189 pgp_check_exit 136
10222 7.4.190 pgp_clearsign_command 136
10223 7.4.191 pgp_decode_command 136
10224 7.4.192 pgp_decrypt_command 137
10225 7.4.193 pgp_encrypt_only_command 137
10226 7.4.194 pgp_encrypt_sign_command 137
10227 7.4.195 pgp_entry_format 137
10228 7.4.196 pgp_export_command 138
10229 7.4.197 pgp_getkeys_command 138
10230 7.4.198 pgp_good_sign 138
10231 7.4.199 pgp_ignore_subkeys 138
10232 7.4.200 pgp_import_command 138
10233 7.4.201 pgp_list_pubring_command 139
10234 7.4.202 pgp_list_secring_command 139
10235 7.4.203 pgp_long_ids 139
10236 7.4.204 pgp_mime_auto 139
10237 7.4.205 pgp_replyinline 139
10238 7.4.206 pgp_retainable_sigs 140
10239 7.4.207 pgp_show_unusable 140
10240 7.4.208 pgp_sign_as 140
10241 7.4.209 pgp_sign_command 140
10242 7.4.210 pgp_sort_keys 141
10243 7.4.211 pgp_strict_enc 141
10247 7.4.212 pgp_timeout 141
10248 7.4.213 pgp_use_gpg_agent 141
10249 7.4.214 pgp_verify_command 142
10250 7.4.215 pgp_verify_key_command 142
10251 7.4.216 pipe_decode 142
10252 7.4.217 pipe_sep 142
10253 7.4.218 pipe_split 142
10254 7.4.219 pop_auth_try_all 142
10255 7.4.220 pop_authenticators 143
10256 7.4.221 pop_delete 143
10257 7.4.222 pop_host 143
10258 7.4.223 pop_last 144
10259 7.4.224 pop_mail_check 144
10260 7.4.225 pop_pass 144
10261 7.4.226 pop_reconnect 144
10262 7.4.227 pop_user 144
10263 7.4.228 post_indent_string 145
10264 7.4.229 postpone 145
10265 7.4.230 postponed 145
10266 7.4.231 preconnect 145
10268 7.4.233 print_command 146
10269 7.4.234 print_decode 146
10270 7.4.235 print_split 146
10271 7.4.236 prompt_after 146
10272 7.4.237 query_command 147
10274 7.4.239 quote_empty 147
10275 7.4.240 quote_quoted 147
10276 7.4.241 quote_regexp 147
10277 7.4.242 read_inc 148
10278 7.4.243 read_only 148
10279 7.4.244 realname 148
10282 7.4.247 reply_regexp 149
10283 7.4.248 reply_self 149
10284 7.4.249 reply_to 149
10285 7.4.250 resolve 149
10286 7.4.251 reverse_alias 150
10287 7.4.252 reverse_name 150
10288 7.4.253 reverse_realname 150
10289 7.4.254 rfc2047_parameters 150
10290 7.4.255 save_address 151
10291 7.4.256 save_empty 151
10292 7.4.257 save_name 151
10294 7.4.259 score_threshold_delete 152
10295 7.4.260 score_threshold_flag 152
10296 7.4.261 score_threshold_read 152
10297 7.4.262 send_charset 152
10298 7.4.263 sendmail 153
10299 7.4.264 sendmail_wait 153
10304 7.4.266 sidebar_boundary 153
10305 7.4.267 sidebar_delim 154
10306 7.4.268 sidebar_newmail_only 154
10307 7.4.269 sidebar_number_format 154
10308 7.4.270 sidebar_shorten_hierarchy 155
10309 7.4.271 sidebar_visible 155
10310 7.4.272 sidebar_width 155
10311 7.4.273 sig_dashes 155
10312 7.4.274 sig_on_top 155
10313 7.4.275 signature 156
10314 7.4.276 signoff_string 156
10315 7.4.277 simple_search 156
10316 7.4.278 sleep_time 156
10317 7.4.279 smart_wrap 157
10318 7.4.280 smileys 157
10319 7.4.281 smime_ask_cert_label 157
10320 7.4.282 smime_ca_location 157
10321 7.4.283 smime_certificates 157
10322 7.4.284 smime_decrypt_command 158
10323 7.4.285 smime_decrypt_use_default_key 158
10324 7.4.286 smime_default_key 158
10325 7.4.287 smime_encrypt_command 159
10326 7.4.288 smime_encrypt_with 159
10327 7.4.289 smime_get_cert_command 159
10328 7.4.290 smime_get_cert_email_command 159
10329 7.4.291 smime_get_signer_cert_command 159
10330 7.4.292 smime_import_cert_command 160
10331 7.4.293 smime_is_default 160
10332 7.4.294 smime_keys 160
10333 7.4.295 smime_pk7out_command 160
10334 7.4.296 smime_sign_command 160
10335 7.4.297 smime_sign_opaque_command 161
10336 7.4.298 smime_timeout 161
10337 7.4.299 smime_verify_command 161
10338 7.4.300 smime_verify_opaque_command 161
10339 7.4.301 smtp_envelope 161
10340 7.4.302 smtp_host 161
10341 7.4.303 smtp_pass 162
10342 7.4.304 smtp_port 162
10343 7.4.305 smtp_use_tls 162
10344 7.4.306 smtp_user 163
10346 7.4.308 sort_alias 163
10347 7.4.309 sort_aux 163
10348 7.4.310 sort_browser 164
10349 7.4.311 sort_re 164
10350 7.4.312 spam_separator 165
10351 7.4.313 spoolfile 165
10352 7.4.314 ssl_ca_certificates_file 165
10353 7.4.315 ssl_client_cert 165
10354 7.4.316 ssl_force_tls 165
10355 7.4.317 ssl_min_dh_prime_bits 166
10359 7.4.318 ssl_starttls 166
10360 7.4.319 ssl_use_sslv2 166
10361 7.4.320 ssl_use_sslv3 166
10362 7.4.321 ssl_use_tlsv1 166
10363 7.4.322 ssl_usesystemcerts 167
10364 7.4.323 status_chars 167
10365 7.4.324 status_format 167
10366 7.4.325 status_on_top 169
10367 7.4.326 strict_mailto 170
10368 7.4.327 strict_mime 170
10369 7.4.328 strict_threads 170
10370 7.4.329 strip_was 170
10371 7.4.330 strip_was_regex 171
10372 7.4.331 stuff_quoted 171
10373 7.4.332 suspend 171
10374 7.4.333 text_flowed 171
10375 7.4.334 thorough_search 171
10376 7.4.335 thread_received 172
10378 7.4.337 timeout 172
10380 7.4.339 to_chars 172
10384 7.4.343 uncollapse_jump 173
10385 7.4.344 use_8bitmime 173
10386 7.4.345 use_domain 174
10387 7.4.346 use_from 174
10388 7.4.347 use_idn 174
10389 7.4.348 use_ipv6 174
10391 7.4.350 wait_key 175
10393 7.4.352 wrap_search 175
10394 7.4.353 wrapmargin 175
10395 7.4.354 write_bcc 175
10396 7.4.355 write_inc 176
10397 7.4.356 xterm_icon 176
10398 7.4.357 xterm_leave 176
10399 7.4.358 xterm_set_titles 176
10400 7.4.359 xterm_title 176
10401 7.5 Functions ....................................................... 177
10417 8. Miscellany ............................................................ 185
10418 8.1 Acknowledgments ................................................. 186
10419 8.2 About this document ............................................. 188