2 T
\bTh
\bhe
\be M
\bMu
\but
\btt
\bt N
\bNe
\bex
\bxt
\bt G
\bGe
\ben
\bne
\ber
\bra
\bat
\bti
\bio
\bon
\bn E
\bE-
\b-M
\bMa
\bai
\bil
\bl C
\bCl
\bli
\bie
\ben
\bnt
\bt
4 by Andreas Krennmair <ak@synflood.at> and others
5 originally based on _
\bm_
\bu_
\bt_
\bt by Michael Elkins <me@cs.hmc.edu> and others
9 A
\bAb
\bbs
\bst
\btr
\bra
\bac
\bct
\bt
11 Michael Elinks on mutt, circa 1995: ``All mail clients suck. This one just
12 sucks less.'' - Sven Guckes on mutt, ca. 2003: ``But it still sucks!''
14 _
\b1_
\b. _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
16 _
\b1_
\b._
\b1 _
\bO_
\bv_
\be_
\br_
\bv_
\bi_
\be_
\bw
18 M
\bMu
\but
\btt
\bt-
\b-n
\bng
\bg is a small but very powerful text-based MIME mail client. Mutt-ng is
19 highly configurable, and is well suited to the mail power user with advanced
20 features like key bindings, keyboard macros, mail threading, regular expression
21 searches and a powerful pattern matching language for selecting groups of mes-
24 This documentation additionally contains documentation to M
\bMu
\but
\btt
\bt-
\b-N
\bNG
\bG, a fork from
25 Mutt with the goal to fix all the little annoyances of Mutt, to integrate all
26 the Mutt patches that are floating around in the web, and to add other new fea-
27 tures. Features specific to Mutt-ng will be discussed in an extra section.
28 Don't be confused when most of the documentation talk about Mutt and not Mutt-
29 ng, Mutt-ng contains all Mutt features, plus many more.
31 _
\b1_
\b._
\b2 _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bH_
\bo_
\bm_
\be _
\bP_
\ba_
\bg_
\be
35 _
\b1_
\b._
\b3 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
37 +
\bo mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user support
40 The Mutt Next Generation E-Mail Client 1
42 The Mutt Next Generation E-Mail Client 2
44 +
\bo mutt-ng-devel@lists.berlios.de -- The development mailing list for mutt-ng
46 _
\b1_
\b._
\b4 _
\bS_
\bo_
\bf_
\bt_
\bw_
\ba_
\br_
\be _
\bD_
\bi_
\bs_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn _
\bS_
\bi_
\bt_
\be_
\bs
48 So far, there are no official releases of Mutt-ng, but you can download daily
49 snapshots from http://mutt-ng.berlios.de/snapshots/
51 _
\b1_
\b._
\b5 _
\bI_
\bR_
\bC
53 Visit channel _
\b#_
\bm_
\bu_
\bt_
\bt_
\bn_
\bg on irc.freenode.net (www.freenode.net) to chat with other
54 people interested in Mutt-ng.
56 _
\b1_
\b._
\b6 _
\bW_
\be_
\bb_
\bl_
\bo_
\bg
58 If you want to read fresh news about the latest development in Mutt-ng, and get
59 informed about stuff like interesting, Mutt-ng-related articles and packages
60 for your favorite distribution, you can read and/or subscribe to our Mutt-ng
63 _
\b1_
\b._
\b7 _
\bC_
\bo_
\bp_
\by_
\br_
\bi_
\bg_
\bh_
\bt
65 Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and others
67 This program is free software; you can redistribute it and/or modify it under
68 the terms of the GNU General Public License as published by the Free Software
69 Foundation; either version 2 of the License, or (at your option) any later ver-
72 This program is distributed in the hope that it will be useful, but WITHOUT ANY
73 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
74 PARTICULAR PURPOSE. See the GNU General Public License for more details.
76 You should have received a copy of the GNU General Public License along with
77 this program; if not, write to the Free Software Foundation, Inc., 59 Temple
78 Place - Suite 330, Boston, MA 02111, USA.
80 _
\b2_
\b. _
\bG_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bS_
\bt_
\ba_
\br_
\bt_
\be_
\bd
82 _
\b2_
\b._
\b1 _
\bB_
\ba_
\bs_
\bi_
\bc _
\bC_
\bo_
\bn_
\bc_
\be_
\bp_
\bt_
\bs
84 The Mutt Next Generation E-Mail Client 3
86 _
\b2_
\b._
\b1_
\b._
\b1 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
88 mutt-ng offers different screens of which every has its special purpose:
90 +
\bo The _
\bi_
\bn_
\bd_
\be_
\bx displays the contents of the currently opened mailbox.
92 +
\bo The _
\bp_
\ba_
\bg_
\be_
\br is responsible for displaying messages, that is, the header, the
93 body and all attached parts.
95 +
\bo The _
\bf_
\bi_
\bl_
\be _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br offers operations on and displays information of all
96 folders mutt-ng should watch for mail.
98 +
\bo The _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br offers a permanent view of which mailboxes contain how many
99 total, new and/or flagged mails.
101 +
\bo The _
\bh_
\be_
\bl_
\bp _
\bs_
\bc_
\br_
\be_
\be_
\bn lists for all currently available commands how to invoke
102 them as well as a short description.
104 +
\bo The _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu is a comfortable interface take last actions before send-
105 ing mail: change subjects, attach files, remove attachements, etc.
107 +
\bo The _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\be_
\bm_
\be_
\bn_
\bt menu gives a summary and the tree structure of the
108 attachements of the current message.
110 +
\bo The _
\ba_
\bl_
\bi_
\ba_
\bs menu lists all or a fraction of the aliases a user has defined.
112 +
\bo The _
\bk_
\be_
\by menu used in connection with encryption lets users choose the
113 right key to encrypt with.
115 When mutt-ng is started without any further options, it'll open the users
116 default mailbox and display the index.
118 _
\b2_
\b._
\b1_
\b._
\b2 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
120 Mutt-ng does _
\bn_
\bo_
\bt feature an internal configuration interface or menu due to the
121 simple fact that this would be too complex to handle (currently there are sev-
122 eral _
\bh_
\bu_
\bn_
\bd_
\br_
\be_
\bd variables which fine-tune the behaviour.)
124 Mutt-ng is configured using configuration files which allow users to add com-
125 ments or manage them via version control systems to ease maintenance.
127 Also, mutt-ng comes with a shell script named grml-muttng kindly contributed by
128 users which really helps and eases the creation of a user's configuration file.
129 When downloading the source code via a snapshot or via subversion, it can be
130 found in the contrib directory.
132 _
\b2_
\b._
\b1_
\b._
\b3 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
134 Mutt-ng offers great flexibility due to the use of functions: internally, every
135 action a user can make mutt-ng perform is named ``function.'' Those functions
137 The Mutt Next Generation E-Mail Client 4
139 are assigned to keys (or even key sequences) and may be completely adjusted to
140 user's needs. The basic idea is that the impatient users get a very intuitive
141 interface to start off with and advanced users virtually get no limits to
144 _
\b2_
\b._
\b1_
\b._
\b4 _
\bI_
\bn_
\bt_
\be_
\br_
\ba_
\bc_
\bt_
\bi_
\bo_
\bn
146 Mutt-ng has two basic concepts of user interaction:
148 1. There is one dedicated line on the screen used to query the user for
149 input, issue any command, query variables and display error and informa-
150 tional messages. As for every type of user input, this requires manual
151 action leading to the need of input.
153 2. The automatized interface for interaction are the so called _
\bh_
\bo_
\bo_
\bk_
\bs. Hooks
154 specify actions the user wants to be performed at well-defined situa-
155 tions: what to do when entering which folder, what to do when displaying
156 or replying to what kind of message, etc. These are optional, i.e. a user
157 doesn't need to specify them but can do so.
159 _
\b2_
\b._
\b1_
\b._
\b5 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
161 Although mutt-ng has many functionality built-in, many features can be dele-
162 gated to external tools to increase flexibility: users can define programs to
163 filter a message through before displaying, users can use any program they want
164 for displaying a message, message types (such as PDF or PostScript) for which
165 mutt-ng doesn't have a built-in filter can be rendered by arbitrary tools and
166 so forth. Although mutt-ng has an alias mechanism built-in, it features using
167 external tools to query for nearly every type of addresses from sources like
168 LDAP, databases or just the list of locally known users.
170 _
\b2_
\b._
\b1_
\b._
\b6 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
172 Mutt-ng has a built-in pattern matching ``language'' which is as widely used as
173 possible to present a consistent interface to users. The same ``pattern terms''
174 can be used for searching, scoring, message selection and much more.
176 _
\b2_
\b._
\b2 _
\bS_
\bc_
\br_
\be_
\be_
\bn_
\bs _
\ba_
\bn_
\bd _
\bM_
\be_
\bn_
\bu_
\bs
178 _
\b2_
\b._
\b2_
\b._
\b1 _
\bI_
\bn_
\bd_
\be_
\bx
180 The index is the screen that you usually see first when you start mutt-ng. It
181 gives an overview over your emails in the currently opened mailbox. By default,
182 this is your system mailbox. The information you see in the index is a list of
184 The Mutt Next Generation E-Mail Client 5
186 emails, each with its number on the left, its flags (new email, important
187 email, email that has been forwarded or replied to, tagged email, ...), the
188 date when email was sent, its sender, the email size, and the subject. Addi-
189 tionally, the index also shows thread hierarchies: when you reply to an email,
190 and the other person replies back, you can see the other's person email in a
191 "sub-tree" below. This is especially useful for personal email between a group
192 of people or when you've subscribed to mailing lists.
194 _
\b2_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bg_
\be_
\br
196 The pager is responsible for showing the email content. On the top of the pager
197 you have an overview over the most important email headers like the sender, the
198 recipient, the subject, and much more information. How much information you
199 actually see depends on your configuration, which we'll describe below.
201 Below the headers, you see the email body which usually contains the message.
202 If the email contains any attachments, you will see more information about them
203 below the email body, or, if the attachments are text files, you can view them
204 directly in the pager.
206 To give the user a good overview, it is possible to configure mutt-ng to show
207 different things in the pager with different colors. Virtually everything that
208 can be described with a regular expression can be colored, e.g. URLs, email
209 addresses or smileys.
211 _
\b2_
\b._
\b2_
\b._
\b3 _
\bF_
\bi_
\bl_
\be _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
213 The file browser is the interface to the local or remote file system. When
214 selecting a mailbox to open, the browser allows custom sorting of items, limit-
215 ing the items shown by a regular expression and a freely adjustable format of
216 what to display in which way. It also allows for easy navigation through the
217 file system when selecting file(s) to attach to a message, select multiple
218 files to attach and many more.
220 _
\b2_
\b._
\b2_
\b._
\b4 _
\bS_
\bi_
\bd_
\be_
\bb_
\ba_
\br
222 The sidebar comes in handy to manage mails which are spread over different
223 folders. All folders users setup mutt-ng to watch for new mail will be listed.
224 The listing includes not only the name but also the number of total messages,
225 the number of new and flagged messages. Items with new mail may be colored dif-
226 ferent from those with flagged mail, items may be shortened or compress if
227 they're they to long to be printed in full form so that by abbreviated names,
228 user still now what the name stands for.
230 _
\b2_
\b._
\b2_
\b._
\b5 _
\bH_
\be_
\bl_
\bp
232 The Mutt Next Generation E-Mail Client 6
234 The help screen is meant to offer a quick help to the user. It lists the cur-
235 rent configuration of key bindings and their associated commands including a
236 short description, and currently unbound functions that still need to be asso-
237 ciated with a key binding (or alternatively, they can be called via the mutt-ng
240 _
\b2_
\b._
\b2_
\b._
\b6 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
242 The compose menu features a split screen containing the information which
243 really matter before actually sending a message by mail or posting an article
244 to a newsgroup: who gets the message as what (recipient, newsgroup, who gets
245 what kind of copy). Additionally, users may set security options like deciding
246 whether to sign, encrypt or sign and encrypt a message with/for what keys.
248 Also, it's used to attach messages, news articles or files to a message, to re-
249 edit any attachment including the message itself.
251 _
\b2_
\b._
\b2_
\b._
\b7 _
\bA_
\bl_
\bi_
\ba_
\bs _
\bM_
\be_
\bn_
\bu
253 The alias menu is used to help users finding the recipients of messages. For
254 users who need to contact many people, there's no need to remember addresses or
255 names completely because it allows for searching, too. The alias mechanism and
256 thus the alias menu also features grouping several addresses by a shorter nick-
257 name, the actual alias, so that users don't have to select each single recipi-
260 _
\b2_
\b._
\b2_
\b._
\b8 _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
262 As will be later discussed in detail, mutt-ng features a good and stable MIME
263 implementation, that is, is greatly supports sending and receiving messages of
264 arbitrary type. The attachment menu displays a message's structure in detail:
265 what content parts are attached to which parent part (which gives a true tree
266 structure), which type is of what type and what size. Single parts may saved,
267 deleted or modified to offer great and easy access to message's internals.
269 _
\b2_
\b._
\b2_
\b._
\b9 _
\bK_
\be_
\by _
\bM_
\be_
\bn_
\bu
273 _
\b2_
\b._
\b3 _
\bM_
\bo_
\bv_
\bi_
\bn_
\bg _
\bA_
\br_
\bo_
\bu_
\bn_
\bd _
\bi_
\bn _
\bM_
\be_
\bn_
\bu_
\bs
275 Information is presented in menus, very similar to ELM. Here is a table
277 The Mutt Next Generation E-Mail Client 7
279 showing the common keys used to navigate menus in Mutt-ng.
281 j or Down next-entry move to the next entry
282 k or Up previous-entry move to the previous entry
283 z or PageDn page-down go to the next page
284 Z or PageUp page-up go to the previous page
285 = or Home first-entry jump to the first entry
286 * or End last-entry jump to the last entry
287 q quit exit the current menu
288 ? help list all key bindings for the current menu
290 _
\b2_
\b._
\b4 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bI_
\bn_
\bp_
\bu_
\bt _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
292 Mutt-ng has a builtin line editor which is used as the primary way to input
293 textual data such as email addresses or filenames. The keys used to move
294 around while editing are very similar to those of Emacs.
296 ^A or <Home> bol move to the start of the line
297 ^B or <Left> backward-char move back one char
298 Esc B backward-word move back one word
299 ^D or <Delete> delete-char delete the char under the cursor
300 ^E or <End> eol move to the end of the line
301 ^F or <Right> forward-char move forward one char
302 Esc F forward-word move forward one word
303 <Tab> complete complete filename or alias
304 ^T complete-query complete address with query
305 ^K kill-eol delete to the end of the line
306 ESC d kill-eow delete to the end of the word
307 ^W kill-word kill the word in front of the cursor
308 ^U kill-line delete entire line
309 ^V quote-char quote the next typed key
310 <Up> history-up recall previous string from history
311 <Down> history-down recall next string from history
312 <BackSpace> backspace kill the char in front of the cursor
313 Esc u upcase-word convert word to upper case
314 Esc l downcase-word convert word to lower case
315 Esc c capitalize-word capitalize the word
317 <Return> n/a finish editing
319 You can remap the _
\be_
\bd_
\bi_
\bt_
\bo_
\br functions using the _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) com-
320 mand. For example, to make the _
\bD_
\be_
\bl_
\be_
\bt_
\be key delete the character in front of the
321 cursor rather than under, you could use
323 bind editor <delete> backspace
325 The Mutt Next Generation E-Mail Client 8
327 _
\b2_
\b._
\b5 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl _
\b- _
\bT_
\bh_
\be _
\bI_
\bn_
\bd_
\be_
\bx _
\ba_
\bn_
\bd _
\bP_
\ba_
\bg_
\be_
\br
329 Similar to many other mail clients, there are two modes in which mail is read
330 in Mutt-ng. The first is the index of messages in the mailbox, which is called
331 the ``index'' in Mutt-ng. The second mode is the display of the message con-
332 tents. This is called the ``pager.''
334 The next few sections describe the functions provided in each of these modes.
336 _
\b2_
\b._
\b5_
\b._
\b1 _
\bT_
\bh_
\be _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bI_
\bn_
\bd_
\be_
\bx
338 c change to a different mailbox
339 ESC c change to a folder in read-only mode
340 C copy the current message to another mailbox
341 ESC C decode a message and copy it to a folder
342 ESC s decode a message and save it to a folder
343 D delete messages matching a pattern
344 d delete the current message
346 l show messages matching a pattern
347 N mark message as new
348 o change the current sort method
349 O reverse sort the mailbox
350 q save changes and exit
352 T tag messages matching a pattern
353 t toggle the tag on a message
354 ESC t toggle tag on entire message thread
355 U undelete messages matching a pattern
358 x abort changes and exit
359 <Return> display-message
360 <Tab> jump to the next new message
361 @ show the author's full e-mail address
362 $ save changes to mailbox
365 ^L clear and redraw the screen
366 ^T untag messages matching a pattern
368 _
\b2_
\b._
\b5_
\b._
\b1_
\b._
\b1 _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs _
\bF_
\bl_
\ba_
\bg_
\bs
370 In addition to who sent the message and the subject, a short summary of the
371 disposition of each message is printed beside the message number. Zero or more
372 of the following ``flags'' may appear, which mean:
375 message is deleted (is marked for deletion)
378 message have attachments marked for deletion
380 The Mutt Next Generation E-Mail Client 9
383 contains a PGP public key
392 message is PGP encrypted
395 message has been replied to
398 message is signed, and the signature is succesfully verified
409 Some of the status flags can be turned on or off using
411 +
\bo s
\bse
\bet
\bt-
\b-f
\bfl
\bla
\bag
\bg (default: w)
413 +
\bo c
\bcl
\ble
\bea
\bar
\br-
\b-f
\bfl
\bla
\bag
\bg (default: W)
415 Furthermore, the following flags reflect who the message is addressed to. They
416 can be customized with the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.325 , page 165) variable.
419 message is to you and you only
422 message is to you, but also to or cc'ed to others
425 message is cc'ed to you
431 message is sent to a subscribed mailing list
433 _
\b2_
\b._
\b5_
\b._
\b2 _
\bT_
\bh_
\be _
\bP_
\ba_
\bg_
\be_
\br
435 By default, Mutt-ng uses its builtin pager to display the body of messages.
437 The Mutt Next Generation E-Mail Client 10
439 The pager is very similar to the Unix program _
\bl_
\be_
\bs_
\bs though not nearly as fea-
442 <Return> go down one line
443 <Space> display the next page (or next message if at the end of a message)
444 - go back to the previous page
445 n search for next match
446 S skip beyond quoted text
447 T toggle display of quoted text
449 / search for a regular expression (pattern)
450 ESC / search backwards for a regular expression
451 \ toggle search pattern coloring
452 ^ jump to the top of the message
454 In addition, many of the functions from the _
\bi_
\bn_
\bd_
\be_
\bx are available in the pager,
455 such as _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be or _
\bc_
\bo_
\bp_
\by_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be (this is one advantage over using an
456 external pager to view messages).
458 Also, the internal pager supports a couple other advanced features. For one, it
459 will accept and translate the ``standard'' nroff sequences for bold and under-
460 line. These sequences are a series of either the letter, backspace (^H), the
461 letter again for bold or the letter, backspace, ``_'' for denoting underline.
462 Mutt-ng will attempt to display these in bold and underline respectively if
463 your terminal supports them. If not, you can use the bold and underline _
\bc_
\bo_
\bl_
\bo_
\br
464 (section 3.8 , page 27) objects to specify a color or mono attribute for them.
466 Additionally, the internal pager supports the ANSI escape sequences for charac-
467 ter attributes. Mutt-ng translates them into the correct color and character
468 settings. The sequences Mutt-ng supports are:
470 ESC [ Ps;Ps;Ps;...;Ps m
477 3x Foreground color is x
478 4x Background color is x
490 The Mutt Next Generation E-Mail Client 11
492 Mutt-ng uses these attributes for handling text/enriched messages, and they can
493 also be used by an external _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) script for high-
494 lighting purposes. N
\bNo
\bot
\bte
\be:
\b: If you change the colors for your display, for exam-
495 ple by changing the color associated with color2 for your xterm, then that
496 color will be used instead of green.
498 _
\b2_
\b._
\b5_
\b._
\b3 _
\bT_
\bh_
\br_
\be_
\ba_
\bd_
\be_
\bd _
\bM_
\bo_
\bd_
\be
500 When the mailbox is _
\bs_
\bo_
\br_
\bt_
\be_
\bd (section 7.4.293 , page 156) 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.111 , page 111). For example, you could use "%?M?(#%03M)&(%4l)?" in
522 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111) to optionally display the number of
523 hidden messages if the thread is collapsed.
525 See also: _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 7.4.314 , page 163).
527 _
\b2_
\b._
\b5_
\b._
\b4 _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\be_
\bo_
\bu_
\bs _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
529 c
\bcr
\bre
\bea
\bat
\bte
\be-
\b-a
\bal
\bli
\bia
\bas
\bs
532 Creates a new alias based upon the current message (or prompts for a new one).
533 Once editing is complete, an _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.3 , page 23) command is added to
534 the file specified by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.3 , page 86) variable for
535 future use. N
\bNo
\bot
\bte
\be:
\b: Specifying an _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.3 , page 86) does not
536 add the aliases specified there-in, you must also _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page
539 c
\bch
\bhe
\bec
\bck
\bk-
\b-t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl-
\b-p
\bpg
\bgp
\bp
542 This function will search the current message for content signed or encrypted
543 with PGP the "traditional" way, that is, without proper MIME tagging.
545 The Mutt Next Generation E-Mail Client 12
547 Technically, this function will temporarily change the MIME content types of
548 the body parts containing PGP data; this is similar to the _
\be_
\bd_
\bi_
\bt_
\b-_
\bt_
\by_
\bp_
\be (section
549 2.5.4 , page 12) function's effect.
551 d
\bdi
\bis
\bsp
\bpl
\bla
\bay
\by-
\b-t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-w
\bwe
\bee
\bed
\bd
554 Toggles the weeding of message header fields specified by _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section
555 3.9 , page 30) commands.
560 This command (available in the ``index'' and ``pager'') allows you to edit the
561 raw current message as it's present in the mail folder. After you have fin-
562 ished editing, the changed message will be appended to the current folder, and
563 the original message will be marked for deletion.
565 e
\bed
\bdi
\bit
\bt-
\b-t
\bty
\byp
\bpe
\be
567 (default: ^E on the attachment menu, and in the pager and index menus; ^T on
570 This command is used to temporarily edit an attachment's content type to fix,
571 for instance, bogus character set parameters. When invoked from the index or
572 from the pager, you'll have the opportunity to edit the top-level attachment's
573 content type. On the _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bm_
\be_
\bn_
\bu (section 5.1.2 , page 68), you can
574 change any attachment's content type. These changes are not persistent, and get
575 lost upon changing folders.
577 Note that this command is also available on the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bm_
\be_
\bn_
\bu (section 5.1.3 ,
578 page 68). There, it's used to fine-tune the properties of attachments you are
581 e
\ben
\bnt
\bte
\ber
\br-
\b-c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
584 This command is used to execute any command you would normally put in a config-
585 uration file. A common use is to check the settings of variables, or in con-
586 junction with _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.7 , page 27) to change settings on the fly.
588 e
\bex
\bxt
\btr
\bra
\bac
\bct
\bt-
\b-k
\bke
\bey
\bys
\bs
591 This command extracts PGP public keys from the current or tagged message(s) and
592 adds them to your PGP public key ring.
594 f
\bfo
\bor
\brg
\bge
\bet
\bt-
\b-p
\bpa
\bas
\bss
\bsp
\bph
\bhr
\bra
\bas
\bse
\be
597 This command wipes the passphrase(s) from memory. It is useful, if you mis-
598 spelled the passphrase.
600 The Mutt Next Generation E-Mail Client 13
602 l
\bli
\bis
\bst
\bt-
\b-r
\bre
\bep
\bpl
\bly
\by
605 Reply to the current or tagged message(s) by extracting any addresses which
606 match the regular expressions given by the _
\bl_
\bi_
\bs_
\bt_
\bs _
\bo_
\br _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 ,
607 page 33) 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.89 , page 106) configuration variable is set.
609 Using this when replying to messages posted to mailing lists helps avoid dupli-
610 cate copies being sent to the author of the message you are replying to.
612 p
\bpi
\bip
\bpe
\be-
\b-m
\bme
\bes
\bss
\bsa
\bag
\bge
\be
615 Asks for an external Unix command and pipes the current or tagged message(s) to
616 it. The variables _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.202 , page 135), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 7.4.204 , page 135), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 7.4.203 , page 135) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.337 , page 168) 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.338 , page 168) variable.
630 This function is also available from the attachment menu. You can use this to
631 easily resend a message which was included with a bounce message as a mes-
632 sage/rfc822 body part.
634 s
\bsh
\bhe
\bel
\bll
\bl-
\b-e
\bes
\bsc
\bca
\bap
\bpe
\be
637 Asks for an external Unix command and executes it. The _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section
638 7.4.337 , page 168) 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.227 , page 140) variable to
646 detect quoted text when displaying the body of the message. This function tog-
647 gles the display of the quoted material in the message. It is particularly
648 useful when are interested in just the response and there is a large amount of
649 quoted text in the way.
651 s
\bsk
\bki
\bip
\bp-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd
654 This function will go to the next line of non-quoted text which come after a
655 line of quoted text in the internal pager.
657 The Mutt Next Generation E-Mail Client 14
659 _
\b2_
\b._
\b6 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
661 The following bindings are available in the _
\bi_
\bn_
\bd_
\be_
\bx for sending messages.
663 m compose compose a new message
664 r reply reply to sender
665 g group-reply reply to all recipients
666 L list-reply reply to mailing list address
667 f forward forward message
668 b bounce bounce (remail) message
669 ESC k mail-key mail a PGP public key to someone
671 Bouncing a message sends the message as is to the recipient you specify. For-
672 warding a message allows you to add comments or modify the message you are for-
673 warding. These items are discussed in greater detail in the next chapter
674 _
\b`_
\b`_
\bF_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bd _
\bB_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\b'_
\b' (section 2.7 , page 20).
676 _
\b2_
\b._
\b6_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg _
\bn_
\be_
\bw _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
678 When you want to send an email using mutt-ng, simply press m on your keyboard.
679 Then, mutt-ng asks for the recipient via a prompt in the last line:
683 After you've finished entering the recipient(s), press return. If you want to
684 send an email to more than one recipient, separate the email addresses using
685 the comma ",". Mutt-ng then asks you for the email subject. Again, press return
686 after you've entered it. After that, mutt-ng got the most important information
687 from you, and starts up an editor where you can then enter your email.
689 The editor that is called is selected in the following way: you can e.g. set it
690 in the mutt-ng configuration:
692 set editor = "vim +/^$/ -c ':set tw=72'"
696 If you don't set your preferred editor in your configuration, mutt-ng first
697 looks whether the environment variable $VISUAL is set, and if so, it takes its
698 value as editor command. Otherwise, it has a look at $EDITOR and takes its
699 value if it is set. If no editor command can be found, mutt-ng simply assumes
700 vi to be the default editor, since it's the most widespread editor in the Unix
701 world and it's pretty safe to assume that it is installed and available.
703 When you've finished entering your message, save it and quit your editor. Mutt-
704 ng will then present you with a summary screen, the compose menu. On the top,
705 you see a summary of the most important available key commands. Below that,
706 you see the sender, the recipient(s), Cc and/or Bcc recipient(s), the subject,
708 The Mutt Next Generation E-Mail Client 15
710 the reply-to address, and optionally information where the sent email will be
711 stored and whether it should be digitally signed and/or encrypted.
713 Below that, you see a list of "attachments". The mail you've just entered
714 before is also an attachment, but due to its special type (it's plain text), it
715 will be displayed as the normal message on the receiver's side.
717 At this point, you can add more attachments, pressing a, you can edit the
718 recipient addresses, pressing t for the "To:" field, c for the "Cc:" field, and
719 b for the "Bcc: field. You can also edit the subject the subject by simply
720 pressing s or the email message that you've entered before by pressing e. You
721 will then again return to the editor. You can even edit the sender, by pressing
722 <esc>f, but this shall only be used with caution.
724 Alternatively, you can configure mutt-ng in a way that most of the above set-
725 tings can be edited using the editor. Therefore, you only need to add the fol-
726 lowing to your configuration:
730 Once you have finished editing the body of your mail message, you are returned
731 to the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu. The following options are available:
733 a attach-file attach a file
734 A attach-message attach message(s) to the message
735 ESC k attach-key attach a PGP public key
736 d edit-description edit description on attachment
737 D detach-file detach a file
738 t edit-to edit the To field
739 ESC f edit-from edit the From field
740 r edit-reply-to edit the Reply-To field
741 c edit-cc edit the Cc field
742 b edit-bcc edit the Bcc field
743 y send-message send the message
744 s edit-subject edit the Subject
745 S smime-menu select S/MIME options
746 f edit-fcc specify an ``Fcc'' mailbox
747 p pgp-menu select PGP options
748 P postpone-message postpone this message until later
749 q quit quit (abort) sending the message
750 w write-fcc write the message to a folder
751 i ispell check spelling (if available on your system)
752 ^F forget-passphrase wipe passphrase(s) from memory
754 N
\bNo
\bot
\bte
\be:
\b: The attach-message function will prompt you for a folder to attach mes-
755 sages from. You can now tag messages in that folder and they will be attached
756 to the message you are sending. Note that certain operations like composing a
757 new mail, replying, forwarding, etc. are not permitted when you are in that
758 folder. The %r in _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.310 , page 160) will change to a
759 'A' to indicate that you are in attach-message mode.
761 The Mutt Next Generation E-Mail Client 16
763 _
\b2_
\b._
\b6_
\b._
\b2 _
\bR_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg
765 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b1 _
\bS_
\bi_
\bm_
\bp_
\bl_
\be _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
767 When you want to reply to an email message, select it in the index menu and
768 then press r. Mutt-ng's behaviour is then similar to the behaviour when you
769 compose a message: first, you will be asked for the recipient, then for the
770 subject, and then, mutt-ng will start the editor with the quote attribution and
771 the quoted message. This can e.g. look like the example below.
773 On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote:
774 > Bill, can you please send last month's progress report to Mr.
775 > Morgan? We also urgently need the cost estimation for the new
776 > production server that we want to set up before our customer's
777 > project will go live.
779 You can start editing the email message. It is strongly recommended to put your
780 answer _
\bb_
\be_
\bl_
\bo_
\bw the quoted text and to only quote what is really necessary and
781 that you refer to. Putting your answer on top of the quoted message, is,
782 although very widespread, very often not considered to be a polite way to
785 The quote attribution is configurable, by default it is set to
787 set attribution = "On %d, %n wrote:"
789 It can also be set to something more compact, e.g.
791 set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"
793 The example above results in the following attribution:
795 * Michael Svensson <svensson@foobar.com> [05-03-06 17:02]:
796 > Bill, can you please send last month's progress report to Mr.
797 > Morgan? We also urgently need the cost estimation for the new
798 > production server that we want to set up before our customer's
799 > project will go live.
801 Generally, try to keep your attribution short yet information-rich. It is _
\bn_
\bo_
\bt
802 the right place for witty quotes, long "attribution" novels or anything like
803 that: the right place for such things is - if at all - the email signature at
804 the very bottom of the message.
806 When you're done with writing your message, save and quit the editor. As
807 before, you will return to the compose menu, which is used in the same way as
809 The Mutt Next Generation E-Mail Client 17
813 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b2 _
\bG_
\br_
\bo_
\bu_
\bp _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
815 In the situation where a group of people uses email as a discussion, most of
816 the emails will have one or more recipients, and probably several "Cc:" recipi-
817 ents. The group reply functionality ensures that when you press g instead of r
818 to do a reply, each and every recipient that is contained in the original mes-
819 sage will receive a copy of the message, either as normal recipient or as "Cc:"
822 _
\b2_
\b._
\b6_
\b._
\b2_
\b._
\b3 _
\bL_
\bi_
\bs_
\bt _
\bR_
\be_
\bp_
\bl_
\bi_
\be_
\bs
824 When you use mailing lists, it's generally better to send your reply to a mes-
825 sage only to the list instead of the list and the original author. To make this
826 easy to use, mutt-ng features list replies.
828 To do a list reply, simply press L. If the email contains a Mail-Followup-To:
829 header, its value will be used as reply address. Otherwise, mutt-ng searches
830 through all mail addresses in the original message and tries to match them a
831 list of regular expressions which can be specified using the lists command. If
832 any of the regular expression matches, a mailing list address has been found,
833 and it will be used as reply address.
835 lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@
837 Nowadays, most mailing list software like GNU Mailman adds a Mail-Followup-To:
838 header to their emails anyway, so setting lists is hardly ever necessary in
841 _
\b2_
\b._
\b6_
\b._
\b3 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br
843 When editing the header of your outgoing message, there are a couple of special
848 Fcc: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
850 Mutt-ng will pick up _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be just as if you had used the _
\be_
\bd_
\bi_
\bt_
\b-_
\bf_
\bc_
\bc function in
851 the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu.
853 You can also attach files to your message by specifying
855 The Mutt Next Generation E-Mail Client 18
857 Attach: _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
859 where _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is the file to attach and _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn is an optional string to
860 use as the description of the attached file.
862 When replying to messages, if you remove the _
\bI_
\bn_
\b-_
\bR_
\be_
\bp_
\bl_
\by_
\b-_
\bT_
\bo_
\b: field from the header
863 field, Mutt-ng will not generate a _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be_
\bs_
\b: field, which allows you to cre-
864 ate a new message thread.
866 Also see _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98).
868 _
\b2_
\b._
\b6_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg _
\bw_
\bi_
\bt_
\bh _
\bP_
\bG_
\bP
870 If you want to use PGP, you can specify
872 Pgp: [ E | S | S_
\b<_
\bi_
\bd_
\b> ]
874 ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting
875 _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.194 , page 133) permanently.
877 If you have told mutt to PGP encrypt a message, it will guide you through a key
878 selection process when you try to send the message. Mutt-ng will not ask you
879 any questions about keys which have a certified user ID matching one of the
880 message recipients' mail addresses. However, there may be situations in which
881 there are several keys, weakly certified user ID fields, or where no matching
884 In these cases, you are dropped into a menu with a list of keys from which you
885 can select one. When you quit this menu, or mutt can't find any matching keys,
886 you are prompted for a user ID. You can, as usually, abort this prompt using
887 ^G. When you do so, mutt will return to the compose screen.
889 Once you have successfully finished the key selection, the message will be
890 encrypted using the selected public keys, and sent out.
892 Most fields of the entries in the key selection menu (see also _
\b$_
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\b-
893 _
\bm_
\ba_
\bt (section 7.4.181 , page 130)) have obvious meanings. But some explana-
894 tions on the capabilities, flags, and validity fields are in order.
896 The flags sequence (%f) will expand to one of the following flags:
898 R The key has been revoked and can't be used.
899 X The key is expired and can't be used.
900 d You have marked the key as disabled.
901 c There are unknown critical self-signature
904 The capabilities field (%c) expands to a two-character sequence representing a
905 key's capabilities. The first character gives the key's encryption capabili-
906 ties: A minus sign (-
\b-) means that the key cannot be used for encryption. A dot
907 (.
\b.) means that it's marked as a signature key in one of the user IDs, but may
909 The Mutt Next Generation E-Mail Client 19
911 also be used for encryption. The letter e
\be indicates that this key can be used
914 The second character indicates the key's signing capabilities. Once again, a
915 ``-
\b-'' implies ``not for signing'', ``.
\b.'' implies that the key is marked as an
916 encryption key in one of the user-ids, and ``s
\bs'' denotes a key which can be
919 Finally, the validity field (%t) indicates how well-certified a user-id is. A
920 question mark (?
\b?) indicates undefined validity, a minus character (-
\b-) marks an
921 untrusted association, a space character means a partially trusted association,
922 and a plus character (+
\b+) indicates complete validity.
924 _
\b2_
\b._
\b6_
\b._
\b5 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bo_
\bn_
\by_
\bm_
\bo_
\bu_
\bs _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs _
\bv_
\bi_
\ba _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
926 You may also have configured mutt to co-operate with Mixmaster, an anonymous
927 remailer. Mixmaster permits you to send your messages anonymously using a
928 chain of remailers. Mixmaster support in mutt is for mixmaster version 2.04
929 (beta 45 appears to be the latest) and 2.03. It does not support earlier ver-
930 sions or the later so-called version 3 betas, of which the latest appears to be
933 To use it, you'll have to obey certain restrictions. Most important, you can-
934 not use the Cc and Bcc headers. To tell Mutt-ng to use mixmaster, you have to
935 select a remailer chain, using the mix function on the compose menu.
937 The chain selection screen is divided into two parts. In the (larger) upper
938 part, you get a list of remailers you may use. In the lower part, you see the
939 currently selected chain of remailers.
941 You can navigate in the chain using the chain-prev and chain-next functions,
942 which are by default bound to the left and right arrows and to the h and l keys
943 (think vi keyboard bindings). To insert a remailer at the current chain posi-
944 tion, use the insert function. To append a remailer behind the current chain
945 position, use select-entry or append. You can also delete entries from the
946 chain, using the corresponding function. Finally, to abandon your changes,
947 leave the menu, or accept them pressing (by default) the Return key.
949 Note that different remailers do have different capabilities, indicated in the
950 %c entry of the remailer menu lines (see _
\b$_
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.141 ,
951 page 119)). Most important is the ``middleman'' capability, indicated by a
952 capital ``M'': This means that the remailer in question cannot be used as the
953 final element of a chain, but will only forward messages to other mixmaster
954 remailers. For details on the other capabilities, please have a look at the
955 mixmaster documentation.
957 _
\b2_
\b._
\b7 _
\bF_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\bi_
\bn_
\bg _
\ba_
\bn_
\bd _
\bB_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
959 The Mutt Next Generation E-Mail Client 20
961 Often, it is necessary to forward mails to other people. Therefore, mutt-ng
962 supports forwarding messages in two different ways.
964 The first one is regular forwarding, as you probably know it from other mail
965 clients. You simply press f, enter the recipient email address, the subject of
966 the forwarded email, and then you can edit the message to be forwarded in the
967 editor. The forwarded message is separated from the rest of the message via the
968 two following markers:
970 ----- Forwarded message from Lucas User <luser@example.com> -----
972 From: Lucas User <luser@example.com>
973 Date: Thu, 02 Dec 2004 03:08:34 +0100
974 To: Michael Random <mrandom@example.com>
975 Subject: Re: blackmail
977 Pay me EUR 50,000.- cash or your favorite stuffed animal will die
980 ----- End forwarded message -----
982 When you're done with editing the mail, save and quit the editor, and you will
983 return to the compose menu, the same menu you also encounter when composing or
986 The second mode of forwarding emails with mutt-ng is the so-called _
\bb_
\bo_
\bu_
\bn_
\bc_
\bi_
\bn_
\bg:
987 when you bounce an email to another address, it will be sent in practically the
988 same format you send it (except for headers that are created during transport-
989 ing the message). To bounce a message, press b and enter the recipient email
990 address. By default, you are then asked whether you really want to bounce the
991 message to the specified recipient. If you answer with yes, the message will
994 To the recipient, the bounced email will look as if he got it like a regular
995 email where he was Bcc: recipient. The only possibility to find out whether it
996 was a bounced email is to carefully study the email headers and to find out
997 which host really sent the email.
999 _
\b2_
\b._
\b8 _
\bP_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl
1001 At times it is desirable to delay sending a message that you have already begun
1002 to compose. When the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be function is used in the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu,
1003 the body of your message and attachments are stored in the mailbox specified by
1004 the _
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.216 , page 138) variable. This means that you can
1005 recall the message even if you exit Mutt-ng and then restart it at a later
1008 Once a message is postponed, there are several ways to resume it. From the
1009 command line you can use the ``-p'' option, or if you _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be a new message
1011 The Mutt Next Generation E-Mail Client 21
1013 from the _
\bi_
\bn_
\bd_
\be_
\bx or _
\bp_
\ba_
\bg_
\be_
\br you will be prompted if postponed messages exist. If
1014 multiple messages are currently postponed, the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd menu will pop up and
1015 you can select which message you would like to resume.
1017 N
\bNo
\bot
\bte
\be:
\b: If you postpone a reply to a message, the reply setting of the message is
1018 only updated when you actually finish the message and send it. Also, you must
1019 be in the same folder with the message you replied to for the status of the
1020 message to be updated.
1022 See also the _
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.215 , page 138) quad-option.
1024 _
\b3_
\b. _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn
1026 _
\b3_
\b._
\b1 _
\bL_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs _
\bo_
\bf _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1028 While the default configuration (or ``preferences'') make Mutt-ng usable right
1029 out of the box, it is often desirable to tailor Mutt-ng to suit your own
1030 tastes. When Mutt-ng is first invoked, it will attempt to read the ``system''
1031 configuration file (defaults set by your local system administrator), unless
1032 the ``-n'' _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be (section 7.1 , page 79) option is specified. This
1033 file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng
1034 users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc.
1035 Mutt will next look for a file named .muttrc in your home directory, Mutt-ng
1036 will look for .muttngrc. If this file does not exist and your home directory
1037 has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc.
1039 .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place
1040 your _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page 82) to configure Mutt-ng.
1042 _
\b3_
\b._
\b2 _
\bS_
\by_
\bn_
\bt_
\ba_
\bx _
\bo_
\bf _
\bI_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bF_
\bi_
\bl_
\be_
\bs
1044 An initialization file consists of a series of _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs (section 7.3 , page
1045 82). Each line of the file may contain one or more commands. When multiple
1046 commands are used, they must be separated by a semicolon (;).
1048 set realname='Mutt-ng user' ; ignore x-
1050 The hash mark, or pound sign (``#''), is used as a ``comment'' character. You
1051 can use it to annotate your initialization file. All text after the comment
1052 character to the end of the line is ignored. For example,
1054 my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
1056 Single quotes (') and double quotes (') can be used to quote strings which
1058 The Mutt Next Generation E-Mail Client 22
1060 contain spaces or other special characters. The difference between the two
1061 types of quotes is similar to that of many popular shell programs, namely that
1062 a single quote is used to specify a literal string (one that is not interpreted
1063 for shell variables or quoting with a backslash [see next paragraph]), while
1064 double quotes indicate a string for which should be evaluated. For example,
1065 backtics are evaluated inside of double quotes, but n
\bno
\bot
\bt for single quotes.
1067 \ quotes the next character, just as in shells such as bash and zsh. For exam-
1068 ple, if want to put quotes ``''' inside of a string, you can use ``\'' to force
1069 the next character to be a literal instead of interpreted character.
1071 set realname="Michael \"MuttDude\" Elkins"
1073 ``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r'' have
1074 their usual C meanings of linefeed and carriage-return, respectively.
1076 A \ at the end of a line can be used to split commands over multiple lines,
1077 provided that the split points don't appear in the middle of command names.
1079 Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the
1080 end of a line also in comments. This allows you to disable a command split over
1081 multiple lines with only one ``#''.
1084 set realname="Michael \"MuttDude\" Elkins"
1086 When testing your config files, beware the following caveat. The backslash at
1087 the end of the commented line extends the current line with the next line -
1088 then referred to as a ``continuation line''. As the first line is commented
1089 with a hash (#) all following continuation lines are also part of a comment and
1090 therefore are ignored, too. So take care of comments when continuation lines
1091 are involved within your setup files!
1101 line1 ``continues'' until line4. however, the part after the # is a comment
1102 which includes line3 and line4. line5 is a new line of its own and thus is
1105 It is also possible to substitute the output of a Unix command in an initial-
1106 ization file. This is accomplished by enclosing the command in backquotes
1109 The Mutt Next Generation E-Mail Client 23
1111 my_hdr X-Operating-System: `uname -a`
1113 The output of the Unix command ``uname -a'' will be substituted before the line
1114 is parsed. Note that since initialization files are line oriented, only the
1115 first line of output from the Unix command will be substituted.
1117 UNIX environments can be accessed like the way it is done in shells like sh and
1118 bash: Prepend the name of the environment by a ``$''. For example,
1120 set record=+sent_on_$HOSTNAME
1122 The commands understood by mutt are explained in the next paragraphs. For a
1123 complete list, see the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.3 , page 82).
1125 _
\b3_
\b._
\b3 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg_
\b/_
\bU_
\bs_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs
1127 Usage: alias _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
1129 It's usually very cumbersome to remember or type out the address of someone you
1130 are communicating with. Mutt-ng allows you to create ``aliases'' which map a
1131 short string to a full address.
1133 N
\bNo
\bot
\bte
\be:
\b: if you want to create an alias for a group (by specifying more than one
1134 address), you m
\bmu
\bus
\bst
\bt separate the addresses with a comma (``,'').
1136 To remove an alias or aliases (``*'' means all aliases):
1138 unalias [ * | _
\bk_
\be_
\by _
\b._
\b._
\b. ]
1140 alias muttdude me@cs.hmc.edu (Michael Elkins)
1141 alias theguys manny, moe, jack
1143 Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe-
1144 cial file. The alias command can appear anywhere in a configuration file, as
1145 long as this file is _
\bs_
\bo_
\bu_
\br_
\bc_
\be_
\bd (section 3.28 , page 42). Consequently, you can
1146 have multiple alias files, or you can have all aliases defined in your muttrc.
1148 On the other hand, the _
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (section 2.5.4 , page 11) function can use
1149 only one file, the one pointed to by the _
\b$_
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be (section 7.4.3 , page 86)
1150 variable (which is ~/.muttrc by default). This file is not special either, in
1151 the sense that Mutt-ng will happily append aliases to any file, but in order
1152 for the new aliases to take effect you need to explicitly _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section
1153 3.28 , page 42) this file too.
1157 The Mutt Next Generation E-Mail Client 24
1159 source /usr/local/share/Mutt-ng.aliases
1160 source ~/.mail_aliases
1161 set alias_file=~/.mail_aliases
1163 To use aliases, you merely use the alias at any place in mutt where mutt
1164 prompts for addresses, such as the _
\bT_
\bo_
\b: or _
\bC_
\bc_
\b: prompt. You can also enter
1165 aliases in your editor at the appropriate headers if you have the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1166 (section 7.4.55 , page 98) variable set.
1168 In addition, at the various address prompts, you can use the tab character to
1169 expand a partial alias to the full alias. If there are multiple matches, mutt
1170 will bring up a menu with the matching aliases. In order to be presented with
1171 the full list of aliases, you must hit tab with out a partial alias, such as at
1172 the beginning of the prompt or after a comma denoting multiple addresses.
1174 In the alias menu, you can select as many aliases as you want with the _
\bs_
\be_
\bl_
\be_
\bc_
\bt_
\b-
1175 _
\be_
\bn_
\bt_
\br_
\by key (default: RET), and use the _
\be_
\bx_
\bi_
\bt key (default: q) to return to the
1178 _
\b3_
\b._
\b4 _
\bC_
\bh_
\ba_
\bn_
\bg_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs
1180 Usage: bind _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1182 This command allows you to change the default key bindings (operation invoked
1183 when pressing a key).
1185 _
\bm_
\ba_
\bp specifies in which menu the binding belongs. Multiple maps may be speci-
1186 fied by separating them with commas (no additional whitespace is allowed). The
1187 currently defined maps are:
1190 This is not a real menu, but is used as a fallback for all of the
1191 other menus except for the pager and editor modes. If a key is not
1192 defined in another menu, Mutt-ng will look for a binding to use in
1193 this menu. This allows you to bind a key to a certain function in
1194 multiple menus instead of having multiple bind statements to accom-
1195 plish the same task.
1198 The alias menu is the list of your personal aliases as defined in
1199 your muttrc. It is the mapping from a short alias name to the full
1200 email address(es) of the recipient(s).
1203 The attachment menu is used to access the attachments on received
1207 The browser is used for both browsing the local directory
1209 The Mutt Next Generation E-Mail Client 25
1211 structure, and for listing all of your incoming mailboxes.
1214 The editor is the line-based editor the user enters text data.
1217 The index is the list of messages contained in a mailbox.
1220 The compose menu is the screen used when sending a new message.
1223 The pager is the mode used to display message/attachment data, and
1227 The pgp menu is used to select the OpenPGP keys used for encrypting
1231 The postpone menu is similar to the index menu, except is used when
1232 recalling a message the user was composing, but saved until later.
1234 _
\bk_
\be_
\by is the key (or key sequence) you wish to bind. To specify a control char-
1235 acter, use the sequence _
\b\_
\bC_
\bx, where _
\bx is the letter of the control character
1236 (for example, to specify control-A use ``\Ca''). Note that the case of _
\bx as
1237 well as _
\b\_
\bC is ignored, so that _
\b\_
\bC_
\bA, _
\b\_
\bC_
\ba, _
\b\_
\bc_
\bA and _
\b\_
\bc_
\ba are all equivalent. An
1238 alternative form is to specify the key as a three digit octal number prefixed
1239 with a ``\'' (for example _
\b\_
\b1_
\b7_
\b7 is equivalent to _
\b\_
\bc_
\b?).
1241 In addition, _
\bk_
\be_
\by may consist of:
1243 The Mutt Next Generation E-Mail Client 26
1247 <backtab> backtab / shift-tab
1257 <pagedown> Page Down
1258 <backspace> Backspace
1267 <f10> function key 10
1269 _
\bk_
\be_
\by does not need to be enclosed in quotes unless it contains a space (`` '').
1271 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn specifies which action to take when _
\bk_
\be_
\by is pressed. For a complete
1272 list of functions, see the _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 170). The special
1273 function noop unbinds the specified key sequence.
1275 _
\b3_
\b._
\b5 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\ba_
\bl_
\bi_
\ba_
\bs_
\be_
\bs _
\bf_
\bo_
\br _
\bc_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bs_
\be_
\bt_
\bs
1277 Usage: charset-hook _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1279 Usage: iconv-hook _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
1281 The charset-hook command defines an alias for a character set. This is useful
1282 to properly display messages which are tagged with a character set name not
1285 The iconv-hook command defines a system-specific name for a character set.
1286 This is helpful when your systems character conversion library insists on using
1287 strange, system-specific names for character sets.
1289 _
\b3_
\b._
\b6 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1291 Usage: folder-hook [!]_
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1293 It is often desirable to change settings based on which mailbox you are
1295 The Mutt Next Generation E-Mail Client 27
1297 reading. The folder-hook command provides a method by which you can execute
1298 any configuration command. _
\br_
\be_
\bg_
\be_
\bx_
\bp is a regular expression specifying in which
1299 mailboxes to execute _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd before loading. If a mailbox matches multiple
1300 folder-hook's, they are executed in the order given in the muttrc.
1302 N
\bNo
\bot
\bte
\be:
\b: if you use the ``!'' shortcut for _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.299 , page
1303 158) at the beginning of the pattern, you must place it inside of double or
1304 single quotes in order to distinguish it from the logical _
\bn_
\bo_
\bt operator for the
1307 Note that the settings are _
\bn_
\bo_
\bt restored when you leave the mailbox. For exam-
1308 ple, a command action to perform is to change the sorting method based upon the
1311 folder-hook mutt set sort=threads
1313 However, the sorting method is not restored to its previous value when reading
1314 a different mailbox. To specify a _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt command, use the pattern ``.'':
1316 folder-hook . set sort=date-sent
1318 _
\b3_
\b._
\b7 _
\bK_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bm_
\ba_
\bc_
\br_
\bo_
\bs
1320 Usage: macro _
\bm_
\be_
\bn_
\bu _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
1322 Macros are useful when you would like a single key to perform a series of
1323 actions. When you press _
\bk_
\be_
\by in menu _
\bm_
\be_
\bn_
\bu, Mutt-ng will behave as if you had
1324 typed _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be. So if you have a common sequence of commands you type, you can
1325 create a macro to execute those commands with a single key.
1327 _
\bm_
\be_
\bn_
\bu is the _
\bm_
\ba_
\bp (section 3.4 , page 24) which the macro will be bound. Multi-
1328 ple maps may be specified by separating multiple menu arguments by commas.
1329 Whitespace may not be used in between the menu arguments and the commas sepa-
1332 _
\bk_
\be_
\by and _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be are expanded by the same rules as the _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs (section
1333 3.4 , page 24). There are some additions however. The first is that control
1334 characters in _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be can also be specified as _
\b^_
\bx. In order to get a caret
1335 (`^'') you need to use _
\b^_
\b^. Secondly, to specify a certain key such as _
\bu_
\bp or to
1336 invoke a function directly, you can use the format _
\b<_
\bk_
\be_
\by _
\bn_
\ba_
\bm_
\be_
\b> and _
\b<_
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
1337 _
\bn_
\ba_
\bm_
\be_
\b>. For a listing of key names see the section on _
\bk_
\be_
\by _
\bb_
\bi_
\bn_
\bd_
\bi_
\bn_
\bg_
\bs (section
1338 3.4 , page 24). Functions are listed in the _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section
1341 The advantage with using function names directly is that the macros will work
1342 regardless of the current key bindings, so they are not dependent on the user
1343 having particular key definitions. This makes them more robust and portable,
1344 and also facilitates defining of macros in files used by more than one user
1346 The Mutt Next Generation E-Mail Client 28
1348 (eg. the system Muttngrc).
1350 Optionally you can specify a descriptive text after _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be, which is shown in
1353 N
\bNo
\bot
\bte
\be:
\b: Macro definitions (if any) listed in the help screen(s), are silently
1354 truncated at the screen width, and are not wrapped.
1356 _
\b3_
\b._
\b8 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bc_
\bo_
\bl_
\bo_
\br _
\ba_
\bn_
\bd _
\bm_
\bo_
\bn_
\bo _
\bv_
\bi_
\bd_
\be_
\bo _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be_
\bs
1358 Usage: color _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
1360 Usage: color index _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1362 Usage: uncolor index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1364 If your terminal supports color, you can spice up Mutt-ng by creating your own
1365 color scheme. To define the color of an object (type of information), you must
1366 specify both a foreground color a
\ban
\bnd
\bd a background color (it is not possible to
1367 only specify one or the other).
1369 _
\bo_
\bb_
\bj_
\be_
\bc_
\bt can be one of:
1373 +
\bo body (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the body of messages)
1375 +
\bo bold (highlighting bold patterns in the body of messages)
1377 +
\bo error (error messages printed by Mutt-ng)
1379 +
\bo header (match _
\br_
\be_
\bg_
\be_
\bx_
\bp in the message header)
1381 +
\bo hdrdefault (default color of the message header in the pager)
1383 +
\bo index (match _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn in the message index)
1385 +
\bo indicator (arrow or bar used to indicate the current item in a menu)
1387 +
\bo markers (the ``+'' markers at the beginning of wrapped lines in the pager)
1389 +
\bo message (informational messages)
1393 +
\bo quoted (text matching _
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.227 , page 140) in the
1396 +
\bo quoted1, quoted2, ..., quotedN
\bN (higher levels of quoting)
1398 +
\bo search (highlighting of words in the pager)
1400 The Mutt Next Generation E-Mail Client 29
1404 +
\bo status (mode lines used to display info about the mailbox or message)
1406 +
\bo tilde (the ``~'' used to pad blank lines in the pager)
1408 +
\bo tree (thread tree drawn in the message index and attachment menu)
1410 +
\bo underline (highlighting underlined patterns in the body of messages)
1412 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd and _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can be one of the following:
1434 _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd can optionally be prefixed with the keyword bright to make the fore-
1435 ground color boldfaced (e.g., brightred).
1437 If your terminal supports it, the special keyword _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt can be used as a
1438 transparent color. The value _
\bb_
\br_
\bi_
\bg_
\bh_
\bt_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt is also valid. If Mutt-ng is
1439 linked against the _
\bS_
\b-_
\bL_
\ba_
\bn_
\bg library, you also need to set the _
\bC_
\bO_
\bL_
\bO_
\bR_
\bF_
\bG_
\bB_
\bG environ-
1440 ment variable to the default colors of your terminal for this to work; for
1441 example (for Bourne-like shells):
1443 set COLORFGBG="green;black"
1446 N
\bNo
\bot
\bte
\be:
\b: The _
\bS_
\b-_
\bL_
\ba_
\bn_
\bg library requires you to use the _
\bl_
\bi_
\bg_
\bh_
\bt_
\bg_
\br_
\ba_
\by and _
\bb_
\br_
\bo_
\bw_
\bn keywords
1447 instead of _
\bw_
\bh_
\bi_
\bt_
\be and _
\by_
\be_
\bl_
\bl_
\bo_
\bw when setting this variable.
1449 N
\bNo
\bot
\bte
\be:
\b: The uncolor command can be applied to the index object only. It removes
1450 entries from the list. You m
\bmu
\bus
\bst
\bt specify the same pattern specified in the color
1451 command for it to be removed. The pattern ``*'' is a special token which means
1452 to clear the color index list of all entries.
1454 The Mutt Next Generation E-Mail Client 30
1456 Mutt-ng also recognizes the keywords _
\bc_
\bo_
\bl_
\bo_
\br_
\b0, _
\bc_
\bo_
\bl_
\bo_
\br_
\b1, ..., _
\bc_
\bo_
\bl_
\bo_
\brN
\bN-
\b-1
\b1 (N
\bN being the
1457 number of colors supported by your terminal). This is useful when you remap
1458 the colors for your display (for example by changing the color associated with
1459 _
\bc_
\bo_
\bl_
\bo_
\br_
\b2 for your xterm), since color names may then lose their normal meaning.
1461 If your terminal does not support color, it is still possible change the video
1462 attributes through the use of the ``mono'' command:
1464 Usage: mono _
\b<_
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b> _
\b<_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be_
\b> [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
1466 Usage: mono index _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1468 Usage: unmono index _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1470 where _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be is one of the following:
1482 _
\b3_
\b._
\b9 _
\bI_
\bg_
\bn_
\bo_
\br_
\bi_
\bn_
\bg _
\b(_
\bw_
\be_
\be_
\bd_
\bi_
\bn_
\bg_
\b) _
\bu_
\bn_
\bw_
\ba_
\bn_
\bt_
\be_
\bd _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1484 Usage: [un]ignore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1486 Messages often have many header fields added by automatic processing systems,
1487 or which may not seem useful to display on the screen. This command allows you
1488 to specify header fields which you don't normally want to see.
1490 You do not need to specify the full header field name. For example, ``ignore
1491 content-'' will ignore all header fields that begin with the pattern ``con-
1492 tent-''. ``ignore *'' will ignore all headers.
1494 To remove a previously added token from the list, use the ``unignore'' command.
1495 The ``unignore'' command will make Mutt-ng display headers with the given pat-
1496 tern. For example, if you do ``ignore x-'' it is possible to ``unignore x-
1499 ``unignore *'' will remove all tokens from the ignore list.
1503 # Sven's draconian header weeding
1505 unignore from date subject to cc
1506 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1509 The Mutt Next Generation E-Mail Client 31
1511 _
\b3_
\b._
\b1_
\b0 _
\bA_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs_
\be_
\bs
1513 Usage: [un]alternates _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1515 With various functions, mutt will treat messages differently, depending on
1516 whether you sent them or whether you received them from someone else. For
1517 instance, when replying to a message that you sent to a different party, mutt
1518 will automatically suggest to send the response to the original message's
1519 recipients -- responding to yourself won't make much sense in many cases. (See
1520 _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section 7.4.235 , page 142).)
1522 Many users receive e-mail under a number of different addresses. To fully use
1523 mutt's features here, the program must be able to recognize what e-mail
1524 addresses you receive mail under. That's the purpose of the alternates command:
1525 It takes a list of regular expressions, each of which can identify an address
1526 under which you receive e-mail.
1528 The unalternates command can be used to write exceptions to alternates pat-
1529 terns. If an address matches something in an alternates command, but you none-
1530 theless do not think it is from you, you can list a more precise pattern under
1531 an unalternates command.
1533 To remove a regular expression from the alternates list, use the unalternates
1534 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1535 command matches an entry on the unalternates list, that unalternates entry will
1536 be removed. If the _
\br_
\be_
\bg_
\be_
\bx_
\bp for unalternates is ``*'', _
\ba_
\bl_
\bl _
\be_
\bn_
\bt_
\br_
\bi_
\be_
\bs on alternates
1539 _
\b3_
\b._
\b1_
\b1 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1541 _
\b3_
\b._
\b1_
\b1_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
1543 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1544 ning of email, each message had a fixed line width, and it was enough for dis-
1545 playing them on fixed-size terminals. But times changed, and nowadays hardly
1546 anybody still uses fixed-size terminals: more people nowaydays use graphical
1547 user interfaces, with dynamically resizable windows. This led to the demand of
1548 a new email format that makes it possible for the email client to make the
1549 email look nice in a resizable window without breaking quoting levels and cre-
1550 ating an incompatible email format that can also be displayed nicely on old
1551 fixed-size terminals.
1553 For introductory information on format=flowed messages, see
1554 <http://www.joeclark.org/ffaq.html>.
1556 _
\b3_
\b._
\b1_
\b1_
\b._
\b2 _
\bR_
\be_
\bc_
\be_
\bi_
\bv_
\bi_
\bn_
\bg_
\b: _
\bD_
\bi_
\bs_
\bp_
\bl_
\ba_
\by _
\bS_
\be_
\bt_
\bu_
\bp
1558 When you receive emails that are marked as format=flowed messages, and is for-
1559 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1560 your terminal. If you want a fixed margin on the right side of your terminal,
1561 you can set the following:
1563 The Mutt Next Generation E-Mail Client 32
1567 The code above makes the line break 10 columns before the right side of the
1570 If your terminal is so wide that the lines are embarrassingly long, you can
1571 also set a maximum line length:
1573 set max_line_length = 120
1575 The example above will give you lines not longer than 120 characters.
1577 When you view at format=flowed messages, you will often see the quoting hierar-
1578 chy like in the following example:
1580 >Bill, can you please send last month's progress report to Mr.
1581 >Morgan? We also urgently need the cost estimation for the new
1582 >production server that we want to set up before our customer's
1583 >project will go live.
1585 This obviously doesn't look very nice, and it makes it very hard to differenti-
1586 ate between text and quoting character. The solution is to configure mutt-ng to
1587 "stuff" the quoting:
1591 This will lead to a nicer result that is easier to read:
1593 > Bill, can you please send last month's progress report to Mr.
1594 > Morgan? We also urgently need the cost estimation for the new
1595 > production server that we want to set up before our customer's
1596 > project will go live.
1598 _
\b3_
\b._
\b1_
\b1_
\b._
\b3 _
\bS_
\be_
\bn_
\bd_
\bi_
\bn_
\bg
1600 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1605 The Mutt Next Generation E-Mail Client 33
1607 Additionally, you have to use an editor which supports writing format=flowed-
1608 conforming emails. For vim, this is done by adding w to the formatoptions (see
1609 :h formatoptions and :h fo-table) when writing emails.
1611 Also note that _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\b=_
\bf_
\bl_
\bo_
\bw_
\be_
\bd knows about ``space-stuffing'', that is, when
1612 sending messages, some kinds of lines have to be indented with a single space
1613 on the sending side. On the receiving side, the first space (if any) is
1614 removed. As a consequence and in addition to the above simple setting, please
1615 keep this in mind when making manual formattings within the editor. Also note
1616 that mutt-ng currently violates the standard (RfC 3676) as it does not space-
1617 stuff lines starting with:
1619 +
\bo > This is _
\bn_
\bo_
\bt the quote character but a right angle used for other reasons
1621 +
\bo From with a trailing space.
1623 +
\bo just a space for formatting reasons
1625 Please make sure that you manually prepend a space to each of them.
1627 _
\b3_
\b._
\b1_
\b1_
\b._
\b4 _
\bA_
\bd_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bN_
\bo_
\bt_
\be_
\bs
1631 For completeness, the _
\b$_
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be (section 7.4.47 , page 96) variable pro-
1632 vides the mechanism to generate a DelSp=yes parameter on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages.
1633 According to the standard, clients receiving a format=flowed messages should
1634 delete the last space of a flowed line but still interpret the line as flowed.
1635 Because flowed lines usually contain only one space at the end, this parameter
1636 would make the receiving client concatenate the last word of the previous with
1637 the first of the current line _
\bw_
\bi_
\bt_
\bh_
\bo_
\bu_
\bt a space. This makes ordinary text unread-
1638 able and is intended for languages rarely using spaces. So please use this set-
1639 ting only if you're sure what you're doing.
1641 _
\b3_
\b._
\b1_
\b2 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1643 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1645 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1647 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 ,
1648 page 58). In order to take advantage of them, you must specify which addresses
1649 belong to mailing lists, and which mailing lists you are subscribed to. Once
1650 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1651 work for all known lists. Additionally, when you send a message to a sub-
1652 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1653 user agents not to send copies of replies to your personal address. Note that
1654 the Mail-Followup-To header is a non-standard extension which is not supported
1655 by all mail user agents. Adding it is not bullet-proof against receiving per-
1656 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1657 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.67 , page 101)
1658 configuration variable.
1660 The Mutt Next Generation E-Mail Client 34
1662 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1663 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1664 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1667 You can use regular expressions with both commands. To mark all messages sent
1668 to a specific bug report's address on mutt's bug tracking system as list mail,
1669 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1670 sufficient to just give a portion of the list's e-mail address.
1672 Specify as much of the address as you need to to remove ambiguity. For exam-
1673 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1674 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
1675 list, you could add ``lists mutt-users'' to your initialization file. To tell
1676 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1677 tialization file instead. If you also happen to get mail from someone whose
1678 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-
1679 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1680 from the actual list.
1682 The ``unlists'' command is used to remove a token from the list of known and
1683 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1685 To remove a mailing list from the list of subscribed mailing lists, but keep it
1686 on the list of known mailing lists, use ``unsubscribe''.
1688 _
\b3_
\b._
\b1_
\b3 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bl_
\bt_
\bi_
\bp_
\bl_
\be _
\bs_
\bp_
\bo_
\bo_
\bl _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs
1690 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1692 This command is used to move read messages from a specified mailbox to a dif-
1693 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1694 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1695 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1697 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1698 (it is not possible to save read mail in more than a single mailbox).
1700 _
\b3_
\b._
\b1_
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs _
\bw_
\bh_
\bi_
\bc_
\bh _
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be _
\bm_
\ba_
\bi_
\bl
1702 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1704 This command specifies folders which can receive mail and which will be checked
1705 for new messages. By default, the main menu status bar displays how many of
1706 these folders have new messages.
1708 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1710 Pressing TAB in the directory browser will bring up a menu showing the files
1711 specified by the mailboxes command, and indicate which contain new messages.
1713 The Mutt Next Generation E-Mail Client 35
1715 Mutt-ng will automatically enter this mode when invoked from the command line
1718 The ``unmailboxes'' command is used to remove a token from the list of folders
1719 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1721 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1722 access time. Utilities like biff or frm or any other program which accesses
1723 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1724 they do not properly reset the access time. Backup tools are another common
1725 reason for updated access times.
1727 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1728 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
1729 57) (such as ``='' and ``!''), any variable definition that affect these char-
1730 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.65 , page 100) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1731 7.4.299 , page 158)) should be executed before the mailboxes command.
1733 _
\b3_
\b._
\b1_
\b5 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1737 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1739 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1741 The ``my_hdr'' command allows you to create your own header fields which will
1742 be added to every message you send.
1744 For example, if you would like to add an ``Organization:'' header field to all
1745 of your outgoing messages, you can put the command
1747 my_hdr Organization: A Really Big Company, Anytown, USA
1751 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1752 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1753 there, so Mutt-ng enforces the rule.
1755 If you would like to add a header field to a single message, you should either
1756 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1757 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1758 header of your message along with the body.
1760 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1761 specify an asterisk (``*'') to remove all header fields, or the fields to
1762 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1765 The Mutt Next Generation E-Mail Client 36
1769 _
\b3_
\b._
\b1_
\b6 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bo_
\br_
\bd_
\be_
\br _
\bo_
\bf _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs _
\bw_
\bh_
\be_
\bn _
\bv_
\bi_
\be_
\bw_
\bi_
\bn_
\bg _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
1771 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1773 With this command, you can specify an order in which mutt will attempt to
1774 present headers to you when viewing messages.
1776 ``unhdr_order *'' will clear all previous headers from the order list, thus
1777 removing the header order effects set by the system-wide startup file.
1779 hdr_order From Date: From: To: Cc: Subject:
1781 _
\b3_
\b._
\b1_
\b7 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1783 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1785 This command is used to override the default filename used when saving mes-
1786 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:
1787 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1788 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1790 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 54) for information on the
1791 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1795 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1796 save-hook aol\\.com$ +spam
1798 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36) command.
1800 _
\b3_
\b._
\b1_
\b8 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bw_
\bh_
\be_
\bn _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg
1802 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1804 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1805 (section 7.4.232 , page 142). Mutt-ng searches the initial list of message
1806 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1807 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1808 7.4.232 , page 142) mailbox.
1810 The Mutt Next Generation E-Mail Client 37
1812 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 54) for information on the
1813 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1815 Example: fcc-hook [@.]aol\\.com$ +spammers
1817 The above will save a copy of all messages going to the aol.com domain to the
1818 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 ,
1821 _
\b3_
\b._
\b1_
\b9 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be _
\ba_
\bn_
\bd _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\ba_
\bt _
\bo_
\bn_
\bc_
\be
1823 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1825 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1826 3.18 , page 36) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 36) with its arguments.
1828 _
\b3_
\b._
\b2_
\b0 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt_
\bs
1830 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1832 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1834 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1836 These commands can be used to execute arbitrary configuration commands based
1837 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1838 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1841 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1842 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1843 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
1844 the order specified in the users's configuration file.
1846 send2-hook is matched every time a message is changed, either by editing it, or
1847 by using the compose menu to change its recipients or subject. send2-hook is
1848 executed after send-hook, and can, e.g., be used to set parameters such as the
1849 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.249 , page 146) variable depending on the message's
1852 For each type of send-hook or reply-hook, when multiple matches occur, commands
1853 are executed in the order they are specified in the muttrc (for that type of
1856 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 54) for information on the
1857 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1859 Example: send-hook mutt 'set mime_forward signature='''
1861 Another typical use for this command is to change the values of the
1863 The Mutt Next Generation E-Mail Client 38
1865 _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.15 , page 89), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.261 , page
1866 149) and _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.115 , page 114) variables in order to change the
1867 language of the attributions and signatures based upon the recipients.
1869 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
1870 recipients. Adding a recipient after replying or editing the message will NOT
1871 cause any send-hook to be executed. Also note that my_hdr commands which mod-
1872 ify recipient headers, or the message's subject, don't have any effect on the
1873 current message when executed from a send-hook.
1875 _
\b3_
\b._
\b2_
\b1 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\be_
\bf_
\bo_
\br_
\be _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bt_
\bi_
\bn_
\bg _
\ba _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
1877 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1879 This command can be used to execute arbitrary configuration commands before
1880 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
1881 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
1882 tiple matches occur, commands are executed in the order they are specified in
1885 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 54) for information on the
1886 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1890 message-hook ~A 'set pager=builtin'
1891 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1893 _
\b3_
\b._
\b2_
\b2 _
\bC_
\bh_
\bo_
\bo_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bc_
\br_
\by_
\bp_
\bt_
\bo_
\bg_
\br_
\ba_
\bp_
\bh_
\bi_
\bc _
\bk_
\be_
\by _
\bo_
\bf _
\bt_
\bh_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt
1895 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
1897 When encrypting messages with PGP or OpenSSL, you may want to associate a cer-
1898 tain key with a given e-mail address automatically, either because the recipi-
1899 ent's public key can't be deduced from the destination address, or because, for
1900 some reasons, you need to override the key Mutt-ng would normally use. The
1901 crypt-hook command provides a method by which you can specify the ID of the
1902 public key to be used when encrypting messages to a certain recipient.
1904 The meaning of "key id" is to be taken broadly in this context: You can either
1905 put a numerical key ID here, an e-mail address, or even just a real name.
1907 _
\b3_
\b._
\b2_
\b3 _
\bA_
\bd_
\bd_
\bi_
\bn_
\bg _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be_
\bs _
\bt_
\bo _
\bt_
\bh_
\be _
\bk_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bb_
\bu_
\bf_
\bf_
\be_
\br
1909 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1911 This command adds the named string to the keyboard buffer. The string may
1913 The Mutt Next Generation E-Mail Client 39
1915 contain control characters, key names and function names like the sequence
1916 string in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.7 , page 27) command. You may use it to auto-
1917 matically run a sequence of commands at startup, or when entering certain fold-
1920 _
\b3_
\b._
\b2_
\b4 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
1922 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
1924 This command can be used to execute any function. Functions are listed in the
1925 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 7.5 , page 170). ``exec function'' is equivalent
1926 to ``push <function>''.
1928 _
\b3_
\b._
\b2_
\b5 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
1930 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
1932 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1934 In situations where you have to cope with a lot of emails, e.g. when you read
1935 many different mailing lists, and take part in discussions, it is always useful
1936 to have the important messages marked and the annoying messages or the ones
1937 that you aren't interested in deleted. For this purpose, mutt-ng features a
1938 mechanism called ``scoring''.
1940 When you use scoring, every message has a base score of 0. You can then use the
1941 score command to define patterns and a positive or negative value associated
1942 with it. When a pattern matches a message, the message's score will be raised
1943 or lowered by the amount of the value associated with the pattern.
1945 score "~f nion@muttng\.org" 50
1946 score "~f @sco\.com" -100
1948 If the pattern matches, it is also possible to set the score value of the cur-
1949 rent message to a certain value and then stop evaluation:
1951 score "~f santaclaus@northpole\.int" =666
1953 What is important to note is that negative score values will be rounded up to
1956 To make scoring actually useful, the score must be applied in some way. That's
1957 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:
1959 +
\bo flag threshold: when a message has a score value equal or higher than the
1960 flag threshold, it will be flagged.
1962 The Mutt Next Generation E-Mail Client 40
1964 +
\bo read threshold: when a message has a score value equal or lower than the
1965 read threshold, it will be marked as read.
1967 +
\bo delete threshold: when a message has a score value equal or lower than the
1968 delete threshold, it will be marked as deleted.
1970 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-
1971 tion 7.4.246 , page 145), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.247 , page 145),
1972 _
\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.245 , page 145) and. By default,
1973 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 7.4.247 , page 145) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
1974 (section 7.4.245 , page 145) are set to -1, which means that in the default
1975 threshold configuration no message will ever get marked as read or deleted.
1977 Scoring gets especially interesting when combined with the color command and
1980 color black yellow "~n 10-"
1981 color red yellow "~n 100-"
1983 The rules above mark all messages with a score between 10 and 99 with black and
1984 yellow, and messages with a score greater or equal 100 with red and yellow.
1985 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
1986 but it is more flexible, as it visually marks different scores.
1988 _
\b3_
\b._
\b2_
\b6 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
1990 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
1992 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1994 Mutt-ng has generalized support for external spam-scoring filters. By defining
1995 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
1996 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
1997 filter. You also can display the spam attributes in your index display using
1998 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111) variable.
1999 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
2002 Your first step is to define your external filter's spam patterns using the
2003 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
2004 mail message. If any message in the mailbox matches this regular expression, it
2005 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
2006 nospam pattern -- see below.) The appearance of this attribute is entirely up
2007 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,
2008 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
2009 expression ``back-reference'' refers to a sub-expression contained within
2010 parentheses.) %1 is replaced with the first back-reference in the regex, %2
2011 with the second, etc.
2013 If you're using multiple spam filters, a message can have more than one spam-
2015 The Mutt Next Generation E-Mail Client 41
2017 related header. You can define spam patterns for each filter you use. If a mes-
2018 sage matches two or more of these patterns, and the $spam_separator variable is
2019 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
2020 strings joined together, with the value of $spam_separator separating them.
2022 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
2023 these spam settings:
2025 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
2026 spam "X-Spam-Status: Yes" "90+/SA"
2027 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
2028 set spam_separator=", "
2030 If I then received a message that DCC registered with ``many'' hits under the
2031 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
2032 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
2033 characters before ``=many'' in a DCC report indicate the checksum used -- in
2034 this case, ``Fuz2''.)
2036 If the $spam_separator variable is unset, then each spam pattern match super-
2037 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
2038 only the last one to match.
2040 The spam tag is what will be displayed in the index when you use %H in the
2041 $index_format variable. It's also the string that the ~H pattern-matching
2042 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2043 ing by spam attribute will use as a sort key.
2045 That's a pretty complicated example, and most people's actual environments will
2046 have only one spam filter. The simpler your configuration, the more effective
2047 mutt can be, especially when it comes to sorting.
2049 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2050 ordering strings alphnumerically. However, if a spam tag begins with a number,
2051 mutt will sort numerically first, and lexically only when two numbers are equal
2052 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2053 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2054 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2055 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2056 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2057 coerce your filter to give you a raw number. But in case you can't, mutt can
2058 still do something useful.
2060 The nospam command can be used to write exceptions to spam patterns. If a
2061 header pattern matches something in a spam command, but you nonetheless do not
2062 want it to receive a spam tag, you can list a more precise pattern under a
2065 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-
2066 ing spam list entry, the effect will be to remove the entry from the spam list,
2067 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2068 matches an entry on the nospam list, that nospam entry will be removed. If the
2069 _
\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
2071 The Mutt Next Generation E-Mail Client 42
2073 might be the default action if you use spam and nospam in conjunction with a
2076 You can have as many spam or nospam commands as you like. You can even do your
2077 own primitive spam detection within mutt -- for example, if you consider all
2078 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2080 spam "^From: .*MAILER-DAEMON" "999"
2082 _
\b3_
\b._
\b2_
\b7 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2084 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 ... ]
2086 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2088 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2090 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2092 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 ,
2093 page 84). There are four basic types of variables: boolean, number, string and
2094 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
2095 variables can be assigned a positive integer value.
2097 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2098 be enclosed in quotes if they contain spaces or tabs. You may also use the
2099 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2101 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2102 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2103 action to be carried out automatically as if you had answered yes to the ques-
2104 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2105 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2106 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2108 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2110 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2111 toggle the value (on or off). This is useful when writing macros. Example:
2114 The toggle command automatically prepends the inv prefix to all specified vari-
2117 The unset command automatically prepends the no prefix to all specified vari-
2120 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2121 a variable by prefixing the name of the variable with a question mark:
2123 The Mutt Next Generation E-Mail Client 43
2127 The question mark is actually only required for boolean and quadoption vari-
2130 The reset command resets all given variables to the compile time defaults
2131 (hopefully mentioned in this manual). If you use the command set and prefix the
2132 variable with ``&'' this has the same behavior as the reset command.
2134 With the reset command there exists the special variable ``all'', which allows
2135 you to reset all variables to their system defaults.
2137 _
\b3_
\b._
\b2_
\b8 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bi_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs _
\bf_
\br_
\bo_
\bm _
\ba_
\bn_
\bo_
\bt_
\bh_
\be_
\br _
\bf_
\bi_
\bl_
\be
2139 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2141 This command allows the inclusion of initialization commands from other files.
2142 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2143 ~/.muttrc readable and keep my aliases private.
2145 If the filename begins with a tilde (``~''), it will be expanded to the path of
2146 your home directory.
2148 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2149 an executable program from which to read input (eg. source ~/bin/myscript|).
2151 _
\b3_
\b._
\b2_
\b9 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2153 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2155 This command permits you to flush hooks you have previously defined. You can
2156 either remove all hooks by giving the ``*'' character as an argument, or you
2157 can remove all hooks of a specific type by saying something like unhook send-
2160 _
\b3_
\b._
\b3_
\b0 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2162 _
\b3_
\b._
\b3_
\b0_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2164 As users may run mutt-ng on different systems, the configuration must be main-
2165 tained because it's likely that people want to use the setup everywhere they
2166 use mutt-ng. And mutt-ng tries to help where it can.
2168 To not produce conflicts with different character sets, mutt-ng allows users to
2169 specify in which character set their configuration files are encoded. Please
2170 note that while reading the configuration files, this is only respected after
2171 the corresponding declaration appears. It's advised to put the following at the
2173 The Mutt Next Generation E-Mail Client 44
2175 very beginning of a users muttngrc:
2177 set config_charset = "..."
2179 and replacing the dots with the actual character set. To avoid problems while
2180 maintaining the setup, vim user's may want to use modelines as show in:
2182 # vim:fileencoding=...:
2184 while, again, replacing the dots with the appropriate name. This tells vim as
2185 which character set to read and save the file.
2187 _
\b3_
\b._
\b3_
\b0_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2189 ``Modularization'' means to divide the setup into several files while sorting
2190 the options or commands by topic. Especially for longer setups (e.g. with many
2191 hooks), this helps maintaining it and solving trouble.
2193 When using separation, setups may be, as a whole or in fractions, shared over
2196 _
\b3_
\b._
\b3_
\b0_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2198 When using a configuration on different systems, the user may not always have
2199 influence on how mutt-ng is installed and which features it includes.
2201 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2202 for mutt. Its basic syntax is:
2204 ifdef <item> <command>
2205 ifndef <item> <command>
2207 ...whereby <item> can be one of:
2209 +
\bo a function name
2211 +
\bo a variable name
2217 All available functions, variables and menus are documented elsewhere in this
2218 manual but ``features'' is specific to these two commands. To test for one,
2220 The Mutt Next Generation E-Mail Client 45
2222 prefix one of the following keywords with feature_:
2224 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2225 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2226 classic_smime, gpgme, header_cache
2228 As an example, one can use the following in ~/.muttngrc:
2230 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2231 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2232 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2234 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2235 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2236 ng/setup-nntp if NNTP support is built in.
2238 An example for testing for variable names can be used if users use different
2239 revisions of mutt-ng whereby the older one may not have a certain variable. To
2240 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.100 , page 109),
2243 ifdef imap_mail_check 'set imap_mail_check = 300'
2245 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
2246 (section 7.4.171 , page 128) only if the pager menu is available, use:
2248 ifdef pager 'set pager_index_lines = 10'
2250 For completeness, too, the opposite of ifdef is provided: ifndef which only
2251 executes the command if the test fails. For example, the following two examples
2254 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2255 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2259 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2260 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2262 The Mutt Next Generation E-Mail Client 46
2264 _
\b3_
\b._
\b3_
\b1 _
\bO_
\bb_
\bs_
\bo_
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2266 In the process of ensuring and creating more consistency, many variables have
2267 been renamed and some of the old names were already removed. Please see _
\bO_
\bb_
\bs_
\bo_
\b-
2268 _
\bl_
\be_
\bt_
\be _
\bV_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 7.4 , page 84) for a complete list.
2270 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2272 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2274 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2275 tion 7.2 , page 80) must be specified using regular expressions (regexp) in
2276 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2277 and GNU awk). For your convenience, we have included below a brief description
2280 The search is case sensitive if the pattern contains at least one upper case
2281 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2282 for a regular expression in an initialization command: ``\\''.
2284 A regular expression is a pattern that describes a set of strings. Regular
2285 expressions are constructed analogously to arithmetic expressions, by using
2286 various operators to combine smaller expressions.
2288 Note that the regular expression can be enclosed/delimited by either ' or '
2289 which is useful if the regular expression includes a white-space character.
2290 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-
2291 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2292 ace it with \ (backslash).
2294 The fundamental building blocks are the regular expressions that match a single
2295 character. Most characters, including all letters and digits, are regular
2296 expressions that match themselves. Any metacharacter with special meaning may
2297 be quoted by preceding it with a backslash.
2299 The period ``.'' matches any single character. The caret ``^'' and the dollar
2300 sign ``$'' are metacharacters that respectively match the empty string at the
2301 beginning and end of a line.
2303 A list of characters enclosed by ``['' and ``]'' matches any single character
2304 in that list; if the first character of the list is a caret ``^'' then it
2305 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2306 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2307 specified by giving the first and last characters, separated by a hyphen ``-''.
2308 Most metacharacters lose their special meaning inside lists. To include a lit-
2309 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2310 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2313 The Mutt Next Generation E-Mail Client 47
2315 Certain named classes of characters are predefined. Character classes consist
2316 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2317 defined by the POSIX standard:
2320 Alphanumeric characters.
2323 Alphabetic characters.
2326 Space or tab characters.
2335 Characters that are both printable and visible. (A space is print-
2336 able, but not visible, while an ``a'' is both.)
2339 Lower-case alphabetic characters.
2342 Printable characters (characters that are not control characters.)
2345 Punctuation characters (characters that are not letter, digits,
2346 control characters, or space characters).
2349 Space characters (such as space, tab and formfeed, to name a few).
2352 Upper-case alphabetic characters.
2355 Characters that are hexadecimal digits.
2357 A character class is only valid in a regular expression inside the brackets of
2358 a character list. Note that the brackets in these class names are part of the
2359 symbolic names, and must be included in addition to the brackets delimiting the
2360 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].
2362 Two additional special sequences can appear in character lists. These apply to
2363 non-ASCII character sets, which can have single symbols (called collating ele-
2364 ments) that are represented with more than one character, as well as several
2365 characters that are equivalent for collating or sorting purposes:
2368 A collating symbol is a multi-character collating element enclosed
2370 The Mutt Next Generation E-Mail Client 48
2372 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2373 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2374 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2377 An equivalence class is a locale-specific name for a list of char-
2378 acters that are equivalent. The name is enclosed in ``[='' and
2379 ``=]''. For example, the name ``e'' might be used to represent all
2380 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2381 matches any of ``'', ``'' and ``e''.
2383 A regular expression matching a single character may be followed by one of sev-
2384 eral repetition operators:
2387 The preceding item is optional and matched at most once.
2390 The preceding item will be matched zero or more times.
2393 The preceding item will be matched one or more times.
2396 The preceding item is matched exactly _
\bn times.
2399 The preceding item is matched _
\bn or more times.
2402 The preceding item is matched at most _
\bm times.
2405 The preceding item is matched at least _
\bn times, but no more than _
\bm
2408 Two regular expressions may be concatenated; the resulting regular expression
2409 matches any string formed by concatenating two substrings that respectively
2410 match the concatenated subexpressions.
2412 Two regular expressions may be joined by the infix operator ``|''; the result-
2413 ing regular expression matches any string matching either subexpression.
2415 Repetition takes precedence over concatenation, which in turn takes precedence
2416 over alternation. A whole subexpression may be enclosed in parentheses to
2417 override these precedence rules.
2419 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2420 may also be used in regular expressions:
2423 Matches the empty string at either the beginning or the end of a
2426 The Mutt Next Generation E-Mail Client 49
2429 Matches the empty string within a word.
2432 Matches the empty string at the beginning of a word.
2435 Matches the empty string at the end of a word.
2438 Matches any word-constituent character (letter, digit, or under-
2442 Matches any character that is not word-constituent.
2445 Matches the empty string at the beginning of a buffer (string).
2448 Matches the empty string at the end of a buffer.
2450 Please note however that these operators are not defined by POSIX, so they may
2451 or may not be available in stock libraries on various systems.
2453 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2455 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2456 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2457 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2458 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2459 _
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 80) in the Reference chapter.
2461 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2462 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2465 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2467 It is possible to combine several sub-patterns to a more complex pattern. The
2468 most simple possibility is to logically AND several patterns by stringing them
2473 The pattern above matches all messages that contain ``SPAM'' in the subject and
2476 To logical OR patterns, simply use the | operator. This one especially useful
2477 when using local groups:
2479 The Mutt Next Generation E-Mail Client 50
2481 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2482 (~b mutt-ng|~s Mutt-ng)
2485 The first pattern matches all messages that were sent by one of the mutt-ng
2486 maintainers, while the seconds pattern matches all messages that contain
2487 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2488 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2489 ences: header, i.e. messages that are not an (indirect) reply to one of my
2490 messages. A pattern can be logicall negated using the ! operator.
2492 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2494 When using dates in patterns, the dates must be specified in a special format,
2495 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2496 rent month or year. When using date ranges, and you specify only the minimum or
2497 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2498 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2500 It is also possible to use so-called ``error margins'' when specifying date
2501 ranges. You simply specify a date, and then the error margin. This margin
2502 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2503 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2504 months, w for weeks and d for days. If you use the special * sign, it means
2505 that the error margin goes to both ``directions'' in time.
2511 The first pattern matches all dates between January 1st, 2005 and January 1st
2512 2006. The second pattern matches all dates between October 18th, 2004 and
2513 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2514 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2516 Relative dates are also very important, as they make it possible to specify
2517 date ranges between a fixed number of units and the current date. How this
2518 works can be seen in the following example:
2520 ~d >2w # messages older than two weeks
2521 ~d <3d # messages newer than 3 days
2522 ~d =1m # messages that are exactly one month old
2524 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2526 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2528 The Mutt Next Generation E-Mail Client 51
2530 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2531 In short, they describe what items to print out how in menus and status mes-
2534 Basically, they work as this: for different menus and bars, there's a variable
2535 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2537 For example, when running mutt-ng on different machines or different versions
2538 for testing purposes, it may be interesting to have the following information
2539 always printed on screen when one is in the index:
2541 +
\bo the current hostname
2543 +
\bo the current mutt-ng version number
2545 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-
2546 _
\bm_
\ba_
\bt (section 7.4.310 , page 160) variable. For the hostname and version
2547 string, there's an expando for $status_format: %h expands to the hostname and
2548 %v to the version string. When just configuring:
2550 set status_format = "%v on %h: ..."
2552 mutt-ng will replace the sequence %v with the version string and %h with the
2553 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2554 mailhost, you'll see the following when you're in the index:
2556 Mutt-ng 1.5.9i on mailhost: ...
2558 In the index, there're more useful information one could want to see:
2560 +
\bo which mailbox is open
2562 +
\bo how man new, flagged or postponed messages
2566 To include the mailbox' name is as easy as:
2568 set status_format = "%v on %h: %B: ...
2570 When the currently opened mailbox is Inbox, this will be expanded to:
2572 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2574 For the number of certain types of messages, one more feature of the format
2575 strings is extremely useful. If there aren't messages of a certain type, it may
2577 The Mutt Next Generation E-Mail Client 52
2579 not be desired to print just that there aren't any but instead only print some-
2580 thing if there are any.
2582 _
\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
2584 To only print the number of messages if there are new messages in the current
2585 mailbox, further extend $status_format to:
2587 set status_format = "%v on %h: %B %?n?%n new? ...
2589 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
2590 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2591 ated if the value of the expando is different from zero. The basic syntax is:
2593 %?<item>?<string if nonzero>?
2595 which tells mutt-ng to only look at <string if nonzero> if the value of the
2596 %<item%gt; expando is different from zero. In our example, we used n as the
2597 expando to check for and %n new as the optional nonzero string.
2599 But this is not all: this feature only offers one alternative: ``print some-
2600 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2601 complete version: ``if zero, print something and else print something else.''
2602 This is achieved by the following syntax for those expandos which may be
2605 %?<item>?<string if nonzero>&<string if zero>?
2607 Using this we can make mutt-ng to do the following:
2609 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2612 +
\bo and make it print ``no new messages'' if there aren't any
2614 The corresponding configuration is:
2616 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2618 This doubles the use of the ``new messages'' string because it'll get always
2619 printed. Thus, it can be shortened to:
2621 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2623 The Mutt Next Generation E-Mail Client 53
2625 As you might see from this rather simple example, one can create very complex
2626 but fancy status messages. Please see the reference chapter for expandos and
2627 those which may be printed nonzero.
2629 _
\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
2631 Besides the information given so far, there're even more features of format
2634 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2635 characters in the expansion of <item> to lowercase.
2637 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2638 dots in the expansion of <item> to underscores (_).
2640 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2644 When this occurs, mutt-ng will fill the rest of the line with the
2645 character X. In our example, filling the rest of the line with
2646 dashes is done by setting:
2648 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2651 Since the previous expando stops at the end of line, there must be
2652 a way to fill the gap between two items via the %>X expando: it
2653 puts as many characters X in between two items so that the rest of
2654 the line will be right-justified. For example, to not put the ver-
2655 sion string and hostname of our example on the left but on the
2656 right and fill the gap with spaces, one might use (note the space
2659 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2661 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2663 Sometimes it is desirable to perform an operation on a group of messages all at
2664 once rather than one at a time. An example might be to save messages to a
2665 mailing list to a separate folder, or to delete all messages with a given sub-
2666 ject. To tag all messages matching a pattern, use the tag-pattern function,
2667 which is bound to ``shift-T'' by default. Or you can select individual mes-
2668 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2670 The Mutt Next Generation E-Mail Client 54
2672 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 80) for Mutt-ng's pattern matching
2675 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2676 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2677 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2678 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 7.4.16 ,
2679 page 90) variable is set, the next operation applies to the tagged messages
2680 automatically, without requiring the ``tag-prefix''.
2682 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.7 , page 27) or _
\bp_
\bu_
\bs_
\bh (section 3.23 , page 38) commands,
2683 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2684 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2685 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2686 this operator the rest of the macro will be executed as normal.
2688 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2690 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2691 arbitrary commands before performing some operation. For example, you may wish
2692 to tailor your configuration based upon which mailbox you are reading, or to
2693 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
2694 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 45) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 80) along
2695 with a configuration option/command. See
2697 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 26)
2699 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 37)
2701 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 37)
2703 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 36)
2705 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 34)
2707 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 36)
2709 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36)
2711 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2713 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2714 until the end of the current mutt session. As this is generally not desired, a
2715 default hook needs to be added before all other hooks to restore configuration
2716 defaults. Here is an example with send-hook and the my_hdr directive:
2718 send-hook . 'unmy_hdr From:'
2719 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2721 The Mutt Next Generation E-Mail Client 55
2723 _
\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
2725 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2726 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2727 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 45) is sufficient. But in dealing with
2728 messages a finer grain of control is needed for matching since for different
2729 purposes you want to match different criteria.
2731 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 7.2 , page 80) language
2732 for matching messages in hook commands. This works in exactly the same way as
2733 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
2734 to those operators which match information mutt extracts from the header of the
2735 message (i.e. from, to, cc, date, subject, etc.).
2737 For example, if you wanted to set your return address based upon sending mail
2738 to a specific address, you could do something like:
2740 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2742 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2744 However, it is not required that you write the pattern to match using the full
2745 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
2746 other hooks, in which case Mutt-ng will translate your pattern into the full
2747 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2748 7.4.45 , page 96) variable. The pattern is translated at the time the hook is
2749 declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 7.4.45 , page 96) that is in
2750 effect at that time will be used.
2752 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2754 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2755 which looks very similar to the ones you probably know from GUI mail clients.
2756 The sidebar lists all specified mailboxes, shows the number in each and high-
2757 lights the ones with new email Use the following configuration commands:
2759 set sidebar_visible="yes"
2760 set sidebar_width=25
2762 If you want to specify the mailboxes you can do so with:
2770 You can also specify the colors for mailboxes with new mails by using:
2772 The Mutt Next Generation E-Mail Client 56
2774 color sidebar_new red black
2775 color sidebar white black
2777 The available functions are:
2779 sidebar-scroll-up Scrolls the mailbox list up 1 page
2780 sidebar-scroll-down Scrolls the mailbox list down 1 page
2781 sidebar-next Highlights the next mailbox
2782 sidebar-next-new Highlights the next mailbox with new mail
2783 sidebar-previous Highlights the previous mailbox
2784 sidebar-open Opens the currently highlighted mailbox
2786 Reasonable key bindings look e.g. like this:
2788 bind index \Cp sidebar-prev
2789 bind index \Cn sidebar-next
2790 bind index \Cb sidebar-open
2791 bind pager \Cp sidebar-prev
2792 bind pager \Cn sidebar-next
2793 bind pager \Cb sidebar-open
2795 macro index B ':toggle sidebar_visible^M'
2796 macro pager B ':toggle sidebar_visible^M'
2798 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2799 off the sidebar simply by pressing 'B'.
2801 _
\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
2803 Mutt-ng supports connecting to external directory databases such as LDAP,
2804 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2805 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.223 , page 140) vari-
2806 able, you specify the wrapper command to use. For example:
2808 set query_command = "mutt_ldap_query.pl '%s'"
2810 The wrapper script should accept the query on the command-line. It should
2811 return a one line message, then each matching response on a single line, each
2812 line containing a tab separated address then name then some other optional
2813 information. On error, or if there are no matching addresses, return a non-
2814 zero exit code and a one line error message.
2816 An example multiple response output:
2818 Searching database ... 20 entries ... 3 matching:
2819 me@cs.hmc.edu Michael Elkins mutt dude
2820 blong@fiction.net Brandon Long mutt and more
2822 The Mutt Next Generation E-Mail Client 57
2824 roessler@guug.de Thomas Roessler mutt pgp
2826 There are two mechanisms for accessing the query function of mutt. One is to
2827 do a query from the index menu using the query function (default: Q). This
2828 will prompt for a query, then bring up the query menu which will list the
2829 matching responses. From the query menu, you can select addresses to create
2830 aliases, or to mail. You can tag multiple addresses to mail, start a new
2831 query, or have a new query appended to the current responses.
2833 The other mechanism for accessing the query function is for address completion,
2834 similar to the alias completion. In any prompt for address entry, you can use
2835 the complete-query function (default: ^T) to run a query based on the current
2836 address you have typed. Like aliases, mutt will look for what you have typed
2837 back to the last space or comma. If there is a single response for that query,
2838 mutt will expand the address in place. If there are multiple responses, mutt
2839 will activate the query menu. At the query menu, you can select one or more
2840 addresses to be added to the prompt.
2842 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2844 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2845 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2846 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2847 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.127 , page 117)
2850 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2851 stored in a single file. Each message has a line of the form:
2853 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2855 to denote the start of a new message (this is often referred to as the
2858 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2859 lines containing ``^A^A^A^A'' (four control-A's).
2861 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2862 and each message is stored in a separate file. The filename indicates the mes-
2863 sage number (however, this is may not correspond to the message number Mutt-ng
2864 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2865 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2866 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
2869 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
2870 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
2871 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
2872 way they are unique, even when two programs are writing the mailbox over NFS,
2874 The Mutt Next Generation E-Mail Client 58
2876 which means that no file locking is needed.
2878 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
2880 There are a number of built in shortcuts which refer to specific mailboxes.
2881 These shortcuts can be used anywhere you are prompted for a file or mailbox
2884 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.299 , page 158) (incoming)
2887 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.126 , page 117) file
2889 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.232 , page 142) file
2891 +
\bo ^ -- refers to the current mailbox
2893 +
\bo - or !! -- refers to the file you've last visited
2895 +
\bo ~ -- refers to your home directory
2897 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.65 , page 100) directory
2899 +
\bo @_
\ba_
\bl_
\bi_
\ba_
\bs -- refers to the _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 3.17 , page 36) as
2900 determined by the address of the alias
2902 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
2904 Mutt-ng has a few configuration options that make dealing with large amounts of
2905 mail easier. The first thing you must do is to let Mutt know what addresses
2906 you consider to be mailing lists (technically this does not have to be a mail-
2907 ing list, but that is what it is most often used for), and what lists you are
2908 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
2909 (section 3.12 , page 33) commands in your muttrc.
2911 Now that Mutt-ng knows what your mailing lists are, it can do several things,
2912 the first of which is the ability to show the name of a list through which you
2913 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
2914 This is useful to distinguish between personal and list mail in the same mail-
2915 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111) variable, the escape
2916 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
2917 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
2918 returns the name of the author).
2920 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
2921 quite large. Most people do not bother to remove the author of the message they
2922 are reply to from the list, resulting in two or more copies being sent to that
2923 person. The ``list-reply'' function, which by default is bound to ``L'' in the
2924 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
2925 mailing list addresses instead of all recipients (except as specified by Mail-
2927 The Mutt Next Generation E-Mail Client 59
2929 Followup-To, see below).
2931 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
2932 a list of recipients which includes one or several subscribed mailing lists,
2933 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 7.4.67 , page 101) option is set, mutt will
2934 generate a Mail-Followup-To header which contains all the recipients to whom
2935 you send this message, but not your address. This indicates that group-replies
2936 or list-replies (also known as ``followups'') to this message should only be
2937 sent to the original recipients of the message, and not separately to you -
2938 you'll receive your copy through one of the mailing lists you are subscribed
2941 Conversely, when group-replying or list-replying to a message which has a Mail-
2942 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
2943 (section 7.4.89 , page 106) configuration variable is set. Using list-reply
2944 will in this case also make sure that the reply goes to the mailing list, even
2945 if it's not specified in the list of recipients in the Mail-Followup-To.
2947 Note that, when header editing is enabled, you can create a Mail-Followup-To
2948 header manually. Mutt-ng will only auto-generate this header if it doesn't
2949 exist when you send the message.
2951 The other method some mailing list admins use is to generate a ``Reply-To''
2952 field which points back to the mailing list address rather than the author of
2953 the message. This can create problems when trying to reply directly to the
2954 author in private, since most mail clients will automatically reply to the
2955 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
2956 7.4.235 , page 142) variable to help decide which address to use. If set to
2957 _
\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
2958 use the address given in the ``Reply-To'' field, or reply directly to the
2959 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
2960 will be used when present.
2962 The ``X-Label:'' header field can be used to further identify mailing lists or
2963 list subject matter (or just to annotate messages individually). The
2964 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111) variable's ``%y'' and ``%Y''
2965 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
2966 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
2967 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
2968 can easily be inserted by procmail and other mail filtering agents.
2970 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 7.4.293 , page 156) the mail-
2971 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
2972 which all relate to the same subject. This is usually organized into a tree-
2973 like structure where a message and all of its replies are represented graphi-
2974 cally. If you've ever used a threaded news client, this is the same concept.
2975 It makes dealing with large volume mailing lists easier because you can easily
2976 delete uninteresting threads and quickly find topics of value.
2978 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2980 Mutt-ng has the ability to dynamically restructure threads that are broken
2982 The Mutt Next Generation E-Mail Client 60
2984 either by misconfigured software or bad behavior from some correspondents. This
2985 allows to clean your mailboxes formats) from these annoyances which make it
2986 hard to follow a discussion.
2988 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2990 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
2991 ences:" headers when replying to a message. This results in broken discussions
2992 because Mutt-ng has not enough information to guess the correct threading. You
2993 can fix this by tagging the reply, then moving to the parent message and using
2994 the ``link-threads'' function (bound to & by default). The reply will then be
2995 connected to this "parent" message.
2997 You can also connect multiple children at once, tagging them and using the tag-
2998 prefix command (';') or the auto_tag option.
3000 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
3002 On mailing lists, some people are in the bad habit of starting a new discussion
3003 by hitting "reply" to any message from the list and changing the subject to a
3004 totally unrelated one. You can fix such threads by using the ``break-thread''
3005 function (bound by default to #), which will turn the subthread starting from
3006 the current message into a whole different thread.
3008 _
\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
3010 RFC1894 defines a set of MIME content types for relaying information about the
3011 status of electronic mail messages. These can be thought of as ``return
3014 Users can make use of it in one of the following two ways:
3016 +
\bo Berkeley sendmail 8.8.x currently has some command line options in which
3017 the mail client can make requests as to what type of status messages
3020 +
\bo The SMTP support via libESMTP supports it, too.
3022 To support this, there are two variables:
3024 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 7.4.52 , page 97) is used to request receipts for
3025 different results (such as failed message, message delivered, etc.).
3027 +
\bo _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 7.4.53 , page 97) requests how much of your message
3028 should be returned with the receipt (headers or full message).
3030 Please see the reference chapter for possible values.
3032 _
\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)
3034 The Mutt Next Generation E-Mail Client 61
3036 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3037 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
3038 remote POP3 server and fetch mail for local browsing.
3040 You can access the remote POP3 mailbox by selecting the folder
3043 You can select an alternative port by specifying it with the server, i.e.:
3044 pop://popserver:port/.
3046 You can also specify different username for each folder, i.e.: pop://user-
3047 name@popserver[:port]/.
3049 Polling for new mail is more expensive over POP3 than locally. For this reason
3050 the frequency at which Mutt-ng will check for mail remotely can be controlled
3051 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.210 , page 137) variable, which defaults
3052 to every 60 seconds.
3054 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3055 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3056 rally requires that the server supports SSL encrypted connections. To access a
3057 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3058 name@]popserver[:port]/.
3060 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3061 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.208 , page 136), fetch all your
3062 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.299 , page 158).
3063 After this point, Mutt-ng runs exactly as if the mail had always been local.
3065 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3066 sider using a specialized program, such as fetchmail
3068 _
\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)
3070 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3071 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
3074 You can access the remote inbox by selecting the folder
3075 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3076 INBOX is the special name for your spool mailbox on the IMAP server. If you
3077 want to access another mail folder at the IMAP server, you should use
3078 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3081 You can select an alternative port by specifying it with the server, i.e.:
3082 imap://imapserver:port/INBOX.
3084 You can also specify different username for each folder, i.e.: imap://user-
3085 name@imapserver[:port]/INBOX.
3087 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3089 The Mutt Next Generation E-Mail Client 62
3091 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This natu-
3092 rally requires that the server supports SSL encrypted connections. To access a
3093 folder with IMAP/SSL, you should use imaps://[user-
3094 name@]imapserver[:port]/path/to/folder as your folder path.
3096 Pine-compatible notation is also supported, i.e. {[user-
3097 name@]imapserver[:port][/ssl]}path/to/folder
3099 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3100 correctly notice which separator is being used by the server and convert paths
3103 When browsing folders on an IMAP server, you can toggle whether to look at only
3104 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
3105 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.98 , page 108) vari-
3108 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3109 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.100 , page 109) and
3110 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.323 , page 165) variables.
3112 Note that if you are using mbox as the mail store on UW servers prior to
3113 v12.250, the server has been reported to disconnect a client if another client
3114 selects the same folder.
3116 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3118 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3119 mostly the same as the local file browser, with the following differences:
3121 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3122 followed by the symbol "+", indicating that the entry contains both mes-
3123 sages and subfolders. On Cyrus-like servers folders will often contain
3124 both messages and subfolders.
3126 +
\bo For the case where an entry can contain both messages and subfolders, the
3127 selection key (bound to enter by default) will choose to descend into the
3128 subfolder view. If you wish to view the messages in that folder, you must
3129 use view-file instead (bound to space by default).
3131 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3132 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3133 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3134 mally these are bound to s and u, respectively).
3136 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3138 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3139 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3140 tion for you poor exchange users out there, but it has yet to be integrated
3141 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3142 which allows you to log in to a public IMAP server without having an account.
3143 To use ANONYMOUS, simply make your username blank or "anonymous".
3145 The Mutt Next Generation E-Mail Client 63
3147 SASL is a special super-authenticator, which selects among several protocols
3148 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3149 available on your host and the server. Using some of these methods (including
3150 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3151 invisible to those teeming network snoops. It is the best option if you have
3152 it. To use it, you must have the Cyrus SASL library installed on your system
3153 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3155 Mutt-ng will try whichever methods are compiled in and available on the server,
3156 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3158 There are a few variables which control authentication:
3160 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.106 , page 110) - controls the username under
3161 which you request authentication on the IMAP server, for all authentica-
3162 tors. This is overridden by an explicit username in the mailbox path (i.e.
3163 by using a mailbox name of the form {user@host}).
3165 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.101 , page 109) - a password which you may pre-
3166 set, used by all authentication methods where a password is needed.
3168 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 7.4.92 , page 107) - a colon-delimited list
3169 of IMAP authentication methods to try, in the order you wish to try them.
3170 If specified, this overrides mutt's default (attempt everything, in the
3171 order listed above).
3173 _
\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)
3175 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3176 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3177 function from the index/pager which is by default bound to i.
3179 The Default newsserver can be obtained from the $NNTPSERVER environment vari-
3180 able. Like other news readers, info about subscribed newsgroups is saved in a
3181 file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 7.4.158 , page 125) variable.
3182 Article headers are cached and can be loaded from a file when a newsgroup is
3183 entered instead loading from newsserver; currently, this caching mechanism
3184 still is different from the header caching for maildir/IMAP.
3186 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3188 Especially for Usenet, people often ask for advanced filtering and scoring
3189 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3190 to use a killfile has been discussed in _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bs_
\bc_
\bo_
\br_
\bi_
\bn_
\bg (section 3.25 , page
3193 What has not been discusses in detail is mutt-ng's built-in realname filter.
3194 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3195 there are frequent request for such functionality. The solutions offered often
3196 are complicated regular expressions.
3198 In mutt-ng this is as easy as
3200 The Mutt Next Generation E-Mail Client 64
3204 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3205 fied a valid realname and a valid email address. Using
3209 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3210 ria which are very strict:
3212 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3213 editor.org/in-notes/rfc2822.txt>
3215 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3216 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3217 ``J. User'' and ``J. A. User'' aren't.
3219 +
\bo it's assumed that users are interested in reading their own mail and mail
3220 from people who they have defined an alias for so that those 2 groups of
3221 messages are excluded from the strict rules.
3223 _
\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)
3225 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3226 functionality. When configure was called with --with-libesmtp or the output
3227 muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP
3228 support includes support for Delivery Status Notification (see _
\bD_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\by _
\bS_
\bt_
\ba_
\bt_
\bu_
\bs
3229 _
\bN_
\bo_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 4.12 , page 59) section) as well as handling the 8BIT-
3230 MIME flag controlled via _
\b$_
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be (section 7.4.330 , page 166).
3232 To enable sending mail directly via SMTP without an MTA such as Postfix or
3233 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 7.4.288 , page 154)
3234 variable pointing to your SMTP server.
3236 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.292 ,
3237 page 155) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 7.4.289 , page 155) variables.
3239 Transport Encryption via the StartTLS command is also available. For this to
3240 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3241 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 7.4.291 , page 155) variable must be either set to
3242 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3243 supports it: for the second case, the connection will fail if it doesn't while
3244 switching back to unencrypted communication for the first one.
3246 Some mail providers require user's to set a particular envelope sender, i.e.
3248 The Mutt Next Generation E-Mail Client 65
3250 they allow for only one value which may not be what the user wants to send as
3251 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.287 ,
3252 page 154) may be used to set the envelope different from the From: header.
3254 _
\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)
3256 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3257 find managing all the authentication settings inconvenient and error-prone.
3258 The account-hook command may help. This hook works like folder-hook but is
3259 invoked whenever you access a remote mailbox (including inside the folder
3260 browser), not just when you open the mailbox.
3264 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3265 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3266 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3268 _
\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)
3270 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
3271 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
3272 start a WWW browser on one of them. This functionality is provided by the
3273 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3274 trib/ and the configuration commands:
3276 macro index \cb |urlview\n
3277 macro pager \cb |urlview\n
3279 _
\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)
3281 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3282 _
\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
3283 an arbitrary format, provided that the user has a script to convert from/to
3284 this format to one of the accepted.
3286 The most common use is to open compressed archived folders e.g. with gzip.
3288 In addition, the user can provide a script that gets a folder in an accepted
3289 format and appends its context to the folder in the user-defined format, which
3290 may be faster than converting the entire folder to the accepted format, append-
3291 ing to it and converting back to the user-defined format.
3293 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3294 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 66) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66))
3295 which define commands to uncompress and compress a folder and to append mes-
3296 sages to an existing compressed folder respectively.
3298 The Mutt Next Generation E-Mail Client 66
3302 open-hook \\.gz$ "gzip -cd %f > %t"
3303 close-hook \\.gz$ "gzip -c %t > %f"
3304 append-hook \\.gz$ "gzip -c %t >> %f"
3306 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-
3307 tion 4.19.3 , page 66), the folder will be open and closed again each time you
3308 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 66) (or give
3309 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3310 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) though you'll be able to append to the folder.
3312 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3313 accepted formats. In particular, if the file is empty, mutt supposes it is not
3314 compressed. This is important because it allows the use of programs that do not
3315 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3316 prising if your compressing script produces empty files. In this situation,
3317 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 7.4.242 , page 144), so that the compressed file
3318 will be removed if you delete all of the messages.
3320 _
\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
3322 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3324 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3325 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3327 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3328 parameters: %f, which is replaced with the (compressed) folder name, and %t
3329 which is replaced with the name of the temporary folder to which to write.
3331 %f and %t can be repeated any number of times in the command string, and all of
3332 the entries are replaced with the appropriate folder name. In addition, %% is
3333 replaced by %, as in printf, and any other %anything is left as is.
3335 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
3336 return non-zero exit status if it fails, so mutt knows something's wrong.
3340 open-hook \\.gz$ "gzip -cd %f > %t"
3342 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3344 _
\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
3346 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3348 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3349 4.19.1 , page 65) command after some changes were made to it.
3351 The Mutt Next Generation E-Mail Client 67
3353 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3354 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
3355 4.19.1 , page 65) command. Temporary folder in this case is the folder previ-
3356 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65) command.
3358 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
3359 non-zero exit status if it fails, so mutt knows something's wrong.
3363 close-hook \\.gz$ "gzip -c %t > %f"
3365 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3366 file can only be open in the readonly mode.
3368 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 66) is not called when you exit from the
3369 folder if the folder was not changed.
3371 _
\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
3373 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3375 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3376 is the command that can be used for appending to the folders whose names match
3377 _
\br_
\be_
\bg_
\be_
\bx_
\bp. It has the same format as in the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65)
3378 command. The temporary folder in this case contains the messages that are
3381 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
3382 non-zero exit status if it fails, so mutt knows something's wrong.
3386 append-hook \\.gz$ "gzip -c %t >> %f"
3388 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) is used, the folder is not opened,
3389 which saves time, but this means that we can not find out what the folder type
3390 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 7.4.127 , page 117)) type is always
3391 supposed (i.e. this is the format used for the temporary folder).
3393 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 ,
3394 page 66) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3395 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) is only for appending to existing folders.
3397 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3398 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3399 4.19.1 , page 65) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 66)respectively) each
3400 time you will add to it.
3402 The Mutt Next Generation E-Mail Client 68
3404 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3406 The compressed folders support can also be used to handle encrypted folders. If
3407 you want to encrypt a folder with PGP, you may want to use the following hooks:
3409 open-hook \\.pgp$ "pgp -f < %f > %t"
3410 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3412 Please note, that PGP does not support appending to an encrypted folder, so
3413 there is no append-hook defined.
3415 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3416 can be read by your system administrator. So think about the security aspects
3419 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3421 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3422 MUA. Every effort has been made to provide the functionality that the discern-
3423 ing MIME user requires, and the conformance to the standards wherever possible.
3424 When configuring Mutt-ng for MIME, there are two extra types of configuration
3425 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3426 ping of file extensions to IANA MIME types. The other is the mailcap file,
3427 which specifies the external commands to use for handling specific MIME types.
3429 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3431 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3432 (while viewing a message), the attachment menu and the compose menu.
3434 _
\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
3436 When you select a message from the index and view it in the pager, Mutt decodes
3437 the message to a text representation. Mutt-ng internally supports a number of
3438 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3439 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3440 variety of PGP MIME types, including PGP/MIME and application/pgp.
3442 Mutt-ng will denote attachments with a couple lines describing them. These
3443 lines are of the form:
3445 [-- Attachment #1: Description --]
3446 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3448 Where the Description is the description or filename given for the attachment,
3449 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3451 The Mutt Next Generation E-Mail Client 69
3453 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3455 [-- image/gif is unsupported (use 'v' to view this part) --]
3457 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3459 The default binding for view-attachments is `v', which displays the attachment
3460 menu for a message. The attachment menu displays a list of the attachments in
3461 a message. From the attachment menu, you can save, print, pipe, delete, and
3462 view attachments. You can apply these operations to a group of attachments at
3463 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3464 can also reply to the current message from this menu, and only the current
3465 attachment (or the attachments tagged) will be quoted in your reply. You can
3466 view attachments as text, or view them using the mailcap viewer definition.
3468 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3469 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3470 of type message/rfc822.
3472 See the help on the attachment menu for more information.
3474 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3476 The compose menu is the menu you see before you send a message. It allows you
3477 to edit the recipient list, the subject, and other aspects of your message. It
3478 also contains a list of the attachments of your message, including the main
3479 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3480 review, and rename an attachment or a list of tagged attachments. You can also
3481 modifying the attachment information, notably the type, encoding and descrip-
3484 Attachments appear as follows:
3486 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3487 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3489 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3490 or canceling) the message. It can be toggled with the toggle-unlink command
3491 (default: u). The next field is the MIME content-type, and can be changed with
3492 the edit-type command (default: ^T). The next field is the encoding for the
3493 attachment, which allows a binary message to be encoded for transmission on
3494 7bit links. It can be changed with the edit-encoding command (default: ^E).
3495 The next field is the size of the attachment, rounded to kilobytes or
3496 megabytes. The next field is the filename, which can be changed with the
3497 rename-file command (default: R). The final field is the description of the
3498 attachment, and can be changed with the edit-description command (default: d).
3500 _
\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
3502 When you add an attachment to your mail message, Mutt-ng searches your personal
3504 The Mutt Next Generation E-Mail Client 70
3506 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3507 /usr/local/share/mutt/mime.types or /etc/mime.types
3509 The mime.types file consist of lines containing a MIME type and a space sepa-
3510 rated list of extensions. For example:
3512 application/postscript ps eps
3514 audio/x-aiff aif aifc aiff
3516 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3517 tain most of the MIME types you are likely to use.
3519 If Mutt-ng can not determine the mime type by the extension of the file you
3520 attach, it will look at the file. If the file is free of binary information,
3521 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3522 the file contains binary information, then Mutt-ng will mark it as applica-
3523 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3524 attachment by using the edit-type command from the compose menu (default: ^T).
3525 The MIME type is actually a major mime type followed by the sub-type, separated
3526 by a '/'. 6 major types: application, text, image, video, audio, and model have
3527 been approved after various internet discussions. Mutt-ng recognises all of
3528 these if the appropriate entry is found in the mime.types file. It also recog-
3529 nises other major mime types, such as the chemical type that is widely used in
3530 the molecular modelling community to pass molecular data in various forms to
3531 various molecular viewers. Non-recognised mime types should only be used if the
3532 recipient of the message is likely to be expecting such attachments.
3534 _
\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
3536 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3537 format specified in Appendix A of RFC 1524. This file format is commonly
3538 referred to as the mailcap format. Many MIME compliant programs utilize the
3539 mailcap format, allowing you to specify handling for all MIME types in one
3540 place for all programs. Programs known to use this format include Netscape,
3541 XMosaic, lynx and metamail.
3543 In order to handle various MIME types that Mutt-ng can not handle internally,
3544 Mutt-ng parses a series of external configuration files to find an external
3545 handler. The default search string for these files is a colon delimited list
3548 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3550 where $HOME is your home directory.
3552 In particular, the metamail distribution will install a mailcap file, usually
3553 as /usr/local/etc/mailcap, which contains some baseline entries.
3555 The Mutt Next Generation E-Mail Client 71
3557 _
\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
3559 A mailcap file consists of a series of lines which are comments, blank, or def-
3562 A comment line consists of a # character followed by anything you want.
3564 A blank line is blank.
3566 A definition line consists of a content type, a view command, and any number of
3567 optional fields. Each field of a definition line is divided by a semicolon ';'
3570 The content type is specified in the MIME standard type/subtype method. For
3571 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3572 mat includes two formats for wildcards, one using the special '*' subtype, the
3573 other is the implicit wild, where you only include the major type. For exam-
3574 ple, image/*, or video, will match all image types and video types, respec-
3577 The view command is a Unix command for viewing the type specified. There are
3578 two different types of commands supported. The default is to send the body of
3579 the MIME message to the command on stdin. You can change this behavior by using
3580 %s as a parameter to your view command. This will cause Mutt-ng to save the
3581 body of the MIME message to a temporary file, and then call the view command
3582 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3583 will turn over the terminal to the view program until the program quits, at
3584 which time Mutt will remove the temporary file if it exists.
3586 So, in the simplest form, you can send a text/plain message to the external
3587 pager more on stdin:
3591 Or, you could send the message as a file:
3595 Perhaps you would like to use lynx to interactively view a text/html message:
3599 In this case, lynx does not support viewing a file from stdin, so you must use
3600 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
3601 _
\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
3602 _
\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
3603 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3605 On the other hand, maybe you don't want to use lynx interactively, you just
3606 want to have it convert the text/html to text/plain, then you can use:
3608 The Mutt Next Generation E-Mail Client 72
3610 text/html; lynx -dump %s | more
3612 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3613 text formats, then you would use the following:
3618 This is the simplest form of a mailcap file.
3620 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3622 The interpretation of shell meta-characters embedded in MIME parameters can
3623 lead to security problems in general. Mutt-ng tries to quote parameters in
3624 expansion of %s syntaxes properly, and avoids risky characters by substituting
3625 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.118 , page 115) variable.
3627 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3628 there are other applications parsing mailcap, maybe taking less care of it.
3629 Therefore you should pay attention to the following rules:
3631 _
\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
3632 double quotes. Mutt-ng does this for you, the right way, as should any other
3633 program which interprets mailcap. Don't put them into backtick expansions. Be
3634 highly careful with eval statements, and avoid them if possible at all. Trying
3635 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3636 tive to correct quoting in the first place.
3638 If you have to use the %-expandos' values in context where you need quoting or
3639 backtick expansions, put that value into a shell variable and reference the
3640 shell variable where necessary, as in the following example (using $charset
3641 inside the backtick expansion is safe, since it is not itself subject to any
3644 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3645 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3647 _
\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
3649 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3651 In addition to the required content-type and view command fields, you can add
3652 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3653 nizes the following optional fields:
3656 This flag tells Mutt-ng that the command passes possibly large
3657 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3658 (either the internal pager or the external pager defined by the
3659 pager variable) on the output of the view command. Without this
3661 The Mutt Next Generation E-Mail Client 73
3663 flag, Mutt-ng assumes that the command is interactive. One could
3664 use this to replace the pipe to more in the lynx -dump example in
3667 text/html; lynx -dump %s ; copiousoutput
3669 This will cause lynx to format the text/html output as text/plain
3670 and Mutt-ng will use your standard pager to display the results.
3673 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (sec-
3674 tion 5.4 , page 75), in order to decide whether it should honor
3675 the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.337 , page 168) variable
3676 or not. When an attachment is viewed using an interactive program,
3677 and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl flag, Mutt-
3678 ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 7.4.337 , page 168) and the exit
3679 status of the program to decide if it will ask you to press a key
3680 after the external program has exited. In all other situations it
3681 will not prompt you for a key.
3684 This flag specifies the command to use to create a new attachment
3685 of a specific MIME type. Mutt-ng supports this from the compose
3688 composetyped=<command>
3689 This flag specifies the command to use to create a new attachment
3690 of a specific MIME type. This command differs from the compose
3691 command in that mutt will expect standard MIME headers on the data.
3692 This can be used to specify parameters, filename, description, etc.
3693 for a new attachment. Mutt-ng supports this from the compose
3697 This flag specifies the command to use to print a specific MIME
3698 type. Mutt-ng supports this from the attachment and compose menus.
3701 This flag specifies the command to use to edit a specific MIME
3702 type. Mutt-ng supports this from the compose menu, and also uses
3703 it to compose new attachments. Mutt-ng will default to the defined
3704 editor for text attachments.
3706 nametemplate=<template>
3707 This field specifies the format for the file denoted by %s in the
3708 command fields. Certain programs will require a certain file
3709 extension, for instance, to correctly view a file. For instance,
3710 lynx will only interpret a file as text/html if the file ends in
3711 .html. So, you would specify lynx as a text/html viewer with a
3712 line in the mailcap file like:
3714 text/html; lynx %s; nametemplate=%s.html
3716 The Mutt Next Generation E-Mail Client 74
3719 This field specifies a command to run to test whether this mailcap
3720 entry should be used. The command is defined with the command
3721 expansion rules defined in the next section. If the command
3722 returns 0, then the test passed, and Mutt-ng uses this entry. If
3723 the command returns non-zero, then the test failed, and Mutt-ng
3724 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
3725 _
\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:
3727 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3730 In this example, Mutt-ng will run the program RunningX which will
3731 return 0 if the X Window manager is running, and non-zero if it
3732 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3733 display the text/html object. If RunningX doesn't return 0, then
3734 Mutt-ng will go on to the next entry and use lynx to display the
3737 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3739 When searching for an entry in the mailcap file, Mutt-ng will search for the
3740 most useful entry for its purpose. For instance, if you are attempting to
3741 print an image/gif, and you have the following entries in your mailcap file,
3742 Mutt-ng will search for an entry with the print command:
3745 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3748 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3751 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) to denote
3752 two commands for viewing an attachment, one to be viewed automatically, the
3753 other to be viewed interactively from the attachment menu. In addition, you
3754 can then use the test feature to determine which viewer to use interactively
3755 depending on your environment.
3757 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3758 text/html; lynx %s; nametemplate=%s.html
3759 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3761 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 75), Mutt-ng will choose the third entry
3762 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3763 program RunningX to determine if it should use the first entry. If the program
3764 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3766 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3768 The various commands defined in the mailcap files are passed to the /bin/sh
3770 The Mutt Next Generation E-Mail Client 75
3772 shell using the system() function. Before the command is passed to /bin/sh -c,
3773 it is parsed to expand various special parameters with information from Mutt-
3774 ng. The keywords Mutt-ng expands are:
3777 As seen in the basic mailcap section, this variable is expanded to
3778 a filename specified by the calling program. This file contains
3779 the body of the message to view/print/edit or where the composing
3780 program should place the results of composition. In addition, the
3781 use of this keyword causes Mutt-ng to not pass the body of the mes-
3782 sage to the view/print/edit program on stdin.
3785 Mutt-ng will expand %t to the text representation of the content
3786 type of the message in the same form as the first parameter of the
3787 mailcap definition line, ie text/html or image/gif.
3790 Mutt-ng will expand this to the value of the specified parameter
3791 from the Content-Type: line of the mail message. For instance, if
3792 Your mail message contains:
3794 Content-Type: text/plain; charset=iso-8859-1
3796 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3797 metamail mailcap file uses this feature to test the charset to
3798 spawn an xterm using the right charset to view the message.
3801 This will be replaced by a %
3803 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3804 1524. The main purpose of these parameters is for multipart messages, which is
3805 handled internally by Mutt-ng.
3807 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3809 This mailcap file is fairly simple and standard:
3811 # I'm always running X :)
3812 video/*; xanim %s > /dev/null
3813 image/*; xv %s > /dev/null
3815 # I'm always running netscape (if my computer had more memory, maybe)
3816 text/html; netscape -remote 'openURL(%s)'
3818 This mailcap file shows quite a number of examples:
3820 The Mutt Next Generation E-Mail Client 76
3822 # Use xanim to view all videos Xanim produces a header on startup,
3823 # send that to /dev/null so I don't see it
3824 video/*; xanim %s > /dev/null
3826 # Send html to a running netscape by remote
3827 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3829 # If I'm not running netscape but I am running X, start netscape on the
3831 text/html; netscape %s; test=RunningX
3833 # Else use lynx to view it as text
3836 # This version would convert the text/html to text/plain
3837 text/html; lynx -dump %s; copiousoutput
3839 # I use enscript to print text in two columns to a page
3840 text/*; more %s; print=enscript -2Gr %s
3842 # Netscape adds a flag to tell itself to view jpegs internally
3843 image/jpeg;xv %s; x-mozilla-flags=internal
3845 # Use xv to view images if I'm running X
3846 # In addition, this uses the \ to extend the line and set my editor
3848 image/*;xv %s; test=RunningX; \
3851 # Convert images to text using the netpbm tools
3852 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3853 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3855 # Send excel spreadsheets to my NT box
3856 application/ms-excel; open.pl %s
3858 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3860 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3861 viewer defined in the mailcap file, Mutt-ng has support for automatically view-
3862 ing MIME attachments while in the pager.
3864 To work, you must define a viewer in the mailcap file which uses the copi-
3865 ousoutput option to denote that it is non-interactive. Usually, you also use
3866 the entry to convert the attachment to a text representation which you can view
3869 You then use the auto_view muttrc command to list the content-types that you
3870 wish to view automatically.
3872 For instance, if you set auto_view to:
3874 The Mutt Next Generation E-Mail Client 77
3876 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3878 Mutt-ng could use the following mailcap entries to automatically view attach-
3879 ments of these types.
3881 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3882 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3883 application/x-gunzip; gzcat; copiousoutput
3884 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3885 application/postscript; ps2ascii %s; copiousoutput
3887 ``unauto_view'' can be used to remove previous entries from the autoview list.
3888 This can be used with message-hook to autoview messages based on size, etc.
3889 ``unauto_view *'' will remove all previous entries.
3891 _
\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
3893 Mutt-ng has some heuristics for determining which attachment of a multi-
3894 part/alternative type to display. First, mutt will check the alternative_order
3895 list to determine if one of the available types is preferred. The alterna-
3896 tive_order list consists of a number of MIME types in order, including support
3897 for implicit and explicit wildcards, for example:
3899 alternative_order text/enriched text/plain text application/postscript image/*
3901 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
3902 5.4 , page 75), and use that. Failing that, Mutt-ng will look for any text
3903 type. As a last attempt, mutt will look for any type it knows how to handle.
3905 To remove a MIME type from the alternative_order list, use the unalterna-
3908 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
3910 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
3911 treated according to their mailcap entry. This option is designed to deal with
3912 binary types such as application/octet-stream. When an attachment's mime-type
3913 is listed in mime_lookup, then the extension of the filename will be compared
3914 to the list of extensions in the mime.types file. The mime-type associated
3915 with this extension will then be used to process the attachment according to
3916 the rules in the mailcap file and according to any other configuration options
3917 (such as auto_view) specified. Common usage would be:
3919 mime_lookup application/octet-stream application/X-Lotus-Manuscript
3921 In addition, the unmime_lookup command may be used to disable this feature for
3923 The Mutt Next Generation E-Mail Client 78
3925 any particular mime-type if it had been set, for example, in a global muttrc.
3927 _
\b6_
\b. _
\bS_
\be_
\bc_
\bu_
\br_
\bi_
\bt_
\by _
\bC_
\bo_
\bn_
\bs_
\bi_
\bd_
\be_
\br_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
3929 First of all, mutt-ng contains no security holes included by intention but may
3930 contain unknown security holes. As a consequence, please run mutt-ng only with
3931 as few permissions as possible.
3933 Please do not run mutt-ng as the super user.
3935 When configuring mutt-ng, there're some points to note about secure setups.
3937 In practice, mutt-ng can be easily made as vulnerable as even the most insecure
3938 mail user agents (in their default configuration) just by changing mutt-ng's
3939 configuration files: it then can execute arbitrary programs and scripts
3940 attached to messages, send out private data on its own, etc. Although this is
3941 not believed to the common type of setup, please read this chapter carefully.
3943 _
\b6_
\b._
\b1 _
\bP_
\ba_
\bs_
\bs_
\bw_
\bo_
\br_
\bd_
\bs
3945 Although mutt-ng can be told the various passwords for accounts, please never
3946 store passwords in configuration files. Besides the fact that the system's
3947 operator can always read them, you could forget to replace the actual password
3948 with asterisks when reporting a bug or asking for help via, for example, a
3949 mailing list so that your mail including your password could be archived by
3950 internet search engines, etc. Please never store passwords on disk.
3952 _
\b6_
\b._
\b2 _
\bT_
\be_
\bm_
\bp_
\bo_
\br_
\ba_
\br_
\by _
\bF_
\bi_
\bl_
\be_
\bs
3954 Mutt-ng uses many temporary files for viewing messages, verifying digital sig-
3955 natures, etc. The _
\b$_
\bu_
\bm_
\ba_
\bs_
\bk (section 7.4.328 , page 166) variable can be used to
3956 change the default permissions of these files. Please only change it if you
3957 really know what you are doing. Also, a different location for these files may
3958 be desired which can be changed via the _
\b$_
\bt_
\bm_
\bp_
\bd_
\bi_
\br (section 7.4.324 , page 165)
3961 _
\b6_
\b._
\b3 _
\bI_
\bn_
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bi_
\bo_
\bn _
\bL_
\be_
\ba_
\bk_
\bs
3963 _
\b6_
\b._
\b3_
\b._
\b1 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bI_
\bD_
\b: _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
3965 In the default configuration, mutt-ng will leak some information to the outside
3966 world when sending messages: the generation of Message-ID: headers includes a
3967 step counter which is increased (and rotated) with every message sent. If you'd
3968 like to hide this information probably telling others how many mail you sent in
3969 which time, you at least need to remove the %P expando from the default setting
3970 of the _
\b$_
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.144 , page 120) variable. Please make sure
3971 that you really know how local parts of these Message-ID: headers are composed.
3973 The Mutt Next Generation E-Mail Client 79
3975 _
\b6_
\b._
\b3_
\b._
\b2 _
\bm_
\ba_
\bi_
\bl_
\bt_
\bo_
\b:_
\b-_
\bs_
\bt_
\by_
\bl_
\be _
\bl_
\bi_
\bn_
\bk_
\bs
3977 As mutt-ng be can be set up to be the mail client to handle mailto: style links
3978 in websites, there're security considerations, too. To keep the old behavior by
3979 default, mutt-ng will be strict in interpreting them which means that arbitrary
3980 header fields can be embedded in these links which could override existing
3981 header fields or attach arbitrary files. This may be problematic if the
3982 _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98) variable is _
\bu_
\bn_
\bs_
\be_
\bt, i.e. the user
3983 doesn't want to see header fields while editing the message.
3985 For example, following a link like
3987 mailto:joe@host?Attach=~/.gnupg/secring.gpg
3989 will send out the user's private gnupg keyring to joe@host if the user doesn't
3990 follow the information on screen carefully enough.
3992 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.312 , page 162) variable, mutt-
3995 +
\bo be less strict when interpreting these links by prepending a X-Mailto-
3996 string to all header fields embedded in such a link _
\ba_
\bn_
\bd
3998 +
\bo turn on the _
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98) variable by force to
3999 let the user see all the headers (because they still may leak informa-
4002 _
\b6_
\b._
\b4 _
\bE_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl _
\ba_
\bp_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn_
\bs
4004 Mutt-ng in many places has to rely on external applications or for convenience
4005 supports mechanisms involving external applications.
4007 _
\b6_
\b._
\b4_
\b._
\b1 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
4009 One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be
4010 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-
4011 cap files (see the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh (section 7.4.117 , page 115) variable for
4014 These utilities may have a variety of security vulnerabilities, including over-
4015 writing of arbitrary files, information leaks or other exploitable bugs. These
4016 vulnerabilities may go unnoticed by the user, especially when they are called
4017 automatically (and without interactive prompting) from the mailcap file(s).
4018 When using mutt-ng's autoview mechanism in combination with mailcap files,
4019 please be sure to...
4021 +
\bo manually select trustworth applications with a reasonable calling sequence
4023 +
\bo periodically check the contents of mailcap files, especially after soft-
4024 ware installations or upgrades
4026 The Mutt Next Generation E-Mail Client 80
4028 +
\bo keep the software packages referenced in the mailcap file up to date
4030 +
\bo leave the _
\b$_
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 7.4.118 , page 115) variable in its
4031 default state to restrict mailcap expandos to a safe set of characters
4033 _
\b6_
\b._
\b4_
\b._
\b2 _
\bO_
\bt_
\bh_
\be_
\br
4035 Besides the mailcap mechanism, mutt-ng uses a number of other external utili-
4038 The same security considerations apply for these as for tools involved via
4039 mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with
4040 compressed folders support if the uncompressed mailbox is too large for the
4041 disk it is saved to.)
4043 As already noted, most of these problems are not built in but caused by wrong
4044 configuration, so please check your configuration.
4046 _
\b7_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
4048 _
\b7_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
4050 Running mutt with no arguments will make Mutt-ng attempt to read your spool
4051 mailbox. However, it is possible to read other mailboxes and to send messages
4052 from the command line as well.
4055 -a attach a file to a message
4056 -b specify a blind carbon-copy (BCC) address
4057 -c specify a carbon-copy (Cc) address
4058 -D print the value of all variables on stdout
4059 -e specify a config command to be run after initialization files are read
4060 -f specify a mailbox to load
4061 -F specify an alternate file to read initialization commands
4062 -h print help on command line options
4063 -H specify a draft file from which to read a header and body
4064 -i specify a file to include in a message composition
4065 -m specify a default mailbox type
4066 -n do not read the system Muttngrc
4067 -p recall a postponed message
4068 -Q query a configuration variable
4069 -R open mailbox in read-only mode
4070 -s specify a subject (enclose in quotes if it contains spaces)
4071 -v show version number and compile-time definitions
4072 -x simulate the mailx(1) compose mode
4073 -y show a menu containing the files specified by the mailboxes command
4074 -z exit immediately if there are no messages in the mailbox
4075 -Z open the first folder with new message,exit immediately if none
4077 To read messages in a mailbox
4079 The Mutt Next Generation E-Mail Client 81
4081 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
4083 To compose a new message
4085 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-
4086 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
4088 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
4089 rect input from the file you wish to send. For example,
4091 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
4093 This command will send a message to ``professor@bigschool.edu'' with a subject
4094 of ``data set for run #2''. In the body of the message will be the contents of
4095 the file ``~/run2.dat''.
4097 _
\b7_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
4099 The Mutt Next Generation E-Mail Client 82
4102 ~b EXPR messages which contain EXPR in the message body
4103 ~B EXPR messages which contain EXPR in the whole message
4104 ~c USER messages carbon-copied to USER
4105 ~C EXPR message is either to: or cc: EXPR
4107 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
4109 ~e EXPR message which contains EXPR in the ``Sender'' field
4111 ~f USER messages originating from USER
4112 ~g cryptographically signed messages
4113 ~G cryptographically encrypted messages
4114 ~H EXPR messages with a spam attribute matching EXPR
4115 ~h EXPR messages which contain EXPR in the message header
4116 ~k message contains PGP key material
4117 ~i ID message which match ID in the ``Message-ID'' field
4118 ~L EXPR message is either originated or received by EXPR
4119 ~l message is addressed to a known mailing list
4120 ~m [MIN]-[MAX] message in the range MIN to MAX *)
4121 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
4124 ~p message is addressed to you (consults alternates)
4125 ~P message is from you (consults alternates)
4126 ~Q messages which have been replied to
4128 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
4129 ~S superseded messages
4130 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
4132 ~t USER messages addressed to USER
4134 ~v message is part of a collapsed thread.
4135 ~V cryptographically verified messages
4136 ~w EXPR messages which contain EXPR in the `Newsgroups' field
4137 (if compiled with NNTP support)
4138 ~x EXPR messages which contain EXPR in the `References' field
4139 ~y EXPR messages which contain EXPR in the `X-Label' field
4140 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
4141 ~= duplicated messages (see $duplicate_threads)
4142 ~$ unreferenced messages (requires threaded view)
4143 ~* ``From'' contains realname and (syntactically) valid
4144 address (excluded are addresses matching against
4145 alternates or any alias)
4147 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
4148 45). Special attention has to be made when using regular expressions inside of
4149 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
4150 level of backslash (\), which is normally used for quoting. If it is your
4151 intention to use a backslash in the regular expression, you will need to use
4152 two backslashes instead (\\).
4154 The Mutt Next Generation E-Mail Client 83
4156 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
4158 _
\b7_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
4160 The following are the commands understood by mutt.
4162 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 64) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4164 +
\bo _
\ba_
\bl_
\bi_
\ba_
\bs (section 3.3 , page 23) _
\bk_
\be_
\by _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ , _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs, ... ]
4166 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.3 , page 23) [ * | _
\bk_
\be_
\by ... ]
4168 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.10 , page 30) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4170 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.10 , page 30) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4172 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4174 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4176 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 66) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4178 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4180 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4182 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4184 +
\bo _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.5 , page 26) _
\ba_
\bl_
\bi_
\ba_
\bs _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4186 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 66) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4188 +
\bo _
\bc_
\bo_
\bl_
\bo_
\br (section 3.8 , page 27) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\bf_
\bo_
\br_
\be_
\bg_
\br_
\bo_
\bu_
\bn_
\bd _
\bb_
\ba_
\bc_
\bk_
\bg_
\br_
\bo_
\bu_
\bn_
\bd [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4190 +
\bo _
\bu_
\bn_
\bc_
\bo_
\bl_
\bo_
\br (section 3.8 , page 27) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4192 +
\bo _
\be_
\bx_
\be_
\bc (section 3.24 , page 38) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4194 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 36) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4196 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4198 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 26) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4200 +
\bo _
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.16 , page 35) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4202 +
\bo _
\bu_
\bn_
\bh_
\bd_
\br_
\b__
\bo_
\br_
\bd_
\be_
\br (section 3.16 , page 35) _
\bh_
\be_
\ba_
\bd_
\be_
\br [ _
\bh_
\be_
\ba_
\bd_
\be_
\br ... ]
4204 +
\bo _
\bi_
\bc_
\bo_
\bn_
\bv_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.5 , page 26) _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt _
\bl_
\bo_
\bc_
\ba_
\bl_
\b-_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4206 +
\bo _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.9 , page 30) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4208 The Mutt Next Generation E-Mail Client 84
4210 +
\bo _
\bu_
\bn_
\bi_
\bg_
\bn_
\bo_
\br_
\be (section 3.9 , page 30) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4212 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.12 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4214 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.12 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4216 +
\bo _
\bm_
\ba_
\bc_
\br_
\bo (section 3.7 , page 27) _
\bm_
\be_
\bn_
\bu _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be [ _
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn ]
4218 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.14 , page 34) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4220 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 34) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4222 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 37) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4224 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4226 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 76) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4228 +
\bo _
\bm_
\bo_
\bn_
\bo (section 3.8 , page 27) _
\bo_
\bb_
\bj_
\be_
\bc_
\bt _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\be [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ]
4230 +
\bo _
\bu_
\bn_
\bm_
\bo_
\bn_
\bo (section 3.8 , page 27) _
\bi_
\bn_
\bd_
\be_
\bx _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4232 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 35) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4234 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 35) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4236 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 65) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4238 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4240 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.23 , page 38) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4242 +
\bo _
\br_
\be_
\bs_
\be_
\bt (section 3.27 , page 41) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4244 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4246 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.25 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4248 +
\bo _
\bu_
\bn_
\bs_
\bc_
\bo_
\br_
\be (section 3.25 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
4250 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 37) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4252 +
\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
4254 +
\bo _
\bs_
\be_
\bt (section 3.27 , page 41) [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4256 +
\bo _
\bu_
\bn_
\bs_
\be_
\bt (section 3.27 , page 41) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4258 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page 42) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4260 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.26 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4262 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.26 , page 40) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4264 The Mutt Next Generation E-Mail Client 85
4266 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4268 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 , page 33) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4270 +
\bo _
\bt_
\bo_
\bg_
\bg_
\bl_
\be (section 3.27 , page 41) _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
4272 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.29 , page 43) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4274 _
\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
4276 The following list contains all variables which, in the process of providing
4277 more consistency, have been renamed and are partially even removed already. The
4278 left column contains the old synonym variables, the right column the full/new
4281 The Mutt Next Generation E-Mail Client 86
4283 edit_hdrs edit_headers
4284 forw_decode forward_decode
4285 forw_format forward_format
4286 forw_quote forward_quote
4287 hdr_format index_format
4288 indent_str indent_string
4289 mime_fwd mime_forward
4290 msg_format message_format
4291 pgp_autosign crypt_autosign
4292 pgp_autoencrypt crypt_autoencrypt
4293 pgp_replyencrypt crypt_replyencrypt
4294 pgp_replysign crypt_replysign
4295 pgp_replysignencrypted crypt_replysignencrypted
4296 pgp_verify_sig crypt_verify_sig
4297 pgp_create_traditional pgp_autoinline
4298 pgp_auto_traditional pgp_replyinline
4299 forw_decrypt forward_decrypt
4300 smime_sign_as smime_default_key
4301 post_indent_str post_indent_string
4302 print_cmd print_command
4303 shorten_hierarchy sidebar_shorten_hierarchy
4304 ask_followup_to nntp_ask_followup_to
4305 ask_x_comment_to nntp_ask_x_comment_to
4306 catchup_newsgroup nntp_catchup
4307 followup_to_poster nntp_followup_to_poster
4308 group_index_format nntp_group_index_format
4310 mime_subject nntp_mime_subject
4311 news_cache_dir nntp_cache_dir
4312 news_server nntp_host
4314 nntp_poll nntp_mail_check
4315 pop_checkinterval pop_mail_check
4316 post_moderated nntp_post_moderated
4317 save_unsubscribed nntp_save_unsubscribed
4318 show_new_news nntp_show_new_news
4319 show_only_unread nntp_show_only_unread
4320 x_comment_to nntp_x_comment_to
4321 smtp_auth_username smtp_user
4322 smtp_auth_password smtp_pass
4324 The contrib subdirectory contains a script named update-config.pl which eases
4327 A complete list of current variables follows.
4329 _
\b7_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4335 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4337 The Mutt Next Generation E-Mail Client 87
4339 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4340 subject given at the subject prompt will never be aborted.
4342 _
\b7_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4348 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4349 body if no changes are made to the file (this check only happens after the
4350 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4352 _
\b7_
\b._
\b4_
\b._
\b3 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4356 Default: '~/.muttngrc'
4358 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4359 tion 2.5.4 , page 11)'' function.
4361 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4362 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page 42)'' command for it to be executed.
4364 _
\b7_
\b._
\b4_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4368 Default: '%4n %2f %t %-10a %r'
4370 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4371 ing printf(3)-style sequences are available:
4377 flags - currently, a 'd' for an alias marked for deletion
4383 address which alias expands to
4386 character which indicates if the alias is tagged for inclusion
4388 _
\b7_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4394 The Mutt Next Generation E-Mail Client 88
4396 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4397 or base64 encoding when sending mail.
4399 _
\b7_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4405 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4406 sages) are to be interpreted. Messages containing these codes are rare, but if
4407 this option is set, their text will be colored accordingly. Note that this may
4408 override your color choices, and even present a security problem, since a mes-
4409 sage could include a line like ``[-- PGP output follows ...' and give it the
4410 same color as your attachment color.
4412 _
\b7_
\b._
\b4_
\b._
\b7 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4418 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4419 instead of highlighting the whole line. On slow network or modem links this
4420 will make response faster because there is less that has to be redrawn on the
4421 screen when moving to the next or previous entries in the menu.
4423 _
\b7_
\b._
\b4_
\b._
\b8 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4429 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4430 attachment trees, instead of the default ACS characters.
4432 _
\b7_
\b._
\b4_
\b._
\b9 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4438 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4439 editing an outgoing message.
4441 _
\b7_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bk_
\bc_
\bc
4447 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4448 the body of an outgoing message.
4450 The Mutt Next Generation E-Mail Client 89
4452 _
\b7_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4458 This variable is a colon-separated list of character encoding schemes for mes-
4459 sages without character encoding indication. Header field values and message
4460 body content without character encoding indication would be assumed that they
4461 are written in one of this list. By default, all the header fields and message
4462 body without any charset indication are assumed to be in us-ascii.
4464 For example, Japanese users might prefer this:
4466 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4468 However, only the first content is valid for the message body. This variable
4469 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 7.4.313 , page 163) is unset.
4471 _
\b7_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4475 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4477 This variable describes the format of the ``attachment'' menu. The following
4478 printf(3)-style sequences are understood:
4484 requires charset conversion (n or c)
4493 MIME Content-Transfer-Encoding: header field
4499 MIME Content-Disposition: header field (I=inline, A=attachment)
4507 The Mutt Next Generation E-Mail Client 90
4519 graphic tree characters
4522 unlink (=to delete) flag
4525 right justify the rest of the string and pad with character 'X'
4528 pad to the end of the line with character 'X'
4530 _
\b7_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4536 The separator to add between attachments when operating (saving, printing, pip-
4537 ing, etc) on a list of tagged attachments.
4539 _
\b7_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4545 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4546 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4547 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 7.4.13 ,
4548 page 89)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4549 operate on the attachments one by one.
4551 _
\b7_
\b._
\b4_
\b._
\b1_
\b5 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4555 Default: 'On %d, %n wrote:'
4557 This is the string that will precede a message which has been included in a
4558 reply. For a full listing of defined printf(3)-like sequences see the section
4559 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111)''.
4561 _
\b7_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4563 The Mutt Next Generation E-Mail Client 91
4569 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4570 all tagged messages (if there are any). When unset, you must first use the
4571 ``tag-prefix'' function (default: ';') to make the next function apply to all
4574 _
\b7_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4580 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98)'', Mutt-ng will
4581 skip the initial send-menu and allow you to immediately begin editing the body
4582 of your message. The send-menu may still be accessed once you have finished
4583 editing the body of your message.
4585 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 7.4.61 , page 99)''.
4587 _
\b7_
\b._
\b4_
\b._
\b1_
\b8 _
\bb_
\be_
\be_
\bp
4593 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4595 _
\b7_
\b._
\b4_
\b._
\b1_
\b9 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4601 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4602 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4603 tion 7.4.18 , page 90)'' variable.
4605 _
\b7_
\b._
\b4_
\b._
\b2_
\b0 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4611 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4612 you don't get asked if you want to bounce a message. Setting this variable to
4613 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4616 _
\b7_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4620 The Mutt Next Generation E-Mail Client 92
4624 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4625 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4627 _
\b7_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4633 When this variable is set, mutt will place the cursor at the beginning of the
4634 current line in menus, even when the arrow_cursor variable is unset, making it
4635 easier for blind persons using Braille displays to follow these menus. The
4636 option is disabled by default because many visual terminals don't permit making
4637 the cursor invisible.
4639 _
\b7_
\b._
\b4_
\b._
\b2_
\b3 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4643 Default: '~/.mutt_certificates'
4645 Availability: SSL or GNUTLS
4647 This variable specifies the file where the certificates you trust are saved.
4648 When an unknown certificate is encountered, you are asked if you accept it or
4649 not. If you accept it, the certificate can also be saved in this file and fur-
4650 ther connections are automatically accepted.
4652 You can also manually add CA certificates in this file. Any server certificate
4653 that is signed with one of these CA certificates are also automatically
4656 Example: set certificate_file=~/.muttng/certificates
4658 _
\b7_
\b._
\b4_
\b._
\b2_
\b4 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4664 Character set your terminal uses to display and enter textual data.
4666 _
\b7_
\b._
\b4_
\b._
\b2_
\b5 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4672 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4674 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4675 Especially with MH mailboxes, this operation can take quite some time since it
4677 The Mutt Next Generation E-Mail Client 93
4679 involves scanning the directory and checking each file to see if it has already
4680 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4683 _
\b7_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4689 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4692 _
\b7_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4696 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4698 Controls the format of the status line displayed in the ``compose'' menu. This
4699 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.310 , page 160)'', but has
4700 its own set of printf(3)-like sequences:
4703 total number of attachments
4709 approximate size (in bytes) of the current message
4712 Mutt-ng version string
4714 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.310 , page 160)''
4715 option for more information on how to set ``_
\b$_
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.27 ,
4718 _
\b7_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4724 When defined, Mutt-ng will recode commands in rc files from this encoding.
4726 _
\b7_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4732 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4734 The Mutt Next Generation E-Mail Client 94
4738 _
\b7_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4744 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4745 box which does not yet exist before creating it.
4747 _
\b7_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4753 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4754 many seconds if the connection is not able to be established. A negative value
4755 causes Mutt-ng to wait indefinitely for the connection to succeed.
4757 _
\b7_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4761 Default: 'text/plain'
4763 Sets the default Content-Type: header field for the body of newly composed mes-
4766 _
\b7_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bp_
\by
4772 This variable controls whether or not copies of your outgoing messages will be
4773 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.232 , page
4774 142)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.243 , page 144)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4775 7.4.69 , page 102)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 36)''.
4777 _
\b7_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4783 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4784 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4785 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4786 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
4787 7.4.279 , page 153)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4788 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4791 The Mutt Next Generation E-Mail Client 95
4793 _
\b7_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4799 This variable controls whether or not Mutt-ng may automatically enable PGP
4800 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
4801 7.4.34 , page 93)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.38 , page 94)'',
4802 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.36 , page 94)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4803 7.4.39 , page 94)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.279 , page 153)''.
4805 _
\b7_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4811 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4812 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4813 signing is not required or encryption is requested as well. If
4814 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.279 , page 153)'' is _
\bs_
\be_
\bt, then OpenSSL is
4815 used instead to create S/MIME messages and settings can be overridden by use of
4816 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4818 _
\b7_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4824 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4825 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
4826 7.4.34 , page 93)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 7.4.38 , page 94)'',
4827 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 7.4.36 , page 94)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4828 7.4.39 , page 94)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 7.4.279 , page 153)''.
4830 _
\b7_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4836 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
4837 encrypted. (Crypto only)
4839 _
\b7_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
4845 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
4847 The Mutt Next Generation E-Mail Client 96
4849 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
4852 _
\b7_
\b._
\b4_
\b._
\b4_
\b0 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd
4858 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
4859 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
4860 7.4.38 , page 94)'', because it allows you to sign all messages which are
4861 automatically encrypted. This works around the problem noted in
4862 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 7.4.39 , page 94)'', that Mutt-ng is not able to
4863 find out whether an encrypted message is also signed. (Crypto only)
4865 _
\b7_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
4871 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
4872 S/MIME output, so spoofing such lines is more difficult. If you are using col-
4873 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
4876 _
\b7_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
4882 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
4883 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
4884 will be used instead of the classic code.
4886 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
4887 won't have any effect when used interactively.
4889 _
\b7_
\b._
\b4_
\b._
\b4_
\b3 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
4895 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
4896 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
4897 cryptographic signatures. (Crypto only)
4899 _
\b7_
\b._
\b4_
\b._
\b4_
\b4 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4903 The Mutt Next Generation E-Mail Client 97
4905 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
4907 This variable controls the format of the date printed by the ``%d'' sequence in
4908 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111)''. This is passed to strftime(3)
4909 to process the date.
4911 Unless the first character in the string is a bang (``!''), the month and week
4912 day names are expanded according to the locale specified in the variable
4913 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 7.4.115 , page 114)''. If the first character in the string
4914 is a bang, the bang is discarded, and the month and week day names in the rest
4915 of the string are expanded in the _
\bC locale (that is in US English).
4917 _
\b7_
\b._
\b4_
\b._
\b4_
\b5 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
4921 Default: '~f %s !~P | (~P ~C %s)'
4923 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
4924 will be interpreted if they are specified with only a simple regexp, instead of
4925 a matching pattern. The hooks are expanded when they are declared, so a hook
4926 will be interpreted according to the value of this variable at the time the
4927 hook is declared. The default value matches if the message is either from a
4928 user matching the regular expression given, or if it is from you (if the from
4929 address matches ``alternates'') and is to or cc'ed to a user matching the given
4932 _
\b7_
\b._
\b4_
\b._
\b4_
\b6 _
\bd_
\be_
\bl_
\be_
\bt_
\be
4938 Controls whether or not messages are really deleted when closing or synchroniz-
4939 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
4940 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
4941 be kept in the mailbox.
4943 _
\b7_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bs_
\bp_
\ba_
\bc_
\be
4949 When sending messages with format=flowed by _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg the $text_flowed variable,
4950 this variable specifies whether to also set the DelSp parameter to yes. If this
4951 is _
\bu_
\bn_
\bs_
\be_
\bt, no additional parameter will be send as a value of no already is the
4954 N
\bNo
\bot
\bte
\be:
\b: this variable only has an effect on _
\bo_
\bu_
\bt_
\bg_
\bo_
\bi_
\bn_
\bg messages (if $text_flowed is
4955 _
\bs_
\be_
\bt) but not on incomming.
4957 _
\b7_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
4959 The Mutt Next Generation E-Mail Client 98
4965 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
4966 tion. This applies when you either explicitly delete a message, or when you
4967 save it to another folder.
4969 _
\b7_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
4975 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
4976 subparts of individual messages in a multipart/digest. To see these subparts,
4977 press 'v' on that menu.
4979 _
\b7_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
4985 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
4986 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.50 ,
4987 page 97), and the filtered message is read from the standard output.
4989 _
\b7_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
4993 Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
4995 Availability: Standalone and Dotlock
4997 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
4999 _
\b7_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
5005 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5006 or in connection with the SMTP support via libESMTP.
5008 This variable sets the request for when notification is returned. The string
5009 consists of a comma separated list (no spaces!) of one or more of the follow-
5010 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
5011 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
5012 notified of successful transmission.
5014 Example: set dsn_notify='failure,delay'
5016 The Mutt Next Generation E-Mail Client 99
5018 _
\b7_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
5024 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or greater
5025 or in connection with the SMTP support via libESMTP.
5027 This variable controls how much of your message is returned in DSN messages.
5028 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
5029 return the full message.
5031 Example: set dsn_return=hdrs
5033 _
\b7_
\b._
\b4_
\b._
\b5_
\b4 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
5039 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
5040 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
5041 indicate that it thinks they are duplicates of each other with an equals sign
5042 in the thread diagram.
5044 _
\b7_
\b._
\b4_
\b._
\b5_
\b5 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5050 This option allows you to edit the header of your outgoing messages along with
5051 the body of your message.
5053 _
\b7_
\b._
\b4_
\b._
\b5_
\b6 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
5059 This variable specifies which editor is used by Mutt-ng. It defaults to the
5060 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
5061 if neither of those are set.
5063 _
\b7_
\b._
\b4_
\b._
\b5_
\b7 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
5069 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
5070 string ``From '' (note the trailing space) in the beginning of a line. Useful
5071 to avoid the tampering certain mail delivery and transport agents tend to do
5073 The Mutt Next Generation E-Mail Client 100
5077 N
\bNo
\bot
\bte
\be:
\b: as mutt-ng currently violates RfC3676 defining format=flowed, it's
5078 <em/strongly/ advised to _
\bs_
\be_
\bt this option although discouraged by the standard.
5079 Alternatively, you must take care of space-stuffing <tt/From / lines (with a
5080 trailing space) yourself.
5082 _
\b7_
\b._
\b4_
\b._
\b5_
\b8 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
5090 The file which includes random data that is used to initialize SSL library
5093 _
\b7_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
5099 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
5100 ``From:'' header field. Note that this information is passed to the sendmail
5101 command using the ``-f' command line switch, so don't set this option if you
5102 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.249 , page 146) yourself, or
5103 if the sendmail on your machine doesn't support that command line switch.
5105 _
\b7_
\b._
\b4_
\b._
\b6_
\b0 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
5111 Escape character to use for functions in the builtin editor.
5113 _
\b7_
\b._
\b4_
\b._
\b6_
\b1 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5119 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
5120 ing to messages, and the initial prompt for subject is skipped when forwarding
5123 N
\bNo
\bot
\bte
\be:
\b: this variable has no effect when the ``_
\b$_
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt (section 7.4.17 , page
5124 90)'' variable is _
\bs_
\be_
\bt.
5126 _
\b7_
\b._
\b4_
\b._
\b6_
\b2 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
5130 The Mutt Next Generation E-Mail Client 101
5134 This variable controls whether or not attachments on outgoing messages are
5135 saved along with the main body of your message.
5137 _
\b7_
\b._
\b4_
\b._
\b6_
\b3 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
5143 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
5144 when the actual message is encrypted and/or signed. (PGP only)
5146 _
\b7_
\b._
\b4_
\b._
\b6_
\b4 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
5152 This variable is a colon-separated list of character encoding schemes for text
5153 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.24 , page 91) value will
5154 be used instead. For example, the following configuration would work for
5155 Japanese text handling:
5157 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
5159 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
5162 _
\b7_
\b._
\b4_
\b._
\b6_
\b5 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
5168 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
5169 beginning of a pathname will be expanded to the value of this variable. Note
5170 that if you change this variable from the default value you need to make sure
5171 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
5172 ables since expansion takes place during the ``set'' command.
5174 _
\b7_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5178 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
5180 This variable allows you to customize the file browser display to your personal
5181 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page
5182 111)'', but has its own set of printf(3)-like sequences:
5187 The Mutt Next Generation E-Mail Client 102
5190 date/time folder was last modified
5199 group name (or numeric gid, if missing)
5202 number of hard links
5205 N if folder has new mail, blank otherwise
5211 * if the file is tagged, blank otherwise
5214 owner name (or numeric uid, if missing)
5217 right justify the rest of the string and pad with character 'X'
5220 pad to the end of the line with character 'X'
5222 _
\b7_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5228 Controls whether or not the Mail-Followup-To: header field is generated when
5229 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
5230 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
5231 3.12 , page 33)'' commands or detected by common mailing list headers.
5233 This field has two purposes. First, preventing you from receiving duplicate
5234 copies of replies to messages which you send to mailing lists. Second, ensuring
5235 that you do get a reply separately for any messages sent to known lists to
5236 which you are not subscribed. The header will contain only the list's address
5237 for subscribed lists, and both the list address and your own email address for
5238 unsubscribed lists. Without this header, a group reply to your message sent to
5239 a subscribed list will be sent to both the list and your address, resulting in
5240 two copies of the same email for you.
5242 The Mutt Next Generation E-Mail Client 103
5244 _
\b7_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5250 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
5251 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
5252 already known to have new mail.
5254 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 7.4.323 , page 165)'',
5255 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.116 , page 114)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
5256 7.4.100 , page 109)''.
5258 _
\b7_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5264 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.243 , page 144)'',
5265 except that Mutt-ng will store a copy of your outgoing message by the username
5266 of the address you are sending to even if that mailbox does not exist.
5268 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.232 , page 142)'' variable.
5270 _
\b7_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5276 Controls the decoding of complex MIME messages into text/plain when forwarding
5277 a message. The message header is also RFC2047 decoded. This variable is only
5278 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.138 , page 119)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5279 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.139 , page 119)'' is used instead.
5281 _
\b7_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5287 Controls the handling of encrypted messages when forwarding a message. When
5288 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5289 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.138 , page 119)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5290 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.139 , page 119)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5292 _
\b7_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5298 The Mutt Next Generation E-Mail Client 104
5300 This quadoption controls whether or not the user is automatically placed in the
5301 editor when forwarding messages. For those who always want to forward with no
5302 modification, use a setting of _
\bn_
\bo.
5304 _
\b7_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5310 This variable controls the default subject when forwarding a message. It uses
5311 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page
5314 _
\b7_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5320 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5321 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.138 , page 119)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5322 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.110 , page 111)''.
5324 _
\b7_
\b._
\b4_
\b._
\b7_
\b5 _
\bf_
\br_
\bo_
\bm
5326 Type: e-mail address
5330 This variable contains a default from address. It can be overridden using
5331 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.238 , page
5332 143)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 7.4.332 , page
5335 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5336 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5337 takes this email address.
5339 Defaults to the contents of the environment variable $EMAIL.
5341 _
\b7_
\b._
\b4_
\b._
\b7_
\b6 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5343 Type: regular expression
5347 A regular expression used by Mutt-ng to parse the GECOS field of a password
5348 entry when expanding the alias. By default the regular expression is set to
5349 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5350 the GECOS field contains a string like 'lastname, firstname' then you should
5351 do: set gecos_mask='.*'.
5353 This can be useful if you see the following behavior: you address a e-mail to
5355 The Mutt Next Generation E-Mail Client 105
5357 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5358 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5359 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5360 to ``Franklin, Steve''.
5362 _
\b7_
\b._
\b4_
\b._
\b7_
\b7 _
\bh_
\bd_
\br_
\bs
5368 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 ,
5369 page 35)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5370 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5371 defined header fields are added to every new message.
5373 _
\b7_
\b._
\b4_
\b._
\b7_
\b8 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5379 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5380 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 7.4.338 , page
5381 168)'' setting applies.
5383 _
\b7_
\b._
\b4_
\b._
\b7_
\b9 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5389 Availability: Header Cache
5391 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.79 , page 104) variable points to the header
5394 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 7.4.79 , page 104) points to a directory it will
5395 contain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section
5396 7.4.79 , page 104) points to a file that file will be a single global header
5397 cache. By default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5399 _
\b7_
\b._
\b4_
\b._
\b8_
\b0 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5405 If enabled the header cache will be compressed. So only one fifth of the usual
5406 diskspace is used, but the uncompression can result in a slower open of the
5409 _
\b7_
\b._
\b4_
\b._
\b8_
\b1 _
\bh_
\be_
\bl_
\bp
5411 The Mutt Next Generation E-Mail Client 106
5417 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5418 by each menu are displayed on the first line of the screen.
5420 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5421 sequence rather than a single keystroke. Also, the help line may not be
5422 updated if a binding is changed while Mutt-ng is running. Since this variable
5423 is primarily aimed at new users, neither of these should present a major prob-
5426 _
\b7_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5432 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5433 7.4.90 , page 106)'' variable when adding the domain part to addresses. This
5434 variable does not affect the generation of Message-ID: header fields, and it
5435 will not lead to the cut-off of first-level domains.
5437 _
\b7_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5443 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5444 limiting, in the thread tree.
5446 _
\b7_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5452 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5455 _
\b7_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5461 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5462 have the same subject as their parent or closest previously displayed sibling.
5464 _
\b7_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5468 The Mutt Next Generation E-Mail Client 107
5472 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5473 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5474 _
\bi_
\bn_
\bg (section 7.4.84 , page 105) is set, this option will have no effect.
5476 _
\b7_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5482 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5483 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 7.4.83 ,
5484 page 105) is _
\bs_
\be_
\bt, this option will have no effect.
5486 _
\b7_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5492 This variable controls the size (in number of strings remembered) of the string
5493 history buffer. The buffer is cleared each time the variable is changed.
5495 _
\b7_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5501 This variable controls whether or not a Mail-Followup-To: header field is hon-
5502 ored when group-replying to a message.
5504 _
\b7_
\b._
\b4_
\b._
\b9_
\b0 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5510 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5511 during generation of Message-Id: headers.
5513 Please be sure to really know what you are doing when changing this variable to
5514 configure a custom domain part of Message-IDs.
5516 _
\b7_
\b._
\b4_
\b._
\b9_
\b1 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5522 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5523 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5525 The Mutt Next Generation E-Mail Client 108
5527 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5528 header field was set by the mailing list to automate responses to the list, and
5529 will ignore this field. To direct a response to the mailing list when this
5530 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
5531 sender and the list.
5533 _
\b7_
\b._
\b4_
\b._
\b9_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5541 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5542 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5543 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5544 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5545 eter is case-insensitive.
5547 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5548 ods, in order from most-secure to least-secure.
5550 Example: set imap_authenticators='gssapi:cram-md5:login'
5552 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5553 ous methods are unavailable. If a method is available but authentication fails,
5554 Mutt-ng will not connect to the IMAP server.
5556 _
\b7_
\b._
\b4_
\b._
\b9_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5562 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5563 connection, and add them to the set of mailboxes it polls for new mail. See
5564 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.14 , page 34)'' command.
5566 _
\b7_
\b._
\b4_
\b._
\b9_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5574 This contains the list of characters which you would like to treat as folder
5575 separators for displaying IMAP paths. In particular it helps in using the '='
5576 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.65 , page 100) variable.
5578 _
\b7_
\b._
\b4_
\b._
\b9_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5582 The Mutt Next Generation E-Mail Client 109
5588 Mutt-ng requests these header fields in addition to the default headers (``DATE
5589 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5590 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5591 ``index'' menu. You may want to add more headers for spam detection.
5593 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5595 _
\b7_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5603 You normally want to see your personal folders alongside your INBOX in the IMAP
5604 browser. If you see something else, you may set this variable to the IMAP path
5607 _
\b7_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5615 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5616 wait before polling open IMAP connections, to prevent the server from closing
5617 them before Mutt-ng has finished with them.
5619 The default is well within the RFC-specified minimum amount of time (30 min-
5620 utes) before a server is allowed to do this, but in practice the RFC does get
5621 violated every now and then.
5623 Reduce this number if you find yourself getting disconnected from your IMAP
5624 server due to inactivity.
5626 _
\b7_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5634 This variable configures whether IMAP folder browsing will look for only sub-
5635 scribed folders or all folders. This can be toggled in the IMAP browser with
5636 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5638 The Mutt Next Generation E-Mail Client 110
5640 _
\b7_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5648 Your login name on the IMAP server.
5650 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 7.4.106 , page
5653 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5659 This variable configures how often (in seconds) Mutt-ng should look for new
5660 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 7.4.116 ,
5661 page 114)'' variable to generate less traffic and get more accurate information
5664 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5672 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5673 you for your password when you invoke the fetch-mail function.
5675 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5676 machine, because the superuser can read your configuration even if you are the
5677 only one who can read the file.
5679 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5687 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5688 Mutt-ng will only check for new mail over existing IMAP connections. This is
5689 useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
5690 cation, or if opening the connection is slow.
5692 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5694 The Mutt Next Generation E-Mail Client 111
5702 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5703 fetch a message from the server. This is generally a good thing, but can make
5704 closing an IMAP folder somewhat slower. This option exists to appease speed
5707 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5715 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5718 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5726 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5727 messages. Since these messages are often harmless, or generated due to configu-
5728 ration problems on the server which are out of the users' hands, you may wish
5729 to suppress them at some point.
5731 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5739 The name of the user whose mail you intend to access on the IMAP server.
5741 This variable defaults to your user name on the local machine.
5743 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5749 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5751 The Mutt Next Generation E-Mail Client 112
5753 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5754 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5755 convert the body part to text form.
5757 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5763 Controls whether or not a copy of the message(s) you are replying to is
5764 included in your reply.
5766 _
\b7_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5772 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5773 sage you are replying.
5775 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5781 Specifies the string to prepend to each line of text quoted in a message to
5782 which you are replying. You are strongly encouraged not to change this value,
5783 as it tends to agitate the more fanatical netizens.
5785 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5789 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5791 This variable allows you to customize the message index display to your per-
5794 ``Format strings'' are similar to the strings used in the ``C'' function
5795 printf(3) to format output (see the man page for more detail). The following
5796 sequences are defined in Mutt-ng:
5799 address of the author
5802 reply-to address (if present; otherwise: address of author)
5805 filename of the original message folder (think mailBox)
5807 The Mutt Next Generation E-Mail Client 113
5810 the list to which the letter was sent, or else the folder name
5814 number of characters (bytes) in the message
5817 current message number
5820 date and time of the message in the format specified by ``date_for-
5821 mat'' converted to sender's time zone
5824 date and time of the message in the format specified by ``date_for-
5825 mat'' converted to the local time zone
5828 current message number in thread
5831 number of messages in current thread
5834 entire From: line (address + real name)
5837 author name, or recipient name if the message is from you
5840 spam attribute(s) of this message
5843 newsgroup name (if compiled with nntp support)
5846 message-id of the current message
5849 number of lines in the message (does not work with maildir, mh, and
5850 possibly IMAP folders)
5853 If an address in the To or CC header field matches an address
5854 defined by the users ``subscribe'' command, this displays 'To
5855 <list-name>', otherwise the same as %F.
5858 total number of message in the mailbox
5861 number of hidden messages if the thread is collapsed.
5863 The Mutt Next Generation E-Mail Client 114
5869 author's real name (or address if missing)
5872 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
5873 the message: list name or recipient name if no list
5876 subject of the message
5879 status of the message (N/D/d/!/r/*)
5882 `to:' field (recipients)
5885 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.325 ,
5889 user (login) name of the author
5892 first name of the author, or the recipient if the message is from
5896 name of organization of author (`organization:' field)
5899 `x-label:' field, if present
5902 `x-label' field, if present, and (1) not at part of a thread tree,
5903 (2) at the top of a thread, or (3) `x-label' is different from pre-
5904 ceding message's `x-label'.
5907 message status flags
5910 the date and time of the message is converted to sender's time
5911 zone, and ``fmt'' is expanded by the library function ``strftime'';
5912 a leading bang disables locales
5915 the date and time of the message is converted to the local time
5916 zone, and ``fmt'' is expanded by the library function ``strftime'';
5917 a leading bang disables locales
5919 The Mutt Next Generation E-Mail Client 115
5922 the local date and time when the message was received. ``fmt'' is
5923 expanded by the library function ``strftime''; a leading bang dis-
5927 the current local time. ``fmt'' is expanded by the library function
5928 ``strftime''; a leading bang disables locales.
5931 right justify the rest of the string and pad with character 'X'
5934 pad to the end of the line with character 'X'
5936 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.325 , page 165)''.
5938 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
5944 How to invoke ispell (GNU's spell-checking software).
5946 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
5952 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
5953 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.126 , page 117)'' mailbox, or as a result of
5954 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 34)'' command.
5956 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5962 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
5963 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
5964 will ask if you really intended to reply to the author only.
5966 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
5972 The locale used by strftime(3) to format dates. Legal values are the strings
5973 your system accepts for the locale variable LC_TIME.
5975 The Mutt Next Generation E-Mail Client 116
5977 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5983 This variable configures how often (in seconds) Mutt-ng should look for new
5986 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
5987 7.4.100 , page 109).
5989 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
5995 This variable specifies which files to consult when attempting to display MIME
5996 bodies not directly supported by Mutt-ng.
5998 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
6004 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
6005 well-defined set of safe characters. This is the safe setting, but we are not
6006 sure it doesn't break some more advanced MIME stuff.
6008 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!
6010 _
\b7_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\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
6016 Availability: Header Cache
6018 Check for Maildir unaware programs other than Mutt-ng having modified maildir
6019 files when the header cache is in use. This incurs one stat(2) per message
6020 every time the folder is opened.
6022 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
6028 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
6029 flag instead of physically deleted.
6031 The Mutt Next Generation E-Mail Client 117
6033 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
6034 effect on other mailbox types.
6036 It is similiar to the trash option.
6038 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
6044 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
6045 mailbox without reading them.
6047 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
6048 up with an 'O' next to them in the ``index'' menu, indicating that they are
6051 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
6057 Controls the display of wrapped lines in the internal pager. If set, a ``+''
6058 marker is displayed at the beginning of wrapped lines. Also see the
6059 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 7.4.265 , page 150)'' variable.
6061 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bs_
\bk
6063 Type: regular expression
6067 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
6068 operator ``!''. Only files whose names match this mask will be shown. The
6069 match is always case-sensitive.
6071 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\ba_
\bx_
\b__
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\br_
\be_
\bc_
\bi_
\bp_
\bs
6077 When set non-zero, this specifies the maximum number of recipient header lines
6078 (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In
6079 case the number of lines exeeds its value, the last line will have 3 dots
6082 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
6088 The Mutt Next Generation E-Mail Client 118
6090 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
6091 is limited to this length. A value of 0 (which is also the default) means that
6092 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
6093 (section 7.4.340 , page 168).
6095 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\bb_
\bo_
\bx
6101 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
6102 7.4.299 , page 158)'' folder will be appended.
6104 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
6110 The default mailbox type used when creating new folders. May be any of mbox,
6111 MMDF, MH and Maildir.
6113 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6119 This variable controls the number of lines of context that are given when
6120 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.169 , page
6123 _
\b7_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
6129 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
6130 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
6131 entry may move off the bottom.
6133 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
6139 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
6140 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
6141 vious page of the menu is displayed (useful for slow links to avoid many
6144 The Mutt Next Generation E-Mail Client 119
6146 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6152 This is the string displayed in the ``attachment'' menu for attachments of type
6153 message/rfc822. For a full listing of defined printf(3)-like sequences see the
6154 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111)''.
6156 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
6162 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
6163 if the user had pressed the ESC key and whatever key remains after having the
6164 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
6165 then this is treated as if the user had pressed ESC then ``x''. This is
6166 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
6167 the ASCII character ``x''.
6169 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\be_
\bt_
\bo_
\bo
6175 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
6176 from the list of recipients when replying to a message.
6178 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
6184 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
6185 _
\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-
6186 able is set, the message files will simply be deleted.
6188 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
6194 The name of the MH sequence used for flagged messages.
6196 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
6200 The Mutt Next Generation E-Mail Client 120
6204 The name of the MH sequence used to tag replied messages.
6206 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
6212 The name of the MH sequence used for unseen messages.
6214 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
6220 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
6221 part instead of included in the main body of the message.
6223 This is useful for forwarding MIME messages so the receiver can properly view
6224 the message as it was delivered to you. If you like to switch between MIME and
6225 not MIME from mail to mail, set this variable to ask-no or ask-yes.
6227 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.70 , page 102)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
6228 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.139 , page 119)''.
6230 _
\b7_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6236 Controls the decoding of complex MIME messages into text/plain when forwarding
6237 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 7.4.138 , page 119)'' is _
\bs_
\be_
\bt. Other-
6238 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 7.4.70 , page 102)'' is used instead.
6240 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
6246 When forwarding multiple attachments of a MIME message from the recvattach
6247 menu, attachments which cannot be decoded in a reasonable manner will be
6248 attached to the newly composed message if this option is set.
6250 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6254 Default: '%4n %c %-16s %a'
6256 The Mutt Next Generation E-Mail Client 121
6258 Availability: Mixmaster
6260 This variable describes the format of a remailer line on the mixmaster chain
6261 selection screen. The following printf(3)-like sequences are supported:
6264 The running number on the menu.
6267 Remailer capabilities.
6270 The remailer's short name.
6273 The remailer's e-mail address.
6275 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6279 Default: 'mixmaster'
6281 Availability: Mixmaster
6283 This variable contains the path to the Mixmaster binary on your system. It is
6284 used with various sets of parameters to gather the list of known remailers, and
6285 to finally send a message through the mixmaster chain.
6287 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bm_
\bo_
\bv_
\be
6293 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6294 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 7.4.126 , page 117)'' mailbox, or as a result of a
6295 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 34)'' command.
6297 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6301 Default: '%Y%m%d%h%M%s.G%P%p'
6303 This is the format for the ``local part'' of the Message-Id: header field gen-
6304 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6305 generated. The '%' character marks that certain data will be added to the
6306 string, similar to printf(3). The following characters are allowed:
6309 the current day of month
6311 The Mutt Next Generation E-Mail Client 122
6323 the current UNIX timestamp (octal)
6329 the current Message-ID prefix (a character rotating with every Mes-
6330 sage-ID being generated)
6333 a random integer value (decimal)
6336 a random integer value (hexadecimal)
6342 the current UNIX timestamp (decimal)
6345 the current UNIX timestamp (hexadecimal)
6348 the current year (Y2K compliant)
6353 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6354 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6356 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6362 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6363 threads to fit on the screen.
6365 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6367 The Mutt Next Generation E-Mail Client 123
6375 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6376 ing the body of an outgoing news article.
6378 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6386 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6387 ing the body of an outgoing news article.
6389 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6393 Default: '~/.muttng'
6397 This variable points to directory where Mutt-ng will cache news article head-
6398 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6399 when you enter a newsgroup.
6401 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6402 cally increases speed and lowers traffic.
6404 _
\b7_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6412 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6413 when you leaving it.
6415 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6423 The Mutt Next Generation E-Mail Client 124
6425 This variable controls how many news articles to cache per newsgroup (if
6426 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 7.4.148 , page 122)) and how
6427 many news articles to show in the ``index'' menu.
6429 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 7.4.150 ,
6430 page 122), all older ones will be removed/not shown in the index.
6432 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6440 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6441 header field, a follow-up to the newsgroup is not permitted. The message will
6442 be mailed to the submitter of the message via mail.
6444 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6448 Default: '%4C %M%N %5s %-45.45f %d'
6452 This variable allows you to customize the newsgroup browser display to your
6453 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 ,
6454 page 111)'', but has its own set of printf(3)-like sequences:
6456 %C current newsgroup number
6457 %d description of newsgroup (retrieved from server)
6459 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6460 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6461 %n number of new articles in newsgroup
6462 %s number of unread articles in newsgroup
6463 %>X right justify the rest of the string and pad with character "X"
6464 %|X pad to the end of the line with character "X"
6466 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6474 This variable specifies the name (or address) of the NNTP server to be used.
6476 It defaults to the value specified via the environment variable $NNTPSERVER or
6478 The Mutt Next Generation E-Mail Client 125
6480 contained in the file /etc/nntpserver.
6482 You can also specify a username and an alternative port for each newsserver,
6485 [nntp[s]://][username[:password]@]newsserver[:port]
6487 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6488 security risk since the superuser of your machine may read it regardless of the
6491 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6499 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6500 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6501 lowing printf(3)-style sequence is understood:
6505 Example: set inews='/usr/local/bin/inews -hS'
6507 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6515 This variable controls whether or not descriptions for newsgroups are to be
6516 loaded when subscribing to a newsgroup.
6518 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6526 The time in seconds until any operations on a newsgroup except posting a new
6527 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6528 each operation in index (stepping, read article, etc.).
6530 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6532 The Mutt Next Generation E-Mail Client 126
6540 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6541 encoded according to RFC2047.
6543 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6545 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6549 Default: '~/.newsrc'
6553 This file contains information about subscribed newsgroup and articles read so
6556 To ease the use of multiple news servers, the following printf(3)-style
6557 sequence is understood:
6561 _
\b7_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6569 Your password for NNTP account.
6571 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6572 the superuser of your machine may read it regardless of the file's permissions.
6574 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6582 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6583 sions to post (e.g. moderated).
6585 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6587 The Mutt Next Generation E-Mail Client 127
6589 is totally read-only, that posting will not have any effect.
6591 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6599 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6600 was connection lost.
6602 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6610 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6611 file and into the news cache.
6613 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6621 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6622 browser. Otherwise, it will be done only once for a newsserver. Also controls
6623 whether or not the number of new articles of subscribed newsgroups will be
6626 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6634 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6635 played in the newsgroup browser.
6637 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6643 The Mutt Next Generation E-Mail Client 128
6647 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6648 tification, Mutt-ng will prompt you for your account name.
6650 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6658 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6659 name of the original article author) to articles that you followup to.
6661 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6667 This specifies the operating system name for the User-Agent: header field. If
6668 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6669 returns. If uname(2) fails, ``UNIX'' will be used.
6671 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6673 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bp_
\ba_
\bg_
\be_
\br
6679 This variable specifies which pager you would like to use to view messages.
6680 ``builtin'' means to use the builtin pager, otherwise this variable should
6681 specify the pathname of the external pager you would like to use.
6683 Using an external pager may have some disadvantages: Additional keystrokes are
6684 necessary because you can't call Mutt-ng functions directly from the pager, and
6685 screen resizes cause lines longer than the screen width to be badly formatted
6688 _
\b7_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6694 This variable controls the number of lines of context that are given when dis-
6695 playing the next or previous page in the internal pager. By default, Mutt-ng
6696 will display the line after the last one on the screen at the top of the next
6697 page (0 lines of context).
6699 The Mutt Next Generation E-Mail Client 129
6701 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6705 Default: '-%Z- %C/%m: %-20.20n %s'
6707 This variable controls the format of the one-line message ``status'' displayed
6708 before each message in either the internal or an external pager. The valid
6709 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111)''
6712 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6718 Determines the number of lines of a mini-index which is shown when in the
6719 pager. The current message, unless near the top or bottom of the folder, will
6720 be roughly one third of the way down this mini-index, giving the reader the
6721 context of a few messages before and after the message. This is useful, for
6722 example, to determine how many messages remain to be read in the current
6723 thread. One of the lines is reserved for the status bar from the index, so a
6724 _
\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
6725 0 results in no index being shown. If the number of messages in the current
6726 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
6729 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6735 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6736 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
6738 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6744 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
6745 whenever the user performs an operation which ordinarily would result in the
6746 contents of the message being operated on. For example, if the user displays a
6747 pgp-traditional message which has not been manually checked with the check-tra-
6748 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
6751 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6755 The Mutt Next Generation E-Mail Client 130
6759 This option controls whether Mutt-ng generates old-style inline (traditional)
6760 PGP encrypted or signed messages under certain circumstances. This can be
6761 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
6763 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6764 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6765 ing PGP/MIME messages when inline (traditional) would not work. See also:
6766 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.190 , page 132)''.
6768 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.
6771 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
6777 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
6778 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
6780 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6786 This format is used to create a old-style ``clearsigned'' PGP message.
6788 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)
6790 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6796 This format strings specifies a command which is used to decode application/pgp
6799 The PGP command formats have their own set of printf(3)-like sequences:
6802 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
6803 string otherwise. Note: This may be used with a %? construct.
6806 Expands to the name of a file containing a message.
6809 Expands to the name of a file containing the signature part of a
6810 multipart/signed attachment when verifying it.
6812 The Mutt Next Generation E-Mail Client 131
6815 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 7.4.194 , page 133).
6818 One or more key IDs.
6820 For examples on how to configure these formats for the various versions of PGP
6821 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
6822 subdirectory which has been installed on your system alongside the documenta-
6825 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6831 This command is used to decrypt a PGP encrypted message. (PGP only)
6833 _
\b7_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6839 This command is used to encrypt a body part without signing it. (PGP only)
6841 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6847 This command is used to both sign and encrypt a body part. (PGP only)
6849 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6853 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
6855 This variable allows you to customize the PGP key selection menu to your per-
6856 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page
6857 111)'', but has its own set of printf(3)-like sequences:
6868 The Mutt Next Generation E-Mail Client 132
6883 trust/validity of the key-uid association
6886 date of the key where <s> is an strftime(3) expression
6890 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6896 This command is used to export a public key from the user's key ring. (PGP
6899 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6905 This command is invoked whenever Mutt-ng will need public key information. %r
6906 is the only printf(3)-like sequence used with this format. (PGP only)
6908 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
6910 Type: regular expression
6914 If you assign a text to this variable, then a PGP signature is only considered
6915 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.200 , page 135)
6916 contains the text. Use this variable if the exit code from the command is 0
6917 even for bad signatures. (PGP only)
6919 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
6925 The Mutt Next Generation E-Mail Client 133
6927 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
6928 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
6929 want to play interesting key selection games. (PGP only)
6931 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6937 This command is used to import a key from a message into the user's public key
6940 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6946 This command is used to list the public key ring's contents. The output format
6947 must be analogous to the one used by gpg --list-keys --with-colons.
6949 This format is also generated by the pgpring utility which comes with Mutt-ng.
6952 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6958 This command is used to list the secret key ring's contents. The output format
6959 must be analogous to the one used by gpg --list-keys --with-colons.
6961 This format is also generated by the pgpring utility which comes with Mutt-ng.
6964 _
\b7_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
6970 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
6973 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
6979 This option controls whether Mutt-ng will prompt you for automatically sending
6980 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
6982 The Mutt Next Generation E-Mail Client 134
6986 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.
6989 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6995 Setting this variable will cause Mutt-ng to always attempt to create an inline
6996 (traditional) message when replying to a message which is PGP encrypted/signed
6997 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
6998 required. This option does not automatically detect if the (replied-to) mes-
6999 sage is inline; instead it relies on Mutt-ng internals for previously
7000 checked/flagged messages.
7002 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
7003 of more than a single MIME part. Mutt-ng can be configured to ask before send-
7004 ing PGP/MIME messages when inline (traditional) would not work. See also:
7005 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 7.4.190 , page 132)''.
7007 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.
7010 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
7016 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
7017 and multipart/encrypted body parts.
7019 This is useful for applications like encrypted and signed mailing lists, where
7020 the outer layer (multipart/encrypted) can be easily removed, while the inner
7021 multipart/signed part is retained. (PGP only)
7023 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
7029 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
7030 This includes keys which have been revoked, have expired, or have been marked
7031 as ``disabled'' by the user. (PGP only)
7033 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
7039 The Mutt Next Generation E-Mail Client 135
7041 If you have more than one key pair, this option allows you to specify which of
7042 your private keys to use. It is recommended that you use the keyid form to
7043 specify your key (e.g., ``0x00112233''). (PGP only)
7045 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7051 This command is used to create the detached PGP signature for a multi-
7052 part/signed PGP/MIME body part. (PGP only)
7054 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
7060 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
7064 sort alphabetically by user id
7067 sort alphabetically by key id
7070 sort by key creation date
7073 sort by the trust of the key
7075 If you prefer reverse order of the above values, prefix it with ``reverse-''.
7078 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
7084 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
7085 printable. Please note that unsetting this variable may lead to problems with
7086 non-verifyable PGP signatures, so only change this if you know what you are
7089 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7095 The Mutt Next Generation E-Mail Client 136
7097 The number of seconds after which a cached passphrase will expire if not used.
7098 Default: 300. (PGP only)
7100 _
\b7_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
7106 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
7108 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7114 This command is used to verify PGP signatures. (PGP only)
7116 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7122 This command is used to verify key information from the key selection menu.
7125 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7131 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
7132 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
7133 ers and will attempt to PGP/MIME decode the messages first.
7135 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7141 The separator to add between messages when piping a list of tagged messages to
7142 an external Unix command.
7144 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7150 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
7152 The Mutt Next Generation E-Mail Client 137
7154 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
7155 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
7156 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
7157 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
7158 (section 7.4.203 , page 135)'' separator is added after each message.
7160 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
7168 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
7169 fall back to other authentication methods if the previous methods are unavail-
7170 able. If a method is available but authentication fails, Mutt-ng will not con-
7171 nect to the POP server.
7173 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
7181 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
7182 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
7183 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
7184 ``digest-md5'', ``gssapi'' or ``cram-md5''.
7186 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
7187 Mutt-ng will try all available methods, in order from most-secure to least-
7190 Example: set pop_authenticators='digest-md5:apop:user'
7192 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7200 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
7201 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
7202 load messages but also leave them on the POP server.
7204 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7208 The Mutt Next Generation E-Mail Client 138
7214 The name of your POP server for the ``fetch-mail'' function. You can also
7215 specify an alternative port, username and password, i.e.:
7217 [pop[s]://][username[:password]@]popserver[:port]
7219 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7220 the superuser of your machine may read it regardless of the file's permissions.
7222 _
\b7_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
7230 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
7231 retrieving only unread messages from the POP server when using the ``fetch-
7234 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
7242 This variable configures how often (in seconds) POP should look for new mail.
7244 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7252 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
7253 for your password when you open POP mailbox.
7255 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7256 the superuser of your machine may read it regardless of the file's permissions.
7258 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7264 The Mutt Next Generation E-Mail Client 139
7268 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7271 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7279 Your login name on the POP server.
7281 This variable defaults to your user name on the local machine.
7283 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7289 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 7.4.15 , page 89)'' variable, Mutt-ng
7290 will append this string after the inclusion of a message which is being replied
7293 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7299 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7300 7.4.216 , page 138)'' mailbox when you elect not to send immediately.
7302 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7306 Default: '~/postponed'
7308 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.215 , page 138)
7309 sending a message'' which you are editing. When you choose to postpone a mes-
7310 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7311 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 7.4.215 , page 138)'' variable.
7313 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7319 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a
7321 The Mutt Next Generation E-Mail Client 140
7323 connection to the server. This is useful for setting up secure connections,
7324 e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up
7325 opening the server. Example:
7327 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7328 /dev/null > /dev/null'
7330 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7332 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7333 machine without having to enter a password.
7335 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\br_
\bi_
\bn_
\bt
7341 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7342 by default, because some people accidentally hit ``p'' often.
7344 _
\b7_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7350 This specifies the command pipe that should be used to print messages.
7352 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7358 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7359 message is decoded before it is passed to the external command specified by
7360 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.219 , page 139). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7361 cessing will be applied to the message when printing it. The latter setting
7362 may be useful if you are using some advanced printer filter which is able to
7363 properly format e-mail messages for printing.
7365 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7371 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7372 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.219 , page 139) is executed
7373 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7374 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 7.4.219 , page 139) is executed
7375 only once, and all the messages are concatenated, with a form feed as the mes-
7378 The Mutt Next Generation E-Mail Client 141
7380 Those who use the enscript(1) program's mail-printing mode will most likely
7381 want to set this option.
7383 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7389 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 7.4.168 , page 127)'', setting this
7390 variable will cause Mutt-ng to prompt you for a command when the pager exits
7391 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7392 index menu when the external pager exits.
7394 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7400 This specifies the command that Mutt-ng will use to make external address
7401 queries. The string should contain a %s, which will be substituted with the
7402 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 56)'' for more
7405 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bq_
\bu_
\bi_
\bt
7411 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7412 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7413 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
7416 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7422 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7423 tion 7.4.110 , page 111)''.
7425 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7431 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7432 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7433 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.110 , page 111)''.
7435 The Mutt Next Generation E-Mail Client 142
7437 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7439 Type: regular expression
7441 Default: '^([ \t]*[|>:}#])+'
7443 A regular expression used in the internal-pager to determine quoted sections of
7444 text in the body of a message.
7446 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
7447 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7448 the beginning of quoted lines.
7450 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7456 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7457 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7458 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7459 reads message 25, and then again when it gets to message 50). This variable is
7460 meant to indicate progress when reading large mailboxes which may take some
7461 time. When set to 0, only a single message will appear before the reading the
7464 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 7.4.342 , page 169)'' variable.
7466 _
\b7_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7472 If set, all folders are opened in read-only mode.
7474 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7480 This variable specifies what ``real'' or ``personal'' name should be used when
7483 By default, this is the GECOS field from /etc/passwd.
7485 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7486 _
\b$_
\bf_
\br_
\bo_
\bm (section 7.4.75 , page 103) variable.
7488 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7492 The Mutt Next Generation E-Mail Client 143
7496 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7497 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 7.4.216 , page 138)''.
7499 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7501 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7507 This specifies the file into which your outgoing messages should be appended.
7508 (This is meant as the primary method for saving a copy of your messages, but
7509 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 35)'' com-
7510 mand to create a Bcc: header field with your email address in it.)
7512 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b4_
\b2_
\b) is overridden by the
7513 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.69 , page 102)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7514 7.4.243 , page 144)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page
7517 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7519 Type: regular expression
7521 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7523 A regular expression used to recognize reply messages when threading and reply-
7524 ing. The default value corresponds to the English ``Re:'' and the German
7527 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7533 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7534 that you want to reply to the recipients of that message rather than to your-
7537 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7543 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7544 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7545 use the address in the ``From:'' header field instead.
7547 This option is useful for reading a mailing list that sets the ``Reply-To:''
7549 The Mutt Next Generation E-Mail Client 144
7551 header field to the list address and you want to send a private message to the
7552 author of a message.
7554 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7560 When set, the cursor will be automatically advanced to the next (possibly
7561 undeleted) message whenever a command that modifies the current message is exe-
7564 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7570 This variable controls whether or not Mutt-ng will display the ``personal''
7571 name from your aliases in the index menu if it finds an alias that matches the
7572 message's sender. For example, if you have the following alias:
7574 alias juser abd30425@somewhere.net (Joe User)
7576 and then you receive mail which contains the following header:
7578 From: abd30425@somewhere.net
7580 It would be displayed in the index menu as ``Joe User'' instead of
7581 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7582 not human friendly (like CompuServe addresses).
7584 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7590 It may sometimes arrive that you receive mail to a certain machine, move the
7591 messages to another machine, and reply to some the messages from there. If
7592 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7593 using the address where you received the messages you are replying to i
\bif
\bf that
7594 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7595 would be used doesn't match your alternates, the From: line will use your
7596 address on the current machine.
7598 _
\b7_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7604 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.238 ,
7606 The Mutt Next Generation E-Mail Client 145
7608 page 143) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7609 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7610 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7611 (section 7.4.230 , page 141) variable.
7613 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7619 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7620 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7621 ments to files named like this:
7623 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7625 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7626 effect before you have changed folders.
7628 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7629 standard, but nevertheless encountered in the wild.
7631 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7632 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7633 encoding specified in RFC 2231.
7635 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7641 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7642 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.243 , page 144)'' or
7643 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.69 , page 102)'' is _
\bs_
\be_
\bt too, the selection of the
7644 fcc folder will be changed as well.
7646 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7652 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7653 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 7.4.299 , page 158)'' which is
7654 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7656 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7657 and Maildir directories.
7659 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7663 The Mutt Next Generation E-Mail Client 146
7667 This variable controls how copies of outgoing messages are saved. When set, a
7668 check is made to see if a mailbox specified by the recipient address exists
7669 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 7.4.65 ,
7670 page 100)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7671 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7672 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 7.4.232 , page 142)'' mailbox.
7674 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 7.4.69 , page 102)'' variable.
7676 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\bs_
\bc_
\bo_
\br_
\be
7682 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7683 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
7684 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 7.4.245 , page 145)'' variable and friends are used.
7686 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7692 Messages which have been assigned a score equal to or lower than the value of
7693 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7694 scores are always greater than or equal to zero, the default setting of this
7695 variable will never mark a message for deletion.
7697 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7703 Messages which have been assigned a score greater than or equal to this vari-
7704 able's value are automatically marked ``flagged''.
7706 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7712 Messages which have been assigned a score equal to or lower than the value of
7713 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7714 scores are always greater than or equal to zero, the default setting of this
7715 variable will never mark a message read.
7717 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7719 The Mutt Next Generation E-Mail Client 147
7723 Default: 'us-ascii:iso-8859-1:utf-8'
7725 A list of character sets for outgoing messages. Mutt-ng will use the first
7726 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7727 (section 7.4.24 , page 91)'' is not iso-8859-1 and recipients may not under-
7728 stand UTF-8, it is advisable to include in the list an appropriate widely used
7729 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7730 instead of or after iso-8859-1.
7732 _
\b7_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7736 Default: '/usr/sbin/sendmail -oem -oi'
7738 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7739 Mutt-ng expects that the specified program interprets additional arguments as
7740 recipient addresses.
7742 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
7748 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.249 ,
7749 page 146)'' process to finish before giving up and putting delivery in the
7752 Mutt-ng interprets the value of this variable as follows:
7755 number of seconds to wait for sendmail to finish before continuing
7758 wait forever for sendmail to finish
7761 always put sendmail in the background without waiting
7763 Note that if you specify a value other than 0, the output of the child process
7764 will be put in a temporary file. If there is some error, you will be informed
7765 as to where to find the output.
7767 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\bs_
\bh_
\be_
\bl_
\bl
7773 Command to use when spawning a subshell. By default, the user's login shell
7774 from /etc/passwd is used.
7776 The Mutt Next Generation E-Mail Client 148
7778 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
7784 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
7785 7.4.256 , page 148) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
7786 split a folder name into ``hierarchy items.''
7788 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
7794 This specifies the delimiter between the sidebar (if visible) and other
7797 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
7803 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
7805 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7809 Default: '%m%?n?(%n)?%?f?[%f]?'
7811 This variable controls how message counts are printed when the sidebar is
7812 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
7813 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
7814 mbox-style mailboxes.)
7816 The following printf(3)-like sequences are supported all of which may be
7820 Number of deleted messages. 1)
7823 Number of flagged messages.
7826 Total number of messages.
7829 Total number of messages shown, i.e. not hidden by a limit. 1)
7831 The Mutt Next Generation E-Mail Client 149
7834 Number of new messages.
7837 Number of tagged messages. 1)
7839 1) These expandos only have a non-zero value for the current mailbox and will
7840 always be zero otherwise.
7842 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\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
7848 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
7849 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
7850 7.4.258 , page 148)'' is set to a too low value). For example, if the news-
7851 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
7852 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
7855 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
7856 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 7.4.252 , page 146) variable.
7858 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
7864 This specifies whether or not to show the sidebar (a list of folders specified
7865 with the ``mailboxes'' command).
7867 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
7873 The width of the sidebar.
7875 _
\b7_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
7881 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
7882 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 7.4.261 , page 149)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
7883 that you not unset this variable unless your ``signature'' contains just your
7884 name. The reason for this is because many software packages use ``-- \n'' to
7885 detect your signature.
7887 The Mutt Next Generation E-Mail Client 150
7889 For example, Mutt-ng has the ability to highlight the signature in a different
7890 color in the builtin pager.
7892 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
7898 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
7899 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
7900 know what you are doing, and are prepared to take some heat from netiquette
7903 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
7907 Default: '~/.signature'
7909 Specifies the filename of your signature, which is appended to all outgoing
7910 messages. If the filename ends with a pipe (``|''), it is assumed that file-
7911 name is a shell command and input should be read from its stdout.
7913 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7919 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
7920 people that want to sign off every message they send with their name.
7922 If you want to insert your website's URL, additional contact information or
7923 witty quotes into your mails, better use a signature file instead of the sig-
7926 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
7930 Default: '~f %s | ~s %s'
7932 Specifies how Mutt-ng should expand a simple search into a real search pattern.
7933 A simple search is one that does not contain any of the ~ operators. See
7934 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 7.2 , page 80)'' for more information on search patterns.
7936 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
7937 will automatically expand it to the value specified by this variable. For the
7938 default value it would be:
7942 The Mutt Next Generation E-Mail Client 151
7944 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
7950 Specifies time, in seconds, to pause while displaying certain informational
7951 messages, while moving from folder to folder and after expunging messages from
7952 the current folder. The default is to pause one second, so a value of zero for
7953 this option suppresses the pause.
7955 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
7961 Controls the display of lines longer than the screen width in the internal
7962 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
7963 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 7.4.122 ,
7964 page 116)'' variable.
7966 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
7968 Type: regular expression
7970 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
7972 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
7973 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.227 , page 140)'', most notably smileys in the
7976 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
7982 This flag controls whether you want to be asked to enter a label for a certifi-
7983 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
7986 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
7992 This variable contains the name of either a directory, or a file which contains
7993 trusted certificates for use with OpenSSL. (S/MIME only)
7995 _
\b7_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
7999 The Mutt Next Generation E-Mail Client 152
8003 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
8004 and retrieval of keys by itself. This is very basic right now, and keys and
8005 certificates are stored in two different directories, both named as the hash-
8006 value retrieved from OpenSSL. There is an index file which contains mailbox-
8007 address keyid pairs, and which can be manually edited. This one points to the
8008 location of the certificates. (S/MIME only)
8010 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8016 This format string specifies a command which is used to decrypt application/x-
8017 pkcs7-mime attachments.
8019 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
8023 Expands to the name of a file containing a message.
8026 Expands to the name of a file containing the signature part of a
8027 multipart/signed attachment when verifying it.
8030 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.272 ,
8034 One or more certificate IDs.
8037 The algorithm used for encryption.
8040 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
8041 7.4.268 , page 150) points to a directory or file, this expands to
8042 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.268 , page 150)' or
8043 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 7.4.268 , page 150)'.
8045 For examples on how to configure these formats, see the smime.rc in the sam-
8046 ples/ subdirectory which has been installed on your system alongside the docu-
8047 mentation. (S/MIME only)
8049 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\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
8055 The Mutt Next Generation E-Mail Client 153
8057 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
8058 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
8059 mailbox-address to determine the key to use. It will ask you to supply a key,
8060 if it can't find one. (S/MIME only)
8062 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
8068 This is the default key-pair to use for signing. This must be set to the keyid
8069 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
8071 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8077 This command is used to create encrypted S/MIME messages. (S/MIME only)
8079 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
8085 This sets the algorithm that should be used for encryption. Valid choices are
8086 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
8088 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
8090 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8096 This command is used to extract X509 certificates from a PKCS7 structure.
8099 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\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
8105 This command is used to extract the mail address(es) used for storing X509 cer-
8106 tificates, and for verification purposes (to check whether the certificate was
8107 issued for the sender's mailbox). (S/MIME only)
8109 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\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
8111 The Mutt Next Generation E-Mail Client 154
8117 This command is used to extract only the signers X509 certificate from a S/MIME
8118 signature, so that the certificate's owner may get compared to the email's
8119 ``From:'' header field. (S/MIME only)
8121 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\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
8127 This command is used to import a certificate via smime_keysng. (S/MIME only)
8129 _
\b7_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
8135 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
8136 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
8138 However, this has no effect while replying, since Mutt-ng will automatically
8139 select the same application that was used to sign/encrypt the original message.
8141 (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-
8142 tion 7.4.37 , page 94).) (S/MIME only)
8144 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
8150 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
8151 retrieval of keys/certs by itself. This is very basic right now, and stores
8152 keys and certificates in two different directories, both named as the hash-
8153 value retrieved from OpenSSL. There is an index file which contains mailbox-
8154 address keyid pair, and which can be manually edited. This one points to the
8155 location of the private keys. (S/MIME only)
8157 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8163 This command is used to extract PKCS7 structures of S/MIME signatures, in order
8164 to extract the public X509 certificate(s). (S/MIME only)
8166 The Mutt Next Generation E-Mail Client 155
8168 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8174 This command is used to created S/MIME signatures of type multipart/signed,
8175 which can be read by all mail clients. (S/MIME only)
8177 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\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
8183 This command is used to created S/MIME signatures of type application/x-
8184 pkcs7-signature, which can only be handled by mail clients supporting the
8185 S/MIME extension. (S/MIME only)
8187 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8193 The number of seconds after which a cached passphrase will expire if not used.
8196 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
8202 This command is used to verify S/MIME signatures of type multipart/signed.
8205 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\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
8211 This command is used to verify S/MIME signatures of type application/x-
8212 pkcs7-mime. (S/MIME only)
8214 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\bs_
\bm_
\bt_
\bp_
\b__
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be
8222 The Mutt Next Generation E-Mail Client 156
8224 If this variable is non-empty, it'll be used as the envelope sender. If it's
8225 empty (the default), the value of the regular From: header will be used.
8227 This may be necessary as some providers don't allow for arbitrary values as the
8228 envelope sender but only a particular one which may not be the same as the
8229 user's desired From: header.
8231 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
8239 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
8240 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
8241 _
\bm_
\ba_
\bi_
\bl (section 7.4.249 , page 146)'', and any associated variables.
8243 _
\b7_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
8251 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section
8252 7.4.292 , page 155)'' is set, but this variable is not, you will be prompted
8253 for a password when sending.
8255 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
8256 the superuser of your machine may read it regardless of the file's permissions.
8258 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
8266 Defines the port that the SMTP host is listening on for mail delivery. Must be
8267 specified as a number.
8269 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
8270 will probably desire 587, the mail submission port.
8272 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
8278 The Mutt Next Generation E-Mail Client 157
8280 Availability: SMTP (and SSL)
8282 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
8283 server does not support STARTTLS or there is an error in the TLS Handshake, the
8284 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
8285 continue without TLS in case of an error. Muttng still needs to have SSL sup-
8286 port enabled in order to use it.
8288 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8296 Defines the username to use with SMTP AUTH. Setting this variable will cause
8297 Mutt-ng to attempt to use SMTP AUTH when sending.
8299 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bo_
\br_
\bt
8305 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8310 mailbox-order (unsorted)
8318 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8319 (example: set sort=reverse-date-sent).
8321 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8327 Specifies how the entries in the ``alias'' menu are sorted. The following are
8330 The Mutt Next Generation E-Mail Client 158
8332 address (sort alphabetically by email address)
8333 alias (sort alphabetically by alias name)
8334 unsorted (leave in order specified in .muttrc)
8336 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8342 When sorting by threads, this variable controls how threads are sorted in rela-
8343 tion to other threads, and how the branches of the thread trees are sorted.
8344 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.293 , page 156)'' can,
8345 except threads (in that case, Mutt-ng will just use date-sent). You can also
8346 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8347 come after reverse-. The last- prefix causes messages to be sorted against its
8348 siblings by which has the last descendant, using the rest of sort_aux as an
8351 For instance, set sort_aux=last-date-received would mean that if a new message
8352 is received in a thread, that thread becomes the last one displayed (or the
8353 first, if you have set sort=reverse-threads.)
8355 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.293 , page 156)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8356 (section 7.4.295 , page 156) is reversed again (which is not the right thing
8357 to do, but kept to not break any existing configuration setting).
8359 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8365 Specifies how to sort entries in the file browser. By default, the entries are
8366 sorted alphabetically. Valid values:
8368 alpha (alphabetically)
8373 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8374 (example: set sort_browser=reverse-date).
8376 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8382 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
8384 The Mutt Next Generation E-Mail Client 159
8386 (section 7.4.314 , page 163)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8387 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.297 ,
8388 page 157) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8389 sage by subject if the subject of the child message starts with a substring
8390 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 7.4.233 , page 142)''. With
8391 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 7.4.297 , page 157) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8392 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
8393 7.4.233 , page 142)'' parts of both messages are identical.
8395 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8401 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.298 , page 157)'' controls what happens when
8402 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will over-
8403 write any previous matches value for the spam label. If _
\bs_
\be_
\bt, each successive
8404 match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 7.4.298 ,
8405 page 157)'' as a separator.
8407 _
\b7_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8413 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8414 you can specify its location with this variable. Mutt-ng will automatically
8415 set this variable to the value of the environment variable $MAIL if it is not
8418 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8424 This variable specifies a file containing trusted CA certificates. Any server
8425 certificate that is signed with one of these CA certificates are also automati-
8428 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8430 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8438 The file containing a client certificate and its associated private key.
8440 The Mutt Next Generation E-Mail Client 160
8442 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8448 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8449 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8450 server does not advertise the capability, since it would otherwise have to
8451 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8452 7.4.304 , page 159)''.
8454 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8460 Availability: GNUTLS
8462 This variable specifies the minimum acceptable prime size (in bits) for use in
8463 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8466 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8472 Availability: SSL or GNUTLS
8474 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8475 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8476 regardless of the server's capabilities.
8478 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8486 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8489 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8495 Availability: SSL or GNUTLS
8497 The Mutt Next Generation E-Mail Client 161
8499 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8502 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8508 Availability: SSL or GNUTLS
8510 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8513 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8521 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8522 store when checking if server certificate is signed by a trusted CA.
8524 _
\b7_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8530 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8531 tion 7.4.310 , page 160)''. The first character is used when the mailbox is
8532 unchanged. The second is used when the mailbox has been changed, and it needs
8533 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8534 if the mailbox will not be written when exiting that mailbox (You can toggle
8535 whether to write changes to a mailbox with the toggle-write operation, bound by
8536 default to ``%''). The fourth is used to indicate that the current folder has
8537 been opened in attach-message mode (Certain operations like composing a new
8538 mail, replying, forwarding, etc. are not permitted in this mode).
8540 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8544 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8545 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8546 %l?]---(%s/%S)-%>-(%P)---'
8548 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8549 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.111 , page 111)'', but has
8550 its own set of printf(3)-like sequences:
8552 The Mutt Next Generation E-Mail Client 162
8555 number of mailboxes with new mail *
8558 the short pathname of the current mailbox
8561 number of deleted messages *
8564 the full pathname of the current mailbox
8567 number of flagged messages *
8573 size (in bytes) of the current mailbox *
8576 size (in bytes) of the messages shown (i.e., which match the cur-
8580 the number of messages in the mailbox *
8583 the number of messages shown (i.e., which match the current limit)
8587 number of new messages in the mailbox *
8590 number of old unread messages *
8593 number of postponed messages *
8596 percentage of the way through the index
8599 modified/read-only/won't-write/attach-message indicator, according
8600 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 7.4.309 , page 160)
8603 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.293 , page 156))
8606 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 7.4.295 , page
8609 The Mutt Next Generation E-Mail Client 163
8612 number of tagged messages *
8615 number of unread messages *
8618 Mutt-ng version string
8621 currently active limit pattern, if any *
8624 right justify the rest of the string and pad with 'X'
8627 pad to the end of the line with 'X'
8629 * = can be optionally printed if nonzero
8631 Some of the above sequences can be used to optionally print a string if their
8632 value is nonzero. For example, you may only want to see the number of flagged
8633 messages if such messages exist, since zero is not particularly meaningful. To
8634 optionally print a string based upon one of the above sequences, the following
8637 %?<sequence_char>?<optional_string>?
8639 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
8640 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
8641 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8644 Here is an example illustrating how to optionally print the number of new mes-
8647 %?n?%n new messages.?
8649 Additionally you can switch between two strings, the first one, if a value is
8650 zero, the second one, if the value is nonzero, by using the following con-
8653 %?<sequence_char>?<if_string>&<else_string>?
8655 You can additionally force the result of any printf(3)-like sequence to be low-
8656 ercase by prefixing the sequence character with an underscore (_) sign. For
8657 example, if you want to display the local hostname in lowercase, you would use:
8661 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8662 replace any dots in the expansion by underscores. This might be helpful with
8663 IMAP folders that don't like dots in folder names.
8665 The Mutt Next Generation E-Mail Client 164
8667 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8673 Setting this variable causes the ``status bar'' to be displayed on the first
8674 line of the screen rather than near the bottom.
8676 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8682 With mailto: style links, a body as well as arbitrary header information may be
8683 embedded. This may lead to (user) headers being overwriten without note if
8684 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98)'' is unset.
8686 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8687 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8688 message including headers will be shown in the editor regardless of what
8689 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 7.4.55 , page 98)'' is set to.
8691 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8697 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8698 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8699 messages are often generated by old mailers or buggy mailers like MS Outlook
8700 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 7.4.11 , page 88).
8702 This option also replaces linear-white-space between encoded-word and *text to
8703 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8704 from being devided into multiple lines.
8706 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8712 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8713 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 7.4.293 , page 156)'' by mes-
8714 sage threads. By default, messages with the same subject are grouped together
8715 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8716 mailbox where you might have several unrelated messages with the subject ``hi''
8717 which will get grouped together.
8719 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8721 The Mutt Next Generation E-Mail Client 165
8727 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8728 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 7.4.316 , page 163) when replying. This is
8729 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8732 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8734 Type: regular expression
8736 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8738 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 7.4.315 , page 163) is _
\bs_
\be_
\bt, mutt-ng
8739 will remove this trailing part of the ``Subject'' line when replying if it
8740 won't be empty afterwards.
8742 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
8748 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
8749 i.e. a space will be inserted between the quote characters and the actual text.
8751 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
8757 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
8758 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
8759 mand like ``xterm -e muttng.''
8761 _
\b7_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
8767 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
8768 format is easier to handle for some mailing software, and generally just looks
8769 like ordinary text. To actually make use of this format's features, you'll
8770 need support in your editor.
8772 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 7.4.110 , page 111) is ignored when this
8775 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8777 The Mutt Next Generation E-Mail Client 166
8783 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
8784 tion 7.2 , page 80)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
8785 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
8786 as they appear in the folder.
8788 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
8794 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
8795 messages by subject.
8797 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bt_
\bi_
\bl_
\bd_
\be
8803 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
8806 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8812 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
8813 pressed in the main menu before timing out and checking for new mail. A value
8814 of zero or less will cause Mutt-ng to never time out.
8816 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
8822 This variable allows you to specify where Mutt-ng will place its temporary
8823 files needed for displaying and composing messages. If this variable is not
8824 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
8827 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8833 The Mutt Next Generation E-Mail Client 167
8835 Controls the character used to indicate mail addressed to you. The first char-
8836 acter is the one used when the mail is NOT addressed to your address (default:
8837 space). The second is used when you are the only recipient of the message
8838 (default: +). The third is when your address appears in the ``To:'' header
8839 field, but you are not the only recipient of the message (default: T). The
8840 fourth character is used when your address is specified in the ``Cc:'' header
8841 field, but you are not the only recipient. The fifth character is used to
8842 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
8843 when a mail was sent to a mailing-list you're subscribe to (default: L).
8845 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bt_
\br_
\ba_
\bs_
\bh
8851 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
8852 marked for deletion will be moved, instead of being irremediably purged.
8854 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
8855 that there is no way to recover mail.
8857 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
8863 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
8864 a raw socket. You may be able to use this to set up preauthenticated connec-
8865 tions to your IMAP/POP3 server. Example:
8867 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
8869 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
8870 without having to enter a password.
8872 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bu_
\bm_
\ba_
\bs_
\bk
8878 This sets the umask that will be used by Mutt-ng when creating all kinds of
8879 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
8881 _
\b7_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
8887 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
8888 rent thread is _
\bu_
\bncollapsed.
8890 The Mutt Next Generation E-Mail Client 168
8892 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
8898 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
8899 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection
8900 with the SMTP support via libESMTP. Otherwise you may not be able to send
8903 When _
\bs_
\be_
\bt, Mutt-ng will either invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 7.4.249 , page
8904 146)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP
8905 negotiation or tell libESMTP to do so.
8907 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
8913 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
8914 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 7.4.90 , page 106)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
8915 no addresses will be qualified.
8917 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
8923 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
8924 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
8925 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 35)'' command.
8927 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
8935 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
8937 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
8940 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
8946 The Mutt Next Generation E-Mail Client 169
8948 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
8949 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
8950 mally, the default should work.
8952 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bu_
\bs_
\be_
\br_
\b__
\ba_
\bg_
\be_
\bn_
\bt
8958 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
8959 cating which version of Mutt-ng was used for composing them.
8961 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
8967 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
8970 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
8976 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-
8977 _
\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.
8979 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
8980 75)'', provided that the corresponding mailcap entry has a needsterminal flag,
8981 and the external program is interactive.
8983 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
8984 a key only if the external command returned a non-zero status.
8986 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bw_
\be_
\be_
\bd
8992 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
8993 replying to messages.
8995 _
\b7_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
9001 Controls whether searches wrap around the end of the mailbox.
9003 The Mutt Next Generation E-Mail Client 170
9005 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
9006 searches will not wrap.
9008 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
9014 Controls the size of the margin remaining at the right side of the terminal
9015 when Mutt-ng's pager does smart wrapping.
9017 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
9023 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
9024 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
9026 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
9032 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
9033 indicate progress. If set to 0, only a single message will be displayed before
9036 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 7.4.228 , page 141)'' variable.
9038 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
9042 Default: 'M%?n?AIL&ail?'
9044 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-
9045 tion 7.4.345 , page 169) is _
\bs_
\be_
\bt. This string is identical in formatting to the
9046 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 7.4.310 , page 160)''.
9048 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b4 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
9054 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.345 , page 169) is _
\bs_
\be_
\bt, this string will be
9055 used to set the title when leaving mutt-ng. For terminal-based programs,
9056 there's no easy and portable way to read the current title so mutt-ng cannot
9057 read it upon startup and restore it when exiting.
9059 The Mutt Next Generation E-Mail Client 171
9061 Based on the xterm FAQ, the following might work:
9063 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
9066 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b5 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
9072 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
9073 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
9076 _
\b7_
\b._
\b4_
\b._
\b3_
\b4_
\b6 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
9080 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
9082 Controls the format of the title bar of the xterm provided that
9083 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 7.4.345 , page 169) has been _
\bs_
\be_
\bt. This string is
9084 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.310 ,
9087 _
\b7_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
9089 The following is the list of available functions listed by the mapping in which
9090 they are available. The default key setting is given, and an explanation of
9091 what the function does. The key bindings of these functions can be changed
9092 with the _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) command.
9094 _
\b7_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
9096 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
9097 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
9098 tings for this menu will affect the default bindings for all menus (except as
9101 The Mutt Next Generation E-Mail Client 172
9103 bottom-page L move to the bottom of the page
9104 current-bottom not bound move current entry to bottom of page
9105 current-middle not bound move current entry to middle of page
9106 current-top not bound move current entry to top of page
9107 enter-command : enter a muttngrc command
9108 exit q exit this menu
9109 first-entry = move to the first entry
9110 half-down ] scroll down 1/2 page
9111 half-up [ scroll up 1/2 page
9113 jump number jump to an index number
9114 last-entry * move to the last entry
9115 middle-page M move to the middle of the page
9116 next-entry j move to the next entry
9117 next-line > scroll down one line
9118 next-page z move to the next page
9119 previous-entry k move to the previous entry
9120 previous-line < scroll up one line
9121 previous-page Z move to the previous page
9122 refresh ^L clear and redraw the screen
9123 search / search for a regular expression
9124 search-next n search for next match
9125 search-opposite not bound search for next match in opposite direction
9126 search-reverse ESC / search backwards for a regular expression
9127 select-entry RET select the current entry
9128 shell-escape ! run a program in a subshell
9129 tag-entry t toggle the tag on the current entry
9130 tag-prefix ; apply next command to tagged entries
9131 tag-prefix-cond not bound apply next function ONLY to tagged messages
9132 top-page H move to the top of the page
9133 what-key not bound display the keycode for a key press
9135 _
\b7_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
9137 The Mutt Next Generation E-Mail Client 173
9139 bounce-message b remail a message to another user
9140 change-folder c open a different folder
9141 change-folder-readonly ESC c open a different folder in read only mode
9142 check-traditional-pgp ESC P check for classic pgp
9143 clear-flag W clear a status flag from a message
9144 copy-message C copy a message to a file/mailbox
9145 create-alias a create an alias from a message sender
9146 decode-copy ESC C decode a message and copy it to a file/mailbox
9147 decode-save ESC s decode a message and save it to a file/mailbox
9148 delete-message d delete the current entry
9149 delete-pattern D delete messages matching a pattern
9150 delete-subthread ESC d delete all messages in subthread
9151 delete-thread ^D delete all messages in thread
9152 display-address @ display full address of sender
9153 display-toggle-weed h display message and toggle header weeding
9154 display-message RET display a message
9155 edit e edit the current message
9156 edit-type ^E edit the current message's Content-Type
9157 exit x exit without saving changes
9158 extract-keys ^K extract PGP public keys
9159 fetch-mail G retrieve mail from POP server
9160 flag-message F toggle a message's 'important' flag
9161 forget-passphrase ^F wipe PGP passphrase from memory
9162 forward-message f forward a message with comments
9163 group-reply g reply to all recipients
9164 limit l show only messages matching a pattern
9165 list-reply L reply to specified mailing list
9166 mail m compose a new mail message
9167 mail-key ESC k mail a PGP public key
9168 next-new TAB jump to the next new message
9169 next-subthread ESC n jump to the next subthread
9170 next-thread ^N jump to the next thread
9171 next-undeleted j move to the next undeleted message
9172 next-unread not bound jump to the next unread message
9173 parent-message P jump to parent message in thread
9174 pipe-message | pipe message/attachment to a shell command
9175 previous-new ESC TAB jump to the previous new message
9176 previous-page Z move to the previous page
9177 previous-subthread ESC p jump to previous subthread
9178 previous-thread ^P jump to previous thread
9179 previous-undeleted k move to the last undelete message
9180 previous-unread not bound jump to the previous unread message
9181 print-message p print the current entry
9182 query Q query external program for addresses
9183 quit q save changes to mailbox and quit
9184 read-subthread ESC r mark the current subthread as read
9185 read-thread ^R mark the current thread as read
9186 recall-message R recall a postponed message
9187 reply r reply to a message
9188 resend-message ESC e resend message and preserve MIME structure
9189 save-message s save message/attachment to a file
9190 set-flag w set a status flag on a message
9191 show-version V show the Mutt-ng version number and date
9192 show-limit ESC l show currently active limit pattern, if any
9194 The Mutt Next Generation E-Mail Client 174
9196 sort-mailbox o sort messages
9197 sort-reverse O sort messages in reverse order
9198 sync-mailbox $ save changes to mailbox
9199 tag-pattern T tag messages matching a pattern
9200 tag-thread ESC t tag/untag all messages in the current thread
9201 toggle-new N toggle a message's 'new' flag
9202 toggle-write % toggle whether the mailbox will be rewritten
9203 undelete-message u undelete the current entry
9204 undelete-pattern U undelete messages matching a pattern
9205 undelete-subthread ESC u undelete all messages in subthread
9206 undelete-thread ^U undelete all messages in thread
9207 untag-pattern ^T untag messages matching a pattern
9208 view-attachments v show MIME attachments
9210 _
\b7_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
9212 The Mutt Next Generation E-Mail Client 175
9214 bottom not bound jump to the bottom of the message
9215 bounce-message b remail a message to another user
9216 change-folder c open a different folder
9217 change-folder-readonly ESC c open a different folder in read only mode
9218 check-traditional-pgp ESC P check for classic pgp
9219 copy-message C copy a message to a file/mailbox
9220 create-alias a create an alias from a message sender
9221 decode-copy ESC C decode a message and copy it to a file/mailbox
9222 decode-save ESC s decode a message and save it to a file/mailbox
9223 delete-message d delete the current entry
9224 delete-subthread ESC d delete all messages in subthread
9225 delete-thread ^D delete all messages in thread
9226 display-address @ display full address of sender
9227 display-toggle-weed h display message and toggle header weeding
9228 edit e edit the current message
9229 edit-type ^E edit the current message's Content-Type
9230 enter-command : enter a muttngrc command
9231 exit i return to the main-menu
9232 extract-keys ^K extract PGP public keys
9233 flag-message F toggle a message's 'important' flag
9234 forget-passphrase ^F wipe PGP passphrase from memory
9235 forward-message f forward a message with comments
9236 group-reply g reply to all recipients
9237 half-up not bound move up one-half page
9238 half-down not bound move down one-half page
9240 list-reply L reply to specified mailing list
9241 mail m compose a new mail message
9242 mail-key ESC k mail a PGP public key
9243 mark-as-new N toggle a message's 'new' flag
9244 next-line RET scroll down one line
9245 next-entry J move to the next entry
9246 next-new TAB jump to the next new message
9247 next-page move to the next page
9248 next-subthread ESC n jump to the next subthread
9249 next-thread ^N jump to the next thread
9250 next-undeleted j move to the next undeleted message
9251 next-unread not bound jump to the next unread message
9252 parent-message P jump to parent message in thread
9253 pipe-message | pipe message/attachment to a shell command
9254 previous-line BackSpace scroll up one line
9255 previous-entry K move to the previous entry
9256 previous-new not bound jump to the previous new message
9257 previous-page - move to the previous page
9258 previous-subthread ESC p jump to previous subthread
9259 previous-thread ^P jump to previous thread
9260 previous-undeleted k move to the last undelete message
9261 previous-unread not bound jump to the previous unread message
9262 print-message p print the current entry
9263 quit Q save changes to mailbox and quit
9264 read-subthread ESC r mark the current subthread as read
9265 read-thread ^R mark the current thread as read
9266 recall-message R recall a postponed message
9267 redraw-screen ^L clear and redraw the screen
9269 The Mutt Next Generation E-Mail Client 176
9271 reply r reply to a message
9272 save-message s save message/attachment to a file
9273 search / search for a regular expression
9274 search-next n search for next match
9275 search-opposite not bound search for next match in opposite direction
9276 search-reverse ESC / search backwards for a regular expression
9277 search-toggle \ toggle search pattern coloring
9278 shell-escape ! invoke a command in a subshell
9279 show-version V show the Mutt-ng version number and date
9280 skip-quoted S skip beyond quoted text
9281 sync-mailbox $ save changes to mailbox
9282 tag-message t tag a message
9283 toggle-quoted T toggle display of quoted text
9284 top ^ jump to the top of the message
9285 undelete-message u undelete the current entry
9286 undelete-subthread ESC u undelete all messages in subthread
9287 undelete-thread ^U undelete all messages in thread
9288 view-attachments v show MIME attachments
9290 _
\b7_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9292 search / search for a regular expression
9293 search-next n search for next match
9294 search-reverse ESC / search backwards for a regular expression
9296 _
\b7_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9298 create-alias a create an alias from a message sender
9299 mail m compose a new mail message
9300 query Q query external program for addresses
9301 query-append A append new query results to current results
9302 search / search for a regular expression
9303 search-next n search for next match
9304 search-opposite not bound search for next match in opposite direction
9305 search-reverse ESC / search backwards for a regular expression
9307 _
\b7_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9309 The Mutt Next Generation E-Mail Client 177
9311 bounce-message b remail a message to another user
9312 collapse-parts v toggle display of subparts
9313 delete-entry d delete the current entry
9314 display-toggle-weed h display message and toggle header weeding
9315 edit-type ^E edit the current entry's Content-Type
9316 extract-keys ^K extract PGP public keys
9317 forward-message f forward a message with comments
9318 group-reply g reply to all recipients
9319 list-reply L reply to specified mailing list
9320 pipe-entry | pipe message/attachment to a shell command
9321 print-entry p print the current entry
9322 reply r reply to a message
9323 resend-message ESC e resend message and preserve MIME structure
9324 save-entry s save message/attachment to a file
9325 undelete-entry u undelete the current entry
9326 view-attach RET view attachment using mailcap entry if necessary
9327 view-mailcap m force viewing of attachment using mailcap
9328 view-text T view attachment as text
9330 _
\b7_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9332 The Mutt Next Generation E-Mail Client 178
9334 attach-file a attach a file(s) to this message
9335 attach-message A attach message(s) to this message
9336 attach-key ESC k attach a PGP public key
9337 copy-file C save message/attachment to a file
9338 detach-file D delete the current entry
9339 display-toggle-weed h display message and toggle header weeding
9340 edit-bcc b edit the BCC list
9341 edit-cc c edit the CC list
9342 edit-description d edit attachment description
9343 edit-encoding ^E edit attachment transfer-encoding
9344 edit-fcc f enter a file to save a copy of this message in
9345 edit-from ESC f edit the from: field
9346 edit-file ^X e edit the file to be attached
9347 edit-headers E edit the message with headers
9348 edit e edit the message
9349 edit-mime m edit attachment using mailcap entry
9350 edit-reply-to r edit the Reply-To field
9351 edit-subject s edit the subject of this message
9352 edit-to t edit the TO list
9353 edit-type ^T edit attachment type
9354 filter-entry F filter attachment through a shell command
9355 forget-passphrase ^F wipe PGP passphrase from memory
9356 ispell i run ispell on the message
9357 new-mime n compose new attachment using mailcap entry
9358 pgp-menu p show PGP options
9359 pipe-entry | pipe message/attachment to a shell command
9360 postpone-message P save this message to send later
9361 print-entry l print the current entry
9362 rename-file R rename/move an attached file
9363 send-message y send the message
9364 toggle-unlink u toggle whether to delete file after sending it
9365 view-attach RET view attachment using mailcap entry if necessary
9366 write-fcc w write the message to a folder
9368 _
\b7_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9370 delete-entry d delete the current entry
9371 undelete-entry u undelete the current entry
9373 _
\b7_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9375 The Mutt Next Generation E-Mail Client 179
9377 change-dir c change directories
9378 check-new TAB check mailboxes for new mail
9379 enter-mask m enter a file mask
9380 search / search for a regular expression
9381 search-next n search for next match
9382 search-reverse ESC / search backwards for a regular expression
9383 select-new N select a new file in this directory
9384 sort o sort messages
9385 sort-reverse O sort messages in reverse order
9386 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9387 view-file SPACE view file
9388 subscribe s subscribe to current mailbox (IMAP Only)
9389 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9390 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9392 _
\b7_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9394 view-name % view the key's user id
9395 verify-key c verify a PGP public key
9397 _
\b7_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9399 backspace BackSpace delete the char in front of the cursor
9400 backward-char ^B move the cursor one character to the left
9401 backward-word ESC b move the cursor to the previous word
9402 bol ^A jump to the beginning of the line
9403 buffy-cycle Space cycle among incoming mailboxes
9404 capitalize-word ESC c uppercase the first character in the word
9405 complete TAB complete filename or alias
9406 complete-query ^T complete address with query
9407 delete-char ^D delete the char under the cursor
9408 downcase-word ESC l lowercase all characters in current word
9409 eol ^E jump to the end of the line
9410 forward-char ^F move the cursor one character to the right
9411 forward-word ESC f move the cursor to the next word
9412 history-down not bound scroll down through the history list
9413 history-up not bound scroll up through the history list
9414 kill-eol ^K delete chars from cursor to end of line
9415 kill-eow ESC d delete chars from cursor to end of word
9416 kill-line ^U delete all chars on the line
9417 kill-word ^W delete the word in front of the cursor
9418 quote-char ^V quote the next typed key
9419 transpose-chars not bound transpose character under cursor with previous
9420 upcase-word ESC u uppercase all characters in current word
9422 _
\b8_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9424 The Mutt Next Generation E-Mail Client 180
9426 _
\b8_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9428 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9429 back in the ELM-ME days.
9431 The following people have been very helpful to the development of Mutt:
9433 Vikas Agnihotri <vikasa@writeme.com>,
9435 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9437 Aric Blumer <aric@fore.com>,
9439 John Capo <jc@irbs.com>,
9441 David Champion <dgc@uchicago.edu,
9443 Brendan Cully <brendan@kublai.com>,
9445 Liviu Daia <daia@stoilow.imar.ro>,
9447 Thomas E. Dickey <dickey@herndon4.his.com>,
9449 David DeSimone <fox@convex.hp.com>,
9451 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9453 Ruslan Ermilov <ru@freebsd.org>,
9455 Edmund Grimley Evans <edmundo@rano.org,
9457 Michael Finken <finken@conware.de>,
9459 Sven Guckes <guckes@math.fu-berlin.de>,
9461 Lars Hecking <lhecking@nmrc.ie>,
9463 Mark Holloman <holloman@nando.net>,
9465 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9467 Marco d'Itri <md@linux.it>,
9469 Bjrn Jacke <bjacke@suse.com>,
9471 Byrial Jensen <byrial@image.dk>,
9473 David Jeske <jeske@igcom.net>,
9475 Christophe Kalt <kalt@hugo.int-evry.fr>,
9477 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9479 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9481 The Mutt Next Generation E-Mail Client 181
9483 Brandon Long <blong@fiction.net>,
9485 Jimmy Mkel <jmy@flashback.net>,
9487 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9489 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9491 Andrew W. Nosenko <awn@bcs.zp.ua>,
9493 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9495 Clint Olsen <olsenc@ichips.intel.com>,
9497 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9499 Thomas Parmelan <tom@ankh.fr.eu.org>,
9501 Ollivier Robert <roberto@keltia.freenix.fr>,
9503 Thomas Roessler <roessler@does-not-exist.org>,
9505 Roland Rosenfeld <roland@spinnaker.de>,
9507 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9509 Allain Thivillon <Allain.Thivillon@alma.fr>,
9511 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9513 Vsevolod Volkov <vvv@lucky.net>,
9515 Ken Weinert <kenw@ihs.com>
9517 Mutt-ng is developed by the following people:
9519 Andreas Krennmair <ak@synflood.at>
9521 Nico Golde <nico@ngolde.de>
9523 Rocco Rutte <pdmef@cs.tu-berlin.de>
9525 The following people have been very helpful to the development of Mutt-ng:
9527 Christian Gall <cg@cgall.de>
9529 Iain Lea <iain@bricbrac.de>
9531 Andreas Kneib <akneib@gmx.net>
9533 Carsten Schoelzki <cjs@weisshuhn.de>
9535 Elimar Riesebieter <riesebie@lxtec.de>
9537 The Mutt Next Generation E-Mail Client 182
9539 _
\b8_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9541 This document was written in SGML, and then rendered using the sgml-tools pack-
9544 The Mutt Next Generation E-Mail Client 183
9548 1. Introduction .......................................................... 1
9549 1.1 Overview ........................................................ 1
9550 1.2 Mutt-ng Home Page ............................................... 1
9551 1.3 Mailing Lists ................................................... 1
9552 1.4 Software Distribution Sites ..................................... 2
9553 1.5 IRC ............................................................. 2
9554 1.6 Weblog .......................................................... 2
9555 1.7 Copyright ....................................................... 2
9557 2. Getting Started ..................................................... 2
9558 2.1 Basic Concepts .............................................. 2
9559 2.1.1 Screens and Menus 3
9560 2.1.2 Configuration 3
9563 2.1.5 Modularization 4
9565 2.2 Screens and Menus ........................................... 4
9568 2.2.3 File Browser 5
9571 2.2.6 Compose Menu 6
9573 2.2.8 Attachment Menu 6
9575 2.3 Moving Around in Menus .......................................... 6
9576 2.4 Editing Input Fields ............................................ 7
9577 2.5 Reading Mail - The Index and Pager .............................. 8
9578 2.5.1 The Message Index 8
9580 2.5.3 Threaded Mode 11
9581 2.5.4 Miscellaneous Functions 11
9582 2.6 Sending Mail ................................................... 14
9583 2.6.1 Composing new messages 14
9585 2.6.3 Editing the message header 17
9586 2.6.4 Using Mutt-ng with PGP 18
9587 2.6.5 Sending anonymous messages via mixmaster 19
9588 2.7 Forwarding and Bouncing Mail ................................... 19
9589 2.8 Postponing Mail ................................................ 20
9591 3. Configuration ........................................................ 21
9592 3.1 Locations of Configuration Files ............................... 21
9593 3.2 Syntax of Initialization Files ................................. 21
9594 3.3 Defining/Using aliases ......................................... 23
9595 3.4 Changing the default key bindings .............................. 24
9596 3.5 Defining aliases for character sets ........................... 26
9600 3.6 Setting variables based upon mailbox ........................... 26
9601 3.7 Keyboard macros ................................................ 27
9602 3.8 Using color and mono video attributes .......................... 28
9603 3.9 Ignoring (weeding) unwanted message headers .................... 30
9604 3.10 Alternative addresses .......................................... 31
9605 3.11 Format = Flowed .............................................. 31
9606 3.11.1 Introduction 31
9607 3.11.2 Receiving: Display Setup 31
9609 3.11.4 Additional Notes 33
9610 3.12 Mailing lists .................................................. 33
9611 3.13 Using Multiple spool mailboxes ................................. 34
9612 3.14 Defining mailboxes which receive mail .......................... 34
9613 3.15 User defined headers ........................................... 35
9614 3.16 Defining the order of headers when viewing messages ............ 36
9615 3.17 Specify default save filename .................................. 36
9616 3.18 Specify default Fcc: mailbox when composing .................... 36
9617 3.19 Specify default save filename and default Fcc: mailbox at once . 37
9618 3.20 Change settings based upon message recipients .................. 37
9619 3.21 Change settings before formatting a message .................... 38
9620 3.22 Choosing the cryptographic key of the recipient ................ 38
9621 3.23 Adding key sequences to the keyboard buffer .................... 38
9622 3.24 Executing functions ............................................ 39
9623 3.25 Message Scoring ................................................ 39
9624 3.26 Spam detection ................................................. 40
9625 3.27 Setting variables .............................................. 42
9626 3.28 Reading initialization commands from another file .............. 43
9627 3.29 Removing hooks ................................................. 43
9628 3.30 Sharing Setups ............................................. 43
9629 3.30.1 Character Sets 43
9630 3.30.2 Modularization 44
9631 3.30.3 Conditional parts 44
9632 3.31 Obsolete Variables ............................................. 46
9634 4. Advanced Usage ....................................................... 46
9635 4.1 Regular Expressions ............................................ 46
9636 4.2 Patterns ....................................................... 49
9637 4.2.1 Complex Patterns 49
9638 4.2.2 Patterns and Dates 50
9639 4.3 Format Strings ............................................. 50
9640 4.3.1 Introduction 50
9641 4.3.2 Conditional Expansion 52
9642 4.3.3 Modifications and Padding 53
9643 4.4 Using Tags ..................................................... 53
9644 4.5 Using Hooks .................................................... 54
9645 4.5.1 Message Matching in Hooks 55
9646 4.6 Using the sidebar .............................................. 55
9647 4.7 External Address Queries ....................................... 56
9648 4.8 Mailbox Formats ................................................ 57
9649 4.9 Mailbox Shortcuts .............................................. 58
9650 4.10 Handling Mailing Lists ......................................... 58
9651 4.11 Editing threads ................................................ 59
9652 4.11.1 Linking threads 60
9656 4.11.2 Breaking threads 60
9657 4.12 Delivery Status Notification (DSN) Support ..................... 60
9658 4.13 POP3 Support (OPTIONAL) ........................................ 60
9659 4.14 IMAP Support (OPTIONAL) ........................................ 61
9660 4.14.1 The Folder Browser 62
9661 4.14.2 Authentication 62
9662 4.15 NNTP Support (OPTIONAL) ........................................ 63
9663 4.15.1 Again: Scoring 63
9664 4.16 SMTP Support (OPTIONAL) ........................................ 64
9665 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 65
9666 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 65
9667 4.19 Compressed folders Support (OPTIONAL) .......................... 65
9668 4.19.1 Open a compressed mailbox for reading 66
9669 4.19.2 Write a compressed mailbox 66
9670 4.19.3 Append a message to a compressed mailbox 67
9671 4.19.4 Encrypted folders 68
9673 5. Mutt-ng's MIME Support ............................................... 68
9674 5.1 Using MIME in Mutt ............................................. 68
9675 5.1.1 Viewing MIME messages in the pager 68
9676 5.1.2 The Attachment Menu 69
9677 5.1.3 The Compose Menu 69
9678 5.2 MIME Type configuration with mime.types ........................ 69
9679 5.3 MIME Viewer configuration with mailcap ......................... 70
9680 5.3.1 The Basics of the mailcap file 71
9681 5.3.2 Secure use of mailcap 72
9682 5.3.3 Advanced mailcap Usage 72
9683 5.3.4 Example mailcap files 75
9684 5.4 MIME Autoview .................................................. 76
9685 5.5 MIME Multipart/Alternative ..................................... 77
9686 5.6 MIME Lookup .................................................... 77
9688 6. Security Considerations ............................................ 78
9689 6.1 Passwords .................................................. 78
9690 6.2 Temporary Files ............................................ 78
9691 6.3 Information Leaks ............................................ 78
9692 6.3.1 Message-ID: headers 78
9693 6.3.2 mailto:-style links 79
9694 6.4 External applications ...................................... 79
9698 7. Reference ............................................................ 80
9699 7.1 Command line options ........................................... 80
9700 7.2 Patterns ....................................................... 81
9701 7.3 Configuration Commands ......................................... 83
9702 7.4 Configuration variables .......................................... 85
9703 7.4.1 abort_nosubject 86
9704 7.4.2 abort_unmodified 87
9706 7.4.4 alias_format 87
9712 7.4.7 arrow_cursor 88
9713 7.4.8 ascii_chars 88
9716 7.4.11 assumed_charset 89
9717 7.4.12 attach_format 89
9718 7.4.13 attach_sep 90
9719 7.4.14 attach_split 90
9720 7.4.15 attribution 90
9726 7.4.21 bounce_delivered 91
9727 7.4.22 braille_friendly 92
9728 7.4.23 certificate_file 92
9731 7.4.26 collapse_unread 93
9732 7.4.27 compose_format 93
9733 7.4.28 config_charset 93
9734 7.4.29 confirmappend 93
9735 7.4.30 confirmcreate 94
9736 7.4.31 connect_timeout 94
9737 7.4.32 content_type 94
9739 7.4.34 crypt_autoencrypt 94
9740 7.4.35 crypt_autopgp 95
9741 7.4.36 crypt_autosign 95
9742 7.4.37 crypt_autosmime 95
9743 7.4.38 crypt_replyencrypt 95
9744 7.4.39 crypt_replysign 95
9745 7.4.40 crypt_replysignencrypted 96
9746 7.4.41 crypt_timestamp 96
9747 7.4.42 crypt_use_gpgme 96
9748 7.4.43 crypt_verify_sig 96
9749 7.4.44 date_format 96
9750 7.4.45 default_hook 97
9752 7.4.47 delete_space 97
9753 7.4.48 delete_untag 97
9754 7.4.49 digest_collapse 98
9755 7.4.50 display_filter 98
9756 7.4.51 dotlock_program 98
9757 7.4.52 dsn_notify 98
9758 7.4.53 dsn_return 99
9759 7.4.54 duplicate_threads 99
9760 7.4.55 edit_headers 99
9762 7.4.57 encode_from 99
9763 7.4.58 entropy_file 100
9764 7.4.59 envelope_from 100
9769 7.4.61 fast_reply 100
9770 7.4.62 fcc_attach 100
9771 7.4.63 fcc_clear 101
9772 7.4.64 file_charset 101
9774 7.4.66 folder_format 101
9775 7.4.67 followup_to 102
9776 7.4.68 force_buffy_check 103
9777 7.4.69 force_name 103
9778 7.4.70 forward_decode 103
9779 7.4.71 forward_decrypt 103
9780 7.4.72 forward_edit 103
9781 7.4.73 forward_format 104
9782 7.4.74 forward_quote 104
9784 7.4.76 gecos_mask 104
9787 7.4.79 header_cache 105
9788 7.4.80 header_cache_compress 105
9790 7.4.82 hidden_host 106
9791 7.4.83 hide_limited 106
9792 7.4.84 hide_missing 106
9793 7.4.85 hide_thread_subject 106
9794 7.4.86 hide_top_limited 106
9795 7.4.87 hide_top_missing 107
9797 7.4.89 honor_followup_to 107
9799 7.4.91 ignore_list_reply_to 107
9800 7.4.92 imap_authenticators 108
9801 7.4.93 imap_check_subscribed 108
9802 7.4.94 imap_delim_chars 108
9803 7.4.95 imap_headers 108
9804 7.4.96 imap_home_namespace 109
9805 7.4.97 imap_keepalive 109
9806 7.4.98 imap_list_subscribed 109
9807 7.4.99 imap_login 110
9808 7.4.100 imap_mail_check 110
9809 7.4.101 imap_pass 110
9810 7.4.102 imap_passive 110
9811 7.4.103 imap_peek 110
9812 7.4.104 imap_reconnect 111
9813 7.4.105 imap_servernoise 111
9814 7.4.106 imap_user 111
9815 7.4.107 implicit_autoview 111
9817 7.4.109 include_onlyfirst 112
9818 7.4.110 indent_string 112
9819 7.4.111 index_format 112
9824 7.4.113 keep_flagged 115
9825 7.4.114 list_reply 115
9827 7.4.116 mail_check 116
9828 7.4.117 mailcap_path 116
9829 7.4.118 mailcap_sanitize 116
9830 7.4.119 maildir_header_cache_verify 116
9831 7.4.120 maildir_trash 116
9832 7.4.121 mark_old 117
9835 7.4.124 max_display_recips 117
9836 7.4.125 max_line_length 117
9838 7.4.127 mbox_type 118
9839 7.4.128 menu_context 118
9840 7.4.129 menu_move_off 118
9841 7.4.130 menu_scroll 118
9842 7.4.131 message_format 119
9843 7.4.132 meta_key 119
9845 7.4.134 mh_purge 119
9846 7.4.135 mh_seq_flagged 119
9847 7.4.136 mh_seq_replied 119
9848 7.4.137 mh_seq_unseen 120
9849 7.4.138 mime_forward 120
9850 7.4.139 mime_forward_decode 120
9851 7.4.140 mime_forward_rest 120
9852 7.4.141 mix_entry_format 120
9853 7.4.142 mixmaster 121
9855 7.4.144 msgid_format 121
9856 7.4.145 narrow_tree 122
9857 7.4.146 nntp_ask_followup_to 122
9858 7.4.147 nntp_ask_x_comment_to 123
9859 7.4.148 nntp_cache_dir 123
9860 7.4.149 nntp_catchup 123
9861 7.4.150 nntp_context 123
9862 7.4.151 nntp_followup_to_poster 124
9863 7.4.152 nntp_group_index_format 124
9864 7.4.153 nntp_host 124
9865 7.4.154 nntp_inews 125
9866 7.4.155 nntp_load_description 125
9867 7.4.156 nntp_mail_check 125
9868 7.4.157 nntp_mime_subject 125
9869 7.4.158 nntp_newsrc 126
9870 7.4.159 nntp_pass 126
9871 7.4.160 nntp_post_moderated 126
9872 7.4.161 nntp_reconnect 127
9873 7.4.162 nntp_save_unsubscribed 127
9874 7.4.163 nntp_show_new_news 127
9875 7.4.164 nntp_show_only_unread 127
9876 7.4.165 nntp_user 127
9880 7.4.166 nntp_x_comment_to 128
9881 7.4.167 operating_system 128
9883 7.4.169 pager_context 128
9884 7.4.170 pager_format 129
9885 7.4.171 pager_index_lines 129
9886 7.4.172 pager_stop 129
9887 7.4.173 pgp_auto_decode 129
9888 7.4.174 pgp_autoinline 129
9889 7.4.175 pgp_check_exit 130
9890 7.4.176 pgp_clearsign_command 130
9891 7.4.177 pgp_decode_command 130
9892 7.4.178 pgp_decrypt_command 131
9893 7.4.179 pgp_encrypt_only_command 131
9894 7.4.180 pgp_encrypt_sign_command 131
9895 7.4.181 pgp_entry_format 131
9896 7.4.182 pgp_export_command 132
9897 7.4.183 pgp_getkeys_command 132
9898 7.4.184 pgp_good_sign 132
9899 7.4.185 pgp_ignore_subkeys 132
9900 7.4.186 pgp_import_command 133
9901 7.4.187 pgp_list_pubring_command 133
9902 7.4.188 pgp_list_secring_command 133
9903 7.4.189 pgp_long_ids 133
9904 7.4.190 pgp_mime_auto 133
9905 7.4.191 pgp_replyinline 134
9906 7.4.192 pgp_retainable_sigs 134
9907 7.4.193 pgp_show_unusable 134
9908 7.4.194 pgp_sign_as 134
9909 7.4.195 pgp_sign_command 135
9910 7.4.196 pgp_sort_keys 135
9911 7.4.197 pgp_strict_enc 135
9912 7.4.198 pgp_timeout 135
9913 7.4.199 pgp_use_gpg_agent 136
9914 7.4.200 pgp_verify_command 136
9915 7.4.201 pgp_verify_key_command 136
9916 7.4.202 pipe_decode 136
9917 7.4.203 pipe_sep 136
9918 7.4.204 pipe_split 136
9919 7.4.205 pop_auth_try_all 137
9920 7.4.206 pop_authenticators 137
9921 7.4.207 pop_delete 137
9922 7.4.208 pop_host 137
9923 7.4.209 pop_last 138
9924 7.4.210 pop_mail_check 138
9925 7.4.211 pop_pass 138
9926 7.4.212 pop_reconnect 138
9927 7.4.213 pop_user 139
9928 7.4.214 post_indent_string 139
9929 7.4.215 postpone 139
9930 7.4.216 postponed 139
9931 7.4.217 preconnect 139
9936 7.4.219 print_command 140
9937 7.4.220 print_decode 140
9938 7.4.221 print_split 140
9939 7.4.222 prompt_after 141
9940 7.4.223 query_command 141
9942 7.4.225 quote_empty 141
9943 7.4.226 quote_quoted 141
9944 7.4.227 quote_regexp 142
9945 7.4.228 read_inc 142
9946 7.4.229 read_only 142
9947 7.4.230 realname 142
9950 7.4.233 reply_regexp 143
9951 7.4.234 reply_self 143
9952 7.4.235 reply_to 143
9954 7.4.237 reverse_alias 144
9955 7.4.238 reverse_name 144
9956 7.4.239 reverse_realname 144
9957 7.4.240 rfc2047_parameters 145
9958 7.4.241 save_address 145
9959 7.4.242 save_empty 145
9960 7.4.243 save_name 145
9962 7.4.245 score_threshold_delete 146
9963 7.4.246 score_threshold_flag 146
9964 7.4.247 score_threshold_read 146
9965 7.4.248 send_charset 146
9966 7.4.249 sendmail 147
9967 7.4.250 sendmail_wait 147
9969 7.4.252 sidebar_boundary 148
9970 7.4.253 sidebar_delim 148
9971 7.4.254 sidebar_newmail_only 148
9972 7.4.255 sidebar_number_format 148
9973 7.4.256 sidebar_shorten_hierarchy 149
9974 7.4.257 sidebar_visible 149
9975 7.4.258 sidebar_width 149
9976 7.4.259 sig_dashes 149
9977 7.4.260 sig_on_top 150
9978 7.4.261 signature 150
9979 7.4.262 signoff_string 150
9980 7.4.263 simple_search 150
9981 7.4.264 sleep_time 151
9982 7.4.265 smart_wrap 151
9984 7.4.267 smime_ask_cert_label 151
9985 7.4.268 smime_ca_location 151
9986 7.4.269 smime_certificates 151
9987 7.4.270 smime_decrypt_command 152
9988 7.4.271 smime_decrypt_use_default_key 152
9992 7.4.272 smime_default_key 153
9993 7.4.273 smime_encrypt_command 153
9994 7.4.274 smime_encrypt_with 153
9995 7.4.275 smime_get_cert_command 153
9996 7.4.276 smime_get_cert_email_command 153
9997 7.4.277 smime_get_signer_cert_command 153
9998 7.4.278 smime_import_cert_command 154
9999 7.4.279 smime_is_default 154
10000 7.4.280 smime_keys 154
10001 7.4.281 smime_pk7out_command 154
10002 7.4.282 smime_sign_command 155
10003 7.4.283 smime_sign_opaque_command 155
10004 7.4.284 smime_timeout 155
10005 7.4.285 smime_verify_command 155
10006 7.4.286 smime_verify_opaque_command 155
10007 7.4.287 smtp_envelope 155
10008 7.4.288 smtp_host 156
10009 7.4.289 smtp_pass 156
10010 7.4.290 smtp_port 156
10011 7.4.291 smtp_use_tls 156
10012 7.4.292 smtp_user 157
10014 7.4.294 sort_alias 157
10015 7.4.295 sort_aux 158
10016 7.4.296 sort_browser 158
10017 7.4.297 sort_re 158
10018 7.4.298 spam_separator 159
10019 7.4.299 spoolfile 159
10020 7.4.300 ssl_ca_certificates_file 159
10021 7.4.301 ssl_client_cert 159
10022 7.4.302 ssl_force_tls 160
10023 7.4.303 ssl_min_dh_prime_bits 160
10024 7.4.304 ssl_starttls 160
10025 7.4.305 ssl_use_sslv2 160
10026 7.4.306 ssl_use_sslv3 160
10027 7.4.307 ssl_use_tlsv1 161
10028 7.4.308 ssl_usesystemcerts 161
10029 7.4.309 status_chars 161
10030 7.4.310 status_format 161
10031 7.4.311 status_on_top 164
10032 7.4.312 strict_mailto 164
10033 7.4.313 strict_mime 164
10034 7.4.314 strict_threads 164
10035 7.4.315 strip_was 164
10036 7.4.316 strip_was_regex 165
10037 7.4.317 stuff_quoted 165
10038 7.4.318 suspend 165
10039 7.4.319 text_flowed 165
10040 7.4.320 thorough_search 165
10041 7.4.321 thread_received 166
10043 7.4.323 timeout 166
10048 7.4.325 to_chars 166
10052 7.4.329 uncollapse_jump 167
10053 7.4.330 use_8bitmime 168
10054 7.4.331 use_domain 168
10055 7.4.332 use_from 168
10056 7.4.333 use_idn 168
10057 7.4.334 use_ipv6 168
10058 7.4.335 user_agent 169
10060 7.4.337 wait_key 169
10062 7.4.339 wrap_search 169
10063 7.4.340 wrapmargin 170
10064 7.4.341 write_bcc 170
10065 7.4.342 write_inc 170
10066 7.4.343 xterm_icon 170
10067 7.4.344 xterm_leave 170
10068 7.4.345 xterm_set_titles 171
10069 7.4.346 xterm_title 171
10070 7.5 Functions ....................................................... 171
10083 8. Miscellany ............................................................ 179
10084 8.1 Acknowledgments ................................................. 180
10085 8.2 About this document ............................................. 182