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 6.4.322 , page 159) 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 74) 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 6.4.290 , page 149) 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 6.4.110 , page 105). For example, you could use "%?M?(#%03M)&(%4l)?" in
522 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105) 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 6.4.311 , page 157).
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 6.4.3 , page 80) 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 6.4.3 , page 80) does not
536 add the aliases specified there-in, you must also _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page
539 c
\bch
\bhe
\bec
\bck
\bk-
\b-t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl-
\b-p
\bpg
\bgp
\bp
542 This function will search the current message for content signed or encrypted
543 with PGP the "traditional" way, that is, without proper MIME tagging.
545 The Mutt Next Generation E-Mail Client 12
547 Technically, this function will temporarily change the MIME content types of
548 the body parts containing PGP data; this is similar to the _
\be_
\bd_
\bi_
\bt_
\b-_
\bt_
\by_
\bp_
\be (section
549 2.5.4 , page 12) function's effect.
551 d
\bdi
\bis
\bsp
\bpl
\bla
\bay
\by-
\b-t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-w
\bwe
\bee
\bed
\bd
554 Toggles the weeding of message header fields specified by _
\bi_
\bg_
\bn_
\bo_
\br_
\be (section
555 3.9 , page 30) commands.
560 This command (available in the ``index'' and ``pager'') allows you to edit the
561 raw current message as it's present in the mail folder. After you have fin-
562 ished editing, the changed message will be appended to the current folder, and
563 the original message will be marked for deletion.
565 e
\bed
\bdi
\bit
\bt-
\b-t
\bty
\byp
\bpe
\be
567 (default: ^E on the attachment menu, and in the pager and index menus; ^T on
570 This command is used to temporarily edit an attachment's content type to fix,
571 for instance, bogus character set parameters. When invoked from the index or
572 from the pager, you'll have the opportunity to edit the top-level attachment's
573 content type. On the _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bm_
\be_
\bn_
\bu (section 5.1.2 , page 67), you can
574 change any attachment's content type. These changes are not persistent, and get
575 lost upon changing folders.
577 Note that this command is also available on the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bm_
\be_
\bn_
\bu (section 5.1.3 ,
578 page 67). There, it's used to fine-tune the properties of attachments you are
581 e
\ben
\bnt
\bte
\ber
\br-
\b-c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
584 This command is used to execute any command you would normally put in a config-
585 uration file. A common use is to check the settings of variables, or in con-
586 junction with _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.7 , page 27) to change settings on the fly.
588 e
\bex
\bxt
\btr
\bra
\bac
\bct
\bt-
\b-k
\bke
\bey
\bys
\bs
591 This command extracts PGP public keys from the current or tagged message(s) and
592 adds them to your PGP public key ring.
594 f
\bfo
\bor
\brg
\bge
\bet
\bt-
\b-p
\bpa
\bas
\bss
\bsp
\bph
\bhr
\bra
\bas
\bse
\be
597 This command wipes the passphrase(s) from memory. It is useful, if you mis-
598 spelled the passphrase.
600 The Mutt Next Generation E-Mail Client 13
602 l
\bli
\bis
\bst
\bt-
\b-r
\bre
\bep
\bpl
\bly
\by
605 Reply to the current or tagged message(s) by extracting any addresses which
606 match the regular expressions given by the _
\bl_
\bi_
\bs_
\bt_
\bs _
\bo_
\br _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 ,
607 page 32) commands, but also honor any Mail-Followup-To header(s) if the
608 _
\b$_
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 6.4.88 , page 100) 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 6.4.200 , page 129), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
617 (section 6.4.202 , page 129), _
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp (section 6.4.201 , page 129) and
618 _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 6.4.334 , page 161) 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 6.4.335 , page 162) 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 6.4.334 , page 161) 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 6.4.225 , page 134) 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 6.4.307 , page 154) 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 6.4.54 , page 92).
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 6.4.192 , page 127) 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 6.4.179 , page 124)) 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 6.4.139 ,
951 page 113)). 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 6.4.214 , page 132) 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 6.4.213 , page 132) 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 6.1 , page 76) 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 6.3 , page 78) 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 6.3 , page
1045 78). 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 6.3 , page 78).
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 6.4.3 , page 80)
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 6.4.54 , page 92) 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 6.5 , page 164). 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 6.4.296 , page
1303 151) 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 6.4.225 , page 134) 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 6.4.233 , page 136).)
1522 Many users receive e-mail under a number of different addresses. To fully use
1523 mutt's features here, the program must be able to recognize what e-mail
1524 addresses you receive mail under. That's the purpose of the alternates command:
1525 It takes a list of regular expressions, each of which can identify an address
1526 under which you receive e-mail.
1528 The unalternates command can be used to write exceptions to alternates pat-
1529 terns. If an address matches something in an alternates command, but you none-
1530 theless do not think it is from you, you can list a more precise pattern under
1531 an unalternates command.
1533 To remove a regular expression from the alternates list, use the unalternates
1534 command with exactly the same _
\br_
\be_
\bg_
\be_
\bx_
\bp. Likewise, if the _
\br_
\be_
\bg_
\be_
\bx_
\bp for a alternates
1535 command matches an entry on the unalternates list, that unalternates entry will
1536 be removed. If the _
\br_
\be_
\bg_
\be_
\bx_
\bp for unalternates is ``*'', _
\ba_
\bl_
\bl _
\be_
\bn_
\bt_
\br_
\bi_
\be_
\bs on alternates
1539 _
\b3_
\b._
\b1_
\b1 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\b= _
\bF_
\bl_
\bo_
\bw_
\be_
\bd
1541 Mutt-ng contains support for so-called format=flowed messages. In the begin-
1542 ning of email, each message had a fixed line width, and it was enough for dis-
1543 playing them on fixed-size terminals. But times changed, and nowadays hardly
1544 anybody still uses fixed-size terminals: more people nowaydays use graphical
1545 user interfaces, with dynamically resizable windows. This led to the demand of
1546 a new email format that makes it possible for the email client to make the
1547 email look nice in a resizable window without breaking quoting levels and cre-
1548 ating an incompatible email format that can also be displayed nicely on old
1549 fixed-size terminals.
1551 For introductory information on format=flowed messages, see
1552 <http://www.joeclark.org/ffaq.html>.
1554 When you receive emails that are marked as format=flowed messages, and is for-
1555 matted correctly, mutt-ng will try to reformat the message to optimally fit on
1556 your terminal. If you want a fixed margin on the right side of your terminal,
1557 you can set the following:
1561 The Mutt Next Generation E-Mail Client 32
1563 The code above makes the line break 10 columns before the right side of the
1566 If your terminal is so wide that the lines are embarrassingly long, you can
1567 also set a maximum line length:
1569 set max_line_length = 120
1571 The example above will give you lines not longer than 120 characters.
1573 When you view at format=flowed messages, you will often see the quoting hierar-
1574 chy like in the following example:
1576 >Bill, can you please send last month's progress report to Mr.
1577 >Morgan? We also urgently need the cost estimation for the new
1578 >production server that we want to set up before our customer's
1579 >project will go live.
1581 This obviously doesn't look very nice, and it makes it very hard to differenti-
1582 ate between text and quoting character. The solution is to configure mutt-ng to
1583 "stuff" the quoting:
1587 This will lead to a nicer result that is easier to read:
1589 > Bill, can you please send last month's progress report to Mr.
1590 > Morgan? We also urgently need the cost estimation for the new
1591 > production server that we want to set up before our customer's
1592 > project will go live.
1594 If you want mutt-ng to send emails with format=flowed set, you need to explic-
1599 Additionally, you have to use an editor which supports writing format=flowed-
1600 conforming emails. For vim, this is done by adding w to the formatoptions (see
1601 :h formatoptions and :h fo-table) when writing emails.
1603 _
\b3_
\b._
\b1_
\b2 _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs
1605 The Mutt Next Generation E-Mail Client 33
1607 Usage: [un]lists _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1609 Usage: [un]subscribe _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
1611 Mutt-ng has a few nice features for _
\bh_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bm_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bl_
\bi_
\bs_
\bt_
\bs (section 4.10 ,
1612 page 57). In order to take advantage of them, you must specify which addresses
1613 belong to mailing lists, and which mailing lists you are subscribed to. Once
1614 you have done this, the _
\bl_
\bi_
\bs_
\bt_
\b-_
\br_
\be_
\bp_
\bl_
\by (section 2.5.4 , page 12) function will
1615 work for all known lists. Additionally, when you send a message to a sub-
1616 scribed list, mutt will add a Mail-Followup-To header to tell other users' mail
1617 user agents not to send copies of replies to your personal address. Note that
1618 the Mail-Followup-To header is a non-standard extension which is not supported
1619 by all mail user agents. Adding it is not bullet-proof against receiving per-
1620 sonal CCs of list messages. Also note that the generation of the Mail-Fol-
1621 lowup-To header is controlled by the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 6.4.66 , page 95)
1622 configuration variable.
1624 More precisely, Mutt-ng maintains lists of patterns for the addresses of known
1625 and subscribed mailing lists. Every subscribed mailing list is known. To mark
1626 a mailing list as known, use the ``lists'' command. To mark it as subscribed,
1629 You can use regular expressions with both commands. To mark all messages sent
1630 to a specific bug report's address on mutt's bug tracking system as list mail,
1631 for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's
1632 sufficient to just give a portion of the list's e-mail address.
1634 Specify as much of the address as you need to to remove ambiguity. For exam-
1635 ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail
1636 addressed to _
\bm_
\bu_
\bt_
\bt_
\b-_
\bu_
\bs_
\be_
\br_
\bs_
\b@_
\bm_
\bu_
\bt_
\bt_
\b._
\bo_
\br_
\bg. So, to tell Mutt-ng that this is a mailing
1637 list, you could add ``lists mutt-users'' to your initialization file. To tell
1638 mutt that you are subscribed to it, add ``subscribe mutt-users'' to your ini-
1639 tialization file instead. If you also happen to get mail from someone whose
1640 address is _
\bm_
\bu_
\bt_
\bt_
\b-_
\bu_
\bs_
\be_
\br_
\bs_
\b@_
\be_
\bx_
\ba_
\bm_
\bp_
\bl_
\be_
\b._
\bc_
\bo_
\bm, you could use ``lists mutt-
1641 users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail
1642 from the actual list.
1644 The ``unlists'' command is used to remove a token from the list of known and
1645 subscribed mailing-lists. Use ``unlists *'' to remove all tokens.
1647 To remove a mailing list from the list of subscribed mailing lists, but keep it
1648 on the list of known mailing lists, use ``unsubscribe''.
1650 _
\b3_
\b._
\b1_
\b3 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bu_
\bl_
\bt_
\bi_
\bp_
\bl_
\be _
\bs_
\bp_
\bo_
\bo_
\bl _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs
1652 Usage: mbox-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1654 This command is used to move read messages from a specified mailbox to a dif-
1655 ferent mailbox automatically when you quit or change folders. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a
1656 regular expression specifying the mailbox to treat as a ``spool'' mailbox and
1657 _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx specifies where mail should be saved when read.
1659 The Mutt Next Generation E-Mail Client 34
1661 Unlike some of the other _
\bh_
\bo_
\bo_
\bk commands, only the _
\bf_
\bi_
\br_
\bs_
\bt matching pattern is used
1662 (it is not possible to save read mail in more than a single mailbox).
1664 _
\b3_
\b._
\b1_
\b4 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs _
\bw_
\bh_
\bi_
\bc_
\bh _
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be _
\bm_
\ba_
\bi_
\bl
1666 Usage: [un]mailboxes [!]_
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
1668 This command specifies folders which can receive mail and which will be checked
1669 for new messages. By default, the main menu status bar displays how many of
1670 these folders have new messages.
1672 When changing folders, pressing _
\bs_
\bp_
\ba_
\bc_
\be will cycle through folders with new mail.
1674 Pressing TAB in the directory browser will bring up a menu showing the files
1675 specified by the mailboxes command, and indicate which contain new messages.
1676 Mutt-ng will automatically enter this mode when invoked from the command line
1679 The ``unmailboxes'' command is used to remove a token from the list of folders
1680 which receive mail. Use ``unmailboxes *'' to remove all tokens.
1682 N
\bNo
\bot
\bte
\be:
\b: new mail is detected by comparing the last modification time to the last
1683 access time. Utilities like biff or frm or any other program which accesses
1684 the mailbox might cause Mutt-ng to never detect new mail for that mailbox if
1685 they do not properly reset the access time. Backup tools are another common
1686 reason for updated access times.
1688 N
\bNo
\bot
\bte
\be:
\b: the filenames in the mailboxes command are resolved when the command is
1689 executed, so if these names contain _
\bs_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt _
\bc_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br_
\bs (section 4.9 , page
1690 56) (such as ``='' and ``!''), any variable definition that affect these char-
1691 acters (like _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 6.4.64 , page 94) and _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
1692 6.4.296 , page 151)) should be executed before the mailboxes command.
1694 _
\b3_
\b._
\b1_
\b5 _
\bU_
\bs_
\be_
\br _
\bd_
\be_
\bf_
\bi_
\bn_
\be_
\bd _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
1698 my_hdr _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1700 unmy_hdr _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
1702 The ``my_hdr'' command allows you to create your own header fields which will
1703 be added to every message you send.
1705 For example, if you would like to add an ``Organization:'' header field to all
1706 of your outgoing messages, you can put the command
1708 my_hdr Organization: A Really Big Company, Anytown, USA
1710 The Mutt Next Generation E-Mail Client 35
1714 N
\bNo
\bot
\bte
\be:
\b: space characters are _
\bn_
\bo_
\bt allowed between the keyword and the colon
1715 (``:''). The standard for electronic mail (RFC822) says that space is illegal
1716 there, so Mutt-ng enforces the rule.
1718 If you would like to add a header field to a single message, you should either
1719 set the _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 6.4.54 , page 92) variable, or use the _
\be_
\bd_
\bi_
\bt_
\b-
1720 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs function (default: ``E'') in the send-menu so that you can edit the
1721 header of your message along with the body.
1723 To remove user defined header fields, use the ``unmy_hdr'' command. You may
1724 specify an asterisk (``*'') to remove all header fields, or the fields to
1725 remove. For example, to remove all ``To'' and ``Cc'' header fields, you could
1730 _
\b3_
\b._
\b1_
\b6 _
\bD_
\be_
\bf_
\bi_
\bn_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bo_
\br_
\bd_
\be_
\br _
\bo_
\bf _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs _
\bw_
\bh_
\be_
\bn _
\bv_
\bi_
\be_
\bw_
\bi_
\bn_
\bg _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\bs
1732 Usage: hdr_order _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b1 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b2 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b3
1734 With this command, you can specify an order in which mutt will attempt to
1735 present headers to you when viewing messages.
1737 ``unhdr_order *'' will clear all previous headers from the order list, thus
1738 removing the header order effects set by the system-wide startup file.
1740 hdr_order From Date: From: To: Cc: Subject:
1742 _
\b3_
\b._
\b1_
\b7 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1744 Usage: save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
1746 This command is used to override the default filename used when saving mes-
1747 sages. _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be will be used as the default filename if the message is _
\bF_
\br_
\bo_
\bm_
\b:
1748 an address matching _
\br_
\be_
\bg_
\be_
\bx_
\bp or if you are the author and the message is
1749 addressed _
\bt_
\bo_
\b: something matching _
\br_
\be_
\bg_
\be_
\bx_
\bp.
1751 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 53) for information on the
1752 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1756 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1758 The Mutt Next Generation E-Mail Client 36
1760 save-hook aol\\.com$ +spam
1762 Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36) command.
1764 _
\b3_
\b._
\b1_
\b8 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bw_
\bh_
\be_
\bn _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\bi_
\bn_
\bg
1766 Usage: fcc-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1768 This command is used to save outgoing mail in a mailbox other than _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd
1769 (section 6.4.230 , page 136). Mutt-ng searches the initial list of message
1770 recipients for the first matching _
\br_
\be_
\bg_
\be_
\bx_
\bp and uses _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx as the default Fcc:
1771 mailbox. If no match is found the message will be saved to _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section
1772 6.4.230 , page 136) mailbox.
1774 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 53) for information on the
1775 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1777 Example: fcc-hook [@.]aol\\.com$ +spammers
1779 The above will save a copy of all messages going to the aol.com domain to the
1780 `+spammers' mailbox by default. Also see the _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 ,
1783 _
\b3_
\b._
\b1_
\b9 _
\bS_
\bp_
\be_
\bc_
\bi_
\bf_
\by _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be _
\ba_
\bn_
\bd _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bF_
\bc_
\bc_
\b: _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\ba_
\bt _
\bo_
\bn_
\bc_
\be
1785 Usage: fcc-save-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
1787 This command is a shortcut, equivalent to doing both a _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section
1788 3.18 , page 35) and a _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 35) with its arguments.
1790 _
\b3_
\b._
\b2_
\b0 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\ba_
\bs_
\be_
\bd _
\bu_
\bp_
\bo_
\bn _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt_
\bs
1792 Usage: reply-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1794 Usage: send-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1796 Usage: send2-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1798 These commands can be used to execute arbitrary configuration commands based
1799 upon recipients of the message. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn is a regular expression matching the
1800 desired address. _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is executed when _
\br_
\be_
\bg_
\be_
\bx_
\bp matches recipients of the
1803 reply-hook is matched against the message you are _
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bg t
\bto
\bo, instead of the
1804 message you are _
\bs_
\be_
\bn_
\bd_
\bi_
\bn_
\bg. send-hook is matched against all messages, both _
\bn_
\be_
\bw
1805 and _
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bs. N
\bNo
\bot
\bte
\be:
\b: reply-hooks are matched b
\bbe
\bef
\bfo
\bor
\bre
\be the send-hook, r
\bre
\beg
\bga
\bar
\brd
\bdl
\ble
\bes
\bss
\bs of
1806 the order specified in the users's configuration file.
1808 The Mutt Next Generation E-Mail Client 37
1810 send2-hook is matched every time a message is changed, either by editing it, or
1811 by using the compose menu to change its recipients or subject. send2-hook is
1812 executed after send-hook, and can, e.g., be used to set parameters such as the
1813 _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 6.4.247 , page 140) variable depending on the message's
1816 For each type of send-hook or reply-hook, when multiple matches occur, commands
1817 are executed in the order they are specified in the muttrc (for that type of
1820 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 53) for information on the
1821 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1823 Example: send-hook mutt 'set mime_forward signature='''
1825 Another typical use for this command is to change the values of the _
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\b-
1826 _
\bt_
\bi_
\bo_
\bn (section 6.4.15 , page 84), _
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 6.4.259 , page 143) and
1827 _
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 6.4.114 , page 108) variables in order to change the language
1828 of the attributions and signatures based upon the recipients.
1830 N
\bNo
\bot
\bte
\be:
\b: the send-hook's are only executed ONCE after getting the initial list of
1831 recipients. Adding a recipient after replying or editing the message will NOT
1832 cause any send-hook to be executed. Also note that my_hdr commands which mod-
1833 ify recipient headers, or the message's subject, don't have any effect on the
1834 current message when executed from a send-hook.
1836 _
\b3_
\b._
\b2_
\b1 _
\bC_
\bh_
\ba_
\bn_
\bg_
\be _
\bs_
\be_
\bt_
\bt_
\bi_
\bn_
\bg_
\bs _
\bb_
\be_
\bf_
\bo_
\br_
\be _
\bf_
\bo_
\br_
\bm_
\ba_
\bt_
\bt_
\bi_
\bn_
\bg _
\ba _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
1838 Usage: message-hook [!]_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
1840 This command can be used to execute arbitrary configuration commands before
1841 viewing or formatting a message based upon information about the message. _
\bc_
\bo_
\bm_
\b-
1842 _
\bm_
\ba_
\bn_
\bd is executed if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn matches the message to be displayed. When mul-
1843 tiple matches occur, commands are executed in the order they are specified in
1846 See _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bM_
\ba_
\bt_
\bc_
\bh_
\bi_
\bn_
\bg _
\bi_
\bn _
\bH_
\bo_
\bo_
\bk_
\bs (section 4.5.1 , page 53) for information on the
1847 exact format of _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn.
1851 message-hook ~A 'set pager=builtin'
1852 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1854 _
\b3_
\b._
\b2_
\b2 _
\bC_
\bh_
\bo_
\bo_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bc_
\br_
\by_
\bp_
\bt_
\bo_
\bg_
\br_
\ba_
\bp_
\bh_
\bi_
\bc _
\bk_
\be_
\by _
\bo_
\bf _
\bt_
\bh_
\be _
\br_
\be_
\bc_
\bi_
\bp_
\bi_
\be_
\bn_
\bt
1856 Usage: crypt-hook _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\bi_
\bd
1858 When encrypting messages with PGP or OpenSSL, you may want to associate a
1860 The Mutt Next Generation E-Mail Client 38
1862 certain key with a given e-mail address automatically, either because the
1863 recipient's public key can't be deduced from the destination address, or
1864 because, for some reasons, you need to override the key Mutt-ng would normally
1865 use. The crypt-hook command provides a method by which you can specify the ID
1866 of the public key to be used when encrypting messages to a certain recipient.
1868 The meaning of "key id" is to be taken broadly in this context: You can either
1869 put a numerical key ID here, an e-mail address, or even just a real name.
1871 _
\b3_
\b._
\b2_
\b3 _
\bA_
\bd_
\bd_
\bi_
\bn_
\bg _
\bk_
\be_
\by _
\bs_
\be_
\bq_
\bu_
\be_
\bn_
\bc_
\be_
\bs _
\bt_
\bo _
\bt_
\bh_
\be _
\bk_
\be_
\by_
\bb_
\bo_
\ba_
\br_
\bd _
\bb_
\bu_
\bf_
\bf_
\be_
\br
1873 Usage: push _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
1875 This command adds the named string to the keyboard buffer. The string may con-
1876 tain control characters, key names and function names like the sequence string
1877 in the _
\bm_
\ba_
\bc_
\br_
\bo (section 3.7 , page 27) command. You may use it to automatically
1878 run a sequence of commands at startup, or when entering certain folders.
1880 _
\b3_
\b._
\b2_
\b4 _
\bE_
\bx_
\be_
\bc_
\bu_
\bt_
\bi_
\bn_
\bg _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
1882 Usage: exec _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
1884 This command can be used to execute any function. Functions are listed in the
1885 _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\br_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be (section 6.5 , page 164). ``exec function'' is equivalent
1886 to ``push <function>''.
1888 _
\b3_
\b._
\b2_
\b5 _
\bM_
\be_
\bs_
\bs_
\ba_
\bg_
\be _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
1890 Usage: score _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
1892 Usage: unscore _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn [ _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn ... ]
1894 In situations where you have to cope with a lot of emails, e.g. when you read
1895 many different mailing lists, and take part in discussions, it is always useful
1896 to have the important messages marked and the annoying messages or the ones
1897 that you aren't interested in deleted. For this purpose, mutt-ng features a
1898 mechanism called ``scoring''.
1900 When you use scoring, every message has a base score of 0. You can then use the
1901 score command to define patterns and a positive or negative value associated
1902 with it. When a pattern matches a message, the message's score will be raised
1903 or lowered by the amount of the value associated with the pattern.
1905 score "~f nion@muttng\.org" 50
1906 score "~f @sco\.com" -100
1908 The Mutt Next Generation E-Mail Client 39
1910 If the pattern matches, it is also possible to set the score value of the cur-
1911 rent message to a certain value and then stop evaluation:
1913 score "~f santaclaus@northpole\.int" =666
1915 What is important to note is that negative score values will be rounded up to
1918 To make scoring actually useful, the score must be applied in some way. That's
1919 what the _
\bs_
\bc_
\bo_
\br_
\be _
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\bs are for. Currently, there are three score thresholds:
1921 +
\bo flag threshold: when a message has a score value equal or higher than the
1922 flag threshold, it will be flagged.
1924 +
\bo read threshold: when a message has a score value equal or lower than the
1925 read threshold, it will be marked as read.
1927 +
\bo delete threshold: when a message has a score value equal or lower than the
1928 delete threshold, it will be marked as deleted.
1930 These three thresholds can be set via the variables _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg (sec-
1931 tion 6.4.244 , page 139), _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 6.4.245 , page 139),
1932 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 6.4.243 , page 139) and. By default,
1933 _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd (section 6.4.245 , page 139) and _
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
1934 (section 6.4.243 , page 139) are set to -1, which means that in the default
1935 threshold configuration no message will ever get marked as read or deleted.
1937 Scoring gets especially interesting when combined with the color command and
1940 color black yellow "~n 10-"
1941 color red yellow "~n 100-"
1943 The rules above mark all messages with a score between 10 and 99 with black and
1944 yellow, and messages with a score greater or equal 100 with red and yellow.
1945 This might be unusual to you if you're used to e.g. slrn's scoring mechanism,
1946 but it is more flexible, as it visually marks different scores.
1948 _
\b3_
\b._
\b2_
\b6 _
\bS_
\bp_
\ba_
\bm _
\bd_
\be_
\bt_
\be_
\bc_
\bt_
\bi_
\bo_
\bn
1950 Usage: spam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
1952 Usage: nospam _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
1954 Mutt-ng has generalized support for external spam-scoring filters. By defining
1955 your spam patterns with the spam and nospam commands, you can _
\bl_
\bi_
\bm_
\bi_
\bt, _
\bs_
\be_
\ba_
\br_
\bc_
\bh,
1956 and _
\bs_
\bo_
\br_
\bt your mail based on its spam attributes, as determined by the external
1957 filter. You also can display the spam attributes in your index display using
1959 The Mutt Next Generation E-Mail Client 40
1961 the %H selector in the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105) variable.
1962 (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a
1965 Your first step is to define your external filter's spam patterns using the
1966 spam command. _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn should be a regular expression that matches a header in a
1967 mail message. If any message in the mailbox matches this regular expression, it
1968 will receive a ``spam tag'' or ``spam attribute'' (unless it also matches a
1969 nospam pattern -- see below.) The appearance of this attribute is entirely up
1970 to you, and is governed by the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt parameter. _
\bf_
\bo_
\br_
\bm_
\ba_
\bt can be any static text,
1971 but it also can include back-references from the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn expression. (A regular
1972 expression ``back-reference'' refers to a sub-expression contained within
1973 parentheses.) %1 is replaced with the first back-reference in the regex, %2
1974 with the second, etc.
1976 If you're using multiple spam filters, a message can have more than one spam-
1977 related header. You can define spam patterns for each filter you use. If a mes-
1978 sage matches two or more of these patterns, and the $spam_separator variable is
1979 set to a string, then the message's spam tag will consist of all the _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
1980 strings joined together, with the value of $spam_separator separating them.
1982 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
1983 these spam settings:
1985 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
1986 spam "X-Spam-Status: Yes" "90+/SA"
1987 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
1988 set spam_separator=", "
1990 If I then received a message that DCC registered with ``many'' hits under the
1991 ``Fuz2'' checksum, and that PureMessage registered with a 97% probability of
1992 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
1993 characters before ``=many'' in a DCC report indicate the checksum used -- in
1994 this case, ``Fuz2''.)
1996 If the $spam_separator variable is unset, then each spam pattern match super-
1997 sedes the previous one. Instead of getting joined _
\bf_
\bo_
\br_
\bm_
\ba_
\bt strings, you'll get
1998 only the last one to match.
2000 The spam tag is what will be displayed in the index when you use %H in the
2001 $index_format variable. It's also the string that the ~H pattern-matching
2002 expression matches against for _
\bs_
\be_
\ba_
\br_
\bc_
\bh and _
\bl_
\bi_
\bm_
\bi_
\bt functions. And it's what sort-
2003 ing by spam attribute will use as a sort key.
2005 That's a pretty complicated example, and most people's actual environments will
2006 have only one spam filter. The simpler your configuration, the more effective
2007 mutt can be, especially when it comes to sorting.
2009 Generally, when you sort by spam tag, mutt will sort _
\bl_
\be_
\bx_
\bi_
\bc_
\ba_
\bl_
\bl_
\by -- that is, by
2010 ordering strings alphnumerically. However, if a spam tag begins with a number,
2011 mutt will sort numerically first, and lexically only when two numbers are equal
2012 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
2013 all -- that is, one that didn't match _
\ba_
\bn_
\by of your spam patterns -- is sorted at
2015 The Mutt Next Generation E-Mail Client 41
2017 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
2018 Finally, non-numeric strings are sorted, with ``a'' taking lower priority than
2019 ``z''. Clearly, in general, sorting by spam tags is most effective when you can
2020 coerce your filter to give you a raw number. But in case you can't, mutt can
2021 still do something useful.
2023 The nospam command can be used to write exceptions to spam patterns. If a
2024 header pattern matches something in a spam command, but you nonetheless do not
2025 want it to receive a spam tag, you can list a more precise pattern under a
2028 If the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn given to nospam is exactly the same as the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn on an exist-
2029 ing spam list entry, the effect will be to remove the entry from the spam list,
2030 instead of adding an exception. Likewise, if the _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for a spam command
2031 matches an entry on the nospam list, that nospam entry will be removed. If the
2032 _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn for nospam is ``*'', _
\ba_
\bl_
\bl _
\be_
\bn_
\bt_
\br_
\bi_
\be_
\bs _
\bo_
\bn _
\bb_
\bo_
\bt_
\bh _
\bl_
\bi_
\bs_
\bt_
\bs will be removed. This
2033 might be the default action if you use spam and nospam in conjunction with a
2036 You can have as many spam or nospam commands as you like. You can even do your
2037 own primitive spam detection within mutt -- for example, if you consider all
2038 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
2040 spam "^From: .*MAILER-DAEMON" "999"
2042 _
\b3_
\b._
\b2_
\b7 _
\bS_
\be_
\bt_
\bt_
\bi_
\bn_
\bg _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
2044 Usage: set [no|inv]_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be[=_
\bv_
\ba_
\bl_
\bu_
\be] [ _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2046 Usage: toggle _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2048 Usage: unset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2050 Usage: reset _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be [_
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be ... ]
2052 This command is used to set (and unset) _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs (section 6.4 ,
2053 page 80). There are four basic types of variables: boolean, number, string and
2054 quadoption. _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables can be _
\bs_
\be_
\bt (true) or _
\bu_
\bn_
\bs_
\be_
\bt (false). _
\bn_
\bu_
\bm_
\bb_
\be_
\br
2055 variables can be assigned a positive integer value.
2057 _
\bs_
\bt_
\br_
\bi_
\bn_
\bg variables consist of any number of printable characters. _
\bs_
\bt_
\br_
\bi_
\bn_
\bg_
\bs must
2058 be enclosed in quotes if they contain spaces or tabs. You may also use the
2059 ``C'' escape sequences \
\b\n
\bn and \
\b\t
\bt for newline and tab, respectively.
2061 _
\bq_
\bu_
\ba_
\bd_
\bo_
\bp_
\bt_
\bi_
\bo_
\bn variables are used to control whether or not to be prompted for cer-
2062 tain actions, or to specify a default action. A value of _
\by_
\be_
\bs will cause the
2063 action to be carried out automatically as if you had answered yes to the ques-
2064 tion. Similarly, a value of _
\bn_
\bo will cause the the action to be carried out as
2065 if you had answered ``no.'' A value of _
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs will cause a prompt with a
2066 default answer of ``yes'' and _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo will provide a default answer of ``no.''
2068 The Mutt Next Generation E-Mail Client 42
2070 Prefixing a variable with ``no'' will unset it. Example: set noaskbcc.
2072 For _
\bb_
\bo_
\bo_
\bl_
\be_
\ba_
\bn variables, you may optionally prefix the variable name with inv to
2073 toggle the value (on or off). This is useful when writing macros. Example:
2076 The toggle command automatically prepends the inv prefix to all specified vari-
2079 The unset command automatically prepends the no prefix to all specified vari-
2082 Using the enter-command function in the _
\bi_
\bn_
\bd_
\be_
\bx menu, you can query the value of
2083 a variable by prefixing the name of the variable with a question mark:
2087 The question mark is actually only required for boolean and quadoption vari-
2090 The reset command resets all given variables to the compile time defaults
2091 (hopefully mentioned in this manual). If you use the command set and prefix the
2092 variable with ``&'' this has the same behavior as the reset command.
2094 With the reset command there exists the special variable ``all'', which allows
2095 you to reset all variables to their system defaults.
2097 _
\b3_
\b._
\b2_
\b8 _
\bR_
\be_
\ba_
\bd_
\bi_
\bn_
\bg _
\bi_
\bn_
\bi_
\bt_
\bi_
\ba_
\bl_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs _
\bf_
\br_
\bo_
\bm _
\ba_
\bn_
\bo_
\bt_
\bh_
\be_
\br _
\bf_
\bi_
\bl_
\be
2099 Usage: source _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
2101 This command allows the inclusion of initialization commands from other files.
2102 For example, I place all of my aliases in ~/.mail_aliases so that I can make my
2103 ~/.muttrc readable and keep my aliases private.
2105 If the filename begins with a tilde (``~''), it will be expanded to the path of
2106 your home directory.
2108 If the filename ends with a vertical bar (|), then _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be is considered to be
2109 an executable program from which to read input (eg. source ~/bin/myscript|).
2111 _
\b3_
\b._
\b2_
\b9 _
\bR_
\be_
\bm_
\bo_
\bv_
\bi_
\bn_
\bg _
\bh_
\bo_
\bo_
\bk_
\bs
2113 Usage: unhook [ * | _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be ]
2115 This command permits you to flush hooks you have previously defined. You can
2116 either remove all hooks by giving the ``*'' character as an argument, or you
2117 can remove all hooks of a specific type by saying something like unhook send-
2119 The Mutt Next Generation E-Mail Client 43
2123 _
\b3_
\b._
\b3_
\b0 _
\bS_
\bh_
\ba_
\br_
\bi_
\bn_
\bg _
\bS_
\be_
\bt_
\bu_
\bp_
\bs
2125 _
\b3_
\b._
\b3_
\b0_
\b._
\b1 _
\bC_
\bh_
\ba_
\br_
\ba_
\bc_
\bt_
\be_
\br _
\bS_
\be_
\bt_
\bs
2127 As users may run mutt-ng on different systems, the configuration must be main-
2128 tained because it's likely that people want to use the setup everywhere they
2129 use mutt-ng. And mutt-ng tries to help where it can.
2131 To not produce conflicts with different character sets, mutt-ng allows users to
2132 specify in which character set their configuration files are encoded. Please
2133 note that while reading the configuration files, this is only respected after
2134 the corresponding declaration appears. It's advised to put the following at the
2135 very beginning of a users muttngrc:
2137 set config_charset = "..."
2139 and replacing the dots with the actual character set. To avoid problems while
2140 maintaining the setup, vim user's may want to use modelines as show in:
2142 # vim:fileencoding=...:
2144 while, again, replacing the dots with the appropriate name. This tells vim as
2145 which character set to read and save the file.
2147 _
\b3_
\b._
\b3_
\b0_
\b._
\b2 _
\bM_
\bo_
\bd_
\bu_
\bl_
\ba_
\br_
\bi_
\bz_
\ba_
\bt_
\bi_
\bo_
\bn
2149 ``Modularization'' means to divide the setup into several files while sorting
2150 the options or commands by topic. Especially for longer setups (e.g. with many
2151 hooks), this helps maintaining it and solving trouble.
2153 When using separation, setups may be, as a whole or in fractions, shared over
2156 _
\b3_
\b._
\b3_
\b0_
\b._
\b3 _
\bC_
\bo_
\bn_
\bd_
\bi_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bp_
\ba_
\br_
\bt_
\bs
2158 When using a configuration on different systems, the user may not always have
2159 influence on how mutt-ng is installed and which features it includes.
2161 To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written
2162 for mutt. Its basic syntax is:
2164 The Mutt Next Generation E-Mail Client 44
2166 ifdef <item> <command>
2167 ifndef <item> <command>
2169 ...whereby <item> can be one of:
2171 +
\bo a function name
2173 +
\bo a variable name
2179 All available functions, variables and menus are documented elsewhere in this
2180 manual but ``features'' is specific to these two commands. To test for one,
2181 prefix one of the following keywords with feature_:
2183 ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl,
2184 gnutls, sasl, sasl2, libesmtp, compressed, color, classic_pgp,
2185 classic_smime, gpgme, header_cache
2187 As an example, one can use the following in ~/.muttngrc:
2189 ifdef feature_imap 'source ~/.mutt-ng/setup-imap'
2190 ifdef feature_pop 'source ~/.mutt-ng/setup-pop'
2191 ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp'
2193 ...to only source ~/.mutt-ng/setup-imap if IMAP support is built in, only
2194 source ~/.mutt-ng/setup-pop if POP support is built in and only source ~/.mutt-
2195 ng/setup-nntp if NNTP support is built in.
2197 An example for testing for variable names can be used if users use different
2198 revisions of mutt-ng whereby the older one may not have a certain variable. To
2199 test for the availability of _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 6.4.99 , page 103),
2202 ifdef imap_mail_check 'set imap_mail_check = 300'
2204 Provided for completeness is the test for menu names. To set _
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
2205 (section 6.4.169 , page 122) only if the pager menu is available, use:
2207 ifdef pager 'set pager_index_lines = 10'
2209 For completeness, too, the opposite of ifdef is provided: ifndef which only
2210 executes the command if the test fails. For example, the following two examples
2212 The Mutt Next Generation E-Mail Client 45
2216 ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses'
2217 ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang'
2221 ifdef feature_slang 'source ~/.mutt-ng/setup-slang'
2222 ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses'
2224 _
\b4_
\b. _
\bA_
\bd_
\bv_
\ba_
\bn_
\bc_
\be_
\bd _
\bU_
\bs_
\ba_
\bg_
\be
2226 _
\b4_
\b._
\b1 _
\bR_
\be_
\bg_
\bu_
\bl_
\ba_
\br _
\bE_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn_
\bs
2228 All string patterns in Mutt-ng including those in more complex _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
2229 tion 6.2 , page 77) must be specified using regular expressions (regexp) in
2230 the ``POSIX extended'' syntax (which is more or less the syntax used by egrep
2231 and GNU awk). For your convenience, we have included below a brief description
2234 The search is case sensitive if the pattern contains at least one upper case
2235 letter, and case insensitive otherwise. Note that ``\'' must be quoted if used
2236 for a regular expression in an initialization command: ``\\''.
2238 A regular expression is a pattern that describes a set of strings. Regular
2239 expressions are constructed analogously to arithmetic expressions, by using
2240 various operators to combine smaller expressions.
2242 Note that the regular expression can be enclosed/delimited by either ' or '
2243 which is useful if the regular expression includes a white-space character.
2244 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-
2245 tion on ' and ' delimiter processing. To match a literal ' or ' you must pref-
2246 ace it with \ (backslash).
2248 The fundamental building blocks are the regular expressions that match a single
2249 character. Most characters, including all letters and digits, are regular
2250 expressions that match themselves. Any metacharacter with special meaning may
2251 be quoted by preceding it with a backslash.
2253 The period ``.'' matches any single character. The caret ``^'' and the dollar
2254 sign ``$'' are metacharacters that respectively match the empty string at the
2255 beginning and end of a line.
2257 The Mutt Next Generation E-Mail Client 46
2259 A list of characters enclosed by ``['' and ``]'' matches any single character
2260 in that list; if the first character of the list is a caret ``^'' then it
2261 matches any character n
\bno
\bot
\bt in the list. For example, the regular expression
2262 [
\b[0
\b01
\b12
\b23
\b34
\b45
\b56
\b67
\b78
\b89
\b9]
\b] matches any single digit. A range of ASCII characters may be
2263 specified by giving the first and last characters, separated by a hyphen ``-''.
2264 Most metacharacters lose their special meaning inside lists. To include a lit-
2265 eral ``]'' place it first in the list. Similarly, to include a literal ``^''
2266 place it anywhere but first. Finally, to include a literal hyphen ``-'' place
2269 Certain named classes of characters are predefined. Character classes consist
2270 of ``[:'', a keyword denoting the class, and ``:]''. The following classes are
2271 defined by the POSIX standard:
2274 Alphanumeric characters.
2277 Alphabetic characters.
2280 Space or tab characters.
2289 Characters that are both printable and visible. (A space is print-
2290 able, but not visible, while an ``a'' is both.)
2293 Lower-case alphabetic characters.
2296 Printable characters (characters that are not control characters.)
2299 Punctuation characters (characters that are not letter, digits,
2300 control characters, or space characters).
2303 Space characters (such as space, tab and formfeed, to name a few).
2306 Upper-case alphabetic characters.
2309 Characters that are hexadecimal digits.
2311 A character class is only valid in a regular expression inside the brackets of
2312 a character list. Note that the brackets in these class names are part of the
2314 The Mutt Next Generation E-Mail Client 47
2316 symbolic names, and must be included in addition to the brackets delimiting the
2317 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].
2319 Two additional special sequences can appear in character lists. These apply to
2320 non-ASCII character sets, which can have single symbols (called collating ele-
2321 ments) that are represented with more than one character, as well as several
2322 characters that are equivalent for collating or sorting purposes:
2325 A collating symbol is a multi-character collating element enclosed
2326 in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele-
2327 ment, then [
\b[[
\b[.
\b.c
\bch
\bh.
\b.]
\b]]
\b] is a regexp that matches this collating ele-
2328 ment, while [
\b[c
\bch
\bh]
\b] is a regexp that matches either ``c'' or ``h''.
2331 An equivalence class is a locale-specific name for a list of char-
2332 acters that are equivalent. The name is enclosed in ``[='' and
2333 ``=]''. For example, the name ``e'' might be used to represent all
2334 of ``'' ``'' and ``e''. In this case, [
\b[[
\b[=
\b=e
\be=
\b=]
\b]]
\b] is a regexp that
2335 matches any of ``'', ``'' and ``e''.
2337 A regular expression matching a single character may be followed by one of sev-
2338 eral repetition operators:
2341 The preceding item is optional and matched at most once.
2344 The preceding item will be matched zero or more times.
2347 The preceding item will be matched one or more times.
2350 The preceding item is matched exactly _
\bn times.
2353 The preceding item is matched _
\bn or more times.
2356 The preceding item is matched at most _
\bm times.
2359 The preceding item is matched at least _
\bn times, but no more than _
\bm
2362 Two regular expressions may be concatenated; the resulting regular expression
2363 matches any string formed by concatenating two substrings that respectively
2364 match the concatenated subexpressions.
2366 Two regular expressions may be joined by the infix operator ``|''; the result-
2367 ing regular expression matches any string matching either subexpression.
2369 Repetition takes precedence over concatenation, which in turn takes precedence
2371 The Mutt Next Generation E-Mail Client 48
2373 over alternation. A whole subexpression may be enclosed in parentheses to
2374 override these precedence rules.
2376 N
\bNo
\bot
\bte
\be:
\b: If you compile Mutt-ng with the GNU _
\br_
\bx package, the following operators
2377 may also be used in regular expressions:
2380 Matches the empty string at either the beginning or the end of a
2384 Matches the empty string within a word.
2387 Matches the empty string at the beginning of a word.
2390 Matches the empty string at the end of a word.
2393 Matches any word-constituent character (letter, digit, or under-
2397 Matches any character that is not word-constituent.
2400 Matches the empty string at the beginning of a buffer (string).
2403 Matches the empty string at the end of a buffer.
2405 Please note however that these operators are not defined by POSIX, so they may
2406 or may not be available in stock libraries on various systems.
2408 _
\b4_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2410 Mutt-ng's pattern language provides a simple yet effective way to set up rules
2411 to match messages, e.g. for operations like tagging and scoring. A pattern con-
2412 sists of one or more sub-pattern, which can be logically grouped, ORed, and
2413 negated. For a complete listing of these patterns, please refer to table _
\bP_
\ba_
\bt_
\b-
2414 _
\bt_
\be_
\br_
\bn_
\bs (section 6.2 , page 77) in the Reference chapter.
2416 It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular
2417 expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also
2420 _
\b4_
\b._
\b2_
\b._
\b1 _
\bC_
\bo_
\bm_
\bp_
\bl_
\be_
\bx _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
2422 It is possible to combine several sub-patterns to a more complex pattern. The
2423 most simple possibility is to logically AND several patterns by stringing them
2426 The Mutt Next Generation E-Mail Client 49
2430 The pattern above matches all messages that contain ``SPAM'' in the subject and
2433 To logical OR patterns, simply use the | operator. This one especially useful
2434 when using local groups:
2436 ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org")
2437 (~b mutt-ng|~s Mutt-ng)
2440 The first pattern matches all messages that were sent by one of the mutt-ng
2441 maintainers, while the seconds pattern matches all messages that contain
2442 ``mutt-ng'' in the message body or ``Mutt-ng'' in the subject. The third pat-
2443 tern matches all messages that do not contain ``@synflood\.at'' in the Refer-
2444 ences: header, i.e. messages that are not an (indirect) reply to one of my
2445 messages. A pattern can be logicall negated using the ! operator.
2447 _
\b4_
\b._
\b2_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs _
\ba_
\bn_
\bd _
\bD_
\ba_
\bt_
\be_
\bs
2449 When using dates in patterns, the dates must be specified in a special format,
2450 i.e. DD/MM/YYYY. If you don't specify month or year, they default to the cur-
2451 rent month or year. When using date ranges, and you specify only the minimum or
2452 the maximum, the specified date will be excluded, e.g. 01/06/2005- matches
2453 against all messages _
\ba_
\bf_
\bt_
\be_
\br Juni 1st, 2005.
2455 It is also possible to use so-called ``error margins'' when specifying date
2456 ranges. You simply specify a date, and then the error margin. This margin
2457 needs to contain the information whether it goes ``forth'' or ``back'' in time,
2458 by using + and -. Then follows a number and a unit, i.e. y for years, m for
2459 months, w for weeks and d for days. If you use the special * sign, it means
2460 that the error margin goes to both ``directions'' in time.
2466 The first pattern matches all dates between January 1st, 2005 and January 1st
2467 2006. The second pattern matches all dates between October 18th, 2004 and
2468 October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches
2469 all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th).
2471 Relative dates are also very important, as they make it possible to specify
2472 date ranges between a fixed number of units and the current date. How this
2473 works can be seen in the following example:
2475 The Mutt Next Generation E-Mail Client 50
2477 ~d >2w # messages older than two weeks
2478 ~d <3d # messages newer than 3 days
2479 ~d =1m # messages that are exactly one month old
2481 _
\b4_
\b._
\b3 _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs
2483 _
\b4_
\b._
\b3_
\b._
\b1 _
\bI_
\bn_
\bt_
\br_
\bo_
\bd_
\bu_
\bc_
\bt_
\bi_
\bo_
\bn
2485 The so called _
\bF_
\bo_
\br_
\bm_
\ba_
\bt _
\bS_
\bt_
\br_
\bi_
\bn_
\bg_
\bs offer great flexibility when configuring mutt-ng.
2486 In short, they describe what items to print out how in menus and status mes-
2489 Basically, they work as this: for different menus and bars, there's a variable
2490 specifying the layout. For every item available, there is a so called _
\be_
\bx_
\bp_
\ba_
\bn_
\bd_
\bo.
2492 For example, when running mutt-ng on different machines or different versions
2493 for testing purposes, it may be interesting to have the following information
2494 always printed on screen when one is in the index:
2496 +
\bo the current hostname
2498 +
\bo the current mutt-ng version number
2500 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-
2501 _
\bm_
\ba_
\bt (section 6.4.307 , page 154) variable. For the hostname and version
2502 string, there's an expando for $status_format: %h expands to the hostname and
2503 %v to the version string. When just configuring:
2505 set status_format = "%v on %h: ..."
2507 mutt-ng will replace the sequence %v with the version string and %h with the
2508 host's name. When you are, for example, running mutt-ng version 1.5.9i on host
2509 mailhost, you'll see the following when you're in the index:
2511 Mutt-ng 1.5.9i on mailhost: ...
2513 In the index, there're more useful information one could want to see:
2515 +
\bo which mailbox is open
2517 +
\bo how man new, flagged or postponed messages
2521 To include the mailbox' name is as easy as:
2523 The Mutt Next Generation E-Mail Client 51
2525 set status_format = "%v on %h: %B: ...
2527 When the currently opened mailbox is Inbox, this will be expanded to:
2529 Mutt-ng 1.5.9i on mailhost: Inbox: ...
2531 For the number of certain types of messages, one more feature of the format
2532 strings is extremely useful. If there aren't messages of a certain type, it may
2533 not be desired to print just that there aren't any but instead only print some-
2534 thing if there are any.
2536 _
\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
2538 To only print the number of messages if there are new messages in the current
2539 mailbox, further extend $status_format to:
2541 set status_format = "%v on %h: %B %?n?%n new? ...
2543 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
2544 optionally printed nonzero, i.e. a portion of the format string is only evalu-
2545 ated if the value of the expando is different from zero. The basic syntax is:
2547 %?<item>?<string if nonzero>?
2549 which tells mutt-ng to only look at <string if nonzero> if the value of the
2550 %<item%gt; expando is different from zero. In our example, we used n as the
2551 expando to check for and %n new as the optional nonzero string.
2553 But this is not all: this feature only offers one alternative: ``print some-
2554 thing if not zero.'' Mutt-ng does, as you might guess, also provide a logically
2555 complete version: ``if zero, print something and else print something else.''
2556 This is achieved by the following syntax for those expandos which may be
2559 %?<item>?<string if nonzero>&<string if zero>?
2561 Using this we can make mutt-ng to do the following:
2563 +
\bo make it print ``_
\bn new messages'' whereby _
\bn is the count but only if there
2566 +
\bo and make it print ``no new messages'' if there aren't any
2568 The Mutt Next Generation E-Mail Client 52
2570 The corresponding configuration is:
2572 set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...
2574 This doubles the use of the ``new messages'' string because it'll get always
2575 printed. Thus, it can be shortened to:
2577 set status_format = "%v on %h: %B: %?n?%n&no? new messages ...
2579 As you might see from this rather simple example, one can create very complex
2580 but fancy status messages. Please see the reference chapter for expandos and
2581 those which may be printed nonzero.
2583 _
\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
2585 Besides the information given so far, there're even more features of format
2588 +
\bo When specifying %_<item> instead of just %<item>, mutt-ng will convert all
2589 characters in the expansion of <item> to lowercase.
2591 +
\bo When specifying %:<item> instead of just %<item>, mutt-ng will convert all
2592 dots in the expansion of <item> to underscores (_).
2594 Also, there's a feature called _
\bP_
\ba_
\bd_
\bd_
\bi_
\bn_
\bg supplied by the following two expandos:
2598 When this occurs, mutt-ng will fill the rest of the line with the
2599 character X. In our example, filling the rest of the line with
2600 dashes is done by setting:
2602 set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
2605 Since the previous expando stops at the end of line, there must be
2606 a way to fill the gap between two items via the %>X expando: it
2607 puts as many characters X in between two items so that the rest of
2608 the line will be right-justified. For example, to not put the ver-
2609 sion string and hostname of our example on the left but on the
2610 right and fill the gap with spaces, one might use (note the space
2613 set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
2615 The Mutt Next Generation E-Mail Client 53
2617 _
\b4_
\b._
\b4 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bT_
\ba_
\bg_
\bs
2619 Sometimes it is desirable to perform an operation on a group of messages all at
2620 once rather than one at a time. An example might be to save messages to a
2621 mailing list to a separate folder, or to delete all messages with a given sub-
2622 ject. To tag all messages matching a pattern, use the tag-pattern function,
2623 which is bound to ``shift-T'' by default. Or you can select individual mes-
2624 sages by hand using the ``tag-message'' function, which is bound to ``t'' by
2625 default. See _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 6.2 , page 77) for Mutt-ng's pattern matching
2628 Once you have tagged the desired messages, you can use the ``tag-prefix'' oper-
2629 ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix''
2630 operator is used, the n
\bne
\bex
\bxt
\bt operation will be applied to all tagged messages if
2631 that operation can be used in that manner. If the _
\b$_
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg (section 6.4.16 ,
2632 page 84) variable is set, the next operation applies to the tagged messages
2633 automatically, without requiring the ``tag-prefix''.
2635 In _
\bm_
\ba_
\bc_
\br_
\bo_
\bs (section 3.7 , page 27) or _
\bp_
\bu_
\bs_
\bh (section 3.23 , page 37) commands,
2636 you can use the ``tag-prefix-cond'' operator. If there are no tagged messages,
2637 mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will
2638 stop "eating" the macro when it encounters the ``end-cond'' operator; after
2639 this operator the rest of the macro will be executed as normal.
2641 _
\b4_
\b._
\b5 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bH_
\bo_
\bo_
\bk_
\bs
2643 A _
\bh_
\bo_
\bo_
\bk is a concept borrowed from the EMACS editor which allows you to execute
2644 arbitrary commands before performing some operation. For example, you may wish
2645 to tailor your configuration based upon which mailbox you are reading, or to
2646 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
2647 _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 44) or _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 6.2 , page 77) along
2648 with a configuration option/command. See
2650 +
\bo _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.6 , page 26)
2652 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 36)
2654 +
\bo _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.21 , page 37)
2656 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 35)
2658 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33)
2660 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 35)
2662 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.19 , page 36)
2664 for specific details on each type of _
\bh_
\bo_
\bo_
\bk available.
2666 N
\bNo
\bot
\bte
\be:
\b: if a hook changes configuration settings, these changes remain effective
2667 until the end of the current mutt session. As this is generally not desired, a
2668 default hook needs to be added before all other hooks to restore configuration
2670 The Mutt Next Generation E-Mail Client 54
2672 defaults. Here is an example with send-hook and the my_hdr directive:
2674 send-hook . 'unmy_hdr From:'
2675 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2677 _
\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
2679 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are
2680 evaluated in a slightly different manner. For the other types of hooks, a _
\br_
\be_
\bg_
\b-
2681 _
\bu_
\bl_
\ba_
\br _
\be_
\bx_
\bp_
\br_
\be_
\bs_
\bs_
\bi_
\bo_
\bn (section 4.1 , page 44) is sufficient. But in dealing with
2682 messages a finer grain of control is needed for matching since for different
2683 purposes you want to match different criteria.
2685 Mutt-ng allows the use of the _
\bs_
\be_
\ba_
\br_
\bc_
\bh _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn (section 6.2 , page 77) language
2686 for matching messages in hook commands. This works in exactly the same way as
2687 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
2688 to those operators which match information mutt extracts from the header of the
2689 message (i.e. from, to, cc, date, subject, etc.).
2691 For example, if you wanted to set your return address based upon sending mail
2692 to a specific address, you could do something like:
2694 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User <user@host>'
2696 which would execute the given command when sending mail to _
\bm_
\be_
\b@_
\bc_
\bs_
\b._
\bh_
\bm_
\bc_
\b._
\be_
\bd_
\bu.
2698 However, it is not required that you write the pattern to match using the full
2699 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
2700 other hooks, in which case Mutt-ng will translate your pattern into the full
2701 language, using the translation specified by the _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section
2702 6.4.45 , page 90) variable. The pattern is translated at the time the hook is
2703 declared, so the value of _
\b$_
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk (section 6.4.45 , page 90) that is in
2704 effect at that time will be used.
2706 _
\b4_
\b._
\b6 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br
2708 The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing
2709 which looks very similar to the ones you probably know from GUI mail clients.
2710 The sidebar lists all specified mailboxes, shows the number in each and high-
2711 lights the ones with new email Use the following configuration commands:
2713 set sidebar_visible="yes"
2714 set sidebar_width=25
2716 If you want to specify the mailboxes you can do so with:
2718 The Mutt Next Generation E-Mail Client 55
2726 You can also specify the colors for mailboxes with new mails by using:
2728 color sidebar_new red black
2729 color sidebar white black
2731 The available functions are:
2733 sidebar-scroll-up Scrolls the mailbox list up 1 page
2734 sidebar-scroll-down Scrolls the mailbox list down 1 page
2735 sidebar-next Highlights the next mailbox
2736 sidebar-next-new Highlights the next mailbox with new mail
2737 sidebar-previous Highlights the previous mailbox
2738 sidebar-open Opens the currently highlighted mailbox
2740 Reasonable key bindings look e.g. like this:
2742 bind index \Cp sidebar-prev
2743 bind index \Cn sidebar-next
2744 bind index \Cb sidebar-open
2745 bind pager \Cp sidebar-prev
2746 bind pager \Cn sidebar-next
2747 bind pager \Cb sidebar-open
2749 macro index B ':toggle sidebar_visible^M'
2750 macro pager B ':toggle sidebar_visible^M'
2752 You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and
2753 off the sidebar simply by pressing 'B'.
2755 _
\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
2757 Mutt-ng supports connecting to external directory databases such as LDAP,
2758 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a
2759 simple interface. Using the _
\b$_
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 6.4.221 , page 134) vari-
2760 able, you specify the wrapper command to use. For example:
2762 set query_command = "mutt_ldap_query.pl '%s'"
2764 The wrapper script should accept the query on the command-line. It should
2765 return a one line message, then each matching response on a single line, each
2767 The Mutt Next Generation E-Mail Client 56
2769 line containing a tab separated address then name then some other optional
2770 information. On error, or if there are no matching addresses, return a non-
2771 zero exit code and a one line error message.
2773 An example multiple response output:
2775 Searching database ... 20 entries ... 3 matching:
2776 me@cs.hmc.edu Michael Elkins mutt dude
2777 blong@fiction.net Brandon Long mutt and more
2778 roessler@guug.de Thomas Roessler mutt pgp
2780 There are two mechanisms for accessing the query function of mutt. One is to
2781 do a query from the index menu using the query function (default: Q). This
2782 will prompt for a query, then bring up the query menu which will list the
2783 matching responses. From the query menu, you can select addresses to create
2784 aliases, or to mail. You can tag multiple addresses to mail, start a new
2785 query, or have a new query appended to the current responses.
2787 The other mechanism for accessing the query function is for address completion,
2788 similar to the alias completion. In any prompt for address entry, you can use
2789 the complete-query function (default: ^T) to run a query based on the current
2790 address you have typed. Like aliases, mutt will look for what you have typed
2791 back to the last space or comma. If there is a single response for that query,
2792 mutt will expand the address in place. If there are multiple responses, mutt
2793 will activate the query menu. At the query menu, you can select one or more
2794 addresses to be added to the prompt.
2796 _
\b4_
\b._
\b8 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bF_
\bo_
\br_
\bm_
\ba_
\bt_
\bs
2798 Mutt-ng supports reading and writing of four different mailbox formats: mbox,
2799 MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
2800 use a flag for different mailbox types. When creating new mailboxes, Mutt-ng
2801 uses the default specified with the _
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 6.4.125 , page 111)
2804 m
\bmb
\bbo
\box
\bx. This is the most widely used mailbox format for UNIX. All messages are
2805 stored in a single file. Each message has a line of the form:
2807 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2809 to denote the start of a new message (this is often referred to as the
2812 M
\bMM
\bMD
\bDF
\bF. This is a variant of the _
\bm_
\bb_
\bo_
\bx format. Each message is surrounded by
2813 lines containing ``^A^A^A^A'' (four control-A's).
2815 M
\bMH
\bH. A radical departure from _
\bm_
\bb_
\bo_
\bx and _
\bM_
\bM_
\bD_
\bF, a mailbox consists of a directory
2816 and each message is stored in a separate file. The filename indicates the mes-
2817 sage number (however, this is may not correspond to the message number Mutt-ng
2819 The Mutt Next Generation E-Mail Client 57
2821 displays). Deleted messages are renamed with a comma (,) prepended to the file-
2822 name. N
\bNo
\bot
\bte
\be:
\b: Mutt detects this type of mailbox by looking for either
2823 .mh_sequences or .xmhcache (needed to distinguish normal directories from MH
2826 M
\bMa
\bai
\bil
\bld
\bdi
\bir
\br. The newest of the mailbox formats, used by the Qmail MTA (a replace-
2827 ment for sendmail). Similar to _
\bM_
\bH, except that it adds three subdirectories of
2828 the mailbox: _
\bt_
\bm_
\bp, _
\bn_
\be_
\bw and _
\bc_
\bu_
\br. Filenames for the messages are chosen in such a
2829 way they are unique, even when two programs are writing the mailbox over NFS,
2830 which means that no file locking is needed.
2832 _
\b4_
\b._
\b9 _
\bM_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx _
\bS_
\bh_
\bo_
\br_
\bt_
\bc_
\bu_
\bt_
\bs
2834 There are a number of built in shortcuts which refer to specific mailboxes.
2835 These shortcuts can be used anywhere you are prompted for a file or mailbox
2838 +
\bo ! -- refers to your _
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 6.4.296 , page 151) (incoming)
2841 +
\bo > -- refers to your _
\b$_
\bm_
\bb_
\bo_
\bx (section 6.4.124 , page 110) file
2843 +
\bo < -- refers to your _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 6.4.230 , page 136) file
2845 +
\bo ^ -- refers to the current mailbox
2847 +
\bo - or !! -- refers to the file you've last visited
2849 +
\bo ~ -- refers to your home directory
2851 +
\bo = or + -- refers to your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 6.4.64 , page 94) directory
2853 +
\bo @_
\ba_
\bl_
\bi_
\ba_
\bs -- refers to the _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt _
\bs_
\ba_
\bv_
\be _
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 3.17 , page 35) as
2854 determined by the address of the alias
2856 _
\b4_
\b._
\b1_
\b0 _
\bH_
\ba_
\bn_
\bd_
\bl_
\bi_
\bn_
\bg _
\bM_
\ba_
\bi_
\bl_
\bi_
\bn_
\bg _
\bL_
\bi_
\bs_
\bt_
\bs
2858 Mutt-ng has a few configuration options that make dealing with large amounts of
2859 mail easier. The first thing you must do is to let Mutt know what addresses
2860 you consider to be mailing lists (technically this does not have to be a mail-
2861 ing list, but that is what it is most often used for), and what lists you are
2862 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
2863 (section 3.12 , page 32) commands in your muttrc.
2865 Now that Mutt-ng knows what your mailing lists are, it can do several things,
2866 the first of which is the ability to show the name of a list through which you
2867 received a message (i.e., of a subscribed list) in the _
\bi_
\bn_
\bd_
\be_
\bx menu display.
2868 This is useful to distinguish between personal and list mail in the same mail-
2869 box. In the _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105) variable, the escape
2870 ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To''
2872 The Mutt Next Generation E-Mail Client 58
2874 field, and ``Cc <list>'' when it appears in the ``Cc'' field (otherwise it
2875 returns the name of the author).
2877 Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get
2878 quite large. Most people do not bother to remove the author of the message they
2879 are reply to from the list, resulting in two or more copies being sent to that
2880 person. The ``list-reply'' function, which by default is bound to ``L'' in the
2881 _
\bi_
\bn_
\bd_
\be_
\bx menu and _
\bp_
\ba_
\bg_
\be_
\br, helps reduce the clutter by only replying to the known
2882 mailing list addresses instead of all recipients (except as specified by Mail-
2883 Followup-To, see below).
2885 Mutt-ng also supports the Mail-Followup-To header. When you send a message to
2886 a list of recipients which includes one or several subscribed mailing lists,
2887 and if the _
\b$_
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo (section 6.4.66 , page 95) option is set, mutt will
2888 generate a Mail-Followup-To header which contains all the recipients to whom
2889 you send this message, but not your address. This indicates that group-replies
2890 or list-replies (also known as ``followups'') to this message should only be
2891 sent to the original recipients of the message, and not separately to you -
2892 you'll receive your copy through one of the mailing lists you are subscribed
2895 Conversely, when group-replying or list-replying to a message which has a Mail-
2896 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
2897 (section 6.4.88 , page 100) configuration variable is set. Using list-reply
2898 will in this case also make sure that the reply goes to the mailing list, even
2899 if it's not specified in the list of recipients in the Mail-Followup-To.
2901 Note that, when header editing is enabled, you can create a Mail-Followup-To
2902 header manually. Mutt-ng will only auto-generate this header if it doesn't
2903 exist when you send the message.
2905 The other method some mailing list admins use is to generate a ``Reply-To''
2906 field which points back to the mailing list address rather than the author of
2907 the message. This can create problems when trying to reply directly to the
2908 author in private, since most mail clients will automatically reply to the
2909 address given in the ``Reply-To'' field. Mutt-ng uses the _
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo (section
2910 6.4.233 , page 136) variable to help decide which address to use. If set to
2911 _
\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
2912 use the address given in the ``Reply-To'' field, or reply directly to the
2913 address given in the ``From'' field. When set to _
\by_
\be_
\bs, the ``Reply-To'' field
2914 will be used when present.
2916 The ``X-Label:'' header field can be used to further identify mailing lists or
2917 list subject matter (or just to annotate messages individually). The
2918 _
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105) variable's ``%y'' and ``%Y''
2919 escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's
2920 pattern-matcher can match regular expressions to ``X-Label:'' fields with the
2921 ``~y'' selector. ``X-Label:'' is not a standard message header field, but it
2922 can easily be inserted by procmail and other mail filtering agents.
2924 Lastly, Mutt-ng has the ability to _
\bs_
\bo_
\br_
\bt (section 6.4.290 , page 149) the mail-
2925 box into _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs (section 2.5.3 , page 11). A thread is a group of messages
2926 which all relate to the same subject. This is usually organized into a tree-
2927 like structure where a message and all of its replies are represented
2929 The Mutt Next Generation E-Mail Client 59
2931 graphically. If you've ever used a threaded news client, this is the same con-
2932 cept. It makes dealing with large volume mailing lists easier because you can
2933 easily delete uninteresting threads and quickly find topics of value.
2935 _
\b4_
\b._
\b1_
\b1 _
\bE_
\bd_
\bi_
\bt_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2937 Mutt-ng has the ability to dynamically restructure threads that are broken
2938 either by misconfigured software or bad behavior from some correspondents. This
2939 allows to clean your mailboxes formats) from these annoyances which make it
2940 hard to follow a discussion.
2942 _
\b4_
\b._
\b1_
\b1_
\b._
\b1 _
\bL_
\bi_
\bn_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2944 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer-
2945 ences:" headers when replying to a message. This results in broken discussions
2946 because Mutt-ng has not enough information to guess the correct threading. You
2947 can fix this by tagging the reply, then moving to the parent message and using
2948 the ``link-threads'' function (bound to & by default). The reply will then be
2949 connected to this "parent" message.
2951 You can also connect multiple children at once, tagging them and using the tag-
2952 prefix command (';') or the auto_tag option.
2954 _
\b4_
\b._
\b1_
\b1_
\b._
\b2 _
\bB_
\br_
\be_
\ba_
\bk_
\bi_
\bn_
\bg _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
2956 On mailing lists, some people are in the bad habit of starting a new discussion
2957 by hitting "reply" to any message from the list and changing the subject to a
2958 totally unrelated one. You can fix such threads by using the ``break-thread''
2959 function (bound by default to #), which will turn the subthread starting from
2960 the current message into a whole different thread.
2962 _
\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
2964 RFC1894 defines a set of MIME content types for relaying information about the
2965 status of electronic mail messages. These can be thought of as ``return
2966 receipts.'' Berkeley sendmail 8.8.x currently has some command line options in
2967 which the mail client can make requests as to what type of status messages
2970 To support this, there are two variables. _
\b$_
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by (section 6.4.51 , page
2971 91) is used to request receipts for different results (such as failed message,
2972 message delivered, etc.). _
\b$_
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn (section 6.4.52 , page 92) requests how
2973 much of your message should be returned with the receipt (headers or full mes-
2974 sage). Refer to the man page on sendmail for more details on DSN.
2976 _
\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)
2978 If Mutt-ng was compiled with POP3 support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
2980 The Mutt Next Generation E-Mail Client 60
2982 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
2983 remote POP3 server and fetch mail for local browsing.
2985 You can access the remote POP3 mailbox by selecting the folder
2988 You can select an alternative port by specifying it with the server, i.e.:
2989 pop://popserver:port/.
2991 You can also specify different username for each folder, i.e.: pop://user-
2992 name@popserver[:port]/.
2994 Polling for new mail is more expensive over POP3 than locally. For this reason
2995 the frequency at which Mutt-ng will check for mail remotely can be controlled
2996 by the _
\b$_
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 6.4.208 , page 131) variable, which defaults
2997 to every 60 seconds.
2999 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3000 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to POP3 servers can be encrypted. This natu-
3001 rally requires that the server supports SSL encrypted connections. To access a
3002 folder with POP3/SSL, you should use pops: prefix, ie: pops://[user-
3003 name@]popserver[:port]/.
3005 Another way to access your POP3 mail is the _
\bf_
\be_
\bt_
\bc_
\bh_
\b-_
\bm_
\ba_
\bi_
\bl function (default: G).
3006 It allows to connect to _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 6.4.206 , page 130), fetch all your
3007 new mail and place it in the local _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 6.4.296 , page 151).
3008 After this point, Mutt-ng runs exactly as if the mail had always been local.
3010 N
\bNo
\bot
\bte
\be:
\b: If you only need to fetch all messages to local mailbox you should con-
3011 sider using a specialized program, such as fetchmail
3013 _
\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)
3015 If Mutt-ng was compiled with IMAP support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3016 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
3019 You can access the remote inbox by selecting the folder
3020 imap://imapserver/INBOX, where imapserver is the name of the IMAP server and
3021 INBOX is the special name for your spool mailbox on the IMAP server. If you
3022 want to access another mail folder at the IMAP server, you should use
3023 imap://imapserver/path/to/folder where path/to/folder is the path of the folder
3026 You can select an alternative port by specifying it with the server, i.e.:
3027 imap://imapserver:port/INBOX.
3029 You can also specify different username for each folder, i.e.: imap://user-
3030 name@imapserver[:port]/INBOX.
3032 If Mutt-ng was compiled with SSL support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\be script with
3033 the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\bs_
\bl flag), connections to IMAP servers can be encrypted. This
3035 The Mutt Next Generation E-Mail Client 61
3037 naturally requires that the server supports SSL encrypted connections. To
3038 access a folder with IMAP/SSL, you should use imaps://[user-
3039 name@]imapserver[:port]/path/to/folder as your folder path.
3041 Pine-compatible notation is also supported, i.e. {[user-
3042 name@]imapserver[:port][/ssl]}path/to/folder
3044 Note that not all servers use / as the hierarchy separator. Mutt-ng should
3045 correctly notice which separator is being used by the server and convert paths
3048 When browsing folders on an IMAP server, you can toggle whether to look at only
3049 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
3050 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 6.4.97 , page 102) vari-
3053 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3054 want to carefully tune the _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 6.4.99 , page 103) and
3055 _
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 6.4.320 , page 159) variables.
3057 Note that if you are using mbox as the mail store on UW servers prior to
3058 v12.250, the server has been reported to disconnect a client if another client
3059 selects the same folder.
3061 _
\b4_
\b._
\b1_
\b4_
\b._
\b1 _
\bT_
\bh_
\be _
\bF_
\bo_
\bl_
\bd_
\be_
\br _
\bB_
\br_
\bo_
\bw_
\bs_
\be_
\br
3063 As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
3064 mostly the same as the local file browser, with the following differences:
3066 +
\bo Instead of file permissions, mutt displays the string "IMAP", possibly
3067 followed by the symbol "+", indicating that the entry contains both mes-
3068 sages and subfolders. On Cyrus-like servers folders will often contain
3069 both messages and subfolders.
3071 +
\bo For the case where an entry can contain both messages and subfolders, the
3072 selection key (bound to enter by default) will choose to descend into the
3073 subfolder view. If you wish to view the messages in that folder, you must
3074 use view-file instead (bound to space by default).
3076 +
\bo You can create, delete and rename mailboxes with the create-mailbox,
3077 delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
3078 respectively). You may also subscribe and unsubscribe to mailboxes (nor-
3079 mally these are bound to s and u, respectively).
3081 _
\b4_
\b._
\b1_
\b4_
\b._
\b2 _
\bA_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
3083 Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI,
3084 CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica-
3085 tion for you poor exchange users out there, but it has yet to be integrated
3086 into the main tree). There is also support for the pseudo-protocol ANONYMOUS,
3087 which allows you to log in to a public IMAP server without having an account.
3088 To use ANONYMOUS, simply make your username blank or "anonymous".
3090 SASL is a special super-authenticator, which selects among several protocols
3092 The Mutt Next Generation E-Mail Client 62
3094 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
3095 available on your host and the server. Using some of these methods (including
3096 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
3097 invisible to those teeming network snoops. It is the best option if you have
3098 it. To use it, you must have the Cyrus SASL library installed on your system
3099 and compile mutt with the _
\b-_
\b-_
\bw_
\bi_
\bt_
\bh_
\b-_
\bs_
\ba_
\bs_
\bl flag.
3101 Mutt-ng will try whichever methods are compiled in and available on the server,
3102 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3104 There are a few variables which control authentication:
3106 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 6.4.105 , page 104) - controls the username under
3107 which you request authentication on the IMAP server, for all authentica-
3108 tors. This is overridden by an explicit username in the mailbox path (i.e.
3109 by using a mailbox name of the form {user@host}).
3111 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 6.4.100 , page 103) - a password which you may pre-
3112 set, used by all authentication methods where a password is needed.
3114 +
\bo _
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs (section 6.4.91 , page 101) - a colon-delimited list
3115 of IMAP authentication methods to try, in the order you wish to try them.
3116 If specified, this overrides mutt's default (attempt everything, in the
3117 order listed above).
3119 _
\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)
3121 If compiled with ``--enable-nntp'' option, Mutt-ng can read news from a
3122 newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup''
3123 function from the index/pager which is by default bound to i.
3125 The Default newsserver can be obtained from the $NNTPSERVER environment vari-
3126 able. Like other news readers, info about subscribed newsgroups is saved in a
3127 file as specified by the _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc (section 6.4.156 , page 119) variable.
3128 Article headers are cached and can be loaded from a file when a newsgroup is
3129 entered instead loading from newsserver; currently, this caching mechanism
3130 still is different from the header caching for maildir/IMAP.
3132 _
\b4_
\b._
\b1_
\b5_
\b._
\b1 _
\bA_
\bg_
\ba_
\bi_
\bn_
\b: _
\bS_
\bc_
\bo_
\br_
\bi_
\bn_
\bg
3134 Especially for Usenet, people often ask for advanced filtering and scoring
3135 functionality. Of course, mutt-ng has scoring and allows a killfile, too. How
3136 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
3139 What has not been discusses in detail is mutt-ng's built-in realname filter.
3140 For may newsreaders including those for ``advanced users'' like _
\bs_
\bl_
\br_
\bn or _
\bt_
\bi_
\bn,
3141 there are frequent request for such functionality. The solutions offered often
3142 are complicated regular expressions.
3144 In mutt-ng this is as easy as
3146 The Mutt Next Generation E-Mail Client 63
3150 This tells mutt-ng to apply a score of 42 to all messages whose sender speci-
3151 fied a valid realname and a valid email address. Using
3155 on the contrary applies a score of 42 to all messages _
\bn_
\bo_
\bt matching those crite-
3156 ria which are very strict:
3158 +
\bo Email addresses must be valid according to RFC 2822, see <ftp://ftp.rfc-
3159 editor.org/in-notes/rfc2822.txt>
3161 +
\bo the name must consist of at least 2 fields whereby a field must not end in
3162 a dot. This means that ``Joe User'' and ``Joe A. User'' are valid while
3163 ``J. User'' and ``J. A. User'' aren't.
3165 +
\bo it's assumed that users are interested in reading their own mail and mail
3166 from people who they have defined an alias for so that those 2 groups of
3167 messages are excluded from the strict rules.
3169 _
\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)
3171 Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP
3172 functionality. When configure was called with --with-libesmtp or the output
3173 muttng -v contains +USE_LIBESMTP, this will be or is the case already.
3175 To enable sending mail directly via SMTP without an MTA such as Postfix or
3176 SSMTP and the like, simply set the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt (section 6.4.285 , page 148)
3177 variable pointing to your SMTP server.
3179 Authentication mechanisms are available via the _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 6.4.289 ,
3180 page 149) and _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs (section 6.4.286 , page 148) variables.
3182 Transport Encryption via the StartTLS command is also available. For this to
3183 work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the
3184 _
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs (section 6.4.288 , page 149) variable must be either set to
3185 ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server
3186 supports it: for the second case, the connection will fail if it doesn't while
3187 switching back to unencrypted communication for the first one.
3189 _
\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)
3191 If you happen to have accounts on multiple IMAP and/or POP servers, you may
3192 find managing all the authentication settings inconvenient and error-prone.
3194 The Mutt Next Generation E-Mail Client 64
3196 The account-hook command may help. This hook works like folder-hook but is
3197 invoked whenever you access a remote mailbox (including inside the folder
3198 browser), not just when you open the mailbox.
3202 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3203 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3204 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3206 _
\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)
3208 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
3209 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
3210 start a WWW browser on one of them. This functionality is provided by the
3211 external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con-
3212 trib/ and the configuration commands:
3214 macro index \cb |urlview\n
3215 macro pager \cb |urlview\n
3217 _
\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)
3219 If Mutt-ng was compiled with compressed folders support (by running the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-
3220 _
\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
3221 an arbitrary format, provided that the user has a script to convert from/to
3222 this format to one of the accepted.
3224 The most common use is to open compressed archived folders e.g. with gzip.
3226 In addition, the user can provide a script that gets a folder in an accepted
3227 format and appends its context to the folder in the user-defined format, which
3228 may be faster than converting the entire folder to the accepted format, append-
3229 ing to it and converting back to the user-defined format.
3231 There are three hooks defined (_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 64), _
\bc_
\bl_
\bo_
\bs_
\be_
\b-
3232 _
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) and _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 65))
3233 which define commands to uncompress and compress a folder and to append mes-
3234 sages to an existing compressed folder respectively.
3238 open-hook \\.gz$ "gzip -cd %f > %t"
3239 close-hook \\.gz$ "gzip -c %t > %f"
3240 append-hook \\.gz$ "gzip -c %t >> %f"
3242 The Mutt Next Generation E-Mail Client 65
3244 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-
3245 tion 4.19.3 , page 65), the folder will be open and closed again each time you
3246 will add to it. If you omit _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) (or give
3247 empty command) , the folder will be open in the mode. If you specify _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3248 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 65) though you'll be able to append to the folder.
3250 Note that Mutt-ng will only try to use hooks if the file is not in one of the
3251 accepted formats. In particular, if the file is empty, mutt supposes it is not
3252 compressed. This is important because it allows the use of programs that do not
3253 have well defined extensions. Just use '.' as a regexp. But this may be sur-
3254 prising if your compressing script produces empty files. In this situation,
3255 unset _
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by (section 6.4.240 , page 138), so that the compressed file
3256 will be removed if you delete all of the messages.
3258 _
\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
3260 Usage: open-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3262 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is the command that can be used for opening the folders whose names
3263 match _
\br_
\be_
\bg_
\be_
\bx_
\bp.
3265 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the printf-like format string, and it should accept two
3266 parameters: %f, which is replaced with the (compressed) folder name, and %t
3267 which is replaced with the name of the temporary folder to which to write.
3269 %f and %t can be repeated any number of times in the command string, and all of
3270 the entries are replaced with the appropriate folder name. In addition, %% is
3271 replaced by %, as in printf, and any other %anything is left as is.
3273 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
3274 return non-zero exit status if it fails, so mutt knows something's wrong.
3278 open-hook \\.gz$ "gzip -cd %f > %t"
3280 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type.
3282 _
\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
3284 Usage: close-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3286 This is used to close the folder that was open with the _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3287 4.19.1 , page 64) command after some changes were made to it.
3289 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd string is the command that can be used for closing the folders
3290 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
3291 4.19.1 , page 64) command. Temporary folder in this case is the folder previ-
3292 ously produced by the <_
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 64) command.
3294 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
3295 non-zero exit status if it fails, so mutt knows something's wrong.
3297 The Mutt Next Generation E-Mail Client 66
3301 close-hook \\.gz$ "gzip -c %t > %f"
3303 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type, and the
3304 file can only be open in the readonly mode.
3306 _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) is not called when you exit from the
3307 folder if the folder was not changed.
3309 _
\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
3311 Usage: append-hook _
\br_
\be_
\bg_
\be_
\bx_
\bp '_
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd'
3313 This command is used for saving to an existing compressed folder. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3314 is the command that can be used for appending to the folders whose names match
3315 _
\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 64)
3316 command. The temporary folder in this case contains the messages that are
3319 The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should n
\bno
\bot
\bt remove the decompressed file. The _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd should return
3320 non-zero exit status if it fails, so mutt knows something's wrong.
3324 append-hook \\.gz$ "gzip -c %t >> %f"
3326 When _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 65) is used, the folder is not opened,
3327 which saves time, but this means that we can not find out what the folder type
3328 is. Thus the default (_
\b$_
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be (section 6.4.125 , page 111)) type is always
3329 supposed (i.e. this is the format used for the temporary folder).
3331 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 ,
3332 page 65) is called, and not _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 65). _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-
3333 _
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 65) is only for appending to existing folders.
3335 If the _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd is empty, this operation is disabled for this file type. In this
3336 case, the folder will be open and closed again (using _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section
3337 4.19.1 , page 64) and _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65)respectively) each
3338 time you will add to it.
3340 _
\b4_
\b._
\b1_
\b9_
\b._
\b4 _
\bE_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\be_
\bd _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\bs
3342 The compressed folders support can also be used to handle encrypted folders. If
3343 you want to encrypt a folder with PGP, you may want to use the following hooks:
3345 open-hook \\.pgp$ "pgp -f < %f > %t"
3346 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
3348 The Mutt Next Generation E-Mail Client 67
3350 Please note, that PGP does not support appending to an encrypted folder, so
3351 there is no append-hook defined.
3353 N
\bNo
\bot
\bte
\be:
\b: the folder is temporary stored decrypted in the /tmp directory, where it
3354 can be read by your system administrator. So think about the security aspects
3357 _
\b5_
\b. _
\bM_
\bu_
\bt_
\bt_
\b-_
\bn_
\bg_
\b'_
\bs _
\bM_
\bI_
\bM_
\bE _
\bS_
\bu_
\bp_
\bp_
\bo_
\br_
\bt
3359 Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME
3360 MUA. Every effort has been made to provide the functionality that the discern-
3361 ing MIME user requires, and the conformance to the standards wherever possible.
3362 When configuring Mutt-ng for MIME, there are two extra types of configuration
3363 files which Mutt-ng uses. One is the mime.types file, which contains the map-
3364 ping of file extensions to IANA MIME types. The other is the mailcap file,
3365 which specifies the external commands to use for handling specific MIME types.
3367 _
\b5_
\b._
\b1 _
\bU_
\bs_
\bi_
\bn_
\bg _
\bM_
\bI_
\bM_
\bE _
\bi_
\bn _
\bM_
\bu_
\bt_
\bt
3369 There are three areas/menus in Mutt-ng which deal with MIME, they are the pager
3370 (while viewing a message), the attachment menu and the compose menu.
3372 _
\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
3374 When you select a message from the index and view it in the pager, Mutt decodes
3375 the message to a text representation. Mutt-ng internally supports a number of
3376 MIME types, including text/plain, text/enriched, message/rfc822, and mes-
3377 sage/news. In addition, the export controlled version of Mutt-ng recognizes a
3378 variety of PGP MIME types, including PGP/MIME and application/pgp.
3380 Mutt-ng will denote attachments with a couple lines describing them. These
3381 lines are of the form:
3383 [-- Attachment #1: Description --]
3384 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
3386 Where the Description is the description or filename given for the attachment,
3387 and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary.
3389 If Mutt-ng cannot deal with a MIME type, it will display a message like:
3391 [-- image/gif is unsupported (use 'v' to view this part) --]
3393 _
\b5_
\b._
\b1_
\b._
\b2 _
\bT_
\bh_
\be _
\bA_
\bt_
\bt_
\ba_
\bc_
\bh_
\bm_
\be_
\bn_
\bt _
\bM_
\be_
\bn_
\bu
3395 The default binding for view-attachments is `v', which displays the attachment
3396 menu for a message. The attachment menu displays a list of the attachments in
3398 The Mutt Next Generation E-Mail Client 68
3400 a message. From the attachment menu, you can save, print, pipe, delete, and
3401 view attachments. You can apply these operations to a group of attachments at
3402 once, by tagging the attachments and by using the ``tag-prefix'' operator. You
3403 can also reply to the current message from this menu, and only the current
3404 attachment (or the attachments tagged) will be quoted in your reply. You can
3405 view attachments as text, or view them using the mailcap viewer definition.
3407 Finally, you can apply the usual message-related functions (like _
\br_
\be_
\bs_
\be_
\bn_
\bd_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be
3408 (section 2.5.4 , page 13), and the reply and forward functions) to attachments
3409 of type message/rfc822.
3411 See the help on the attachment menu for more information.
3413 _
\b5_
\b._
\b1_
\b._
\b3 _
\bT_
\bh_
\be _
\bC_
\bo_
\bm_
\bp_
\bo_
\bs_
\be _
\bM_
\be_
\bn_
\bu
3415 The compose menu is the menu you see before you send a message. It allows you
3416 to edit the recipient list, the subject, and other aspects of your message. It
3417 also contains a list of the attachments of your message, including the main
3418 body. From this menu, you can print, copy, filter, pipe, edit, compose,
3419 review, and rename an attachment or a list of tagged attachments. You can also
3420 modifying the attachment information, notably the type, encoding and descrip-
3423 Attachments appear as follows:
3425 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
3426 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
3428 The '-' denotes that Mutt-ng will delete the file after sending (or postponing,
3429 or canceling) the message. It can be toggled with the toggle-unlink command
3430 (default: u). The next field is the MIME content-type, and can be changed with
3431 the edit-type command (default: ^T). The next field is the encoding for the
3432 attachment, which allows a binary message to be encoded for transmission on
3433 7bit links. It can be changed with the edit-encoding command (default: ^E).
3434 The next field is the size of the attachment, rounded to kilobytes or
3435 megabytes. The next field is the filename, which can be changed with the
3436 rename-file command (default: R). The final field is the description of the
3437 attachment, and can be changed with the edit-description command (default: d).
3439 _
\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
3441 When you add an attachment to your mail message, Mutt-ng searches your personal
3442 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
3443 /usr/local/share/mutt/mime.types or /etc/mime.types
3445 The mime.types file consist of lines containing a MIME type and a space sepa-
3446 rated list of extensions. For example:
3448 application/postscript ps eps
3450 audio/x-aiff aif aifc aiff
3452 The Mutt Next Generation E-Mail Client 69
3454 A sample mime.types file comes with the Mutt-ng distribution, and should con-
3455 tain most of the MIME types you are likely to use.
3457 If Mutt-ng can not determine the mime type by the extension of the file you
3458 attach, it will look at the file. If the file is free of binary information,
3459 Mutt-ng will assume that the file is plain text, and mark it as text/plain. If
3460 the file contains binary information, then Mutt-ng will mark it as applica-
3461 tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an
3462 attachment by using the edit-type command from the compose menu (default: ^T).
3463 The MIME type is actually a major mime type followed by the sub-type, separated
3464 by a '/'. 6 major types: application, text, image, video, audio, and model have
3465 been approved after various internet discussions. Mutt-ng recognises all of
3466 these if the appropriate entry is found in the mime.types file. It also recog-
3467 nises other major mime types, such as the chemical type that is widely used in
3468 the molecular modelling community to pass molecular data in various forms to
3469 various molecular viewers. Non-recognised mime types should only be used if the
3470 recipient of the message is likely to be expecting such attachments.
3472 _
\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
3474 Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific
3475 format specified in Appendix A of RFC 1524. This file format is commonly
3476 referred to as the mailcap format. Many MIME compliant programs utilize the
3477 mailcap format, allowing you to specify handling for all MIME types in one
3478 place for all programs. Programs known to use this format include Netscape,
3479 XMosaic, lynx and metamail.
3481 In order to handle various MIME types that Mutt-ng can not handle internally,
3482 Mutt-ng parses a series of external configuration files to find an external
3483 handler. The default search string for these files is a colon delimited list
3486 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
3488 where $HOME is your home directory.
3490 In particular, the metamail distribution will install a mailcap file, usually
3491 as /usr/local/etc/mailcap, which contains some baseline entries.
3493 _
\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
3495 A mailcap file consists of a series of lines which are comments, blank, or def-
3498 A comment line consists of a # character followed by anything you want.
3500 A blank line is blank.
3502 A definition line consists of a content type, a view command, and any number of
3503 optional fields. Each field of a definition line is divided by a semicolon ';'
3506 The Mutt Next Generation E-Mail Client 70
3508 The content type is specified in the MIME standard type/subtype method. For
3509 example, text/plain, text/html, image/gif, etc. In addition, the mailcap for-
3510 mat includes two formats for wildcards, one using the special '*' subtype, the
3511 other is the implicit wild, where you only include the major type. For exam-
3512 ple, image/*, or video, will match all image types and video types, respec-
3515 The view command is a Unix command for viewing the type specified. There are
3516 two different types of commands supported. The default is to send the body of
3517 the MIME message to the command on stdin. You can change this behavior by using
3518 %s as a parameter to your view command. This will cause Mutt-ng to save the
3519 body of the MIME message to a temporary file, and then call the view command
3520 with the %s replaced by the name of the temporary file. In both cases, Mutt-ng
3521 will turn over the terminal to the view program until the program quits, at
3522 which time Mutt will remove the temporary file if it exists.
3524 So, in the simplest form, you can send a text/plain message to the external
3525 pager more on stdin:
3529 Or, you could send the message as a file:
3533 Perhaps you would like to use lynx to interactively view a text/html message:
3537 In this case, lynx does not support viewing a file from stdin, so you must use
3538 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
3539 _
\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
3540 _
\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
3541 _
\bv_
\bi_
\be_
\bw _
\bt_
\bh_
\be _
\bo_
\bb_
\bj_
\be_
\bc_
\bt_
\b.
3543 On the other hand, maybe you don't want to use lynx interactively, you just
3544 want to have it convert the text/html to text/plain, then you can use:
3546 text/html; lynx -dump %s | more
3548 Perhaps you wish to use lynx to view text/html files, and a pager on all other
3549 text formats, then you would use the following:
3554 This is the simplest form of a mailcap file.
3556 The Mutt Next Generation E-Mail Client 71
3558 _
\b5_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\bc_
\bu_
\br_
\be _
\bu_
\bs_
\be _
\bo_
\bf _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp
3560 The interpretation of shell meta-characters embedded in MIME parameters can
3561 lead to security problems in general. Mutt-ng tries to quote parameters in
3562 expansion of %s syntaxes properly, and avoids risky characters by substituting
3563 them, see the _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be (section 6.4.117 , page 109) variable.
3565 Although mutt's procedures to invoke programs with mailcap seem to be safe,
3566 there are other applications parsing mailcap, maybe taking less care of it.
3567 Therefore you should pay attention to the following rules:
3569 _
\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
3570 double quotes. Mutt-ng does this for you, the right way, as should any other
3571 program which interprets mailcap. Don't put them into backtick expansions. Be
3572 highly careful with eval statements, and avoid them if possible at all. Trying
3573 to fix broken behaviour with quotes introduces new leaks - there is no alterna-
3574 tive to correct quoting in the first place.
3576 If you have to use the %-expandos' values in context where you need quoting or
3577 backtick expansions, put that value into a shell variable and reference the
3578 shell variable where necessary, as in the following example (using $charset
3579 inside the backtick expansion is safe, since it is not itself subject to any
3582 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3583 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3585 _
\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
3587 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b1 _
\bO_
\bp_
\bt_
\bi_
\bo_
\bn_
\ba_
\bl _
\bF_
\bi_
\be_
\bl_
\bd_
\bs
3589 In addition to the required content-type and view command fields, you can add
3590 semi-colon ';' separated fields to set flags and other options. Mutt-ng recog-
3591 nizes the following optional fields:
3594 This flag tells Mutt-ng that the command passes possibly large
3595 amounts of text on stdout. This causes Mutt-ng to invoke a pager
3596 (either the internal pager or the external pager defined by the
3597 pager variable) on the output of the view command. Without this
3598 flag, Mutt-ng assumes that the command is interactive. One could
3599 use this to replace the pipe to more in the lynx -dump example in
3602 text/html; lynx -dump %s ; copiousoutput
3604 This will cause lynx to format the text/html output as text/plain
3605 and Mutt-ng will use your standard pager to display the results.
3608 Mutt-ng uses this flag when viewing attachments with _
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3610 The Mutt Next Generation E-Mail Client 72
3612 (section 5.4 , page 74), in order to decide whether it should
3613 honor the setting of the _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 6.4.334 , page 161)
3614 variable or not. When an attachment is viewed using an interactive
3615 program, and the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl
3616 flag, Mutt-ng will use _
\b$_
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by (section 6.4.334 , page 161) and
3617 the exit status of the program to decide if it will ask you to
3618 press a key after the external program has exited. In all other
3619 situations it will not prompt you for a key.
3622 This flag specifies the command to use to create a new attachment
3623 of a specific MIME type. Mutt-ng supports this from the compose
3626 composetyped=<command>
3627 This flag specifies the command to use to create a new attachment
3628 of a specific MIME type. This command differs from the compose
3629 command in that mutt will expect standard MIME headers on the data.
3630 This can be used to specify parameters, filename, description, etc.
3631 for a new attachment. Mutt-ng supports this from the compose
3635 This flag specifies the command to use to print a specific MIME
3636 type. Mutt-ng supports this from the attachment and compose menus.
3639 This flag specifies the command to use to edit a specific MIME
3640 type. Mutt-ng supports this from the compose menu, and also uses
3641 it to compose new attachments. Mutt-ng will default to the defined
3642 editor for text attachments.
3644 nametemplate=<template>
3645 This field specifies the format for the file denoted by %s in the
3646 command fields. Certain programs will require a certain file
3647 extension, for instance, to correctly view a file. For instance,
3648 lynx will only interpret a file as text/html if the file ends in
3649 .html. So, you would specify lynx as a text/html viewer with a
3650 line in the mailcap file like:
3652 text/html; lynx %s; nametemplate=%s.html
3655 This field specifies a command to run to test whether this mailcap
3656 entry should be used. The command is defined with the command
3657 expansion rules defined in the next section. If the command
3658 returns 0, then the test passed, and Mutt-ng uses this entry. If
3659 the command returns non-zero, then the test failed, and Mutt-ng
3660 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
3661 _
\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:
3663 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3666 The Mutt Next Generation E-Mail Client 73
3668 In this example, Mutt-ng will run the program RunningX which will
3669 return 0 if the X Window manager is running, and non-zero if it
3670 isn't. If RunningX returns 0, then Mutt-ng will call netscape to
3671 display the text/html object. If RunningX doesn't return 0, then
3672 Mutt-ng will go on to the next entry and use lynx to display the
3675 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b2 _
\bS_
\be_
\ba_
\br_
\bc_
\bh _
\bO_
\br_
\bd_
\be_
\br
3677 When searching for an entry in the mailcap file, Mutt-ng will search for the
3678 most useful entry for its purpose. For instance, if you are attempting to
3679 print an image/gif, and you have the following entries in your mailcap file,
3680 Mutt-ng will search for an entry with the print command:
3683 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3686 Mutt-ng will skip the image/* entry and use the image/gif entry with the print
3689 In addition, you can use this with _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 74) to denote
3690 two commands for viewing an attachment, one to be viewed automatically, the
3691 other to be viewed interactively from the attachment menu. In addition, you
3692 can then use the test feature to determine which viewer to use interactively
3693 depending on your environment.
3695 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3696 text/html; lynx %s; nametemplate=%s.html
3697 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3699 For _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw (section 5.4 , page 74), Mutt-ng will choose the third entry
3700 because of the copiousoutput tag. For interactive viewing, Mutt will run the
3701 program RunningX to determine if it should use the first entry. If the program
3702 returns non-zero, Mutt-ng will use the second entry for interactive viewing.
3704 _
\b5_
\b._
\b3_
\b._
\b3_
\b._
\b3 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bE_
\bx_
\bp_
\ba_
\bn_
\bs_
\bi_
\bo_
\bn
3706 The various commands defined in the mailcap files are passed to the /bin/sh
3707 shell using the system() function. Before the command is passed to /bin/sh -c,
3708 it is parsed to expand various special parameters with information from Mutt-
3709 ng. The keywords Mutt-ng expands are:
3712 As seen in the basic mailcap section, this variable is expanded to
3713 a filename specified by the calling program. This file contains
3714 the body of the message to view/print/edit or where the composing
3715 program should place the results of composition. In addition, the
3716 use of this keyword causes Mutt-ng to not pass the body of the mes-
3717 sage to the view/print/edit program on stdin.
3719 The Mutt Next Generation E-Mail Client 74
3722 Mutt-ng will expand %t to the text representation of the content
3723 type of the message in the same form as the first parameter of the
3724 mailcap definition line, ie text/html or image/gif.
3727 Mutt-ng will expand this to the value of the specified parameter
3728 from the Content-Type: line of the mail message. For instance, if
3729 Your mail message contains:
3731 Content-Type: text/plain; charset=iso-8859-1
3733 then Mutt-ng will expand %{charset} to iso-8859-1. The default
3734 metamail mailcap file uses this feature to test the charset to
3735 spawn an xterm using the right charset to view the message.
3738 This will be replaced by a %
3740 Mutt-ng does not currently support the %F and %n keywords specified in RFC
3741 1524. The main purpose of these parameters is for multipart messages, which is
3742 handled internally by Mutt-ng.
3744 _
\b5_
\b._
\b3_
\b._
\b4 _
\bE_
\bx_
\ba_
\bm_
\bp_
\bl_
\be _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp _
\bf_
\bi_
\bl_
\be_
\bs
3746 This mailcap file is fairly simple and standard:
3748 # I'm always running X :)
3749 video/*; xanim %s > /dev/null
3750 image/*; xv %s > /dev/null
3752 # I'm always running netscape (if my computer had more memory, maybe)
3753 text/html; netscape -remote 'openURL(%s)'
3755 This mailcap file shows quite a number of examples:
3757 The Mutt Next Generation E-Mail Client 75
3759 # Use xanim to view all videos Xanim produces a header on startup,
3760 # send that to /dev/null so I don't see it
3761 video/*; xanim %s > /dev/null
3763 # Send html to a running netscape by remote
3764 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3766 # If I'm not running netscape but I am running X, start netscape on the
3768 text/html; netscape %s; test=RunningX
3770 # Else use lynx to view it as text
3773 # This version would convert the text/html to text/plain
3774 text/html; lynx -dump %s; copiousoutput
3776 # I use enscript to print text in two columns to a page
3777 text/*; more %s; print=enscript -2Gr %s
3779 # Netscape adds a flag to tell itself to view jpegs internally
3780 image/jpeg;xv %s; x-mozilla-flags=internal
3782 # Use xv to view images if I'm running X
3783 # In addition, this uses the \ to extend the line and set my editor
3785 image/*;xv %s; test=RunningX; \
3788 # Convert images to text using the netpbm tools
3789 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3790 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3792 # Send excel spreadsheets to my NT box
3793 application/ms-excel; open.pl %s
3795 _
\b5_
\b._
\b4 _
\bM_
\bI_
\bM_
\bE _
\bA_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
3797 In addition to explicitly telling Mutt-ng to view an attachment with the MIME
3798 viewer defined in the mailcap file, Mutt-ng has support for automatically view-
3799 ing MIME attachments while in the pager.
3801 To work, you must define a viewer in the mailcap file which uses the copi-
3802 ousoutput option to denote that it is non-interactive. Usually, you also use
3803 the entry to convert the attachment to a text representation which you can view
3806 You then use the auto_view muttrc command to list the content-types that you
3807 wish to view automatically.
3809 For instance, if you set auto_view to:
3811 The Mutt Next Generation E-Mail Client 76
3813 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3815 Mutt-ng could use the following mailcap entries to automatically view attach-
3816 ments of these types.
3818 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3819 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3820 application/x-gunzip; gzcat; copiousoutput
3821 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3822 application/postscript; ps2ascii %s; copiousoutput
3824 ``unauto_view'' can be used to remove previous entries from the autoview list.
3825 This can be used with message-hook to autoview messages based on size, etc.
3826 ``unauto_view *'' will remove all previous entries.
3828 _
\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
3830 Mutt-ng has some heuristics for determining which attachment of a multi-
3831 part/alternative type to display. First, mutt will check the alternative_order
3832 list to determine if one of the available types is preferred. The alterna-
3833 tive_order list consists of a number of MIME types in order, including support
3834 for implicit and explicit wildcards, for example:
3836 alternative_order text/enriched text/plain text application/postscript image/*
3838 Next, mutt will check if any of the types have a defined _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section
3839 5.4 , page 74), and use that. Failing that, Mutt-ng will look for any text
3840 type. As a last attempt, mutt will look for any type it knows how to handle.
3842 To remove a MIME type from the alternative_order list, use the unalterna-
3845 _
\b5_
\b._
\b6 _
\bM_
\bI_
\bM_
\bE _
\bL_
\bo_
\bo_
\bk_
\bu_
\bp
3847 Mutt-ng's mime_lookup list specifies a list of mime-types that should not be
3848 treated according to their mailcap entry. This option is designed to deal with
3849 binary types such as application/octet-stream. When an attachment's mime-type
3850 is listed in mime_lookup, then the extension of the filename will be compared
3851 to the list of extensions in the mime.types file. The mime-type associated
3852 with this extension will then be used to process the attachment according to
3853 the rules in the mailcap file and according to any other configuration options
3854 (such as auto_view) specified. Common usage would be:
3856 mime_lookup application/octet-stream application/X-Lotus-Manuscript
3858 In addition, the unmime_lookup command may be used to disable this feature for
3860 The Mutt Next Generation E-Mail Client 77
3862 any particular mime-type if it had been set, for example, in a global muttrc.
3864 _
\b6_
\b. _
\bR_
\be_
\bf_
\be_
\br_
\be_
\bn_
\bc_
\be
3866 _
\b6_
\b._
\b1 _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd _
\bl_
\bi_
\bn_
\be _
\bo_
\bp_
\bt_
\bi_
\bo_
\bn_
\bs
3868 Running mutt with no arguments will make Mutt-ng attempt to read your spool
3869 mailbox. However, it is possible to read other mailboxes and to send messages
3870 from the command line as well.
3873 -a attach a file to a message
3874 -b specify a blind carbon-copy (BCC) address
3875 -c specify a carbon-copy (Cc) address
3876 -D print the value of all variables on stdout
3877 -e specify a config command to be run after initialization files are read
3878 -f specify a mailbox to load
3879 -F specify an alternate file to read initialization commands
3880 -h print help on command line options
3881 -H specify a draft file from which to read a header and body
3882 -i specify a file to include in a message composition
3883 -m specify a default mailbox type
3884 -n do not read the system Muttngrc
3885 -p recall a postponed message
3886 -Q query a configuration variable
3887 -R open mailbox in read-only mode
3888 -s specify a subject (enclose in quotes if it contains spaces)
3889 -v show version number and compile-time definitions
3890 -x simulate the mailx(1) compose mode
3891 -y show a menu containing the files specified by the mailboxes command
3892 -z exit immediately if there are no messages in the mailbox
3893 -Z open the first folder with new message,exit immediately if none
3895 To read messages in a mailbox
3897 mutt [ -nz ] [ -F _
\bm_
\bu_
\bt_
\bt_
\br_
\bc ] [ -m _
\bt_
\by_
\bp_
\be ] [ -f _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx ]
3899 To compose a new message
3901 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-
3902 _
\bj_
\be_
\bc_
\bt ] _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs [ _
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs ... ]
3904 Mutt-ng also supports a ``batch'' mode to send prepared messages. Simply redi-
3905 rect input from the file you wish to send. For example,
3907 mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat
3909 The Mutt Next Generation E-Mail Client 78
3911 This command will send a message to ``professor@bigschool.edu'' with a subject
3912 of ``data set for run #2''. In the body of the message will be the contents of
3913 the file ``~/run2.dat''.
3915 _
\b6_
\b._
\b2 _
\bP_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs
3918 ~b EXPR messages which contain EXPR in the message body
3919 ~B EXPR messages which contain EXPR in the whole message
3920 ~c USER messages carbon-copied to USER
3921 ~C EXPR message is either to: or cc: EXPR
3923 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
3925 ~e EXPR message which contains EXPR in the ``Sender'' field
3927 ~f USER messages originating from USER
3928 ~g cryptographically signed messages
3929 ~G cryptographically encrypted messages
3930 ~H EXPR messages with a spam attribute matching EXPR
3931 ~h EXPR messages which contain EXPR in the message header
3932 ~k message contains PGP key material
3933 ~i ID message which match ID in the ``Message-ID'' field
3934 ~L EXPR message is either originated or received by EXPR
3935 ~l message is addressed to a known mailing list
3936 ~m [MIN]-[MAX] message in the range MIN to MAX *)
3937 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
3940 ~p message is addressed to you (consults alternates)
3941 ~P message is from you (consults alternates)
3942 ~Q messages which have been replied to
3944 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
3945 ~S superseded messages
3946 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
3948 ~t USER messages addressed to USER
3950 ~v message is part of a collapsed thread.
3951 ~V cryptographically verified messages
3952 ~w EXPR messages which contain EXPR in the `Newsgroups' field
3953 (if compiled with NNTP support)
3954 ~x EXPR messages which contain EXPR in the `References' field
3955 ~y EXPR messages which contain EXPR in the `X-Label' field
3956 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
3957 ~= duplicated messages (see $duplicate_threads)
3958 ~$ unreferenced messages (requires threaded view)
3959 ~* ``From'' contains realname and (syntactically) valid
3960 address (excluded are addresses matching against
3961 alternates or any alias)
3963 The Mutt Next Generation E-Mail Client 79
3965 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
3966 44). Special attention has to be made when using regular expressions inside of
3967 patterns. Specifically, Mutt-ng's parser for these patterns will strip one
3968 level of backslash (\), which is normally used for quoting. If it is your
3969 intention to use a backslash in the regular expression, you will need to use
3970 two backslashes instead (\\).
3972 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
3974 _
\b6_
\b._
\b3 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bC_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd_
\bs
3976 The following are the commands understood by mutt.
3978 +
\bo _
\ba_
\bc_
\bc_
\bo_
\bu_
\bn_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.17 , page 63) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3980 +
\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, ... ]
3982 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bi_
\ba_
\bs (section 3.3 , page 23) [ * | _
\bk_
\be_
\by ... ]
3984 +
\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 ... ]
3986 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\be_
\bs (section 3.10 , page 30) [ * | _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
3988 +
\bo _
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
3990 +
\bo _
\bu_
\bn_
\ba_
\bl_
\bt_
\be_
\br_
\bn_
\ba_
\bt_
\bi_
\bv_
\be_
\b__
\bo_
\br_
\bd_
\be_
\br (section 5.5 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
3992 +
\bo _
\ba_
\bp_
\bp_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.3 , page 65) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
3994 +
\bo _
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 74) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
3996 +
\bo _
\bu_
\bn_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page 74) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
3998 +
\bo _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) _
\bm_
\ba_
\bp _
\bk_
\be_
\by _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn
4000 +
\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
4002 +
\bo _
\bc_
\bl_
\bo_
\bs_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.2 , page 65) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4004 +
\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 ]
4006 +
\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 ... ]
4008 +
\bo _
\be_
\bx_
\be_
\bc (section 3.24 , page 37) _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn [ _
\bf_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn ... ]
4010 +
\bo _
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 35) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4012 +
\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
4014 +
\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
4016 The Mutt Next Generation E-Mail Client 80
4018 +
\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 ... ]
4020 +
\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 ... ]
4022 +
\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
4024 +
\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 ... ]
4026 +
\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 ... ]
4028 +
\bo _
\bl_
\bi_
\bs_
\bt_
\bs (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4030 +
\bo _
\bu_
\bn_
\bl_
\bi_
\bs_
\bt_
\bs (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4032 +
\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 ]
4034 +
\bo _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.14 , page 33) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be [ _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be ... ]
4036 +
\bo _
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx
4038 +
\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
4040 +
\bo _
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4042 +
\bo _
\bu_
\bn_
\bm_
\bi_
\bm_
\be_
\b__
\bl_
\bo_
\bo_
\bk_
\bu_
\bp (section 5.6 , page 75) _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be [ _
\bm_
\bi_
\bm_
\be_
\bt_
\by_
\bp_
\be ... ]
4044 +
\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 ]
4046 +
\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 ... ]
4048 +
\bo _
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4050 +
\bo _
\bu_
\bn_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34) _
\bf_
\bi_
\be_
\bl_
\bd [ _
\bf_
\bi_
\be_
\bl_
\bd ... ]
4052 +
\bo _
\bo_
\bp_
\be_
\bn_
\b-_
\bh_
\bo_
\bo_
\bk (section 4.19.1 , page 64) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4054 +
\bo _
\bc_
\br_
\by_
\bp_
\bt_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.22 , page 37) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bk_
\be_
\by_
\b-_
\bi_
\bd
4056 +
\bo _
\bp_
\bu_
\bs_
\bh (section 3.23 , page 37) _
\bs_
\bt_
\br_
\bi_
\bn_
\bg
4058 +
\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 ... ]
4060 +
\bo _
\bs_
\ba_
\bv_
\be_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.17 , page 35) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4062 +
\bo _
\bs_
\bc_
\bo_
\br_
\be (section 3.25 , page 38) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bv_
\ba_
\bl_
\bu_
\be
4064 +
\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 ... ]
4066 +
\bo _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.20 , page 36) _
\br_
\be_
\bg_
\be_
\bx_
\bp _
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
4068 +
\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
4070 +
\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 ... ]
4072 The Mutt Next Generation E-Mail Client 81
4074 +
\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 ... ]
4076 +
\bo _
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page 42) _
\bf_
\bi_
\bl_
\be_
\bn_
\ba_
\bm_
\be
4078 +
\bo _
\bs_
\bp_
\ba_
\bm (section 3.26 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn _
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4080 +
\bo _
\bn_
\bo_
\bs_
\bp_
\ba_
\bm (section 3.26 , page 39) _
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn
4082 +
\bo _
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4084 +
\bo _
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be (section 3.12 , page 32) _
\br_
\be_
\bg_
\be_
\bx_
\bp [ _
\br_
\be_
\bg_
\be_
\bx_
\bp ... ]
4086 +
\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 ... ]
4088 +
\bo _
\bu_
\bn_
\bh_
\bo_
\bo_
\bk (section 3.29 , page 42) _
\bh_
\bo_
\bo_
\bk_
\b-_
\bt_
\by_
\bp_
\be
4090 _
\b6_
\b._
\b4 _
\bC_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn _
\bv_
\ba_
\br_
\bi_
\ba_
\bb_
\bl_
\be_
\bs
4092 _
\b6_
\b._
\b4_
\b._
\b1 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bn_
\bo_
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
4098 If set to _
\by_
\be_
\bs, when composing messages and no subject is given at the subject
4099 prompt, composition will be aborted. If set to _
\bn_
\bo, composing messages with no
4100 subject given at the subject prompt will never be aborted.
4102 _
\b6_
\b._
\b4_
\b._
\b2 _
\ba_
\bb_
\bo_
\br_
\bt_
\b__
\bu_
\bn_
\bm_
\bo_
\bd_
\bi_
\bf_
\bi_
\be_
\bd
4108 If set to _
\by_
\be_
\bs, composition will automatically abort after editing the message
4109 body if no changes are made to the file (this check only happens after the
4110 _
\bf_
\bi_
\br_
\bs_
\bt edit of the file). When set to _
\bn_
\bo, composition will never be aborted.
4112 _
\b6_
\b._
\b4_
\b._
\b3 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bi_
\bl_
\be
4116 Default: '~/.muttngrc'
4118 The default file in which to save aliases created by the ``_
\bc_
\br_
\be_
\ba_
\bt_
\be_
\b-_
\ba_
\bl_
\bi_
\ba_
\bs (sec-
4119 tion 2.5.4 , page 11)'' function.
4121 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will not automatically source this file; you must explicitly use
4122 the ``_
\bs_
\bo_
\bu_
\br_
\bc_
\be (section 3.28 , page 42)'' command for it to be executed.
4124 _
\b6_
\b._
\b4_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4128 The Mutt Next Generation E-Mail Client 82
4130 Default: '%4n %2f %t %-10a %r'
4132 Specifies the format of the data displayed for the ``alias'' menu. The follow-
4133 ing printf(3)-style sequences are available:
4139 flags - currently, a 'd' for an alias marked for deletion
4145 address which alias expands to
4148 character which indicates if the alias is tagged for inclusion
4150 _
\b6_
\b._
\b4_
\b._
\b5 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\b8_
\bb_
\bi_
\bt
4156 Controls whether 8-bit data is converted to 7-bit using either quoted-printable
4157 or base64 encoding when sending mail.
4159 _
\b6_
\b._
\b4_
\b._
\b6 _
\ba_
\bl_
\bl_
\bo_
\bw_
\b__
\ba_
\bn_
\bs_
\bi
4165 Controls whether ANSI color codes in messages (and color tags in rich text mes-
4166 sages) are to be interpreted. Messages containing these codes are rare, but if
4167 this option is set, their text will be colored accordingly. Note that this may
4168 override your color choices, and even present a security problem, since a mes-
4169 sage could include a line like ``[-- PGP output follows ...' and give it the
4170 same color as your attachment color.
4172 _
\b6_
\b._
\b4_
\b._
\b7 _
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bc_
\bu_
\br_
\bs_
\bo_
\br
4178 When _
\bs_
\be_
\bt, an arrow (``->'') will be used to indicate the current entry in menus
4179 instead of highlighting the whole line. On slow network or modem links this
4180 will make response faster because there is less that has to be redrawn on the
4181 screen when moving to the next or previous entries in the menu.
4183 The Mutt Next Generation E-Mail Client 83
4185 _
\b6_
\b._
\b4_
\b._
\b8 _
\ba_
\bs_
\bc_
\bi_
\bi_
\b__
\bc_
\bh_
\ba_
\br_
\bs
4191 If _
\bs_
\be_
\bt, Mutt-ng will use plain ASCII characters when displaying thread and
4192 attachment trees, instead of the default ACS characters.
4194 _
\b6_
\b._
\b4_
\b._
\b9 _
\ba_
\bs_
\bk_
\bb_
\bc_
\bc
4200 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before
4201 editing an outgoing message.
4203 _
\b6_
\b._
\b4_
\b._
\b1_
\b0 _
\ba_
\bs_
\bk_
\bc_
\bc
4209 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing
4210 the body of an outgoing message.
4212 _
\b6_
\b._
\b4_
\b._
\b1_
\b1 _
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4218 This variable is a colon-separated list of character encoding schemes for mes-
4219 sages without character encoding indication. Header field values and message
4220 body content without character encoding indication would be assumed that they
4221 are written in one of this list. By default, all the header fields and message
4222 body without any charset indication are assumed to be in us-ascii.
4224 For example, Japanese users might prefer this:
4226 set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4228 However, only the first content is valid for the message body. This variable
4229 is valid only if _
\b$_
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be (section 6.4.310 , page 156) is unset.
4231 _
\b6_
\b._
\b4_
\b._
\b1_
\b2 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4235 Default: '%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] '
4237 This variable describes the format of the ``attachment'' menu. The following
4238 printf(3)-style sequences are understood:
4240 The Mutt Next Generation E-Mail Client 84
4246 requires charset conversion (n or c)
4255 MIME Content-Transfer-Encoding: header field
4261 MIME Content-Disposition: header field (I=inline, A=attachment)
4279 graphic tree characters
4282 unlink (=to delete) flag
4285 right justify the rest of the string and pad with character 'X'
4288 pad to the end of the line with character 'X'
4290 _
\b6_
\b._
\b4_
\b._
\b1_
\b3 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp
4296 The Mutt Next Generation E-Mail Client 85
4298 The separator to add between attachments when operating (saving, printing, pip-
4299 ing, etc) on a list of tagged attachments.
4301 _
\b6_
\b._
\b4_
\b._
\b1_
\b4 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
4307 If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when operating (saving, printing, piping, etc) on a
4308 list of tagged attachments, Mutt-ng will concatenate the attachments and will
4309 operate on them as a single attachment. The ``_
\b$_
\ba_
\bt_
\bt_
\ba_
\bc_
\bh_
\b__
\bs_
\be_
\bp (section 6.4.13 ,
4310 page 83)'' separator is added after each attachment. When _
\bs_
\be_
\bt, Mutt-ng will
4311 operate on the attachments one by one.
4313 _
\b6_
\b._
\b4_
\b._
\b1_
\b5 _
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn
4317 Default: 'On %d, %n wrote:'
4319 This is the string that will precede a message which has been included in a
4320 reply. For a full listing of defined printf(3)-like sequences see the section
4321 on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105)''.
4323 _
\b6_
\b._
\b4_
\b._
\b1_
\b6 _
\ba_
\bu_
\bt_
\bo_
\b__
\bt_
\ba_
\bg
4329 When _
\bs_
\be_
\bt, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be applied to
4330 all tagged messages (if there are any). When unset, you must first use the
4331 ``tag-prefix'' function (default: ';') to make the next function apply to all
4334 _
\b6_
\b._
\b4_
\b._
\b1_
\b7 _
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt
4340 When _
\bs_
\be_
\bt along with ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 6.4.54 , page 92)'', Mutt-ng will
4341 skip the initial send-menu and allow you to immediately begin editing the body
4342 of your message. The send-menu may still be accessed once you have finished
4343 editing the body of your message.
4345 Also see ``_
\b$_
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by (section 6.4.60 , page 93)''.
4347 _
\b6_
\b._
\b4_
\b._
\b1_
\b8 _
\bb_
\be_
\be_
\bp
4353 The Mutt Next Generation E-Mail Client 86
4355 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep when an error occurs.
4357 _
\b6_
\b._
\b4_
\b._
\b1_
\b9 _
\bb_
\be_
\be_
\bp_
\b__
\bn_
\be_
\bw
4363 When this variable is _
\bs_
\be_
\bt, Mutt-ng will beep whenever it prints a message noti-
4364 fying you of new mail. This is independent of the setting of the ``_
\b$_
\bb_
\be_
\be_
\bp (sec-
4365 tion 6.4.18 , page 84)'' variable.
4367 _
\b6_
\b._
\b4_
\b._
\b2_
\b0 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be
4373 Controls whether you will be asked to confirm bouncing messages. If set to _
\by_
\be_
\bs
4374 you don't get asked if you want to bounce a message. Setting this variable to
4375 _
\bn_
\bo is not generally useful, and thus not recommended, because you are unable to
4378 _
\b6_
\b._
\b4_
\b._
\b2_
\b1 _
\bb_
\bo_
\bu_
\bn_
\bc_
\be_
\b__
\bd_
\be_
\bl_
\bi_
\bv_
\be_
\br_
\be_
\bd
4384 When this variable is _
\bs_
\be_
\bt, Mutt-ng will include Delivered-To: header fields
4385 when bouncing messages. Postfix users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this variable.
4387 _
\b6_
\b._
\b4_
\b._
\b2_
\b2 _
\bb_
\br_
\ba_
\bi_
\bl_
\bl_
\be_
\b__
\bf_
\br_
\bi_
\be_
\bn_
\bd_
\bl_
\by
4393 When this variable is set, mutt will place the cursor at the beginning of the
4394 current line in menus, even when the arrow_cursor variable is unset, making it
4395 easier for blind persons using Braille displays to follow these menus. The
4396 option is disabled by default because many visual terminals don't permit making
4397 the cursor invisible.
4399 _
\b6_
\b._
\b4_
\b._
\b2_
\b3 _
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bf_
\bi_
\bl_
\be
4403 Default: '~/.mutt_certificates'
4405 Availability: SSL or GNUTLS
4407 This variable specifies the file where the certificates you trust are saved.
4408 When an unknown certificate is encountered, you are asked if you accept it or
4410 The Mutt Next Generation E-Mail Client 87
4412 not. If you accept it, the certificate can also be saved in this file and fur-
4413 ther connections are automatically accepted.
4415 You can also manually add CA certificates in this file. Any server certificate
4416 that is signed with one of these CA certificates are also automatically
4419 Example: set certificate_file=~/.muttng/certificates
4421 _
\b6_
\b._
\b4_
\b._
\b2_
\b4 _
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4427 Character set your terminal uses to display and enter textual data.
4429 _
\b6_
\b._
\b4_
\b._
\b2_
\b5 _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw
4435 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
4437 When _
\bs_
\be_
\bt, Mutt-ng will check for new mail delivered while the mailbox is open.
4438 Especially with MH mailboxes, this operation can take quite some time since it
4439 involves scanning the directory and checking each file to see if it has already
4440 been looked at. If it's _
\bu_
\bn_
\bs_
\be_
\bt, no check for new mail is performed while the
4443 _
\b6_
\b._
\b4_
\b._
\b2_
\b6 _
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
4449 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not collapse a thread if it contains any unread mes-
4452 _
\b6_
\b._
\b4_
\b._
\b2_
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4456 Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-'
4458 Controls the format of the status line displayed in the ``compose'' menu. This
4459 string is similar to ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.307 , page 154)'', but has
4460 its own set of printf(3)-like sequences:
4463 total number of attachments
4465 The Mutt Next Generation E-Mail Client 88
4471 approximate size (in bytes) of the current message
4474 Mutt-ng version string
4476 See the text describing the ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.307 , page 154)''
4477 option for more information on how to set ``_
\b$_
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.27 ,
4480 _
\b6_
\b._
\b4_
\b._
\b2_
\b8 _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4486 When defined, Mutt-ng will recode commands in rc files from this encoding.
4488 _
\b6_
\b._
\b4_
\b._
\b2_
\b9 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\ba_
\bp_
\bp_
\be_
\bn_
\bd
4494 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when appending messages to an
4497 _
\b6_
\b._
\b4_
\b._
\b3_
\b0 _
\bc_
\bo_
\bn_
\bf_
\bi_
\br_
\bm_
\bc_
\br_
\be_
\ba_
\bt_
\be
4503 When _
\bs_
\be_
\bt, Mutt-ng will prompt for confirmation when saving messages to a mail-
4504 box which does not yet exist before creating it.
4506 _
\b6_
\b._
\b4_
\b._
\b3_
\b1 _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
4512 Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
4513 many seconds if the connection is not able to be established. A negative value
4514 causes Mutt-ng to wait indefinitely for the connection to succeed.
4516 _
\b6_
\b._
\b4_
\b._
\b3_
\b2 _
\bc_
\bo_
\bn_
\bt_
\be_
\bn_
\bt_
\b__
\bt_
\by_
\bp_
\be
4520 Default: 'text/plain'
4522 The Mutt Next Generation E-Mail Client 89
4524 Sets the default Content-Type: header field for the body of newly composed mes-
4527 _
\b6_
\b._
\b4_
\b._
\b3_
\b3 _
\bc_
\bo_
\bp_
\by
4533 This variable controls whether or not copies of your outgoing messages will be
4534 saved for later references. Also see ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 6.4.230 , page
4535 136)'', ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.241 , page 138)'', ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
4536 6.4.68 , page 96)'' and ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page 35)''.
4538 _
\b6_
\b._
\b4_
\b._
\b3_
\b4 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4544 Setting this variable will cause Mutt-ng to always attempt to PGP encrypt out-
4545 going messages. This is probably only useful in connection to the _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk
4546 command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when encryption is not
4547 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
4548 6.4.277 , page 147)'' is _
\bs_
\be_
\bt, then OpenSSL is used instead to create S/MIME
4549 messages and settings can be overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto
4552 _
\b6_
\b._
\b4_
\b._
\b3_
\b5 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bp_
\bg_
\bp
4558 This variable controls whether or not Mutt-ng may automatically enable PGP
4559 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
4560 6.4.34 , page 88)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 6.4.38 , page 89)'',
4561 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 6.4.36 , page 88)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4562 6.4.39 , page 89)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 6.4.277 , page 147)''.
4564 _
\b6_
\b._
\b4_
\b._
\b3_
\b6 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn
4570 Setting this variable will cause Mutt-ng to always attempt to cryptographically
4571 sign outgoing messages. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
4572 signing is not required or encryption is requested as well. If
4573 ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 6.4.277 , page 147)'' is _
\bs_
\be_
\bt, then OpenSSL is
4574 used instead to create S/MIME messages and settings can be overridden by use of
4575 the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
4577 The Mutt Next Generation E-Mail Client 90
4579 _
\b6_
\b._
\b4_
\b._
\b3_
\b7 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bm_
\bi_
\bm_
\be
4585 This variable controls whether or not Mutt-ng may automatically enable S/MIME
4586 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
4587 6.4.34 , page 88)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt (section 6.4.38 , page 89)'',
4588 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bs_
\bi_
\bg_
\bn (section 6.4.36 , page 88)'', ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section
4589 6.4.39 , page 89)'' and ``_
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt (section 6.4.277 , page 147)''.
4591 _
\b6_
\b._
\b4_
\b._
\b3_
\b8 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt
4597 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL encrypt replies to messages which are
4598 encrypted. (Crypto only)
4600 _
\b6_
\b._
\b4_
\b._
\b3_
\b9 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn
4606 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are signed.
4608 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed! (Crypto
4611 _
\b6_
\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
4617 If _
\bs_
\be_
\bt, automatically PGP or OpenSSL sign replies to messages which are
4618 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
4619 6.4.38 , page 89)'', because it allows you to sign all messages which are
4620 automatically encrypted. This works around the problem noted in
4621 ``_
\b$_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bs_
\bi_
\bg_
\bn (section 6.4.39 , page 89)'', that Mutt-ng is not able to
4622 find out whether an encrypted message is also signed. (Crypto only)
4624 _
\b6_
\b._
\b4_
\b._
\b4_
\b1 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bt_
\bi_
\bm_
\be_
\bs_
\bt_
\ba_
\bm_
\bp
4630 If _
\bs_
\be_
\bt, Mutt-ng will include a time stamp in the lines surrounding PGP or
4631 S/MIME output, so spoofing such lines is more difficult. If you are using col-
4632 ors to mark these lines, and rely on these, you may _
\bu_
\bn_
\bs_
\be_
\bt this setting.
4634 The Mutt Next Generation E-Mail Client 91
4638 _
\b6_
\b._
\b4_
\b._
\b4_
\b2 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\bm_
\be
4644 This variable controls the use the GPGME enabled crypto backends. If it is _
\bs_
\be_
\bt
4645 and Mutt-ng was build with gpgme support, the gpgme code for S/MIME and PGP
4646 will be used instead of the classic code.
4648 N
\bNo
\bot
\bte
\be: You need to use this option in your .muttngrc configuration file as it
4649 won't have any effect when used interactively.
4651 _
\b6_
\b._
\b4_
\b._
\b4_
\b3 _
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bs_
\bi_
\bg
4657 If ``_
\by_
\be_
\bs'', always attempt to verify PGP or S/MIME signatures. If ``_
\ba_
\bs_
\bk'', ask
4658 whether or not to verify the signature. If ``_
\bn_
\bo'', never attempt to verify
4659 cryptographic signatures. (Crypto only)
4661 _
\b6_
\b._
\b4_
\b._
\b4_
\b4 _
\bd_
\ba_
\bt_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4665 Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z'
4667 This variable controls the format of the date printed by the ``%d'' sequence in
4668 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105)''. This is passed to strftime(3)
4669 to process the date.
4671 Unless the first character in the string is a bang (``!''), the month and week
4672 day names are expanded according to the locale specified in the variable
4673 ``_
\b$_
\bl_
\bo_
\bc_
\ba_
\bl_
\be (section 6.4.114 , page 108)''. If the first character in the string
4674 is a bang, the bang is discarded, and the month and week day names in the rest
4675 of the string are expanded in the _
\bC locale (that is in US English).
4677 _
\b6_
\b._
\b4_
\b._
\b4_
\b5 _
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bh_
\bo_
\bo_
\bk
4681 Default: '~f %s !~P | (~P ~C %s)'
4683 This variable controls how send-hooks, message-hooks, save-hooks, and fcc-hooks
4684 will be interpreted if they are specified with only a simple regexp, instead of
4685 a matching pattern. The hooks are expanded when they are declared, so a hook
4686 will be interpreted according to the value of this variable at the time the
4687 hook is declared. The default value matches if the message is either from a
4688 user matching the regular expression given, or if it is from you (if the from
4689 address matches ``alternates'') and is to or cc'ed to a user matching the given
4691 The Mutt Next Generation E-Mail Client 92
4695 _
\b6_
\b._
\b4_
\b._
\b4_
\b6 _
\bd_
\be_
\bl_
\be_
\bt_
\be
4701 Controls whether or not messages are really deleted when closing or synchroniz-
4702 ing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting will automatically
4703 be purged without prompting. If set to _
\bn_
\bo, messages marked for deletion will
4704 be kept in the mailbox.
4706 _
\b6_
\b._
\b4_
\b._
\b4_
\b7 _
\bd_
\be_
\bl_
\be_
\bt_
\be_
\b__
\bu_
\bn_
\bt_
\ba_
\bg
4712 If this option is _
\bs_
\be_
\bt, Mutt-ng will untag messages when marking them for dele-
4713 tion. This applies when you either explicitly delete a message, or when you
4714 save it to another folder.
4716 _
\b6_
\b._
\b4_
\b._
\b4_
\b8 _
\bd_
\bi_
\bg_
\be_
\bs_
\bt_
\b__
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be
4722 If this option is _
\bs_
\be_
\bt, Mutt-ng's received-attachments menu will not show the
4723 subparts of individual messages in a multipart/digest. To see these subparts,
4724 press 'v' on that menu.
4726 _
\b6_
\b._
\b4_
\b._
\b4_
\b9 _
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br
4732 When _
\bs_
\be_
\bt, specifies a command used to filter messages. When a message is
4733 viewed it is passed as standard input to _
\b$_
\bd_
\bi_
\bs_
\bp_
\bl_
\ba_
\by_
\b__
\bf_
\bi_
\bl_
\bt_
\be_
\br (section 6.4.49 ,
4734 page 91), and the filtered message is read from the standard output.
4736 _
\b6_
\b._
\b4_
\b._
\b5_
\b0 _
\bd_
\bo_
\bt_
\bl_
\bo_
\bc_
\bk_
\b__
\bp_
\br_
\bo_
\bg_
\br_
\ba_
\bm
4740 Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock'
4742 Availability: Standalone and Dotlock
4744 Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
4746 The Mutt Next Generation E-Mail Client 93
4748 _
\b6_
\b._
\b4_
\b._
\b5_
\b1 _
\bd_
\bs_
\bn_
\b__
\bn_
\bo_
\bt_
\bi_
\bf_
\by
4754 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or
4757 This variable sets the request for when notification is returned. The string
4758 consists of a comma separated list (no spaces!) of one or more of the follow-
4759 ing: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to request notification on
4760 transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be
4761 notified of successful transmission.
4763 Example: set dsn_notify='failure,delay'
4765 _
\b6_
\b._
\b4_
\b._
\b5_
\b2 _
\bd_
\bs_
\bn_
\b__
\br_
\be_
\bt_
\bu_
\br_
\bn
4771 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x or
4774 This variable controls how much of your message is returned in DSN messages.
4775 It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message header, or _
\bf_
\bu_
\bl_
\bl to
4776 return the full message.
4778 Example: set dsn_return=hdrs
4780 _
\b6_
\b._
\b4_
\b._
\b5_
\b3 _
\bd_
\bu_
\bp_
\bl_
\bi_
\bc_
\ba_
\bt_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
4786 This variable controls whether Mutt-ng, when sorting by threads, threads mes-
4787 sages with the same Message-Id: header field together. If it is _
\bs_
\be_
\bt, it will
4788 indicate that it thinks they are duplicates of each other with an equals sign
4789 in the thread diagram.
4791 _
\b6_
\b._
\b4_
\b._
\b5_
\b4 _
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
4797 This option allows you to edit the header of your outgoing messages along with
4798 the body of your message.
4800 _
\b6_
\b._
\b4_
\b._
\b5_
\b5 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
4802 The Mutt Next Generation E-Mail Client 94
4808 This variable specifies which editor is used by Mutt-ng. It defaults to the
4809 value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi'
4810 if neither of those are set.
4812 _
\b6_
\b._
\b4_
\b._
\b5_
\b6 _
\be_
\bn_
\bc_
\bo_
\bd_
\be_
\b__
\bf_
\br_
\bo_
\bm
4818 When _
\bs_
\be_
\bt, Mutt-ng will quoted-printable encode messages when they contain the
4819 string ``From '' (note the trailing space) in the beginning of a line. Useful
4820 to avoid the tampering certain mail delivery and transport agents tend to do
4823 _
\b6_
\b._
\b4_
\b._
\b5_
\b7 _
\be_
\bn_
\bt_
\br_
\bo_
\bp_
\by_
\b__
\bf_
\bi_
\bl_
\be
4831 The file which includes random data that is used to initialize SSL library
4834 _
\b6_
\b._
\b4_
\b._
\b5_
\b8 _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be_
\b__
\bf_
\br_
\bo_
\bm
4840 When _
\bs_
\be_
\bt, Mutt-ng will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from the
4841 ``From:'' header field. Note that this information is passed to the sendmail
4842 command using the ``-f' command line switch, so don't set this option if you
4843 are using that switch in _
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 6.4.247 , page 140) yourself, or
4844 if the sendmail on your machine doesn't support that command line switch.
4846 _
\b6_
\b._
\b4_
\b._
\b5_
\b9 _
\be_
\bs_
\bc_
\ba_
\bp_
\be
4852 Escape character to use for functions in the builtin editor.
4854 _
\b6_
\b._
\b4_
\b._
\b6_
\b0 _
\bf_
\ba_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
4858 The Mutt Next Generation E-Mail Client 95
4862 When _
\bs_
\be_
\bt, the initial prompt for recipients and subject are skipped when reply-
4863 ing to messages, and the initial prompt for subject is skipped when forwarding
4866 N
\bNo
\bot
\bte
\be:
\b: this variable has no effect when the ``_
\b$_
\ba_
\bu_
\bt_
\bo_
\be_
\bd_
\bi_
\bt (section 6.4.17 , page
4867 84)'' variable is _
\bs_
\be_
\bt.
4869 _
\b6_
\b._
\b4_
\b._
\b6_
\b1 _
\bf_
\bc_
\bc_
\b__
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
4875 This variable controls whether or not attachments on outgoing messages are
4876 saved along with the main body of your message.
4878 _
\b6_
\b._
\b4_
\b._
\b6_
\b2 _
\bf_
\bc_
\bc_
\b__
\bc_
\bl_
\be_
\ba_
\br
4884 When this variable is _
\bs_
\be_
\bt, FCCs will be stored unencrypted and unsigned, even
4885 when the actual message is encrypted and/or signed. (PGP only)
4887 _
\b6_
\b._
\b4_
\b._
\b6_
\b3 _
\bf_
\bi_
\bl_
\be_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
4893 This variable is a colon-separated list of character encoding schemes for text
4894 file attatchments. If _
\bu_
\bn_
\bs_
\be_
\bt, _
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 6.4.24 , page 86) value will
4895 be used instead. For example, the following configuration would work for
4896 Japanese text handling:
4898 set file_charset='iso-2022-jp:euc-jp:shift_jis:utf-8'
4900 Note: ``iso-2022-*'' must be put at the head of the value as shown above if
4903 _
\b6_
\b._
\b4_
\b._
\b6_
\b4 _
\bf_
\bo_
\bl_
\bd_
\be_
\br
4909 Specifies the default location of your mailboxes. A ``+'' or ``='' at the
4910 beginning of a pathname will be expanded to the value of this variable. Note
4911 that if you change this variable from the default value you need to make sure
4912 that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use ``+'' or ``='' for any other vari-
4913 ables since expansion takes place during the ``set'' command.
4915 The Mutt Next Generation E-Mail Client 96
4917 _
\b6_
\b._
\b4_
\b._
\b6_
\b5 _
\bf_
\bo_
\bl_
\bd_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
4921 Default: '%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f'
4923 This variable allows you to customize the file browser display to your personal
4924 taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page
4925 105)'', but has its own set of printf(3)-like sequences:
4931 date/time folder was last modified
4940 group name (or numeric gid, if missing)
4943 number of hard links
4946 N if folder has new mail, blank otherwise
4952 * if the file is tagged, blank otherwise
4955 owner name (or numeric uid, if missing)
4958 right justify the rest of the string and pad with character 'X'
4961 pad to the end of the line with character 'X'
4963 _
\b6_
\b._
\b4_
\b._
\b6_
\b6 _
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
4969 Controls whether or not the Mail-Followup-To: header field is generated when
4970 sending mail. When _
\bs_
\be_
\bt, Mutt-ng will generate this field when you are replying
4972 The Mutt Next Generation E-Mail Client 97
4974 to a known mailing list, specified with the ``subscribe'' or ``_
\bl_
\bi_
\bs_
\bt_
\bs (section
4975 3.12 , page 32)'' commands or detected by common mailing list headers.
4977 This field has two purposes. First, preventing you from receiving duplicate
4978 copies of replies to messages which you send to mailing lists. Second, ensuring
4979 that you do get a reply separately for any messages sent to known lists to
4980 which you are not subscribed. The header will contain only the list's address
4981 for subscribed lists, and both the list address and your own email address for
4982 unsubscribed lists. Without this header, a group reply to your message sent to
4983 a subscribed list will be sent to both the list and your address, resulting in
4984 two copies of the same email for you.
4986 _
\b6_
\b._
\b4_
\b._
\b6_
\b7 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bb_
\bu_
\bf_
\bf_
\by_
\b__
\bc_
\bh_
\be_
\bc_
\bk
4992 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
4993 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
4994 already known to have new mail.
4996 Also see the following variables: ``_
\b$_
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt (section 6.4.320 , page 159)'',
4997 ``_
\b$_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 6.4.115 , page 109)'' and ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section
4998 6.4.99 , page 103)''.
5000 _
\b6_
\b._
\b4_
\b._
\b6_
\b8 _
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be
5006 This variable is similar to ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.241 , page 138)'',
5007 except that Mutt-ng will store a copy of your outgoing message by the username
5008 of the address you are sending to even if that mailbox does not exist.
5010 Also see the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 6.4.230 , page 136)'' variable.
5012 _
\b6_
\b._
\b4_
\b._
\b6_
\b9 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5018 Controls the decoding of complex MIME messages into text/plain when forwarding
5019 a message. The message header is also RFC2047 decoded. This variable is only
5020 used, if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 6.4.136 , page 113)'' is _
\bu_
\bn_
\bs_
\be_
\bt, otherwise
5021 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 6.4.137 , page 113)'' is used instead.
5023 _
\b6_
\b._
\b4_
\b._
\b7_
\b0 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt
5029 The Mutt Next Generation E-Mail Client 98
5031 Controls the handling of encrypted messages when forwarding a message. When
5032 _
\bs_
\be_
\bt, the outer layer of encryption is stripped off. This variable is only used
5033 if ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 6.4.136 , page 113)'' is _
\bs_
\be_
\bt and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5034 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 6.4.137 , page 113)'' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5036 _
\b6_
\b._
\b4_
\b._
\b7_
\b1 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\be_
\bd_
\bi_
\bt
5042 This quadoption controls whether or not the user is automatically placed in the
5043 editor when forwarding messages. For those who always want to forward with no
5044 modification, use a setting of _
\bn_
\bo.
5046 _
\b6_
\b._
\b4_
\b._
\b7_
\b2 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5052 This variable controls the default subject when forwarding a message. It uses
5053 the same format sequences as the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page
5056 _
\b6_
\b._
\b4_
\b._
\b7_
\b3 _
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bq_
\bu_
\bo_
\bt_
\be
5062 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message (when
5063 ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 6.4.136 , page 113)'' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
5064 ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 6.4.109 , page 105)''.
5066 _
\b6_
\b._
\b4_
\b._
\b7_
\b4 _
\bf_
\br_
\bo_
\bm
5068 Type: e-mail address
5072 This variable contains a default from address. It can be overridden using
5073 my_hdr (including from send-hooks) and ``_
\b$_
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.236 , page
5074 137)''. This variable is ignored if ``_
\b$_
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm (section 6.4.329 , page
5077 E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar
5078 <foo@bar.fb>' when replying to the mutt-ng developer's mailing list and Mutt-ng
5079 takes this email address.
5081 Defaults to the contents of the environment variable $EMAIL.
5083 _
\b6_
\b._
\b4_
\b._
\b7_
\b5 _
\bg_
\be_
\bc_
\bo_
\bs_
\b__
\bm_
\ba_
\bs_
\bk
5085 The Mutt Next Generation E-Mail Client 99
5087 Type: regular expression
5091 A regular expression used by Mutt-ng to parse the GECOS field of a password
5092 entry when expanding the alias. By default the regular expression is set to
5093 ``^[^,]*'' which will return the string up to the first ``,'' encountered. If
5094 the GECOS field contains a string like 'lastname, firstname' then you should
5095 do: set gecos_mask='.*'.
5097 This can be useful if you see the following behavior: you address a e-mail to
5098 user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to
5099 ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular
5100 expression that will match the whole name so Mutt-ng will expand ``Franklin''
5101 to ``Franklin, Steve''.
5103 _
\b6_
\b._
\b4_
\b._
\b7_
\b6 _
\bh_
\bd_
\br_
\bs
5109 When _
\bu_
\bn_
\bs_
\be_
\bt, the header fields normally added by the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 ,
5110 page 34)'' command are not created. This variable _
\bm_
\bu_
\bs_
\bt be _
\bu_
\bn_
\bs_
\be_
\bt before compos-
5111 ing a new message or replying in order to take effect. If _
\bs_
\be_
\bt, the user
5112 defined header fields are added to every new message.
5114 _
\b6_
\b._
\b4_
\b._
\b7_
\b7 _
\bh_
\be_
\ba_
\bd_
\be_
\br
5120 When _
\bs_
\be_
\bt, this variable causes Mutt-ng to include the header of the message you
5121 are replying to into the edit buffer. The ``_
\b$_
\bw_
\be_
\be_
\bd (section 6.4.335 , page
5122 162)'' setting applies.
5124 _
\b6_
\b._
\b4_
\b._
\b7_
\b8 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be
5130 Availability: Header Cache
5132 The _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 6.4.78 , page 98) variable points to the header
5135 If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 6.4.78 , page 98) points to a directory it will con-
5136 tain a header cache database per folder. If _
\b$_
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be (section 6.4.78 ,
5137 page 98) points to a file that file will be a single global header cache. By
5138 default it is _
\bu_
\bn_
\bs_
\be_
\bt so no header caching will be used.
5140 The Mutt Next Generation E-Mail Client 100
5142 _
\b6_
\b._
\b4_
\b._
\b7_
\b9 _
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bc_
\bo_
\bm_
\bp_
\br_
\be_
\bs_
\bs
5148 If enabled the header cache will be compressed. So only one fifth of the usual
5149 diskspace is used, but the uncompression can result in a slower open of the
5152 _
\b6_
\b._
\b4_
\b._
\b8_
\b0 _
\bh_
\be_
\bl_
\bp
5158 When _
\bs_
\be_
\bt, help lines describing the bindings for the major functions provided
5159 by each menu are displayed on the first line of the screen.
5161 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is bound to a
5162 sequence rather than a single keystroke. Also, the help line may not be
5163 updated if a binding is changed while Mutt-ng is running. Since this variable
5164 is primarily aimed at new users, neither of these should present a major prob-
5167 _
\b6_
\b._
\b4_
\b._
\b8_
\b1 _
\bh_
\bi_
\bd_
\bd_
\be_
\bn_
\b__
\bh_
\bo_
\bs_
\bt
5173 When _
\bs_
\be_
\bt, Mutt-ng will skip the host name part of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section
5174 6.4.89 , page 100)'' variable when adding the domain part to addresses. This
5175 variable does not affect the generation of Message-ID: header fields, and it
5176 will not lead to the cut-off of first-level domains.
5178 _
\b6_
\b._
\b4_
\b._
\b8_
\b2 _
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5184 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5185 limiting, in the thread tree.
5187 _
\b6_
\b._
\b4_
\b._
\b8_
\b3 _
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5193 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages in the thread
5196 The Mutt Next Generation E-Mail Client 101
5198 _
\b6_
\b._
\b4_
\b._
\b8_
\b4 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
5204 When _
\bs_
\be_
\bt, Mutt-ng will not show the subject of messages in the thread tree that
5205 have the same subject as their parent or closest previously displayed sibling.
5207 _
\b6_
\b._
\b4_
\b._
\b8_
\b5 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd
5213 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of messages that are hidden by
5214 limiting, at the top of threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bm_
\bi_
\bs_
\bs_
\b-
5215 _
\bi_
\bn_
\bg (section 6.4.83 , page 99) is set, this option will have no effect.
5217 _
\b6_
\b._
\b4_
\b._
\b8_
\b6 _
\bh_
\bi_
\bd_
\be_
\b__
\bt_
\bo_
\bp_
\b__
\bm_
\bi_
\bs_
\bs_
\bi_
\bn_
\bg
5223 When _
\bs_
\be_
\bt, Mutt-ng will not show the presence of missing messages at the top of
5224 threads in the thread tree. Note that when _
\b$_
\bh_
\bi_
\bd_
\be_
\b__
\bl_
\bi_
\bm_
\bi_
\bt_
\be_
\bd (section 6.4.82 ,
5225 page 99) is _
\bs_
\be_
\bt, this option will have no effect.
5227 _
\b6_
\b._
\b4_
\b._
\b8_
\b7 _
\bh_
\bi_
\bs_
\bt_
\bo_
\br_
\by
5233 This variable controls the size (in number of strings remembered) of the string
5234 history buffer. The buffer is cleared each time the variable is changed.
5236 _
\b6_
\b._
\b4_
\b._
\b8_
\b8 _
\bh_
\bo_
\bn_
\bo_
\br_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
5242 This variable controls whether or not a Mail-Followup-To: header field is hon-
5243 ored when group-replying to a message.
5245 _
\b6_
\b._
\b4_
\b._
\b8_
\b9 _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be
5251 Specifies the hostname to use after the ``@'' in local e-mail addresses and
5253 The Mutt Next Generation E-Mail Client 102
5255 during generation of Message-Id: headers.
5257 Please be sure to really know what you are doing when changing this variable to
5258 configure a custom domain part of Message-IDs.
5260 _
\b6_
\b._
\b4_
\b._
\b9_
\b0 _
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
5266 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages from
5267 mailing lists. When _
\bs_
\be_
\bt, if the ``Reply-To:'' header field is set to the same
5268 value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:''
5269 header field was set by the mailing list to automate responses to the list, and
5270 will ignore this field. To direct a response to the mailing list when this
5271 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
5272 sender and the list.
5274 _
\b6_
\b._
\b4_
\b._
\b9_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
5282 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
5283 use to log in to an IMAP server, in the order Mutt-ng should try them. Authen-
5284 tication methods are either ``login'' or the right side of an IMAP ``AUTH=''
5285 capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param-
5286 eter is case-insensitive.
5288 If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default) Mutt-ng will try all available meth-
5289 ods, in order from most-secure to least-secure.
5291 Example: set imap_authenticators='gssapi:cram-md5:login'
5293 N
\bNo
\bot
\bte
\be:
\b: Mutt-ng will only fall back to other authentication methods if the previ-
5294 ous methods are unavailable. If a method is available but authentication fails,
5295 Mutt-ng will not connect to the IMAP server.
5297 _
\b6_
\b._
\b4_
\b._
\b9_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5303 When _
\bs_
\be_
\bt, mutt will fetch the set of subscribed folders from your server on
5304 connection, and add them to the set of mailboxes it polls for new mail. See
5305 also the ``_
\bm_
\ba_
\bi_
\bl_
\bb_
\bo_
\bx_
\be_
\bs (section 3.14 , page 33)'' command.
5307 _
\b6_
\b._
\b4_
\b._
\b9_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\bd_
\be_
\bl_
\bi_
\bm_
\b__
\bc_
\bh_
\ba_
\br_
\bs
5309 The Mutt Next Generation E-Mail Client 103
5317 This contains the list of characters which you would like to treat as folder
5318 separators for displaying IMAP paths. In particular it helps in using the '='
5319 shortcut for your _
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 6.4.64 , page 94) variable.
5321 _
\b6_
\b._
\b4_
\b._
\b9_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs
5329 Mutt-ng requests these header fields in addition to the default headers (``DATE
5330 FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-
5331 REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP servers before displaying the
5332 ``index'' menu. You may want to add more headers for spam detection.
5334 N
\bNo
\bot
\bte
\be:
\b: This is a space separated list.
5336 _
\b6_
\b._
\b4_
\b._
\b9_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bh_
\bo_
\bm_
\be_
\b__
\bn_
\ba_
\bm_
\be_
\bs_
\bp_
\ba_
\bc_
\be
5344 You normally want to see your personal folders alongside your INBOX in the IMAP
5345 browser. If you see something else, you may set this variable to the IMAP path
5348 _
\b6_
\b._
\b4_
\b._
\b9_
\b6 _
\bi_
\bm_
\ba_
\bp_
\b__
\bk_
\be_
\be_
\bp_
\ba_
\bl_
\bi_
\bv_
\be
5356 This variable specifies the maximum amount of time in seconds that Mutt-ng will
5357 wait before polling open IMAP connections, to prevent the server from closing
5358 them before Mutt-ng has finished with them.
5360 The default is well within the RFC-specified minimum amount of time (30 min-
5361 utes) before a server is allowed to do this, but in practice the RFC does get
5362 violated every now and then.
5364 Reduce this number if you find yourself getting disconnected from your IMAP
5366 The Mutt Next Generation E-Mail Client 104
5368 server due to inactivity.
5370 _
\b6_
\b._
\b4_
\b._
\b9_
\b7 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
5378 This variable configures whether IMAP folder browsing will look for only sub-
5379 scribed folders or all folders. This can be toggled in the IMAP browser with
5380 the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
5382 _
\b6_
\b._
\b4_
\b._
\b9_
\b8 _
\bi_
\bm_
\ba_
\bp_
\b__
\bl_
\bo_
\bg_
\bi_
\bn
5390 Your login name on the IMAP server.
5392 This variable defaults to the value of ``_
\b$_
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br (section 6.4.105 , page
5395 _
\b6_
\b._
\b4_
\b._
\b9_
\b9 _
\bi_
\bm_
\ba_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5401 This variable configures how often (in seconds) Mutt-ng should look for new
5402 mail in IMAP folders. This is split from the ``_
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk (section 6.4.115 ,
5403 page 109)'' variable to generate less traffic and get more accurate information
5406 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b0 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
5414 Specifies the password for your IMAP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt
5415 you for your password when you invoke the fetch-mail function.
5417 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly secure
5418 machine, because the superuser can read your configuration even if you are the
5419 only one who can read the file.
5421 The Mutt Next Generation E-Mail Client 105
5423 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b1 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\ba_
\bs_
\bs_
\bi_
\bv_
\be
5431 When _
\bs_
\be_
\bt, Mutt-ng will not open new IMAP connections to check for new mail.
5432 Mutt-ng will only check for new mail over existing IMAP connections. This is
5433 useful if you don't want to be prompted to user/password pairs on Mutt-ng invo-
5434 cation, or if opening the connection is slow.
5436 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b2 _
\bi_
\bm_
\ba_
\bp_
\b__
\bp_
\be_
\be_
\bk
5444 If _
\bs_
\be_
\bt, Mutt-ng will avoid implicitly marking your mail as read whenever you
5445 fetch a message from the server. This is generally a good thing, but can make
5446 closing an IMAP folder somewhat slower. This option exists to appease speed
5449 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b3 _
\bi_
\bm_
\ba_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
5457 Controls whether or not Mutt-ng will try to reconnect to IMAP server when the
5460 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b4 _
\bi_
\bm_
\ba_
\bp_
\b__
\bs_
\be_
\br_
\bv_
\be_
\br_
\bn_
\bo_
\bi_
\bs_
\be
5468 When _
\bs_
\be_
\bt, Mutt-ng will display warning messages from the IMAP server as error
5469 messages. Since these messages are often harmless, or generated due to configu-
5470 ration problems on the server which are out of the users' hands, you may wish
5471 to suppress them at some point.
5473 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b5 _
\bi_
\bm_
\ba_
\bp_
\b__
\bu_
\bs_
\be_
\br
5477 The Mutt Next Generation E-Mail Client 106
5483 The name of the user whose mail you intend to access on the IMAP server.
5485 This variable defaults to your user name on the local machine.
5487 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b6 _
\bi_
\bm_
\bp_
\bl_
\bi_
\bc_
\bi_
\bt_
\b__
\ba_
\bu_
\bt_
\bo_
\bv_
\bi_
\be_
\bw
5493 If _
\bs_
\be_
\bt, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag
5494 set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an internal viewer defined for.
5495 If such an entry is found, Mutt-ng will use the viewer defined in that entry to
5496 convert the body part to text form.
5498 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b7 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be
5504 Controls whether or not a copy of the message(s) you are replying to is
5505 included in your reply.
5507 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b8 _
\bi_
\bn_
\bc_
\bl_
\bu_
\bd_
\be_
\b__
\bo_
\bn_
\bl_
\by_
\bf_
\bi_
\br_
\bs_
\bt
5513 Controls whether or not Mutt-ng includes only the first attachment of the mes-
5514 sage you are replying.
5516 _
\b6_
\b._
\b4_
\b._
\b1_
\b0_
\b9 _
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
5522 Specifies the string to prepend to each line of text quoted in a message to
5523 which you are replying. You are strongly encouraged not to change this value,
5524 as it tends to agitate the more fanatical netizens.
5526 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b0 _
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5530 Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s'
5532 This variable allows you to customize the message index display to your
5534 The Mutt Next Generation E-Mail Client 107
5538 ``Format strings'' are similar to the strings used in the ``C'' function
5539 printf(3) to format output (see the man page for more detail). The following
5540 sequences are defined in Mutt-ng:
5543 address of the author
5546 reply-to address (if present; otherwise: address of author)
5549 filename of the original message folder (think mailBox)
5552 the list to which the letter was sent, or else the folder name
5556 number of characters (bytes) in the message
5559 current message number
5562 date and time of the message in the format specified by ``date_for-
5563 mat'' converted to sender's time zone
5566 date and time of the message in the format specified by ``date_for-
5567 mat'' converted to the local time zone
5570 current message number in thread
5573 number of messages in current thread
5576 entire From: line (address + real name)
5579 author name, or recipient name if the message is from you
5582 spam attribute(s) of this message
5585 newsgroup name (if compiled with nntp support)
5588 message-id of the current message
5590 The Mutt Next Generation E-Mail Client 108
5593 number of lines in the message (does not work with maildir, mh, and
5594 possibly IMAP folders)
5597 If an address in the To or CC header field matches an address
5598 defined by the users ``subscribe'' command, this displays 'To
5599 <list-name>', otherwise the same as %F.
5602 total number of message in the mailbox
5605 number of hidden messages if the thread is collapsed.
5611 author's real name (or address if missing)
5614 (_O_riginal save folder) Where Mutt-ng would formerly have stashed
5615 the message: list name or recipient name if no list
5618 subject of the message
5621 status of the message (N/D/d/!/r/*)
5624 `to:' field (recipients)
5627 the appropriate character from the _
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 6.4.322 ,
5631 user (login) name of the author
5634 first name of the author, or the recipient if the message is from
5638 name of organization of author (`organization:' field)
5641 `x-label:' field, if present
5644 `x-label' field, if present, and (1) not at part of a thread tree,
5645 (2) at the top of a thread, or (3) `x-label' is different from
5647 The Mutt Next Generation E-Mail Client 109
5649 preceding message's `x-label'.
5652 message status flags
5655 the date and time of the message is converted to sender's time
5656 zone, and ``fmt'' is expanded by the library function ``strftime'';
5657 a leading bang disables locales
5660 the date and time of the message is converted to the local time
5661 zone, and ``fmt'' is expanded by the library function ``strftime'';
5662 a leading bang disables locales
5665 the local date and time when the message was received. ``fmt'' is
5666 expanded by the library function ``strftime''; a leading bang dis-
5670 the current local time. ``fmt'' is expanded by the library function
5671 ``strftime''; a leading bang disables locales.
5674 right justify the rest of the string and pad with character 'X'
5677 pad to the end of the line with character 'X'
5679 See also: ``_
\b$_
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 6.4.322 , page 159)''.
5681 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b1 _
\bi_
\bs_
\bp_
\be_
\bl_
\bl
5687 How to invoke ispell (GNU's spell-checking software).
5689 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b2 _
\bk_
\be_
\be_
\bp_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
5695 If _
\bs_
\be_
\bt, read messages marked as flagged will not be moved from your spool mail-
5696 box to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 6.4.124 , page 110)'' mailbox, or as a result of
5697 a ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33)'' command.
5699 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b3 _
\bl_
\bi_
\bs_
\bt_
\b__
\br_
\be_
\bp_
\bl_
\by
5703 The Mutt Next Generation E-Mail Client 110
5707 When _
\bs_
\be_
\bt, address replies to the mailing list the original message came from
5708 (instead to the author only). Setting this option to ``_
\ba_
\bs_
\bk_
\b-_
\by_
\be_
\bs'' or ``_
\ba_
\bs_
\bk_
\b-_
\bn_
\bo''
5709 will ask if you really intended to reply to the author only.
5711 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b4 _
\bl_
\bo_
\bc_
\ba_
\bl_
\be
5717 The locale used by strftime(3) to format dates. Legal values are the strings
5718 your system accepts for the locale variable LC_TIME.
5720 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b5 _
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
5726 This variable configures how often (in seconds) Mutt-ng should look for new
5729 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
5732 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b6 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bp_
\ba_
\bt_
\bh
5738 This variable specifies which files to consult when attempting to display MIME
5739 bodies not directly supported by Mutt-ng.
5741 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b7 _
\bm_
\ba_
\bi_
\bl_
\bc_
\ba_
\bp_
\b__
\bs_
\ba_
\bn_
\bi_
\bt_
\bi_
\bz_
\be
5747 If _
\bs_
\be_
\bt, Mutt-ng will restrict possible characters in mailcap % expandos to a
5748 well-defined set of safe characters. This is the safe setting, but we are not
5749 sure it doesn't break some more advanced MIME stuff.
5751 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!
5753 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b8 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by
5759 The Mutt Next Generation E-Mail Client 111
5761 Availability: Header Cache
5763 Check for Maildir unaware programs other than Mutt-ng having modified maildir
5764 files when the header cache is in use. This incurs one stat(2) per message
5765 every time the folder is opened.
5767 _
\b6_
\b._
\b4_
\b._
\b1_
\b1_
\b9 _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br_
\b__
\bt_
\br_
\ba_
\bs_
\bh
5773 If _
\bs_
\be_
\bt, messages marked as deleted will be saved with the maildir (T)rashed
5774 flag instead of physically deleted.
5776 N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to maildir-style mailboxes. Setting it will have no
5777 effect on other mailbox types.
5779 It is similiar to the trash option.
5781 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b0 _
\bm_
\ba_
\br_
\bk_
\b__
\bo_
\bl_
\bd
5787 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
5788 mailbox without reading them.
5790 With this option _
\bs_
\be_
\bt, the next time you start Mutt-ng, the messages will show
5791 up with an 'O' next to them in the ``index'' menu, indicating that they are
5794 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b1 _
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs
5800 Controls the display of wrapped lines in the internal pager. If set, a ``+''
5801 marker is displayed at the beginning of wrapped lines. Also see the
5802 ``_
\b$_
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp (section 6.4.263 , page 144)'' variable.
5804 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b2 _
\bm_
\ba_
\bs_
\bk
5806 Type: regular expression
5810 A regular expression used in the file browser, optionally preceded by the _
\bn_
\bo_
\bt
5811 operator ``!''. Only files whose names match this mask will be shown. The
5812 match is always case-sensitive.
5814 The Mutt Next Generation E-Mail Client 112
5816 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b3 _
\bm_
\ba_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\b__
\bl_
\be_
\bn_
\bg_
\bt_
\bh
5822 When _
\bs_
\be_
\bt, the maximum line length for displaying ``format = flowed'' messages
5823 is limited to this length. A value of 0 (which is also the default) means that
5824 the maximum line length is determined by the terminal width and _
\b$_
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
5825 (section 6.4.337 , page 162).
5827 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b4 _
\bm_
\bb_
\bo_
\bx
5833 This specifies the folder into which read mail in your ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section
5834 6.4.296 , page 151)'' folder will be appended.
5836 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b5 _
\bm_
\bb_
\bo_
\bx_
\b__
\bt_
\by_
\bp_
\be
5842 The default mailbox type used when creating new folders. May be any of mbox,
5843 MMDF, MH and Maildir.
5845 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b6 _
\bm_
\be_
\bn_
\bu_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
5851 This variable controls the number of lines of context that are given when
5852 scrolling through menus. (Similar to ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 6.4.167 , page
5855 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b7 _
\bm_
\be_
\bn_
\bu_
\b__
\bm_
\bo_
\bv_
\be_
\b__
\bo_
\bf_
\bf
5861 When _
\bu_
\bn_
\bs_
\be_
\bt, the bottom entry of menus will never scroll up past the bottom of
5862 the screen, unless there are less entries than lines. When _
\bs_
\be_
\bt, the bottom
5863 entry may move off the bottom.
5865 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b8 _
\bm_
\be_
\bn_
\bu_
\b__
\bs_
\bc_
\br_
\bo_
\bl_
\bl
5871 The Mutt Next Generation E-Mail Client 113
5873 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt to move
5874 across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and the next or pre-
5875 vious page of the menu is displayed (useful for slow links to avoid many
5878 _
\b6_
\b._
\b4_
\b._
\b1_
\b2_
\b9 _
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5884 This is the string displayed in the ``attachment'' menu for attachments of type
5885 message/rfc822. For a full listing of defined printf(3)-like sequences see the
5886 section on ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105)''.
5888 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b0 _
\bm_
\be_
\bt_
\ba_
\b__
\bk_
\be_
\by
5894 If _
\bs_
\be_
\bt, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as
5895 if the user had pressed the ESC key and whatever key remains after having the
5896 high bit removed. For example, if the key pressed has an ASCII value of 0xf4,
5897 then this is treated as if the user had pressed ESC then ``x''. This is
5898 because the result of removing the high bit from ``0xf4'' is ``0x74'', which is
5899 the ASCII character ``x''.
5901 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b1 _
\bm_
\be_
\bt_
\bo_
\bo
5907 If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will remove your address (see the ``alternates'' command)
5908 from the list of recipients when replying to a message.
5910 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b2 _
\bm_
\bh_
\b__
\bp_
\bu_
\br_
\bg_
\be
5916 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will mimic mh's behaviour and rename deleted messages to
5917 _
\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-
5918 able is set, the message files will simply be deleted.
5920 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b3 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bf_
\bl_
\ba_
\bg_
\bg_
\be_
\bd
5926 The name of the MH sequence used for flagged messages.
5928 The Mutt Next Generation E-Mail Client 114
5930 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b4 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\br_
\be_
\bp_
\bl_
\bi_
\be_
\bd
5936 The name of the MH sequence used to tag replied messages.
5938 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b5 _
\bm_
\bh_
\b__
\bs_
\be_
\bq_
\b__
\bu_
\bn_
\bs_
\be_
\be_
\bn
5944 The name of the MH sequence used for unseen messages.
5946 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b6 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd
5952 When _
\bs_
\be_
\bt, the message you are forwarding will be attached as a separate MIME
5953 part instead of included in the main body of the message.
5955 This is useful for forwarding MIME messages so the receiver can properly view
5956 the message as it was delivered to you. If you like to switch between MIME and
5957 not MIME from mail to mail, set this variable to ask-no or ask-yes.
5959 Also see ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 6.4.69 , page 96)'' and ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\b-
5960 _
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 6.4.137 , page 113)''.
5962 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b7 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
5968 Controls the decoding of complex MIME messages into text/plain when forwarding
5969 a message while ``_
\b$_
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd (section 6.4.136 , page 113)'' is _
\bs_
\be_
\bt. Other-
5970 wise ``_
\b$_
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be (section 6.4.69 , page 96)'' is used instead.
5972 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b8 _
\bm_
\bi_
\bm_
\be_
\b__
\bf_
\bo_
\br_
\bw_
\ba_
\br_
\bd_
\b__
\br_
\be_
\bs_
\bt
5978 When forwarding multiple attachments of a MIME message from the recvattach
5979 menu, attachments which cannot be decoded in a reasonable manner will be
5980 attached to the newly composed message if this option is set.
5982 _
\b6_
\b._
\b4_
\b._
\b1_
\b3_
\b9 _
\bm_
\bi_
\bx_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
5984 The Mutt Next Generation E-Mail Client 115
5988 Default: '%4n %c %-16s %a'
5990 Availability: Mixmaster
5992 This variable describes the format of a remailer line on the mixmaster chain
5993 selection screen. The following printf(3)-like sequences are supported:
5996 The running number on the menu.
5999 Remailer capabilities.
6002 The remailer's short name.
6005 The remailer's e-mail address.
6007 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b0 _
\bm_
\bi_
\bx_
\bm_
\ba_
\bs_
\bt_
\be_
\br
6011 Default: 'mixmaster'
6013 Availability: Mixmaster
6015 This variable contains the path to the Mixmaster binary on your system. It is
6016 used with various sets of parameters to gather the list of known remailers, and
6017 to finally send a message through the mixmaster chain.
6019 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b1 _
\bm_
\bo_
\bv_
\be
6025 Controls whether or not Mutt-ng will move read messages from your spool mailbox
6026 to your ``_
\b$_
\bm_
\bb_
\bo_
\bx (section 6.4.124 , page 110)'' mailbox, or as a result of a
6027 ``_
\bm_
\bb_
\bo_
\bx_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.13 , page 33)'' command.
6029 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b2 _
\bm_
\bs_
\bg_
\bi_
\bd_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6033 Default: '%Y%m%d%h%M%s.G%P%p'
6035 This is the format for the ``local part'' of the Message-Id: header field gen-
6036 erated by Mutt-ng. If this variable is empty, no Message-Id: headers will be
6037 generated. The '%' character marks that certain data will be added to the
6038 string, similar to printf(3). The following characters are allowed:
6040 The Mutt Next Generation E-Mail Client 116
6043 the current day of month
6055 the current UNIX timestamp (octal)
6061 the current Message-ID prefix (a character rotating with every Mes-
6062 sage-ID being generated)
6065 a random integer value (decimal)
6068 a random integer value (hexadecimal)
6074 the current UNIX timestamp (decimal)
6077 the current UNIX timestamp (hexadecimal)
6080 the current year (Y2K compliant)
6085 N
\bNo
\bot
\bte
\be:
\b: Please only change this setting if you know what you are doing. Also
6086 make sure to consult RFC2822 to produce technically _
\bv_
\ba_
\bl_
\bi_
\bd strings.
6088 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b3 _
\bn_
\ba_
\br_
\br_
\bo_
\bw_
\b__
\bt_
\br_
\be_
\be
6094 This variable, when _
\bs_
\be_
\bt, makes the thread tree narrower, allowing deeper
6095 threads to fit on the screen.
6097 The Mutt Next Generation E-Mail Client 117
6099 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo
6107 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the Followup-To: header field before edit-
6108 ing the body of an outgoing news article.
6110 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\ba_
\bs_
\bk_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6118 If _
\bs_
\be_
\bt, Mutt-ng will prompt you for the X-Comment-To: header field before edit-
6119 ing the body of an outgoing news article.
6121 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br
6125 Default: '~/.muttng'
6129 This variable points to directory where Mutt-ng will cache news article head-
6130 ers. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and will be reloaded each time
6131 when you enter a newsgroup.
6133 As for the header caching in connection with IMAP and/or Maildir, this drasti-
6134 cally increases speed and lowers traffic.
6136 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bt_
\bc_
\bh_
\bu_
\bp
6144 If this variable is _
\bs_
\be_
\bt, Mutt-ng will mark all articles in a newsgroup as read
6145 when you leaving it.
6147 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6153 The Mutt Next Generation E-Mail Client 118
6157 This variable controls how many news articles to cache per newsgroup (if
6158 caching is enabled, see _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\ba_
\bc_
\bh_
\be_
\b__
\bd_
\bi_
\br (section 6.4.146 , page 116)) and how
6159 many news articles to show in the ``index'' menu.
6161 If there're more articles than defined with _
\b$_
\bn_
\bn_
\bt_
\bp_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt (section 6.4.148 ,
6162 page 116), all older ones will be removed/not shown in the index.
6164 _
\b6_
\b._
\b4_
\b._
\b1_
\b4_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\bf_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b__
\bt_
\bo_
\b__
\bp_
\bo_
\bs_
\bt_
\be_
\br
6172 If this variable is _
\bs_
\be_
\bt and the keyword 'poster' is present in the Followup-To:
6173 header field, a follow-up to the newsgroup is not permitted. The message will
6174 be mailed to the submitter of the message via mail.
6176 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bg_
\br_
\bo_
\bu_
\bp_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6180 Default: '%4C %M%N %5s %-45.45f %d'
6184 This variable allows you to customize the newsgroup browser display to your
6185 personal taste. This string is similar to ``_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 ,
6186 page 105)'', but has its own set of printf(3)-like sequences:
6188 %C current newsgroup number
6189 %d description of newsgroup (retrieved from server)
6191 %M ``-'' if newsgroup not allowed for direct post (moderated for example)
6192 %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
6193 %n number of new articles in newsgroup
6194 %s number of unread articles in newsgroup
6195 %>X right justify the rest of the string and pad with character "X"
6196 %|X pad to the end of the line with character "X"
6198 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6206 This variable specifies the name (or address) of the NNTP server to be used.
6208 The Mutt Next Generation E-Mail Client 119
6210 It defaults to the value specified via the environment variable $NNTPSERVER or
6211 contained in the file /etc/nntpserver.
6213 You can also specify a username and an alternative port for each newsserver,
6216 [nntp[s]://][username[:password]@]newsserver[:port]
6218 N
\bNo
\bot
\bte
\be:
\b: Using a password as shown and stored in a configuration file presents a
6219 security risk since the superuser of your machine may read it regardless of the
6222 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bi_
\bn_
\be_
\bw_
\bs
6230 If _
\bs_
\be_
\bt, specifies the program and arguments used to deliver news posted by
6231 Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol-
6232 lowing printf(3)-style sequence is understood:
6236 Example: set inews='/usr/local/bin/inews -hS'
6238 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bl_
\bo_
\ba_
\bd_
\b__
\bd_
\be_
\bs_
\bc_
\br_
\bi_
\bp_
\bt_
\bi_
\bo_
\bn
6246 This variable controls whether or not descriptions for newsgroups are to be
6247 loaded when subscribing to a newsgroup.
6249 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6257 The time in seconds until any operations on a newsgroup except posting a new
6258 article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on
6259 each operation in index (stepping, read article, etc.).
6261 The Mutt Next Generation E-Mail Client 120
6263 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b5 _
\bn_
\bn_
\bt_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bu_
\bb_
\bj_
\be_
\bc_
\bt
6271 If _
\bu_
\bn_
\bs_
\be_
\bt, an 8-bit ``Subject:'' header field in a news article will not be
6272 encoded according to RFC2047.
6274 N
\bNo
\bot
\bte
\be:
\b: Only change this setting if you know what you are doing.
6276 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b6 _
\bn_
\bn_
\bt_
\bp_
\b__
\bn_
\be_
\bw_
\bs_
\br_
\bc
6280 Default: '~/.newsrc'
6284 This file contains information about subscribed newsgroup and articles read so
6287 To ease the use of multiple news servers, the following printf(3)-style
6288 sequence is understood:
6292 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b7 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6300 Your password for NNTP account.
6302 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6303 the superuser of your machine may read it regardless of the file's permissions.
6305 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b8 _
\bn_
\bn_
\bt_
\bp_
\b__
\bp_
\bo_
\bs_
\bt_
\b__
\bm_
\bo_
\bd_
\be_
\br_
\ba_
\bt_
\be_
\bd
6313 If set to _
\by_
\be_
\bs, Mutt-ng will post articles to newsgroup that have not permis-
6314 sions to post (e.g. moderated).
6316 The Mutt Next Generation E-Mail Client 121
6318 N
\bNo
\bot
\bte
\be:
\b: if the newsserver does not support posting to that newsgroup or a group
6319 is totally read-only, that posting will not have any effect.
6321 _
\b6_
\b._
\b4_
\b._
\b1_
\b5_
\b9 _
\bn_
\bn_
\bt_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6329 Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
6330 was connection lost.
6332 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b0 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\ba_
\bv_
\be_
\b__
\bu_
\bn_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd
6340 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into the ``newsrc''
6341 file and into the news cache.
6343 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b1 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bn_
\be_
\bw_
\b__
\bn_
\be_
\bw_
\bs
6351 If _
\bs_
\be_
\bt, the newsserver will be asked for new newsgroups on entering the
6352 browser. Otherwise, it will be done only once for a newsserver. Also controls
6353 whether or not the number of new articles of subscribed newsgroups will be
6356 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b2 _
\bn_
\bn_
\bt_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bu_
\bn_
\br_
\be_
\ba_
\bd
6364 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will be dis-
6365 played in the newsgroup browser.
6367 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b3 _
\bn_
\bn_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
6373 The Mutt Next Generation E-Mail Client 122
6377 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and the server requires authen-
6378 tification, Mutt-ng will prompt you for your account name.
6380 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b4 _
\bn_
\bn_
\bt_
\bp_
\b__
\bx_
\b__
\bc_
\bo_
\bm_
\bm_
\be_
\bn_
\bt_
\b__
\bt_
\bo
6388 If _
\bs_
\be_
\bt, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full
6389 name of the original article author) to articles that you followup to.
6391 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b5 _
\bo_
\bp_
\be_
\br_
\ba_
\bt_
\bi_
\bn_
\bg_
\b__
\bs_
\by_
\bs_
\bt_
\be_
\bm
6397 This specifies the operating system name for the User-Agent: header field. If
6398 this is _
\bu_
\bn_
\bs_
\be_
\bt, it will be set to the operating system name that uname(2)
6399 returns. If uname(2) fails, ``UNIX'' will be used.
6401 It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
6403 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b6 _
\bp_
\ba_
\bg_
\be_
\br
6409 This variable specifies which pager you would like to use to view messages.
6410 ``builtin'' means to use the builtin pager, otherwise this variable should
6411 specify the pathname of the external pager you would like to use.
6413 Using an external pager may have some disadvantages: Additional keystrokes are
6414 necessary because you can't call Mutt-ng functions directly from the pager, and
6415 screen resizes cause lines longer than the screen width to be badly formatted
6418 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b7 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bc_
\bo_
\bn_
\bt_
\be_
\bx_
\bt
6424 This variable controls the number of lines of context that are given when dis-
6425 playing the next or previous page in the internal pager. By default, Mutt-ng
6426 will display the line after the last one on the screen at the top of the next
6427 page (0 lines of context).
6429 The Mutt Next Generation E-Mail Client 123
6431 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b8 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6435 Default: '-%Z- %C/%m: %-20.20n %s'
6437 This variable controls the format of the one-line message ``status'' displayed
6438 before each message in either the internal or an external pager. The valid
6439 sequences are listed in the ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105)''
6442 _
\b6_
\b._
\b4_
\b._
\b1_
\b6_
\b9 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs
6448 Determines the number of lines of a mini-index which is shown when in the
6449 pager. The current message, unless near the top or bottom of the folder, will
6450 be roughly one third of the way down this mini-index, giving the reader the
6451 context of a few messages before and after the message. This is useful, for
6452 example, to determine how many messages remain to be read in the current
6453 thread. One of the lines is reserved for the status bar from the index, so a
6454 _
\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
6455 0 results in no index being shown. If the number of messages in the current
6456 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
6459 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b0 _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bs_
\bt_
\bo_
\bp
6465 When _
\bs_
\be_
\bt, the internal-pager will n
\bno
\bot
\bt move to the next message when you are at
6466 the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
6468 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b1 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6474 If _
\bs_
\be_
\bt, Mutt-ng will automatically attempt to decrypt traditional PGP messages
6475 whenever the user performs an operation which ordinarily would result in the
6476 contents of the message being operated on. For example, if the user displays a
6477 pgp-traditional message which has not been manually checked with the check-tra-
6478 ditional-pgp function, Mutt-ng will automatically check the message for tradi-
6481 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b2 _
\bp_
\bg_
\bp_
\b__
\ba_
\bu_
\bt_
\bo_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6485 The Mutt Next Generation E-Mail Client 124
6489 This option controls whether Mutt-ng generates old-style inline (traditional)
6490 PGP encrypted or signed messages under certain circumstances. This can be
6491 overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not required.
6493 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6494 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6495 ing PGP/MIME messages when inline (traditional) would not work. See also:
6496 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 6.4.188 , page 126)''.
6498 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.
6501 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b3 _
\bp_
\bg_
\bp_
\b__
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\be_
\bx_
\bi_
\bt
6507 If _
\bs_
\be_
\bt, Mutt-ng will check the exit code of the PGP subprocess when signing or
6508 encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
6510 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b4 _
\bp_
\bg_
\bp_
\b__
\bc_
\bl_
\be_
\ba_
\br_
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6516 This format is used to create a old-style ``clearsigned'' PGP message.
6518 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)
6520 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b5 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6526 This format strings specifies a command which is used to decode application/pgp
6529 The PGP command formats have their own set of printf(3)-like sequences:
6532 Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
6533 string otherwise. Note: This may be used with a %? construct.
6536 Expands to the name of a file containing a message.
6539 Expands to the name of a file containing the signature part of a
6540 multipart/signed attachment when verifying it.
6542 The Mutt Next Generation E-Mail Client 125
6545 The value of _
\b$_
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs (section 6.4.192 , page 127).
6548 One or more key IDs.
6550 For examples on how to configure these formats for the various versions of PGP
6551 which are floating around, see the pgp*.rc and gpg.rc files in the samples/
6552 subdirectory which has been installed on your system alongside the documenta-
6555 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b6 _
\bp_
\bg_
\bp_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6561 This command is used to decrypt a PGP encrypted message. (PGP only)
6563 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b7 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bo_
\bn_
\bl_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6569 This command is used to encrypt a body part without signing it. (PGP only)
6571 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b8 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6577 This command is used to both sign and encrypt a body part. (PGP only)
6579 _
\b6_
\b._
\b4_
\b._
\b1_
\b7_
\b9 _
\bp_
\bg_
\bp_
\b__
\be_
\bn_
\bt_
\br_
\by_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
6583 Default: '%4n %t%f %4l/0x%k %-4a %2c %u'
6585 This variable allows you to customize the PGP key selection menu to your per-
6586 sonal taste. This string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page
6587 105)'', but has its own set of printf(3)-like sequences:
6598 The Mutt Next Generation E-Mail Client 126
6613 trust/validity of the key-uid association
6616 date of the key where <s> is an strftime(3) expression
6620 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b0 _
\bp_
\bg_
\bp_
\b__
\be_
\bx_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6626 This command is used to export a public key from the user's key ring. (PGP
6629 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b1 _
\bp_
\bg_
\bp_
\b__
\bg_
\be_
\bt_
\bk_
\be_
\by_
\bs_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6635 This command is invoked whenever Mutt-ng will need public key information. %r
6636 is the only printf(3)-like sequence used with this format. (PGP only)
6638 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b2 _
\bp_
\bg_
\bp_
\b__
\bg_
\bo_
\bo_
\bd_
\b__
\bs_
\bi_
\bg_
\bn
6640 Type: regular expression
6644 If you assign a text to this variable, then a PGP signature is only considered
6645 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 6.4.198 , page 129)
6646 contains the text. Use this variable if the exit code from the command is 0
6647 even for bad signatures. (PGP only)
6649 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b3 _
\bp_
\bg_
\bp_
\b__
\bi_
\bg_
\bn_
\bo_
\br_
\be_
\b__
\bs_
\bu_
\bb_
\bk_
\be_
\by_
\bs
6655 The Mutt Next Generation E-Mail Client 127
6657 Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
6658 the principal key will inherit the subkeys' capabilities. _
\bU_
\bn_
\bs_
\be_
\bt this if you
6659 want to play interesting key selection games. (PGP only)
6661 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b4 _
\bp_
\bg_
\bp_
\b__
\bi_
\bm_
\bp_
\bo_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6667 This command is used to import a key from a message into the user's public key
6670 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b5 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bp_
\bu_
\bb_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6676 This command is used to list the public key ring's contents. The output format
6677 must be analogous to the one used by gpg --list-keys --with-colons.
6679 This format is also generated by the pgpring utility which comes with Mutt-ng.
6682 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b6 _
\bp_
\bg_
\bp_
\b__
\bl_
\bi_
\bs_
\bt_
\b__
\bs_
\be_
\bc_
\br_
\bi_
\bn_
\bg_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6688 This command is used to list the secret key ring's contents. The output format
6689 must be analogous to the one used by gpg --list-keys --with-colons.
6691 This format is also generated by the pgpring utility which comes with Mutt-ng.
6694 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b7 _
\bp_
\bg_
\bp_
\b__
\bl_
\bo_
\bn_
\bg_
\b__
\bi_
\bd_
\bs
6700 If _
\bs_
\be_
\bt, use 64 bit PGP key IDs. _
\bU_
\bn_
\bs_
\be_
\bt uses the normal 32 bit Key IDs. (PGP
6703 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b8 _
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo
6709 This option controls whether Mutt-ng will prompt you for automatically sending
6710 a (signed/encrypted) message using PGP/MIME when inline (traditional) fails
6712 The Mutt Next Generation E-Mail Client 128
6716 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.
6719 _
\b6_
\b._
\b4_
\b._
\b1_
\b8_
\b9 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bp_
\bl_
\by_
\bi_
\bn_
\bl_
\bi_
\bn_
\be
6725 Setting this variable will cause Mutt-ng to always attempt to create an inline
6726 (traditional) message when replying to a message which is PGP encrypted/signed
6727 inline. This can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when inline is not
6728 required. This option does not automatically detect if the (replied-to) mes-
6729 sage is inline; instead it relies on Mutt-ng internals for previously
6730 checked/flagged messages.
6732 Note that Mutt-ng might automatically use PGP/MIME for messages which consist
6733 of more than a single MIME part. Mutt-ng can be configured to ask before send-
6734 ing PGP/MIME messages when inline (traditional) would not work. See also:
6735 ``_
\b$_
\bp_
\bg_
\bp_
\b__
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bu_
\bt_
\bo (section 6.4.188 , page 126)''.
6737 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.
6740 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b0 _
\bp_
\bg_
\bp_
\b__
\br_
\be_
\bt_
\ba_
\bi_
\bn_
\ba_
\bb_
\bl_
\be_
\b__
\bs_
\bi_
\bg_
\bs
6746 If _
\bs_
\be_
\bt, signed and encrypted messages will consist of nested multipart/signed
6747 and multipart/encrypted body parts.
6749 This is useful for applications like encrypted and signed mailing lists, where
6750 the outer layer (multipart/encrypted) can be easily removed, while the inner
6751 multipart/signed part is retained. (PGP only)
6753 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b1 _
\bp_
\bg_
\bp_
\b__
\bs_
\bh_
\bo_
\bw_
\b__
\bu_
\bn_
\bu_
\bs_
\ba_
\bb_
\bl_
\be
6759 If _
\bs_
\be_
\bt, Mutt-ng will display non-usable keys on the PGP key selection menu.
6760 This includes keys which have been revoked, have expired, or have been marked
6761 as ``disabled'' by the user. (PGP only)
6763 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b2 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\ba_
\bs
6769 The Mutt Next Generation E-Mail Client 129
6771 If you have more than one key pair, this option allows you to specify which of
6772 your private keys to use. It is recommended that you use the keyid form to
6773 specify your key (e.g., ``0x00112233''). (PGP only)
6775 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b3 _
\bp_
\bg_
\bp_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6781 This command is used to create the detached PGP signature for a multi-
6782 part/signed PGP/MIME body part. (PGP only)
6784 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b4 _
\bp_
\bg_
\bp_
\b__
\bs_
\bo_
\br_
\bt_
\b__
\bk_
\be_
\by_
\bs
6790 Specifies how the entries in the ``pgp keys'' menu are sorted. The following
6794 sort alphabetically by user id
6797 sort alphabetically by key id
6800 sort by key creation date
6803 sort by the trust of the key
6805 If you prefer reverse order of the above values, prefix it with ``reverse-''.
6808 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b5 _
\bp_
\bg_
\bp_
\b__
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\be_
\bn_
\bc
6814 If _
\bs_
\be_
\bt, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-
6815 printable. Please note that unsetting this variable may lead to problems with
6816 non-verifyable PGP signatures, so only change this if you know what you are
6819 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b6 _
\bp_
\bg_
\bp_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
6825 The Mutt Next Generation E-Mail Client 130
6827 The number of seconds after which a cached passphrase will expire if not used.
6828 Default: 300. (PGP only)
6830 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b7 _
\bp_
\bg_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bg_
\bp_
\bg_
\b__
\ba_
\bg_
\be_
\bn_
\bt
6836 If _
\bs_
\be_
\bt, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
6838 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b8 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6844 This command is used to verify PGP signatures. (PGP only)
6846 _
\b6_
\b._
\b4_
\b._
\b1_
\b9_
\b9 _
\bp_
\bg_
\bp_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bk_
\be_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
6852 This command is used to verify key information from the key selection menu.
6855 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b0 _
\bp_
\bi_
\bp_
\be_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
6861 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
6862 pipe the messages without any preprocessing. When _
\bs_
\be_
\bt, Mutt-ng will weed head-
6863 ers and will attempt to PGP/MIME decode the messages first.
6865 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b1 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
6871 The separator to add between messages when piping a list of tagged messages to
6872 an external Unix command.
6874 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b2 _
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
6880 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag- prefix'' or
6882 The Mutt Next Generation E-Mail Client 131
6884 ``tag-prefix-cond'' operators. If this variable is _
\bu_
\bn_
\bs_
\be_
\bt, when piping a list
6885 of tagged messages Mutt-ng will concatenate the messages and will pipe them as
6886 a single folder. When _
\bs_
\be_
\bt, Mutt-ng will pipe the messages one by one. In both
6887 cases the messages are piped in the current sorted order, and the ``_
\b$_
\bp_
\bi_
\bp_
\be_
\b__
\bs_
\be_
\bp
6888 (section 6.4.201 , page 129)'' separator is added after each message.
6890 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b3 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bt_
\br_
\by_
\b__
\ba_
\bl_
\bl
6898 If _
\bs_
\be_
\bt, Mutt-ng will try all available methods. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will only
6899 fall back to other authentication methods if the previous methods are unavail-
6900 able. If a method is available but authentication fails, Mutt-ng will not con-
6901 nect to the POP server.
6903 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b4 _
\bp_
\bo_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\be_
\bn_
\bt_
\bi_
\bc_
\ba_
\bt_
\bo_
\br_
\bs
6911 This is a colon-delimited list of authentication methods Mutt-ng may attempt to
6912 use to log in to an POP server, in the order Mutt-ng should try them. Authen-
6913 tication methods are either ``user'', ``apop'' or any SASL mechanism, eg
6914 ``digest-md5'', ``gssapi'' or ``cram-md5''.
6916 This parameter is case-insensitive. If this parameter is _
\bu_
\bn_
\bs_
\be_
\bt (the default)
6917 Mutt-ng will try all available methods, in order from most-secure to least-
6920 Example: set pop_authenticators='digest-md5:apop:user'
6922 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b5 _
\bp_
\bo_
\bp_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
6930 If _
\bs_
\be_
\bt, Mutt-ng will delete successfully downloaded messages from the POP
6931 server when using the ``fetch-mail'' function. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will down-
6932 load messages but also leave them on the POP server.
6934 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b6 _
\bp_
\bo_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
6938 The Mutt Next Generation E-Mail Client 132
6944 The name of your POP server for the ``fetch-mail'' function. You can also
6945 specify an alternative port, username and password, i.e.:
6947 [pop[s]://][username[:password]@]popserver[:port]
6949 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6950 the superuser of your machine may read it regardless of the file's permissions.
6952 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b7 _
\bp_
\bo_
\bp_
\b__
\bl_
\ba_
\bs_
\bt
6960 If this variable is _
\bs_
\be_
\bt, Mutt-ng will try to use the ``LAST'' POP command for
6961 retrieving only unread messages from the POP server when using the ``fetch-
6964 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b8 _
\bp_
\bo_
\bp_
\b__
\bm_
\ba_
\bi_
\bl_
\b__
\bc_
\bh_
\be_
\bc_
\bk
6972 This variable configures how often (in seconds) POP should look for new mail.
6974 _
\b6_
\b._
\b4_
\b._
\b2_
\b0_
\b9 _
\bp_
\bo_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
6982 Specifies the password for your POP account. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will prompt you
6983 for your password when you open POP mailbox.
6985 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
6986 the superuser of your machine may read it regardless of the file's permissions.
6988 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b0 _
\bp_
\bo_
\bp_
\b__
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
6994 The Mutt Next Generation E-Mail Client 133
6998 Controls whether or not Mutt-ng will try to reconnect to a POP server when the
7001 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b1 _
\bp_
\bo_
\bp_
\b__
\bu_
\bs_
\be_
\br
7009 Your login name on the POP server.
7011 This variable defaults to your user name on the local machine.
7013 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b2 _
\bp_
\bo_
\bs_
\bt_
\b__
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7019 Similar to the ``_
\b$_
\ba_
\bt_
\bt_
\br_
\bi_
\bb_
\bu_
\bt_
\bi_
\bo_
\bn (section 6.4.15 , page 84)'' variable, Mutt-ng
7020 will append this string after the inclusion of a message which is being replied
7023 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b3 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
7029 Controls whether or not messages are saved in the ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section
7030 6.4.214 , page 132)'' mailbox when you elect not to send immediately.
7032 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b4 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd
7036 Default: '~/postponed'
7038 Mutt-ng allows you to indefinitely ``_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 6.4.213 , page 132)
7039 sending a message'' which you are editing. When you choose to postpone a mes-
7040 sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the
7041 ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be (section 6.4.213 , page 132)'' variable.
7043 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b5 _
\bp_
\br_
\be_
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt
7049 If _
\bs_
\be_
\bt, a shell command to be executed if Mutt-ng fails to establish a
7051 The Mutt Next Generation E-Mail Client 134
7053 connection to the server. This is useful for setting up secure connections,
7054 e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up
7055 opening the server. Example:
7057 preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
7058 /dev/null > /dev/null'
7060 Mailbox ``foo'' on mailhost.net can now be reached as ``{localhost:1234}foo''.
7062 N
\bNo
\bot
\bte
\be:
\b: For this example to work, you must be able to log in to the remote
7063 machine without having to enter a password.
7065 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b6 _
\bp_
\br_
\bi_
\bn_
\bt
7071 Controls whether or not Mutt-ng really prints messages. This is set to _
\ba_
\bs_
\bk_
\b-_
\bn_
\bo
7072 by default, because some people accidentally hit ``p'' often.
7074 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b7 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7080 This specifies the command pipe that should be used to print messages.
7082 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b8 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bd_
\be_
\bc_
\bo_
\bd_
\be
7088 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7089 message is decoded before it is passed to the external command specified by
7090 _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 6.4.217 , page 133). If this option is _
\bu_
\bn_
\bs_
\be_
\bt, no pro-
7091 cessing will be applied to the message when printing it. The latter setting
7092 may be useful if you are using some advanced printer filter which is able to
7093 properly format e-mail messages for printing.
7095 _
\b6_
\b._
\b4_
\b._
\b2_
\b1_
\b9 _
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bs_
\bp_
\bl_
\bi_
\bt
7101 Used in connection with the print-message command. If this option is _
\bs_
\be_
\bt, the
7102 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 6.4.217 , page 133) is executed
7103 once for each message which is to be printed. If this option is _
\bu_
\bn_
\bs_
\be_
\bt, the
7104 command specified by _
\b$_
\bp_
\br_
\bi_
\bn_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd (section 6.4.217 , page 133) is executed
7105 only once, and all the messages are concatenated, with a form feed as the mes-
7108 The Mutt Next Generation E-Mail Client 135
7110 Those who use the enscript(1) program's mail-printing mode will most likely
7111 want to set this option.
7113 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b0 _
\bp_
\br_
\bo_
\bm_
\bp_
\bt_
\b__
\ba_
\bf_
\bt_
\be_
\br
7119 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ``_
\b$_
\bp_
\ba_
\bg_
\be_
\br (section 6.4.166 , page 121)'', setting this
7120 variable will cause Mutt-ng to prompt you for a command when the pager exits
7121 rather than returning to the index menu. If _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will return to the
7122 index menu when the external pager exits.
7124 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b1 _
\bq_
\bu_
\be_
\br_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7130 This specifies the command that Mutt-ng will use to make external address
7131 queries. The string should contain a %s, which will be substituted with the
7132 query string the user types. See ``_
\bq_
\bu_
\be_
\br_
\by (section 4.7 , page 55)'' for more
7135 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b2 _
\bq_
\bu_
\bi_
\bt
7141 This variable controls whether ``quit'' and ``exit'' actually quit from Mutt-
7142 ng. If it set to _
\by_
\be_
\bs, they do quit, if it is set to _
\bn_
\bo, they have no effect,
7143 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
7146 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b3 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7152 Controls whether or not empty lines will be quoted using ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (sec-
7153 tion 6.4.109 , page 105)''.
7155 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b4 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
7161 Controls how quoted lines will be quoted. If _
\bs_
\be_
\bt, one quote character will be
7162 added to the end of existing prefix. Otherwise, quoted lines will be prepended
7163 by ``_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 6.4.109 , page 105)''.
7165 The Mutt Next Generation E-Mail Client 136
7167 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b5 _
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7169 Type: regular expression
7171 Default: '^([ \t]*[|>:}#])+'
7173 A regular expression used in the internal-pager to determine quoted sections of
7174 text in the body of a message.
7176 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
7177 set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the quote characters at
7178 the beginning of quoted lines.
7180 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b6 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc
7186 If set to a value greater than 0, Mutt-ng will display which message it is cur-
7187 rently on when reading a mailbox. The message is printed after _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc mes-
7188 sages have been read (e.g., if set to 25, Mutt-ng will print a message when it
7189 reads message 25, and then again when it gets to message 50). This variable is
7190 meant to indicate progress when reading large mailboxes which may take some
7191 time. When set to 0, only a single message will appear before the reading the
7194 Also see the ``_
\b$_
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc (section 6.4.339 , page 162)'' variable.
7196 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b7 _
\br_
\be_
\ba_
\bd_
\b__
\bo_
\bn_
\bl_
\by
7202 If set, all folders are opened in read-only mode.
7204 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b8 _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7210 This variable specifies what ``real'' or ``personal'' name should be used when
7213 By default, this is the GECOS field from /etc/passwd.
7215 _
\bN_
\bo_
\bt_
\be_
\b: This variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
7216 _
\b$_
\bf_
\br_
\bo_
\bm (section 6.4.74 , page 97) variable.
7218 _
\b6_
\b._
\b4_
\b._
\b2_
\b2_
\b9 _
\br_
\be_
\bc_
\ba_
\bl_
\bl
7222 The Mutt Next Generation E-Mail Client 137
7226 Controls whether or not Mutt-ng recalls postponed messages when composing a new
7227 message. Also see ``_
\b$_
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd (section 6.4.214 , page 132)''.
7229 Setting this variable to _
\by_
\be_
\bs is not generally useful, and thus not recommended.
7231 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\br_
\be_
\bc_
\bo_
\br_
\bd
7237 This specifies the file into which your outgoing messages should be appended.
7238 (This is meant as the primary method for saving a copy of your messages, but
7239 another way to do this is using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34)'' com-
7240 mand to create a Bcc: header field with your email address in it.)
7242 The value of _
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd _
\b(_
\bs_
\be_
\bc_
\bt_
\bi_
\bo_
\bn _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b0 _
\b, _
\bp_
\ba_
\bg_
\be _
\b1_
\b3_
\b6_
\b) is overridden by the
7243 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.68 , page 96)'' and ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section
7244 6.4.241 , page 138)'' variables, and the ``_
\bf_
\bc_
\bc_
\b-_
\bh_
\bo_
\bo_
\bk (section 3.18 , page
7247 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b1 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp
7249 Type: regular expression
7251 Default: '^(re([\[0-9\]+])*|aw):[ \t]*'
7253 A regular expression used to recognize reply messages when threading and reply-
7254 ing. The default value corresponds to the English ``Re:'' and the German
7257 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b2 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bs_
\be_
\bl_
\bf
7263 If _
\bu_
\bn_
\bs_
\be_
\bt and you are replying to a message sent by you, Mutt-ng will assume
7264 that you want to reply to the recipients of that message rather than to your-
7267 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b3 _
\br_
\be_
\bp_
\bl_
\by_
\b__
\bt_
\bo
7273 If _
\bs_
\be_
\bt, when replying to a message, Mutt-ng will use the address listed in the
7274 ``Reply-To:'' header field as the recipient of the reply. If _
\bu_
\bn_
\bs_
\be_
\bt, it will
7275 use the address in the ``From:'' header field instead.
7277 This option is useful for reading a mailing list that sets the ``Reply-To:''
7279 The Mutt Next Generation E-Mail Client 138
7281 header field to the list address and you want to send a private message to the
7282 author of a message.
7284 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b4 _
\br_
\be_
\bs_
\bo_
\bl_
\bv_
\be
7290 When set, the cursor will be automatically advanced to the next (possibly
7291 undeleted) message whenever a command that modifies the current message is exe-
7294 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b5 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
7300 This variable controls whether or not Mutt-ng will display the ``personal''
7301 name from your aliases in the index menu if it finds an alias that matches the
7302 message's sender. For example, if you have the following alias:
7304 alias juser abd30425@somewhere.net (Joe User)
7306 and then you receive mail which contains the following header:
7308 From: abd30425@somewhere.net
7310 It would be displayed in the index menu as ``Joe User'' instead of
7311 ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is
7312 not human friendly (like CompuServe addresses).
7314 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b6 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be
7320 It may sometimes arrive that you receive mail to a certain machine, move the
7321 messages to another machine, and reply to some the messages from there. If
7322 this variable is _
\bs_
\be_
\bt, the default From: line of the reply messages is built
7323 using the address where you received the messages you are replying to i
\bif
\bf that
7324 address matches your alternates. If the variable is _
\bu_
\bn_
\bs_
\be_
\bt, or the address that
7325 would be used doesn't match your alternates, the From: line will use your
7326 address on the current machine.
7328 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b7 _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7334 This variable fine-tunes the behaviour of the _
\br_
\be_
\bv_
\be_
\br_
\bs_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.236 ,
7336 The Mutt Next Generation E-Mail Client 139
7338 page 137) feature. When it is _
\bs_
\be_
\bt, Mutt-ng will use the address from incoming
7339 messages as-is, possibly including eventual real names. When it is _
\bu_
\bn_
\bs_
\be_
\bt,
7340 Mutt-ng will override any such real names with the setting of the _
\br_
\be_
\ba_
\bl_
\bn_
\ba_
\bm_
\be
7341 (section 6.4.228 , page 135) variable.
7343 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b8 _
\br_
\bf_
\bc_
\b2_
\b0_
\b4_
\b7_
\b__
\bp_
\ba_
\br_
\ba_
\bm_
\be_
\bt_
\be_
\br_
\bs
7349 When this variable is _
\bs_
\be_
\bt, Mutt-ng will decode RFC-2047-encoded MIME parame-
7350 ters. You want to set this variable when Mutt-ng suggests you to save attach-
7351 ments to files named like this:
7353 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
7355 When this variable is _
\bs_
\be_
\bt interactively, the change doesn't have the desired
7356 effect before you have changed folders.
7358 Note that this use of RFC 2047's encoding is explicitly, prohibited by the
7359 standard, but nevertheless encountered in the wild.
7361 Also note that setting this parameter will _
\bn_
\bo_
\bt have the effect that Mutt-ng
7362 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, Mutt-ng will unconditionally use the
7363 encoding specified in RFC 2231.
7365 _
\b6_
\b._
\b4_
\b._
\b2_
\b3_
\b9 _
\bs_
\ba_
\bv_
\be_
\b__
\ba_
\bd_
\bd_
\br_
\be_
\bs_
\bs
7371 If _
\bs_
\be_
\bt, Mutt-ng will take the sender's full address when choosing a default
7372 folder for saving a mail. If ``_
\b$_
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.241 , page 138)'' or
7373 ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.68 , page 96)'' is _
\bs_
\be_
\bt too, the selection of the
7374 fcc folder will be changed as well.
7376 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b0 _
\bs_
\ba_
\bv_
\be_
\b__
\be_
\bm_
\bp_
\bt_
\by
7382 When _
\bu_
\bn_
\bs_
\be_
\bt, mailboxes which contain no saved messages will be removed when
7383 closed (the exception is ``_
\b$_
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be (section 6.4.296 , page 151)'' which is
7384 never removed). If _
\bs_
\be_
\bt, mailboxes are never removed.
7386 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH
7387 and Maildir directories.
7389 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b1 _
\bs_
\ba_
\bv_
\be_
\b__
\bn_
\ba_
\bm_
\be
7393 The Mutt Next Generation E-Mail Client 140
7397 This variable controls how copies of outgoing messages are saved. When set, a
7398 check is made to see if a mailbox specified by the recipient address exists
7399 (this is done by searching for a mailbox in the ``_
\b$_
\bf_
\bo_
\bl_
\bd_
\be_
\br (section 6.4.64 ,
7400 page 94)'' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient address). If the
7401 mailbox exists, the outgoing message will be saved to that mailbox, otherwise
7402 the message is saved to the ``_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd (section 6.4.230 , page 136)'' mailbox.
7404 Also see the ``_
\b$_
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bn_
\ba_
\bm_
\be (section 6.4.68 , page 96)'' variable.
7406 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b2 _
\bs_
\bc_
\bo_
\br_
\be
7412 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be useful to
7413 selectively disable scoring for certain folders when the ``_
\b$_
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\b-
7414 _
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be (section 6.4.243 , page 139)'' variable and friends are used.
7416 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b3 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bd_
\be_
\bl_
\be_
\bt_
\be
7422 Messages which have been assigned a score equal to or lower than the value of
7423 this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng
7424 scores are always greater than or equal to zero, the default setting of this
7425 variable will never mark a message for deletion.
7427 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b4 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\bf_
\bl_
\ba_
\bg
7433 Messages which have been assigned a score greater than or equal to this vari-
7434 able's value are automatically marked ``flagged''.
7436 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b5 _
\bs_
\bc_
\bo_
\br_
\be_
\b__
\bt_
\bh_
\br_
\be_
\bs_
\bh_
\bo_
\bl_
\bd_
\b__
\br_
\be_
\ba_
\bd
7442 Messages which have been assigned a score equal to or lower than the value of
7443 this variable are automatically marked as read by Mutt-ng. Since Mutt-ng
7444 scores are always greater than or equal to zero, the default setting of this
7445 variable will never mark a message read.
7447 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b6 _
\bs_
\be_
\bn_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7449 The Mutt Next Generation E-Mail Client 141
7453 Default: 'us-ascii:iso-8859-1:utf-8'
7455 A list of character sets for outgoing messages. Mutt-ng will use the first
7456 character set into which the text can be converted exactly. If your ``_
\b$_
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt
7457 (section 6.4.24 , page 86)'' is not iso-8859-1 and recipients may not under-
7458 stand UTF-8, it is advisable to include in the list an appropriate widely used
7459 standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either
7460 instead of or after iso-8859-1.
7462 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b7 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl
7466 Default: '/usr/sbin/sendmail -oem -oi'
7468 Specifies the program and arguments used to deliver mail sent by Mutt-ng.
7469 Mutt-ng expects that the specified program interprets additional arguments as
7470 recipient addresses.
7472 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b8 _
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl_
\b__
\bw_
\ba_
\bi_
\bt
7478 Specifies the number of seconds to wait for the ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 6.4.247 ,
7479 page 140)'' process to finish before giving up and putting delivery in the
7482 Mutt-ng interprets the value of this variable as follows:
7485 number of seconds to wait for sendmail to finish before continuing
7488 wait forever for sendmail to finish
7491 always put sendmail in the background without waiting
7493 Note that if you specify a value other than 0, the output of the child process
7494 will be put in a temporary file. If there is some error, you will be informed
7495 as to where to find the output.
7497 _
\b6_
\b._
\b4_
\b._
\b2_
\b4_
\b9 _
\bs_
\bh_
\be_
\bl_
\bl
7503 Command to use when spawning a subshell. By default, the user's login shell
7504 from /etc/passwd is used.
7506 The Mutt Next Generation E-Mail Client 142
7508 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b0 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by
7514 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
7515 6.4.254 , page 142) is _
\bs_
\be_
\bt, this variable specifies the characters at which to
7516 split a folder name into ``hierarchy items.''
7518 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b1 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bd_
\be_
\bl_
\bi_
\bm
7524 This specifies the delimiter between the sidebar (if visible) and other
7527 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b2 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\be_
\bw_
\bm_
\ba_
\bi_
\bl_
\b__
\bo_
\bn_
\bl_
\by
7533 If _
\bs_
\be_
\bt, only folders with new mail will be shown in the sidebar.
7535 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b3 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bn_
\bu_
\bm_
\bb_
\be_
\br_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
7539 Default: '%m%?n?(%n)?%?f?[%f]?'
7541 This variable controls how message counts are printed when the sidebar is
7542 enabled. If this variable is _
\be_
\bm_
\bp_
\bt_
\by (_
\ba_
\bn_
\bd _
\bo_
\bn_
\bl_
\by _
\bi_
\bf), no numbers will be printed
7543 _
\ba_
\bn_
\bd mutt-ng won't frequently count mail (which may be a great speedup esp. with
7544 mbox-style mailboxes.)
7546 The following printf(3)-like sequences are supported all of which may be
7550 Number of deleted messages. 1)
7553 Number of flagged messages.
7556 Total number of messages.
7559 Total number of messages shown, i.e. not hidden by a limit. 1)
7561 The Mutt Next Generation E-Mail Client 143
7564 Number of new messages.
7567 Number of tagged messages. 1)
7569 1) These expandos only have a non-zero value for the current mailbox and will
7570 always be zero otherwise.
7572 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b4 _
\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
7578 When _
\bs_
\be_
\bt, the ``hierarchy'' of the sidebar entries will be shortened only if
7579 they cannot be printed in full length (because ``_
\b$_
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh (section
7580 6.4.256 , page 142)'' is set to a too low value). For example, if the news-
7581 group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
7582 shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not
7585 At which characters this compression is done is controled via the _
\b$_
\bs_
\bi_
\bd_
\be_
\b-
7586 _
\bb_
\ba_
\br_
\b__
\bb_
\bo_
\bu_
\bn_
\bd_
\ba_
\br_
\by (section 6.4.250 , page 140) variable.
7588 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b5 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bv_
\bi_
\bs_
\bi_
\bb_
\bl_
\be
7594 This specifies whether or not to show the sidebar (a list of folders specified
7595 with the ``mailboxes'' command).
7597 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b6 _
\bs_
\bi_
\bd_
\be_
\bb_
\ba_
\br_
\b__
\bw_
\bi_
\bd_
\bt_
\bh
7603 The width of the sidebar.
7605 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b7 _
\bs_
\bi_
\bg_
\b__
\bd_
\ba_
\bs_
\bh_
\be_
\bs
7611 If set, a line containing ``-- '' (dash, dash, space) will be inserted before
7612 your ``_
\b$_
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be (section 6.4.259 , page 143)''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended
7613 that you not unset this variable unless your ``signature'' contains just your
7614 name. The reason for this is because many software packages use ``-- \n'' to
7615 detect your signature.
7617 The Mutt Next Generation E-Mail Client 144
7619 For example, Mutt-ng has the ability to highlight the signature in a different
7620 color in the builtin pager.
7622 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b8 _
\bs_
\bi_
\bg_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
7628 If _
\bs_
\be_
\bt, the signature will be included before any quoted or forwarded text. It
7629 is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable unless you really
7630 know what you are doing, and are prepared to take some heat from netiquette
7633 _
\b6_
\b._
\b4_
\b._
\b2_
\b5_
\b9 _
\bs_
\bi_
\bg_
\bn_
\ba_
\bt_
\bu_
\br_
\be
7637 Default: '~/.signature'
7639 Specifies the filename of your signature, which is appended to all outgoing
7640 messages. If the filename ends with a pipe (``|''), it is assumed that file-
7641 name is a shell command and input should be read from its stdout.
7643 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b0 _
\bs_
\bi_
\bg_
\bn_
\bo_
\bf_
\bf_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg
7649 If _
\bs_
\be_
\bt, this string will be inserted before the signature. This is useful for
7650 people that want to sign off every message they send with their name.
7652 If you want to insert your website's URL, additional contact information or
7653 witty quotes into your mails, better use a signature file instead of the sig-
7656 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b1 _
\bs_
\bi_
\bm_
\bp_
\bl_
\be_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
7660 Default: '~f %s | ~s %s'
7662 Specifies how Mutt-ng should expand a simple search into a real search pattern.
7663 A simple search is one that does not contain any of the ~ operators. See
7664 ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (section 6.2 , page 77)'' for more information on search patterns.
7666 For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
7667 will automatically expand it to the value specified by this variable. For the
7668 default value it would be:
7672 The Mutt Next Generation E-Mail Client 145
7674 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b2 _
\bs_
\bl_
\be_
\be_
\bp_
\b__
\bt_
\bi_
\bm_
\be
7680 Specifies time, in seconds, to pause while displaying certain informational
7681 messages, while moving from folder to folder and after expunging messages from
7682 the current folder. The default is to pause one second, so a value of zero for
7683 this option suppresses the pause.
7685 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b3 _
\bs_
\bm_
\ba_
\br_
\bt_
\b__
\bw_
\br_
\ba_
\bp
7691 Controls the display of lines longer than the screen width in the internal
7692 pager. If _
\bs_
\be_
\bt, long lines are wrapped at a word boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, lines are
7693 simply wrapped at the screen edge. Also see the ``_
\b$_
\bm_
\ba_
\br_
\bk_
\be_
\br_
\bs (section 6.4.121 ,
7694 page 110)'' variable.
7696 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b4 _
\bs_
\bm_
\bi_
\bl_
\be_
\by_
\bs
7698 Type: regular expression
7700 Default: '(>From )|(:[-^]?[][)(><}{|/DP])'
7702 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
7703 ``_
\b$_
\bq_
\bu_
\bo_
\bt_
\be_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 6.4.225 , page 134)'', most notably smileys in the
7706 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b5 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\ba_
\bs_
\bk_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bl_
\ba_
\bb_
\be_
\bl
7712 This flag controls whether you want to be asked to enter a label for a certifi-
7713 cate about to be added to the database or not. It is _
\bs_
\be_
\bt by default. (S/MIME
7716 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b6 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn
7722 This variable contains the name of either a directory, or a file which contains
7723 trusted certificates for use with OpenSSL. (S/MIME only)
7725 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs
7729 The Mutt Next Generation E-Mail Client 146
7733 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage
7734 and retrieval of keys by itself. This is very basic right now, and keys and
7735 certificates are stored in two different directories, both named as the hash-
7736 value retrieved from OpenSSL. There is an index file which contains mailbox-
7737 address keyid pairs, and which can be manually edited. This one points to the
7738 location of the certificates. (S/MIME only)
7740 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7746 This format string specifies a command which is used to decrypt application/x-
7747 pkcs7-mime attachments.
7749 The OpenSSL command formats have their own set of printf(3)-like sequences sim-
7753 Expands to the name of a file containing a message.
7756 Expands to the name of a file containing the signature part of a
7757 multipart/signed attachment when verifying it.
7760 The key-pair specified with _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by (section 6.4.270 ,
7764 One or more certificate IDs.
7767 The algorithm used for encryption.
7770 CA location: Depending on whether _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section
7771 6.4.266 , page 144) points to a directory or file, this expands to
7772 '-CApath _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 6.4.266 , page 144)' or
7773 '-CAfile _
\b$_
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bc_
\ba_
\b__
\bl_
\bo_
\bc_
\ba_
\bt_
\bi_
\bo_
\bn (section 6.4.266 , page 144)'.
7775 For examples on how to configure these formats, see the smime.rc in the sam-
7776 ples/ subdirectory which has been installed on your system alongside the docu-
7777 mentation. (S/MIME only)
7779 _
\b6_
\b._
\b4_
\b._
\b2_
\b6_
\b9 _
\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
7785 The Mutt Next Generation E-Mail Client 147
7787 If _
\bs_
\be_
\bt (default) this tells Mutt-ng to use the default key for decryption. Oth-
7788 erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the
7789 mailbox-address to determine the key to use. It will ask you to supply a key,
7790 if it can't find one. (S/MIME only)
7792 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt_
\b__
\bk_
\be_
\by
7798 This is the default key-pair to use for signing. This must be set to the keyid
7799 (the hash-value that OpenSSL generates) to work properly (S/MIME only)
7801 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b1 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7807 This command is used to create encrypted S/MIME messages. (S/MIME only)
7809 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\be_
\bn_
\bc_
\br_
\by_
\bp_
\bt_
\b__
\bw_
\bi_
\bt_
\bh
7815 This sets the algorithm that should be used for encryption. Valid choices are
7816 ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
7818 If _
\bu_
\bn_
\bs_
\be_
\bt ``_
\b3_
\bd_
\be_
\bs'' (TripleDES) is used. (S/MIME only)
7820 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bg_
\be_
\bt_
\b__
\bc_
\be_
\br_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7826 This command is used to extract X509 certificates from a PKCS7 structure.
7829 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b4 _
\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
7835 This command is used to extract the mail address(es) used for storing X509 cer-
7836 tificates, and for verification purposes (to check whether the certificate was
7837 issued for the sender's mailbox). (S/MIME only)
7839 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b5 _
\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
7841 The Mutt Next Generation E-Mail Client 148
7847 This command is used to extract only the signers X509 certificate from a S/MIME
7848 signature, so that the certificate's owner may get compared to the email's
7849 ``From:'' header field. (S/MIME only)
7851 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b6 _
\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
7857 This command is used to import a certificate via smime_keysng. (S/MIME only)
7859 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b7 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bi_
\bs_
\b__
\bd_
\be_
\bf_
\ba_
\bu_
\bl_
\bt
7865 The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
7866 operations. To override and to use OpenSSL instead this must be _
\bs_
\be_
\bt.
7868 However, this has no effect while replying, since Mutt-ng will automatically
7869 select the same application that was used to sign/encrypt the original message.
7871 (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-
7872 tion 6.4.37 , page 89).) (S/MIME only)
7874 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b8 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bk_
\be_
\by_
\bs
7880 Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage ad
7881 retrieval of keys/certs by itself. This is very basic right now, and stores
7882 keys and certificates in two different directories, both named as the hash-
7883 value retrieved from OpenSSL. There is an index file which contains mailbox-
7884 address keyid pair, and which can be manually edited. This one points to the
7885 location of the private keys. (S/MIME only)
7887 _
\b6_
\b._
\b4_
\b._
\b2_
\b7_
\b9 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bp_
\bk_
\b7_
\bo_
\bu_
\bt_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7893 This command is used to extract PKCS7 structures of S/MIME signatures, in order
7894 to extract the public X509 certificate(s). (S/MIME only)
7896 The Mutt Next Generation E-Mail Client 149
7898 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b0 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bs_
\bi_
\bg_
\bn_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7904 This command is used to created S/MIME signatures of type multipart/signed,
7905 which can be read by all mail clients. (S/MIME only)
7907 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b1 _
\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
7913 This command is used to created S/MIME signatures of type application/x-
7914 pkcs7-signature, which can only be handled by mail clients supporting the
7915 S/MIME extension. (S/MIME only)
7917 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b2 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
7923 The number of seconds after which a cached passphrase will expire if not used.
7926 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b3 _
\bs_
\bm_
\bi_
\bm_
\be_
\b__
\bv_
\be_
\br_
\bi_
\bf_
\by_
\b__
\bc_
\bo_
\bm_
\bm_
\ba_
\bn_
\bd
7932 This command is used to verify S/MIME signatures of type multipart/signed.
7935 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b4 _
\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
7941 This command is used to verify S/MIME signatures of type application/x-
7942 pkcs7-mime. (S/MIME only)
7944 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b5 _
\bs_
\bm_
\bt_
\bp_
\b__
\bh_
\bo_
\bs_
\bt
7952 The Mutt Next Generation E-Mail Client 150
7954 Defines the SMTP host which will be used to deliver mail, as opposed to invok-
7955 ing the sendmail binary. Setting this variable overrides the value of ``_
\b$_
\bs_
\be_
\bn_
\bd_
\b-
7956 _
\bm_
\ba_
\bi_
\bl (section 6.4.247 , page 140)'', and any associated variables.
7958 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b6 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\ba_
\bs_
\bs
7966 Defines the password to use with SMTP AUTH. If ``_
\b$_
\bs_
\bm_
\bt_
\bp_
\b__
\ba_
\bu_
\bt_
\bh_
\b__
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be (section
7967 , page )'' is set, but this variable is not, you will be prompted for a pass-
7970 N
\bNo
\bot
\bte
\be:
\b: Storing passwords in a configuration file presents a security risk since
7971 the superuser of your machine may read it regardless of the file's permissions.
7973 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b7 _
\bs_
\bm_
\bt_
\bp_
\b__
\bp_
\bo_
\br_
\bt
7981 Defines the port that the SMTP host is listening on for mail delivery. Must be
7982 specified as a number.
7984 Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers
7985 will probably desire 587, the mail submission port.
7987 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b8 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs
7993 Availability: SMTP (and SSL)
7995 Defines wether to use STARTTLS. If this option is set to ``_
\br_
\be_
\bq_
\bu_
\bi_
\br_
\be_
\bd'' and the
7996 server does not support STARTTLS or there is an error in the TLS Handshake, the
7997 connection will fail. Setting this to ``_
\be_
\bn_
\ba_
\bb_
\bl_
\be_
\bd'' will try to start TLS and
7998 continue without TLS in case of an error. Muttng still needs to have SSL sup-
7999 port enabled in order to use it.
8001 _
\b6_
\b._
\b4_
\b._
\b2_
\b8_
\b9 _
\bs_
\bm_
\bt_
\bp_
\b__
\bu_
\bs_
\be_
\br
8009 The Mutt Next Generation E-Mail Client 151
8011 Defines the username to use with SMTP AUTH. Setting this variable will cause
8012 Mutt-ng to attempt to use SMTP AUTH when sending.
8014 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b0 _
\bs_
\bo_
\br_
\bt
8020 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
8025 mailbox-order (unsorted)
8033 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8034 (example: set sort=reverse-date-sent).
8036 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b1 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bl_
\bi_
\ba_
\bs
8042 Specifies how the entries in the ``alias'' menu are sorted. The following are
8045 address (sort alphabetically by email address)
8046 alias (sort alphabetically by alias name)
8047 unsorted (leave in order specified in .muttrc)
8049 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b2 _
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8055 When sorting by threads, this variable controls how threads are sorted in rela-
8056 tion to other threads, and how the branches of the thread trees are sorted.
8057 This can be set to any value that ``_
\b$_
\bs_
\bo_
\br_
\bt (section 6.4.290 , page 149)'' can,
8058 except threads (in that case, Mutt-ng will just use date-sent). You can also
8059 specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must
8060 come after reverse-. The last- prefix causes messages to be sorted against its
8062 The Mutt Next Generation E-Mail Client 152
8064 siblings by which has the last descendant, using the rest of sort_aux as an
8067 For instance, set sort_aux=last-date-received would mean that if a new message
8068 is received in a thread, that thread becomes the last one displayed (or the
8069 first, if you have set sort=reverse-threads.)
8071 N
\bNo
\bot
\bte
\be:
\b: For reversed ``_
\b$_
\bs_
\bo_
\br_
\bt (section 6.4.290 , page 149)'' order _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx
8072 (section 6.4.292 , page 150) is reversed again (which is not the right thing
8073 to do, but kept to not break any existing configuration setting).
8075 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b3 _
\bs_
\bo_
\br_
\bt_
\b__
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
8081 Specifies how to sort entries in the file browser. By default, the entries are
8082 sorted alphabetically. Valid values:
8084 alpha (alphabetically)
8089 You may optionally use the ``reverse-'' prefix to specify reverse sorting order
8090 (example: set sort_browser=reverse-date).
8092 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b4 _
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be
8098 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
8099 (section 6.4.311 , page 157)'' _
\bu_
\bn_
\bs_
\be_
\bt. In that case, it changes the heuristic
8100 Mutt-ng uses to thread messages by subject. With _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 6.4.294 ,
8101 page 151) _
\bs_
\be_
\bt, Mutt-ng will only attach a message as the child of another mes-
8102 sage by subject if the subject of the child message starts with a substring
8103 matching the setting of ``_
\b$_
\br_
\be_
\bp_
\bl_
\by_
\b__
\br_
\be_
\bg_
\be_
\bx_
\bp (section 6.4.231 , page 136)''. With
8104 _
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\br_
\be (section 6.4.294 , page 151) _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will attach the message
8105 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
8106 6.4.231 , page 136)'' parts of both messages are identical.
8108 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b5 _
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br
8114 ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section 6.4.295 , page 151)'' controls what happens when
8115 multiple spam headers are matched: if _
\bu_
\bn_
\bs_
\be_
\bt, each successive header will
8117 The Mutt Next Generation E-Mail Client 153
8119 overwrite any previous matches value for the spam label. If _
\bs_
\be_
\bt, each succes-
8120 sive match will append to the previous, using ``_
\bs_
\bp_
\ba_
\bm_
\b__
\bs_
\be_
\bp_
\ba_
\br_
\ba_
\bt_
\bo_
\br (section
8121 6.4.295 , page 151)'' as a separator.
8123 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b6 _
\bs_
\bp_
\bo_
\bo_
\bl_
\bf_
\bi_
\bl_
\be
8129 If your spool mailbox is in a non-default place where Mutt-ng cannot find it,
8130 you can specify its location with this variable. Mutt-ng will automatically
8131 set this variable to the value of the environment variable $MAIL if it is not
8134 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b7 _
\bs_
\bs_
\bl_
\b__
\bc_
\ba_
\b__
\bc_
\be_
\br_
\bt_
\bi_
\bf_
\bi_
\bc_
\ba_
\bt_
\be_
\bs_
\b__
\bf_
\bi_
\bl_
\be
8140 This variable specifies a file containing trusted CA certificates. Any server
8141 certificate that is signed with one of these CA certificates are also automati-
8144 Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
8146 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b8 _
\bs_
\bs_
\bl_
\b__
\bc_
\bl_
\bi_
\be_
\bn_
\bt_
\b__
\bc_
\be_
\br_
\bt
8154 The file containing a client certificate and its associated private key.
8156 _
\b6_
\b._
\b4_
\b._
\b2_
\b9_
\b9 _
\bs_
\bs_
\bl_
\b__
\bf_
\bo_
\br_
\bc_
\be_
\b__
\bt_
\bl_
\bs
8162 If this variable is _
\bs_
\be_
\bt, mutt-ng will require that all connections to remote
8163 servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
8164 server does not advertise the capability, since it would otherwise have to
8165 abort the connection anyway. This option supersedes ``_
\b$_
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs (section
8166 6.4.301 , page 152)''.
8168 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b0 _
\bs_
\bs_
\bl_
\b__
\bm_
\bi_
\bn_
\b__
\bd_
\bh_
\b__
\bp_
\br_
\bi_
\bm_
\be_
\b__
\bb_
\bi_
\bt_
\bs
8174 The Mutt Next Generation E-Mail Client 154
8176 Availability: GNUTLS
8178 This variable specifies the minimum acceptable prime size (in bits) for use in
8179 any Diffie-Hellman key exchange. A value of 0 will use the default from the
8182 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b1 _
\bs_
\bs_
\bl_
\b__
\bs_
\bt_
\ba_
\br_
\bt_
\bt_
\bl_
\bs
8188 Availability: SSL or GNUTLS
8190 If _
\bs_
\be_
\bt (the default), Mutt-ng will attempt to use STARTTLS on servers advertis-
8191 ing the capability. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will not attempt to use STARTTLS
8192 regardless of the server's capabilities.
8194 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b2 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b2
8202 This variables specifies whether to attempt to use SSLv2 in the SSL authentica-
8205 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b3 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bs_
\bs_
\bl_
\bv_
\b3
8211 Availability: SSL or GNUTLS
8213 This variables specifies whether to attempt to use SSLv3 in the SSL authentica-
8216 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b4 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\b__
\bt_
\bl_
\bs_
\bv_
\b1
8222 Availability: SSL or GNUTLS
8224 This variables specifies whether to attempt to use TLSv1 in the SSL authentica-
8227 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b5 _
\bs_
\bs_
\bl_
\b__
\bu_
\bs_
\be_
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bc_
\be_
\br_
\bt_
\bs
8231 The Mutt Next Generation E-Mail Client 155
8237 If set to _
\by_
\be_
\bs, Mutt-ng will use CA certificates in the system-wide certificate
8238 store when checking if server certificate is signed by a trusted CA.
8240 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b6 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8246 Controls the characters used by the ``%r'' indicator in ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (sec-
8247 tion 6.4.307 , page 154)''. The first character is used when the mailbox is
8248 unchanged. The second is used when the mailbox has been changed, and it needs
8249 to be resynchronized. The third is used if the mailbox is in read-only mode, or
8250 if the mailbox will not be written when exiting that mailbox (You can toggle
8251 whether to write changes to a mailbox with the toggle-write operation, bound by
8252 default to ``%''). The fourth is used to indicate that the current folder has
8253 been opened in attach-message mode (Certain operations like composing a new
8254 mail, replying, forwarding, etc. are not permitted in this mode).
8256 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b7 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt
8260 Default: '-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
8261 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
8262 %l?]---(%s/%S)-%>-(%P)---'
8264 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu. This
8265 string is similar to ``_
\b$_
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.110 , page 105)'', but has
8266 its own set of printf(3)-like sequences:
8269 number of mailboxes with new mail *
8272 the short pathname of the current mailbox
8275 number of deleted messages *
8278 the full pathname of the current mailbox
8281 number of flagged messages *
8286 The Mutt Next Generation E-Mail Client 156
8289 size (in bytes) of the current mailbox *
8292 size (in bytes) of the messages shown (i.e., which match the cur-
8296 the number of messages in the mailbox *
8299 the number of messages shown (i.e., which match the current limit)
8303 number of new messages in the mailbox *
8306 number of old unread messages *
8309 number of postponed messages *
8312 percentage of the way through the index
8315 modified/read-only/won't-write/attach-message indicator, according
8316 to _
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bc_
\bh_
\ba_
\br_
\bs (section 6.4.306 , page 154)
8319 current sorting mode (_
\b$_
\bs_
\bo_
\br_
\bt (section 6.4.290 , page 149))
8322 current aux sorting method (_
\b$_
\bs_
\bo_
\br_
\bt_
\b__
\ba_
\bu_
\bx (section 6.4.292 , page
8326 number of tagged messages *
8329 number of unread messages *
8332 Mutt-ng version string
8335 currently active limit pattern, if any *
8338 right justify the rest of the string and pad with 'X'
8341 pad to the end of the line with 'X'
8343 The Mutt Next Generation E-Mail Client 157
8345 * = can be optionally printed if nonzero
8347 Some of the above sequences can be used to optionally print a string if their
8348 value is nonzero. For example, you may only want to see the number of flagged
8349 messages if such messages exist, since zero is not particularly meaningful. To
8350 optionally print a string based upon one of the above sequences, the following
8353 %?<sequence_char>?<optional_string>?
8355 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
8356 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
8357 m
\bma
\bay
\by contain other sequences as well as normal text, but you may n
\bno
\bot
\bt nest
8360 Here is an example illustrating how to optionally print the number of new mes-
8363 %?n?%n new messages.?
8365 Additionally you can switch between two strings, the first one, if a value is
8366 zero, the second one, if the value is nonzero, by using the following con-
8369 %?<sequence_char>?<if_string>&<else_string>?
8371 You can additionally force the result of any printf(3)-like sequence to be low-
8372 ercase by prefixing the sequence character with an underscore (_) sign. For
8373 example, if you want to display the local hostname in lowercase, you would use:
8377 If you prefix the sequence character with a colon (:) character, Mutt-ng will
8378 replace any dots in the expansion by underscores. This might be helpful with
8379 IMAP folders that don't like dots in folder names.
8381 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b8 _
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bo_
\bn_
\b__
\bt_
\bo_
\bp
8387 Setting this variable causes the ``status bar'' to be displayed on the first
8388 line of the screen rather than near the bottom.
8390 _
\b6_
\b._
\b4_
\b._
\b3_
\b0_
\b9 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\ba_
\bi_
\bl_
\bt_
\bo
8396 With mailto: style links, a body as well as arbitrary header information may be
8397 embedded. This may lead to (user) headers being overwriten without note if
8398 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 6.4.54 , page 92)'' is unset.
8400 The Mutt Next Generation E-Mail Client 158
8402 If this variable is _
\bs_
\be_
\bt, mutt-ng is strict and allows anything to be changed.
8403 If it's _
\bu_
\bn_
\bs_
\be_
\bt, all headers given will be prefixed with ``X-Mailto-'' and the
8404 message including headers will be shown in the editor regardless of what
8405 ``_
\b$_
\be_
\bd_
\bi_
\bt_
\b__
\bh_
\be_
\ba_
\bd_
\be_
\br_
\bs (section 6.4.54 , page 92)'' is set to.
8407 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b0 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bm_
\bi_
\bm_
\be
8413 When _
\bu_
\bn_
\bs_
\be_
\bt, non MIME-compliant messages that doesn't have any charset indica-
8414 tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant
8415 messages are often generated by old mailers or buggy mailers like MS Outlook
8416 Express). See also _
\b$_
\ba_
\bs_
\bs_
\bu_
\bm_
\be_
\bd_
\b__
\bc_
\bh_
\ba_
\br_
\bs_
\be_
\bt (section 6.4.11 , page 82).
8418 This option also replaces linear-white-space between encoded-word and *text to
8419 a single space to prevent the display of MIME-encoded ``Subject:'' header field
8420 from being devided into multiple lines.
8422 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b1 _
\bs_
\bt_
\br_
\bi_
\bc_
\bt_
\b__
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs
8428 If _
\bs_
\be_
\bt, threading will only make use of the ``In-Reply-To:'' and ``Refer-
8429 ences:'' header fields when you ``_
\b$_
\bs_
\bo_
\br_
\bt (section 6.4.290 , page 149)'' by mes-
8430 sage threads. By default, messages with the same subject are grouped together
8431 in ``pseudo threads.'' This may not always be desirable, such as in a personal
8432 mailbox where you might have several unrelated messages with the subject ``hi''
8433 which will get grouped together.
8435 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b2 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs
8441 When _
\bs_
\be_
\bt, mutt-ng will remove the trailing part of the ``Subject:'' line which
8442 matches _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx (section 6.4.313 , page 157) when replying. This is
8443 useful to properly react on subject changes and reduce ``subject noise.'' (esp.
8446 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b3 _
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs_
\b__
\br_
\be_
\bg_
\be_
\bx
8448 Type: regular expression
8450 Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$'
8452 When non-empty and _
\b$_
\bs_
\bt_
\br_
\bi_
\bp_
\b__
\bw_
\ba_
\bs (section 6.4.312 , page 157) is _
\bs_
\be_
\bt, mutt-ng
8453 will remove this trailing part of the ``Subject'' line when replying if it
8454 won't be empty afterwards.
8456 The Mutt Next Generation E-Mail Client 159
8458 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b4 _
\bs_
\bt_
\bu_
\bf_
\bf_
\b__
\bq_
\bu_
\bo_
\bt_
\be_
\bd
8464 If _
\bs_
\be_
\bt, attachments with flowed format will have their quoting ``stuffed'',
8465 i.e. a space will be inserted between the quote characters and the actual text.
8467 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b5 _
\bs_
\bu_
\bs_
\bp_
\be_
\bn_
\bd
8473 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp key,
8474 usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com-
8475 mand like ``xterm -e muttng.''
8477 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b6 _
\bt_
\be_
\bx_
\bt_
\b__
\bf_
\bl_
\bo_
\bw_
\be_
\bd
8483 When _
\bs_
\be_
\bt, Mutt-ng will generate text/plain; format=flowed attachments. This
8484 format is easier to handle for some mailing software, and generally just looks
8485 like ordinary text. To actually make use of this format's features, you'll
8486 need support in your editor.
8488 Note that _
\b$_
\bi_
\bn_
\bd_
\be_
\bn_
\bt_
\b__
\bs_
\bt_
\br_
\bi_
\bn_
\bg (section 6.4.109 , page 105) is ignored when this
8491 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b7 _
\bt_
\bh_
\bo_
\br_
\bo_
\bu_
\bg_
\bh_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8497 Affects the ~b and ~h search operations described in section ``_
\bp_
\ba_
\bt_
\bt_
\be_
\br_
\bn_
\bs (sec-
8498 tion 6.2 , page 77)'' above. If _
\bs_
\be_
\bt, the headers and attachments of messages
8499 to be searched are decoded before searching. If _
\bu_
\bn_
\bs_
\be_
\bt, messages are searched
8500 as they appear in the folder.
8502 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b8 _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\b__
\br_
\be_
\bc_
\be_
\bi_
\bv_
\be_
\bd
8508 When _
\bs_
\be_
\bt, Mutt-ng uses the date received rather than the date sent to thread
8509 messages by subject.
8511 The Mutt Next Generation E-Mail Client 160
8513 _
\b6_
\b._
\b4_
\b._
\b3_
\b1_
\b9 _
\bt_
\bi_
\bl_
\bd_
\be
8519 When _
\bs_
\be_
\bt, the internal-pager will pad blank lines to the bottom of the screen
8522 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b0 _
\bt_
\bi_
\bm_
\be_
\bo_
\bu_
\bt
8528 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
8529 pressed in the main menu before timing out and checking for new mail. A value
8530 of zero or less will cause Mutt-ng to never time out.
8532 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b1 _
\bt_
\bm_
\bp_
\bd_
\bi_
\br
8538 This variable allows you to specify where Mutt-ng will place its temporary
8539 files needed for displaying and composing messages. If this variable is not
8540 set, the environment variable $TMPDIR is used. If $TMPDIR is not set then
8543 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b2 _
\bt_
\bo_
\b__
\bc_
\bh_
\ba_
\br_
\bs
8549 Controls the character used to indicate mail addressed to you. The first char-
8550 acter is the one used when the mail is NOT addressed to your address (default:
8551 space). The second is used when you are the only recipient of the message
8552 (default: +). The third is when your address appears in the ``To:'' header
8553 field, but you are not the only recipient of the message (default: T). The
8554 fourth character is used when your address is specified in the ``Cc:'' header
8555 field, but you are not the only recipient. The fifth character is used to
8556 indicate mail that was sent by _
\by_
\bo_
\bu. The sixth character is used to indicate
8557 when a mail was sent to a mailing-list you're subscribe to (default: L).
8559 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b3 _
\bt_
\br_
\ba_
\bs_
\bh
8565 If _
\bs_
\be_
\bt, this variable specifies the path of the trash folder where the mails
8566 marked for deletion will be moved, instead of being irremediably purged.
8568 The Mutt Next Generation E-Mail Client 161
8570 N
\bNo
\bot
\bte
\be: When you delete a message in the trash folder, it is really deleted, so
8571 that there is no way to recover mail.
8573 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b4 _
\bt_
\bu_
\bn_
\bn_
\be_
\bl
8579 Setting this variable will cause Mutt-ng to open a pipe to a command instead of
8580 a raw socket. You may be able to use this to set up preauthenticated connec-
8581 tions to your IMAP/POP3 server. Example:
8583 tunnel='ssh -q mailhost.net /usr/local/libexec/imapd'
8585 N
\bNo
\bot
\bte
\be:
\b: For this example to work you must be able to log in to the remote machine
8586 without having to enter a password.
8588 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b5 _
\bu_
\bm_
\ba_
\bs_
\bk
8594 This sets the umask that will be used by Mutt-ng when creating all kinds of
8595 files. If _
\bu_
\bn_
\bs_
\be_
\bt, the default value is 077.
8597 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b6 _
\bu_
\bn_
\bc_
\bo_
\bl_
\bl_
\ba_
\bp_
\bs_
\be_
\b__
\bj_
\bu_
\bm_
\bp
8603 When _
\bs_
\be_
\bt, Mutt-ng will jump to the next unread message, if any, when the cur-
8604 rent thread is _
\bu_
\bncollapsed.
8606 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b7 _
\bu_
\bs_
\be_
\b__
\b8_
\bb_
\bi_
\bt_
\bm_
\bi_
\bm_
\be
8612 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of sendmail
8613 which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be
8616 When _
\bs_
\be_
\bt, Mutt-ng will invoke ``_
\b$_
\bs_
\be_
\bn_
\bd_
\bm_
\ba_
\bi_
\bl (section 6.4.247 , page 140)'' with
8617 the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation.
8619 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b8 _
\bu_
\bs_
\be_
\b__
\bd_
\bo_
\bm_
\ba_
\bi_
\bn
8625 The Mutt Next Generation E-Mail Client 162
8627 When _
\bs_
\be_
\bt, Mutt-ng will qualify all local addresses (ones without the @host por-
8628 tion) with the value of ``_
\b$_
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be (section 6.4.89 , page 100)''. If _
\bu_
\bn_
\bs_
\be_
\bt,
8629 no addresses will be qualified.
8631 _
\b6_
\b._
\b4_
\b._
\b3_
\b2_
\b9 _
\bu_
\bs_
\be_
\b__
\bf_
\br_
\bo_
\bm
8637 When _
\bs_
\be_
\bt, Mutt-ng will generate the ``From:'' header field when sending mes-
8638 sages. If _
\bu_
\bn_
\bs_
\be_
\bt, no ``From:'' header field will be generated unless the user
8639 explicitly sets one using the ``_
\bm_
\by_
\b__
\bh_
\bd_
\br (section 3.15 , page 34)'' command.
8641 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b0 _
\bu_
\bs_
\be_
\b__
\bi_
\bd_
\bn
8649 When _
\bs_
\be_
\bt, Mutt-ng will show you international domain names decoded.
8651 N
\bNo
\bot
\bte
\be:
\b: You can use IDNs for addresses even if this is _
\bu_
\bn_
\bs_
\be_
\bt. This variable only
8654 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b1 _
\bu_
\bs_
\be_
\b__
\bi_
\bp_
\bv_
\b6
8660 When _
\bs_
\be_
\bt, Mutt-ng will look for IPv6 addresses of hosts it tries to contact.
8661 If this option is _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will restrict itself to IPv4 addresses. Nor-
8662 mally, the default should work.
8664 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b2 _
\bu_
\bs_
\be_
\br_
\b__
\ba_
\bg_
\be_
\bn_
\bt
8670 When _
\bs_
\be_
\bt, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi-
8671 cating which version of Mutt-ng was used for composing them.
8673 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b3 _
\bv_
\bi_
\bs_
\bu_
\ba_
\bl
8679 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in the
8682 The Mutt Next Generation E-Mail Client 163
8684 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b4 _
\bw_
\ba_
\bi_
\bt_
\b__
\bk_
\be_
\by
8690 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-
8691 _
\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.
8693 It is also used when viewing attachments with ``_
\ba_
\bu_
\bt_
\bo_
\b__
\bv_
\bi_
\be_
\bw (section 5.4 , page
8694 74)'', provided that the corresponding mailcap entry has a needsterminal flag,
8695 and the external program is interactive.
8697 When _
\bs_
\be_
\bt, Mutt-ng will always ask for a key. When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt-ng will wait for
8698 a key only if the external command returned a non-zero status.
8700 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b5 _
\bw_
\be_
\be_
\bd
8706 When _
\bs_
\be_
\bt, Mutt-ng will weed headers when displaying, forwarding, printing, or
8707 replying to messages.
8709 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b6 _
\bw_
\br_
\ba_
\bp_
\b__
\bs_
\be_
\ba_
\br_
\bc_
\bh
8715 Controls whether searches wrap around the end of the mailbox.
8717 When _
\bs_
\be_
\bt, searches will wrap around the first (or last) message. When _
\bu_
\bn_
\bs_
\be_
\bt,
8718 searches will not wrap.
8720 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b7 _
\bw_
\br_
\ba_
\bp_
\bm_
\ba_
\br_
\bg_
\bi_
\bn
8726 Controls the size of the margin remaining at the right side of the terminal
8727 when Mutt-ng's pager does smart wrapping.
8729 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b8 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bb_
\bc_
\bc
8735 Controls whether Mutt-ng writes out the Bcc header when preparing messages to
8736 be sent. Exim users may wish to _
\bu_
\bn_
\bs_
\be_
\bt this.
8738 The Mutt Next Generation E-Mail Client 164
8740 _
\b6_
\b._
\b4_
\b._
\b3_
\b3_
\b9 _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
8746 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc messages to
8747 indicate progress. If set to 0, only a single message will be displayed before
8750 Also see the ``_
\b$_
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc (section 6.4.226 , page 135)'' variable.
8752 _
\b6_
\b._
\b4_
\b._
\b3_
\b4_
\b0 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bi_
\bc_
\bo_
\bn
8756 Default: 'M%?n?AIL&ail?'
8758 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-
8759 tion 6.4.342 , page 163) is _
\bs_
\be_
\bt. This string is identical in formatting to the
8760 one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.307 , page 154)''.
8762 _
\b6_
\b._
\b4_
\b._
\b3_
\b4_
\b1 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bl_
\be_
\ba_
\bv_
\be
8768 If _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 6.4.342 , page 163) is _
\bs_
\be_
\bt, this string will be
8769 used to set the title when leaving mutt-ng. For terminal-based programs,
8770 there's no easy and portable way to read the current title so mutt-ng cannot
8771 read it upon startup and restore it when exiting.
8773 Based on the xterm FAQ, the following might work:
8775 set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME |
8778 _
\b6_
\b._
\b4_
\b._
\b3_
\b4_
\b2 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs
8784 Controls whether Mutt-ng sets the xterm title bar and icon name (as long as
8785 you're in an appropriate terminal). The default must be _
\bu_
\bn_
\bs_
\be_
\bt to force in the
8788 _
\b6_
\b._
\b4_
\b._
\b3_
\b4_
\b3 _
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bt_
\bi_
\bt_
\bl_
\be
8792 Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?'
8794 The Mutt Next Generation E-Mail Client 165
8796 Controls the format of the title bar of the xterm provided that
8797 _
\b$_
\bx_
\bt_
\be_
\br_
\bm_
\b__
\bs_
\be_
\bt_
\b__
\bt_
\bi_
\bt_
\bl_
\be_
\bs (section 6.4.342 , page 163) has been _
\bs_
\be_
\bt. This string is
8798 identical in formatting to the one used by ``_
\b$_
\bs_
\bt_
\ba_
\bt_
\bu_
\bs_
\b__
\bf_
\bo_
\br_
\bm_
\ba_
\bt (section 6.4.307 ,
8801 _
\b6_
\b._
\b5 _
\bF_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn_
\bs
8803 The following is the list of available functions listed by the mapping in which
8804 they are available. The default key setting is given, and an explanation of
8805 what the function does. The key bindings of these functions can be changed
8806 with the _
\bb_
\bi_
\bn_
\bd (section 3.4 , page 24) command.
8808 _
\b6_
\b._
\b5_
\b._
\b1 _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc
8810 The _
\bg_
\be_
\bn_
\be_
\br_
\bi_
\bc menu is not a real menu, but specifies common functions (such as
8811 movement) available in all menus except for _
\bp_
\ba_
\bg_
\be_
\br and _
\be_
\bd_
\bi_
\bt_
\bo_
\br. Changing set-
8812 tings for this menu will affect the default bindings for all menus (except as
8815 bottom-page L move to the bottom of the page
8816 current-bottom not bound move current entry to bottom of page
8817 current-middle not bound move current entry to middle of page
8818 current-top not bound move current entry to top of page
8819 enter-command : enter a muttngrc command
8820 exit q exit this menu
8821 first-entry = move to the first entry
8822 half-down ] scroll down 1/2 page
8823 half-up [ scroll up 1/2 page
8825 jump number jump to an index number
8826 last-entry * move to the last entry
8827 middle-page M move to the middle of the page
8828 next-entry j move to the next entry
8829 next-line > scroll down one line
8830 next-page z move to the next page
8831 previous-entry k move to the previous entry
8832 previous-line < scroll up one line
8833 previous-page Z move to the previous page
8834 refresh ^L clear and redraw the screen
8835 search / search for a regular expression
8836 search-next n search for next match
8837 search-opposite not bound search for next match in opposite direction
8838 search-reverse ESC / search backwards for a regular expression
8839 select-entry RET select the current entry
8840 shell-escape ! run a program in a subshell
8841 tag-entry t toggle the tag on the current entry
8842 tag-prefix ; apply next command to tagged entries
8843 tag-prefix-cond not bound apply next function ONLY to tagged messages
8844 top-page H move to the top of the page
8845 what-key not bound display the keycode for a key press
8847 The Mutt Next Generation E-Mail Client 166
8849 _
\b6_
\b._
\b5_
\b._
\b2 _
\bi_
\bn_
\bd_
\be_
\bx
8851 The Mutt Next Generation E-Mail Client 167
8853 bounce-message b remail a message to another user
8854 change-folder c open a different folder
8855 change-folder-readonly ESC c open a different folder in read only mode
8856 check-traditional-pgp ESC P check for classic pgp
8857 clear-flag W clear a status flag from a message
8858 copy-message C copy a message to a file/mailbox
8859 create-alias a create an alias from a message sender
8860 decode-copy ESC C decode a message and copy it to a file/mailbox
8861 decode-save ESC s decode a message and save it to a file/mailbox
8862 delete-message d delete the current entry
8863 delete-pattern D delete messages matching a pattern
8864 delete-subthread ESC d delete all messages in subthread
8865 delete-thread ^D delete all messages in thread
8866 display-address @ display full address of sender
8867 display-toggle-weed h display message and toggle header weeding
8868 display-message RET display a message
8869 edit e edit the current message
8870 edit-type ^E edit the current message's Content-Type
8871 exit x exit without saving changes
8872 extract-keys ^K extract PGP public keys
8873 fetch-mail G retrieve mail from POP server
8874 flag-message F toggle a message's 'important' flag
8875 forget-passphrase ^F wipe PGP passphrase from memory
8876 forward-message f forward a message with comments
8877 group-reply g reply to all recipients
8878 limit l show only messages matching a pattern
8879 list-reply L reply to specified mailing list
8880 mail m compose a new mail message
8881 mail-key ESC k mail a PGP public key
8882 next-new TAB jump to the next new message
8883 next-subthread ESC n jump to the next subthread
8884 next-thread ^N jump to the next thread
8885 next-undeleted j move to the next undeleted message
8886 next-unread not bound jump to the next unread message
8887 parent-message P jump to parent message in thread
8888 pipe-message | pipe message/attachment to a shell command
8889 previous-new ESC TAB jump to the previous new message
8890 previous-page Z move to the previous page
8891 previous-subthread ESC p jump to previous subthread
8892 previous-thread ^P jump to previous thread
8893 previous-undeleted k move to the last undelete message
8894 previous-unread not bound jump to the previous unread message
8895 print-message p print the current entry
8896 query Q query external program for addresses
8897 quit q save changes to mailbox and quit
8898 read-subthread ESC r mark the current subthread as read
8899 read-thread ^R mark the current thread as read
8900 recall-message R recall a postponed message
8901 reply r reply to a message
8902 resend-message ESC e resend message and preserve MIME structure
8903 save-message s save message/attachment to a file
8904 set-flag w set a status flag on a message
8905 show-version V show the Mutt-ng version number and date
8906 show-limit ESC l show currently active limit pattern, if any
8908 The Mutt Next Generation E-Mail Client 168
8910 sort-mailbox o sort messages
8911 sort-reverse O sort messages in reverse order
8912 sync-mailbox $ save changes to mailbox
8913 tag-pattern T tag messages matching a pattern
8914 tag-thread ESC t tag/untag all messages in the current thread
8915 toggle-new N toggle a message's 'new' flag
8916 toggle-write % toggle whether the mailbox will be rewritten
8917 undelete-message u undelete the current entry
8918 undelete-pattern U undelete messages matching a pattern
8919 undelete-subthread ESC u undelete all messages in subthread
8920 undelete-thread ^U undelete all messages in thread
8921 untag-pattern ^T untag messages matching a pattern
8922 view-attachments v show MIME attachments
8924 _
\b6_
\b._
\b5_
\b._
\b3 _
\bp_
\ba_
\bg_
\be_
\br
8926 The Mutt Next Generation E-Mail Client 169
8928 bottom not bound jump to the bottom of the message
8929 bounce-message b remail a message to another user
8930 change-folder c open a different folder
8931 change-folder-readonly ESC c open a different folder in read only mode
8932 check-traditional-pgp ESC P check for classic pgp
8933 copy-message C copy a message to a file/mailbox
8934 create-alias a create an alias from a message sender
8935 decode-copy ESC C decode a message and copy it to a file/mailbox
8936 decode-save ESC s decode a message and save it to a file/mailbox
8937 delete-message d delete the current entry
8938 delete-subthread ESC d delete all messages in subthread
8939 delete-thread ^D delete all messages in thread
8940 display-address @ display full address of sender
8941 display-toggle-weed h display message and toggle header weeding
8942 edit e edit the current message
8943 edit-type ^E edit the current message's Content-Type
8944 enter-command : enter a muttngrc command
8945 exit i return to the main-menu
8946 extract-keys ^K extract PGP public keys
8947 flag-message F toggle a message's 'important' flag
8948 forget-passphrase ^F wipe PGP passphrase from memory
8949 forward-message f forward a message with comments
8950 group-reply g reply to all recipients
8951 half-up not bound move up one-half page
8952 half-down not bound move down one-half page
8954 list-reply L reply to specified mailing list
8955 mail m compose a new mail message
8956 mail-key ESC k mail a PGP public key
8957 mark-as-new N toggle a message's 'new' flag
8958 next-line RET scroll down one line
8959 next-entry J move to the next entry
8960 next-new TAB jump to the next new message
8961 next-page move to the next page
8962 next-subthread ESC n jump to the next subthread
8963 next-thread ^N jump to the next thread
8964 next-undeleted j move to the next undeleted message
8965 next-unread not bound jump to the next unread message
8966 parent-message P jump to parent message in thread
8967 pipe-message | pipe message/attachment to a shell command
8968 previous-line BackSpace scroll up one line
8969 previous-entry K move to the previous entry
8970 previous-new not bound jump to the previous new message
8971 previous-page - move to the previous page
8972 previous-subthread ESC p jump to previous subthread
8973 previous-thread ^P jump to previous thread
8974 previous-undeleted k move to the last undelete message
8975 previous-unread not bound jump to the previous unread message
8976 print-message p print the current entry
8977 quit Q save changes to mailbox and quit
8978 read-subthread ESC r mark the current subthread as read
8979 read-thread ^R mark the current thread as read
8980 recall-message R recall a postponed message
8981 redraw-screen ^L clear and redraw the screen
8983 The Mutt Next Generation E-Mail Client 170
8985 reply r reply to a message
8986 save-message s save message/attachment to a file
8987 search / search for a regular expression
8988 search-next n search for next match
8989 search-opposite not bound search for next match in opposite direction
8990 search-reverse ESC / search backwards for a regular expression
8991 search-toggle \ toggle search pattern coloring
8992 shell-escape ! invoke a command in a subshell
8993 show-version V show the Mutt-ng version number and date
8994 skip-quoted S skip beyond quoted text
8995 sync-mailbox $ save changes to mailbox
8996 tag-message t tag a message
8997 toggle-quoted T toggle display of quoted text
8998 top ^ jump to the top of the message
8999 undelete-message u undelete the current entry
9000 undelete-subthread ESC u undelete all messages in subthread
9001 undelete-thread ^U undelete all messages in thread
9002 view-attachments v show MIME attachments
9004 _
\b6_
\b._
\b5_
\b._
\b4 _
\ba_
\bl_
\bi_
\ba_
\bs
9006 search / search for a regular expression
9007 search-next n search for next match
9008 search-reverse ESC / search backwards for a regular expression
9010 _
\b6_
\b._
\b5_
\b._
\b5 _
\bq_
\bu_
\be_
\br_
\by
9012 create-alias a create an alias from a message sender
9013 mail m compose a new mail message
9014 query Q query external program for addresses
9015 query-append A append new query results to current results
9016 search / search for a regular expression
9017 search-next n search for next match
9018 search-opposite not bound search for next match in opposite direction
9019 search-reverse ESC / search backwards for a regular expression
9021 _
\b6_
\b._
\b5_
\b._
\b6 _
\ba_
\bt_
\bt_
\ba_
\bc_
\bh
9023 The Mutt Next Generation E-Mail Client 171
9025 bounce-message b remail a message to another user
9026 collapse-parts v toggle display of subparts
9027 delete-entry d delete the current entry
9028 display-toggle-weed h display message and toggle header weeding
9029 edit-type ^E edit the current entry's Content-Type
9030 extract-keys ^K extract PGP public keys
9031 forward-message f forward a message with comments
9032 group-reply g reply to all recipients
9033 list-reply L reply to specified mailing list
9034 pipe-entry | pipe message/attachment to a shell command
9035 print-entry p print the current entry
9036 reply r reply to a message
9037 resend-message ESC e resend message and preserve MIME structure
9038 save-entry s save message/attachment to a file
9039 undelete-entry u undelete the current entry
9040 view-attach RET view attachment using mailcap entry if necessary
9041 view-mailcap m force viewing of attachment using mailcap
9042 view-text T view attachment as text
9044 _
\b6_
\b._
\b5_
\b._
\b7 _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
9046 The Mutt Next Generation E-Mail Client 172
9048 attach-file a attach a file(s) to this message
9049 attach-message A attach message(s) to this message
9050 attach-key ESC k attach a PGP public key
9051 copy-file C save message/attachment to a file
9052 detach-file D delete the current entry
9053 display-toggle-weed h display message and toggle header weeding
9054 edit-bcc b edit the BCC list
9055 edit-cc c edit the CC list
9056 edit-description d edit attachment description
9057 edit-encoding ^E edit attachment transfer-encoding
9058 edit-fcc f enter a file to save a copy of this message in
9059 edit-from ESC f edit the from: field
9060 edit-file ^X e edit the file to be attached
9061 edit-headers E edit the message with headers
9062 edit e edit the message
9063 edit-mime m edit attachment using mailcap entry
9064 edit-reply-to r edit the Reply-To field
9065 edit-subject s edit the subject of this message
9066 edit-to t edit the TO list
9067 edit-type ^T edit attachment type
9068 filter-entry F filter attachment through a shell command
9069 forget-passphrase ^F wipe PGP passphrase from memory
9070 ispell i run ispell on the message
9071 new-mime n compose new attachment using mailcap entry
9072 pgp-menu p show PGP options
9073 pipe-entry | pipe message/attachment to a shell command
9074 postpone-message P save this message to send later
9075 print-entry l print the current entry
9076 rename-file R rename/move an attached file
9077 send-message y send the message
9078 toggle-unlink u toggle whether to delete file after sending it
9079 view-attach RET view attachment using mailcap entry if necessary
9080 write-fcc w write the message to a folder
9082 _
\b6_
\b._
\b5_
\b._
\b8 _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be
9084 delete-entry d delete the current entry
9085 undelete-entry u undelete the current entry
9087 _
\b6_
\b._
\b5_
\b._
\b9 _
\bb_
\br_
\bo_
\bw_
\bs_
\be_
\br
9089 The Mutt Next Generation E-Mail Client 173
9091 change-dir c change directories
9092 check-new TAB check mailboxes for new mail
9093 enter-mask m enter a file mask
9094 search / search for a regular expression
9095 search-next n search for next match
9096 search-reverse ESC / search backwards for a regular expression
9097 select-new N select a new file in this directory
9098 sort o sort messages
9099 sort-reverse O sort messages in reverse order
9100 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
9101 view-file SPACE view file
9102 subscribe s subscribe to current mailbox (IMAP Only)
9103 unsubscribe u unsubscribe to current mailbox (IMAP Only)
9104 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
9106 _
\b6_
\b._
\b5_
\b._
\b1_
\b0 _
\bp_
\bg_
\bp
9108 view-name % view the key's user id
9109 verify-key c verify a PGP public key
9111 _
\b6_
\b._
\b5_
\b._
\b1_
\b1 _
\be_
\bd_
\bi_
\bt_
\bo_
\br
9113 backspace BackSpace delete the char in front of the cursor
9114 backward-char ^B move the cursor one character to the left
9115 backward-word ESC b move the cursor to the previous word
9116 bol ^A jump to the beginning of the line
9117 buffy-cycle Space cycle among incoming mailboxes
9118 capitalize-word ESC c uppercase the first character in the word
9119 complete TAB complete filename or alias
9120 complete-query ^T complete address with query
9121 delete-char ^D delete the char under the cursor
9122 downcase-word ESC l lowercase all characters in current word
9123 eol ^E jump to the end of the line
9124 forward-char ^F move the cursor one character to the right
9125 forward-word ESC f move the cursor to the next word
9126 history-down not bound scroll down through the history list
9127 history-up not bound scroll up through the history list
9128 kill-eol ^K delete chars from cursor to end of line
9129 kill-eow ESC d delete chars from cursor to end of word
9130 kill-line ^U delete all chars on the line
9131 kill-word ^W delete the word in front of the cursor
9132 quote-char ^V quote the next typed key
9133 transpose-chars not bound transpose character under cursor with previous
9134 upcase-word ESC u uppercase all characters in current word
9136 _
\b7_
\b. _
\bM_
\bi_
\bs_
\bc_
\be_
\bl_
\bl_
\ba_
\bn_
\by
9138 The Mutt Next Generation E-Mail Client 174
9140 _
\b7_
\b._
\b1 _
\bA_
\bc_
\bk_
\bn_
\bo_
\bw_
\bl_
\be_
\bd_
\bg_
\bm_
\be_
\bn_
\bt_
\bs
9142 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME parsing code
9143 back in the ELM-ME days.
9145 The following people have been very helpful to the development of Mutt:
9147 Vikas Agnihotri <vikasa@writeme.com>,
9149 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
9151 Aric Blumer <aric@fore.com>,
9153 John Capo <jc@irbs.com>,
9155 David Champion <dgc@uchicago.edu,
9157 Brendan Cully <brendan@kublai.com>,
9159 Liviu Daia <daia@stoilow.imar.ro>,
9161 Thomas E. Dickey <dickey@herndon4.his.com>,
9163 David DeSimone <fox@convex.hp.com>,
9165 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
9167 Ruslan Ermilov <ru@freebsd.org>,
9169 Edmund Grimley Evans <edmundo@rano.org,
9171 Michael Finken <finken@conware.de>,
9173 Sven Guckes <guckes@math.fu-berlin.de>,
9175 Lars Hecking <lhecking@nmrc.ie>,
9177 Mark Holloman <holloman@nando.net>,
9179 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
9181 Marco d'Itri <md@linux.it>,
9183 Bjrn Jacke <bjacke@suse.com>,
9185 Byrial Jensen <byrial@image.dk>,
9187 David Jeske <jeske@igcom.net>,
9189 Christophe Kalt <kalt@hugo.int-evry.fr>,
9191 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
9193 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
9195 The Mutt Next Generation E-Mail Client 175
9197 Brandon Long <blong@fiction.net>,
9199 Jimmy Mkel <jmy@flashback.net>,
9201 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
9203 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
9205 Andrew W. Nosenko <awn@bcs.zp.ua>,
9207 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
9209 Clint Olsen <olsenc@ichips.intel.com>,
9211 Park Myeong Seok <pms@romance.kaist.ac.kr>,
9213 Thomas Parmelan <tom@ankh.fr.eu.org>,
9215 Ollivier Robert <roberto@keltia.freenix.fr>,
9217 Thomas Roessler <roessler@does-not-exist.org>,
9219 Roland Rosenfeld <roland@spinnaker.de>,
9221 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
9223 Allain Thivillon <Allain.Thivillon@alma.fr>,
9225 Gero Treuner <gero@faveve.uni-stuttgart.de>,
9227 Vsevolod Volkov <vvv@lucky.net>,
9229 Ken Weinert <kenw@ihs.com>
9231 Mutt-ng is developed by the following people:
9233 Andreas Krennmair <ak@synflood.at>
9235 Nico Golde <nico@ngolde.de>
9237 Rocco Rutte <pdmef@cs.tu-berlin.de>
9239 The following people have been very helpful to the development of Mutt-ng:
9241 Christian Gall <cg@cgall.de>
9243 Iain Lea <iain@bricbrac.de>
9245 Andreas Kneib <akneib@gmx.net>
9247 Carsten Schoelzki <cjs@weisshuhn.de>
9249 Elimar Riesebieter <riesebie@lxtec.de>
9251 The Mutt Next Generation E-Mail Client 176
9253 _
\b7_
\b._
\b2 _
\bA_
\bb_
\bo_
\bu_
\bt _
\bt_
\bh_
\bi_
\bs _
\bd_
\bo_
\bc_
\bu_
\bm_
\be_
\bn_
\bt
9255 This document was written in SGML, and then rendered using the sgml-tools pack-
9258 The Mutt Next Generation E-Mail Client 177
9262 1. Introduction .......................................................... 1
9263 1.1 Overview ........................................................ 1
9264 1.2 Mutt-ng Home Page ............................................... 1
9265 1.3 Mailing Lists ................................................... 1
9266 1.4 Software Distribution Sites ..................................... 2
9267 1.5 IRC ............................................................. 2
9268 1.6 Weblog .......................................................... 2
9269 1.7 Copyright ....................................................... 2
9271 2. Getting Started ..................................................... 2
9272 2.1 Basic Concepts .............................................. 2
9273 2.1.1 Screens and Menus 3
9274 2.1.2 Configuration 3
9277 2.1.5 Modularization 4
9279 2.2 Screens and Menus ........................................... 4
9282 2.2.3 File Browser 5
9285 2.2.6 Compose Menu 6
9287 2.2.8 Attachment Menu 6
9289 2.3 Moving Around in Menus .......................................... 6
9290 2.4 Editing Input Fields ............................................ 7
9291 2.5 Reading Mail - The Index and Pager .............................. 8
9292 2.5.1 The Message Index 8
9294 2.5.3 Threaded Mode 11
9295 2.5.4 Miscellaneous Functions 11
9296 2.6 Sending Mail ................................................... 14
9297 2.6.1 Composing new messages 14
9299 2.6.3 Editing the message header 17
9300 2.6.4 Using Mutt-ng with PGP 18
9301 2.6.5 Sending anonymous messages via mixmaster 19
9302 2.7 Forwarding and Bouncing Mail ................................... 19
9303 2.8 Postponing Mail ................................................ 20
9305 3. Configuration ........................................................ 21
9306 3.1 Locations of Configuration Files ............................... 21
9307 3.2 Syntax of Initialization Files ................................. 21
9308 3.3 Defining/Using aliases ......................................... 23
9309 3.4 Changing the default key bindings .............................. 24
9310 3.5 Defining aliases for character sets ........................... 26
9314 3.6 Setting variables based upon mailbox ........................... 26
9315 3.7 Keyboard macros ................................................ 27
9316 3.8 Using color and mono video attributes .......................... 28
9317 3.9 Ignoring (weeding) unwanted message headers .................... 30
9318 3.10 Alternative addresses .......................................... 31
9319 3.11 Format = Flowed ................................................ 31
9320 3.12 Mailing lists .................................................. 32
9321 3.13 Using Multiple spool mailboxes ................................. 33
9322 3.14 Defining mailboxes which receive mail .......................... 34
9323 3.15 User defined headers ........................................... 34
9324 3.16 Defining the order of headers when viewing messages ............ 35
9325 3.17 Specify default save filename .................................. 35
9326 3.18 Specify default Fcc: mailbox when composing .................... 36
9327 3.19 Specify default save filename and default Fcc: mailbox at once . 36
9328 3.20 Change settings based upon message recipients .................. 36
9329 3.21 Change settings before formatting a message .................... 37
9330 3.22 Choosing the cryptographic key of the recipient ................ 37
9331 3.23 Adding key sequences to the keyboard buffer .................... 38
9332 3.24 Executing functions ............................................ 38
9333 3.25 Message Scoring ................................................ 38
9334 3.26 Spam detection ................................................. 39
9335 3.27 Setting variables .............................................. 41
9336 3.28 Reading initialization commands from another file .............. 42
9337 3.29 Removing hooks ................................................. 42
9338 3.30 Sharing Setups ............................................. 43
9339 3.30.1 Character Sets 43
9340 3.30.2 Modularization 43
9341 3.30.3 Conditional parts 43
9343 4. Advanced Usage ....................................................... 45
9344 4.1 Regular Expressions ............................................ 45
9345 4.2 Patterns ....................................................... 48
9346 4.2.1 Complex Patterns 48
9347 4.2.2 Patterns and Dates 49
9348 4.3 Format Strings ............................................. 50
9349 4.3.1 Introduction 50
9350 4.3.2 Conditional Expansion 51
9351 4.3.3 Modifications and Padding 52
9352 4.4 Using Tags ..................................................... 53
9353 4.5 Using Hooks .................................................... 53
9354 4.5.1 Message Matching in Hooks 54
9355 4.6 Using the sidebar .............................................. 54
9356 4.7 External Address Queries ....................................... 55
9357 4.8 Mailbox Formats ................................................ 56
9358 4.9 Mailbox Shortcuts .............................................. 57
9359 4.10 Handling Mailing Lists ......................................... 57
9360 4.11 Editing threads ................................................ 59
9361 4.11.1 Linking threads 59
9362 4.11.2 Breaking threads 59
9363 4.12 Delivery Status Notification (DSN) Support ..................... 59
9364 4.13 POP3 Support (OPTIONAL) ........................................ 59
9365 4.14 IMAP Support (OPTIONAL) ........................................ 60
9366 4.14.1 The Folder Browser 61
9370 4.14.2 Authentication 61
9371 4.15 NNTP Support (OPTIONAL) ........................................ 62
9372 4.15.1 Again: Scoring 62
9373 4.16 SMTP Support (OPTIONAL) ........................................ 63
9374 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 63
9375 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64
9376 4.19 Compressed folders Support (OPTIONAL) .......................... 64
9377 4.19.1 Open a compressed mailbox for reading 65
9378 4.19.2 Write a compressed mailbox 65
9379 4.19.3 Append a message to a compressed mailbox 66
9380 4.19.4 Encrypted folders 66
9382 5. Mutt-ng's MIME Support ............................................... 67
9383 5.1 Using MIME in Mutt ............................................. 67
9384 5.1.1 Viewing MIME messages in the pager 67
9385 5.1.2 The Attachment Menu 67
9386 5.1.3 The Compose Menu 68
9387 5.2 MIME Type configuration with mime.types ........................ 68
9388 5.3 MIME Viewer configuration with mailcap ......................... 69
9389 5.3.1 The Basics of the mailcap file 69
9390 5.3.2 Secure use of mailcap 71
9391 5.3.3 Advanced mailcap Usage 71
9392 5.3.4 Example mailcap files 74
9393 5.4 MIME Autoview .................................................. 75
9394 5.5 MIME Multipart/Alternative ..................................... 76
9395 5.6 MIME Lookup .................................................... 76
9397 6. Reference ............................................................ 77
9398 6.1 Command line options ........................................... 77
9399 6.2 Patterns ....................................................... 78
9400 6.3 Configuration Commands ......................................... 79
9401 6.4 Configuration variables .......................................... 81
9402 6.4.1 abort_nosubject 81
9403 6.4.2 abort_unmodified 81
9405 6.4.4 alias_format 81
9408 6.4.7 arrow_cursor 82
9409 6.4.8 ascii_chars 83
9412 6.4.11 assumed_charset 83
9413 6.4.12 attach_format 83
9414 6.4.13 attach_sep 84
9415 6.4.14 attach_split 85
9416 6.4.15 attribution 85
9422 6.4.21 bounce_delivered 86
9426 6.4.22 braille_friendly 86
9427 6.4.23 certificate_file 86
9430 6.4.26 collapse_unread 87
9431 6.4.27 compose_format 87
9432 6.4.28 config_charset 88
9433 6.4.29 confirmappend 88
9434 6.4.30 confirmcreate 88
9435 6.4.31 connect_timeout 88
9436 6.4.32 content_type 88
9438 6.4.34 crypt_autoencrypt 89
9439 6.4.35 crypt_autopgp 89
9440 6.4.36 crypt_autosign 89
9441 6.4.37 crypt_autosmime 90
9442 6.4.38 crypt_replyencrypt 90
9443 6.4.39 crypt_replysign 90
9444 6.4.40 crypt_replysignencrypted 90
9445 6.4.41 crypt_timestamp 90
9446 6.4.42 crypt_use_gpgme 91
9447 6.4.43 crypt_verify_sig 91
9448 6.4.44 date_format 91
9449 6.4.45 default_hook 91
9451 6.4.47 delete_untag 92
9452 6.4.48 digest_collapse 92
9453 6.4.49 display_filter 92
9454 6.4.50 dotlock_program 92
9455 6.4.51 dsn_notify 93
9456 6.4.52 dsn_return 93
9457 6.4.53 duplicate_threads 93
9458 6.4.54 edit_headers 93
9460 6.4.56 encode_from 94
9461 6.4.57 entropy_file 94
9462 6.4.58 envelope_from 94
9464 6.4.60 fast_reply 94
9465 6.4.61 fcc_attach 95
9467 6.4.63 file_charset 95
9469 6.4.65 folder_format 96
9470 6.4.66 followup_to 96
9471 6.4.67 force_buffy_check 97
9472 6.4.68 force_name 97
9473 6.4.69 forward_decode 97
9474 6.4.70 forward_decrypt 97
9475 6.4.71 forward_edit 98
9476 6.4.72 forward_format 98
9477 6.4.73 forward_quote 98
9482 6.4.75 gecos_mask 98
9485 6.4.78 header_cache 99
9486 6.4.79 header_cache_compress 100
9488 6.4.81 hidden_host 100
9489 6.4.82 hide_limited 100
9490 6.4.83 hide_missing 100
9491 6.4.84 hide_thread_subject 101
9492 6.4.85 hide_top_limited 101
9493 6.4.86 hide_top_missing 101
9495 6.4.88 honor_followup_to 101
9497 6.4.90 ignore_list_reply_to 102
9498 6.4.91 imap_authenticators 102
9499 6.4.92 imap_check_subscribed 102
9500 6.4.93 imap_delim_chars 102
9501 6.4.94 imap_headers 103
9502 6.4.95 imap_home_namespace 103
9503 6.4.96 imap_keepalive 103
9504 6.4.97 imap_list_subscribed 104
9505 6.4.98 imap_login 104
9506 6.4.99 imap_mail_check 104
9507 6.4.100 imap_pass 104
9508 6.4.101 imap_passive 105
9509 6.4.102 imap_peek 105
9510 6.4.103 imap_reconnect 105
9511 6.4.104 imap_servernoise 105
9512 6.4.105 imap_user 105
9513 6.4.106 implicit_autoview 106
9515 6.4.108 include_onlyfirst 106
9516 6.4.109 indent_string 106
9517 6.4.110 index_format 106
9519 6.4.112 keep_flagged 109
9520 6.4.113 list_reply 109
9522 6.4.115 mail_check 110
9523 6.4.116 mailcap_path 110
9524 6.4.117 mailcap_sanitize 110
9525 6.4.118 maildir_header_cache_verify 110
9526 6.4.119 maildir_trash 111
9527 6.4.120 mark_old 111
9530 6.4.123 max_line_length 112
9532 6.4.125 mbox_type 112
9533 6.4.126 menu_context 112
9534 6.4.127 menu_move_off 112
9538 6.4.128 menu_scroll 112
9539 6.4.129 message_format 113
9540 6.4.130 meta_key 113
9542 6.4.132 mh_purge 113
9543 6.4.133 mh_seq_flagged 113
9544 6.4.134 mh_seq_replied 114
9545 6.4.135 mh_seq_unseen 114
9546 6.4.136 mime_forward 114
9547 6.4.137 mime_forward_decode 114
9548 6.4.138 mime_forward_rest 114
9549 6.4.139 mix_entry_format 114
9550 6.4.140 mixmaster 115
9552 6.4.142 msgid_format 115
9553 6.4.143 narrow_tree 116
9554 6.4.144 nntp_ask_followup_to 117
9555 6.4.145 nntp_ask_x_comment_to 117
9556 6.4.146 nntp_cache_dir 117
9557 6.4.147 nntp_catchup 117
9558 6.4.148 nntp_context 117
9559 6.4.149 nntp_followup_to_poster 118
9560 6.4.150 nntp_group_index_format 118
9561 6.4.151 nntp_host 118
9562 6.4.152 nntp_inews 119
9563 6.4.153 nntp_load_description 119
9564 6.4.154 nntp_mail_check 119
9565 6.4.155 nntp_mime_subject 120
9566 6.4.156 nntp_newsrc 120
9567 6.4.157 nntp_pass 120
9568 6.4.158 nntp_post_moderated 120
9569 6.4.159 nntp_reconnect 121
9570 6.4.160 nntp_save_unsubscribed 121
9571 6.4.161 nntp_show_new_news 121
9572 6.4.162 nntp_show_only_unread 121
9573 6.4.163 nntp_user 121
9574 6.4.164 nntp_x_comment_to 122
9575 6.4.165 operating_system 122
9577 6.4.167 pager_context 122
9578 6.4.168 pager_format 123
9579 6.4.169 pager_index_lines 123
9580 6.4.170 pager_stop 123
9581 6.4.171 pgp_auto_decode 123
9582 6.4.172 pgp_autoinline 123
9583 6.4.173 pgp_check_exit 124
9584 6.4.174 pgp_clearsign_command 124
9585 6.4.175 pgp_decode_command 124
9586 6.4.176 pgp_decrypt_command 125
9587 6.4.177 pgp_encrypt_only_command 125
9588 6.4.178 pgp_encrypt_sign_command 125
9589 6.4.179 pgp_entry_format 125
9590 6.4.180 pgp_export_command 126
9594 6.4.181 pgp_getkeys_command 126
9595 6.4.182 pgp_good_sign 126
9596 6.4.183 pgp_ignore_subkeys 126
9597 6.4.184 pgp_import_command 127
9598 6.4.185 pgp_list_pubring_command 127
9599 6.4.186 pgp_list_secring_command 127
9600 6.4.187 pgp_long_ids 127
9601 6.4.188 pgp_mime_auto 127
9602 6.4.189 pgp_replyinline 128
9603 6.4.190 pgp_retainable_sigs 128
9604 6.4.191 pgp_show_unusable 128
9605 6.4.192 pgp_sign_as 128
9606 6.4.193 pgp_sign_command 129
9607 6.4.194 pgp_sort_keys 129
9608 6.4.195 pgp_strict_enc 129
9609 6.4.196 pgp_timeout 129
9610 6.4.197 pgp_use_gpg_agent 130
9611 6.4.198 pgp_verify_command 130
9612 6.4.199 pgp_verify_key_command 130
9613 6.4.200 pipe_decode 130
9614 6.4.201 pipe_sep 130
9615 6.4.202 pipe_split 130
9616 6.4.203 pop_auth_try_all 131
9617 6.4.204 pop_authenticators 131
9618 6.4.205 pop_delete 131
9619 6.4.206 pop_host 131
9620 6.4.207 pop_last 132
9621 6.4.208 pop_mail_check 132
9622 6.4.209 pop_pass 132
9623 6.4.210 pop_reconnect 132
9624 6.4.211 pop_user 133
9625 6.4.212 post_indent_string 133
9626 6.4.213 postpone 133
9627 6.4.214 postponed 133
9628 6.4.215 preconnect 133
9630 6.4.217 print_command 134
9631 6.4.218 print_decode 134
9632 6.4.219 print_split 134
9633 6.4.220 prompt_after 135
9634 6.4.221 query_command 135
9636 6.4.223 quote_empty 135
9637 6.4.224 quote_quoted 135
9638 6.4.225 quote_regexp 136
9639 6.4.226 read_inc 136
9640 6.4.227 read_only 136
9641 6.4.228 realname 136
9644 6.4.231 reply_regexp 137
9645 6.4.232 reply_self 137
9646 6.4.233 reply_to 137
9651 6.4.235 reverse_alias 138
9652 6.4.236 reverse_name 138
9653 6.4.237 reverse_realname 138
9654 6.4.238 rfc2047_parameters 139
9655 6.4.239 save_address 139
9656 6.4.240 save_empty 139
9657 6.4.241 save_name 139
9659 6.4.243 score_threshold_delete 140
9660 6.4.244 score_threshold_flag 140
9661 6.4.245 score_threshold_read 140
9662 6.4.246 send_charset 140
9663 6.4.247 sendmail 141
9664 6.4.248 sendmail_wait 141
9666 6.4.250 sidebar_boundary 142
9667 6.4.251 sidebar_delim 142
9668 6.4.252 sidebar_newmail_only 142
9669 6.4.253 sidebar_number_format 142
9670 6.4.254 sidebar_shorten_hierarchy 143
9671 6.4.255 sidebar_visible 143
9672 6.4.256 sidebar_width 143
9673 6.4.257 sig_dashes 143
9674 6.4.258 sig_on_top 144
9675 6.4.259 signature 144
9676 6.4.260 signoff_string 144
9677 6.4.261 simple_search 144
9678 6.4.262 sleep_time 145
9679 6.4.263 smart_wrap 145
9681 6.4.265 smime_ask_cert_label 145
9682 6.4.266 smime_ca_location 145
9683 6.4.267 smime_certificates 145
9684 6.4.268 smime_decrypt_command 146
9685 6.4.269 smime_decrypt_use_default_key 146
9686 6.4.270 smime_default_key 147
9687 6.4.271 smime_encrypt_command 147
9688 6.4.272 smime_encrypt_with 147
9689 6.4.273 smime_get_cert_command 147
9690 6.4.274 smime_get_cert_email_command 147
9691 6.4.275 smime_get_signer_cert_command 147
9692 6.4.276 smime_import_cert_command 148
9693 6.4.277 smime_is_default 148
9694 6.4.278 smime_keys 148
9695 6.4.279 smime_pk7out_command 148
9696 6.4.280 smime_sign_command 149
9697 6.4.281 smime_sign_opaque_command 149
9698 6.4.282 smime_timeout 149
9699 6.4.283 smime_verify_command 149
9700 6.4.284 smime_verify_opaque_command 149
9701 6.4.285 smtp_host 149
9702 6.4.286 smtp_pass 150
9706 6.4.287 smtp_port 150
9707 6.4.288 smtp_use_tls 150
9708 6.4.289 smtp_user 150
9710 6.4.291 sort_alias 151
9711 6.4.292 sort_aux 151
9712 6.4.293 sort_browser 152
9714 6.4.295 spam_separator 152
9715 6.4.296 spoolfile 153
9716 6.4.297 ssl_ca_certificates_file 153
9717 6.4.298 ssl_client_cert 153
9718 6.4.299 ssl_force_tls 153
9719 6.4.300 ssl_min_dh_prime_bits 153
9720 6.4.301 ssl_starttls 154
9721 6.4.302 ssl_use_sslv2 154
9722 6.4.303 ssl_use_sslv3 154
9723 6.4.304 ssl_use_tlsv1 154
9724 6.4.305 ssl_usesystemcerts 154
9725 6.4.306 status_chars 155
9726 6.4.307 status_format 155
9727 6.4.308 status_on_top 157
9728 6.4.309 strict_mailto 157
9729 6.4.310 strict_mime 158
9730 6.4.311 strict_threads 158
9731 6.4.312 strip_was 158
9732 6.4.313 strip_was_regex 158
9733 6.4.314 stuff_quoted 159
9735 6.4.316 text_flowed 159
9736 6.4.317 thorough_search 159
9737 6.4.318 thread_received 159
9741 6.4.322 to_chars 160
9745 6.4.326 uncollapse_jump 161
9746 6.4.327 use_8bitmime 161
9747 6.4.328 use_domain 161
9748 6.4.329 use_from 162
9750 6.4.331 use_ipv6 162
9751 6.4.332 user_agent 162
9753 6.4.334 wait_key 163
9755 6.4.336 wrap_search 163
9756 6.4.337 wrapmargin 163
9757 6.4.338 write_bcc 163
9758 6.4.339 write_inc 164
9762 6.4.340 xterm_icon 164
9763 6.4.341 xterm_leave 164
9764 6.4.342 xterm_set_titles 164
9765 6.4.343 xterm_title 164
9766 6.5 Functions ....................................................... 165
9779 7. Miscellany ............................................................ 173
9780 7.1 Acknowledgments ................................................. 174
9781 7.2 About this document ............................................. 176
projects / apps / madmutt.git / blob