2 T
\bTh
\bhe
\be M
\bMu
\but
\btt
\bt N
\bNe
\bex
\bxt
\bt G
\bGe
\ben
\bne
\ber
\bra
\bat
\bti
\bio
\bon
\bn E
\bE-
\b-M
\bMa
\bai
\bil
\bl C
\bCl
\bli
\bie
\ben
\bnt
\bt
4 by Andreas Krennmair <ak@synflood.at> and others
5 originally based on _
\bm_
\bu_
\bt_
\bt by Michael Elkins <me@cs.hmc.edu> and others
9 A
\bAb
\bbs
\bst
\btr
\bra
\bac
\bct
\bt
11 Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
12 sucks less.'' - Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
14 _
\b1_
\b. _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
16 _
\b1_
\b._
\b1 _
\bO_
\bv_
\be_
\br_
\bv_
\bi_
\be_
\bw
18 M
\bMu
\but
\btt
\bt-
\b-n
\bng
\bg is a small but very powerful text-based MIME mail client. Mutt-ng is
19 highly configurable, and is well suited to the mail power user with advanced
20 features like key bindings, keyboard macros, mail threading, regular expression
21 searches and a powerful pattern matching language for selecting groups of mes-
24 This documentation additionally contains documentation to M
\bMu
\but
\btt
\bt-
\b-N
\bNG
\bG, a fork from
25 Mutt with the goal to fix all the little annoyances of Mutt, to integrate all
26 the Mutt patches that are floating around in the web, and to add other new fea-
27 tures. Features specific to Mutt-ng will be discussed in an extra section.
28 Don't be confused when most of the documentation talk about Mutt and not Mutt-
29 ng, Mutt-ng contains all Mutt features, plus many more.
31 _
\b1_
\b._
\b2 _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bH_
\bo_
\bm_
\be _
\bP_
\ba_
\bg_
\be
35 _
\b1_
\b._
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
37 +
\bo mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user support
40 The Mutt Next Generation E-Mail Client 1
42 The Mutt Next Generation E-Mail Client 2
44 +
\bo mutt-ng-devel@lists.berlios.de -- The development mailing list for mutt-ng
46 _
\b1_
\b._
\b4 _
\bS_
\bo_
\bf_
\bt_
\bw_
\ba_
\br_
\be _
\bD_
\bi_
\bs_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn _
\bS_
\bi_
\bt_
\be_
\bs
48 So far, there are no official releases of Mutt-ng, but you can download daily
49 snapshots from http://mutt-ng.berlios.de/snapshots/
51 _
\b1_
\b._
\b5 _
\bI_
\bR_
\bC
53 Visit channel _
\b#_
\bm_
\bu_
\bt_
\bt_
\bn_
\bg on irc.freenode.net (www.freenode.net) to chat with other
54 people interested in Mutt-ng.
56 _
\b1_
\b._
\b6 _
\bW_
\be_
\bb_
\bl_
\bo_
\bg
58 If you want to read fresh news about the latest development in Mutt-ng, and get
59 informed about stuff like interesting, Mutt-ng-related articles and packages
60 for your favorite distribution, you can read and/or subscribe to our Mutt-ng
63 _
\b1_
\b._
\b7 _
\bC_
\bo_
\bp_
\by_
\br_
\bi_
\bg_
\bh_
\bt
65 Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and others
67 This program is free software; you can redistribute it and/or modify it under
68 the terms of the GNU General Public License as published by the Free Software
69 Foundation; either version 2 of the License, or (at your option) any later ver-
72 This program is distributed in the hope that it will be useful, but WITHOUT ANY
73 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
74 PARTICULAR PURPOSE. See the GNU General Public License for more details.
76 You should have received a copy of the GNU General Public License along with
77 this program; if not, write to the Free Software Foundation, Inc., 59 Temple
78 Place - Suite 330, Boston, MA 02111, USA.
80 _
\b2_
\b. _
\bG_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bS_
\bt_
\ba_
\br_
\bt_
\be_
\bd
82 _
\b2_
\b._
\b1 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bC_
\bo_
\bn_
\bc_
\be_
\bp_
\bt_
\bs
84 The Mutt Next Generation E-Mail Client 3
86 _
\b2_
\b._
\b1_
\b._
\b1 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
88 mutt-ng offers different screens of which every has its special purpose:
90 +
\bo The _
\bi_
\bn_
\bd_
\be_
\bx displays the contents of the currently opened mailbox.
92 +
\bo The _
\bp_
\ba_
\bg_
\be_
\br is responsible for displaying messages, that is, the header, the
93 body and all attached parts.
95 +
\bo The _
\bf_
\bi_
\bl_
\be _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br offers operations on and displays information of all
96 folders mutt-ng should watch for mail.
98 +
\bo The _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br offers a permanent view of which mailboxes contain how many
99 total, new and/or flagged mails.
101 +
\bo The _
\bh_
\be_
\bl_
\bp _
\bs_
\bc_
\br_
\be_
\be_
\bn lists for all currently available commands how to invoke
102 them as well as a short description.
104 +
\bo The _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu is a comfortable interface take last actions before send-
105 ing mail: change subjects, attach files, remove attachements, etc.
107 +
\bo The _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\be_
\bm_
\be_
\bn_
\bt menu gives a summary and the tree structure of the
108 attachements of the current message.
110 +
\bo The _
\ba_
\bl_
\bi_
\ba_
\bs menu lists all or a fraction of the aliases a user has defined.
112 +
\bo The _
\bk_
\be_
\by menu used in connection with encryption lets users choose the
113 right key to encrypt with.
115 When mutt-ng is started without any further options, it'll open the users
116 default mailbox and display the index.
118 _
\b2_
\b._
\b1_
\b._
\b2 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
120 Mutt-ng does _
\bn_
\bo_
\bt feature an internal configuration interface or menu due to the
121 simple fact that this would be too complex to handle (currently there are sev-
122 eral _
\bh_
\bu_
\bn_
\bd_
\br_
\be_
\bd variables which fine-tune the behaviour.)
124 Mutt-ng is configured using configuration files which allow users to add com-
125 ments or manage them via version control systems to ease maintenance.
127 Also, mutt-ng comes with a shell script named grml-muttng kindly contributed by
128 users which really helps and eases the creation of a user's configuration file.
129 When downloading the source code via a snapshot or via subversion, it can be
130 found in the contrib directory.
132 _
\b2_
\b._
\b1_
\b._
\b3 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
134 Mutt-ng offers great flexibility due to the use of functions: internally, every
135 action a user can make mutt-ng perform is named ``function.'' Those functions
137 The Mutt Next Generation E-Mail Client 4
139 are assigned to keys (or even key sequences) and may be completely adjusted to
140 user's needs. The basic idea is that the impatient users get a very intuitive
141 interface to start off with and advanced users virtually get no limits to
144 _
\b2_
\b._
\b1_
\b._
\b4 _
\bI_
\bn_
\bt_
\be_
\br_
\ba_
\bc_
\bt_
\bi_
\bo_
\bn
146 Mutt-ng has two basic concepts of user interaction:
148 1. There is one dedicated line on the screen used to query the user for
149 input, issue any command, query variables and display error and informa-
150 tional messages. As for every type of user input, this requires manual
151 action leading to the need of input.
153 2. The automatized interface for interaction are the so called _
\bh_
\bo_
\bo_
\bk_
\bs. Hooks
154 specify actions the user wants to be performed at well-defined situa-
155 tions: what to do when entering which folder, what to do when displaying
156 or replying to what kind of message, etc. These are optional, i.e. a user
157 doesn't need to specify them but can do so.
159 _
\b2_
\b._
\b1_
\b._
\b5 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
161 Although mutt-ng has many functionality built-in, many features can be dele-
162 gated to external tools to increase flexibility: users can define programs to
163 filter a message through before displaying, users can use any program they want
164 for displaying a message, message types (such as PDF or PostScript) for which
165 mutt-ng doesn't have a built-in filter can be rendered by arbitrary tools and
166 so forth. Although mutt-ng has an alias mechanism built-in, it features using
167 external tools to query for nearly every type of addresses from sources like
168 LDAP, databases or just the list of locally known users.
170 _
\b2_
\b._
\b1_
\b._
\b6 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
172 Mutt-ng has a built-in pattern matching ``language'' which is as widely used as
173 possible to present a consistent interface to users. The same ``pattern terms''
174 can be used for searching, scoring, message selection and much more.
176 _
\b2_
\b._
\b2 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
178 _
\b2_
\b._
\b2_
\b._
\b1 _
\bI_
\bn_
\bd_
\be_
\bx
180 The index is the screen that you usually see first when you start mutt-ng. It
181 gives an overview over your emails in the currently opened mailbox. By default,
182 this is your system mailbox. The information you see in the index is a list of
184 The Mutt Next Generation E-Mail Client 5
186 emails, each with its number on the left, its flags (new email, important
187 email, email that has been forwarded or replied to, tagged email, ...), the
188 date when email was sent, its sender, the email size, and the subject. Addi-
189 tionally, the index also shows thread hierarchies: when you reply to an email,
190 and the other person replies back, you can see the other's person email in a
191 "sub-tree" below. This is especially useful for personal email between a group
192 of people or when you've subscribed to mailing lists.
194 _
\b2_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bg_
\be_
\br
196 The pager is responsible for showing the email content. On the top of the pager
197 you have an overview over the most important email headers like the sender, the
198 recipient, the subject, and much more information. How much information you
199 actually see depends on your configuration, which we'll describe below.
201 Below the headers, you see the email body which usually contains the message.
202 If the email contains any attachments, you will see more information about them
203 below the email body, or, if the attachments are text files, you can view them
204 directly in the pager.
206 To give the user a good overview, it is possible to configure mutt-ng to show
207 different things in the pager with different colors. Virtually everything that
208 can be described with a regular expression can be colored, e.g. URLs, email
209 addresses or smileys.
211 _
\b2_
\b._
\b2_
\b._
\b3 _
\bF_
\bi_
\bl_
\be _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
213 The file browser is the interface to the local or remote file system. When
214 selecting a mailbox to open, the browser allows custom sorting of items, limit-
215 ing the items shown by a regular expression and a freely adjustable format of
216 what to display in which way. It also allows for easy navigation through the
217 file system when selecting file(s) to attach to a message, select multiple
218 files to attach and many more.
220 _
\b2_
\b._
\b2_
\b._
\b4 _
\bS_
\bi_
\bd_
\be_
\bb_
\ba_
\br
222 The sidebar comes in handy to manage mails which are spread over different
223 folders. All folders users setup mutt-ng to watch for new mail will be listed.
224 The listing includes not only the name but also the number of total messages,
225 the number of new and flagged messages. Items with new mail may be colored dif-
226 ferent from those with flagged mail, items may be shortened or compress if
227 they're they to long to be printed in full form so that by abbreviated names,
228 user still now what the name stands for.
230 _
\b2_
\b._
\b2_
\b._
\b5 _
\bH_
\be_
\bl_
\bp
232 The Mutt Next Generation E-Mail Client 6
234 The help screen is meant to offer a quick help to the user. It lists the cur-
235 rent configuration of key bindings and their associated commands including a
236 short description, and currently unbound functions that still need to be asso-
237 ciated with a key binding (or alternatively, they can be called via the mutt-ng
240 _
\b2_
\b._
\b2_
\b._
\b6 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
242 The compose menu features a split screen containing the information which
243 really matter before actually sending a message by mail or posting an article
244 to a newsgroup: who gets the message as what (recipient, newsgroup, who gets
245 what kind of copy). Additionally, users may set security options like deciding
246 whether to sign, encrypt or sign and encrypt a message with/for what keys.
248 Also, it's used to attach messages, news articles or files to a message, to re-
249 edit any attachment including the message itself.
251 _
\b2_
\b._
\b2_
\b._
\b7 _
\bA_
\bl_
\bi_
\ba_
\bs _
\bM_
\be_
\bn_
\bu
253 The alias menu is used to help users finding the recipients of messages. For
254 users who need to contact many people, there's no need to remember addresses or
255 names completely because it allows for searching, too. The alias mechanism and
256 thus the alias menu also features grouping several addresses by a shorter nick-
257 name, the actual alias, so that users don't have to select each single recipi-
260 _
\b2_
\b._
\b2_
\b._
\b8 _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
262 As will be later discussed in detail, mutt-ng features a good and stable MIME
263 implementation, that is, is greatly supports sending and receiving messages of
264 arbitrary type. The attachment menu displays a message's structure in detail:
265 what content parts are attached to which parent part (which gives a true tree
266 structure), which type is of what type and what size. Single parts may saved,
267 deleted or modified to offer great and easy access to message's internals.
269 _
\b2_
\b._
\b2_
\b._
\b9 _
\bK_
\be_
\by _
\bM_
\be_
\bn_
\bu
273 _
\b2_
\b._
\b3 _
\bM_
\bo_
\bv_
\bi_
\bn_
\bg _
\bA_
\br_
\bo_
\bu_
\bn_
\bd _
\bi_
\bn _
\bM_
\be_
\bn_
\bu_
\bs
275 Information is presented in menus, very similar to ELM. Here is a table
277 The Mutt Next Generation E-Mail Client 7
279 showing the common keys used to navigate menus in Mutt-ng.
281 j or Down next-entry move to the next entry
282 k or Up previous-entry move to the previous entry
283 z or PageDn page-down go to the next page
284 Z or PageUp page-up go to the previous page
285 = or Home first-entry jump to the first entry
286 * or End last-entry jump to the last entry
287 q quit exit the current menu
288 ? help list all key bindings for the current menu
290 _
\b2_
\b._
\b4 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bI_
\bn_
\bp_
\bu_
\bt _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
292 Mutt-ng has a builtin line editor which is used as the primary way to input
293 textual data such as email addresses or filenames. The keys used to move
294 around while editing are very similar to those of Emacs.
296 ^A or <Home> bol move to the start of the line
297 ^B or <Left> backward-char move back one char
298 Esc B backward-word move back one word
299 ^D or <Delete> delete-char delete the char under the cursor
300 ^E or <End> eol move to the end of the line
301 ^F or <Right> forward-char move forward one char
302 Esc F forward-word move forward one word
303 <Tab> complete complete filename or alias
304 ^T complete-query complete address with query
305 ^K kill-eol delete to the end of the line
306 ESC d kill-eow delete to the end of the word
307 ^W kill-word kill the word in front of the cursor
308 ^U kill-line delete entire line
309 ^V quote-char quote the next typed key
310 <Up> history-up recall previous string from history
311 <Down> history-down recall next string from history
312 <BackSpace> backspace kill the char in front of the cursor
313 Esc u upcase-word convert word to upper case
314 Esc l downcase-word convert word to lower case
315 Esc c capitalize-word capitalize the word
317 <Return> n/a finish editing
319 You can remap the _
\be_
\bd_
\bi_
\bt_
\bo_
\br functions using the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 26) com-
320 mand. For example, to make the _
\bD_
\be_
\bl_
\be_
\bt_
\be key delete the character in front of the
321 cursor rather than under, you could use
323 bind editor <delete> backspace
325 The Mutt Next Generation E-Mail Client 8
327 _
\b2_
\b._
\b5 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl _
\b- _
\bT_
\bh_
\be _
\bI_
\bn_
\bd_
\be_
\bx _
\ba_
\bn_
\bd _
\bP_
\ba_
\bg_
\be_
\br
329 Similar to many other mail clients, there are two modes in which mail is read
330 in Mutt-ng. The first is the index of messages in the mailbox, which is called
331 the ``index'' in Mutt-ng. The second mode is the display of the message con-
332 tents. This is called the ``pager.''
334 The next few sections describe the functions provided in each of these modes.
336 _
\b2_
\b._
\b5_
\b._
\b1 _
\bT_
\bh_
\be _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bI_
\bn_
\bd_
\be_
\bx
338 c change to a different mailbox
339 ESC c change to a folder in read-only mode
340 C copy the current message to another mailbox
341 ESC C decode a message and copy it to a folder
342 ESC s decode a message and save it to a folder
343 D delete messages matching a pattern
344 d delete the current message
346 l show messages matching a pattern
347 N mark message as new
348 o change the current sort method
349 O reverse sort the mailbox
350 q save changes and exit
352 T tag messages matching a pattern
353 t toggle the tag on a message
354 ESC t toggle tag on entire message thread
355 U undelete messages matching a pattern
358 x abort changes and exit
359 <Return> display-message
360 <Tab> jump to the next new message
361 @ show the author's full e-mail address
362 $ save changes to mailbox
365 ^L clear and redraw the screen
366 ^T untag messages matching a pattern
368 _
\b2_
\b._
\b5_
\b._
\b1_
\b._
\b1 _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs _
\bF_
\bl_
\ba_
\bg_
\bs
370 In addition to who sent the message and the subject, a short summary of the
371 disposition of each message is printed beside the message number. Zero or more
372 of the following ``flags'' may appear, which mean:
375 message is deleted (is marked for deletion)
378 message have attachments marked for deletion
380 The Mutt Next Generation E-Mail Client 9
383 contains a PGP public key
392 message is PGP encrypted
395 message has been replied to
398 message is signed, and the signature is succesfully verified
409 Some of the status flags can be turned on or off using
411 +
\bo s
\bse
\bet
\bt-
\b-f
\bfl
\bla
\bag
\bg (default: w)
413 +
\bo c
\bcl
\ble
\bea
\bar
\br-
\b-f
\bfl
\bla
\bag
\bg (default: W)
415 Furthermore, the following flags reflect who the message is addressed to. They
416 can be customized with the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.329 , page 169) variable.
419 message is to you and you only
422 message is to you, but also to or cc'ed to others
425 message is cc'ed to you
431 message is sent to a subscribed mailing list
433 _
\b2_
\b._
\b5_
\b._
\b2 _
\bT_
\bh_
\be _
\bP_
\ba_
\bg_
\be_
\br
435 By default, Mutt-ng uses its builtin pager to display the body of messages.
437 The Mutt Next Generation E-Mail Client 10
439 The pager is very similar to the Unix program _
\bl_
\be_
\bs_
\bs though not nearly as fea-
442 <Return> go down one line
443 <Space> display the next page (or next message if at the end of a message)
444 - go back to the previous page
445 n search for next match
446 S skip beyond quoted text
447 T toggle display of quoted text
449 / search for a regular expression (pattern)
450 ESC / search backwards for a regular expression
451 \ toggle search pattern coloring
452 ^ jump to the top of the message
454 In addition, many of the functions from the _
\bi_
\bn_
\bd_
\be_
\bx are available in the pager,
455 such as _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be or _
\bc_
\bo_
\bp_
\by_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be (this is one advantage over using an
456 external pager to view messages).
458 Also, the internal pager supports a couple other advanced features. For one, it
459 will accept and translate the ``standard'' nroff sequences for bold and under-
460 line. These sequences are a series of either the letter, backspace (^H), the
461 letter again for bold or the letter, backspace, ``_'' for denoting underline.
462 Mutt-ng will attempt to display these in bold and underline respectively if
463 your terminal supports them. If not, you can use the bold and underline _
\bc_
\bo_
\bl_
\bo_
\br
464 (section 3.9 , page 30) objects to specify a color or mono attribute for them.
466 Additionally, the internal pager supports the ANSI escape sequences for charac-
467 ter attributes. Mutt-ng translates them into the correct color and character
468 settings. The sequences Mutt-ng supports are:
470 ESC [ Ps;Ps;Ps;...;Ps m
477 3x Foreground color is x
478 4x Background color is x
490 The Mutt Next Generation E-Mail Client 11
492 Mutt-ng uses these attributes for handling text/enriched messages, and they can
493 also be used by an external _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) script for high-
494 lighting purposes. N
\bNo
\bot
\bte
\be:
\b: If you change the colors for your display, for exam-
495 ple by changing the color associated with color2 for your xterm, then that
496 color will be used instead of green.
498 _
\b2_
\b._
\b5_
\b._
\b3 _
\bT_
\bh_
\br_
\be_
\ba_
\bd_
\be_
\bd _
\bM_
\bo_
\bd_
\be
500 When the mailbox is _
\bs_
\bo_
\br_
\bt_
\be_
\bd (section 7.4.297 , page 160) by _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs, there are
501 a few additional functions available in the _
\bi_
\bn_
\bd_
\be_
\bx and _
\bp_
\ba_
\bg_
\be_
\br modes.
503 ^D delete-thread delete all messages in the current thread
504 ^U undelete-thread undelete all messages in the current thread
505 ^N next-thread jump to the start of the next thread
506 ^P previous-thread jump to the start of the previous thread
507 ^R read-thread mark the current thread as read
508 ESC d delete-subthread delete all messages in the current subthread
509 ESC u undelete-subthread undelete all messages in the current subthread
510 ESC n next-subthread jump to the start of the next subthread
511 ESC p previous-subthread jump to the start of the previous subthread
512 ESC r read-subthread mark the current subthread as read
513 ESC t tag-thread toggle the tag on the current thread
514 ESC v collapse-thread toggle collapse for the current thread
515 ESC V collapse-all toggle collapse for all threads
516 P parent-message jump to parent message in thread
518 N
\bNo
\bot
\bte
\be:
\b: Collapsing a thread displays only the first message in the thread and
519 hides the others. This is useful when threads contain so many messages that you
520 can only see a handful of threads on the screen. See %M in _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
521 tion 7.4.115 , page 115). For example, you could use "%?M?(#%03M)&(%4l)?" in
522 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) to optionally display the number of
523 hidden messages if the thread is collapsed.
525 See also: _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 7.4.318 , page 167).
527 _
\b2_
\b._
\b5_
\b._
\b4 _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\be_
\bo_
\bu_
\bs _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
529 c
\bcr
\bre
\bea
\bat
\bte
\be-
\b-a
\bal
\bli
\bia
\bas
\bs
532 Creates a new alias based upon the current message (or prompts for a new one).
533 Once editing is complete, an _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 25) command is added to
534 the file specified by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 89) variable for
535 future use. N
\bNo
\bot
\bte
\be:
\b: Specifying an _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 89) does not
536 add the aliases specified there-in, you must also _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page
539 c
\bch
\bhe
\bec
\bck
\bk-
\b-t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl-
\b-p
\bpg
\bgp
\bp
542 This function will search the current message for content signed or encrypted
543 with PGP the "traditional" way, that is, without proper MIME tagging.
545 The Mutt Next Generation E-Mail Client 12
547 Technically, this function will temporarily change the MIME content types of
548 the body parts containing PGP data; this is similar to the _
\be_
\bd_
\bi_
\bt_
\b-_
\bt_
\by_
\bp_
\be (section
549 2.5.4 , page 12) function's effect.
551 d
\bdi
\bis
\bsp
\bpl
\bla
\bay
\by-
\b-t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-w
\bwe
\bee
\bed
\bd
554 Toggles the weeding of message header fields specified by _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section
555 3.10 , page 32) commands.
560 This command (available in the ``index'' and ``pager'') allows you to edit the
561 raw current message as it's present in the mail folder. After you have fin-
562 ished editing, the changed message will be appended to the current folder, and
563 the original message will be marked for deletion.
565 e
\bed
\bdi
\bit
\bt-
\b-t
\bty
\byp
\bpe
\be
567 (default: ^E on the attachment menu, and in the pager and index menus; ^T on
570 This command is used to temporarily edit an attachment's content type to fix,
571 for instance, bogus character set parameters. When invoked from the index or
572 from the pager, you'll have the opportunity to edit the top-level attachment's
573 content type. On the _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bm_
\be_
\bn_
\bu (section 5.1.2 , page 70), you can
574 change any attachment's content type. These changes are not persistent, and get
575 lost upon changing folders.
577 Note that this command is also available on the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bm_
\be_
\bn_
\bu (section 5.1.3 ,
578 page 71). There, it's used to fine-tune the properties of attachments you are
581 e
\ben
\bnt
\bte
\ber
\br-
\b-c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
584 This command is used to execute any command you would normally put in a config-
585 uration file. A common use is to check the settings of variables, or in con-
586 junction with _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 29) to change settings on the fly.
588 e
\bex
\bxt
\btr
\bra
\bac
\bct
\bt-
\b-k
\bke
\bey
\bys
\bs
591 This command extracts PGP public keys from the current or tagged message(s) and
592 adds them to your PGP public key ring.
594 f
\bfo
\bor
\brg
\bge
\bet
\bt-
\b-p
\bpa
\bas
\bss
\bsp
\bph
\bhr
\bra
\bas
\bse
\be
597 This command wipes the passphrase(s) from memory. It is useful, if you mis-
598 spelled the passphrase.
600 The Mutt Next Generation E-Mail Client 13
602 l
\bli
\bis
\bst
\bt-
\b-r
\bre
\bep
\bpl
\bly
\by
605 Reply to the current or tagged message(s) by extracting any addresses which
606 match the regular expressions given by the _
\bl_
\bi_
\bs_
\bt_
\bs _
\bo_
\br _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 ,
607 page 35) commands, but also honor any Mail-Followup-To header(s) if the
608 _
\b$_
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.93 , page 110) configuration variable is set.
609 Using this when replying to messages posted to mailing lists helps avoid dupli-
610 cate copies being sent to the author of the message you are replying to.
612 p
\bpi
\bip
\bpe
\be-
\b-m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
615 Asks for an external Unix command and pipes the current or tagged message(s) to
616 it. The variables _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.206 , page 139), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.208 , page 139), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.207 , page 139) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.340 , page 172) control the exact behavior of this
621 r
\bre
\bes
\bse
\ben
\bnd
\bd-
\b-m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
624 With resend-message, mutt takes the current message as a template for a new
625 message. This function is best described as "recall from arbitrary folders".
626 It can conveniently be used to forward MIME messages while preserving the orig-
627 inal mail structure. Note that the amount of headers included here depends on
628 the value of the _
\b$_
\bw_
\be_
\be_
\bd (section 7.4.341 , page 172) variable.
630 This function is also available from the attachment menu. You can use this to
631 easily resend a message which was included with a bounce message as a mes-
632 sage/rfc822 body part.
634 s
\bsh
\bhe
\bel
\bll
\bl-
\b-e
\bes
\bsc
\bca
\bap
\bpe
\be
637 Asks for an external Unix command and executes it. The _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section
638 7.4.340 , page 172) can be used to control whether Mutt-ng will wait for a key
639 to be pressed when the command returns (presumably to let the user read the
640 output of the command), based on the return status of the named command.
642 t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd
645 The _
\bp_
\ba_
\bg_
\be_
\br uses the _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.231 , page 144) variable to
646 detect quoted text when displaying the body of the message. This function tog-
647 gles the display of the quoted material in the message. It is particularly
648 useful when are interested in just the response and there is a large amount of
649 quoted text in the way.
651 s
\bsk
\bki
\bip
\bp-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd
654 This function will go to the next line of non-quoted text which come after a
655 line of quoted text in the internal pager.
657 The Mutt Next Generation E-Mail Client 14
659 _
\b2_
\b._
\b6 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
661 The following bindings are available in the _
\bi_
\bn_
\bd_
\be_
\bx for sending messages.
663 m compose compose a new message
664 r reply reply to sender
665 g group-reply reply to all recipients
666 L list-reply reply to mailing list address
667 f forward forward message
668 b bounce bounce (remail) message
669 ESC k mail-key mail a PGP public key to someone
671 Bouncing a message sends the message as is to the recipient you specify. For-
672 warding a message allows you to add comments or modify the message you are for-
673 warding. These items are discussed in greater detail in the next chapter
674 _
\b`_
\b`_
\bF_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bd _
\bB_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\b'_
\b' (section 2.7 , page 20).
676 _
\b2_
\b._
\b6_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg _
\bn_
\be_
\bw _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
678 When you want to send an email using mutt-ng, simply press m on your keyboard.
679 Then, mutt-ng asks for the recipient via a prompt in the last line:
683 After you've finished entering the recipient(s), press return. If you want to
684 send an email to more than one recipient, separate the email addresses using
685 the comma ",". Mutt-ng then asks you for the email subject. Again, press return
686 after you've entered it. After that, mutt-ng got the most important information
687 from you, and starts up an editor where you can then enter your email.
689 The editor that is called is selected in the following way: you can e.g. set it
690 in the mutt-ng configuration:
692 set editor = "vim +/^$/ -c ':set tw=72'"
696 If you don't set your preferred editor in your configuration, mutt-ng first
697 looks whether the environment variable $VISUAL is set, and if so, it takes its
698 value as editor command. Otherwise, it has a look at $EDITOR and takes its
699 value if it is set. If no editor command can be found, mutt-ng simply assumes
700 vi to be the default editor, since it's the most widespread editor in the Unix
701 world and it's pretty safe to assume that it is installed and available.
703 When you've finished entering your message, save it and quit your editor. Mutt-
704 ng will then present you with a summary screen, the compose menu. On the top,
705 you see a summary of the most important available key commands. Below that,
706 you see the sender, the recipient(s), Cc and/or Bcc recipient(s), the subject,
708 The Mutt Next Generation E-Mail Client 15
710 the reply-to address, and optionally information where the sent email will be
711 stored and whether it should be digitally signed and/or encrypted.
713 Below that, you see a list of "attachments". The mail you've just entered
714 before is also an attachment, but due to its special type (it's plain text), it
715 will be displayed as the normal message on the receiver's side.
717 At this point, you can add more attachments, pressing a, you can edit the
718 recipient addresses, pressing t for the "To:" field, c for the "Cc:" field, and
719 b for the "Bcc: field. You can also edit the subject the subject by simply
720 pressing s or the email message that you've entered before by pressing e. You
721 will then again return to the editor. You can even edit the sender, by pressing
722 <esc>f, but this shall only be used with caution.
724 Alternatively, you can configure mutt-ng in a way that most of the above set-
725 tings can be edited using the editor. Therefore, you only need to add the fol-
726 lowing to your configuration:
730 Once you have finished editing the body of your mail message, you are returned
731 to the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu. The following options are available:
733 a attach-file attach a file
734 A attach-message attach message(s) to the message
735 ESC k attach-key attach a PGP public key
736 d edit-description edit description on attachment
737 D detach-file detach a file
738 t edit-to edit the To field
739 ESC f edit-from edit the From field
740 r edit-reply-to edit the Reply-To field
741 c edit-cc edit the Cc field
742 b edit-bcc edit the Bcc field
743 y send-message send the message
744 s edit-subject edit the Subject
745 S smime-menu select S/MIME options
746 f edit-fcc specify an ``Fcc'' mailbox
747 p pgp-menu select PGP options
748 P postpone-message postpone this message until later
749 q quit quit (abort) sending the message
750 w write-fcc write the message to a folder
751 i ispell check spelling (if available on your system)
752 ^F forget-passphrase wipe passphrase(s) from memory
754 N
\bNo
\bot
\bte
\be:
\b: The attach-message function will prompt you for a folder to attach mes-
755 sages from. You can now tag messages in that folder and they will be attached
756 to the message you are sending. Note that certain operations like composing a
757 new mail, replying, forwarding, etc. are not permitted when you are in that
758 folder. The %r in _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164) will change to a
759 'A' to indicate that you are in attach-message mode.
761 The Mutt Next Generation E-Mail Client 16
763 _
\b2_
\b._
\b6_
\b._
\b2 _
\bR_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg
765 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b1 _
\bS_
\bi_
\bm_
\bp_
\bl_
\be _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
767 When you want to reply to an email message, select it in the index menu and
768 then press r. Mutt-ng's behaviour is then similar to the behaviour when you
769 compose a message: first, you will be asked for the recipient, then for the
770 subject, and then, mutt-ng will start the editor with the quote attribution and
771 the quoted message. This can e.g. look like the example below.
773 On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote:
774 > Bill, can you please send last month's progress report to Mr.
775 > Morgan? We also urgently need the cost estimation for the new
776 > production server that we want to set up before our customer's
777 > project will go live.
779 You can start editing the email message. It is strongly recommended to put your
780 answer _
\bb_
\be_
\bl_
\bo_
\bw the quoted text and to only quote what is really necessary and
781 that you refer to. Putting your answer on top of the quoted message, is,
782 although very widespread, very often not considered to be a polite way to
785 The quote attribution is configurable, by default it is set to
787 set attribution = "On %d, %n wrote:"
789 It can also be set to something more compact, e.g.
791 set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
793 The example above results in the following attribution:
795 * Michael Svensson <svensson@foobar.com> [05-03-06 17:02]:
796 > Bill, can you please send last month's progress report to Mr.
797 > Morgan? We also urgently need the cost estimation for the new
798 > production server that we want to set up before our customer's
799 > project will go live.
801 Generally, try to keep your attribution short yet information-rich. It is _
\bn_
\bo_
\bt
802 the right place for witty quotes, long "attribution" novels or anything like
803 that: the right place for such things is - if at all - the email signature at
804 the very bottom of the message.
806 When you're done with writing your message, save and quit the editor. As
807 before, you will return to the compose menu, which is used in the same way as
809 The Mutt Next Generation E-Mail Client 17
813 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b2 _
\bG_
\br_
\bo_
\bu_
\bp _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
815 In the situation where a group of people uses email as a discussion, most of
816 the emails will have one or more recipients, and probably several "Cc:" recipi-
817 ents. The group reply functionality ensures that when you press g instead of r
818 to do a reply, each and every recipient that is contained in the original mes-
819 sage will receive a copy of the message, either as normal recipient or as "Cc:"
822 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b3 _
\bL_
\bi_
\bs_
\bt _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
824 When you use mailing lists, it's generally better to send your reply to a mes-
825 sage only to the list instead of the list and the original author. To make this
826 easy to use, mutt-ng features list replies.
828 To do a list reply, simply press L. If the email contains a Mail-Followup-To:
829 header, its value will be used as reply address. Otherwise, mutt-ng searches
830 through all mail addresses in the original message and tries to match them a
831 list of regular expressions which can be specified using the lists command. If
832 any of the regular expression matches, a mailing list address has been found,
833 and it will be used as reply address.
835 lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
837 Nowadays, most mailing list software like GNU Mailman adds a Mail-Followup-To:
838 header to their emails anyway, so setting lists is hardly ever necessary in
841 _
\b2_
\b._
\b6_
\b._
\b3 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br
843 When editing the header of your outgoing message, there are a couple of special
848 Fcc: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
850 Mutt-ng will pick up _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be just as if you had used the _
\be_
\bd_
\bi_
\bt_
\b-_
\bf_
\bc_
\bc function in
851 the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu.
853 You can also attach files to your message by specifying
855 The Mutt Next Generation E-Mail Client 18
857 Attach: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
859 where _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is the file to attach and _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn is an optional string to
860 use as the description of the attached file.
862 When replying to messages, if you remove the _
\bI_
\bn_
\b-_
\bR_
\be_
\bp_
\bl_
\by_
\b-_
\bT_
\bo_
\b: field from the header
863 field, Mutt-ng will not generate a _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be_
\bs_
\b: field, which allows you to cre-
864 ate a new message thread.
866 Also see _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102).
868 _
\b2_
\b._
\b6_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bw_
\bi_
\bt_
\bh _
\bP_
\bG_
\bP
870 If you want to use PGP, you can specify
872 Pgp: [ E | S | S_
\b<_
\bi_
\bd_
\b> ]
874 ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
875 _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.198 , page 137) permanently.
877 If you have told mutt to PGP encrypt a message, it will guide you through a key
878 selection process when you try to send the message. Mutt-ng will not ask you
879 any questions about keys which have a certified user ID matching one of the
880 message recipients' mail addresses. However, there may be situations in which
881 there are several keys, weakly certified user ID fields, or where no matching
884 In these cases, you are dropped into a menu with a list of keys from which you
885 can select one. When you quit this menu, or mutt can't find any matching keys,
886 you are prompted for a user ID. You can, as usually, abort this prompt using
887 ^G. When you do so, mutt will return to the compose screen.
889 Once you have successfully finished the key selection, the message will be
890 encrypted using the selected public keys, and sent out.
892 Most fields of the entries in the key selection menu (see also _
\b$_
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\b-
893 _
\bm_
\ba_
\bt (section 7.4.185 , page 134)) have obvious meanings. But some explana-
894 tions on the capabilities, flags, and validity fields are in order.
896 The flags sequence (%f) will expand to one of the following flags:
898 R The key has been revoked and can't be used.
899 X The key is expired and can't be used.
900 d You have marked the key as disabled.
901 c There are unknown critical self-signature
904 The capabilities field (%c) expands to a two-character sequence representing a
905 key's capabilities. The first character gives the key's encryption capabili-
906 ties: A minus sign (-
\b-) means that the key cannot be used for encryption. A dot
907 (.
\b.) means that it's marked as a signature key in one of the user IDs, but may
909 The Mutt Next Generation E-Mail Client 19
911 also be used for encryption. The letter e
\be indicates that this key can be used
914 The second character indicates the key's signing capabilities. Once again, a
915 ``-
\b-'' implies ``not for signing'', ``.
\b.'' implies that the key is marked as an
916 encryption key in one of the user-ids, and ``s
\bs'' denotes a key which can be
919 Finally, the validity field (%t) indicates how well-certified a user-id is. A
920 question mark (?
\b?) indicates undefined validity, a minus character (-
\b-) marks an
921 untrusted association, a space character means a partially trusted association,
922 and a plus character (+
\b+) indicates complete validity.
924 _
\b2_
\b._
\b6_
\b._
\b5 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bo_
\bn_
\by_
\bm_
\bo_
\bu_
\bs _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs _
\bv_
\bi_
\ba _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
926 You may also have configured mutt to co-operate with Mixmaster, an anonymous
927 remailer. Mixmaster permits you to send your messages anonymously using a
928 chain of remailers. Mixmaster support in mutt is for mixmaster version 2.04
929 (beta 45 appears to be the latest) and 2.03. It does not support earlier ver-
930 sions or the later so-called version 3 betas, of which the latest appears to be
933 To use it, you'll have to obey certain restrictions. Most important, you can-
934 not use the Cc and Bcc headers. To tell Mutt-ng to use mixmaster, you have to
935 select a remailer chain, using the mix function on the compose menu.
937 The chain selection screen is divided into two parts. In the (larger) upper
938 part, you get a list of remailers you may use. In the lower part, you see the
939 currently selected chain of remailers.
941 You can navigate in the chain using the chain-prev and chain-next functions,
942 which are by default bound to the left and right arrows and to the h and l keys
943 (think vi keyboard bindings). To insert a remailer at the current chain posi-
944 tion, use the insert function. To append a remailer behind the current chain
945 position, use select-entry or append. You can also delete entries from the
946 chain, using the corresponding function. Finally, to abandon your changes,
947 leave the menu, or accept them pressing (by default) the Return key.
949 Note that different remailers do have different capabilities, indicated in the
950 %c entry of the remailer menu lines (see _
\b$_
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.145 ,
951 page 123)). Most important is the ``middleman'' capability, indicated by a
952 capital ``M'': This means that the remailer in question cannot be used as the
953 final element of a chain, but will only forward messages to other mixmaster
954 remailers. For details on the other capabilities, please have a look at the
955 mixmaster documentation.
957 _
\b2_
\b._
\b7 _
\bF_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bd _
\bB_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
959 The Mutt Next Generation E-Mail Client 20
961 Often, it is necessary to forward mails to other people. Therefore, mutt-ng
962 supports forwarding messages in two different ways.
964 The first one is regular forwarding, as you probably know it from other mail
965 clients. You simply press f, enter the recipient email address, the subject of
966 the forwarded email, and then you can edit the message to be forwarded in the
967 editor. The forwarded message is separated from the rest of the message via the
968 two following markers:
970 ----- Forwarded message from Lucas User <luser@example.com> -----
972 From: Lucas User <luser@example.com>
973 Date: Thu, 02 Dec 2004 03:08:34 +0100
974 To: Michael Random <mrandom@example.com>
975 Subject: Re: blackmail
977 Pay me EUR 50,000.- cash or your favorite stuffed animal will die
980 ----- End forwarded message -----
982 When you're done with editing the mail, save and quit the editor, and you will
983 return to the compose menu, the same menu you also encounter when composing or
986 The second mode of forwarding emails with mutt-ng is the so-called _
\bb_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg:
987 when you bounce an email to another address, it will be sent in practically the
988 same format you send it (except for headers that are created during transport-
989 ing the message). To bounce a message, press b and enter the recipient email
990 address. By default, you are then asked whether you really want to bounce the
991 message to the specified recipient. If you answer with yes, the message will
994 To the recipient, the bounced email will look as if he got it like a regular
995 email where he was Bcc: recipient. The only possibility to find out whether it
996 was a bounced email is to carefully study the email headers and to find out
997 which host really sent the email.
999 _
\b2_
\b._
\b8 _
\bP_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
1001 At times it is desirable to delay sending a message that you have already begun
1002 to compose. When the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be function is used in the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu,
1003 the body of your message and attachments are stored in the mailbox specified by
1004 the _
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.220 , page 142) variable. This means that you can
1005 recall the message even if you exit Mutt-ng and then restart it at a later
1008 Once a message is postponed, there are several ways to resume it. From the
1009 command line you can use the ``-p'' option, or if you _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be a new message
1011 The Mutt Next Generation E-Mail Client 21
1013 from the _
\bi_
\bn_
\bd_
\be_
\bx or _
\bp_
\ba_
\bg_
\be_
\br you will be prompted if postponed messages exist. If
1014 multiple messages are currently postponed, the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd menu will pop up and
1015 you can select which message you would like to resume.
1017 N
\bNo
\bot
\bte
\be:
\b: If you postpone a reply to a message, the reply setting of the message is
1018 only updated when you actually finish the message and send it. Also, you must
1019 be in the same folder with the message you replied to for the status of the
1020 message to be updated.
1022 See also the _
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.219 , page 142) quad-option.
1024 _
\b3_
\b. _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
1026 _
\b3_
\b._
\b1 _
\bL_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs _
\bo_
\bf _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1028 While the default configuration (or ``preferences'') make Mutt-ng usable right
1029 out of the box, it is often desirable to tailor Mutt-ng to suit your own
1030 tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
1031 configuration file (defaults set by your local system administrator), unless
1032 the ``-n'' _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be (section 7.1 , page 82) option is specified. This
1033 file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
1034 users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
1035 Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
1036 will look for .muttngrc. If this file does not exist and your home directory
1037 has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
1039 .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
1040 your _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page 85) to configure Mutt-ng.
1042 _
\b3_
\b._
\b2 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bS_
\by_
\bn_
\bt_
\ba_
\bx _
\bo_
\bf _
\bI_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1044 An initialization file consists of a series of _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page
1045 85). Each line of the file may contain one or more commands. When multiple
1046 commands are used, they must be separated by a semicolon (;).
1048 set realname='Mutt-ng user' ; ignore x-
1050 The hash mark, or pound sign (``#''), is used as a ``comment'' character. You
1051 can use it to annotate your initialization file. All text after the comment
1052 character to the end of the line is ignored. For example,
1054 my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
1056 Single quotes (') and double quotes (') can be used to quote strings which
1058 The Mutt Next Generation E-Mail Client 22
1060 contain spaces or other special characters. The difference between the two
1061 types of quotes is similar to that of many popular shell programs, namely that
1062 a single quote is used to specify a literal string (one that is not interpreted
1063 for shell variables or quoting with a backslash [see next paragraph]), while
1064 double quotes indicate a string for which should be evaluated. For example,
1065 backtics are evaluated inside of double quotes, but n
\bno
\bot
\bt for single quotes.
1067 \ quotes the next character, just as in shells such as bash and zsh. For exam-
1068 ple, if want to put quotes ``''' inside of a string, you can use ``\'' to force
1069 the next character to be a literal instead of interpreted character.
1071 set realname="Michael \"MuttDude\" Elkins"
1073 ``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r'' have
1074 their usual C meanings of linefeed and carriage-return, respectively.
1076 A \ at the end of a line can be used to split commands over multiple lines,
1077 provided that the split points don't appear in the middle of command names.
1079 Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the
1080 end of a line also in comments. This allows you to disable a command split over
1081 multiple lines with only one ``#''.
1084 set realname="Michael \"MuttDude\" Elkins"
1086 When testing your config files, beware the following caveat. The backslash at
1087 the end of the commented line extends the current line with the next line -
1088 then referred to as a ``continuation line''. As the first line is commented
1089 with a hash (#) all following continuation lines are also part of a comment and
1090 therefore are ignored, too. So take care of comments when continuation lines
1091 are involved within your setup files!
1101 line1 ``continues'' until line4. however, the part after the # is a comment
1102 which includes line3 and line4. line5 is a new line of its own and thus is
1105 The commands understood by mutt are explained in the next paragraphs. For a
1106 complete list, see the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.3 , page 85).
1108 The Mutt Next Generation E-Mail Client 23
1110 _
\b3_
\b._
\b3 _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
1112 _
\b3_
\b._
\b3_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs_
\b' _
\bO_
\bu_
\bt_
\bp_
\bu_
\bt
1114 It is possible to substitute the output of a Unix command in an initialization
1115 file. This is accomplished by enclosing the command in backquotes (``) as in,
1118 my_hdr X-Operating-System: `uname -a`
1120 The output of the Unix command ``uname -a'' will be substituted before the line
1121 is parsed. Note that since initialization files are line oriented, only the
1122 first line of output from the Unix command will be substituted.
1124 _
\b3_
\b._
\b3_
\b._
\b2 _
\bE_
\bn_
\bv_
\bi_
\br_
\bo_
\bn_
\bm_
\be_
\bn_
\bt _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1126 UNIX environments can be accessed like the way it is done in shells like sh and
1127 bash: Prepend the name of the environment by a ``$'' sign. For example,
1129 set record=+sent_on_$HOSTNAME
1131 sets the _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146) variable to the string _
\b+_
\bs_
\be_
\bn_
\bt_
\b__
\bo_
\bn_
\b_
1132 and appends the value of the evironment variable $HOSTNAME.
1134 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if an environment variable is not defined. The
1135 result will of the expansion will then be empty.
1137 _
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1139 As for environment variables, the values of all configuration variables as
1140 string can be used in the same way, too. For example,
1142 set imap_home_namespace = $folder
1144 would set the value of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.100 , page 112) to
1145 the value to which _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) is _
\bc_
\bu_
\br_
\br_
\be_
\bn_
\bt_
\bl_
\by set to.
1147 N
\bNo
\bot
\bte
\be:
\b: There're no logical links established in such cases so that the the value
1148 for _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.100 , page 112) won't change even if
1149 _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) gets changed.
1151 N
\bNo
\bot
\bte
\be:
\b: There will be no warning if a configuration variable is not defined or is
1152 empty. The result will of the expansion will then be empty.
1154 _
\b3_
\b._
\b3_
\b._
\b4 _
\bS_
\be_
\bl_
\bf_
\b-_
\bD_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
1156 Mutt-ng flexibly allows users to define their own variables. To avoid conflicts
1157 with the standard set and to prevent misleading error messages, there's a
1159 The Mutt Next Generation E-Mail Client 24
1161 reserved namespace for them: all user-defined variables must be prefixed with
1162 user_ and can be used just like any ordinary configuration or environment vari-
1165 For example, to view the manual, users can either define three macros like the
1168 macro generic <F1> "!less -r /path/to/manual" "Show manual"
1169 macro pager <F1> "!less -r /path/to/manual" "Show manual"
1170 macro index <F1> "!less -r /path/to/manual" "Show manual"
1172 for generic, pager and index. The alternative is to define a custom variable
1175 set user_manualcmd = '!less -r /path/to_manual"
1176 macro generic <F1> "$user_manualcmd<enter>" "Show manual"
1177 macro pager <F1> "$user_manualcmd<enter>" "Show manual"
1178 macro index <F1> "$user_manualcmd<enter>" "Show manual"
1180 Using this feature, arbitrary sequences can be defined once and recalled and
1181 reused where necessary. More advanced scenarios could include to save a vari-
1182 able's value at the beginning of macro sequence and restore it at end.
1184 When the variable is first defined, the first value it gets assigned is also
1185 the initial value to which it can be reset using the reset command.
1187 The complete removal is done via the unset keyword.
1189 After the following sequence:
1194 the variable $user_foo has a current value of 666 and an initial of 42. The
1199 will show 666. After doing the reset via
1203 a following query will give 42 as the result. After unsetting it via
1205 The Mutt Next Generation E-Mail Client 25
1209 any query or operation (except the noted expansion within other statements)
1210 will lead to an error message.
1212 _
\b3_
\b._
\b3_
\b._
\b5 _
\bT_
\by_
\bp_
\be _
\bC_
\bo_
\bn_
\bv_
\be_
\br_
\bs_
\bi_
\bo_
\bn_
\bs
1214 A note about variable's types during conversion: internally values are stored
1215 in internal types but for any dump/query or set operation they're converted to
1216 and from string. That means that there's no need to worry about types when ref-
1217 erencing any variable. As an example, the following can be used without harm
1218 (besides makeing muttng very likely behave strange):
1221 set folder = $read_inc
1222 set read_inc = $folder
1223 set user_magic_number = 42
1224 set folder = $user_magic_number
1226 _
\b3_
\b._
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1228 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1230 It's usually very cumbersome to remember or type out the address of someone you
1231 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1232 short string to a full address.
1234 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1235 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1237 To remove an alias or aliases (``*'' means all aliases):
1239 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1241 alias muttdude me@cs.hmc.edu (Michael Elkins)
1242 alias theguys manny, moe, jack
1244 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1245 cial file. The alias command can appear anywhere in a configuration file, as
1246 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.29 , page 45). Consequently, you can
1247 have multiple alias files, or you can have all aliases defined in your muttrc.
1249 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
1250 only one file, the one pointed to by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.5 , page 89)
1251 variable (which is ~/.muttrc by default). This file is not special either, in
1252 the sense that Mutt-ng will happily append aliases to any file, but in order
1253 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1254 3.29 , page 45) this file too.
1256 The Mutt Next Generation E-Mail Client 26
1260 source /usr/local/share/Mutt-ng.aliases
1261 source ~/.mail_aliases
1262 set alias_file=~/.mail_aliases
1264 To use aliases, you merely use the alias at any place in mutt where mutt
1265 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1266 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
1267 (section 7.4.59 , page 102) variable set.
1269 In addition, at the various address prompts, you can use the tab character to
1270 expand a partial alias to the full alias. If there are multiple matches, mutt
1271 will bring up a menu with the matching aliases. In order to be presented with
1272 the full list of aliases, you must hit tab with out a partial alias, such as at
1273 the beginning of the prompt or after a comma denoting multiple addresses.
1275 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1276 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1279 _
\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
1281 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1283 This command allows you to change the default key bindings (operation invoked
1284 when pressing a key).
1286 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be speci-
1287 fied by separating them with commas (no additional whitespace is allowed). The
1288 currently defined maps are:
1291 This is not a real menu, but is used as a fallback for all of the
1292 other menus except for the pager and editor modes. If a key is not
1293 defined in another menu, Mutt-ng will look for a binding to use in
1294 this menu. This allows you to bind a key to a certain function in
1295 multiple menus instead of having multiple bind statements to accom-
1296 plish the same task.
1299 The alias menu is the list of your personal aliases as defined in
1300 your muttrc. It is the mapping from a short alias name to the full
1301 email address(es) of the recipient(s).
1304 The attachment menu is used to access the attachments on received
1307 The Mutt Next Generation E-Mail Client 27
1310 The browser is used for both browsing the local directory struc-
1311 ture, and for listing all of your incoming mailboxes.
1314 The editor is the line-based editor the user enters text data.
1317 The index is the list of messages contained in a mailbox.
1320 The compose menu is the screen used when sending a new message.
1323 The pager is the mode used to display message/attachment data, and
1327 The pgp menu is used to select the OpenPGP keys used for encrypting
1331 The postpone menu is similar to the index menu, except is used when
1332 recalling a message the user was composing, but saved until later.
1334 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1335 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1336 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1337 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
1338 alternative form is to specify the key as a three digit octal number prefixed
1339 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1341 In addition, _
\bk_
\be_
\by may consist of:
1343 The Mutt Next Generation E-Mail Client 28
1347 <backtab> backtab / shift-tab
1357 <pagedown> Page Down
1358 <backspace> Backspace
1367 <f10> function key 10
1369 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1371 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1372 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 174). The special
1373 function noop unbinds the specified key sequence.
1375 _
\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
1377 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1379 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1381 The charset-hook command defines an alias for a character set. This is useful
1382 to properly display messages which are tagged with a character set name not
1385 The iconv-hook command defines a system-specific name for a character set.
1386 This is helpful when your systems character conversion library insists on using
1387 strange, system-specific names for character sets.
1389 _
\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
1391 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1393 It is often desirable to change settings based on which mailbox you are
1395 The Mutt Next Generation E-Mail Client 29
1397 reading. The folder-hook command provides a method by which you can execute
1398 any configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1399 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1400 folder-hook's, they are executed in the order given in the muttrc.
1402 N
\bNo
\bot
\bte
\be:
\b: if you use the ``!'' shortcut for _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page
1403 162) at the beginning of the pattern, you must place it inside of double or
1404 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1407 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1408 ple, a command action to perform is to change the sorting method based upon the
1411 folder-hook mutt set sort=threads
1413 However, the sorting method is not restored to its previous value when reading
1414 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1416 folder-hook . set sort=date-sent
1418 _
\b3_
\b._
\b8 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1420 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 ]
1422 Macros are useful when you would like a single key to perform a series of
1423 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1424 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1425 create a macro to execute those commands with a single key.
1427 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.5 , page 26) which the macro will be bound. Multi-
1428 ple maps may be specified by separating multiple menu arguments by commas.
1429 Whitespace may not be used in between the menu arguments and the commas sepa-
1432 _
\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
1433 3.5 , page 26). There are some additions however. The first is that control
1434 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1435 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1436 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
1437 _
\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
1438 3.5 , page 26). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1441 The advantage with using function names directly is that the macros will work
1442 regardless of the current key bindings, so they are not dependent on the user
1443 having particular key definitions. This makes them more robust and portable,
1444 and also facilitates defining of macros in files used by more than one user
1446 The Mutt Next Generation E-Mail Client 30
1448 (eg. the system Muttngrc).
1450 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1453 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1454 truncated at the screen width, and are not wrapped.
1456 _
\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
1458 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 ]
1460 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
1462 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1464 If your terminal supports color, you can spice up Mutt-ng by creating your own
1465 color scheme. To define the color of an object (type of information), you must
1466 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1467 only specify one or the other).
1469 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1473 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1475 +
\bo bold (highlighting bold patterns in the body of messages)
1477 +
\bo error (error messages printed by Mutt-ng)
1479 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1481 +
\bo hdrdefault (default color of the message header in the pager)
1483 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1485 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1487 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1489 +
\bo message (informational messages)
1493 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.231 , page 144) in the
1496 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1498 +
\bo search (highlighting of words in the pager)
1500 The Mutt Next Generation E-Mail Client 31
1504 +
\bo status (mode lines used to display info about the mailbox or message)
1506 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1508 +
\bo tree (thread tree drawn in the message index and attachment menu)
1510 +
\bo underline (highlighting underlined patterns in the body of messages)
1512 _
\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:
1534 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the fore-
1535 ground color boldfaced (e.g., brightred).
1537 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1538 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1539 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-
1540 ment variable to the default colors of your terminal for this to work; for
1541 example (for Bourne-like shells):
1543 set COLORFGBG="green;black"
1546 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
1547 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1549 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1550 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1551 command for it to be removed. The pattern ``*'' is a special token which means
1552 to clear the color index list of all entries.
1554 The Mutt Next Generation E-Mail Client 32
1556 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
1557 number of colors supported by your terminal). This is useful when you remap
1558 the colors for your display (for example by changing the color associated with
1559 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1561 If your terminal does not support color, it is still possible change the video
1562 attributes through the use of the ``mono'' command:
1564 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 ]
1566 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1568 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1570 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1582 _
\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
1584 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1586 Messages often have many header fields added by automatic processing systems,
1587 or which may not seem useful to display on the screen. This command allows you
1588 to specify header fields which you don't normally want to see.
1590 You do not need to specify the full header field name. For example, ``ignore
1591 content-'' will ignore all header fields that begin with the pattern ``con-
1592 tent-''. ``ignore *'' will ignore all headers.
1594 To remove a previously added token from the list, use the ``unignore'' command.
1595 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1596 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1599 ``unignore *'' will remove all tokens from the ignore list.
1603 # Sven's draconian header weeding
1605 unignore from date subject to cc
1606 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1609 The Mutt Next Generation E-Mail Client 33
1611 _
\b3_
\b._
\b1_
\b1 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1613 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1615 With various functions, mutt will treat messages differently, depending on
1616 whether you sent them or whether you received them from someone else. For
1617 instance, when replying to a message that you sent to a different party, mutt
1618 will automatically suggest to send the response to the original message's
1619 recipients -- responding to yourself won't make much sense in many cases. (See
1620 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.239 , page 146).)
1622 Many users receive e-mail under a number of different addresses. To fully use
1623 mutt's features here, the program must be able to recognize what e-mail
1624 addresses you receive mail under. That's the purpose of the alternates command:
1625 It takes a list of regular expressions, each of which can identify an address
1626 under which you receive e-mail.
1628 The unalternates command can be used to write exceptions to alternates pat-
1629 terns. If an address matches something in an alternates command, but you none-
1630 theless do not think it is from you, you can list a more precise pattern under
1631 an unalternates command.
1633 To remove a regular expression from the alternates list, use the unalternates
1634 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1635 command matches an entry on the unalternates list, that unalternates entry will
1636 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
1639 _
\b3_
\b._
\b1_
\b2 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1641 _
\b3_
\b._
\b1_
\b2_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
1643 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1644 ning of email, each message had a fixed line width, and it was enough for dis-
1645 playing them on fixed-size terminals. But times changed, and nowadays hardly
1646 anybody still uses fixed-size terminals: more people nowaydays use graphical
1647 user interfaces, with dynamically resizable windows. This led to the demand of
1648 a new email format that makes it possible for the email client to make the
1649 email look nice in a resizable window without breaking quoting levels and cre-
1650 ating an incompatible email format that can also be displayed nicely on old
1651 fixed-size terminals.
1653 For introductory information on format=flowed messages, see
1654 <http://www.joeclark.org/ffaq.html>.
1656 _
\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
1658 When you receive emails that are marked as format=flowed messages, and is for-
1659 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1660 your terminal. If you want a fixed margin on the right side of your terminal,
1661 you can set the following:
1663 The Mutt Next Generation E-Mail Client 34
1667 The code above makes the line break 10 columns before the right side of the
1670 If your terminal is so wide that the lines are embarrassingly long, you can
1671 also set a maximum line length:
1673 set max_line_length = 120
1675 The example above will give you lines not longer than 120 characters.
1677 When you view at format=flowed messages, you will often see the quoting hierar-
1678 chy like in the following example:
1680 >Bill, can you please send last month's progress report to Mr.
1681 >Morgan? We also urgently need the cost estimation for the new
1682 >production server that we want to set up before our customer's
1683 >project will go live.
1685 This obviously doesn't look very nice, and it makes it very hard to differenti-
1686 ate between text and quoting character. The solution is to configure mutt-ng to
1687 "stuff" the quoting:
1691 This will lead to a nicer result that is easier to read:
1693 > Bill, can you please send last month's progress report to Mr.
1694 > Morgan? We also urgently need the cost estimation for the new
1695 > production server that we want to set up before our customer's
1696 > project will go live.
1698 _
\b3_
\b._
\b1_
\b2_
\b._
\b3 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg
1700 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1705 The Mutt Next Generation E-Mail Client 35
1707 Additionally, you have to use an editor which supports writing format=flowed-
1708 conforming emails. For vim, this is done by adding w to the formatoptions (see
1709 :h formatoptions and :h fo-table) when writing emails.
1711 Also note that _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\b=_
\bf_
\bl_
\bo_
\bw_
\be_
\bd knows about ``space-stuffing'', that is, when
1712 sending messages, some kinds of lines have to be indented with a single space
1713 on the sending side. On the receiving side, the first space (if any) is
1714 removed. As a consequence and in addition to the above simple setting, please
1715 keep this in mind when making manual formattings within the editor. Also note
1716 that mutt-ng currently violates the standard (RfC 3676) as it does not space-
1717 stuff lines starting with:
1719 +
\bo > This is _
\bn_
\bo_
\bt the quote character but a right angle used for other reasons
1721 +
\bo From with a trailing space.
1723 +
\bo just a space for formatting reasons
1725 Please make sure that you manually prepend a space to each of them.
1727 _
\b3_
\b._
\b1_
\b2_
\b._
\b4 _
\bA_
\bd_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bN_
\bo_
\bt_
\be_
\bs
1731 For completeness, the _
\b$_
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.51 , page 100) variable pro-
1732 vides the mechanism to generate a DelSp=yes parameter on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages.
1733 According to the standard, clients receiving a format=flowed messages should
1734 delete the last space of a flowed line but still interpret the line as flowed.
1735 Because flowed lines usually contain only one space at the end, this parameter
1736 would make the receiving client concatenate the last word of the previous with
1737 the first of the current line _
\bw_
\bi_
\bt_
\bh_
\bo_
\bu_
\bt a space. This makes ordinary text unread-
1738 able and is intended for languages rarely using spaces. So please use this set-
1739 ting only if you're sure what you're doing.
1741 _
\b3_
\b._
\b1_
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1743 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1745 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1747 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 ,
1748 page 60). In order to take advantage of them, you must specify which addresses
1749 belong to mailing lists, and which mailing lists you are subscribed to. Once
1750 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1751 work for all known lists. Additionally, when you send a message to a sub-
1752 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1753 user agents not to send copies of replies to your personal address. Note that
1754 the Mail-Followup-To header is a non-standard extension which is not supported
1755 by all mail user agents. Adding it is not bullet-proof against receiving per-
1756 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1757 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.71 , page 105)
1758 configuration variable.
1760 The Mutt Next Generation E-Mail Client 36
1762 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1763 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1764 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1767 You can use regular expressions with both commands. To mark all messages sent
1768 to a specific bug report's address on mutt's bug tracking system as list mail,
1769 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1770 sufficient to just give a portion of the list's e-mail address.
1772 Specify as much of the address as you need to to remove ambiguity. For exam-
1773 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1774 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
1775 list, you could add ``lists mutt-users'' to your initialization file. To tell
1776 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1777 tialization file instead. If you also happen to get mail from someone whose
1778 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-
1779 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1780 from the actual list.
1782 The ``unlists'' command is used to remove a token from the list of known and
1783 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1785 To remove a mailing list from the list of subscribed mailing lists, but keep it
1786 on the list of known mailing lists, use ``unsubscribe''.
1788 _
\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
1790 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1792 This command is used to move read messages from a specified mailbox to a dif-
1793 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1794 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1795 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1797 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1798 (it is not possible to save read mail in more than a single mailbox).
1800 _
\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
1802 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1804 This command specifies folders which can receive mail and which will be checked
1805 for new messages. By default, the main menu status bar displays how many of
1806 these folders have new messages.
1808 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1810 Pressing TAB in the directory browser will bring up a menu showing the files
1811 specified by the mailboxes command, and indicate which contain new messages.
1813 The Mutt Next Generation E-Mail Client 37
1815 Mutt-ng will automatically enter this mode when invoked from the command line
1818 The ``unmailboxes'' command is used to remove a token from the list of folders
1819 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1821 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1822 access time. Utilities like biff or frm or any other program which accesses
1823 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1824 they do not properly reset the access time. Backup tools are another common
1825 reason for updated access times.
1827 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1828 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
1829 60) (such as ``='' and ``!''), any variable definition that affect these char-
1830 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1831 7.4.303 , page 162)) should be executed before the mailboxes command.
1833 _
\b3_
\b._
\b1_
\b6 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1837 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1839 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1841 The ``my_hdr'' command allows you to create your own header fields which will
1842 be added to every message you send.
1844 For example, if you would like to add an ``Organization:'' header field to all
1845 of your outgoing messages, you can put the command
1847 my_hdr Organization: A Really Big Company, Anytown, USA
1851 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1852 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1853 there, so Mutt-ng enforces the rule.
1855 If you would like to add a header field to a single message, you should either
1856 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1857 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1858 header of your message along with the body.
1860 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1861 specify an asterisk (``*'') to remove all header fields, or the fields to
1862 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1865 The Mutt Next Generation E-Mail Client 38
1869 _
\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
1871 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1873 With this command, you can specify an order in which mutt will attempt to
1874 present headers to you when viewing messages.
1876 ``unhdr_order *'' will clear all previous headers from the order list, thus
1877 removing the header order effects set by the system-wide startup file.
1879 hdr_order From Date: From: To: Cc: Subject:
1881 _
\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
1883 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1885 This command is used to override the default filename used when saving mes-
1886 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:
1887 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1888 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1890 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1891 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1895 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1896 save-hook aol\\.com$ +spam
1898 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39) command.
1900 _
\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
1902 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1904 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1905 (section 7.4.236 , page 146). Mutt-ng searches the initial list of message
1906 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1907 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1908 7.4.236 , page 146) mailbox.
1910 The Mutt Next Generation E-Mail Client 39
1912 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1913 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1915 Example: fcc-hook [@.]aol\\.com$ +spammers
1917 The above will save a copy of all messages going to the aol.com domain to the
1918 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 ,
1921 _
\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
1923 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1925 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1926 3.19 , page 38) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38) with its arguments.
1928 _
\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
1930 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1932 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1934 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1936 These commands can be used to execute arbitrary configuration commands based
1937 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1938 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1941 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1942 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1943 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
1944 the order specified in the users's configuration file.
1946 send2-hook is matched every time a message is changed, either by editing it, or
1947 by using the compose menu to change its recipients or subject. send2-hook is
1948 executed after send-hook, and can, e.g., be used to set parameters such as the
1949 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page 150) variable depending on the message's
1952 For each type of send-hook or reply-hook, when multiple matches occur, commands
1953 are executed in the order they are specified in the muttrc (for that type of
1956 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1957 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1959 Example: send-hook mutt 'set mime_forward signature='''
1961 Another typical use for this command is to change the values of the
1963 The Mutt Next Generation E-Mail Client 40
1965 _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 93), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.265 , page
1966 153) and _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.119 , page 118) variables in order to change the
1967 language of the attributions and signatures based upon the recipients.
1969 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
1970 recipients. Adding a recipient after replying or editing the message will NOT
1971 cause any send-hook to be executed. Also note that my_hdr commands which mod-
1972 ify recipient headers, or the message's subject, don't have any effect on the
1973 current message when executed from a send-hook.
1975 _
\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
1977 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1979 This command can be used to execute arbitrary configuration commands before
1980 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
1981 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
1982 tiple matches occur, commands are executed in the order they are specified in
1985 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 57) for information on the
1986 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1990 message-hook ~A 'set pager=builtin'
1991 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1993 _
\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
1995 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
1997 When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
1998 tain key with a given e-mail address automatically, either because the recipi-
1999 ent's public key can't be deduced from the destination address, or because, for
2000 some reasons, you need to override the key Mutt-ng would normally use. The
2001 crypt-hook command provides a method by which you can specify the ID of the
2002 public key to be used when encrypting messages to a certain recipient.
2004 The meaning of "key id" is to be taken broadly in this context: You can either
2005 put a numerical key ID here, an e-mail address, or even just a real name.
2007 _
\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
2009 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
2011 This command adds the named string to the keyboard buffer. The string may
2013 The Mutt Next Generation E-Mail Client 41
2015 contain control characters, key names and function names like the sequence
2016 string in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 29) command. You may use it to auto-
2017 matically run a sequence of commands at startup, or when entering certain fold-
2020 _
\b3_
\b._
\b2_
\b5 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
2022 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
2024 This command can be used to execute any function. Functions are listed in the
2025 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 174). ``exec function'' is equivalent
2026 to ``push <function>''.
2028 _
\b3_
\b._
\b2_
\b6 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
2030 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
2032 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
2034 In situations where you have to cope with a lot of emails, e.g. when you read
2035 many different mailing lists, and take part in discussions, it is always useful
2036 to have the important messages marked and the annoying messages or the ones
2037 that you aren't interested in deleted. For this purpose, mutt-ng features a
2038 mechanism called ``scoring''.
2040 When you use scoring, every message has a base score of 0. You can then use the
2041 score command to define patterns and a positive or negative value associated
2042 with it. When a pattern matches a message, the message's score will be raised
2043 or lowered by the amount of the value associated with the pattern.
2045 score "~f nion@muttng\.org" 50
2046 score "~f @sco\.com" -100
2048 If the pattern matches, it is also possible to set the score value of the cur-
2049 rent message to a certain value and then stop evaluation:
2051 score "~f santaclaus@northpole\.int" =666
2053 What is important to note is that negative score values will be rounded up to
2056 To make scoring actually useful, the score must be applied in some way. That's
2057 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:
2059 +
\bo flag threshold: when a message has a score value equal or higher than the
2060 flag threshold, it will be flagged.
2062 The Mutt Next Generation E-Mail Client 42
2064 +
\bo read threshold: when a message has a score value equal or lower than the
2065 read threshold, it will be marked as read.
2067 +
\bo delete threshold: when a message has a score value equal or lower than the
2068 delete threshold, it will be marked as deleted.
2070 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-
2071 tion 7.4.250 , page 149), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.251 , page 149),
2072 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.249 , page 149) and. By default,
2073 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.251 , page 149) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
2074 (section 7.4.249 , page 149) are set to -1, which means that in the default
2075 threshold configuration no message will ever get marked as read or deleted.
2077 Scoring gets especially interesting when combined with the color command and
2080 color black yellow "~n 10-"
2081 color red yellow "~n 100-"
2083 The rules above mark all messages with a score between 10 and 99 with black and
2084 yellow, and messages with a score greater or equal 100 with red and yellow.
2085 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
2086 but it is more flexible, as it visually marks different scores.
2088 _
\b3_
\b._
\b2_
\b7 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
2090 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2092 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
2094 Mutt-ng has generalized support for external spam-scoring filters. By defining
2095 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
2096 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
2097 filter. You also can display the spam attributes in your index display using
2098 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) variable.
2099 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
2102 Your first step is to define your external filter's spam patterns using the
2103 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
2104 mail message. If any message in the mailbox matches this regular expression, it
2105 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
2106 nospam pattern -- see below.) The appearance of this attribute is entirely up
2107 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,
2108 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
2109 expression ``back-reference'' refers to a sub-expression contained within
2110 parentheses.) %1 is replaced with the first back-reference in the regex, %2
2111 with the second, etc.
2113 If you're using multiple spam filters, a message can have more than one spam-
2115 The Mutt Next Generation E-Mail Client 43
2117 related header. You can define spam patterns for each filter you use. If a mes-
2118 sage matches two or more of these patterns, and the $spam_separator variable is
2119 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2120 strings joined together, with the value of $spam_separator separating them.
2122 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
2123 these spam settings:
2125 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
2126 spam "X-Spam-Status: Yes" "90+/SA"
2127 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
2128 set spam_separator=", "
2130 If I then received a message that DCC registered with ``many'' hits under the
2131 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
2132 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
2133 characters before ``=many'' in a DCC report indicate the checksum used -- in
2134 this case, ``Fuz2''.)
2136 If the $spam_separator variable is unset, then each spam pattern match super-
2137 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
2138 only the last one to match.
2140 The spam tag is what will be displayed in the index when you use %H in the
2141 $index_format variable. It's also the string that the ~H pattern-matching
2142 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2143 ing by spam attribute will use as a sort key.
2145 That's a pretty complicated example, and most people's actual environments will
2146 have only one spam filter. The simpler your configuration, the more effective
2147 mutt can be, especially when it comes to sorting.
2149 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2150 ordering strings alphnumerically. However, if a spam tag begins with a number,
2151 mutt will sort numerically first, and lexically only when two numbers are equal
2152 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2153 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2154 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2155 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2156 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2157 coerce your filter to give you a raw number. But in case you can't, mutt can
2158 still do something useful.
2160 The nospam command can be used to write exceptions to spam patterns. If a
2161 header pattern matches something in a spam command, but you nonetheless do not
2162 want it to receive a spam tag, you can list a more precise pattern under a
2165 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-
2166 ing spam list entry, the effect will be to remove the entry from the spam list,
2167 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2168 matches an entry on the nospam list, that nospam entry will be removed. If the
2169 _
\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
2171 The Mutt Next Generation E-Mail Client 44
2173 might be the default action if you use spam and nospam in conjunction with a
2176 You can have as many spam or nospam commands as you like. You can even do your
2177 own primitive spam detection within mutt -- for example, if you consider all
2178 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2180 spam "^From: .*MAILER-DAEMON" "999"
2182 _
\b3_
\b._
\b2_
\b8 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2184 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 ... ]
2186 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2188 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2190 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2192 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 ,
2193 page 87). There are four basic types of variables: boolean, number, string and
2194 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
2195 variables can be assigned a positive integer value.
2197 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2198 be enclosed in quotes if they contain spaces or tabs. You may also use the
2199 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2201 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2202 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2203 action to be carried out automatically as if you had answered yes to the ques-
2204 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2205 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2206 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2208 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2210 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2211 toggle the value (on or off). This is useful when writing macros. Example:
2214 The toggle command automatically prepends the inv prefix to all specified vari-
2217 The unset command automatically prepends the no prefix to all specified vari-
2220 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2221 a variable by prefixing the name of the variable with a question mark:
2223 The Mutt Next Generation E-Mail Client 45
2227 The question mark is actually only required for boolean and quadoption vari-
2230 The reset command resets all given variables to the compile time defaults
2231 (hopefully mentioned in this manual). If you use the command set and prefix the
2232 variable with ``&'' this has the same behavior as the reset command.
2234 With the reset command there exists the special variable ``all'', which allows
2235 you to reset all variables to their system defaults.
2237 _
\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
2239 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2241 This command allows the inclusion of initialization commands from other files.
2242 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2243 ~/.muttrc readable and keep my aliases private.
2245 If the filename begins with a tilde (``~''), it will be expanded to the path of
2246 your home directory.
2248 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2249 an executable program from which to read input (eg. source ~/bin/myscript|).
2251 _
\b3_
\b._
\b3_
\b0 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2253 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2255 This command permits you to flush hooks you have previously defined. You can
2256 either remove all hooks by giving the ``*'' character as an argument, or you
2257 can remove all hooks of a specific type by saying something like unhook send-
2260 _
\b3_
\b._
\b3_
\b1 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2262 _
\b3_
\b._
\b3_
\b1_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2264 As users may run mutt-ng on different systems, the configuration must be main-
2265 tained because it's likely that people want to use the setup everywhere they
2266 use mutt-ng. And mutt-ng tries to help where it can.
2268 To not produce conflicts with different character sets, mutt-ng allows users to
2269 specify in which character set their configuration files are encoded. Please
2270 note that while reading the configuration files, this is only respected after
2271 the corresponding declaration appears. It's advised to put the following at the
2273 The Mutt Next Generation E-Mail Client 46
2275 very beginning of a users muttngrc:
2277 set config_charset = "..."
2279 and replacing the dots with the actual character set. To avoid problems while
2280 maintaining the setup, vim user's may want to use modelines as show in:
2282 # vim:fileencoding=...:
2284 while, again, replacing the dots with the appropriate name. This tells vim as
2285 which character set to read and save the file.
2287 _
\b3_
\b._
\b3_
\b1_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2289 ``Modularization'' means to divide the setup into several files while sorting
2290 the options or commands by topic. Especially for longer setups (e.g. with many
2291 hooks), this helps maintaining it and solving trouble.
2293 When using separation, setups may be, as a whole or in fractions, shared over
2296 _
\b3_
\b._
\b3_
\b1_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2298 When using a configuration on different systems, the user may not always have
2299 influence on how mutt-ng is installed and which features it includes.
2301 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2302 for mutt. Its basic syntax is:
2304 ifdef <item> <command>
2305 ifndef <item> <command>
2307 ...whereby <item> can be one of:
2309 +
\bo a function name
2311 +
\bo a variable name
2317 All available functions, variables and menus are documented elsewhere in this
2318 manual but ``features'' is specific to these two commands. To test for one,
2320 The Mutt Next Generation E-Mail Client 47
2322 prefix one of the following keywords with feature_:
2324 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2325 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2326 classic_smime, gpgme, header_cache
2328 As an example, one can use the following in ~/.muttngrc:
2330 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2331 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2332 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2334 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2335 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2336 ng/setup-nntp if NNTP support is built in.
2338 An example for testing for variable names can be used if users use different
2339 revisions of mutt-ng whereby the older one may not have a certain variable. To
2340 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.104 , page 113),
2343 ifdef imap_mail_check 'set imap_mail_check = 300'
2345 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
2346 (section 7.4.175 , page 132) only if the pager menu is available, use:
2348 ifdef pager 'set pager_index_lines = 10'
2350 For completeness, too, the opposite of ifdef is provided: ifndef which only
2351 executes the command if the test fails. For example, the following two examples
2354 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2355 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2359 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2360 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2362 The Mutt Next Generation E-Mail Client 48
2364 _
\b3_
\b._
\b3_
\b2 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2366 In the process of ensuring and creating more consistency, many variables have
2367 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2368 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 87) for a complete list.
2370 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2372 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2374 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2375 tion 7.2 , page 83) must be specified using regular expressions (regexp) in
2376 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2377 and GNU awk). For your convenience, we have included below a brief description
2380 The search is case sensitive if the pattern contains at least one upper case
2381 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2382 for a regular expression in an initialization command: ``\\''.
2384 A regular expression is a pattern that describes a set of strings. Regular
2385 expressions are constructed analogously to arithmetic expressions, by using
2386 various operators to combine smaller expressions.
2388 Note that the regular expression can be enclosed/delimited by either ' or '
2389 which is useful if the regular expression includes a white-space character.
2390 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-
2391 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2392 ace it with \ (backslash).
2394 The fundamental building blocks are the regular expressions that match a single
2395 character. Most characters, including all letters and digits, are regular
2396 expressions that match themselves. Any metacharacter with special meaning may
2397 be quoted by preceding it with a backslash.
2399 The period ``.'' matches any single character. The caret ``^'' and the dollar
2400 sign ``$'' are metacharacters that respectively match the empty string at the
2401 beginning and end of a line.
2403 A list of characters enclosed by ``['' and ``]'' matches any single character
2404 in that list; if the first character of the list is a caret ``^'' then it
2405 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2406 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2407 specified by giving the first and last characters, separated by a hyphen ``-''.
2408 Most metacharacters lose their special meaning inside lists. To include a lit-
2409 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2410 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2413 The Mutt Next Generation E-Mail Client 49
2415 Certain named classes of characters are predefined. Character classes consist
2416 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2417 defined by the POSIX standard:
2420 Alphanumeric characters.
2423 Alphabetic characters.
2426 Space or tab characters.
2435 Characters that are both printable and visible. (A space is print-
2436 able, but not visible, while an ``a'' is both.)
2439 Lower-case alphabetic characters.
2442 Printable characters (characters that are not control characters.)
2445 Punctuation characters (characters that are not letter, digits,
2446 control characters, or space characters).
2449 Space characters (such as space, tab and formfeed, to name a few).
2452 Upper-case alphabetic characters.
2455 Characters that are hexadecimal digits.
2457 A character class is only valid in a regular expression inside the brackets of
2458 a character list. Note that the brackets in these class names are part of the
2459 symbolic names, and must be included in addition to the brackets delimiting the
2460 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].
2462 Two additional special sequences can appear in character lists. These apply to
2463 non-ASCII character sets, which can have single symbols (called collating ele-
2464 ments) that are represented with more than one character, as well as several
2465 characters that are equivalent for collating or sorting purposes:
2468 A collating symbol is a multi-character collating element enclosed
2470 The Mutt Next Generation E-Mail Client 50
2472 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2473 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2474 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2477 An equivalence class is a locale-specific name for a list of char-
2478 acters that are equivalent. The name is enclosed in ``[='' and
2479 ``=]''. For example, the name ``e'' might be used to represent all
2480 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2481 matches any of ``'', ``'' and ``e''.
2483 A regular expression matching a single character may be followed by one of sev-
2484 eral repetition operators:
2487 The preceding item is optional and matched at most once.
2490 The preceding item will be matched zero or more times.
2493 The preceding item will be matched one or more times.
2496 The preceding item is matched exactly _
\bn times.
2499 The preceding item is matched _
\bn or more times.
2502 The preceding item is matched at most _
\bm times.
2505 The preceding item is matched at least _
\bn times, but no more than _
\bm
2508 Two regular expressions may be concatenated; the resulting regular expression
2509 matches any string formed by concatenating two substrings that respectively
2510 match the concatenated subexpressions.
2512 Two regular expressions may be joined by the infix operator ``|''; the result-
2513 ing regular expression matches any string matching either subexpression.
2515 Repetition takes precedence over concatenation, which in turn takes precedence
2516 over alternation. A whole subexpression may be enclosed in parentheses to
2517 override these precedence rules.
2519 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2520 may also be used in regular expressions:
2523 Matches the empty string at either the beginning or the end of a
2526 The Mutt Next Generation E-Mail Client 51
2529 Matches the empty string within a word.
2532 Matches the empty string at the beginning of a word.
2535 Matches the empty string at the end of a word.
2538 Matches any word-constituent character (letter, digit, or under-
2542 Matches any character that is not word-constituent.
2545 Matches the empty string at the beginning of a buffer (string).
2548 Matches the empty string at the end of a buffer.
2550 Please note however that these operators are not defined by POSIX, so they may
2551 or may not be available in stock libraries on various systems.
2553 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2555 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2556 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2557 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2558 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2559 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83) in the Reference chapter.
2561 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2562 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2565 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2567 It is possible to combine several sub-patterns to a more complex pattern. The
2568 most simple possibility is to logically AND several patterns by stringing them
2573 The pattern above matches all messages that contain ``SPAM'' in the subject and
2576 To logical OR patterns, simply use the | operator. This one especially useful
2577 when using local groups:
2579 The Mutt Next Generation E-Mail Client 52
2581 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2582 (~b mutt-ng|~s Mutt-ng)
2585 The first pattern matches all messages that were sent by one of the mutt-ng
2586 maintainers, while the seconds pattern matches all messages that contain
2587 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2588 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2589 ences: header, i.e. messages that are not an (indirect) reply to one of my
2590 messages. A pattern can be logicall negated using the ! operator.
2592 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2594 When using dates in patterns, the dates must be specified in a special format,
2595 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2596 rent month or year. When using date ranges, and you specify only the minimum or
2597 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2598 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2600 It is also possible to use so-called ``error margins'' when specifying date
2601 ranges. You simply specify a date, and then the error margin. This margin
2602 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2603 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2604 months, w for weeks and d for days. If you use the special * sign, it means
2605 that the error margin goes to both ``directions'' in time.
2611 The first pattern matches all dates between January 1st, 2005 and January 1st
2612 2006. The second pattern matches all dates between October 18th, 2004 and
2613 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2614 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2616 Relative dates are also very important, as they make it possible to specify
2617 date ranges between a fixed number of units and the current date. How this
2618 works can be seen in the following example:
2620 ~d >2w # messages older than two weeks
2621 ~d <3d # messages newer than 3 days
2622 ~d =1m # messages that are exactly one month old
2624 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2626 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2628 The Mutt Next Generation E-Mail Client 53
2630 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2631 In short, they describe what items to print out how in menus and status mes-
2634 Basically, they work as this: for different menus and bars, there's a variable
2635 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2637 For example, when running mutt-ng on different machines or different versions
2638 for testing purposes, it may be interesting to have the following information
2639 always printed on screen when one is in the index:
2641 +
\bo the current hostname
2643 +
\bo the current mutt-ng version number
2645 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-
2646 _
\bm_
\ba_
\bt (section 7.4.314 , page 164) variable. For the hostname and version
2647 string, there's an expando for $status_format: %h expands to the hostname and
2648 %v to the version string. When just configuring:
2650 set status_format = "%v on %h: ..."
2652 mutt-ng will replace the sequence %v with the version string and %h with the
2653 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2654 mailhost, you'll see the following when you're in the index:
2656 Mutt-ng 1.5.9i on mailhost: ...
2658 In the index, there're more useful information one could want to see:
2660 +
\bo which mailbox is open
2662 +
\bo how man new, flagged or postponed messages
2666 To include the mailbox' name is as easy as:
2668 set status_format = "%v on %h: %B: ...
2670 When the currently opened mailbox is Inbox, this will be expanded to:
2672 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2674 For the number of certain types of messages, one more feature of the format
2675 strings is extremely useful. If there aren't messages of a certain type, it may
2677 The Mutt Next Generation E-Mail Client 54
2679 not be desired to print just that there aren't any but instead only print some-
2680 thing if there are any.
2682 _
\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
2684 To only print the number of messages if there are new messages in the current
2685 mailbox, further extend $status_format to:
2687 set status_format = "%v on %h: %B %?n?%n new? ...
2689 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
2690 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2691 ated if the value of the expando is different from zero. The basic syntax is:
2693 %?<item>?<string if nonzero>?
2695 which tells mutt-ng to only look at <string if nonzero> if the value of the
2696 %<item%gt; expando is different from zero. In our example, we used n as the
2697 expando to check for and %n new as the optional nonzero string.
2699 But this is not all: this feature only offers one alternative: ``print some-
2700 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2701 complete version: ``if zero, print something and else print something else.''
2702 This is achieved by the following syntax for those expandos which may be
2705 %?<item>?<string if nonzero>&<string if zero>?
2707 Using this we can make mutt-ng to do the following:
2709 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2712 +
\bo and make it print ``no new messages'' if there aren't any
2714 The corresponding configuration is:
2716 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2718 This doubles the use of the ``new messages'' string because it'll get always
2719 printed. Thus, it can be shortened to:
2721 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2723 The Mutt Next Generation E-Mail Client 55
2725 As you might see from this rather simple example, one can create very complex
2726 but fancy status messages. Please see the reference chapter for expandos and
2727 those which may be printed nonzero.
2729 _
\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
2731 Besides the information given so far, there're even more features of format
2734 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2735 characters in the expansion of <item> to lowercase.
2737 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2738 dots in the expansion of <item> to underscores (_).
2740 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2744 When this occurs, mutt-ng will fill the rest of the line with the
2745 character X. In our example, filling the rest of the line with
2746 dashes is done by setting:
2748 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2751 Since the previous expando stops at the end of line, there must be
2752 a way to fill the gap between two items via the %>X expando: it
2753 puts as many characters X in between two items so that the rest of
2754 the line will be right-justified. For example, to not put the ver-
2755 sion string and hostname of our example on the left but on the
2756 right and fill the gap with spaces, one might use (note the space
2759 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2761 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2763 Sometimes it is desirable to perform an operation on a group of messages all at
2764 once rather than one at a time. An example might be to save messages to a
2765 mailing list to a separate folder, or to delete all messages with a given sub-
2766 ject. To tag all messages matching a pattern, use the tag-pattern function,
2767 which is bound to ``shift-T'' by default. Or you can select individual mes-
2768 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2770 The Mutt Next Generation E-Mail Client 56
2772 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83) for Mutt-ng's pattern matching
2775 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2776 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2777 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2778 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.19 ,
2779 page 93) variable is set, the next operation applies to the tagged messages
2780 automatically, without requiring the ``tag-prefix''.
2782 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.8 , page 29) or _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 40) commands,
2783 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2784 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2785 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2786 this operator the rest of the macro will be executed as normal.
2788 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2790 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2791 arbitrary commands before performing some operation. For example, you may wish
2792 to tailor your configuration based upon which mailbox you are reading, or to
2793 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
2794 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 48) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 83) along
2795 with a configuration option/command. See
2797 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 28)
2799 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 39)
2801 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 40)
2803 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38)
2805 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36)
2807 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38)
2809 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39)
2811 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2813 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2814 until the end of the current mutt session. As this is generally not desired, a
2815 default hook needs to be added before all other hooks to restore configuration
2816 defaults. Here is an example with send-hook and the my_hdr directive:
2818 send-hook . 'unmy_hdr From:'
2819 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2821 The Mutt Next Generation E-Mail Client 57
2823 _
\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
2825 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2826 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2827 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 48) is sufficient. But in dealing with
2828 messages a finer grain of control is needed for matching since for different
2829 purposes you want to match different criteria.
2831 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 83) language
2832 for matching messages in hook commands. This works in exactly the same way as
2833 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
2834 to those operators which match information mutt extracts from the header of the
2835 message (i.e. from, to, cc, date, subject, etc.).
2837 For example, if you wanted to set your return address based upon sending mail
2838 to a specific address, you could do something like:
2840 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2842 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2844 However, it is not required that you write the pattern to match using the full
2845 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
2846 other hooks, in which case Mutt-ng will translate your pattern into the full
2847 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2848 7.4.49 , page 100) variable. The pattern is translated at the time the hook
2849 is declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.49 , page 100) that is
2850 in effect at that time will be used.
2852 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2854 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2855 which looks very similar to the ones you probably know from GUI mail clients.
2856 The sidebar lists all specified mailboxes, shows the number in each and high-
2857 lights the ones with new email Use the following configuration commands:
2859 set sidebar_visible="yes"
2860 set sidebar_width=25
2862 If you want to specify the mailboxes you can do so with:
2870 You can also specify the colors for mailboxes with new mails by using:
2872 The Mutt Next Generation E-Mail Client 58
2874 color sidebar_new red black
2875 color sidebar white black
2877 The available functions are:
2879 sidebar-scroll-up Scrolls the mailbox list up 1 page
2880 sidebar-scroll-down Scrolls the mailbox list down 1 page
2881 sidebar-next Highlights the next mailbox
2882 sidebar-next-new Highlights the next mailbox with new mail
2883 sidebar-previous Highlights the previous mailbox
2884 sidebar-open Opens the currently highlighted mailbox
2886 Reasonable key bindings look e.g. like this:
2888 bind index \Cp sidebar-prev
2889 bind index \Cn sidebar-next
2890 bind index \Cb sidebar-open
2891 bind pager \Cp sidebar-prev
2892 bind pager \Cn sidebar-next
2893 bind pager \Cb sidebar-open
2895 macro index B ':toggle sidebar_visible^M'
2896 macro pager B ':toggle sidebar_visible^M'
2898 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2899 off the sidebar simply by pressing 'B'.
2901 _
\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
2903 Mutt-ng supports connecting to external directory databases such as LDAP,
2904 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2905 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.227 , page 144) vari-
2906 able, you specify the wrapper command to use. For example:
2908 set query_command = "mutt_ldap_query.pl '%s'"
2910 The wrapper script should accept the query on the command-line. It should
2911 return a one line message, then each matching response on a single line, each
2912 line containing a tab separated address then name then some other optional
2913 information. On error, or if there are no matching addresses, return a non-
2914 zero exit code and a one line error message.
2916 An example multiple response output:
2918 Searching database ... 20 entries ... 3 matching:
2919 me@cs.hmc.edu Michael Elkins mutt dude
2920 blong@fiction.net Brandon Long mutt and more
2922 The Mutt Next Generation E-Mail Client 59
2924 roessler@guug.de Thomas Roessler mutt pgp
2926 There are two mechanisms for accessing the query function of mutt. One is to
2927 do a query from the index menu using the query function (default: Q). This
2928 will prompt for a query, then bring up the query menu which will list the
2929 matching responses. From the query menu, you can select addresses to create
2930 aliases, or to mail. You can tag multiple addresses to mail, start a new
2931 query, or have a new query appended to the current responses.
2933 The other mechanism for accessing the query function is for address completion,
2934 similar to the alias completion. In any prompt for address entry, you can use
2935 the complete-query function (default: ^T) to run a query based on the current
2936 address you have typed. Like aliases, mutt will look for what you have typed
2937 back to the last space or comma. If there is a single response for that query,
2938 mutt will expand the address in place. If there are multiple responses, mutt
2939 will activate the query menu. At the query menu, you can select one or more
2940 addresses to be added to the prompt.
2942 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2944 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2945 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2946 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2947 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.131 , page 121)
2950 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2951 stored in a single file. Each message has a line of the form:
2953 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2955 to denote the start of a new message (this is often referred to as the
2958 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2959 lines containing ``^A^A^A^A'' (four control-A's).
2961 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2962 and each message is stored in a separate file. The filename indicates the mes-
2963 sage number (however, this is may not correspond to the message number Mutt-ng
2964 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2965 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2966 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
2969 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
2970 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
2971 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
2972 way they are unique, even when two programs are writing the mailbox over NFS,
2974 The Mutt Next Generation E-Mail Client 60
2976 which means that no file locking is needed.
2978 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
2980 There are a number of built in shortcuts which refer to specific mailboxes.
2981 These shortcuts can be used anywhere you are prompted for a file or mailbox
2984 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page 162) (incoming)
2987 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.130 , page 121) file
2989 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146) file
2991 +
\bo ^ -- refers to the current mailbox
2993 +
\bo - or !! -- refers to the file you've last visited
2995 +
\bo ~ -- refers to your home directory
2997 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) directory
2999 +
\bo @_
\ba_
\bl_
\bi_
\ba_
\bs -- refers to the _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 3.18 , page 38) as
3000 determined by the address of the alias
3002 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
3004 Mutt-ng has a few configuration options that make dealing with large amounts of
3005 mail easier. The first thing you must do is to let Mutt know what addresses
3006 you consider to be mailing lists (technically this does not have to be a mail-
3007 ing list, but that is what it is most often used for), and what lists you are
3008 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
3009 (section 3.13 , page 35) commands in your muttrc.
3011 Now that Mutt-ng knows what your mailing lists are, it can do several things,
3012 the first of which is the ability to show the name of a list through which you
3013 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
3014 This is useful to distinguish between personal and list mail in the same mail-
3015 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) variable, the escape
3016 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
3017 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
3018 returns the name of the author).
3020 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
3021 quite large. Most people do not bother to remove the author of the message they
3022 are reply to from the list, resulting in two or more copies being sent to that
3023 person. The ``list-reply'' function, which by default is bound to ``L'' in the
3024 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
3025 mailing list addresses instead of all recipients (except as specified by Mail-
3027 The Mutt Next Generation E-Mail Client 61
3029 Followup-To, see below).
3031 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
3032 a list of recipients which includes one or several subscribed mailing lists,
3033 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.71 , page 105) option is set, mutt will
3034 generate a Mail-Followup-To header which contains all the recipients to whom
3035 you send this message, but not your address. This indicates that group-replies
3036 or list-replies (also known as ``followups'') to this message should only be
3037 sent to the original recipients of the message, and not separately to you -
3038 you'll receive your copy through one of the mailing lists you are subscribed
3041 Conversely, when group-replying or list-replying to a message which has a Mail-
3042 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
3043 (section 7.4.93 , page 110) configuration variable is set. Using list-reply
3044 will in this case also make sure that the reply goes to the mailing list, even
3045 if it's not specified in the list of recipients in the Mail-Followup-To.
3047 Note that, when header editing is enabled, you can create a Mail-Followup-To
3048 header manually. Mutt-ng will only auto-generate this header if it doesn't
3049 exist when you send the message.
3051 The other method some mailing list admins use is to generate a ``Reply-To''
3052 field which points back to the mailing list address rather than the author of
3053 the message. This can create problems when trying to reply directly to the
3054 author in private, since most mail clients will automatically reply to the
3055 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
3056 7.4.239 , page 146) variable to help decide which address to use. If set to
3057 _
\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
3058 use the address given in the ``Reply-To'' field, or reply directly to the
3059 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
3060 will be used when present.
3062 The ``X-Label:'' header field can be used to further identify mailing lists or
3063 list subject matter (or just to annotate messages individually). The
3064 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115) variable's ``%y'' and ``%Y''
3065 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
3066 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
3067 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
3068 can easily be inserted by procmail and other mail filtering agents.
3070 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160) the mail-
3071 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
3072 which all relate to the same subject. This is usually organized into a tree-
3073 like structure where a message and all of its replies are represented graphi-
3074 cally. If you've ever used a threaded news client, this is the same concept.
3075 It makes dealing with large volume mailing lists easier because you can easily
3076 delete uninteresting threads and quickly find topics of value.
3078 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3080 Mutt-ng has the ability to dynamically restructure threads that are broken
3082 The Mutt Next Generation E-Mail Client 62
3084 either by misconfigured software or bad behavior from some correspondents. This
3085 allows to clean your mailboxes formats) from these annoyances which make it
3086 hard to follow a discussion.
3088 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3090 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
3091 ences:" headers when replying to a message. This results in broken discussions
3092 because Mutt-ng has not enough information to guess the correct threading. You
3093 can fix this by tagging the reply, then moving to the parent message and using
3094 the ``link-threads'' function (bound to & by default). The reply will then be
3095 connected to this "parent" message.
3097 You can also connect multiple children at once, tagging them and using the tag-
3098 prefix command (';') or the auto_tag option.
3100 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3102 On mailing lists, some people are in the bad habit of starting a new discussion
3103 by hitting "reply" to any message from the list and changing the subject to a
3104 totally unrelated one. You can fix such threads by using the ``break-thread''
3105 function (bound by default to #), which will turn the subthread starting from
3106 the current message into a whole different thread.
3108 _
\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
3110 RFC1894 defines a set of MIME content types for relaying information about the
3111 status of electronic mail messages. These can be thought of as ``return
3114 Users can make use of it in one of the following two ways:
3116 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
3117 the mail client can make requests as to what type of status messages
3120 +
\bo The SMTP support via libESMTP supports it, too.
3122 To support this, there are two variables:
3124 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.56 , page 101) is used to request receipts for
3125 different results (such as failed message, message delivered, etc.).
3127 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.57 , page 102) requests how much of your message
3128 should be returned with the receipt (headers or full message).
3130 Please see the reference chapter for possible values.
3132 _
\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)
3134 The Mutt Next Generation E-Mail Client 63
3136 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3137 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
3138 remote POP3 server and fetch mail for local browsing.
3140 You can access the remote POP3 mailbox by selecting the folder
3143 You can select an alternative port by specifying it with the server, i.e.:
3144 pop://popserver:port/.
3146 You can also specify different username for each folder, i.e.: pop://user-
3147 name@popserver[:port]/.
3149 Polling for new mail is more expensive over POP3 than locally. For this reason
3150 the frequency at which Mutt-ng will check for mail remotely can be controlled
3151 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.214 , page 141) variable, which defaults
3152 to every 60 seconds.
3154 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3155 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3156 rally requires that the server supports SSL encrypted connections. To access a
3157 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3158 name@]popserver[:port]/.
3160 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3161 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.212 , page 140), fetch all your
3162 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page 162).
3163 After this point, Mutt-ng runs exactly as if the mail had always been local.
3165 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3166 sider using a specialized program, such as fetchmail
3168 _
\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)
3170 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3171 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
3174 You can access the remote inbox by selecting the folder
3175 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3176 INBOX is the special name for your spool mailbox on the IMAP server. If you
3177 want to access another mail folder at the IMAP server, you should use
3178 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3181 You can select an alternative port by specifying it with the server, i.e.:
3182 imap://imapserver:port/INBOX.
3184 You can also specify different username for each folder, i.e.: imap://user-
3185 name@imapserver[:port]/INBOX.
3187 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3189 The Mutt Next Generation E-Mail Client 64
3191 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3192 rally requires that the server supports SSL encrypted connections. To access a
3193 folder with IMAP/SSL, you should use imaps://[user-
3194 name@]imapserver[:port]/path/to/folder as your folder path.
3196 Pine-compatible notation is also supported, i.e. {[user-
3197 name@]imapserver[:port][/ssl]}path/to/folder
3199 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3200 correctly notice which separator is being used by the server and convert paths
3203 When browsing folders on an IMAP server, you can toggle whether to look at only
3204 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
3205 command. See also the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd (section 7.4.102 , page 112)
3208 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3209 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.104 , page 113) and
3210 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.327 , page 169) variables.
3212 Note that if you are using mbox as the mail store on UW servers prior to
3213 v12.250, the server has been reported to disconnect a client if another client
3214 selects the same folder.
3216 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3218 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3219 mostly the same as the local file browser, with the following differences:
3221 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3222 followed by the symbol "+", indicating that the entry contains both mes-
3223 sages and subfolders. On Cyrus-like servers folders will often contain
3224 both messages and subfolders.
3226 +
\bo For the case where an entry can contain both messages and subfolders, the
3227 selection key (bound to enter by default) will choose to descend into the
3228 subfolder view. If you wish to view the messages in that folder, you must
3229 use view-file instead (bound to space by default).
3231 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3232 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3233 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3234 mally these are bound to s and u, respectively).
3236 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3238 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3239 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3240 tion for you poor exchange users out there, but it has yet to be integrated
3241 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3242 which allows you to log in to a public IMAP server without having an account.
3243 To use ANONYMOUS, simply make your username blank or "anonymous".
3245 The Mutt Next Generation E-Mail Client 65
3247 SASL is a special super-authenticator, which selects among several protocols
3248 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3249 available on your host and the server. Using some of these methods (including
3250 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3251 invisible to those teeming network snoops. It is the best option if you have
3252 it. To use it, you must have the Cyrus SASL library installed on your system
3253 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3255 Mutt-ng will try whichever methods are compiled in and available on the server,
3256 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3258 There are a few variables which control authentication:
3260 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.110 , page 114) - controls the username under
3261 which you request authentication on the IMAP server, for all authentica-
3262 tors. This is overridden by an explicit username in the mailbox path (i.e.
3263 by using a mailbox name of the form {user@host}).
3265 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.105 , page 113) - a password which you may pre-
3266 set, used by all authentication methods where a password is needed.
3268 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.96 , page 111) - a colon-delimited list
3269 of IMAP authentication methods to try, in the order you wish to try them.
3270 If specified, this overrides mutt's default (attempt everything, in the
3271 order listed above).
3273 _
\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)
3275 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3276 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3277 function from the index/pager which is by default bound to i.
3279 The Default newsserver can be obtained from the $NNTPSERVER environment vari-
3280 able. Like other news readers, info about subscribed newsgroups is saved in a
3281 file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.162 , page 129) variable.
3282 Article headers are cached and can be loaded from a file when a newsgroup is
3283 entered instead loading from newsserver; currently, this caching mechanism
3284 still is different from the header caching for maildir/IMAP.
3286 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3288 Especially for Usenet, people often ask for advanced filtering and scoring
3289 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3290 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
3293 What has not been discusses in detail is mutt-ng's built-in realname filter.
3294 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3295 there are frequent request for such functionality. The solutions offered often
3296 are complicated regular expressions.
3298 In mutt-ng this is as easy as
3300 The Mutt Next Generation E-Mail Client 66
3304 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3305 fied a valid realname and a valid email address. Using
3309 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3310 ria which are very strict:
3312 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3313 editor.org/in-notes/rfc2822.txt>
3315 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3316 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3317 ``J. User'' and ``J. A. User'' aren't.
3319 +
\bo it's assumed that users are interested in reading their own mail and mail
3320 from people who they have defined an alias for so that those 2 groups of
3321 messages are excluded from the strict rules.
3323 _
\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)
3325 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3326 functionality. When configure was called with --with-libesmtp or the output
3327 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3328 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3329 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 62) section) as well as handling the 8BIT-
3330 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.334 , page 170).
3332 To enable sending mail directly via SMTP without an MTA such as Postfix or
3333 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.292 , page 158)
3334 variable pointing to your SMTP server.
3336 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.296 ,
3337 page 159) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.293 , page 159) variables.
3339 Transport Encryption via the StartTLS command is also available. For this to
3340 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3341 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.295 , page 159) variable must be either set to
3342 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3343 supports it: for the second case, the connection will fail if it doesn't while
3344 switching back to unencrypted communication for the first one.
3346 Some mail providers require user's to set a particular envelope sender, i.e.
3348 The Mutt Next Generation E-Mail Client 67
3350 they allow for only one value which may not be what the user wants to send as
3351 the From: header. In this case, the variable _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be (section 7.4.291 ,
3352 page 158) may be used to set the envelope different from the From: header.
3354 _
\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)
3356 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3357 find managing all the authentication settings inconvenient and error-prone.
3358 The account-hook command may help. This hook works like folder-hook but is
3359 invoked whenever you access a remote mailbox (including inside the folder
3360 browser), not just when you open the mailbox.
3364 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3365 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3366 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3368 _
\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)
3370 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
3371 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
3372 start a WWW browser on one of them. This functionality is provided by the
3373 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3374 trib/ and the configuration commands:
3376 macro index \cb |urlview\n
3377 macro pager \cb |urlview\n
3379 _
\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)
3381 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3382 _
\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
3383 an arbitrary format, provided that the user has a script to convert from/to
3384 this format to one of the accepted.
3386 The most common use is to open compressed archived folders e.g. with gzip.
3388 In addition, the user can provide a script that gets a folder in an accepted
3389 format and appends its context to the folder in the user-defined format, which
3390 may be faster than converting the entire folder to the accepted format, append-
3391 ing to it and converting back to the user-defined format.
3393 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3394 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69))
3395 which define commands to uncompress and compress a folder and to append mes-
3396 sages to an existing compressed folder respectively.
3398 The Mutt Next Generation E-Mail Client 68
3402 open-hook \\.gz$ "gzip -cd %f > %t"
3403 close-hook \\.gz$ "gzip -c %t > %f"
3404 append-hook \\.gz$ "gzip -c %t >> %f"
3406 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-
3407 tion 4.19.3 , page 69), the folder will be open and closed again each time you
3408 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) (or give
3409 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3410 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) though you'll be able to append to the folder.
3412 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3413 accepted formats. In particular, if the file is empty, mutt supposes it is not
3414 compressed. This is important because it allows the use of programs that do not
3415 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3416 prising if your compressing script produces empty files. In this situation,
3417 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.246 , page 148), so that the compressed file
3418 will be removed if you delete all of the messages.
3420 _
\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
3422 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3424 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3425 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3427 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3428 parameters: %f, which is replaced with the (compressed) folder name, and %t
3429 which is replaced with the name of the temporary folder to which to write.
3431 %f and %t can be repeated any number of times in the command string, and all of
3432 the entries are replaced with the appropriate folder name. In addition, %% is
3433 replaced by %, as in printf, and any other %anything is left as is.
3435 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
3436 return non-zero exit status if it fails, so mutt knows something's wrong.
3440 open-hook \\.gz$ "gzip -cd %f > %t"
3442 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3444 _
\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
3446 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3448 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3449 4.19.1 , page 68) command after some changes were made to it.
3451 The Mutt Next Generation E-Mail Client 69
3453 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3454 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
3455 4.19.1 , page 68) command. Temporary folder in this case is the folder previ-
3456 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68) command.
3458 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
3459 non-zero exit status if it fails, so mutt knows something's wrong.
3463 close-hook \\.gz$ "gzip -c %t > %f"
3465 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3466 file can only be open in the readonly mode.
3468 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) is not called when you exit from the
3469 folder if the folder was not changed.
3471 _
\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
3473 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3475 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3476 is the command that can be used for appending to the folders whose names match
3477 _
\br_
\be_
\bg_
\be_
\bx_
\bp. It has the same format as in the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68)
3478 command. The temporary folder in this case contains the messages that are
3481 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
3482 non-zero exit status if it fails, so mutt knows something's wrong.
3486 append-hook \\.gz$ "gzip -c %t >> %f"
3488 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) is used, the folder is not opened,
3489 which saves time, but this means that we can not find out what the folder type
3490 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.131 , page 121)) type is always
3491 supposed (i.e. this is the format used for the temporary folder).
3493 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 ,
3494 page 68) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3495 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) is only for appending to existing folders.
3497 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3498 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3499 4.19.1 , page 68) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68)respectively) each
3500 time you will add to it.
3502 The Mutt Next Generation E-Mail Client 70
3504 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3506 The compressed folders support can also be used to handle encrypted folders. If
3507 you want to encrypt a folder with PGP, you may want to use the following hooks:
3509 open-hook \\.pgp$ "pgp -f < %f > %t"
3510 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3512 Please note, that PGP does not support appending to an encrypted folder, so
3513 there is no append-hook defined.
3515 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3516 can be read by your system administrator. So think about the security aspects
3519 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3521 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3522 MUA. Every effort has been made to provide the functionality that the discern-
3523 ing MIME user requires, and the conformance to the standards wherever possible.
3524 When configuring Mutt-ng for MIME, there are two extra types of configuration
3525 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3526 ping of file extensions to IANA MIME types. The other is the mailcap file,
3527 which specifies the external commands to use for handling specific MIME types.
3529 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3531 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3532 (while viewing a message), the attachment menu and the compose menu.
3534 _
\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
3536 When you select a message from the index and view it in the pager, Mutt decodes
3537 the message to a text representation. Mutt-ng internally supports a number of
3538 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3539 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3540 variety of PGP MIME types, including PGP/MIME and application/pgp.
3542 Mutt-ng will denote attachments with a couple lines describing them. These
3543 lines are of the form:
3545 [-- Attachment #1: Description --]
3546 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3548 Where the Description is the description or filename given for the attachment,
3549 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3551 The Mutt Next Generation E-Mail Client 71
3553 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3555 [-- image/gif is unsupported (use 'v' to view this part) --]
3557 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3559 The default binding for view-attachments is `v', which displays the attachment
3560 menu for a message. The attachment menu displays a list of the attachments in
3561 a message. From the attachment menu, you can save, print, pipe, delete, and
3562 view attachments. You can apply these operations to a group of attachments at
3563 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3564 can also reply to the current message from this menu, and only the current
3565 attachment (or the attachments tagged) will be quoted in your reply. You can
3566 view attachments as text, or view them using the mailcap viewer definition.
3568 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3569 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3570 of type message/rfc822.
3572 See the help on the attachment menu for more information.
3574 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3576 The compose menu is the menu you see before you send a message. It allows you
3577 to edit the recipient list, the subject, and other aspects of your message. It
3578 also contains a list of the attachments of your message, including the main
3579 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3580 review, and rename an attachment or a list of tagged attachments. You can also
3581 modifying the attachment information, notably the type, encoding and descrip-
3584 Attachments appear as follows:
3586 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3587 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3589 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3590 or canceling) the message. It can be toggled with the toggle-unlink command
3591 (default: u). The next field is the MIME content-type, and can be changed with
3592 the edit-type command (default: ^T). The next field is the encoding for the
3593 attachment, which allows a binary message to be encoded for transmission on
3594 7bit links. It can be changed with the edit-encoding command (default: ^E).
3595 The next field is the size of the attachment, rounded to kilobytes or
3596 megabytes. The next field is the filename, which can be changed with the
3597 rename-file command (default: R). The final field is the description of the
3598 attachment, and can be changed with the edit-description command (default: d).
3600 _
\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
3602 When you add an attachment to your mail message, Mutt-ng searches your personal
3604 The Mutt Next Generation E-Mail Client 72
3606 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3607 /usr/local/share/mutt/mime.types or /etc/mime.types
3609 The mime.types file consist of lines containing a MIME type and a space sepa-
3610 rated list of extensions. For example:
3612 application/postscript ps eps
3614 audio/x-aiff aif aifc aiff
3616 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3617 tain most of the MIME types you are likely to use.
3619 If Mutt-ng can not determine the mime type by the extension of the file you
3620 attach, it will look at the file. If the file is free of binary information,
3621 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3622 the file contains binary information, then Mutt-ng will mark it as applica-
3623 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3624 attachment by using the edit-type command from the compose menu (default: ^T).
3625 The MIME type is actually a major mime type followed by the sub-type, separated
3626 by a '/'. 6 major types: application, text, image, video, audio, and model have
3627 been approved after various internet discussions. Mutt-ng recognises all of
3628 these if the appropriate entry is found in the mime.types file. It also recog-
3629 nises other major mime types, such as the chemical type that is widely used in
3630 the molecular modelling community to pass molecular data in various forms to
3631 various molecular viewers. Non-recognised mime types should only be used if the
3632 recipient of the message is likely to be expecting such attachments.
3634 _
\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
3636 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3637 format specified in Appendix A of RFC 1524. This file format is commonly
3638 referred to as the mailcap format. Many MIME compliant programs utilize the
3639 mailcap format, allowing you to specify handling for all MIME types in one
3640 place for all programs. Programs known to use this format include Netscape,
3641 XMosaic, lynx and metamail.
3643 In order to handle various MIME types that Mutt-ng can not handle internally,
3644 Mutt-ng parses a series of external configuration files to find an external
3645 handler. The default search string for these files is a colon delimited list
3648 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3650 where $HOME is your home directory.
3652 In particular, the metamail distribution will install a mailcap file, usually
3653 as /usr/local/etc/mailcap, which contains some baseline entries.
3655 The Mutt Next Generation E-Mail Client 73
3657 _
\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
3659 A mailcap file consists of a series of lines which are comments, blank, or def-
3662 A comment line consists of a # character followed by anything you want.
3664 A blank line is blank.
3666 A definition line consists of a content type, a view command, and any number of
3667 optional fields. Each field of a definition line is divided by a semicolon ';'
3670 The content type is specified in the MIME standard type/subtype method. For
3671 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3672 mat includes two formats for wildcards, one using the special '*' subtype, the
3673 other is the implicit wild, where you only include the major type. For exam-
3674 ple, image/*, or video, will match all image types and video types, respec-
3677 The view command is a Unix command for viewing the type specified. There are
3678 two different types of commands supported. The default is to send the body of
3679 the MIME message to the command on stdin. You can change this behavior by using
3680 %s as a parameter to your view command. This will cause Mutt-ng to save the
3681 body of the MIME message to a temporary file, and then call the view command
3682 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3683 will turn over the terminal to the view program until the program quits, at
3684 which time Mutt will remove the temporary file if it exists.
3686 So, in the simplest form, you can send a text/plain message to the external
3687 pager more on stdin:
3691 Or, you could send the message as a file:
3695 Perhaps you would like to use lynx to interactively view a text/html message:
3699 In this case, lynx does not support viewing a file from stdin, so you must use
3700 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
3701 _
\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
3702 _
\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
3703 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3705 On the other hand, maybe you don't want to use lynx interactively, you just
3706 want to have it convert the text/html to text/plain, then you can use:
3708 The Mutt Next Generation E-Mail Client 74
3710 text/html; lynx -dump %s | more
3712 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3713 text formats, then you would use the following:
3718 This is the simplest form of a mailcap file.
3720 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3722 The interpretation of shell meta-characters embedded in MIME parameters can
3723 lead to security problems in general. Mutt-ng tries to quote parameters in
3724 expansion of %s syntaxes properly, and avoids risky characters by substituting
3725 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.122 , page 119) variable.
3727 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3728 there are other applications parsing mailcap, maybe taking less care of it.
3729 Therefore you should pay attention to the following rules:
3731 _
\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
3732 double quotes. Mutt-ng does this for you, the right way, as should any other
3733 program which interprets mailcap. Don't put them into backtick expansions. Be
3734 highly careful with eval statements, and avoid them if possible at all. Trying
3735 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3736 tive to correct quoting in the first place.
3738 If you have to use the %-expandos' values in context where you need quoting or
3739 backtick expansions, put that value into a shell variable and reference the
3740 shell variable where necessary, as in the following example (using $charset
3741 inside the backtick expansion is safe, since it is not itself subject to any
3744 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3745 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3747 _
\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
3749 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3751 In addition to the required content-type and view command fields, you can add
3752 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3753 nizes the following optional fields:
3756 This flag tells Mutt-ng that the command passes possibly large
3757 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3758 (either the internal pager or the external pager defined by the
3759 pager variable) on the output of the view command. Without this
3761 The Mutt Next Generation E-Mail Client 75
3763 flag, Mutt-ng assumes that the command is interactive. One could
3764 use this to replace the pipe to more in the lynx -dump example in
3767 text/html; lynx -dump %s ; copiousoutput
3769 This will cause lynx to format the text/html output as text/plain
3770 and Mutt-ng will use your standard pager to display the results.
3773 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3774 tion 5.4 , page 78), in order to decide whether it should honor
3775 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.340 , page 172) variable
3776 or not. When an attachment is viewed using an interactive program,
3777 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3778 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.340 , page 172) and the exit
3779 status of the program to decide if it will ask you to press a key
3780 after the external program has exited. In all other situations it
3781 will not prompt you for a key.
3784 This flag specifies the command to use to create a new attachment
3785 of a specific MIME type. Mutt-ng supports this from the compose
3788 composetyped=<command>
3789 This flag specifies the command to use to create a new attachment
3790 of a specific MIME type. This command differs from the compose
3791 command in that mutt will expect standard MIME headers on the data.
3792 This can be used to specify parameters, filename, description, etc.
3793 for a new attachment. Mutt-ng supports this from the compose
3797 This flag specifies the command to use to print a specific MIME
3798 type. Mutt-ng supports this from the attachment and compose menus.
3801 This flag specifies the command to use to edit a specific MIME
3802 type. Mutt-ng supports this from the compose menu, and also uses
3803 it to compose new attachments. Mutt-ng will default to the defined
3804 editor for text attachments.
3806 nametemplate=<template>
3807 This field specifies the format for the file denoted by %s in the
3808 command fields. Certain programs will require a certain file
3809 extension, for instance, to correctly view a file. For instance,
3810 lynx will only interpret a file as text/html if the file ends in
3811 .html. So, you would specify lynx as a text/html viewer with a
3812 line in the mailcap file like:
3814 text/html; lynx %s; nametemplate=%s.html
3816 The Mutt Next Generation E-Mail Client 76
3819 This field specifies a command to run to test whether this mailcap
3820 entry should be used. The command is defined with the command
3821 expansion rules defined in the next section. If the command
3822 returns 0, then the test passed, and Mutt-ng uses this entry. If
3823 the command returns non-zero, then the test failed, and Mutt-ng
3824 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
3825 _
\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:
3827 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3830 In this example, Mutt-ng will run the program RunningX which will
3831 return 0 if the X Window manager is running, and non-zero if it
3832 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3833 display the text/html object. If RunningX doesn't return 0, then
3834 Mutt-ng will go on to the next entry and use lynx to display the
3837 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3839 When searching for an entry in the mailcap file, Mutt-ng will search for the
3840 most useful entry for its purpose. For instance, if you are attempting to
3841 print an image/gif, and you have the following entries in your mailcap file,
3842 Mutt-ng will search for an entry with the print command:
3845 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3848 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3851 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) to denote
3852 two commands for viewing an attachment, one to be viewed automatically, the
3853 other to be viewed interactively from the attachment menu. In addition, you
3854 can then use the test feature to determine which viewer to use interactively
3855 depending on your environment.
3857 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3858 text/html; lynx %s; nametemplate=%s.html
3859 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3861 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 78), Mutt-ng will choose the third entry
3862 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3863 program RunningX to determine if it should use the first entry. If the program
3864 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3866 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3868 The various commands defined in the mailcap files are passed to the /bin/sh
3870 The Mutt Next Generation E-Mail Client 77
3872 shell using the system() function. Before the command is passed to /bin/sh -c,
3873 it is parsed to expand various special parameters with information from Mutt-
3874 ng. The keywords Mutt-ng expands are:
3877 As seen in the basic mailcap section, this variable is expanded to
3878 a filename specified by the calling program. This file contains
3879 the body of the message to view/print/edit or where the composing
3880 program should place the results of composition. In addition, the
3881 use of this keyword causes Mutt-ng to not pass the body of the mes-
3882 sage to the view/print/edit program on stdin.
3885 Mutt-ng will expand %t to the text representation of the content
3886 type of the message in the same form as the first parameter of the
3887 mailcap definition line, ie text/html or image/gif.
3890 Mutt-ng will expand this to the value of the specified parameter
3891 from the Content-Type: line of the mail message. For instance, if
3892 Your mail message contains:
3894 Content-Type: text/plain; charset=iso-8859-1
3896 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3897 metamail mailcap file uses this feature to test the charset to
3898 spawn an xterm using the right charset to view the message.
3901 This will be replaced by a %
3903 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3904 1524. The main purpose of these parameters is for multipart messages, which is
3905 handled internally by Mutt-ng.
3907 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3909 This mailcap file is fairly simple and standard:
3911 # I'm always running X :)
3912 video/*; xanim %s > /dev/null
3913 image/*; xv %s > /dev/null
3915 # I'm always running netscape (if my computer had more memory, maybe)
3916 text/html; netscape -remote 'openURL(%s)'
3918 This mailcap file shows quite a number of examples:
3920 The Mutt Next Generation E-Mail Client 78
3922 # Use xanim to view all videos Xanim produces a header on startup,
3923 # send that to /dev/null so I don't see it
3924 video/*; xanim %s > /dev/null
3926 # Send html to a running netscape by remote
3927 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3929 # If I'm not running netscape but I am running X, start netscape on the
3931 text/html; netscape %s; test=RunningX
3933 # Else use lynx to view it as text
3936 # This version would convert the text/html to text/plain
3937 text/html; lynx -dump %s; copiousoutput
3939 # I use enscript to print text in two columns to a page
3940 text/*; more %s; print=enscript -2Gr %s
3942 # Netscape adds a flag to tell itself to view jpegs internally
3943 image/jpeg;xv %s; x-mozilla-flags=internal
3945 # Use xv to view images if I'm running X
3946 # In addition, this uses the \ to extend the line and set my editor
3948 image/*;xv %s; test=RunningX; \
3951 # Convert images to text using the netpbm tools
3952 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3953 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3955 # Send excel spreadsheets to my NT box
3956 application/ms-excel; open.pl %s
3958 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3960 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3961 viewer defined in the mailcap file, Mutt-ng has support for automatically view-
3962 ing MIME attachments while in the pager.
3964 To work, you must define a viewer in the mailcap file which uses the copi-
3965 ousoutput option to denote that it is non-interactive. Usually, you also use
3966 the entry to convert the attachment to a text representation which you can view
3969 You then use the auto_view muttrc command to list the content-types that you
3970 wish to view automatically.
3972 For instance, if you set auto_view to:
3974 The Mutt Next Generation E-Mail Client 79
3976 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3978 Mutt-ng could use the following mailcap entries to automatically view attach-
3979 ments of these types.
3981 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3982 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3983 application/x-gunzip; gzcat; copiousoutput
3984 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3985 application/postscript; ps2ascii %s; copiousoutput
3987 ``unauto_view'' can be used to remove previous entries from the autoview list.
3988 This can be used with message-hook to autoview messages based on size, etc.
3989 ``unauto_view *'' will remove all previous entries.
3991 _
\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
3993 Mutt-ng has some heuristics for determining which attachment of a multi-
3994 part/alternative type to display. First, mutt will check the alternative_order
3995 list to determine if one of the available types is preferred. The alterna-
3996 tive_order list consists of a number of MIME types in order, including support
3997 for implicit and explicit wildcards, for example:
3999 alternative_order text/enriched text/plain text application/postscript image/*
4001 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
4002 5.4 , page 78), and use that. Failing that, Mutt-ng will look for any text
4003 type. As a last attempt, mutt will look for any type it knows how to handle.
4005 To remove a MIME type from the alternative_order list, use the unalterna-
4008 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
4010 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
4011 treated according to their mailcap entry. This option is designed to deal with
4012 binary types such as application/octet-stream. When an attachment's mime-type
4013 is listed in mime_lookup, then the extension of the filename will be compared
4014 to the list of extensions in the mime.types file. The mime-type associated
4015 with this extension will then be used to process the attachment according to
4016 the rules in the mailcap file and according to any other configuration options
4017 (such as auto_view) specified. Common usage would be:
4019 mime_lookup application/octet-stream application/X-Lotus-Manuscript
4021 In addition, the unmime_lookup command may be used to disable this feature for
4023 The Mutt Next Generation E-Mail Client 80
4025 any particular mime-type if it had been set, for example, in a global muttrc.
4027 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4029 First of all, mutt-ng contains no security holes included by intention but may
4030 contain unknown security holes. As a consequence, please run mutt-ng only with
4031 as few permissions as possible.
4033 Please do not run mutt-ng as the super user.
4035 When configuring mutt-ng, there're some points to note about secure setups.
4037 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
4038 mail user agents (in their default configuration) just by changing mutt-ng's
4039 configuration files: it then can execute arbitrary programs and scripts
4040 attached to messages, send out private data on its own, etc. Although this is
4041 not believed to the common type of setup, please read this chapter carefully.
4043 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
4045 Although mutt-ng can be told the various passwords for accounts, please never
4046 store passwords in configuration files. Besides the fact that the system's
4047 operator can always read them, you could forget to replace the actual password
4048 with asterisks when reporting a bug or asking for help via, for example, a
4049 mailing list so that your mail including your password could be archived by
4050 internet search engines, etc. Please never store passwords on disk.
4052 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
4054 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
4055 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.332 , page 170) variable can be used to
4056 change the default permissions of these files. Please only change it if you
4057 really know what you are doing. Also, a different location for these files may
4058 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.328 , page 169)
4061 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
4063 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4065 In the default configuration, mutt-ng will leak some information to the outside
4066 world when sending messages: the generation of Message-ID: headers includes a
4067 step counter which is increased (and rotated) with every message sent. If you'd
4068 like to hide this information probably telling others how many mail you sent in
4069 which time, you at least need to remove the %P expando from the default setting
4070 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.148 , page 124) variable. Please make sure
4071 that you really know how local parts of these Message-ID: headers are composed.
4073 The Mutt Next Generation E-Mail Client 81
4075 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
4077 As mutt-ng be can be set up to be the mail client to handle mailto: style links
4078 in websites, there're security considerations, too. To keep the old behavior by
4079 default, mutt-ng will be strict in interpreting them which means that arbitrary
4080 header fields can be embedded in these links which could override existing
4081 header fields or attach arbitrary files. This may be problematic if the
4082 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
4083 doesn't want to see header fields while editing the message.
4085 For example, following a link like
4087 mailto:joe@host?Attach=~/.gnupg/secring.gpg
4089 will send out the user's private gnupg keyring to joe@host if the user doesn't
4090 follow the information on screen carefully enough.
4092 When _
\bu_
\bn_
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg the _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo (section 7.4.316 , page 166) variable, mutt-
4095 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
4096 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
4098 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102) variable by force
4099 to let the user see all the headers (because they still may leak informa-
4102 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4104 Mutt-ng in many places has to rely on external applications or for convenience
4105 supports mechanisms involving external applications.
4107 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
4109 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
4110 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-
4111 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.121 , page 119) variable for
4114 These utilities may have a variety of security vulnerabilities, including over-
4115 writing of arbitrary files, information leaks or other exploitable bugs. These
4116 vulnerabilities may go unnoticed by the user, especially when they are called
4117 automatically (and without interactive prompting) from the mailcap file(s).
4118 When using mutt-ng's autoview mechanism in combination with mailcap files,
4119 please be sure to...
4121 +
\bo manually select trustworth applications with a reasonable calling sequence
4123 +
\bo periodically check the contents of mailcap files, especially after soft-
4124 ware installations or upgrades
4126 The Mutt Next Generation E-Mail Client 82
4128 +
\bo keep the software packages referenced in the mailcap file up to date
4130 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.122 , page 119) variable in its
4131 default state to restrict mailcap expandos to a safe set of characters
4133 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
4135 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4138 The same security considerations apply for these as for tools involved via
4139 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4140 compressed folders support if the uncompressed mailbox is too large for the
4141 disk it is saved to.)
4143 As already noted, most of these problems are not built in but caused by wrong
4144 configuration, so please check your configuration.
4146 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4148 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4150 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4151 mailbox. However, it is possible to read other mailboxes and to send messages
4152 from the command line as well.
4155 -a attach a file to a message
4156 -b specify a blind carbon-copy (BCC) address
4157 -c specify a carbon-copy (Cc) address
4158 -e specify a config command to be run after initialization files are read
4159 -f specify a mailbox to load
4160 -F specify an alternate file to read initialization commands
4161 -h print help on command line options
4162 -H specify a draft file from which to read a header and body
4163 -i specify a file to include in a message composition
4164 -m specify a default mailbox type
4165 -n do not read the system Muttngrc
4166 -p recall a postponed message
4167 -Q query a configuration variable
4168 -R open mailbox in read-only mode
4169 -s specify a subject (enclose in quotes if it contains spaces)
4170 -t dump the value of all variables to stdout
4171 -T dump the value of all changed variables to stdout
4172 -v show version number and compile-time definitions
4173 -x simulate the mailx(1) compose mode
4174 -y show a menu containing the files specified by the mailboxes command
4175 -z exit immediately if there are no messages in the mailbox
4176 -Z open the first folder with new message,exit immediately if none
4178 To read messages in a mailbox
4180 The Mutt Next Generation E-Mail Client 83
4182 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4184 To compose a new message
4186 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-
4187 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4189 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4190 rect input from the file you wish to send. For example,
4192 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4194 This command will send a message to ``professor@bigschool.edu'' with a subject
4195 of ``data set for run #2''. In the body of the message will be the contents of
4196 the file ``~/run2.dat''.
4198 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4200 The Mutt Next Generation E-Mail Client 84
4203 ~b EXPR messages which contain EXPR in the message body
4204 ~B EXPR messages which contain EXPR in the whole message
4205 ~c USER messages carbon-copied to USER
4206 ~C EXPR message is either to: or cc: EXPR
4208 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4210 ~e EXPR message which contains EXPR in the ``Sender'' field
4212 ~f USER messages originating from USER
4213 ~g cryptographically signed messages
4214 ~G cryptographically encrypted messages
4215 ~H EXPR messages with a spam attribute matching EXPR
4216 ~h EXPR messages which contain EXPR in the message header
4217 ~k message contains PGP key material
4218 ~i ID message which match ID in the ``Message-ID'' field
4219 ~L EXPR message is either originated or received by EXPR
4220 ~l message is addressed to a known mailing list
4221 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4222 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4225 ~p message is addressed to you (consults alternates)
4226 ~P message is from you (consults alternates)
4227 ~Q messages which have been replied to
4229 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4230 ~S superseded messages
4231 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4233 ~t USER messages addressed to USER
4235 ~v message is part of a collapsed thread.
4236 ~V cryptographically verified messages
4237 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4238 (if compiled with NNTP support)
4239 ~x EXPR messages which contain EXPR in the `References' field
4240 ~y EXPR messages which contain EXPR in the `X-Label' field
4241 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4242 ~= duplicated messages (see $duplicate_threads)
4243 ~$ unreferenced messages (requires threaded view)
4244 ~* ``From'' contains realname and (syntactically) valid
4245 address (excluded are addresses matching against
4246 alternates or any alias)
4248 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
4249 48). Special attention has to be made when using regular expressions inside of
4250 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4251 level of backslash (\), which is normally used for quoting. If it is your
4252 intention to use a backslash in the regular expression, you will need to use
4253 two backslashes instead (\\).
4255 The Mutt Next Generation E-Mail Client 85
4257 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4259 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4261 The following are the commands understood by mutt.
4263 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 66) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4265 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 25) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4267 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.4 , page 25) [ * | _
\bk_
\be_
\by ... ]
4269 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4271 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.11 , page 33) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4273 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4275 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4277 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 69) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4279 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4281 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 78) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4283 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 26) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4285 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 28) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4287 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 68) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4289 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 30) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4291 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.9 , page 30) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4293 +
\bo _
\be_
\bx_
\be_
\bc (section 3.25 , page 41) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4295 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4297 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4299 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.7 , page 28) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4301 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 38) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4303 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.17 , page 38) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4305 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 28) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4307 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 32) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4309 The Mutt Next Generation E-Mail Client 86
4311 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.10 , page 32) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4313 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4315 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4317 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.8 , page 29) _
\bm_
\be_
\bn_
\bu _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
4319 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 36) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4321 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4323 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4325 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4327 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 79) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4329 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.9 , page 30) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4331 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.9 , page 30) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4333 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4335 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4337 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 68) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4339 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.23 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4341 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.24 , page 40) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4343 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4345 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 38) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4347 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4349 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.26 , page 41) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4351 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 39) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4353 +
\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
4355 +
\bo _
\bs_
\be_
\bt (section 3.28 , page 44) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4357 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4359 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 45) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4361 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.27 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4363 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.27 , page 42) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4365 The Mutt Next Generation E-Mail Client 87
4367 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4369 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.13 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4371 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.28 , page 44) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4373 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.30 , page 45) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4375 _
\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
4377 The following list contains all variables which, in the process of providing
4378 more consistency, have been renamed and are partially even removed already. The
4379 left column contains the old synonym variables, the right column the full/new
4382 The Mutt Next Generation E-Mail Client 88
4384 edit_hdrs edit_headers
4385 forw_decode forward_decode
4386 forw_format forward_format
4387 forw_quote forward_quote
4388 hdr_format index_format
4389 indent_str indent_string
4390 mime_fwd mime_forward
4391 msg_format message_format
4392 pgp_autosign crypt_autosign
4393 pgp_autoencrypt crypt_autoencrypt
4394 pgp_replyencrypt crypt_replyencrypt
4395 pgp_replysign crypt_replysign
4396 pgp_replysignencrypted crypt_replysignencrypted
4397 pgp_verify_sig crypt_verify_sig
4398 pgp_create_traditional pgp_autoinline
4399 pgp_auto_traditional pgp_replyinline
4400 forw_decrypt forward_decrypt
4401 smime_sign_as smime_default_key
4402 post_indent_str post_indent_string
4403 print_cmd print_command
4404 shorten_hierarchy sidebar_shorten_hierarchy
4405 ask_followup_to nntp_ask_followup_to
4406 ask_x_comment_to nntp_ask_x_comment_to
4407 catchup_newsgroup nntp_catchup
4408 followup_to_poster nntp_followup_to_poster
4409 group_index_format nntp_group_index_format
4411 mime_subject nntp_mime_subject
4412 news_cache_dir nntp_cache_dir
4413 news_server nntp_host
4415 nntp_poll nntp_mail_check
4416 pop_checkinterval pop_mail_check
4417 post_moderated nntp_post_moderated
4418 save_unsubscribed nntp_save_unsubscribed
4419 show_new_news nntp_show_new_news
4420 show_only_unread nntp_show_only_unread
4421 x_comment_to nntp_x_comment_to
4422 smtp_auth_username smtp_user
4423 smtp_auth_password smtp_pass
4425 The contrib subdirectory contains a script named update-config.pl which eases
4428 A complete list of current variables follows.
4430 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
4436 This variable specifies whether to abort sending if no attachment was made but
4438 The Mutt Next Generation E-Mail Client 89
4440 the content references them, i.e. the content matches the regular expression
4441 given in _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 92). If a match was
4442 found and this variable is set to _
\by_
\be_
\bs, message sending will be aborted but the
4443 mail will be send nevertheless if set to _
\bn_
\bo.
4445 This variable and _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 92) are
4446 intended to remind the user to attach files if the message's text references
4449 See also the _
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\br_
\be_
\bm_
\bi_
\bn_
\bd_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.15 , page 92) variable.
4451 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4457 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4458 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4459 subject given at the subject prompt will never be aborted.
4461 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4467 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4468 body if no changes are made to the file (this check only happens after the
4469 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4471 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bg_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4477 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
4478 cating which version of Mutt-ng was used for composing them.
4480 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4484 Default: '~/.muttngrc'
4486 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4487 tion 2.5.4 , page 11)'' function.
4489 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4490 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.29 , page 45)'' command for it to be executed.
4492 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4494 The Mutt Next Generation E-Mail Client 90
4498 Default: '%4n %2f %t %-10a %r'
4500 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4501 ing printf(3)-style sequences are available:
4507 flags - currently, a 'd' for an alias marked for deletion
4513 address which alias expands to
4516 character which indicates if the alias is tagged for inclusion
4518 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4524 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4525 or base64 encoding when sending mail.
4527 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4533 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4534 sages) are to be interpreted. Messages containing these codes are rare, but if
4535 this option is set, their text will be colored accordingly. Note that this may
4536 override your color choices, and even present a security problem, since a mes-
4537 sage could include a line like ``[-- PGP output follows ...' and give it the
4538 same color as your attachment color.
4540 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4546 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4547 instead of highlighting the whole line. On slow network or modem links this
4548 will make response faster because there is less that has to be redrawn on the
4549 screen when moving to the next or previous entries in the menu.
4551 The Mutt Next Generation E-Mail Client 91
4553 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4559 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4560 attachment trees, instead of the default ACS characters.
4562 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4568 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4569 editing an outgoing message.
4571 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bs_
\bk_
\bc_
\bc
4577 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4578 the body of an outgoing message.
4580 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4586 This variable is a colon-separated list of character encoding schemes for mes-
4587 sages without character encoding indication. Header field values and message
4588 body content without character encoding indication would be assumed that they
4589 are written in one of this list. By default, all the header fields and message
4590 body without any charset indication are assumed to be in us-ascii.
4592 For example, Japanese users might prefer this:
4594 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4596 However, only the first content is valid for the message body. This variable
4597 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.317 , page 167) is unset.
4599 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4603 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4605 This variable describes the format of the ``attachment'' menu. The following
4606 printf(3)-style sequences are understood:
4608 The Mutt Next Generation E-Mail Client 92
4614 requires charset conversion (n or c)
4623 MIME Content-Transfer-Encoding: header field
4629 MIME Content-Disposition: header field (I=inline, A=attachment)
4647 graphic tree characters
4650 unlink (=to delete) flag
4653 right justify the rest of the string and pad with character 'X'
4656 pad to the end of the line with character 'X'
4658 _
\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
4660 Type: regular expression
4664 The Mutt Next Generation E-Mail Client 93
4666 If this variable is non-empty, muttng will scan a message's contents before
4667 sending for this regular expression. If it is found, it will ask for what to do
4668 depending on the setting of _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 88).
4670 This variable and _
\b$_
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh (section 7.4.1 , page 88) are intended to
4671 remind the user to attach files if the message's text references them.
4673 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4679 The separator to add between attachments when operating (saving, printing, pip-
4680 ing, etc) on a list of tagged attachments.
4682 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4688 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4689 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4690 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.16 ,
4691 page 93)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4692 operate on the attachments one by one.
4694 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4698 Default: 'On %d, %n wrote:'
4700 This is the string that will precede a message which has been included in a
4701 reply. For a full listing of defined printf(3)-like sequences see the section
4702 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''.
4704 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4710 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4711 all tagged messages (if there are any). When unset, you must first use the
4712 ``tag-prefix'' function (default: ';') to make the next function apply to all
4715 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4721 The Mutt Next Generation E-Mail Client 94
4723 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'', Mutt-ng
4724 will skip the initial send-menu and allow you to immediately begin editing the
4725 body of your message. The send-menu may still be accessed once you have fin-
4726 ished editing the body of your message.
4728 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.65 , page 103)''.
4730 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\be_
\be_
\bp
4736 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4738 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4744 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4745 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4746 tion 7.4.21 , page 94)'' variable.
4748 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4754 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4755 you don't get asked if you want to bounce a message. Setting this variable to
4756 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4759 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4765 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4766 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4768 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4774 When this variable is set, mutt will place the cursor at the beginning of the
4775 current line in menus, even when the arrow_cursor variable is unset, making it
4776 easier for blind persons using Braille displays to follow these menus. The
4778 The Mutt Next Generation E-Mail Client 95
4780 option is disabled by default because many visual terminals don't permit making
4781 the cursor invisible.
4783 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4787 Default: '~/.mutt_certificates'
4789 Availability: SSL or GNUTLS
4791 This variable specifies the file where the certificates you trust are saved.
4792 When an unknown certificate is encountered, you are asked if you accept it or
4793 not. If you accept it, the certificate can also be saved in this file and fur-
4794 ther connections are automatically accepted.
4796 You can also manually add CA certificates in this file. Any server certificate
4797 that is signed with one of these CA certificates are also automatically
4800 Example: set certificate_file=~/.muttng/certificates
4802 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4808 Character set your terminal uses to display and enter textual data.
4810 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4816 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4818 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4819 Especially with MH mailboxes, this operation can take quite some time since it
4820 involves scanning the directory and checking each file to see if it has already
4821 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4824 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4830 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4833 The Mutt Next Generation E-Mail Client 96
4835 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4839 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4841 Controls the format of the status line displayed in the ``compose'' menu. This
4842 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164)'', but has
4843 its own set of printf(3)-like sequences:
4846 total number of attachments
4852 approximate size (in bytes) of the current message
4855 Mutt-ng version string
4857 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164)''
4858 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 ,
4861 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4867 When defined, Mutt-ng will recode commands in rc files from this encoding.
4869 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4875 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4878 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4884 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4885 box which does not yet exist before creating it.
4887 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4889 The Mutt Next Generation E-Mail Client 97
4895 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4896 many seconds if the connection is not able to be established. A negative value
4897 causes Mutt-ng to wait indefinitely for the connection to succeed.
4899 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4903 Default: 'text/plain'
4905 Sets the default Content-Type: header field for the body of newly composed mes-
4908 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\bo_
\bp_
\by
4914 This variable controls whether or not copies of your outgoing messages will be
4915 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page
4916 146)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.247 , page 148)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4917 7.4.73 , page 106)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 38)''.
4919 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4925 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4926 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4927 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4928 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
4929 7.4.283 , page 157)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4930 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4933 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4939 This variable controls whether or not Mutt-ng may automatically enable PGP
4940 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
4941 7.4.37 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 98)'',
4942 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4943 7.4.42 , page 98)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.283 , page 157)''.
4945 The Mutt Next Generation E-Mail Client 98
4947 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4953 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4954 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4955 signing is not required or encryption is requested as well. If
4956 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.283 , page 157)'' is _
\bs_
\be_
\bt, then OpenSSL is
4957 used instead to create S/MIME messages and settings can be overridden by use of
4958 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4960 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4966 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4967 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
4968 7.4.37 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.41 , page 98)'',
4969 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 97)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4970 7.4.42 , page 98)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.283 , page 157)''.
4972 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4978 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
4979 encrypted. (Crypto only)
4981 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
4987 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
4989 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
4992 _
\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
4998 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
4999 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
5000 7.4.41 , page 98)'', because it allows you to sign all messages which are
5002 The Mutt Next Generation E-Mail Client 99
5004 automatically encrypted. This works around the problem noted in
5005 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.42 , page 98)'', that Mutt-ng is not able to
5006 find out whether an encrypted message is also signed. (Crypto only)
5008 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
5014 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
5015 S/MIME output, so spoofing such lines is more difficult. If you are using col-
5016 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
5019 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
5025 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
5026 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
5027 will be used instead of the classic code.
5029 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
5030 won't have any effect when used interactively.
5032 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
5038 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
5039 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
5040 cryptographic signatures. (Crypto only)
5042 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5046 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
5048 This variable controls the format of the date printed by the ``%d'' sequence in
5049 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''. This is passed to strftime(3)
5050 to process the date.
5052 Unless the first character in the string is a bang (``!''), the month and week
5053 day names are expanded according to the locale specified in the variable
5054 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.119 , page 118)''. If the first character in the string
5055 is a bang, the bang is discarded, and the month and week day names in the rest
5056 of the string are expanded in the _
\bC locale (that is in US English).
5058 The Mutt Next Generation E-Mail Client 100
5060 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\be_
\bb_
\bu_
\bg_
\b__
\bl_
\be_
\bv_
\be_
\bl
5068 This variable specifies the current debug level and may be used to increase or
5069 decrease the verbosity level during runtime. It overrides the level given with
5070 the -d command line option.
5072 Currently, this number must be >= 0 and <= 5 and muttng must be started with -d
5073 to enable debugging at all; enabling at runtime is not possible.
5075 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
5079 Default: '~f %s !~P | (~P ~C %s)'
5081 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
5082 will be interpreted if they are specified with only a simple regexp, instead of
5083 a matching pattern. The hooks are expanded when they are declared, so a hook
5084 will be interpreted according to the value of this variable at the time the
5085 hook is declared. The default value matches if the message is either from a
5086 user matching the regular expression given, or if it is from you (if the from
5087 address matches ``alternates'') and is to or cc'ed to a user matching the given
5090 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\be_
\bl_
\be_
\bt_
\be
5096 Controls whether or not messages are really deleted when closing or synchroniz-
5097 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
5098 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
5099 be kept in the mailbox.
5101 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be
5107 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
5108 7.4.323 , page 168) variable, this variable specifies whether to also set the
5109 DelSp parameter to yes. If this is _
\bu_
\bn_
\bs_
\be_
\bt, no additional parameter will be send
5110 as a value of no already is the default behavior.
5112 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
5113 (section 7.4.323 , page 168) is _
\bs_
\be_
\bt) but not on incomming.
5115 The Mutt Next Generation E-Mail Client 101
5117 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
5123 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
5124 tion. This applies when you either explicitly delete a message, or when you
5125 save it to another folder.
5127 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
5133 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
5134 subparts of individual messages in a multipart/digest. To see these subparts,
5135 press 'v' on that menu.
5137 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
5143 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
5144 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 ,
5145 page 101), and the filtered message is read from the standard output.
5147 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
5151 Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
5153 Availability: Standalone and Dotlock
5155 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
5157 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
5163 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5164 or in connection with the SMTP support via libESMTP.
5166 This variable sets the request for when notification is returned. The string
5167 consists of a comma separated list (no spaces!) of one or more of the follow-
5168 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
5169 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
5170 notified of successful transmission.
5172 The Mutt Next Generation E-Mail Client 102
5174 Example: set dsn_notify='failure,delay'
5176 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
5182 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5183 or in connection with the SMTP support via libESMTP.
5185 This variable controls how much of your message is returned in DSN messages.
5186 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
5187 return the full message.
5189 Example: set dsn_return=hdrs
5191 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
5197 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
5198 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
5199 indicate that it thinks they are duplicates of each other with an equals sign
5200 in the thread diagram.
5202 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5208 This option allows you to edit the header of your outgoing messages along with
5209 the body of your message.
5211 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5217 This variable specifies which editor is used by Mutt-ng. It defaults to the
5218 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5219 if neither of those are set.
5221 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5227 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5229 The Mutt Next Generation E-Mail Client 103
5231 string ``From '' (note the trailing space) in the beginning of a line. Useful
5232 to avoid the tampering certain mail delivery and transport agents tend to do
5235 N
\bNo
\bot
\bte
\be:
\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
5236 <em/strongly/ advised to _
\bs_
\be_
\bt this option although discouraged by the standard.
5237 Alternatively, you must take care of space-stuffing <tt/From / lines (with a
5238 trailing space) yourself.
5240 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5248 The file which includes random data that is used to initialize SSL library
5251 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5257 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5258 ``From:'' header field. Note that this information is passed to the sendmail
5259 command using the ``-f' command line switch, so don't set this option if you
5260 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page 150) yourself, or
5261 if the sendmail on your machine doesn't support that command line switch.
5263 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5269 Escape character to use for functions in the builtin editor.
5271 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5277 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5278 ing to messages, and the initial prompt for subject is skipped when forwarding
5281 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
5282 93)'' variable is _
\bs_
\be_
\bt.
5284 The Mutt Next Generation E-Mail Client 104
5286 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5292 This variable controls whether or not attachments on outgoing messages are
5293 saved along with the main body of your message.
5295 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5301 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5302 when the actual message is encrypted and/or signed. (PGP only)
5304 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5310 This variable is a colon-separated list of character encoding schemes for text
5311 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.27 , page 95) value will
5312 be used instead. For example, the following configuration would work for
5313 Japanese text handling:
5315 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5317 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5320 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5326 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5327 beginning of a pathname will be expanded to the value of this variable. Note
5328 that if you change this variable from the default value you need to make sure
5329 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5330 ables since expansion takes place during the ``set'' command.
5332 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5336 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5338 This variable allows you to customize the file browser display to your personal
5339 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page
5341 The Mutt Next Generation E-Mail Client 105
5343 115)'', but has its own set of printf(3)-like sequences:
5349 date/time folder was last modified
5358 group name (or numeric gid, if missing)
5361 number of hard links
5364 N if folder has new mail, blank otherwise
5370 * if the file is tagged, blank otherwise
5373 owner name (or numeric uid, if missing)
5376 right justify the rest of the string and pad with character 'X'
5379 pad to the end of the line with character 'X'
5381 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5387 Controls whether or not the Mail-Followup-To: header field is generated when
5388 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5389 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5390 3.13 , page 35)'' commands or detected by common mailing list headers.
5392 This field has two purposes. First, preventing you from receiving duplicate
5393 copies of replies to messages which you send to mailing lists. Second, ensuring
5394 that you do get a reply separately for any messages sent to known lists to
5395 which you are not subscribed. The header will contain only the list's address
5396 for subscribed lists, and both the list address and your own email address for
5398 The Mutt Next Generation E-Mail Client 106
5400 unsubscribed lists. Without this header, a group reply to your message sent to
5401 a subscribed list will be sent to both the list and your address, resulting in
5402 two copies of the same email for you.
5404 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5410 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
5411 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
5412 already known to have new mail.
5414 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.327 , page 169)'',
5415 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.120 , page 118)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5416 7.4.104 , page 113)''.
5418 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5424 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.247 , page 148)'',
5425 except that Mutt-ng will store a copy of your outgoing message by the username
5426 of the address you are sending to even if that mailbox does not exist.
5428 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146)'' variable.
5430 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5436 Controls the decoding of complex MIME messages into text/plain when forwarding
5437 a message. The message header is also RFC2047 decoded. This variable is only
5438 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5439 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.143 , page 123)'' is used instead.
5441 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5447 Controls the handling of encrypted messages when forwarding a message. When
5448 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5449 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5450 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.143 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5452 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5454 The Mutt Next Generation E-Mail Client 107
5460 This quadoption controls whether or not the user is automatically placed in the
5461 editor when forwarding messages. For those who always want to forward with no
5462 modification, use a setting of _
\bn_
\bo.
5464 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5470 This variable controls the default subject when forwarding a message. It uses
5471 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page
5474 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5480 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5481 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5482 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.114 , page 115)''.
5484 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bf_
\br_
\bo_
\bm
5486 Type: e-mail address
5490 This variable contains a default from address. It can be overridden using
5491 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 , page
5492 147)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.336 , page
5495 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5496 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5497 takes this email address.
5499 Defaults to the contents of the environment variable $EMAIL.
5501 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5503 Type: regular expression
5507 A regular expression used by Mutt-ng to parse the GECOS field of a password
5508 entry when expanding the alias. By default the regular expression is set to
5509 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5511 The Mutt Next Generation E-Mail Client 108
5513 the GECOS field contains a string like 'lastname, firstname' then you should
5514 do: set gecos_mask='.*'.
5516 This can be useful if you see the following behavior: you address a e-mail to
5517 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5518 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5519 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5520 to ``Franklin, Steve''.
5522 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bh_
\bd_
\br_
\bs
5528 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 ,
5529 page 37)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5530 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5531 defined header fields are added to every new message.
5533 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5539 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5540 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.341 , page
5541 172)'' setting applies.
5543 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5549 Availability: Header Cache
5551 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.83 , page 108) variable points to the header
5554 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.83 , page 108) points to a directory it will
5555 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5556 7.4.83 , page 108) points to a file that file will be a single global header
5557 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5559 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5565 If enabled the header cache will be compressed. So only one fifth of the usual
5566 diskspace is used, but the uncompression can result in a slower open of the
5568 The Mutt Next Generation E-Mail Client 109
5572 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\be_
\bl_
\bp
5578 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5579 by each menu are displayed on the first line of the screen.
5581 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5582 sequence rather than a single keystroke. Also, the help line may not be
5583 updated if a binding is changed while Mutt-ng is running. Since this variable
5584 is primarily aimed at new users, neither of these should present a major prob-
5587 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5593 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5594 7.4.94 , page 110)'' variable when adding the domain part to addresses. This
5595 variable does not affect the generation of Message-ID: header fields, and it
5596 will not lead to the cut-off of first-level domains.
5598 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5604 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5605 limiting, in the thread tree.
5607 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5613 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5616 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5622 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5623 have the same subject as their parent or closest previously displayed sibling.
5625 The Mutt Next Generation E-Mail Client 110
5627 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5633 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5634 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5635 _
\bi_
\bn_
\bg (section 7.4.88 , page 109) is set, this option will have no effect.
5637 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5643 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5644 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.87 ,
5645 page 109) is _
\bs_
\be_
\bt, this option will have no effect.
5647 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5653 This variable controls the size (in number of strings remembered) of the string
5654 history buffer. The buffer is cleared each time the variable is changed.
5656 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5662 This variable controls whether or not a Mail-Followup-To: header field is hon-
5663 ored when group-replying to a message.
5665 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5671 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5672 during generation of Message-Id: headers.
5674 Please be sure to really know what you are doing when changing this variable to
5675 configure a custom domain part of Message-IDs.
5677 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5681 The Mutt Next Generation E-Mail Client 111
5685 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5686 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5687 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5688 header field was set by the mailing list to automate responses to the list, and
5689 will ignore this field. To direct a response to the mailing list when this
5690 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
5691 sender and the list.
5693 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5701 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5702 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5703 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5704 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5705 eter is case-insensitive.
5707 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5708 ods, in order from most-secure to least-secure.
5710 Example: set imap_authenticators='gssapi:cram-md5:login'
5712 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5713 ous methods are unavailable. If a method is available but authentication fails,
5714 Mutt-ng will not connect to the IMAP server.
5716 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5722 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5723 connection, and add them to the set of mailboxes it polls for new mail. See
5724 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.15 , page 36)'' command.
5726 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5734 This contains the list of characters which you would like to treat as folder
5735 separators for displaying IMAP paths. In particular it helps in using the '='
5736 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 , page 104) variable.
5738 The Mutt Next Generation E-Mail Client 112
5740 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5748 Mutt-ng requests these header fields in addition to the default headers (``DATE
5749 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5750 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5751 ``index'' menu. You may want to add more headers for spam detection.
5753 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5755 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5763 You normally want to see your personal folders alongside your INBOX in the IMAP
5764 browser. If you see something else, you may set this variable to the IMAP path
5767 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5775 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5776 wait before polling open IMAP connections, to prevent the server from closing
5777 them before Mutt-ng has finished with them.
5779 The default is well within the RFC-specified minimum amount of time (30 min-
5780 utes) before a server is allowed to do this, but in practice the RFC does get
5781 violated every now and then.
5783 Reduce this number if you find yourself getting disconnected from your IMAP
5784 server due to inactivity.
5786 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5794 The Mutt Next Generation E-Mail Client 113
5796 This variable configures whether IMAP folder browsing will look for only sub-
5797 scribed folders or all folders. This can be toggled in the IMAP browser with
5798 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5800 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5808 Your login name on the IMAP server.
5810 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.110 , page
5813 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5819 This variable configures how often (in seconds) Mutt-ng should look for new
5820 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.120 ,
5821 page 118)'' variable to generate less traffic and get more accurate information
5824 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5832 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5833 you for your password when you invoke the fetch-mail function.
5835 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5836 machine, because the superuser can read your configuration even if you are the
5837 only one who can read the file.
5839 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5847 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5848 Mutt-ng will only check for new mail over existing IMAP connections. This is
5849 useful if you don't want to be prompted to user/password pairs on Mutt-ng
5851 The Mutt Next Generation E-Mail Client 114
5853 invocation, or if opening the connection is slow.
5855 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5863 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5864 fetch a message from the server. This is generally a good thing, but can make
5865 closing an IMAP folder somewhat slower. This option exists to appease speed
5868 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5876 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5879 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5887 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5888 messages. Since these messages are often harmless, or generated due to configu-
5889 ration problems on the server which are out of the users' hands, you may wish
5890 to suppress them at some point.
5892 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5900 The name of the user whose mail you intend to access on the IMAP server.
5902 This variable defaults to your user name on the local machine.
5904 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5908 The Mutt Next Generation E-Mail Client 115
5912 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5913 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5914 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5915 convert the body part to text form.
5917 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5923 Controls whether or not a copy of the message(s) you are replying to is
5924 included in your reply.
5926 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5932 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5933 sage you are replying.
5935 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5941 Specifies the string to prepend to each line of text quoted in a message to
5942 which you are replying. You are strongly encouraged not to change this value,
5943 as it tends to agitate the more fanatical netizens.
5945 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5949 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5951 This variable allows you to customize the message index display to your per-
5954 ``Format strings'' are similar to the strings used in the ``C'' function
5955 printf(3) to format output (see the man page for more detail). The following
5956 sequences are defined in Mutt-ng:
5959 address of the author
5962 reply-to address (if present; otherwise: address of author)
5964 The Mutt Next Generation E-Mail Client 116
5967 filename of the original message folder (think mailBox)
5970 the list to which the letter was sent, or else the folder name
5974 number of characters (bytes) in the message
5977 current message number
5980 date and time of the message in the format specified by ``date_for-
5981 mat'' converted to sender's time zone
5984 date and time of the message in the format specified by ``date_for-
5985 mat'' converted to the local time zone
5988 current message number in thread
5991 number of messages in current thread
5994 entire From: line (address + real name)
5997 author name, or recipient name if the message is from you
6000 spam attribute(s) of this message
6003 newsgroup name (if compiled with nntp support)
6006 message-id of the current message
6009 number of lines in the message (does not work with maildir, mh, and
6010 possibly IMAP folders)
6013 If an address in the To or CC header field matches an address
6014 defined by the users ``subscribe'' command, this displays 'To
6015 <list-name>', otherwise the same as %F.
6018 total number of message in the mailbox
6020 The Mutt Next Generation E-Mail Client 117
6023 number of hidden messages if the thread is collapsed.
6029 author's real name (or address if missing)
6032 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
6033 the message: list name or recipient name if no list
6036 subject of the message
6039 status of the message (N/D/d/!/r/*)
6042 `to:' field (recipients)
6045 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.329 ,
6049 user (login) name of the author
6052 first name of the author, or the recipient if the message is from
6056 name of organization of author (`organization:' field)
6059 `x-label:' field, if present
6062 `x-label' field, if present, and (1) not at part of a thread tree,
6063 (2) at the top of a thread, or (3) `x-label' is different from pre-
6064 ceding message's `x-label'.
6067 message status flags
6070 the date and time of the message is converted to sender's time
6071 zone, and ``fmt'' is expanded by the library function ``strftime'';
6072 a leading bang disables locales
6075 the date and time of the message is converted to the local time
6077 The Mutt Next Generation E-Mail Client 118
6079 zone, and ``fmt'' is expanded by the library function ``strftime'';
6080 a leading bang disables locales
6083 the local date and time when the message was received. ``fmt'' is
6084 expanded by the library function ``strftime''; a leading bang dis-
6088 the current local time. ``fmt'' is expanded by the library function
6089 ``strftime''; a leading bang disables locales.
6092 right justify the rest of the string and pad with character 'X'
6095 pad to the end of the line with character 'X'
6097 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.329 , page 169)''.
6099 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
6105 How to invoke ispell (GNU's spell-checking software).
6107 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6113 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
6114 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.130 , page 121)'' mailbox, or as a result of
6115 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36)'' command.
6117 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
6123 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
6124 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
6125 will ask if you really intended to reply to the author only.
6127 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
6133 The Mutt Next Generation E-Mail Client 119
6135 The locale used by strftime(3) to format dates. Legal values are the strings
6136 your system accepts for the locale variable LC_TIME.
6138 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6144 This variable configures how often (in seconds) Mutt-ng should look for new
6147 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
6148 7.4.104 , page 113).
6150 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
6156 This variable specifies which files to consult when attempting to display MIME
6157 bodies not directly supported by Mutt-ng.
6159 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
6165 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
6166 well-defined set of safe characters. This is the safe setting, but we are not
6167 sure it doesn't break some more advanced MIME stuff.
6169 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!
6171 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by
6177 Availability: Header Cache
6179 Check for Maildir unaware programs other than Mutt-ng having modified maildir
6180 files when the header cache is in use. This incurs one stat(2) per message
6181 every time the folder is opened.
6183 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
6189 The Mutt Next Generation E-Mail Client 120
6191 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
6192 flag instead of physically deleted.
6194 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
6195 effect on other mailbox types.
6197 It is similiar to the trash option.
6199 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
6205 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
6206 mailbox without reading them.
6208 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
6209 up with an 'O' next to them in the ``index'' menu, indicating that they are
6212 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
6218 Controls the display of wrapped lines in the internal pager. If set, a ``+''
6219 marker is displayed at the beginning of wrapped lines. Also see the
6220 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.269 , page 154)'' variable.
6222 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\ba_
\bs_
\bk
6224 Type: regular expression
6228 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6229 operator ``!''. Only files whose names match this mask will be shown. The
6230 match is always case-sensitive.
6232 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6238 When set non-zero, this specifies the maximum number of recipient header lines
6239 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6240 case the number of lines exeeds its value, the last line will have 3 dots
6243 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6245 The Mutt Next Generation E-Mail Client 121
6251 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6252 is limited to this length. A value of 0 (which is also the default) means that
6253 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6254 (section 7.4.343 , page 172).
6256 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\bb_
\bo_
\bx
6262 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6263 7.4.303 , page 162)'' folder will be appended.
6265 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6271 The default mailbox type used when creating new folders. May be any of mbox,
6272 MMDF, MH and Maildir.
6274 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6280 This variable controls the number of lines of context that are given when
6281 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.173 , page
6284 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6290 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6291 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6292 entry may move off the bottom.
6294 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6300 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6302 The Mutt Next Generation E-Mail Client 122
6304 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6305 vious page of the menu is displayed (useful for slow links to avoid many
6308 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6314 This is the string displayed in the ``attachment'' menu for attachments of type
6315 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6316 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''.
6318 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6324 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6325 if the user had pressed the ESC key and whatever key remains after having the
6326 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6327 then this is treated as if the user had pressed ESC then ``x''. This is
6328 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6329 the ASCII character ``x''.
6331 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\be_
\bt_
\bo_
\bo
6337 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6338 from the list of recipients when replying to a message.
6340 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6346 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6347 _
\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-
6348 able is set, the message files will simply be deleted.
6350 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6356 The name of the MH sequence used for flagged messages.
6358 The Mutt Next Generation E-Mail Client 123
6360 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6366 The name of the MH sequence used to tag replied messages.
6368 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6374 The name of the MH sequence used for unseen messages.
6376 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6382 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6383 part instead of included in the main body of the message.
6385 This is useful for forwarding MIME messages so the receiver can properly view
6386 the message as it was delivered to you. If you like to switch between MIME and
6387 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6389 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.74 , page 106)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6390 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.143 , page 123)''.
6392 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6398 Controls the decoding of complex MIME messages into text/plain when forwarding
6399 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.142 , page 123)'' is _
\bs_
\be_
\bt. Other-
6400 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.74 , page 106)'' is used instead.
6402 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6408 When forwarding multiple attachments of a MIME message from the recvattach
6409 menu, attachments which cannot be decoded in a reasonable manner will be
6410 attached to the newly composed message if this option is set.
6412 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6414 The Mutt Next Generation E-Mail Client 124
6418 Default: '%4n %c %-16s %a'
6420 Availability: Mixmaster
6422 This variable describes the format of a remailer line on the mixmaster chain
6423 selection screen. The following printf(3)-like sequences are supported:
6426 The running number on the menu.
6429 Remailer capabilities.
6432 The remailer's short name.
6435 The remailer's e-mail address.
6437 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6441 Default: 'mixmaster'
6443 Availability: Mixmaster
6445 This variable contains the path to the Mixmaster binary on your system. It is
6446 used with various sets of parameters to gather the list of known remailers, and
6447 to finally send a message through the mixmaster chain.
6449 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bm_
\bo_
\bv_
\be
6455 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6456 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.130 , page 121)'' mailbox, or as a result of a
6457 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.14 , page 36)'' command.
6459 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6463 Default: '%Y%m%d%h%M%s.G%P%p'
6465 This is the format for the ``local part'' of the Message-Id: header field gen-
6466 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6467 generated. The '%' character marks that certain data will be added to the
6468 string, similar to printf(3). The following characters are allowed:
6470 The Mutt Next Generation E-Mail Client 125
6473 the current day of month
6485 the current UNIX timestamp (octal)
6491 the current Message-ID prefix (a character rotating with every Mes-
6492 sage-ID being generated)
6495 a random integer value (decimal)
6498 a random integer value (hexadecimal)
6504 the current UNIX timestamp (decimal)
6507 the current UNIX timestamp (hexadecimal)
6510 the current year (Y2K compliant)
6515 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6516 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6518 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6524 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6525 threads to fit on the screen.
6527 The Mutt Next Generation E-Mail Client 126
6529 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6537 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6538 ing the body of an outgoing news article.
6540 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6548 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6549 ing the body of an outgoing news article.
6551 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6555 Default: '~/.muttng'
6559 This variable points to directory where Mutt-ng will cache news article head-
6560 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6561 when you enter a newsgroup.
6563 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6564 cally increases speed and lowers traffic.
6566 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6574 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6575 when you leaving it.
6577 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6583 The Mutt Next Generation E-Mail Client 127
6587 This variable controls how many news articles to cache per newsgroup (if
6588 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.152 , page 126)) and how
6589 many news articles to show in the ``index'' menu.
6591 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.154 ,
6592 page 126), all older ones will be removed/not shown in the index.
6594 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6602 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6603 header field, a follow-up to the newsgroup is not permitted. The message will
6604 be mailed to the submitter of the message via mail.
6606 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6610 Default: '%4C %M%N %5s %-45.45f %d'
6614 This variable allows you to customize the newsgroup browser display to your
6615 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 ,
6616 page 115)'', but has its own set of printf(3)-like sequences:
6618 %C current newsgroup number
6619 %d description of newsgroup (retrieved from server)
6621 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6622 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6623 %n number of new articles in newsgroup
6624 %s number of unread articles in newsgroup
6625 %>X right justify the rest of the string and pad with character "X"
6626 %|X pad to the end of the line with character "X"
6628 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6636 This variable specifies the name (or address) of the NNTP server to be used.
6638 The Mutt Next Generation E-Mail Client 128
6640 It defaults to the value specified via the environment variable $NNTPSERVER or
6641 contained in the file /etc/nntpserver.
6643 You can also specify a username and an alternative port for each newsserver,
6646 [nntp[s]://][username[:password]@]newsserver[:port]
6648 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6649 security risk since the superuser of your machine may read it regardless of the
6652 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6660 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6661 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6662 lowing printf(3)-style sequence is understood:
6666 Example: set inews='/usr/local/bin/inews -hS'
6668 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6676 This variable controls whether or not descriptions for newsgroups are to be
6677 loaded when subscribing to a newsgroup.
6679 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6687 The time in seconds until any operations on a newsgroup except posting a new
6688 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6689 each operation in index (stepping, read article, etc.).
6691 The Mutt Next Generation E-Mail Client 129
6693 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6701 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6702 encoded according to RFC2047.
6704 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6706 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6710 Default: '~/.newsrc'
6714 This file contains information about subscribed newsgroup and articles read so
6717 To ease the use of multiple news servers, the following printf(3)-style
6718 sequence is understood:
6722 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6730 Your password for NNTP account.
6732 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6733 the superuser of your machine may read it regardless of the file's permissions.
6735 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6743 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6744 sions to post (e.g. moderated).
6746 The Mutt Next Generation E-Mail Client 130
6748 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6749 is totally read-only, that posting will not have any effect.
6751 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6759 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6760 was connection lost.
6762 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6770 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6771 file and into the news cache.
6773 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6781 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6782 browser. Otherwise, it will be done only once for a newsserver. Also controls
6783 whether or not the number of new articles of subscribed newsgroups will be
6786 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6794 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6795 played in the newsgroup browser.
6797 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6803 The Mutt Next Generation E-Mail Client 131
6807 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6808 tification, Mutt-ng will prompt you for your account name.
6810 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6818 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6819 name of the original article author) to articles that you followup to.
6821 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6827 This specifies the operating system name for the User-Agent: header field. If
6828 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6829 returns. If uname(2) fails, ``UNIX'' will be used.
6831 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6833 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bp_
\ba_
\bg_
\be_
\br
6839 This variable specifies which pager you would like to use to view messages.
6840 ``builtin'' means to use the builtin pager, otherwise this variable should
6841 specify the pathname of the external pager you would like to use.
6843 Using an external pager may have some disadvantages: Additional keystrokes are
6844 necessary because you can't call Mutt-ng functions directly from the pager, and
6845 screen resizes cause lines longer than the screen width to be badly formatted
6848 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6854 This variable controls the number of lines of context that are given when dis-
6855 playing the next or previous page in the internal pager. By default, Mutt-ng
6856 will display the line after the last one on the screen at the top of the next
6857 page (0 lines of context).
6859 The Mutt Next Generation E-Mail Client 132
6861 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6865 Default: '-%Z- %C/%m: %-20.20n %s'
6867 This variable controls the format of the one-line message ``status'' displayed
6868 before each message in either the internal or an external pager. The valid
6869 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)''
6872 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6878 Determines the number of lines of a mini-index which is shown when in the
6879 pager. The current message, unless near the top or bottom of the folder, will
6880 be roughly one third of the way down this mini-index, giving the reader the
6881 context of a few messages before and after the message. This is useful, for
6882 example, to determine how many messages remain to be read in the current
6883 thread. One of the lines is reserved for the status bar from the index, so a
6884 _
\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
6885 0 results in no index being shown. If the number of messages in the current
6886 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
6889 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6895 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6896 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
6898 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6904 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
6905 whenever the user performs an operation which ordinarily would result in the
6906 contents of the message being operated on. For example, if the user displays a
6907 pgp-traditional message which has not been manually checked with the check-tra-
6908 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
6911 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6915 The Mutt Next Generation E-Mail Client 133
6919 This option controls whether Mutt-ng generates old-style inline (traditional)
6920 PGP encrypted or signed messages under certain circumstances. This can be
6921 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
6923 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6924 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6925 ing PGP/MIME messages when inline (traditional) would not work. See also:
6926 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.194 , page 136)''.
6928 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.
6931 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
6937 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
6938 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
6940 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6946 This format is used to create a old-style ``clearsigned'' PGP message.
6948 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)
6950 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6956 This format strings specifies a command which is used to decode application/pgp
6959 The PGP command formats have their own set of printf(3)-like sequences:
6962 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
6963 string otherwise. Note: This may be used with a %? construct.
6966 Expands to the name of a file containing a message.
6969 Expands to the name of a file containing the signature part of a
6970 multipart/signed attachment when verifying it.
6972 The Mutt Next Generation E-Mail Client 134
6975 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.198 , page 137).
6978 One or more key IDs.
6980 For examples on how to configure these formats for the various versions of PGP
6981 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
6982 subdirectory which has been installed on your system alongside the documenta-
6985 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6991 This command is used to decrypt a PGP encrypted message. (PGP only)
6993 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6999 This command is used to encrypt a body part without signing it. (PGP only)
7001 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7007 This command is used to both sign and encrypt a body part. (PGP only)
7009 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7013 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
7015 This variable allows you to customize the PGP key selection menu to your per-
7016 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page
7017 115)'', but has its own set of printf(3)-like sequences:
7028 The Mutt Next Generation E-Mail Client 135
7043 trust/validity of the key-uid association
7046 date of the key where <s> is an strftime(3) expression
7050 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7056 This command is used to export a public key from the user's key ring. (PGP
7059 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7065 This command is invoked whenever Mutt-ng will need public key information. %r
7066 is the only printf(3)-like sequence used with this format. (PGP only)
7068 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
7070 Type: regular expression
7074 If you assign a text to this variable, then a PGP signature is only considered
7075 verified if the output from _
\b$_
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.204 , page 139)
7076 contains the text. Use this variable if the exit code from the command is 0
7077 even for bad signatures. (PGP only)
7079 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
7085 The Mutt Next Generation E-Mail Client 136
7087 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
7088 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
7089 want to play interesting key selection games. (PGP only)
7091 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7097 This command is used to import a key from a message into the user's public key
7100 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7106 This command is used to list the public key ring's contents. The output format
7107 must be analogous to the one used by gpg --list-keys --with-colons.
7109 This format is also generated by the pgpring utility which comes with Mutt-ng.
7112 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7118 This command is used to list the secret key ring's contents. The output format
7119 must be analogous to the one used by gpg --list-keys --with-colons.
7121 This format is also generated by the pgpring utility which comes with Mutt-ng.
7124 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
7130 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
7133 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
7139 This option controls whether Mutt-ng will prompt you for automatically sending
7140 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
7142 The Mutt Next Generation E-Mail Client 137
7146 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.
7149 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
7155 Setting this variable will cause Mutt-ng to always attempt to create an inline
7156 (traditional) message when replying to a message which is PGP encrypted/signed
7157 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
7158 required. This option does not automatically detect if the (replied-to) mes-
7159 sage is inline; instead it relies on Mutt-ng internals for previously
7160 checked/flagged messages.
7162 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7163 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7164 ing PGP/MIME messages when inline (traditional) would not work. See also:
7165 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.194 , page 136)''.
7167 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.
7170 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
7176 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
7177 and multipart/encrypted body parts.
7179 This is useful for applications like encrypted and signed mailing lists, where
7180 the outer layer (multipart/encrypted) can be easily removed, while the inner
7181 multipart/signed part is retained. (PGP only)
7183 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
7189 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
7190 This includes keys which have been revoked, have expired, or have been marked
7191 as ``disabled'' by the user. (PGP only)
7193 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
7199 The Mutt Next Generation E-Mail Client 138
7201 If you have more than one key pair, this option allows you to specify which of
7202 your private keys to use. It is recommended that you use the keyid form to
7203 specify your key (e.g., ``0x00112233''). (PGP only)
7205 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7211 This command is used to create the detached PGP signature for a multi-
7212 part/signed PGP/MIME body part. (PGP only)
7214 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
7220 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7224 sort alphabetically by user id
7227 sort alphabetically by key id
7230 sort by key creation date
7233 sort by the trust of the key
7235 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7238 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7244 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7245 printable. Please note that unsetting this variable may lead to problems with
7246 non-verifyable PGP signatures, so only change this if you know what you are
7249 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7255 The Mutt Next Generation E-Mail Client 139
7257 The number of seconds after which a cached passphrase will expire if not used.
7258 Default: 300. (PGP only)
7260 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7266 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7268 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7274 This command is used to verify PGP signatures. (PGP only)
7276 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7282 This command is used to verify key information from the key selection menu.
7285 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7291 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
7292 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7293 ers and will attempt to PGP/MIME decode the messages first.
7295 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7301 The separator to add between messages when piping a list of tagged messages to
7302 an external Unix command.
7304 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7310 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7312 The Mutt Next Generation E-Mail Client 140
7314 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7315 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7316 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7317 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7318 (section 7.4.207 , page 139)'' separator is added after each message.
7320 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7328 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7329 fall back to other authentication methods if the previous methods are unavail-
7330 able. If a method is available but authentication fails, Mutt-ng will not con-
7331 nect to the POP server.
7333 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7341 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7342 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7343 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7344 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7346 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7347 Mutt-ng will try all available methods, in order from most-secure to least-
7350 Example: set pop_authenticators='digest-md5:apop:user'
7352 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7360 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7361 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7362 load messages but also leave them on the POP server.
7364 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7368 The Mutt Next Generation E-Mail Client 141
7374 The name of your POP server for the ``fetch-mail'' function. You can also
7375 specify an alternative port, username and password, i.e.:
7377 [pop[s]://][username[:password]@]popserver[:port]
7379 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7380 the superuser of your machine may read it regardless of the file's permissions.
7382 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7390 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7391 retrieving only unread messages from the POP server when using the ``fetch-
7394 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7402 This variable configures how often (in seconds) POP should look for new mail.
7404 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7412 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7413 for your password when you open POP mailbox.
7415 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7416 the superuser of your machine may read it regardless of the file's permissions.
7418 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7424 The Mutt Next Generation E-Mail Client 142
7428 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7431 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7439 Your login name on the POP server.
7441 This variable defaults to your user name on the local machine.
7443 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7449 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.18 , page 93)'' variable, Mutt-ng
7450 will append this string after the inclusion of a message which is being replied
7453 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7459 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7460 7.4.220 , page 142)'' mailbox when you elect not to send immediately.
7462 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7466 Default: '~/postponed'
7468 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.219 , page 142)
7469 sending a message'' which you are editing. When you choose to postpone a mes-
7470 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7471 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.219 , page 142)'' variable.
7473 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7479 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a
7481 The Mutt Next Generation E-Mail Client 143
7483 connection to the server. This is useful for setting up secure connections,
7484 e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up
7485 opening the server. Example:
7487 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7488 /dev/null > /dev/null'
7490 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7492 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7493 machine without having to enter a password.
7495 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bp_
\br_
\bi_
\bn_
\bt
7501 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7502 by default, because some people accidentally hit ``p'' often.
7504 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7510 This specifies the command pipe that should be used to print messages.
7512 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7518 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7519 message is decoded before it is passed to the external command specified by
7520 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 143). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7521 cessing will be applied to the message when printing it. The latter setting
7522 may be useful if you are using some advanced printer filter which is able to
7523 properly format e-mail messages for printing.
7525 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7531 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7532 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 143) is executed
7533 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7534 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 143) is executed
7535 only once, and all the messages are concatenated, with a form feed as the mes-
7538 The Mutt Next Generation E-Mail Client 144
7540 Those who use the enscript(1) program's mail-printing mode will most likely
7541 want to set this option.
7543 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7549 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.172 , page 131)'', setting this
7550 variable will cause Mutt-ng to prompt you for a command when the pager exits
7551 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7552 index menu when the external pager exits.
7554 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7560 This specifies the command that Mutt-ng will use to make external address
7561 queries. The string should contain a %s, which will be substituted with the
7562 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 58)'' for more
7565 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\bq_
\bu_
\bi_
\bt
7571 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7572 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7573 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
7576 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7582 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7583 tion 7.4.114 , page 115)''.
7585 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7591 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7592 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7593 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.114 , page 115)''.
7595 The Mutt Next Generation E-Mail Client 145
7597 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7599 Type: regular expression
7601 Default: '^([ \t]*[|>:}#])+'
7603 A regular expression used in the internal-pager to determine quoted sections of
7604 text in the body of a message.
7606 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
7607 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7608 the beginning of quoted lines.
7610 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7616 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7617 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7618 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7619 reads message 25, and then again when it gets to message 50). This variable is
7620 meant to indicate progress when reading large mailboxes which may take some
7621 time. When set to 0, only a single message will appear before the reading the
7624 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.345 , page 173)'' variable.
7626 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7632 If set, all folders are opened in read-only mode.
7634 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7640 This variable specifies what ``real'' or ``personal'' name should be used when
7643 By default, this is the GECOS field from /etc/passwd.
7645 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7646 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.79 , page 107) variable.
7648 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7652 The Mutt Next Generation E-Mail Client 146
7656 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7657 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.220 , page 142)''.
7659 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7661 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7667 This specifies the file into which your outgoing messages should be appended.
7668 (This is meant as the primary method for saving a copy of your messages, but
7669 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37)'' com-
7670 mand to create a Bcc: header field with your email address in it.)
7672 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b6_
\b) is overridden by the
7673 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.73 , page 106)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7674 7.4.247 , page 148)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page
7677 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7679 Type: regular expression
7681 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7683 A regular expression used to recognize reply messages when threading and reply-
7684 ing. The default value corresponds to the English ``Re:'' and the German
7687 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7693 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7694 that you want to reply to the recipients of that message rather than to your-
7697 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7703 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7704 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7705 use the address in the ``From:'' header field instead.
7707 This option is useful for reading a mailing list that sets the ``Reply-To:''
7709 The Mutt Next Generation E-Mail Client 147
7711 header field to the list address and you want to send a private message to the
7712 author of a message.
7714 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7720 When set, the cursor will be automatically advanced to the next (possibly
7721 undeleted) message whenever a command that modifies the current message is exe-
7724 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7730 This variable controls whether or not Mutt-ng will display the ``personal''
7731 name from your aliases in the index menu if it finds an alias that matches the
7732 message's sender. For example, if you have the following alias:
7734 alias juser abd30425@somewhere.net (Joe User)
7736 and then you receive mail which contains the following header:
7738 From: abd30425@somewhere.net
7740 It would be displayed in the index menu as ``Joe User'' instead of
7741 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7742 not human friendly (like CompuServe addresses).
7744 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7750 It may sometimes arrive that you receive mail to a certain machine, move the
7751 messages to another machine, and reply to some the messages from there. If
7752 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7753 using the address where you received the messages you are replying to i
\bif
\bf that
7754 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7755 would be used doesn't match your alternates, the From: line will use your
7756 address on the current machine.
7758 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7764 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.242 ,
7766 The Mutt Next Generation E-Mail Client 148
7768 page 147) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7769 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7770 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7771 (section 7.4.234 , page 145) variable.
7773 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7779 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7780 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7781 ments to files named like this:
7783 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7785 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7786 effect before you have changed folders.
7788 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7789 standard, but nevertheless encountered in the wild.
7791 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7792 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7793 encoding specified in RFC 2231.
7795 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7801 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7802 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.247 , page 148)'' or
7803 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.73 , page 106)'' is _
\bs_
\be_
\bt too, the selection of the
7804 fcc folder will be changed as well.
7806 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7812 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7813 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.303 , page 162)'' which is
7814 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7816 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7817 and Maildir directories.
7819 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7823 The Mutt Next Generation E-Mail Client 149
7827 This variable controls how copies of outgoing messages are saved. When set, a
7828 check is made to see if a mailbox specified by the recipient address exists
7829 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.69 ,
7830 page 104)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7831 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7832 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.236 , page 146)'' mailbox.
7834 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.73 , page 106)'' variable.
7836 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\bs_
\bc_
\bo_
\br_
\be
7842 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7843 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
7844 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.249 , page 149)'' variable and friends are used.
7846 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7852 Messages which have been assigned a score equal to or lower than the value of
7853 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7854 scores are always greater than or equal to zero, the default setting of this
7855 variable will never mark a message for deletion.
7857 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7863 Messages which have been assigned a score greater than or equal to this vari-
7864 able's value are automatically marked ``flagged''.
7866 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7872 Messages which have been assigned a score equal to or lower than the value of
7873 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7874 scores are always greater than or equal to zero, the default setting of this
7875 variable will never mark a message read.
7877 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7879 The Mutt Next Generation E-Mail Client 150
7883 Default: 'us-ascii:iso-8859-1:utf-8'
7885 A list of character sets for outgoing messages. Mutt-ng will use the first
7886 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7887 (section 7.4.27 , page 95)'' is not iso-8859-1 and recipients may not under-
7888 stand UTF-8, it is advisable to include in the list an appropriate widely used
7889 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7890 instead of or after iso-8859-1.
7892 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7896 Default: '/usr/sbin/sendmail -oem -oi'
7898 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7899 Mutt-ng expects that the specified program interprets additional arguments as
7900 recipient addresses.
7902 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
7908 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 ,
7909 page 150)'' process to finish before giving up and putting delivery in the
7912 Mutt-ng interprets the value of this variable as follows:
7915 number of seconds to wait for sendmail to finish before continuing
7918 wait forever for sendmail to finish
7921 always put sendmail in the background without waiting
7923 Note that if you specify a value other than 0, the output of the child process
7924 will be put in a temporary file. If there is some error, you will be informed
7925 as to where to find the output.
7927 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\bh_
\be_
\bl_
\bl
7933 Command to use when spawning a subshell. By default, the user's login shell
7934 from /etc/passwd is used.
7936 The Mutt Next Generation E-Mail Client 151
7938 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
7944 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
7945 7.4.260 , page 152) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
7946 split a folder name into ``hierarchy items.''
7948 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
7954 This specifies the delimiter between the sidebar (if visible) and other
7957 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
7963 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
7965 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7969 Default: '%m%?n?(%n)?%?f?[%f]?'
7971 This variable controls how message counts are printed when the sidebar is
7972 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
7973 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
7974 mbox-style mailboxes.)
7976 The following printf(3)-like sequences are supported all of which may be
7980 Number of deleted messages. 1)
7983 Number of flagged messages.
7986 Total number of messages.
7989 Total number of messages shown, i.e. not hidden by a limit. 1)
7991 The Mutt Next Generation E-Mail Client 152
7994 Number of new messages.
7997 Number of tagged messages. 1)
7999 1) These expandos only have a non-zero value for the current mailbox and will
8000 always be zero otherwise.
8002 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bs_
\bh_
\bo_
\br_
\bt_
\be_
\bn_
\b__
\bh_
\bi_
\be_
\br_
\ba_
\br_
\bc_
\bh_
\by
8008 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
8009 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
8010 7.4.262 , page 152)'' is set to a too low value). For example, if the news-
8011 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
8012 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
8015 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
8016 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.256 , page 150) variable.
8018 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
8024 This specifies whether or not to show the sidebar (a list of folders specified
8025 with the ``mailboxes'' command).
8027 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
8033 The width of the sidebar.
8035 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
8041 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
8042 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.265 , page 153)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
8043 that you not unset this variable unless your ``signature'' contains just your
8044 name. The reason for this is because many software packages use ``-- \n'' to
8045 detect your signature.
8047 The Mutt Next Generation E-Mail Client 153
8049 For example, Mutt-ng has the ability to highlight the signature in a different
8050 color in the builtin pager.
8052 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8058 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
8059 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
8060 know what you are doing, and are prepared to take some heat from netiquette
8063 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
8067 Default: '~/.signature'
8069 Specifies the filename of your signature, which is appended to all outgoing
8070 messages. If the filename ends with a pipe (``|''), it is assumed that file-
8071 name is a shell command and input should be read from its stdout.
8073 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
8079 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
8080 people that want to sign off every message they send with their name.
8082 If you want to insert your website's URL, additional contact information or
8083 witty quotes into your mails, better use a signature file instead of the sig-
8086 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8090 Default: '~f %s | ~s %s'
8092 Specifies how Mutt-ng should expand a simple search into a real search pattern.
8093 A simple search is one that does not contain any of the ~ operators. See
8094 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 83)'' for more information on search patterns.
8096 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
8097 will automatically expand it to the value specified by this variable. For the
8098 default value it would be:
8102 The Mutt Next Generation E-Mail Client 154
8104 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
8110 Specifies time, in seconds, to pause while displaying certain informational
8111 messages, while moving from folder to folder and after expunging messages from
8112 the current folder. The default is to pause one second, so a value of zero for
8113 this option suppresses the pause.
8115 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
8121 Controls the display of lines longer than the screen width in the internal
8122 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
8123 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.126 ,
8124 page 120)'' variable.
8126 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
8128 Type: regular expression
8130 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
8132 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
8133 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.231 , page 144)'', most notably smileys in the
8136 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
8142 This flag controls whether you want to be asked to enter a label for a certifi-
8143 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
8146 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
8152 This variable contains the name of either a directory, or a file which contains
8153 trusted certificates for use with OpenSSL. (S/MIME only)
8155 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
8159 The Mutt Next Generation E-Mail Client 155
8163 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
8164 and retrieval of keys by itself. This is very basic right now, and keys and
8165 certificates are stored in two different directories, both named as the hash-
8166 value retrieved from OpenSSL. There is an index file which contains mailbox-
8167 address keyid pairs, and which can be manually edited. This one points to the
8168 location of the certificates. (S/MIME only)
8170 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8176 This format string specifies a command which is used to decrypt application/x-
8177 pkcs7-mime attachments.
8179 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
8183 Expands to the name of a file containing a message.
8186 Expands to the name of a file containing the signature part of a
8187 multipart/signed attachment when verifying it.
8190 The key-pair specified with _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by (section 7.4.276 ,
8194 One or more certificate IDs.
8197 The algorithm used for encryption.
8200 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
8201 7.4.272 , page 154) points to a directory or file, this expands to
8202 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.272 , page 154)' or
8203 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.272 , page 154)'.
8205 For examples on how to configure these formats, see the smime.rc in the sam-
8206 ples/ subdirectory which has been installed on your system alongside the docu-
8207 mentation. (S/MIME only)
8209 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8215 The Mutt Next Generation E-Mail Client 156
8217 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
8218 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8219 mailbox-address to determine the key to use. It will ask you to supply a key,
8220 if it can't find one. (S/MIME only)
8222 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8228 This is the default key-pair to use for signing. This must be set to the keyid
8229 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8231 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8237 This command is used to create encrypted S/MIME messages. (S/MIME only)
8239 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8245 This sets the algorithm that should be used for encryption. Valid choices are
8246 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8248 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8250 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8256 This command is used to extract X509 certificates from a PKCS7 structure.
8259 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\be_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8265 This command is used to extract the mail address(es) used for storing X509 cer-
8266 tificates, and for verification purposes (to check whether the certificate was
8267 issued for the sender's mailbox). (S/MIME only)
8269 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\be_
\br_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8271 The Mutt Next Generation E-Mail Client 157
8277 This command is used to extract only the signers X509 certificate from a S/MIME
8278 signature, so that the certificate's owner may get compared to the email's
8279 ``From:'' header field. (S/MIME only)
8281 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8287 This command is used to import a certificate via smime_keysng. (S/MIME only)
8289 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8295 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8296 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8298 However, this has no effect while replying, since Mutt-ng will automatically
8299 select the same application that was used to sign/encrypt the original message.
8301 (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-
8302 tion 7.4.40 , page 98).) (S/MIME only)
8304 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8310 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8311 retrieval of keys/certs by itself. This is very basic right now, and stores
8312 keys and certificates in two different directories, both named as the hash-
8313 value retrieved from OpenSSL. There is an index file which contains mailbox-
8314 address keyid pair, and which can be manually edited. This one points to the
8315 location of the private keys. (S/MIME only)
8317 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8323 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8324 to extract the public X509 certificate(s). (S/MIME only)
8326 The Mutt Next Generation E-Mail Client 158
8328 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8334 This command is used to created S/MIME signatures of type multipart/signed,
8335 which can be read by all mail clients. (S/MIME only)
8337 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bo_
\bp_
\ba_
\bq_
\bu_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8343 This command is used to created S/MIME signatures of type application/x-
8344 pkcs7-signature, which can only be handled by mail clients supporting the
8345 S/MIME extension. (S/MIME only)
8347 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8353 The number of seconds after which a cached passphrase will expire if not used.
8356 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8362 This command is used to verify S/MIME signatures of type multipart/signed.
8365 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bo_
\bp_
\ba_
\bq_
\bu_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8371 This command is used to verify S/MIME signatures of type application/x-
8372 pkcs7-mime. (S/MIME only)
8374 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8382 The Mutt Next Generation E-Mail Client 159
8384 If this variable is non-empty, it'll be used as the envelope sender. If it's
8385 empty (the default), the value of the regular From: header will be used.
8387 This may be necessary as some providers don't allow for arbitrary values as the
8388 envelope sender but only a particular one which may not be the same as the
8389 user's desired From: header.
8391 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8399 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8400 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8401 _
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page 150)'', and any associated variables.
8403 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8411 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8412 7.4.296 , page 159)'' is set, but this variable is not, you will be prompted
8413 for a password when sending.
8415 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8416 the superuser of your machine may read it regardless of the file's permissions.
8418 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8426 Defines the port that the SMTP host is listening on for mail delivery. Must be
8427 specified as a number.
8429 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8430 will probably desire 587, the mail submission port.
8432 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8438 The Mutt Next Generation E-Mail Client 160
8440 Availability: SMTP (and SSL)
8442 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8443 server does not support STARTTLS or there is an error in the TLS Handshake, the
8444 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8445 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8446 port enabled in order to use it.
8448 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8456 Defines the username to use with SMTP AUTH. Setting this variable will cause
8457 Mutt-ng to attempt to use SMTP AUTH when sending.
8459 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\bs_
\bo_
\br_
\bt
8465 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8470 mailbox-order (unsorted)
8478 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8479 (example: set sort=reverse-date-sent).
8481 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8487 Specifies how the entries in the ``alias'' menu are sorted. The following are
8490 The Mutt Next Generation E-Mail Client 161
8492 address (sort alphabetically by email address)
8493 alias (sort alphabetically by alias name)
8494 unsorted (leave in order specified in .muttrc)
8496 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8502 When sorting by threads, this variable controls how threads are sorted in rela-
8503 tion to other threads, and how the branches of the thread trees are sorted.
8504 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160)'' can,
8505 except threads (in that case, Mutt-ng will just use date-sent). You can also
8506 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8507 come after reverse-. The last- prefix causes messages to be sorted against its
8508 siblings by which has the last descendant, using the rest of sort_aux as an
8511 For instance, set sort_aux=last-date-received would mean that if a new message
8512 is received in a thread, that thread becomes the last one displayed (or the
8513 first, if you have set sort=reverse-threads.)
8515 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8516 (section 7.4.299 , page 160) is reversed again (which is not the right thing
8517 to do, but kept to not break any existing configuration setting).
8519 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8525 Specifies how to sort entries in the file browser. By default, the entries are
8526 sorted alphabetically. Valid values:
8528 alpha (alphabetically)
8533 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8534 (example: set sort_browser=reverse-date).
8536 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8542 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
8544 The Mutt Next Generation E-Mail Client 162
8546 (section 7.4.318 , page 167)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8547 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.301 ,
8548 page 161) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8549 sage by subject if the subject of the child message starts with a substring
8550 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.237 , page 146)''. With
8551 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.301 , page 161) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8552 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
8553 7.4.237 , page 146)'' parts of both messages are identical.
8555 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8561 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.302 , page 161)'' controls what happens when
8562 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8563 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8564 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.302 ,
8565 page 161)'' as a separator.
8567 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8573 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8574 you can specify its location with this variable. Mutt-ng will automatically
8575 set this variable to the value of the environment variable $MAIL if it is not
8578 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8584 This variable specifies a file containing trusted CA certificates. Any server
8585 certificate that is signed with one of these CA certificates are also automati-
8588 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8590 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8598 The file containing a client certificate and its associated private key.
8600 The Mutt Next Generation E-Mail Client 163
8602 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8608 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8609 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8610 server does not advertise the capability, since it would otherwise have to
8611 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8612 7.4.308 , page 163)''.
8614 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8620 Availability: GNUTLS
8622 This variable specifies the minimum acceptable prime size (in bits) for use in
8623 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8626 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8632 Availability: SSL or GNUTLS
8634 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8635 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8636 regardless of the server's capabilities.
8638 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8646 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8649 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8655 Availability: SSL or GNUTLS
8657 The Mutt Next Generation E-Mail Client 164
8659 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8662 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8668 Availability: SSL or GNUTLS
8670 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8673 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8681 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8682 store when checking if server certificate is signed by a trusted CA.
8684 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8690 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8691 tion 7.4.314 , page 164)''. The first character is used when the mailbox is
8692 unchanged. The second is used when the mailbox has been changed, and it needs
8693 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8694 if the mailbox will not be written when exiting that mailbox (You can toggle
8695 whether to write changes to a mailbox with the toggle-write operation, bound by
8696 default to ``%''). The fourth is used to indicate that the current folder has
8697 been opened in attach-message mode (Certain operations like composing a new
8698 mail, replying, forwarding, etc. are not permitted in this mode).
8700 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8704 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8705 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8706 %l?]---(%s/%S)-%>-(%P)---'
8708 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8709 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.115 , page 115)'', but has
8710 its own set of printf(3)-like sequences:
8712 The Mutt Next Generation E-Mail Client 165
8715 number of mailboxes with new mail *
8718 the short pathname of the current mailbox
8721 number of deleted messages *
8724 the full pathname of the current mailbox
8727 number of flagged messages *
8733 size (in bytes) of the current mailbox *
8736 size (in bytes) of the messages shown (i.e., which match the cur-
8740 the number of messages in the mailbox *
8743 the number of messages shown (i.e., which match the current limit)
8747 number of new messages in the mailbox *
8750 number of old unread messages *
8753 number of postponed messages *
8756 percentage of the way through the index
8759 modified/read-only/won't-write/attach-message indicator, according
8760 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.313 , page 164)
8763 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160))
8766 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.299 , page
8769 The Mutt Next Generation E-Mail Client 166
8772 number of tagged messages *
8775 number of unread messages *
8778 Mutt-ng version string
8781 currently active limit pattern, if any *
8784 right justify the rest of the string and pad with 'X'
8787 pad to the end of the line with 'X'
8789 * = can be optionally printed if nonzero
8791 Some of the above sequences can be used to optionally print a string if their
8792 value is nonzero. For example, you may only want to see the number of flagged
8793 messages if such messages exist, since zero is not particularly meaningful. To
8794 optionally print a string based upon one of the above sequences, the following
8797 %?<sequence_char>?<optional_string>?
8799 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
8800 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
8801 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8804 Here is an example illustrating how to optionally print the number of new mes-
8807 %?n?%n new messages.?
8809 Additionally you can switch between two strings, the first one, if a value is
8810 zero, the second one, if the value is nonzero, by using the following con-
8813 %?<sequence_char>?<if_string>&<else_string>?
8815 You can additionally force the result of any printf(3)-like sequence to be low-
8816 ercase by prefixing the sequence character with an underscore (_) sign. For
8817 example, if you want to display the local hostname in lowercase, you would use:
8821 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8822 replace any dots in the expansion by underscores. This might be helpful with
8823 IMAP folders that don't like dots in folder names.
8825 The Mutt Next Generation E-Mail Client 167
8827 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8833 Setting this variable causes the ``status bar'' to be displayed on the first
8834 line of the screen rather than near the bottom.
8836 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8842 With mailto: style links, a body as well as arbitrary header information may be
8843 embedded. This may lead to (user) headers being overwriten without note if
8844 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'' is unset.
8846 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8847 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8848 message including headers will be shown in the editor regardless of what
8849 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.59 , page 102)'' is set to.
8851 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8857 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8858 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8859 messages are often generated by old mailers or buggy mailers like MS Outlook
8860 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.13 , page 91).
8862 This option also replaces linear-white-space between encoded-word and *text to
8863 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8864 from being devided into multiple lines.
8866 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8872 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8873 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.297 , page 160)'' by mes-
8874 sage threads. By default, messages with the same subject are grouped together
8875 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8876 mailbox where you might have several unrelated messages with the subject ``hi''
8877 which will get grouped together.
8879 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8881 The Mutt Next Generation E-Mail Client 168
8887 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8888 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.320 , page 167) when replying. This is
8889 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8892 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8894 Type: regular expression
8896 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8898 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.319 , page 167) is _
\bs_
\be_
\bt, mutt-ng
8899 will remove this trailing part of the ``Subject'' line when replying if it
8900 won't be empty afterwards.
8902 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
8908 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
8909 i.e. a space will be inserted between the quote characters and the actual text.
8911 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
8917 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
8918 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
8919 mand like ``xterm -e muttng.''
8921 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
8927 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
8928 format is easier to handle for some mailing software, and generally just looks
8929 like ordinary text. To actually make use of this format's features, you'll
8930 need support in your editor.
8932 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.114 , page 115) is ignored when this
8935 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8937 The Mutt Next Generation E-Mail Client 169
8943 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
8944 tion 7.2 , page 83)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
8945 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
8946 as they appear in the folder.
8948 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
8954 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
8955 messages by subject.
8957 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bt_
\bi_
\bl_
\bd_
\be
8963 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
8966 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8972 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
8973 pressed in the main menu before timing out and checking for new mail. A value
8974 of zero or less will cause Mutt-ng to never time out.
8976 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
8982 This variable allows you to specify where Mutt-ng will place its temporary
8983 files needed for displaying and composing messages. If this variable is not
8984 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
8987 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8993 The Mutt Next Generation E-Mail Client 170
8995 Controls the character used to indicate mail addressed to you. The first char-
8996 acter is the one used when the mail is NOT addressed to your address (default:
8997 space). The second is used when you are the only recipient of the message
8998 (default: +). The third is when your address appears in the ``To:'' header
8999 field, but you are not the only recipient of the message (default: T). The
9000 fourth character is used when your address is specified in the ``Cc:'' header
9001 field, but you are not the only recipient. The fifth character is used to
9002 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
9003 when a mail was sent to a mailing-list you're subscribe to (default: L).
9005 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bt_
\br_
\ba_
\bs_
\bh
9011 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
9012 marked for deletion will be moved, instead of being irremediably purged.
9014 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
9015 that there is no way to recover mail.
9017 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
9023 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
9024 a raw socket. You may be able to use this to set up preauthenticated connec-
9025 tions to your IMAP/POP3 server. Example:
9027 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
9029 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
9030 without having to enter a password.
9032 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bu_
\bm_
\ba_
\bs_
\bk
9038 This sets the umask that will be used by Mutt-ng when creating all kinds of
9039 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
9041 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
9047 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
9048 rent thread is _
\bu_
\bncollapsed.
9050 The Mutt Next Generation E-Mail Client 171
9052 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
9058 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
9059 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
9060 with the SMTP support via libESMTP. Otherwise you may not be able to send
9063 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.253 , page
9064 150)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
9065 negotiation or tell libESMTP to do so.
9067 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
9073 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
9074 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.94 , page 110)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
9075 no addresses will be qualified.
9077 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
9083 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
9084 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
9085 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.16 , page 37)'' command.
9087 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
9095 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
9097 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
9100 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
9106 The Mutt Next Generation E-Mail Client 172
9108 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
9109 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
9110 mally, the default should work.
9112 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
9118 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
9121 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
9127 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-
9128 _
\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.
9130 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
9131 78)'', provided that the corresponding mailcap entry has a needsterminal flag,
9132 and the external program is interactive.
9134 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
9135 a key only if the external command returned a non-zero status.
9137 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bw_
\be_
\be_
\bd
9143 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
9144 replying to messages.
9146 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9152 Controls whether searches wrap around the end of the mailbox.
9154 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
9155 searches will not wrap.
9157 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
9163 The Mutt Next Generation E-Mail Client 173
9165 Controls the size of the margin remaining at the right side of the terminal
9166 when Mutt-ng's pager does smart wrapping.
9168 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
9174 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
9175 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
9177 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
9183 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
9184 indicate progress. If set to 0, only a single message will be displayed before
9187 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.232 , page 145)'' variable.
9189 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b6 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
9193 Default: 'M%?n?AIL&ail?'
9195 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-
9196 tion 7.4.348 , page 173) is _
\bs_
\be_
\bt. This string is identical in formatting to the
9197 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 , page 164)''.
9199 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b7 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
9205 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.348 , page 173) is _
\bs_
\be_
\bt, this string will be
9206 used to set the title when leaving mutt-ng. For terminal-based programs,
9207 there's no easy and portable way to read the current title so mutt-ng cannot
9208 read it upon startup and restore it when exiting.
9210 Based on the xterm FAQ, the following might work:
9212 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9215 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b8 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9219 The Mutt Next Generation E-Mail Client 174
9223 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9224 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9227 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b9 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9231 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9233 Controls the format of the title bar of the xterm provided that
9234 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.348 , page 173) has been _
\bs_
\be_
\bt. This string is
9235 identical in formatting to the one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.314 ,
9238 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9240 The following is the list of available functions listed by the mapping in which
9241 they are available. The default key setting is given, and an explanation of
9242 what the function does. The key bindings of these functions can be changed
9243 with the _
\bb_
\bi_
\bn_
\bd (section 3.5 , page 26) command.
9245 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9247 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9248 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9249 tings for this menu will affect the default bindings for all menus (except as
9252 The Mutt Next Generation E-Mail Client 175
9254 bottom-page L move to the bottom of the page
9255 current-bottom not bound move current entry to bottom of page
9256 current-middle not bound move current entry to middle of page
9257 current-top not bound move current entry to top of page
9258 enter-command : enter a muttngrc command
9259 exit q exit this menu
9260 first-entry = move to the first entry
9261 half-down ] scroll down 1/2 page
9262 half-up [ scroll up 1/2 page
9264 jump number jump to an index number
9265 last-entry * move to the last entry
9266 middle-page M move to the middle of the page
9267 next-entry j move to the next entry
9268 next-line > scroll down one line
9269 next-page z move to the next page
9270 previous-entry k move to the previous entry
9271 previous-line < scroll up one line
9272 previous-page Z move to the previous page
9273 refresh ^L clear and redraw the screen
9274 search / search for a regular expression
9275 search-next n search for next match
9276 search-opposite not bound search for next match in opposite direction
9277 search-reverse ESC / search backwards for a regular expression
9278 select-entry RET select the current entry
9279 shell-escape ! run a program in a subshell
9280 tag-entry t toggle the tag on the current entry
9281 tag-prefix ; apply next command to tagged entries
9282 tag-prefix-cond not bound apply next function ONLY to tagged messages
9283 top-page H move to the top of the page
9284 what-key not bound display the keycode for a key press
9286 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9288 The Mutt Next Generation E-Mail Client 176
9290 bounce-message b remail a message to another user
9291 change-folder c open a different folder
9292 change-folder-readonly ESC c open a different folder in read only mode
9293 check-traditional-pgp ESC P check for classic pgp
9294 clear-flag W clear a status flag from a message
9295 copy-message C copy a message to a file/mailbox
9296 create-alias a create an alias from a message sender
9297 decode-copy ESC C decode a message and copy it to a file/mailbox
9298 decode-save ESC s decode a message and save it to a file/mailbox
9299 delete-message d delete the current entry
9300 delete-pattern D delete messages matching a pattern
9301 delete-subthread ESC d delete all messages in subthread
9302 delete-thread ^D delete all messages in thread
9303 display-address @ display full address of sender
9304 display-toggle-weed h display message and toggle header weeding
9305 display-message RET display a message
9306 edit e edit the current message
9307 edit-type ^E edit the current message's Content-Type
9308 exit x exit without saving changes
9309 extract-keys ^K extract PGP public keys
9310 fetch-mail G retrieve mail from POP server
9311 flag-message F toggle a message's 'important' flag
9312 forget-passphrase ^F wipe PGP passphrase from memory
9313 forward-message f forward a message with comments
9314 group-reply g reply to all recipients
9315 limit l show only messages matching a pattern
9316 list-reply L reply to specified mailing list
9317 mail m compose a new mail message
9318 mail-key ESC k mail a PGP public key
9319 next-new TAB jump to the next new message
9320 next-subthread ESC n jump to the next subthread
9321 next-thread ^N jump to the next thread
9322 next-undeleted j move to the next undeleted message
9323 next-unread not bound jump to the next unread message
9324 parent-message P jump to parent message in thread
9325 pipe-message | pipe message/attachment to a shell command
9326 previous-new ESC TAB jump to the previous new message
9327 previous-page Z move to the previous page
9328 previous-subthread ESC p jump to previous subthread
9329 previous-thread ^P jump to previous thread
9330 previous-undeleted k move to the last undelete message
9331 previous-unread not bound jump to the previous unread message
9332 print-message p print the current entry
9333 query Q query external program for addresses
9334 quit q save changes to mailbox and quit
9335 read-subthread ESC r mark the current subthread as read
9336 read-thread ^R mark the current thread as read
9337 recall-message R recall a postponed message
9338 reply r reply to a message
9339 resend-message ESC e resend message and preserve MIME structure
9340 save-message s save message/attachment to a file
9341 set-flag w set a status flag on a message
9342 show-version V show the Mutt-ng version number and date
9343 show-limit ESC l show currently active limit pattern, if any
9345 The Mutt Next Generation E-Mail Client 177
9347 sort-mailbox o sort messages
9348 sort-reverse O sort messages in reverse order
9349 sync-mailbox $ save changes to mailbox
9350 tag-pattern T tag messages matching a pattern
9351 tag-thread ESC t tag/untag all messages in the current thread
9352 toggle-new N toggle a message's 'new' flag
9353 toggle-write % toggle whether the mailbox will be rewritten
9354 undelete-message u undelete the current entry
9355 undelete-pattern U undelete messages matching a pattern
9356 undelete-subthread ESC u undelete all messages in subthread
9357 undelete-thread ^U undelete all messages in thread
9358 untag-pattern ^T untag messages matching a pattern
9359 view-attachments v show MIME attachments
9361 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9363 The Mutt Next Generation E-Mail Client 178
9365 bottom not bound jump to the bottom of the message
9366 bounce-message b remail a message to another user
9367 change-folder c open a different folder
9368 change-folder-readonly ESC c open a different folder in read only mode
9369 check-traditional-pgp ESC P check for classic pgp
9370 copy-message C copy a message to a file/mailbox
9371 create-alias a create an alias from a message sender
9372 decode-copy ESC C decode a message and copy it to a file/mailbox
9373 decode-save ESC s decode a message and save it to a file/mailbox
9374 delete-message d delete the current entry
9375 delete-subthread ESC d delete all messages in subthread
9376 delete-thread ^D delete all messages in thread
9377 display-address @ display full address of sender
9378 display-toggle-weed h display message and toggle header weeding
9379 edit e edit the current message
9380 edit-type ^E edit the current message's Content-Type
9381 enter-command : enter a muttngrc command
9382 exit i return to the main-menu
9383 extract-keys ^K extract PGP public keys
9384 flag-message F toggle a message's 'important' flag
9385 forget-passphrase ^F wipe PGP passphrase from memory
9386 forward-message f forward a message with comments
9387 group-reply g reply to all recipients
9388 half-up not bound move up one-half page
9389 half-down not bound move down one-half page
9391 list-reply L reply to specified mailing list
9392 mail m compose a new mail message
9393 mail-key ESC k mail a PGP public key
9394 mark-as-new N toggle a message's 'new' flag
9395 next-line RET scroll down one line
9396 next-entry J move to the next entry
9397 next-new TAB jump to the next new message
9398 next-page move to the next page
9399 next-subthread ESC n jump to the next subthread
9400 next-thread ^N jump to the next thread
9401 next-undeleted j move to the next undeleted message
9402 next-unread not bound jump to the next unread message
9403 parent-message P jump to parent message in thread
9404 pipe-message | pipe message/attachment to a shell command
9405 previous-line BackSpace scroll up one line
9406 previous-entry K move to the previous entry
9407 previous-new not bound jump to the previous new message
9408 previous-page - move to the previous page
9409 previous-subthread ESC p jump to previous subthread
9410 previous-thread ^P jump to previous thread
9411 previous-undeleted k move to the last undelete message
9412 previous-unread not bound jump to the previous unread message
9413 print-message p print the current entry
9414 quit Q save changes to mailbox and quit
9415 read-subthread ESC r mark the current subthread as read
9416 read-thread ^R mark the current thread as read
9417 recall-message R recall a postponed message
9418 redraw-screen ^L clear and redraw the screen
9420 The Mutt Next Generation E-Mail Client 179
9422 reply r reply to a message
9423 save-message s save message/attachment to a file
9424 search / search for a regular expression
9425 search-next n search for next match
9426 search-opposite not bound search for next match in opposite direction
9427 search-reverse ESC / search backwards for a regular expression
9428 search-toggle \ toggle search pattern coloring
9429 shell-escape ! invoke a command in a subshell
9430 show-version V show the Mutt-ng version number and date
9431 skip-quoted S skip beyond quoted text
9432 sync-mailbox $ save changes to mailbox
9433 tag-message t tag a message
9434 toggle-quoted T toggle display of quoted text
9435 top ^ jump to the top of the message
9436 undelete-message u undelete the current entry
9437 undelete-subthread ESC u undelete all messages in subthread
9438 undelete-thread ^U undelete all messages in thread
9439 view-attachments v show MIME attachments
9441 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9443 search / search for a regular expression
9444 search-next n search for next match
9445 search-reverse ESC / search backwards for a regular expression
9447 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9449 create-alias a create an alias from a message sender
9450 mail m compose a new mail message
9451 query Q query external program for addresses
9452 query-append A append new query results to current results
9453 search / search for a regular expression
9454 search-next n search for next match
9455 search-opposite not bound search for next match in opposite direction
9456 search-reverse ESC / search backwards for a regular expression
9458 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9460 The Mutt Next Generation E-Mail Client 180
9462 bounce-message b remail a message to another user
9463 collapse-parts v toggle display of subparts
9464 delete-entry d delete the current entry
9465 display-toggle-weed h display message and toggle header weeding
9466 edit-type ^E edit the current entry's Content-Type
9467 extract-keys ^K extract PGP public keys
9468 forward-message f forward a message with comments
9469 group-reply g reply to all recipients
9470 list-reply L reply to specified mailing list
9471 pipe-entry | pipe message/attachment to a shell command
9472 print-entry p print the current entry
9473 reply r reply to a message
9474 resend-message ESC e resend message and preserve MIME structure
9475 save-entry s save message/attachment to a file
9476 undelete-entry u undelete the current entry
9477 view-attach RET view attachment using mailcap entry if necessary
9478 view-mailcap m force viewing of attachment using mailcap
9479 view-text T view attachment as text
9481 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9483 The Mutt Next Generation E-Mail Client 181
9485 attach-file a attach a file(s) to this message
9486 attach-message A attach message(s) to this message
9487 attach-key ESC k attach a PGP public key
9488 copy-file C save message/attachment to a file
9489 detach-file D delete the current entry
9490 display-toggle-weed h display message and toggle header weeding
9491 edit-bcc b edit the BCC list
9492 edit-cc c edit the CC list
9493 edit-description d edit attachment description
9494 edit-encoding ^E edit attachment transfer-encoding
9495 edit-fcc f enter a file to save a copy of this message in
9496 edit-from ESC f edit the from: field
9497 edit-file ^X e edit the file to be attached
9498 edit-headers E edit the message with headers
9499 edit e edit the message
9500 edit-mime m edit attachment using mailcap entry
9501 edit-reply-to r edit the Reply-To field
9502 edit-subject s edit the subject of this message
9503 edit-to t edit the TO list
9504 edit-type ^T edit attachment type
9505 filter-entry F filter attachment through a shell command
9506 forget-passphrase ^F wipe PGP passphrase from memory
9507 ispell i run ispell on the message
9508 new-mime n compose new attachment using mailcap entry
9509 pgp-menu p show PGP options
9510 pipe-entry | pipe message/attachment to a shell command
9511 postpone-message P save this message to send later
9512 print-entry l print the current entry
9513 rename-file R rename/move an attached file
9514 send-message y send the message
9515 toggle-unlink u toggle whether to delete file after sending it
9516 view-attach RET view attachment using mailcap entry if necessary
9517 write-fcc w write the message to a folder
9519 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9521 delete-entry d delete the current entry
9522 undelete-entry u undelete the current entry
9524 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9526 The Mutt Next Generation E-Mail Client 182
9528 change-dir c change directories
9529 check-new TAB check mailboxes for new mail
9530 enter-mask m enter a file mask
9531 search / search for a regular expression
9532 search-next n search for next match
9533 search-reverse ESC / search backwards for a regular expression
9534 select-new N select a new file in this directory
9535 sort o sort messages
9536 sort-reverse O sort messages in reverse order
9537 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9538 view-file SPACE view file
9539 subscribe s subscribe to current mailbox (IMAP Only)
9540 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9541 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9543 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9545 view-name % view the key's user id
9546 verify-key c verify a PGP public key
9548 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9550 backspace BackSpace delete the char in front of the cursor
9551 backward-char ^B move the cursor one character to the left
9552 backward-word ESC b move the cursor to the previous word
9553 bol ^A jump to the beginning of the line
9554 buffy-cycle Space cycle among incoming mailboxes
9555 capitalize-word ESC c uppercase the first character in the word
9556 complete TAB complete filename or alias
9557 complete-query ^T complete address with query
9558 delete-char ^D delete the char under the cursor
9559 downcase-word ESC l lowercase all characters in current word
9560 eol ^E jump to the end of the line
9561 forward-char ^F move the cursor one character to the right
9562 forward-word ESC f move the cursor to the next word
9563 history-down not bound scroll down through the history list
9564 history-up not bound scroll up through the history list
9565 kill-eol ^K delete chars from cursor to end of line
9566 kill-eow ESC d delete chars from cursor to end of word
9567 kill-line ^U delete all chars on the line
9568 kill-word ^W delete the word in front of the cursor
9569 quote-char ^V quote the next typed key
9570 transpose-chars not bound transpose character under cursor with previous
9571 upcase-word ESC u uppercase all characters in current word
9573 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9575 The Mutt Next Generation E-Mail Client 183
9577 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9579 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9580 back in the ELM-ME days.
9582 The following people have been very helpful to the development of Mutt:
9584 Vikas Agnihotri <vikasa@writeme.com>,
9586 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9588 Aric Blumer <aric@fore.com>,
9590 John Capo <jc@irbs.com>,
9592 David Champion <dgc@uchicago.edu,
9594 Brendan Cully <brendan@kublai.com>,
9596 Liviu Daia <daia@stoilow.imar.ro>,
9598 Thomas E. Dickey <dickey@herndon4.his.com>,
9600 David DeSimone <fox@convex.hp.com>,
9602 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9604 Ruslan Ermilov <ru@freebsd.org>,
9606 Edmund Grimley Evans <edmundo@rano.org,
9608 Michael Finken <finken@conware.de>,
9610 Sven Guckes <guckes@math.fu-berlin.de>,
9612 Lars Hecking <lhecking@nmrc.ie>,
9614 Mark Holloman <holloman@nando.net>,
9616 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9618 Marco d'Itri <md@linux.it>,
9620 Bjrn Jacke <bjacke@suse.com>,
9622 Byrial Jensen <byrial@image.dk>,
9624 David Jeske <jeske@igcom.net>,
9626 Christophe Kalt <kalt@hugo.int-evry.fr>,
9628 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9630 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9632 The Mutt Next Generation E-Mail Client 184
9634 Brandon Long <blong@fiction.net>,
9636 Jimmy Mkel <jmy@flashback.net>,
9638 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9640 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9642 Andrew W. Nosenko <awn@bcs.zp.ua>,
9644 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9646 Clint Olsen <olsenc@ichips.intel.com>,
9648 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9650 Thomas Parmelan <tom@ankh.fr.eu.org>,
9652 Ollivier Robert <roberto@keltia.freenix.fr>,
9654 Thomas Roessler <roessler@does-not-exist.org>,
9656 Roland Rosenfeld <roland@spinnaker.de>,
9658 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9660 Allain Thivillon <Allain.Thivillon@alma.fr>,
9662 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9664 Vsevolod Volkov <vvv@lucky.net>,
9666 Ken Weinert <kenw@ihs.com>
9668 Mutt-ng is developed by the following people:
9670 Andreas Krennmair <ak@synflood.at>
9672 Nico Golde <nico@ngolde.de>
9674 Rocco Rutte <pdmef@cs.tu-berlin.de>
9676 The following people have been very helpful to the development of Mutt-ng:
9678 Christian Gall <cg@cgall.de>
9680 Iain Lea <iain@bricbrac.de>
9682 Andreas Kneib <akneib@gmx.net>
9684 Carsten Schoelzki <cjs@weisshuhn.de>
9686 Elimar Riesebieter <riesebie@lxtec.de>
9688 The Mutt Next Generation E-Mail Client 185
9690 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9692 This document was written in SGML, and then rendered using the sgml-tools pack-
9695 The Mutt Next Generation E-Mail Client 186
9699 1. Introduction .......................................................... 1
9700 1.1 Overview ........................................................ 1
9701 1.2 Mutt-ng Home Page ............................................... 1
9702 1.3 Mailing Lists ................................................... 1
9703 1.4 Software Distribution Sites ..................................... 2
9704 1.5 IRC ............................................................. 2
9705 1.6 Weblog .......................................................... 2
9706 1.7 Copyright ....................................................... 2
9708 2. Getting Started ..................................................... 2
9709 2.1 Basic Concepts .............................................. 2
9710 2.1.1 Screens and Menus 3
9711 2.1.2 Configuration 3
9714 2.1.5 Modularization 4
9716 2.2 Screens and Menus ........................................... 4
9719 2.2.3 File Browser 5
9722 2.2.6 Compose Menu 6
9724 2.2.8 Attachment Menu 6
9726 2.3 Moving Around in Menus .......................................... 6
9727 2.4 Editing Input Fields ............................................ 7
9728 2.5 Reading Mail - The Index and Pager .............................. 8
9729 2.5.1 The Message Index 8
9731 2.5.3 Threaded Mode 11
9732 2.5.4 Miscellaneous Functions 11
9733 2.6 Sending Mail ................................................... 14
9734 2.6.1 Composing new messages 14
9736 2.6.3 Editing the message header 17
9737 2.6.4 Using Mutt-ng with PGP 18
9738 2.6.5 Sending anonymous messages via mixmaster 19
9739 2.7 Forwarding and Bouncing Mail ................................... 19
9740 2.8 Postponing Mail ................................................ 20
9742 3. Configuration ........................................................ 21
9743 3.1 Locations of Configuration Files ............................... 21
9744 3.2 Basic Syntax of Initialization Files ........................... 21
9745 3.3 Variable Expansion ........................................... 23
9746 3.3.1 Commands' Output 23
9747 3.3.2 Environment Variables 23
9751 3.3.3 Configuration Variables 23
9752 3.3.4 Self-Defined Variables 23
9753 3.3.5 Type Conversions 25
9754 3.4 Defining/Using aliases ......................................... 25
9755 3.5 Changing the default key bindings .............................. 26
9756 3.6 Defining aliases for character sets ........................... 28
9757 3.7 Setting variables based upon mailbox ........................... 28
9758 3.8 Keyboard macros ................................................ 29
9759 3.9 Using color and mono video attributes .......................... 30
9760 3.10 Ignoring (weeding) unwanted message headers .................... 32
9761 3.11 Alternative addresses .......................................... 33
9762 3.12 Format = Flowed .............................................. 33
9763 3.12.1 Introduction 33
9764 3.12.2 Receiving: Display Setup 33
9766 3.12.4 Additional Notes 35
9767 3.13 Mailing lists .................................................. 35
9768 3.14 Using Multiple spool mailboxes ................................. 36
9769 3.15 Defining mailboxes which receive mail .......................... 36
9770 3.16 User defined headers ........................................... 37
9771 3.17 Defining the order of headers when viewing messages ............ 38
9772 3.18 Specify default save filename .................................. 38
9773 3.19 Specify default Fcc: mailbox when composing .................... 38
9774 3.20 Specify default save filename and default Fcc: mailbox at once . 39
9775 3.21 Change settings based upon message recipients .................. 39
9776 3.22 Change settings before formatting a message .................... 40
9777 3.23 Choosing the cryptographic key of the recipient ................ 40
9778 3.24 Adding key sequences to the keyboard buffer .................... 40
9779 3.25 Executing functions ............................................ 41
9780 3.26 Message Scoring ................................................ 41
9781 3.27 Spam detection ................................................. 42
9782 3.28 Setting variables .............................................. 44
9783 3.29 Reading initialization commands from another file .............. 45
9784 3.30 Removing hooks ................................................. 45
9785 3.31 Sharing Setups ............................................. 45
9786 3.31.1 Character Sets 45
9787 3.31.2 Modularization 46
9788 3.31.3 Conditional parts 46
9789 3.32 Obsolete Variables ............................................. 48
9791 4. Advanced Usage ....................................................... 48
9792 4.1 Regular Expressions ............................................ 48
9793 4.2 Patterns ....................................................... 51
9794 4.2.1 Complex Patterns 51
9795 4.2.2 Patterns and Dates 52
9796 4.3 Format Strings ............................................. 52
9797 4.3.1 Introduction 52
9798 4.3.2 Conditional Expansion 54
9799 4.3.3 Modifications and Padding 55
9800 4.4 Using Tags ..................................................... 55
9801 4.5 Using Hooks .................................................... 56
9802 4.5.1 Message Matching in Hooks 57
9803 4.6 Using the sidebar .............................................. 57
9807 4.7 External Address Queries ....................................... 58
9808 4.8 Mailbox Formats ................................................ 59
9809 4.9 Mailbox Shortcuts .............................................. 60
9810 4.10 Handling Mailing Lists ......................................... 60
9811 4.11 Editing threads ................................................ 61
9812 4.11.1 Linking threads 62
9813 4.11.2 Breaking threads 62
9814 4.12 Delivery Status Notification (DSN) Support ..................... 62
9815 4.13 POP3 Support (OPTIONAL) ........................................ 62
9816 4.14 IMAP Support (OPTIONAL) ........................................ 63
9817 4.14.1 The Folder Browser 64
9818 4.14.2 Authentication 64
9819 4.15 NNTP Support (OPTIONAL) ........................................ 65
9820 4.15.1 Again: Scoring 65
9821 4.16 SMTP Support (OPTIONAL) ........................................ 66
9822 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 67
9823 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 67
9824 4.19 Compressed folders Support (OPTIONAL) .......................... 67
9825 4.19.1 Open a compressed mailbox for reading 68
9826 4.19.2 Write a compressed mailbox 68
9827 4.19.3 Append a message to a compressed mailbox 69
9828 4.19.4 Encrypted folders 70
9830 5. Mutt-ng's MIME Support ............................................... 70
9831 5.1 Using MIME in Mutt ............................................. 70
9832 5.1.1 Viewing MIME messages in the pager 70
9833 5.1.2 The Attachment Menu 71
9834 5.1.3 The Compose Menu 71
9835 5.2 MIME Type configuration with mime.types ........................ 71
9836 5.3 MIME Viewer configuration with mailcap ......................... 72
9837 5.3.1 The Basics of the mailcap file 73
9838 5.3.2 Secure use of mailcap 74
9839 5.3.3 Advanced mailcap Usage 74
9840 5.3.4 Example mailcap files 77
9841 5.4 MIME Autoview .................................................. 78
9842 5.5 MIME Multipart/Alternative ..................................... 79
9843 5.6 MIME Lookup .................................................... 79
9845 6. Security Considerations ............................................ 80
9846 6.1 Passwords .................................................. 80
9847 6.2 Temporary Files ............................................ 80
9848 6.3 Information Leaks ............................................ 80
9849 6.3.1 Message-ID: headers 80
9850 6.3.2 mailto:-style links 81
9851 6.4 External applications ...................................... 81
9855 7. Reference ............................................................ 82
9856 7.1 Command line options ........................................... 82
9857 7.2 Patterns ....................................................... 83
9858 7.3 Configuration Commands ......................................... 85
9859 7.4 Configuration variables .......................................... 87
9863 7.4.1 abort_noattach 88
9864 7.4.2 abort_nosubject 89
9865 7.4.3 abort_unmodified 89
9866 7.4.4 agent_string 89
9868 7.4.6 alias_format 89
9871 7.4.9 arrow_cursor 90
9872 7.4.10 ascii_chars 91
9875 7.4.13 assumed_charset 91
9876 7.4.14 attach_format 91
9877 7.4.15 attach_remind_regexp 92
9878 7.4.16 attach_sep 93
9879 7.4.17 attach_split 93
9880 7.4.18 attribution 93
9886 7.4.24 bounce_delivered 94
9887 7.4.25 braille_friendly 94
9888 7.4.26 certificate_file 95
9891 7.4.29 collapse_unread 95
9892 7.4.30 compose_format 96
9893 7.4.31 config_charset 96
9894 7.4.32 confirmappend 96
9895 7.4.33 confirmcreate 96
9896 7.4.34 connect_timeout 96
9897 7.4.35 content_type 97
9899 7.4.37 crypt_autoencrypt 97
9900 7.4.38 crypt_autopgp 97
9901 7.4.39 crypt_autosign 98
9902 7.4.40 crypt_autosmime 98
9903 7.4.41 crypt_replyencrypt 98
9904 7.4.42 crypt_replysign 98
9905 7.4.43 crypt_replysignencrypted 98
9906 7.4.44 crypt_timestamp 99
9907 7.4.45 crypt_use_gpgme 99
9908 7.4.46 crypt_verify_sig 99
9909 7.4.47 date_format 99
9910 7.4.48 debug_level 100
9911 7.4.49 default_hook 100
9913 7.4.51 delete_space 100
9914 7.4.52 delete_untag 101
9915 7.4.53 digest_collapse 101
9919 7.4.54 display_filter 101
9920 7.4.55 dotlock_program 101
9921 7.4.56 dsn_notify 101
9922 7.4.57 dsn_return 102
9923 7.4.58 duplicate_threads 102
9924 7.4.59 edit_headers 102
9926 7.4.61 encode_from 102
9927 7.4.62 entropy_file 103
9928 7.4.63 envelope_from 103
9930 7.4.65 fast_reply 103
9931 7.4.66 fcc_attach 104
9932 7.4.67 fcc_clear 104
9933 7.4.68 file_charset 104
9935 7.4.70 folder_format 104
9936 7.4.71 followup_to 105
9937 7.4.72 force_buffy_check 106
9938 7.4.73 force_name 106
9939 7.4.74 forward_decode 106
9940 7.4.75 forward_decrypt 106
9941 7.4.76 forward_edit 106
9942 7.4.77 forward_format 107
9943 7.4.78 forward_quote 107
9945 7.4.80 gecos_mask 107
9948 7.4.83 header_cache 108
9949 7.4.84 header_cache_compress 108
9951 7.4.86 hidden_host 109
9952 7.4.87 hide_limited 109
9953 7.4.88 hide_missing 109
9954 7.4.89 hide_thread_subject 109
9955 7.4.90 hide_top_limited 110
9956 7.4.91 hide_top_missing 110
9958 7.4.93 honor_followup_to 110
9960 7.4.95 ignore_list_reply_to 110
9961 7.4.96 imap_authenticators 111
9962 7.4.97 imap_check_subscribed 111
9963 7.4.98 imap_delim_chars 111
9964 7.4.99 imap_headers 112
9965 7.4.100 imap_home_namespace 112
9966 7.4.101 imap_keepalive 112
9967 7.4.102 imap_list_subscribed 112
9968 7.4.103 imap_login 113
9969 7.4.104 imap_mail_check 113
9970 7.4.105 imap_pass 113
9971 7.4.106 imap_passive 113
9975 7.4.107 imap_peek 114
9976 7.4.108 imap_reconnect 114
9977 7.4.109 imap_servernoise 114
9978 7.4.110 imap_user 114
9979 7.4.111 implicit_autoview 114
9981 7.4.113 include_onlyfirst 115
9982 7.4.114 indent_string 115
9983 7.4.115 index_format 115
9985 7.4.117 keep_flagged 118
9986 7.4.118 list_reply 118
9988 7.4.120 mail_check 119
9989 7.4.121 mailcap_path 119
9990 7.4.122 mailcap_sanitize 119
9991 7.4.123 maildir_header_cache_verify 119
9992 7.4.124 maildir_trash 119
9993 7.4.125 mark_old 120
9996 7.4.128 max_display_recips 120
9997 7.4.129 max_line_length 120
9999 7.4.131 mbox_type 121
10000 7.4.132 menu_context 121
10001 7.4.133 menu_move_off 121
10002 7.4.134 menu_scroll 121
10003 7.4.135 message_format 122
10004 7.4.136 meta_key 122
10006 7.4.138 mh_purge 122
10007 7.4.139 mh_seq_flagged 122
10008 7.4.140 mh_seq_replied 123
10009 7.4.141 mh_seq_unseen 123
10010 7.4.142 mime_forward 123
10011 7.4.143 mime_forward_decode 123
10012 7.4.144 mime_forward_rest 123
10013 7.4.145 mix_entry_format 123
10014 7.4.146 mixmaster 124
10016 7.4.148 msgid_format 124
10017 7.4.149 narrow_tree 125
10018 7.4.150 nntp_ask_followup_to 126
10019 7.4.151 nntp_ask_x_comment_to 126
10020 7.4.152 nntp_cache_dir 126
10021 7.4.153 nntp_catchup 126
10022 7.4.154 nntp_context 126
10023 7.4.155 nntp_followup_to_poster 127
10024 7.4.156 nntp_group_index_format 127
10025 7.4.157 nntp_host 127
10026 7.4.158 nntp_inews 128
10027 7.4.159 nntp_load_description 128
10031 7.4.160 nntp_mail_check 128
10032 7.4.161 nntp_mime_subject 129
10033 7.4.162 nntp_newsrc 129
10034 7.4.163 nntp_pass 129
10035 7.4.164 nntp_post_moderated 129
10036 7.4.165 nntp_reconnect 130
10037 7.4.166 nntp_save_unsubscribed 130
10038 7.4.167 nntp_show_new_news 130
10039 7.4.168 nntp_show_only_unread 130
10040 7.4.169 nntp_user 130
10041 7.4.170 nntp_x_comment_to 131
10042 7.4.171 operating_system 131
10044 7.4.173 pager_context 131
10045 7.4.174 pager_format 132
10046 7.4.175 pager_index_lines 132
10047 7.4.176 pager_stop 132
10048 7.4.177 pgp_auto_decode 132
10049 7.4.178 pgp_autoinline 132
10050 7.4.179 pgp_check_exit 133
10051 7.4.180 pgp_clearsign_command 133
10052 7.4.181 pgp_decode_command 133
10053 7.4.182 pgp_decrypt_command 134
10054 7.4.183 pgp_encrypt_only_command 134
10055 7.4.184 pgp_encrypt_sign_command 134
10056 7.4.185 pgp_entry_format 134
10057 7.4.186 pgp_export_command 135
10058 7.4.187 pgp_getkeys_command 135
10059 7.4.188 pgp_good_sign 135
10060 7.4.189 pgp_ignore_subkeys 135
10061 7.4.190 pgp_import_command 136
10062 7.4.191 pgp_list_pubring_command 136
10063 7.4.192 pgp_list_secring_command 136
10064 7.4.193 pgp_long_ids 136
10065 7.4.194 pgp_mime_auto 136
10066 7.4.195 pgp_replyinline 137
10067 7.4.196 pgp_retainable_sigs 137
10068 7.4.197 pgp_show_unusable 137
10069 7.4.198 pgp_sign_as 137
10070 7.4.199 pgp_sign_command 138
10071 7.4.200 pgp_sort_keys 138
10072 7.4.201 pgp_strict_enc 138
10073 7.4.202 pgp_timeout 138
10074 7.4.203 pgp_use_gpg_agent 139
10075 7.4.204 pgp_verify_command 139
10076 7.4.205 pgp_verify_key_command 139
10077 7.4.206 pipe_decode 139
10078 7.4.207 pipe_sep 139
10079 7.4.208 pipe_split 139
10080 7.4.209 pop_auth_try_all 140
10081 7.4.210 pop_authenticators 140
10082 7.4.211 pop_delete 140
10083 7.4.212 pop_host 140
10087 7.4.213 pop_last 141
10088 7.4.214 pop_mail_check 141
10089 7.4.215 pop_pass 141
10090 7.4.216 pop_reconnect 141
10091 7.4.217 pop_user 142
10092 7.4.218 post_indent_string 142
10093 7.4.219 postpone 142
10094 7.4.220 postponed 142
10095 7.4.221 preconnect 142
10097 7.4.223 print_command 143
10098 7.4.224 print_decode 143
10099 7.4.225 print_split 143
10100 7.4.226 prompt_after 144
10101 7.4.227 query_command 144
10103 7.4.229 quote_empty 144
10104 7.4.230 quote_quoted 144
10105 7.4.231 quote_regexp 145
10106 7.4.232 read_inc 145
10107 7.4.233 read_only 145
10108 7.4.234 realname 145
10111 7.4.237 reply_regexp 146
10112 7.4.238 reply_self 146
10113 7.4.239 reply_to 146
10114 7.4.240 resolve 147
10115 7.4.241 reverse_alias 147
10116 7.4.242 reverse_name 147
10117 7.4.243 reverse_realname 147
10118 7.4.244 rfc2047_parameters 148
10119 7.4.245 save_address 148
10120 7.4.246 save_empty 148
10121 7.4.247 save_name 148
10123 7.4.249 score_threshold_delete 149
10124 7.4.250 score_threshold_flag 149
10125 7.4.251 score_threshold_read 149
10126 7.4.252 send_charset 149
10127 7.4.253 sendmail 150
10128 7.4.254 sendmail_wait 150
10130 7.4.256 sidebar_boundary 151
10131 7.4.257 sidebar_delim 151
10132 7.4.258 sidebar_newmail_only 151
10133 7.4.259 sidebar_number_format 151
10134 7.4.260 sidebar_shorten_hierarchy 152
10135 7.4.261 sidebar_visible 152
10136 7.4.262 sidebar_width 152
10137 7.4.263 sig_dashes 152
10138 7.4.264 sig_on_top 153
10139 7.4.265 signature 153
10143 7.4.266 signoff_string 153
10144 7.4.267 simple_search 153
10145 7.4.268 sleep_time 154
10146 7.4.269 smart_wrap 154
10147 7.4.270 smileys 154
10148 7.4.271 smime_ask_cert_label 154
10149 7.4.272 smime_ca_location 154
10150 7.4.273 smime_certificates 154
10151 7.4.274 smime_decrypt_command 155
10152 7.4.275 smime_decrypt_use_default_key 155
10153 7.4.276 smime_default_key 156
10154 7.4.277 smime_encrypt_command 156
10155 7.4.278 smime_encrypt_with 156
10156 7.4.279 smime_get_cert_command 156
10157 7.4.280 smime_get_cert_email_command 156
10158 7.4.281 smime_get_signer_cert_command 156
10159 7.4.282 smime_import_cert_command 157
10160 7.4.283 smime_is_default 157
10161 7.4.284 smime_keys 157
10162 7.4.285 smime_pk7out_command 157
10163 7.4.286 smime_sign_command 158
10164 7.4.287 smime_sign_opaque_command 158
10165 7.4.288 smime_timeout 158
10166 7.4.289 smime_verify_command 158
10167 7.4.290 smime_verify_opaque_command 158
10168 7.4.291 smtp_envelope 158
10169 7.4.292 smtp_host 159
10170 7.4.293 smtp_pass 159
10171 7.4.294 smtp_port 159
10172 7.4.295 smtp_use_tls 159
10173 7.4.296 smtp_user 160
10175 7.4.298 sort_alias 160
10176 7.4.299 sort_aux 161
10177 7.4.300 sort_browser 161
10178 7.4.301 sort_re 161
10179 7.4.302 spam_separator 162
10180 7.4.303 spoolfile 162
10181 7.4.304 ssl_ca_certificates_file 162
10182 7.4.305 ssl_client_cert 162
10183 7.4.306 ssl_force_tls 163
10184 7.4.307 ssl_min_dh_prime_bits 163
10185 7.4.308 ssl_starttls 163
10186 7.4.309 ssl_use_sslv2 163
10187 7.4.310 ssl_use_sslv3 163
10188 7.4.311 ssl_use_tlsv1 164
10189 7.4.312 ssl_usesystemcerts 164
10190 7.4.313 status_chars 164
10191 7.4.314 status_format 164
10192 7.4.315 status_on_top 167
10193 7.4.316 strict_mailto 167
10194 7.4.317 strict_mime 167
10195 7.4.318 strict_threads 167
10199 7.4.319 strip_was 167
10200 7.4.320 strip_was_regex 168
10201 7.4.321 stuff_quoted 168
10202 7.4.322 suspend 168
10203 7.4.323 text_flowed 168
10204 7.4.324 thorough_search 168
10205 7.4.325 thread_received 169
10207 7.4.327 timeout 169
10209 7.4.329 to_chars 169
10213 7.4.333 uncollapse_jump 170
10214 7.4.334 use_8bitmime 171
10215 7.4.335 use_domain 171
10216 7.4.336 use_from 171
10217 7.4.337 use_idn 171
10218 7.4.338 use_ipv6 171
10220 7.4.340 wait_key 172
10222 7.4.342 wrap_search 172
10223 7.4.343 wrapmargin 172
10224 7.4.344 write_bcc 173
10225 7.4.345 write_inc 173
10226 7.4.346 xterm_icon 173
10227 7.4.347 xterm_leave 173
10228 7.4.348 xterm_set_titles 173
10229 7.4.349 xterm_title 174
10230 7.5 Functions ....................................................... 174
10243 8. Miscellany ............................................................ 182
10244 8.1 Acknowledgments ................................................. 183
10245 8.2 About this document ............................................. 185