All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
1 # Auto-generated using mkconf from manual.txt
2 # on 2021-09-13 12:06:16
12 # When the body of the message matches $abort_noattach_regexp and there are no
13 # attachments, this quadoption controls whether to abort sending the message.
15 set abort_noattach=ask-yes
18 # 3.2. abort_noattach_regexp
20 # Type: regular expression
23 # Specifies a regular expression to match against the body of the message, to
24 # determine if an attachment was mentioned but mistakenly forgotten. If it
25 # matches, $abort_noattach will be consulted to determine if message sending will
28 # Like other regular expressions in Mutt, the search is case sensitive if the
29 # pattern contains at least one upper case letter, and case insensitive
32 set abort_noattach_regexp='attach|beigefügt|angehängt|an(hang|lage)|screenshot|bildschirmphoto'
33 #'attach(ing|ed|ment)?|included\W+(with|in)\W+th(is|e\W+(curr|pres)ent)\W+mail|an(geh(ä|=E4|=C3=A4)ngt|h(ä|=E4|=C3=A4)ngsel|bei)|bei(gef(ü|=FC|=C3=BC)gt|lage)|(im|siehe)\W+(anhang|beilage)|attach(e|er|(é|=E9|=C3=A9)e?s?|ement|ant)'
36 # 3.3. abort_nosubject
41 # If set to yes, when composing messages and no subject is given at the subject
42 # prompt, composition will be aborted. If set to no, composing messages with no
43 # subject given at the subject prompt will never be aborted.
47 # 3.4. abort_unmodified
52 # If set to yes, composition will automatically abort after editing the message
53 # body if no changes are made to the file (this check only happens after the
54 # first edit of the file). When set to no, composition will never be aborted.
61 # Default: “~/.muttrc”
63 # The default file in which to save aliases created by the <create-alias>
64 # function. Entries added to this file are encoded in the character set specified
65 # by $config_charset if it is set or the current character set otherwise.
67 # Note: Mutt will not automatically source this file; you must explicitly use the
68 # “source” command for it to be executed in case this option points to a
69 # dedicated alias file.
71 # The default for this option is the currently used muttrc file, or “~/.muttrc”
72 # if no user muttrc was found.
74 set alias_file="$my_confdir/aliases"
80 # Default: “%4n %2f %t %-10a %r”
82 # Specifies the format of the data displayed for the “alias” menu. The following
83 # printf(3)-style sequences are available:
85 # ┌──┬──────────────────────────────────────────────────────────────┐
87 # ├──┼──────────────────────────────────────────────────────────────┤
88 # │%f│flags - currently, a “d” for an alias marked for deletion │
89 # ├──┼──────────────────────────────────────────────────────────────┤
91 # ├──┼──────────────────────────────────────────────────────────────┤
92 # │%r│address which alias expands to │
93 # ├──┼──────────────────────────────────────────────────────────────┤
94 # │%t│character which indicates if the alias is tagged for inclusion│
95 # └──┴──────────────────────────────────────────────────────────────┘
104 # Controls whether 8-bit data is converted to 7-bit using either Quoted-
105 # Printable or Base64 encoding when sending mail.
114 # Controls whether ANSI color codes in messages (and color tags in rich text
115 # messages) are to be interpreted. Messages containing these codes are rare, but
116 # if this option is set, their text will be colored accordingly. Note that this
117 # may override your color choices, and even present a security problem, since a
118 # message could include a line like
120 # [-- PGP output follows ...
122 # and give it the same color as your attachment color (see also $crypt_timestamp
132 # When set, an arrow (“->”) will be used to indicate the current entry in menus
133 # instead of highlighting the whole line. On slow network or modem links this
134 # will make response faster because there is less that has to be redrawn on the
135 # screen when moving to the next or previous entries in the menu.
144 # If set, Mutt will use plain ASCII characters when displaying thread and
145 # attachment trees, instead of the default ACS characters.
154 # If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before
155 # editing an outgoing message.
164 # If set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the
165 # body of an outgoing message.
169 # 3.13. assumed_charset
174 # This variable is a colon-separated list of character encoding schemes for
175 # messages without character encoding indication. Header field values and message
176 # body content without character encoding indication would be assumed that they
177 # are written in one of this list. By default, all the header fields and message
178 # body without any charset indication are assumed to be in “us-ascii”.
180 # For example, Japanese users might prefer this:
182 # set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
184 # However, only the first content is valid for the message body.
188 # 3.14. attach_charset
193 # This variable is a colon-separated list of character encoding schemes for text
194 # file attachments. Mutt uses this setting to guess which encoding files being
195 # attached are encoded in to convert them to a proper character set given in
198 # If unset, the value of $charset will be used instead. For example, the
199 # following configuration would work for Japanese text handling:
201 # set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
203 # Note: for Japanese users, “iso-2022-*” must be put at the head of the value as
204 # shown above if included.
208 # 3.15. attach_format
211 # Default: “%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] ”
213 # This variable describes the format of the “attachment” menu. The following
214 # printf(3)-style sequences are understood:
216 # ┌───┬─────────────────────────────────────────────────────────────────────────┐
218 # ├───┼─────────────────────────────────────────────────────────────────────────┤
219 # │%c │requires charset conversion (“n” or “c”) │
220 # ├───┼─────────────────────────────────────────────────────────────────────────┤
221 # │%D │deleted flag │
222 # ├───┼─────────────────────────────────────────────────────────────────────────┤
223 # │%d │description (if none, falls back to %F) │
224 # ├───┼─────────────────────────────────────────────────────────────────────────┤
225 # │%e │MIME content-transfer-encoding │
226 # ├───┼─────────────────────────────────────────────────────────────────────────┤
227 # │%F │filename in content-disposition header (if none, falls back to %f) │
228 # ├───┼─────────────────────────────────────────────────────────────────────────┤
230 # ├───┼─────────────────────────────────────────────────────────────────────────┤
231 # │%I │disposition (“I” for inline, “A” for attachment) │
232 # ├───┼─────────────────────────────────────────────────────────────────────────┤
233 # │%m │major MIME type │
234 # ├───┼─────────────────────────────────────────────────────────────────────────┤
235 # │%M │MIME subtype │
236 # ├───┼─────────────────────────────────────────────────────────────────────────┤
237 # │%n │attachment number │
238 # ├───┼─────────────────────────────────────────────────────────────────────────┤
239 # │%Q │“Q”, if MIME part qualifies for attachment counting │
240 # ├───┼─────────────────────────────────────────────────────────────────────────┤
241 # │%s │size (see formatstrings-size) │
242 # ├───┼─────────────────────────────────────────────────────────────────────────┤
244 # ├───┼─────────────────────────────────────────────────────────────────────────┤
245 # │%T │graphic tree characters │
246 # ├───┼─────────────────────────────────────────────────────────────────────────┤
247 # │%u │unlink (=to delete) flag │
248 # ├───┼─────────────────────────────────────────────────────────────────────────┤
249 # │%X │number of qualifying MIME parts in this part and its children (please see│
250 # │ │the “attachments” section for possible speed effects) │
251 # ├───┼─────────────────────────────────────────────────────────────────────────┤
252 # │%>X│right justify the rest of the string and pad with character “X” │
253 # ├───┼─────────────────────────────────────────────────────────────────────────┤
254 # │%|X│pad to the end of the line with character “X” │
255 # ├───┼─────────────────────────────────────────────────────────────────────────┤
256 # │%*X│soft-fill with character “X” as pad │
257 # └───┴─────────────────────────────────────────────────────────────────────────┘
259 # For an explanation of “soft-fill”, see the $index_format documentation.
263 # 3.16. attach_save_dir
268 # The default directory to save attachments from the “attachment” menu. If it
269 # doesn't exist, Mutt will prompt to create the directory before saving.
271 # If the path is invalid (e.g. not a directory, or cannot be chdir'ed to), Mutt
272 # will fall back to using the current directory.
274 set attach_save_dir=$tmpdir
282 # The separator to add between attachments when operating (saving, printing,
283 # piping, etc) on a list of tagged attachments.
292 # If this variable is unset, when operating (saving, printing, piping, etc) on a
293 # list of tagged attachments, Mutt will concatenate the attachments and will
294 # operate on them as a single attachment. The $attach_sep separator is added
295 # after each attachment. When set, Mutt will operate on the attachments one by
302 # Type: string (localized)
303 # Default: “On %d, %n wrote:”
305 # This is the string that will precede a message which has been included in a
306 # reply. For a full listing of defined printf(3)-like sequences see the section
309 set attribution="$my_attribution_en"
312 # 3.20. attribution_locale
317 # The locale used by strftime(3) to format dates in the attribution string. Legal
318 # values are the strings your system accepts for the locale environment variable
321 # This variable is to allow the attribution date format to be customized by
322 # recipient or folder using hooks. By default, Mutt will use your locale
323 # environment, so there is no need to set this except to override that default.
327 # 3.21. auto_subscribe
332 # When set, Mutt assumes the presence of a List-Post header means the recipient
333 # is subscribed to the list. Unless the mailing list is in the “unsubscribe” or “
334 # unlist” lists, it will be added to the “subscribe” list. Parsing and checking
335 # these things slows header reading down, so this option is disabled by default.
344 # When set, functions in the index menu which affect a message will be applied to
345 # all tagged messages (if there are any). When unset, you must first use the
346 # <tag-prefix> function (bound to “;” by default) to make the next function apply
347 # to all tagged messages.
356 # When set, enables autocrypt, which provides passive encryption protection with
357 # keys exchanged via headers. See “autocryptdoc” for more details. (Autocrypt
362 # 3.24. autocrypt_acct_format
365 # Default: “%4n %-30a %20p %10s”
367 # This variable describes the format of the “autocrypt account” menu. The
368 # following printf(3)-style sequences are understood
370 # ┌──┬─────────────────────────────┐
371 # │%a│email address │
372 # ├──┼─────────────────────────────┤
374 # ├──┼─────────────────────────────┤
375 # │%n│current entry number │
376 # ├──┼─────────────────────────────┤
377 # │%p│prefer-encrypt flag │
378 # ├──┼─────────────────────────────┤
379 # │%s│status flag (active/inactive)│
380 # └──┴─────────────────────────────┘
386 # 3.25. autocrypt_dir
389 # Default: “~/.mutt/autocrypt”
391 # This variable sets where autocrypt files are stored, including the GPG keyring
392 # and sqlite database. See “autocryptdoc” for more details. (Autocrypt only)
396 # 3.26. autocrypt_reply
401 # When set, replying to an autocrypt email automatically enables autocrypt in the
402 # reply. You may want to unset this if you're using the same key for autocrypt as
403 # normal web-of-trust, so that autocrypt isn't forced on for all encrypted
404 # replies. (Autocrypt only)
413 # When set along with $edit_headers, Mutt will skip the initial send-menu
414 # (prompting for subject and recipients) and allow you to immediately begin
415 # editing the body of your message. The send-menu may still be accessed once you
416 # have finished editing the body of your message.
418 # Note: when this option is set, you cannot use send-hooks that depend on the
419 # recipients when composing a new (non-reply) message, as the initial list of
420 # recipients is empty.
422 # Also see $fast_reply.
427 # 3.28. background_edit
432 # When set, Mutt will run $editor in the background during message composition. A
433 # landing page will display, waiting for the $editor to exit. The landing page
434 # may be exited, allowing perusal of the mailbox, or even for other messages to
435 # be composed. Backgrounded sessions may be returned to via the
436 # <background-compose-menu> function.
438 # For background editing to work properly, $editor must be set to an editor that
439 # does not try to use the Mutt terminal: for example a graphical editor, or a
440 # script launching (and waiting for) the editor in another Gnu Screen window.
442 # For more details, see “bgedit” ("Background Editing" in the manual).
446 # 3.29. background_confirm_quit
451 # When set, if there are any background edit sessions, you will be prompted to
452 # confirm exiting Mutt, in addition to the $quit prompt.
456 # 3.30. background_format
459 # Default: “%10S %7p %s”
461 # This variable describes the format of the “background compose” menu. The
462 # following printf(3)-style sequences are understood:
464 # ┌──┬──────────────────────────────────────────────────────┐
465 # │%i│parent message id (for replies and forwarded messages)│
466 # ├──┼──────────────────────────────────────────────────────┤
467 # │%n│the running number on the menu │
468 # ├──┼──────────────────────────────────────────────────────┤
469 # │%p│pid of the $editor process │
470 # ├──┼──────────────────────────────────────────────────────┤
471 # │%r│comma separated list of “To:” recipients │
472 # ├──┼──────────────────────────────────────────────────────┤
473 # │%R│comma separated list of “Cc:” recipients │
474 # ├──┼──────────────────────────────────────────────────────┤
475 # │%s│subject of the message │
476 # ├──┼──────────────────────────────────────────────────────┤
477 # │%S│status of the $editor process: running/finished │
478 # └──┴──────────────────────────────────────────────────────┘
487 # When this variable is set, mutt will beep when an error occurs.
497 # When this variable is set, mutt will beep whenever it prints a message
498 # notifying you of new mail. This is independent of the setting of the $beep
508 # Controls whether you will be asked to confirm bouncing messages. If set to yes
509 # you don't get asked if you want to bounce a message. Setting this variable to
510 # no is not generally useful, and thus not recommended, because you are unable to
515 # 3.34. bounce_delivered
520 # When this variable is set, mutt will include Delivered-To headers when bouncing
521 # messages. Postfix users may wish to unset this variable.
523 set bounce_delivered=no
526 # 3.35. braille_friendly
531 # When this variable is set, mutt will place the cursor at the beginning of the
532 # current line in menus, even when the $arrow_cursor variable is unset, making it
533 # easier for blind persons using Braille displays to follow these menus. The
534 # option is unset by default because many visual terminals don't permit making
535 # the cursor invisible.
539 # 3.36. browser_abbreviate_mailboxes
544 # When this variable is set, mutt will abbreviate mailbox names in the browser
545 # mailbox list, using '~' and '=' shortcuts.
547 # The default "alpha" setting of $sort_browser uses locale-based sorting (using
548 # strcoll(3)), which ignores some punctuation. This can lead to some situations
549 # where the order doesn't make intuitive sense. In those cases, it may be
550 # desirable to unset this variable.
554 # 3.37. browser_sticky_cursor
559 # When this variable is set, the browser will attempt to keep the cursor on the
560 # same mailbox when performing various functions. These include moving up a
561 # directory, toggling between mailboxes and directory listing, creating/renaming
562 # a mailbox, toggling subscribed mailboxes, and entering a new mask.
566 # 3.38. certificate_file
569 # Default: “~/.mutt_certificates”
571 # This variable specifies the file where the certificates you trust are saved.
572 # When an unknown certificate is encountered, you are asked if you accept it or
573 # not. If you accept it, the certificate can also be saved in this file and
574 # further connections are automatically accepted.
576 # You can also manually add CA certificates in this file. Any server certificate
577 # that is signed with one of these CA certificates is also automatically
582 # set certificate_file=~/.mutt/certificates
586 # 3.39. change_folder_next
591 # When this variable is set, the <change-folder> function mailbox suggestion will
592 # start at the next folder in your “mailboxes” list, instead of starting at the
593 # first folder in the list.
602 # Character set your terminal uses to display and enter textual data. It is also
603 # the fallback for $send_charset.
605 # Upon startup Mutt tries to derive this value from environment variables such as
606 # $LC_CTYPE or $LANG.
608 # Note: It should only be set in case Mutt isn't able to determine the character
609 # set used correctly.
613 # 3.41. check_mbox_size
618 # When this variable is set, mutt will use file size attribute instead of access
619 # time when checking for new mail in mbox and mmdf folders.
621 # This variable is unset by default and should only be enabled when new mail
622 # detection for these folder types is unreliable or doesn't work.
624 # Note that enabling this variable should happen before any “mailboxes”
625 # directives occur in configuration files regarding mbox or mmdf folders because
626 # mutt needs to determine the initial new mail status of such a mailbox by
627 # performing a fast mailbox scan when it is defined. Afterwards the new mail
628 # status is tracked by file size changes.
637 # Note: this option only affects maildir and MH style mailboxes.
639 # When set, Mutt will check for new mail delivered while the mailbox is open.
640 # Especially with MH mailboxes, this operation can take quite some time since it
641 # involves scanning the directory and checking each file to see if it has already
642 # been looked at. If this variable is unset, no check for new mail is performed
643 # while the mailbox is open.
647 # 3.43. collapse_unread
652 # When unset, Mutt will not collapse a thread if it contains any unread messages.
656 # 3.44. compose_format
658 # Type: string (localized)
659 # Default: “-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-”
661 # Controls the format of the status line displayed in the “compose” menu. This
662 # string is similar to $status_format, but has its own set of printf(3)-like
665 # ┌──┬──────────────────────────────────────────────────────────────────────────┐
666 # │%a│total number of attachments │
667 # ├──┼──────────────────────────────────────────────────────────────────────────┤
668 # │%h│local hostname │
669 # ├──┼──────────────────────────────────────────────────────────────────────────┤
670 # │%l│approximate size (in bytes) of the current message (see formatstrings-size│
672 # ├──┼──────────────────────────────────────────────────────────────────────────┤
673 # │%v│Mutt version string │
674 # └──┴──────────────────────────────────────────────────────────────────────────┘
676 # See the text describing the $status_format option for more information on how
677 # to set $compose_format.
681 # 3.45. config_charset
686 # When defined, Mutt will recode commands in rc files from this encoding to the
687 # current character set as specified by $charset and aliases written to
688 # $alias_file from the current character set.
690 # Please note that if setting $charset it must be done before setting
693 # Recoding should be avoided as it may render unconvertable characters as
694 # question marks which can lead to undesired side effects (for example in regular
699 # 3.46. confirmappend
704 # When set, Mutt will prompt for confirmation when appending messages to an
710 # 3.47. confirmcreate
715 # When set, Mutt will prompt for confirmation when saving messages to a mailbox
716 # which does not yet exist before creating it.
720 # 3.48. connect_timeout
725 # Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
726 # many seconds if the connection is not able to be established. A negative value
727 # causes Mutt to wait indefinitely for the connection attempt to succeed.
734 # Default: “text/plain”
736 # Sets the default Content-Type for the body of newly composed messages.
738 set content_type="text/plain; markup=markdown"
746 # This variable controls whether or not copies of your outgoing messages will be
747 # saved for later references. Also see $record, $save_name, $force_name and “
753 # 3.51. copy_decode_weed
758 # Controls whether Mutt will weed headers when invoking the <decode-copy> or
759 # <decode-save> functions.
763 # 3.52. count_alternatives
768 # When set, Mutt will recurse inside multipart/alternatives while performing
769 # attachment searching and counting (see attachments).
771 # Traditionally, multipart/alternative parts have simply represented different
772 # encodings of the main content of the email. Unfortunately, some mail clients
773 # have started to place email attachments inside one of alternatives. Setting
774 # this will allow Mutt to find and count matching attachments hidden there, and
775 # include them in the index via %X or through ~X pattern matching.
779 # 3.53. cursor_overlay
784 # When set, Mutt will overlay the indicator, tree, sidebar_highlight, and
785 # sidebar_indicator colors onto the currently selected line. This will allow
786 # default colors in those to be overridden, and for attributes to be merged
787 # between the layers.
791 # 3.54. crypt_autoencrypt
796 # Setting this variable will cause Mutt to always attempt to PGP encrypt outgoing
797 # messages. This is probably only useful in connection to the “send-hook”
798 # command. It can be overridden by use of the pgp menu, when encryption is not
799 # required or signing is requested as well. If $smime_is_default is set, then
800 # OpenSSL is used instead to create S/MIME messages and settings can be
801 # overridden by use of the smime menu instead. (Crypto only)
805 # 3.55. crypt_autopgp
810 # This variable controls whether or not mutt may automatically enable PGP
811 # encryption/signing for messages. See also $crypt_autoencrypt,
812 # $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and $smime_is_default.
816 # 3.56. crypt_autosign
821 # Setting this variable will cause Mutt to always attempt to cryptographically
822 # sign outgoing messages. This can be overridden by use of the pgp menu, when
823 # signing is not required or encryption is requested as well. If
824 # $smime_is_default is set, then OpenSSL is used instead to create S/MIME
825 # messages and settings can be overridden by use of the smime menu instead of the
826 # pgp menu. (Crypto only)
828 set crypt_autosign=no
831 # 3.57. crypt_autosmime
836 # This variable controls whether or not mutt may automatically enable S/MIME
837 # encryption/signing for messages. See also $crypt_autoencrypt,
838 # $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and $smime_is_default.
840 set crypt_autosmime=no
843 # 3.58. crypt_confirmhook
848 # If set, then you will be prompted for confirmation of keys when using the
849 # crypt-hook command. If unset, no such confirmation prompt will be presented.
850 # This is generally considered unsafe, especially where typos are concerned.
854 # 3.59. crypt_opportunistic_encrypt
859 # Setting this variable will cause Mutt to automatically enable and disable
860 # encryption, based on whether all message recipient keys can be located by Mutt.
862 # When this option is enabled, Mutt will enable/disable encryption each time the
863 # TO, CC, and BCC lists are edited. If $edit_headers is set, Mutt will also do so
864 # each time the message is edited.
866 # While this is set, encryption can't be manually enabled/disabled. The pgp or
867 # smime menus provide a selection to temporarily disable this option for the
870 # If $crypt_autoencrypt or $crypt_replyencrypt enable encryption for a message,
871 # this option will be disabled for that message. It can be manually re-enabled in
872 # the pgp or smime menus. (Crypto only)
874 set crypt_opportunistic_encrypt=no
877 # 3.60. crypt_opportunistic_encrypt_strong_keys
882 # When set, this modifies the behavior of $crypt_opportunistic_encrypt to only
883 # search for "strong keys", that is, keys with full validity according to the
884 # web-of-trust algorithm. A key with marginal or no validity will not enable
885 # opportunistic encryption.
887 # For S/MIME, the behavior depends on the backend. Classic S/MIME will filter for
888 # certificates with the 't' (trusted) flag in the .index file. The GPGME backend
889 # will use the same filters as with OpenPGP, and depends on GPGME's logic for
890 # assigning the GPGME_VALIDITY_FULL and GPGME_VALIDITY_ULTIMATE validity flag.
894 # 3.61. crypt_protected_headers_read
899 # When set, Mutt will display protected headers in the pager, and will update the
900 # index and header cache with revised headers. Protected headers are stored
901 # inside the encrypted or signed part of an an email, to prevent disclosure or
902 # tampering. For more information see https://github.com/autocrypt/
903 # protected-headers. Currently Mutt only supports the Subject header.
905 # Encrypted messages using protected headers often substitute the exposed Subject
906 # header with a dummy value (see $crypt_protected_headers_subject). Mutt will
907 # update its concept of the correct subject after the message is opened, i.e. via
908 # the <display-message> function. If you reply to a message before opening it,
909 # Mutt will end up using the dummy Subject header, so be sure to open such a
910 # message first. (Crypto only)
914 # 3.62. crypt_protected_headers_save
919 # When $crypt_protected_headers_read is set, and a message with a protected
920 # Subject is opened, Mutt will save the updated Subject into the header cache by
921 # default. This allows searching/limiting based on the protected Subject header
922 # if the mailbox is re-opened, without having to re-open the message each time.
923 # However, for mbox/mh mailbox types, or if header caching is not set up, you
924 # would need to re-open the message each time the mailbox was reopened before you
925 # could see or search/limit on the protected subject again.
927 # When this variable is set, Mutt additionally saves the protected Subject back
928 # in the clear-text message headers. This provides better usability, but with the
929 # tradeoff of reduced security. The protected Subject header, which may have
930 # previously been encrypted, is now stored in clear-text in the message headers.
931 # Copying the message elsewhere, via Mutt or external tools, could expose this
932 # previously encrypted data. Please make sure you understand the consequences of
933 # this before you enable this variable. (Crypto only)
937 # 3.63. crypt_protected_headers_subject
942 # When $crypt_protected_headers_write is set, and the message is marked for
943 # encryption, this will be substituted into the Subject field in the message
944 # headers. To prevent a subject from being substituted, unset this variable, or
945 # set it to the empty string. (Crypto only)
949 # 3.64. crypt_protected_headers_write
954 # When set, Mutt will generate protected headers for signed and encrypted emails.
955 # Protected headers are stored inside the encrypted or signed part of an an
956 # email, to prevent disclosure or tampering. For more information see https://
957 # github.com/autocrypt/protected-headers. Currently Mutt only supports the
958 # Subject header. (Crypto only)
962 # 3.65. crypt_replyencrypt
967 # If set, automatically PGP or OpenSSL encrypt replies to messages which are
968 # encrypted. (Crypto only)
972 # 3.66. crypt_replysign
977 # If set, automatically PGP or OpenSSL sign replies to messages which are signed.
979 # Note: this does not work on messages that are encrypted and signed! (Crypto
982 set crypt_replysign=yes
985 # 3.67. crypt_replysignencrypted
990 # If set, automatically PGP or OpenSSL sign replies to messages which are
991 # encrypted. This makes sense in combination with $crypt_replyencrypt, because it
992 # allows you to sign all messages which are automatically encrypted. This works
993 # around the problem noted in $crypt_replysign, that mutt is not able to find out
994 # whether an encrypted message is also signed. (Crypto only)
996 set crypt_replysignencrypted=yes
999 # 3.68. crypt_timestamp
1004 # If set, mutt will include a time stamp in the lines surrounding PGP or S/MIME
1005 # output, so spoofing such lines is more difficult. If you are using colors to
1006 # mark these lines, and rely on these, you may unset this setting. (Crypto only)
1010 # 3.69. crypt_use_gpgme
1015 # This variable controls the use of the GPGME-enabled crypto backends. If it is
1016 # set and Mutt was built with gpgme support, the gpgme code for S/MIME and PGP
1017 # will be used instead of the classic code. Note that you need to set this option
1018 # in .muttrc; it won't have any effect when used interactively.
1020 # Note that the GPGME backend does not support creating old-style inline
1021 # (traditional) PGP encrypted or signed messages (see $pgp_autoinline).
1025 # 3.70. crypt_use_pka
1030 # Controls whether mutt uses PKA (see http://www.g10code.de/docs/
1031 # pka-intro.de.pdf) during signature verification (only supported by the GPGME
1034 set crypt_use_pka=yes
1037 # 3.71. crypt_verify_sig
1042 # If “yes”, always attempt to verify PGP or S/MIME signatures. If “ask-*”, ask
1043 # whether or not to verify the signature. If “no”, never attempt to verify
1044 # cryptographic signatures. (Crypto only)
1051 # Default: “!%a, %b %d, %Y at %I:%M:%S%p %Z”
1053 # This variable controls the format of the date printed by the “%d” sequence in
1054 # $index_format. This is passed to the strftime(3) function to process the date,
1055 # see the man page for the proper syntax.
1057 # Unless the first character in the string is a bang (“!”), the month and week
1058 # day names are expanded according to the locale. If the first character in the
1059 # string is a bang, the bang is discarded, and the month and week day names in
1060 # the rest of the string are expanded in the C locale (that is in US English).
1062 set date_format="%F"
1065 # 3.73. default_hook
1068 # Default: “~f %s !~P | (~P ~C %s)”
1070 # This variable controls how “message-hook”, “reply-hook”, “send-hook”, “
1071 # send2-hook”, “save-hook”, and “fcc-hook” will be interpreted if they are
1072 # specified with only a simple regexp, instead of a matching pattern. The hooks
1073 # are expanded when they are declared, so a hook will be interpreted according to
1074 # the value of this variable at the time the hook is declared.
1076 # The default value matches if the message is either from a user matching the
1077 # regular expression given, or if it is from you (if the from address matches “
1078 # alternates”) and is to or cc'ed to a user matching the given regular
1088 # Controls whether or not messages are really deleted when closing or
1089 # synchronizing a mailbox. If set to yes, messages marked for deleting will
1090 # automatically be purged without prompting. If set to no, messages marked for
1091 # deletion will be kept in the mailbox.
1096 # 3.75. delete_untag
1101 # If this option is set, mutt will untag messages when marking them for deletion.
1102 # This applies when you either explicitly delete a message, or when you save it
1103 # to another folder.
1107 # 3.76. digest_collapse
1112 # If this option is set, mutt's received-attachments menu will not show the
1113 # subparts of individual messages in a multipart/digest. To see these subparts,
1114 # press “v” on that menu.
1118 # 3.77. display_filter
1123 # When set, specifies a command used to filter messages. When a message is viewed
1124 # it is passed as standard input to $display_filter, and the filtered message is
1125 # read from the standard output.
1129 # 3.78. dotlock_program
1132 # Default: “/usr/bin/mutt_dotlock”
1134 # Contains the path of the mutt_dotlock(1) binary to be used by mutt.
1143 # This variable sets the request for when notification is returned. The string
1144 # consists of a comma separated list (no spaces!) of one or more of the
1145 # following: never, to never request notification, failure, to request
1146 # notification on transmission failure, delay, to be notified of message delays,
1147 # success, to be notified of successful transmission.
1151 # set dsn_notify="failure,delay"
1153 # Note: when using $sendmail for delivery, you should not enable this unless you
1154 # are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)
1155 # -compatible interface supporting the -N option for DSN. For SMTP delivery, DSN
1156 # support is auto-detected so that it depends on the server whether DSN will be
1166 # This variable controls how much of your message is returned in DSN messages. It
1167 # may be set to either hdrs to return just the message header, or full to return
1172 # set dsn_return=hdrs
1174 # Note: when using $sendmail for delivery, you should not enable this unless you
1175 # are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)
1176 # -compatible interface supporting the -R option for DSN. For SMTP delivery, DSN
1177 # support is auto-detected so that it depends on the server whether DSN will be
1182 # 3.81. duplicate_threads
1187 # This variable controls whether mutt, when $sort is set to threads, threads
1188 # messages with the same Message-Id together. If it is set, it will indicate that
1189 # it thinks they are duplicates of each other with an equals sign in the thread
1194 # 3.82. edit_headers
1199 # This option allows you to edit the header of your outgoing messages along with
1200 # the body of your message.
1202 # Although the compose menu may have localized header labels, the labels passed
1203 # to your editor will be standard RFC 2822 headers, (e.g. To:, Cc:, Subject:).
1204 # Headers added in your editor must also be RFC 2822 headers, or one of the
1205 # pseudo headers listed in “edit-header”. Mutt will not understand localized
1206 # header labels, just as it would not when parsing an actual email.
1208 # Note that changes made to the References: and Date: headers are ignored for
1209 # interoperability reasons.
1211 set edit_headers=yes
1219 # This variable specifies which editor is used by mutt. It defaults to the value
1220 # of the $VISUAL, or $EDITOR, environment variable, or to the string “vi” if
1221 # neither of those are set.
1223 # The $editor string may contain a %s escape, which will be replaced by the name
1224 # of the file to be edited. If the %s escape does not appear in $editor, a space
1225 # and the name to be edited are appended.
1227 # The resulting string is then executed by running
1231 # where string is the expansion of $editor described above.
1233 set editor="mailplate --edit --auto --keep-unknown"
1241 # When set, mutt will quoted-printable encode messages when they contain the
1242 # string “From ” (note the trailing space) in the beginning of a line. This is
1243 # useful to avoid the tampering certain mail delivery and transport agents tend
1244 # to do with messages (in order to prevent tools from misinterpreting the line as
1245 # a mbox message separator).
1249 # 3.85. entropy_file
1254 # The file which includes random data that is used to initialize SSL library
1259 # 3.86. envelope_from_address
1261 # Type: e-mail address
1264 # Manually sets the envelope sender for outgoing messages. This value is ignored
1265 # if $use_envelope_from is unset.
1269 # 3.87. error_history
1274 # This variable controls the size (in number of strings remembered) of the error
1275 # messages displayed by mutt. These can be shown with the <error-history>
1276 # function. The history is cleared each time this variable is set.
1285 # Escape character to use for functions in the built-in editor.
1294 # When set, the initial prompt for recipients and subject are skipped when
1295 # replying to messages, and the initial prompt for subject is skipped when
1296 # forwarding messages.
1298 # Note: this variable has no effect when the $autoedit variable is set.
1307 # This variable controls whether or not attachments on outgoing messages are
1308 # saved along with the main body of your message.
1313 # 3.91. fcc_before_send
1318 # When this variable is set, FCCs will occur before sending the message. Before
1319 # sending, the message cannot be manipulated, so it will be stored the exact same
1320 # as sent: $fcc_attach and $fcc_clear will be ignored (using their default
1323 # When unset, the default, FCCs will occur after sending. Variables $fcc_attach
1324 # and $fcc_clear will be respected, allowing it to be stored without attachments
1325 # or encryption/signing if desired.
1334 # When this variable is set, FCCs will be stored unencrypted and unsigned, even
1335 # when the actual message is encrypted and/or signed. (PGP only)
1339 # 3.93. fcc_delimiter
1344 # When specified, this allows the ability to Fcc to more than one mailbox. The
1345 # fcc value will be split by this delimiter and Mutt will evaluate each part as a
1346 # mailbox separately.
1348 # See $record, “fcc-hook”, and “fcc-save-hook”.
1357 # If set, flagged messages cannot be deleted.
1366 # Specifies the default location of your mailboxes. A “+” or “=” at the beginning
1367 # of a pathname will be expanded to the value of this variable. Note that if you
1368 # change this variable (from the default) value you need to make sure that the
1369 # assignment occurs before you use “+” or “=” for any other variables since
1370 # expansion takes place when handling the “mailboxes” command.
1375 # 3.96. folder_format
1378 # Default: “%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f”
1380 # This variable allows you to customize the file browser display to your personal
1381 # taste. This string is similar to $index_format, but has its own set of printf
1382 # (3)-like sequences:
1384 # ┌───┬─────────────────────────────────────────────────────────────────────────┐
1385 # │%C │current file number │
1386 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1387 # │%d │date/time folder was last modified │
1388 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1389 # │%D │date/time folder was last modified using $date_format. │
1390 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1391 # │%f │filename (“/” is appended to directory names, “@” to symbolic links and “│
1392 # │ │*” to executable files) │
1393 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1394 # │%F │file permissions │
1395 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1396 # │%g │group name (or numeric gid, if missing) │
1397 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1398 # │%l │number of hard links │
1399 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1400 # │%m │number of messages in the mailbox * │
1401 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1402 # │%n │number of unread messages in the mailbox * │
1403 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1404 # │%N │N if mailbox has new mail, blank otherwise │
1405 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1406 # │%s │size in bytes (see formatstrings-size) │
1407 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1408 # │%t │“*” if the file is tagged, blank otherwise │
1409 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1410 # │%u │owner name (or numeric uid, if missing) │
1411 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1412 # │%>X│right justify the rest of the string and pad with character “X” │
1413 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1414 # │%|X│pad to the end of the line with character “X” │
1415 # ├───┼─────────────────────────────────────────────────────────────────────────┤
1416 # │%*X│soft-fill with character “X” as pad │
1417 # └───┴─────────────────────────────────────────────────────────────────────────┘
1419 # For an explanation of “soft-fill”, see the $index_format documentation.
1421 # * = can be optionally printed if nonzero
1423 # %m, %n, and %N only work for monitored mailboxes. %m requires $mail_check_stats
1424 # to be set. %n requires $mail_check_stats to be set (except for IMAP mailboxes).
1426 set folder_format='%t%N%2C %D %4s %f'
1434 # Controls whether or not the “Mail-Followup-To:” header field is generated when
1435 # sending mail. When set, Mutt will generate this field when you are replying to
1436 # a known mailing list, specified with the “subscribe” or “lists” commands.
1438 # This field has two purposes. First, preventing you from receiving duplicate
1439 # copies of replies to messages which you send to mailing lists, and second,
1440 # ensuring that you do get a reply separately for any messages sent to known
1441 # lists to which you are not subscribed.
1443 # The header will contain only the list's address for subscribed lists, and both
1444 # the list address and your own email address for unsubscribed lists. Without
1445 # this header, a group reply to your message sent to a subscribed list will be
1446 # sent to both the list and your address, resulting in two copies of the same
1456 # This variable is similar to $save_name, except that Mutt will store a copy of
1457 # your outgoing message by the username of the address you are sending to even if
1458 # that mailbox does not exist.
1460 # Also see the $record variable.
1464 # 3.99. forward_attachments
1469 # When forwarding inline (i.e. $mime_forward unset or answered with “no” and
1470 # $forward_decode set), attachments which cannot be decoded in a reasonable
1471 # manner will be attached to the newly composed message if this quadoption is set
1472 # or answered with “yes”.
1476 # 3.100. forward_attribution_intro
1478 # Type: string (localized)
1479 # Default: “----- Forwarded message from %f -----”
1481 # This is the string that will precede a message which has been forwarded in the
1482 # main body of a message (when $mime_forward is unset). For a full listing of
1483 # defined printf(3)-like sequences see the section on $index_format. See also
1484 # $attribution_locale.
1488 # 3.101. forward_attribution_trailer
1490 # Type: string (localized)
1491 # Default: “----- End forwarded message -----”
1493 # This is the string that will follow a message which has been forwarded in the
1494 # main body of a message (when $mime_forward is unset). For a full listing of
1495 # defined printf(3)-like sequences see the section on $index_format. See also
1496 # $attribution_locale.
1500 # 3.102. forward_decode
1505 # Controls the decoding of complex MIME messages into text/plain when forwarding
1506 # a message. The message header is also RFC2047 decoded. This variable is only
1507 # used, if $mime_forward is unset, otherwise $mime_forward_decode is used
1512 # 3.103. forward_decrypt
1517 # Controls the handling of encrypted messages when forwarding a message. When set
1518 # , the outer layer of encryption is stripped off. This variable is only used if
1519 # $mime_forward is set and $mime_forward_decode is unset. (PGP only)
1523 # 3.104. forward_edit
1528 # This quadoption controls whether or not the user is automatically placed in the
1529 # editor when forwarding messages. For those who always want to forward with no
1530 # modification, use a setting of “no”.
1534 # 3.105. forward_format
1537 # Default: “[%a: %s]”
1539 # This variable controls the default subject when forwarding a message. It uses
1540 # the same format sequences as the $index_format variable.
1542 set forward_format="(fwd) %s"
1545 # 3.106. forward_quote
1550 # When set, forwarded messages included in the main body of the message (when
1551 # $mime_forward is unset) will be quoted using $indent_string.
1557 # Type: e-mail address
1560 # When set, this variable contains a default from address. It can be overridden
1561 # using “my_hdr” (including from a “send-hook”) and $reverse_name. This variable
1562 # is ignored if $use_from is unset.
1564 # This setting defaults to the contents of the environment variable $EMAIL.
1566 set from='martin f krafft <madduck@madduck.net>'
1571 # Type: regular expression
1574 # A regular expression used by mutt to parse the GECOS field of a password entry
1575 # when expanding the alias. The default value will return the string up to the
1576 # first “,” encountered. If the GECOS field contains a string like “lastname,
1577 # firstname” then you should set it to “.*”.
1579 # This can be useful if you see the following behavior: you address an e-mail to
1580 # user ID “stevef” whose full name is “Steve Franklin”. If mutt expands “stevef”
1581 # to “"Franklin" stevef@foo.bar” then you should set the $gecos_mask to a regular
1582 # expression that will match the whole name so mutt will expand “Franklin” to “
1592 # When unset, the header fields normally added by the “my_hdr” command are not
1593 # created. This variable must be unset before composing a new message or replying
1594 # in order to take effect. If set, the user defined header fields are added to
1595 # every new message.
1604 # When set, this variable causes Mutt to include the header of the message you
1605 # are replying to into the edit buffer. The $weed setting applies.
1609 # 3.111. header_cache
1614 # This variable points to the header cache database. If pointing to a directory
1615 # Mutt will contain a header cache database file per folder, if pointing to a
1616 # file that file will be a single global header cache. By default it is unset so
1617 # no header caching will be used.
1619 # Header caching can greatly improve speed when opening POP, IMAP MH or Maildir
1620 # folders, see “caching” for details.
1622 set header_cache="~/.var/mutt/header_cache"
1625 # 3.112. header_cache_compress
1630 # When mutt is compiled with qdbm, tokyocabinet, or kyotocabinet as header cache
1631 # backend, this option determines whether the database will be compressed.
1632 # Compression results in database files roughly being one fifth of the usual
1633 # diskspace, but the decompression can result in a slower opening of cached
1634 # folder(s) which in general is still much faster than opening non header cached
1637 set header_cache_compress=no
1640 # 3.113. header_cache_pagesize
1642 # Type: number (long)
1645 # When mutt is compiled with either gdbm or bdb4 as the header cache backend,
1646 # this option changes the database page size. Too large or too small values can
1647 # waste space, memory, or CPU time. The default should be more or less optimal
1648 # for most use cases.
1652 # 3.114. header_color_partial
1657 # When set, color header regexps behave like color body regexps: color is applied
1658 # to the exact text matched by the regexp. When unset, color is applied to the
1661 # One use of this option might be to apply color to just the header labels.
1663 # See “color” for more details.
1672 # When set, help lines describing the bindings for the major functions provided
1673 # by each menu are displayed on the first line of the screen.
1675 # Note: The binding will not be displayed correctly if the function is bound to a
1676 # sequence rather than a single keystroke. Also, the help line may not be updated
1677 # if a binding is changed while Mutt is running. Since this variable is primarily
1678 # aimed at new users, neither of these should present a major problem.
1682 # 3.116. hidden_host
1687 # When set, mutt will skip the host name part of $hostname variable when adding
1688 # the domain part to addresses. This variable does not affect the generation of
1689 # Message-IDs, and it will not lead to the cut-off of first-level domains.
1693 # 3.117. hide_limited
1698 # When set, mutt will not show the presence of messages that are hidden by
1699 # limiting, in the thread tree.
1703 # 3.118. hide_missing
1708 # When set, mutt will not show the presence of missing messages in the thread
1713 # 3.119. hide_thread_subject
1718 # When set, mutt will not show the subject of messages in the thread tree that
1719 # have the same subject as their parent or closest previously displayed sibling.
1723 # 3.120. hide_top_limited
1728 # When set, mutt will not show the presence of messages that are hidden by
1729 # limiting, at the top of threads in the thread tree. Note that when
1730 # $hide_limited is set, this option will have no effect.
1734 # 3.121. hide_top_missing
1739 # When set, mutt will not show the presence of missing messages at the top of
1740 # threads in the thread tree. Note that when $hide_missing is set, this option
1741 # will have no effect.
1750 # This variable controls the size (in number of strings remembered) of the string
1751 # history buffer per category. The buffer is cleared each time the variable is
1756 # 3.123. history_file
1759 # Default: “~/.mutthistory”
1761 # The file in which Mutt will save its history.
1763 # Also see $save_history.
1765 set history_file="~/.var/mutt/history"
1768 # 3.124. history_remove_dups
1773 # When set, all of the string history will be scanned for duplicates when a new
1774 # entry is added. Duplicate entries in the $history_file will also be removed
1775 # when it is periodically compacted.
1779 # 3.125. honor_disposition
1784 # When set, Mutt will not display attachments with a disposition of “attachment”
1785 # inline even if it could render the part to plain text. These MIME parts can
1786 # only be viewed from the attachment menu.
1788 # If unset, Mutt will render all MIME parts it can properly transform to plain
1793 # 3.126. honor_followup_to
1798 # This variable controls whether or not a Mail-Followup-To header is honored when
1799 # group-replying to a message.
1808 # Specifies the fully-qualified hostname of the system mutt is running on
1809 # containing the host's name and the DNS domain it belongs to. It is used as the
1810 # domain part (after “@”) for local email addresses as well as Message-Id
1813 # Its value is determined at startup as follows: the node's hostname is first
1814 # determined by the uname(3) function. The domain is then looked up using the
1815 # gethostname(2) and getaddrinfo(3) functions. If those calls are unable to
1816 # determine the domain, the full value returned by uname is used. Optionally,
1817 # Mutt can be compiled with a fixed domain name in which case a detected one is
1820 # Starting in Mutt 2.0, the operations described in the previous paragraph are
1821 # performed after the muttrc is processed, instead of beforehand. This way, if
1822 # the DNS operations are creating delays at startup, you can avoid those by
1823 # manually setting the value in your muttrc.
1825 # Also see $use_domain and $hidden_host.
1834 # When set, Mutt will show you international domain names decoded. Note: You can
1835 # use IDNs for addresses even if this is unset. This variable only affects
1836 # decoding. (IDN only)
1845 # When set, Mutt will encode international domain names using IDN. Unset this if
1846 # your SMTP server can handle newer (RFC 6531) UTF-8 encoded domains. (IDN only)
1850 # 3.130. ignore_linear_white_space
1855 # This option replaces linear-white-space between encoded-word and text to a
1856 # single space to prevent the display of MIME-encoded “Subject:” field from being
1857 # divided into multiple lines.
1861 # 3.131. ignore_list_reply_to
1866 # Affects the behavior of the <reply> function when replying to messages from
1867 # mailing lists (as defined by the “subscribe” or “lists” commands). When set, if
1868 # the “Reply-To:” field is set to the same value as the “To:” field, Mutt assumes
1869 # that the “Reply-To:” field was set by the mailing list to automate responses to
1870 # the list, and will ignore this field. To direct a response to the mailing list
1871 # when this option is set, use the <list-reply> function; <group-reply> will
1872 # reply to both the sender and the list.
1874 set ignore_list_reply_to=yes
1877 # 3.132. imap_authenticators
1882 # This is a colon-delimited list of authentication methods mutt may attempt to
1883 # use to log in to an IMAP server, in the order mutt should try them.
1884 # Authentication methods are either “login” or the right side of an IMAP “AUTH=
1885 # xxx” capability string, e.g. “digest-md5”, “gssapi” or “cram-md5”. This option
1886 # is case-insensitive. If it's unset (the default) mutt will try all available
1887 # methods, in order from most-secure to least-secure.
1891 # set imap_authenticators="gssapi:cram-md5:login"
1893 # Note: Mutt will only fall back to other authentication methods if the previous
1894 # methods are unavailable. If a method is available but authentication fails,
1895 # mutt will not connect to the IMAP server.
1899 # 3.133. imap_check_subscribed
1904 # When set, mutt will fetch the set of subscribed folders from your server on
1905 # connection, and add them to the set of mailboxes it polls for new mail just as
1906 # if you had issued individual “mailboxes” commands.
1910 # 3.134. imap_condstore
1915 # When set, mutt will use the CONDSTORE extension (RFC 7162) if advertised by the
1916 # server. Mutt's current implementation is basic, used only for initial message
1917 # fetching and flag updates.
1919 # For some IMAP servers, enabling this will slightly speed up downloading initial
1920 # messages. Unfortunately, Gmail is not one those, and displays worse performance
1921 # when enabled. Your mileage may vary.
1925 # 3.135. imap_deflate
1930 # When set, mutt will use the COMPRESS=DEFLATE extension (RFC 4978) if advertised
1933 # In general a good compression efficiency can be achieved, which speeds up
1934 # reading large mailboxes also on fairly good connections.
1938 # 3.136. imap_delim_chars
1943 # This contains the list of characters which you would like to treat as folder
1944 # separators for displaying IMAP paths. In particular it helps in using the “=”
1945 # shortcut for your folder variable.
1949 # 3.137. imap_fetch_chunk_size
1951 # Type: number (long)
1954 # When set to a value greater than 0, new headers will be downloaded in groups of
1955 # this many headers per request. If you have a very large mailbox, this might
1956 # prevent a timeout and disconnect when opening the mailbox, by sending a FETCH
1957 # per set of this many headers, instead of a single FETCH for all new headers.
1961 # 3.138. imap_headers
1966 # Mutt requests these header fields in addition to the default headers (“Date:”,
1967 # “From:”, “Sender:”, “Subject:”, “To:”, “Cc:”, “Message-Id:”, “References:”, “
1968 # Content-Type:”, “Content-Description:”, “In-Reply-To:”, “Reply-To:”, “Lines:”,
1969 # “List-Post:”, “X-Label:”) from IMAP servers before displaying the index menu.
1970 # You may want to add more headers for spam detection.
1972 # Note: This is a space separated list, items should be uppercase and not contain
1973 # the colon, e.g. “X-BOGOSITY X-SPAM-STATUS” for the “X-Bogosity:” and “
1974 # X-Spam-Status:” header fields.
1983 # When set, mutt will attempt to use the IMAP IDLE extension to check for new
1984 # mail in the current mailbox. Some servers (dovecot was the inspiration for this
1985 # option) react badly to mutt's implementation. If your connection seems to
1986 # freeze up periodically, try unsetting this.
1990 # 3.140. imap_keepalive
1995 # This variable specifies the maximum amount of time in seconds that mutt will
1996 # wait before polling open IMAP connections, to prevent the server from closing
1997 # them before mutt has finished with them. The default is well within the
1998 # RFC-specified minimum amount of time (30 minutes) before a server is allowed to
1999 # do this, but in practice the RFC does get violated every now and then. Reduce
2000 # this number if you find yourself getting disconnected from your IMAP server due
2005 # 3.141. imap_list_subscribed
2010 # This variable configures whether IMAP folder browsing will look for only
2011 # subscribed folders or all folders. This can be toggled in the IMAP browser with
2012 # the <toggle-subscribed> function.
2021 # Your login name on the IMAP server.
2023 # This variable defaults to the value of $imap_user.
2027 # 3.143. imap_oauth_refresh_command
2032 # The command to run to generate an OAUTH refresh token for authorizing your
2033 # connection to your IMAP server. This command will be run on every connection
2034 # attempt that uses the OAUTHBEARER authentication mechanism. See “oauth” for
2044 # Specifies the password for your IMAP account. If unset, Mutt will prompt you
2045 # for your password when you invoke the <imap-fetch-mail> function or try to open
2048 # Warning: you should only use this option when you are on a fairly secure
2049 # machine, because the superuser can read your muttrc even if you are the only
2050 # one who can read the file.
2054 # 3.145. imap_passive
2059 # When set, mutt will not open new IMAP connections to check for new mail. Mutt
2060 # will only check for new mail over existing IMAP connections. This is useful if
2061 # you don't want to be prompted for user/password pairs on mutt invocation, or if
2062 # opening the connection is slow.
2071 # When set, mutt will avoid implicitly marking your mail as read whenever you
2072 # fetch a message from the server. This is generally a good thing, but can make
2073 # closing an IMAP folder somewhat slower. This option exists to appease speed
2078 # 3.147. imap_pipeline_depth
2083 # Controls the number of IMAP commands that may be queued up before they are sent
2084 # to the server. A deeper pipeline reduces the amount of time mutt must wait for
2085 # the server, and can make IMAP servers feel much more responsive. But not all
2086 # servers correctly handle pipelined commands, so if you have problems you might
2087 # want to try setting this variable to 0.
2089 # Note: Changes to this variable have no effect on open connections.
2093 # 3.148. imap_poll_timeout
2098 # This variable specifies the maximum amount of time in seconds that mutt will
2099 # wait for a response when polling IMAP connections for new mail, before timing
2100 # out and closing the connection. Set to 0 to disable timing out.
2104 # 3.149. imap_qresync
2109 # When set, mutt will use the QRESYNC extension (RFC 7162) if advertised by the
2110 # server. Mutt's current implementation is basic, used only for initial message
2111 # fetching and flag updates.
2113 # Note: this feature is currently experimental. If you experience strange
2114 # behavior, such as duplicate or missing messages please file a bug report to let
2119 # 3.150. imap_servernoise
2124 # When set, mutt will display warning messages from the IMAP server as error
2125 # messages. Since these messages are often harmless, or generated due to
2126 # configuration problems on the server which are out of the users' hands, you may
2127 # wish to suppress them at some point.
2136 # The name of the user whose mail you intend to access on the IMAP server.
2138 # This variable defaults to your user name on the local machine.
2142 # 3.152. implicit_autoview
2147 # If set to “yes”, mutt will look for a mailcap entry with the “copiousoutput”
2148 # flag set for every MIME attachment it doesn't have an internal viewer defined
2149 # for. If such an entry is found, mutt will use the viewer defined in that entry
2150 # to convert the body part to text form.
2152 set implicit_autoview=no
2160 # Controls whether or not a copy of the message(s) you are replying to is
2161 # included in your reply.
2166 # 3.154. include_encrypted
2171 # Controls whether or not Mutt includes separately encrypted attachment contents
2174 # This variable was added to prevent accidental exposure of encrypted contents
2175 # when replying to an attacker. If a previously encrypted message were attached
2176 # by the attacker, they could trick an unwary recipient into decrypting and
2177 # including the message in their reply.
2181 # 3.155. include_onlyfirst
2186 # Controls whether or not Mutt includes only the first attachment of the message
2191 # 3.156. indent_string
2196 # Specifies the string to prepend to each line of text quoted in a message to
2197 # which you are replying. You are strongly encouraged not to change this value,
2198 # as it tends to agitate the more fanatical netizens.
2200 # The value of this option is ignored if $text_flowed is set, because the quoting
2201 # mechanism is strictly defined for format=flowed.
2203 # This option is a format string, please see the description of $index_format for
2204 # supported printf(3)-style sequences.
2208 # 3.157. index_format
2211 # Default: “%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s”
2213 # This variable allows you to customize the message index display to your
2216 # “Format strings” are similar to the strings used in the C function printf(3) to
2217 # format output (see the man page for more details). For an explanation of the %?
2218 # construct, see the $status_format description. The following sequences are
2221 # ┌───────┬─────────────────────────────────────────────────────────────────────┐
2222 # │%a │address of the author │
2223 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2224 # │%A │reply-to address (if present; otherwise: address of author) │
2225 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2226 # │%b │filename of the original message folder (think mailbox) │
2227 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2228 # │%B │the list to which the letter was sent, or else the folder name (%b). │
2229 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2230 # │%c │number of characters (bytes) in the message (see formatstrings-size) │
2231 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2232 # │%C │current message number │
2233 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2234 # │%d │date and time of the message in the format specified by $date_format │
2235 # │ │converted to sender's time zone │
2236 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2237 # │%D │date and time of the message in the format specified by $date_format │
2238 # │ │converted to the local time zone │
2239 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2240 # │%e │current message number in thread │
2241 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2242 # │%E │number of messages in current thread │
2243 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2244 # │%f │sender (address + real name), either From: or Return-Path: │
2245 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2246 # │%F │author name, or recipient name if the message is from you │
2247 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2248 # │%H │spam attribute(s) of this message │
2249 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2250 # │%i │message-id of the current message │
2251 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2252 # │%l │number of lines in the unprocessed message (may not work with │
2253 # │ │maildir, mh, and IMAP folders) │
2254 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2255 # │ │If an address in the “To:” or “Cc:” header field matches an address │
2256 # │%L │defined by the users “subscribe” command, this displays "To │
2257 # │ │<list-name>", otherwise the same as %F. │
2258 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2259 # │%m │total number of message in the mailbox │
2260 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2261 # │%M │number of hidden messages if the thread is collapsed. │
2262 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2263 # │%N │message score │
2264 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2265 # │%n │author's real name (or address if missing) │
2266 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2267 # │%O │original save folder where mutt would formerly have stashed the │
2268 # │ │message: list name or recipient name if not sent to a list │
2269 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2270 # │%P │progress indicator for the built-in pager (how much of the file has │
2271 # │ │been displayed) │
2272 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2273 # │%r │comma separated list of “To:” recipients │
2274 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2275 # │%R │comma separated list of “Cc:” recipients │
2276 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2277 # │%s │subject of the message │
2278 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2279 # │%S │single character status of the message (“N”/“O”/“D”/“d”/“!”/“r”/“*”) │
2280 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2281 # │%t │“To:” field (recipients) │
2282 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2283 # │%T │the appropriate character from the $to_chars string │
2284 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2285 # │%u │user (login) name of the author │
2286 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2287 # │%v │first name of the author, or the recipient if the message is from you│
2288 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2289 # │%X │number of attachments (please see the “attachments” section for │
2290 # │ │possible speed effects) │
2291 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2292 # │%y │“X-Label:” field, if present │
2293 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2294 # │ │“X-Label:” field, if present, and (1) not at part of a thread tree, │
2295 # │%Y │(2) at the top of a thread, or (3) “X-Label:” is different from │
2296 # │ │preceding message's “X-Label:”. │
2297 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2298 # │ │a three character set of message status flags. the first character is│
2299 # │ │new/read/replied flags (“n”/“o”/“r”/“O”/“N”). the second is deleted │
2300 # │%Z │or encryption flags (“D”/“d”/“S”/“P”/“s”/“K”). the third is either │
2301 # │ │tagged/flagged (“*”/“!”), or one of the characters listed in │
2303 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2304 # │%@name@│insert and evaluate format-string from the matching “ │
2305 # │ │index-format-hook” command │
2306 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2307 # │ │the date and time of the message is converted to sender's time zone, │
2308 # │%{fmt} │and “fmt” is expanded by the library function strftime(3); a leading │
2309 # │ │bang disables locales │
2310 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2311 # │ │the date and time of the message is converted to the local time zone,│
2312 # │%[fmt] │and “fmt” is expanded by the library function strftime(3); a leading │
2313 # │ │bang disables locales │
2314 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2315 # │ │the local date and time when the message was received. “fmt” is │
2316 # │%(fmt) │expanded by the library function strftime(3); a leading bang disables│
2318 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2319 # │%<fmt> │the current local time. “fmt” is expanded by the library function │
2320 # │ │strftime(3); a leading bang disables locales. │
2321 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2322 # │%>X │right justify the rest of the string and pad with character “X” │
2323 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2324 # │%|X │pad to the end of the line with character “X” │
2325 # ├───────┼─────────────────────────────────────────────────────────────────────┤
2326 # │%*X │soft-fill with character “X” as pad │
2327 # └───────┴─────────────────────────────────────────────────────────────────────┘
2329 # Note that for mbox/mmdf, “%l” applies to the unprocessed message, and for
2330 # maildir/mh, the value comes from the “Lines:” header field when present (the
2331 # meaning is normally the same). Thus the value depends on the encodings used in
2332 # the different parts of the message and has little meaning in practice.
2334 # “Soft-fill” deserves some explanation: Normal right-justification will print
2335 # everything to the left of the “%>”, displaying padding and whatever lies to the
2336 # right only if there's room. By contrast, soft-fill gives priority to the
2337 # right-hand side, guaranteeing space to display it and showing padding only if
2338 # there's still room. If necessary, soft-fill will eat text leftwards to make
2339 # room for rightward text.
2341 # Note that these expandos are supported in “save-hook”, “fcc-hook”, “
2342 # fcc-save-hook”, and “index-format-hook”.
2344 # They are also supported in the configuration variables $attribution,
2345 # $forward_attribution_intro, $forward_attribution_trailer, $forward_format,
2346 # $indent_string, $message_format, $pager_format, and $post_indent_string.
2355 # How to invoke ispell (GNU's spell-checking software).
2359 # 3.159. keep_flagged
2364 # If set, read messages marked as flagged will not be moved from your spool
2365 # mailbox to your $mbox mailbox, or as a result of a “mbox-hook” command.
2374 # This variable configures how often (in seconds) mutt should look for new mail.
2375 # Also see the $timeout variable.
2379 # 3.161. mail_check_recent
2384 # When set, Mutt will only notify you about new mail that has been received since
2385 # the last time you opened the mailbox. When unset, Mutt will notify you if any
2386 # new mail exists in the mailbox, regardless of whether you have visited it
2389 # When $mark_old is set, Mutt does not consider the mailbox to contain new mail
2390 # if only old messages exist.
2394 # 3.162. mail_check_stats
2399 # When set, mutt will periodically calculate message statistics of a mailbox
2400 # while polling for new mail. It will check for unread, flagged, and total
2401 # message counts. Because this operation is more performance intensive, it
2402 # defaults to unset, and has a separate option, $mail_check_stats_interval, to
2403 # control how often to update these counts.
2405 # Message statistics can also be explicitly calculated by invoking the
2406 # <check-stats> function.
2408 set mail_check_stats=yes
2411 # 3.163. mail_check_stats_interval
2416 # When $mail_check_stats is set, this variable configures how often (in seconds)
2417 # mutt will update message counts.
2421 # 3.164. mailcap_path
2426 # This variable specifies which files to consult when attempting to display MIME
2427 # bodies not directly supported by Mutt. The default value is generated during
2428 # startup: see the “mailcap” section of the manual.
2430 set mailcap_path="$my_confdir/mailcap.containers:$my_confdir/mailcap.icalendar:$my_confdir/mailcap.backgrounding:$my_confdir/mailcap.htmldump"
2433 # 3.165. mailcap_sanitize
2438 # If set, mutt will restrict possible characters in mailcap % expandos to a
2439 # well-defined set of safe characters. This is the safe setting, but we are not
2440 # sure it doesn't break some more advanced MIME stuff.
2442 # DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING!
2446 # 3.166. maildir_header_cache_verify
2451 # Check for Maildir unaware programs other than mutt having modified maildir
2452 # files when the header cache is in use. This incurs one stat(2) per message
2453 # every time the folder is opened (which can be very slow for NFS folders).
2455 set maildir_header_cache_verify=no
2458 # 3.167. maildir_trash
2463 # If set, messages marked as deleted will be saved with the maildir trashed flag
2464 # instead of unlinked. Note: this only applies to maildir-style mailboxes.
2465 # Setting it will have no effect on other mailbox types.
2469 # 3.168. maildir_check_cur
2474 # If set, mutt will poll both the new and cur directories of a maildir folder for
2475 # new messages. This might be useful if other programs interacting with the
2476 # folder (e.g. dovecot) are moving new messages to the cur directory. Note that
2477 # setting this option may slow down polling for new messages in large folders,
2478 # since mutt has to scan all cur messages.
2482 # 3.169. mark_macro_prefix
2487 # Prefix for macros created using mark-message. A new macro automatically
2488 # generated with <mark-message>a will be composed from this prefix and the letter
2498 # Controls whether or not mutt marks new unread messages as old if you exit a
2499 # mailbox without reading them. With this option set, the next time you start
2500 # mutt, the messages will show up with an “O” next to them in the index menu,
2501 # indicating that they are old.
2511 # Controls the display of wrapped lines in the internal pager. If set, a “+”
2512 # marker is displayed at the beginning of wrapped lines.
2514 # Also see the $smart_wrap variable.
2521 # Type: regular expression
2522 # Default: “!^.[^.]”
2524 # A regular expression used in the file browser, optionally preceded by the not
2525 # operator “!”. Only files whose names match this mask will be shown. The match
2526 # is always case-sensitive.
2535 # This specifies the folder into which read mail in your $spoolfile folder will
2538 # Also see the $move variable.
2545 # Type: folder magic
2548 # The default mailbox type used when creating new folders. May be any of “mbox”,
2549 # “MMDF”, “MH” and “Maildir”. This is overridden by the -m command-line option.
2551 set mbox_type=Maildir
2554 # 3.175. menu_context
2559 # This variable controls the number of lines of context that are given when
2560 # scrolling through menus. (Similar to $pager_context.)
2565 # 3.176. menu_move_off
2570 # When unset, the bottom entry of menus will never scroll up past the bottom of
2571 # the screen, unless there are less entries than lines. When set, the bottom
2572 # entry may move off the bottom.
2576 # 3.177. menu_scroll
2581 # When set, menus will be scrolled up or down one line when you attempt to move
2582 # across a screen boundary. If unset, the screen is cleared and the next or
2583 # previous page of the menu is displayed (useful for slow links to avoid many
2589 # 3.178. message_cache_clean
2594 # If set, mutt will clean out obsolete entries from the message cache when the
2595 # mailbox is synchronized. You probably only want to set it every once in a
2596 # while, since it can be a little slow (especially for large folders).
2600 # 3.179. message_cachedir
2605 # Set this to a directory and mutt will cache copies of messages from your IMAP
2606 # and POP servers here. You are free to remove entries at any time.
2608 # When setting this variable to a directory, mutt needs to fetch every remote
2609 # message only once and can perform regular expression searches as fast as for
2612 # Also see the $message_cache_clean variable.
2616 # 3.180. message_format
2621 # This is the string displayed in the “attachment” menu for attachments of type
2622 # message/rfc822. For a full listing of defined printf(3)-like sequences see the
2623 # section on $index_format.
2632 # If set, forces Mutt to interpret keystrokes with the high bit (bit 8) set as if
2633 # the user had pressed the Esc key and whatever key remains after having the high
2634 # bit removed. For example, if the key pressed has an ASCII value of 0xf8, then
2635 # this is treated as if the user had pressed Esc then “x”. This is because the
2636 # result of removing the high bit from 0xf8 is 0x78, which is the ASCII character
2646 # If unset, Mutt will remove your address (see the “alternates” command) from the
2647 # list of recipients when replying to a message.
2656 # When unset, mutt will mimic mh's behavior and rename deleted messages to ,<old
2657 # file name> in mh folders instead of really deleting them. This leaves the
2658 # message on disk but makes programs reading the folder ignore it. If the
2659 # variable is set, the message files will simply be deleted.
2661 # This option is similar to $maildir_trash for Maildir folders.
2665 # 3.184. mh_seq_flagged
2668 # Default: “flagged”
2670 # The name of the MH sequence used for flagged messages.
2674 # 3.185. mh_seq_replied
2677 # Default: “replied”
2679 # The name of the MH sequence used to tag replied messages.
2683 # 3.186. mh_seq_unseen
2688 # The name of the MH sequence used for unseen messages.
2692 # 3.187. mime_forward
2697 # When set, the message you are forwarding will be attached as a separate message
2698 # /rfc822 MIME part instead of included in the main body of the message. This is
2699 # useful for forwarding MIME messages so the receiver can properly view the
2700 # message as it was delivered to you. If you like to switch between MIME and not
2701 # MIME from mail to mail, set this variable to “ask-no” or “ask-yes”.
2703 # Also see $forward_decode and $mime_forward_decode.
2705 set mime_forward=ask-yes
2708 # 3.188. mime_forward_decode
2713 # Controls the decoding of complex MIME messages into text/plain when forwarding
2714 # a message while $mime_forward is set. Otherwise $forward_decode is used
2719 # 3.189. mime_forward_rest
2724 # When forwarding multiple attachments of a MIME message from the attachment
2725 # menu, attachments which cannot be decoded in a reasonable manner will be
2726 # attached to the newly composed message if this option is set.
2730 # 3.190. mime_type_query_command
2735 # This specifies a command to run, to determine the mime type of a new attachment
2736 # when composing a message. Unless $mime_type_query_first is set, this will only
2737 # be run if the attachment's extension is not found in the mime.types file.
2739 # The string may contain a “%s”, which will be substituted with the attachment
2740 # filename. Mutt will add quotes around the string substituted for “%s”
2741 # automatically according to shell quoting rules, so you should avoid adding your
2742 # own. If no “%s” is found in the string, Mutt will append the attachment
2743 # filename to the end of the string.
2745 # The command should output a single line containing the attachment's mime type.
2747 # Suggested values are “xdg-mime query filetype” or “file -bi”.
2751 # 3.191. mime_type_query_first
2756 # When set, the $mime_type_query_command will be run before the mime.types
2761 # 3.192. mix_entry_format
2764 # Default: “%4n %c %-16s %a”
2766 # This variable describes the format of a remailer line on the mixmaster chain
2767 # selection screen. The following printf(3)-like sequences are supported:
2769 # ┌──┬───────────────────────────────┐
2770 # │%n│The running number on the menu.│
2771 # ├──┼───────────────────────────────┤
2772 # │%c│Remailer capabilities. │
2773 # ├──┼───────────────────────────────┤
2774 # │%s│The remailer's short name. │
2775 # ├──┼───────────────────────────────┤
2776 # │%a│The remailer's e-mail address. │
2777 # └──┴───────────────────────────────┘
2784 # Default: “mixmaster”
2786 # This variable contains the path to the Mixmaster binary on your system. It is
2787 # used with various sets of parameters to gather the list of known remailers, and
2788 # to finally send a message through the mixmaster chain.
2790 set mixmaster="mixmaster-filter"
2798 # Controls whether or not Mutt will move read messages from your spool mailbox to
2799 # your $mbox mailbox, or as a result of a “mbox-hook” command.
2804 # 3.195. muttlisp_inline_eval
2809 # If set, Mutt will evaluate bare parenthesis arguments to commands as MuttLisp
2814 # 3.196. narrow_tree
2819 # This variable, when set, makes the thread tree narrower, allowing deeper
2820 # threads to fit on the screen.
2830 # Operations that expect to transfer a large amount of data over the network will
2831 # update their progress every $net_inc kilobytes. If set to 0, no progress
2832 # messages will be displayed.
2834 # See also $read_inc, $write_inc and $net_inc.
2838 # 3.198. new_mail_command
2843 # If set, Mutt will call this command after a new message is received. See the
2844 # $status_format documentation for the values that can be formatted into this
2852 # Default: “builtin”
2854 # This variable specifies which pager you would like to use to view messages. The
2855 # value “builtin” means to use the built-in pager, otherwise this variable should
2856 # specify the pathname of the external pager you would like to use.
2858 # Using an external pager may have some disadvantages: Additional keystrokes are
2859 # necessary because you can't call mutt functions directly from the pager, and
2860 # screen resizes cause lines longer than the screen width to be badly formatted
2863 # When using an external pager, also see $prompt_after which defaults set.
2867 # 3.200. pager_context
2872 # This variable controls the number of lines of context that are given when
2873 # displaying the next or previous page in the internal pager. By default, Mutt
2874 # will display the line after the last one on the screen at the top of the next
2875 # page (0 lines of context).
2877 # This variable also specifies the amount of context given for search results. If
2878 # positive, this many lines will be given before a match, if 0, the match will be
2884 # 3.201. pager_format
2887 # Default: “-%Z- %C/%m: %-20.20n %s%* -- (%P)”
2889 # This variable controls the format of the one-line message “status” displayed
2890 # before each message in either the internal or an external pager. The valid
2891 # sequences are listed in the $index_format section.
2893 set pager_format="<%a> %* %i (%P)"
2896 # 3.202. pager_index_lines
2901 # Determines the number of lines of a mini-index which is shown when in the
2902 # pager. The current message, unless near the top or bottom of the folder, will
2903 # be roughly one third of the way down this mini-index, giving the reader the
2904 # context of a few messages before and after the message. This is useful, for
2905 # example, to determine how many messages remain to be read in the current
2906 # thread. One of the lines is reserved for the status bar from the index, so a
2907 # setting of 6 will only show 5 lines of the actual index. A value of 0 results
2908 # in no index being shown. If the number of messages in the current folder is
2909 # less than $pager_index_lines, then the index will only use as many lines as it
2912 set pager_index_lines=$menu_context
2920 # When set, the internal-pager will not move to the next message when you are at
2921 # the end of a message and invoke the <next-page> function.
2926 # 3.204. pattern_format
2929 # Default: “%2n %-15e %d”
2931 # This variable describes the format of the “pattern completion” menu. The
2932 # following printf(3)-style sequences are understood:
2934 # ┌──┬────────────────────┐
2935 # │%d│pattern description │
2936 # ├──┼────────────────────┤
2937 # │%e│pattern expression │
2938 # ├──┼────────────────────┤
2939 # │%n│index number │
2940 # └──┴────────────────────┘
2944 # 3.205. pgp_auto_decode
2949 # If set, mutt will automatically attempt to decrypt traditional PGP messages
2950 # whenever the user performs an operation which ordinarily would result in the
2951 # contents of the message being operated on. For example, if the user displays a
2952 # pgp-traditional message which has not been manually checked with the
2953 # <check-traditional-pgp> function, mutt will automatically check the message for
2956 set pgp_auto_decode=yes
2959 # 3.206. pgp_autoinline
2964 # This option controls whether Mutt generates old-style inline (traditional) PGP
2965 # encrypted or signed messages under certain circumstances. This can be
2966 # overridden by use of the pgp menu, when inline is not required. The GPGME
2967 # backend does not support this option.
2969 # Note that Mutt might automatically use PGP/MIME for messages which consist of
2970 # more than a single MIME part. Mutt can be configured to ask before sending PGP/
2971 # MIME messages when inline (traditional) would not work.
2973 # Also see the $pgp_mime_auto variable.
2975 # Also note that using the old-style PGP message format is strongly deprecated.
2980 # 3.207. pgp_check_exit
2985 # If set, mutt will check the exit code of the PGP subprocess when signing or
2986 # encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
2990 # 3.208. pgp_check_gpg_decrypt_status_fd
2995 # If set, mutt will check the status file descriptor output of
2996 # $pgp_decrypt_command and $pgp_decode_command for GnuPG status codes indicating
2997 # successful decryption. This will check for the presence of DECRYPTION_OKAY,
2998 # absence of DECRYPTION_FAILED, and that all PLAINTEXT occurs between the
2999 # BEGIN_DECRYPTION and END_DECRYPTION status codes.
3001 # If unset, mutt will instead match the status fd output against
3002 # $pgp_decryption_okay. (PGP only)
3006 # 3.209. pgp_clearsign_command
3011 # This format is used to create an old-style “clearsigned” PGP message. Note that
3012 # the use of this format is strongly deprecated.
3014 # This is a format string, see the $pgp_decode_command command for possible
3015 # printf(3)-like sequences. (PGP only)
3019 # 3.210. pgp_decode_command
3024 # This format strings specifies a command which is used to decode application/pgp
3027 # The PGP command formats have their own set of printf(3)-like sequences:
3029 # ┌──┬──────────────────────────────────────────────────────────────────────────┐
3030 # │%p│Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty string │
3031 # │ │otherwise. Note: This may be used with a %? construct. │
3032 # ├──┼──────────────────────────────────────────────────────────────────────────┤
3033 # │%f│Expands to the name of a file containing a message. │
3034 # ├──┼──────────────────────────────────────────────────────────────────────────┤
3035 # │%s│Expands to the name of a file containing the signature part of a multipart│
3036 # │ │/signed attachment when verifying it. │
3037 # ├──┼──────────────────────────────────────────────────────────────────────────┤
3038 # │%a│The value of $pgp_sign_as if set, otherwise the value of $pgp_default_key.│
3039 # ├──┼──────────────────────────────────────────────────────────────────────────┤
3040 # │%r│One or more key IDs (or fingerprints if available). │
3041 # └──┴──────────────────────────────────────────────────────────────────────────┘
3043 # For examples on how to configure these formats for the various versions of PGP
3044 # which are floating around, see the pgp and gpg sample configuration files in
3045 # the samples/ subdirectory which has been installed on your system alongside the
3046 # documentation. (PGP only)
3050 # 3.211. pgp_decrypt_command
3055 # This command is used to decrypt a PGP encrypted message.
3057 # This is a format string, see the $pgp_decode_command command for possible
3058 # printf(3)-like sequences. (PGP only)
3062 # 3.212. pgp_decryption_okay
3064 # Type: regular expression
3067 # If you assign text to this variable, then an encrypted PGP message is only
3068 # considered successfully decrypted if the output from $pgp_decrypt_command
3069 # contains the text. This is used to protect against a spoofed encrypted message,
3070 # with multipart/encrypted headers but containing a block that is not actually
3071 # encrypted. (e.g. simply signed and ascii armored text).
3073 # Note that if $pgp_check_gpg_decrypt_status_fd is set, this variable is ignored.
3078 # 3.213. pgp_default_key
3083 # This is the default key-pair to use for PGP operations. It will be used for
3084 # encryption (see $postpone_encrypt and $pgp_self_encrypt).
3086 # It will also be used for signing unless $pgp_sign_as is set.
3088 # The (now deprecated) pgp_self_encrypt_as is an alias for this variable, and
3089 # should no longer be used. (PGP only)
3093 # 3.214. pgp_encrypt_only_command
3098 # This command is used to encrypt a body part without signing it.
3100 # This is a format string, see the $pgp_decode_command command for possible
3101 # printf(3)-like sequences. (PGP only)
3105 # 3.215. pgp_encrypt_sign_command
3110 # This command is used to both sign and encrypt a body part.
3112 # This is a format string, see the $pgp_decode_command command for possible
3113 # printf(3)-like sequences. (PGP only)
3117 # 3.216. pgp_entry_format
3120 # Default: “%4n %t%f %4l/0x%k %-4a %2c %u”
3122 # This variable allows you to customize the PGP key selection menu to your
3123 # personal taste. This string is similar to $index_format, but has its own set of
3124 # printf(3)-like sequences:
3126 # ┌──────┬──────────────────────────────────────────────────────┐
3128 # ├──────┼──────────────────────────────────────────────────────┤
3130 # ├──────┼──────────────────────────────────────────────────────┤
3132 # ├──────┼──────────────────────────────────────────────────────┤
3134 # ├──────┼──────────────────────────────────────────────────────┤
3136 # ├──────┼──────────────────────────────────────────────────────┤
3138 # ├──────┼──────────────────────────────────────────────────────┤
3139 # │%c │capabilities │
3140 # ├──────┼──────────────────────────────────────────────────────┤
3141 # │%t │trust/validity of the key-uid association │
3142 # ├──────┼──────────────────────────────────────────────────────┤
3143 # │%[<s>]│date of the key where <s> is an strftime(3) expression│
3144 # └──────┴──────────────────────────────────────────────────────┘
3150 # 3.217. pgp_export_command
3155 # This command is used to export a public key from the user's key ring.
3157 # This is a format string, see the $pgp_decode_command command for possible
3158 # printf(3)-like sequences. (PGP only)
3162 # 3.218. pgp_getkeys_command
3167 # This command is invoked whenever Mutt needs to fetch the public key associated
3168 # with an email address. Of the sequences supported by $pgp_decode_command, %r is
3169 # the only printf(3)-like sequence used with this format. Note that in this case,
3170 # %r expands to the email address, not the public key ID (the key ID is unknown,
3171 # which is why Mutt is invoking this command). (PGP only)
3175 # 3.219. pgp_good_sign
3177 # Type: regular expression
3180 # If you assign a text to this variable, then a PGP signature is only considered
3181 # verified if the output from $pgp_verify_command contains the text. Use this
3182 # variable if the exit code from the command is 0 even for bad signatures. (PGP
3187 # 3.220. pgp_ignore_subkeys
3192 # Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, the
3193 # principal key will inherit the subkeys' capabilities. Unset this if you want to
3194 # play interesting key selection games. (PGP only)
3198 # 3.221. pgp_import_command
3203 # This command is used to import a key from a message into the user's public key
3206 # This is a format string, see the $pgp_decode_command command for possible
3207 # printf(3)-like sequences. (PGP only)
3211 # 3.222. pgp_list_pubring_command
3216 # This command is used to list the public key ring's contents. The output format
3217 # must be analogous to the one used by
3219 # gpg --list-keys --with-colons --with-fingerprint
3221 # This format is also generated by the mutt_pgpring utility which comes with
3224 # Note: gpg's fixed-list-mode option should not be used. It produces a different
3225 # date format which may result in mutt showing incorrect key generation dates.
3227 # This is a format string, see the $pgp_decode_command command for possible
3228 # printf(3)-like sequences. Note that in this case, %r expands to the search
3229 # string, which is a list of one or more quoted values such as email address,
3230 # name, or keyid. (PGP only)
3234 # 3.223. pgp_list_secring_command
3239 # This command is used to list the secret key ring's contents. The output format
3240 # must be analogous to the one used by:
3242 # gpg --list-keys --with-colons --with-fingerprint
3244 # This format is also generated by the mutt_pgpring utility which comes with
3247 # Note: gpg's fixed-list-mode option should not be used. It produces a different
3248 # date format which may result in mutt showing incorrect key generation dates.
3250 # This is a format string, see the $pgp_decode_command command for possible
3251 # printf(3)-like sequences. Note that in this case, %r expands to the search
3252 # string, which is a list of one or more quoted values such as email address,
3253 # name, or keyid. (PGP only)
3257 # 3.224. pgp_long_ids
3262 # If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. NOTE:
3263 # Internally, Mutt has transitioned to using fingerprints (or long key IDs as a
3264 # fallback). This option now only controls the display of key IDs in the key
3265 # selection menu and a few other places. (PGP only)
3269 # 3.225. pgp_mime_auto
3274 # This option controls whether Mutt will prompt you for automatically sending a
3275 # (signed/encrypted) message using PGP/MIME when inline (traditional) fails (for
3278 # Also note that using the old-style PGP message format is strongly deprecated.
3283 # 3.226. pgp_replyinline
3288 # Setting this variable will cause Mutt to always attempt to create an inline
3289 # (traditional) message when replying to a message which is PGP encrypted/signed
3290 # inline. This can be overridden by use of the pgp menu, when inline is not
3291 # required. This option does not automatically detect if the (replied-to) message
3292 # is inline; instead it relies on Mutt internals for previously checked/flagged
3295 # Note that Mutt might automatically use PGP/MIME for messages which consist of
3296 # more than a single MIME part. Mutt can be configured to ask before sending PGP/
3297 # MIME messages when inline (traditional) would not work.
3299 # Also see the $pgp_mime_auto variable.
3301 # Also note that using the old-style PGP message format is strongly deprecated.
3306 # 3.227. pgp_retainable_sigs
3311 # If set, signed and encrypted messages will consist of nested multipart/signed
3312 # and multipart/encrypted body parts.
3314 # This is useful for applications like encrypted and signed mailing lists, where
3315 # the outer layer (multipart/encrypted) can be easily removed, while the inner
3316 # multipart/signed part is retained. (PGP only)
3318 set pgp_retainable_sigs=yes
3321 # 3.228. pgp_self_encrypt
3326 # When set, PGP encrypted messages will also be encrypted using the key in
3327 # $pgp_default_key. (PGP only)
3331 # 3.229. pgp_show_unusable
3336 # If set, mutt will display non-usable keys on the PGP key selection menu. This
3337 # includes keys which have been revoked, have expired, or have been marked as “
3338 # disabled” by the user. (PGP only)
3340 set pgp_show_unusable=no
3343 # 3.230. pgp_sign_as
3348 # If you have a different key pair to use for signing, you should set this to the
3349 # signing key. Most people will only need to set $pgp_default_key. It is
3350 # recommended that you use the keyid form to specify your key (e.g. 0x00112233).
3353 set pgp_sign_as="0x9C9D6979AE941637"
3356 # 3.231. pgp_sign_command
3361 # This command is used to create the detached PGP signature for a multipart/
3362 # signed PGP/MIME body part.
3364 # This is a format string, see the $pgp_decode_command command for possible
3365 # printf(3)-like sequences. (PGP only)
3369 # 3.232. pgp_sort_keys
3374 # Specifies how the entries in the pgp menu are sorted. The following are legal
3377 # ┌───────┬──────────────────────────────┐
3378 # │address│sort alphabetically by user id│
3379 # ├───────┼──────────────────────────────┤
3380 # │keyid │sort alphabetically by key id │
3381 # ├───────┼──────────────────────────────┤
3382 # │date │sort by key creation date │
3383 # ├───────┼──────────────────────────────┤
3384 # │trust │sort by the trust of the key │
3385 # └───────┴──────────────────────────────┘
3387 # If you prefer reverse order of the above values, prefix it with “reverse-”.
3392 # 3.233. pgp_strict_enc
3397 # If set, Mutt will automatically encode PGP/MIME signed messages as
3398 # quoted-printable. Please note that unsetting this variable may lead to problems
3399 # with non-verifyable PGP signatures, so only change this if you know what you
3400 # are doing. (PGP only)
3404 # 3.234. pgp_timeout
3406 # Type: number (long)
3409 # The number of seconds after which a cached passphrase will expire if not used.
3414 # 3.235. pgp_use_gpg_agent
3419 # If set, mutt expects a gpg-agent(1) process will handle private key passphrase
3420 # prompts. If unset, mutt will prompt for the passphrase and pass it via stdin to
3423 # Note that as of version 2.1, GnuPG automatically spawns an agent and requires
3424 # the agent be used for passphrase management. Since that version is increasingly
3425 # prevalent, this variable now defaults set.
3427 # Mutt works with a GUI or curses pinentry program. A TTY pinentry should not be
3430 # If you are using an older version of GnuPG without an agent running, or another
3431 # encryption program without an agent, you will need to unset this variable. (PGP
3434 set pgp_use_gpg_agent=yes
3437 # 3.236. pgp_verify_command
3442 # This command is used to verify PGP signatures.
3444 # This is a format string, see the $pgp_decode_command command for possible
3445 # printf(3)-like sequences. (PGP only)
3449 # 3.237. pgp_verify_key_command
3454 # This command is used to verify key information from the key selection menu.
3456 # This is a format string, see the $pgp_decode_command command for possible
3457 # printf(3)-like sequences. (PGP only)
3461 # 3.238. pipe_decode
3466 # Used in connection with the <pipe-message> function. When unset, Mutt will pipe
3467 # the messages without any preprocessing. When set, Mutt will attempt to decode
3468 # the messages first.
3470 # Also see $pipe_decode_weed, which controls whether headers will be weeded when
3475 # 3.239. pipe_decode_weed
3480 # For <pipe-message>, when $pipe_decode is set, this further controls whether
3481 # Mutt will weed headers.
3490 # The separator to add between messages when piping a list of tagged messages to
3491 # an external Unix command.
3500 # Used in connection with the <pipe-message> function following <tag-prefix>. If
3501 # this variable is unset, when piping a list of tagged messages Mutt will
3502 # concatenate the messages and will pipe them all concatenated. When set, Mutt
3503 # will pipe the messages one by one. In both cases the messages are piped in the
3504 # current sorted order, and the $pipe_sep separator is added after each message.
3508 # 3.242. pop_auth_try_all
3513 # If set, Mutt will try all available authentication methods. When unset, Mutt
3514 # will only fall back to other authentication methods if the previous methods are
3515 # unavailable. If a method is available but authentication fails, Mutt will not
3516 # connect to the POP server.
3520 # 3.243. pop_authenticators
3525 # This is a colon-delimited list of authentication methods mutt may attempt to
3526 # use to log in to an POP server, in the order mutt should try them.
3527 # Authentication methods are either “user”, “apop” or any SASL mechanism, e.g. “
3528 # digest-md5”, “gssapi” or “cram-md5”. This option is case-insensitive. If this
3529 # option is unset (the default) mutt will try all available methods, in order
3530 # from most-secure to least-secure.
3534 # set pop_authenticators="digest-md5:apop:user"
3538 # 3.244. pop_checkinterval
3543 # This variable configures how often (in seconds) mutt should look for new mail
3544 # in the currently selected mailbox if it is a POP mailbox.
3553 # If set, Mutt will delete successfully downloaded messages from the POP server
3554 # when using the <fetch-mail> function. When unset, Mutt will download messages
3555 # but also leave them on the POP server.
3564 # The name of your POP server for the <fetch-mail> function. You can also specify
3565 # an alternative port, username and password, i.e.:
3567 # [pop[s]://][username[:password]@]popserver[:port]
3569 # where “[...]” denotes an optional part.
3578 # If this variable is set, mutt will try to use the “LAST” POP command for
3579 # retrieving only unread messages from the POP server when using the <fetch-mail>
3584 # 3.248. pop_oauth_refresh_command
3589 # The command to run to generate an OAUTH refresh token for authorizing your
3590 # connection to your POP server. This command will be run on every connection
3591 # attempt that uses the OAUTHBEARER authentication mechanism. See “oauth” for
3601 # Specifies the password for your POP account. If unset, Mutt will prompt you for
3602 # your password when you open a POP mailbox.
3604 # Warning: you should only use this option when you are on a fairly secure
3605 # machine, because the superuser can read your muttrc even if you are the only
3606 # one who can read the file.
3610 # 3.250. pop_reconnect
3615 # Controls whether or not Mutt will try to reconnect to the POP server if the
3616 # connection is lost.
3625 # Your login name on the POP server.
3627 # This variable defaults to your user name on the local machine.
3631 # 3.252. post_indent_string
3636 # Similar to the $attribution variable, Mutt will append this string after the
3637 # inclusion of a message which is being replied to. For a full listing of defined
3638 # printf(3)-like sequences see the section on $index_format.
3647 # Controls whether or not messages are saved in the $postponed mailbox when you
3648 # elect not to send immediately.
3650 # Also see the $recall variable.
3657 # Default: “~/postponed”
3659 # Mutt allows you to indefinitely “postpone sending a message” which you are
3660 # editing. When you choose to postpone a message, Mutt saves it in the mailbox
3661 # specified by this variable.
3663 # Also see the $postpone variable.
3665 set postponed="=drafts"
3668 # 3.255. postpone_encrypt
3673 # When set, postponed messages that are marked for encryption will be
3674 # self-encrypted. Mutt will first try to encrypt using the value specified in
3675 # $pgp_default_key or $smime_default_key. If those are not set, it will try the
3676 # deprecated $postpone_encrypt_as. (Crypto only)
3680 # 3.256. postpone_encrypt_as
3685 # This is a deprecated fall-back variable for $postpone_encrypt. Please use
3686 # $pgp_default_key or $smime_default_key. (Crypto only)
3695 # If set, a shell command to be executed if mutt fails to establish a connection
3696 # to the server. This is useful for setting up secure connections, e.g. with ssh
3697 # (1). If the command returns a nonzero status, mutt gives up opening the server.
3700 # set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 < /dev/null > /dev/null"
3702 # Mailbox “foo” on “mailhost.net” can now be reached as “{localhost:1234}foo”.
3704 # Note: For this example to work, you must be able to log in to the remote
3705 # machine without having to enter a password.
3714 # Controls whether or not Mutt really prints messages. This is set to “ask-no” by
3715 # default, because some people accidentally hit “p” often.
3719 # 3.259. print_command
3724 # This specifies the command pipe that should be used to print messages.
3726 set print_command="muttprint"
3729 # 3.260. print_decode
3734 # Used in connection with the <print-message> function. If this option is set,
3735 # the message is decoded before it is passed to the external command specified by
3736 # $print_command. If this option is unset, no processing will be applied to the
3737 # message when printing it. The latter setting may be useful if you are using
3738 # some advanced printer filter which is able to properly format e-mail messages
3741 # Also see $print_decode_weed, which controls whether headers will be weeded when
3746 # 3.261. print_decode_weed
3751 # For <print-message>, when $print_decode is set, this further controls whether
3752 # Mutt will weed headers.
3756 # 3.262. print_split
3761 # Used in connection with the <print-message> function. If this option is set,
3762 # the command specified by $print_command is executed once for each message which
3763 # is to be printed. If this option is unset, the command specified by
3764 # $print_command is executed only once, and all the messages are concatenated,
3765 # with a form feed as the message separator.
3767 # Those who use the enscript(1) program's mail-printing mode will most likely
3768 # want to set this option.
3773 # 3.263. prompt_after
3778 # If you use an external $pager, setting this variable will cause Mutt to prompt
3779 # you for a command when the pager exits rather than returning to the index menu.
3780 # If unset, Mutt will return to the index menu when the external pager exits.
3784 # 3.264. query_command
3789 # This specifies the command Mutt will use to make external address queries. The
3790 # string may contain a “%s”, which will be substituted with the query string the
3791 # user types. Mutt will add quotes around the string substituted for “%s”
3792 # automatically according to shell quoting rules, so you should avoid adding your
3793 # own. If no “%s” is found in the string, Mutt will append the user's query to
3794 # the end of the string. See “query” for more information.
3796 set query_command="lbdbq"
3799 # 3.265. query_format
3802 # Default: “%4c %t %-25.25a %-25.25n %?e?(%e)?”
3804 # This variable describes the format of the “query” menu. The following printf(3)
3805 # -style sequences are understood:
3807 # ┌───┬─────────────────────────────────────────────────────┐
3808 # │%a │destination address │
3809 # ├───┼─────────────────────────────────────────────────────┤
3810 # │%c │current entry number │
3811 # ├───┼─────────────────────────────────────────────────────┤
3812 # │%e │extra information * │
3813 # ├───┼─────────────────────────────────────────────────────┤
3814 # │%n │destination name │
3815 # ├───┼─────────────────────────────────────────────────────┤
3816 # │%t │“*” if current entry is tagged, a space otherwise │
3817 # ├───┼─────────────────────────────────────────────────────┤
3818 # │%>X│right justify the rest of the string and pad with “X”│
3819 # ├───┼─────────────────────────────────────────────────────┤
3820 # │%|X│pad to the end of the line with “X” │
3821 # ├───┼─────────────────────────────────────────────────────┤
3822 # │%*X│soft-fill with character “X” as pad │
3823 # └───┴─────────────────────────────────────────────────────┘
3825 # For an explanation of “soft-fill”, see the $index_format documentation.
3827 # * = can be optionally printed if nonzero, see the $status_format documentation.
3836 # This variable controls whether “quit” and “exit” actually quit from mutt. If
3837 # this option is set, they do quit, if it is unset, they have no effect, and if
3838 # it is set to ask-yes or ask-no, you are prompted for confirmation when you try
3843 # 3.267. quote_regexp
3845 # Type: regular expression
3846 # Default: “^([ t]*[|>:}#])+”
3848 # A regular expression used in the internal pager to determine quoted sections of
3849 # text in the body of a message. Quoted text may be filtered out using the
3850 # <toggle-quoted> command, or colored according to the “color quoted” family of
3853 # Higher levels of quoting may be colored differently (“color quoted1”, “color
3854 # quoted2”, etc.). The quoting level is determined by removing the last character
3855 # from the matched text and recursively reapplying the regular expression until
3856 # it fails to produce a match.
3858 # Match detection may be overridden by the $smileys regular expression.
3867 # If set to a value greater than 0, Mutt will display which message it is
3868 # currently on when reading a mailbox or when performing search actions such as
3869 # search and limit. The message is printed after this many messages have been
3870 # read or searched (e.g., if set to 25, Mutt will print a message when it is at
3871 # message 25, and then again when it gets to message 50). This variable is meant
3872 # to indicate progress when reading or searching large mailboxes which may take
3873 # some time. When set to 0, only a single message will appear before the reading
3876 # Also see the $write_inc, $net_inc and $time_inc variables and the “tuning”
3877 # section of the manual for performance considerations.
3886 # If set, all folders are opened in read-only mode.
3895 # This variable specifies what “real” or “personal” name should be used when
3898 # By default, this is the GECOS field from /etc/passwd. Note that this variable
3899 # will not be used when the user has set a real name in the $from variable.
3908 # Controls whether or not Mutt recalls postponed messages when composing a new
3911 # Setting this variable to yes is not generally useful, and thus not recommended.
3912 # Note that the <recall-message> function can be used to manually recall
3913 # postponed messages.
3915 # Also see $postponed variable.
3925 # This specifies the file into which your outgoing messages should be appended.
3926 # (This is meant as the primary method for saving a copy of your messages, but
3927 # another way to do this is using the “my_hdr” command to create a “Bcc:” field
3928 # with your email address in it.)
3930 # The value of $record is overridden by the $force_name and $save_name variables,
3931 # and the “fcc-hook” command. Also see $copy and $write_bcc.
3933 # Multiple mailboxes may be specified if $fcc_delimiter is set to a string
3939 # 3.273. reflow_space_quotes
3944 # This option controls how quotes from format=flowed messages are displayed in
3945 # the pager and when replying (with $text_flowed unset). When set, this option
3946 # adds spaces after each level of quote marks, turning ">>>foo" into "> > > foo".
3948 # Note: If $reflow_text is unset, this option has no effect. Also, this option
3949 # does not affect replies when $text_flowed is set.
3953 # 3.274. reflow_text
3958 # When set, Mutt will reformat paragraphs in text/plain parts marked format=
3959 # flowed. If unset, Mutt will display paragraphs unaltered from how they appear
3960 # in the message body. See RFC3676 for details on the format=flowed format.
3962 # Also see $reflow_wrap, and $wrap.
3966 # 3.275. reflow_wrap
3971 # This variable controls the maximum paragraph width when reformatting text/plain
3972 # parts when $reflow_text is set. When the value is 0, paragraphs will be wrapped
3973 # at the terminal's right margin. A positive value sets the paragraph width
3974 # relative to the left margin. A negative value set the paragraph width relative
3975 # to the right margin.
3982 # 3.276. reply_regexp
3984 # Type: regular expression
3985 # Default: “^(re([[0-9]+])*|aw):[ t]*”
3987 # A regular expression used to recognize reply messages when threading and
3988 # replying. The default value corresponds to the English "Re:" and the German
3991 set reply_regexp="^((re([-[(]?[[:digit:]]+[)]]?)?|a(nt)?w(ort)?|wg|s(gkb|v)):[[:space:]]*)+"
3999 # If unset and you are replying to a message sent by you, Mutt will assume that
4000 # you want to reply to the recipients of that message rather than to yourself.
4002 # Also see the “alternates” command.
4011 # If set, when replying to a message, Mutt will use the address listed in the
4012 # Reply-to: header as the recipient of the reply. If unset, it will use the
4013 # address in the From: header field instead. This option is useful for reading a
4014 # mailing list that sets the Reply-To: header field to the list address and you
4015 # want to send a private message to the author of a message.
4024 # When set, the cursor will be automatically advanced to the next (possibly
4025 # undeleted) message whenever a command that modifies the current message is
4030 # 3.280. resume_draft_files
4035 # If set, draft files (specified by -H on the command line) are processed
4036 # similarly to when resuming a postponed message. Recipients are not prompted
4037 # for; send-hooks are not evaluated; no alias expansion takes place; user-defined
4038 # headers and signatures are not added to the message.
4042 # 3.281. resume_edited_draft_files
4047 # If set, draft files previously edited (via -E -H on the command line) will have
4048 # $resume_draft_files automatically set when they are used as a draft file again.
4050 # The first time a draft file is saved, mutt will add a header,
4051 # X-Mutt-Resume-Draft to the saved file. The next time the draft file is read in,
4052 # if mutt sees the header, it will set $resume_draft_files.
4054 # This option is designed to prevent multiple signatures, user-defined headers,
4055 # and other processing effects from being made multiple times to the draft file.
4059 # 3.282. reverse_alias
4064 # This variable controls whether or not Mutt will display the “personal” name
4065 # from your aliases in the index menu if it finds an alias that matches the
4066 # message's sender. For example, if you have the following alias:
4068 # alias juser abd30425@somewhere.net (Joe User)
4070 # and then you receive mail which contains the following header:
4072 # From: abd30425@somewhere.net
4074 # It would be displayed in the index menu as “Joe User” instead of “
4075 # abd30425@somewhere.net.” This is useful when the person's e-mail address is not
4080 # 3.283. reverse_name
4085 # It may sometimes arrive that you receive mail to a certain machine, move the
4086 # messages to another machine, and reply to some the messages from there. If this
4087 # variable is set, the default From: line of the reply messages is built using
4088 # the address where you received the messages you are replying to if that address
4089 # matches your “alternates”. If the variable is unset, or the address that would
4090 # be used doesn't match your “alternates”, the From: line will use your address
4091 # on the current machine.
4093 # Also see the “alternates” command and $reverse_realname.
4095 set reverse_name=yes
4098 # 3.284. reverse_realname
4103 # This variable fine-tunes the behavior of the $reverse_name feature.
4105 # When it is unset, Mutt will remove the real name part of a matching address.
4106 # This allows the use of the email address without having to also use what the
4107 # sender put in the real name field.
4109 # When it is set, Mutt will use the matching address as-is.
4111 # In either case, a missing real name will be filled in afterwards using the
4112 # value of $realname.
4116 # 3.285. rfc2047_parameters
4121 # When this variable is set, Mutt will decode RFC2047-encoded MIME parameters.
4122 # You want to set this variable when mutt suggests you to save attachments to
4125 # =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
4127 # When this variable is set interactively, the change won't be active until you
4130 # Note that this use of RFC2047's encoding is explicitly prohibited by the
4131 # standard, but nevertheless encountered in the wild.
4133 # Also note that setting this parameter will not have the effect that mutt
4134 # generates this kind of encoding. Instead, mutt will unconditionally use the
4135 # encoding specified in RFC2231.
4137 set rfc2047_parameters=yes
4140 # 3.286. save_address
4145 # If set, mutt will take the sender's full address when choosing a default folder
4146 # for saving a mail. If $save_name or $force_name is set too, the selection of
4147 # the Fcc folder will be changed as well.
4156 # When unset, mailboxes which contain no saved messages will be removed when
4157 # closed (the exception is $spoolfile which is never removed). If set, mailboxes
4158 # are never removed.
4160 # Note: This only applies to mbox and MMDF folders, Mutt does not delete MH and
4161 # Maildir directories.
4165 # 3.288. save_history
4170 # This variable controls the size of the history (per category) saved in the
4171 # $history_file file.
4173 set save_history=100
4181 # This variable controls how copies of outgoing messages are saved. When set, a
4182 # check is made to see if a mailbox specified by the recipient address exists
4183 # (this is done by searching for a mailbox in the $folder directory with the
4184 # username part of the recipient address). If the mailbox exists, the outgoing
4185 # message will be saved to that mailbox, otherwise the message is saved to the
4188 # Also see the $force_name variable.
4197 # When this variable is unset, scoring is turned off. This can be useful to
4198 # selectively disable scoring for certain folders when the
4199 # $score_threshold_delete variable and related are used.
4203 # 3.291. score_threshold_delete
4208 # Messages which have been assigned a score equal to or lower than the value of
4209 # this variable are automatically marked for deletion by mutt. Since mutt scores
4210 # are always greater than or equal to zero, the default setting of this variable
4211 # will never mark a message for deletion.
4215 # 3.292. score_threshold_flag
4220 # Messages which have been assigned a score greater than or equal to this
4221 # variable's value are automatically marked "flagged".
4225 # 3.293. score_threshold_read
4230 # Messages which have been assigned a score equal to or lower than the value of
4231 # this variable are automatically marked as read by mutt. Since mutt scores are
4232 # always greater than or equal to zero, the default setting of this variable will
4233 # never mark a message read.
4237 # 3.294. search_context
4242 # For the pager, this variable specifies the number of lines shown before search
4243 # results. By default, search results will be top-aligned.
4245 set search_context=5
4248 # 3.295. send_charset
4251 # Default: “us-ascii:iso-8859-1:utf-8”
4253 # A colon-delimited list of character sets for outgoing messages. Mutt will use
4254 # the first character set into which the text can be converted exactly. If your
4255 # $charset is not “iso-8859-1” and recipients may not understand “UTF-8”, it is
4256 # advisable to include in the list an appropriate widely used standard character
4257 # set (such as “iso-8859-2”, “koi8-r” or “iso-2022-jp”) either instead of or
4258 # after “iso-8859-1”.
4260 # In case the text cannot be converted into one of these exactly, mutt uses
4261 # $charset as a fallback.
4263 set send_charset="utf-8"
4266 # 3.296. send_multipart_alternative
4271 # If set, Mutt will generate a multipart/alternative container and an alternative
4272 # part using the filter script specified in $send_multipart_alternative_filter.
4273 # See the section “MIME Multipart/Alternative” (alternative-order).
4275 # Note that enabling multipart/alternative is not compatible with inline PGP
4276 # encryption. Mutt will prompt to use PGP/MIME in that case.
4278 set send_multipart_alternative=yes
4281 # 3.297. send_multipart_alternative_filter
4286 # This specifies a filter script, which will convert the main (composed) message
4287 # of the email to an alternative format. The message will be piped to the
4288 # filter's stdin. The expected output of the filter is the generated mime type,
4289 # e.g. text/html, followed by a blank line, and then the converted content. See
4290 # the section “MIME Multipart/Alternative” (alternative-order).
4292 set send_multipart_alternative_filter=$my_confdir/markdown2html
4298 # Default: “/usr/sbin/sendmail -oem -oi”
4300 # Specifies the program and arguments used to deliver mail sent by Mutt. Mutt
4301 # expects that the specified program interprets additional arguments as recipient
4302 # addresses. Mutt appends all recipients after adding a -- delimiter (if not
4303 # already present). Additional flags, such as for $use_8bitmime,
4304 # $use_envelope_from, $dsn_notify, or $dsn_return will be added before the
4307 # See also: $write_bcc.
4309 set sendmail="$my_confdir/sendmail"
4312 # 3.299. sendmail_wait
4317 # Specifies the number of seconds to wait for the $sendmail process to finish
4318 # before giving up and putting delivery in the background.
4320 # Mutt interprets the value of this variable as follows:
4322 # ┌──┬──────────────────────────────────────────────────────────────────┐
4323 # │>0│number of seconds to wait for sendmail to finish before continuing│
4324 # ├──┼──────────────────────────────────────────────────────────────────┤
4325 # │0 │wait forever for sendmail to finish │
4326 # ├──┼──────────────────────────────────────────────────────────────────┤
4327 # │<0│always put sendmail in the background without waiting │
4328 # └──┴──────────────────────────────────────────────────────────────────┘
4330 # Note that if you specify a value other than 0, the output of the child process
4331 # will be put in a temporary file. If there is some error, you will be informed
4332 # as to where to find the output.
4341 # Command to use when spawning a subshell. By default, the user's login shell
4342 # from /etc/passwd is used.
4346 # 3.301. sidebar_delim_chars
4351 # This contains the list of characters which you would like to treat as folder
4352 # separators for displaying paths in the sidebar.
4354 # Local mail is often arranged in directories: `dir1/dir2/mailbox'.
4356 # set sidebar_delim_chars='/'
4358 # IMAP mailboxes are often named: `folder1.folder2.mailbox'.
4360 # set sidebar_delim_chars='.'
4362 # See also: $sidebar_short_path, $sidebar_folder_indent, $sidebar_indent_string.
4366 # 3.302. sidebar_divider_char
4371 # This specifies the characters to be drawn between the sidebar (when visible)
4372 # and the other Mutt panels. ASCII and Unicode line-drawing characters are
4375 set sidebar_divider_char=" "
4378 # 3.303. sidebar_folder_indent
4383 # Set this to indent mailboxes in the sidebar.
4385 # See also: $sidebar_short_path, $sidebar_indent_string, $sidebar_delim_chars.
4387 set sidebar_folder_indent=yes
4390 # 3.304. sidebar_format
4393 # Default: “%B%* %n”
4395 # This variable allows you to customize the sidebar display. This string is
4396 # similar to $index_format, but has its own set of printf(3)-like sequences:
4398 # ┌───┬─────────────────────────────────────────────────────────────────────────┐
4399 # │%B │Name of the mailbox │
4400 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4401 # │%S │* Size of mailbox (total number of messages) │
4402 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4403 # │%N │* Number of unread messages in the mailbox │
4404 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4405 # │%n │N if mailbox has new mail, blank otherwise │
4406 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4407 # │%F │* Number of Flagged messages in the mailbox │
4408 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4409 # │%! │“!” : one flagged message; “!!” : two flagged messages; “n!” : n flagged │
4410 # │ │messages (for n > 2). Otherwise prints nothing. │
4411 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4412 # │%d │* @ Number of deleted messages │
4413 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4414 # │%L │* @ Number of messages after limiting │
4415 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4416 # │%t │* @ Number of tagged messages │
4417 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4418 # │%>X│right justify the rest of the string and pad with “X” │
4419 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4420 # │%|X│pad to the end of the line with “X” │
4421 # ├───┼─────────────────────────────────────────────────────────────────────────┤
4422 # │%*X│soft-fill with character “X” as pad │
4423 # └───┴─────────────────────────────────────────────────────────────────────────┘
4425 # * = Can be optionally printed if nonzero @ = Only applicable to the current
4428 # In order to use %S, %N, %F, and %!, $mail_check_stats must be set. When thus
4429 # set, a suggested value for this option is "%B%?F? [%F]?%* %?N?%N/?%S".
4431 set sidebar_format="%B%?F? [%F]?%* %?N?%N/?%S"
4434 # 3.305. sidebar_indent_string
4439 # This specifies the string that is used to indent mailboxes in the sidebar. It
4440 # defaults to two spaces.
4442 # See also: $sidebar_short_path, $sidebar_folder_indent, $sidebar_delim_chars.
4444 set sidebar_indent_string=" "
4447 # 3.306. sidebar_new_mail_only
4452 # When set, the sidebar will only display mailboxes containing new, or flagged,
4455 # See also: sidebar_whitelist.
4459 # 3.307. sidebar_next_new_wrap
4464 # When set, the <sidebar-next-new> command will not stop and the end of the list
4465 # of mailboxes, but wrap around to the beginning. The <sidebar-prev-new> command
4466 # is similarly affected, wrapping around to the end of the list.
4468 set sidebar_next_new_wrap=yes
4471 # 3.308. sidebar_relative_shortpath_indent
4476 # When set, this option changes how $sidebar_short_path and
4477 # $sidebar_folder_indent perform shortening and indentation: both will look at
4478 # the previous sidebar entries and shorten/indent relative to the most recent
4481 # An example of this option set/unset for mailboxes listed in this order, with
4482 # $sidebar_short_path=yes, $sidebar_folder_indent=yes, and $sidebar_indent_string
4485 # ┌─────────┬────┬─────┐
4486 # │mailbox │set │unset│
4487 # ├─────────┼────┼─────┤
4489 # ├─────────┼────┼─────┤
4490 # │=a.b.c.d │→c.d│→→→d │
4491 # ├─────────┼────┼─────┤
4492 # │=a.b.e │→e │→→e │
4493 # └─────────┴────┴─────┘
4495 # The second line illustrates most clearly. With this option set, =a.b.c.d is
4496 # shortened relative to =a.b, becoming c.d; it is also indented one place
4497 # relative to =a.b. With this option unset =a.b.c.d is always shortened to the
4498 # last part of the mailbox, d and is indented three places, with respect to
4499 # $folder (represented by '=').
4501 # When set, the third line will also be indented and shortened relative to the
4506 # 3.309. sidebar_short_path
4511 # By default the sidebar will show the mailbox's path, relative to the $folder
4512 # variable. Setting sidebar_shortpath=yes will shorten the names relative to the
4513 # previous name. Here's an example:
4515 # ┌────────────┬─────────────┬───────────────────────────────────────────────┐
4516 # │shortpath=no│shortpath=yes│shortpath=yes, folderindent=yes, indentstr=".."│
4517 # ├────────────┼─────────────┼───────────────────────────────────────────────┤
4518 # │fruit │fruit │fruit │
4519 # ├────────────┼─────────────┼───────────────────────────────────────────────┤
4520 # │fruit.apple │apple │..apple │
4521 # ├────────────┼─────────────┼───────────────────────────────────────────────┤
4522 # │fruit.banana│banana │..banana │
4523 # ├────────────┼─────────────┼───────────────────────────────────────────────┤
4524 # │fruit.cherry│cherry │..cherry │
4525 # └────────────┴─────────────┴───────────────────────────────────────────────┘
4527 # See also: $sidebar_delim_chars, $sidebar_folder_indent, $sidebar_indent_string.
4529 set sidebar_short_path=yes
4532 # 3.310. sidebar_sort_method
4537 # Specifies how to sort mailbox entries in the sidebar. By default, the entries
4538 # are sorted alphabetically. Valid values:
4540 # • alpha (alphabetically)
4542 # • count (all message count)
4544 # • flagged (flagged message count)
4546 # • name (alphabetically)
4548 # • new (unread message count)
4550 # • path (alphabetically)
4552 # • unread (unread message count)
4556 # You may optionally use the “reverse-” prefix to specify reverse sorting order
4557 # (example: “set sidebar_sort_method=reverse-alpha”).
4559 set sidebar_sort_method=path
4562 # 3.311. sidebar_use_mailbox_shortcuts
4567 # When set, sidebar mailboxes will be displayed with mailbox shortcut prefixes "=
4570 # When unset, the sidebar will trim off a matching $folder prefix but otherwise
4571 # not use mailbox shortcuts.
4575 # 3.312. sidebar_visible
4580 # This specifies whether or not to show sidebar. The sidebar shows a list of all
4583 # See also: $sidebar_format, $sidebar_width
4585 set sidebar_visible=no
4588 # 3.313. sidebar_width
4593 # This controls the width of the sidebar. It is measured in screen columns. For
4594 # example: sidebar_width=20 could display 20 ASCII characters, or 10 Chinese
4597 set sidebar_width=20
4605 # If set, a line containing “-- ” (note the trailing space) will be inserted
4606 # before your $signature. It is strongly recommended that you not unset this
4607 # variable unless your signature contains just your name. The reason for this is
4608 # because many software packages use “-- n” to detect your signature. For
4609 # example, Mutt has the ability to highlight the signature in a different color
4610 # in the built-in pager.
4620 # If set, the signature will be included before any quoted or forwarded text. It
4621 # is strongly recommended that you do not set this variable unless you really
4622 # know what you are doing, and are prepared to take some heat from netiquette
4630 # Default: “~/.signature”
4632 # Specifies the filename of your signature, which is appended to all outgoing
4633 # messages. If the filename ends with a pipe (“|”), it is assumed that filename
4634 # is a shell command and input should be read from its standard output.
4638 # 3.317. simple_search
4641 # Default: “~f %s | ~s %s”
4643 # Specifies how Mutt should expand a simple search into a real search pattern. A
4644 # simple search is one that does not contain any of the “~” pattern modifiers.
4645 # See “patterns” for more information on search patterns.
4647 # For example, if you simply type “joe” at a search or limit prompt, Mutt will
4648 # automatically expand it to the value specified by this variable by replacing “
4649 # %s” with the supplied string. For the default value, “joe” would be expanded
4650 # to: “~f joe | ~s joe”.
4652 set simple_search="~L %s | ~s %s"
4655 # 3.318. size_show_bytes
4660 # If set, message sizes will display bytes for values less than 1 kilobyte. See
4661 # formatstrings-size.
4665 # 3.319. size_show_fractions
4670 # If set, message sizes will be displayed with a single decimal value for sizes
4671 # from 0 to 10 kilobytes and 1 to 10 megabytes. See formatstrings-size.
4675 # 3.320. size_show_mb
4680 # If set, message sizes will display megabytes for values greater than or equal
4681 # to 1 megabyte. See formatstrings-size.
4685 # 3.321. size_units_on_left
4690 # If set, message sizes units will be displayed to the left of the number. See
4691 # formatstrings-size.
4700 # Specifies time, in seconds, to pause while displaying certain informational
4701 # messages, while moving from folder to folder and after expunging messages from
4702 # the current folder. The default is to pause one second, so a value of zero for
4703 # this option suppresses the pause.
4712 # Controls the display of lines longer than the screen width in the internal
4713 # pager. If set, long lines are wrapped at a word boundary. If unset, lines are
4714 # simply wrapped at the screen edge. Also see the $markers variable.
4720 # Type: regular expression
4721 # Default: “(>From )|(:[-^]?[][)(><}{|/DP])”
4723 # The pager uses this variable to catch some common false positives of
4724 # $quote_regexp, most notably smileys and not consider a line quoted text if it
4725 # also matches $smileys. This mostly happens at the beginning of a line.
4729 # 3.325. smime_ask_cert_label
4734 # This flag controls whether you want to be asked to enter a label for a
4735 # certificate about to be added to the database or not. It is set by default. (S/
4740 # 3.326. smime_ca_location
4745 # This variable contains the name of either a directory, or a file which contains
4746 # trusted certificates for use with OpenSSL. (S/MIME only)
4750 # 3.327. smime_certificates
4755 # Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
4756 # storage and retrieval of keys by itself. This is very basic right now, and keys
4757 # and certificates are stored in two different directories, both named as the
4758 # hash-value retrieved from OpenSSL. There is an index file which contains
4759 # mailbox-address keyid pairs, and which can be manually edited. This option
4760 # points to the location of the certificates. (S/MIME only)
4762 set smime_certificates="~/.smime/certificates"
4765 # 3.328. smime_decrypt_command
4770 # This format string specifies a command which is used to decrypt application/
4771 # x-pkcs7-mime attachments.
4773 # The OpenSSL command formats have their own set of printf(3)-like sequences
4776 # ┌──┬──────────────────────────────────────────────────────────────────────────┐
4777 # │%f│Expands to the name of a file containing a message. │
4778 # ├──┼──────────────────────────────────────────────────────────────────────────┤
4779 # │%s│Expands to the name of a file containing the signature part of a multipart│
4780 # │ │/signed attachment when verifying it. │
4781 # ├──┼──────────────────────────────────────────────────────────────────────────┤
4782 # │%k│The key-pair specified with $smime_default_key │
4783 # ├──┼──────────────────────────────────────────────────────────────────────────┤
4784 # │%c│One or more certificate IDs. │
4785 # ├──┼──────────────────────────────────────────────────────────────────────────┤
4786 # │%a│The algorithm used for encryption. │
4787 # ├──┼──────────────────────────────────────────────────────────────────────────┤
4788 # │%d│The message digest algorithm specified with $smime_sign_digest_alg. │
4789 # ├──┼──────────────────────────────────────────────────────────────────────────┤
4790 # │ │CA location: Depending on whether $smime_ca_location points to a directory│
4791 # │%C│or file, this expands to “-CApath $smime_ca_location” or “-CAfile │
4792 # │ │$smime_ca_location”. │
4793 # └──┴──────────────────────────────────────────────────────────────────────────┘
4795 # For examples on how to configure these formats, see the smime.rc in the samples
4796 # / subdirectory which has been installed on your system alongside the
4797 # documentation. (S/MIME only)
4801 # 3.329. smime_decrypt_use_default_key
4806 # If set (default) this tells mutt to use the default key for decryption.
4807 # Otherwise, if managing multiple certificate-key-pairs, mutt will try to use the
4808 # mailbox-address to determine the key to use. It will ask you to supply a key,
4809 # if it can't find one. (S/MIME only)
4813 # 3.330. smime_default_key
4818 # This is the default key-pair to use for S/MIME operations, and must be set to
4819 # the keyid (the hash-value that OpenSSL generates) to work properly.
4821 # It will be used for encryption (see $postpone_encrypt and $smime_self_encrypt).
4822 # If GPGME is enabled, this is the key id displayed by gpgsm.
4824 # It will be used for decryption unless $smime_decrypt_use_default_key is unset.
4826 # It will also be used for signing unless $smime_sign_as is set.
4828 # The (now deprecated) smime_self_encrypt_as is an alias for this variable, and
4829 # should no longer be used. (S/MIME only)
4833 # 3.331. smime_encrypt_command
4838 # This command is used to create encrypted S/MIME messages.
4840 # This is a format string, see the $smime_decrypt_command command for possible
4841 # printf(3)-like sequences. (S/MIME only)
4845 # 3.332. smime_encrypt_with
4850 # This sets the algorithm that should be used for encryption. Valid choices are “
4851 # aes128”, “aes192”, “aes256”, “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”. (S/
4856 # 3.333. smime_get_cert_command
4861 # This command is used to extract X509 certificates from a PKCS7 structure.
4863 # This is a format string, see the $smime_decrypt_command command for possible
4864 # printf(3)-like sequences. (S/MIME only)
4868 # 3.334. smime_get_cert_email_command
4873 # This command is used to extract the mail address(es) used for storing X509
4874 # certificates, and for verification purposes (to check whether the certificate
4875 # was issued for the sender's mailbox).
4877 # This is a format string, see the $smime_decrypt_command command for possible
4878 # printf(3)-like sequences. (S/MIME only)
4882 # 3.335. smime_get_signer_cert_command
4887 # This command is used to extract only the signers X509 certificate from a S/MIME
4888 # signature, so that the certificate's owner may get compared to the email's “
4891 # This is a format string, see the $smime_decrypt_command command for possible
4892 # printf(3)-like sequences. (S/MIME only)
4896 # 3.336. smime_import_cert_command
4901 # This command is used to import a certificate via smime_keys.
4903 # This is a format string, see the $smime_decrypt_command command for possible
4904 # printf(3)-like sequences. (S/MIME only)
4908 # 3.337. smime_is_default
4913 # The default behavior of mutt is to use PGP on all auto-sign/encryption
4914 # operations. To override and to use OpenSSL instead this must be set. However,
4915 # this has no effect while replying, since mutt will automatically select the
4916 # same application that was used to sign/encrypt the original message. (Note that
4917 # this variable can be overridden by unsetting $crypt_autosmime.) (S/MIME only)
4926 # Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
4927 # storage and retrieval of keys/certs by itself. This is very basic right now,
4928 # and stores keys and certificates in two different directories, both named as
4929 # the hash-value retrieved from OpenSSL. There is an index file which contains
4930 # mailbox-address keyid pair, and which can be manually edited. This option
4931 # points to the location of the private keys. (S/MIME only)
4933 set smime_keys="~/.smime/keys"
4936 # 3.339. smime_pk7out_command
4941 # This command is used to extract PKCS7 structures of S/MIME signatures, in order
4942 # to extract the public X509 certificate(s).
4944 # This is a format string, see the $smime_decrypt_command command for possible
4945 # printf(3)-like sequences. (S/MIME only)
4949 # 3.340. smime_self_encrypt
4954 # When set, S/MIME encrypted messages will also be encrypted using the
4955 # certificate in $smime_default_key. (S/MIME only)
4959 # 3.341. smime_sign_as
4964 # If you have a separate key to use for signing, you should set this to the
4965 # signing key. Most people will only need to set $smime_default_key. (S/MIME
4970 # 3.342. smime_sign_command
4975 # This command is used to created S/MIME signatures of type multipart/signed,
4976 # which can be read by all mail clients.
4978 # This is a format string, see the $smime_decrypt_command command for possible
4979 # printf(3)-like sequences. NOTE: %c and %k will default to $smime_sign_as if
4980 # set, otherwise $smime_default_key. (S/MIME only)
4984 # 3.343. smime_sign_digest_alg
4989 # This sets the algorithm that should be used for the signature message digest.
4990 # Valid choices are “md5”, “sha1”, “sha224”, “sha256”, “sha384”, “sha512”. (S/
4995 # 3.344. smime_sign_opaque_command
5000 # This command is used to created S/MIME signatures of type application/
5001 # x-pkcs7-signature, which can only be handled by mail clients supporting the S/
5004 # This is a format string, see the $smime_decrypt_command command for possible
5005 # printf(3)-like sequences. (S/MIME only)
5009 # 3.345. smime_timeout
5011 # Type: number (long)
5014 # The number of seconds after which a cached passphrase will expire if not used.
5019 # 3.346. smime_verify_command
5024 # This command is used to verify S/MIME signatures of type multipart/signed.
5026 # This is a format string, see the $smime_decrypt_command command for possible
5027 # printf(3)-like sequences. (S/MIME only)
5031 # 3.347. smime_verify_opaque_command
5036 # This command is used to verify S/MIME signatures of type application/
5039 # This is a format string, see the $smime_decrypt_command command for possible
5040 # printf(3)-like sequences. (S/MIME only)
5044 # 3.348. smtp_authenticators
5049 # This is a colon-delimited list of authentication methods mutt may attempt to
5050 # use to log in to an SMTP server, in the order mutt should try them.
5051 # Authentication methods are any SASL mechanism, e.g. “digest-md5”, “gssapi” or “
5052 # cram-md5”. This option is case-insensitive. If it is “unset” (the default) mutt
5053 # will try all available methods, in order from most-secure to least-secure.
5057 # set smtp_authenticators="digest-md5:cram-md5"
5061 # 3.349. smtp_oauth_refresh_command
5066 # The command to run to generate an OAUTH refresh token for authorizing your
5067 # connection to your SMTP server. This command will be run on every connection
5068 # attempt that uses the OAUTHBEARER authentication mechanism. See “oauth” for
5078 # Specifies the password for your SMTP account. If unset, Mutt will prompt you
5079 # for your password when you first send mail via SMTP. See $smtp_url to configure
5080 # mutt to send mail via SMTP.
5082 # Warning: you should only use this option when you are on a fairly secure
5083 # machine, because the superuser can read your muttrc even if you are the only
5084 # one who can read the file.
5093 # Defines the SMTP smarthost where sent messages should relayed for delivery.
5094 # This should take the form of an SMTP URL, e.g.:
5096 # smtp[s]://[user[:pass]@]host[:port]
5098 # where “[...]” denotes an optional part. Setting this variable overrides the
5099 # value of the $sendmail variable.
5101 # Also see $write_bcc.
5110 # Specifies how to sort messages in the “index” menu. Valid values are:
5112 # • date or date-sent
5118 # • mailbox-order (unsorted)
5132 # You may optionally use the “reverse-” prefix to specify reverse sorting order
5133 # (example: “set sort=reverse-date-sent”).
5143 # Specifies how the entries in the “alias” menu are sorted. The following are
5146 # • address (sort alphabetically by email address)
5148 # • alias (sort alphabetically by alias name)
5150 # • unsorted (leave in order specified in .muttrc)
5159 # This provides a secondary sort for messages in the “index” menu, used when the
5160 # $sort value is equal for two messages.
5162 # When sorting by threads, this variable controls how threads are sorted in
5163 # relation to other threads, and how the branches of the thread trees are sorted.
5164 # This can be set to any value that $sort can, except “threads” (in that case,
5165 # mutt will just use “date-sent”). You can also specify the “last-” prefix in
5166 # addition to the “reverse-” prefix, but “last-” must come after “reverse-”. The
5167 # “last-” prefix causes messages to be sorted against its siblings by which has
5168 # the last descendant, using the rest of $sort_aux as an ordering. For instance,
5170 # set sort_aux=last-date-received
5172 # would mean that if a new message is received in a thread, that thread becomes
5173 # the last one displayed (or the first, if you have “set sort=reverse-threads”.)
5175 # Note: For reversed-threads $sort order, $sort_aux is reversed again (which is
5176 # not the right thing to do, but kept to not break any existing configuration
5179 set sort_aux=last-date-received
5182 # 3.355. sort_browser
5187 # Specifies how to sort entries in the file browser. By default, the entries are
5188 # sorted alphabetically. Valid values:
5190 # • alpha (alphabetically)
5202 # You may optionally use the “reverse-” prefix to specify reverse sorting order
5203 # (example: “set sort_browser=reverse-date”).
5212 # This variable is only useful when sorting by threads with $strict_threads unset
5213 # . In that case, it changes the heuristic mutt uses to thread messages by
5214 # subject. With $sort_re set, mutt will only attach a message as the child of
5215 # another message by subject if the subject of the child message starts with a
5216 # substring matching the setting of $reply_regexp. With $sort_re unset, mutt will
5217 # attach the message whether or not this is the case, as long as the non-
5218 # $reply_regexp parts of both messages are identical.
5222 # 3.357. spam_separator
5227 # This variable controls what happens when multiple spam headers are matched: if
5228 # unset, each successive header will overwrite any previous matches value for the
5229 # spam label. If set, each successive match will append to the previous, using
5230 # this variable's value as a separator.
5239 # If your spool mailbox is in a non-default place where Mutt cannot find it, you
5240 # can specify its location with this variable. Mutt will initially set this
5241 # variable to the value of the environment variable $MAIL or $MAILDIR if either
5244 set spoolfile="=inbox"
5247 # 3.359. ssl_ca_certificates_file
5252 # This variable specifies a file containing trusted CA certificates. Any server
5253 # certificate that is signed with one of these CA certificates is also
5254 # automatically accepted. (GnuTLS only)
5258 # set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
5260 set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt"
5263 # 3.360. ssl_client_cert
5268 # The file containing a client certificate and its associated private key.
5272 # 3.361. ssl_force_tls
5277 # If this variable is set, Mutt will require that all connections to remote
5278 # servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
5279 # server does not advertise the capability, since it would otherwise have to
5280 # abort the connection anyway. This option supersedes $ssl_starttls.
5284 # 3.362. ssl_min_dh_prime_bits
5289 # This variable specifies the minimum acceptable prime size (in bits) for use in
5290 # any Diffie-Hellman key exchange. A value of 0 will use the default from the
5291 # GNUTLS library. (GnuTLS only)
5295 # 3.363. ssl_starttls
5300 # If set (the default), mutt will attempt to use STARTTLS on servers advertising
5301 # the capability. When unset, mutt will not attempt to use STARTTLS regardless of
5302 # the server's capabilities.
5304 # Note that STARTTLS is subject to many kinds of attacks, including the ability
5305 # of a machine-in-the-middle to suppress the advertising of support. Setting
5306 # $ssl_force_tls is recommended if you rely on STARTTLS.
5310 # 3.364. ssl_use_sslv2
5315 # If set , Mutt will use SSLv2 when communicating with servers that request it.
5316 # N.B. As of 2011, SSLv2 is considered insecure, and using is inadvisable. See
5317 # https://tools.ietf.org/html/rfc6176 . (OpenSSL only)
5321 # 3.365. ssl_use_sslv3
5326 # If set , Mutt will use SSLv3 when communicating with servers that request it.
5327 # N.B. As of 2015, SSLv3 is considered insecure, and using it is inadvisable. See
5328 # https://tools.ietf.org/html/rfc7525 .
5332 # 3.366. ssl_use_tlsv1
5337 # If set , Mutt will use TLSv1.0 when communicating with servers that request it.
5338 # N.B. As of 2015, TLSv1.0 is considered insecure, and using it is inadvisable.
5339 # See https://tools.ietf.org/html/rfc7525 .
5343 # 3.367. ssl_use_tlsv1_1
5348 # If set , Mutt will use TLSv1.1 when communicating with servers that request it.
5349 # N.B. As of 2015, TLSv1.1 is considered insecure, and using it is inadvisable.
5350 # See https://tools.ietf.org/html/rfc7525 .
5354 # 3.368. ssl_use_tlsv1_2
5359 # If set , Mutt will use TLSv1.2 when communicating with servers that request it.
5363 # 3.369. ssl_use_tlsv1_3
5368 # If set , Mutt will use TLSv1.3 when communicating with servers that request it.
5372 # 3.370. ssl_usesystemcerts
5377 # If set to yes, mutt will use CA certificates in the system-wide certificate
5378 # store when checking if a server certificate is signed by a trusted CA. (OpenSSL
5383 # 3.371. ssl_verify_dates
5388 # If set (the default), mutt will not automatically accept a server certificate
5389 # that is either not yet valid or already expired. You should only unset this for
5390 # particular known hosts, using the <account-hook> function.
5394 # 3.372. ssl_verify_host
5399 # If set (the default), mutt will not automatically accept a server certificate
5400 # whose host name does not match the host used in your folder URL. You should
5401 # only unset this for particular known hosts, using the <account-hook> function.
5405 # 3.373. ssl_verify_partial_chains
5410 # This option should not be changed from the default unless you understand what
5413 # Setting this variable to yes will permit verifying partial certification
5414 # chains, i. e. a certificate chain where not the root, but an intermediate
5415 # certificate CA, or the host certificate, are marked trusted (in
5416 # $certificate_file), without marking the root signing CA as trusted.
5418 # (OpenSSL 1.0.2b and newer only).
5422 # 3.374. ssl_ciphers
5427 # Contains a colon-separated list of ciphers to use when using SSL. For OpenSSL,
5428 # see ciphers(1) for the syntax of the string.
5430 # For GnuTLS, this option will be used in place of "NORMAL" at the start of the
5431 # priority string. See gnutls_priority_init(3) for the syntax and more details.
5432 # (Note: GnuTLS version 2.1.7 or higher is required.)
5436 # 3.375. status_chars
5441 # Controls the characters used by the “%r” indicator in $status_format. The first
5442 # character is used when the mailbox is unchanged. The second is used when the
5443 # mailbox has been changed, and it needs to be resynchronized. The third is used
5444 # if the mailbox is in read-only mode, or if the mailbox will not be written when
5445 # exiting that mailbox (You can toggle whether to write changes to a mailbox with
5446 # the <toggle-write> operation, bound by default to “%”). The fourth is used to
5447 # indicate that the current folder has been opened in attach- message mode
5448 # (Certain operations like composing a new mail, replying, forwarding, etc. are
5449 # not permitted in this mode).
5453 # 3.376. status_format
5455 # Type: string (localized)
5456 # Default: “-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F?
5457 # Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?B? Back:%B?%?l? %l?]---(%s/%S)
5460 # Controls the format of the status line displayed in the “index” menu. This
5461 # string is similar to $index_format, but has its own set of printf(3)-like
5464 # ┌───┬─────────────────────────────────────────────────────────────────────────┐
5465 # │%b │number of mailboxes with new mail * │
5466 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5467 # │%B │number of backgrounded editing sessions * │
5468 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5469 # │%d │number of deleted messages * │
5470 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5471 # │%f │the full pathname of the current mailbox │
5472 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5473 # │%F │number of flagged messages * │
5474 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5475 # │%h │local hostname │
5476 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5477 # │%l │size (in bytes) of the current mailbox (see formatstrings-size) * │
5478 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5479 # │%L │size (in bytes) of the messages shown (i.e., which match the current │
5480 # │ │limit) (see formatstrings-size) * │
5481 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5482 # │%m │the number of messages in the mailbox * │
5483 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5484 # │%M │the number of messages shown (i.e., which match the current limit) * │
5485 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5486 # │%n │number of new messages in the mailbox * │
5487 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5488 # │%o │number of old unread messages * │
5489 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5490 # │%p │number of postponed messages * │
5491 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5492 # │%P │percentage of the way through the index │
5493 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5494 # │%r │modified/read-only/won't-write/attach-message indicator, according to │
5495 # │ │$status_chars │
5496 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5497 # │%R │number of read messages * │
5498 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5499 # │%s │current sorting mode ($sort) │
5500 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5501 # │%S │current aux sorting method ($sort_aux) │
5502 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5503 # │%t │number of tagged messages * │
5504 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5505 # │%u │number of unread messages * │
5506 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5507 # │%v │Mutt version string │
5508 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5509 # │%V │currently active limit pattern, if any * │
5510 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5511 # │%>X│right justify the rest of the string and pad with “X” │
5512 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5513 # │%|X│pad to the end of the line with “X” │
5514 # ├───┼─────────────────────────────────────────────────────────────────────────┤
5515 # │%*X│soft-fill with character “X” as pad │
5516 # └───┴─────────────────────────────────────────────────────────────────────────┘
5518 # For an explanation of “soft-fill”, see the $index_format documentation.
5520 # * = can be optionally printed if nonzero
5522 # Some of the above sequences can be used to optionally print a string if their
5523 # value is nonzero. For example, you may only want to see the number of flagged
5524 # messages if such messages exist, since zero is not particularly meaningful. To
5525 # optionally print a string based upon one of the above sequences, the following
5526 # construct is used:
5528 # %?<sequence_char>?<optional_string>?
5530 # where sequence_char is a character from the table above, and optional_string is
5531 # the string you would like printed if sequence_char is nonzero. optional_string
5532 # may contain other sequences as well as normal text, but you may not nest
5535 # Here is an example illustrating how to optionally print the number of new
5536 # messages in a mailbox:
5538 # %?n?%n new messages.?
5540 # You can also switch between two strings using the following construct:
5542 # %?<sequence_char>?<if_string>&<else_string>?
5544 # If the value of sequence_char is non-zero, if_string will be expanded,
5545 # otherwise else_string will be expanded.
5547 # You can force the result of any printf(3)-like sequence to be lowercase by
5548 # prefixing the sequence character with an underscore (“_”) sign. For example, if
5549 # you want to display the local hostname in lowercase, you would use: “%_h”.
5551 # If you prefix the sequence character with a colon (“:”) character, mutt will
5552 # replace any dots in the expansion by underscores. This might be helpful with
5553 # IMAP folders that don't like dots in folder names.
5555 set status_format=" %r %f [m:%?M?%M/?%m%?n? n:%n?%?o? o:%o?%?d? d:%d?%?F? f:%F?%?t? t:%t?%?p? p:%p?%?b? i:%b?%?l? %l?] %?V?%V ?(%s/%S) %> (%P) "
5558 # 3.377. status_on_top
5563 # Setting this variable causes the “status bar” to be displayed on the first line
5564 # of the screen rather than near the bottom. If $help is set, too it'll be placed
5569 # 3.378. strict_threads
5574 # If set, threading will only make use of the “In-Reply-To” and “References:”
5575 # fields when you $sort by message threads. By default, messages with the same
5576 # subject are grouped together in “pseudo threads.”. This may not always be
5577 # desirable, such as in a personal mailbox where you might have several unrelated
5578 # messages with the subjects like “hi” which will get grouped together. See also
5579 # $sort_re for a less drastic way of controlling this behavior.
5581 set strict_threads=yes
5589 # When unset, mutt won't stop when the user presses the terminal's susp key,
5590 # usually “^Z”. This is useful if you run mutt inside an xterm using a command
5591 # like “xterm -e mutt”.
5595 # 3.380. text_flowed
5600 # When set, mutt will generate “format=flowed” bodies with a content type of “
5601 # text/plain; format=flowed”. This format is easier to handle for some mailing
5602 # software, and generally just looks like ordinary text. To actually make use of
5603 # this format's features, you'll need support in your editor.
5605 # The option only controls newly composed messages. Postponed messages, resent
5606 # messages, and draft messages (via -H on the command line) will use the
5607 # content-type of the source message.
5609 # Note that $indent_string is ignored when this option is set.
5614 # 3.381. thorough_search
5619 # Affects the ~b and ~h search operations described in section “patterns”. If set
5620 # , the headers and body/attachments of messages to be searched are decoded
5621 # before searching. If unset, messages are searched as they appear in the folder.
5623 # Users searching attachments or for non-ASCII characters should set this value
5624 # because decoding also includes MIME parsing/decoding and possible character set
5625 # conversions. Otherwise mutt will attempt to match against the raw message
5626 # received (for example quoted-printable encoded or with encoded headers) which
5627 # may lead to incorrect search results.
5629 set thorough_search=yes
5632 # 3.382. thread_received
5637 # When set, mutt uses the date received rather than the date sent to thread
5638 # messages by subject.
5640 set thread_received=yes
5648 # When set, the internal-pager will pad blank lines to the bottom of the screen
5649 # with a tilde (“~”).
5659 # Along with $read_inc, $write_inc, and $net_inc, this variable controls the
5660 # frequency with which progress updates are displayed. It suppresses updates less
5661 # than $time_inc milliseconds apart. This can improve throughput on systems with
5662 # slow terminals, or when running mutt on a remote system.
5664 # Also see the “tuning” section of the manual for performance considerations.
5674 # When Mutt is waiting for user input either idling in menus or in an interactive
5675 # prompt, Mutt would block until input is present. Depending on the context, this
5676 # would prevent certain operations from working, like checking for new mail or
5677 # keeping an IMAP connection alive.
5679 # This variable controls how many seconds Mutt will at most wait until it aborts
5680 # waiting for input, performs these operations and continues to wait for input.
5682 # A value of zero or less will cause Mutt to never time out.
5691 # This variable allows you to specify where Mutt will place its temporary files
5692 # needed for displaying and composing messages. If this variable is not set, the
5693 # environment variable $TMPDIR is used. If $TMPDIR is not set then “/var/tmp” is
5703 # Controls the character used to indicate mail addressed to you. The first
5704 # character is the one used when the mail is not addressed to your address. The
5705 # second is used when you are the only recipient of the message. The third is
5706 # when your address appears in the “To:” header field, but you are not the only
5707 # recipient of the message. The fourth character is used when your address is
5708 # specified in the “Cc:” header field, but you are not the only recipient. The
5709 # fifth character is used to indicate mail that was sent by you. The sixth
5710 # character is used to indicate when a mail was sent to a mailing-list you
5720 # If set, this variable specifies the path of the trash folder where the mails
5721 # marked for deletion will be moved, instead of being irremediably purged.
5723 # NOTE: When you delete a message in the trash folder, it is really deleted, so
5724 # that you have a way to clean the trash.
5728 # 3.389. ts_icon_format
5730 # Type: string (localized)
5731 # Default: “M%?n?AIL&ail?”
5733 # Controls the format of the icon title, as long as “$ts_enabled” is set. This
5734 # string is identical in formatting to the one used by “$status_format”.
5743 # Controls whether mutt tries to set the terminal status line and icon name. Most
5744 # terminal emulators emulate the status line in the window title.
5749 # 3.391. ts_status_format
5751 # Type: string (localized)
5752 # Default: “Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?”
5754 # Controls the format of the terminal status line (or window title), provided
5755 # that “$ts_enabled” has been set. This string is identical in formatting to the
5756 # one used by “$status_format”.
5758 set ts_status_format="[`tty|sed -re 's,.+pts/,,'`]mutt@%h%r %f%?V?[%V]&?"
5766 # Setting this variable will cause mutt to open a pipe to a command instead of a
5767 # raw socket. You may be able to use this to set up preauthenticated connections
5768 # to your IMAP/POP3/SMTP server. Example:
5770 # set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
5772 # Note: For this example to work you must be able to log in to the remote machine
5773 # without having to enter a password.
5775 # When set, Mutt uses the tunnel for all remote connections. Please see “
5776 # account-hook” in the manual for how to use different tunnel commands per
5781 # 3.393. tunnel_is_secure
5786 # When set, Mutt will assume the $tunnel connection does not need STARTTLS to be
5787 # enabled. It will also allow IMAP PREAUTH server responses inside a tunnel to
5788 # proceed. This is appropriate if $tunnel uses ssh or directly invokes the server
5791 # When unset, Mutt will negotiate STARTTLS according to the ssl_starttls and
5792 # ssl_force_tls variables. If ssl_force_tls is set, Mutt will abort connecting if
5793 # an IMAP server responds with PREAUTH. This setting is appropriate if $tunnel
5794 # does not provide security and could be tampered with by attackers.
5798 # 3.394. uncollapse_jump
5803 # When set, Mutt will jump to the next unread message, if any, when the current
5804 # thread is uncollapsed.
5808 # 3.395. uncollapse_new
5813 # When set, Mutt will automatically uncollapse any collapsed thread that receives
5814 # a new message. When unset, collapsed threads will remain collapsed. the
5815 # presence of the new message will still affect index sorting, though.
5819 # 3.396. use_8bitmime
5824 # Warning: do not set this variable unless you are using a version of sendmail
5825 # which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be
5826 # able to send mail.
5828 # When set, Mutt will invoke $sendmail with the -B8BITMIME flag when sending
5829 # 8-bit messages to enable ESMTP negotiation.
5838 # When set, Mutt will qualify all local addresses (ones without the “@host”
5839 # portion) with the value of $hostname. If unset, no addresses will be qualified.
5843 # 3.398. use_envelope_from
5848 # When set, mutt will set the envelope sender of the message. If
5849 # $envelope_from_address is set, it will be used as the sender address. If unset,
5850 # mutt will attempt to derive the sender from the “From:” header.
5852 # Note that this information is passed to sendmail command using the -f command
5853 # line switch. Therefore setting this option is not useful if the $sendmail
5854 # variable already contains -f or if the executable pointed to by $sendmail
5855 # doesn't support the -f switch.
5857 set use_envelope_from=yes
5865 # When set, Mutt will generate the “From:” header field when sending messages. If
5866 # unset, no “From:” header field will be generated unless the user explicitly
5867 # sets one using the “my_hdr” command.
5876 # When set, Mutt will look for IPv6 addresses of hosts it tries to contact. If
5877 # this option is unset, Mutt will restrict itself to IPv4 addresses. Normally,
5878 # the default should work.
5887 # When set, mutt will add a “User-Agent:” header to outgoing messages, indicating
5888 # which version of mutt was used for composing them.
5897 # Specifies the visual editor to invoke when the “~v” command is given in the
5907 # Controls whether Mutt will ask you to press a key after an external command has
5908 # been invoked by these functions: <shell-escape>, <pipe-message>, <pipe-entry>,
5909 # <print-message>, and <print-entry> commands.
5911 # It is also used when viewing attachments with “auto_view”, provided that the
5912 # corresponding mailcap entry has a needsterminal flag, and the external program
5915 # When set, Mutt will always ask for a key. When unset, Mutt will wait for a key
5916 # only if the external command returned a non-zero status.
5926 # When set, mutt will weed headers when displaying, forwarding, or replying to
5929 # Also see $copy_decode_weed, $pipe_decode_weed, $print_decode_weed.
5938 # When set to a positive value, mutt will wrap text at $wrap characters. When set
5939 # to a negative value, mutt will wrap text so that there are $wrap characters of
5940 # empty space on the right side of the terminal. Setting it to zero makes mutt
5941 # wrap at the terminal width.
5943 # Also see $reflow_wrap.
5945 set wrap=$reflow_wrap
5948 # 3.406. wrap_headers
5953 # This option specifies the number of characters to use for wrapping an outgoing
5954 # message's headers. Allowed values are between 78 and 998 inclusive.
5956 # Note: This option usually shouldn't be changed. RFC5233 recommends a line
5957 # length of 78 (the default), so please only change this setting when you know
5958 # what you're doing.
5962 # 3.407. wrap_search
5967 # Controls whether searches wrap around the end.
5969 # When set, searches will wrap around the first (or last) item. When unset,
5970 # incremental searches will not wrap.
5979 # (DEPRECATED) Equivalent to setting $wrap with a negative value.
5988 # Controls whether mutt writes out the “Bcc:” header when preparing messages to
5989 # be sent. Some MTAs, such as Exim and Courier, do not strip the “Bcc:” header;
5990 # so it is advisable to leave this unset unless you have a particular need for
5991 # the header to be in the sent message.
5993 # If mutt is set to deliver directly via SMTP (see $smtp_url), this option does
5994 # nothing: mutt will never write out the “Bcc:” header in this case.
5996 # Note this option only affects the sending of messages. Fcc'ed copies of a
5997 # message will always contain the “Bcc:” header if one exists.
5999 # On Debian systems, exim4 and postfix strip BCC headers by default. The above
6000 # warning applies to exim3 users, see /etc/Muttrc.
6009 # When writing a mailbox, a message will be printed every $write_inc messages to
6010 # indicate progress. If set to 0, only a single message will be displayed before
6011 # writing a mailbox.
6013 # Also see the $read_inc, $net_inc and $time_inc variables and the “tuning”
6014 # section of the manual for performance considerations.
6017 # vim:sw=12:noet:sts=12:ts=12:ft=muttrc