2 by Michael Elkins <me@cs.hmc.edu>
5 ``All mail clients suck. This one just sucks less.'' -me, circa 1995
6 ______________________________________________________________________
14 1.3 Software Distribution Sites
21 2.1 Moving Around in Menus
22 2.2 Editing Input Fields
23 2.3 Reading Mail - The Index and Pager
24 2.3.1 The Message Index
28 2.3.4 Miscellaneous Functions
30 2.4.1 Editing the message header
31 2.4.2 Using Mutt with PGP
32 2.4.3 Sending anonymous messages via mixmaster.
33 2.5 Forwarding and Bouncing Mail
35 2.7 Reading news via NNTP
39 3.1 Syntax of Initialization Files
40 3.2 Defining/Using aliases
41 3.3 Changing the default key bindings
42 3.4 Defining aliases for character sets
43 3.5 Setting variables based upon mailbox
45 3.7 Using color and mono video attributes
46 3.8 Ignoring (weeding) unwanted message headers
47 3.9 Alternative addresses
49 3.11 Using Multiple spool mailboxes
50 3.12 Defining mailboxes which receive mail
51 3.13 User defined headers
52 3.14 Defining the order of headers when viewing messages
53 3.15 Specify default save filename
54 3.16 Specify default Fcc: mailbox when composing
55 3.17 Specify default save filename and default Fcc: mailbox at once
56 3.18 Change settings based upon message recipients
57 3.19 Change settings before formatting a message
58 3.20 Choosing the cryptographic key of the recipient
59 3.21 Adding key sequences to the keyboard buffer
60 3.22 Executing functions
63 3.25 Setting variables
64 3.26 Reading initialization commands from another file
69 4.1 Regular Expressions
71 4.2.1 Pattern Modifier
72 4.2.2 Complex Patterns
73 4.2.3 Searching by Date
76 4.4.1 Message Matching in Hooks
77 4.5 External Address Queries
80 4.8 Handling Mailing Lists
81 4.9 Delivery Status Notification (DSN) Support
82 4.10 POP3 Support (OPTIONAL)
83 4.11 IMAP Support (OPTIONAL)
84 4.11.1 The Folder Browser
86 4.12 Managing multiple IMAP/POP accounts (OPTIONAL)
87 4.13 Start a WWW Browser on URLs (EXTERNAL)
89 5. Mutt's MIME Support
91 5.1 Using MIME in Mutt
92 5.1.1 Viewing MIME messages in the pager
93 5.1.2 The Attachment Menu
94 5.1.3 The Compose Menu
95 5.2 MIME Type configuration with
96 5.3 MIME Viewer configuration with
97 5.3.1 The Basics of the mailcap file
98 5.3.2 Secure use of mailcap
99 5.3.3 Advanced mailcap Usage
100 5.3.3.1 Optional Fields
102 5.3.3.3 Command Expansion
103 5.3.4 Example mailcap files
105 5.5 MIME Multipart/Alternative
110 6.1 Command line options
111 6.2 Configuration Commands
112 6.3 Configuration variables
113 6.3.1 abort_nosubject
114 6.3.2 abort_unmodified
124 6.3.12 ask_x_comment_to
134 6.3.22 bounce_delivered
135 6.3.23 catchup_newsgroup
138 6.3.26 collapse_unread
139 6.3.27 uncollapse_jump
140 6.3.28 compose_format
143 6.3.31 connect_timeout
147 6.3.35 crypt_autosmime
152 6.3.40 digest_collapse
153 6.3.41 display_filter
154 6.3.42 dotlock_program
157 6.3.45 duplicate_threads
169 6.3.57 followup_to_poster
171 6.3.59 forward_decode
173 6.3.61 forward_format
177 6.3.65 group_index_format
184 6.3.72 hide_top_limited
185 6.3.73 hide_top_missing
187 6.3.75 honor_followup_to
189 6.3.77 ignore_list_reply_to
190 6.3.78 imap_authenticators
191 6.3.79 imap_delim_chars
192 6.3.80 imap_force_ssl
193 6.3.81 imap_home_namespace
194 6.3.82 imap_keepalive
195 6.3.83 imap_list_subscribed
199 6.3.87 imap_servernoise
201 6.3.89 implicit_autoview
211 6.3.99 mailcap_sanitize
212 6.3.100 maildir_trash
222 6.3.110 mh_seq_flagged
223 6.3.111 mh_seq_replied
224 6.3.112 mh_seq_unseen
226 6.3.114 mime_forward_decode
227 6.3.115 mime_forward_rest
229 6.3.117 mix_entry_format
232 6.3.120 message_format
234 6.3.122 news_cache_dir
238 6.3.126 nntp_load_description
242 6.3.130 nntp_reconnect
244 6.3.132 pager_context
246 6.3.134 pager_index_lines
248 6.3.136 crypt_autosign
249 6.3.137 crypt_autoencrypt
250 6.3.138 pgp_ignore_subkeys
251 6.3.139 crypt_replyencrypt
252 6.3.140 crypt_replysign
253 6.3.141 crypt_replysignencrypted
254 6.3.142 crypt_timestamp
255 6.3.143 pgp_use_gpg_agent
256 6.3.144 crypt_verify_sig
257 6.3.145 smime_is_default
258 6.3.146 smime_ask_cert_label
259 6.3.147 smime_decrypt_use_default_key
260 6.3.148 pgp_entry_format
261 6.3.149 pgp_good_sign
262 6.3.150 pgp_check_exit
264 6.3.152 pgp_retainable_sigs
265 6.3.153 pgp_show_unusable
267 6.3.155 pgp_strict_enc
269 6.3.157 pgp_sort_keys
270 6.3.158 pgp_create_traditional
271 6.3.159 pgp_auto_traditional
272 6.3.160 pgp_decode_command
273 6.3.161 pgp_getkeys_command
274 6.3.162 pgp_verify_command
275 6.3.163 pgp_decrypt_command
276 6.3.164 pgp_clearsign_command
277 6.3.165 pgp_sign_command
278 6.3.166 pgp_encrypt_sign_command
279 6.3.167 pgp_encrypt_only_command
280 6.3.168 pgp_import_command
281 6.3.169 pgp_export_command
282 6.3.170 pgp_verify_key_command
283 6.3.171 pgp_list_secring_command
284 6.3.172 pgp_list_pubring_command
285 6.3.173 forward_decrypt
286 6.3.174 smime_timeout
287 6.3.175 smime_encrypt_with
289 6.3.177 smime_ca_location
290 6.3.178 smime_certificates
291 6.3.179 smime_decrypt_command
292 6.3.180 smime_verify_command
293 6.3.181 smime_verify_opaque_command
294 6.3.182 smime_sign_command
295 6.3.183 smime_sign_opaque_command
296 6.3.184 smime_encrypt_command
297 6.3.185 smime_pk7out_command
298 6.3.186 smime_get_cert_command
299 6.3.187 smime_get_signer_cert_command
300 6.3.188 smime_import_cert_command
301 6.3.189 smime_get_cert_email_command
302 6.3.190 smime_default_key
304 6.3.192 certificate_file
305 6.3.193 ssl_usesystemcerts
307 6.3.195 ssl_use_sslv2
308 6.3.196 ssl_use_sslv3
309 6.3.197 ssl_use_tlsv1
313 6.3.201 pop_authenticators
314 6.3.202 pop_auth_try_all
315 6.3.203 pop_checkinterval
319 6.3.207 pop_reconnect
322 6.3.210 post_indent_string
323 6.3.211 post_moderated
328 6.3.216 print_command
332 6.3.220 query_command
344 6.3.232 reverse_alias
346 6.3.234 reverse_realname
347 6.3.235 rfc2047_parameters
352 6.3.240 score_threshold_delete
353 6.3.241 score_threshold_flag
354 6.3.242 score_threshold_read
357 6.3.245 sendmail_wait
359 6.3.247 save_unsubscribed
360 6.3.248 show_new_news
361 6.3.249 show_only_unread
365 6.3.253 simple_search
376 6.3.264 status_format
377 6.3.265 status_on_top
378 6.3.266 strict_threads
381 6.3.269 thread_received
382 6.3.270 thorough_search
417 7.2 About this document
419 ______________________________________________________________________
421 \e[1m1. Introduction
\e[0m
423 \e[1mMutt
\e[22mis a small but very powerful text-based MIME mail client. Mutt
424 is highly configurable, and is well suited to the mail power user with
425 advanced features like key bindings, keyboard macros, mail threading,
426 regular expression searches and a powerful pattern matching language
427 for selecting groups of messages.
429 \e[1m1.1. Mutt Home Page
\e[0m
433 \e[1m1.2. Mailing Lists
\e[0m
435 To subscribe to one of the following mailing lists, send a message
436 with the word
\e[4msubscribe
\e[24m in the body to list-name
\e[4m-request
\e[24m@mutt.org.
438 · mutt-announce@mutt.org -- low traffic list for announcements
440 · mutt-users@mutt.org -- help, bug reports and feature requests
442 · mutt-dev@mutt.org -- development mailing list
444 \e[1mNote:
\e[22mall messages posted to
\e[4mmutt-announce
\e[24m are automatically forwarded
445 to
\e[4mmutt-users
\e[24m, so you do not need to be subscribed to both lists.
447 \e[1m1.3. Software Distribution Sites
\e[0m
449 · ftp://ftp.mutt.org/mutt/
451 For a list of mirror sites, please refer to
452 http://www.mutt.org/download.html.
456 Visit channel
\e[4m#mutt
\e[24m on OpenProjects.Net (www.openprojects.net) to chat
457 with other people interested in Mutt.
459 \e[1m1.5. USENET
\e[0m
461 See the newsgroup comp.mail.mutt.
463 \e[1m1.6. Copyright
\e[0m
465 Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and
468 This program is free software; you can redistribute it and/or modify
469 it under the terms of the GNU General Public License as published by
470 the Free Software Foundation; either version 2 of the License, or (at
471 your option) any later version.
473 This program is distributed in the hope that it will be useful, but
474 WITHOUT ANY WARRANTY; without even the implied warranty of
475 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
476 General Public License for more details.
478 You should have received a copy of the GNU General Public License
479 along with this program; if not, write to the Free Software
480 Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
482 \e[1m2. Getting Started
\e[0m
484 This section is intended as a brief overview of how to use Mutt.
485 There are many other features which are described elsewhere in the
486 manual. There is even more information available in the Mutt FAQ and
487 various web pages. See the Mutt Page for more details.
489 The keybindings described in this section are the defaults as
490 distributed. Your local system administrator may have altered the
491 defaults for your site. You can always type ``?'' in any menu to
492 display the current bindings.
494 The first thing you need to do is invoke mutt, simply by typing mutt
495 at the command line. There are various command-line options, see
496 either the mutt man page or the ``reference''.
498 \e[1m2.1. Moving Around in Menus
\e[0m
500 Information is presented in menus, very similar to ELM. Here is a
501 table showing the common keys used to navigate menus in Mutt.
503 j or Down next-entry move to the next entry
504 k or Up previous-entry move to the previous entry
505 z or PageDn page-down go to the next page
506 Z or PageUp page-up go to the previous page
507 = or Home first-entry jump to the first entry
508 * or End last-entry jump to the last entry
509 q quit exit the current menu
510 ? help list all keybindings for the current menu
512 2
\b2.
\b.2
\b2.
\b. E
\bEd
\bdi
\bit
\bti
\bin
\bng
\bg I
\bIn
\bnp
\bpu
\but
\bt F
\bFi
\bie
\bel
\bld
\bds
\bs
514 Mutt has a builtin line editor which is used as the primary way to
515 input textual data such as email addresses or filenames. The keys
516 used to move around while editing are very similar to those of Emacs.
518 ^A or <Home> bol move to the start of the line
519 ^B or <Left> backward-char move back one char
520 Esc B backward-word move back one word
521 ^D or <Delete> delete-char delete the char under the cursor
522 ^E or <End> eol move to the end of the line
523 ^F or <Right> forward-char move forward one char
524 Esc F forward-word move forward one word
525 <Tab> complete complete filename or alias
526 ^T complete-query complete address with query
527 ^K kill-eol delete to the end of the line
528 ESC d kill-eow delete to the end ot the word
529 ^W kill-word kill the word in front of the cursor
530 ^U kill-line delete entire line
531 ^V quote-char quote the next typed key
532 <Up> history-up recall previous string from history
533 <Down> history-down recall next string from history
534 <BackSpace> backspace kill the char in front of the cursor
535 Esc u upcase-word convert word to upper case
536 Esc l downcase-word convert word to lower case
537 Esc c capitalize-word capitalize the word
539 <Return> n/a finish editing
541 You can remap the _
\be_
\bd_
\bi_
\bt_
\bo_
\br functions using the ``bind'' command. For
542 example, to make the _
\bD_
\be_
\bl_
\be_
\bt_
\be key delete the character in front of the
543 cursor rather than under, you could use
545 bind editor <delete> backspace
547 2
\b2.
\b.3
\b3.
\b. R
\bRe
\bea
\bad
\bdi
\bin
\bng
\bg M
\bMa
\bai
\bil
\bl -
\b- T
\bTh
\bhe
\be I
\bIn
\bnd
\bde
\bex
\bx a
\ban
\bnd
\bd P
\bPa
\bag
\bge
\ber
\br
549 Similar to many other mail clients, there are two modes in which mail
550 is read in Mutt. The first is the index of messages in the mailbox,
551 which is called the ``index'' in Mutt. The second mode is the display
552 of the message contents. This is called the ``pager.''
554 The next few sections describe the functions provided in each of these
557 2
\b2.
\b.3
\b3.
\b.1
\b1.
\b. T
\bTh
\bhe
\be M
\bMe
\bes
\bss
\bsa
\bag
\bge
\be I
\bIn
\bnd
\bde
\bex
\bx
559 c change to a different mailbox
560 ESC c change to a folder in read-only mode
561 C copy the current message to another mailbox
562 ESC C decode a message and copy it to a folder
563 ESC s decode a message and save it to a folder
564 D delete messages matching a pattern
565 d delete the current message
567 l show messages matching a pattern
568 N mark message as new
569 o change the current sort method
570 O reverse sort the mailbox
571 q save changes and exit
573 T tag messages matching a pattern
574 t toggle the tag on a message
575 ESC t toggle tag on entire message thread
576 U undelete messages matching a pattern
579 x abort changes and exit
580 <Return> display-message
581 <Tab> jump to the next new message
582 @ show the author's full e-mail address
583 $ save changes to mailbox
586 ^L clear and redraw the screen
587 ^T untag messages matching a pattern
589 2
\b2.
\b.3
\b3.
\b.1
\b1.
\b.1
\b1.
\b. S
\bSt
\bta
\bat
\btu
\bus
\bs F
\bFl
\bla
\bag
\bgs
\bs
591 In addition to who sent the message and the subject, a short summary
592 of the disposition of each message is printed beside the message
593 number. Zero or more of the following ``flags'' may appear, which
596 D
\bD message is deleted (is marked for deletion)
598 d
\bd message have attachments marked for deletion
600 K
\bK contains a PGP public key
606 P
\bP message is PGP encrypted
608 r
\br message has been replied to
610 S
\bS message is signed, and the signature is succesfully verified
612 s
\bs message is signed
614 !
\b! message is flagged
616 *
\b* message is tagged
618 Some of the status flags can be turned on or off using
620 · s
\bse
\bet
\bt-
\b-f
\bfl
\bla
\bag
\bg (default: w)
622 · c
\bcl
\ble
\bea
\bar
\br-
\b-f
\bfl
\bla
\bag
\bg (default: W)
624 Furthermore, the following flags reflect who the message is addressed
625 to. They can be customized with the ``$to_chars'' variable.
627 +
\b+ message is to you and you only
629 T
\bT message is to you, but also to or cc'ed to others
631 C
\bC message is cc'ed to you
633 F
\bF message is from you
635 L
\bL message is sent to a subscribed mailing list
637 2
\b2.
\b.3
\b3.
\b.2
\b2.
\b. T
\bTh
\bhe
\be P
\bPa
\bag
\bge
\ber
\br
639 By default, Mutt uses its builtin pager to display the body of
640 messages. The pager is very similar to the Unix program _
\bl_
\be_
\bs_
\bs though
641 not nearly as featureful.
643 <Return> go down one line
644 <Space> display the next page (or next message if at the end of a message)
645 - go back to the previous page
646 n search for next match
647 S skip beyond quoted text
648 T toggle display of quoted text
650 / search for a regular expression (pattern)
651 ESC / search backwards for a regular expression
652 \ toggle search pattern coloring
653 ^ jump to the top of the message
655 In addition, many of the functions from the
\e[4mindex
\e[24m are available in the
656 pager, such as
\e[4mdelete-message
\e[24m or
\e[4mcopy-message
\e[24m (this is one advantage
657 over using an external pager to view messages).
659 Also, the internal pager supports a couple other advanced features.
660 For one, it will accept and translate the ``standard'' nroff sequences
661 for bold and underline. These sequences are a series of either the
662 letter, backspace (^H), the letter again for bold or the letter,
663 backspace, ``_'' for denoting underline. Mutt will attempt to display
664 these in bold and underline respectively if your terminal supports
665 them. If not, you can use the bold and underline ``color'' objects to
666 specify a color or mono attribute for them.
668 Additionally, the internal pager supports the ANSI escape sequences
669 for character attributes. Mutt translates them into the correct color
670 and character settings. The sequences Mutt supports are:
672 ESC [ Ps;Ps;Ps;...;Ps m
679 3x Foreground color is x
680 4x Background color is x
692 Mutt uses these attributes for handling text/enriched messages, and
693 they can also be used by an external ``autoview'' script for
694 highlighting purposes. N
\bNo
\bot
\bte
\be:
\b: If you change the colors for your
695 display, for example by changing the color associated with color2 for
696 your xterm, then that color will be used instead of green.
698 2
\b2.
\b.3
\b3.
\b.3
\b3.
\b. T
\bTh
\bhr
\bre
\bea
\bad
\bde
\bed
\bd M
\bMo
\bod
\bde
\be
700 When the mailbox is ``sorted'' by _
\bt_
\bh_
\br_
\be_
\ba_
\bd_
\bs, there are a few additional
701 functions available in the _
\bi_
\bn_
\bd_
\be_
\bx and _
\bp_
\ba_
\bg_
\be_
\br modes.
703 ^D delete-thread delete all messages in the current thread
704 ^U undelete-thread undelete all messages in the current thread
705 ^N next-thread jump to the start of the next thread
706 ^P previous-thread jump to the start of the previous thread
707 ^R read-thread mark the current thread as read
708 ESC d delete-subthread delete all messages in the current subthread
709 ESC u undelete-subthread undelete all messages in the current subthread
710 ESC n next-subthread jump to the start of the next subthread
711 ESC p previous-subthread jump to the start of the previous subthread
712 ESC r read-subthread mark the current subthread as read
713 ESC t tag-thread toggle the tag on the current thread
714 ESC v collapse-thread toggle collapse for the current thread
715 ESC V collapse-all toggle collapse for all threads
716 P parent-message jump to parent message in thread
718 N
\bNo
\bot
\bte
\be:
\b: Collapsing a thread displays only the first message in the
719 thread and hides the others. This is useful when threads contain so
720 many messages that you can only see a handful of threads on the
721 screen. See %M in ``$index_format''. For example, you could use
722 "%?M?(#%03M)&(%4l)?" in ``$index_format'' to optionally display the
723 number of hidden messages if the thread is collapsed.
725 See also: ``$strict_threads''.
727 \e[1m2.3.4. Miscellaneous Functions
\e[0m
729 \e[1mcreate-alias
\e[22m(default: a)
731 Creates a new alias based upon the current message (or prompts for a
732 new one). Once editing is complete, an ``alias'' command is added to
733 the file specified by the ``$alias_file'' variable for future use.
734 \e[1mNote:
\e[22mSpecifying an ``$alias_file'' does not add the aliases specified
735 there-in, you must also ``source'' the file.
737 \e[1mcheck-traditional-pgp
\e[22m(default: ESC P)
739 This function will search the current message for content signed or
740 encrypted with PGP the "traditional" way, that is, without proper MIME
741 tagging. Technically, this function will temporarily change the MIME
742 content types of the body parts containing PGP data; this is similar
743 to the ``edit-type'' function's effect.
745 \e[1mdisplay-toggle-weed
\e[22m(default: h)
747 Toggles the weeding of message header fields specified by ``ignore''
750 \e[1medit
\e[22m(default: e)
752 This command (available in the ``index'' and ``pager'') allows you to
753 edit the raw current message as it's present in the mail folder.
754 After you have finished editing, the changed message will be appended
755 to the current folder, and the original message will be marked for
759 (default: ^E on the attachment menu, and in the pager and index menus;
760 ^T on the compose menu)
762 This command is used to temporarily edit an attachment's content type
763 to fix, for instance, bogus character set parameters. When invoked
764 from the index or from the pager, you'll have the opportunity to edit
765 the top-level attachment's content type. On the ``attachment menu'',
766 you can change any attachment's content type. These changes are not
767 persistent, and get lost upon changing folders.
769 Note that this command is also available on the ``compose menu''.
770 There, it's used to fine-tune the properties of attachments you are
773 \e[1menter-command
\e[22m(default: ``:'')
775 This command is used to execute any command you would normally put in
776 a configuration file. A common use is to check the settings of
777 variables, or in conjunction with ``macros'' to change settings on the
780 \e[1mextract-keys
\e[22m(default: ^K)
782 This command extracts PGP public keys from the current or tagged
783 message(s) and adds them to your PGP public key ring.
785 \e[1mforget-passphrase
\e[22m(default: ^F)
787 This command wipes the passphrase(s) from memory. It is useful, if you
788 misspelled the passphrase.
790 \e[1mlist-reply
\e[22m(default: L)
792 Reply to the current or tagged message(s) by extracting any addresses
793 which match the addresses given by the ``lists or subscribe''
794 commands, but also honor any Mail-Followup-To header(s) if the
795 ``$honor_followup_to'' configuration variable is set. Using this when
796 replying to messages posted to mailing lists helps avoid duplicate
797 copies being sent to the author of the message you are replying to.
799 \e[1mpipe-message
\e[22m(default: |)
801 Asks for an external Unix command and pipes the current or tagged
802 message(s) to it. The variables ``$pipe_decode'', ``$pipe_split'',
803 ``$pipe_sep'' and ``$wait_key'' control the exact behaviour of this
806 \e[1mresend-message
\e[22m(default: ESC e)
808 With resend-message, mutt takes the current message as a template for
809 a new message. This function is best described as "recall from
810 arbitrary folders". It can conveniently be used to forward MIME
811 messages while preserving the original mail structure. Note that the
812 amount of headers included here depends on the value of the ``$weed''
815 This function is also available from the attachment menu. You can use
816 this to easily resend a message which was included with a bounce
817 message as a message/rfc822 body part.
819 s
\bsh
\bhe
\bel
\bll
\bl-
\b-e
\bes
\bsc
\bca
\bap
\bpe
\be (default: !)
821 Asks for an external Unix command and executes it. The ``$wait_key''
822 can be used to control whether Mutt will wait for a key to be pressed
823 when the command returns (presumably to let the user read the output
824 of the command), based on the return status of the named command.
826 t
\bto
\bog
\bgg
\bgl
\ble
\be-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd (default: T)
828 The _
\bp_
\ba_
\bg_
\be_
\br uses the ``$quote_regexp'' variable to detect quoted text
829 when displaying the body of the message. This function toggles the
830 display of the quoted material in the message. It is particularly
831 useful when are interested in just the response and there is a large
832 amount of quoted text in the way.
834 s
\bsk
\bki
\bip
\bp-
\b-q
\bqu
\buo
\bot
\bte
\bed
\bd (default: S)
836 This function will go to the next line of non-quoted text which come
837 after a line of quoted text in the internal pager.
839 2
\b2.
\b.4
\b4.
\b. S
\bSe
\ben
\bnd
\bdi
\bin
\bng
\bg M
\bMa
\bai
\bil
\bl
841 The following bindings are available in the _
\bi_
\bn_
\bd_
\be_
\bx for sending
844 m compose compose a new message
845 r reply reply to sender
846 g group-reply reply to all recipients
847 L list-reply reply to mailing list address
848 f forward forward message
849 b bounce bounce (remail) message
850 ESC k mail-key mail a PGP public key to someone
852 Bouncing a message sends the message as is to the recipient you
853 specify. Forwarding a message allows you to add comments or modify
854 the message you are forwarding. These items are discussed in greater
855 detail in the next chapter ````Forwarding and Bouncing Mail''''.
857 Mutt will then enter the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu and prompt you for the
858 recipients to place on the ``To:'' header field. Next, it will ask
859 you for the ``Subject:'' field for the message, providing a default if
860 you are replying to or forwarding a message. See also ``$askcc'',
861 ``$askbcc'', ``$autoedit'', ``$bounce'', and ``$fast_reply'' for
862 changing how Mutt asks these questions.
864 Mutt will then automatically start your ``$editor'' on the message
865 body. If the ``$edit_headers'' variable is set, the headers will be
866 at the top of the message in your editor. Any messages you are
867 replying to will be added in sort order to the message, with
868 appropriate ``$attribution'', ``$indent_string'' and
869 ``$post_indent_string''. When forwarding a message, if the
870 ``$mime_forward'' variable is unset, a copy of the forwarded message
871 will be included. If you have specified a ``$signature'', it will be
872 appended to the message.
874 Once you have finished editing the body of your mail message, you are
875 returned to the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu. The following options are available:
877 a attach-file attach a file
878 A attach-message attach message(s) to the message
879 ESC k attach-key attach a PGP public key
880 d edit-description edit description on attachment
881 D detach-file detach a file
882 t edit-to edit the To field
883 ESC f edit-from edit the From field
884 r edit-reply-to edit the Reply-To field
885 c edit-cc edit the Cc field
886 b edit-bcc edit the Bcc field
887 y send-message send the message
888 s edit-subject edit the Subject
889 S smime-menu select S/MIME options
890 f edit-fcc specify an ``Fcc'' mailbox
891 p pgp-menu select PGP options
892 P postpone-message postpone this message until later
893 q quit quit (abort) sending the message
894 w write-fcc write the message to a folder
895 i ispell check spelling (if available on your system)
896 ^F forget-passphrase wipe passphrase(s) from memory
898 N
\bNo
\bot
\bte
\be:
\b: The attach-message function will prompt you for a folder to
899 attach messages from. You can now tag messages in that folder and they
900 will be attached to the message you are sending. Note that certain
901 operations like composing a new mail, replying, forwarding, etc. are
902 not permitted when you are in that folder. The %r in
903 ``$status_format'' will change to a 'A' to indicate that you are in
906 \e[1m2.4.1. Editing the message header
\e[0m
908 When editing the header of your outgoing message, there are a couple
909 of special features available.
912 Fcc:
\e[4mfilename
\e[0m
913 Mutt will pick up
\e[4mfilename
\e[24m just as if you had used the
\e[4medit-fcc
\e[0m
914 function in the
\e[4mcompose
\e[24m menu.
916 You can also attach files to your message by specifying
917 Attach:
\e[4mfilename
\e[24m [
\e[4mdescription
\e[24m ]
918 where
\e[4mfilename
\e[24m is the file to attach and
\e[4mdescription
\e[24m is an optional
919 string to use as the description of the attached file.
921 When replying to messages, if you remove the
\e[4mIn-Reply-To:
\e[24m field from
922 the header field, Mutt will not generate a
\e[4mReferences:
\e[24m field, which
923 allows you to create a new message thread.
925 Also see ``edit_headers''.
927 \e[1m2.4.2. Using Mutt with PGP
\e[0m
929 If you want to use PGP, you can specify
931 Pgp: [ E | S | S
\e[4m<id>
\e[24m ]
933 ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key,
934 setting ``$pgp_sign_as'' permanently.
936 If you have told mutt to PGP encrypt a message, it will guide you
937 through a key selection process when you try to send the message.
938 Mutt will not ask you any questions about keys which have a certified
939 user ID matching one of the message recipients' mail addresses.
940 However, there may be situations in which there are several keys,
941 weakly certified user ID fields, or where no matching keys can be
944 In these cases, you are dropped into a menu with a list of keys from
945 which you can select one. When you quit this menu, or mutt can't find
946 any matching keys, you are prompted for a user ID. You can, as
947 usually, abort this prompt using ^G. When you do so, mutt will return
948 to the compose screen.
950 Once you have successfully finished the key selection, the message
951 will be encrypted using the selected public keys, and sent out.
953 Most fields of the entries in the key selection menu (see also
954 ``$pgp_entry_format'') have obvious meanings. But some explanations
955 on the capabilities, flags, and validity fields are in order.
957 The flags sequence (%f) will expand to one of the following flags:
959 R The key has been revoked and can't be used.
960 X The key is expired and can't be used.
961 d You have marked the key as disabled.
962 c There are unknown critical self-signature
965 The capabilities field (%c) expands to a two-character sequence
966 representing a key's capabilities. The first character gives the
967 key's encryption capabilities: A minus sign (
\e[1m-
\e[22m) means that the key
968 cannot be used for encryption. A dot (
\e[1m.
\e[22m) means that it's marked as a
969 signature key in one of the user IDs, but may also be used for
970 encryption. The letter
\e[1me
\e[22mindicates that this key can be used for
973 The second character indicates the key's signing capabilities. Once
974 again, a ``
\e[1m-
\e[22m'' implies ``not for signing'', ``
\e[1m.
\e[22m'' implies that the key
975 is marked as an encryption key in one of the user-ids, and ``
\e[1ms
\e[22m''
976 denotes a key which can be used for signing.
978 Finally, the validity field (%t) indicates how well-certified a user-
979 id is. A question mark (
\e[1m?
\e[22m) indicates undefined validity, a minus
980 character (
\e[1m-
\e[22m) marks an untrusted association, a space character means
981 a partially trusted association, and a plus character (
\e[1m+
\e[22m) indicates
984 \e[1m2.4.3. Sending anonymous messages via mixmaster.
\e[0m
986 You may also have configured mutt to co-operate with Mixmaster, an
987 anonymous remailer. Mixmaster permits you to send your messages
988 anonymously using a chain of remailers. Mixmaster support in mutt is
989 for mixmaster version 2.04 (beta 45 appears to be the latest) and
990 2.03. It does not support earlier versions or the later so-called
991 version 3 betas, of which the latest appears to be called 2.9b23.
993 To use it, you'll have to obey certain restrictions. Most important,
994 you cannot use the Cc and Bcc headers. To tell Mutt to use mixmaster,
995 you have to select a remailer chain, using the mix function on the
998 The chain selection screen is divided into two parts. In the (larger)
999 upper part, you get a list of remailers you may use. In the lower
1000 part, you see the currently selected chain of remailers.
1002 You can navigate in the chain using the chain-prev and chain-next
1003 functions, which are by default bound to the left and right arrows and
1004 to the h and l keys (think vi keyboard bindings). To insert a
1005 remailer at the current chain position, use the insert function. To
1006 append a remailer behind the current chain position, use select-entry
1007 or append. You can also delete entries from the chain, using the
1008 corresponding function. Finally, to abandon your changes, leave the
1009 menu, or accept them pressing (by default) the Return key.
1011 Note that different remailers do have different capabilities,
1012 indicated in the %c entry of the remailer menu lines (see
1013 ``$mix_entry_format''). Most important is the ``middleman''
1014 capability, indicated by a capital ``M'': This means that the remailer
1015 in question cannot be used as the final element of a chain, but will
1016 only forward messages to other mixmaster remailers. For details on
1017 the other capabilities, please have a look at the mixmaster
1020 \e[1m2.5. Forwarding and Bouncing Mail
\e[0m
1022 Bouncing and forwarding let you send an existing message to recipients
1023 that you specify. Bouncing a message uses the ``sendmail'' command to
1024 send a copy to alternative addresses as if they were the message's
1025 original recipients. Forwarding a message, on the other hand, allows
1026 you to modify the message before it is resent (for example, by adding
1028 The following keys are bound by default:
1030 f forward forward message
1031 b bounce bounce (remail) message
1033 Forwarding can be done by including the original message in the new
1034 message's body (surrounded by indicating lines) or including it as a
1035 MIME attachment, depending on the value of the ``$mime_forward''
1036 variable. Decoding of attachments, like in the pager, can be
1037 controlled by the ``$forward_decode'' and ``$mime_forward_decode''
1038 variables, respectively. The desired forwarding format may depend on
1039 the content, therefore
\e[4m$mime_forward
\e[24m is a quadoption which, for
1040 example, can be set to ``ask-no''.
1042 The inclusion of headers is controlled by the current setting of the
1043 ``$weed'' variable, unless ``mime_forward'' is set.
1045 Editing the message to forward follows the same procedure as sending
1046 or replying to a message does.
1048 2
\b2.
\b.6
\b6.
\b. P
\bPo
\bos
\bst
\btp
\bpo
\bon
\bni
\bin
\bng
\bg M
\bMa
\bai
\bil
\bl
1050 At times it is desirable to delay sending a message that you have
1051 already begun to compose. When the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be function is used
1052 in the _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be menu, the body of your message and attachments are
1053 stored in the mailbox specified by the ``$postponed'' variable. This
1054 means that you can recall the message even if you exit Mutt and then
1055 restart it at a later time.
1057 Once a message is postponed, there are several ways to resume it.
1058 From the command line you can use the ``-p'' option, or if you _
\bc_
\bo_
\bm_
\bp_
\bo_
\bs_
\be
1059 a new message from the _
\bi_
\bn_
\bd_
\be_
\bx or _
\bp_
\ba_
\bg_
\be_
\br you will be prompted if
1060 postponed messages exist. If multiple messages are currently
1061 postponed, the _
\bp_
\bo_
\bs_
\bt_
\bp_
\bo_
\bn_
\be_
\bd menu will pop up and you can select which
1062 message you would like to resume.
1064 N
\bNo
\bot
\bte
\be:
\b: If you postpone a reply to a message, the reply setting of the
1065 message is only updated when you actually finish the message and send
1066 it. Also, you must be in the same folder with the message you replied
1067 to for the status of the message to be updated.
1069 See also the ``$postpone'' quad-option.
1071 2
\b2.
\b.7
\b7.
\b. R
\bRe
\bea
\bad
\bdi
\bin
\bng
\bg n
\bne
\bew
\bws
\bs v
\bvi
\bia
\ba N
\bNN
\bNT
\bTP
\bP
1073 If compiled with ``--enable-nntp'' option, Mutt can read news from
1074 newsserver via NNTP. You can open a newsgroup with function ``change-
1075 newsgroup'' (default: i). Default newsserver can be obtained from
1076 _
\bN_
\bN_
\bT_
\bP_
\bS_
\bE_
\bR_
\bV_
\bE_
\bR environment variable. Like other news readers, info about
1077 subscribed newsgroups is saved in file by ``$newsrc'' variable.
1078 Article headers are cached and can be loaded from file when newsgroup
1079 entered instead loading from newsserver.
1081 3
\b3.
\b. C
\bCo
\bon
\bnf
\bfi
\big
\bgu
\bur
\bra
\bat
\bti
\bio
\bon
\bn
1083 While the default configuration (or ``preferences'') make Mutt usable
1084 right out of the box, it is often desirable to tailor Mutt to suit
1085 your own tastes. When Mutt is first invoked, it will attempt to read
1086 the ``system'' configuration file (defaults set by your local system
1087 administrator), unless the ``-n'' ``command line'' option is
1088 specified. This file is typically /usr/local/share/mutt/Muttrc or
1089 /etc/Muttrc. Mutt will next look for a file named .muttrc in your home
1090 directory. If this file does not exist and your home directory has a
1091 subdirectory named .mutt, mutt try to load a file named .mutt/muttrc.
1093 .muttrc is the file where you will usually place your ``commands'' to
1095 In addition, mutt supports version specific configuration files that
1096 are parsed instead of the default files as explained above. For
1097 instance, if your system has a Muttrc-0.88 file in the system
1098 configuration directory, and you are running version 0.88 of mutt,
1099 this file will be sourced instead of the Muttrc file. The same is
1100 true of the user configuration file, if you have a file .muttrc-0.88.6
1101 in your home directory, when you run mutt version 0.88.6, it will
1102 source this file instead of the default .muttrc file. The version
1103 number is the same which is visible using the ``-v'' ``command line''
1104 switch or using the show-version key (default: V) from the index menu.
1106 \e[1m3.1. Syntax of Initialization Files
\e[0m
1108 An initialization file consists of a series of ``commands''. Each
1109 line of the file may contain one or more commands. When multiple
1110 commands are used, they must be separated by a semicolon (;).
1112 set realname='Mutt user' ; ignore x-
1114 The hash mark, or pound sign (``#''), is used as a ``comment'' charac
1115 ter. You can use it to annotate your initialization file. All text
1116 after the comment character to the end of the line is ignored. For
1119 my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
1121 Single quotes (') and double quotes (") can be used to quote strings
1122 which contain spaces or other special characters. The difference
1123 between the two types of quotes is similar to that of many popular
1124 shell programs, namely that a single quote is used to specify a
1125 literal string (one that is not interpreted for shell variables or
1126 quoting with a backslash [see next paragraph]), while double quotes
1127 indicate a string for which should be evaluated. For example,
1128 backtics are evaluated inside of double quotes, but
\e[1mnot
\e[22mfor single
1131 \ quotes the next character, just as in shells such as bash and zsh.
1132 For example, if want to put quotes ``"'' inside of a string, you can
1133 use ``\'' to force the next character to be a literal instead of
1134 interpreted character.
1136 set realname="Michael \"MuttDude\" Elkins"
1138 ``\\'' means to insert a literal ``\'' into the line. ``\n'' and
1139 ``\r'' have their usual C meanings of linefeed and carriage-return,
1142 A \ at the end of a line can be used to split commands over multiple
1143 lines, provided that the split points don't appear in the middle of
1146 It is also possible to substitute the output of a Unix command in an
1147 initialization file. This is accomplished by enclosing the command in
1148 backquotes (``). For example,
1150 my_hdr X-Operating-System: `uname -a`
1152 The output of the Unix command ``uname -a'' will be substituted before
1153 the line is parsed. Note that since initialization files are line
1154 oriented, only the first line of output from the Unix command will be
1157 UNIX environments can be accessed like the way it is done in shells
1158 like sh and bash: Prepend the name of the environment by a ``$''. For
1161 set record=+sent_on_$HOSTNAME
1163 The commands understood by mutt are explained in the next paragraphs.
1164 For a complete list, see the ``command reference''.
1166 \e[1m3.2. Defining/Using aliases
\e[0m
1168 Usage: alias
\e[4mkey
\e[24m
\e[4maddress
\e[24m [ ,
\e[4maddress
\e[24m, ... ]
1170 It's usually very cumbersome to remember or type out the address of
1171 someone you are communicating with. Mutt allows you to create
1172 ``aliases'' which map a short string to a full address.
1174 \e[1mNote:
\e[22mif you want to create an alias for a group (by specifying more
1175 than one address), you
\e[1mmust
\e[22mseparate the addresses with a comma
1178 To remove an alias or aliases (``*'' means all aliases):
1180 unalias [ * |
\e[4mkey
\e[24m
\e[4m...
\e[24m ]
1182 alias muttdude me@cs.hmc.edu (Michael Elkins)
1183 alias theguys manny, moe, jack
1185 Unlike other mailers, Mutt doesn't require aliases to be defined in a
1186 special file. The alias command can appear anywhere in a
1187 configuration file, as long as this file is ``sourced''.
1188 Consequently, you can have multiple alias files, or you can have all
1189 aliases defined in your muttrc.
1191 On the other hand, the ``create-alias'' function can use only one
1192 file, the one pointed to by the ``$alias_file'' variable (which is
1193 ~/.muttrc by default). This file is not special either, in the sense
1194 that Mutt will happily append aliases to any file, but in order for
1195 the new aliases to take effect you need to explicitly ``source'' this
1199 source /usr/local/share/Mutt.aliases
1200 source ~/.mail_aliases
1201 set alias_file=~/.mail_aliases
1203 To use aliases, you merely use the alias at any place in mutt where
1204 mutt prompts for addresses, such as the
\e[4mTo:
\e[24m or
\e[4mCc:
\e[24m prompt. You can
1205 also enter aliases in your editor at the appropriate headers if you
1206 have the ``$edit_headers'' variable set.
1208 In addition, at the various address prompts, you can use the tab
1209 character to expand a partial alias to the full alias. If there are
1210 multiple matches, mutt will bring up a menu with the matching aliases.
1211 In order to be presented with the full list of aliases, you must hit
1212 tab with out a partial alias, such as at the beginning of the prompt
1213 or after a comma denoting multiple addresses.
1215 In the alias menu, you can select as many aliases as you want with the
1216 \e[4mselect-entry
\e[24m key (default: RET), and use the
\e[4mexit
\e[24m key (default: q) to
1217 return to the address prompt.
1219 \e[1m3.3. Changing the default key bindings
\e[0m
1221 Usage: bind
\e[4mmap
\e[24m
\e[4mkey
\e[24m
\e[4mfunction
\e[0m
1223 This command allows you to change the default key bindings (operation
1224 invoked when pressing a key).
1226 \e[4mmap
\e[24m specifies in which menu the binding belongs. Multiple maps may be
1227 specified by separating them with commas (no additional whitespace is
1228 allowed). The currently defined maps are:
1231 This is not a real menu, but is used as a fallback for all of
1232 the other menus except for the pager and editor modes. If a key
1233 is not defined in another menu, Mutt will look for a binding to
1234 use in this menu. This allows you to bind a key to a certain
1235 function in multiple menus instead of having multiple bind
1236 statements to accomplish the same task.
1239 The alias menu is the list of your personal aliases as defined
1240 in your muttrc. It is the mapping from a short alias name to
1241 the full email address(es) of the recipient(s).
1244 The attachment menu is used to access the attachments on
1248 The browser is used for both browsing the local directory
1249 structure, and for listing all of your incoming mailboxes.
1252 The editor is the line-based editor the user enters text data.
1255 The index is the list of messages contained in a mailbox.
1258 The compose menu is the screen used when sending a new message.
1261 The pager is the mode used to display message/attachment data,
1265 The pgp menu is used to select the OpenPGP keys used for
1266 encrypting outgoing messages.
1269 The postpone menu is similar to the index menu, except is used
1270 when recalling a message the user was composing, but saved until
1273 \e[4mkey
\e[24m is the key (or key sequence) you wish to bind. To specify a
1274 control character, use the sequence
\e[4m\Cx
\e[24m, where
\e[4mx
\e[24m is the letter of the
1275 control character (for example, to specify control-A use ``\Ca'').
1276 Note that the case of
\e[4mx
\e[24m as well as
\e[4m\C
\e[24m is ignored, so that
\e[4m\CA
\e[24m,
\e[4m\Ca
\e[24m,
1277 \e[4m\cA
\e[24m and
\e[4m\ca
\e[24m are all equivalent. An alternative form is to specify the
1278 key as a three digit octal number prefixed with a ``\'' (for example
1279 \e[4m\177
\e[24m is equivalent to
\e[4m\c?
\e[24m).
1281 In addition,
\e[4mkey
\e[24m may consist of:
1294 <pagedown> Page Down
1295 <backspace> Backspace
1304 <f10> function key 10
1306 \e[4mkey
\e[24m does not need to be enclosed in quotes unless it contains a space
1309 \e[4mfunction
\e[24m specifies which action to take when
\e[4mkey
\e[24m is pressed. For a
1310 complete list of functions, see the ``reference''. The special
1311 function noop unbinds the specified key sequence.
1313 \e[1m3.4. Defining aliases for character sets
\e[0m
1315 Usage: charset-hook
\e[4malias
\e[24m
\e[4mcharset
\e[0m
1316 Usage: iconv-hook
\e[4mcharset
\e[24m
\e[4mlocal-charset
\e[0m
1318 The charset-hook command defines an alias for a character set. This
1319 is useful to properly display messages which are tagged with a
1320 character set name not known to mutt.
1322 The iconv-hook command defines a system-specific name for a character
1323 set. This is helpful when your systems character conversion library
1324 insists on using strange, system-specific names for character sets.
1326 \e[1m3.5. Setting variables based upon mailbox
\e[0m
1328 Usage: folder-hook [!]
\e[4mregexp
\e[24m
\e[4mcommand
\e[0m
1330 It is often desirable to change settings based on which mailbox you
1331 are reading. The folder-hook command provides a method by which you
1332 can execute any configuration command.
\e[4mregexp
\e[24m is a regular expression
1333 specifying in which mailboxes to execute
\e[4mcommand
\e[24m before loading. If a
1334 mailbox matches multiple folder-hook's, they are executed in the order
1335 given in the muttrc.
1337 \e[1mNote:
\e[22mif you use the ``!'' shortcut for ``$spoolfile'' at the
1338 beginning of the pattern, you must place it inside of double or single
1339 quotes in order to distinguish it from the logical
\e[4mnot
\e[24m operator for
1342 Note that the settings are
\e[4mnot
\e[24m restored when you leave the mailbox.
1343 For example, a command action to perform is to change the sorting
1344 method based upon the mailbox being read:
1346 folder-hook mutt set sort=threads
1348 However, the sorting method is not restored to its previous value when
1349 reading a different mailbox. To specify a
\e[4mdefault
\e[24m command, use the
1352 folder-hook . set sort=date-sent
1354 \e[1m3.6. Keyboard macros
\e[0m
1356 Usage: macro
\e[4mmenu
\e[24m
\e[4mkey
\e[24m
\e[4msequence
\e[24m [
\e[4mdescription
\e[24m ]
1358 Macros are useful when you would like a single key to perform a series
1359 of actions. When you press
\e[4mkey
\e[24m in menu
\e[4mmenu
\e[24m, Mutt will behave as if
1360 you had typed
\e[4msequence
\e[24m. So if you have a common sequence of commands
1361 you type, you can create a macro to execute those commands with a
1364 \e[4mmenu
\e[24m is the ``map'' which the macro will be bound. Multiple maps may
1365 be specified by separating multiple menu arguments by commas.
1366 Whitespace may not be used in between the menu arguments and the
1367 commas separating them.
1369 \e[4mkey
\e[24m and
\e[4msequence
\e[24m are expanded by the same rules as the ``key
1370 bindings''. There are some additions however. The first is that
1371 control characters in
\e[4msequence
\e[24m can also be specified as
\e[4m^x
\e[24m. In order
1372 to get a caret (`^'') you need to use
\e[4m^^
\e[24m. Secondly, to specify a
1373 certain key such as
\e[4mup
\e[24m or to invoke a function directly, you can use
1374 the format
\e[4m<key
\e[24m
\e[4mname>
\e[24m and
\e[4m<function
\e[24m
\e[4mname>
\e[24m. For a listing of key names
1375 see the section on ``key bindings''. Functions are listed in the
1376 ``function reference''.
1378 The advantage with using function names directly is that the macros
1379 will work regardless of the current key bindings, so they are not
1380 dependent on the user having particular key definitions. This makes
1381 them more robust and portable, and also facilitates defining of macros
1382 in files used by more than one user (eg. the system Muttrc).
1384 Optionally you can specify a descriptive text after
\e[4msequence
\e[24m, which is
1385 shown in the help screens.
1387 \e[1mNote:
\e[22mMacro definitions (if any) listed in the help screen(s), are
1388 silently truncated at the screen width, and are not wrapped.
1390 \e[1m3.7. Using color and mono video attributes
\e[0m
1392 Usage: color
\e[4mobject
\e[24m
\e[4mforeground
\e[24m
\e[4mbackground
\e[24m [
\e[4mregexp
\e[24m ]
1393 Usage: color index
\e[4mforeground
\e[24m
\e[4mbackground
\e[24m
\e[4mpattern
\e[0m
1394 Usage: uncolor index
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
1396 If your terminal supports color, you can spice up Mutt by creating
1397 your own color scheme. To define the color of an object (type of
1398 information), you must specify both a foreground color
\e[1mand
\e[22ma
1399 background color (it is not possible to only specify one or the
1402 \e[4mobject
\e[24m can be one of:
1406 · body (match
\e[4mregexp
\e[24m in the body of messages)
1408 · bold (hiliting bold patterns in the body of messages)
1410 · error (error messages printed by Mutt)
1412 · header (match
\e[4mregexp
\e[24m in the message header)
1414 · hdrdefault (default color of the message header in the pager)
1416 · index (match
\e[4mpattern
\e[24m in the message index)
1418 · indicator (arrow or bar used to indicate the current item in a
1421 · markers (the ``+'' markers at the beginning of wrapped lines in the
1424 · message (informational messages)
1428 · quoted (text matching ``$quote_regexp'' in the body of a message)
1430 · quoted1, quoted2, ..., quoted
\e[1mN
\e[22m(higher levels of quoting)
1432 · search (hiliting of words in the pager)
1436 · status (mode lines used to display info about the mailbox or
1439 · tilde (the ``~'' used to pad blank lines in the pager)
1441 · tree (thread tree drawn in the message index and attachment menu)
1443 · underline (hiliting underlined patterns in the body of messages)
1445 \e[4mforeground
\e[24m and
\e[4mbackground
\e[24m can be one of the following:
1467 \e[4mforeground
\e[24m can optionally be prefixed with the keyword bright to make
1468 the foreground color boldfaced (e.g., brightred).
1470 If your terminal supports it, the special keyword
\e[4mdefault
\e[24m can be used
1471 as a transparent color. The value
\e[4mbrightdefault
\e[24m is also valid. If
1472 Mutt is linked against the
\e[4mS-Lang
\e[24m library, you also need to set the
1473 \e[4mCOLORFGBG
\e[24m environment variable to the default colors of your terminal
1474 for this to work; for example (for Bourne-like shells):
1476 set COLORFGBG="green;black"
1479 \e[1mNote:
\e[22mThe
\e[4mS-Lang
\e[24m library requires you to use the
\e[4mlightgray
\e[24m and
\e[4mbrown
\e[0m
1480 keywords instead of
\e[4mwhite
\e[24m and
\e[4myellow
\e[24m when setting this variable.
1482 \e[1mNote:
\e[22mThe uncolor command can be applied to the index object only. It
1483 removes entries from the list. You
\e[1mmust
\e[22mspecify the same pattern
1484 specified in the color command for it to be removed. The pattern
1485 ``*'' is a special token which means to clear the color index list of
1488 Mutt also recognizes the keywords
\e[4mcolor0
\e[24m,
\e[4mcolor1
\e[24m, ...,
\e[4mcolor
\e[24m
\e[1mN-1
\e[22m(
\e[1mN
\e[0m
1489 being the number of colors supported by your terminal). This is
1490 useful when you remap the colors for your display (for example by
1491 changing the color associated with
\e[4mcolor2
\e[24m for your xterm), since color
1492 names may then lose their normal meaning.
1494 If your terminal does not support color, it is still possible change
1495 the video attributes through the use of the ``mono'' command:
1497 Usage: mono
\e[4m<object>
\e[24m
\e[4m<attribute>
\e[24m [
\e[4mregexp
\e[24m ]
1498 Usage: mono index
\e[4mattribute
\e[24m
\e[4mpattern
\e[0m
1499 Usage: unmono index
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
1501 where
\e[4mattribute
\e[24m is one of the following:
1513 \e[1m3.8. Ignoring (weeding) unwanted message headers
\e[0m
1515 Usage: [un]ignore
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
1517 Messages often have many header fields added by automatic processing
1518 systems, or which may not seem useful to display on the screen. This
1519 command allows you to specify header fields which you don't normally
1522 You do not need to specify the full header field name. For example,
1523 ``ignore content-'' will ignore all header fields that begin with the
1524 pattern ``content-''. ``ignore *'' will ignore all headers.
1526 To remove a previously added token from the list, use the ``unignore''
1527 command. The ``unignore'' command will make Mutt display headers with
1528 the given pattern. For example, if you do ``ignore x-'' it is
1529 possible to ``unignore x-mailer''.
1531 ``unignore *'' will remove all tokens from the ignore list.
1535 # Sven's draconian header weeding
1537 unignore from date subject to cc
1538 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1541 \e[1m3.9. Alternative addresses
\e[0m
1543 Usage: [un]alternates
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
1545 With various functions, mutt will treat messages differently,
1546 depending on whether you sent them or whether you received them from
1547 someone else. For instance, when replying to a message that you sent
1548 to a different party, mutt will automatically suggest to send the
1549 response to the original message's recipients -- responding to
1550 yourself won't make much sense in many cases. (See ``$reply_to''.)
1552 Many users receive e-mail under a number of different addresses. To
1553 fully use mutt's features here, the program must be able to recognize
1554 what e-mail addresses you receive mail under. That's the purpose of
1555 the alternates command: It takes a list of regular expressions, each
1556 of which can identify an address under which you receive e-mail.
1558 To remove a regular expression from this list, use the unalternates
1561 \e[1m3.10. Mailing lists
\e[0m
1563 Usage: [un]lists
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
1564 Usage: [un]subscribe
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
1566 Mutt has a few nice features for ``handling mailing lists''. In order
1567 to take advantage of them, you must specify which addresses belong to
1568 mailing lists, and which mailing lists you are subscribed to. Once
1569 you have done this, the ``list-reply'' function will work for all
1570 known lists. Additionally, when you send a message to a subscribed
1571 list, mutt will add a Mail-Followup-To header to tell other users'
1572 mail user agents not to send copies of replies to your personal
1573 address. Note that the Mail-Followup-To header is a non-standard
1574 extension which is not supported by all mail user agents. Adding it
1575 is not bullet-proof against receiving personal CCs of list messages.
1576 Also note that the generation of the Mail-Followup-To header is
1577 controlled by the ``$followup_to'' configuration variable.
1579 More precisely, Mutt maintains lists of patterns for the addresses of
1580 known and subscribed mailing lists. Every subscribed mailing list is
1581 known. To mark a mailing list as known, use the ``lists'' command. To
1582 mark it as subscribed, use ``subscribe''.
1584 You can use regular expressions with both commands. To mark all
1585 messages sent to a specific bug report's address on mutt's bug
1586 tracking system as list mail, for instance, you could say ``subscribe
1587 [0-9]*@bugs.guug.de''. Often, it's sufficient to just give a portion
1588 of the list's e-mail address.
1590 Specify as much of the address as you need to to remove ambiguity.
1591 For example, if you've subscribed to the Mutt mailing list, you will
1592 receive mail addresssed to
\e[4mmutt-users@mutt.org
\e[24m. So, to tell Mutt that
1593 this is a mailing list, you could add ``lists mutt-users'' to your
1594 initialization file. To tell mutt that you are subscribed to it, add
1595 ``subscribe mutt-users'' to your initialization file instead. If you
1596 also happen to get mail from someone whose address is
\e[4mmutt-
\e[0m
1597 \e[4musers@example.com
\e[24m, you could use ``lists mutt-users@mutt.org'' or
1598 ``subscribe mutt-users@mutt.org'' to match only mail from the actual
1601 The ``unlists'' command is used to remove a token from the list of
1602 known and subscribed mailing-lists. Use ``unlists *'' to remove all
1605 To remove a mailing list from the list of subscribed mailing lists,
1606 but keep it on the list of known mailing lists, use ``unsubscribe''.
1608 \e[1m3.11. Using Multiple spool mailboxes
\e[0m
1610 Usage: mbox-hook [!]
\e[4mpattern
\e[24m
\e[4mmailbox
\e[0m
1612 This command is used to move read messages from a specified mailbox to
1613 a different mailbox automatically when you quit or change folders.
1614 \e[4mpattern
\e[24m is a regular expression specifying the mailbox to treat as a
1615 ``spool'' mailbox and
\e[4mmailbox
\e[24m specifies where mail should be saved
1618 Unlike some of the other
\e[4mhook
\e[24m commands, only the
\e[4mfirst
\e[24m matching
1619 pattern is used (it is not possible to save read mail in more than a
1622 \e[1m3.12. Defining mailboxes which receive mail
\e[0m
1624 Usage: [un]mailboxes [!]
\e[4mfilename
\e[24m [
\e[4mfilename
\e[24m ... ]
1626 This command specifies folders which can receive mail and which will
1627 be checked for new messages. By default, the main menu status bar
1628 displays how many of these folders have new messages.
1630 When changing folders, pressing
\e[4mspace
\e[24m will cycle through folders with
1633 Pressing TAB in the directory browser will bring up a menu showing the
1634 files specified by the mailboxes command, and indicate which contain
1635 new messages. Mutt will automatically enter this mode when invoked
1636 from the command line with the -y option.
1638 The ``unmailboxes'' command is used to remove a token from the list of
1639 folders which receive mail. Use ``unmailboxes *'' to remove all
1642 \e[1mNote:
\e[22mnew mail is detected by comparing the last modification time to
1643 the last access time. Utilities like biff or frm or any other program
1644 which accesses the mailbox might cause Mutt to never detect new mail
1645 for that mailbox if they do not properly reset the access time.
1646 Backup tools are another common reason for updated access times.
1648 \e[1mNote:
\e[22mthe filenames in the mailboxes command are resolved when the
1649 command is executed, so if these names contain ``shortcut characters''
1650 (such as ``='' and ``!''), any variable definition that affect these
1651 characters (like ``$folder'' and ``$spoolfile'') should be executed
1652 before the mailboxes command.
1654 \e[1m3.13. User defined headers
\e[0m
1657 my_hdr
\e[4mstring
\e[0m
1658 unmy_hdr
\e[4mfield
\e[24m [
\e[4mfield
\e[24m ... ]
1660 The ``my_hdr'' command allows you to create your own header fields
1661 which will be added to every message you send.
1663 For example, if you would like to add an ``Organization:'' header
1664 field to all of your outgoing messages, you can put the command
1666 my_hdr Organization: A Really Big Company, Anytown, USA
1670 \e[1mNote:
\e[22mspace characters are
\e[4mnot
\e[24m allowed between the keyword and the
1671 colon (``:''). The standard for electronic mail (RFC822) says that
1672 space is illegal there, so Mutt enforces the rule.
1674 If you would like to add a header field to a single message, you
1675 should either set the ``edit_headers'' variable, or use the
\e[4medit-
\e[0m
1676 \e[4mheaders
\e[24m function (default: ``E'') in the send-menu so that you can
1677 edit the header of your message along with the body.
1679 To remove user defined header fields, use the ``unmy_hdr'' command.
1680 You may specify an asterisk (``*'') to remove all header fields, or
1681 the fields to remove. For example, to remove all ``To'' and ``Cc''
1682 header fields, you could use:
1686 \e[1m3.14. Defining the order of headers when viewing messages
\e[0m
1688 Usage: hdr_order
\e[4mheader1
\e[24m
\e[4mheader2
\e[24m
\e[4mheader3
\e[0m
1690 With this command, you can specify an order in which mutt will attempt
1691 to present headers to you when viewing messages.
1693 ``unhdr_order *'' will clear all previous headers from the order list,
1694 thus removing the header order effects set by the system-wide startup
1697 hdr_order From Date: From: To: Cc: Subject:
1699 \e[1m3.15. Specify default save filename
\e[0m
1701 Usage: save-hook [!]
\e[4mpattern
\e[24m
\e[4mfilename
\e[0m
1703 This command is used to override the default filename used when saving
1704 messages.
\e[4mfilename
\e[24m will be used as the default filename if the
1705 message is
\e[4mFrom:
\e[24m an address matching
\e[4mregexp
\e[24m or if you are the author
1706 and the message is addressed
\e[4mto:
\e[24m something matching
\e[4mregexp
\e[24m.
1708 See ``Message Matching in Hooks'' for information on the exact format
1709 of
\e[4mpattern
\e[24m.
1713 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1714 save-hook aol\\.com$ +spam
1716 Also see the ``fcc-save-hook'' command.
1718 \e[1m3.16. Specify default Fcc: mailbox when composing
\e[0m
1720 Usage: fcc-hook [!]
\e[4mpattern
\e[24m
\e[4mmailbox
\e[0m
1722 This command is used to save outgoing mail in a mailbox other than
1723 ``$record''. Mutt searches the initial list of message recipients for
1724 the first matching
\e[4mregexp
\e[24m and uses
\e[4mmailbox
\e[24m as the default Fcc:
1725 mailbox. If no match is found the message will be saved to
1726 ``$record'' mailbox.
1728 See ``Message Matching in Hooks'' for information on the exact format
1729 of
\e[4mpattern
\e[24m.
1731 Example: fcc-hook aol.com$ +spammers
1733 The above will save a copy of all messages going to the aol.com domain
1734 to the `+spammers' mailbox by default. Also see the ``fcc-save-hook''
1737 \e[1m3.17. Specify default save filename and default Fcc: mailbox at once
\e[0m
1739 Usage: fcc-save-hook [!]
\e[4mpattern
\e[24m
\e[4mmailbox
\e[0m
1741 This command is a shortcut, equivalent to doing both a ``fcc-hook''
1742 and a ``save-hook'' with its arguments.
1744 \e[1m3.18. Change settings based upon message recipients
\e[0m
1746 Usage: reply-hook [!]
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
1747 Usage: send-hook [!]
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
1748 Usage: send2-hook [!]
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
1750 These commands can be used to execute arbitrary configuration commands
1751 based upon recipients of the message.
\e[4mpattern
\e[24m is a regular expression
1752 matching the desired address.
\e[4mcommand
\e[24m is executed when
\e[4mregexp
\e[24m matches
1753 recipients of the message.
1755 reply-hook is matched against the message you are
\e[4mreplying
\e[24m
\e[1mto
\e[22m, instead
1756 of the message you are
\e[4msending
\e[24m. send-hook is matched against all
1757 messages, both
\e[4mnew
\e[24m and
\e[4mreplies
\e[24m.
\e[1mNote:
\e[22mreply-hooks are matched
\e[1mbefore
\e[0m
1758 the send-hook,
\e[1mregardless
\e[22mof the order specified in the users's
1761 send2-hook is matched every time a message is changed, either by
1762 editing it, or by using the compose menu to change its recipients or
1763 subject. send2-hook is executed after send-hook, and can, e.g., be
1764 used to set parameters such as the ``$sendmail'' variable depending on
1765 the message's sender address.
1767 For each type of send-hook or reply-hook, when multiple matches occur,
1768 commands are executed in the order they are specified in the muttrc
1769 (for that type of hook).
1771 See ``Message Matching in Hooks'' for information on the exact format
1772 of
\e[4mpattern
\e[24m.
1774 Example: send-hook mutt "set mime_forward signature=''"
1776 Another typical use for this command is to change the values of the
1777 ``$attribution'', ``$signature'' and ``$locale'' variables in order to
1778 change the language of the attributions and signatures based upon the
1781 \e[1mNote:
\e[22mthe send-hook's are only executed ONCE after getting the initial
1782 list of recipients. Adding a recipient after replying or editing the
1783 message will NOT cause any send-hook to be executed. Also note that
1784 my_hdr commands which modify recipient headers, or the message's
1785 subject, don't have any effect on the current message when executed
1788 \e[1m3.19. Change settings before formatting a message
\e[0m
1790 Usage: message-hook [!]
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
1792 This command can be used to execute arbitrary configuration commands
1793 before viewing or formatting a message based upon information about
1794 the message.
\e[4mcommand
\e[24m is executed if the
\e[4mpattern
\e[24m matches the message
1795 to be displayed. When multiple matches occur, commands are executed in
1796 the order they are specified in the muttrc.
1798 See ``Message Matching in Hooks'' for information on the exact format
1799 of
\e[4mpattern
\e[24m.
1803 message-hook ~A 'set pager=builtin'
1804 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1806 \e[1m3.20. Choosing the cryptographic key of the recipient
\e[0m
1808 Usage: crypt-hook
\e[4mpattern
\e[24m
\e[4mkeyid
\e[0m
1810 When encrypting messages with PGP or OpenSSL, you may want to
1811 associate a certain key with a given e-mail address automatically,
1812 either because the recipient's public key can't be deduced from the
1813 destination address, or because, for some reasons, you need to
1814 override the key Mutt would normally use. The crypt-hook command
1815 provides a method by which you can specify the ID of the public key to
1816 be used when encrypting messages to a certain recipient.
1818 The meaning of "key id" is to be taken broadly in this context: You
1819 can either put a numerical key ID here, an e-mail address, or even
1822 \e[1m3.21. Adding key sequences to the keyboard buffer
\e[0m
1824 Usage: push
\e[4mstring
\e[0m
1826 This command adds the named string to the keyboard buffer. The string
1827 may contain control characters, key names and function names like the
1828 sequence string in the ``macro'' command. You may use it to
1829 automatically run a sequence of commands at startup, or when entering
1832 \e[1m3.22. Executing functions
\e[0m
1834 Usage: exec
\e[4mfunction
\e[24m [
\e[4mfunction
\e[24m ... ]
1836 This command can be used to execute any function. Functions are listed
1837 in the ``function reference''. ``exec function'' is equivalent to
1838 ``push <function>''.
1839 \e[1m3.23. Message Scoring
\e[0m
1841 Usage: score
\e[4mpattern
\e[24m
\e[4mvalue
\e[0m
1842 Usage: unscore
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
1844 The score commands adds
\e[4mvalue
\e[24m to a message's score if
\e[4mpattern
\e[24m matches
1845 it.
\e[4mpattern
\e[24m is a string in the format described in the ``patterns''
1846 section (note: For efficiency reasons, patterns which scan information
1847 not available in the index, such as ~b, ~B or ~h, may not be used).
1848 \e[4mvalue
\e[24m is a positive or negative integer. A message's final score is
1849 the sum total of all matching score entries. However, you may
1850 optionally prefix
\e[4mvalue
\e[24m with an equal sign (=) to cause evaluation to
1851 stop at a particular entry if there is a match. Negative final scores
1852 are rounded up to 0.
1854 The unscore command removes score entries from the list. You
\e[1mmust
\e[0m
1855 specify the same pattern specified in the score command for it to be
1856 removed. The pattern ``*'' is a special token which means to clear
1857 the list of all score entries.
1859 \e[1m3.24. Spam detection
\e[0m
1861 Usage: spam
\e[4mpattern
\e[24m
\e[4mformat
\e[0m
1862 Usage: nospam
\e[4mpattern
\e[0m
1864 Mutt has generalized support for external spam-scoring filters. By
1865 defining your spam patterns with the spam and nospam commands, you can
1866 \e[4mlimit
\e[24m,
\e[4msearch
\e[24m, and
\e[4msort
\e[24m your mail based on its spam attributes, as
1867 determined by the external filter. You also can display the spam
1868 attributes in your index display using the %H selector in the
1869 ``$index_format'' variable. (Tip: try %?H?[%H] ? to display spam tags
1870 only when they are defined for a given message.)
1872 Your first step is to define your external filter's spam patterns
1873 using the spam command.
\e[4mpattern
\e[24m should be a regular expression that
1874 matches a header in a mail message. If any message in the mailbox
1875 matches this regular expression, it will receive a ``spam tag'' or
1876 ``spam attribute'' (unless it also matches a nospam pattern -- see
1877 below.) The appearance of this attribute is entirely up to you, and is
1878 governed by the
\e[4mformat
\e[24m parameter.
\e[4mformat
\e[24m can be any static text, but
1879 it also can include back-references from the
\e[4mpattern
\e[24m expression. (A
1880 regular expression ``back-reference'' refers to a sub-expression
1881 contained within parentheses.) %1 is replaced with the first back-
1882 reference in the regex, %2 with the second, etc.
1884 If you're using multiple spam filters, a message can have more than
1885 one spam-related header. You can define spam patterns for each filter
1886 you use. If a message matches two or more of these patterns, and the
1887 $spam_separator variable is set to a string, then the message's spam
1888 tag will consist of all the
\e[4mformat
\e[24m strings joined together, with the
1889 value of $spam_separator separating them.
1891 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
1892 define these spam settings:
1894 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
1895 spam "X-Spam-Status: Yes" "90+/SA"
1896 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
1897 set spam_separator=", "
1899 If I then received a message that DCC registered with ``many'' hits
1900 under the ``Fuz2'' checksum, and that PureMessage registered with a
1901 97% probability of being spam, that message's spam tag would read
1902 90+/DCC-Fuz2, 97/PM. (The four characters before ``=many'' in a DCC
1903 report indicate the checksum used -- in this case, ``Fuz2''.)
1905 If the $spam_separator variable is unset, then each spam pattern match
1906 supercedes the previous one. Instead of getting joined
\e[4mformat
\e[24m strings,
1907 you'll get only the last one to match.
1909 The spam tag is what will be displayed in the index when you use %H in
1910 the $index_format variable. It's also the string that the ~H pattern-
1911 matching expression matches against for
\e[4msearch
\e[24m and
\e[4mlimit
\e[24m functions.
1912 And it's what sorting by spam attribute will use as a sort key.
1914 That's a pretty complicated example, and most people's actual
1915 environments will have only one spam filter. The simpler your
1916 configuration, the more effective mutt can be, especially when it
1919 Generally, when you sort by spam tag, mutt will sort
\e[4mlexically
\e[24m -- that
1920 is, by ordering strings alphnumerically. However, if a spam tag begins
1921 with a number, mutt will sort numerically first, and lexically only
1922 when two numbers are equal in value. (This is like UNIX's sort -n.) A
1923 message with no spam attributes at all -- that is, one that didn't
1924 match
\e[4many
\e[24m of your spam patterns -- is sorted at lowest priority.
1925 Numbers are sorted next, beginning with 0 and ranging upward. Finally,
1926 non-numeric strings are sorted, with ``a'' taking lower priority than
1927 ``z''. Clearly, in general, sorting by spam tags is most effective
1928 when you can coerce your filter to give you a raw number. But in case
1929 you can't, mutt can still do something useful.
1931 The nospam command can be used to write exceptions to spam patterns.
1932 If a header pattern matches something in a spam command, but you
1933 nonetheless do not want it to receive a spam tag, you can list a more
1934 precise pattern under a nospam command.
1936 If the
\e[4mpattern
\e[24m given to nospam is exactly the same as the
\e[4mpattern
\e[24m on
1937 an existing spam list entry, the effect will be to remove the entry
1938 from the spam list, instead of adding an exception. Likewise, if the
1939 \e[4mpattern
\e[24m for a spam command matches an entry on the nospam list, that
1940 nospam entry will be removed. If the
\e[4mpattern
\e[24m for nospam is ``*'',
\e[4mall
\e[0m
1941 \e[4mentries
\e[24m
\e[4mon
\e[24m
\e[4mboth
\e[24m
\e[4mlists
\e[24m will be removed. This might be the default
1942 action if you use spam and nospam in conjunction with a folder-hook.
1944 You can have as many spam or nospam commands as you like. You can
1945 even do your own primitive spam detection within mutt -- for example,
1946 if you consider all mail from MAILER-DAEMON to be spam, you can use a
1947 spam command like this:
1949 spam "^From: .*MAILER-DAEMON" "999"
1951 \e[1m3.25. Setting variables
\e[0m
1953 Usage: set [no|inv]
\e[4mvariable
\e[24m[=
\e[4mvalue
\e[24m] [
\e[4mvariable
\e[24m ... ]
1954 Usage: toggle
\e[4mvariable
\e[24m [
\e[4mvariable
\e[24m ... ]
1955 Usage: unset
\e[4mvariable
\e[24m [
\e[4mvariable
\e[24m ... ]
1956 Usage: reset
\e[4mvariable
\e[24m [
\e[4mvariable
\e[24m ... ]
1958 This command is used to set (and unset) ``configuration variables''.
1959 There are four basic types of variables: boolean, number, string and
1960 quadoption.
\e[4mboolean
\e[24m variables can be
\e[4mset
\e[24m (true) or
\e[4munset
\e[24m (false).
1961 \e[4mnumber
\e[24m variables can be assigned a positive integer value.
1963 \e[4mstring
\e[24m variables consist of any number of printable characters.
1964 \e[4mstrings
\e[24m must be enclosed in quotes if they contain spaces or tabs.
1965 You may also use the ``C'' escape sequences
\e[1m\n
\e[22mand
\e[1m\t
\e[22mfor newline and
1968 \e[4mquadoption
\e[24m variables are used to control whether or not to be prompted
1969 for certain actions, or to specify a default action. A value of
\e[4myes
\e[0m
1970 will cause the action to be carried out automatically as if you had
1971 answered yes to the question. Similarly, a value of
\e[4mno
\e[24m will cause the
1972 the action to be carried out as if you had answered ``no.'' A value
1973 of
\e[4mask-yes
\e[24m will cause a prompt with a default answer of ``yes'' and
1974 \e[4mask-no
\e[24m will provide a default answer of ``no.''
1976 Prefixing a variable with ``no'' will unset it. Example: set
1979 For
\e[4mboolean
\e[24m variables, you may optionally prefix the variable name
1980 with inv to toggle the value (on or off). This is useful when writing
1981 macros. Example: set invsmart_wrap.
1983 The toggle command automatically prepends the inv prefix to all
1984 specified variables.
1986 The unset command automatically prepends the no prefix to all
1987 specified variables.
1989 Using the enter-command function in the
\e[4mindex
\e[24m menu, you can query the
1990 value of a variable by prefixing the name of the variable with a
1995 The question mark is actually only required for boolean and quadoption
1998 The reset command resets all given variables to the compile time
1999 defaults (hopefully mentioned in this manual). If you use the command
2000 set and prefix the variable with ``&'' this has the same behavior as
2003 With the reset command there exists the special variable ``all'',
2004 which allows you to reset all variables to their system defaults.
2006 \e[1m3.26. Reading initialization commands from another file
\e[0m
2008 Usage: source
\e[4mfilename
\e[0m
2010 This command allows the inclusion of initialization commands from
2011 other files. For example, I place all of my aliases in
2012 ~/.mail_aliases so that I can make my ~/.muttrc readable and keep my
2015 If the filename begins with a tilde (``~''), it will be expanded to
2016 the path of your home directory.
2018 If the filename ends with a vertical bar (|), then
\e[4mfilename
\e[24m is
2019 considered to be an executable program from which to read input (eg.
2020 source ~/bin/myscript|).
2022 \e[1m3.27. Removing hooks
\e[0m
2024 Usage: unhook [ * |
\e[4mhook-type
\e[24m ]
2026 This command permits you to flush hooks you have previously defined.
2027 You can either remove all hooks by giving the ``*'' character as an
2028 argument, or you can remove all hooks of a specific type by saying
2029 something like unhook send-hook.
2031 \e[1m4. Advanced Usage
\e[0m
2033 \e[1m4.1. Regular Expressions
\e[0m
2035 All string patterns in Mutt including those in more complex
2036 ``patterns'' must be specified using regular expressions (regexp) in
2037 the ``POSIX extended'' syntax (which is more or less the syntax used
2038 by egrep and GNU awk). For your convenience, we have included below a
2039 brief description of this syntax.
2041 The search is case sensitive if the pattern contains at least one
2042 upper case letter, and case insensitive otherwise. Note that ``\''
2043 must be quoted if used for a regular expression in an initialization
2046 A regular expression is a pattern that describes a set of strings.
2047 Regular expressions are constructed analogously to arithmetic
2048 expressions, by using various operators to combine smaller
2051 Note that the regular expression can be enclosed/delimited by either "
2052 or ' which is useful if the regular expression includes a white-space
2053 character. See ``Syntax of Initialization Files'' for more
2054 information on " and ' delimiter processing. To match a literal " or
2055 ' you must preface it with \ (backslash).
2057 The fundamental building blocks are the regular expressions that match
2058 a single character. Most characters, including all letters and
2059 digits, are regular expressions that match themselves. Any
2060 metacharacter with special meaning may be quoted by preceding it with
2063 The period ``.'' matches any single character. The caret ``^'' and
2064 the dollar sign ``$'' are metacharacters that respectively match the
2065 empty string at the beginning and end of a line.
2067 A list of characters enclosed by ``['' and ``]'' matches any single
2068 character in that list; if the first character of the list is a caret
2069 ``^'' then it matches any character
\e[1mnot
\e[22min the list. For example, the
2070 regular expression
\e[1m[0123456789]
\e[22mmatches any single digit. A range of
2071 ASCII characters may be specified by giving the first and last
2072 characters, separated by a hyphen ``-''. Most metacharacters lose
2073 their special meaning inside lists. To include a literal ``]'' place
2074 it first in the list. Similarly, to include a literal ``^'' place it
2075 anywhere but first. Finally, to include a literal hyphen ``-'' place
2078 Certain named classes of characters are predefined. Character classes
2079 consist of ``[:'', a keyword denoting the class, and ``:]''. The
2080 following classes are defined by the POSIX standard:
2083 Alphanumeric characters.
2086 Alphabetic characters.
2089 Space or tab characters.
2098 Characters that are both printable and visible. (A space is
2099 printable, but not visible, while an ``a'' is both.)
2102 Lower-case alphabetic characters.
2105 Printable characters (characters that are not control
2109 Punctuation characters (characters that are not letter, digits,
2110 control characters, or space characters).
2113 Space characters (such as space, tab and formfeed, to name a
2117 Upper-case alphabetic characters.
2119 \e[1m[:xdigit:]
\e[0m
2120 Characters that are hexadecimal digits.
2122 A character class is only valid in a regular expression inside the
2123 brackets of a character list. Note that the brackets in these class
2124 names are part of the symbolic names, and must be included in addition
2125 to the brackets delimiting the bracket list. For example,
\e[1m[[:digit:]]
\e[0m
2126 is equivalent to
\e[1m[0-9]
\e[22m.
2128 Two additional special sequences can appear in character lists. These
2129 apply to non-ASCII character sets, which can have single symbols
2130 (called collating elements) that are represented with more than one
2131 character, as well as several characters that are equivalent for
2132 collating or sorting purposes:
2134 \e[1mCollating Symbols
\e[0m
2135 A collating symbol is a multi-character collating element
2136 enclosed in ``[.'' and ``.]''. For example, if ``ch'' is a
2137 collating element, then
\e[1m[[.ch.]]
\e[22mis a regexp that matches this
2138 collating element, while
\e[1m[ch]
\e[22mis a regexp that matches either
2141 \e[1mEquivalence Classes
\e[0m
2142 An equivalence class is a locale-specific name for a list of
2143 characters that are equivalent. The name is enclosed in ``[=''
2144 and ``=]''. For example, the name ``e'' might be used to
2145 represent all of ``è'' ``é'' and ``e''. In this case,
\e[1m[[=e=]]
\e[0m
2146 is a regexp that matches any of ``è'', ``é'' and ``e''.
2147 A regular expression matching a single character may be followed by
2148 one of several repetition operators:
2150 \e[1m?
\e[22mThe preceding item is optional and matched at most once.
2152 \e[1m*
\e[22mThe preceding item will be matched zero or more times.
2154 \e[1m+
\e[22mThe preceding item will be matched one or more times.
2157 The preceding item is matched exactly
\e[4mn
\e[24m times.
2160 The preceding item is matched
\e[4mn
\e[24m or more times.
2163 The preceding item is matched at most
\e[4mm
\e[24m times.
2166 The preceding item is matched at least
\e[4mn
\e[24m times, but no more than
2169 Two regular expressions may be concatenated; the resulting regular
2170 expression matches any string formed by concatenating two substrings
2171 that respectively match the concatenated subexpressions.
2173 Two regular expressions may be joined by the infix operator ``|''; the
2174 resulting regular expression matches any string matching either
2177 Repetition takes precedence over concatenation, which in turn takes
2178 precedence over alternation. A whole subexpression may be enclosed in
2179 parentheses to override these precedence rules.
2181 \e[1mNote:
\e[22mIf you compile Mutt with the GNU
\e[4mrx
\e[24m package, the following
2182 operators may also be used in regular expressions:
2185 Matches the empty string at either the beginning or the end of a
2189 Matches the empty string within a word.
2192 Matches the empty string at the beginning of a word.
2195 Matches the empty string at the end of a word.
2198 Matches any word-constituent character (letter, digit, or
2202 Matches any character that is not word-constituent.
2205 Matches the empty string at the beginning of a buffer (string).
2208 Matches the empty string at the end of a buffer.
2210 Please note however that these operators are not defined by POSIX, so
2211 they may or may not be available in stock libraries on various
2214 \e[1m4.2. Patterns
\e[0m
2216 Many of Mutt's commands allow you to specify a pattern to match
2217 (limit, tag-pattern, delete-pattern, etc.). There are several ways to
2221 ~b EXPR messages which contain EXPR in the message body
2222 ~B EXPR messages which contain EXPR in the whole message
2223 ~c USER messages carbon-copied to USER
2224 ~C EXPR message is either to: or cc: EXPR
2226 ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
2228 ~e EXPR message which contains EXPR in the ``Sender'' field
2230 ~f USER messages originating from USER
2231 ~g cryptographically signed messages
2232 ~G cryptographically encrypted messages
2233 ~H EXPR messages with a spam attribute matching EXPR
2234 ~h EXPR messages which contain EXPR in the message header
2235 ~k message contains PGP key material
2236 ~i ID message which match ID in the ``Message-ID'' field
2237 ~L EXPR message is either originated or received by EXPR
2238 ~l message is addressed to a known mailing list
2239 ~m [MIN]-[MAX] message in the range MIN to MAX *)
2240 ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
2243 ~p message is addressed to you (consults alternates)
2244 ~P message is from you (consults alternates)
2245 ~Q messages which have been replied to
2247 ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
2248 ~S superseded messages
2249 ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
2251 ~t USER messages addressed to USER
2253 ~v message is part of a collapsed thread.
2254 ~V cryptographically verified messages
2255 ~x EXPR messages which contain EXPR in the `References' field
2256 ~y EXPR messages which contain EXPR in the `X-Label' field
2257 ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
2258 ~= duplicated messages (see $duplicate_threads)
2259 ~$ unreferenced messages (requires threaded view)
2261 Where EXPR, USER, ID, and SUBJECT are ``regular expressions''.
2262 Special attention has to be made when using regular expressions inside
2263 of patterns. Specifically, Mutt's parser for these patterns will
2264 strip one level of backslash (\), which is normally used for quoting.
2265 If it is your intention to use a backslash in the regular expression,
2266 you will need to use two backslashes instead (\\).
2268 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
2270 \e[1m4.2.1. Pattern Modifier
\e[0m
2272 Note that patterns matching 'lists' of addresses (notably c,C,p,P and
2273 t) match if there is at least one match in the whole list. If you want
2274 to make sure that all elements of that list match, you need to prefix
2275 your pattern with ^. This example matches all mails which only has
2276 recipients from Germany.
2280 \e[1m4.2.2. Complex Patterns
\e[0m
2282 Logical AND is performed by specifying more than one criterion. For
2287 would select messages which contain the word ``mutt'' in the list of
2288 recipients
\e[1mand
\e[22mthat have the word ``elkins'' in the ``From'' header
2291 Mutt also recognizes the following operators to create more complex
2294 · ! -- logical NOT operator
2296 · | -- logical OR operator
2298 · () -- logical grouping operator
2300 Here is an example illustrating a complex search pattern. This
2301 pattern will select all messages which do not contain ``mutt'' in the
2302 ``To'' or ``Cc'' field and which are from ``elkins''.
2304 !(~t mutt|~c mutt) ~f elkins
2306 Here is an example using white space in the regular expression (note
2307 the ' and " delimiters). For this to match, the mail's subject must
2308 match the ``^Junk +From +Me$'' and it must be from either ``Jim
2309 +Somebody'' or ``Ed +SomeoneElse'':
2311 '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
2313 Note that if a regular expression contains parenthesis, or a veritical
2314 bar ("|"), you
\e[1mmust
\e[22menclose the expression in double or single quotes
2315 since those characters are also used to separate different parts of
2316 Mutt's pattern language. For example,
2318 ~f "me@(mutt\.org|cs\.hmc\.edu)"
2320 Without the quotes, the parenthesis wouldn't end. This would be
2321 seperated to two OR'd patterns:
\e[4m~f
\e[24m
\e[4mme@(mutt\.org
\e[24m and
\e[4mcs\.hmc\.edu)
\e[24m.
2322 They are never what you want.
2324 \e[1m4.2.3. Searching by Date
\e[0m
2326 Mutt supports two types of dates,
\e[4mabsolute
\e[24m and
\e[4mrelative
\e[24m.
2328 \e[1mAbsolute
\e[22m. Dates
\e[1mmust
\e[22mbe in DD/MM/YY format (month and year are
2329 optional, defaulting to the current month and year). An example of a
2330 valid range of dates is:
2332 Limit to messages matching: ~d 20/1/95-31/10
2334 If you omit the minimum (first) date, and just specify ``-DD/MM/YY'',
2335 all messages
\e[4mbefore
\e[24m the given date will be selected. If you omit the
2336 maximum (second) date, and specify ``DD/MM/YY-'', all messages
\e[4mafter
\e[0m
2337 the given date will be selected. If you specify a single date with no
2338 dash (``-''), only messages sent on the given date will be selected.
2340 \e[1mError Margins
\e[22m. You can add error margins to absolute dates. An error
2341 margin is a sign (+ or -), followed by a digit, followed by one of the
2349 As a special case, you can replace the sign by a ``*'' character,
2350 which is equivalent to giving identical plus and minus error margins.
2352 Example: To select any messages two weeks around January 15, 2001,
2353 you'd use the following pattern:
2355 Limit to messages matching: ~d 15/1/2001*2w
2357 \e[1mRelative
\e[22m. This type of date is relative to the current date, and may
2360 · >
\e[4moffset
\e[24m (messages older than
\e[4moffset
\e[24m units)
2362 · <
\e[4moffset
\e[24m (messages newer than
\e[4moffset
\e[24m units)
2364 · =
\e[4moffset
\e[24m (messages exactly
\e[4moffset
\e[24m units old)
2366 \e[4moffset
\e[24m is specified as a positive number with one of the following
2374 Example: to select messages less than 1 month old, you would use
2376 Limit to messages matching: ~d <1m
2378 \e[1mNote:
\e[22mall dates used when searching are relative to the
\e[1mlocal
\e[22mtime
2379 zone, so unless you change the setting of your ``$index_format'' to
2380 include a %[...] format, these are
\e[1mnot
\e[22mthe dates shown in the main
2383 \e[1m4.3. Using Tags
\e[0m
2385 Sometimes it is desirable to perform an operation on a group of
2386 messages all at once rather than one at a time. An example might be
2387 to save messages to a mailing list to a separate folder, or to delete
2388 all messages with a given subject. To tag all messages matching a
2389 pattern, use the tag-pattern function, which is bound to ``shift-T''
2390 by default. Or you can select individual messages by hand using the
2391 ``tag-message'' function, which is bound to ``t'' by default. See
2392 ``patterns'' for Mutt's pattern matching syntax.
2394 Once you have tagged the desired messages, you can use the ``tag-
2395 prefix'' operator, which is the ``;'' (semicolon) key by default.
2396 When the ``tag-prefix'' operator is used, the
\e[1mnext
\e[22moperation will be
2397 applied to all tagged messages if that operation can be used in that
2398 manner. If the ``$auto_tag'' variable is set, the next operation
2399 applies to the tagged messages automatically, without requiring the
2402 In ``macros'' or ``push'' commands, you can use the ``tag-prefix-
2403 cond'' operator. If there are no tagged messages, mutt will "eat" the
2404 rest of the macro to abort it's execution. Mutt will stop "eating"
2405 the macro when it encounters the ``end-cond'' operator; after this
2406 operator the rest of the macro will be executed as normal.
2408 \e[1m4.4. Using Hooks
\e[0m
2410 A
\e[4mhook
\e[24m is a concept borrowed from the EMACS editor which allows you to
2411 execute arbitrary commands before performing some operation. For
2412 example, you may wish to tailor your configuration based upon which
2413 mailbox you are reading, or to whom you are sending mail. In the Mutt
2414 world, a
\e[4mhook
\e[24m consists of a ``regular expression'' or ``pattern''
2415 along with a configuration option/command. See
2431 for specific details on each type of
\e[4mhook
\e[24m available.
2433 \e[1mNote:
\e[22mif a hook changes configuration settings, these changes remain
2434 effective until the end of the current mutt session. As this is
2435 generally not desired, a default hook needs to be added before all
2436 other hooks to restore configuration defaults. Here is an example with
2437 send-hook and the my_hdr directive:
2439 send-hook . 'unmy_hdr From:'
2440 send-hook ~Cb@b.b my_hdr from: c@c.c
2442 \e[1m4.4.1. Message Matching in Hooks
\e[0m
2444 Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-
2445 hook) are evaluated in a slightly different manner. For the other
2446 types of hooks, a ``regular expression'' is sufficient. But in
2447 dealing with messages a finer grain of control is needed for matching
2448 since for different purposes you want to match different criteria.
2450 Mutt allows the use of the ``search pattern'' language for matching
2451 messages in hook commands. This works in exactly the same way as it
2452 would when
\e[4mlimiting
\e[24m or
\e[4msearching
\e[24m the mailbox, except that you are
2453 restricted to those operators which match information mutt extracts
2454 from the header of the message (i.e. from, to, cc, date, subject,
2457 For example, if you wanted to set your return address based upon
2458 sending mail to a specific address, you could do something like:
2460 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
2462 which would execute the given command when sending mail to
2463 \e[4mme@cs.hmc.edu
\e[24m.
2465 However, it is not required that you write the pattern to match using
2466 the full searching language. You can still specify a simple
\e[4mregular
\e[0m
2467 \e[4mexpression
\e[24m like the other hooks, in which case Mutt will translate
2468 your pattern into the full language, using the translation specified
2469 by the ``$default_hook'' variable. The pattern is translated at the
2470 time the hook is declared, so the value of ``$default_hook'' that is
2471 in effect at that time will be used.
2473 \e[1m4.5. External Address Queries
\e[0m
2475 Mutt supports connecting to external directory databases such as LDAP,
2476 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
2477 using a simple interface. Using the ``$query_command'' variable, you
2478 specify the wrapper command to use. For example:
2480 set query_command = "mutt_ldap_query.pl '%s'"
2482 The wrapper script should accept the query on the command-line. It
2483 should return a one line message, then each matching response on a
2484 single line, each line containing a tab separated address then name
2485 then some other optional information. On error, or if there are no
2486 matching addresses, return a non-zero exit code and a one line error
2489 An example multiple response output:
2491 Searching database ... 20 entries ... 3 matching:
2492 me@cs.hmc.edu Michael Elkins mutt dude
2493 blong@fiction.net Brandon Long mutt and more
2494 roessler@guug.de Thomas Roessler mutt pgp
2496 There are two mechanisms for accessing the query function of mutt.
2497 One is to do a query from the index menu using the query function
2498 (default: Q). This will prompt for a query, then bring up the query
2499 menu which will list the matching responses. From the query menu, you
2500 can select addresses to create aliases, or to mail. You can tag
2501 multiple addresses to mail, start a new query, or have a new query
2502 appended to the current responses.
2504 The other mechanism for accessing the query function is for address
2505 completion, similar to the alias completion. In any prompt for
2506 address entry, you can use the complete-query function (default: ^T)
2507 to run a query based on the current address you have typed. Like
2508 aliases, mutt will look for what you have typed back to the last space
2509 or comma. If there is a single response for that query, mutt will
2510 expand the address in place. If there are multiple responses, mutt
2511 will activate the query menu. At the query menu, you can select one
2512 or more addresses to be added to the prompt.
2514 \e[1m4.6. Mailbox Formats
\e[0m
2516 Mutt supports reading and writing of four different mailbox formats:
2517 mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so
2518 there is no need to use a flag for different mailbox types. When
2519 creating new mailboxes, Mutt uses the default specified with the
2520 ``$mbox_type'' variable.
2522 \e[1mmbox
\e[22m. This is the most widely used mailbox format for UNIX. All
2523 messages are stored in a single file. Each message has a line of the
2526 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2528 to denote the start of a new message (this is often referred to as the
2531 \e[1mMMDF
\e[22m. This is a variant of the
\e[4mmbox
\e[24m format. Each message is
2532 surrounded by lines containing ``^A^A^A^A'' (four control-A's).
2534 \e[1mMH
\e[22m. A radical departure from
\e[4mmbox
\e[24m and
\e[4mMMDF
\e[24m, a mailbox consists of a
2535 directory and each message is stored in a separate file. The filename
2536 indicates the message number (however, this is may not correspond to
2537 the message number Mutt displays). Deleted messages are renamed with a
2538 comma (,) prepended to the filename.
\e[1mNote:
\e[22mMutt detects this type of
2539 mailbox by looking for either .mh_sequences or .xmhcache (needed to
2540 distinguish normal directories from MH mailboxes).
2542 \e[1mMaildir
\e[22m. The newest of the mailbox formats, used by the Qmail MTA (a
2543 replacement for sendmail). Similar to
\e[4mMH
\e[24m, except that it adds three
2544 subdirectories of the mailbox:
\e[4mtmp
\e[24m,
\e[4mnew
\e[24m and
\e[4mcur
\e[24m. Filenames for the
2545 messages are chosen in such a way they are unique, even when two
2546 programs are writing the mailbox over NFS, which means that no file
2549 \e[1m4.7. Mailbox Shortcuts
\e[0m
2551 There are a number of built in shortcuts which refer to specific
2552 mailboxes. These shortcuts can be used anywhere you are prompted for
2553 a file or mailbox path.
2555 · ! -- refers to your ``$spoolfile'' (incoming) mailbox
2557 · > -- refers to your ``$mbox'' file
2559 · < -- refers to your ``$record'' file
2561 · - or !! -- refers to the file you've last visited
2563 · ~ -- refers to your home directory
2565 · = or + -- refers to your ``$folder'' directory
2567 · @
\e[4malias
\e[24m -- refers to the ``default save folder'' as determined by
2568 the address of the alias
2570 \e[1m4.8. Handling Mailing Lists
\e[0m
2572 Mutt has a few configuration options that make dealing with large
2573 amounts of mail easier. The first thing you must do is to let Mutt
2574 know what addresses you consider to be mailing lists (technically this
2575 does not have to be a mailing list, but that is what it is most often
2576 used for), and what lists you are subscribed to. This is accomplished
2577 through the use of the ``lists and subscribe'' commands in your
2580 Now that Mutt knows what your mailing lists are, it can do several
2581 things, the first of which is the ability to show the name of a list
2582 through which you received a message (i.e., of a subscribed list) in
2583 the
\e[4mindex
\e[24m menu display. This is useful to distinguish between
2584 personal and list mail in the same mailbox. In the ``$index_format''
2585 variable, the escape ``%L'' will return the string ``To <list>'' when
2586 ``list'' appears in the ``To'' field, and ``Cc <list>'' when it
2587 appears in the ``Cc'' field (otherwise it returns the name of the
2590 Often times the ``To'' and ``Cc'' fields in mailing list messages tend
2591 to get quite large. Most people do not bother to remove the author of
2592 the message they are reply to from the list, resulting in two or more
2593 copies being sent to that person. The ``list-reply'' function, which
2594 by default is bound to ``L'' in the
\e[4mindex
\e[24m menu and
\e[4mpager
\e[24m, helps reduce
2595 the clutter by only replying to the known mailing list addresses
2596 instead of all recipients (except as specified by Mail-Followup-To,
2599 Mutt also supports the Mail-Followup-To header. When you send a
2600 message to a list of recipients which includes one or several
2601 subscribed mailing lists, and if the ``$followup_to'' option is set,
2602 mutt will generate a Mail-Followup-To header which contains all the
2603 recipients to whom you send this message, but not your address. This
2604 indicates that group-replies or list-replies (also known as
2605 ``followups'') to this message should only be sent to the original
2606 recipients of the message, and not separately to you - you'll receive
2607 your copy through one of the mailing lists you are subscribed to.
2609 Conversely, when group-replying or list-replying to a message which
2610 has a Mail-Followup-To header, mutt will respect this header if the
2611 ``$honor_followup_to'' configuration variable is set. Using list-
2612 reply will in this case also make sure that the reply goes to the
2613 mailing list, even if it's not specified in the list of recipients in
2614 the Mail-Followup-To.
2616 Note that, when header editing is enabled, you can create a Mail-
2617 Followup-To header manually. Mutt will only auto-generate this header
2618 if it doesn't exist when you send the message.
2620 The other method some mailing list admins use is to generate a
2621 ``Reply-To'' field which points back to the mailing list address
2622 rather than the author of the message. This can create problems when
2623 trying to reply directly to the author in private, since most mail
2624 clients will automatically reply to the address given in the ``Reply-
2625 To'' field. Mutt uses the ``$reply_to'' variable to help decide which
2626 address to use. If set, you will be prompted as to whether or not you
2627 would like to use the address given in the ``Reply-To'' field, or
2628 reply directly to the address given in the ``From'' field. When
2629 unset, the ``Reply-To'' field will be used when present.
2631 The ``X-Label:'' header field can be used to further identify mailing
2632 lists or list subject matter (or just to annotate messages
2633 individually). The ``$index_format'' variable's ``%y'' and ``%Y''
2634 escapes can be used to expand ``X-Label:'' fields in the index, and
2635 Mutt's pattern-matcher can match regular expressions to ``X-Label:''
2636 fields with the ``y'' selector. ``X-Label:'' is not a standard
2637 message header field, but it can easily be inserted by procmail and
2638 other mail filtering agents.
2640 Lastly, Mutt has the ability to ``sort'' the mailbox into ``threads''.
2641 A thread is a group of messages which all relate to the same subject.
2642 This is usually organized into a tree-like structure where a message
2643 and all of its replies are represented graphically. If you've ever
2644 used a threaded news client, this is the same concept. It makes
2645 dealing with large volume mailing lists easier because you can easily
2646 delete uninteresting threads and quickly find topics of value.
2648 \e[1m4.9. Delivery Status Notification (DSN) Support
\e[0m
2650 RFC1894 defines a set of MIME content types for relaying information
2651 about the status of electronic mail messages. These can be thought of
2652 as ``return receipts.'' Berkeley sendmail 8.8.x currently has some
2653 command line options in which the mail client can make requests as to
2654 what type of status messages should be returned.
2656 To support this, there are two variables. ``$dsn_notify'' is used to
2657 request receipts for different results (such as failed message,
2658 message delivered, etc.). ``$dsn_return'' requests how much of your
2659 message should be returned with the receipt (headers or full message).
2660 Refer to the man page on sendmail for more details on DSN.
2662 \e[1m4.10. POP3 Support (OPTIONAL)
\e[0m
2664 If Mutt was compiled with POP3 support (by running the
\e[4mconfigure
\e[0m
2665 script with the
\e[4m--enable-pop
\e[24m flag), it has the ability to work with
2666 mailboxes located on a remote POP3 server and fetch mail for local
2669 You can access the remote POP3 mailbox by selecting the folder
2672 You can select an alternative port by specifying it with the server,
2673 ie: pop://popserver:port/.
2675 You can also specify different username for each folder, ie:
2676 pop://username@popserver[:port]/.
2678 Polling for new mail is more expensive over POP3 than locally. For
2679 this reason the frequency at which Mutt will check for mail remotely
2680 can be controlled by the ``$pop_checkinterval'' variable, which
2681 defaults to every 60 seconds.
2683 If Mutt was compiled with SSL support (by running the
\e[4mconfigure
\e[24m script
2684 with the
\e[4m--with-ssl
\e[24m flag), connections to POP3 servers can be
2685 encrypted. This naturally requires that the server supports SSL
2686 encrypted connections. To access a folder with POP3/SSL, you should
2687 use pops: prefix, ie: pops://[username@]popserver[:port]/.
2689 Another way to access your POP3 mail is the
\e[4mfetch-mail
\e[24m function
2690 (default: G). It allows to connect to ``pop_host'', fetch all your
2691 new mail and place it in the local ``spoolfile''. After this point,
2692 Mutt runs exactly as if the mail had always been local.
2694 \e[1mNote:
\e[22mIf you only need to fetch all messages to local mailbox you
2695 should consider using a specialized program, such as fetchmail
2697 \e[1m4.11. IMAP Support (OPTIONAL)
\e[0m
2699 If Mutt was compiled with IMAP support (by running the
\e[4mconfigure
\e[0m
2700 script with the
\e[4m--enable-imap
\e[24m flag), it has the ability to work with
2701 folders located on a remote IMAP server.
2703 You can access the remote inbox by selecting the folder
2704 imap://imapserver/INBOX, where imapserver is the name of the IMAP
2705 server and INBOX is the special name for your spool mailbox on the
2706 IMAP server. If you want to access another mail folder at the IMAP
2707 server, you should use imap://imapserver/path/to/folder where
2708 path/to/folder is the path of the folder you want to access.
2710 You can select an alternative port by specifying it with the server,
2711 ie: imap://imapserver:port/INBOX.
2713 You can also specify different username for each folder, ie:
2714 imap://username@imapserver[:port]/INBOX.
2716 If Mutt was compiled with SSL support (by running the
\e[4mconfigure
\e[24m script
2717 with the
\e[4m--with-ssl
\e[24m flag), connections to IMAP servers can be
2718 encrypted. This naturally requires that the server supports SSL
2719 encrypted connections. To access a folder with IMAP/SSL, you should
2720 use imaps://[username@]imapserver[:port]/path/to/folder as your folder
2723 Pine-compatible notation is also supported, ie
2724 {[username@]imapserver[:port][/ssl]}path/to/folder
2726 Note that not all servers use / as the hierarchy separator. Mutt
2727 should correctly notice which separator is being used by the server
2728 and convert paths accordingly.
2730 When browsing folders on an IMAP server, you can toggle whether to
2731 look at only the folders you are subscribed to, or all folders with
2732 the
\e[4mtoggle-subscribed
\e[24m command. See also the ``$imap_list_subscribed''
2735 Polling for new mail on an IMAP server can cause noticeable delays.
2736 So, you'll want to carefully tune the ``$mail_check'' and ``$timeout''
2737 variables. Personally I use
2742 with relatively good results over my slow modem line.
2744 Note that if you are using mbox as the mail store on UW servers prior
2745 to v12.250, the server has been reported to disconnect a client if
2746 another client selects the same folder.
2748 \e[1m4.11.1. The Folder Browser
\e[0m
2750 As of version 1.2, mutt supports browsing mailboxes on an IMAP server.
2751 This is mostly the same as the local file browser, with the following
2754 · In lieu of file permissions, mutt displays the string "IMAP",
2755 possibly followed by the symbol "+", indicating that the entry
2756 contains both messages and subfolders. On Cyrus-like servers
2757 folders will often contain both messages and subfolders.
2759 · For the case where an entry can contain both messages and
2760 subfolders, the selection key (bound to enter by default) will
2761 choose to descend into the subfolder view. If you wish to view the
2762 messages in that folder, you must use view-file instead (bound to
2765 · You can delete mailboxes with the delete-mailbox command (bound to
2766 d by default. You may also subscribe and unsubscribe to mailboxes
2767 (normally these are bound to s and u, respectively).
2769 \e[1m4.11.2. Authentication
\e[0m
2771 Mutt supports four authentication methods with IMAP servers: SASL,
2772 GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
2773 NTLM authentication for you poor exchange users out there, but it has
2774 yet to be integrated into the main tree). There is also support for
2775 the pseudo-protocol ANONYMOUS, which allows you to log in to a public
2776 IMAP server without having an account. To use ANONYMOUS, simply make
2777 your username blank or "anonymous".
2779 SASL is a special super-authenticator, which selects among several
2780 protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the
2781 most secure method available on your host and the server. Using some
2782 of these methods (including DIGEST-MD5 and possibly GSSAPI), your
2783 entire session will be encrypted and invisible to those teeming
2784 network snoops. It is the best option if you have it. To use it, you
2785 must have the Cyrus SASL library installed on your system and compile
2786 mutt with the
\e[4m--with-sasl
\e[24m flag.
2788 Mutt will try whichever methods are compiled in and available on the
2789 server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5,
2792 There are a few variables which control authentication:
2794 · ``$imap_user'' - controls the username under which you request
2795 authentication on the IMAP server, for all authenticators. This is
2796 overridden by an explicit username in the mailbox path (ie by using
2797 a mailbox name of the form {user@host}).
2799 · ``$imap_pass'' - a password which you may preset, used by all
2800 authentication methods where a password is needed.
2802 · ``$imap_authenticators'' - a colon-delimited list of IMAP
2803 authentication methods to try, in the order you wish to try them.
2804 If specified, this overrides mutt's default (attempt everything, in
2805 the order listed above).
2807 \e[1m4.12. Managing multiple IMAP/POP accounts (OPTIONAL)
\e[0m
2809 If you happen to have accounts on multiple IMAP and/or POP servers,
2810 you may find managing all the authentication settings inconvenient and
2811 error-prone. The account-hook command may help. This hook works like
2812 folder-hook but is invoked whenever you access a remote mailbox
2813 (including inside the folder browser), not just when you open the
2818 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
2819 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
2820 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
2822 \e[1m4.13. Start a WWW Browser on URLs (EXTERNAL)
\e[0m
2824 If a message contains URLs (
\e[4munified
\e[24m
\e[4mresource
\e[24m
\e[4mlocator
\e[24m = address in the
2825 WWW space like
\e[4mhttp://www.mutt.org/
\e[24m), it is efficient to get a menu
2826 with all the URLs and start a WWW browser on one of them. This
2827 functionality is provided by the external urlview program which can be
2828 retrieved at ftp://ftp.mutt.org/mutt/contrib/ and the configuration
2831 macro index \cb |urlview\n
2832 macro pager \cb |urlview\n
2834 \e[1m5. Mutt's MIME Support
\e[0m
2836 Quite a bit of effort has been made to make Mutt the premier text-mode
2837 MIME MUA. Every effort has been made to provide the functionality
2838 that the discerning MIME user requires, and the conformance to the
2839 standards wherever possible. When configuring Mutt for MIME, there
2840 are two extra types of configuration files which Mutt uses. One is
2841 the mime.types file, which contains the mapping of file extensions to
2842 IANA MIME types. The other is the mailcap file, which specifies the
2843 external commands to use for handling specific MIME types.
2845 \e[1m5.1. Using MIME in Mutt
\e[0m
2847 There are three areas/menus in Mutt which deal with MIME, they are the
2848 pager (while viewing a message), the attachment menu and the compose
2851 \e[1m5.1.1. Viewing MIME messages in the pager
\e[0m
2853 When you select a message from the index and view it in the pager,
2854 Mutt decodes the message to a text representation. Mutt internally
2855 supports a number of MIME types, including text/plain, text/enriched,
2856 message/rfc822, and message/news. In addition, the export controlled
2857 version of Mutt recognizes a variety of PGP MIME types, including
2858 PGP/MIME and application/pgp.
2860 Mutt will denote attachments with a couple lines describing them.
2861 These lines are of the form:
2863 [-- Attachment #1: Description --]
2864 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
2866 Where the Description is the description or filename given for the
2867 attachment, and the Encoding is one of 7bit/8bit/quoted-print-
2870 If Mutt cannot deal with a MIME type, it will display a message like:
2872 [-- image/gif is unsupported (use 'v' to view this part) --]
2874 \e[1m5.1.2. The Attachment Menu
\e[0m
2876 The default binding for view-attachments is `v', which displays the
2877 attachment menu for a message. The attachment menu displays a list of
2878 the attachments in a message. From the attachment menu, you can save,
2879 print, pipe, delete, and view attachments. You can apply these
2880 operations to a group of attachments at once, by tagging the
2881 attachments and by using the ``tag-prefix'' operator. You can also
2882 reply to the current message from this menu, and only the current
2883 attachment (or the attachments tagged) will be quoted in your reply.
2884 You can view attachments as text, or view them using the mailcap
2887 Finally, you can apply the usual message-related functions (like
2888 ``resend-message'', and the reply and forward functions) to
2889 attachments of type message/rfc822.
2891 See the help on the attachment menu for more information.
2893 \e[1m5.1.3. The Compose Menu
\e[0m
2895 The compose menu is the menu you see before you send a message. It
2896 allows you to edit the recipient list, the subject, and other aspects
2897 of your message. It also contains a list of the attachments of your
2898 message, including the main body. From this menu, you can print,
2899 copy, filter, pipe, edit, compose, review, and rename an attachment or
2900 a list of tagged attachments. You can also modifying the attachment
2901 information, notably the type, encoding and description.
2903 Attachments appear as follows:
2905 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
2906 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
2908 The '-' denotes that Mutt will delete the file after sending (or
2909 postponing, or cancelling) the message. It can be toggled with the
2910 toggle-unlink command (default: u). The next field is the MIME
2911 content-type, and can be changed with the edit-type command (default:
2912 ^T). The next field is the encoding for the attachment, which allows
2913 a binary message to be encoded for transmission on 7bit links. It can
2914 be changed with the edit-encoding command (default: ^E). The next
2915 field is the size of the attachment, rounded to kilobytes or
2916 megabytes. The next field is the filename, which can be changed with
2917 the rename-file command (default: R). The final field is the
2918 description of the attachment, and can be changed with the edit-
2919 description command (default: d).
2921 \e[1m5.2. MIME Type configuration with mime.types
\e[0m
2923 When you add an attachment to your mail message, Mutt searches your
2924 personal mime.types file at ${HOME}/.mime.types, and then the system
2925 mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types
2927 The mime.types file consist of lines containing a MIME type and a
2928 space separated list of extensions. For example:
2930 application/postscript ps eps
2932 audio/x-aiff aif aifc aiff
2934 A sample mime.types file comes with the Mutt distribution, and should
2935 contain most of the MIME types you are likely to use.
2937 If Mutt can not determine the mime type by the extension of the file
2938 you attach, it will look at the file. If the file is free of binary
2939 information, Mutt will assume that the file is plain text, and mark it
2940 as text/plain. If the file contains binary information, then Mutt
2941 will mark it as application/octet-stream. You can change the MIME
2942 type that Mutt assigns to an attachment by using the edit-type command
2943 from the compose menu (default: ^T). The MIME type is actually a major
2944 mime type followed by the sub-type, separated by a '/'. 6 major types:
2945 application, text, image, video, audio, and model have been approved
2946 after various internet discussions. Mutt recognises all of these if
2947 the appropriate entry is found in the mime.types file. It also
2948 recognises other major mime types, such as the chemical type that is
2949 widely used in the molecular modelling community to pass molecular
2950 data in various forms to various molecular viewers. Non-recognised
2951 mime types should only be used if the recipient of the message is
2952 likely to be expecting such attachments.
2954 \e[1m5.3. MIME Viewer configuration with mailcap
\e[0m
2956 Mutt supports RFC 1524 MIME Configuration, in particular the Unix
2957 specific format specified in Appendix A of RFC 1524. This file format
2958 is commonly referred to as the mailcap format. Many MIME compliant
2959 programs utilize the mailcap format, allowing you to specify handling
2960 for all MIME types in one place for all programs. Programs known to
2961 use this format include Netscape, XMosaic, lynx and metamail.
2963 In order to handle various MIME types that Mutt can not handle
2964 internally, Mutt parses a series of external configuration files to
2965 find an external handler. The default search string for these files
2966 is a colon delimited list set to
2968 ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
2970 where $HOME is your home directory.
2972 In particular, the metamail distribution will install a mailcap file,
2973 usually as /usr/local/etc/mailcap, which contains some baseline
2976 \e[1m5.3.1. The Basics of the mailcap file
\e[0m
2978 A mailcap file consists of a series of lines which are comments,
2979 blank, or definitions.
2981 A comment line consists of a # character followed by anything you
2984 A blank line is blank.
2986 A definition line consists of a content type, a view command, and any
2987 number of optional fields. Each field of a definition line is divided
2988 by a semicolon ';' character.
2990 The content type is specified in the MIME standard type/subtype
2991 method. For example, text/plain, text/html, image/gif, etc. In
2992 addition, the mailcap format includes two formats for wildcards, one
2993 using the special '*' subtype, the other is the implicit wild, where
2994 you only include the major type. For example, image/*, or video, will
2995 match all image types and video types, respectively.
2997 The view command is a Unix command for viewing the type specified.
2998 There are two different types of commands supported. The default is to
2999 send the body of the MIME message to the command on stdin. You can
3000 change this behaviour by using %s as a parameter to your view command.
3001 This will cause Mutt to save the body of the MIME message to a
3002 temporary file, and then call the view command with the %s replaced by
3003 the name of the temporary file. In both cases, Mutt will turn over the
3004 terminal to the view program until the program quits, at which time
3005 Mutt will remove the temporary file if it exists.
3007 So, in the simplest form, you can send a text/plain message to the
3008 external pager more on stdin:
3012 Or, you could send the message as a file:
3016 Perhaps you would like to use lynx to interactively view a text/html
3021 In this case, lynx does not support viewing a file from stdin, so you
3022 must use the %s syntax.
\e[1mNote:
\e[4m
\e[22mSome
\e[24m
\e[4molder
\e[24m
\e[4mversions
\e[24m
\e[4mof
\e[24m
\e[4mlynx
\e[24m
\e[4mcontain
\e[24m
\e[4ma
\e[0m
3023 \e[4mbug
\e[24m
\e[4mwhere
\e[24m
\e[4mthey
\e[24m
\e[4mwill
\e[24m
\e[4mcheck
\e[24m
\e[4mthe
\e[24m
\e[4mmailcap
\e[24m
\e[4mfile
\e[24m
\e[4mfor
\e[24m
\e[4ma
\e[24m
\e[4mviewer
\e[24m
\e[4mfor
\e[24m
\e[4mtext/html.
\e[0m
3024 \e[4mThey
\e[24m
\e[4mwill
\e[24m
\e[4mfind
\e[24m
\e[4mthe
\e[24m
\e[4mline
\e[24m
\e[4mwhich
\e[24m
\e[4mcalls
\e[24m
\e[4mlynx,
\e[24m
\e[4mand
\e[24m
\e[4mrun
\e[24m
\e[4mit.
\e[24m
\e[4mThis
\e[24m
\e[4mcauses
\e[0m
3025 \e[4mlynx
\e[24m
\e[4mto
\e[24m
\e[4mcontinuously
\e[24m
\e[4mspawn
\e[24m
\e[4mitself
\e[24m
\e[4mto
\e[24m
\e[4mview
\e[24m
\e[4mthe
\e[24m
\e[4mobject.
\e[0m
3027 On the other hand, maybe you don't want to use lynx interactively, you
3028 just want to have it convert the text/html to text/plain, then you can
3031 text/html; lynx -dump %s | more
3033 Perhaps you wish to use lynx to view text/html files, and a pager on
3034 all other text formats, then you would use the following:
3039 This is the simplest form of a mailcap file.
3040 \e[1m5.3.2. Secure use of mailcap
\e[0m
3042 The interpretion of shell meta-characters embedded in MIME parameters
3043 can lead to security problems in general. Mutt tries to quote
3044 parameters in expansion of %s syntaxes properly, and avoids risky
3045 characters by substituting them, see the ``mailcap_sanitize''
3048 Although mutt's procedures to invoke programs with mailcap seem to be
3049 safe, there are other applications parsing mailcap, maybe taking less
3050 care of it. Therefore you should pay attention to the following
3053 \e[4mKeep
\e[24m
\e[4mthe
\e[24m
\e[4m%-expandos
\e[24m
\e[4maway
\e[24m
\e[4mfrom
\e[24m
\e[4mshell
\e[24m
\e[4mquoting.
\e[24m Don't quote them with
3054 single or double quotes. Mutt does this for you, the right way, as
3055 should any other program which interprets mailcap. Don't put them
3056 into backtick expansions. Be highly careful with eval statements, and
3057 avoid them if possible at all. Trying to fix broken behaviour with
3058 quotes introduces new leaks - there is no alternative to correct
3059 quoting in the first place.
3061 If you have to use the %-expandos' values in context where you need
3062 quoting or backtick expansions, put that value into a shell variable
3063 and reference the shell variable where necessary, as in the following
3064 example (using $charset inside the backtick expansion is safe, since
3065 it is not itself subject to any further expansion):
3067 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
3068 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
3070 \e[1m5.3.3. Advanced mailcap Usage
\e[0m
3072 \e[1m5.3.3.1. Optional Fields
\e[0m
3074 In addition to the required content-type and view command fields, you
3075 can add semi-colon ';' separated fields to set flags and other
3076 options. Mutt recognizes the following optional fields:
3078 \e[1mcopiousoutput
\e[0m
3079 This flag tells Mutt that the command passes possibly large
3080 amounts of text on stdout. This causes Mutt to invoke a pager
3081 (either the internal pager or the external pager defined by the
3082 pager variable) on the output of the view command. Without this
3083 flag, Mutt assumes that the command is interactive. One could
3084 use this to replace the pipe to more in the lynx -dump example
3085 in the Basic section:
3087 text/html; lynx -dump %s ; copiousoutput
3089 This will cause lynx to format the text/html output as text/plain
3090 and Mutt will use your standard pager to display the results.
3092 \e[1mneedsterminal
\e[0m
3093 Mutt uses this flag when viewing attachments with ``autoview'',
3094 in order to decide whether it should honor the setting of the
3095 ``$wait_key'' variable or not. When an attachment is viewed
3096 using an interactive program, and the corresponding mailcap
3097 entry has a
\e[4mneedsterminal
\e[24m flag, Mutt will use ``$wait_key'' and
3098 the exit status of the program to decide if it will ask you to
3099 press a key after the external program has exited. In all other
3100 situations it will not prompt you for a key.
3102 \e[1mcompose=<command>
\e[0m
3103 This flag specifies the command to use to create a new
3104 attachment of a specific MIME type. Mutt supports this from the
3107 \e[1mcomposetyped=<command>
\e[0m
3108 This flag specifies the command to use to create a new
3109 attachment of a specific MIME type. This command differs from
3110 the compose command in that mutt will expect standard MIME
3111 headers on the data. This can be used to specify parameters,
3112 filename, description, etc. for a new attachment. Mutt
3113 supports this from the compose menu.
3115 \e[1mprint=<command>
\e[0m
3116 This flag specifies the command to use to print a specific MIME
3117 type. Mutt supports this from the attachment and compose menus.
3119 \e[1medit=<command>
\e[0m
3120 This flag specifies the command to use to edit a specific MIME
3121 type. Mutt supports this from the compose menu, and also uses
3122 it to compose new attachments. Mutt will default to the defined
3123 editor for text attachments.
3125 \e[1mnametemplate=<template>
\e[0m
3126 This field specifies the format for the file denoted by %s in
3127 the command fields. Certain programs will require a certain
3128 file extension, for instance, to correctly view a file. For
3129 instance, lynx will only interpret a file as text/html if the
3130 file ends in .html. So, you would specify lynx as a text/html
3131 viewer with a line in the mailcap file like:
3133 text/html; lynx %s; nametemplate=%s.html
3135 \e[1mtest=<command>
\e[0m
3136 This field specifies a command to run to test whether this
3137 mailcap entry should be used. The command is defined with the
3138 command expansion rules defined in the next section. If the
3139 command returns 0, then the test passed, and Mutt uses this
3140 entry. If the command returns non-zero, then the test failed,
3141 and Mutt continues searching for the right entry.
\e[1mNote:
\e[4m
\e[22mthe
\e[0m
3142 \e[4mcontent-type
\e[24m
\e[4mmust
\e[24m
\e[4mmatch
\e[24m
\e[4mbefore
\e[24m
\e[4mMutt
\e[24m
\e[4mperforms
\e[24m
\e[4mthe
\e[24m
\e[4mtest.
\e[24m For
3145 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3148 In this example, Mutt will run the program RunningX which will
3149 return 0 if the X Window manager is running, and non-zero if it
3150 isn't. If RunningX returns 0, then Mutt will call netscape to dis-
3151 play the text/html object. If RunningX doesn't return 0, then Mutt
3152 will go on to the next entry and use lynx to display the text/html
3155 \e[1m5.3.3.2. Search Order
\e[0m
3157 When searching for an entry in the mailcap file, Mutt will search for
3158 the most useful entry for its purpose. For instance, if you are
3159 attempting to print an image/gif, and you have the following entries
3160 in your mailcap file, Mutt will search for an entry with the print
3164 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
3167 Mutt will skip the image/* entry and use the image/gif entry with the
3170 In addition, you can use this with ``Autoview'' to denote two commands
3171 for viewing an attachment, one to be viewed automatically, the other
3172 to be viewed interactively from the attachment menu. In addition, you
3173 can then use the test feature to determine which viewer to use
3174 interactively depending on your environment.
3176 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
3177 text/html; lynx %s; nametemplate=%s.html
3178 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
3180 For ``Autoview'', Mutt will choose the third entry because of the
3181 copiousoutput tag. For interactive viewing, Mutt will run the program
3182 RunningX to determine if it should use the first entry. If the pro-
3183 gram returns non-zero, Mutt will use the second entry for interactive
3186 \e[1m5.3.3.3. Command Expansion
\e[0m
3188 The various commands defined in the mailcap files are passed to the
3189 /bin/sh shell using the system() function. Before the command is
3190 passed to /bin/sh -c, it is parsed to expand various special
3191 parameters with information from Mutt. The keywords Mutt expands are:
3193 \e[1m%s
\e[22mAs seen in the basic mailcap section, this variable is expanded
3194 to a filename specified by the calling program. This file
3195 contains the body of the message to view/print/edit or where the
3196 composing program should place the results of composition. In
3197 addition, the use of this keyword causes Mutt to not pass the
3198 body of the message to the view/print/edit program on stdin.
3200 \e[1m%t
\e[22mMutt will expand %t to the text representation of the content
3201 type of the message in the same form as the first parameter of
3202 the mailcap definition line, ie text/html or image/gif.
3204 \e[1m%{<parameter>}
\e[0m
3205 Mutt will expand this to the value of the specified parameter
3206 from the Content-Type: line of the mail message. For instance,
3207 if Your mail message contains:
3208 Content-Type: text/plain; charset=iso-8859-1
3210 then Mutt will expand %{charset} to iso-8859-1. The default meta-
3211 mail mailcap file uses this feature to test the charset to spawn an
3212 xterm using the right charset to view the message.
3214 \e[1m\%
\e[22mThis will be replaced by a %
3216 Mutt does not currently support the %F and %n keywords specified in
3217 RFC 1524. The main purpose of these parameters is for multipart mes-
3218 sages, which is handled internally by Mutt.
3220 \e[1m5.3.4. Example mailcap files
\e[0m
3222 This mailcap file is fairly simple and standard:
3224 ______________________________________________________________________
3225 # I'm always running X :)
3226 video/*; xanim %s > /dev/null
3227 image/*; xv %s > /dev/null
3229 # I'm always running netscape (if my computer had more memory, maybe)
3230 text/html; netscape -remote 'openURL(%s)'
3231 ______________________________________________________________________
3233 This mailcap file shows quite a number of examples:
3235 ______________________________________________________________________
3236 # Use xanim to view all videos Xanim produces a header on startup,
3237 # send that to /dev/null so I don't see it
3238 video/*; xanim %s > /dev/null
3240 # Send html to a running netscape by remote
3241 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3243 # If I'm not running netscape but I am running X, start netscape on the
3245 text/html; netscape %s; test=RunningX
3247 # Else use lynx to view it as text
3250 # This version would convert the text/html to text/plain
3251 text/html; lynx -dump %s; copiousoutput
3253 # I use enscript to print text in two columns to a page
3254 text/*; more %s; print=enscript -2Gr %s
3256 # Netscape adds a flag to tell itself to view jpegs internally
3257 image/jpeg;xv %s; x-mozilla-flags=internal
3259 # Use xv to view images if I'm running X
3260 # In addition, this uses the \ to extend the line and set my editor
3262 image/*;xv %s; test=RunningX; \
3265 # Convert images to text using the netpbm tools
3266 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3267 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3269 # Send excel spreadsheets to my NT box
3270 application/ms-excel; open.pl %s
3271 ______________________________________________________________________
3273 \e[1m5.4. MIME Autoview
\e[0m
3275 In addition to explicitly telling Mutt to view an attachment with the
3276 MIME viewer defined in the mailcap file, Mutt has support for
3277 automatically viewing MIME attachments while in the pager.
3279 To work, you must define a viewer in the mailcap file which uses the
3280 copiousoutput option to denote that it is non-interactive. Usually,
3281 you also use the entry to convert the attachment to a text
3282 representation which you can view in the pager.
3284 You then use the auto_view muttrc command to list the content-types
3285 that you wish to view automatically.
3287 For instance, if you set auto_view to:
3289 auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz
3291 Mutt could use the following mailcap entries to automatically view
3292 attachments of these types.
3294 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3295 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
3296 application/x-gunzip; gzcat; copiousoutput
3297 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3298 application/postscript; ps2ascii %s; copiousoutput
3300 ``unauto_view'' can be used to remove previous entries from the
3301 autoview list. This can be used with message-hook to autoview
3302 messages based on size, etc. ``unauto_view *'' will remove all
3305 \e[1m5.5. MIME Multipart/Alternative
\e[0m
3307 Mutt has some heuristics for determining which attachment of a
3308 multipart/alternative type to display. First, mutt will check the
3309 alternative_order list to determine if one of the available types is
3310 preferred. The alternative_order list consists of a number of
3311 mimetypes in order, including support for implicit and explicit
3312 wildcards, for example:
3314 alternative_order text/enriched text/plain text application/postscript image/*
3316 Next, mutt will check if any of the types have a defined
3317 ``auto_view'', and use that. Failing that, Mutt will look for any
3318 text type. As a last attempt, mutt will look for any type it knows
3321 To remove a MIME type from the alternative_order list, use the
3322 unalternative_order command.
3324 \e[1m5.6. MIME Lookup
\e[0m
3326 Mutt's mime_lookup list specifies a list of mime-types that should not
3327 be treated according to their mailcap entry. This option is designed
3328 to deal with binary types such as application/octet-stream. When an
3329 attachment's mime-type is listed in mime_lookup, then the extension of
3330 the filename will be compared to the list of extensions in the
3331 mime.types file. The mime-type associated with this extension will
3332 then be used to process the attachment according to the rules in the
3333 mailcap file and according to any other configuration options (such as
3334 auto_view) specified. Common usage would be:
3336 mime_lookup application/octet-stream application/X-Lotus-Manuscript
3338 In addition, the unmime_lookup command may be used to disable this
3339 feature for any particular mime-type if it had been set, for example,
3342 \e[1m6. Reference
\e[0m
3344 \e[1m6.1. Command line options
\e[0m
3346 Running mutt with no arguments will make Mutt attempt to read your
3347 spool mailbox. However, it is possible to read other mailboxes and to
3348 send messages from the command line as well.
3351 -a attach a file to a message
3352 -b specify a blind carbon-copy (BCC) address
3353 -c specify a carbon-copy (Cc) address
3354 -e specify a config command to be run after initilization files are read
3355 -f specify a mailbox to load
3356 -F specify an alternate file to read initialization commands
3357 -h print help on command line options
3358 -H specify a draft file from which to read a header and body
3359 -i specify a file to include in a message composition
3360 -m specify a default mailbox type
3361 -n do not read the system Muttrc
3362 -p recall a postponed message
3363 -Q query a configuration variable
3364 -R open mailbox in read-only mode
3365 -s specify a subject (enclose in quotes if it contains spaces)
3366 -v show version number and compile-time definitions
3367 -x simulate the mailx(1) compose mode
3368 -y show a menu containing the files specified by the mailboxes command
3369 -z exit immediately if there are no messages in the mailbox
3370 -Z open the first folder with new message,exit immediately if none
3372 To read messages in a mailbox
3374 mutt [ -nz ] [ -F
\e[4mmuttrc
\e[24m ] [ -m
\e[4mtype
\e[24m ] [ -f
\e[4mmailbox
\e[24m ]
3376 To compose a new message
3378 mutt [ -n ] [ -F
\e[4mmuttrc
\e[24m ] [ -a
\e[4mfile
\e[24m ] [ -c
\e[4maddress
\e[24m ] [ -i
\e[4mfilename
\e[24m ] [
3379 -s
\e[4msubject
\e[24m ]
\e[4maddress
\e[24m [
\e[4maddress
\e[24m ... ]
3381 Mutt also supports a ``batch'' mode to send prepared messages. Simply
3382 redirect input from the file you wish to send. For example,
3384 mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
3386 This command will send a message to ``professor@bigschool.edu'' with a
3387 subject of ``data set for run #2''. In the body of the message will
3388 be the contents of the file ``~/run2.dat''.
3390 \e[1m6.2. Configuration Commands
\e[0m
3392 The following are the commands understood by mutt.
3394 · ``account-hook''
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
3396 · ``alias''
\e[4mkey
\e[24m
\e[4maddress
\e[24m [ ,
\e[4maddress
\e[24m, ... ]
3398 · ``unalias'' [ * |
\e[4mkey
\e[24m ... ]
3400 · ``alternates''
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
3402 · ``unalternates'' [ * |
\e[4mregexp
\e[24m ... ]
3404 · ``alternative_order''
\e[4mmimetype
\e[24m [
\e[4mmimetype
\e[24m ... ]
3406 · ``unalternative_order''
\e[4mmimetype
\e[24m [
\e[4mmimetype
\e[24m ... ]
3408 · ``auto_view''
\e[4mmimetype
\e[24m [
\e[4mmimetype
\e[24m ... ]
3410 · ``unauto_view''
\e[4mmimetype
\e[24m [
\e[4mmimetype
\e[24m ... ]
3412 · ``bind''
\e[4mmap
\e[24m
\e[4mkey
\e[24m
\e[4mfunction
\e[0m
3414 · ``charset-hook''
\e[4malias
\e[24m
\e[4mcharset
\e[0m
3416 · ``color''
\e[4mobject
\e[24m
\e[4mforeground
\e[24m
\e[4mbackground
\e[24m [
\e[4mregexp
\e[24m ]
3418 · ``uncolor''
\e[4mindex
\e[24m
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
3420 · ``exec''
\e[4mfunction
\e[24m [
\e[4mfunction
\e[24m ... ]
3422 · ``fcc-hook''
\e[4mpattern
\e[24m
\e[4mmailbox
\e[0m
3424 · ``fcc-save-hook''
\e[4mpattern
\e[24m
\e[4mmailbox
\e[0m
3426 · ``folder-hook''
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
3428 · ``hdr_order''
\e[4mheader
\e[24m [
\e[4mheader
\e[24m ... ]
3430 · ``unhdr_order''
\e[4mheader
\e[24m [
\e[4mheader
\e[24m ... ]
3432 · ``iconv-hook''
\e[4mcharset
\e[24m
\e[4mlocal-charset
\e[0m
3434 · ``ignore''
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
3436 · ``unignore''
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
3438 · ``lists''
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
3440 · ``unlists''
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
3442 · ``macro''
\e[4mmenu
\e[24m
\e[4mkey
\e[24m
\e[4msequence
\e[24m [
\e[4mdescription
\e[24m ]
3444 · ``mailboxes''
\e[4mfilename
\e[24m [
\e[4mfilename
\e[24m ... ]
3446 · ``mbox-hook''
\e[4mpattern
\e[24m
\e[4mmailbox
\e[0m
3448 · ``message-hook''
\e[4mpattern
\e[24m
\e[4mcommand
\e[0m
3450 · ``mime_lookup''
\e[4mmimetype
\e[24m [
\e[4mmimetype
\e[24m ... ]
3452 · ``unmime_lookup''
\e[4mmimetype
\e[24m [
\e[4mmimetype
\e[24m ... ]
3454 · ``mono''
\e[4mobject
\e[24m
\e[4mattribute
\e[24m [
\e[4mregexp
\e[24m ]
3456 · ``unmono''
\e[4mindex
\e[24m
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
3458 · ``my_hdr''
\e[4mstring
\e[0m
3460 · ``unmy_hdr''
\e[4mfield
\e[24m [
\e[4mfield
\e[24m ... ]
3462 · ``crypt-hook''
\e[4mpattern
\e[24m
\e[4mkey-id
\e[0m
3464 · ``push''
\e[4mstring
\e[0m
3466 · ``reset''
\e[4mvariable
\e[24m [
\e[4mvariable
\e[24m ... ]
3468 · ``save-hook''
\e[4mregexp
\e[24m
\e[4mfilename
\e[0m
3470 · ``score''
\e[4mpattern
\e[24m
\e[4mvalue
\e[0m
3472 · ``unscore''
\e[4mpattern
\e[24m [
\e[4mpattern
\e[24m ... ]
3474 · ``send-hook''
\e[4mregexp
\e[24m
\e[4mcommand
\e[0m
3476 · ``reply-hook''
\e[4mregexp
\e[24m
\e[4mcommand
\e[0m
3478 · ``set'' [no|inv]
\e[4mvariable
\e[24m[=
\e[4mvalue
\e[24m] [
\e[4mvariable
\e[24m ... ]
3480 · ``unset''
\e[4mvariable
\e[24m [
\e[4mvariable
\e[24m ... ]
3482 · ``source''
\e[4mfilename
\e[0m
3484 · ``spam''
\e[4mpattern
\e[24m
\e[4mformat
\e[0m
3486 · ``nospam''
\e[4mpattern
\e[0m
3488 · ``subscribe''
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
3490 · ``unsubscribe''
\e[4mregexp
\e[24m [
\e[4mregexp
\e[24m ... ]
3492 · ``toggle''
\e[4mvariable
\e[24m [
\e[4mvariable
\e[24m ... ]
3494 · ``unhook''
\e[4mhook-type
\e[0m
3496 \e[1m6.3. Configuration variables
\e[0m
3498 \e[1m6.3.1. abort_nosubject
\e[0m
3503 If set to
\e[4myes
\e[24m, when composing messages and no subject is given at the
3504 subject prompt, composition will be aborted. If set to
\e[4mno
\e[24m, composing
3505 messages with no subject given at the subject prompt will never be
3508 \e[1m6.3.2. abort_unmodified
\e[0m
3513 If set to
\e[4myes
\e[24m, composition will automatically abort after editing the
3514 message body if no changes are made to the file (this check only
3515 happens after the
\e[4mfirst
\e[24m edit of the file). When set to
\e[4mno
\e[24m,
3516 composition will never be aborted.
3518 \e[1m6.3.3. alias_file
\e[0m
3521 Default: "~/.muttrc"
3523 The default file in which to save aliases created by the ````create-
3526 \e[1mNote:
\e[22mMutt will not automatically source this file; you must
3527 explicitly use the ````source'''' command for it to be executed.
3529 \e[1m6.3.4. alias_format
\e[0m
3532 Default: "%4n %2f %t %-10a %r"
3534 Specifies the format of the data displayed for the `alias' menu. The
3535 following printf(3)-style sequences are available:
3537 \e[1m%a
\e[22malias name
3539 \e[1m%f
\e[22mflags - currently, a "d" for an alias marked for deletion
3541 \e[1m%n
\e[22mindex number
3543 \e[1m%r
\e[22maddress which alias expands to
3545 \e[1m%t
\e[22mcharacter which indicates if the alias is tagged for inclusion
3547 \e[1m6.3.5. allow_8bit
\e[0m
3552 Controls whether 8-bit data is converted to 7-bit using either Quoted-
3553 Printable or Base64 encoding when sending mail.
3555 \e[1m6.3.6. allow_ansi
\e[0m
3560 Controls whether ANSI color codes in messages (and color tags in rich
3561 text messages) are to be interpreted. Messages containing these codes
3562 are rare, but if this option is set, their text will be colored
3563 accordingly. Note that this may override your color choices, and even
3564 present a security problem, since a message could include a line like
3565 "[-- PGP output follows ..." and give it the same color as your
3568 \e[1m6.3.7. arrow_cursor
\e[0m
3573 When set, an arrow (``->'') will be used to indicate the current entry
3574 in menus instead of highlighting the whole line. On slow network or
3575 modem links this will make response faster because there is less that
3576 has to be redrawn on the screen when moving to the next or previous
3577 entries in the menu.
3579 \e[1m6.3.8. ascii_chars
\e[0m
3584 If set, Mutt will use plain ASCII characters when displaying thread
3585 and attachment trees, instead of the default
\e[4mACS
\e[24m characters.
3587 \e[1m6.3.9. askbcc
\e[0m
3592 If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
3593 before editing an outgoing message.
3595 \e[1m6.3.10. askcc
\e[0m
3600 If set, Mutt will prompt you for carbon-copy (Cc) recipients before
3601 editing the body of an outgoing message.
3603 6
\b6.
\b.3
\b3.
\b.1
\b11
\b1.
\b. a
\bas
\bsk
\bk_
\b_f
\bfo
\bol
\bll
\blo
\bow
\bw_
\b_u
\bup
\bp
3608 If set, Mutt will prompt you for follow-up groups before editing the
3609 body of an outgoing message.
3611 6
\b6.
\b.3
\b3.
\b.1
\b12
\b2.
\b. a
\bas
\bsk
\bk_
\b_x
\bx_
\b_c
\bco
\bom
\bmm
\bme
\ben
\bnt
\bt_
\b_t
\bto
\bo
3616 If set, Mutt will prompt you for x-comment-to field before editing the
3617 body of an outgoing message.
3618 6
\b6.
\b.3
\b3.
\b.1
\b13
\b3.
\b. a
\bat
\btt
\bta
\bac
\bch
\bh_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
3621 Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
3623 This variable describes the format of the `attachment' menu. The
3624 following printf-style sequences are understood:
3628 %
\b%c
\bc reqiures charset conversion (n or c)
3630 %
\b%D
\bD deleted flag
3632 %
\b%d
\bd description
3634 %
\b%e
\be MIME content-transfer-encoding
3638 %
\b%I
\bI disposition (I=inline, A=attachment)
3640 %
\b%m
\bm major MIME type
3642 %
\b%M
\bM MIME subtype
3644 %
\b%n
\bn attachment number
3648 %
\b%t
\bt tagged flag
3650 %
\b%T
\bT graphic tree characters
3652 %
\b%u
\bu unlink (=to delete) flag
3655 right justify the rest of the string and pad with character "X"
3658 pad to the end of the line with character "X"
3660 6
\b6.
\b.3
\b3.
\b.1
\b14
\b4.
\b. a
\bat
\btt
\bta
\bac
\bch
\bh_
\b_s
\bse
\bep
\bp
3665 The separator to add between attachments when operating (saving,
3666 printing, piping, etc) on a list of tagged attachments.
3668 6
\b6.
\b.3
\b3.
\b.1
\b15
\b5.
\b. a
\bat
\btt
\bta
\bac
\bch
\bh_
\b_s
\bsp
\bpl
\bli
\bit
\bt
3673 If this variable is unset, when operating (saving, printing, piping,
3674 etc) on a list of tagged attachments, Mutt will concatenate the
3675 attachments and will operate on them as a single attachment. The
3676 ````$attach_sep'''' separator is added after each attachment. When
3677 set, Mutt will operate on the attachments one by one.
3679 6
\b6.
\b.3
\b3.
\b.1
\b16
\b6.
\b. a
\bat
\btt
\btr
\bri
\bib
\bbu
\but
\bti
\bio
\bon
\bn
3682 Default: "On %d, %n wrote:"
3684 This is the string that will precede a message which has been included
3685 in a reply. For a full listing of defined printf()-like sequences see
3686 the section on ````$index_format''''.
3688 6
\b6.
\b.3
\b3.
\b.1
\b17
\b7.
\b. a
\bau
\but
\bto
\boe
\bed
\bdi
\bit
\bt
3693 When set along with ````$edit_headers'''', Mutt will skip the initial
3694 send-menu and allow you to immediately begin editing the body of your
3695 message. The send-menu may still be accessed once you have finished
3696 editing the body of your message.
3698 Also see ````$fast_reply''''.
3700 6
\b6.
\b.3
\b3.
\b.1
\b18
\b8.
\b. a
\bau
\but
\bto
\bo_
\b_t
\bta
\bag
\bg
3705 When set, functions in the _
\bi_
\bn_
\bd_
\be_
\bx menu which affect a message will be
3706 applied to all tagged messages (if there are any). When unset, you
3707 must first use the tag-prefix function (default: ";") to make the next
3708 function apply to all tagged messages.
3710 6
\b6.
\b.3
\b3.
\b.1
\b19
\b9.
\b. b
\bbe
\bee
\bep
\bp
3715 When this variable is set, mutt will beep when an error occurs.
3717 6
\b6.
\b.3
\b3.
\b.2
\b20
\b0.
\b. b
\bbe
\bee
\bep
\bp_
\b_n
\bne
\bew
\bw
3722 When this variable is set, mutt will beep whenever it prints a message
3723 notifying you of new mail. This is independent of the setting of the
3724 ````$beep'''' variable.
3726 6
\b6.
\b.3
\b3.
\b.2
\b21
\b1.
\b. b
\bbo
\bou
\bun
\bnc
\bce
\be
3731 Controls whether you will be asked to confirm bouncing messages. If
3732 set to _
\by_
\be_
\bs you don't get asked if you want to bounce a message.
3733 Setting this variable to _
\bn_
\bo is not generally useful, and thus not
3734 recommended, because you are unable to bounce messages.
3736 6
\b6.
\b.3
\b3.
\b.2
\b22
\b2.
\b. b
\bbo
\bou
\bun
\bnc
\bce
\be_
\b_d
\bde
\bel
\bli
\biv
\bve
\ber
\bre
\bed
\bd
3741 When this variable is set, mutt will include Delivered-To headers when
3742 bouncing messages. Postfix users may wish to unset this variable.
3744 6
\b6.
\b.3
\b3.
\b.2
\b23
\b3.
\b. c
\bca
\bat
\btc
\bch
\bhu
\bup
\bp_
\b_n
\bne
\bew
\bws
\bsg
\bgr
\bro
\bou
\bup
\bp
3749 If this variable is _
\bs_
\be_
\bt, Mutt will mark all articles in newsgroup as
3750 read when you quit the newsgroup (catchup newsgroup).
3752 6
\b6.
\b.3
\b3.
\b.2
\b24
\b4.
\b. c
\bch
\bha
\bar
\brs
\bse
\bet
\bt
3757 Character set your terminal uses to display and enter textual data.
3759 6
\b6.
\b.3
\b3.
\b.2
\b25
\b5.
\b. c
\bch
\bhe
\bec
\bck
\bk_
\b_n
\bne
\bew
\bw
3764 N
\bNo
\bot
\bte
\be:
\b: this option only affects _
\bm_
\ba_
\bi_
\bl_
\bd_
\bi_
\br and _
\bM_
\bH style mailboxes.
3766 When _
\bs_
\be_
\bt, Mutt will check for new mail delivered while the mailbox is
3767 open. Especially with MH mailboxes, this operation can take quite
3768 some time since it involves scanning the directory and checking each
3769 file to see if it has already been looked at. If _
\bc_
\bh_
\be_
\bc_
\bk_
\b__
\bn_
\be_
\bw is _
\bu_
\bn_
\bs_
\be_
\bt,
3770 no check for new mail is performed while the mailbox is open.
3772 6
\b6.
\b.3
\b3.
\b.2
\b26
\b6.
\b. c
\bco
\bol
\bll
\bla
\bap
\bps
\bse
\be_
\b_u
\bun
\bnr
\bre
\bea
\bad
\bd
3777 When _
\bu_
\bn_
\bs_
\be_
\bt, Mutt will not collapse a thread if it contains any unread
3780 6
\b6.
\b.3
\b3.
\b.2
\b27
\b7.
\b. u
\bun
\bnc
\bco
\bol
\bll
\bla
\bap
\bps
\bse
\be_
\b_j
\bju
\bum
\bmp
\bp
3785 When _
\bs_
\be_
\bt, Mutt will jump to the next unread message, if any, when the
3786 current thread is _
\bu_
\bncollapsed.
3788 6
\b6.
\b.3
\b3.
\b.2
\b28
\b8.
\b. c
\bco
\bom
\bmp
\bpo
\bos
\bse
\be_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
3791 Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
3793 Controls the format of the status line displayed in the \fCompose
3794 menu. This string is similar to ````$status_format'''', but has its
3795 own set of printf()-like sequences:
3797 %
\b%a
\ba total number of attachments
3799 %
\b%h
\bh local hostname
3801 %
\b%l
\bl approximate size (in bytes) of the current message
3803 %
\b%v
\bv Mutt version string
3805 See the text describing the ````$status_format'''' option for more
3806 information on how to set ````$compose_format''''.
3808 6
\b6.
\b.3
\b3.
\b.2
\b29
\b9.
\b. c
\bco
\bon
\bnf
\bfi
\bir
\brm
\bma
\bap
\bpp
\bpe
\ben
\bnd
\bd
3813 When set, Mutt will prompt for confirmation when appending messages to
3814 an existing mailbox.
3816 6
\b6.
\b.3
\b3.
\b.3
\b30
\b0.
\b. c
\bco
\bon
\bnf
\bfi
\bir
\brm
\bmc
\bcr
\bre
\bea
\bat
\bte
\be
3821 When set, Mutt will prompt for confirmation when saving messages to a
3822 mailbox which does not yet exist before creating it.
3824 6
\b6.
\b.3
\b3.
\b.3
\b31
\b1.
\b. c
\bco
\bon
\bnn
\bne
\bec
\bct
\bt_
\b_t
\bti
\bim
\bme
\beo
\bou
\but
\bt
3829 Causes Mutt to timeout a network connection (for IMAP or POP) after
3830 this many seconds if the connection is not able to be established. A
3831 negative value causes Mutt to wait indefinitely for the connection to
3834 6
\b6.
\b.3
\b3.
\b.3
\b32
\b2.
\b. c
\bco
\bon
\bnt
\bte
\ben
\bnt
\bt_
\b_t
\bty
\byp
\bpe
\be
3837 Default: "text/plain"
3839 Sets the default Content-Type for the body of newly composed messages.
3841 6
\b6.
\b.3
\b3.
\b.3
\b33
\b3.
\b. c
\bco
\bop
\bpy
\by
3846 This variable controls whether or not copies of your outgoing messages
3847 will be saved for later references. Also see ````$record'''',
3848 ````$save_name'''', ````$force_name'''' and ````fcc-hook''''.
3850 6
\b6.
\b.3
\b3.
\b.3
\b34
\b4.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_a
\bau
\but
\bto
\bop
\bpg
\bgp
\bp
3855 This variable controls whether or not mutt may automatically enable
3856 PGP encryption/signing for messages. See also
3857 ````$crypt_autoencrypt'''', ````$crypt_replyencrypt'''',
3858 ````$crypt_autosign'''', ````$crypt_replysign'''' and
3859 ````$smime_is_default''''.
3861 6
\b6.
\b.3
\b3.
\b.3
\b35
\b5.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_a
\bau
\but
\bto
\bos
\bsm
\bmi
\bim
\bme
\be
3866 This variable controls whether or not mutt may automatically enable
3867 S/MIME encryption/signing for messages. See also
3868 ````$crypt_autoencrypt'''', ````$crypt_replyencrypt'''',
3869 ````$crypt_autosign'''', ````$crypt_replysign'''' and
3870 ````$smime_is_default''''.
3872 6
\b6.
\b.3
\b3.
\b.3
\b36
\b6.
\b. d
\bda
\bat
\bte
\be_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
3875 Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
3877 This variable controls the format of the date printed by the ``%d''
3878 sequence in ````$index_format''''. This is passed to the _
\bs_
\bt_
\br_
\bf_
\bt_
\bi_
\bm_
\be
3879 call to process the date. See the man page for _
\bs_
\bt_
\br_
\bf_
\bt_
\bi_
\bm_
\be_
\b(_
\b3_
\b) for the
3882 Unless the first character in the string is a bang (``!''), the month
3883 and week day names are expanded according to the locale specified in
3884 the variable ````$locale''''. If the first character in the string is
3885 a bang, the bang is discarded, and the month and week day names in the
3886 rest of the string are expanded in the _
\bC locale (that is in US
3889 6
\b6.
\b.3
\b3.
\b.3
\b37
\b7.
\b. d
\bde
\bef
\bfa
\bau
\bul
\blt
\bt_
\b_h
\bho
\boo
\bok
\bk
3892 Default: "~f %s !~P | (~P ~C %s)"
3894 This variable controls how send-hooks, message-hooks, save-hooks, and
3895 fcc-hooks will be interpreted if they are specified with only a simple
3896 regexp, instead of a matching pattern. The hooks are expanded when
3897 they are declared, so a hook will be interpreted according to the
3898 value of this variable at the time the hook is declared. The default
3899 value matches if the message is either from a user matching the
3900 regular expression given, or if it is from you (if the from address
3901 matches ``alternates'') and is to or cc'ed to a user matching the
3902 given regular expression.
3904 6
\b6.
\b.3
\b3.
\b.3
\b38
\b8.
\b. d
\bde
\bel
\ble
\bet
\bte
\be
3909 Controls whether or not messages are really deleted when closing or
3910 synchronizing a mailbox. If set to _
\by_
\be_
\bs, messages marked for deleting
3911 will automatically be purged without prompting. If set to _
\bn_
\bo,
3912 messages marked for deletion will be kept in the mailbox.
3914 6
\b6.
\b.3
\b3.
\b.3
\b39
\b9.
\b. d
\bde
\bel
\ble
\bet
\bte
\be_
\b_u
\bun
\bnt
\bta
\bag
\bg
3919 If this option is _
\bs_
\be_
\bt, mutt will untag messages when marking them for
3920 deletion. This applies when you either explicitly delete a message,
3921 or when you save it to another folder.
3923 6
\b6.
\b.3
\b3.
\b.4
\b40
\b0.
\b. d
\bdi
\big
\bge
\bes
\bst
\bt_
\b_c
\bco
\bol
\bll
\bla
\bap
\bps
\bse
\be
3928 If this option is _
\bs_
\be_
\bt, mutt's revattach menu will not show the
3929 subparts of individual messages in a digest. To see these subparts,
3930 press 'v' on that menu.
3932 6
\b6.
\b.3
\b3.
\b.4
\b41
\b1.
\b. d
\bdi
\bis
\bsp
\bpl
\bla
\bay
\by_
\b_f
\bfi
\bil
\blt
\bte
\ber
\br
3937 When set, specifies a command used to filter messages. When a message
3938 is viewed it is passed as standard input to ``$display_filter'', and
3939 the filtered message is read from the standard output.
3941 6
\b6.
\b.3
\b3.
\b.4
\b42
\b2.
\b. d
\bdo
\bot
\btl
\blo
\boc
\bck
\bk_
\b_p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bm
3944 Default: "/usr/local/bin/mutt_dotlock"
3946 Contains the path of the mutt_dotlock (8) binary to be used by mutt.
3948 6
\b6.
\b.3
\b3.
\b.4
\b43
\b3.
\b. d
\bds
\bsn
\bn_
\b_n
\bno
\bot
\bti
\bif
\bfy
\by
3953 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x
3956 This variable sets the request for when notification is returned. The
3957 string consists of a comma separated list (no spaces!) of one or more
3958 of the following: _
\bn_
\be_
\bv_
\be_
\br, to never request notification, _
\bf_
\ba_
\bi_
\bl_
\bu_
\br_
\be, to
3959 request notification on transmission failure, _
\bd_
\be_
\bl_
\ba_
\by, to be notified of
3960 message delays, _
\bs_
\bu_
\bc_
\bc_
\be_
\bs_
\bs, to be notified of successful transmission.
3962 Example: set dsn_notify="failure,delay"
3964 6
\b6.
\b.3
\b3.
\b.4
\b44
\b4.
\b. d
\bds
\bsn
\bn_
\b_r
\bre
\bet
\btu
\bur
\brn
\bn
3969 N
\bNo
\bot
\bte
\be:
\b: you should not enable this unless you are using Sendmail 8.8.x
3972 This variable controls how much of your message is returned in DSN
3973 messages. It may be set to either _
\bh_
\bd_
\br_
\bs to return just the message
3974 header, or _
\bf_
\bu_
\bl_
\bl to return the full message.
3976 Example: set dsn_return=hdrs
3978 6
\b6.
\b.3
\b3.
\b.4
\b45
\b5.
\b. d
\bdu
\bup
\bpl
\bli
\bic
\bca
\bat
\bte
\be_
\b_t
\bth
\bhr
\bre
\bea
\bad
\bds
\bs
3983 This variable controls whether mutt, when sorting by threads, threads
3984 messages with the same message-id together. If it is set, it will
3985 indicate that it thinks they are duplicates of each other with an
3986 equals sign in the thread diagram.
3988 6
\b6.
\b.3
\b3.
\b.4
\b46
\b6.
\b. e
\bed
\bdi
\bit
\bt_
\b_h
\bhe
\bea
\bad
\bde
\ber
\brs
\bs
3993 This option allows you to edit the header of your outgoing messages
3994 along with the body of your message.
3996 6
\b6.
\b.3
\b3.
\b.4
\b47
\b7.
\b. e
\bed
\bdi
\bit
\bto
\bor
\br
4001 This variable specifies which editor is used by mutt. It defaults to
4002 the value of the VISUAL, or EDITOR, environment variable, or to the
4003 string "vi" if neither of those are set.
4005 6
\b6.
\b.3
\b3.
\b.4
\b48
\b8.
\b. e
\ben
\bnc
\bco
\bod
\bde
\be_
\b_f
\bfr
\bro
\bom
\bm
4010 When _
\bs_
\be_
\bt, mutt will quoted-printable encode messages when they contain
4011 the string "From " in the beginning of a line. Useful to avoid the
4012 tampering certain mail delivery and transport agents tend to do with
4015 6
\b6.
\b.3
\b3.
\b.4
\b49
\b9.
\b. e
\ben
\bnv
\bve
\bel
\blo
\bop
\bpe
\be_
\b_f
\bfr
\bro
\bom
\bm
4020 When _
\bs_
\be_
\bt, mutt will try to derive the message's _
\be_
\bn_
\bv_
\be_
\bl_
\bo_
\bp_
\be sender from
4021 the "From:" header. Note that this information is passed to sendmail
4022 command using the "-f" command line switch, so don't set this option
4023 if you are using that switch in ``$sendmail'' yourself, or if the
4024 sendmail on your machine doesn't support that command line switch.
4026 6
\b6.
\b.3
\b3.
\b.5
\b50
\b0.
\b. e
\bes
\bsc
\bca
\bap
\bpe
\be
4031 Escape character to use for functions in the builtin editor.
4033 6
\b6.
\b.3
\b3.
\b.5
\b51
\b1.
\b. f
\bfa
\bas
\bst
\bt_
\b_r
\bre
\bep
\bpl
\bly
\by
4038 When set, the initial prompt for recipients and subject are skipped
4039 when replying to messages, and the initial prompt for subject is
4040 skipped when forwarding messages.
4042 N
\bNo
\bot
\bte
\be:
\b: this variable has no effect when the ````$autoedit'''' variable
4045 6
\b6.
\b.3
\b3.
\b.5
\b52
\b2.
\b. f
\bfc
\bcc
\bc_
\b_a
\bat
\btt
\bta
\bac
\bch
\bh
4050 This variable controls whether or not attachments on outgoing messages
4051 are saved along with the main body of your message.
4053 6
\b6.
\b.3
\b3.
\b.5
\b53
\b3.
\b. f
\bfc
\bcc
\bc_
\b_c
\bcl
\ble
\bea
\bar
\br
4058 When this variable is set, FCCs will be stored unencrypted and
4059 unsigned, even when the actual message is encrypted and/or signed.
4062 6
\b6.
\b.3
\b3.
\b.5
\b54
\b4.
\b. f
\bfo
\bol
\bld
\bde
\ber
\br
4067 Specifies the default location of your mailboxes. A `+' or `=' at the
4068 beginning of a pathname will be expanded to the value of this
4069 variable. Note that if you change this variable from the default
4070 value you need to make sure that the assignment occurs _
\bb_
\be_
\bf_
\bo_
\br_
\be you use
4071 `+' or `=' for any other variables since expansion takes place during
4074 6
\b6.
\b.3
\b3.
\b.5
\b55
\b5.
\b. f
\bfo
\bol
\bld
\bde
\ber
\br_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4077 Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
4079 This variable allows you to customize the file browser display to your
4080 personal taste. This string is similar to ````$index_format'''', but
4081 has its own set of printf()-like sequences:
4083 %
\b%C
\bC current file number
4085 %
\b%d
\bd date/time folder was last modified
4089 %
\b%F
\bF file permissions
4091 %
\b%g
\bg group name (or numeric gid, if missing)
4093 %
\b%l
\bl number of hard links
4095 %
\b%N
\bN N if folder has new mail, blank otherwise
4097 %
\b%s
\bs size in bytes
4099 %
\b%t
\bt * if the file is tagged, blank otherwise
4101 %
\b%u
\bu owner name (or numeric uid, if missing)
4104 right justify the rest of the string and pad with character "X"
4107 pad to the end of the line with character "X"
4109 6
\b6.
\b.3
\b3.
\b.5
\b56
\b6.
\b. f
\bfo
\bol
\bll
\blo
\bow
\bwu
\bup
\bp_
\b_t
\bto
\bo
4114 Controls whether or not the _
\bM_
\ba_
\bi_
\bl_
\b-_
\bF_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b-_
\bT_
\bo header field is generated
4115 when sending mail. When _
\bs_
\be_
\bt, Mutt will generate this field when you
4116 are replying to a known mailing list, specified with the ``subscribe''
4117 or ````lists'''' commands.
4119 This field has two purposes. First, preventing you from receiving
4120 duplicate copies of replies to messages which you send to mailing
4121 lists, and second, ensuring that you do get a reply separately for any
4122 messages sent to known lists to which you are not subscribed. The
4123 header will contain only the list's address for subscribed lists, and
4124 both the list address and your own email address for unsubscribed
4125 lists. Without this header, a group reply to your message sent to a
4126 subscribed list will be sent to both the list and your address,
4127 resulting in two copies of the same email for you.
4129 6
\b6.
\b.3
\b3.
\b.5
\b57
\b7.
\b. f
\bfo
\bol
\bll
\blo
\bow
\bwu
\bup
\bp_
\b_t
\bto
\bo_
\b_p
\bpo
\bos
\bst
\bte
\ber
\br
4134 If this variable is _
\bs_
\be_
\bt and the keyword "poster" is present in
4135 _
\bF_
\bo_
\bl_
\bl_
\bo_
\bw_
\bu_
\bp_
\b-_
\bT_
\bo header, follow-up to newsgroup function is not permitted.
4136 The message will be mailed to the submitter of the message via mail.
4138 6
\b6.
\b.3
\b3.
\b.5
\b58
\b8.
\b. f
\bfo
\bor
\brc
\bce
\be_
\b_n
\bna
\bam
\bme
\be
4143 This variable is similar to ````$save_name'''', except that Mutt will
4144 store a copy of your outgoing message by the username of the address
4145 you are sending to even if that mailbox does not exist.
4147 Also see the ````$record'''' variable.
4149 6
\b6.
\b.3
\b3.
\b.5
\b59
\b9.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_d
\bde
\bec
\bco
\bod
\bde
\be
4154 Controls the decoding of complex MIME messages into text/plain when
4155 forwarding a message. The message header is also RFC2047 decoded.
4156 This variable is only used, if ````$mime_forward'''' is _
\bu_
\bn_
\bs_
\be_
\bt,
4157 otherwise ````$mime_forward_decode'''' is used instead.
4159 6
\b6.
\b.3
\b3.
\b.6
\b60
\b0.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_e
\bed
\bdi
\bit
\bt
4164 This quadoption controls whether or not the user is automatically
4165 placed in the editor when forwarding messages. For those who always
4166 want to forward with no modification, use a setting of ``no''.
4168 6
\b6.
\b.3
\b3.
\b.6
\b61
\b1.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4173 This variable controls the default subject when forwarding a message.
4174 It uses the same format sequences as the ````$index_format''''
4177 6
\b6.
\b.3
\b3.
\b.6
\b62
\b2.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_q
\bqu
\buo
\bot
\bte
\be
4182 When _
\bs_
\be_
\bt forwarded messages included in the main body of the message
4183 (when ````$mime_forward'''' is _
\bu_
\bn_
\bs_
\be_
\bt) will be quoted using
4184 ````$indent_string''''.
4186 6
\b6.
\b.3
\b3.
\b.6
\b63
\b3.
\b. f
\bfr
\bro
\bom
\bm
4188 Type: e-mail address
4191 When set, this variable contains a default from address. It can be
4192 overridden using my_hdr (including from send-hooks) and
4193 ````$reverse_name''''. This variable is ignored if ````$use_from''''
4196 Defaults to the contents of the environment variable EMAIL.
4198 6
\b6.
\b.3
\b3.
\b.6
\b64
\b4.
\b. g
\bge
\bec
\bco
\bos
\bs_
\b_m
\bma
\bas
\bsk
\bk
4200 Type: regular expression
4203 A regular expression used by mutt to parse the GECOS field of a
4204 password entry when expanding the alias. By default the regular
4205 expression is set to "^[^,]*" which will return the string up to the
4206 first "," encountered. If the GECOS field contains a string like
4207 "lastname, firstname" then you should set the gecos_mask=".*".
4209 This can be useful if you see the following behavior: you address a e-
4210 mail to user ID stevef whose full name is Steve Franklin. If mutt
4211 expands stevef to "Franklin" stevef@foo.bar then you should set the
4212 gecos_mask to a regular expression that will match the whole name so
4213 mutt will expand "Franklin" to "Franklin, Steve".
4215 6
\b6.
\b.3
\b3.
\b.6
\b65
\b5.
\b. g
\bgr
\bro
\bou
\bup
\bp_
\b_i
\bin
\bnd
\bde
\bex
\bx_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4218 Default: "%4C %M%N %5s %-45.45f %d"
4220 This variable allows you to customize the newsgroup browser display to
4221 your personal taste. This string is similar to ````index_format'''',
4222 but has its own set of printf()-like sequences:
4224 %C current newsgroup number
4225 %d description of newsgroup (becomes from server)
4227 %M - if newsgroup not allowed for direct post (moderated for example)
4228 %N N if newsgroup is new, u if unsubscribed, blank otherwise
4229 %n number of new articles in newsgroup
4230 %s number of unread articles in newsgroup
4231 %>X right justify the rest of the string and pad with character "X"
4232 %|X pad to the end of the line with character "X"
4234 6
\b6.
\b.3
\b3.
\b.6
\b66
\b6.
\b. h
\bhd
\bdr
\brs
\bs
4239 When unset, the header fields normally added by the ````my_hdr''''
4240 command are not created. This variable _
\bm_
\bu_
\bs_
\bt be unset before composing
4241 a new message or replying in order to take effect. If set, the user
4242 defined header fields are added to every new message.
4244 6
\b6.
\b.3
\b3.
\b.6
\b67
\b7.
\b. h
\bhe
\bea
\bad
\bde
\ber
\br
4249 When set, this variable causes Mutt to include the header of the
4250 message you are replying to into the edit buffer. The ````$weed''''
4253 6
\b6.
\b.3
\b3.
\b.6
\b68
\b8.
\b. h
\bhe
\bel
\blp
\bp
4258 When set, help lines describing the bindings for the major functions
4259 provided by each menu are displayed on the first line of the screen.
4261 N
\bNo
\bot
\bte
\be:
\b: The binding will not be displayed correctly if the function is
4262 bound to a sequence rather than a single keystroke. Also, the help
4263 line may not be updated if a binding is changed while Mutt is running.
4264 Since this variable is primarily aimed at new users, neither of these
4265 should present a major problem.
4267 6
\b6.
\b.3
\b3.
\b.6
\b69
\b9.
\b. h
\bhi
\bid
\bdd
\bde
\ben
\bn_
\b_h
\bho
\bos
\bst
\bt
4272 When set, mutt will skip the host name part of ````$hostname''''
4273 variable when adding the domain part to addresses. This variable does
4274 not affect the generation of Message-IDs, and it will not lead to the
4275 cut-off of first-level domains.
4276 6
\b6.
\b.3
\b3.
\b.7
\b70
\b0.
\b. h
\bhi
\bid
\bde
\be_
\b_l
\bli
\bim
\bmi
\bit
\bte
\bed
\bd
4281 When set, mutt will not show the presence of messages that are hidden
4282 by limiting, in the thread tree.
4284 6
\b6.
\b.3
\b3.
\b.7
\b71
\b1.
\b. h
\bhi
\bid
\bde
\be_
\b_m
\bmi
\bis
\bss
\bsi
\bin
\bng
\bg
4289 When set, mutt will not show the presence of missing messages in the
4292 6
\b6.
\b.3
\b3.
\b.7
\b72
\b2.
\b. h
\bhi
\bid
\bde
\be_
\b_t
\bto
\bop
\bp_
\b_l
\bli
\bim
\bmi
\bit
\bte
\bed
\bd
4297 When set, mutt will not show the presence of messages that are hidden
4298 by limiting, at the top of threads in the thread tree. Note that when
4299 ``$hide_missing'' is set, this option will have no effect.
4301 6
\b6.
\b.3
\b3.
\b.7
\b73
\b3.
\b. h
\bhi
\bid
\bde
\be_
\b_t
\bto
\bop
\bp_
\b_m
\bmi
\bis
\bss
\bsi
\bin
\bng
\bg
4306 When set, mutt will not show the presence of missing messages at the
4307 top of threads in the thread tree. Note that when ``$hide_limited''
4308 is set, this option will have no effect.
4310 6
\b6.
\b.3
\b3.
\b.7
\b74
\b4.
\b. h
\bhi
\bis
\bst
\bto
\bor
\bry
\by
4315 This variable controls the size (in number of strings remembered) of
4316 the string history buffer. The buffer is cleared each time the
4319 6
\b6.
\b.3
\b3.
\b.7
\b75
\b5.
\b. h
\bho
\bon
\bno
\bor
\br_
\b_f
\bfo
\bol
\bll
\blo
\bow
\bwu
\bup
\bp_
\b_t
\bto
\bo
4324 This variable controls whether or not a Mail-Followup-To header is
4325 honored when group-replying to a message.
4326 6
\b6.
\b.3
\b3.
\b.7
\b76
\b6.
\b. h
\bho
\bos
\bst
\btn
\bna
\bam
\bme
\be
4331 Specifies the hostname to use after the ``@'' in local e-mail
4332 addresses. This overrides the compile time definition obtained from
4335 6
\b6.
\b.3
\b3.
\b.7
\b77
\b7.
\b. i
\big
\bgn
\bno
\bor
\bre
\be_
\b_l
\bli
\bis
\bst
\bt_
\b_r
\bre
\bep
\bpl
\bly
\by_
\b_t
\bto
\bo
4340 Affects the behaviour of the _
\br_
\be_
\bp_
\bl_
\by function when replying to messages
4341 from mailing lists. When set, if the ``Reply-To:'' field is set to
4342 the same value as the ``To:'' field, Mutt assumes that the ``Reply-
4343 To:'' field was set by the mailing list to automate responses to the
4344 list, and will ignore this field. To direct a response to the mailing
4345 list when this 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
4346 will reply to both the sender and the list.
4348 6
\b6.
\b.3
\b3.
\b.7
\b78
\b8.
\b. i
\bim
\bma
\bap
\bp_
\b_a
\bau
\but
\bth
\bhe
\ben
\bnt
\bti
\bic
\bca
\bat
\bto
\bor
\brs
\bs
4353 This is a colon-delimited list of authentication methods mutt may
4354 attempt to use to log in to an IMAP server, in the order mutt should
4355 try them. Authentication methods are either 'login' or the right side
4356 of an IMAP 'AUTH=xxx' capability string, eg 'digest-md5', parameter is
4357 unset (the default) mutt will try all available methods, in order from
4358 most-secure to least-secure.
4360 Example: set imap_authenticators="gssapi:cram-md5:login"
4362 N
\bNo
\bot
\bte
\be:
\b: Mutt will only fall back to other authentication methods if the
4363 previous methods are unavailable. If a method is available but
4364 authentication fails, mutt will not connect to the IMAP server.
4366 6
\b6.
\b.3
\b3.
\b.7
\b79
\b9.
\b. i
\bim
\bma
\bap
\bp_
\b_d
\bde
\bel
\bli
\bim
\bm_
\b_c
\bch
\bha
\bar
\brs
\bs
4371 This contains the list of characters which you would like to treat as
4372 folder separators for displaying IMAP paths. In particular it helps in
4373 using the '=' shortcut for your _
\bf_
\bo_
\bl_
\bd_
\be_
\br variable.
4375 6
\b6.
\b.3
\b3.
\b.8
\b80
\b0.
\b. i
\bim
\bma
\bap
\bp_
\b_f
\bfo
\bor
\brc
\bce
\be_
\b_s
\bss
\bsl
\bl
4380 If this variable is set, Mutt will always use SSL when connecting to
4383 6
\b6.
\b.3
\b3.
\b.8
\b81
\b1.
\b. i
\bim
\bma
\bap
\bp_
\b_h
\bho
\bom
\bme
\be_
\b_n
\bna
\bam
\bme
\bes
\bsp
\bpa
\bac
\bce
\be
4388 You normally want to see your personal folders alongside your INBOX in
4389 the IMAP browser. If you see something else, you may set this variable
4390 to the IMAP path to your folders.
4392 6
\b6.
\b.3
\b3.
\b.8
\b82
\b2.
\b. i
\bim
\bma
\bap
\bp_
\b_k
\bke
\bee
\bep
\bpa
\bal
\bli
\biv
\bve
\be
4397 This variable specifies the maximum amount of time in seconds that
4398 mutt will wait before polling open IMAP connections, to prevent the
4399 server from closing them before mutt has finished with them. The
4400 default is well within the RFC-specified minimum amount of time (30
4401 minutes) before a server is allowed to do this, but in practice the
4402 RFC does get violated every now and then. Reduce this number if you
4403 find yourself getting disconnected from your IMAP server due to
4406 6
\b6.
\b.3
\b3.
\b.8
\b83
\b3.
\b. i
\bim
\bma
\bap
\bp_
\b_l
\bli
\bis
\bst
\bt_
\b_s
\bsu
\bub
\bbs
\bsc
\bcr
\bri
\bib
\bbe
\bed
\bd
4411 This variable configures whether IMAP folder browsing will look for
4412 only subscribed folders or all folders. This can be toggled in the
4413 IMAP browser with the _
\bt_
\bo_
\bg_
\bg_
\bl_
\be_
\b-_
\bs_
\bu_
\bb_
\bs_
\bc_
\br_
\bi_
\bb_
\be_
\bd function.
4415 6
\b6.
\b.3
\b3.
\b.8
\b84
\b4.
\b. i
\bim
\bma
\bap
\bp_
\b_p
\bpa
\bas
\bss
\bs
4420 Specifies the password for your IMAP account. If unset, Mutt will
4421 prompt you for your password when you invoke the fetch-mail function.
4422 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you should only use this option when you are on a fairly
4423 secure machine, because the superuser can read your muttrc even if you
4424 are the only one who can read the file.
4426 6
\b6.
\b.3
\b3.
\b.8
\b85
\b5.
\b. i
\bim
\bma
\bap
\bp_
\b_p
\bpa
\bas
\bss
\bsi
\biv
\bve
\be
4431 When set, mutt will not open new IMAP connections to check for new
4432 mail. Mutt will only check for new mail over existing IMAP
4433 connections. This is useful if you don't want to be prompted to
4434 user/password pairs on mutt invocation, or if opening the connection
4437 6
\b6.
\b.3
\b3.
\b.8
\b86
\b6.
\b. i
\bim
\bma
\bap
\bp_
\b_p
\bpe
\bee
\bek
\bk
4442 If set, mutt will avoid implicitly marking your mail as read whenever
4443 you fetch a message from the server. This is generally a good thing,
4444 but can make closing an IMAP folder somewhat slower. This option
4445 exists to appease speed freaks.
4447 6
\b6.
\b.3
\b3.
\b.8
\b87
\b7.
\b. i
\bim
\bma
\bap
\bp_
\b_s
\bse
\ber
\brv
\bve
\ber
\brn
\bno
\boi
\bis
\bse
\be
4452 When set, mutt will display warning messages from the IMAP server as
4453 error messages. Since these messages are often harmless, or generated
4454 due to configuration problems on the server which are out of the
4455 users' hands, you may wish to suppress them at some point.
4457 6
\b6.
\b.3
\b3.
\b.8
\b88
\b8.
\b. i
\bim
\bma
\bap
\bp_
\b_u
\bus
\bse
\ber
\br
4462 Your login name on the IMAP server.
4464 This variable defaults to your user name on the local machine.
4466 6
\b6.
\b.3
\b3.
\b.8
\b89
\b9.
\b. i
\bim
\bmp
\bpl
\bli
\bic
\bci
\bit
\bt_
\b_a
\bau
\but
\bto
\bov
\bvi
\bie
\bew
\bw
4471 If set to ``yes'', mutt will look for a mailcap entry with the
4472 copiousoutput flag set for _
\be_
\bv_
\be_
\br_
\by MIME attachment it doesn't have an
4473 internal viewer defined for. If such an entry is found, mutt will use
4474 the viewer defined in that entry to convert the body part to text
4477 6
\b6.
\b.3
\b3.
\b.9
\b90
\b0.
\b. i
\bin
\bnc
\bcl
\blu
\bud
\bde
\be
4482 Controls whether or not a copy of the message(s) you are replying to
4483 is included in your reply.
4485 6
\b6.
\b.3
\b3.
\b.9
\b91
\b1.
\b. i
\bin
\bnd
\bde
\ben
\bnt
\bt_
\b_s
\bst
\btr
\bri
\bin
\bng
\bg
4490 Specifies the string to prepend to each line of text quoted in a
4491 message to which you are replying. You are strongly encouraged not to
4492 change this value, as it tends to agitate the more fanatical netizens.
4494 6
\b6.
\b.3
\b3.
\b.9
\b92
\b2.
\b. i
\bin
\bnd
\bde
\bex
\bx_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4497 Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
4499 This variable allows you to customize the message index display to
4500 your personal taste.
4502 ``Format strings'' are similar to the strings used in the ``C''
4503 function printf to format output (see the man page for more detail).
4504 The following sequences are defined in Mutt:
4506 %
\b%a
\ba address of the author
4508 %
\b%A
\bA reply-to address (if present; otherwise: address of author)
4510 %
\b%b
\bb filename of the original message folder (think mailBox)
4512 %
\b%B
\bB the list to which the letter was sent, or else the folder name
4515 %
\b%c
\bc number of characters (bytes) in the message
4517 %
\b%C
\bC current message number
4519 %
\b%d
\bd date and time of the message in the format specified by
4520 ``date_format'' converted to sender's time zone
4522 %
\b%D
\bD date and time of the message in the format specified by
4523 ``date_format'' converted to the local time zone
4525 %
\b%e
\be current message number in thread
4527 %
\b%E
\bE number of messages in current thread
4529 %
\b%f
\bf entire From: line (address + real name)
4531 %
\b%F
\bF author name, or recipient name if the message is from you
4533 %
\b%g
\bg newsgroup name (if compiled with nntp support)
4535 %
\b%i
\bi message-id of the current message
4537 %
\b%l
\bl number of lines in the message (does not work with maildir, mh,
4538 and possibly IMAP folders)
4540 %
\b%L
\bL If an address in the To or CC header field matches an address
4541 defined by the users ``subscribe'' command, this displays "To
4542 <list-name>", otherwise the same as %F.
4544 %
\b%m
\bm total number of message in the mailbox
4546 %
\b%M
\bM number of hidden messages if the thread is collapsed.
4548 %
\b%N
\bN message score
4550 %
\b%n
\bn author's real name (or address if missing)
4552 %
\b%O
\bO (_O_riginal save folder) Where mutt would formerly have stashed
4553 the message: list name or recipient name if no list
4555 %
\b%s
\bs subject of the message
4557 %
\b%S
\bS status of the message (N/D/d/!/r/*)
4559 %
\b%t
\bt `to:' field (recipients)
4561 %
\b%T
\bT the appropriate character from the ``$to_chars'' string
4563 %
\b%u
\bu user (login) name of the author
4565 %
\b%v
\bv first name of the author, or the recipient if the message is
4568 %
\b%W
\bW name of organization of author (`organization:' field)
4570 %
\b%y
\by `x-label:' field, if present
4572 %
\b%Y
\bY `x-label' field, if present, and (1) not at part of a thread
4573 tree, (2) at the top of a thread, or (3) `x-label' is different
4574 from preceding message's `x-label'.
4576 %
\b%Z
\bZ message status flags
4578 %
\b%{
\b{f
\bfm
\bmt
\bt}
\b}
4579 the date and time of the message is converted to sender's time
4580 zone, and ``fmt'' is expanded by the library function
4581 ``strftime''; a leading bang disables locales
4583 %
\b%[
\b[f
\bfm
\bmt
\bt]
\b]
4584 the date and time of the message is converted to the local time
4585 zone, and ``fmt'' is expanded by the library function
4586 ``strftime''; a leading bang disables locales
4588 %
\b%(
\b(f
\bfm
\bmt
\bt)
\b)
4589 the local date and time when the message was received. ``fmt''
4590 is expanded by the library function ``strftime''; a leading bang
4593 %
\b%<
\b<f
\bfm
\bmt
\bt>
\b>
4594 the current local time. ``fmt'' is expanded by the library
4595 function ``strftime''; a leading bang disables locales.
4598 right justify the rest of the string and pad with character "X"
4601 pad to the end of the line with character "X"
4603 See also: ````$to_chars''''.
4605 6
\b6.
\b.3
\b3.
\b.9
\b93
\b3.
\b. i
\bin
\bne
\bew
\bws
\bs
4610 If set, specifies the program and arguments used to deliver news
4611 posted by Mutt. Otherwise, mutt posts article using current
4612 connection to news server. The following printf-style sequence is
4617 Example: set inews="/usr/local/bin/inews -hS"
4619 6
\b6.
\b.3
\b3.
\b.9
\b94
\b4.
\b. i
\bis
\bsp
\bpe
\bel
\bll
\bl
4622 Default: "/usr/bin/ispell"
4624 How to invoke ispell (GNU's spell-checking software).
4626 6
\b6.
\b.3
\b3.
\b.9
\b95
\b5.
\b. k
\bke
\bee
\bep
\bp_
\b_f
\bfl
\bla
\bag
\bgg
\bge
\bed
\bd
4631 If set, read messages marked as flagged will not be moved from your
4632 spool mailbox to your ````$mbox'''' mailbox, or as a result of a
4633 ````mbox-hook'''' command.
4635 6
\b6.
\b.3
\b3.
\b.9
\b96
\b6.
\b. l
\blo
\boc
\bca
\bal
\ble
\be
4640 The locale used by _
\bs_
\bt_
\br_
\bf_
\bt_
\bi_
\bm_
\be_
\b(_
\b3_
\b) to format dates. Legal values are the
4641 strings your system accepts for the locale variable _
\bL_
\bC_
\b__
\bT_
\bI_
\bM_
\bE.
4643 6
\b6.
\b.3
\b3.
\b.9
\b97
\b7.
\b. m
\bma
\bai
\bil
\bl_
\b_c
\bch
\bhe
\bec
\bck
\bk
4648 This variable configures how often (in seconds) mutt should look for
4651 6
\b6.
\b.3
\b3.
\b.9
\b98
\b8.
\b. m
\bma
\bai
\bil
\blc
\bca
\bap
\bp_
\b_p
\bpa
\bat
\bth
\bh
4656 This variable specifies which files to consult when attempting to
4657 display MIME bodies not directly supported by Mutt.
4659 6
\b6.
\b.3
\b3.
\b.9
\b99
\b9.
\b. m
\bma
\bai
\bil
\blc
\bca
\bap
\bp_
\b_s
\bsa
\ban
\bni
\bit
\bti
\biz
\bze
\be
4664 If set, mutt will restrict possible characters in mailcap % expandos
4665 to a well-defined set of safe characters. This is the safe setting,
4666 but we are not sure it doesn't break some more advanced MIME stuff.
4668 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
4669 D
\bDO
\bOI
\bIN
\bNG
\bG!
\b!
4671 6
\b6.
\b.3
\b3.
\b.1
\b10
\b00
\b0.
\b. m
\bma
\bai
\bil
\bld
\bdi
\bir
\br_
\b_t
\btr
\bra
\bas
\bsh
\bh
4676 If set, messages marked as deleted will be saved with the maildir
4677 (T)rashed flag instead of unlinked. N
\bNO
\bOT
\bTE
\bE:
\b: this only applies to
4678 maildir-style mailboxes. Setting it will have no effect on other
4681 6
\b6.
\b.3
\b3.
\b.1
\b10
\b01
\b1.
\b. m
\bma
\bar
\brk
\bk_
\b_o
\bol
\bld
\bd
4686 Controls whether or not mutt marks _
\bn_
\be_
\bw u
\bun
\bnr
\bre
\bea
\bad
\bd messages as _
\bo_
\bl_
\bd if you
4687 exit a mailbox without reading them. With this option set, the next
4688 time you start mutt, the messages will show up with an "O" next to
4689 them in the index menu, indicating that they are old.
4691 6
\b6.
\b.3
\b3.
\b.1
\b10
\b02
\b2.
\b. m
\bma
\bar
\brk
\bke
\ber
\brs
\bs
4696 Controls the display of wrapped lines in the internal pager. If set, a
4697 ``+'' marker is displayed at the beginning of wrapped lines. Also see
4698 the ````$smart_wrap'''' variable.
4700 6
\b6.
\b.3
\b3.
\b.1
\b10
\b03
\b3.
\b. m
\bma
\bas
\bsk
\bk
4702 Type: regular expression
4705 A regular expression used in the file browser, optionally preceded by
4706 the _
\bn_
\bo_
\bt operator ``!''. Only files whose names match this mask will
4707 be shown. The match is always case-sensitive.
4709 6
\b6.
\b.3
\b3.
\b.1
\b10
\b04
\b4.
\b. m
\bmb
\bbo
\box
\bx
4714 This specifies the folder into which read mail in your
4715 ````$spoolfile'''' folder will be appended.
4717 6
\b6.
\b.3
\b3.
\b.1
\b10
\b05
\b5.
\b. m
\bmb
\bbo
\box
\bx_
\b_t
\bty
\byp
\bpe
\be
4722 The default mailbox type used when creating new folders. May be any of
4723 mbox, MMDF, MH and Maildir.
4725 6
\b6.
\b.3
\b3.
\b.1
\b10
\b06
\b6.
\b. m
\bme
\bet
\bto
\boo
\bo
4730 If unset, Mutt will remove your address (see the ``alternates''
4731 command) from the list of recipients when replying to a message.
4733 6
\b6.
\b.3
\b3.
\b.1
\b10
\b07
\b7.
\b. m
\bme
\ben
\bnu
\bu_
\b_s
\bsc
\bcr
\bro
\bol
\bll
\bl
4738 When _
\bs_
\be_
\bt, menus will be scrolled up or down one line when you attempt
4739 to move across a screen boundary. If _
\bu_
\bn_
\bs_
\be_
\bt, the screen is cleared and
4740 the next or previous page of the menu is displayed (useful for slow
4741 links to avoid many redraws).
4743 6
\b6.
\b.3
\b3.
\b.1
\b10
\b08
\b8.
\b. m
\bme
\bet
\bta
\ba_
\b_k
\bke
\bey
\by
4748 If set, forces Mutt to interpret keystrokes with the high bit (bit 8)
4749 set as if the user had pressed the ESC key and whatever key remains
4750 after having the high bit removed. For example, if the key pressed
4751 has an ASCII value of 0xf4, then this is treated as if the user had
4752 pressed ESC then ``x''. This is because the result of removing the
4753 high bit from ``0xf4'' is ``0x74'', which is the ASCII character
4756 6
\b6.
\b.3
\b3.
\b.1
\b10
\b09
\b9.
\b. m
\bmh
\bh_
\b_p
\bpu
\bur
\brg
\bge
\be
4761 When unset, mutt will mimic mh's behaviour and rename deleted messages
4762 to _
\b,_
\b<_
\bo_
\bl_
\bd _
\bf_
\bi_
\bl_
\be _
\bn_
\ba_
\bm_
\be_
\b> in mh folders instead of really deleting them. If
4763 the variable is set, the message files will simply be deleted.
4765 6
\b6.
\b.3
\b3.
\b.1
\b11
\b10
\b0.
\b. m
\bmh
\bh_
\b_s
\bse
\beq
\bq_
\b_f
\bfl
\bla
\bag
\bgg
\bge
\bed
\bd
4770 The name of the MH sequence used for flagged messages.
4772 6
\b6.
\b.3
\b3.
\b.1
\b11
\b11
\b1.
\b. m
\bmh
\bh_
\b_s
\bse
\beq
\bq_
\b_r
\bre
\bep
\bpl
\bli
\bie
\bed
\bd
4777 The name of the MH sequence used to tag replied messages.
4779 6
\b6.
\b.3
\b3.
\b.1
\b11
\b12
\b2.
\b. m
\bmh
\bh_
\b_s
\bse
\beq
\bq_
\b_u
\bun
\bns
\bse
\bee
\ben
\bn
4784 The name of the MH sequence used for unseen messages.
4786 6
\b6.
\b.3
\b3.
\b.1
\b11
\b13
\b3.
\b. m
\bmi
\bim
\bme
\be_
\b_f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd
4791 When set, the message you are forwarding will be attached as a
4792 separate MIME part instead of included in the main body of the
4793 message. This is useful for forwarding MIME messages so the receiver
4794 can properly view the message as it was delivered to you. If you like
4795 to switch between MIME and not MIME from mail to mail, set this
4796 variable to ask-no or ask-yes.
4798 Also see ````$forward_decode'''' and ````$mime_forward_decode''''.
4800 6
\b6.
\b.3
\b3.
\b.1
\b11
\b14
\b4.
\b. m
\bmi
\bim
\bme
\be_
\b_f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_d
\bde
\bec
\bco
\bod
\bde
\be
4805 Controls the decoding of complex MIME messages into text/plain when
4806 forwarding a message while ````$mime_forward'''' is _
\bs_
\be_
\bt. Otherwise
4807 ````$forward_decode'''' is used instead.
4809 6
\b6.
\b.3
\b3.
\b.1
\b11
\b15
\b5.
\b. m
\bmi
\bim
\bme
\be_
\b_f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_r
\bre
\bes
\bst
\bt
4814 When forwarding multiple attachments of a MIME message from the
4815 recvattach menu, attachments which cannot be decoded in a reasonable
4816 manner will be attached to the newly composed message if this option
4819 6
\b6.
\b.3
\b3.
\b.1
\b11
\b16
\b6.
\b. m
\bmi
\bim
\bme
\be_
\b_s
\bsu
\bub
\bbj
\bje
\bec
\bct
\bt
4824 If _
\bu_
\bn_
\bs_
\be_
\bt, 8-bit ``subject:'' line in article header will not be
4825 encoded according to RFC2047 to base64. This is useful when message
4826 is Usenet article, because MIME for news is nonstandard feature.
4828 6
\b6.
\b.3
\b3.
\b.1
\b11
\b17
\b7.
\b. m
\bmi
\bix
\bx_
\b_e
\ben
\bnt
\btr
\bry
\by_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4831 Default: "%4n %c %-16s %a"
4833 This variable describes the format of a remailer line on the mixmaster
4834 chain selection screen. The following printf-like sequences are
4837 %
\b%n
\bn The running number on the menu.
4839 %
\b%c
\bc Remailer capabilities.
4841 %
\b%s
\bs The remailer's short name.
4843 %
\b%a
\ba The remailer's e-mail address.
4845 6
\b6.
\b.3
\b3.
\b.1
\b11
\b18
\b8.
\b. m
\bmi
\bix
\bxm
\bma
\bas
\bst
\bte
\ber
\br
4848 Default: "mixmaster"
4850 This variable contains the path to the Mixmaster binary on your
4851 system. It is used with various sets of parameters to gather the list
4852 of known remailers, and to finally send a message through the
4855 6
\b6.
\b.3
\b3.
\b.1
\b11
\b19
\b9.
\b. m
\bmo
\bov
\bve
\be
4860 Controls whether you will be asked to confirm moving read messages
4861 from your spool mailbox to your ````$mbox'''' mailbox, or as a result
4862 of a ````mbox-hook'''' command.
4864 6
\b6.
\b.3
\b3.
\b.1
\b12
\b20
\b0.
\b. m
\bme
\bes
\bss
\bsa
\bag
\bge
\be_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4869 This is the string displayed in the ``attachment'' menu for
4870 attachments of type message/rfc822. For a full listing of defined
4871 printf()-like sequences see the section on ````$index_format''''.
4873 6
\b6.
\b.3
\b3.
\b.1
\b12
\b21
\b1.
\b. n
\bna
\bar
\brr
\bro
\bow
\bw_
\b_t
\btr
\bre
\bee
\be
4878 This variable, when set, makes the thread tree narrower, allowing
4879 deeper threads to fit on the screen.
4881 6
\b6.
\b.3
\b3.
\b.1
\b12
\b22
\b2.
\b. n
\bne
\bew
\bws
\bs_
\b_c
\bca
\bac
\bch
\bhe
\be_
\b_d
\bdi
\bir
\br
4886 This variable pointing to directory where Mutt will save cached news
4887 articles headers in. If _
\bu_
\bn_
\bs_
\be_
\bt, headers will not be saved at all and
4888 will be reloaded each time when you enter to newsgroup.
4890 6
\b6.
\b.3
\b3.
\b.1
\b12
\b23
\b3.
\b. n
\bne
\bew
\bws
\bs_
\b_s
\bse
\ber
\brv
\bve
\ber
\br
4895 This variable specifies domain name or address of NNTP server. It
4896 defaults to the newsserver specified in the environment variable
4897 $NNTPSERVER or contained in the file /etc/nntpserver. You can also
4898 specify username and an alternative port for each newsserver, ie:
4900 [nntp[s]://][username[:password]@]newsserver[:port]
4902 6
\b6.
\b.3
\b3.
\b.1
\b12
\b24
\b4.
\b. n
\bne
\bew
\bws
\bsr
\brc
\bc
4905 Default: "~/.newsrc"
4907 The file, containing info about subscribed newsgroups - names and
4908 indexes of read articles. The following printf-style sequence is
4913 6
\b6.
\b.3
\b3.
\b.1
\b12
\b25
\b5.
\b. n
\bnn
\bnt
\btp
\bp_
\b_c
\bco
\bon
\bnt
\bte
\bex
\bxt
\bt
4918 This variable defines number of articles which will be in index when
4919 newsgroup entered. If active newsgroup have more articles than this
4920 number, oldest articles will be ignored. Also controls how many
4921 articles headers will be saved in cache when you quit newsgroup.
4923 6
\b6.
\b.3
\b3.
\b.1
\b12
\b26
\b6.
\b. n
\bnn
\bnt
\btp
\bp_
\b_l
\blo
\boa
\bad
\bd_
\b_d
\bde
\bes
\bsc
\bcr
\bri
\bip
\bpt
\bti
\bio
\bon
\bn
4928 This variable controls whether or not descriptions for each newsgroup
4929 must be loaded when newsgroup is added to list (first time list
4930 loading or new newsgroup adding).
4932 6
\b6.
\b.3
\b3.
\b.1
\b12
\b27
\b7.
\b. n
\bnn
\bnt
\btp
\bp_
\b_u
\bus
\bse
\ber
\br
4937 Your login name on the NNTP server. If _
\bu_
\bn_
\bs_
\be_
\bt and NNTP server requires
4938 authentification, Mutt will prompt you for your account name when you
4939 connect to newsserver.
4941 6
\b6.
\b.3
\b3.
\b.1
\b12
\b28
\b8.
\b. n
\bnn
\bnt
\btp
\bp_
\b_p
\bpa
\bas
\bss
\bs
4946 Your password for NNTP account.
4948 6
\b6.
\b.3
\b3.
\b.1
\b12
\b29
\b9.
\b. n
\bnn
\bnt
\btp
\bp_
\b_p
\bpo
\bol
\bll
\bl
4953 The time in seconds until any operations on newsgroup except post new
4954 article will cause recheck for new news. If set to 0, Mutt will
4955 recheck newsgroup on each operation in index (stepping, read article,
4958 6
\b6.
\b.3
\b3.
\b.1
\b13
\b30
\b0.
\b. n
\bnn
\bnt
\btp
\bp_
\b_r
\bre
\bec
\bco
\bon
\bnn
\bne
\bec
\bct
\bt
4963 Controls whether or not Mutt will try to reconnect to newsserver when
4966 6
\b6.
\b.3
\b3.
\b.1
\b13
\b31
\b1.
\b. p
\bpa
\bag
\bge
\ber
\br
4971 This variable specifies which pager you would like to use to view
4972 messages. builtin means to use the builtin pager, otherwise this
4973 variable should specify the pathname of the external pager you would
4976 Using an external pager may have some disadvantages: Additional
4977 keystrokes are necessary because you can't call mutt functions
4978 directly from the pager, and screen resizes cause lines longer than
4979 the screen width to be badly formatted in the help menu.
4981 6
\b6.
\b.3
\b3.
\b.1
\b13
\b32
\b2.
\b. p
\bpa
\bag
\bge
\ber
\br_
\b_c
\bco
\bon
\bnt
\bte
\bex
\bxt
\bt
4986 This variable controls the number of lines of context that are given
4987 when displaying the next or previous page in the internal pager. By
4988 default, Mutt will display the line after the last one on the screen
4989 at the top of the next page (0 lines of context).
4991 6
\b6.
\b.3
\b3.
\b.1
\b13
\b33
\b3.
\b. p
\bpa
\bag
\bge
\ber
\br_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
4994 Default: "-%Z- %C/%m: %-20.20n %s"
4996 This variable controls the format of the one-line message ``status''
4997 displayed before each message in either the internal or an external
4998 pager. The valid sequences are listed in the ````$index_format''''
5001 6
\b6.
\b.3
\b3.
\b.1
\b13
\b34
\b4.
\b. p
\bpa
\bag
\bge
\ber
\br_
\b_i
\bin
\bnd
\bde
\bex
\bx_
\b_l
\bli
\bin
\bne
\bes
\bs
5006 Determines the number of lines of a mini-index which is shown when in
5007 the pager. The current message, unless near the top or bottom of the
5008 folder, will be roughly one third of the way down this mini-index,
5009 giving the reader the context of a few messages before and after the
5010 message. This is useful, for example, to determine how many messages
5011 remain to be read in the current thread. One of the lines is reserved
5012 for the status bar from the index, so a _
\bp_
\ba_
\bg_
\be_
\br_
\b__
\bi_
\bn_
\bd_
\be_
\bx_
\b__
\bl_
\bi_
\bn_
\be_
\bs of 6 will
5013 only show 5 lines of the actual index. A value of 0 results in no
5014 index being shown. If the number of messages in the current folder is
5015 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
5018 6
\b6.
\b.3
\b3.
\b.1
\b13
\b35
\b5.
\b. p
\bpa
\bag
\bge
\ber
\br_
\b_s
\bst
\bto
\bop
\bp
5023 When set, the internal-pager will n
\bno
\bot
\bt move to the next message when
5024 you are at the end of a message and invoke the _
\bn_
\be_
\bx_
\bt_
\b-_
\bp_
\ba_
\bg_
\be function.
5026 6
\b6.
\b.3
\b3.
\b.1
\b13
\b36
\b6.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_a
\bau
\but
\bto
\bos
\bsi
\big
\bgn
\bn
5031 Setting this variable will cause Mutt to always attempt to
5032 cryptographically sign outgoing messages. This can be overridden by
5033 use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when signing is not required or encryption is
5034 requested as well. If ````$smime_is_default'''' is set, then OpenSSL
5035 is used instead to create S/MIME messages and settings can be
5036 overridden by use of the _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
5038 6
\b6.
\b.3
\b3.
\b.1
\b13
\b37
\b7.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_a
\bau
\but
\bto
\boe
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bt
5043 Setting this variable will cause Mutt to always attempt to PGP encrypt
5044 outgoing messages. This is probably only useful in connection to the
5045 _
\bs_
\be_
\bn_
\bd_
\b-_
\bh_
\bo_
\bo_
\bk command. It can be overridden by use of the _
\bp_
\bg_
\bp_
\b-_
\bm_
\be_
\bn_
\bu, when
5046 encryption is not required or signing is requested as well. IF
5047 ````$smime_is_default'''' is set, then OpenSSL is used instead to
5048 create S/MIME messages and settings can be overridden by use of the
5049 _
\bs_
\bm_
\bi_
\bm_
\be_
\b-_
\bm_
\be_
\bn_
\bu. (Crypto only)
5050 6
\b6.
\b.3
\b3.
\b.1
\b13
\b38
\b8.
\b. p
\bpg
\bgp
\bp_
\b_i
\big
\bgn
\bno
\bor
\bre
\be_
\b_s
\bsu
\bub
\bbk
\bke
\bey
\bys
\bs
5055 Setting this variable will cause Mutt to ignore OpenPGP subkeys.
5056 Instead, the principal key will inherit the subkeys' capabilities.
5057 Unset this if you want to play interesting key selection games. (PGP
5060 6
\b6.
\b.3
\b3.
\b.1
\b13
\b39
\b9.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_r
\bre
\bep
\bpl
\bly
\bye
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bt
5065 If set, automatically PGP or OpenSSL encrypt replies to messages which
5066 are encrypted. (Crypto only)
5068 6
\b6.
\b.3
\b3.
\b.1
\b14
\b40
\b0.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_r
\bre
\bep
\bpl
\bly
\bys
\bsi
\big
\bgn
\bn
5073 If set, automatically PGP or OpenSSL sign replies to messages which
5076 N
\bNo
\bot
\bte
\be:
\b: this does not work on messages that are encrypted a
\ban
\bnd
\bd signed!
5079 6
\b6.
\b.3
\b3.
\b.1
\b14
\b41
\b1.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_r
\bre
\bep
\bpl
\bly
\bys
\bsi
\big
\bgn
\bne
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bte
\bed
\bd
5084 If set, automatically PGP or OpenSSL sign replies to messages which
5085 are encrypted. This makes sense in combination with
5086 ````$crypt_replyencrypt'''', because it allows you to sign all
5087 messages which are automatically encrypted. This works around the
5088 problem noted in ````$crypt_replysign'''', that mutt is not able to
5089 find out whether an encrypted message is also signed. (Crypto only)
5091 6
\b6.
\b.3
\b3.
\b.1
\b14
\b42
\b2.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_t
\bti
\bim
\bme
\bes
\bst
\bta
\bam
\bmp
\bp
5096 If set, mutt will include a time stamp in the lines surrounding PGP or
5097 S/MIME output, so spoofing such lines is more difficult. If you are
5098 using colors to mark these lines, and rely on these, you may unset
5099 this setting. (Crypto only)
5101 6
\b6.
\b.3
\b3.
\b.1
\b14
\b43
\b3.
\b. p
\bpg
\bgp
\bp_
\b_u
\bus
\bse
\be_
\b_g
\bgp
\bpg
\bg_
\b_a
\bag
\bge
\ben
\bnt
\bt
5106 If set, mutt will use a possibly-running gpg-agent process. (PGP
5109 6
\b6.
\b.3
\b3.
\b.1
\b14
\b44
\b4.
\b. c
\bcr
\bry
\byp
\bpt
\bt_
\b_v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_s
\bsi
\big
\bg
5114 If ``yes'', always attempt to verify PGP or S/MIME signatures. If
5115 ``ask'', ask whether or not to verify the signature. If ``no'', never
5116 attempt to verify cryptographic signatures. (Crypto only)
5118 6
\b6.
\b.3
\b3.
\b.1
\b14
\b45
\b5.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_i
\bis
\bs_
\b_d
\bde
\bef
\bfa
\bau
\bul
\blt
\bt
5123 The default behaviour of mutt is to use PGP on all auto-
5124 sign/encryption operations. To override and to use OpenSSL instead
5125 this must be set. However, this has no effect while replying, since
5126 mutt will automatically select the same application that was used to
5127 sign/encrypt the original message. (Note that this variable can be
5128 overridden by unsetting ``$crypt_autosmime''.) (S/MIME only)
5130 6
\b6.
\b.3
\b3.
\b.1
\b14
\b46
\b6.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_a
\bas
\bsk
\bk_
\b_c
\bce
\ber
\brt
\bt_
\b_l
\bla
\bab
\bbe
\bel
\bl
5135 This flag controls whether you want to be asked to enter a label for a
5136 certificate about to be added to the database or not. It is set by
5137 default. (S/MIME only)
5139 6
\b6.
\b.3
\b3.
\b.1
\b14
\b47
\b7.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_d
\bde
\bec
\bcr
\bry
\byp
\bpt
\bt_
\b_u
\bus
\bse
\be_
\b_d
\bde
\bef
\bfa
\bau
\bul
\blt
\bt_
\b_k
\bke
\bey
\by
5144 If set (default) this tells mutt to use the default key for
5145 decryption. Otherwise, if manage multiple certificate-key-pairs, mutt
5146 will try to use the mailbox-address to determine the key to use. It
5147 will ask you to supply a key, if it can't find one. (S/MIME only)
5149 6
\b6.
\b.3
\b3.
\b.1
\b14
\b48
\b8.
\b. p
\bpg
\bgp
\bp_
\b_e
\ben
\bnt
\btr
\bry
\by_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
5152 Default: "%4n %t%f %4l/0x%k %-4a %2c %u"
5154 This variable allows you to customize the PGP key selection menu to
5155 your personal taste. This string is similar to ````$index_format'''',
5156 but has its own set of printf()-like sequences:
5170 %
\b%c
\bc capabilities
5172 %
\b%t
\bt trust/validity of the key-uid association
5174 %
\b%[
\b[<
\b<s
\bs>
\b>]
\b]
5175 date of the key where <s> is an strftime(3) expression
5179 6
\b6.
\b.3
\b3.
\b.1
\b14
\b49
\b9.
\b. p
\bpg
\bgp
\bp_
\b_g
\bgo
\boo
\bod
\bd_
\b_s
\bsi
\big
\bgn
\bn
5181 Type: regular expression
5184 If you assign a text to this variable, then a PGP signature is only
5185 considered verified if the output from ``$pgp_verify_command''
5186 contains the text. Use this variable if the exit code from the command
5187 is 0 even for bad signatures. (PGP only)
5189 6
\b6.
\b.3
\b3.
\b.1
\b15
\b50
\b0.
\b. p
\bpg
\bgp
\bp_
\b_c
\bch
\bhe
\bec
\bck
\bk_
\b_e
\bex
\bxi
\bit
\bt
5194 If set, mutt will check the exit code of the PGP subprocess when
5195 signing or encrypting. A non-zero exit code means that the subprocess
5198 6
\b6.
\b.3
\b3.
\b.1
\b15
\b51
\b1.
\b. p
\bpg
\bgp
\bp_
\b_l
\blo
\bon
\bng
\bg_
\b_i
\bid
\bds
\bs
5203 If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs.
5206 6
\b6.
\b.3
\b3.
\b.1
\b15
\b52
\b2.
\b. p
\bpg
\bgp
\bp_
\b_r
\bre
\bet
\bta
\bai
\bin
\bna
\bab
\bbl
\ble
\be_
\b_s
\bsi
\big
\bgs
\bs
5211 If set, signed and encrypted messages will consist of nested
5212 multipart/signed and multipart/encrypted body parts.
5214 This is useful for applications like encrypted and signed mailing
5215 lists, where the outer layer (multipart/encrypted) can be easily
5216 removed, while the inner multipart/signed part is retained. (PGP
5219 6
\b6.
\b.3
\b3.
\b.1
\b15
\b53
\b3.
\b. p
\bpg
\bgp
\bp_
\b_s
\bsh
\bho
\bow
\bw_
\b_u
\bun
\bnu
\bus
\bsa
\bab
\bbl
\ble
\be
5224 If set, mutt will display non-usable keys on the PGP key selection
5225 menu. This includes keys which have been revoked, have expired, or
5226 have been marked as ``disabled'' by the user. (PGP only)
5228 6
\b6.
\b.3
\b3.
\b.1
\b15
\b54
\b4.
\b. p
\bpg
\bgp
\bp_
\b_s
\bsi
\big
\bgn
\bn_
\b_a
\bas
\bs
5233 If you have more than one key pair, this option allows you to specify
5234 which of your private keys to use. It is recommended that you use the
5235 keyid form to specify your key (e.g., ``0x00112233''). (PGP only)
5237 6
\b6.
\b.3
\b3.
\b.1
\b15
\b55
\b5.
\b. p
\bpg
\bgp
\bp_
\b_s
\bst
\btr
\bri
\bic
\bct
\bt_
\b_e
\ben
\bnc
\bc
5242 If set, Mutt will automatically encode PGP/MIME signed messages as
5243 _
\bq_
\bu_
\bo_
\bt_
\be_
\bd_
\b-_
\bp_
\br_
\bi_
\bn_
\bt_
\ba_
\bb_
\bl_
\be. Please note that unsetting this variable may lead
5244 to problems with non-verifyable PGP signatures, so only change this if
5245 you know what you are doing. (PGP only)
5247 6
\b6.
\b.3
\b3.
\b.1
\b15
\b56
\b6.
\b. p
\bpg
\bgp
\bp_
\b_t
\bti
\bim
\bme
\beo
\bou
\but
\bt
5252 The number of seconds after which a cached passphrase will expire if
5253 not used. (PGP only)
5254 6
\b6.
\b.3
\b3.
\b.1
\b15
\b57
\b7.
\b. p
\bpg
\bgp
\bp_
\b_s
\bso
\bor
\brt
\bt_
\b_k
\bke
\bey
\bys
\bs
5259 Specifies how the entries in the `pgp keys' menu are sorted. The
5260 following are legal values:
5262 a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs
5263 sort alphabetically by user id
5265 k
\bke
\bey
\byi
\bid
\bd
5266 sort alphabetically by key id
5269 sort by key creation date
5271 t
\btr
\bru
\bus
\bst
\bt
5272 sort by the trust of the key
5274 If you prefer reverse order of the above values, prefix it with
5275 `reverse-'. (PGP only)
5277 6
\b6.
\b.3
\b3.
\b.1
\b15
\b58
\b8.
\b. p
\bpg
\bgp
\bp_
\b_c
\bcr
\bre
\bea
\bat
\bte
\be_
\b_t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl
5282 This option controls whether Mutt generates old-style inline PGP
5283 encrypted or signed messages.
5285 Note that PGP/MIME will be used automatically for messages which have
5286 a character set different from us-ascii, or which consist of more than
5289 Also note that using the old-style PGP message format is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by
5290 d
\bde
\bep
\bpr
\bre
\bec
\bca
\bat
\bte
\bed
\bd. (PGP only)
5292 6
\b6.
\b.3
\b3.
\b.1
\b15
\b59
\b9.
\b. p
\bpg
\bgp
\bp_
\b_a
\bau
\but
\bto
\bo_
\b_t
\btr
\bra
\bad
\bdi
\bit
\bti
\bio
\bon
\bna
\bal
\bl
5297 This option causes Mutt to generate an old-style inline PGP encrypted
5298 or signed message when replying to an old-style message, and a
5299 PGP/MIME message when replying to a PGP/MIME message. Note that this
5300 option is only meaningful when using ````$crypt_replyencrypt'''',
5301 ````$crypt_replysign'''', or ````$crypt_replysignencrypted''''.
5303 Also note that PGP/MIME will be used automatically for messages which
5304 have a character set different from us-ascii, or which consist of more
5305 than a single MIME part.
5307 This option overrides ````$pgp_create_traditional'''' (PGP only)
5309 6
\b6.
\b.3
\b3.
\b.1
\b16
\b60
\b0.
\b. p
\bpg
\bgp
\bp_
\b_d
\bde
\bec
\bco
\bod
\bde
\be_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5314 This format strings specifies a command which is used to decode
5315 application/pgp attachments.
5317 The PGP command formats have their own set of printf-like sequences:
5319 %
\b%p
\bp Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
5320 string otherwise. Note: This may be used with a %? construct.
5322 %
\b%f
\bf Expands to the name of a file containing a message.
5324 %
\b%s
\bs Expands to the name of a file containing the signature part of a
5325 multipart/signed attachment when verifying it.
5327 %
\b%a
\ba The value of ``$pgp_sign_as''.
5329 %
\b%r
\br One or more key IDs.
5331 For examples on how to configure these formats for the various
5332 versions of PGP which are floating around, see the pgp*.rc and gpg.rc
5333 files in the samples/ subdirectory which has been installed on your
5334 system alongside the documentation. (PGP only)
5336 6
\b6.
\b.3
\b3.
\b.1
\b16
\b61
\b1.
\b. p
\bpg
\bgp
\bp_
\b_g
\bge
\bet
\btk
\bke
\bey
\bys
\bs_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5341 This command is invoked whenever mutt will need public key
5342 information. %r is the only printf-like sequence used with this
5345 6
\b6.
\b.3
\b3.
\b.1
\b16
\b62
\b2.
\b. p
\bpg
\bgp
\bp_
\b_v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5350 This command is used to verify PGP signatures. (PGP only)
5352 6
\b6.
\b.3
\b3.
\b.1
\b16
\b63
\b3.
\b. p
\bpg
\bgp
\bp_
\b_d
\bde
\bec
\bcr
\bry
\byp
\bpt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5357 This command is used to decrypt a PGP encrypted message. (PGP only)
5359 6
\b6.
\b.3
\b3.
\b.1
\b16
\b64
\b4.
\b. p
\bpg
\bgp
\bp_
\b_c
\bcl
\ble
\bea
\bar
\brs
\bsi
\big
\bgn
\bn_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5364 This format is used to create a old-style "clearsigned" PGP message.
5365 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)
5367 6
\b6.
\b.3
\b3.
\b.1
\b16
\b65
\b5.
\b. p
\bpg
\bgp
\bp_
\b_s
\bsi
\big
\bgn
\bn_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5372 This command is used to create the detached PGP signature for a
5373 multipart/signed PGP/MIME body part. (PGP only)
5375 6
\b6.
\b.3
\b3.
\b.1
\b16
\b66
\b6.
\b. p
\bpg
\bgp
\bp_
\b_e
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bt_
\b_s
\bsi
\big
\bgn
\bn_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5380 This command is used to both sign and encrypt a body part. (PGP only)
5382 6
\b6.
\b.3
\b3.
\b.1
\b16
\b67
\b7.
\b. p
\bpg
\bgp
\bp_
\b_e
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bt_
\b_o
\bon
\bnl
\bly
\by_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5387 This command is used to encrypt a body part without signing it. (PGP
5390 6
\b6.
\b.3
\b3.
\b.1
\b16
\b68
\b8.
\b. p
\bpg
\bgp
\bp_
\b_i
\bim
\bmp
\bpo
\bor
\brt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5395 This command is used to import a key from a message into the user's
5396 public key ring. (PGP only)
5398 6
\b6.
\b.3
\b3.
\b.1
\b16
\b69
\b9.
\b. p
\bpg
\bgp
\bp_
\b_e
\bex
\bxp
\bpo
\bor
\brt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5403 This command is used to export a public key from the user's key ring.
5406 6
\b6.
\b.3
\b3.
\b.1
\b17
\b70
\b0.
\b. p
\bpg
\bgp
\bp_
\b_v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bke
\bey
\by_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5411 This command is used to verify key information from the key selection
5414 6
\b6.
\b.3
\b3.
\b.1
\b17
\b71
\b1.
\b. p
\bpg
\bgp
\bp_
\b_l
\bli
\bis
\bst
\bt_
\b_s
\bse
\bec
\bcr
\bri
\bin
\bng
\bg_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5419 This command is used to list the secret key ring's contents. The
5420 output format must be analogous to the one used by gpg --list-keys
5423 This format is also generated by the pgpring utility which comes with
5426 6
\b6.
\b.3
\b3.
\b.1
\b17
\b72
\b2.
\b. p
\bpg
\bgp
\bp_
\b_l
\bli
\bis
\bst
\bt_
\b_p
\bpu
\bub
\bbr
\bri
\bin
\bng
\bg_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5431 This command is used to list the public key ring's contents. The
5432 output format must be analogous to the one used by gpg --list-keys
5435 This format is also generated by the pgpring utility which comes with
5438 6
\b6.
\b.3
\b3.
\b.1
\b17
\b73
\b3.
\b. f
\bfo
\bor
\brw
\bwa
\bar
\brd
\bd_
\b_d
\bde
\bec
\bcr
\bry
\byp
\bpt
\bt
5443 Controls the handling of encrypted messages when forwarding a message.
5444 When set, the outer layer of encryption is stripped off. This
5445 variable is only used if ````$mime_forward'''' is _
\bs_
\be_
\bt and
5446 ````$mime_forward_decode'''' is _
\bu_
\bn_
\bs_
\be_
\bt. (PGP only)
5448 6
\b6.
\b.3
\b3.
\b.1
\b17
\b74
\b4.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_t
\bti
\bim
\bme
\beo
\bou
\but
\bt
5453 The number of seconds after which a cached passphrase will expire if
5454 not used. (S/MIME only)
5456 6
\b6.
\b.3
\b3.
\b.1
\b17
\b75
\b5.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_e
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bt_
\b_w
\bwi
\bit
\bth
\bh
5461 This sets the algorithm that should be used for encryption. Valid
5462 choices are "des", "des3", "rc2-40", "rc2-64", "rc2-128". If unset
5463 "3des" (TripleDES) is used. (S/MIME only)
5465 6
\b6.
\b.3
\b3.
\b.1
\b17
\b76
\b6.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_k
\bke
\bey
\bys
\bs
5470 Since there is no pubring/secring as with PGP, mutt has to handle
5471 storage ad retrieval of keys/certs by itself. This is very basic right
5472 now, and stores keys and certificates in two different directories,
5473 both named as the hash-value retrieved from OpenSSL. There is an index
5474 file which contains mailbox-address keyid pair, and which can be
5475 manually edited. This one points to the location of the private keys.
5478 6
\b6.
\b.3
\b3.
\b.1
\b17
\b77
\b7.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_c
\bca
\ba_
\b_l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn
5483 This variable contains the name of either a directory, or a file which
5484 contains trusted certificates for use with OpenSSL. (S/MIME only)
5486 6
\b6.
\b.3
\b3.
\b.1
\b17
\b78
\b8.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_c
\bce
\ber
\brt
\bti
\bif
\bfi
\bic
\bca
\bat
\bte
\bes
\bs
5491 Since there is no pubring/secring as with PGP, mutt has to handle
5492 storage and retrieval of keys by itself. This is very basic right now,
5493 and keys and certificates are stored in two different directories,
5494 both named as the hash-value retrieved from OpenSSL. There is an index
5495 file which contains mailbox-address keyid pairs, and which can be
5496 manually edited. This one points to the location of the certificates.
5499 6
\b6.
\b.3
\b3.
\b.1
\b17
\b79
\b9.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_d
\bde
\bec
\bcr
\bry
\byp
\bpt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5504 This format string specifies a command which is used to decrypt
5505 application/x-pkcs7-mime attachments.
5507 The OpenSSL command formats have their own set of printf-like
5508 sequences similar to PGP's:
5509 %
\b%f
\bf Expands to the name of a file containing a message.
5511 %
\b%s
\bs Expands to the name of a file containing the signature part of a
5512 multipart/signed attachment when verifying it.
5514 %
\b%k
\bk The key-pair specified with ``$smime_default_key''
5516 %
\b%c
\bc One or more certificate IDs.
5518 %
\b%a
\ba The algorithm used for encryption.
5520 %
\b%C
\bC CA location: Depending on whether ``$smime_ca_location'' points
5521 to a directory or file, this expands to "-CApath
5522 ``$smime_ca_location''" or "-CAfile ``$smime_ca_location''".
5524 For examples on how to configure these formats, see the smime.rc in
5525 the samples/ subdirectory which has been installed on your system
5526 alongside the documentation. (S/MIME only)
5528 6
\b6.
\b.3
\b3.
\b.1
\b18
\b80
\b0.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5533 This command is used to verify S/MIME signatures of type
5534 multipart/signed. (S/MIME only)
5536 6
\b6.
\b.3
\b3.
\b.1
\b18
\b81
\b1.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_o
\bop
\bpa
\baq
\bqu
\bue
\be_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5541 This command is used to verify S/MIME signatures of type
5542 application/x-pkcs7-mime. (S/MIME only)
5544 6
\b6.
\b.3
\b3.
\b.1
\b18
\b82
\b2.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_s
\bsi
\big
\bgn
\bn_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5549 This command is used to created S/MIME signatures of type
5550 multipart/signed, which can be read by all mail clients. (S/MIME
5553 6
\b6.
\b.3
\b3.
\b.1
\b18
\b83
\b3.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_s
\bsi
\big
\bgn
\bn_
\b_o
\bop
\bpa
\baq
\bqu
\bue
\be_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5558 This command is used to created S/MIME signatures of type
5559 application/x-pkcs7-signature, which can only be handled by mail
5560 clients supporting the S/MIME extension. (S/MIME only)
5562 6
\b6.
\b.3
\b3.
\b.1
\b18
\b84
\b4.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_e
\ben
\bnc
\bcr
\bry
\byp
\bpt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5567 This command is used to create encrypted S/MIME messages. (S/MIME
5570 6
\b6.
\b.3
\b3.
\b.1
\b18
\b85
\b5.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_p
\bpk
\bk7
\b7o
\bou
\but
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5575 This command is used to extract PKCS7 structures of S/MIME signatures,
5576 in order to extract the public X509 certificate(s). (S/MIME only)
5578 6
\b6.
\b.3
\b3.
\b.1
\b18
\b86
\b6.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_g
\bge
\bet
\bt_
\b_c
\bce
\ber
\brt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5583 This command is used to extract X509 certificates from a PKCS7
5584 structure. (S/MIME only)
5586 6
\b6.
\b.3
\b3.
\b.1
\b18
\b87
\b7.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_g
\bge
\bet
\bt_
\b_s
\bsi
\big
\bgn
\bne
\ber
\br_
\b_c
\bce
\ber
\brt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5591 This command is used to extract only the signers X509 certificate from
5592 a S/MIME signature, so that the certificate's owner may get compared
5593 to the email's (S/MIME only)
5595 6
\b6.
\b.3
\b3.
\b.1
\b18
\b88
\b8.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_i
\bim
\bmp
\bpo
\bor
\brt
\bt_
\b_c
\bce
\ber
\brt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5600 This command is used to import a certificate via smime_keys. (S/MIME
5603 6
\b6.
\b.3
\b3.
\b.1
\b18
\b89
\b9.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_g
\bge
\bet
\bt_
\b_c
\bce
\ber
\brt
\bt_
\b_e
\bem
\bma
\bai
\bil
\bl_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5608 This command is used to extract the mail address(es) used for storing
5609 X509 certificates, and for verification purposes (to check whether the
5610 certificate was issued for the sender's mailbox). (S/MIME only)
5612 6
\b6.
\b.3
\b3.
\b.1
\b19
\b90
\b0.
\b. s
\bsm
\bmi
\bim
\bme
\be_
\b_d
\bde
\bef
\bfa
\bau
\bul
\blt
\bt_
\b_k
\bke
\bey
\by
5617 This is the default key-pair to use for signing. This must be set to
5618 the keyid (the hash-value that OpenSSL generates) to work properly
5621 6
\b6.
\b.3
\b3.
\b.1
\b19
\b91
\b1.
\b. s
\bss
\bsl
\bl_
\b_s
\bst
\bta
\bar
\brt
\btt
\btl
\bls
\bs
5626 If set (the default), mutt will attempt to use STARTTLS on servers
5627 advertising the capability. When unset, mutt will not attempt to use
5628 STARTTLS regardless of the server's capabilities.
5630 6
\b6.
\b.3
\b3.
\b.1
\b19
\b92
\b2.
\b. c
\bce
\ber
\brt
\bti
\bif
\bfi
\bic
\bca
\bat
\bte
\be_
\b_f
\bfi
\bil
\ble
\be
5635 This variable specifies the file where the certificates you trust are
5636 saved. When an unknown certificate is encountered, you are asked if
5637 you accept it or not. If you accept it, the certificate can also be
5638 saved in this file and further connections are automatically accepted.
5640 You can also manually add CA certificates in this file. Any server
5641 certificate that is signed with one of these CA certificates are also
5642 automatically accepted.
5644 Example: set certificate_file=~/.mutt/certificates
5646 6
\b6.
\b.3
\b3.
\b.1
\b19
\b93
\b3.
\b. s
\bss
\bsl
\bl_
\b_u
\bus
\bse
\bes
\bsy
\bys
\bst
\bte
\bem
\bmc
\bce
\ber
\brt
\bts
\bs
5651 If set to _
\by_
\be_
\bs, mutt will use CA certificates in the system-wide
5652 certificate store when checking if server certificate is signed by a
5655 6
\b6.
\b.3
\b3.
\b.1
\b19
\b94
\b4.
\b. e
\ben
\bnt
\btr
\bro
\bop
\bpy
\by_
\b_f
\bfi
\bil
\ble
\be
5660 The file which includes random data that is used to initialize SSL
5663 6
\b6.
\b.3
\b3.
\b.1
\b19
\b95
\b5.
\b. s
\bss
\bsl
\bl_
\b_u
\bus
\bse
\be_
\b_s
\bss
\bsl
\blv
\bv2
\b2
5668 This variables specifies whether to attempt to use SSLv2 in the SSL
5669 authentication process.
5671 6
\b6.
\b.3
\b3.
\b.1
\b19
\b96
\b6.
\b. s
\bss
\bsl
\bl_
\b_u
\bus
\bse
\be_
\b_s
\bss
\bsl
\blv
\bv3
\b3
5676 This variables specifies whether to attempt to use SSLv3 in the SSL
5677 authentication process.
5679 6
\b6.
\b.3
\b3.
\b.1
\b19
\b97
\b7.
\b. s
\bss
\bsl
\bl_
\b_u
\bus
\bse
\be_
\b_t
\btl
\bls
\bsv
\bv1
\b1
5684 This variables specifies whether to attempt to use TLSv1 in the SSL
5685 authentication process.
5687 6
\b6.
\b.3
\b3.
\b.1
\b19
\b98
\b8.
\b. p
\bpi
\bip
\bpe
\be_
\b_s
\bsp
\bpl
\bli
\bit
\bt
5692 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command and the ``tag-
5693 prefix'' operator. If this variable is unset, when piping a list of
5694 tagged messages Mutt will concatenate the messages and will pipe them
5695 as a single folder. When set, Mutt will pipe the messages one by one.
5696 In both cases the messages are piped in the current sorted order, and
5697 the ````$pipe_sep'''' separator is added after each message.
5699 6
\b6.
\b.3
\b3.
\b.1
\b19
\b99
\b9.
\b. p
\bpi
\bip
\bpe
\be_
\b_d
\bde
\bec
\bco
\bod
\bde
\be
5704 Used in connection with the _
\bp_
\bi_
\bp_
\be_
\b-_
\bm_
\be_
\bs_
\bs_
\ba_
\bg_
\be command. When unset, Mutt
5705 will pipe the messages without any preprocessing. When set, Mutt will
5706 weed headers and will attempt to PGP/MIME decode the messages first.
5708 6
\b6.
\b.3
\b3.
\b.2
\b20
\b00
\b0.
\b. p
\bpi
\bip
\bpe
\be_
\b_s
\bse
\bep
\bp
5713 The separator to add between messages when piping a list of tagged
5714 messages to an external Unix command.
5716 6
\b6.
\b.3
\b3.
\b.2
\b20
\b01
\b1.
\b. p
\bpo
\bop
\bp_
\b_a
\bau
\but
\bth
\bhe
\ben
\bnt
\bti
\bic
\bca
\bat
\bto
\bor
\brs
\bs
5721 This is a colon-delimited list of authentication methods mutt may
5722 attempt to use to log in to an POP server, in the order mutt should
5723 try them. Authentication methods are either 'user', 'apop' or any
5724 SASL mechanism, eg 'digest-md5', 'gssapi' or 'cram-md5'. This
5725 parameter is case-insensitive. If this parameter is unset (the
5726 default) mutt will try all available methods, in order from most-
5727 secure to least-secure.
5729 Example: set pop_authenticators="digest-md5:apop:user"
5731 6
\b6.
\b.3
\b3.
\b.2
\b20
\b02
\b2.
\b. p
\bpo
\bop
\bp_
\b_a
\bau
\but
\bth
\bh_
\b_t
\btr
\bry
\by_
\b_a
\bal
\bll
\bl
5736 If set, Mutt will try all available methods. When unset, Mutt will
5737 only fall back to other authentication methods if the previous methods
5738 are unavailable. If a method is available but authentication fails,
5739 Mutt will not connect to the POP server.
5741 6
\b6.
\b.3
\b3.
\b.2
\b20
\b03
\b3.
\b. p
\bpo
\bop
\bp_
\b_c
\bch
\bhe
\bec
\bck
\bki
\bin
\bnt
\bte
\ber
\brv
\bva
\bal
\bl
5746 This variable configures how often (in seconds) POP should look for
5749 6
\b6.
\b.3
\b3.
\b.2
\b20
\b04
\b4.
\b. p
\bpo
\bop
\bp_
\b_d
\bde
\bel
\ble
\bet
\bte
\be
5754 If set, Mutt will delete successfully downloaded messages from the POP
5755 server when using the fetch-mail function. When unset, Mutt will
5756 download messages but also leave them on the POP server.
5758 6
\b6.
\b.3
\b3.
\b.2
\b20
\b05
\b5.
\b. p
\bpo
\bop
\bp_
\b_h
\bho
\bos
\bst
\bt
5763 The name of your POP server for the fetch-mail function. You can also
5764 specify an alternative port, username and password, ie:
5766 [pop[s]://][username[:password]@]popserver[:port]
5768 6
\b6.
\b.3
\b3.
\b.2
\b20
\b06
\b6.
\b. p
\bpo
\bop
\bp_
\b_l
\bla
\bas
\bst
\bt
5773 If this variable is set, mutt will try to use the "LAST" POP command
5774 for retrieving only unread messages from the POP server when using the
5775 fetch-mail function.
5777 6
\b6.
\b.3
\b3.
\b.2
\b20
\b07
\b7.
\b. p
\bpo
\bop
\bp_
\b_r
\bre
\bec
\bco
\bon
\bnn
\bne
\bec
\bct
\bt
5782 Controls whether or not Mutt will try to reconnect to POP server when
5785 6
\b6.
\b.3
\b3.
\b.2
\b20
\b08
\b8.
\b. p
\bpo
\bop
\bp_
\b_u
\bus
\bse
\ber
\br
5790 Your login name on the POP server.
5792 This variable defaults to your user name on the local machine.
5794 6
\b6.
\b.3
\b3.
\b.2
\b20
\b09
\b9.
\b. p
\bpo
\bop
\bp_
\b_p
\bpa
\bas
\bss
\bs
5799 Specifies the password for your POP account. If unset, Mutt will
5800 prompt you for your password when you open POP mailbox. W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg: you
5801 should only use this option when you are on a fairly secure machine,
5802 because the superuser can read your muttrc even if you are the only
5803 one who can read the file.
5805 6
\b6.
\b.3
\b3.
\b.2
\b21
\b10
\b0.
\b. p
\bpo
\bos
\bst
\bt_
\b_i
\bin
\bnd
\bde
\ben
\bnt
\bt_
\b_s
\bst
\btr
\bri
\bin
\bng
\bg
5810 Similar to the ````$attribution'''' variable, Mutt will append this
5811 string after the inclusion of a message which is being replied to.
5813 6
\b6.
\b.3
\b3.
\b.2
\b21
\b11
\b1.
\b. p
\bpo
\bos
\bst
\bt_
\b_m
\bmo
\bod
\bde
\ber
\bra
\bat
\bte
\bed
\bd
5818 If set to _
\by_
\be_
\bs, Mutt will post article to newsgroup that have not
5819 permissions to posting (e.g. moderated). N
\bNo
\bot
\bte
\be:
\b: if newsserver does not
5820 support posting to that newsgroup or totally read-only, that posting
5821 will not have an effect.
5823 6
\b6.
\b.3
\b3.
\b.2
\b21
\b12
\b2.
\b. p
\bpo
\bos
\bst
\btp
\bpo
\bon
\bne
\be
5828 Controls whether or not messages are saved in the ````$postponed''''
5829 mailbox when you elect not to send immediately.
5831 6
\b6.
\b.3
\b3.
\b.2
\b21
\b13
\b3.
\b. p
\bpo
\bos
\bst
\btp
\bpo
\bon
\bne
\bed
\bd
5834 Default: "~/postponed"
5836 Mutt allows you to indefinitely ````postpone'' sending a message''
5837 which you are editing. When you choose to postpone a message, Mutt
5838 saves it in the mailbox specified by this variable. Also see the
5839 ````$postpone'''' variable.
5841 6
\b6.
\b.3
\b3.
\b.2
\b21
\b14
\b4.
\b. p
\bpr
\bre
\bec
\bco
\bon
\bnn
\bne
\bec
\bct
\bt
5846 If set, a shell command to be executed if mutt fails to establish a
5847 connection to the server. This is useful for setting up secure
5848 connections, e.g. with ssh(1). If the command returns a nonzero
5849 status, mutt gives up opening the server. Example:
5851 preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
5852 /dev/null > /dev/null"
5854 Mailbox 'foo' on mailhost.net can now be reached as
5855 '{localhost:1234}foo'.
5857 NOTE: For this example to work, you must be able to log in to the
5858 remote machine without having to enter a password.
5860 6
\b6.
\b.3
\b3.
\b.2
\b21
\b15
\b5.
\b. p
\bpr
\bri
\bin
\bnt
\bt
5865 Controls whether or not Mutt asks for confirmation before printing.
5866 This is useful for people (like me) who accidentally hit ``p'' often.
5868 6
\b6.
\b.3
\b3.
\b.2
\b21
\b16
\b6.
\b. p
\bpr
\bri
\bin
\bnt
\bt_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5873 This specifies the command pipe that should be used to print messages.
5875 6
\b6.
\b.3
\b3.
\b.2
\b21
\b17
\b7.
\b. p
\bpr
\bri
\bin
\bnt
\bt_
\b_d
\bde
\bec
\bco
\bod
\bde
\be
5880 Used in connection with the print-message command. If this option is
5881 set, the message is decoded before it is passed to the external
5882 command specified by ``$print_command''. If this option is unset, no
5883 processing will be applied to the message when printing it. The
5884 latter setting may be useful if you are using some advanced printer
5885 filter which is able to properly format e-mail messages for printing.
5887 6
\b6.
\b.3
\b3.
\b.2
\b21
\b18
\b8.
\b. p
\bpr
\bri
\bin
\bnt
\bt_
\b_s
\bsp
\bpl
\bli
\bit
\bt
5892 Used in connection with the print-message command. If this option is
5893 set, the command specified by ``$print_command'' is executed once for
5894 each message which is to be printed. If this option is unset, the
5895 command specified by ``$print_command'' is executed only once, and all
5896 the messages are concatenated, with a form feed as the message
5899 Those who use the e
\ben
\bns
\bsc
\bcr
\bri
\bip
\bpt
\bt(1) program's mail-printing mode will most
5900 likely want to set this option.
5902 6
\b6.
\b.3
\b3.
\b.2
\b21
\b19
\b9.
\b. p
\bpr
\bro
\bom
\bmp
\bpt
\bt_
\b_a
\baf
\bft
\bte
\ber
\br
5907 If you use an _
\be_
\bx_
\bt_
\be_
\br_
\bn_
\ba_
\bl ````$pager'''', setting this variable will
5908 cause Mutt to prompt you for a command when the pager exits rather
5909 than returning to the index menu. If unset, Mutt will return to the
5910 index menu when the external pager exits.
5912 6
\b6.
\b.3
\b3.
\b.2
\b22
\b20
\b0.
\b. q
\bqu
\bue
\ber
\bry
\by_
\b_c
\bco
\bom
\bmm
\bma
\ban
\bnd
\bd
5917 This specifies the command that mutt will use to make external address
5918 queries. The string should contain a %s, which will be substituted
5919 with the query string the user types. See ````query'''' for more
5922 6
\b6.
\b.3
\b3.
\b.2
\b22
\b21
\b1.
\b. q
\bqu
\bui
\bit
\bt
5927 This variable controls whether ``quit'' and ``exit'' actually quit
5928 from mutt. If it set to yes, they do quit, if it is set to no, they
5929 have no effect, and if it is set to ask-yes or ask-no, you are
5930 prompted for confirmation when you try to quit.
5932 6
\b6.
\b.3
\b3.
\b.2
\b22
\b22
\b2.
\b. q
\bqu
\buo
\bot
\bte
\be_
\b_r
\bre
\beg
\bge
\bex
\bxp
\bp
5934 Type: regular expression
5935 Default: "^([ \t]*[|>:}#])+"
5937 A regular expression used in the internal-pager to determine quoted
5938 sections of text in the body of a message.
5940 N
\bNo
\bot
\bte
\be:
\b: In order to use the _
\bq_
\bu_
\bo_
\bt_
\be_
\bdx
\bx patterns in the internal pager, you
5941 need to set this to a regular expression that matches _
\be_
\bx_
\ba_
\bc_
\bt_
\bl_
\by the
5942 quote characters at the beginning of quoted lines.
5944 6
\b6.
\b.3
\b3.
\b.2
\b22
\b23
\b3.
\b. r
\bre
\bea
\bad
\bd_
\b_i
\bin
\bnc
\bc
5949 If set to a value greater than 0, Mutt will display which message it
5950 is currently on when reading a mailbox. The message is printed after
5951 _
\br_
\be_
\ba_
\bd_
\b__
\bi_
\bn_
\bc messages have been read (e.g., if set to 25, Mutt will print
5952 a message when it reads message 25, and then again when it gets to
5953 message 50). This variable is meant to indicate progress when reading
5954 large mailboxes which may take some time. When set to 0, only a
5955 single message will appear before the reading the mailbox.
5957 Also see the ````$write_inc'''' variable.
5959 6
\b6.
\b.3
\b3.
\b.2
\b22
\b24
\b4.
\b. r
\bre
\bea
\bad
\bd_
\b_o
\bon
\bnl
\bly
\by
5964 If set, all folders are opened in read-only mode.
5966 6
\b6.
\b.3
\b3.
\b.2
\b22
\b25
\b5.
\b. r
\bre
\bea
\bal
\bln
\bna
\bam
\bme
\be
5971 This variable specifies what "real" or "personal" name should be used
5972 when sending messages.
5974 By default, this is the GECOS field from /etc/passwd. Note that this
5975 variable will _
\bn_
\bo_
\bt be used when the user has set a real name in the
5978 6
\b6.
\b.3
\b3.
\b.2
\b22
\b26
\b6.
\b. r
\bre
\bec
\bca
\bal
\bll
\bl
5983 Controls whether or not you are prompted to recall postponed messages
5984 when composing a new message. Also see ````$postponed''''.
5986 Setting this variable to ``yes'' is not generally useful, and thus not
5989 6
\b6.
\b.3
\b3.
\b.2
\b22
\b27
\b7.
\b. r
\bre
\bec
\bco
\bor
\brd
\bd
5994 This specifies the file into which your outgoing messages should be
5995 appended. (This is meant as the primary method for saving a copy of
5996 your messages, but another way to do this is using the ````my_hdr''''
5997 command to create a _
\bB_
\bc_
\bc_
\b: field with your email address in it.)
5999 The value of _
\b`_
\b`_
\b$_
\br_
\be_
\bc_
\bo_
\br_
\bd_
\b'_
\b' is overridden by the ````$force_name'''' and
6000 ````$save_name'''' variables, and the ````fcc-hook'''' command.
6002 6
\b6.
\b.3
\b3.
\b.2
\b22
\b28
\b8.
\b. r
\bre
\bep
\bpl
\bly
\by_
\b_r
\bre
\beg
\bge
\bex
\bxp
\bp
6004 Type: regular expression
6005 Default: "^(re([\[0-9\]+])*|aw):[ \t]*"
6007 A regular expression used to recognize reply messages when threading
6008 and replying. The default value corresponds to the English "Re:" and
6011 6
\b6.
\b.3
\b3.
\b.2
\b22
\b29
\b9.
\b. r
\bre
\bep
\bpl
\bly
\by_
\b_s
\bse
\bel
\blf
\bf
6016 If unset and you are replying to a message sent by you, Mutt will
6017 assume that you want to reply to the recipients of that message rather
6019 6
\b6.
\b.3
\b3.
\b.2
\b23
\b30
\b0.
\b. r
\bre
\bep
\bpl
\bly
\by_
\b_t
\bto
\bo
6024 If set, Mutt will ask you if you want to use the address listed in the
6025 Reply-To: header field when replying to a message. If you answer no,
6026 it will use the address in the From: header field instead. This
6027 option is useful for reading a mailing list that sets the Reply-To:
6028 header field to the list address and you want to send a private
6029 message to the author of a message.
6031 6
\b6.
\b.3
\b3.
\b.2
\b23
\b31
\b1.
\b. r
\bre
\bes
\bso
\bol
\blv
\bve
\be
6036 When set, the cursor will be automatically advanced to the next
6037 (possibly undeleted) message whenever a command that modifies the
6038 current message is executed.
6040 6
\b6.
\b.3
\b3.
\b.2
\b23
\b32
\b2.
\b. r
\bre
\bev
\bve
\ber
\brs
\bse
\be_
\b_a
\bal
\bli
\bia
\bas
\bs
6045 This variable controls whether or not Mutt will display the "personal"
6046 name from your aliases in the index menu if it finds an alias that
6047 matches the message's sender. For example, if you have the following
6050 alias juser abd30425@somewhere.net (Joe User)
6052 and then you receive mail which contains the following header:
6054 From: abd30425@somewhere.net
6056 It would be displayed in the index menu as ``Joe User'' instead of
6057 ``abd30425@somewhere.net.'' This is useful when the person's e-mail
6058 address is not human friendly (like CompuServe addresses).
6060 6
\b6.
\b.3
\b3.
\b.2
\b23
\b33
\b3.
\b. r
\bre
\bev
\bve
\ber
\brs
\bse
\be_
\b_n
\bna
\bam
\bme
\be
6064 It may sometimes arrive that you receive mail to a certain machine,
6065 move the messages to another machine, and reply to some the messages
6066 from there. If this variable is set, the default _
\bF_
\br_
\bo_
\bm_
\b: line of the
6067 reply messages is built using the address where you received the
6068 messages you are replying to. If the variable is unset, the _
\bF_
\br_
\bo_
\bm_
\b:
6069 line will use your address on the current machine.
6071 6
\b6.
\b.3
\b3.
\b.2
\b23
\b34
\b4.
\b. r
\bre
\bev
\bve
\ber
\brs
\bse
\be_
\b_r
\bre
\bea
\bal
\bln
\bna
\bam
\bme
\be
6076 This variable fine-tunes the behaviour of the ``reverse_name''
6077 feature. When it is set, mutt will use the address from incoming
6078 messages as-is, possibly including eventual real names. When it is
6079 unset, mutt will override any such real names with the setting of the
6080 ``realname'' variable.
6082 6
\b6.
\b.3
\b3.
\b.2
\b23
\b35
\b5.
\b. r
\brf
\bfc
\bc2
\b20
\b04
\b47
\b7_
\b_p
\bpa
\bar
\bra
\bam
\bme
\bet
\bte
\ber
\brs
\bs
6087 When this variable is set, Mutt will decode RFC-2047-encoded MIME
6088 parameters. You want to set this variable when mutt suggests you to
6089 save attachments to files named like this:
6090 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
6092 When this variable is set interactively, the change doesn't have the
6093 desired effect before you have changed folders.
6095 Note that this use of RFC 2047's encoding is explicitly, prohibited by
6096 the standard, but nevertheless encountered in the wild. Also note
6097 that setting this parameter will _
\bn_
\bo_
\bt have the effect that mutt
6098 _
\bg_
\be_
\bn_
\be_
\br_
\ba_
\bt_
\be_
\bs this kind of encoding. Instead, mutt will unconditionally
6099 use the encoding specified in RFC 2231.
6101 6
\b6.
\b.3
\b3.
\b.2
\b23
\b36
\b6.
\b. s
\bsa
\bav
\bve
\be_
\b_a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs
6106 If set, mutt will take the sender's full address when choosing a
6107 default folder for saving a mail. If ````$save_name'''' or
6108 ````$force_name'''' is set too, the selection of the fcc folder will
6111 6
\b6.
\b.3
\b3.
\b.2
\b23
\b37
\b7.
\b. s
\bsa
\bav
\bve
\be_
\b_e
\bem
\bmp
\bpt
\bty
\by
6116 When unset, mailboxes which contain no saved messages will be removed
6117 when closed (the exception is ````$spoolfile'''' which is never
6118 removed). If set, mailboxes are never removed.
6120 N
\bNo
\bot
\bte
\be:
\b: This only applies to mbox and MMDF folders, Mutt does not delete
6121 MH and Maildir directories.
6123 6
\b6.
\b.3
\b3.
\b.2
\b23
\b38
\b8.
\b. s
\bsa
\bav
\bve
\be_
\b_n
\bna
\bam
\bme
\be
6128 This variable controls how copies of outgoing messages are saved.
6129 When set, a check is made to see if a mailbox specified by the
6130 recipient address exists (this is done by searching for a mailbox in
6131 the ````$folder'''' directory with the _
\bu_
\bs_
\be_
\br_
\bn_
\ba_
\bm_
\be part of the recipient
6132 address). If the mailbox exists, the outgoing message will be saved
6133 to that mailbox, otherwise the message is saved to the ````$record''''
6136 Also see the ````$force_name'''' variable.
6138 6
\b6.
\b.3
\b3.
\b.2
\b23
\b39
\b9.
\b. s
\bsc
\bco
\bor
\bre
\be
6143 When this variable is _
\bu_
\bn_
\bs_
\be_
\bt, scoring is turned off. This can be
6144 useful to selectively disable scoring for certain folders when the
6145 ````$score_threshold_delete'''' variable and friends are used.
6147 6
\b6.
\b.3
\b3.
\b.2
\b24
\b40
\b0.
\b. s
\bsc
\bco
\bor
\bre
\be_
\b_t
\bth
\bhr
\bre
\bes
\bsh
\bho
\bol
\bld
\bd_
\b_d
\bde
\bel
\ble
\bet
\bte
\be
6152 Messages which have been assigned a score equal to or lower than the
6153 value of this variable are automatically marked for deletion by mutt.
6154 Since mutt scores are always greater than or equal to zero, the
6155 default setting of this variable will never mark a message for
6158 6
\b6.
\b.3
\b3.
\b.2
\b24
\b41
\b1.
\b. s
\bsc
\bco
\bor
\bre
\be_
\b_t
\bth
\bhr
\bre
\bes
\bsh
\bho
\bol
\bld
\bd_
\b_f
\bfl
\bla
\bag
\bg
6163 Messages which have been assigned a score greater than or equal to
6164 this variable's value are automatically marked "flagged".
6166 6
\b6.
\b.3
\b3.
\b.2
\b24
\b42
\b2.
\b. s
\bsc
\bco
\bor
\bre
\be_
\b_t
\bth
\bhr
\bre
\bes
\bsh
\bho
\bol
\bld
\bd_
\b_r
\bre
\bea
\bad
\bd
6170 Messages which have been assigned a score equal to or lower than the
6171 value of this variable are automatically marked as read by mutt.
6172 Since mutt scores are always greater than or equal to zero, the
6173 default setting of this variable will never mark a message read.
6175 6
\b6.
\b.3
\b3.
\b.2
\b24
\b43
\b3.
\b. s
\bse
\ben
\bnd
\bd_
\b_c
\bch
\bha
\bar
\brs
\bse
\bet
\bt
6178 Default: "us-ascii:iso-8859-1:utf-8"
6180 A list of character sets for outgoing messages. Mutt will use the
6181 first character set into which the text can be converted exactly. If
6182 your ````$charset'''' is not iso-8859-1 and recipients may not
6183 understand UTF-8, it is advisable to include in the list an
6184 appropriate widely used standard character set (such as iso-8859-2,
6185 koi8-r or iso-2022-jp) either instead of or after "iso-8859-1".
6187 6
\b6.
\b.3
\b3.
\b.2
\b24
\b44
\b4.
\b. s
\bse
\ben
\bnd
\bdm
\bma
\bai
\bil
\bl
6190 Default: "/usr/sbin/sendmail -oem -oi"
6192 Specifies the program and arguments used to deliver mail sent by Mutt.
6193 Mutt expects that the specified program interprets additional
6194 arguments as recipient addresses.
6196 6
\b6.
\b.3
\b3.
\b.2
\b24
\b45
\b5.
\b. s
\bse
\ben
\bnd
\bdm
\bma
\bai
\bil
\bl_
\b_w
\bwa
\bai
\bit
\bt
6201 Specifies the number of seconds to wait for the ````$sendmail''''
6202 process to finish before giving up and putting delivery in the
6205 Mutt interprets the value of this variable as follows:
6207 >
\b>0
\b0 number of seconds to wait for sendmail to finish before
6210 0
\b0 wait forever for sendmail to finish
6212 <
\b<0
\b0 always put sendmail in the background without waiting
6214 Note that if you specify a value other than 0, the output of the child
6215 process will be put in a temporary file. If there is some error, you
6216 will be informed as to where to find the output.
6218 6
\b6.
\b.3
\b3.
\b.2
\b24
\b46
\b6.
\b. s
\bsh
\bhe
\bel
\bll
\bl
6223 Command to use when spawning a subshell. By default, the user's login
6224 shell from /etc/passwd is used.
6226 6
\b6.
\b.3
\b3.
\b.2
\b24
\b47
\b7.
\b. s
\bsa
\bav
\bve
\be_
\b_u
\bun
\bns
\bsu
\bub
\bbs
\bsc
\bcr
\bri
\bib
\bbe
\bed
\bd
6231 When _
\bs_
\be_
\bt, info about unsubscribed newsgroups will be saved into
6232 ``newsrc'' file and into cache.
6234 6
\b6.
\b.3
\b3.
\b.2
\b24
\b48
\b8.
\b. s
\bsh
\bho
\bow
\bw_
\b_n
\bne
\bew
\bw_
\b_n
\bne
\bew
\bws
\bs
6239 If _
\bs_
\be_
\bt, newsserver will be asked for new newsgroups on entering the
6240 browser. Otherwise, it will be done only once for a newsserver. Also
6241 controls whether or not number of new articles of subscribed
6242 newsgroups will be then checked.
6244 6
\b6.
\b.3
\b3.
\b.2
\b24
\b49
\b9.
\b. s
\bsh
\bho
\bow
\bw_
\b_o
\bon
\bnl
\bly
\by_
\b_u
\bun
\bnr
\bre
\bea
\bad
\bd
6249 If _
\bs_
\be_
\bt, only subscribed newsgroups that contain unread articles will
6250 be displayed in browser.
6252 6
\b6.
\b.3
\b3.
\b.2
\b25
\b50
\b0.
\b. s
\bsi
\big
\bg_
\b_d
\bda
\bas
\bsh
\bhe
\bes
\bs
6257 If set, a line containing ``-- '' will be inserted before your
6258 ````$signature''''. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you not unset
6259 this variable unless your ``signature'' contains just your name. The
6260 reason for this is because many software packages use ``-- \n'' to
6261 detect your signature. For example, Mutt has the ability to highlight
6262 the signature in a different color in the builtin pager.
6264 6
\b6.
\b.3
\b3.
\b.2
\b25
\b51
\b1.
\b. s
\bsi
\big
\bg_
\b_o
\bon
\bn_
\b_t
\bto
\bop
\bp
6269 If set, the signature will be included before any quoted or forwarded
6270 text. It is s
\bst
\btr
\bro
\bon
\bng
\bgl
\bly
\by recommended that you do not set this variable
6271 unless you really know what you are doing, and are prepared to take
6272 some heat from netiquette guardians.
6274 6
\b6.
\b.3
\b3.
\b.2
\b25
\b52
\b2.
\b. s
\bsi
\big
\bgn
\bna
\bat
\btu
\bur
\bre
\be
6277 Default: "~/.signature"
6279 Specifies the filename of your signature, which is appended to all
6280 outgoing messages. If the filename ends with a pipe (``|''), it is
6281 assumed that filename is a shell command and input should be read from
6284 6
\b6.
\b.3
\b3.
\b.2
\b25
\b53
\b3.
\b. s
\bsi
\bim
\bmp
\bpl
\ble
\be_
\b_s
\bse
\bea
\bar
\brc
\bch
\bh
6287 Default: "~f %s | ~s %s"
6289 Specifies how Mutt should expand a simple search into a real search
6290 pattern. A simple search is one that does not contain any of the ~
6291 operators. See ````patterns'''' for more information on search
6294 For example, if you simply type joe at a search or limit prompt, Mutt
6295 will automatically expand it to the value specified by this variable.
6296 For the default value it would be:
6300 6
\b6.
\b.3
\b3.
\b.2
\b25
\b54
\b4.
\b. s
\bsm
\bma
\bar
\brt
\bt_
\b_w
\bwr
\bra
\bap
\bp
6305 Controls the display of lines longer than the screen width in the
6306 internal pager. If set, long lines are wrapped at a word boundary. If
6307 unset, lines are simply wrapped at the screen edge. Also see the
6308 ````$markers'''' variable.
6310 6
\b6.
\b.3
\b3.
\b.2
\b25
\b55
\b5.
\b. s
\bsm
\bmi
\bil
\ble
\bey
\bys
\bs
6312 Type: regular expression
6313 Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
6315 The _
\bp_
\ba_
\bg_
\be_
\br uses this variable to catch some common false positives of
6316 ````$quote_regexp'''', most notably smileys in the beginning of a line
6318 6
\b6.
\b.3
\b3.
\b.2
\b25
\b56
\b6.
\b. s
\bsl
\ble
\bee
\bep
\bp_
\b_t
\bti
\bim
\bme
\be
6323 Specifies time, in seconds, to pause while displaying certain
6324 informational messages, while moving from folder to folder and after
6325 expunging messages from the current folder. The default is to pause
6326 one second, so a value of zero for this option suppresses the pause.
6327 6
\b6.
\b.3
\b3.
\b.2
\b25
\b57
\b7.
\b. s
\bso
\bor
\brt
\bt
6332 Specifies how to sort messages in the _
\bi_
\bn_
\bd_
\be_
\bx menu. Valid values are:
6337 mailbox-order (unsorted)
6345 You may optionally use the reverse- prefix to specify reverse sorting
6346 order (example: set sort=reverse-date-sent).
6348 6
\b6.
\b.3
\b3.
\b.2
\b25
\b58
\b8.
\b. s
\bso
\bor
\brt
\bt_
\b_a
\bal
\bli
\bia
\bas
\bs
6353 Specifies how the entries in the `alias' menu are sorted. The
6354 following are legal values:
6356 address (sort alphabetically by email address)
6357 alias (sort alphabetically by alias name)
6358 unsorted (leave in order specified in .muttrc)
6360 6
\b6.
\b.3
\b3.
\b.2
\b25
\b59
\b9.
\b. s
\bso
\bor
\brt
\bt_
\b_a
\bau
\bux
\bx
6365 When sorting by threads, this variable controls how threads are sorted
6366 in relation to other threads, and how the branches of the thread trees
6367 are sorted. This can be set to any value that ````$sort'''' can,
6368 except threads (in that case, mutt will just use date-sent). You can
6369 also specify the last- prefix in addition to the reverse- prefix, but
6370 last- must come after reverse-. The last- prefix causes messages to
6371 be sorted against its siblings by which has the last descendant, using
6372 the rest of sort_aux as an ordering. For instance, set sort_aux=last-
6373 date-received would mean that if a new message is received in a
6374 thread, that thread becomes the last one displayed (or the first, if
6375 you have set sort=reverse-threads.) Note: For reversed ````$sort''''
6376 order ``$sort_aux'' is reversed again (which is not the right thing to
6377 do, but kept to not break any existing configuration setting).
6379 6
\b6.
\b.3
\b3.
\b.2
\b26
\b60
\b0.
\b. s
\bso
\bor
\brt
\bt_
\b_b
\bbr
\bro
\bow
\bws
\bse
\ber
\br
6384 Specifies how to sort entries in the file browser. By default, the
6385 entries are sorted alphabetically. Valid values:
6387 alpha (alphabetically)
6392 You may optionally use the reverse- prefix to specify reverse sorting
6393 order (example: set sort_browser=reverse-date).
6395 6
\b6.
\b.3
\b3.
\b.2
\b26
\b61
\b1.
\b. s
\bso
\bor
\brt
\bt_
\b_r
\bre
\be
6400 This variable is only useful when sorting by threads with
6401 ````$strict_threads'''' unset. In that case, it changes the heuristic
6402 mutt uses to thread messages by subject. With sort_re set, mutt will
6403 only attach a message as the child of another message by subject if
6404 the subject of the child message starts with a substring matching the
6405 setting of ````$reply_regexp''''. With sort_re unset, mutt will
6406 attach the message whether or not this is the case, as long as the
6407 non-````$reply_regexp'''' parts of both messages are identical.
6409 6
\b6.
\b.3
\b3.
\b.2
\b26
\b62
\b2.
\b. s
\bsp
\bpo
\boo
\bol
\blf
\bfi
\bil
\ble
\be
6414 If your spool mailbox is in a non-default place where Mutt cannot find
6415 it, you can specify its location with this variable. Mutt will
6416 automatically set this variable to the value of the environment
6417 variable $MAIL if it is not set.
6419 6
\b6.
\b.3
\b3.
\b.2
\b26
\b63
\b3.
\b. s
\bst
\bta
\bat
\btu
\bus
\bs_
\b_c
\bch
\bha
\bar
\brs
\bs
6424 Controls the characters used by the "%r" indicator in
6425 ````$status_format''''. The first character is used when the mailbox
6426 is unchanged. The second is used when the mailbox has been changed,
6427 and it needs to be resynchronized. The third is used if the mailbox is
6428 in read-only mode, or if the mailbox will not be written when exiting
6429 that mailbox (You can toggle whether to write changes to a mailbox
6430 with the toggle-write operation, bound by default to "%"). The fourth
6431 is used to indicate that the current folder has been opened in attach-
6432 message mode (Certain operations like composing a new mail, replying,
6433 forwarding, etc. are not permitted in this mode).
6435 6
\b6.
\b.3
\b3.
\b.2
\b26
\b64
\b4.
\b. s
\bst
\bta
\bat
\btu
\bus
\bs_
\b_f
\bfo
\bor
\brm
\bma
\bat
\bt
6438 Default: "-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
6439 Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
6440 %l?]---(%s/%S)-%>-(%P)---"
6442 Controls the format of the status line displayed in the _
\bi_
\bn_
\bd_
\be_
\bx menu.
6443 This string is similar to ````$index_format'''', but has its own set
6444 of printf()-like sequences:
6446 %
\b%b
\bb number of mailboxes with new mail *
6448 %
\b%d
\bd number of deleted messages *
6450 %
\b%f
\bf the full pathname of the current mailbox
6452 %
\b%F
\bF number of flagged messages *
6454 %
\b%h
\bh local hostname
6456 %
\b%l
\bl size (in bytes) of the current mailbox *
6458 %
\b%L
\bL size (in bytes) of the messages shown (i.e., which match the
6461 %
\b%m
\bm the number of messages in the mailbox *
6463 %
\b%M
\bM the number of messages shown (i.e., which match the current
6466 %
\b%n
\bn number of new messages in the mailbox *
6468 %
\b%o
\bo number of old unread messages
6470 %
\b%p
\bp number of postponed messages *
6472 %
\b%P
\bP percentage of the way through the index
6474 %
\b%r
\br modified/read-only/won't-write/attach-message indicator,
6475 according to ``$status_chars''
6477 %
\b%s
\bs current sorting mode (``$sort'')
6479 %
\b%S
\bS current aux sorting method (``$sort_aux'')
6481 %
\b%t
\bt number of tagged messages *
6483 %
\b%u
\bu number of unread messages *
6485 %
\b%v
\bv Mutt version string
6487 %
\b%V
\bV currently active limit pattern, if any *
6490 right justify the rest of the string and pad with "X"
6493 pad to the end of the line with "X"
6495 * = can be optionally printed if nonzero
6497 Some of the above sequences can be used to optionally print a string
6498 if their value is nonzero. For example, you may only want to see the
6499 number of flagged messages if such messages exist, since zero is not
6500 particularly meaningful. To optionally print a string based upon one
6501 of the above sequences, the following construct is used
6503 %?<sequence_char>?<optional_string>?
6505 where
\e[4msequence_char
\e[24m is a character from the table above, and
6506 \e[4moptional_string
\e[24m is the string you would like printed if
\e[4mstatus_char
\e[24m is
6507 nonzero.
\e[4moptional_string
\e[24m
\e[1mmay
\e[22mcontain other sequence as well as normal
6508 text, but you may
\e[1mnot
\e[22mnest optional strings.
6510 Here is an example illustrating how to optionally print the number of
6511 new messages in a mailbox: %?n?%n new messages.?
6513 Additionally you can switch between two strings, the first one, if a
6514 value is zero, the second one, if the value is nonzero, by using the
6515 following construct: %?<sequence_char>?<if_string>&<else_string>?
6517 You can additionally force the result of any printf-like sequence to
6518 be lowercase by prefixing the sequence character with an underscore
6519 (_) sign. For example, if you want to display the local hostname in
6520 lowercase, you would use: %_h
6522 If you prefix the sequence character with a colon (:) character, mutt
6523 will replace any dots in the expansion by underscores. This might be
6524 helpful with IMAP folders that don't like dots in folder names.
6526 6
\b6.
\b.3
\b3.
\b.2
\b26
\b65
\b5.
\b. s
\bst
\bta
\bat
\btu
\bus
\bs_
\b_o
\bon
\bn_
\b_t
\bto
\bop
\bp
6531 Setting this variable causes the ``status bar'' to be displayed on the
6532 first line of the screen rather than near the bottom.
6534 6
\b6.
\b.3
\b3.
\b.2
\b26
\b66
\b6.
\b. s
\bst
\btr
\bri
\bic
\bct
\bt_
\b_t
\bth
\bhr
\bre
\bea
\bad
\bds
\bs
6539 If set, threading will only make use of the ``In-Reply-To'' and
6540 ``References'' fields when you ````$sort'''' by message threads. By
6541 default, messages with the same subject are grouped together in
6542 ``pseudo threads.'' This may not always be desirable, such as in a
6543 personal mailbox where you might have several unrelated messages with
6544 the subject ``hi'' which will get grouped together.
6546 6
\b6.
\b.3
\b3.
\b.2
\b26
\b67
\b7.
\b. s
\bsu
\bus
\bsp
\bpe
\ben
\bnd
\bd
6551 When _
\bu_
\bn_
\bs_
\be_
\bt, mutt won't stop when the user presses the terminal's _
\bs_
\bu_
\bs_
\bp
6552 key, usually ``control-Z''. This is useful if you run mutt inside an
6553 xterm using a command like xterm -e mutt.
6555 6
\b6.
\b.3
\b3.
\b.2
\b26
\b68
\b8.
\b. t
\bte
\bex
\bxt
\bt_
\b_f
\bfl
\blo
\bow
\bwe
\bed
\bd
6560 When set, mutt will generate text/plain; format=flowed attachments.
6561 This format is easier to handle for some mailing software, and
6562 generally just looks like ordinary text. To actually make use of this
6563 format's features, you'll need support in your editor.
6565 Note that ``$indent_string'' is ignored when this option is set.
6567 6
\b6.
\b.3
\b3.
\b.2
\b26
\b69
\b9.
\b. t
\bth
\bhr
\bre
\bea
\bad
\bd_
\b_r
\bre
\bec
\bce
\bei
\biv
\bve
\bed
\bd
6572 When set, mutt uses the date received rather than the date sent to
6573 thread messages by subject.
6575 6
\b6.
\b.3
\b3.
\b.2
\b27
\b70
\b0.
\b. t
\bth
\bho
\bor
\bro
\bou
\bug
\bgh
\bh_
\b_s
\bse
\bea
\bar
\brc
\bch
\bh
6580 Affects the _
\b~_
\bb and _
\b~_
\bh search operations described in section
6581 ````patterns'''' above. If set, the headers and attachments of
6582 messages to be searched are decoded before searching. If unset,
6583 messages are searched as they appear in the folder.
6585 6
\b6.
\b.3
\b3.
\b.2
\b27
\b71
\b1.
\b. t
\bti
\bil
\bld
\bde
\be
6590 When set, the internal-pager will pad blank lines to the bottom of the
6591 screen with a tilde (~).
6593 6
\b6.
\b.3
\b3.
\b.2
\b27
\b72
\b2.
\b. t
\bti
\bim
\bme
\beo
\bou
\but
\bt
6598 This variable controls the _
\bn_
\bu_
\bm_
\bb_
\be_
\br _
\bo_
\bf _
\bs_
\be_
\bc_
\bo_
\bn_
\bd_
\bs Mutt will wait for a key
6599 to be pressed in the main menu before timing out and checking for new
6600 mail. A value of zero or less will cause Mutt to never time out.
6602 6
\b6.
\b.3
\b3.
\b.2
\b27
\b73
\b3.
\b. t
\btm
\bmp
\bpd
\bdi
\bir
\br
6607 This variable allows you to specify where Mutt will place its
6608 temporary files needed for displaying and composing messages. If this
6609 variable is not set, the environment variable TMPDIR is used. If
6610 TMPDIR is not set then "/tmp" is used.
6612 6
\b6.
\b.3
\b3.
\b.2
\b27
\b74
\b4.
\b. t
\bto
\bo_
\b_c
\bch
\bha
\bar
\brs
\bs
6617 Controls the character used to indicate mail addressed to you. The
6618 first character is the one used when the mail is NOT addressed to your
6619 address (default: space). The second is used when you are the only
6620 recipient of the message (default: +). The third is when your address
6621 appears in the TO header field, but you are not the only recipient of
6622 the message (default: T). The fourth character is used when your
6623 address is specified in the CC header field, but you are not the only
6624 recipient. The fifth character is used to indicate mail that was sent
6625 by _
\by_
\bo_
\bu. The sixth character is used to indicate when a mail was sent
6626 to a mailing-list you subscribe to (default: L).
6628 6
\b6.
\b.3
\b3.
\b.2
\b27
\b75
\b5.
\b. t
\btu
\bun
\bnn
\bne
\bel
\bl
6633 Setting this variable will cause mutt to open a pipe to a command
6634 instead of a raw socket. You may be able to use this to set up
6635 preauthenticated connections to your IMAP/POP3 server. Example:
6637 tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
6639 NOTE: For this example to work you must be able to log in to the
6640 remote machine without having to enter a password.
6642 6
\b6.
\b.3
\b3.
\b.2
\b27
\b76
\b6.
\b. u
\bus
\bse
\be_
\b_8
\b8b
\bbi
\bit
\btm
\bmi
\bim
\bme
\be
6647 W
\bWa
\bar
\brn
\bni
\bin
\bng
\bg:
\b: do not set this variable unless you are using a version of
6648 sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x)
6649 or you may not be able to send mail.
6651 When _
\bs_
\be_
\bt, Mutt will invoke ````$sendmail'''' with the -B8BITMIME flag
6652 when sending 8-bit messages to enable ESMTP negotiation.
6654 6
\b6.
\b.3
\b3.
\b.2
\b27
\b77
\b7.
\b. u
\bus
\bse
\be_
\b_d
\bdo
\bom
\bma
\bai
\bin
\bn
6659 When set, Mutt will qualify all local addresses (ones without the
6660 @host portion) with the value of ````$hostname''''. If _
\bu_
\bn_
\bs_
\be_
\bt, no
6661 addresses will be qualified.
6663 6
\b6.
\b.3
\b3.
\b.2
\b27
\b78
\b8.
\b. u
\bus
\bse
\be_
\b_f
\bfr
\bro
\bom
\bm
6668 When _
\bs_
\be_
\bt, Mutt will generate the `From:' header field when sending
6669 messages. If _
\bu_
\bn_
\bs_
\be_
\bt, no `From:' header field will be generated unless
6670 the user explicitly sets one using the ````my_hdr'''' command.
6672 6
\b6.
\b.3
\b3.
\b.2
\b27
\b79
\b9.
\b. u
\bus
\bse
\be_
\b_i
\bip
\bpv
\bv6
\b6
6677 When _
\bs_
\be_
\bt, Mutt will look for IPv6 addresses of hosts it tries to
6678 contact. If this option is unset, Mutt will restrict itself to IPv4
6679 addresses. Normally, the default should work.
6681 6
\b6.
\b.3
\b3.
\b.2
\b28
\b80
\b0.
\b. u
\bus
\bse
\ber
\br_
\b_a
\bag
\bge
\ben
\bnt
\bt
6686 When _
\bs_
\be_
\bt, mutt will add a "User-Agent" header to outgoing messages,
6687 indicating which version of mutt was used for composing them.
6689 6
\b6.
\b.3
\b3.
\b.2
\b28
\b81
\b1.
\b. v
\bvi
\bis
\bsu
\bua
\bal
\bl
6694 Specifies the visual editor to invoke when the _
\b~_
\bv command is given in
6697 6
\b6.
\b.3
\b3.
\b.2
\b28
\b82
\b2.
\b. w
\bwa
\bai
\bit
\bt_
\b_k
\bke
\bey
\by
6702 Controls whether Mutt will ask you to press a key after _
\bs_
\bh_
\be_
\bl_
\bl_
\b- _
\be_
\bs_
\bc_
\ba_
\bp_
\be,
6703 _
\bp_
\bi_
\bp_
\be_
\b-_
\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.
6705 It is also used when viewing attachments with ````auto_view'''',
6706 provided that the corresponding mailcap entry has a _
\bn_
\be_
\be_
\bd_
\bs_
\bt_
\be_
\br_
\bm_
\bi_
\bn_
\ba_
\bl
6707 flag, and the external program is interactive.
6709 When set, Mutt will always ask for a key. When unset, Mutt will wait
6710 for a key only if the external command returned a non-zero status.
6712 6
\b6.
\b.3
\b3.
\b.2
\b28
\b83
\b3.
\b. w
\bwe
\bee
\bed
\bd
6717 When set, mutt will weed headers when when displaying, forwarding,
6718 printing, or replying to messages.
6720 6
\b6.
\b.3
\b3.
\b.2
\b28
\b84
\b4.
\b. w
\bwr
\bra
\bap
\bp_
\b_s
\bse
\bea
\bar
\brc
\bch
\bh
6725 Controls whether searches wrap around the end of the mailbox.
6727 When set, searches will wrap around the first (or last) message. When
6728 unset, searches will not wrap.
6730 6
\b6.
\b.3
\b3.
\b.2
\b28
\b85
\b5.
\b. w
\bwr
\bra
\bap
\bpm
\bma
\bar
\brg
\bgi
\bin
\bn
6735 Controls the size of the margin remaining at the right side of the
6736 terminal when mutt's pager does smart wrapping.
6738 6
\b6.
\b.3
\b3.
\b.2
\b28
\b86
\b6.
\b. w
\bwr
\bri
\bit
\bte
\be_
\b_i
\bin
\bnc
\bc
6743 When writing a mailbox, a message will be printed every _
\bw_
\br_
\bi_
\bt_
\be_
\b__
\bi_
\bn_
\bc
6744 messages to indicate progress. If set to 0, only a single message
6745 will be displayed before writing a mailbox.
6747 Also see the ````$read_inc'''' variable.
6749 6
\b6.
\b.3
\b3.
\b.2
\b28
\b87
\b7.
\b. w
\bwr
\bri
\bit
\bte
\be_
\b_b
\bbc
\bcc
\bc
6754 Controls whether mutt writes out the Bcc header when preparing
6755 messages to be sent. Exim users may wish to use this.
6757 6
\b6.
\b.3
\b3.
\b.2
\b28
\b88
\b8.
\b. x
\bx_
\b_c
\bco
\bom
\bmm
\bme
\ben
\bnt
\bt_
\b_t
\bto
\bo
6762 If _
\bs_
\be_
\bt, Mutt will add ``X-Comment-To:'' field (that contains full name
6763 of original article author) to article that followuped to newsgroup.
6765 \e[1m6.4. Functions
\e[0m
6767 The following is the list of available functions listed by the mapping
6768 in which they are available. The default key setting is given, and an
6769 explanation of what the function does. The key bindings of these
6770 functions can be changed with the ``bind'' command.
6772 \e[1m6.4.1. generic
\e[0m
6774 The
\e[4mgeneric
\e[24m menu is not a real menu, but specifies common functions
6775 (such as movement) available in all menus except for
\e[4mpager
\e[24m and
\e[4meditor
\e[24m.
6776 Changing settings for this menu will affect the default bindings for
6777 all menus (except as noted).
6779 bottom-page L move to the bottom of the page
6780 current-bottom not bound move current entry to bottom of page
6781 current-middle not bound move current entry to middle of page
6782 current-top not bound move current entry to top of page
6783 enter-command : enter a muttrc command
6784 exit q exit this menu
6785 first-entry = move to the first entry
6786 half-down ] scroll down 1/2 page
6787 half-up [ scroll up 1/2 page
6789 jump number jump to an index number
6790 last-entry * move to the last entry
6791 middle-page M move to the middle of the page
6792 next-entry j move to the next entry
6793 next-line > scroll down one line
6794 next-page z move to the next page
6795 previous-entry k move to the previous entry
6796 previous-line < scroll up one line
6797 previous-page Z move to the previous page
6798 refresh ^L clear and redraw the screen
6799 search / search for a regular expression
6800 search-next n search for next match
6801 search-opposite not bound search for next match in opposite direction
6802 search-reverse ESC / search backwards for a regular expression
6803 select-entry RET select the current entry
6804 shell-escape ! run a program in a subshell
6805 tag-entry t toggle the tag on the current entry
6806 tag-prefix ; apply next command to tagged entries
6807 tag-prefix-cond not bound apply next function ONLY to tagged messages
6808 top-page H move to the top of the page
6810 \e[1m6.4.2. index
\e[0m
6812 bounce-message b remail a message to another user
6813 change-folder c open a different folder
6814 change-folder-readonly ESC c open a different folder in read only mode
6815 check-traditional-pgp ESC P check for classic pgp
6816 clear-flag W clear a status flag from a message
6817 copy-message C copy a message to a file/mailbox
6818 create-alias a create an alias from a message sender
6819 decode-copy ESC C decode a message and copy it to a file/mailbox
6820 decode-save ESC s decode a message and save it to a file/mailbox
6821 delete-message d delete the current entry
6822 delete-pattern D delete messages matching a pattern
6823 delete-subthread ESC d delete all messages in subthread
6824 delete-thread ^D delete all messages in thread
6825 display-address @ display full address of sender
6826 display-toggle-weed h display message and toggle header weeding
6827 display-message RET display a message
6828 edit e edit the current message
6829 edit-type ^E edit the current message's Content-Type
6830 exit x exit without saving changes
6831 extract-keys ^K extract PGP public keys
6832 fetch-mail G retrieve mail from POP server
6833 flag-message F toggle a message's 'important' flag
6834 forget-passphrase ^F wipe PGP passphrase from memory
6835 forward-message f forward a message with comments
6836 group-reply g reply to all recipients
6837 limit l show only messages matching a pattern
6838 list-reply L reply to specified mailing list
6839 mail m compose a new mail message
6840 mail-key ESC k mail a PGP public key
6841 next-new TAB jump to the next new message
6842 next-subthread ESC n jump to the next subthread
6843 next-thread ^N jump to the next thread
6844 next-undeleted j move to the next undeleted message
6845 next-unread not bound jump to the next unread message
6846 parent-message P jump to parent message in thread
6847 pipe-message | pipe message/attachment to a shell command
6848 previous-new ESC TAB jump to the previous new message
6849 previous-page Z move to the previous page
6850 previous-subthread ESC p jump to previous subthread
6851 previous-thread ^P jump to previous thread
6852 previous-undeleted k move to the last undelete message
6853 previous-unread not bound jump to the previous unread message
6854 print-message p print the current entry
6855 query Q query external program for addresses
6856 quit q save changes to mailbox and quit
6857 read-subthread ESC r mark the current subthread as read
6858 read-thread ^R mark the current thread as read
6859 recall-message R recall a postponed message
6860 reply r reply to a message
6861 resend-message ESC e resend message and preserve MIME structure
6862 save-message s save message/attachment to a file
6863 set-flag w set a status flag on a message
6864 show-version V show the Mutt version number and date
6865 show-limit ESC l show currently active limit pattern, if any
6866 sort-mailbox o sort messages
6867 sort-reverse O sort messages in reverse order
6868 sync-mailbox $ save changes to mailbox
6869 tag-pattern T tag messages matching a pattern
6870 tag-thread ESC t tag/untag all messages in the current thread
6871 toggle-new N toggle a message's 'new' flag
6872 toggle-write % toggle whether the mailbox will be rewritten
6873 undelete-message u undelete the current entry
6874 undelete-pattern U undelete messages matching a pattern
6875 undelete-subthread ESC u undelete all messages in subthread
6876 undelete-thread ^U undelete all messages in thread
6877 untag-pattern ^T untag messages matching a pattern
6878 view-attachments v show MIME attachments
6880 \e[1m6.4.3. pager
\e[0m
6882 bottom not bound jump to the bottom of the message
6883 bounce-message b remail a message to another user
6884 change-folder c open a different folder
6885 change-folder-readonly ESC c open a different folder in read only mode
6886 check-traditional-pgp ESC P check for classic pgp
6887 copy-message C copy a message to a file/mailbox
6888 create-alias a create an alias from a message sender
6889 decode-copy ESC C decode a message and copy it to a file/mailbox
6890 decode-save ESC s decode a message and save it to a file/mailbox
6891 delete-message d delete the current entry
6892 delete-subthread ESC d delete all messages in subthread
6893 delete-thread ^D delete all messages in thread
6894 display-address @ display full address of sender
6895 display-toggle-weed h display message and toggle header weeding
6896 edit e edit the current message
6897 edit-type ^E edit the current message's Content-Type
6898 enter-command : enter a muttrc command
6899 exit i return to the main-menu
6900 extract-keys ^K extract PGP public keys
6901 flag-message F toggle a message's 'important' flag
6902 forget-passphrase ^F wipe PGP passphrase from memory
6903 forward-message f forward a message with comments
6904 group-reply g reply to all recipients
6905 half-up not bound move up one-half page
6906 half-down not bound move down one-half page
6908 list-reply L reply to specified mailing list
6909 mail m compose a new mail message
6910 mail-key ESC k mail a PGP public key
6911 mark-as-new N toggle a message's 'new' flag
6912 next-line RET scroll down one line
6913 next-entry J move to the next entry
6914 next-new TAB jump to the next new message
6915 next-page move to the next page
6916 next-subthread ESC n jump to the next subthread
6917 next-thread ^N jump to the next thread
6918 next-undeleted j move to the next undeleted message
6919 next-unread not bound jump to the next unread message
6920 parent-message P jump to parent message in thread
6921 pipe-message | pipe message/attachment to a shell command
6922 previous-line BackSpace scroll up one line
6923 previous-entry K move to the previous entry
6924 previous-new not bound jump to the previous new message
6925 previous-page - move to the previous page
6926 previous-subthread ESC p jump to previous subthread
6927 previous-thread ^P jump to previous thread
6928 previous-undeleted k move to the last undelete message
6929 previous-unread not bound jump to the previous unread message
6930 print-message p print the current entry
6931 quit Q save changes to mailbox and quit
6932 read-subthread ESC r mark the current subthread as read
6933 read-thread ^R mark the current thread as read
6934 recall-message R recall a postponed message
6935 redraw-screen ^L clear and redraw the screen
6936 reply r reply to a message
6937 save-message s save message/attachment to a file
6938 search / search for a regular expression
6939 search-next n search for next match
6940 search-opposite not bound search for next match in opposite direction
6941 search-reverse ESC / search backwards for a regular expression
6942 search-toggle \ toggle search pattern coloring
6943 shell-escape ! invoke a command in a subshell
6944 show-version V show the Mutt version number and date
6945 skip-quoted S skip beyond quoted text
6946 sync-mailbox $ save changes to mailbox
6947 tag-message t tag a message
6948 toggle-quoted T toggle display of quoted text
6949 top ^ jump to the top of the message
6950 undelete-message u undelete the current entry
6951 undelete-subthread ESC u undelete all messages in subthread
6952 undelete-thread ^U undelete all messages in thread
6953 view-attachments v show MIME attachments
6955 \e[1m6.4.4. alias
\e[0m
6957 search / search for a regular expression
6958 search-next n search for next match
6959 search-reverse ESC / search backwards for a regular expression
6961 \e[1m6.4.5. query
\e[0m
6963 create-alias a create an alias from a message sender
6964 mail m compose a new mail message
6965 query Q query external program for addresses
6966 query-append A append new query results to current results
6967 search / search for a regular expression
6968 search-next n search for next match
6969 search-opposite not bound search for next match in opposite direction
6970 search-reverse ESC / search backwards for a regular expression
6972 \e[1m6.4.6. attach
\e[0m
6974 bounce-message b remail a message to another user
6975 collapse-parts v toggle display of subparts
6976 delete-entry d delete the current entry
6977 display-toggle-weed h display message and toggle header weeding
6978 edit-type ^E edit the current entry's Content-Type
6979 extract-keys ^K extract PGP public keys
6980 forward-message f forward a message with comments
6981 group-reply g reply to all recipients
6982 list-reply L reply to specified mailing list
6983 pipe-entry | pipe message/attachment to a shell command
6984 print-entry p print the current entry
6985 reply r reply to a message
6986 resend-message ESC e resend message and preserve MIME structure
6987 save-entry s save message/attachment to a file
6988 undelete-entry u undelete the current entry
6989 view-attach RET view attachment using mailcap entry if necessary
6990 view-mailcap m force viewing of attachment using mailcap
6991 view-text T view attachment as text
6993 \e[1m6.4.7. compose
\e[0m
6995 attach-file a attach a file(s) to this message
6996 attach-message A attach message(s) to this message
6997 attach-key ESC k attach a PGP public key
6998 copy-file C save message/attachment to a file
6999 detach-file D delete the current entry
7000 display-toggle-weed h display message and toggle header weeding
7001 edit-bcc b edit the BCC list
7002 edit-cc c edit the CC list
7003 edit-description d edit attachment description
7004 edit-encoding ^E edit attachment transfer-encoding
7005 edit-fcc f enter a file to save a copy of this message in
7006 edit-from ESC f edit the from: field
7007 edit-file ^X e edit the file to be attached
7008 edit-headers E edit the message with headers
7009 edit e edit the message
7010 edit-mime m edit attachment using mailcap entry
7011 edit-reply-to r edit the Reply-To field
7012 edit-subject s edit the subject of this message
7013 edit-to t edit the TO list
7014 edit-type ^T edit attachment type
7015 filter-entry F filter attachment through a shell command
7016 forget-passphrase ^F wipe PGP passphrase from memory
7017 ispell i run ispell on the message
7018 new-mime n compose new attachment using mailcap entry
7019 pgp-menu p show PGP options
7020 pipe-entry | pipe message/attachment to a shell command
7021 postpone-message P save this message to send later
7022 print-entry l print the current entry
7023 rename-file R rename/move an attached file
7024 send-message y send the message
7025 toggle-unlink u toggle whether to delete file after sending it
7026 view-attach RET view attachment using mailcap entry if necessary
7027 write-fcc w write the message to a folder
7029 \e[1m6.4.8. postpone
\e[0m
7031 delete-entry d delete the current entry
7032 undelete-entry u undelete the current entry
7034 \e[1m6.4.9. browser
\e[0m
7036 change-dir c change directories
7037 check-new TAB check mailboxes for new mail
7038 enter-mask m enter a file mask
7039 search / search for a regular expression
7040 search-next n search for next match
7041 search-reverse ESC / search backwards for a regular expression
7042 select-new N select a new file in this directory
7043 sort o sort messages
7044 sort-reverse O sort messages in reverse order
7045 toggle-mailboxes TAB toggle whether to browse mailboxes or all files
7046 view-file SPACE view file
7047 subscribe s subscribe to current mailbox (IMAP Only)
7048 unsubscribe u unsubscribe to current mailbox (IMAP Only)
7049 toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
7051 \e[1m6.4.10. pgp
\e[0m
7053 view-name % view the key's user id
7054 verify-key c verify a PGP public key
7056 \e[1m6.4.11. editor
\e[0m
7058 backspace BackSpace delete the char in front of the cursor
7059 backward-char ^B move the cursor one character to the left
7060 backward-word ESC b move the cursor to the previous word
7061 bol ^A jump to the beginning of the line
7062 buffy-cycle Space cycle among incoming mailboxes
7063 capitalize-word ESC c uppercase the first character in the word
7064 complete TAB complete filename or alias
7065 complete-query ^T complete address with query
7066 delete-char ^D delete the char under the cursor
7067 downcase-word ESC l lowercase all characters in current word
7068 eol ^E jump to the end of the line
7069 forward-char ^F move the cursor one character to the right
7070 forward-word ESC f move the cursor to the next word
7071 history-down not bound scroll down through the history list
7072 history-up not bound scroll up through the history list
7073 kill-eol ^K delete chars from cursor to end of line
7074 kill-eow ESC d delete chars from cursor to end of word
7075 kill-line ^U delete all chars on the line
7076 kill-word ^W delete the word in front of the cursor
7077 quote-char ^V quote the next typed key
7078 transpose-chars not bound transpose character under cursor with previous
7079 upcase-word ESC u uppercase all characters in current word
7081 \e[1m7. Miscellany
\e[0m
7083 \e[1m7.1. Acknowledgements
\e[0m
7085 Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME
7086 parsing code back in the ELM-ME days.
7088 The following people have been very helpful to the development of
7091 Vikas Agnihotri <vikasa@writeme.com>,
7092 Francois Berjon <Francois.Berjon@aar.alcatel-alsthom.fr>,
7093 Aric Blumer <aric@fore.com>,
7094 John Capo <jc@irbs.com>,
7095 David Champion <dgc@uchicago.edu,
7096 Brendan Cully <brendan@kublai.com>,
7097 Liviu Daia <daia@stoilow.imar.ro>,
7098 Thomas E. Dickey <dickey@herndon4.his.com>,
7099 David DeSimone <fox@convex.hp.com>,
7100 Nickolay N. Dudorov <nnd@wint.itfs.nsk.su>,
7101 Ruslan Ermilov <ru@freebsd.org>,
7102 Edmund Grimley Evans <edmundo@rano.org,
7103 Michael Finken <finken@conware.de>,
7104 Sven Guckes <guckes@math.fu-berlin.de>,
7105 Lars Hecking <lhecking@nmrc.ie>,
7106 Mark Holloman <holloman@nando.net>,
7107 Andreas Holzmann <holzmann@fmi.uni-passau.de>,
7108 Marco d'Itri <md@linux.it>,
7109 Björn Jacke <bjacke@suse.com>,
7110 Byrial Jensen <byrial@image.dk>,
7111 David Jeske <jeske@igcom.net>,
7112 Christophe Kalt <kalt@hugo.int-evry.fr>,
7113 Tommi Komulainen <Tommi.Komulainen@iki.fi>,
7114 Felix von Leitner (a.k.a ``Fefe'') <leitner@math.fu-berlin.de>,
7115 Brandon Long <blong@fiction.net>,
7116 Jimmy Mäkelä <jmy@flashback.net>,
7117 Lars Marowsky-Bree <lmb@pointer.in-minden.de>,
7118 Thomas ``Mike'' Michlmayr <mike@cosy.sbg.ac.at>,
7119 Andrew W. Nosenko <awn@bcs.zp.ua>,
7120 David O'Brien <obrien@Nuxi.cs.ucdavis.edu>,
7121 Clint Olsen <olsenc@ichips.intel.com>,
7122 Park Myeong Seok <pms@romance.kaist.ac.kr>,
7123 Thomas Parmelan <tom@ankh.fr.eu.org>,
7124 Ollivier Robert <roberto@keltia.freenix.fr>,
7125 Thomas Roessler <roessler@does-not-exist.org>,
7126 Roland Rosenfeld <roland@spinnaker.de>,
7127 TAKIZAWA Takashi <taki@luna.email.ne.jp>,
7128 Allain Thivillon <Allain.Thivillon@alma.fr>,
7129 Gero Treuner <gero@faveve.uni-stuttgart.de>,
7130 Vsevolod Volkov <vvv@lucky.net>,
7131 Ken Weinert <kenw@ihs.com>
7133 \e[1m7.2. About this document
\e[0m
7135 This document was written in SGML, and then rendered using the sgml-