1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2 <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Mutt E-Mail Client</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="description" content="All mail clients suck. This one just sucks less. -me, circa 1995" /><style xmlns="" type="text/css">
3 body { margin-left:2%; margin-right:2%; font-family:serif; }
4 .toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
5 h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
6 em.replaceable code { font-family:sans-serif; }
7 p { text-align:justify; }
8 div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
9 .email, .email a { font-family:monospace; }
10 div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
11 div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
12 div.table-contents table th {
13 font-family:sans-serif;
18 pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
19 div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
20 div.note h3:after { content: ":" }
21 div.note { margin-bottom: 5px; }
23 </style></head><body><div class="book" lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="id2473523"></a>The Mutt E-Mail Client</h1></div><div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Elkins</span></h3><code class="email"><<a class="email" href="mailto:me@cs.hmc.edu">me@cs.hmc.edu</a>></code></div></div><div><p class="releaseinfo">version 1.5.19 (2009-01-05)</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
24 “<span class="quote">All mail clients suck. This one just sucks less.</span>” -me, circa 1995
25 </p></div></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="#copyright">7. Copyright</a></span></dt></dl></dd><dt><span class="chapter"><a href="#gettingstarted">2. Getting Started</a></span></dt><dd><dl><dt><span class="sect1"><a href="#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="#postponing-mail">7. Postponing Mail</a></span></dt></dl></dd><dt><span class="chapter"><a href="#configuration">3. Configuration</a></span></dt><dd><dl><dt><span class="sect1"><a href="#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#advancedusage">4. Advanced Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#mimesupport">5. Mutt's MIME Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="#mime-lookup">7. MIME Lookup</a></span></dt></dl></dd><dt><span class="chapter"><a href="#optionalfeatures">6. Optional features</a></span></dt><dd><dl><dt><span class="sect1"><a href="#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="#exact-address">8. Exact address generation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#tuning">7. Performance tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="#tuning-search">3. Searching and limiting</a></span></dt></dl></dd><dt><span class="chapter"><a href="#reference">8. Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="#sidebar-delim">3.150. sidebar_delim</a></span></dt><dt><span class="sect2"><a href="#sidebar-visible">3.151. sidebar_visible</a></span></dt><dt><span class="sect2"><a href="#sidebar-width">3.152. sidebar_width</a></span></dt><dt><span class="sect2"><a href="#pgp-use-gpg-agent">3.153. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="#crypt-verify-sig">3.154. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="#smime-is-default">3.155. smime_is_default</a></span></dt><dt><span class="sect2"><a href="#smime-ask-cert-label">3.156. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-use-default-key">3.157. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="#pgp-entry-format">3.158. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="#pgp-good-sign">3.159. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="#pgp-check-exit">3.160. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="#pgp-long-ids">3.161. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="#pgp-retainable-sigs">3.162. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="#pgp-autoinline">3.163. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="#pgp-replyinline">3.164. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="#pgp-show-unusable">3.165. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-as">3.166. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="#pgp-strict-enc">3.167. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="#pgp-timeout">3.168. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="#pgp-sort-keys">3.169. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-auto">3.170. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="#pgp-auto-decode">3.171. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-filename">3.172. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-description">3.173. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="#pgp-decode-command">3.174. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="#pgp-getkeys-command">3.175. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-command">3.176. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="#pgp-decrypt-command">3.177. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#pgp-clearsign-command">3.178. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-command">3.179. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-sign-command">3.180. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-only-command">3.181. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="#pgp-import-command">3.182. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="#pgp-export-command">3.183. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-key-command">3.184. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-secring-command">3.185. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-pubring-command">3.186. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="#forward-decrypt">3.187. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="#smime-timeout">3.188. smime_timeout</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-with">3.189. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="#smime-keys">3.190. smime_keys</a></span></dt><dt><span class="sect2"><a href="#smime-ca-location">3.191. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="#smime-certificates">3.192. smime_certificates</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-command">3.193. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-command">3.194. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-opaque-command">3.195. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-command">3.196. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-opaque-command">3.197. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-command">3.198. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-pk7out-command">3.199. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-command">3.200. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-signer-cert-command">3.201. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-import-cert-command">3.202. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-email-command">3.203. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="#smime-default-key">3.204. smime_default_key</a></span></dt><dt><span class="sect2"><a href="#ssl-client-cert">3.205. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="#ssl-force-tls">3.206. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="#ssl-starttls">3.207. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="#certificate-file">3.208. certificate_file</a></span></dt><dt><span class="sect2"><a href="#ssl-use-sslv3">3.209. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="#ssl-use-tlsv1">3.210. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="#ssl-min-dh-prime-bits">3.211. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="#ssl-ca-certificates-file">3.212. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="#pipe-split">3.213. pipe_split</a></span></dt><dt><span class="sect2"><a href="#pipe-decode">3.214. pipe_decode</a></span></dt><dt><span class="sect2"><a href="#pipe-sep">3.215. pipe_sep</a></span></dt><dt><span class="sect2"><a href="#pop-authenticators">3.216. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="#pop-auth-try-all">3.217. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="#pop-checkinterval">3.218. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="#pop-delete">3.219. pop_delete</a></span></dt><dt><span class="sect2"><a href="#pop-host">3.220. pop_host</a></span></dt><dt><span class="sect2"><a href="#pop-last">3.221. pop_last</a></span></dt><dt><span class="sect2"><a href="#pop-reconnect">3.222. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="#pop-user">3.223. pop_user</a></span></dt><dt><span class="sect2"><a href="#pop-pass">3.224. pop_pass</a></span></dt><dt><span class="sect2"><a href="#post-indent-string">3.225. post_indent_string</a></span></dt><dt><span class="sect2"><a href="#postpone">3.226. postpone</a></span></dt><dt><span class="sect2"><a href="#postponed">3.227. postponed</a></span></dt><dt><span class="sect2"><a href="#preconnect">3.228. preconnect</a></span></dt><dt><span class="sect2"><a href="#print">3.229. print</a></span></dt><dt><span class="sect2"><a href="#print-command">3.230. print_command</a></span></dt><dt><span class="sect2"><a href="#print-decode">3.231. print_decode</a></span></dt><dt><span class="sect2"><a href="#print-split">3.232. print_split</a></span></dt><dt><span class="sect2"><a href="#prompt-after">3.233. prompt_after</a></span></dt><dt><span class="sect2"><a href="#query-command">3.234. query_command</a></span></dt><dt><span class="sect2"><a href="#query-format">3.235. query_format</a></span></dt><dt><span class="sect2"><a href="#quit">3.236. quit</a></span></dt><dt><span class="sect2"><a href="#quote-regexp">3.237. quote_regexp</a></span></dt><dt><span class="sect2"><a href="#read-inc">3.238. read_inc</a></span></dt><dt><span class="sect2"><a href="#read-only">3.239. read_only</a></span></dt><dt><span class="sect2"><a href="#realname">3.240. realname</a></span></dt><dt><span class="sect2"><a href="#recall">3.241. recall</a></span></dt><dt><span class="sect2"><a href="#record">3.242. record</a></span></dt><dt><span class="sect2"><a href="#reply-regexp">3.243. reply_regexp</a></span></dt><dt><span class="sect2"><a href="#reply-self">3.244. reply_self</a></span></dt><dt><span class="sect2"><a href="#reply-to">3.245. reply_to</a></span></dt><dt><span class="sect2"><a href="#resolve">3.246. resolve</a></span></dt><dt><span class="sect2"><a href="#reverse-alias">3.247. reverse_alias</a></span></dt><dt><span class="sect2"><a href="#reverse-name">3.248. reverse_name</a></span></dt><dt><span class="sect2"><a href="#reverse-realname">3.249. reverse_realname</a></span></dt><dt><span class="sect2"><a href="#rfc2047-parameters">3.250. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="#save-address">3.251. save_address</a></span></dt><dt><span class="sect2"><a href="#save-empty">3.252. save_empty</a></span></dt><dt><span class="sect2"><a href="#save-history">3.253. save_history</a></span></dt><dt><span class="sect2"><a href="#save-name">3.254. save_name</a></span></dt><dt><span class="sect2"><a href="#score">3.255. score</a></span></dt><dt><span class="sect2"><a href="#score-threshold-delete">3.256. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="#score-threshold-flag">3.257. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="#score-threshold-read">3.258. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="#send-charset">3.259. send_charset</a></span></dt><dt><span class="sect2"><a href="#sendmail">3.260. sendmail</a></span></dt><dt><span class="sect2"><a href="#sendmail-wait">3.261. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="#shell">3.262. shell</a></span></dt><dt><span class="sect2"><a href="#sig-dashes">3.263. sig_dashes</a></span></dt><dt><span class="sect2"><a href="#sig-on-top">3.264. sig_on_top</a></span></dt><dt><span class="sect2"><a href="#signature">3.265. signature</a></span></dt><dt><span class="sect2"><a href="#simple-search">3.266. simple_search</a></span></dt><dt><span class="sect2"><a href="#smart-wrap">3.267. smart_wrap</a></span></dt><dt><span class="sect2"><a href="#smileys">3.268. smileys</a></span></dt><dt><span class="sect2"><a href="#sleep-time">3.269. sleep_time</a></span></dt><dt><span class="sect2"><a href="#smtp-authenticators">3.270. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="#smtp-pass">3.271. smtp_pass</a></span></dt><dt><span class="sect2"><a href="#smtp-url">3.272. smtp_url</a></span></dt><dt><span class="sect2"><a href="#sort">3.273. sort</a></span></dt><dt><span class="sect2"><a href="#sort-alias">3.274. sort_alias</a></span></dt><dt><span class="sect2"><a href="#sort-aux">3.275. sort_aux</a></span></dt><dt><span class="sect2"><a href="#sort-browser">3.276. sort_browser</a></span></dt><dt><span class="sect2"><a href="#sort-re">3.277. sort_re</a></span></dt><dt><span class="sect2"><a href="#spam-separator">3.278. spam_separator</a></span></dt><dt><span class="sect2"><a href="#spoolfile">3.279. spoolfile</a></span></dt><dt><span class="sect2"><a href="#status-chars">3.280. status_chars</a></span></dt><dt><span class="sect2"><a href="#status-format">3.281. status_format</a></span></dt><dt><span class="sect2"><a href="#status-on-top">3.282. status_on_top</a></span></dt><dt><span class="sect2"><a href="#strict-threads">3.283. strict_threads</a></span></dt><dt><span class="sect2"><a href="#suspend">3.284. suspend</a></span></dt><dt><span class="sect2"><a href="#text-flowed">3.285. text_flowed</a></span></dt><dt><span class="sect2"><a href="#thread-received">3.286. thread_received</a></span></dt><dt><span class="sect2"><a href="#thorough-search">3.287. thorough_search</a></span></dt><dt><span class="sect2"><a href="#tilde">3.288. tilde</a></span></dt><dt><span class="sect2"><a href="#time-inc">3.289. time_inc</a></span></dt><dt><span class="sect2"><a href="#timeout">3.290. timeout</a></span></dt><dt><span class="sect2"><a href="#tmpdir">3.291. tmpdir</a></span></dt><dt><span class="sect2"><a href="#to-chars">3.292. to_chars</a></span></dt><dt><span class="sect2"><a href="#trash">3.293. trash</a></span></dt><dt><span class="sect2"><a href="#tunnel">3.294. tunnel</a></span></dt><dt><span class="sect2"><a href="#use-8bitmime">3.295. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="#use-domain">3.296. use_domain</a></span></dt><dt><span class="sect2"><a href="#use-envelope-from">3.297. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="#use-from">3.298. use_from</a></span></dt><dt><span class="sect2"><a href="#use-idn">3.299. use_idn</a></span></dt><dt><span class="sect2"><a href="#use-ipv6">3.300. use_ipv6</a></span></dt><dt><span class="sect2"><a href="#user-agent">3.301. user_agent</a></span></dt><dt><span class="sect2"><a href="#visual">3.302. visual</a></span></dt><dt><span class="sect2"><a href="#wait-key">3.303. wait_key</a></span></dt><dt><span class="sect2"><a href="#weed">3.304. weed</a></span></dt><dt><span class="sect2"><a href="#wrap">3.305. wrap</a></span></dt><dt><span class="sect2"><a href="#wrap-search">3.306. wrap_search</a></span></dt><dt><span class="sect2"><a href="#wrapmargin">3.307. wrapmargin</a></span></dt><dt><span class="sect2"><a href="#write-inc">3.308. write_inc</a></span></dt><dt><span class="sect2"><a href="#write-bcc">3.309. write_bcc</a></span></dt><dt><span class="sect2"><a href="#xterm-icon">3.310. xterm_icon</a></span></dt><dt><span class="sect2"><a href="#xterm-set-titles">3.311. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="#xterm-title">3.312. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#miscellany">9. Miscellany</a></span></dt><dd><dl><dt><span class="sect1"><a href="#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="#about">2. About this document</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="#tab-typo">Typographical conventions for special terms</a></dt><dt>2.1. <a href="#tab-keys-nav">Most common navigation keys</a></dt><dt>2.2. <a href="#tab-keys-editor">Most common line editor keys</a></dt><dt>2.3. <a href="#tab-key-index">Most common message index keys</a></dt><dt>2.4. <a href="#tab-msg-status-flags">Message status flags</a></dt><dt>2.5. <a href="#tab-msg-recip-flags">Message recipient flags</a></dt><dt>2.6. <a href="#tab-key-pager">Most common pager keys</a></dt><dt>2.7. <a href="#tab-ansi-esc">ANSI escape sequences</a></dt><dt>2.8. <a href="#tab-color">Color sequences</a></dt><dt>2.9. <a href="#tab-key-threads">Most common thread mode keys</a></dt><dt>2.10. <a href="#tab-key-send">Most common mail sending keys</a></dt><dt>2.11. <a href="#tab-func-compose">Most common compose menu keys</a></dt><dt>2.12. <a href="#tab-pgp-menuflags">PGP key menu flags</a></dt><dt>3.1. <a href="#tab-key-names">Symbolic key names</a></dt><dt>4.1. <a href="#posix-regex-char-classes">POSIX regular expression character classes</a></dt><dt>4.2. <a href="#regex-repeat">Regular expression repetition operators</a></dt><dt>4.3. <a href="#regex-gnu-ext">GNU regular expression extensions</a></dt><dt>4.4. <a href="#tab-patterns">Pattern modifiers</a></dt><dt>4.5. <a href="#tab-simplesearch-keywords">Simple search keywords</a></dt><dt>4.6. <a href="#tab-date-units">Date units</a></dt><dt>8.1. <a href="#tab-commandline-options">Command line options</a></dt><dt>8.2. <a href="#generic_table">Default generic function bindings</a></dt><dt>8.3. <a href="#index_table">Default index function bindings</a></dt><dt>8.4. <a href="#pager_table">Default pager function bindings</a></dt><dt>8.5. <a href="#alias_table">Default alias function bindings</a></dt><dt>8.6. <a href="#query_table">Default query function bindings</a></dt><dt>8.7. <a href="#attach_table">Default attach function bindings</a></dt><dt>8.8. <a href="#compose_table">Default compose function bindings</a></dt><dt>8.9. <a href="#postpone_table">Default postpone function bindings</a></dt><dt>8.10. <a href="#browser_table">Default browser function bindings</a></dt><dt>8.11. <a href="#pgp_table">Default pgp function bindings</a></dt><dt>8.12. <a href="#smime_table">Default smime function bindings</a></dt><dt>8.13. <a href="#mix_table">Default mix function bindings</a></dt><dt>8.14. <a href="#editor_table">Default editor function bindings</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>3.1. <a href="#ex-rc-multiple-cmds">Multiple configuration commands per line</a></dt><dt>3.2. <a href="#ex-ec-comment">Commenting configuration files</a></dt><dt>3.3. <a href="#ex-rc-quote">Escaping quotes in congfiguration files</a></dt><dt>3.4. <a href="#ex-rc-backtick">Using external command's output in configuration files</a></dt><dt>3.5. <a href="#ex-rc-env">Using environment variables in configuration files</a></dt><dt>3.6. <a href="#ex-alias-external">Configuring external alias files</a></dt><dt>3.7. <a href="#ex-folder-sorting">Setting sort method based on mailbox name</a></dt><dt>3.8. <a href="#ex-header-weeding">Header weeding</a></dt><dt>3.9. <a href="#ex-hdr-order">Configuring header display order</a></dt><dt>3.10. <a href="#ex-my-hdr">Defining custom headers</a></dt><dt>3.11. <a href="#ex-save-hook-exando">Using %-expandos in <code class="literal">save-hook</code></a></dt><dt>3.12. <a href="#ex-folder-hook-push">Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></a></dt><dt>3.13. <a href="#ex-spam">Configuring spam detection</a></dt><dt>3.14. <a href="#ex-myvar1">Using user-defined variables for config file readability</a></dt><dt>3.15. <a href="#ex-myvar2">Using user-defined variables for backing up other config option values</a></dt><dt>3.16. <a href="#ex-myvar3">Deferring user-defined variable expansion to runtime</a></dt><dt>3.17. <a href="#ex-fmtpipe">Using external filters in format strings</a></dt><dt>4.1. <a href="#ex-pattern-bool">Using boolean operators in patterns</a></dt><dt>4.2. <a href="#ex-send-hook-my-hdr">Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></a></dt><dt>5.1. <a href="#ex-attach-count">Attachment counting</a></dt></dl></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="#copyright">7. Copyright</a></span></dt></dl></div><p>
26 <span class="bold"><strong>Mutt</strong></span> is a small but very powerful text-based MIME mail client. Mutt is
27 highly configurable, and is well suited to the mail power user with advanced
28 features like key bindings, keyboard macros, mail threading, regular
29 expression searches and a powerful pattern matching language for selecting
31 </p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="homepage"></a>1. Mutt Home Page</h2></div></div></div><p>
32 The official homepage can be found at
33 <a class="ulink" href="http://www.mutt.org/" target="_top">http://www.mutt.org/</a>.
34 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttlists"></a>2. Mailing Lists</h2></div></div></div><p>
35 To subscribe to one of the following mailing lists, send a message with the
36 word <span class="emphasis"><em>subscribe</em></span> in the body to
37 <code class="literal">list-name</code><span class="emphasis"><em>-request</em></span><code class="literal">@mutt.org</code>.
38 </p><div class="itemizedlist"><ul type="disc"><li><p>
39 <code class="email"><<a class="email" href="mailto:mutt-announce-request@mutt.org">mutt-announce-request@mutt.org</a>></code> -- low traffic list for announcements
41 <code class="email"><<a class="email" href="mailto:mutt-users-request@mutt.org">mutt-users-request@mutt.org</a>></code> -- help, bug reports and feature requests
43 <code class="email"><<a class="email" href="mailto:mutt-dev-request@mutt.org">mutt-dev-request@mutt.org</a>></code> -- development mailing list
44 </p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
45 All messages posted to
46 <span class="emphasis"><em>mutt-announce</em></span> are automatically forwarded to
47 <span class="emphasis"><em>mutt-users</em></span>, so you do not need to be subscribed to
49 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="distribution"></a>3. Software Distribution Sites</h2></div></div></div><p>
50 Mutt releases can be downloaded from
51 <a class="ulink" href="ftp://ftp.mutt.org/mutt/" target="_top">ftp://ftp.mutt.org/mutt/</a>.
52 For a list of mirror sites, please refer to
53 <a class="ulink" href="http://www.mutt.org/download.html" target="_top">http://www.mutt.org/download.html</a>.
54 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="irc"></a>4. Mutt online resources</h2></div></div></div><div class="variablelist"><dl><dt><span class="term">Bug Tracking System</span></dt><dd><p>
55 The official mutt bug tracking system can be found at
56 <a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a>
57 </p></dd><dt><span class="term">Wiki</span></dt><dd><p>
58 An (unofficial) wiki can be found
59 at <a class="ulink" href="http://wiki.mutt.org/" target="_top">http://wiki.mutt.org/</a>.
60 </p></dd><dt><span class="term">IRC</span></dt><dd><p>
61 For the IRC user community, visit channel <span class="emphasis"><em>#mutt</em></span> on
62 <a class="ulink" href="http://www.freenode.net/" target="_top">irc.freenode.net</a>.
63 </p></dd><dt><span class="term">USENET</span></dt><dd><p>
64 For USENET, see the newsgroup <a class="ulink" href="news:comp.mail.mutt" target="_top">comp.mail.mutt</a>.
65 </p></dd></dl></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="contrib"></a>5. Contributing to Mutt</h2></div></div></div><p>
66 There are various ways to contribute to the Mutt project.
68 Especially for new users it may be helpful to meet other new and
69 experienced users to chat about Mutt, talk about problems and share
72 Since translations of Mutt into other languages are highly appreciated,
73 the mutt developers always look for skilled translators that help
74 improve and continue to maintain stale translations.
76 For contributing code patches for new features and bug fixes, please
77 refer to the developer pages at
78 <a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a> for more details.
79 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="typo"></a>6. Typograhical conventions</h2></div></div></div><p>
80 This section lists typographical conventions followed throughout this
81 manual. See table <a class="xref" href="#tab-typo" title="Table 1.1. Typographical conventions for special terms">Table 1.1, “Typographical conventions for special terms”</a> for typographical
82 conventions for special terms.
83 </p><div class="table"><a id="tab-typo"></a><p class="title"><b>Table 1.1. Typographical conventions for special terms</b></p><div class="table-contents"><table summary="Typographical conventions for special terms" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Item</th><th>Refers to...</th></tr></thead><tbody><tr><td><code class="literal">printf(3)</code></td><td>UNIX manual pages, execute <code class="literal">man 3 printf</code></td></tr><tr><td><code class="literal"><PageUp></code></td><td>named keys</td></tr><tr><td><code class="literal"><create-alias></code></td><td>named Mutt function</td></tr><tr><td><code class="literal">^G</code></td><td>Control+G key combination</td></tr><tr><td><code class="literal">$mail_check</code></td><td>Mutt configuration option</td></tr></tbody></table></div></div><br class="table-break" /><p>
84 Examples are presented as:
85 </p><pre class="screen">
88 Within command synopsis, curly brackets (“<span class="quote">{}</span>”) denote a set
89 of options of which one is mandatory, square brackets
90 (“<span class="quote">[]</span>”) denote optional arguments, three dots
91 denote that the argument may be repeated arbitrary times.
92 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="copyright"></a>7. Copyright</h2></div></div></div><p>
93 Mutt is Copyright (C) 1996-2009 Michael R. Elkins
94 <code class="email"><<a class="email" href="mailto:me@mutt.org">me@mutt.org</a>></code> and others.
96 This program is free software; you can redistribute it and/or modify
97 it under the terms of the GNU General Public License as published by
98 the Free Software Foundation; either version 2 of the License, or
99 (at your option) any later version.
101 This program is distributed in the hope that it will be useful,
102 but WITHOUT ANY WARRANTY; without even the implied warranty of
103 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
104 GNU General Public License for more details.
106 You should have received a copy of the GNU General Public License
107 along with this program; if not, write to the Free Software
108 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
109 </p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="gettingstarted"></a>Chapter 2. Getting Started</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="#postponing-mail">7. Postponing Mail</a></span></dt></dl></div><p>
110 This section is intended as a brief overview of how to use Mutt. There are
111 many other features which are described elsewhere in the manual. There
112 is even more information available in the Mutt FAQ and various web
113 pages. See the <a class="ulink" href="http://www.mutt.org/" target="_top">Mutt homepage</a> for more details.
115 The keybindings described in this section are the defaults as distributed.
116 Your local system administrator may have altered the defaults for your site.
117 You can always type “<span class="quote">?</span>” in any menu to display the current bindings.
119 The first thing you need to do is invoke mutt, simply by typing <code class="literal">mutt</code>
120 at the command line. There are various command-line options, see
121 either the mutt man page or the <a class="link" href="#commandline" title="1. Command line options">reference</a>.
122 </p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="core-concepts"></a>1. Core concepts</h2></div></div></div><p>
123 Mutt is a text-based application which interacts with users through
124 different menus which are mostly line-/entry-based or page-based. A
125 line-based menu is the so-called “<span class="quote">index</span>” menu (listing all messages of
126 the currently opened folder) or the “<span class="quote">alias</span>” menu (allowing you to
127 select recipients from a list). Examples for page-based menus are the
128 “<span class="quote">pager</span>” (showing one message at a time) or the “<span class="quote">help</span>” menu listing
129 all available key bindings.
131 The user interface consists of a context sensitive help line at the top,
132 the menu's contents followed by a context sensitive status line and
133 finally the command line. The command line is used to display
134 informational and error messages as well as for prompts and for entering
135 interactive commands.
137 Because Mutt allows for customizing almost all key bindings, there are
138 so-called “<span class="quote">functions</span>” which can be executed manually (using the
139 command line) or in macros. Macros allow the user to bind a sequence of
140 commands to a single key or a short key sequence instead of repeating a
141 sequence of actions over and over.
143 Many commands (such as saving or copying a message to another folder)
144 can be applied to a single message or a set of messages (so-called
145 “<span class="quote">tagged</span>” messages). To help selecting messages, Mutt provides a rich
146 set of message patterns (such as recipients, sender, body contents, date
147 sent/received, etc.) which can be combined into complex expressions
148 using the boolean <span class="emphasis"><em>and</em></span> and <span class="emphasis"><em>or</em></span>
149 operations as well as negating. These patterns can also be used to (for
150 example) search for messages or to limit the index to show only matching
153 Mutt supports a “<span class="quote">hook</span>” concept which allows the user to execute
154 arbitrary configuration commands and functions in certain situations
155 such as entering a folder, starting a new message or replying to an
156 existing one. These hooks can be used to highly customize Mutt's
157 behaviour including managing multiple identities, customizing the
158 display for a folder or even implementing auto-archiving based on a
159 per-folder basis and much more.
160 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="menus"></a>2. Moving Around in Menus</h2></div></div></div><p>
161 The most important navigation keys common to all menus are shown in
162 <a class="xref" href="#tab-keys-nav" title="Table 2.1. Most common navigation keys">Table 2.1, “Most common navigation keys”</a>.
163 </p><div class="table"><a id="tab-keys-nav"></a><p class="title"><b>Table 2.1. Most common navigation keys</b></p><div class="table-contents"><table summary="Most common navigation keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>j or <Down></td><td><code class="literal"><next-entry></code></td><td>move to the next entry</td></tr><tr><td>k or <Up></td><td><code class="literal"><previous-entry></code></td><td>move to the previous entry</td></tr><tr><td>z or <PageDn></td><td><code class="literal"><page-down></code></td><td>go to the next page</td></tr><tr><td>Z or <PageUp></td><td><code class="literal"><page-up></code></td><td>go to the previous page</td></tr><tr><td>= or <Home></td><td><code class="literal"><first-entry></code></td><td>jump to the first entry</td></tr><tr><td>* or <End></td><td><code class="literal"><last-entry></code></td><td>jump to the last entry</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>exit the current menu</td></tr><tr><td>?</td><td><code class="literal"><help></code></td><td>list all keybindings for the current menu</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing"></a>3. Editing Input Fields</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-intro"></a>3.1. Introduction</h3></div></div></div><p>
164 Mutt has a built-in line editor for inputting text, e.g. email
165 addresses or filenames. The keys used to manipulate text input are
166 very similar to those of Emacs. See <a class="xref" href="#tab-keys-editor" title="Table 2.2. Most common line editor keys">Table 2.2, “Most common line editor keys”</a> for a full
167 reference of available functions, their default key bindings, and
169 </p><div class="table"><a id="tab-keys-editor"></a><p class="title"><b>Table 2.2. Most common line editor keys</b></p><div class="table-contents"><table summary="Most common line editor keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^A or <Home></td><td><code class="literal"><bol></code></td><td>move to the start of the line</td></tr><tr><td>^B or <Left></td><td><code class="literal"><backward-char></code></td><td>move back one char</td></tr><tr><td>Esc B</td><td><code class="literal"><backward-word></code></td><td>move back one word</td></tr><tr><td>^D or <Delete></td><td><code class="literal"><delete-char></code></td><td>delete the char under the cursor</td></tr><tr><td>^E or <End></td><td><code class="literal"><eol></code></td><td>move to the end of the line</td></tr><tr><td>^F or <Right></td><td><code class="literal"><forward-char></code></td><td>move forward one char</td></tr><tr><td>Esc F</td><td><code class="literal"><forward-word></code></td><td>move forward one word</td></tr><tr><td><Tab></td><td><code class="literal"><complete></code></td><td>complete filename or alias</td></tr><tr><td>^T</td><td><code class="literal"><complete-query></code></td><td>complete address with query</td></tr><tr><td>^K</td><td><code class="literal"><kill-eol></code></td><td>delete to the end of the line</td></tr><tr><td>Esc d</td><td><code class="literal"><kill-eow></code></td><td>delete to the end of the word</td></tr><tr><td>^W</td><td><code class="literal"><kill-word></code></td><td>kill the word in front of the cursor</td></tr><tr><td>^U</td><td><code class="literal"><kill-line></code></td><td>delete entire line</td></tr><tr><td>^V</td><td><code class="literal"><quote-char></code></td><td>quote the next typed key</td></tr><tr><td><Up></td><td><code class="literal"><history-up></code></td><td>recall previous string from history</td></tr><tr><td><Down></td><td><code class="literal"><history-down></code></td><td>recall next string from history</td></tr><tr><td><BackSpace></td><td><code class="literal"><backspace></code></td><td>kill the char in front of the cursor</td></tr><tr><td>Esc u</td><td><code class="literal"><upcase-word></code></td><td>convert word to upper case</td></tr><tr><td>Esc l</td><td><code class="literal"><downcase-word></code></td><td>convert word to lower case</td></tr><tr><td>Esc c</td><td><code class="literal"><capitalize-word></code></td><td>capitalize the word</td></tr><tr><td>^G</td><td>n/a</td><td>abort</td></tr><tr><td><Return></td><td>n/a</td><td>finish editing</td></tr></tbody></table></div></div><br class="table-break" /><p>
170 You can remap the <span class="emphasis"><em>editor</em></span> functions using the
171 <a class="link" href="#bind" title="5. Changing the default key bindings">bind</a> command. For example, to make
172 the <Delete> key delete the character in front of
173 the cursor rather than under, you could use:
174 </p><pre class="screen">
175 bind editor <delete> backspace
176 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-history"></a>3.2. History</h3></div></div></div><p>
177 Mutt maintains a history for the built-in editor. The number of items
178 is controlled by the <a class="link" href="#history" title="3.77. history">$history</a>
179 variable and can be made persistent using an external file specified
180 using <a class="link" href="#history-file" title="3.78. history_file">$history_file</a>.
181 You may cycle through them at an editor prompt by using the
182 <code class="literal"><history-up></code> and/or
183 <code class="literal"><history-down></code> commands.
185 Mutt maintains several distinct history lists, one for each of the
186 following categories:
187 </p><div class="itemizedlist"><ul type="disc"><li><p>muttrc commands</p></li><li><p>addresses and aliases</p></li><li><p>shell commands</p></li><li><p>filenames</p></li><li><p>patterns</p></li><li><p>everything else</p></li></ul></div><p>
188 Mutt automatically filters out repeated items from the history. It
189 also mimics the behavior of some shells by ignoring items starting
190 with a space. The latter feature can be useful in macros to not clobber
191 the history's valuable entries with unwanted entries.
192 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="reading"></a>4. Reading Mail - The Index and Pager</h2></div></div></div><p>
193 Similar to many other mail clients, there are two modes in which mail is
194 read in Mutt. The first is the index of messages in the mailbox, which is
195 called the “<span class="quote">index</span>” in Mutt. The second mode is the display of the
196 message contents. This is called the “<span class="quote">pager.</span>”
198 The next few sections describe the functions provided in each of these
200 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-menu"></a>4.1. The Message Index</h3></div></div></div><p>
201 Common keys used to navigate through and manage messages in the index
202 are shown in <a class="xref" href="#tab-key-index" title="Table 2.3. Most common message index keys">Table 2.3, “Most common message index keys”</a>. How messages are presented
203 in the index menu can be customized using the
204 <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable.
205 </p><div class="table"><a id="tab-key-index"></a><p class="title"><b>Table 2.3. Most common message index keys</b></p><div class="table-contents"><table summary="Most common message index keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td>c</td><td>change to a different mailbox</td></tr><tr><td>Esc c</td><td>change to a folder in read-only mode</td></tr><tr><td>C</td><td>copy the current message to another mailbox</td></tr><tr><td>Esc C</td><td>decode a message and copy it to a folder</td></tr><tr><td>Esc s</td><td>decode a message and save it to a folder</td></tr><tr><td>D</td><td>delete messages matching a pattern</td></tr><tr><td>d</td><td>delete the current message</td></tr><tr><td>F</td><td>mark as important</td></tr><tr><td>l</td><td>show messages matching a pattern</td></tr><tr><td>N</td><td>mark message as new</td></tr><tr><td>o</td><td>change the current sort method</td></tr><tr><td>O</td><td>reverse sort the mailbox</td></tr><tr><td>q</td><td>save changes and exit</td></tr><tr><td>s</td><td>save-message</td></tr><tr><td>T</td><td>tag messages matching a pattern</td></tr><tr><td>t</td><td>toggle the tag on a message</td></tr><tr><td>Esc t</td><td>toggle tag on entire message thread</td></tr><tr><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td>u</td><td>undelete-message</td></tr><tr><td>v</td><td>view-attachments</td></tr><tr><td>x</td><td>abort changes and exit</td></tr><tr><td><Return></td><td>display-message</td></tr><tr><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td>@</td><td>show the author's full e-mail address</td></tr><tr><td>$</td><td>save changes to mailbox</td></tr><tr><td>/</td><td>search</td></tr><tr><td>Esc /</td><td>search-reverse</td></tr><tr><td>^L</td><td>clear and redraw the screen</td></tr><tr><td>^T</td><td>untag messages matching a pattern</td></tr></tbody></table></div></div><br class="table-break" /><p>
206 In addition to who sent the message and the subject, a short summary of
207 the disposition of each message is printed beside the message number.
208 Zero or more of the “<span class="quote">flags</span>” in <a class="xref" href="#tab-msg-status-flags" title="Table 2.4. Message status flags">Table 2.4, “Message status flags”</a>
209 may appear, some of which can be turned on or off using these functions:
210 <code class="literal"><set-flag></code> and
211 <code class="literal"><clear-flag></code>
212 bound by default to “<span class="quote">w</span>” and “<span class="quote">W</span>” respectively.
214 Furthermore, the flags in <a class="xref" href="#tab-msg-recip-flags" title="Table 2.5. Message recipient flags">Table 2.5, “Message recipient flags”</a> reflect
215 who the message is addressed to. They can be customized with the
216 <a class="link" href="#to-chars" title="3.292. to_chars">$to_chars</a> variable.
217 </p><div class="table"><a id="tab-msg-status-flags"></a><p class="title"><b>Table 2.4. Message status flags</b></p><div class="table-contents"><table summary="Message status flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>D</td><td>message is deleted (is marked for deletion)</td></tr><tr><td>d</td><td>message has attachments marked for deletion</td></tr><tr><td>K</td><td>contains a PGP public key</td></tr><tr><td>N</td><td>message is new</td></tr><tr><td>O</td><td>message is old</td></tr><tr><td>P</td><td>message is PGP encrypted</td></tr><tr><td>r</td><td>message has been replied to</td></tr><tr><td>S</td><td>message is signed, and the signature is successfully verified</td></tr><tr><td>s</td><td>message is signed</td></tr><tr><td>!</td><td>message is flagged</td></tr><tr><td>*</td><td>message is tagged</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-msg-recip-flags"></a><p class="title"><b>Table 2.5. Message recipient flags</b></p><div class="table-contents"><table summary="Message recipient flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>+</td><td>message is to you and you only</td></tr><tr><td>T</td><td>message is to you, but also to or cc'ed to others</td></tr><tr><td>C</td><td>message is cc'ed to you</td></tr><tr><td>F</td><td>message is from you</td></tr><tr><td>L</td><td>message is sent to a subscribed mailing list</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-menu"></a>4.2. The Pager</h3></div></div></div><p>
218 By default, Mutt uses its builtin pager to display the contents of messages.
219 The pager is very similar to the Unix program <span class="emphasis"><em>less</em></span> though not nearly as
221 </p><div class="table"><a id="tab-key-pager"></a><p class="title"><b>Table 2.6. Most common pager keys</b></p><div class="table-contents"><table summary="Most common pager keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td><Return></td><td>go down one line</td></tr><tr><td><Space></td><td>display the next page (or next message if at the end of a message)</td></tr><tr><td>-</td><td>go back to the previous page</td></tr><tr><td>n</td><td>search for next match</td></tr><tr><td>S</td><td>skip beyond quoted text</td></tr><tr><td>T</td><td>toggle display of quoted text</td></tr><tr><td>?</td><td>show keybindings</td></tr><tr><td>/</td><td>regular expression search</td></tr><tr><td>Esc /</td><td>backward regular expression search</td></tr><tr><td>\</td><td>toggle highlighting of search matches</td></tr><tr><td>^</td><td>jump to the top of the message</td></tr></tbody></table></div></div><br class="table-break" /><p>
222 In addition to key bindings in <a class="xref" href="#tab-key-pager" title="Table 2.6. Most common pager keys">Table 2.6, “Most common pager keys”</a>,
223 many of the functions from the index menu are also available in
224 the pager, such as <code class="literal"><delete-message></code> or <code class="literal"><copy-message></code>
225 (this is one advantage over using an external pager to view messages).
227 Also, the internal pager supports a couple other advanced features. For
228 one, it will accept and translate the “<span class="quote">standard</span>” nroff sequences for
229 bold and underline. These sequences are a series of either the letter,
230 backspace (^H), the letter again for bold or the letter, backspace,
231 “<span class="quote">_</span>” for denoting underline. Mutt will attempt to display these
232 in bold and underline respectively if your terminal supports them. If
233 not, you can use the bold and underline <a class="link" href="#color" title="9. Using color and mono video attributes">color</a>
234 objects to specify a color or mono attribute for them.
236 Additionally, the internal pager supports the ANSI escape sequences for
237 character attributes. Mutt translates them into the correct color and
238 character settings. The sequences Mutt supports are:
239 </p><pre class="screen">
240 \e[<span class="emphasis"><em>Ps</em></span>;<span class="emphasis"><em>Ps</em></span>;..<span class="emphasis"><em>Ps</em></span>;m
242 where <span class="emphasis"><em>Ps</em></span> can be one of the codes shown in
243 <a class="xref" href="#tab-ansi-esc" title="Table 2.7. ANSI escape sequences">Table 2.7, “ANSI escape sequences”</a>.
244 </p><div class="table"><a id="tab-ansi-esc"></a><p class="title"><b>Table 2.7. ANSI escape sequences</b></p><div class="table-contents"><table summary="ANSI escape sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Escape code</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>All attributes off</td></tr><tr><td>1</td><td>Bold on</td></tr><tr><td>4</td><td>Underline on</td></tr><tr><td>5</td><td>Blink on</td></tr><tr><td>7</td><td>Reverse video on</td></tr><tr><td>3<span class="emphasis"><em><color></em></span></td><td>Foreground color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr><tr><td>4<span class="emphasis"><em><color></em></span></td><td>Background color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-color"></a><p class="title"><b>Table 2.8. Color sequences</b></p><div class="table-contents"><table summary="Color sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Color code</th><th>Color</th></tr></thead><tbody><tr><td>0</td><td>Black</td></tr><tr><td>1</td><td>Red</td></tr><tr><td>2</td><td>Green</td></tr><tr><td>3</td><td>Yellow</td></tr><tr><td>4</td><td>Blue</td></tr><tr><td>5</td><td>Magenta</td></tr><tr><td>6</td><td>Cyan</td></tr><tr><td>7</td><td>White</td></tr></tbody></table></div></div><br class="table-break" /><p>
245 Mutt uses these attributes for handling <code class="literal">text/enriched</code>
246 messages, and they can also be used by an external
247 <a class="link" href="#auto-view" title="4. MIME Autoview">autoview</a> script for highlighting
249 </p><div class="note"><h3 class="title">Note</h3><p>
250 If you change the colors for your
251 display, for example by changing the color associated with color2 for
252 your xterm, then that color will be used instead of green.
253 </p></div><div class="note"><h3 class="title">Note</h3><p>
254 Note that the search commands in the pager take regular expressions,
255 which are not quite the same as the more
256 complex <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> used by the search
257 command in the index. This is because the pager only performs simple
258 text search, whereas the index provides boolean filtering on several
260 </p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="threads"></a>4.3. Threaded Mode</h3></div></div></div><p>
261 When the mailbox is <a class="link" href="#sort" title="3.273. sort">sorted</a> by <span class="emphasis"><em>threads</em></span>, there are
262 a few additional functions available in the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> modes
263 as shown in <a class="xref" href="#tab-key-threads" title="Table 2.9. Most common thread mode keys">Table 2.9, “Most common thread mode keys”</a>.
264 </p><div class="table"><a id="tab-key-threads"></a><p class="title"><b>Table 2.9. Most common thread mode keys</b></p><div class="table-contents"><table summary="Most common thread mode keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^D</td><td><code class="literal"><delete-thread></code></td><td>delete all messages in the current thread</td></tr><tr><td>^U</td><td><code class="literal"><undelete-thread></code></td><td>undelete all messages in the current thread</td></tr><tr><td>^N</td><td><code class="literal"><next-thread></code></td><td>jump to the start of the next thread</td></tr><tr><td>^P</td><td><code class="literal"><previous-thread></code></td><td>jump to the start of the previous thread</td></tr><tr><td>^R</td><td><code class="literal"><read-thread></code></td><td>mark the current thread as read</td></tr><tr><td>Esc d</td><td><code class="literal"><delete-subthread></code></td><td>delete all messages in the current subthread</td></tr><tr><td>Esc u</td><td><code class="literal"><undelete-subthread></code></td><td>undelete all messages in the current subthread</td></tr><tr><td>Esc n</td><td><code class="literal"><next-subthread></code></td><td>jump to the start of the next subthread</td></tr><tr><td>Esc p</td><td><code class="literal"><previous-subthread></code></td><td>jump to the start of the previous subthread</td></tr><tr><td>Esc r</td><td><code class="literal"><read-subthread></code></td><td>mark the current subthread as read</td></tr><tr><td>Esc t</td><td><code class="literal"><tag-thread></code></td><td>toggle the tag on the current thread</td></tr><tr><td>Esc v</td><td><code class="literal"><collapse-thread></code></td><td>toggle collapse for the current thread</td></tr><tr><td>Esc V</td><td><code class="literal"><collapse-all></code></td><td>toggle collapse for all threads</td></tr><tr><td>P</td><td><code class="literal"><parent-message></code></td><td>jump to parent message in thread</td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><h3 class="title">Note</h3><p>
265 Collapsing a thread displays only the first message
266 in the thread and hides the others. This is useful when threads
267 contain so many messages that you can only see a handful of threads on
268 the screen. See %M in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
269 For example, you could use "%?M?(#%03M)&(%4l)?" in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to optionally
270 display the number of hidden messages if the thread is collapsed.
272 See also: <a class="link" href="#strict-threads" title="3.283. strict_threads">$strict_threads</a>.
273 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reading-misc"></a>4.4. Miscellaneous Functions</h3></div></div></div><p>
274 In addition, the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span>
275 menus have these interesting functions:
276 </p><div class="variablelist"><dl><dt><span class="term">
277 <code class="literal"><create-alias></code><a id="create-alias"></a> (default: a)
279 Creates a new alias based upon the current message (or prompts for a
280 new one). Once editing is complete, an <a class="link" href="#alias" title="4. Defining/Using aliases">alias</a>
281 command is added to the file specified by
282 the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> variable
284 </p><div class="note"><h3 class="title">Note</h3><p>
285 Mutt does not read the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a>
286 upon startup so you must explicitly <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> the file.
287 </p></div></dd><dt><span class="term">
288 <code class="literal"><check-traditional-pgp></code><a id="check-traditional-pgp"></a> (default: Esc P)
290 This function will search the current message for content signed or
291 encrypted with PGP the “<span class="quote">traditional</span>” way, that is, without proper
292 MIME tagging. Technically, this function will temporarily change
293 the MIME content types of the body parts containing PGP data; this
294 is similar to the <a class="link" href="#edit-type"><code class="literal"><edit-type></code></a> function's
296 </p></dd><dt><span class="term">
297 <code class="literal"><edit></code><a id="edit"></a> (default: e)
299 This command (available in the index and pager) allows you to
300 edit the raw current message as it's present in the mail folder.
301 After you have finished editing, the changed message will be
302 appended to the current folder, and the original message will be
303 marked for deletion; if the message is unchanged it won't be replaced.
304 </p></dd><dt><span class="term">
305 <code class="literal"><edit-type></code><a id="edit-type"></a> (default:
306 ^E on the attachment menu, and in the pager and index menus;
307 ^T on the compose menu)
309 This command is used to temporarily edit an attachment's content
310 type to fix, for instance, bogus character set parameters. When
311 invoked from the index or from the pager, you'll have the
312 opportunity to edit the top-level attachment's content type. On the
313 <a class="link" href="#attach-menu" title="1.2. The Attachment Menu">attachment menu</a>, you can change any
314 attachment's content type. These changes are not persistent, and get
315 lost upon changing folders.
317 Note that this command is also available on the <a class="link" href="#compose-menu" title="1.3. The Compose Menu">compose
318 menu</a>. There, it's used to fine-tune the properties of attachments you are going
320 </p></dd><dt><span class="term">
321 <code class="literal"><enter-command></code><a id="enter-command"></a> (default: “<span class="quote">:</span>”)
323 This command is used to execute any command you would normally put in a
324 configuration file. A common use is to check the settings of variables, or
325 in conjunction with <a class="link" href="#macro" title="8. Keyboard macros">macros</a> to change settings on the
327 </p></dd><dt><span class="term">
328 <code class="literal"><extract-keys></code><a id="extract-keys"></a> (default: ^K)
330 This command extracts PGP public keys from the current or tagged
331 message(s) and adds them to your PGP public key ring.
332 </p></dd><dt><span class="term">
333 <code class="literal"><forget-passphrase></code><a id="forget-passphrase"></a> (default:
336 This command wipes the passphrase(s) from memory. It is useful, if
337 you misspelled the passphrase.
338 </p></dd><dt><span class="term">
339 <code class="literal"><list-reply></code><a id="list-reply"></a> (default: L)
341 Reply to the current or tagged message(s) by extracting any addresses which
342 match the regular expressions given by the <a class="link" href="#lists" title="12. Mailing lists">lists or subscribe</a>
343 commands, but also honor any <code class="literal">Mail-Followup-To</code> header(s) if the
344 <a class="link" href="#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a>
345 configuration variable is set. Using this when replying to messages posted
346 to mailing lists helps avoid duplicate copies being sent to the author of
347 the message you are replying to.
348 </p></dd><dt><span class="term">
349 <code class="literal"><pipe-message></code><a id="pipe-message"></a> (default: |)
351 Asks for an external Unix command and pipes the current or
352 tagged message(s) to it. The variables <a class="link" href="#pipe-decode" title="3.214. pipe_decode">$pipe_decode</a>, <a class="link" href="#pipe-split" title="3.213. pipe_split">$pipe_split</a>,
353 <a class="link" href="#pipe-sep" title="3.215. pipe_sep">$pipe_sep</a> and <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> control the exact behavior of this function.
354 </p></dd><dt><span class="term">
355 <code class="literal"><resend-message></code><a id="resend-message"></a> (default: Esc e)
357 Mutt takes the current message as a template for a
358 new message. This function is best described as "recall from arbitrary
359 folders". It can conveniently be used to forward MIME messages while
360 preserving the original mail structure. Note that the amount of headers
361 included here depends on the value of the <a class="link" href="#weed" title="3.304. weed">$weed</a>
364 This function is also available from the attachment menu. You can use this
365 to easily resend a message which was included with a bounce message
366 as a <code class="literal">message/rfc822</code> body part.
367 </p></dd><dt><span class="term">
368 <code class="literal"><shell-escape></code><a id="shell-escape"></a> (default: !)
370 Asks for an external Unix command and executes it. The <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> can be used to control
371 whether Mutt will wait for a key to be pressed when the command returns
372 (presumably to let the user read the output of the command), based on
373 the return status of the named command. If no command is given, an
374 interactive shell is executed.
375 </p></dd><dt><span class="term">
376 <code class="literal"><toggle-quoted></code><a id="toggle-quoted"></a> (default: T)
378 The pager uses the <a class="link" href="#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a> variable to detect quoted text when
379 displaying the body of the message. This function toggles the display
380 of the quoted material in the message. It is particularly useful when
381 being interested in just the response and there is a large amount of
382 quoted text in the way.
383 </p></dd><dt><span class="term">
384 <code class="literal"><skip-quoted></code><a id="skip-quoted"></a> (default: S)
386 This function will go to the next line of non-quoted text which comes
387 after a line of quoted text in the internal pager.
388 </p></dd></dl></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending"></a>5. Sending Mail</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-intro"></a>5.1. Introduction</h3></div></div></div><p>
389 The bindings shown in <a class="xref" href="#tab-key-send" title="Table 2.10. Most common mail sending keys">Table 2.10, “Most common mail sending keys”</a> are available in the
390 <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> to start a new message.
391 </p><div class="table"><a id="tab-key-send"></a><p class="title"><b>Table 2.10. Most common mail sending keys</b></p><div class="table-contents"><table summary="Most common mail sending keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>m</td><td><code class="literal"><compose></code></td><td>compose a new message</td></tr><tr><td>r</td><td><code class="literal"><reply></code></td><td>reply to sender</td></tr><tr><td>g</td><td><code class="literal"><group-reply></code></td><td>reply to all recipients</td></tr><tr><td>L</td><td><code class="literal"><list-reply></code></td><td>reply to mailing list address</td></tr><tr><td>f</td><td><code class="literal"><forward></code></td><td>forward message</td></tr><tr><td>b</td><td><code class="literal"><bounce></code></td><td>bounce (remail) message</td></tr><tr><td>Esc k</td><td><code class="literal"><mail-key></code></td><td>mail a PGP public key to someone</td></tr></tbody></table></div></div><br class="table-break" /><p>
392 <span class="emphasis"><em>Bouncing</em></span> a message sends the message as-is to the recipient you
393 specify. <span class="emphasis"><em>Forwarding</em></span> a message allows you to add comments or
394 modify the message you are forwarding. These items are discussed
395 in greater detail in the next chapter “<span class="quote"><a class="link" href="#forwarding-mail" title="6. Forwarding and Bouncing Mail">Forwarding
396 and Bouncing Mail</a>.</span>”
398 Mutt will then enter the <span class="emphasis"><em>compose</em></span> menu and prompt you for the
399 recipients to place on the “<span class="quote">To:</span>” header field. Next, it will ask
400 you for the “<span class="quote">Subject:</span>” field for the message, providing a default if
401 you are replying to or forwarding a message. See also
402 <a class="link" href="#askcc" title="3.10. askcc">$askcc</a>,
403 <a class="link" href="#askbcc" title="3.9. askbcc">$askbcc</a>,
404 <a class="link" href="#autoedit" title="3.17. autoedit">$autoedit</a>,
405 <a class="link" href="#bounce" title="3.21. bounce">$bounce</a>,
406 <a class="link" href="#fast-reply" title="3.55. fast_reply">$fast_reply</a>,
407 and <a class="link" href="#include" title="3.98. include">$include</a>
408 for changing how Mutt asks these questions.
410 Mutt will then automatically start your <a class="link" href="#editor" title="3.51. editor">$editor</a>
411 on the message body. If the <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>
412 variable is set, the headers will be at the top of the message in your editor.
413 Any messages you are replying to will be added in sort order to the message,
414 with appropriate <a class="link" href="#attribution" title="3.16. attribution">$attribution</a>,
415 <a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a> and
416 <a class="link" href="#post-indent-string" title="3.225. post_indent_string">$post_indent_string</a>.
417 When forwarding a message, if the <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a>
418 variable is unset, a copy of the forwarded message will be included. If
419 you have specified a <a class="link" href="#signature" title="3.265. signature">$signature</a>, it
420 will be appended to the message.
422 Once you have finished editing the body of your mail message, you are
423 returned to the <span class="emphasis"><em>compose</em></span> menu providing the functions
424 shown in <a class="xref" href="#tab-func-compose" title="Table 2.11. Most common compose menu keys">Table 2.11, “Most common compose menu keys”</a> to modify, send or postpone the
426 </p><div class="table"><a id="tab-func-compose"></a><p class="title"><b>Table 2.11. Most common compose menu keys</b></p><div class="table-contents"><table summary="Most common compose menu keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>a</td><td><code class="literal"><attach-file></code></td><td>attach a file</td></tr><tr><td>A</td><td><code class="literal"><attach-message></code></td><td>attach message(s) to the message</td></tr><tr><td>Esc k</td><td><code class="literal"><attach-key></code></td><td>attach a PGP public key</td></tr><tr><td>d</td><td><code class="literal"><edit-description></code></td><td>edit description on attachment</td></tr><tr><td>D</td><td><code class="literal"><detach-file></code></td><td>detach a file</td></tr><tr><td>t</td><td><code class="literal"><edit-to></code></td><td>edit the To field</td></tr><tr><td>Esc f</td><td><code class="literal"><edit-from></code></td><td>edit the From field</td></tr><tr><td>r</td><td><code class="literal"><edit-reply-to></code></td><td>edit the Reply-To field</td></tr><tr><td>c</td><td><code class="literal"><edit-cc></code></td><td>edit the Cc field</td></tr><tr><td>b</td><td><code class="literal"><edit-bcc></code></td><td>edit the Bcc field</td></tr><tr><td>y</td><td><code class="literal"><send-message></code></td><td>send the message</td></tr><tr><td>s</td><td><code class="literal"><edit-subject></code></td><td>edit the Subject</td></tr><tr><td>S</td><td><code class="literal"><smime-menu></code></td><td>select S/MIME options</td></tr><tr><td>f</td><td><code class="literal"><edit-fcc></code></td><td>specify an “<span class="quote">Fcc</span>” mailbox</td></tr><tr><td>p</td><td><code class="literal"><pgp-menu></code></td><td>select PGP options</td></tr><tr><td>P</td><td><code class="literal"><postpone-message></code></td><td>postpone this message until later</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>quit (abort) sending the message</td></tr><tr><td>w</td><td><code class="literal"><write-fcc></code></td><td>write the message to a folder</td></tr><tr><td>i</td><td><code class="literal"><ispell></code></td><td>check spelling (if available on your system)</td></tr><tr><td>^F</td><td><code class="literal"><forget-passphrase></code></td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /><p>
427 The compose menu is also used to edit the attachments for a message which can be either files
428 or other messages. The <code class="literal"><attach-message></code> function to will prompt you for a folder to
429 attach messages from. You can now tag messages in that folder and they
430 will be attached to the message you are sending.
431 </p><div class="note"><h3 class="title">Note</h3><p>
433 operations like composing a new mail, replying, forwarding, etc. are
434 not permitted when you are in that folder. The %r in
435 <a class="link" href="#status-format" title="3.281. status_format">$status_format</a> will change to
436 a “<span class="quote">A</span>” to indicate that you are in attach-message mode.
437 </p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-header"></a>5.2. Editing the message header</h3></div></div></div><p>
438 When editing the header because of <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>
439 being set, there are a several pseudo headers available which
440 will not be included in sent messages.
441 </p><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="fcc-header"></a>5.2.1. Fcc: pseudo header</h4></div></div></div><p>
444 <code class="literal">Fcc:</code> <span class="emphasis"><em>filename</em></span>
446 as a header, Mutt will pick up <span class="emphasis"><em>filename</em></span>
447 just as if you had used the <code class="literal"><edit-fcc></code> function in the <span class="emphasis"><em>compose</em></span> menu.
448 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="attach-header"></a>5.2.2. Attach: pseudo header</h4></div></div></div><p>
449 You can also attach files to your message by specifying
451 <code class="literal">Attach:</code> <span class="emphasis"><em>filename</em></span> [ <span class="emphasis"><em>description</em></span> ]
453 where <span class="emphasis"><em>filename</em></span> is the file to attach and <span class="emphasis"><em>description</em></span> is an
454 optional string to use as the description of the attached file.
455 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="pgp-header"></a>5.2.3. Pgp: pseudo header</h4></div></div></div><p>
456 If you want to use PGP, you can specify
458 <code class="literal">Pgp:</code> [ <code class="literal">E</code> | <code class="literal">S</code> | <code class="literal">S</code><span class="emphasis"><em><id></em></span> ]
461 “<span class="quote">E</span>” selects encryption, “<span class="quote">S</span>” selects signing and
462 “<span class="quote">S<id></span>” selects signing with the given key, setting
463 <a class="link" href="#pgp-sign-as" title="3.166. pgp_sign_as">$pgp_sign_as</a>
465 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="in-reply-to-header"></a>5.2.4. In-Reply-To: header</h4></div></div></div><p>
466 When replying to messages, the <span class="emphasis"><em>In-Reply-To:</em></span> header contains the
467 Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
468 <span class="emphasis"><em>References:</em></span> field, which allows you to create a new message thread, for example
469 to create a new message to a mailing list without having to enter the mailing list's address.
470 </p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-crypto"></a>5.3. Sending cryptographically signed/encrypted messages</h3></div></div></div><p>
471 If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
472 through a key selection process when you try to send the message.
473 Mutt will not ask you any questions about keys which have a
474 certified user ID matching one of the message recipients' mail
475 addresses. However, there may be situations in which there are
476 several keys, weakly certified user ID fields, or where no matching
479 In these cases, you are dropped into a menu with a list of keys from
480 which you can select one. When you quit this menu, or mutt can't
481 find any matching keys, you are prompted for a user ID. You can, as
482 usually, abort this prompt using <code class="literal">^G</code>. When you do so, mutt will
483 return to the compose screen.
485 Once you have successfully finished the key selection, the message
486 will be encrypted using the selected public keys when sent out.
488 Most fields of the entries in the key selection menu (see also <a class="link" href="#pgp-entry-format" title="3.158. pgp_entry_format">$pgp_entry_format</a>)
489 have obvious meanings. But some explanations on the capabilities, flags,
490 and validity fields are in order.
492 The flags sequence (%f) will expand to one of the flags in
493 <a class="xref" href="#tab-pgp-menuflags" title="Table 2.12. PGP key menu flags">Table 2.12, “PGP key menu flags”</a>.
494 </p><div class="table"><a id="tab-pgp-menuflags"></a><p class="title"><b>Table 2.12. PGP key menu flags</b></p><div class="table-contents"><table summary="PGP key menu flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>R</td><td>The key has been revoked and can't be used.</td></tr><tr><td>X</td><td>The key is expired and can't be used.</td></tr><tr><td>d</td><td>You have marked the key as disabled.</td></tr><tr><td>c</td><td>There are unknown critical self-signature packets.</td></tr></tbody></table></div></div><br class="table-break" /><p>
495 The capabilities field (%c) expands to a two-character sequence
496 representing a key's capabilities. The first character gives
497 the key's encryption capabilities: A minus sign (“<span class="quote">-</span>”) means
498 that the key cannot be used for encryption. A dot (“<span class="quote">.</span>”) means that
499 it's marked as a signature key in one of the user IDs, but may
500 also be used for encryption. The letter “<span class="quote">e</span>” indicates that
501 this key can be used for encryption.
503 The second character indicates the key's signing capabilities. Once
504 again, a “<span class="quote">-</span>” implies “<span class="quote">not for signing</span>”, “<span class="quote">.</span>” implies
505 that the key is marked as an encryption key in one of the user-ids, and
506 “<span class="quote">s</span>” denotes a key which can be used for signing.
508 Finally, the validity field (%t) indicates how well-certified a user-id
509 is. A question mark (“<span class="quote">?</span>”) indicates undefined validity, a minus
510 character (“<span class="quote">-</span>”) marks an untrusted association, a space character
511 means a partially trusted association, and a plus character (“<span class="quote">+</span>”)
512 indicates complete validity.
513 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-mixmaster"></a>5.4. Sending anonymous messages via mixmaster</h3></div></div></div><p>
514 You may also have compiled mutt to co-operate with Mixmaster, an
515 anonymous remailer. Mixmaster permits you to send your messages
516 anonymously using a chain of remailers. Mixmaster support in mutt is for
517 mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03.
518 It does not support earlier versions or the later so-called version 3 betas,
519 of which the latest appears to be called 2.9b23.
521 To use it, you'll have to obey certain restrictions. Most
522 important, you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code> headers. To tell
523 Mutt to use mixmaster, you have to select a remailer chain, using
524 the mix function on the compose menu.
526 The chain selection screen is divided into two parts. In the
527 (larger) upper part, you get a list of remailers you may use. In
528 the lower part, you see the currently selected chain of remailers.
530 You can navigate in the chain using the <code class="literal"><chain-prev></code> and
531 <code class="literal"><chain-next></code> functions, which are by default bound to the left
532 and right arrows and to the <code class="literal">h</code> and <code class="literal">l</code> keys (think vi
533 keyboard bindings). To insert a remailer at the current chain
534 position, use the <code class="literal"><insert></code> function. To append a remailer behind
535 the current chain position, use <code class="literal"><select-entry></code> or <code class="literal"><append></code>.
536 You can also delete entries from the chain, using the corresponding
537 function. Finally, to abandon your changes, leave the menu, or
538 <code class="literal"><accept></code> them pressing (by default) the <code class="literal">Return</code> key.
540 Note that different remailers do have different capabilities,
541 indicated in the %c entry of the remailer menu lines (see
542 <a class="link" href="#mix-entry-format" title="3.130. mix_entry_format">$mix_entry_format</a>). Most important is
543 the “<span class="quote">middleman</span>” capability, indicated by a capital “<span class="quote">M</span>”: This
544 means that the remailer in question cannot be used as the final
545 element of a chain, but will only forward messages to other
546 mixmaster remailers. For details on the other capabilities, please
547 have a look at the mixmaster documentation.
548 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ff"></a>5.5. Sending format=flowed messages</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-concept"></a>5.5.1. Concept</h4></div></div></div><p>
549 <code class="literal">format=flowed</code>-style messages (or <code class="literal">f=f</code>
550 for short) are <code class="literal">text/plain</code> messages that consist of paragraphs which a receiver's
551 mail client may reformat to its own needs which mostly means to
552 customize line lengths regardless of what the sender sent. Technically this is
553 achieved by letting lines of a “<span class="quote">flowable</span>” paragraph end in spaces
554 except for the last line.
556 While for text-mode clients like mutt it's the best way to assume only a
557 standard 80x25 character cell terminal, it may be desired to let the
558 receiver decide completely how to view a message.
559 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-support"></a>5.5.2. Mutt support</h4></div></div></div><p>
560 Mutt only supports setting the required <code class="literal">format=flowed</code>
561 MIME parameter on outgoing messages if the <a class="link" href="#text-flowed" title="3.285. text_flowed">$text_flowed</a>
562 variable is set, specifically it does not add the
565 After editing the initial message text and before entering
566 the compose menu, mutt properly space-stuffes the message.
567 <span class="emphasis"><em>Space-stuffing</em></span> is required by RfC3676 defining
568 <code class="literal">format=flowed</code> and means to prepend a space to:
569 </p><div class="itemizedlist"><ul type="disc"><li><p>all lines starting with a space</p></li><li><p>lines starting with the word “<span class="quote"><code class="literal">From</code></span>”
570 followed by space</p></li><li><p>all lines starting with “<span class="quote"><code class="literal">></code></span>” which
571 is not intended to be a quote character</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
572 Mutt only supports space-stuffing
573 for the first two types of lines but not for the third: It is impossible to
574 safely detect whether a leading <code class="literal">></code> character starts a
575 quote or not. Furthermore, Mutt only applies space-stuffing
576 <span class="emphasis"><em>once</em></span> after the initial edit is finished.
578 All leading spaces are to be removed by receiving clients to restore
579 the original message prior to further processing.
580 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-editor"></a>5.5.3. Editor considerations</h4></div></div></div><p>
581 As mutt provides no additional features to compose <code class="literal">f=f</code>
582 messages, it's completely up to the user and his editor to produce
583 proper messages. Please consider your editor's documentation if you
584 intend to send <code class="literal">f=f</code> messages.
586 Please note that when editing messages from the compose menu several
587 times before really sending a mail, it's up to the user to ensure that
588 the message is properly space-stuffed.
590 For example, <span class="emphasis"><em>vim</em></span> provides the <code class="literal">w</code>
591 flag for its <code class="literal">formatoptions</code> setting to assist in
592 creating <code class="literal">f=f</code> messages, see <code class="literal">:help
593 fo-table</code> for details.
594 </p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="forwarding-mail"></a>6. Forwarding and Bouncing Mail</h2></div></div></div><p>
595 Bouncing and forwarding let you send an existing message to recipients
596 that you specify. Bouncing a message sends a verbatim copy of a message
597 to alternative addresses as if they were the message's original
598 recipients specified in the Bcc header.
599 Forwarding a message, on the other hand, allows you to modify the message
600 before it is resent (for example, by adding your own comments). Bouncing
601 is done using the <code class="literal"><bounce></code> function and forwarding
602 using the <code class="literal"><forward></code> function bound to “<span class="quote">b</span>” and “<span class="quote">f</span>”
605 Forwarding can be done by including the original message in the new
606 message's body (surrounded by indicating lines) or including it as a MIME
607 attachment, depending on the value of the <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> variable. Decoding of attachments,
608 like in the pager, can be controlled by the <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> variables,
609 respectively. The desired forwarding format may depend on the content,
610 therefore <span class="emphasis"><em>$mime_forward</em></span> is a quadoption which, for
611 example, can be set to “<span class="quote">ask-no</span>”.
613 The inclusion of headers is controlled by the current setting of the
614 <a class="link" href="#weed" title="3.304. weed">$weed</a> variable, unless <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is set.
616 Editing the message to forward follows the same procedure as sending or
617 replying to a message does.
618 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="postponing-mail"></a>7. Postponing Mail</h2></div></div></div><p>
619 At times it is desirable to delay sending a message that you have
620 already begun to compose. When the <code class="literal"><postpone-message></code> function is
621 used in the <span class="emphasis"><em>compose</em></span> menu, the body of your message and attachments
622 are stored in the mailbox specified by the <a class="link" href="#postponed" title="3.227. postponed">$postponed</a> variable. This means that you can recall the
623 message even if you exit Mutt and then restart it at a later time.
625 Once a message is postponed, there are several ways to resume it. From the
626 command line you can use the “<span class="quote">-p</span>” option, or if you compose a new
627 message from the <span class="emphasis"><em>index</em></span> or <span class="emphasis"><em>pager</em></span> you will be prompted if postponed
628 messages exist. If multiple messages are currently postponed, the
629 <span class="emphasis"><em>postponed</em></span> menu will pop up and you can select which message you would
631 </p><div class="note"><h3 class="title">Note</h3><p>
632 If you postpone a reply to a message, the reply setting of
633 the message is only updated when you actually finish the message and
634 send it. Also, you must be in the same folder with the message you
635 replied to for the status of the message to be updated.
637 See also the <a class="link" href="#postpone" title="3.226. postpone">$postpone</a> quad-option.
638 </p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="configuration"></a>Chapter 3. Configuration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="configuration-files"></a>1. Location of initialization files</h2></div></div></div><p>
639 While the default configuration (or “<span class="quote">preferences</span>”) make Mutt
640 usable right out of the box, it is often desirable to tailor Mutt to
641 suit your own tastes. When Mutt is first invoked, it will attempt to
642 read the “<span class="quote">system</span>” configuration file (defaults set by your local
643 system administrator), unless the “<span class="quote">-n</span>” <a class="link" href="#commandline" title="1. Command line options">command line</a> option is specified. This file is typically
644 <code class="literal">/usr/local/share/mutt/Muttrc</code> or <code class="literal">/etc/Muttrc</code>. Mutt
645 will next look for a file named <code class="literal">.muttrc</code> in your home
646 directory. If this file does not exist and your home directory has
647 a subdirectory named <code class="literal">.mutt</code>, mutt try to load a file named
648 <code class="literal">.mutt/muttrc</code>.
650 <code class="literal">.muttrc</code> is the file where you will usually place your <a class="link" href="#commands" title="2. Configuration Commands">commands</a> to configure Mutt.
652 In addition, mutt supports version specific configuration files that are
653 parsed instead of the default files as explained above. For instance, if
654 your system has a <code class="literal">Muttrc-0.88</code> file in the system configuration
655 directory, and you are running version 0.88 of mutt, this file will be
656 sourced instead of the <code class="literal">Muttrc</code> file. The same is true of the user
657 configuration file, if you have a file <code class="literal">.muttrc-0.88.6</code> in your home
658 directory, when you run mutt version 0.88.6, it will source this file
659 instead of the default <code class="literal">.muttrc</code> file. The version number is the
660 same which is visible using the “<span class="quote">-v</span>” <a class="link" href="#commandline" title="1. Command line options">command line</a> switch or using the <code class="literal">show-version</code> key (default:
661 V) from the index menu.
662 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttrc-syntax"></a>2. Syntax of Initialization Files</h2></div></div></div><p>
663 An initialization file consists of a series of <a class="link" href="#commands" title="2. Configuration Commands">commands</a>. Each line of the file may contain one or more commands.
664 When multiple commands are used, they must be separated by a semicolon
666 </p><div class="example"><a id="ex-rc-multiple-cmds"></a><p class="title"><b>Example 3.1. Multiple configuration commands per line</b></p><div class="example-contents"><pre class="screen">
667 set realname='Mutt user' ; ignore x-
668 </pre></div></div><br class="example-break" /><p>
669 The hash mark, or pound sign
670 (“<span class="quote">#</span>”), is used as a “<span class="quote">comment</span>” character. You can use it to
671 annotate your initialization file. All text after the comment character
672 to the end of the line is ignored. For example,
673 </p><div class="example"><a id="ex-ec-comment"></a><p class="title"><b>Example 3.2. Commenting configuration files</b></p><div class="example-contents"><pre class="screen">
674 my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
675 </pre></div></div><br class="example-break" /><p>
676 Single quotes (') and double quotes (") can be used to quote strings
677 which contain spaces or other special characters. The difference between
678 the two types of quotes is similar to that of many popular shell programs,
679 namely that a single quote is used to specify a literal string (one that is
680 not interpreted for shell variables or quoting with a backslash [see
681 next paragraph]), while double quotes indicate a string for which
682 should be evaluated. For example, backticks are evaluated inside of double
683 quotes, but <span class="bold"><strong>not</strong></span> for single quotes.
685 \ quotes the next character, just as in shells such as bash and zsh.
686 For example, if want to put quotes “<span class="quote">"</span>” inside of a string, you can use
687 “<span class="quote">\</span>” to force the next character to be a literal instead of interpreted
689 </p><div class="example"><a id="ex-rc-quote"></a><p class="title"><b>Example 3.3. Escaping quotes in congfiguration files</b></p><div class="example-contents"><pre class="screen">
690 set realname="Michael \"MuttDude\" Elkins"
691 </pre></div></div><br class="example-break" /><p>
692 “<span class="quote">\\</span>” means to insert a literal “<span class="quote">\</span>” into the line.
693 “<span class="quote">\n</span>” and “<span class="quote">\r</span>” have their usual C meanings of linefeed and
694 carriage-return, respectively.
696 A \ at the end of a line can be used to split commands over
697 multiple lines, provided that the split points don't appear in the
698 middle of command names.
700 It is also possible to substitute the output of a Unix command in an
701 initialization file. This is accomplished by enclosing the command in
702 backticks (``). For example,
703 </p><div class="example"><a id="ex-rc-backtick"></a><p class="title"><b>Example 3.4. Using external command's output in configuration files</b></p><div class="example-contents"><pre class="screen">
704 my_hdr X-Operating-System: `uname -a`
705 </pre></div></div><br class="example-break" /><p>
706 The output of the Unix command “<span class="quote">uname -a</span>” will be substituted before the
708 </p><div class="note"><h3 class="title">Note</h3><p>
709 Since initialization files are line oriented, only
710 the first line of output from the Unix command will be substituted.
712 Both environment variables and mutt variables can be accessed by
713 prepending “<span class="quote">$</span>” to the name of the variable. For example,
714 </p><div class="example"><a id="ex-rc-env"></a><p class="title"><b>Example 3.5. Using environment variables in configuration files</b></p><div class="example-contents"><pre class="screen">
715 set record=+sent_on_$HOSTNAME
716 </pre></div></div><br class="example-break" /><p>
717 will cause mutt to save outgoing messages to a folder named
718 “<span class="quote">sent_on_kremvax</span>” if the environment variable HOSTNAME is set to
719 “<span class="quote">kremvax.</span>” (See <a class="link" href="#record" title="3.242. record">$record</a> for
722 Mutt expands the variable when it is assigned, not when it is used. If
723 the value of a variable on the right-hand side of an assignment
724 changes after the assignment, the variable on the left-hand side will
727 The commands understood by mutt are explained in the next paragraphs.
728 For a complete list, see the <a class="link" href="#commands" title="2. Configuration Commands">command reference</a>.
730 All configuration files are expected to be in the current locale as
731 specified by the <a class="link" href="#charset" title="3.25. charset">$charset</a> variable
732 which doesn't have a default value since it's determined by Mutt at startup.
733 If a configuration file is not encoded in the same character set the
734 <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a>
735 variable should be used: all lines starting with the next are recoded
736 from $config_charset to $charset.
738 This mechanism should be avoided if possible as it has the
739 following implications:
740 </p><div class="itemizedlist"><ul type="disc"><li><p>These variables should be set early in a configuration
741 file with $charset preceding $config_charset so Mutt
742 know what character set to convert to.</p></li><li><p>If $config_charset is set, it should be set
743 in each configuration file because the value is global and <span class="emphasis"><em>not</em></span>
744 per configuration file.</p></li><li><p>Because Mutt first recodes a line before it attempts to parse it,
745 a conversion introducing question marks or other characters as
746 part of errors (unconvertable characters, transliteration) may introduce syntax
747 errors or silently change the meaning of certain tokens (e.g. inserting
748 question marks into regular expressions).</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="addrgroup"></a>3. Address groups</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">group</code> [
749 <code class="option">-group</code>
750 <em class="replaceable"><code>name</code></em>
752 <code class="option">-rx</code>
753 <em class="replaceable"><code>expr</code></em>
755 <code class="option">-addr</code>
756 <em class="replaceable"><code>expr</code></em>
757 ... }</p></div><div class="cmdsynopsis"><p><code class="command">ungroup</code> [
758 <code class="option">-group</code>
759 <em class="replaceable"><code>name</code></em>
761 <em class="replaceable"><code>*</code></em>
763 <code class="option">-rx</code>
764 <em class="replaceable"><code>expr</code></em>
766 <code class="option">-addr</code>
767 <em class="replaceable"><code>expr</code></em>
769 <code class="literal">group</code> is used to directly add either addresses or
770 regular expressions to the specified group or groups. The different
771 categories of arguments to the <code class="literal">group</code> command can be
772 in any order. The flags <code class="literal">-rx</code> and
773 <code class="literal">-addr</code> specify what the following strings (that cannot
774 begin with a hyphen) should be interpreted as: either a regular
775 expression or an email address, respectively.
777 These address groups can also be created implicitly by the
778 <a class="link" href="#alias" title="4. Defining/Using aliases">alias</a>, <a class="link" href="#lists" title="12. Mailing lists">lists</a>,
779 <a class="link" href="#lists" title="12. Mailing lists">subscribe</a> and
780 <a class="link" href="#alternates" title="11. Alternative addresses">alternates</a> commands by specifying the
781 optional <code class="literal">-group</code> option.
783 Once defined, these address groups can be used in
784 <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> to search for and limit the
785 display to messages matching a group.
787 <code class="literal">ungroup</code> is used to remove addresses or regular
788 expressions from the specified group or groups. The syntax is similar to
789 the <code class="literal">group</code> command, however the special character
790 <code class="literal">*</code> can be used to empty a group of all of its
792 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alias"></a>4. Defining/Using aliases</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alias</code> [
793 <code class="option">-group</code>
794 <em class="replaceable"><code>name</code></em>
796 <em class="replaceable"><code>key</code></em>
798 <em class="replaceable"><code>address</code></em>
800 <em class="replaceable"><code>address</code></em>
802 It's usually very cumbersome to remember or type out the address of someone
803 you are communicating with. Mutt allows you to create “<span class="quote">aliases</span>” which map
804 a short string to a full address.
805 </p><div class="note"><h3 class="title">Note</h3><p>
806 If you want to create an alias for more than
807 one address, you <span class="bold"><strong>must</strong></span> separate the addresses with a comma (“<span class="quote">,</span>”).
809 The optional <code class="literal">-group</code> argument to
810 <code class="literal">alias</code> causes the aliased address(es) to be added to
811 the named <span class="emphasis"><em>group</em></span>.
813 To remove an alias or aliases (“<span class="quote">*</span>” means all aliases):
814 </p><div class="cmdsynopsis"><p><code class="command">unalias</code> [
815 <code class="option">-group</code>
816 <em class="replaceable"><code>name</code></em>
818 <em class="replaceable"><code>*</code></em>
820 <em class="replaceable"><code>key</code></em>
821 ... }</p></div><pre class="screen">
822 alias muttdude me@cs.hmc.edu (Michael Elkins)
823 alias theguys manny, moe, jack
825 Unlike other mailers, Mutt doesn't require aliases to be defined
826 in a special file. The <code class="literal">alias</code> command can appear anywhere in
827 a configuration file, as long as this file is <a class="link" href="#source" title="27. Reading initialization commands from another file">sourced</a>. Consequently, you can have multiple alias files, or
828 you can have all aliases defined in your muttrc.
830 On the other hand, the <a class="link" href="#create-alias"><code class="literal"><create-alias></code></a>
831 function can use only one file, the one pointed to by the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> variable (which is
832 <code class="literal">˜/.muttrc</code> by default). This file is not special either,
833 in the sense that Mutt will happily append aliases to any file, but in
834 order for the new aliases to take effect you need to explicitly <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> this file too.
837 </p><div class="example"><a id="ex-alias-external"></a><p class="title"><b>Example 3.6. Configuring external alias files</b></p><div class="example-contents"><pre class="screen">
838 source /usr/local/share/Mutt.aliases
839 source ~/.mail_aliases
840 set alias_file=~/.mail_aliases
841 </pre></div></div><br class="example-break" /><p>
842 To use aliases, you merely use the alias at any place in mutt where mutt
843 prompts for addresses, such as the <span class="emphasis"><em>To:</em></span> or <span class="emphasis"><em>Cc:</em></span> prompt. You can
844 also enter aliases in your editor at the appropriate headers if you have the
845 <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable set.
847 In addition, at the various address prompts, you can use the tab character
848 to expand a partial alias to the full alias. If there are multiple matches,
849 mutt will bring up a menu with the matching aliases. In order to be
850 presented with the full list of aliases, you must hit tab with out a partial
851 alias, such as at the beginning of the prompt or after a comma denoting
854 In the alias menu, you can select as many aliases as you want with the
855 <code class="literal">select-entry</code> key (default: <Return>), and use the
856 <span class="emphasis"><em>exit</em></span> key (default: q) to return to the address prompt.
857 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="bind"></a>5. Changing the default key bindings</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">bind</code>
858 <em class="replaceable"><code>map</code></em>
860 <em class="replaceable"><code>key</code></em>
862 <em class="replaceable"><code>function</code></em>
864 This command allows you to change the default key bindings (operation
865 invoked when pressing a key).
867 <span class="emphasis"><em>map</em></span> specifies in which menu the binding belongs. Multiple maps may
868 be specified by separating them with commas (no additional whitespace is
869 allowed). The currently defined maps are:
870 </p><a id="maps"></a><div class="variablelist"><dl><dt><span class="term">generic</span></dt><dd><p>
871 This is not a real menu, but is used as a fallback for all of the other
872 menus except for the pager and editor modes. If a key is not defined in
873 another menu, Mutt will look for a binding to use in this menu. This allows
874 you to bind a key to a certain function in multiple menus instead of having
875 multiple bind statements to accomplish the same task.
876 </p></dd><dt><span class="term">alias</span></dt><dd><p>
877 The alias menu is the list of your personal aliases as defined in your
878 muttrc. It is the mapping from a short alias name to the full email
879 address(es) of the recipient(s).
880 </p></dd><dt><span class="term">attach</span></dt><dd><p>
881 The attachment menu is used to access the attachments on received messages.
882 </p></dd><dt><span class="term">browser</span></dt><dd><p>
883 The browser is used for both browsing the local directory structure, and for
884 listing all of your incoming mailboxes.
885 </p></dd><dt><span class="term">editor</span></dt><dd><p>
886 The editor is the line-based editor the user enters text data.
887 </p></dd><dt><span class="term">index</span></dt><dd><p>
888 The index is the list of messages contained in a mailbox.
889 </p></dd><dt><span class="term">compose</span></dt><dd><p>
890 The compose menu is the screen used when sending a new message.
891 </p></dd><dt><span class="term">pager</span></dt><dd><p>
892 The pager is the mode used to display message/attachment data, and help
894 </p></dd><dt><span class="term">pgp</span></dt><dd><p>
895 The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
897 </p></dd><dt><span class="term">smime</span></dt><dd><p>
898 The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
900 </p></dd><dt><span class="term">postpone</span></dt><dd><p>
901 The postpone menu is similar to the index menu, except is used when
902 recalling a message the user was composing, but saved until later.
903 </p></dd><dt><span class="term">query</span></dt><dd><p>
904 The query menu is the browser for results returned by
905 <a class="link" href="#query-command" title="3.234. query_command">$query_command</a>.
906 </p></dd><dt><span class="term">mix</span></dt><dd><p>
907 The mixmaster screen is used to select remailer options for outgoing
908 messages (if Mutt is compiled with Mixmaster support).
909 </p></dd></dl></div><p>
910 <span class="emphasis"><em>key</em></span> is the key (or key sequence) you wish to bind. To specify a
911 control character, use the sequence <span class="emphasis"><em>\Cx</em></span>, where <span class="emphasis"><em>x</em></span> is the
912 letter of the control character (for example, to specify control-A use
913 “<span class="quote">\Ca</span>”). Note that the case of <span class="emphasis"><em>x</em></span> as well as <span class="emphasis"><em>\C</em></span> is
914 ignored, so that <span class="emphasis"><em>\CA</em></span>, <span class="emphasis"><em>\Ca</em></span>, <span class="emphasis"><em>\cA</em></span> and <span class="emphasis"><em>\ca</em></span> are all
915 equivalent. An alternative form is to specify the key as a three digit
916 octal number prefixed with a “<span class="quote">\</span>” (for example <span class="emphasis"><em>\177</em></span> is
917 equivalent to <span class="emphasis"><em>\c?</em></span>). In addition, <span class="emphasis"><em>key</em></span> may
918 be a symbolic name as shown in <a class="xref" href="#tab-key-names" title="Table 3.1. Symbolic key names">Table 3.1, “Symbolic key names”</a>.
919 </p><div class="table"><a id="tab-key-names"></a><p class="title"><b>Table 3.1. Symbolic key names</b></p><div class="table-contents"><table summary="Symbolic key names" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Symbolic name</th><th>Meaning</th></tr></thead><tbody><tr><td>\t</td><td>tab</td></tr><tr><td><tab></td><td>tab</td></tr><tr><td><backtab></td><td>backtab / shift-tab</td></tr><tr><td>\r</td><td>carriage return</td></tr><tr><td>\n</td><td>newline</td></tr><tr><td>\e</td><td>escape</td></tr><tr><td><esc></td><td>escape</td></tr><tr><td><up></td><td>up arrow</td></tr><tr><td><down></td><td>down arrow</td></tr><tr><td><left></td><td>left arrow</td></tr><tr><td><right></td><td>right arrow</td></tr><tr><td><pageup></td><td>Page Up</td></tr><tr><td><pagedown></td><td>Page Down</td></tr><tr><td><backspace></td><td>Backspace</td></tr><tr><td><delete></td><td>Delete</td></tr><tr><td><insert></td><td>Insert</td></tr><tr><td><enter></td><td>Enter</td></tr><tr><td><return></td><td>Return</td></tr><tr><td><home></td><td>Home</td></tr><tr><td><end></td><td>End</td></tr><tr><td><space></td><td>Space bar</td></tr><tr><td><f1></td><td>function key 1</td></tr><tr><td><f10></td><td>function key 10</td></tr></tbody></table></div></div><br class="table-break" /><p>
920 <span class="emphasis"><em>key</em></span> does not need to be enclosed in quotes unless it contains a
921 space (“<span class="quote"> </span>”) or semi-colon (“<span class="quote">;</span>”).
923 <span class="emphasis"><em>function</em></span> specifies which action to take when <span class="emphasis"><em>key</em></span> is pressed.
924 For a complete list of functions, see the <a class="link" href="#functions" title="4. Functions">reference</a>. The special function <code class="literal"><noop></code> unbinds the specified key
926 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="charset-hook"></a>6. Defining aliases for character sets </h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">charset-hook</code>
927 <em class="replaceable"><code>alias</code></em>
929 <em class="replaceable"><code>charset</code></em>
930 </p></div><div class="cmdsynopsis"><p><code class="command">iconv-hook</code>
931 <em class="replaceable"><code>charset</code></em>
933 <em class="replaceable"><code>local-charset</code></em>
935 The <code class="literal">charset-hook</code> command defines an alias for a character set.
936 This is useful to properly display messages which are tagged with a
937 character set name not known to mutt.
939 The <code class="literal">iconv-hook</code> command defines a system-specific name for a
940 character set. This is helpful when your systems character
941 conversion library insists on using strange, system-specific names
943 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="folder-hook"></a>7. Setting variables based upon mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">folder-hook</code>
944 <em class="replaceable"><code>[!]regexp</code></em>
946 <em class="replaceable"><code>command</code></em>
948 It is often desirable to change settings based on which mailbox you are
949 reading. The folder-hook command provides a method by which you can execute
950 any configuration command. <span class="emphasis"><em>regexp</em></span> is a regular expression specifying
951 in which mailboxes to execute <span class="emphasis"><em>command</em></span> before loading. If a mailbox
952 matches multiple folder-hook's, they are executed in the order given in the
954 </p><div class="note"><h3 class="title">Note</h3><p>
955 If you use the “<span class="quote">!</span>” shortcut for <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a> at the beginning of the pattern, you must place it
956 inside of double or single quotes in order to distinguish it from the
957 logical <span class="emphasis"><em>not</em></span> operator for the expression.
958 </p></div><div class="note"><h3 class="title">Note</h3><p>
959 Settings are <span class="emphasis"><em>not</em></span> restored when you leave the mailbox.
960 For example, a command action to perform is to change the sorting method
961 based upon the mailbox being read:
962 </p></div><pre class="screen">
963 folder-hook mutt set sort=threads
965 However, the sorting method is not restored to its previous value when
966 reading a different mailbox. To specify a <span class="emphasis"><em>default</em></span> command, use the
967 pattern “<span class="quote">.</span>” before other folder-hooks adjusting a value on a per-folder basis
968 because folder-hooks are evaluated in the order given in the configuration file.
969 The following example will set the <a class="link" href="#sort" title="3.273. sort">sort</a> variable
970 to <code class="literal">date-sent</code> for all folders but to <code class="literal">threads</code>
971 for all folders containing “<span class="quote">mutt</span>” in their name.
972 </p><div class="example"><a id="ex-folder-sorting"></a><p class="title"><b>Example 3.7. Setting sort method based on mailbox name</b></p><div class="example-contents"><pre class="screen">
973 folder-hook . set sort=date-sent
974 folder-hook mutt set sort=threads
975 </pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="macro"></a>8. Keyboard macros</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">macro</code>
976 <em class="replaceable"><code>menu</code></em>
978 <em class="replaceable"><code>key</code></em>
980 <em class="replaceable"><code>sequence</code></em>
982 <em class="replaceable"><code>description</code></em>
984 Macros are useful when you would like a single key to perform a series of
985 actions. When you press <span class="emphasis"><em>key</em></span> in menu <span class="emphasis"><em>menu</em></span>, Mutt will behave as if
986 you had typed <span class="emphasis"><em>sequence</em></span>. So if you have a common sequence of commands
987 you type, you can create a macro to execute those commands with a single
990 <span class="emphasis"><em>menu</em></span> is the <a class="link" href="#maps">map</a> which the macro will be bound in.
991 Multiple maps may be specified by separating multiple menu arguments by
992 commas. Whitespace may not be used in between the menu arguments and the
993 commas separating them.
995 <span class="emphasis"><em>key</em></span> and <span class="emphasis"><em>sequence</em></span> are expanded by the same rules as the
996 <a class="link" href="#bind" title="5. Changing the default key bindings">key bindings</a> with some additions. The
997 first is that control characters in <span class="emphasis"><em>sequence</em></span> can also be specified
998 as <span class="emphasis"><em>^x</em></span>. In order to get a caret (“<span class="quote">^</span>”) you need to use
999 <span class="emphasis"><em>^^</em></span>. Secondly, to specify a certain key such as <span class="emphasis"><em>up</em></span>
1000 or to invoke a function directly, you can use the format
1001 <span class="emphasis"><em><key name></em></span> and <span class="emphasis"><em><function name></em></span>. For a listing of key
1002 names see the section on <a class="link" href="#bind" title="5. Changing the default key bindings">key bindings</a>. Functions
1003 are listed in the <a class="link" href="#functions" title="4. Functions">reference</a>.
1005 The advantage with using function names directly is that the macros will
1006 work regardless of the current key bindings, so they are not dependent on
1007 the user having particular key definitions. This makes them more robust
1008 and portable, and also facilitates defining of macros in files used by more
1009 than one user (e.g., the system Muttrc).
1011 Optionally you can specify a descriptive text after <span class="emphasis"><em>sequence</em></span>,
1012 which is shown in the help screens.
1013 </p><div class="note"><h3 class="title">Note</h3><p>
1014 Macro definitions (if any) listed in the help screen(s), are
1015 silently truncated at the screen width, and are not wrapped.
1016 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="color"></a>9. Using color and mono video attributes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">color</code>
1017 <em class="replaceable"><code>object</code></em>
1019 <em class="replaceable"><code>foreground</code></em>
1021 <em class="replaceable"><code>background</code></em>
1022 </p></div><div class="cmdsynopsis"><p><code class="command">color</code> {
1023 <code class="option">header</code>
1025 <code class="option">body</code>
1027 <em class="replaceable"><code>foreground</code></em>
1029 <em class="replaceable"><code>background</code></em>
1031 <em class="replaceable"><code>regexp</code></em>
1032 </p></div><div class="cmdsynopsis"><p><code class="command">color</code>
1033 <code class="option">index</code>
1035 <em class="replaceable"><code>foreground</code></em>
1037 <em class="replaceable"><code>background</code></em>
1039 <em class="replaceable"><code>pattern</code></em>
1040 </p></div><div class="cmdsynopsis"><p><code class="command">uncolor</code>
1041 <code class="option">index</code>
1043 <em class="replaceable"><code>*</code></em>
1045 <em class="replaceable"><code>pattern</code></em>
1047 If your terminal supports color, you can spice up Mutt by creating your own
1048 color scheme. To define the color of an object (type of information), you
1049 must specify both a foreground color <span class="bold"><strong>and</strong></span> a background color (it is not
1050 possible to only specify one or the other).
1052 <span class="emphasis"><em>header</em></span> and <span class="emphasis"><em>body</em></span> match <span class="emphasis"><em>regexp</em></span>
1053 in the header/body of a message, <span class="emphasis"><em>index</em></span> matches <span class="emphasis"><em>pattern</em></span>
1054 (see <a class="xref" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">Section 2, “Patterns: Searching, Limiting and Tagging”</a>) in the message index.
1056 <span class="emphasis"><em>object</em></span> can be one of:
1057 </p><div class="itemizedlist"><ul type="disc"><li><p>attachment</p></li><li><p>bold (hiliting bold patterns in the body of messages)</p></li><li><p>error (error messages printed by Mutt)</p></li><li><p>hdrdefault (default color of the message header in the pager)</p></li><li><p>indicator (arrow or bar used to indicate the current item in a menu)</p></li><li><p>markers (the “<span class="quote">+</span>” markers at the beginning of wrapped lines in the pager)</p></li><li><p>message (informational messages)</p></li><li><p>normal</p></li><li><p>quoted (text matching <a class="link" href="#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a> in the body of a message)</p></li><li><p>quoted1, quoted2, ..., quoted<span class="bold"><strong>N</strong></span> (higher levels of quoting)</p></li><li><p>search (hiliting of words in the pager)</p></li><li><p>signature</p></li><li><p>status (mode lines used to display info about the mailbox or message)</p></li><li><p>tilde (the “<span class="quote">˜</span>” used to pad blank lines in the pager)</p></li><li><p>tree (thread tree drawn in the message index and attachment menu)</p></li><li><p>underline (hiliting underlined patterns in the body of messages)</p></li></ul></div><p>
1058 <span class="emphasis"><em>foreground</em></span> and <span class="emphasis"><em>background</em></span> can be one of the following:
1059 </p><div class="itemizedlist"><ul type="disc"><li><p>white</p></li><li><p>black</p></li><li><p>green</p></li><li><p>magenta</p></li><li><p>blue</p></li><li><p>cyan</p></li><li><p>yellow</p></li><li><p>red</p></li><li><p>default</p></li><li><p>color<span class="emphasis"><em>x</em></span></p></li></ul></div><p>
1060 <span class="emphasis"><em>foreground</em></span> can optionally be prefixed with the keyword <code class="literal">bright</code> to make
1061 the foreground color boldfaced (e.g., <code class="literal">brightred</code>).
1063 If your terminal supports it, the special keyword <span class="emphasis"><em>default</em></span> can be
1064 used as a transparent color. The value <span class="emphasis"><em>brightdefault</em></span> is also valid.
1065 If Mutt is linked against the <span class="emphasis"><em>S-Lang</em></span> library, you also need to set
1066 the <span class="emphasis"><em>COLORFGBG</em></span> environment variable to the default colors of your
1067 terminal for this to work; for example (for Bourne-like shells):
1068 </p><pre class="screen">
1069 set COLORFGBG="green;black"
1071 </pre><div class="note"><h3 class="title">Note</h3><p>
1072 The <span class="emphasis"><em>S-Lang</em></span> library requires you to use the <span class="emphasis"><em>lightgray</em></span>
1073 and <span class="emphasis"><em>brown</em></span> keywords instead of <span class="emphasis"><em>white</em></span> and <span class="emphasis"><em>yellow</em></span> when
1074 setting this variable.
1075 </p></div><div class="note"><h3 class="title">Note</h3><p>
1076 The uncolor command can be applied to the index object only. It
1077 removes entries from the list. You <span class="bold"><strong>must</strong></span> specify the same pattern
1078 specified in the color command for it to be removed. The pattern “<span class="quote">*</span>” is
1079 a special token which means to clear the color index list of all entries.
1081 Mutt also recognizes the keywords <span class="emphasis"><em>color0</em></span>, <span class="emphasis"><em>color1</em></span>, …,
1082 <span class="emphasis"><em>color</em></span><span class="bold"><strong>N-1</strong></span> (<span class="bold"><strong>N</strong></span> being the number of colors supported
1083 by your terminal). This is useful when you remap the colors for your
1084 display (for example by changing the color associated with <span class="emphasis"><em>color2</em></span>
1085 for your xterm), since color names may then lose their normal meaning.
1087 If your terminal does not support color, it is still possible change the video
1088 attributes through the use of the “<span class="quote">mono</span>” command:
1089 </p><a id="mono"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mono</code>
1090 <em class="replaceable"><code>object</code></em>
1092 <em class="replaceable"><code>attribute</code></em>
1093 </p></div><div class="cmdsynopsis"><p><code class="command">mono</code> {
1094 <code class="option">header</code>
1096 <code class="option">body</code>
1098 <em class="replaceable"><code>attribute</code></em>
1100 <em class="replaceable"><code>regexp</code></em>
1101 </p></div><div class="cmdsynopsis"><p><code class="command">mono</code>
1102 <code class="option">index</code>
1104 <em class="replaceable"><code>attribute</code></em>
1106 <em class="replaceable"><code>pattern</code></em>
1107 </p></div><div class="cmdsynopsis"><p><code class="command">unmono</code>
1108 <code class="option">index</code>
1110 <em class="replaceable"><code>*</code></em>
1112 <em class="replaceable"><code>pattern</code></em>
1114 For <span class="emphasis"><em>object</em></span>, see the color command. <span class="emphasis"><em>attribute</em></span>
1115 can be one of the following:
1116 </p><div class="itemizedlist"><ul type="disc"><li><p>none</p></li><li><p>bold</p></li><li><p>underline</p></li><li><p>reverse</p></li><li><p>standout</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ignore"></a>10. Message header display</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">ignore</code>
1117 <em class="replaceable"><code>pattern</code></em>
1119 <em class="replaceable"><code>pattern</code></em>
1120 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unignore</code> {
1121 <em class="replaceable"><code>*</code></em>
1123 <em class="replaceable"><code>pattern</code></em>
1125 Messages often have many header fields added by automatic processing systems,
1126 or which may not seem useful to display on the screen. This command allows
1127 you to specify header fields which you don't normally want to see in the pager.
1129 You do not need to specify the full header field name. For example,
1130 “<span class="quote">ignore content-</span>” will ignore all header fields that begin with the pattern
1131 “<span class="quote">content-</span>”. “<span class="quote">ignore *</span>” will ignore all headers.
1133 To remove a previously added token from the list, use the “<span class="quote">unignore</span>” command.
1134 The “<span class="quote">unignore</span>” command will make Mutt display headers with the given pattern.
1135 For example, if you do “<span class="quote">ignore x-</span>” it is possible to “<span class="quote">unignore x-mailer</span>”.
1137 “<span class="quote">unignore *</span>” will remove all tokens from the ignore list.
1140 </p><div class="example"><a id="ex-header-weeding"></a><p class="title"><b>Example 3.8. Header weeding</b></p><div class="example-contents"><pre class="screen">
1141 # Sven's draconian header weeding
1143 unignore from date subject to cc
1144 unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
1146 </pre></div></div><br class="example-break" /><a id="hdr-order"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">hdr_order</code>
1147 <em class="replaceable"><code>header</code></em>
1149 <em class="replaceable"><code>header</code></em>
1150 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unhdr_order</code> {
1151 <em class="replaceable"><code>*</code></em>
1153 <em class="replaceable"><code>header</code></em>
1155 With the <code class="literal">hdr_order</code> command you can specify an order in
1156 which mutt will attempt to present these headers to you when viewing messages.
1158 “<span class="quote">unhdr_order *</span>” will clear all previous headers from the order list,
1159 thus removing the header order effects set by the system-wide startup file.
1160 </p><div class="example"><a id="ex-hdr-order"></a><p class="title"><b>Example 3.9. Configuring header display order</b></p><div class="example-contents"><pre class="screen">
1161 hdr_order From Date: From: To: Cc: Subject:
1162 </pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternates"></a>11. Alternative addresses</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alternates</code> [
1163 <code class="option">-group</code>
1164 <em class="replaceable"><code>name</code></em>
1166 <em class="replaceable"><code>regexp</code></em>
1168 <em class="replaceable"><code>regexp</code></em>
1169 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unalternates</code> [
1170 <code class="option">-group</code>
1171 <em class="replaceable"><code>name</code></em>
1173 <em class="replaceable"><code>*</code></em>
1175 <em class="replaceable"><code>regexp</code></em>
1177 With various functions, mutt will treat messages differently,
1178 depending on whether you sent them or whether you received them from
1179 someone else. For instance, when replying to a message that you
1180 sent to a different party, mutt will automatically suggest to send
1181 the response to the original message's recipients -- responding to
1182 yourself won't make much sense in many cases. (See <a class="link" href="#reply-to" title="3.245. reply_to">$reply_to</a>.)
1184 Many users receive e-mail under a number of different addresses. To
1185 fully use mutt's features here, the program must be able to
1186 recognize what e-mail addresses you receive mail under. That's the
1187 purpose of the <code class="literal">alternates</code> command: It takes a list of regular
1188 expressions, each of which can identify an address under which you
1191 As addresses are matched using regular expressions and not exact strict
1192 comparisons, you should make sure you specify your addresses as precise
1193 as possible to avoid mismatches. For example, if you specify:
1194 </p><pre class="screen">
1195 alternates user@example
1197 mutt will consider “<span class="quote"><code class="literal">some-user@example</code></span>” as
1198 being your address, too which may not be desired. As a solution, in such
1199 cases addresses should be specified as:
1200 </p><pre class="screen">
1201 alternates '^user@example$'
1203 The <code class="literal">-group</code> flag causes all of the subsequent regular expressions
1204 to be added to the named group.
1206 The <code class="literal">unalternates</code> command can be used to write exceptions to
1207 <code class="literal">alternates</code> patterns. If an address matches something in an
1208 <code class="literal">alternates</code> command, but you nonetheless do not think it is
1209 from you, you can list a more precise pattern under an <code class="literal">unalternates</code>
1212 To remove a regular expression from the <code class="literal">alternates</code> list, use the
1213 <code class="literal">unalternates</code> command with exactly the same <span class="emphasis"><em>regexp</em></span>.
1214 Likewise, if the <span class="emphasis"><em>regexp</em></span> for an <code class="literal">alternates</code> command matches
1215 an entry on the <code class="literal">unalternates</code> list, that <code class="literal">unalternates</code>
1216 entry will be removed. If the <span class="emphasis"><em>regexp</em></span> for <code class="literal">unalternates</code>
1217 is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries</em></span> on <code class="literal">alternates</code> will be removed.
1218 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="lists"></a>12. Mailing lists</h2></div></div></div><a id="subscribe"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">lists</code> [
1219 <code class="option">-group</code>
1220 <em class="replaceable"><code>name</code></em>
1222 <em class="replaceable"><code>regexp</code></em>
1224 <em class="replaceable"><code>regexp</code></em>
1225 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unlists</code> [
1226 <code class="option">-group</code>
1227 <em class="replaceable"><code>name</code></em>
1229 <em class="replaceable"><code>*</code></em>
1231 <em class="replaceable"><code>regexp</code></em>
1232 ... }</p></div><div class="cmdsynopsis"><p><code class="command">subscribe</code> [
1233 <code class="option">-group</code>
1234 <em class="replaceable"><code>name</code></em>
1236 <em class="replaceable"><code>regexp</code></em>
1238 <em class="replaceable"><code>regexp</code></em>
1239 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unsubscribe</code> [
1240 <code class="option">-group</code>
1241 <em class="replaceable"><code>name</code></em>
1243 <em class="replaceable"><code>*</code></em>
1245 <em class="replaceable"><code>regexp</code></em>
1247 Mutt has a few nice features for <a class="link" href="#using-lists" title="8. Handling Mailing Lists">handling mailing lists</a>. In order to take advantage of them, you must
1248 specify which addresses belong to mailing lists, and which mailing
1249 lists you are subscribed to. Once you have done this, the <a class="link" href="#list-reply"><code class="literal"><list-reply></code></a> function will work for all known lists.
1250 Additionally, when you send a message to a subscribed list, mutt will
1251 add a Mail-Followup-To header to tell other users' mail user agents
1252 not to send copies of replies to your personal address.
1253 </p><div class="note"><h3 class="title">Note</h3><p>
1254 The Mail-Followup-To header is a non-standard extension which is not
1255 supported by all mail user agents. Adding it is not bullet-proof against
1256 receiving personal CCs of list messages. Also note that the generation
1257 of the Mail-Followup-To header is controlled by the
1258 <a class="link" href="#followup-to" title="3.60. followup_to">$followup_to</a>
1259 configuration variable.
1261 More precisely, Mutt maintains lists of patterns for the addresses
1262 of known and subscribed mailing lists. Every subscribed mailing
1263 list is known. To mark a mailing list as known, use the “<span class="quote">lists</span>”
1264 command. To mark it as subscribed, use “<span class="quote">subscribe</span>”.
1266 You can use regular expressions with both commands. To mark all
1267 messages sent to a specific bug report's address on mutt's bug
1268 tracking system as list mail, for instance, you could say
1269 “<span class="quote">subscribe [0-9]*@bugs.guug.de</span>”. Often, it's sufficient to just
1270 give a portion of the list's e-mail address.
1272 Specify as much of the address as you need to to remove ambiguity. For
1273 example, if you've subscribed to the Mutt mailing list, you will receive mail
1274 addressed to <span class="emphasis"><em>mutt-users@mutt.org</em></span>. So, to tell Mutt
1275 that this is a mailing list, you could add “<span class="quote">lists mutt-users@</span>” to your
1276 initialization file. To tell mutt that you are subscribed to it,
1277 add “<span class="quote">subscribe mutt-users</span>” to your initialization file instead.
1278 If you also happen to get mail from someone whose address is
1279 <span class="emphasis"><em>mutt-users@example.com</em></span>, you could use
1280 “<span class="quote">lists ^mutt-users@mutt\\.org$</span>”
1281 or “<span class="quote">subscribe ^mutt-users@mutt\\.org$</span>” to
1282 match only mail from the actual list.
1284 The <code class="literal">-group</code> flag adds all of the subsequent regular expressions
1287 The “<span class="quote">unlists</span>” command is used to remove a token from the list of
1288 known and subscribed mailing-lists. Use “<span class="quote">unlists *</span>” to remove all
1291 To remove a mailing list from the list of subscribed mailing lists,
1292 but keep it on the list of known mailing lists, use “<span class="quote">unsubscribe</span>”.
1293 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mbox-hook"></a>13. Using Multiple spool mailboxes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mbox-hook</code>
1294 <em class="replaceable"><code>[!]pattern</code></em>
1296 <em class="replaceable"><code>mailbox</code></em>
1298 This command is used to move read messages from a specified mailbox to a
1299 different mailbox automatically when you quit or change folders.
1300 <span class="emphasis"><em>pattern</em></span> is a regular expression specifying the mailbox to treat as a
1301 “<span class="quote">spool</span>” mailbox and <span class="emphasis"><em>mailbox</em></span> specifies where mail should be saved when
1304 Unlike some of the other <span class="emphasis"><em>hook</em></span> commands, only the <span class="emphasis"><em>first</em></span> matching
1305 pattern is used (it is not possible to save read mail in more than a single
1307 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailboxes"></a>14. Monitoring incoming mail</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mailboxes</code>
1308 <em class="replaceable"><code>mailbox</code></em>
1310 <em class="replaceable"><code>mailbox</code></em>
1311 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unmailboxes</code> {
1312 <em class="replaceable"><code>*</code></em>
1314 <em class="replaceable"><code>mailbox</code></em>
1316 This command specifies folders which can receive mail and
1317 which will be checked for new messages periodically.
1319 <span class="emphasis"><em>folder</em></span> can either be a local file or directory
1320 (Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
1321 support, <span class="emphasis"><em>folder</em></span> can also be a POP/IMAP folder
1322 URL. The URL syntax is described in <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>,
1323 POP and IMAP are described in <a class="xref" href="#pop" title="3. POP3 Support">Section 3, “POP3 Support”</a> and <a class="xref" href="#imap" title="4. IMAP Support">Section 4, “IMAP Support”</a>
1326 Mutt provides a number of advanced features for handling (possibly many)
1327 folders and new mail within them, please refer to
1328 <a class="xref" href="#handling-folders" title="9. Handling multiple folders">Section 9, “Handling multiple folders”</a> for details (including in what
1329 situations and how often Mutt checks for new mail).
1331 The “<span class="quote">unmailboxes</span>” command is used to remove a token from the list
1332 of folders which receive mail. Use “<span class="quote">unmailboxes *</span>” to remove all
1334 </p><div class="note"><h3 class="title">Note</h3><p>
1335 The folders in the <code class="literal">mailboxes</code> command are resolved when
1336 the command is executed, so if these names contain <a class="link" href="#shortcuts" title="7. Mailbox Shortcuts">shortcut characters</a> (such as “<span class="quote">=</span>” and “<span class="quote">!</span>”), any variable
1337 definition that affects these characters (like <a class="link" href="#folder" title="3.58. folder">$folder</a> and <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a>)
1338 should be set before the <code class="literal">mailboxes</code> command. If
1339 none of these shorcuts are used, a local path should be absolute as
1340 otherwise mutt tries to find it relative to the directory
1341 from where mutt was started which may not always be desired.
1343 For Mbox and Mmdf folders, new mail is detected by comparing access and/or
1344 modification times of files: Mutt assumes a folder has new mail if it wasn't
1345 accessed after it was last modified. Utilities like <code class="literal">biff</code> or
1346 <code class="literal">frm</code> or any other program which accesses the mailbox might cause
1347 Mutt to never detect new mail for that mailbox if they do not properly reset the
1348 access time. Other possible causes of Mutt not detecting new mail in these folders
1349 are backup tools (updating access times) or filesystems mounted without
1350 access time update support.
1352 In cases where new mail detection for Mbox or Mmdf folders appears to be
1354 <a class="link" href="#check-mbox-size" title="3.24. check_mbox_size">$check_mbox_size</a>
1355 option can be used to make Mutt track and consult file sizes for new
1356 mail detection instead.
1357 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="my-hdr"></a>15. User defined headers</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">my_hdr</code>
1358 <em class="replaceable"><code>string</code></em>
1359 </p></div><div class="cmdsynopsis"><p><code class="command">unmy_hdr</code> {
1360 <em class="replaceable"><code>*</code></em>
1362 <em class="replaceable"><code>field</code></em>
1364 The <code class="literal">my_hdr</code> command allows you to create your own header
1365 fields which will be added to every message you send.
1367 For example, if you would like to add an “<span class="quote">Organization:</span>” header field to
1368 all of your outgoing messages, you can put the command
1369 </p><div class="example"><a id="ex-my-hdr"></a><p class="title"><b>Example 3.10. Defining custom headers</b></p><div class="example-contents"><pre class="screen">
1370 my_hdr Organization: A Really Big Company, Anytown, USA
1371 </pre></div></div><br class="example-break" /><p>
1372 in your <code class="literal">.muttrc</code>.
1373 </p><div class="note"><h3 class="title">Note</h3><p>
1374 Space characters are <span class="emphasis"><em>not</em></span> allowed between the keyword and
1375 the colon (“<span class="quote">:</span>”). The standard for electronic mail (RFC2822) says that
1376 space is illegal there, so Mutt enforces the rule.
1378 If you would like to add a header field to a single message, you should
1379 either set the <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable,
1380 or use the <code class="literal"><edit-headers></code> function (default: “<span class="quote">E</span>”) in the compose menu so
1381 that you can edit the header of your message along with the body.
1383 To remove user defined header fields, use the <code class="literal">unmy_hdr</code>
1384 command. You may specify an asterisk (“<span class="quote">*</span>”) to remove all header
1385 fields, or the fields to remove. For example, to remove all “<span class="quote">To</span>” and
1386 “<span class="quote">Cc</span>” header fields, you could use:
1387 </p><pre class="screen">
1389 </pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="save-hook"></a>16. Specify default save mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">save-hook</code>
1390 <em class="replaceable"><code>[!]pattern</code></em>
1392 <em class="replaceable"><code>mailbox</code></em>
1394 This command is used to override the default mailbox used when saving
1395 messages. <span class="emphasis"><em>mailbox</em></span> will be used as the default if the message
1396 matches <span class="emphasis"><em>pattern</em></span>, see <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information
1397 on the exact format.
1399 To provide more flexibility and good defaults, Mutt applies the
1400 expandos of <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to
1401 <span class="emphasis"><em>mailbox</em></span> after it was expanded.
1404 </p><div class="example"><a id="ex-save-hook-exando"></a><p class="title"><b>Example 3.11. Using %-expandos in <code class="literal">save-hook</code></b></p><div class="example-contents"><pre class="screen">
1405 # default: save all to ~/Mail/<author name>
1406 save-hook . ~/Mail/%F
1408 # save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
1409 save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
1411 # save from aol.com to $folder/spam
1412 save-hook aol\\.com$ +spam
1413 </pre></div></div><br class="example-break" /><p>
1414 Also see the <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
1415 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-hook"></a>17. Specify default Fcc: mailbox when composing</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-hook</code>
1416 <em class="replaceable"><code>[!]pattern</code></em>
1418 <em class="replaceable"><code>mailbox</code></em>
1420 This command is used to save outgoing mail in a mailbox other than
1421 <a class="link" href="#record" title="3.242. record">$record</a>. Mutt searches the initial list of
1422 message recipients for the first matching <span class="emphasis"><em>regexp</em></span> and uses <span class="emphasis"><em>mailbox</em></span>
1423 as the default Fcc: mailbox. If no match is found the message will be saved
1424 to <a class="link" href="#record" title="3.242. record">$record</a> mailbox.
1426 To provide more flexibility and good defaults, Mutt applies the
1427 expandos of <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to
1428 <span class="emphasis"><em>mailbox</em></span> after it was expanded.
1430 See <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information on the exact format of <span class="emphasis"><em>pattern</em></span>.
1432 Example: <code class="literal">fcc-hook [@.]aol\\.com$ +spammers</code>
1434 The above will save a copy of all messages going to the aol.com domain to
1435 the `+spammers' mailbox by default. Also see the <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
1436 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-save-hook"></a>18. Specify default save filename and default Fcc: mailbox at once</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-save-hook</code>
1437 <em class="replaceable"><code>[!]pattern</code></em>
1439 <em class="replaceable"><code>mailbox</code></em>
1441 This command is a shortcut, equivalent to doing both a <a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
1442 and a <a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a> with its arguments,
1443 including %-expansion on <span class="emphasis"><em>mailbox</em></span> according
1444 to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
1445 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="send-hook"></a>19. Change settings based upon message recipients</h2></div></div></div><a id="reply-hook"></a><a id="send2-hook"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">reply-hook</code>
1446 <em class="replaceable"><code>[!]pattern</code></em>
1448 <em class="replaceable"><code>command</code></em>
1449 </p></div><div class="cmdsynopsis"><p><code class="command">send-hook</code>
1450 <em class="replaceable"><code>[!]pattern</code></em>
1452 <em class="replaceable"><code>command</code></em>
1453 </p></div><div class="cmdsynopsis"><p><code class="command">send2-hook</code>
1454 <em class="replaceable"><code>[!]pattern</code></em>
1456 <em class="replaceable"><code>command</code></em>
1458 These commands can be used to execute arbitrary configuration commands based
1459 upon recipients of the message. <span class="emphasis"><em>pattern</em></span> is used to match
1460 the message, see <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for details. <span class="emphasis"><em>command</em></span>
1461 is executed when <span class="emphasis"><em>pattern</em></span> matches.
1463 <code class="literal">reply-hook</code> is matched against the message you are <span class="emphasis"><em>replying to</em></span>,
1464 instead of the message you are <span class="emphasis"><em>sending</em></span>. <code class="literal">send-hook</code> is
1465 matched against all messages, both <span class="emphasis"><em>new</em></span>
1466 and <span class="emphasis"><em>replies</em></span>.
1467 </p><div class="note"><h3 class="title">Note</h3><p>
1468 <code class="literal">reply-hook</code>s are matched <span class="bold"><strong>before</strong></span> the <code class="literal">send-hook</code>, <span class="bold"><strong>regardless</strong></span>
1469 of the order specified in the user's configuration file.
1471 <code class="literal">send2-hook</code> is matched every time a message is changed, either
1472 by editing it, or by using the compose menu to change its recipients
1473 or subject. <code class="literal">send2-hook</code> is executed after <code class="literal">send-hook</code>, and
1474 can, e.g., be used to set parameters such as the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> variable depending on the message's sender
1477 For each type of <code class="literal">send-hook</code> or <code class="literal">reply-hook</code>, when multiple matches
1478 occur, commands are executed in the order they are specified in the muttrc
1479 (for that type of hook).
1481 Example: <code class="literal">send-hook mutt "set mime_forward signature=''"</code>
1483 Another typical use for this command is to change the values of the
1484 <a class="link" href="#attribution" title="3.16. attribution">$attribution</a>, <a class="link" href="#signature" title="3.265. signature">$signature</a> and <a class="link" href="#locale" title="3.104. locale">$locale</a>
1485 variables in order to change the language of the attributions and
1486 signatures based upon the recipients.
1487 </p><div class="note"><h3 class="title">Note</h3><p>
1488 send-hook's are only executed once after getting the initial
1489 list of recipients. Adding a recipient after replying or editing the
1490 message will not cause any send-hook to be executed. Also note that
1491 <code class="literal">my_hdr</code> commands which modify recipient headers, or the message's
1492 subject, don't have any effect on the current message when executed
1494 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="message-hook"></a>20. Change settings before formatting a message</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">message-hook</code>
1495 <em class="replaceable"><code>[!]pattern</code></em>
1497 <em class="replaceable"><code>command</code></em>
1499 This command can be used to execute arbitrary configuration commands
1500 before viewing or formatting a message based upon information about the message.
1501 <span class="emphasis"><em>command</em></span> is executed if the <span class="emphasis"><em>pattern</em></span> matches the message to be
1502 displayed. When multiple matches occur, commands are executed in the order
1503 they are specified in the muttrc.
1505 See <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for
1506 information on the exact format of <span class="emphasis"><em>pattern</em></span>.
1509 </p><pre class="screen">
1510 message-hook ~A 'set pager=builtin'
1511 message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
1512 </pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="crypt-hook"></a>21. Choosing the cryptographic key of the recipient</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">crypt-hook</code>
1513 <em class="replaceable"><code>pattern</code></em>
1515 <em class="replaceable"><code>keyid</code></em>
1517 When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a certain
1518 key with a given e-mail address automatically, either because the
1519 recipient's public key can't be deduced from the destination address,
1520 or because, for some reasons, you need to override the key Mutt would
1521 normally use. The <code class="literal">crypt-hook</code> command provides a
1522 method by which you can specify the ID of the public key to be used
1523 when encrypting messages to a certain recipient.
1525 The meaning of <span class="emphasis"><em>keyid</em></span> is to be taken broadly in this context: You
1526 can either put a numerical key ID here, an e-mail address, or even
1528 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="push"></a>22. Adding key sequences to the keyboard buffer</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">push</code>
1529 <em class="replaceable"><code>string</code></em>
1531 This command adds the named string to the keyboard buffer. The string may
1532 contain control characters, key names and function names like the sequence
1533 string in the <a class="link" href="#macro" title="8. Keyboard macros">macro</a> command. You may use it to
1534 automatically run a sequence of commands at startup, or when entering
1535 certain folders. For example, the following command will automatically
1536 collapse all threads when entering a folder:
1537 </p><div class="example"><a id="ex-folder-hook-push"></a><p class="title"><b>Example 3.12. Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></b></p><div class="example-contents"><pre class="screen">
1538 folder-hook . 'push <collapse-all>'
1539 </pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exec"></a>23. Executing functions</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">exec</code>
1540 <em class="replaceable"><code>function</code></em>
1542 <em class="replaceable"><code>function</code></em>
1544 This command can be used to execute any function. Functions are
1545 listed in the <a class="link" href="#functions" title="4. Functions">function reference</a>.
1546 “<span class="quote">exec function</span>” is equivalent to “<span class="quote">push <function></span>”.
1547 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="score-command"></a>24. Message Scoring</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">score</code>
1548 <em class="replaceable"><code>pattern</code></em>
1550 <em class="replaceable"><code>value</code></em>
1551 </p></div><div class="cmdsynopsis"><p><code class="command">unscore</code> {
1552 <em class="replaceable"><code>*</code></em>
1554 <em class="replaceable"><code>pattern</code></em>
1556 The <code class="literal">score</code> commands adds <span class="emphasis"><em>value</em></span> to a message's score if <span class="emphasis"><em>pattern</em></span>
1557 matches it. <span class="emphasis"><em>pattern</em></span> is a string in the format described in the <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> section (note: For efficiency reasons, patterns
1558 which scan information not available in the index, such as <code class="literal">˜b</code>,
1559 <code class="literal">˜B</code> or <code class="literal">˜h</code>, may not be used). <span class="emphasis"><em>value</em></span> is a
1560 positive or negative integer. A message's final score is the sum total of all
1561 matching <code class="literal">score</code> entries. However, you may optionally prefix <span class="emphasis"><em>value</em></span> with
1562 an equal sign (=) to cause evaluation to stop at a particular entry if there is
1563 a match. Negative final scores are rounded up to 0.
1565 The <code class="literal">unscore</code> command removes score entries from the list. You <span class="bold"><strong>must</strong></span>
1566 specify the same pattern specified in the <code class="literal">score</code> command for it to be
1567 removed. The pattern “<span class="quote">*</span>” is a special token which means to clear the list
1568 of all score entries.
1569 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="spam"></a>25. Spam detection</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">spam</code>
1570 <em class="replaceable"><code>pattern</code></em>
1572 <em class="replaceable"><code>format</code></em>
1573 </p></div><div class="cmdsynopsis"><p><code class="command">nospam</code> {
1574 <em class="replaceable"><code>*</code></em>
1576 <em class="replaceable"><code>pattern</code></em>
1578 Mutt has generalized support for external spam-scoring filters.
1579 By defining your spam patterns with the <code class="literal">spam</code> and <code class="literal">nospam</code>
1580 commands, you can <span class="emphasis"><em>limit</em></span>, <span class="emphasis"><em>search</em></span>, and <span class="emphasis"><em>sort</em></span> your
1581 mail based on its spam attributes, as determined by the external
1582 filter. You also can display the spam attributes in your index
1583 display using the <code class="literal">%H</code> selector in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable. (Tip: try <code class="literal">%?H?[%H] ?</code>
1584 to display spam tags only when they are defined for a given message.)
1586 Your first step is to define your external filter's spam patterns using
1587 the <code class="literal">spam</code> command. <span class="emphasis"><em>pattern</em></span> should be a regular expression
1588 that matches a header in a mail message. If any message in the mailbox
1589 matches this regular expression, it will receive a “<span class="quote">spam tag</span>” or
1590 “<span class="quote">spam attribute</span>” (unless it also matches a <code class="literal">nospam</code> pattern -- see
1591 below.) The appearance of this attribute is entirely up to you, and is
1592 governed by the <span class="emphasis"><em>format</em></span> parameter. <span class="emphasis"><em>format</em></span> can be any static
1593 text, but it also can include back-references from the <span class="emphasis"><em>pattern</em></span>
1594 expression. (A regular expression “<span class="quote">back-reference</span>” refers to a
1595 sub-expression contained within parentheses.) <code class="literal">%1</code> is replaced with
1596 the first back-reference in the regex, <code class="literal">%2</code> with the second, etc.
1598 If you're using multiple spam filters, a message can have more than
1599 one spam-related header. You can define <code class="literal">spam</code> patterns for each
1600 filter you use. If a message matches two or more of these patterns, and
1601 the $spam_separator variable is set to a string, then the
1602 message's spam tag will consist of all the <span class="emphasis"><em>format</em></span> strings joined
1603 together, with the value of $spam_separator separating
1606 For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
1607 define these spam settings:
1608 </p><div class="example"><a id="ex-spam"></a><p class="title"><b>Example 3.13. Configuring spam detection</b></p><div class="example-contents"><pre class="screen">
1609 spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
1610 spam "X-Spam-Status: Yes" "90+/SA"
1611 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
1612 set spam_separator=", "
1613 </pre></div></div><br class="example-break" /><p>
1614 If I then received a message that DCC registered with “<span class="quote">many</span>” hits
1615 under the “<span class="quote">Fuz2</span>” checksum, and that PureMessage registered with a
1616 97% probability of being spam, that message's spam tag would read
1617 <code class="literal">90+/DCC-Fuz2, 97/PM</code>. (The four characters before “<span class="quote">=many</span>” in a
1618 DCC report indicate the checksum used -- in this case, “<span class="quote">Fuz2</span>”.)
1620 If the $spam_separator variable is unset, then each
1621 spam pattern match supersedes the previous one. Instead of getting
1622 joined <span class="emphasis"><em>format</em></span> strings, you'll get only the last one to match.
1624 The spam tag is what will be displayed in the index when you use
1625 <code class="literal">%H</code> in the <code class="literal">$index_format</code> variable. It's also the
1626 string that the <code class="literal">˜H</code> pattern-matching expression matches against for
1627 <code class="literal"><search></code> and <code class="literal"><limit></code> functions. And it's what sorting by spam
1628 attribute will use as a sort key.
1630 That's a pretty complicated example, and most people's actual
1631 environments will have only one spam filter. The simpler your
1632 configuration, the more effective mutt can be, especially when it comes
1635 Generally, when you sort by spam tag, mutt will sort <span class="emphasis"><em>lexically</em></span> --
1636 that is, by ordering strings alphanumerically. However, if a spam tag
1637 begins with a number, mutt will sort numerically first, and lexically
1638 only when two numbers are equal in value. (This is like UNIX's
1639 <code class="literal">sort -n</code>.) A message with no spam attributes at all -- that is, one
1640 that didn't match <span class="emphasis"><em>any</em></span> of your <code class="literal">spam</code> patterns -- is sorted at
1641 lowest priority. Numbers are sorted next, beginning with 0 and ranging
1642 upward. Finally, non-numeric strings are sorted, with “<span class="quote">a</span>” taking lower
1643 priority than “<span class="quote">z</span>”. Clearly, in general, sorting by spam tags is most
1644 effective when you can coerce your filter to give you a raw number. But
1645 in case you can't, mutt can still do something useful.
1647 The <code class="literal">nospam</code> command can be used to write exceptions to <code class="literal">spam</code>
1648 patterns. If a header pattern matches something in a <code class="literal">spam</code> command,
1649 but you nonetheless do not want it to receive a spam tag, you can list a
1650 more precise pattern under a <code class="literal">nospam</code> command.
1652 If the <span class="emphasis"><em>pattern</em></span> given to <code class="literal">nospam</code> is exactly the same as the
1653 <span class="emphasis"><em>pattern</em></span> on an existing <code class="literal">spam</code> list entry, the effect will be to
1654 remove the entry from the spam list, instead of adding an exception.
1655 Likewise, if the <span class="emphasis"><em>pattern</em></span> for a <code class="literal">spam</code> command matches an entry
1656 on the <code class="literal">nospam</code> list, that <code class="literal">nospam</code> entry will be removed. If the
1657 <span class="emphasis"><em>pattern</em></span> for <code class="literal">nospam</code> is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries on both lists</em></span>
1658 will be removed. This might be the default action if you use <code class="literal">spam</code>
1659 and <code class="literal">nospam</code> in conjunction with a <code class="literal">folder-hook</code>.
1661 You can have as many <code class="literal">spam</code> or <code class="literal">nospam</code> commands as you like.
1662 You can even do your own primitive spam detection within mutt -- for
1663 example, if you consider all mail from <code class="literal">MAILER-DAEMON</code> to be spam,
1664 you can use a <code class="literal">spam</code> command like this:
1665 </p><pre class="screen">
1666 spam "^From: .*MAILER-DAEMON" "999"
1667 </pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="set"></a>26. Setting and Querying Variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-commands"></a>26.1. Commands</h3></div></div></div><p>
1668 The following commands are available to manipulate and query variables:
1669 </p><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">set</code> {
1670 [ <code class="option">no</code> | <code class="option">inv</code> ]
1671 <em class="replaceable"><code>variable</code></em>
1673 <em class="replaceable"><code>variable=value</code></em>
1674 } [...]</p></div><div class="cmdsynopsis"><p><code class="command">toggle</code>
1675 <em class="replaceable"><code>variable</code></em>
1677 <em class="replaceable"><code>variable</code></em>
1678 ...]</p></div><div class="cmdsynopsis"><p><code class="command">unset</code>
1679 <em class="replaceable"><code>variable</code></em>
1681 <em class="replaceable"><code>variable</code></em>
1682 ...]</p></div><div class="cmdsynopsis"><p><code class="command">reset</code>
1683 <em class="replaceable"><code>variable</code></em>
1685 <em class="replaceable"><code>variable</code></em>
1687 This command is used to set (and unset) <a class="link" href="#variables" title="3. Configuration variables">configuration variables</a>. There are four basic types of variables:
1688 boolean, number, string and quadoption. <span class="emphasis"><em>boolean</em></span> variables can be
1689 <span class="emphasis"><em>set</em></span> (true) or <span class="emphasis"><em>unset</em></span> (false). <span class="emphasis"><em>number</em></span> variables can be
1690 assigned a positive integer value.
1691 <span class="emphasis"><em>string</em></span> variables consist of any number of printable characters and
1692 must be enclosed in quotes if they contain spaces or tabs. You
1693 may also use the escape sequences “<span class="quote">\n</span>” and “<span class="quote">\t</span>” for newline and tab, respectively.
1694 <span class="emphasis"><em>quadoption</em></span> variables are used to control whether or not to be prompted
1695 for certain actions, or to specify a default action. A value of <span class="emphasis"><em>yes</em></span>
1696 will cause the action to be carried out automatically as if you had answered
1697 yes to the question. Similarly, a value of <span class="emphasis"><em>no</em></span> will cause the
1698 action to be carried out as if you had answered “<span class="quote">no.</span>” A value of
1699 <span class="emphasis"><em>ask-yes</em></span> will cause a prompt with a default answer of “<span class="quote">yes</span>” and
1700 <span class="emphasis"><em>ask-no</em></span> will provide a default answer of “<span class="quote">no.</span>”
1702 Prefixing a variable with “<span class="quote">no</span>” will unset it. Example: <code class="literal">set noaskbcc</code>.
1704 For <span class="emphasis"><em>boolean</em></span> variables, you may optionally prefix the variable name with
1705 <code class="literal">inv</code> to toggle the value (on or off). This is useful when writing
1706 macros. Example: <code class="literal">set invsmart_wrap</code>.
1708 The <code class="literal">toggle</code> command automatically prepends the <code class="literal">inv</code> prefix to all
1709 specified variables.
1711 The <code class="literal">unset</code> command automatically prepends the <code class="literal">no</code> prefix to all
1712 specified variables.
1714 Using the <code class="literal"><enter-command></code> function in the <span class="emphasis"><em>index</em></span> menu, you can query the
1715 value of a variable by prefixing the name of the variable with a question
1717 </p><pre class="screen">
1720 The question mark is actually only required for boolean and quadoption
1723 The <code class="literal">reset</code> command resets all given variables to the compile time
1724 defaults (hopefully mentioned in this manual). If you use the command
1725 <code class="literal">set</code> and prefix the variable with “<span class="quote">&</span>” this has the same
1726 behavior as the reset command.
1728 With the <code class="literal">reset</code> command there exists the special variable “<span class="quote">all</span>”,
1729 which allows you to reset all variables to their system defaults.
1730 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-myvar"></a>26.2. User-defined variables</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-intro"></a>26.2.1. Introduction</h4></div></div></div><p>
1731 Along with the variables listed in the
1732 <a class="link" href="#variables" title="3. Configuration variables">Configuration variables</a> section, mutt
1733 supports user-defined variables with names starting
1734 with <code class="literal">my_</code> as in, for
1735 example, <code class="literal">my_cfgdir</code>.
1737 The <code class="literal">set</code> command either creates a
1738 custom <code class="literal">my_</code> variable or changes its
1739 value if it does exist already. The <code class="literal">unset</code> and <code class="literal">reset</code>
1740 commands remove the variable entirely.
1742 Since user-defined variables are expanded in the same way that
1743 environment variables are (except for
1744 the <a class="link" href="#shell-escape">shell-escape</a> command and
1745 backtick expansion), this feature can be used to make configuration
1746 files more readable.
1747 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-examples"></a>26.2.2. Examples</h4></div></div></div><p>
1748 The following example defines and uses the variable <code class="literal">my_cfgdir</code>
1749 to abbreviate the calls of the <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> command:
1750 </p><div class="example"><a id="ex-myvar1"></a><p class="title"><b>Example 3.14. Using user-defined variables for config file readability</b></p><div class="example-contents"><pre class="screen">
1751 set my_cfgdir = $HOME/mutt/config
1753 source $my_cfgdir/hooks
1754 source $my_cfgdir/macros
1755 # more source commands...
1756 </pre></div></div><br class="example-break" /><p>
1757 A custom variable can also be used in macros to backup the current value
1758 of another variable. In the following example, the value of the
1759 <a class="link" href="#delete" title="3.42. delete">$delete</a> is changed temporarily
1760 while its original value is saved as <code class="literal">my_delete</code>.
1761 After the macro has executed all commands, the original value of <a class="link" href="#delete" title="3.42. delete">$delete</a> is restored.
1762 </p><div class="example"><a id="ex-myvar2"></a><p class="title"><b>Example 3.15. Using user-defined variables for backing up other config option values</b></p><div class="example-contents"><pre class="screen">
1764 <enter-command>set my_delete=$delete<enter>\
1765 <enter-command>set delete=yes<enter>\
1767 <enter-command>set delete=$my_delete<enter>'
1768 </pre></div></div><br class="example-break" /><p>
1769 Since mutt expands such values already when parsing the configuration
1770 file(s), the value of <code class="literal">$my_delete</code> in the
1771 last example would be the value of <code class="literal">$delete</code> exactly
1772 as it was at that point during parsing the configuration file. If
1773 another statement would change the value for <code class="literal">$delete</code>
1774 later in the same or another file, it would have no effect on
1775 <code class="literal">$my_delete</code>. However, the expansion can
1776 be deferred to runtime, as shown in the next example, when escaping the
1778 </p><div class="example"><a id="ex-myvar3"></a><p class="title"><b>Example 3.16. Deferring user-defined variable expansion to runtime</b></p><div class="example-contents"><pre class="screen">
1779 macro pager <PageDown> "\
1780 <enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
1782 <enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
1783 <enter-command> unset my_old_pager_stop<Enter>"
1784 </pre></div></div><br class="example-break" /><p>
1785 Note that there is a space
1786 between <code class="literal"><enter-command></code> and
1787 the <code class="literal">set</code> configuration command, preventing mutt from
1788 recording the macro's commands into its history.
1789 </p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="source"></a>27. Reading initialization commands from another file</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">source</code>
1790 <em class="replaceable"><code>filename</code></em>
1792 This command allows the inclusion of initialization commands
1793 from other files. For example, I place all of my aliases in
1794 <code class="literal">˜/.mail_aliases</code> so that I can make my
1795 <code class="literal">˜/.muttrc</code> readable and keep my aliases private.
1797 If the filename begins with a tilde (“<span class="quote">˜</span>”), it will be expanded to the
1798 path of your home directory.
1800 If the filename ends with a vertical bar (|), then <span class="emphasis"><em>filename</em></span> is
1801 considered to be an executable program from which to read input (eg.
1802 <code class="literal">source ˜/bin/myscript|</code>).
1803 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ifdef"></a>28. Configuring features conditionnaly</h2></div></div></div><p>
1804 Usage: <code class="literal">ifdef</code> <span class="emphasis"><em>item</em></span> <span class="emphasis"><em>command</em></span>
1806 This command allows to test if a feature has been compiled in, before
1807 actually executing the command. Item can be either the name of a
1808 function, variable, or command. Example:
1810 </p><pre class="screen">
1811 ifdef imap_keepalive 'source ~/.mutt/imap_setup'
1813 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="unhook"></a>29. Removing hooks</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">unhook</code> {
1814 <em class="replaceable"><code>*</code></em>
1816 <em class="replaceable"><code>hook-type</code></em>
1818 This command permits you to flush hooks you have previously defined.
1819 You can either remove all hooks by giving the “<span class="quote">*</span>” character as an
1820 argument, or you can remove all hooks of a specific type by saying
1821 something like <code class="literal">unhook send-hook</code>.
1822 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="formatstrings"></a>30. Format Strings</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-basics"></a>30.1. Basic usage</h3></div></div></div><p>
1823 Format strings are a general concept you'll find in several locations
1824 through the mutt configuration, especially in the
1825 <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>,
1826 <a class="link" href="#pager-format" title="3.140. pager_format">$pager_format</a>,
1827 <a class="link" href="#status-format" title="3.281. status_format">$status_format</a>,
1828 and other “<span class="quote">*_format</span>” variables. These can be very straightforward,
1829 and it's quite possible you already know how to use them.
1831 The most basic format string element is a percent symbol followed
1832 by another character. For example, <code class="literal">%s</code>
1833 represents a message's Subject: header in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable. The
1834 “<span class="quote">expandos</span>” available are documented with each format variable, but
1835 there are general modifiers available with all formatting expandos,
1836 too. Those are our concern here.
1838 Some of the modifiers are borrowed right out of C (though you might
1839 know them from Perl, Python, shell, or another language). These are
1840 the [-]m.n modifiers, as in <code class="literal">%-12.12s</code>. As with
1841 such programming languages, these modifiers allow you to specify the
1842 minimum and maximum size of the resulting string, as well as its
1843 justification. If the “<span class="quote">-</span>” sign follows the percent, the string will
1844 be left-justified instead of right-justified. If there's a number
1845 immediately following that, it's the minimum amount of space the
1846 formatted string will occupy -- if it's naturally smaller than that, it
1847 will be padded out with spaces. If a decimal point and another number
1848 follow, that's the maximum space allowable -- the string will not be
1849 permitted to exceed that width, no matter its natural size. Each of
1850 these three elements is optional, so that all these are legal format
1852 <code class="literal">%-12s</code>
1853 <code class="literal">%4c</code>
1854 <code class="literal">%.15F</code>
1855 <code class="literal">%-12.15L</code>
1857 Mutt adds some other modifiers to format strings. If you use an equals
1858 symbol (<code class="literal">=</code>) as a numeric prefix (like the minus
1859 above), it will force the string to be centered within its minimum
1860 space range. For example, <code class="literal">%=14y</code> will reserve 14
1861 characters for the %y expansion -- that's the X-Label: header, in
1862 <code class="literal">$index_format</code>. If the expansion
1863 results in a string less than 14 characters, it will be centered in a
1864 14-character space. If the X-Label for a message were "test", that
1865 expansion would look like “<span class="quote"> test </span>”.
1867 There are two very little-known modifiers that affect the way that an
1868 expando is replaced. If there is an underline (“<span class="quote">_</span>”) character
1869 between any format modifiers (as above) and the expando letter, it will
1870 expands in all lower case. And if you use a colon (“<span class="quote">:</span>”), it will
1871 replace all decimal points with underlines.
1872 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-filters"></a>30.2. Filters</h3></div></div></div><p>
1873 Any format string ending in a vertical bar (“<span class="quote">|</span>”) will be
1874 expanded and piped through the first word in the string, using spaces
1875 as separator. The string returned will be used for display.
1876 If the returned string ends in %, it will be passed through
1877 the formatter a second time. This allows the filter to generate a
1878 replacement format string including % expandos.
1880 All % expandos in a format string are expanded before the script
1882 </p><div class="example"><a id="ex-fmtpipe"></a><p class="title"><b>Example 3.17. Using external filters in format strings</b></p><div class="example-contents"><pre class="screen">
1883 set status_format="script.sh '%r %f (%L)'|"
1884 </pre></div></div><br class="example-break" /><p>
1885 will make mutt expand <code class="literal">%r</code>,
1886 <code class="literal">%f</code> and <code class="literal">%L</code>
1887 before calling the script. The example also shows that arguments can be
1888 quoted: the script will receive the expanded string between the single quotes
1889 as the only argument.
1891 A practical example is the <code class="literal">mutt_xtitle</code>
1892 script installed in the <code class="literal">samples</code>
1893 subdirectory of the mutt documentation: it can be used as filter for
1894 <code class="literal">$status_format</code> to set the current
1895 terminal's title, if supported.
1896 </p></div></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="advancedusage"></a>Chapter 4. Advanced Usage</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="regexp"></a>1. Regular Expressions</h2></div></div></div><p>
1897 All string patterns in Mutt including those in more complex
1898 <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> must be specified
1899 using regular expressions (regexp) in the “<span class="quote">POSIX extended</span>” syntax (which
1900 is more or less the syntax used by egrep and GNU awk). For your
1901 convenience, we have included below a brief description of this syntax.
1903 The search is case sensitive if the pattern contains at least one upper
1904 case letter, and case insensitive otherwise.
1905 </p><div class="note"><h3 class="title">Note</h3><p>
1906 Note that “<span class="quote">\</span>”
1907 must be quoted if used for a regular expression in an initialization
1908 command: “<span class="quote">\\</span>”.
1910 A regular expression is a pattern that describes a set of strings.
1911 Regular expressions are constructed analogously to arithmetic
1912 expressions, by using various operators to combine smaller expressions.
1913 </p><div class="note"><h3 class="title">Note</h3><p>
1914 Note that the regular expression can be enclosed/delimited by either "
1915 or ' which is useful if the regular expression includes a white-space
1916 character. See <a class="xref" href="#muttrc-syntax" title="2. Syntax of Initialization Files">Syntax of Initialization Files</a>
1917 for more information on " and ' delimiter processing. To match a
1918 literal " or ' you must preface it with \ (backslash).
1920 The fundamental building blocks are the regular expressions that match
1921 a single character. Most characters, including all letters and digits,
1922 are regular expressions that match themselves. Any metacharacter with
1923 special meaning may be quoted by preceding it with a backslash.
1925 The period “<span class="quote">.</span>” matches any single character. The caret “<span class="quote">^</span>” and
1926 the dollar sign “<span class="quote">$</span>” are metacharacters that respectively match
1927 the empty string at the beginning and end of a line.
1929 A list of characters enclosed by “<span class="quote">[</span>” and “<span class="quote">]</span>” matches any
1930 single character in that list; if the first character of the list
1931 is a caret “<span class="quote">^</span>” then it matches any character <span class="bold"><strong>not</strong></span> in the
1932 list. For example, the regular expression <span class="bold"><strong>[0123456789]</strong></span>
1933 matches any single digit. A range of ASCII characters may be specified
1934 by giving the first and last characters, separated by a hyphen
1935 “<span class="quote">-</span>”. Most metacharacters lose their special meaning inside
1936 lists. To include a literal “<span class="quote">]</span>” place it first in the list.
1937 Similarly, to include a literal “<span class="quote">^</span>” place it anywhere but first.
1938 Finally, to include a literal hyphen “<span class="quote">-</span>” place it last.
1940 Certain named classes of characters are predefined. Character classes
1941 consist of “<span class="quote">[:</span>”, a keyword denoting the class, and “<span class="quote">:]</span>”.
1942 The following classes are defined by the POSIX standard in
1943 <a class="xref" href="#posix-regex-char-classes" title="Table 4.1. POSIX regular expression character classes">Table 4.1, “POSIX regular expression character classes”</a>
1944 </p><div class="table"><a id="posix-regex-char-classes"></a><p class="title"><b>Table 4.1. POSIX regular expression character classes</b></p><div class="table-contents"><table summary="POSIX regular expression character classes" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Character class</th><th>Description</th></tr></thead><tbody><tr><td>[:alnum:]</td><td>Alphanumeric characters</td></tr><tr><td>[:alpha:]</td><td>Alphabetic characters</td></tr><tr><td>[:blank:]</td><td>Space or tab characters</td></tr><tr><td>[:cntrl:]</td><td>Control characters</td></tr><tr><td>[:digit:]</td><td>Numeric characters</td></tr><tr><td>[:graph:]</td><td>Characters that are both printable and visible. (A space is printable, but not visible, while an “<span class="quote">a</span>” is both)</td></tr><tr><td>[:lower:]</td><td>Lower-case alphabetic characters</td></tr><tr><td>[:print:]</td><td>Printable characters (characters that are not control characters)</td></tr><tr><td>[:punct:]</td><td>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</td></tr><tr><td>[:space:]</td><td>Space characters (such as space, tab and formfeed, to name a few)</td></tr><tr><td>[:upper:]</td><td>Upper-case alphabetic characters</td></tr><tr><td>[:xdigit:]</td><td>Characters that are hexadecimal digits</td></tr></tbody></table></div></div><br class="table-break" /><p>
1945 A character class is only valid in a regular expression inside the
1946 brackets of a character list.
1947 </p><div class="note"><h3 class="title">Note</h3><p>
1948 Note that the brackets in these
1949 class names are part of the symbolic names, and must be included
1950 in addition to the brackets delimiting the bracket list. For
1951 example, <span class="bold"><strong>[[:digit:]]</strong></span> is equivalent to
1952 <span class="bold"><strong>[0-9]</strong></span>.
1954 Two additional special sequences can appear in character lists. These
1955 apply to non-ASCII character sets, which can have single symbols (called
1956 collating elements) that are represented with more than one character,
1957 as well as several characters that are equivalent for collating or
1959 </p><div class="variablelist"><dl><dt><span class="term">Collating Symbols</span></dt><dd><p>
1960 A collating symbol is a multi-character collating element enclosed in
1961 “<span class="quote">[.</span>” and “<span class="quote">.]</span>”. For example, if “<span class="quote">ch</span>” is a collating
1962 element, then <span class="bold"><strong>[[.ch.]]</strong></span> is a regexp that matches
1963 this collating element, while <span class="bold"><strong>[ch]</strong></span> is a regexp that
1964 matches either “<span class="quote">c</span>” or “<span class="quote">h</span>”.
1965 </p></dd><dt><span class="term">Equivalence Classes</span></dt><dd><p>
1966 An equivalence class is a locale-specific name for a list of
1967 characters that are equivalent. The name is enclosed in “<span class="quote">[=</span>”
1968 and “<span class="quote">=]</span>”. For example, the name “<span class="quote">e</span>” might be used to
1969 represent all of “<span class="quote">è</span>” “<span class="quote">é</span>” and “<span class="quote">e</span>”. In this case,
1970 <span class="bold"><strong>[[=e=]]</strong></span> is a regexp that matches any of
1971 “<span class="quote">è</span>”, “<span class="quote">é</span>” and “<span class="quote">e</span>”.
1972 </p></dd></dl></div><p>
1973 A regular expression matching a single character may be followed by one
1974 of several repetition operators described in <a class="xref" href="#regex-repeat" title="Table 4.2. Regular expression repetition operators">Table 4.2, “Regular expression repetition operators”</a>.
1975 </p><div class="table"><a id="regex-repeat"></a><p class="title"><b>Table 4.2. Regular expression repetition operators</b></p><div class="table-contents"><table summary="Regular expression repetition operators" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Operator</th><th>Description</th></tr></thead><tbody><tr><td>?</td><td>The preceding item is optional and matched at most once</td></tr><tr><td>*</td><td>The preceding item will be matched zero or more times</td></tr><tr><td>+</td><td>The preceding item will be matched one or more times</td></tr><tr><td>{n}</td><td>The preceding item is matched exactly <span class="emphasis"><em>n</em></span> times</td></tr><tr><td>{n,}</td><td>The preceding item is matched <span class="emphasis"><em>n</em></span> or more times</td></tr><tr><td>{,m}</td><td>The preceding item is matched at most <span class="emphasis"><em>m</em></span> times</td></tr><tr><td>{n,m}</td><td>The preceding item is matched at least <span class="emphasis"><em>n</em></span> times, but no more than <span class="emphasis"><em>m</em></span> times</td></tr></tbody></table></div></div><br class="table-break" /><p>
1976 Two regular expressions may be concatenated; the resulting regular
1977 expression matches any string formed by concatenating two substrings
1978 that respectively match the concatenated subexpressions.
1980 Two regular expressions may be joined by the infix operator “<span class="quote">|</span>”;
1981 the resulting regular expression matches any string matching either
1984 Repetition takes precedence over concatenation, which in turn takes
1985 precedence over alternation. A whole subexpression may be enclosed in
1986 parentheses to override these precedence rules.
1987 </p><div class="note"><h3 class="title">Note</h3><p>
1988 If you compile Mutt with the GNU <span class="emphasis"><em>rx</em></span> package, the
1989 following operators may also be used in regular expressions as described in <a class="xref" href="#regex-gnu-ext" title="Table 4.3. GNU regular expression extensions">Table 4.3, “GNU regular expression extensions”</a>.
1990 </p></div><div class="table"><a id="regex-gnu-ext"></a><p class="title"><b>Table 4.3. GNU regular expression extensions</b></p><div class="table-contents"><table summary="GNU regular expression extensions" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Expression</th><th>Description</th></tr></thead><tbody><tr><td>\\y</td><td>Matches the empty string at either the beginning or the end of a word</td></tr><tr><td>\\B</td><td>Matches the empty string within a word</td></tr><tr><td>\\<</td><td>Matches the empty string at the beginning of a word</td></tr><tr><td>\\></td><td>Matches the empty string at the end of a word</td></tr><tr><td>\\w</td><td>Matches any word-constituent character (letter, digit, or underscore)</td></tr><tr><td>\\W</td><td>Matches any character that is not word-constituent</td></tr><tr><td>\\`</td><td>Matches the empty string at the beginning of a buffer (string)</td></tr><tr><td>\\'</td><td>Matches the empty string at the end of a buffer</td></tr></tbody></table></div></div><br class="table-break" /><p>
1991 Please note however that these operators are not defined by POSIX, so
1992 they may or may not be available in stock libraries on various systems.
1993 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="patterns"></a>2. Patterns: Searching, Limiting and Tagging</h2></div></div></div><p>
1994 Many of Mutt's commands allow you to specify a pattern to match
1995 (<code class="literal">limit</code>, <code class="literal">tag-pattern</code>,
1996 <code class="literal">delete-pattern</code>, etc.). <a class="xref" href="#tab-patterns" title="Table 4.4. Pattern modifiers">Table 4.4, “Pattern modifiers”</a>
1997 shows several ways to select messages.
1998 </p><div class="table"><a id="tab-patterns"></a><p class="title"><b>Table 4.4. Pattern modifiers</b></p><div class="table-contents"><table summary="Pattern modifiers" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Pattern modifier</th><th>Description</th></tr></thead><tbody><tr><td>~A</td><td>all messages</td></tr><tr><td>~b <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message body</td></tr><tr><td>=b <span class="emphasis"><em>STRING</em></span></td><td>messages which contain <span class="emphasis"><em>STRING</em></span> in the message body. If IMAP is enabled, searches for <span class="emphasis"><em>STRING</em></span> on the server, rather than downloading each message and searching it locally.</td></tr><tr><td>~B <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the whole message</td></tr><tr><td>~c <span class="emphasis"><em>EXPR</em></span></td><td>messages carbon-copied to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%c <span class="emphasis"><em>GROUP</em></span></td><td>messages carbon-copied to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~C <span class="emphasis"><em>EXPR</em></span></td><td>messages either to: or cc: <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%C <span class="emphasis"><em>GROUP</em></span></td><td>messages either to: or cc: to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~d [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-sent</span>” in a Date range</td></tr><tr><td>~D</td><td>deleted messages</td></tr><tr><td>~e <span class="emphasis"><em>EXPR</em></span></td><td>messages which contains <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>%e <span class="emphasis"><em>GROUP</em></span></td><td>messages which contain a member of <span class="emphasis"><em>GROUP</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>~E</td><td>expired messages</td></tr><tr><td>~F</td><td>flagged messages</td></tr><tr><td>~f <span class="emphasis"><em>EXPR</em></span></td><td>messages originating from <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%f <span class="emphasis"><em>GROUP</em></span></td><td>messages originating from any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~g</td><td>cryptographically signed messages</td></tr><tr><td>~G</td><td>cryptographically encrypted messages</td></tr><tr><td>~h <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message header</td></tr><tr><td>~H <span class="emphasis"><em>EXPR</em></span></td><td>messages with a spam attribute matching <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~i <span class="emphasis"><em>EXPR</em></span></td><td>messages which match <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Message-ID</span>” field</td></tr><tr><td>~k</td><td>messages which contain PGP key material</td></tr><tr><td>~L <span class="emphasis"><em>EXPR</em></span></td><td>messages either originated or received by <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%L <span class="emphasis"><em>GROUP</em></span></td><td>message either originated or received by any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~l</td><td>messages addressed to a known mailing list</td></tr><tr><td>~m [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~n [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a score in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~N</td><td>new messages</td></tr><tr><td>~O</td><td>old messages</td></tr><tr><td>~p</td><td>messages addressed to you (consults alternates)</td></tr><tr><td>~P</td><td>messages from you (consults alternates)</td></tr><tr><td>~Q</td><td>messages which have been replied to</td></tr><tr><td>~r [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-received</span>” in a Date range</td></tr><tr><td>~R</td><td>read messages</td></tr><tr><td>~s <span class="emphasis"><em>EXPR</em></span></td><td>messages having <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Subject</span>” field.</td></tr><tr><td>~S</td><td>superseded messages</td></tr><tr><td>~t <span class="emphasis"><em>EXPR</em></span></td><td>messages addressed to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~T</td><td>tagged messages</td></tr><tr><td>~u</td><td>messages addressed to a subscribed mailing list</td></tr><tr><td>~U</td><td>unread messages</td></tr><tr><td>~v</td><td>messages part of a collapsed thread.</td></tr><tr><td>~V</td><td>cryptographically verified messages</td></tr><tr><td>~x <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">References</span>” field</td></tr><tr><td>~X [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> attachments *)</td></tr><tr><td>~y <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">X-Label</span>” field</td></tr><tr><td>~z [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a size in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~=</td><td>duplicated messages (see <a class="link" href="#duplicate-threads" title="3.49. duplicate_threads">$duplicate_threads</a>)</td></tr><tr><td>~$</td><td>unreferenced messages (requires threaded view)</td></tr><tr><td>~(<span class="emphasis"><em>PATTERN</em></span>)</td><td>messages in threads
1999 containing messages matching <span class="emphasis"><em>PATTERN</em></span>, e.g. all
2000 threads containing messages from you: ~(~P)</td></tr></tbody></table></div></div><br class="table-break" /><p>
2001 Where <span class="emphasis"><em>EXPR</em></span> is a
2002 <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a>. Special attention has to be
2003 made when using regular expressions inside of patterns. Specifically,
2004 Mutt's parser for these patterns will strip one level of backslash (“<span class="quote">\</span>”),
2005 which is normally used for quoting. If it is your intention to use a
2006 backslash in the regular expression, you will need to use two backslashes
2007 instead (“<span class="quote">\\</span>”). You can force mutt to treat <span class="emphasis"><em>EXPR</em></span> as a simple string
2008 instead of a regular expression by using = instead of ˜ in the
2009 pattern name. For example, <code class="literal">=b *.*</code> will find all messages that contain
2010 the literal string “<span class="quote">*.*</span>”. Simple string matches are less powerful than
2011 regular expressions but can be considerably faster. This is especially
2012 true for IMAP folders, because string matches can be performed on the
2013 server instead of by fetching every message. IMAP treats <code class="literal">=h</code> specially:
2014 it must be of the form "header: substring" and will not partially
2015 match header names. The substring part may be omitted if you simply
2016 wish to find messages containing a particular header without regard to
2019 *) The forms “<span class="quote"><[<span class="emphasis"><em>MAX</em></span>]</span>”, “<span class="quote">>[<span class="emphasis"><em>MIN</em></span>]</span>”,
2020 “<span class="quote">[<span class="emphasis"><em>MIN</em></span>]-</span>” and “<span class="quote">-[<span class="emphasis"><em>MAX</em></span>]</span>”
2022 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="patterns-modifier"></a>2.1. Pattern Modifier</h3></div></div></div><div class="note"><h3 class="title">Note</h3><p>
2023 Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
2024 match if there is at least one match in the whole list. If you want to
2025 make sure that all elements of that list match, you need to prefix your
2026 pattern with “<span class="quote">^</span>”.
2027 This example matches all mails which only has recipients from Germany.
2028 </p></div><pre class="screen">
2030 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-patterns"></a>2.2. Simple Patterns</h3></div></div></div><p>
2031 Mutt supports two versions of so called “<span class="quote">simple searches</span>” which are
2032 issued if the query entered for searching, limiting and similar
2033 operations does not seem to be a valid pattern (i.e. it does not contain
2034 one of these characters: “<span class="quote">˜</span>”, “<span class="quote">=</span>” or “<span class="quote">%</span>”). If the query is
2035 supposed to contain one of these special characters, they must be escaped
2036 by prepending a backslash (“<span class="quote">\</span>”).
2038 The first type is by checking whether the query string equals
2039 a keyword case-insensitively from <a class="xref" href="#tab-simplesearch-keywords" title="Table 4.5. Simple search keywords">Table 4.5, “Simple search keywords”</a>:
2040 If that is the case, Mutt will use the shown pattern modifier instead.
2041 If a keyword would conflict with your search keyword, you need to turn
2042 it into a regular expression to avoid matching the keyword table. For
2043 example, if you want to find all messages matching “<span class="quote">flag</span>”
2044 (using <a class="link" href="#simple-search" title="3.266. simple_search">$simple_search</a>)
2045 but don't want to match flagged messages, simply search for
2046 “<span class="quote"><code class="literal">[f]lag</code></span>”.
2047 </p><div class="table"><a id="tab-simplesearch-keywords"></a><p class="title"><b>Table 4.5. Simple search keywords</b></p><div class="table-contents"><table summary="Simple search keywords" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Keyword</th><th>Pattern modifier</th></tr></thead><tbody><tr><td>all</td><td>~A</td></tr><tr><td>.</td><td>~A</td></tr><tr><td>^</td><td>~A</td></tr><tr><td>del</td><td>~D</td></tr><tr><td>flag</td><td>~F</td></tr><tr><td>new</td><td>~N</td></tr><tr><td>old</td><td>~O</td></tr><tr><td>repl</td><td>~Q</td></tr><tr><td>read</td><td>~R</td></tr><tr><td>tag</td><td>~T</td></tr><tr><td>unread</td><td>~U</td></tr></tbody></table></div></div><br class="table-break" /><p>
2048 The second type of simple search is to build a complex search
2049 pattern using <a class="link" href="#simple-search" title="3.266. simple_search">$simple_search</a>
2050 as a template. Mutt will insert your query properly quoted and search
2051 for the composed complex query.
2052 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="complex-patterns"></a>2.3. Complex Patterns</h3></div></div></div><p>
2053 Logical AND is performed by specifying more than one criterion. For
2055 </p><pre class="screen">
2058 would select messages which contain the word “<span class="quote">mutt</span>” in the list of
2059 recipients <span class="bold"><strong>and</strong></span> that have the word “<span class="quote">elkins</span>” in the “<span class="quote">From</span>” header
2062 Mutt also recognizes the following operators to create more complex search
2064 </p><div class="itemizedlist"><ul type="disc"><li><p>
2065 ! -- logical NOT operator
2067 | -- logical OR operator
2069 () -- logical grouping operator
2070 </p></li></ul></div><p>
2071 Here is an example illustrating a complex search pattern. This pattern will
2072 select all messages which do not contain “<span class="quote">mutt</span>” in the “<span class="quote">To</span>” or “<span class="quote">Cc</span>”
2073 field and which are from “<span class="quote">elkins</span>”.
2074 </p><div class="example"><a id="ex-pattern-bool"></a><p class="title"><b>Example 4.1. Using boolean operators in patterns</b></p><div class="example-contents"><pre class="screen">
2075 !(~t mutt|~c mutt) ~f elkins
2076 </pre></div></div><br class="example-break" /><p>
2077 Here is an example using white space in the regular expression (note
2078 the ' and " delimiters). For this to match, the mail's subject must
2079 match the “<span class="quote">^Junk +From +Me$</span>” and it must be from either “<span class="quote">Jim +Somebody</span>”
2080 or “<span class="quote">Ed +SomeoneElse</span>”:
2081 </p><pre class="screen">
2082 '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
2083 </pre><div class="note"><h3 class="title">Note</h3><p>
2084 If a regular expression contains parenthesis, or a vertical bar
2085 ("|"), you <span class="bold"><strong>must</strong></span> enclose the expression in double or single quotes since
2086 those characters are also used to separate different parts of Mutt's
2087 pattern language. For example: <code class="literal">~f "me@(mutt\.org|cs\.hmc\.edu)"</code>
2089 Without the quotes, the parenthesis wouldn't end.
2090 This would be separated to two OR'd patterns: <span class="emphasis"><em>˜f me@(mutt\.org</em></span>
2091 and <span class="emphasis"><em>cs\.hmc\.edu)</em></span>. They are never what you want.
2092 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-patterns"></a>2.4. Searching by Date</h3></div></div></div><p>
2093 Mutt supports two types of dates, <span class="emphasis"><em>absolute</em></span> and <span class="emphasis"><em>relative</em></span>.
2095 <span class="bold"><strong>Absolute</strong></span>. Dates <span class="bold"><strong>must</strong></span> be in DD/MM/YY format (month and year are
2096 optional, defaulting to the current month and year). An example of a valid
2098 </p><pre class="screen">
2099 Limit to messages matching: ~d 20/1/95-31/10
2101 If you omit the minimum (first) date, and just specify “<span class="quote">-DD/MM/YY</span>”, all
2102 messages <span class="emphasis"><em>before</em></span> the given date will be selected. If you omit the maximum
2103 (second) date, and specify “<span class="quote">DD/MM/YY-</span>”, all messages <span class="emphasis"><em>after</em></span> the given
2104 date will be selected. If you specify a single date with no dash (“<span class="quote">-</span>”),
2105 only messages sent on the given date will be selected.
2107 <span class="bold"><strong>Error Margins</strong></span>. You can add error margins to absolute dates.
2108 An error margin is a sign (+ or -), followed by a digit, followed by
2109 one of the units in <a class="xref" href="#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>. As a special case, you can replace the
2110 sign by a “<span class="quote">*</span>” character, which is equivalent to giving identical plus and minus error margins.
2111 </p><div class="table"><a id="tab-date-units"></a><p class="title"><b>Table 4.6. Date units</b></p><div class="table-contents"><table summary="Date units" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>y</td><td>Years</td></tr><tr><td>m</td><td>Months</td></tr><tr><td>w</td><td>Weeks</td></tr><tr><td>d</td><td>Days</td></tr></tbody></table></div></div><br class="table-break" /><p>
2112 Example: To select any messages two weeks around January 15, 2001,
2113 you'd use the following pattern:
2114 </p><pre class="screen">
2115 Limit to messages matching: ~d 15/1/2001*2w
2117 <span class="bold"><strong>Relative</strong></span>. This type of date is relative to the current date, and may
2119 </p><div class="itemizedlist"><ul type="disc"><li><p>
2120 ><span class="emphasis"><em>offset</em></span> (messages older than <span class="emphasis"><em>offset</em></span> units)
2122 <<span class="emphasis"><em>offset</em></span> (messages newer than <span class="emphasis"><em>offset</em></span> units)
2124 =<span class="emphasis"><em>offset</em></span> (messages exactly <span class="emphasis"><em>offset</em></span> units old)
2125 </p></li></ul></div><p>
2126 <span class="emphasis"><em>offset</em></span> is specified as a positive number with one of the units from <a class="xref" href="#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>.
2128 Example: to select messages less than 1 month old, you would use
2129 </p><pre class="screen">
2130 Limit to messages matching: ~d <1m
2131 </pre><div class="note"><h3 class="title">Note</h3><p>
2132 All dates used when searching are relative to the
2133 <span class="bold"><strong>local</strong></span> time zone, so unless you change the setting of your <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to include a
2134 <code class="literal">%[...]</code> format, these are <span class="bold"><strong>not</strong></span> the dates shown
2136 </p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tags"></a>3. Using Tags</h2></div></div></div><p>
2137 Sometimes it is desirable to perform an operation on a group of
2138 messages all at once rather than one at a time. An example might be
2139 to save messages to a mailing list to a separate folder, or to
2140 delete all messages with a given subject. To tag all messages
2141 matching a pattern, use the <code class="literal"><tag-pattern></code> function, which is bound to
2142 “<span class="quote">shift-T</span>” by default. Or you can select individual messages by
2143 hand using the <code class="literal"><tag-message></code> function, which is bound to “<span class="quote">t</span>” by
2144 default. See <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> for Mutt's pattern
2147 Once you have tagged the desired messages, you can use the
2148 “<span class="quote">tag-prefix</span>” operator, which is the “<span class="quote">;</span>” (semicolon) key by default.
2149 When the “<span class="quote">tag-prefix</span>” operator is used, the <span class="bold"><strong>next</strong></span> operation will
2150 be applied to all tagged messages if that operation can be used in that
2151 manner. If the <a class="link" href="#auto-tag" title="3.18. auto_tag">$auto_tag</a>
2152 variable is set, the next operation applies to the tagged messages
2153 automatically, without requiring the “<span class="quote">tag-prefix</span>”.
2155 In <a class="link" href="#macro" title="8. Keyboard macros">macros</a> or <a class="link" href="#push" title="22. Adding key sequences to the keyboard buffer">push</a> commands,
2156 you can use the “<span class="quote">tag-prefix-cond</span>” operator. If there are no tagged
2157 messages, mutt will "eat" the rest of the macro to abort it's execution.
2158 Mutt will stop "eating" the macro when it encounters the “<span class="quote">end-cond</span>”
2159 operator; after this operator the rest of the macro will be executed as
2161 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="hooks"></a>4. Using Hooks</h2></div></div></div><p>
2162 A <span class="emphasis"><em>hook</em></span> is a concept found in many other programs which allows you to
2163 execute arbitrary commands before performing some operation. For example,
2164 you may wish to tailor your configuration based upon which mailbox you are
2165 reading, or to whom you are sending mail. In the Mutt world, a <span class="emphasis"><em>hook</em></span>
2166 consists of a <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a> or
2167 <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">pattern</a> along with a
2168 configuration option/command. See
2170 </p><div class="itemizedlist"><ul type="disc"><li><p>
2171 <a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a>
2173 <a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a>
2175 <a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a>
2177 <a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a>
2179 <a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a>
2181 <a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
2183 <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a>
2184 </p></li></ul></div><p>
2186 for specific details on each type of <span class="emphasis"><em>hook</em></span> available.
2187 </p><div class="note"><h3 class="title">Note</h3><p>
2188 If a hook changes configuration settings, these changes remain
2189 effective until the end of the current mutt session. As this is generally
2190 not desired, a default hook needs to be added before all other hooks to
2191 restore configuration defaults. Here is an example with send-hook and the
2193 </p></div><div class="example"><a id="ex-send-hook-my-hdr"></a><p class="title"><b>Example 4.2. Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></b></p><div class="example-contents"><pre class="screen">
2194 send-hook . 'unmy_hdr From:'
2195 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
2196 </pre></div></div><br class="example-break" /><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pattern-hook"></a>4.1. Message Matching in Hooks</h3></div></div></div><p>
2197 Hooks that act upon messages (<code class="literal">message-hook, reply-hook,
2198 send-hook, send2-hook, save-hook, fcc-hook</code>) are evaluated in a
2199 slightly different manner. For the other
2200 types of hooks, a <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a> is
2201 sufficient. But in dealing with messages a finer grain of control is
2202 needed for matching since for different purposes you want to match
2205 Mutt allows the use of the <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">search pattern</a>
2206 language for matching messages in hook commands. This works in
2207 exactly the same way as it would when <span class="emphasis"><em>limiting</em></span> or
2208 <span class="emphasis"><em>searching</em></span> the mailbox, except that you are restricted to those
2209 operators which match information mutt extracts from the header of
2210 the message (i.e., from, to, cc, date, subject, etc.).
2212 For example, if you wanted to set your return address based upon sending
2213 mail to a specific address, you could do something like:
2214 </p><pre class="screen">
2215 send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
2217 which would execute the given command when sending mail to
2218 <span class="emphasis"><em>me@cs.hmc.edu</em></span>.
2220 However, it is not required that you write the pattern to match using the
2221 full searching language. You can still specify a simple <span class="emphasis"><em>regular
2222 expression</em></span> like the other hooks, in which case Mutt will translate your
2223 pattern into the full language, using the translation specified by the
2224 <a class="link" href="#default-hook" title="3.41. default_hook">$default_hook</a> variable. The
2225 pattern is translated at the time the hook is declared, so the value of
2226 <a class="link" href="#default-hook" title="3.41. default_hook">$default_hook</a> that is in effect
2227 at that time will be used.
2228 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="query"></a>5. External Address Queries</h2></div></div></div><p>
2229 Mutt supports connecting to external directory databases such as LDAP,
2230 ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
2231 using a simple interface. Using the <a class="link" href="#query-command" title="3.234. query_command">$query_command</a> variable, you specify the wrapper
2232 command to use. For example:
2233 </p><pre class="screen">
2234 set query_command = "mutt_ldap_query.pl '%s'"
2236 The wrapper script should accept the query on the command-line. It
2237 should return a one line message, then each matching response on a
2238 single line, each line containing a tab separated address then name then
2239 some other optional information. On error, or if there are no matching
2240 addresses, return a non-zero exit code and a one line error message.
2242 An example multiple response output:
2243 </p><pre class="screen">
2244 Searching database ... 20 entries ... 3 matching:
2245 me@cs.hmc.edu Michael Elkins mutt dude
2246 blong@fiction.net Brandon Long mutt and more
2247 roessler@does-not-exist.org Thomas Roessler mutt pgp
2249 There are two mechanisms for accessing the query function of mutt. One
2250 is to do a query from the index menu using the <code class="literal"><query></code> function (default: Q).
2251 This will prompt for a query, then bring up the query menu which will
2252 list the matching responses. From the query menu, you can select
2253 addresses to create aliases, or to mail. You can tag multiple addresses
2254 to mail, start a new query, or have a new query appended to the current
2257 The other mechanism for accessing the query function is for address
2258 completion, similar to the alias completion. In any prompt for address
2259 entry, you can use the <code class="literal"><complete-query></code> function (default: ^T) to run a
2260 query based on the current address you have typed. Like aliases, mutt
2261 will look for what you have typed back to the last space or comma. If
2262 there is a single response for that query, mutt will expand the address
2263 in place. If there are multiple responses, mutt will activate the query
2264 menu. At the query menu, you can select one or more addresses to be
2265 added to the prompt.
2266 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailbox-formats"></a>6. Mailbox Formats</h2></div></div></div><p>
2267 Mutt supports reading and writing of four different mailbox formats:
2268 mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there
2269 is no need to use a flag for different mailbox types. When creating new
2270 mailboxes, Mutt uses the default specified with the <a class="link" href="#mbox-type" title="3.117. mbox_type">$mbox_type</a> variable.
2272 <span class="bold"><strong>mbox</strong></span>. This is the most widely used mailbox format for UNIX. All
2273 messages are stored in a single file. Each message has a line of the form:
2274 </p><pre class="screen">
2275 From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
2277 to denote the start of a new message (this is often referred to as the
2278 “<span class="quote">From_</span>” line).
2280 <span class="bold"><strong>MMDF</strong></span>. This is a variant of the <span class="emphasis"><em>mbox</em></span> format. Each message is
2281 surrounded by lines containing “<span class="quote">^A^A^A^A</span>” (four control-A's).
2283 <span class="bold"><strong>MH</strong></span>. A radical departure from <span class="emphasis"><em>mbox</em></span> and <span class="emphasis"><em>MMDF</em></span>, a mailbox
2284 consists of a directory and each message is stored in a separate file.
2285 The filename indicates the message number (however, this is may not
2286 correspond to the message number Mutt displays). Deleted messages are
2287 renamed with a comma (,) prepended to the filename. Mutt
2288 detects this type of mailbox by looking for either <code class="literal">.mh_sequences</code>
2289 or <code class="literal">.xmhcache</code> (needed to distinguish normal directories from MH
2292 <span class="bold"><strong>Maildir</strong></span>. The newest of the mailbox formats, used by the Qmail MTA (a
2293 replacement for sendmail). Similar to <span class="emphasis"><em>MH</em></span>, except that it adds three
2294 subdirectories of the mailbox: <span class="emphasis"><em>tmp</em></span>, <span class="emphasis"><em>new</em></span> and <span class="emphasis"><em>cur</em></span>. Filenames
2295 for the messages are chosen in such a way they are unique, even when two
2296 programs are writing the mailbox over NFS, which means that no file locking
2298 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="shortcuts"></a>7. Mailbox Shortcuts</h2></div></div></div><p>
2299 There are a number of built in shortcuts which refer to specific mailboxes.
2300 These shortcuts can be used anywhere you are prompted for a file or mailbox
2302 </p><div class="itemizedlist"><ul type="disc"><li><p>
2303 ! -- refers to your <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a> (incoming) mailbox
2305 > -- refers to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> file
2307 < -- refers to your <a class="link" href="#record" title="3.242. record">$record</a> file
2309 ^ -- refers to the current mailbox
2311 - or !! -- refers to the file you've last visited
2313 ˜ -- refers to your home directory
2315 = or + -- refers to your <a class="link" href="#folder" title="3.58. folder">$folder</a> directory
2317 @<span class="emphasis"><em>alias</em></span> -- refers to the <a class="link" href="#save-hook" title="16. Specify default save mailbox">default save folder</a> as determined by the address of the alias
2318 </p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-lists"></a>8. Handling Mailing Lists</h2></div></div></div><p>
2319 Mutt has a few configuration options that make dealing with large
2320 amounts of mail easier. The first thing you must do is to let Mutt
2321 know what addresses you consider to be mailing lists (technically
2322 this does not have to be a mailing list, but that is what it is most
2323 often used for), and what lists you are subscribed to. This is
2324 accomplished through the use of the <a class="link" href="#lists" title="12. Mailing lists">lists and subscribe</a> commands in your muttrc.
2326 Now that Mutt knows what your mailing lists are, it can do several
2327 things, the first of which is the ability to show the name of a list
2328 through which you received a message (i.e., of a subscribed list) in
2329 the <span class="emphasis"><em>index</em></span> menu display. This is useful to distinguish between
2330 personal and list mail in the same mailbox. In the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable, the escape “<span class="quote">%L</span>”
2331 will return the string “<span class="quote">To <list></span>” when “<span class="quote">list</span>” appears in the
2332 “<span class="quote">To</span>” field, and “<span class="quote">Cc <list></span>” when it appears in the “<span class="quote">Cc</span>”
2333 field (otherwise it returns the name of the author).
2335 Often times the “<span class="quote">To</span>” and “<span class="quote">Cc</span>” fields in mailing list messages
2336 tend to get quite large. Most people do not bother to remove the
2337 author of the message they reply to from the list, resulting in
2338 two or more copies being sent to that person. The <code class="literal"><list-reply></code>
2339 function, which by default is bound to “<span class="quote">L</span>” in the <span class="emphasis"><em>index</em></span> menu
2340 and <span class="emphasis"><em>pager</em></span>, helps reduce the clutter by only replying to the
2341 known mailing list addresses instead of all recipients (except as
2342 specified by <code class="literal">Mail-Followup-To</code>, see below).
2344 Mutt also supports the <code class="literal">Mail-Followup-To</code> header. When you send
2345 a message to a list of recipients which includes one or several
2346 subscribed mailing lists, and if the <a class="link" href="#followup-to" title="3.60. followup_to">$followup_to</a> option is set, mutt will generate
2347 a Mail-Followup-To header which contains all the recipients to whom
2348 you send this message, but not your address. This indicates that
2349 group-replies or list-replies (also known as “<span class="quote">followups</span>”) to this
2350 message should only be sent to the original recipients of the
2351 message, and not separately to you - you'll receive your copy through
2352 one of the mailing lists you are subscribed to.
2354 Conversely, when group-replying or list-replying to a message which
2355 has a <code class="literal">Mail-Followup-To</code> header, mutt will respect this header if
2356 the <a class="link" href="#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a> configuration
2357 variable is set. Using list-reply will in this case also make sure
2358 that the reply goes to the mailing list, even if it's not specified
2359 in the list of recipients in the <code class="literal">Mail-Followup-To</code>.
2360 </p><div class="note"><h3 class="title">Note</h3><p>
2361 When header editing is enabled, you can create a
2362 <code class="literal">Mail-Followup-To</code> header manually. Mutt will only auto-generate
2363 this header if it doesn't exist when you send the message.
2365 The other method some mailing list admins use is to generate a
2366 “<span class="quote">Reply-To</span>” field which points back to the mailing list address rather
2367 than the author of the message. This can create problems when trying
2368 to reply directly to the author in private, since most mail clients
2369 will automatically reply to the address given in the “<span class="quote">Reply-To</span>”
2370 field. Mutt uses the <a class="link" href="#reply-to" title="3.245. reply_to">$reply_to</a>
2371 variable to help decide which address to use. If set to <span class="emphasis"><em>ask-yes</em></span> or
2372 <span class="emphasis"><em>ask-no</em></span>, you will be
2373 prompted as to whether or not you would like to use the address given in
2374 the “<span class="quote">Reply-To</span>” field, or reply directly to the address given in the
2375 “<span class="quote">From</span>” field. When set to <span class="emphasis"><em>yes</em></span>, the “<span class="quote">Reply-To</span>” field will be used when
2378 The “<span class="quote">X-Label:</span>” header field can be used to further identify mailing
2379 lists or list subject matter (or just to annotate messages
2380 individually). The <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable's “<span class="quote">%y</span>” and
2381 “<span class="quote">%Y</span>” escapes can be used to expand “<span class="quote">X-Label:</span>” fields in the
2382 index, and Mutt's pattern-matcher can match regular expressions to
2383 “<span class="quote">X-Label:</span>” fields with the “<span class="quote">˜y</span>” selector. “<span class="quote">X-Label:</span>” is not a
2384 standard message header field, but it can easily be inserted by procmail
2385 and other mail filtering agents.
2387 Lastly, Mutt has the ability to <a class="link" href="#sort" title="3.273. sort">sort</a> the mailbox into
2388 <a class="link" href="#threads" title="4.3. Threaded Mode">threads</a>. A thread is a group of messages which all relate to the same
2389 subject. This is usually organized into a tree-like structure where a
2390 message and all of its replies are represented graphically. If you've ever
2391 used a threaded news client, this is the same concept. It makes dealing
2392 with large volume mailing lists easier because you can easily delete
2393 uninteresting threads and quickly find topics of value.
2394 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="handling-folders"></a>9. Handling multiple folders</h2></div></div></div><p>
2395 Mutt supports setups with multiple folders, allowing all of them to
2396 be monitored for new mail (see <a class="xref" href="#mailboxes" title="14. Monitoring incoming mail">Section 14, “Monitoring incoming mail”</a> for details).
2398 When in the index menu and being idle (also see
2399 <a class="link" href="#timeout" title="3.290. timeout">$timeout</a>), Mutt periodically checks
2400 for new mail in all folders which have been configured via the
2401 <code class="literal">mailboxes</code> command. The interval depends on the folder
2402 type: for local/IMAP folders it consults
2403 <a class="link" href="#mail-check" title="3.105. mail_check">$mail_check</a> and
2404 <a class="link" href="#pop-checkinterval" title="3.218. pop_checkinterval">$pop_checkinterval</a>
2407 Outside the index menu the directory browser supports checking
2408 for new mail using the <code class="literal"><check-new></code> function which is
2409 unbound by default. Pressing TAB will bring up a
2410 menu showing the files specified by the <code class="literal">mailboxes</code> command,
2411 and indicate which contain new messages. Mutt will automatically enter this
2412 mode when invoked from the command line with the <code class="literal">-y</code> option.
2414 For the pager, index and directory browser menus, Mutt contains the
2415 <code class="literal"><buffy-list></code> function (bound to “<span class="quote">.</span>” by default)
2416 which will print a list of folders with new mail in the command line at
2417 the bottom of the screen.
2419 For the index, by default Mutt displays the number of mailboxes with new
2420 mail in the status bar, please refer to the
2421 <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>
2422 variable for details.
2424 When changing folders, Mutt fills the prompt with the first folder from
2425 the mailboxes list containing new mail (if any), pressing
2426 <span class="emphasis"><em>space</em></span> will cycle through folders with new mail.
2427 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing-threads"></a>10. Editing threads</h2></div></div></div><p>
2428 Mutt has the ability to dynamically restructure threads that are broken
2429 either by misconfigured software or bad behavior from some
2430 correspondents. This allows to clean your mailboxes formats) from these
2431 annoyances which make it hard to follow a discussion.
2432 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="link-threads"></a>10.1. Linking threads</h3></div></div></div><p>
2433 Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
2434 "References:" headers when replying to a message. This results in broken
2435 discussions because Mutt has not enough information to guess the correct
2437 You can fix this by tagging the reply, then moving to the parent message
2438 and using the <code class="literal"><link-threads></code> function (bound to & by default). The
2439 reply will then be connected to this "parent" message.
2441 You can also connect multiple children at once, tagging them and using the
2442 tag-prefix command (';') or the auto_tag option.
2443 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="break-threads"></a>10.2. Breaking threads</h3></div></div></div><p>
2444 On mailing lists, some people are in the bad habit of starting a new
2445 discussion by hitting "reply" to any message from the list and changing
2446 the subject to a totally unrelated one.
2447 You can fix such threads by using the <code class="literal"><break-thread></code> function (bound
2448 by default to #), which will turn the subthread starting from the
2449 current message into a whole different thread.
2450 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="dsn"></a>11. Delivery Status Notification (DSN) Support</h2></div></div></div><p>
2451 RFC1894 defines a set of MIME content types for relaying information
2452 about the status of electronic mail messages. These can be thought of as
2453 “<span class="quote">return receipts.</span>”
2455 To support DSN, there are two variables. <a class="link" href="#dsn-notify" title="3.47. dsn_notify">$dsn_notify</a> is used to request receipts for
2456 different results (such as failed message, message delivered, etc.).
2457 <a class="link" href="#dsn-return" title="3.48. dsn_return">$dsn_return</a> requests how much
2458 of your message should be returned with the receipt (headers or full
2461 When using <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> for mail
2462 delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
2463 supporting DSN command line options compatible to Sendmail: The -N and -R
2464 options can be used by the mail client to make requests as to what type of
2465 status messages should be returned. Please consider your MTA documentation
2466 whether DSN is supported.
2468 For SMTP delivery using <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a>, it depends on the
2469 capabilities announced by the server whether mutt will attempt to
2471 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="urlview"></a>12. Start a WWW Browser on URLs</h2></div></div></div><p>
2472 If a message contains URLs, it is efficient to get
2473 a menu with all the URLs and start a WWW browser on one of them. This
2474 functionality is provided by the external urlview program which can be
2476 <a class="ulink" href="ftp://ftp.mutt.org/mutt/contrib/" target="_top">ftp://ftp.mutt.org/mutt/contrib/</a>
2477 and the configuration commands:
2478 </p><pre class="screen">
2479 macro index \cb |urlview\n
2480 macro pager \cb |urlview\n
2481 </pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="compressedfolders"></a>1. Compressed folders Support (OPTIONAL)</h2></div></div></div><p>
2482 If Mutt was compiled with compressed folders support (by running the
2483 <span class="emphasis"><em>configure</em></span> script with the
2484 <span class="emphasis"><em>--enable-compressed</em></span> flag), Mutt can open folders
2485 stored in an arbitrary format, provided that the user has a script to
2486 convert from/to this format to one of the accepted.
2488 The most common use is to open compressed archived folders e.g. with
2491 In addition, the user can provide a script that gets a folder in an
2492 accepted format and appends its context to the folder in the
2493 user-defined format, which may be faster than converting the entire
2494 folder to the accepted format, appending to it and converting back to
2495 the user-defined format.
2497 There are three hooks defined (<a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a>, <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> and <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>) which define commands to
2498 uncompress and compress a folder and to append messages to an existing
2499 compressed folder respectively.
2503 </p><pre class="screen">
2504 open-hook \\.gz$ "gzip -cd %f > %t"
2505 close-hook \\.gz$ "gzip -c %t > %f"
2506 append-hook \\.gz$ "gzip -c %t >> %f"
2509 You do not have to specify all of the commands. If you omit <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>, the folder will be open and
2510 closed again each time you will add to it. If you omit <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> (or give empty command) , the
2511 folder will be open in the mode. If you specify <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> though you'll be able to
2512 append to the folder.
2514 Note that Mutt will only try to use hooks if the file is not in one of
2515 the accepted formats. In particular, if the file is empty, mutt
2516 supposes it is not compressed. This is important because it allows the
2517 use of programs that do not have well defined extensions. Just use
2518 "." as a regexp. But this may be surprising if your
2519 compressing script produces empty files. In this situation, unset
2520 <a class="link" href="#save-empty" title="3.252. save_empty">$save_empty</a>, so that
2521 the compressed file will be removed if you delete all of the messages.
2522 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="open-hook"></a>1.1. Open a compressed mailbox for reading</h3></div></div></div><p>
2523 Usage: <code class="literal">open-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
2525 The <span class="emphasis"><em>command</em></span> is the command that can be used for
2526 opening the folders whose names match <span class="emphasis"><em>regexp</em></span>.
2528 The <span class="emphasis"><em>command</em></span> string is the printf-like format
2529 string, and it should accept two parameters: %f, which is
2530 replaced with the (compressed) folder name, and %t which is
2531 replaced with the name of the temporary folder to which to write.
2533 %f and %t can be repeated any number of times in the
2534 command string, and all of the entries are replaced with the
2535 appropriate folder name. In addition, %% is replaced by
2536 %, as in printf, and any other %anything is left as is.
2538 The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the original compressed file. The
2539 <span class="emphasis"><em>command</em></span> should return non-zero exit status if it
2540 fails, so mutt knows something's wrong.
2544 </p><pre class="screen">
2545 open-hook \\.gz$ "gzip -cd %f > %t"
2548 If the <span class="emphasis"><em>command</em></span> is empty, this operation is
2549 disabled for this file type.
2550 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="close-hook"></a>1.2. Write a compressed mailbox</h3></div></div></div><p>
2551 Usage: <code class="literal">close-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
2553 This is used to close the folder that was open with the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command after some changes were
2556 The <span class="emphasis"><em>command</em></span> string is the command that can be
2557 used for closing the folders whose names match
2558 <span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. Temporary folder in this
2559 case is the folder previously produced by the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command.
2561 The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
2562 <span class="emphasis"><em>command</em></span> should return non-zero exit status if it
2563 fails, so mutt knows something's wrong.
2567 </p><pre class="screen">
2568 close-hook \\.gz$ "gzip -c %t > %f"
2571 If the <span class="emphasis"><em>command</em></span> is empty, this operation is
2572 disabled for this file type, and the file can only be open in the
2575 <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is not called when you
2576 exit from the folder if the folder was not changed.
2577 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="append-hook"></a>1.3. Append a message to a compressed mailbox</h3></div></div></div><p>
2578 Usage: <code class="literal">append-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
2580 This command is used for saving to an existing compressed folder. The
2581 <span class="emphasis"><em>command</em></span> is the command that can be used for
2582 appending to the folders whose names match
2583 <span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. The temporary folder in
2584 this case contains the messages that are being appended.
2586 The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
2587 <span class="emphasis"><em>command</em></span> should return non-zero exit status if it
2588 fails, so mutt knows something's wrong.
2592 </p><pre class="screen">
2593 append-hook \\.gz$ "gzip -c %t >> %f"
2596 When <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> is used, the folder
2597 is not opened, which saves time, but this means that we can not find
2598 out what the folder type is. Thus the default (<a class="link" href="#mbox-type" title="3.117. mbox_type">$mbox_type</a>) type is always
2599 supposed (i.e. this is the format used for the temporary folder).
2601 If the file does not exist when you save to it, <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is called, and not <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>. <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> is only for appending to
2604 If the <span class="emphasis"><em>command</em></span> is empty, this operation is
2605 disabled for this file type. In this case, the folder will be open and
2606 closed again (using <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> and
2607 <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a>respectively) each time you
2609 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id2592001"></a>1.4. Encrypted folders</h3></div></div></div><p>
2610 The compressed folders support can also be used to handle encrypted
2611 folders. If you want to encrypt a folder with PGP, you may want to use
2612 the following hooks:
2614 </p><pre class="screen">
2615 open-hook \\.pgp$ "pgp -f < %f > %t"
2616 close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
2619 Please note, that PGP does not support appending to an encrypted
2620 folder, so there is no append-hook defined.
2622 If you are using GnuPG instead of PGP, you may use the following hooks
2625 </p><pre class="screen">
2626 open-hook \\.gpg$ "gpg --decrypt < %f > %t"
2627 close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
2630 <span class="bold"><strong>Note:</strong></span> the folder is temporary stored
2631 decrypted in the /tmp directory, where it can be read by your system
2632 administrator. So think about the security aspects of this.
2633 </p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="mimesupport"></a>Chapter 5. Mutt's MIME Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="#mime-lookup">7. MIME Lookup</a></span></dt></dl></div><p>
2634 Quite a bit of effort has been made to make Mutt the premier text-mode
2635 MIME MUA. Every effort has been made to provide the functionality that
2636 the discerning MIME user requires, and the conformance to the standards
2637 wherever possible. When configuring Mutt for MIME, there are two extra
2638 types of configuration files which Mutt uses. One is the
2639 <code class="literal">mime.types</code> file, which contains the mapping of file extensions to
2640 IANA MIME types. The other is the <code class="literal">mailcap</code> file, which specifies
2641 the external commands to use for handling specific MIME types.
2642 </p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-mime"></a>1. Using MIME in Mutt</h2></div></div></div><p>
2643 There are three areas/menus in Mutt which deal with MIME, they are the
2644 pager (while viewing a message), the attachment menu and the compose
2646 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-pager"></a>1.1. Viewing MIME messages in the pager</h3></div></div></div><p>
2647 When you select a message from the index and view it in the pager, Mutt
2648 decodes the message to a text representation. Mutt internally supports
2649 a number of MIME types, including <code class="literal">text/plain, text/enriched,
2650 message/rfc822, and message/news</code>. In addition, the export
2651 controlled version of Mutt recognizes a variety of PGP MIME types,
2652 including PGP/MIME and application/pgp.
2654 Mutt will denote attachments with a couple lines describing them.
2655 These lines are of the form:
2656 </p><pre class="screen">
2657 [-- Attachment #1: Description --]
2658 [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
2660 Where the <code class="literal">Description</code> is the description or filename given for the
2661 attachment, and the <code class="literal">Encoding</code> is one of
2662 <code class="literal">7bit/8bit/quoted-printable/base64/binary</code>.
2664 If Mutt cannot deal with a MIME type, it will display a message like:
2665 </p><pre class="screen">
2666 [-- image/gif is unsupported (use 'v' to view this part) --]
2667 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-menu"></a>1.2. The Attachment Menu</h3></div></div></div><p>
2668 The default binding for <code class="literal">view-attachments</code> is `v', which displays the
2669 attachment menu for a message. The attachment menu displays a list of
2670 the attachments in a message. From the attachment menu, you can save,
2671 print, pipe, delete, and view attachments. You can apply these
2672 operations to a group of attachments at once, by tagging the attachments
2673 and by using the “<span class="quote">tag-prefix</span>” operator. You can also reply to the
2674 current message from this menu, and only the current attachment (or the
2675 attachments tagged) will be quoted in your reply. You can view
2676 attachments as text, or view them using the mailcap viewer definition.
2678 Finally, you can apply the usual message-related functions (like
2679 <a class="link" href="#resend-message"><code class="literal"><resend-message></code></a>, and the
2680 <code class="literal"><reply></code> and <code class="literal"><forward></code>
2681 functions) to attachments of type <code class="literal">message/rfc822</code>.
2683 See the help on the attachment menu for more information.
2684 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-menu"></a>1.3. The Compose Menu</h3></div></div></div><p>
2685 The compose menu is the menu you see before you send a message. It
2686 allows you to edit the recipient list, the subject, and other aspects
2687 of your message. It also contains a list of the attachments of your
2688 message, including the main body. From this menu, you can print, copy,
2689 filter, pipe, edit, compose, review, and rename an attachment or a
2690 list of tagged attachments. You can also modifying the attachment
2691 information, notably the type, encoding and description.
2693 Attachments appear as follows:
2694 </p><pre class="screen">
2695 - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
2696 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
2698 The '-' denotes that Mutt will delete the file after sending (or
2699 postponing, or canceling) the message. It can be toggled with the
2700 <code class="literal">toggle-unlink</code> command (default: u). The next field is the MIME
2701 content-type, and can be changed with the <code class="literal">edit-type</code> command
2702 (default: ^T). The next field is the encoding for the attachment,
2703 which allows a binary message to be encoded for transmission on 7bit
2704 links. It can be changed with the <code class="literal">edit-encoding</code> command
2705 (default: ^E). The next field is the size of the attachment,
2706 rounded to kilobytes or megabytes. The next field is the filename,
2707 which can be changed with the <code class="literal">rename-file</code> command (default: R).
2708 The final field is the description of the attachment, and can be
2709 changed with the <code class="literal">edit-description</code> command (default: d).
2710 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-types"></a>2. MIME Type configuration with <code class="literal">mime.types</code></h2></div></div></div><p>
2711 When you add an attachment to your mail message, Mutt searches your
2712 personal mime.types file at <code class="literal">${HOME}/.mime.types</code>, and then
2713 the system mime.types file at <code class="literal">/usr/local/share/mutt/mime.types</code> or
2714 <code class="literal">/etc/mime.types</code>
2716 The mime.types file consist of lines containing a MIME type and a space
2717 separated list of extensions. For example:
2718 </p><pre class="screen">
2719 application/postscript ps eps
2721 audio/x-aiff aif aifc aiff
2723 A sample <code class="literal">mime.types</code> file comes with the Mutt distribution, and
2724 should contain most of the MIME types you are likely to use.
2726 If Mutt can not determine the mime type by the extension of the file you
2727 attach, it will look at the file. If the file is free of binary
2728 information, Mutt will assume that the file is plain text, and mark it
2729 as <code class="literal">text/plain</code>. If the file contains binary information, then Mutt will
2730 mark it as <code class="literal">application/octet-stream</code>. You can change the MIME
2731 type that Mutt assigns to an attachment by using the <code class="literal">edit-type</code>
2732 command from the compose menu (default: ^T). The MIME type is actually a
2733 major mime type followed by the sub-type, separated by a '/'. 6 major
2734 types: application, text, image, video, audio, and model have been approved
2735 after various internet discussions. Mutt recognizes all of these if the
2736 appropriate entry is found in the mime.types file. It also recognizes other
2737 major mime types, such as the chemical type that is widely used in the
2738 molecular modeling community to pass molecular data in various forms to
2739 various molecular viewers. Non-recognized mime types should only be used
2740 if the recipient of the message is likely to be expecting such attachments.
2741 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailcap"></a>3. MIME Viewer configuration with <code class="literal">mailcap</code></h2></div></div></div><p>
2742 Mutt supports RFC 1524 MIME Configuration, in particular the Unix
2743 specific format specified in Appendix A of RFC 1524. This file format
2744 is commonly referred to as the mailcap format. Many MIME compliant
2745 programs utilize the mailcap format, allowing you to specify handling
2746 for all MIME types in one place for all programs. Programs known to
2747 use this format include Netscape, XMosaic, lynx and metamail.
2749 In order to handle various MIME types that Mutt can not handle
2750 internally, Mutt parses a series of external configuration files to
2751 find an external handler. The default search string for these files
2752 is a colon delimited list containing the following files:
2753 </p><div class="orderedlist"><ol type="1"><li><p><code class="literal">$HOME/.mailcap</code></p></li><li><p><code class="literal">$PKGDATADIR/mailcap</code></p></li><li><p><code class="literal">$SYSCONFDIR/mailcap</code></p></li><li><p><code class="literal">/etc/mailcap</code></p></li><li><p><code class="literal">/usr/etc/mailcap</code></p></li><li><p><code class="literal">/usr/local/etc/mailcap</code></p></li></ol></div><p>
2754 where <code class="literal">$HOME</code> is your home directory. The
2755 <code class="literal">$PKGDATADIR</code> and the
2756 <code class="literal">$SYSCONFDIR</code> directories depend on where mutt
2757 is installed: the former is the default for shared data, the
2758 latter for system configuration files.
2760 The default search path can be obtained by running the following
2762 </p><pre class="screen">
2763 mutt -nF /dev/null -Q mailcap_path
2765 In particular, the metamail distribution will install a mailcap file,
2766 usually as <code class="literal">/usr/local/etc/mailcap</code>, which contains some baseline
2768 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-basics"></a>3.1. The Basics of the mailcap file</h3></div></div></div><p>
2769 A mailcap file consists of a series of lines which are comments, blank,
2772 A comment line consists of a # character followed by anything you want.
2774 A blank line is blank.
2776 A definition line consists of a content type, a view command, and any
2777 number of optional fields. Each field of a definition line is divided
2778 by a semicolon ';' character.
2780 The content type is specified in the MIME standard type/subtype method.
2782 <code class="literal">text/plain, text/html, image/gif, </code>
2783 etc. In addition, the mailcap format includes two formats for
2784 wildcards, one using the special '*' subtype, the other is the implicit
2785 wild, where you only include the major type. For example, <code class="literal">image/*</code>, or
2786 <code class="literal">video,</code> will match all image types and video types,
2789 The view command is a Unix command for viewing the type specified. There
2790 are two different types of commands supported. The default is to send
2791 the body of the MIME message to the command on stdin. You can change
2792 this behavior by using %s as a parameter to your view command.
2793 This will cause Mutt to save the body of the MIME message to a temporary
2794 file, and then call the view command with the %s replaced by
2795 the name of the temporary file. In both cases, Mutt will turn over the
2796 terminal to the view program until the program quits, at which time Mutt
2797 will remove the temporary file if it exists.
2799 So, in the simplest form, you can send a text/plain message to the
2800 external pager more on stdin:
2801 </p><pre class="screen">
2804 Or, you could send the message as a file:
2805 </p><pre class="screen">
2808 Perhaps you would like to use lynx to interactively view a text/html
2810 </p><pre class="screen">
2813 In this case, lynx does not support viewing a file from stdin, so you
2814 must use the %s syntax.
2815 </p><div class="note"><h3 class="title">Note</h3><p>
2816 <span class="emphasis"><em>Some older versions of lynx contain a bug where they
2817 will check the mailcap file for a viewer for text/html. They will find
2818 the line which calls lynx, and run it. This causes lynx to continuously
2819 spawn itself to view the object.</em></span>
2821 On the other hand, maybe you don't want to use lynx interactively, you
2822 just want to have it convert the text/html to text/plain, then you can
2824 </p><pre class="screen">
2825 text/html; lynx -dump %s | more
2827 Perhaps you wish to use lynx to view text/html files, and a pager on
2828 all other text formats, then you would use the following:
2829 </p><pre class="screen">
2833 This is the simplest form of a mailcap file.
2834 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="secure-mailcap"></a>3.2. Secure use of mailcap</h3></div></div></div><p>
2835 The interpretation of shell meta-characters embedded in MIME parameters
2836 can lead to security problems in general. Mutt tries to quote parameters
2837 in expansion of %s syntaxes properly, and avoids risky characters by
2838 substituting them, see the <a class="link" href="#mailcap-sanitize" title="3.107. mailcap_sanitize">$mailcap_sanitize</a> variable.
2840 Although mutt's procedures to invoke programs with mailcap seem to be
2841 safe, there are other applications parsing mailcap, maybe taking less care
2842 of it. Therefore you should pay attention to the following rules:
2844 <span class="emphasis"><em>Keep the %-expandos away from shell quoting.</em></span>
2845 Don't quote them with single or double quotes. Mutt does this for
2846 you, the right way, as should any other program which interprets
2847 mailcap. Don't put them into backtick expansions. Be highly careful
2848 with eval statements, and avoid them if possible at all. Trying to fix
2849 broken behavior with quotes introduces new leaks - there is no
2850 alternative to correct quoting in the first place.
2852 If you have to use the %-expandos' values in context where you need
2853 quoting or backtick expansions, put that value into a shell variable
2854 and reference the shell variable where necessary, as in the following
2855 example (using <code class="literal">$charset</code> inside the backtick expansion is safe,
2856 since it is not itself subject to any further expansion):
2857 </p><pre class="screen">
2858 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
2859 && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
2860 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="advanced-mailcap"></a>3.3. Advanced mailcap Usage</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="optional-mailcap-fields"></a>3.3.1. Optional Fields</h4></div></div></div><p>
2861 In addition to the required content-type and view command fields, you
2862 can add semi-colon ';' separated fields to set flags and other options.
2863 Mutt recognizes the following optional fields:
2864 </p><div class="variablelist"><dl><dt><span class="term">copiousoutput</span></dt><dd><p>
2865 This flag tells Mutt that the command passes possibly large amounts of
2866 text on stdout. This causes Mutt to invoke a pager (either the internal
2867 pager or the external pager defined by the pager variable) on the output
2868 of the view command. Without this flag, Mutt assumes that the command
2869 is interactive. One could use this to replace the pipe to <code class="literal">more</code>
2870 in the <code class="literal">lynx -dump</code> example in the Basic section:
2871 </p><pre class="screen">
2872 text/html; lynx -dump %s ; copiousoutput
2874 This will cause lynx to format the text/html output as text/plain
2875 and Mutt will use your standard pager to display the results.
2876 </p></dd><dt><span class="term">needsterminal</span></dt><dd><p>
2877 Mutt uses this flag when viewing attachments with <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, in order to decide whether it should honor the setting
2878 of the <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> variable or
2879 not. When an attachment is viewed using an interactive program, and the
2880 corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag, Mutt will use
2881 <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> and the exit status
2882 of the program to decide if it will ask you to press a key after the
2883 external program has exited. In all other situations it will not prompt
2885 </p></dd><dt><span class="term">compose=<command></span></dt><dd><p>
2886 This flag specifies the command to use to create a new attachment of a
2887 specific MIME type. Mutt supports this from the compose menu.
2888 </p></dd><dt><span class="term">composetyped=<command></span></dt><dd><p>
2889 This flag specifies the command to use to create a new attachment of a
2890 specific MIME type. This command differs from the compose command in
2891 that mutt will expect standard MIME headers on the data. This can be
2892 used to specify parameters, filename, description, etc. for a new
2893 attachment. Mutt supports this from the compose menu.
2894 </p></dd><dt><span class="term">print=<command></span></dt><dd><p>
2895 This flag specifies the command to use to print a specific MIME type.
2896 Mutt supports this from the attachment and compose menus.
2897 </p></dd><dt><span class="term">edit=<command></span></dt><dd><p>
2898 This flag specifies the command to use to edit a specific MIME type.
2899 Mutt supports this from the compose menu, and also uses it to compose
2900 new attachments. Mutt will default to the defined editor for text
2902 </p></dd><dt><span class="term">nametemplate=<template></span></dt><dd><p>
2903 This field specifies the format for the file denoted by %s in the
2904 command fields. Certain programs will require a certain file extension,
2905 for instance, to correctly view a file. For instance, lynx will only
2906 interpret a file as <code class="literal">text/html</code> if the file ends in <code class="literal">.html</code>.
2907 So, you would specify lynx as a <code class="literal">text/html</code> viewer with a line in
2908 the mailcap file like:
2909 </p><pre class="screen">
2910 text/html; lynx %s; nametemplate=%s.html
2911 </pre></dd><dt><span class="term">test=<command></span></dt><dd><p>
2912 This field specifies a command to run to test whether this mailcap
2913 entry should be used. The command is defined with the command expansion
2914 rules defined in the next section. If the command returns 0, then the
2915 test passed, and Mutt uses this entry. If the command returns non-zero,
2916 then the test failed, and Mutt continues searching for the right entry.
2917 Note that the content-type must match before Mutt performs the test.
2919 </p><pre class="screen">
2920 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
2923 In this example, Mutt will run the program RunningX which will return 0
2924 if the X Window manager is running, and non-zero if it isn't. If
2925 RunningX returns 0, then Mutt will call netscape to display the
2926 text/html object. If RunningX doesn't return 0, then Mutt will go on
2927 to the next entry and use lynx to display the text/html object.
2928 </p></dd></dl></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-search-order"></a>3.3.2. Search Order</h4></div></div></div><p>
2929 When searching for an entry in the mailcap file, Mutt will search for
2930 the most useful entry for its purpose. For instance, if you are
2931 attempting to print an <code class="literal">image/gif</code>, and you have the following
2932 entries in your mailcap file, Mutt will search for an entry with the
2934 </p><pre class="screen">
2936 image/gif; ; print= anytopnm %s | pnmtops | lpr; \
2939 Mutt will skip the <code class="literal">image/*</code> entry and use the <code class="literal">image/gif</code>
2940 entry with the print command.
2942 In addition, you can use this with <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>
2943 to denote two commands for viewing an attachment, one to be viewed
2944 automatically, the other to be viewed interactively from the attachment
2945 menu. In addition, you can then use the test feature to determine which
2946 viewer to use interactively depending on your environment.
2947 </p><pre class="screen">
2948 text/html; netscape -remote 'openURL(%s)' ; test=RunningX
2949 text/html; lynx %s; nametemplate=%s.html
2950 text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
2952 For <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, Mutt will choose the third
2953 entry because of the copiousoutput tag. For interactive viewing, Mutt
2954 will run the program RunningX to determine if it should use the first
2955 entry. If the program returns non-zero, Mutt will use the second entry
2956 for interactive viewing.
2957 </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-command-expansion"></a>3.3.3. Command Expansion</h4></div></div></div><p>
2958 The various commands defined in the mailcap files are passed to the
2959 <code class="literal">/bin/sh</code> shell using the system() function. Before the
2960 command is passed to <code class="literal">/bin/sh -c</code>, it is parsed to expand
2961 various special parameters with information from Mutt. The keywords
2963 </p><div class="variablelist"><dl><dt><span class="term">%s</span></dt><dd><p>
2964 As seen in the basic mailcap section, this variable is expanded
2965 to a filename specified by the calling program. This file contains
2966 the body of the message to view/print/edit or where the composing
2967 program should place the results of composition. In addition, the
2968 use of this keyword causes Mutt to not pass the body of the message
2969 to the view/print/edit program on stdin.
2970 </p></dd><dt><span class="term">%t</span></dt><dd><p>
2971 Mutt will expand %t to the text representation of the content
2972 type of the message in the same form as the first parameter of the
2973 mailcap definition line, ie <code class="literal">text/html</code> or
2974 <code class="literal">image/gif</code>.
2975 </p></dd><dt><span class="term">%{<parameter>}</span></dt><dd><p>
2976 Mutt will expand this to the value of the specified parameter
2977 from the Content-Type: line of the mail message. For instance, if
2978 Your mail message contains:
2979 </p><pre class="screen">
2980 Content-Type: text/plain; charset=iso-8859-1
2982 then Mutt will expand %{charset} to iso-8859-1. The default metamail
2983 mailcap file uses this feature to test the charset to spawn an xterm
2984 using the right charset to view the message.
2985 </p></dd><dt><span class="term">\%</span></dt><dd><p>
2986 This will be replaced by a %
2987 </p></dd></dl></div><p>
2988 Mutt does not currently support the %F and %n keywords
2989 specified in RFC 1524. The main purpose of these parameters is for
2990 multipart messages, which is handled internally by Mutt.
2991 </p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-example"></a>3.4. Example mailcap files</h3></div></div></div><p>
2992 This mailcap file is fairly simple and standard:
2993 </p><pre class="screen">
2994 # I'm always running X :)
2995 video/*; xanim %s > /dev/null
2996 image/*; xv %s > /dev/null
2998 # I'm always running netscape (if my computer had more memory, maybe)
2999 text/html; netscape -remote 'openURL(%s)'
3001 This mailcap file shows quite a number of examples:
3002 </p><pre class="screen">
3003 # Use xanim to view all videos Xanim produces a header on startup,
3004 # send that to /dev/null so I don't see it
3005 video/*; xanim %s > /dev/null
3007 # Send html to a running netscape by remote
3008 text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
3010 # If I'm not running netscape but I am running X, start netscape on the
3012 text/html; netscape %s; test=RunningX
3014 # Else use lynx to view it as text
3017 # This version would convert the text/html to text/plain
3018 text/html; lynx -dump %s; copiousoutput
3020 # I use enscript to print text in two columns to a page
3021 text/*; more %s; print=enscript -2Gr %s
3023 # Netscape adds a flag to tell itself to view jpegs internally
3024 image/jpeg;xv %s; x-mozilla-flags=internal
3026 # Use xv to view images if I'm running X
3027 # In addition, this uses the \ to extend the line and set my editor
3029 image/*;xv %s; test=RunningX; \
3032 # Convert images to text using the netpbm tools
3033 image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
3034 pbmtoascii -1x2 ) 2>&1 ; copiousoutput
3036 # Send excel spreadsheets to my NT box
3037 application/ms-excel; open.pl %s
3038 </pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="auto-view"></a>4. MIME Autoview</h2></div></div></div><p>
3039 In addition to explicitly telling Mutt to view an attachment with the
3040 MIME viewer defined in the mailcap file, Mutt has support for
3041 automatically viewing MIME attachments while in the pager.
3043 To work, you must define a viewer in the mailcap file which uses the
3044 <code class="literal">copiousoutput</code> option to denote that it is non-interactive.
3045 Usually, you also use the entry to convert the attachment to a text
3046 representation which you can view in the pager.
3048 You then use the <code class="literal">auto_view</code> muttrc command to list the
3049 content-types that you wish to view automatically.
3051 For instance, if you set auto_view to:
3052 </p><pre class="screen">
3053 auto_view text/html application/x-gunzip \
3054 application/postscript image/gif application/x-tar-gz
3056 Mutt could use the following mailcap entries to automatically view
3057 attachments of these types.
3058 </p><pre class="screen">
3059 text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
3060 image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | \
3061 pgmtopbm | pbmtoascii ; copiousoutput
3062 application/x-gunzip; gzcat; copiousoutput
3063 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
3064 application/postscript; ps2ascii %s; copiousoutput
3066 “<span class="quote">unauto_view</span>” can be used to remove previous entries from the autoview list.
3067 This can be used with message-hook to autoview messages based on size, etc.
3068 “<span class="quote">unauto_view *</span>” will remove all previous entries.
3069 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternative-order"></a>5. MIME Multipart/Alternative</h2></div></div></div><p>
3070 Mutt has some heuristics for determining which attachment of a
3071 multipart/alternative type to display. First, mutt will check the
3072 alternative_order list to determine if one of the available types
3073 is preferred. The alternative_order list consists of a number of
3074 mimetypes in order, including support for implicit and explicit
3075 wildcards, for example:
3076 </p><pre class="screen">
3077 alternative_order text/enriched text/plain text application/postscript image/*
3079 Next, mutt will check if any of the types have a defined
3080 <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, and use that. Failing
3081 that, Mutt will look for any text type. As a last attempt, mutt will
3082 look for any type it knows how to handle.
3084 To remove a MIME type from the <code class="literal">alternative_order</code> list, use the
3085 <code class="literal">unalternative_order</code> command.
3086 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="attachments"></a>6. Attachment Searching and Counting</h2></div></div></div><p>
3087 If you ever lose track of attachments in your mailboxes, Mutt's
3088 attachment-counting and -searching support might be for you. You can
3089 make your message index display the number of qualifying attachments in
3090 each message, or search for messages by attachment count. You also can
3091 configure what kinds of attachments qualify for this feature with the
3092 attachments and unattachments commands.
3094 In order to provide this information, mutt needs to fully MIME-parse
3095 all messages affected first. This can slow down operation especially for
3096 remote mail folders such as IMAP because all messages have to be
3097 downloaded first regardless whether the user really wants to view them
3101 </p><pre class="screen">
3102 attachments {+|-}disposition mime-type
3103 unattachments {+|-}disposition mime-type
3106 Disposition is the attachment's Content-disposition type -- either
3107 <code class="literal">inline</code> or <code class="literal">attachment</code>.
3108 You can abbreviate this to <code class="literal">I</code> or <code class="literal">A</code>.
3110 Disposition is prefixed by either a + symbol or a - symbol. If it's
3111 a +, you're saying that you want to allow this disposition and MIME
3112 type to qualify. If it's a -, you're saying that this disposition
3113 and MIME type is an exception to previous + rules. There are examples
3114 below of how this is useful.
3116 Mime-type is, unsurprisingly, the MIME type of the attachment you want
3117 to affect. A MIME type is always of the format <code class="literal">major/minor</code>, where
3118 <code class="literal">major</code> describes the broad category of document you're looking at, and
3119 <code class="literal">minor</code> describes the specific type within that category. The major
3120 part of mime-type must be literal text (or the special token “<span class="quote"><code class="literal">*</code></span>”), but
3121 the minor part may be a regular expression. (Therefore, “<span class="quote"><code class="literal">*/.*</code></span>” matches
3124 The MIME types you give to the attachments directive are a kind of
3125 pattern. When you use the attachments directive, the patterns you
3126 specify are added to a list. When you use unattachments, the pattern
3127 is removed from the list. The patterns are not expanded and matched
3128 to specific MIME types at this time -- they're just text in a list.
3129 They're only matched when actually evaluating a message.
3131 Some examples might help to illustrate. The examples that are not
3132 commented out define the default configuration of the lists.
3133 </p><div class="example"><a id="ex-attach-count"></a><p class="title"><b>Example 5.1. Attachment counting</b></p><div class="example-contents"><pre class="screen">
3134 ## Removing a pattern from a list removes that pattern literally. It
3135 ## does not remove any type matching the pattern.
3137 ## attachments +A */.*
3138 ## attachments +A image/jpeg
3139 ## unattachments +A */.*
3141 ## This leaves "attached" image/jpeg files on the allowed attachments
3142 ## list. It does not remove all items, as you might expect, because the
3143 ## second */.* is not a matching expression at this time.
3145 ## Remember: "unattachments" only undoes what "attachments" has done!
3146 ## It does not trigger any matching on actual messages.
3149 ## Qualify any MIME part with an "attachment" disposition, EXCEPT for
3150 ## text/x-vcard and application/pgp parts. (PGP parts are already known
3151 ## to mutt, and can be searched for with ~g, ~G, and ~k.)
3153 ## I've added x-pkcs7 to this, since it functions (for S/MIME)
3154 ## analogously to PGP signature attachments. S/MIME isn't supported
3155 ## in a stock mutt build, but we can still treat it specially here.
3158 attachments -A text/x-vcard application/pgp.*
3159 attachments -A application/x-pkcs7-.*
3161 ## Discount all MIME parts with an "inline" disposition, unless they're
3162 ## text/plain. (Why inline a text/plain part unless it's external to the
3165 attachments +I text/plain
3167 ## These two lines make Mutt qualify MIME containers. (So, for example,
3168 ## a message/rfc822 forward will count as an attachment.) The first
3169 ## line is unnecessary if you already have "attach-allow */.*", of
3170 ## course. These are off by default! The MIME elements contained
3171 ## within a message/* or multipart/* are still examined, even if the
3172 ## containers themseves don't qualify.
3174 #attachments +A message/.* multipart/.*
3175 #attachments +I message/.* multipart/.*
3177 ## You probably don't really care to know about deleted attachments.
3178 attachments -A message/external-body
3179 attachments -I message/external-body
3180 </pre></div></div><br class="example-break" /><p>
3181 Entering the command “<span class="quote"><code class="literal">attachments ?</code></span>”
3182 as a command will list your current settings in Muttrc format, so that
3183 it can be pasted elsewhere.
3184 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-lookup"></a>7. MIME Lookup</h2></div></div></div><p>
3185 Mutt's mime_lookup list specifies a list of mime-types that should not
3186 be treated according to their mailcap entry. This option is designed to
3187 deal with binary types such as application/octet-stream. When an attachment's
3188 mime-type is listed in mime_lookup, then the extension of the filename will
3189 be compared to the list of extensions in the mime.types file. The mime-type
3190 associated with this extension will then be used to process the attachment
3191 according to the rules in the mailcap file and according to any other configuration
3192 options (such as auto_view) specified. Common usage would be:
3193 </p><pre class="screen">
3194 mime_lookup application/octet-stream application/X-Lotus-Manuscript
3196 In addition, the unmime_lookup command may be used to disable this feature
3197 for any particular mime-type if it had been set, for example, in a global
3199 </p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="#exact-address">8. Exact address generation</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General notes</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/disabling features</h3></div></div></div><p>
3200 Mutt supports several of optional features which can be enabled or
3201 disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script
3202 certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of
3203 the <span class="emphasis"><em>configure --help</em></span> output.
3205 Which features are enabled or disabled can later be determined from the
3206 output of <code class="literal">mutt -v</code>. If a compile option starts with
3207 “<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if
3208 mutt was compiled using GnuTLS for encrypted communication instead of
3209 OpenSSL, <code class="literal">mutt -v</code> would contain:
3210 </p><pre class="screen">
3211 -USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL syntax</h3></div></div></div><p>
3212 Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
3213 to access servers using URLs. The canonical syntax for specifying URLs
3214 in mutt is (an item enclosed in <code class="literal">[]</code> means it is optional and
3216 </p><pre class="screen">
3217 proto[s]://[username[:password]@]server[:port]/[path]
3219 <code class="literal">proto</code> is the communication protocol:
3220 <code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and
3221 <code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”
3222 is appended, mutt will attempt to establish an encrypted communication
3223 using SSL or TLS. If no explicit port is given, mutt will use the
3224 system's default for the given protocol.
3226 Since all protocols by mutt support authentication, the username may be
3227 given directly in the URL instead of using the <code class="literal">pop_user</code> or
3228 <code class="literal">imap_user</code> variables. It may contain the “<span class="quote">@</span>” symbol
3229 being used by many mail systems as part of the login name. A password can be
3230 given, too but is not recommended if the URL is specified in a configuration
3233 The optional path is only relevant for IMAP.
3235 For IMAP for example, you can select an alternative port by specifying it with the
3236 server: <code class="literal">imap://imapserver:port/INBOX</code>. You can also specify different
3237 username for each folder: <code class="literal">imap://username@imapserver[:port]/INBOX</code>
3238 or <code class="literal">imap://username2@imapserver[:port]/path/to/folder</code>.
3239 Replacing <code class="literal">imap://</code> by <code class="literal">imaps://</code>
3240 would make mutt attempt to connect using SSL or TLS on a different port
3241 to encrypt the communication.
3242 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
3243 If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
3244 compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
3245 by running the <span class="emphasis"><em>configure</em></span> script with the
3246 <span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or
3247 <span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then
3248 attempt to encrypt communication with remote servers if these protocols
3249 are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.
3250 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
3251 If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
3252 script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
3253 with mailboxes located on a remote POP3 server and fetch mail for local
3256 Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol
3257 for unencrypted and <code class="literal">pops</code> for encrypted
3258 communication, see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.
3260 Polling for new mail is more expensive over POP3 than locally. For this
3261 reason the frequency at which Mutt will check for mail remotely can be
3263 <a class="link" href="#pop-checkinterval" title="3.218. pop_checkinterval">$pop_checkinterval</a>
3264 variable, which defaults to every 60 seconds.
3265 </p><a id="fetch-mail"></a><p>
3266 Another way to access your POP3 mail is the <code class="literal"><fetch-mail$</code> function
3267 (default: G). It allows to connect to <a class="link" href="#pop-host" title="3.220. pop_host">$pop_host</a>, fetch all your new mail and place it in the
3268 local <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a>. After this
3269 point, Mutt runs exactly as if the mail had always been local.
3270 </p><div class="note"><h3 class="title">Note</h3><p>
3271 If you only need to fetch all messages to a
3272 local mailbox you should consider using a specialized program, such as
3273 <code class="literal">fetchmail</code>, <code class="literal">getmail</code> or similar.
3274 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
3275 If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>
3276 script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
3277 with folders located on a remote IMAP server.
3279 You can access the remote inbox by selecting the folder by its URL
3280 (see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the
3281 <code class="literal">imap</code> or <code class="literal">imaps</code> protocol.
3282 Alternatively, a pine-compatible notation is also supported, ie
3283 <code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>
3285 Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should
3286 correctly notice which separator is being used by the server and convert
3289 When browsing folders on an IMAP server, you can toggle whether to look
3290 at only the folders you are subscribed to, or all folders with the
3291 <span class="emphasis"><em>toggle-subscribed</em></span> command. See also the
3292 <a class="link" href="#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.
3294 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
3295 want to carefully tune the
3296 <a class="link" href="#mail-check" title="3.105. mail_check">$mail_check</a>
3298 <a class="link" href="#timeout" title="3.290. timeout">$timeout</a>
3299 variables. Personally I use
3300 </p><pre class="screen">
3304 with relatively good results over my slow modem line.
3305 </p><div class="note"><h3 class="title">Note</h3><p>
3306 Note that if you are using mbox as the mail store on UW servers prior to
3307 v12.250, the server has been reported to disconnect a client if another client
3308 selects the same folder.
3309 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The Folder Browser</h3></div></div></div><p>
3310 As of version 1.2, mutt supports browsing mailboxes on an IMAP
3311 server. This is mostly the same as the local file browser, with the
3312 following differences:
3313 </p><div class="itemizedlist"><ul type="disc"><li><p>
3314 In lieu of file permissions, mutt displays the string "IMAP",
3315 possibly followed by the symbol "+", indicating
3316 that the entry contains both messages and subfolders. On
3317 Cyrus-like servers folders will often contain both messages and
3320 For the case where an entry can contain both messages and
3321 subfolders, the selection key (bound to <code class="literal">enter</code> by default)
3322 will choose to descend into the subfolder view. If you wish to view
3323 the messages in that folder, you must use <code class="literal">view-file</code> instead
3324 (bound to <code class="literal">space</code> by default).
3326 You can create, delete and rename mailboxes with the
3327 <code class="literal">create-mailbox</code>, <code class="literal">delete-mailbox</code>, and
3328 <code class="literal">rename-mailbox</code> commands (default bindings: <code class="literal">C</code>,
3329 <code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also
3330 <code class="literal">subscribe</code> and <code class="literal">unsubscribe</code> to mailboxes (normally
3331 these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
3332 </p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
3333 Mutt supports four authentication methods with IMAP servers: SASL,
3334 GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
3335 NTLM authentication for you poor exchange users out there, but it has
3336 yet to be integrated into the main tree). There is also support for
3337 the pseudo-protocol ANONYMOUS, which allows you to log in to a public
3338 IMAP server without having an account. To use ANONYMOUS, simply make
3339 your username blank or "anonymous".
3341 SASL is a special super-authenticator, which selects among several protocols
3342 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure
3343 method available on your host and the server. Using some of these methods
3344 (including DIGEST-MD5 and possibly GSSAPI), your entire session will be
3345 encrypted and invisible to those teeming network snoops. It is the best
3346 option if you have it. To use it, you must have the Cyrus SASL library
3347 installed on your system and compile mutt with the <span class="emphasis"><em>--with-sasl</em></span> flag.
3349 Mutt will try whichever methods are compiled in and available on the server,
3350 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
3352 There are a few variables which control authentication:
3353 </p><div class="itemizedlist"><ul type="disc"><li><p>
3354 <a class="link" href="#imap-user" title="3.96. imap_user">$imap_user</a> - controls
3355 the username under which you request authentication on the IMAP server,
3356 for all authenticators. This is overridden by an explicit username in
3357 the mailbox path (ie by using a mailbox name of the form
3358 <code class="literal">{user@host}</code>).
3360 <a class="link" href="#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a
3361 password which you may preset, used by all authentication methods where
3362 a password is needed.
3364 <a class="link" href="#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - a colon-delimited list of IMAP
3365 authentication methods to try, in the order you wish to try them. If
3366 specified, this overrides mutt's default (attempt everything, in the order
3368 </p></li></ul></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
3369 Besides supporting traditional mail delivery through a
3370 sendmail-compatible program, mutt supports delivery through SMTP if it
3371 was configured and built with <code class="literal">--enable-smtp</code>.
3373 If the configuration variable
3374 <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a> is set, mutt
3375 will contact the given SMTP server to deliver messages; if it is unset,
3376 mutt will use the program specified by <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a>.
3378 For details on the URL syntax, please see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>.
3380 The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol
3381 using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
3382 for SASL are specified in <a class="link" href="#smtp-authenticators" title="3.270. smtp_authenticators">$smtp_authenticators</a>
3383 defaulting to an empty list which makes mutt try all available methods
3384 from most-secure to least-secure.
3385 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing multiple accounts</h2></div></div></div><p>
3386 If you happen to have accounts on multiple IMAP, POP and/or SMTP servers,
3387 you may find managing all the authentication settings inconvenient and
3388 error-prone. The account-hook command may help. This hook works like
3389 folder-hook but is invoked whenever you access a remote mailbox
3390 (including inside the folder browser), not just when you open the
3391 mailbox which includes (for example) polling for new mail, storing Fcc
3392 messages and saving messages to a folder. As a consequence,
3393 account-hook should only be used to set connection-related settings such
3394 as passwords or tunnel commands but not settings such as sender
3395 address or name (because in general it should be considered unpredictable
3396 which account-hook was last used).
3399 </p><pre class="screen">
3400 account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
3401 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
3402 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
3403 account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
3404 </pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local caching</h2></div></div></div><p>
3405 Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>
3406 the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the
3407 so-called “<span class="quote">body caching</span>” which are both described in this section.
3409 Header caching is optional as it depends on external libraries, body
3410 caching is always enabled if mutt is compiled with POP and/or IMAP
3411 support as these use it (body caching requires no external library).
3412 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header caching</h3></div></div></div><p>
3413 Mutt provides optional support for caching message headers for the
3414 following types of folders: IMAP, POP, Maildir and MH. Header caching
3415 greatly improves speed because for remote folders, headers
3416 usually only need to be downloaded once. For Maildir and MH, reading the
3417 headers from a single file is much faster than looking at possibly
3418 thousands of single files (since Maildir and MH use one file per message.)
3420 Header caching can be enabled via the configure script and the
3421 <span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on
3422 by default because external database libraries are required: one
3423 of tokyocabinet, qdbm, gdbm or bdb must be present.
3425 If enabled, <a class="link" href="#header-cache" title="3.109. header_cache">$header_cache</a> can be
3426 used to either point to a file or a directory. If set to point to
3427 a file, one database file for all folders will be used (which may
3428 result in lower performance), but one file per folder if it points
3431 For the one-file-per-folder case, database files for remote folders
3432 will be named according to their URL while database files for local
3433 folders will be named by the MD5 checksums of their path. These database
3434 files may be safely removed if a system is short on space. You
3435 can compute the name of the header cache file for a particular local folder
3436 through a command like the following:
3437 </p><pre class="screen">
3438 $ printf '%s' '/path/to/folder' | md5sum
3440 The <code class="literal">md5sum</code> command may also be
3441 named <code class="literal">md5</code>, depending on your operating system.
3442 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body caching</h3></div></div></div><p>
3443 Both cache methods can be combined using the same directory for storage
3444 (and for IMAP/POP even provide meaningful file names) which simplifies
3445 manual maintenance tasks.
3447 In addition to caching message headers only, mutt can also cache
3448 whole message bodies. This results in faster display of messages
3449 for POP and IMAP folders because messages usually have to be
3450 downloaded only once.
3452 For configuration, the variable <a class="link" href="#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a
3453 directory. There, mutt will create a hierarchy of subdirectories
3454 named like: <code class="literal">proto:user@hostname</code> where
3455 <code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within
3456 there for each folder, mutt stores messages in single files (just
3457 like Maildir) so that with manual symlink creation these cache
3458 directories can be examined with mutt as read-only Maildir folders.
3460 All files can be removed as needed if the consumed disk space
3461 becomes an issue as mutt will silently fetch missing items again.
3462 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.3. Maintenance</h3></div></div></div><p>
3463 Mutt does not (yet) support maintenance features for header cache
3464 database files so that files have to be removed in case they grow too
3465 big. It depends on the database library used for header caching whether
3466 disk space freed by removing messages is re-used.
3468 For body caches, mutt can keep the local cache in sync with the
3469 remote mailbox if the
3470 <a class="link" href="#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a>
3471 variable is set. Cleaning means to remove messages from the cache which
3472 are no longer present in the mailbox which only happens when other mail
3473 clients or instances of mutt using a different body cache location
3474 delete messages (Mutt itself removes deleted messages from the cache
3475 when syncing a mailbox). As cleaning can take a noticeable amount of time,
3476 it should not be set in general but only occasionally.
3477 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact address generation</h2></div></div></div><p>
3478 Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and
3479 writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when
3480 reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
3481 switch can be given to configure to build it with write-support
3482 for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
3483 <code class="literal">mutt -v</code> indicates whether it's supported.
3484 </p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="tuning"></a>Chapter 7. Performance tuning</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="#tuning-search">3. Searching and limiting</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-mailboxes"></a>1. Reading and writing mailboxes</h2></div></div></div><p>
3485 Mutt's performance when reading mailboxes can be improved in two ways:
3486 </p><div class="orderedlist"><ol type="1"><li><p>
3487 For remote folders (IMAP and POP) as well as folders using
3488 one-file-per message storage (Maildir and MH), mutt's
3489 performance can be greatly improved using
3490 <a class="link" href="#header-caching" title="7.1. Header caching">header caching</a>.
3491 Using a single database per folder may further increase
3494 Mutt provides the <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>
3495 and <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a>
3496 variables to specify at which rate to update progress
3497 counters. If these values are too low, mutt may spend more
3498 time on updating the progress counter than it spends on
3499 actually reading/writing folders.
3501 For example, when opening a maildir folder with a few
3502 thousand messages, the default value for
3503 <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>
3504 may be too low. It can be tuned on on a folder-basis using
3505 <a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hooks</a>:
3506 </p><pre class="screen">
3507 # use very high $read_inc to speed up reading hcache'd maildirs
3508 folder-hook . 'set read_inc=1000'
3509 # use lower value for reading slower remote IMAP folders
3510 folder-hook ^imap 'set read_inc=100'
3511 # use even lower value for reading even slower remote POP folders
3512 folder-hook ^pop 'set read_inc=1'</pre></li></ol></div><p>These settings work on a per-message basis. However, as messages may
3513 greatly differ in size and certain operations are much faster than others,
3514 even per-folder settings of the increment variables may not be
3515 desirable as they produce either too few or too much progress updates.
3516 Thus, Mutt allows to limit the number of progress updates per second it'll
3517 actually send to the terminal using the
3518 <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> variable.</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-messages"></a>2. Reading messages from remote folders</h2></div></div></div><p>
3519 Reading messages from remote folders such as IMAP an POP can be
3520 slow especially for large mailboxes since mutt only caches a very
3521 limited number of recently viewed messages (usually 10) per
3522 session (so that it will be gone for the next session.)
3524 To improve performance and permanently cache whole messages,
3525 please refer to mutt's so-called
3526 <a class="link" href="#body-caching" title="7.2. Body caching">body caching</a> for details.
3527 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-search"></a>3. Searching and limiting</h2></div></div></div><p>
3528 When searching mailboxes either via a search or a limit action, for
3529 some patterns mutt distinguishes between regular expression and string
3530 searches. For regular expressions, patterns are prefixed with
3531 “<span class="quote">˜</span>” and with “<span class="quote">=</span>” for string searches.
3533 Even though a regular expression search is fast, it's several times
3534 slower than a pure string search which is noticeable especially on large
3535 folders. As a consequence, a string search should be used instead of a
3536 regular expression search if the user already knows enough about the
3539 For example, when limiting a large folder to all messages sent to or by
3540 an author, it's much faster to search for the initial part of an e-mail
3541 address via <code class="literal">=Luser@</code> instead of
3542 <code class="literal">˜Luser@</code>. This is especially true for searching
3543 message bodies since a larger amount of input has to be searched.
3545 Please note that string search is an exact case-sensitive search
3546 while a regular expression search with only lower-case letters performs
3547 a case-insensitive search.
3548 </p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="reference"></a>Chapter 8. Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="#sidebar-delim">3.150. sidebar_delim</a></span></dt><dt><span class="sect2"><a href="#sidebar-visible">3.151. sidebar_visible</a></span></dt><dt><span class="sect2"><a href="#sidebar-width">3.152. sidebar_width</a></span></dt><dt><span class="sect2"><a href="#pgp-use-gpg-agent">3.153. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="#crypt-verify-sig">3.154. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="#smime-is-default">3.155. smime_is_default</a></span></dt><dt><span class="sect2"><a href="#smime-ask-cert-label">3.156. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-use-default-key">3.157. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="#pgp-entry-format">3.158. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="#pgp-good-sign">3.159. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="#pgp-check-exit">3.160. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="#pgp-long-ids">3.161. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="#pgp-retainable-sigs">3.162. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="#pgp-autoinline">3.163. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="#pgp-replyinline">3.164. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="#pgp-show-unusable">3.165. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-as">3.166. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="#pgp-strict-enc">3.167. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="#pgp-timeout">3.168. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="#pgp-sort-keys">3.169. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-auto">3.170. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="#pgp-auto-decode">3.171. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-filename">3.172. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-description">3.173. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="#pgp-decode-command">3.174. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="#pgp-getkeys-command">3.175. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-command">3.176. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="#pgp-decrypt-command">3.177. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#pgp-clearsign-command">3.178. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-command">3.179. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-sign-command">3.180. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-only-command">3.181. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="#pgp-import-command">3.182. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="#pgp-export-command">3.183. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-key-command">3.184. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-secring-command">3.185. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-pubring-command">3.186. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="#forward-decrypt">3.187. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="#smime-timeout">3.188. smime_timeout</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-with">3.189. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="#smime-keys">3.190. smime_keys</a></span></dt><dt><span class="sect2"><a href="#smime-ca-location">3.191. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="#smime-certificates">3.192. smime_certificates</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-command">3.193. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-command">3.194. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-opaque-command">3.195. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-command">3.196. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-opaque-command">3.197. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-command">3.198. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-pk7out-command">3.199. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-command">3.200. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-signer-cert-command">3.201. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-import-cert-command">3.202. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-email-command">3.203. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="#smime-default-key">3.204. smime_default_key</a></span></dt><dt><span class="sect2"><a href="#ssl-client-cert">3.205. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="#ssl-force-tls">3.206. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="#ssl-starttls">3.207. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="#certificate-file">3.208. certificate_file</a></span></dt><dt><span class="sect2"><a href="#ssl-use-sslv3">3.209. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="#ssl-use-tlsv1">3.210. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="#ssl-min-dh-prime-bits">3.211. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="#ssl-ca-certificates-file">3.212. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="#pipe-split">3.213. pipe_split</a></span></dt><dt><span class="sect2"><a href="#pipe-decode">3.214. pipe_decode</a></span></dt><dt><span class="sect2"><a href="#pipe-sep">3.215. pipe_sep</a></span></dt><dt><span class="sect2"><a href="#pop-authenticators">3.216. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="#pop-auth-try-all">3.217. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="#pop-checkinterval">3.218. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="#pop-delete">3.219. pop_delete</a></span></dt><dt><span class="sect2"><a href="#pop-host">3.220. pop_host</a></span></dt><dt><span class="sect2"><a href="#pop-last">3.221. pop_last</a></span></dt><dt><span class="sect2"><a href="#pop-reconnect">3.222. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="#pop-user">3.223. pop_user</a></span></dt><dt><span class="sect2"><a href="#pop-pass">3.224. pop_pass</a></span></dt><dt><span class="sect2"><a href="#post-indent-string">3.225. post_indent_string</a></span></dt><dt><span class="sect2"><a href="#postpone">3.226. postpone</a></span></dt><dt><span class="sect2"><a href="#postponed">3.227. postponed</a></span></dt><dt><span class="sect2"><a href="#preconnect">3.228. preconnect</a></span></dt><dt><span class="sect2"><a href="#print">3.229. print</a></span></dt><dt><span class="sect2"><a href="#print-command">3.230. print_command</a></span></dt><dt><span class="sect2"><a href="#print-decode">3.231. print_decode</a></span></dt><dt><span class="sect2"><a href="#print-split">3.232. print_split</a></span></dt><dt><span class="sect2"><a href="#prompt-after">3.233. prompt_after</a></span></dt><dt><span class="sect2"><a href="#query-command">3.234. query_command</a></span></dt><dt><span class="sect2"><a href="#query-format">3.235. query_format</a></span></dt><dt><span class="sect2"><a href="#quit">3.236. quit</a></span></dt><dt><span class="sect2"><a href="#quote-regexp">3.237. quote_regexp</a></span></dt><dt><span class="sect2"><a href="#read-inc">3.238. read_inc</a></span></dt><dt><span class="sect2"><a href="#read-only">3.239. read_only</a></span></dt><dt><span class="sect2"><a href="#realname">3.240. realname</a></span></dt><dt><span class="sect2"><a href="#recall">3.241. recall</a></span></dt><dt><span class="sect2"><a href="#record">3.242. record</a></span></dt><dt><span class="sect2"><a href="#reply-regexp">3.243. reply_regexp</a></span></dt><dt><span class="sect2"><a href="#reply-self">3.244. reply_self</a></span></dt><dt><span class="sect2"><a href="#reply-to">3.245. reply_to</a></span></dt><dt><span class="sect2"><a href="#resolve">3.246. resolve</a></span></dt><dt><span class="sect2"><a href="#reverse-alias">3.247. reverse_alias</a></span></dt><dt><span class="sect2"><a href="#reverse-name">3.248. reverse_name</a></span></dt><dt><span class="sect2"><a href="#reverse-realname">3.249. reverse_realname</a></span></dt><dt><span class="sect2"><a href="#rfc2047-parameters">3.250. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="#save-address">3.251. save_address</a></span></dt><dt><span class="sect2"><a href="#save-empty">3.252. save_empty</a></span></dt><dt><span class="sect2"><a href="#save-history">3.253. save_history</a></span></dt><dt><span class="sect2"><a href="#save-name">3.254. save_name</a></span></dt><dt><span class="sect2"><a href="#score">3.255. score</a></span></dt><dt><span class="sect2"><a href="#score-threshold-delete">3.256. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="#score-threshold-flag">3.257. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="#score-threshold-read">3.258. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="#send-charset">3.259. send_charset</a></span></dt><dt><span class="sect2"><a href="#sendmail">3.260. sendmail</a></span></dt><dt><span class="sect2"><a href="#sendmail-wait">3.261. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="#shell">3.262. shell</a></span></dt><dt><span class="sect2"><a href="#sig-dashes">3.263. sig_dashes</a></span></dt><dt><span class="sect2"><a href="#sig-on-top">3.264. sig_on_top</a></span></dt><dt><span class="sect2"><a href="#signature">3.265. signature</a></span></dt><dt><span class="sect2"><a href="#simple-search">3.266. simple_search</a></span></dt><dt><span class="sect2"><a href="#smart-wrap">3.267. smart_wrap</a></span></dt><dt><span class="sect2"><a href="#smileys">3.268. smileys</a></span></dt><dt><span class="sect2"><a href="#sleep-time">3.269. sleep_time</a></span></dt><dt><span class="sect2"><a href="#smtp-authenticators">3.270. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="#smtp-pass">3.271. smtp_pass</a></span></dt><dt><span class="sect2"><a href="#smtp-url">3.272. smtp_url</a></span></dt><dt><span class="sect2"><a href="#sort">3.273. sort</a></span></dt><dt><span class="sect2"><a href="#sort-alias">3.274. sort_alias</a></span></dt><dt><span class="sect2"><a href="#sort-aux">3.275. sort_aux</a></span></dt><dt><span class="sect2"><a href="#sort-browser">3.276. sort_browser</a></span></dt><dt><span class="sect2"><a href="#sort-re">3.277. sort_re</a></span></dt><dt><span class="sect2"><a href="#spam-separator">3.278. spam_separator</a></span></dt><dt><span class="sect2"><a href="#spoolfile">3.279. spoolfile</a></span></dt><dt><span class="sect2"><a href="#status-chars">3.280. status_chars</a></span></dt><dt><span class="sect2"><a href="#status-format">3.281. status_format</a></span></dt><dt><span class="sect2"><a href="#status-on-top">3.282. status_on_top</a></span></dt><dt><span class="sect2"><a href="#strict-threads">3.283. strict_threads</a></span></dt><dt><span class="sect2"><a href="#suspend">3.284. suspend</a></span></dt><dt><span class="sect2"><a href="#text-flowed">3.285. text_flowed</a></span></dt><dt><span class="sect2"><a href="#thread-received">3.286. thread_received</a></span></dt><dt><span class="sect2"><a href="#thorough-search">3.287. thorough_search</a></span></dt><dt><span class="sect2"><a href="#tilde">3.288. tilde</a></span></dt><dt><span class="sect2"><a href="#time-inc">3.289. time_inc</a></span></dt><dt><span class="sect2"><a href="#timeout">3.290. timeout</a></span></dt><dt><span class="sect2"><a href="#tmpdir">3.291. tmpdir</a></span></dt><dt><span class="sect2"><a href="#to-chars">3.292. to_chars</a></span></dt><dt><span class="sect2"><a href="#trash">3.293. trash</a></span></dt><dt><span class="sect2"><a href="#tunnel">3.294. tunnel</a></span></dt><dt><span class="sect2"><a href="#use-8bitmime">3.295. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="#use-domain">3.296. use_domain</a></span></dt><dt><span class="sect2"><a href="#use-envelope-from">3.297. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="#use-from">3.298. use_from</a></span></dt><dt><span class="sect2"><a href="#use-idn">3.299. use_idn</a></span></dt><dt><span class="sect2"><a href="#use-ipv6">3.300. use_ipv6</a></span></dt><dt><span class="sect2"><a href="#user-agent">3.301. user_agent</a></span></dt><dt><span class="sect2"><a href="#visual">3.302. visual</a></span></dt><dt><span class="sect2"><a href="#wait-key">3.303. wait_key</a></span></dt><dt><span class="sect2"><a href="#weed">3.304. weed</a></span></dt><dt><span class="sect2"><a href="#wrap">3.305. wrap</a></span></dt><dt><span class="sect2"><a href="#wrap-search">3.306. wrap_search</a></span></dt><dt><span class="sect2"><a href="#wrapmargin">3.307. wrapmargin</a></span></dt><dt><span class="sect2"><a href="#write-inc">3.308. write_inc</a></span></dt><dt><span class="sect2"><a href="#write-bcc">3.309. write_bcc</a></span></dt><dt><span class="sect2"><a href="#xterm-icon">3.310. xterm_icon</a></span></dt><dt><span class="sect2"><a href="#xterm-set-titles">3.311. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="#xterm-title">3.312. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commandline"></a>1. Command line options</h2></div></div></div><p>
3549 Running <code class="literal">mutt</code> with no arguments will make Mutt attempt to read your spool
3550 mailbox. However, it is possible to read other mailboxes and
3551 to send messages from the command line as well.
3552 </p><div class="table"><a id="tab-commandline-options"></a><p class="title"><b>Table 8.1. Command line options</b></p><div class="table-contents"><table summary="Command line options" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>-A</td><td>expand an alias</td></tr><tr><td>-a</td><td>attach a file to a message</td></tr><tr><td>-b</td><td>specify a blind carbon-copy (BCC) address</td></tr><tr><td>-c</td><td>specify a carbon-copy (Cc) address</td></tr><tr><td>-D</td><td>print the value of all mutt variables to stdout</td></tr><tr><td>-e</td><td>specify a config command to be run after initialization files are read</td></tr><tr><td>-f</td><td>specify a mailbox to load</td></tr><tr><td>-F</td><td>specify an alternate file to read initialization commands</td></tr><tr><td>-h</td><td>print help on command line options</td></tr><tr><td>-H</td><td>specify a draft file from which to read a header and body</td></tr><tr><td>-i</td><td>specify a file to include in a message composition</td></tr><tr><td>-m</td><td>specify a default mailbox type</td></tr><tr><td>-n</td><td>do not read the system Muttrc</td></tr><tr><td>-p</td><td>recall a postponed message</td></tr><tr><td>-Q</td><td>query a configuration variable</td></tr><tr><td>-R</td><td>open mailbox in read-only mode</td></tr><tr><td>-s</td><td>specify a subject (enclose in quotes if it contains spaces)</td></tr><tr><td>-v</td><td>show version number and compile-time definitions</td></tr><tr><td>-x</td><td>simulate the mailx(1) compose mode</td></tr><tr><td>-y</td><td>show a menu containing the files specified by the mailboxes command</td></tr><tr><td>-z</td><td>exit immediately if there are no messages in the mailbox</td></tr><tr><td>-Z</td><td>open the first folder with new message,exit immediately if none</td></tr></tbody></table></div></div><br class="table-break" /><p>
3553 To read messages in a mailbox
3554 </p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-nz</code>] [<code class="option">-F</code>
3555 <em class="replaceable"><code>muttrc</code></em>
3556 ] [<code class="option">-m</code>
3557 <em class="replaceable"><code>type</code></em>
3558 ] [<code class="option">-f</code>
3559 <em class="replaceable"><code>mailbox</code></em>
3561 To compose a new message
3562 </p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-n</code>] [<code class="option">-F</code>
3563 <em class="replaceable"><code>muttrc</code></em>
3564 ] [<code class="option">-c</code>
3565 <em class="replaceable"><code>address</code></em>
3566 ] [<code class="option">-i</code>
3567 <em class="replaceable"><code>filename</code></em>
3568 ] [<code class="option">-s</code>
3569 <em class="replaceable"><code>subject</code></em>
3571 <code class="option">-a</code>
3572 <em class="replaceable"><code>file</code></em>
3576 <em class="replaceable"><code>address</code></em>
3578 Mutt also supports a “<span class="quote">batch</span>” mode to send prepared messages. Simply redirect
3579 input from the file you wish to send. For example,
3581 <code class="literal">mutt -s "data set for run #2" professor@bigschool.edu
3582 < ˜/run2.dat</code>
3584 This command will send a message to “<span class="quote">professor@bigschool.edu</span>” with a subject
3585 of “<span class="quote">data set for run #2</span>”. In the body of the message will be the contents
3586 of the file “<span class="quote">˜/run2.dat</span>”.
3588 All files passed with -a <span class="emphasis"><em>file</em></span> will be attached as a MIME
3589 part to the message. To attach several files, use “<span class="quote">--</span>” to separate files and
3590 recipient addresses: <code class="literal">mutt -a *.png -- some@one.org</code>
3591 </p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commands"></a>2. Configuration Commands</h2></div></div></div><p>
3592 The following are the commands understood by mutt.
3593 </p><div class="itemizedlist"><ul type="disc"><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#account-hook" title="6. Managing multiple accounts">account-hook</a></code>
3594 <em class="replaceable"><code>pattern</code></em>
3595 <em class="replaceable"><code>command</code></em>
3596 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alias" title="4. Defining/Using aliases">alias</a></code> [
3597 <code class="option">-group</code>
3598 <em class="replaceable"><code>name</code></em>
3600 <em class="replaceable"><code>key</code></em>
3602 <em class="replaceable"><code>address</code></em>
3604 <em class="replaceable"><code>address</code></em>
3605 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alias" title="4. Defining/Using aliases">unalias</a></code> [
3606 <code class="option">-group</code>
3607 <em class="replaceable"><code>name</code></em>
3609 <em class="replaceable"><code>*</code></em>
3611 <em class="replaceable"><code>key</code></em>
3612 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></code> [
3613 <code class="option">-group</code>
3614 <em class="replaceable"><code>name</code></em>
3616 <em class="replaceable"><code>regexp</code></em>
3618 <em class="replaceable"><code>regexp</code></em>
3619 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternates" title="11. Alternative addresses">unalternates</a></code> [
3620 <code class="option">-group</code>
3621 <em class="replaceable"><code>name</code></em>
3623 <em class="replaceable"><code>*</code></em>
3625 <em class="replaceable"><code>regexp</code></em>
3626 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternative-order" title="5. MIME Multipart/Alternative">alternative-order</a></code>
3627 <em class="replaceable"><code>mimetype</code></em>
3629 <em class="replaceable"><code>mimetype</code></em>
3630 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternative-order" title="5. MIME Multipart/Alternative">unalternative-order</a></code> {
3631 <em class="replaceable"><code>*</code></em>
3633 <em class="replaceable"><code>mimetype</code></em>
3634 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#auto-view" title="4. MIME Autoview">auto-view</a></code>
3635 <em class="replaceable"><code>mimetype</code></em>
3637 <em class="replaceable"><code>mimetype</code></em>
3638 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#auto-view" title="4. MIME Autoview">unauto-view</a></code> {
3639 <em class="replaceable"><code>*</code></em>
3641 <em class="replaceable"><code>mimetype</code></em>
3642 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#bind" title="5. Changing the default key bindings">bind</a></code>
3643 <em class="replaceable"><code>map</code></em>
3645 <em class="replaceable"><code>key</code></em>
3647 <em class="replaceable"><code>function</code></em>
3648 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#charset-hook" title="6. Defining aliases for character sets">charset-hook</a></code>
3649 <em class="replaceable"><code>alias</code></em>
3651 <em class="replaceable"><code>charset</code></em>
3652 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#charset-hook" title="6. Defining aliases for character sets">iconv-hook</a></code>
3653 <em class="replaceable"><code>charset</code></em>
3655 <em class="replaceable"><code>local-charset</code></em>
3656 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code>
3657 <em class="replaceable"><code>object</code></em>
3659 <em class="replaceable"><code>foreground</code></em>
3661 <em class="replaceable"><code>background</code></em>
3662 </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code> {
3663 <code class="option">header</code>
3665 <code class="option">body</code>
3667 <em class="replaceable"><code>foreground</code></em>
3669 <em class="replaceable"><code>background</code></em>
3671 <em class="replaceable"><code>regexp</code></em>
3672 </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code>
3673 <code class="option">index</code>
3675 <em class="replaceable"><code>foreground</code></em>
3677 <em class="replaceable"><code>background</code></em>
3679 <em class="replaceable"><code>pattern</code></em>
3680 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">uncolor</a></code>
3681 <code class="option">index</code>
3683 <em class="replaceable"><code>pattern</code></em>
3684 ... </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#exec" title="23. Executing functions">exec</a></code>
3685 <em class="replaceable"><code>function</code></em>
3687 <em class="replaceable"><code>function</code></em>
3688 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></code>
3689 <em class="replaceable"><code>[!]pattern</code></em>
3691 <em class="replaceable"><code>mailbox</code></em>
3692 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></code>
3693 <em class="replaceable"><code>[!]pattern</code></em>
3695 <em class="replaceable"><code>mailbox</code></em>
3696 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a></code>
3697 <em class="replaceable"><code>[!]regexp</code></em>
3699 <em class="replaceable"><code>command</code></em>
3700 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#addrgroup" title="3. Address groups">group</a></code> [
3701 <code class="option">-group</code>
3702 <em class="replaceable"><code>name</code></em>
3704 <code class="option">-rx</code>
3705 <em class="replaceable"><code>expr</code></em>
3707 <code class="option">-addr</code>
3708 <em class="replaceable"><code>expr</code></em>
3709 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#addrgroup" title="3. Address groups">ungroup</a></code> [
3710 <code class="option">-group</code>
3711 <em class="replaceable"><code>name</code></em>
3713 <em class="replaceable"><code>*</code></em>
3715 <code class="option">-rx</code>
3716 <em class="replaceable"><code>expr</code></em>
3718 <code class="option">-addr</code>
3719 <em class="replaceable"><code>expr</code></em>
3720 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#hdr-order">hdr_order</a></code>
3721 <em class="replaceable"><code>header</code></em>
3723 <em class="replaceable"><code>header</code></em>
3724 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#hdr-order">unhdr_order</a></code> {
3725 <em class="replaceable"><code>*</code></em>
3727 <em class="replaceable"><code>header</code></em>
3728 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#ignore" title="10. Message header display">ignore</a></code>
3729 <em class="replaceable"><code>pattern</code></em>
3731 <em class="replaceable"><code>pattern</code></em>
3732 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#ignore" title="10. Message header display">unignore</a></code> {
3733 <em class="replaceable"><code>*</code></em>
3735 <em class="replaceable"><code>pattern</code></em>
3736 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#lists" title="12. Mailing lists">lists</a></code> [
3737 <code class="option">-group</code>
3738 <em class="replaceable"><code>name</code></em>
3740 <em class="replaceable"><code>regexp</code></em>
3742 <em class="replaceable"><code>regexp</code></em>
3743 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#lists" title="12. Mailing lists">unlists</a></code> [
3744 <code class="option">-group</code>
3745 <em class="replaceable"><code>name</code></em>
3747 <em class="replaceable"><code>*</code></em>
3749 <em class="replaceable"><code>regexp</code></em>
3750 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#macro" title="8. Keyboard macros">macro</a></code>
3751 <em class="replaceable"><code>menu</code></em>
3753 <em class="replaceable"><code>key</code></em>
3755 <em class="replaceable"><code>sequence</code></em>
3757 <em class="replaceable"><code>description</code></em>
3758 ]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></code>
3759 <em class="replaceable"><code>mailbox</code></em>
3761 <em class="replaceable"><code>mailbox</code></em>
3762 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">unmailboxes</a></code> {
3763 <em class="replaceable"><code>*</code></em>
3765 <em class="replaceable"><code>mailbox</code></em>
3766 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></code>
3767 <em class="replaceable"><code>[!]pattern</code></em>
3769 <em class="replaceable"><code>mailbox</code></em>
3770 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a></code>
3771 <em class="replaceable"><code>[!]pattern</code></em>
3773 <em class="replaceable"><code>command</code></em>
3774 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mime-lookup" title="7. MIME Lookup">mime-lookup</a></code>
3775 <em class="replaceable"><code>mimetype</code></em>
3777 <em class="replaceable"><code>mimetype</code></em>
3778 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mime-lookup" title="7. MIME Lookup">unmime-lookup</a></code> {
3779 <em class="replaceable"><code>*</code></em>
3781 <em class="replaceable"><code>mimetype</code></em>
3782 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code>
3783 <em class="replaceable"><code>object</code></em>
3785 <em class="replaceable"><code>attribute</code></em>
3786 </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code> {
3787 <code class="option">header</code>
3789 <code class="option">body</code>
3791 <em class="replaceable"><code>attribute</code></em>
3793 <em class="replaceable"><code>regexp</code></em>
3794 </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code>
3795 <code class="option">index</code>
3797 <em class="replaceable"><code>attribute</code></em>
3799 <em class="replaceable"><code>pattern</code></em>
3800 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">unmono</a></code>
3801 <code class="option">index</code>
3803 <em class="replaceable"><code>*</code></em>
3805 <em class="replaceable"><code>pattern</code></em>
3806 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></code>
3807 <em class="replaceable"><code>string</code></em>
3808 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#my-hdr" title="15. User defined headers">unmy_hdr</a></code> {
3809 <em class="replaceable"><code>*</code></em>
3811 <em class="replaceable"><code>field</code></em>
3812 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#crypt-hook" title="21. Choosing the cryptographic key of the recipient">crypt-hook</a></code>
3813 <em class="replaceable"><code>pattern</code></em>
3815 <em class="replaceable"><code>keyid</code></em>
3816 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#push" title="22. Adding key sequences to the keyboard buffer">push</a></code>
3817 <em class="replaceable"><code>string</code></em>
3818 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">reset</a></code>
3819 <em class="replaceable"><code>variable</code></em>
3821 <em class="replaceable"><code>variable</code></em>
3822 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></code>
3823 <em class="replaceable"><code>[!]pattern</code></em>
3825 <em class="replaceable"><code>mailbox</code></em>
3826 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#score" title="3.255. score">score</a></code>
3827 <em class="replaceable"><code>pattern</code></em>
3829 <em class="replaceable"><code>value</code></em>
3830 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#score" title="3.255. score">unscore</a></code> {
3831 <em class="replaceable"><code>*</code></em>
3833 <em class="replaceable"><code>pattern</code></em>
3834 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#reply-hook">reply-hook</a></code>
3835 <em class="replaceable"><code>[!]pattern</code></em>
3837 <em class="replaceable"><code>command</code></em>
3838 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></code>
3839 <em class="replaceable"><code>[!]pattern</code></em>
3841 <em class="replaceable"><code>command</code></em>
3842 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#send2-hook">send2-hook</a></code>
3843 <em class="replaceable"><code>[!]pattern</code></em>
3845 <em class="replaceable"><code>command</code></em>
3846 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">set</a></code> {
3847 [ <code class="option">no</code> | <code class="option">inv</code> ]
3848 <em class="replaceable"><code>variable</code></em>
3850 <em class="replaceable"><code>variable=value</code></em>
3851 } [...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">unset</a></code>
3852 <em class="replaceable"><code>variable</code></em>
3854 <em class="replaceable"><code>variable</code></em>
3855 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#source" title="27. Reading initialization commands from another file">source</a></code>
3856 <em class="replaceable"><code>filename</code></em>
3857 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#spam" title="25. Spam detection">spam</a></code>
3858 <em class="replaceable"><code>pattern</code></em>
3860 <em class="replaceable"><code>format</code></em>
3861 </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#spam" title="25. Spam detection">nospam</a></code> {
3862 <em class="replaceable"><code>*</code></em>
3864 <em class="replaceable"><code>pattern</code></em>
3865 }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#subscribe">subscribe</a></code> [
3866 <code class="option">-group</code>
3867 <em class="replaceable"><code>name</code></em>
3869 <em class="replaceable"><code>regexp</code></em>
3871 <em class="replaceable"><code>regexp</code></em>
3872 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#subscribe">unsubscribe</a></code> [
3873 <code class="option">-group</code>
3874 <em class="replaceable"><code>name</code></em>
3876 <em class="replaceable"><code>*</code></em>
3878 <em class="replaceable"><code>regexp</code></em>
3879 ... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">toggle</a></code>
3880 <em class="replaceable"><code>variable</code></em>
3882 <em class="replaceable"><code>variable</code></em>
3883 ...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#unhook" title="29. Removing hooks">unhook</a></code> {
3884 <em class="replaceable"><code>*</code></em>
3886 <em class="replaceable"><code>hook-type</code></em>
3887 }</p></div></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="variables"></a>3. Configuration variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-nosubject"></a>3.1. abort_nosubject</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
3888 Default: ask-yes</p></div><p>
3889 If set to <span class="emphasis"><em>yes</em></span>, when composing messages and no subject is given
3890 at the subject prompt, composition will be aborted. If set to
3891 <span class="emphasis"><em>no</em></span>, composing messages with no subject given at the subject
3892 prompt will never be aborted.
3893 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-unmodified"></a>3.2. abort_unmodified</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
3894 Default: yes</p></div><p>
3895 If set to <span class="emphasis"><em>yes</em></span>, composition will automatically abort after
3896 editing the message body if no changes are made to the file (this
3897 check only happens after the <span class="emphasis"><em>first</em></span> edit of the file). When set
3898 to <span class="emphasis"><em>no</em></span>, composition will never be aborted.
3899 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-file"></a>3.3. alias_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
3900 Default: “<span class="quote"><code class="literal">˜/.muttrc</code></span>”</p></div><p>
3901 The default file in which to save aliases created by the
3902 <code class="literal"><a class="link" href="#create-alias"><create-alias></a></code> function. Entries added to this file are
3903 encoded in the character set specified by <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a> if it
3904 is <span class="emphasis"><em>set</em></span> or the current character set otherwise.
3906 <span class="bold"><strong>Note:</strong></span> Mutt will not automatically source this file; you must
3907 explicitly use the “<span class="quote"><a class="link" href="#source" title="27. Reading initialization commands from another file">source</a></span>” command for it to be executed in case
3908 this option points to a dedicated alias file.
3910 The default for this option is the currently used muttrc file, or
3911 “<span class="quote">˜/.muttrc</span>” if no user muttrc was found.
3912 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-format"></a>3.4. alias_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
3913 Default: “<span class="quote"><code class="literal">%4n %2f %t %-10a %r</code></span>”</p></div><p>
3914 Specifies the format of the data displayed for the “<span class="quote"><a class="link" href="#alias" title="4. Defining/Using aliases">alias</a></span>” menu. The
3915 following <code class="literal">printf(3)</code>-style sequences are available:
3917 </p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>alias name
3918 </p></dd><dt><span class="term">%f </span></dt><dd><p>flags - currently, a “<span class="quote">d</span>” for an alias marked for deletion
3919 </p></dd><dt><span class="term">%n </span></dt><dd><p>index number
3920 </p></dd><dt><span class="term">%r </span></dt><dd><p>address which alias expands to
3921 </p></dd><dt><span class="term">%t </span></dt><dd><p>character which indicates if the alias is tagged for inclusion
3922 </p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-8bit"></a>3.5. allow_8bit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
3923 Default: yes</p></div><p>
3924 Controls whether 8-bit data is converted to 7-bit using either Quoted-
3925 Printable or Base64 encoding when sending mail.
3926 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-ansi"></a>3.6. allow_ansi</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
3927 Default: no</p></div><p>
3928 Controls whether ANSI color codes in messages (and color tags in
3929 rich text messages) are to be interpreted.
3930 Messages containing these codes are rare, but if this option is <span class="emphasis"><em>set</em></span>,
3931 their text will be colored accordingly. Note that this may override
3932 your color choices, and even present a security problem, since a
3933 message could include a line like
3935 </p><pre class="screen">
3936 [-- PGP output follows ...
3939 and give it the same color as your attachment color (see also
3940 <a class="link" href="#crypt-timestamp" title="3.149. crypt_timestamp">$crypt_timestamp</a>).
3941 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="arrow-cursor"></a>3.7. arrow_cursor</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
3942 Default: no</p></div><p>
3943 When <span class="emphasis"><em>set</em></span>, an arrow (“<span class="quote">-></span>”) will be used to indicate the current entry
3944 in menus instead of highlighting the whole line. On slow network or modem
3945 links this will make response faster because there is less that has to
3946 be redrawn on the screen when moving to the next or previous entries
3948 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ascii-chars"></a>3.8. ascii_chars</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
3949 Default: no</p></div><p>
3950 If <span class="emphasis"><em>set</em></span>, Mutt will use plain ASCII characters when displaying thread
3951 and attachment trees, instead of the default <span class="emphasis"><em>ACS</em></span> characters.
3952 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askbcc"></a>3.9. askbcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
3953 Default: no</p></div><p>
3954 If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
3955 before editing an outgoing message.
3956 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askcc"></a>3.10. askcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
3957 Default: no</p></div><p>
3958 If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for carbon-copy (Cc) recipients before
3959 editing the body of an outgoing message.
3960 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="assumed-charset"></a>3.11. assumed_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
3961 Default: (empty)</p></div><p>
3962 This variable is a colon-separated list of character encoding
3963 schemes for messages without character encoding indication.
3964 Header field values and message body content without character encoding
3965 indication would be assumed that they are written in one of this list.
3966 By default, all the header fields and message body without any charset
3967 indication are assumed to be in “<span class="quote">us-ascii</span>”.
3969 For example, Japanese users might prefer this:
3971 </p><pre class="screen">
3972 set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
3975 However, only the first content is valid for the message body.
3976 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-charset"></a>3.12. attach_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
3977 Default: (empty)</p></div><p>
3978 This variable is a colon-separated list of character encoding
3979 schemes for text file attachments. Mutt uses this setting to guess
3980 which encoding files being attached are encoded in to convert them to
3981 a proper character set given in <a class="link" href="#send-charset" title="3.259. send_charset">$send_charset</a>.
3983 If <span class="emphasis"><em>unset</em></span>, the value of <a class="link" href="#charset" title="3.25. charset">$charset</a> will be used instead.
3984 For example, the following configuration would work for Japanese
3987 </p><pre class="screen">
3988 set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
3991 Note: for Japanese users, “<span class="quote">iso-2022-*</span>” must be put at the head
3992 of the value as shown above if included.
3993 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-format"></a>3.13. attach_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
3994 Default: “<span class="quote"><code class="literal">%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </code></span>”</p></div><p>
3995 This variable describes the format of the “<span class="quote">attachment</span>” menu. The
3996 following <code class="literal">printf(3)</code>-style sequences are understood:
3998 </p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>charset
3999 </p></dd><dt><span class="term">%c </span></dt><dd><p>requires charset conversion (“<span class="quote">n</span>” or “<span class="quote">c</span>”)
4000 </p></dd><dt><span class="term">%D </span></dt><dd><p>deleted flag
4001 </p></dd><dt><span class="term">%d </span></dt><dd><p>description
4002 </p></dd><dt><span class="term">%e </span></dt><dd><p>MIME content-transfer-encoding
4003 </p></dd><dt><span class="term">%f </span></dt><dd><p>filename
4004 </p></dd><dt><span class="term">%I </span></dt><dd><p>disposition (“<span class="quote">I</span>” for inline, “<span class="quote">A</span>” for attachment)
4005 </p></dd><dt><span class="term">%m </span></dt><dd><p>major MIME type
4006 </p></dd><dt><span class="term">%M </span></dt><dd><p>MIME subtype
4007 </p></dd><dt><span class="term">%n </span></dt><dd><p>attachment number
4008 </p></dd><dt><span class="term">%Q </span></dt><dd><p>“<span class="quote">Q</span>”, if MIME part qualifies for attachment counting
4009 </p></dd><dt><span class="term">%s </span></dt><dd><p>size
4010 </p></dd><dt><span class="term">%t </span></dt><dd><p>tagged flag
4011 </p></dd><dt><span class="term">%T </span></dt><dd><p>graphic tree characters
4012 </p></dd><dt><span class="term">%u </span></dt><dd><p>unlink (=to delete) flag
4013 </p></dd><dt><span class="term">%X </span></dt><dd><p>number of qualifying MIME parts in this part and its children
4014 (please see the “<span class="quote"><a class="link" href="#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
4015 </p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
4016 </p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
4017 </p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
4018 </p></dd></dl></div><p>
4019 For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
4020 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-sep"></a>3.14. attach_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4021 Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
4022 The separator to add between attachments when operating (saving,
4023 printing, piping, etc) on a list of tagged attachments.
4024 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-split"></a>3.15. attach_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4025 Default: yes</p></div><p>
4026 If this variable is <span class="emphasis"><em>unset</em></span>, when operating (saving, printing, piping,
4027 etc) on a list of tagged attachments, Mutt will concatenate the
4028 attachments and will operate on them as a single attachment. The
4029 <a class="link" href="#attach-sep" title="3.14. attach_sep">$attach_sep</a> separator is added after each attachment. When <span class="emphasis"><em>set</em></span>,
4030 Mutt will operate on the attachments one by one.
4031 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attribution"></a>3.16. attribution</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4032 Default: “<span class="quote"><code class="literal">On %d, %n wrote:</code></span>”</p></div><p>
4033 This is the string that will precede a message which has been included
4034 in a reply. For a full listing of defined <code class="literal">printf(3)</code>-like sequences see
4035 the section on <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
4036 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="autoedit"></a>3.17. autoedit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4037 Default: no</p></div><p>
4038 When <span class="emphasis"><em>set</em></span> along with <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>, Mutt will skip the initial
4039 send-menu (prompting for subject and recipients) and allow you to
4040 immediately begin editing the body of your
4041 message. The send-menu may still be accessed once you have finished
4042 editing the body of your message.
4044 Also see <a class="link" href="#fast-reply" title="3.55. fast_reply">$fast_reply</a>.
4045 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="auto-tag"></a>3.18. auto_tag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4046 Default: no</p></div><p>
4047 When <span class="emphasis"><em>set</em></span>, functions in the <span class="emphasis"><em>index</em></span> menu which affect a message
4048 will be applied to all tagged messages (if there are any). When
4049 unset, you must first use the <code class="literal"><tag-prefix></code> function (bound to “<span class="quote">;</span>”
4050 by default) to make the next function apply to all tagged messages.
4051 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep"></a>3.19. beep</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4052 Default: yes</p></div><p>
4053 When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep when an error occurs.
4054 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep-new"></a>3.20. beep_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4055 Default: no</p></div><p>
4056 When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep whenever it prints a message
4057 notifying you of new mail. This is independent of the setting of the
4058 <a class="link" href="#beep" title="3.19. beep">$beep</a> variable.
4059 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce"></a>3.21. bounce</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4060 Default: ask-yes</p></div><p>
4061 Controls whether you will be asked to confirm bouncing messages.
4062 If set to <span class="emphasis"><em>yes</em></span> you don't get asked if you want to bounce a
4063 message. Setting this variable to <span class="emphasis"><em>no</em></span> is not generally useful,
4064 and thus not recommended, because you are unable to bounce messages.
4065 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce-delivered"></a>3.22. bounce_delivered</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4066 Default: yes</p></div><p>
4067 When this variable is <span class="emphasis"><em>set</em></span>, mutt will include Delivered-To headers when
4068 bouncing messages. Postfix users may wish to <span class="emphasis"><em>unset</em></span> this variable.
4070 <span class="bold"><strong>Note:</strong></span> On Debian systems, this option is unset by default in
4072 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="braille-friendly"></a>3.23. braille_friendly</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4073 Default: no</p></div><p>
4074 When this variable is <span class="emphasis"><em>set</em></span>, mutt will place the cursor at the beginning
4075 of the current line in menus, even when the <a class="link" href="#arrow-cursor" title="3.7. arrow_cursor">$arrow_cursor</a> variable
4076 is <span class="emphasis"><em>unset</em></span>, making it easier for blind persons using Braille displays to
4077 follow these menus. The option is <span class="emphasis"><em>unset</em></span> by default because many
4078 visual terminals don't permit making the cursor invisible.
4079 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-mbox-size"></a>3.24. check_mbox_size</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4080 Default: no</p></div><p>
4081 When this variable is <span class="emphasis"><em>set</em></span>, mutt will use file size attribute instead of
4082 access time when checking for new mail in mbox and mmdf folders.
4084 This variable is <span class="emphasis"><em>unset</em></span> by default and should only be enabled when
4085 new mail detection for these folder types is unreliable or doesn't work.
4087 Note that enabling this variable should happen before any “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
4088 directives occur in configuration files regarding mbox or mmdf folders
4089 because mutt needs to determine the initial new mail status of such a
4090 mailbox by performing a fast mailbox scan when it is defined.
4091 Afterwards the new mail status is tracked by file size changes.
4092 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="charset"></a>3.25. charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4093 Default: (empty)</p></div><p>
4094 Character set your terminal uses to display and enter textual data.
4095 It is also the fallback for <a class="link" href="#send-charset" title="3.259. send_charset">$send_charset</a>.
4097 Upon startup Mutt tries to derive this value from environment variables
4098 such as <code class="literal">$LC_CTYPE</code> or <code class="literal">$LANG</code>.
4100 <span class="bold"><strong>Note:</strong></span> It should only be set in case Mutt isn't abled to determine the
4101 character set used correctly.
4102 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-new"></a>3.26. check_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4103 Default: yes</p></div><p>
4104 <span class="bold"><strong>Note:</strong></span> this option only affects <span class="emphasis"><em>maildir</em></span> and <span class="emphasis"><em>MH</em></span> style
4107 When <span class="emphasis"><em>set</em></span>, Mutt will check for new mail delivered while the
4108 mailbox is open. Especially with MH mailboxes, this operation can
4109 take quite some time since it involves scanning the directory and
4110 checking each file to see if it has already been looked at. If
4111 this variable is <span class="emphasis"><em>unset</em></span>, no check for new mail is performed
4112 while the mailbox is open.
4113 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="collapse-unread"></a>3.27. collapse_unread</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4114 Default: yes</p></div><p>
4115 When <span class="emphasis"><em>unset</em></span>, Mutt will not collapse a thread if it contains any
4117 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="uncollapse-jump"></a>3.28. uncollapse_jump</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4118 Default: no</p></div><p>
4119 When <span class="emphasis"><em>set</em></span>, Mutt will jump to the next unread message, if any,
4120 when the current thread is <span class="emphasis"><em>un</em></span>collapsed.
4121 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-format"></a>3.29. compose_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4122 Default: “<span class="quote"><code class="literal">-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</code></span>”</p></div><p>
4123 Controls the format of the status line displayed in the “<span class="quote">compose</span>”
4124 menu. This string is similar to <a class="link" href="#status-format" title="3.281. status_format">$status_format</a>, but has its own
4125 set of <code class="literal">printf(3)</code>-like sequences:
4127 </p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>total number of attachments
4128 </p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
4129 </p></dd><dt><span class="term">%l </span></dt><dd><p>approximate size (in bytes) of the current message
4130 </p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
4131 </p></dd></dl></div><p>
4132 See the text describing the <a class="link" href="#status-format" title="3.281. status_format">$status_format</a> option for more
4133 information on how to set <a class="link" href="#compose-format" title="3.29. compose_format">$compose_format</a>.
4134 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="config-charset"></a>3.30. config_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4135 Default: (empty)</p></div><p>
4136 When defined, Mutt will recode commands in rc files from this
4137 encoding to the current character set as specified by <a class="link" href="#charset" title="3.25. charset">$charset</a>
4138 and aliases written to <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> from the current character set.
4140 Please note that if setting <a class="link" href="#charset" title="3.25. charset">$charset</a> it must be done before
4141 setting <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a>.
4143 Recoding should be avoided as it may render unconvertable
4144 characters as question marks which can lead to undesired
4145 side effects (for example in regular expressions).
4146 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmappend"></a>3.31. confirmappend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4147 Default: yes</p></div><p>
4148 When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when appending messages to
4149 an existing mailbox.
4150 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmcreate"></a>3.32. confirmcreate</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4151 Default: yes</p></div><p>
4152 When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when saving messages to a
4153 mailbox which does not yet exist before creating it.
4154 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="connect-timeout"></a>3.33. connect_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4155 Default: 30</p></div><p>
4156 Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
4157 many seconds if the connection is not able to be established. A negative
4158 value causes Mutt to wait indefinitely for the connection attempt to succeed.
4159 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="content-type"></a>3.34. content_type</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4160 Default: “<span class="quote"><code class="literal">text/plain</code></span>”</p></div><p>
4161 Sets the default Content-Type for the body of newly composed messages.
4162 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="copy"></a>3.35. copy</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4163 Default: yes</p></div><p>
4164 This variable controls whether or not copies of your outgoing messages
4165 will be saved for later references. Also see <a class="link" href="#record" title="3.242. record">$record</a>,
4166 <a class="link" href="#save-name" title="3.254. save_name">$save_name</a>, <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> and “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>”.
4167 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-gpgme"></a>3.36. crypt_use_gpgme</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4168 Default: no</p></div><p>
4169 This variable controls the use of the GPGME-enabled crypto backends.
4170 If it is <span class="emphasis"><em>set</em></span> and Mutt was built with gpgme support, the gpgme code for
4171 S/MIME and PGP will be used instead of the classic code. Note that
4172 you need to set this option in .muttrc; it won't have any effect when
4174 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-pka"></a>3.37. crypt_use_pka</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4175 Default: no</p></div><p>
4176 Controls whether mutt uses PKA
4177 (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
4178 verification (only supported by the GPGME backend).
4179 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autopgp"></a>3.38. crypt_autopgp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4180 Default: yes</p></div><p>
4181 This variable controls whether or not mutt may automatically enable
4182 PGP encryption/signing for messages. See also <a class="link" href="#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
4183 <a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
4184 <a class="link" href="#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a>.
4185 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosmime"></a>3.39. crypt_autosmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4186 Default: yes</p></div><p>
4187 This variable controls whether or not mutt may automatically enable
4188 S/MIME encryption/signing for messages. See also <a class="link" href="#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
4189 <a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
4190 <a class="link" href="#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a>.
4191 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-format"></a>3.40. date_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4192 Default: “<span class="quote"><code class="literal">!%a, %b %d, %Y at %I:%M:%S%p %Z</code></span>”</p></div><p>
4193 This variable controls the format of the date printed by the “<span class="quote">%d</span>”
4194 sequence in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>. This is passed to the <code class="literal">strftime(3)</code>
4195 function to process the date, see the man page for the proper syntax.
4197 Unless the first character in the string is a bang (“<span class="quote">!</span>”), the month
4198 and week day names are expanded according to the locale specified in
4199 the variable <a class="link" href="#locale" title="3.104. locale">$locale</a>. If the first character in the string is a
4200 bang, the bang is discarded, and the month and week day names in the
4201 rest of the string are expanded in the <span class="emphasis"><em>C</em></span> locale (that is in US
4203 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="default-hook"></a>3.41. default_hook</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4204 Default: “<span class="quote"><code class="literal">˜f %s !˜P | (˜P ˜C %s)</code></span>”</p></div><p>
4205 This variable controls how “<span class="quote"><a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a></span>”, “<span class="quote"><a class="link" href="#reply-hook">reply-hook</a></span>”, “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”,
4206 “<span class="quote"><a class="link" href="#send2-hook">send2-hook</a></span>”, “<span class="quote"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, and “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” will
4207 be interpreted if they are specified with only a simple regexp,
4208 instead of a matching pattern. The hooks are expanded when they are
4209 declared, so a hook will be interpreted according to the value of this
4210 variable at the time the hook is declared.
4212 The default value matches
4213 if the message is either from a user matching the regular expression
4214 given, or if it is from you (if the from address matches
4215 “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”) and is to or cc'ed to a user matching the given
4217 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete"></a>3.42. delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4218 Default: ask-yes</p></div><p>
4219 Controls whether or not messages are really deleted when closing or
4220 synchronizing a mailbox. If set to <span class="emphasis"><em>yes</em></span>, messages marked for
4221 deleting will automatically be purged without prompting. If set to
4222 <span class="emphasis"><em>no</em></span>, messages marked for deletion will be kept in the mailbox.
4223 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete-untag"></a>3.43. delete_untag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4224 Default: yes</p></div><p>
4225 If this option is <span class="emphasis"><em>set</em></span>, mutt will untag messages when marking them
4226 for deletion. This applies when you either explicitly delete a message,
4227 or when you save it to another folder.
4228 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="digest-collapse"></a>3.44. digest_collapse</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4229 Default: yes</p></div><p>
4230 If this option is <span class="emphasis"><em>set</em></span>, mutt's received-attachments menu will not show the subparts of
4231 individual messages in a multipart/digest. To see these subparts, press “<span class="quote">v</span>” on that menu.
4232 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="display-filter"></a>3.45. display_filter</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4233 Default: (empty)</p></div><p>
4234 When set, specifies a command used to filter messages. When a message
4235 is viewed it is passed as standard input to <a class="link" href="#display-filter" title="3.45. display_filter">$display_filter</a>, and the
4236 filtered message is read from the standard output.
4237 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dotlock-program"></a>3.46. dotlock_program</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4238 Default: “<span class="quote"><code class="literal">/usr/bin/mutt_dotlock</code></span>”</p></div><p>
4239 Contains the path of the <code class="literal">mutt_dotlock(8)</code> binary to be used by
4241 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-notify"></a>3.47. dsn_notify</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4242 Default: (empty)</p></div><p>
4243 This variable sets the request for when notification is returned. The
4244 string consists of a comma separated list (no spaces!) of one or more
4245 of the following: <span class="emphasis"><em>never</em></span>, to never request notification,
4246 <span class="emphasis"><em>failure</em></span>, to request notification on transmission failure,
4247 <span class="emphasis"><em>delay</em></span>, to be notified of message delays, <span class="emphasis"><em>success</em></span>, to be
4248 notified of successful transmission.
4252 </p><pre class="screen">
4253 set dsn_notify="failure,delay"
4256 <span class="bold"><strong>Note:</strong></span> when using <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> for delivery, you should not enable
4257 this unless you are either using Sendmail 8.8.x or greater or a MTA
4258 providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-N</code> option
4259 for DSN. For SMTP delivery, DSN support is autodetected so that it
4260 depends on the server whether DSN will be used or not.
4261 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-return"></a>3.48. dsn_return</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4262 Default: (empty)</p></div><p>
4263 This variable controls how much of your message is returned in DSN
4264 messages. It may be set to either <span class="emphasis"><em>hdrs</em></span> to return just the
4265 message header, or <span class="emphasis"><em>full</em></span> to return the full message.
4269 </p><pre class="screen">
4273 <span class="bold"><strong>Note:</strong></span> when using <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> for delivery, you should not enable
4274 this unless you are either using Sendmail 8.8.x or greater or a MTA
4275 providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-R</code> option
4276 for DSN. For SMTP delivery, DSN support is autodetected so that it
4277 depends on the server whether DSN will be used or not.
4278 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="duplicate-threads"></a>3.49. duplicate_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4279 Default: yes</p></div><p>
4280 This variable controls whether mutt, when <a class="link" href="#sort" title="3.273. sort">$sort</a> is set to <span class="emphasis"><em>threads</em></span>, threads
4281 messages with the same Message-Id together. If it is <span class="emphasis"><em>set</em></span>, it will indicate
4282 that it thinks they are duplicates of each other with an equals sign
4284 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-headers"></a>3.50. edit_headers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4285 Default: no</p></div><p>
4286 This option allows you to edit the header of your outgoing messages
4287 along with the body of your message.
4289 <span class="bold"><strong>Note</strong></span> that changes made to the References: and Date: headers are
4290 ignored for interoperability reasons.
4291 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor"></a>3.51. editor</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4292 Default: (empty)</p></div><p>
4293 This variable specifies which editor is used by mutt.
4294 It defaults to the value of the <code class="literal">$VISUAL</code>, or <code class="literal">$EDITOR</code>, environment
4295 variable, or to the string “<span class="quote">/usr/bin/editor</span>” if neither of those are set.
4296 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="encode-from"></a>3.52. encode_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4297 Default: no</p></div><p>
4298 When <span class="emphasis"><em>set</em></span>, mutt will quoted-printable encode messages when
4299 they contain the string “<span class="quote">From </span>” (note the trailing space) in the beginning of a line.
4300 This is useful to avoid the tampering certain mail delivery and transport
4301 agents tend to do with messages (in order to prevent tools from
4302 misinterpreting the line as a mbox message separator).
4303 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="envelope-from-address"></a>3.53. envelope_from_address</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
4304 Default: (empty)</p></div><p>
4305 Manually sets the <span class="emphasis"><em>envelope</em></span> sender for outgoing messages.
4306 This value is ignored if <a class="link" href="#use-envelope-from" title="3.297. use_envelope_from">$use_envelope_from</a> is <span class="emphasis"><em>unset</em></span>.
4307 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="escape"></a>3.54. escape</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4308 Default: “<span class="quote"><code class="literal">˜</code></span>”</p></div><p>
4309 Escape character to use for functions in the builtin editor.
4310 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fast-reply"></a>3.55. fast_reply</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4311 Default: no</p></div><p>
4312 When <span class="emphasis"><em>set</em></span>, the initial prompt for recipients and subject are skipped
4313 when replying to messages, and the initial prompt for subject is
4314 skipped when forwarding messages.
4316 <span class="bold"><strong>Note:</strong></span> this variable has no effect when the <a class="link" href="#autoedit" title="3.17. autoedit">$autoedit</a>
4317 variable is <span class="emphasis"><em>set</em></span>.
4318 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-attach"></a>3.56. fcc_attach</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4319 Default: yes</p></div><p>
4320 This variable controls whether or not attachments on outgoing messages
4321 are saved along with the main body of your message.
4322 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-clear"></a>3.57. fcc_clear</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4323 Default: no</p></div><p>
4324 When this variable is <span class="emphasis"><em>set</em></span>, FCCs will be stored unencrypted and
4325 unsigned, even when the actual message is encrypted and/or
4328 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder"></a>3.58. folder</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4329 Default: “<span class="quote"><code class="literal">˜/Mail</code></span>”</p></div><p>
4330 Specifies the default location of your mailboxes. A “<span class="quote">+</span>” or “<span class="quote">=</span>” at the
4331 beginning of a pathname will be expanded to the value of this
4332 variable. Note that if you change this variable (from the default)
4333 value you need to make sure that the assignment occurs <span class="emphasis"><em>before</em></span>
4334 you use “<span class="quote">+</span>” or “<span class="quote">=</span>” for any other variables since expansion takes place
4335 when handling the “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>” command.
4336 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder-format"></a>3.59. folder_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4337 Default: “<span class="quote"><code class="literal">%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</code></span>”</p></div><p>
4338 This variable allows you to customize the file browser display to your
4339 personal taste. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but has
4340 its own set of <code class="literal">printf(3)</code>-like sequences:
4342 </p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>current file number
4343 </p></dd><dt><span class="term">%d </span></dt><dd><p>date/time folder was last modified
4344 </p></dd><dt><span class="term">%f </span></dt><dd><p>filename
4345 </p></dd><dt><span class="term">%F </span></dt><dd><p>file permissions
4346 </p></dd><dt><span class="term">%g </span></dt><dd><p>group name (or numeric gid, if missing)
4347 </p></dd><dt><span class="term">%l </span></dt><dd><p>number of hard links
4348 </p></dd><dt><span class="term">%N </span></dt><dd><p>N if folder has new mail, blank otherwise
4349 </p></dd><dt><span class="term">%s </span></dt><dd><p>size in bytes
4350 </p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if the file is tagged, blank otherwise
4351 </p></dd><dt><span class="term">%u </span></dt><dd><p>owner name (or numeric uid, if missing)
4352 </p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
4353 </p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
4354 </p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
4355 </p></dd></dl></div><p>
4356 For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
4357 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="followup-to"></a>3.60. followup_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4358 Default: yes</p></div><p>
4359 Controls whether or not the “<span class="quote">Mail-Followup-To:</span>” header field is
4360 generated when sending mail. When <span class="emphasis"><em>set</em></span>, Mutt will generate this
4361 field when you are replying to a known mailing list, specified with
4362 the “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” or “<span class="quote"><a class="link" href="#lists" title="12. Mailing lists">lists</a></span>” commands.
4364 This field has two purposes. First, preventing you from
4365 receiving duplicate copies of replies to messages which you send
4366 to mailing lists, and second, ensuring that you do get a reply
4367 separately for any messages sent to known lists to which you are
4370 The header will contain only the list's address
4371 for subscribed lists, and both the list address and your own
4372 email address for unsubscribed lists. Without this header, a
4373 group reply to your message sent to a subscribed list will be
4374 sent to both the list and your address, resulting in two copies
4375 of the same email for you.
4376 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="force-name"></a>3.61. force_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4377 Default: no</p></div><p>
4378 This variable is similar to <a class="link" href="#save-name" title="3.254. save_name">$save_name</a>, except that Mutt will
4379 store a copy of your outgoing message by the username of the address
4380 you are sending to even if that mailbox does not exist.
4382 Also see the <a class="link" href="#record" title="3.242. record">$record</a> variable.
4383 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decode"></a>3.62. forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4384 Default: yes</p></div><p>
4385 Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
4386 forwarding a message. The message header is also RFC2047 decoded.
4387 This variable is only used, if <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>,
4388 otherwise <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is used instead.
4389 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-edit"></a>3.63. forward_edit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4390 Default: yes</p></div><p>
4391 This quadoption controls whether or not the user is automatically
4392 placed in the editor when forwarding messages. For those who always want
4393 to forward with no modification, use a setting of “<span class="quote">no</span>”.
4394 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-format"></a>3.64. forward_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4395 Default: “<span class="quote"><code class="literal">[%a: %s]</code></span>”</p></div><p>
4396 This variable controls the default subject when forwarding a message.
4397 It uses the same format sequences as the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable.
4398 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-quote"></a>3.65. forward_quote</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4399 Default: no</p></div><p>
4400 When <span class="emphasis"><em>set</em></span>, forwarded messages included in the main body of the
4401 message (when <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>) will be quoted using
4402 <a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a>.
4403 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="from"></a>3.66. from</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
4404 Default: (empty)</p></div><p>
4405 When <span class="emphasis"><em>set</em></span>, this variable contains a default from address. It
4406 can be overridden using “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>” (including from a “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”) and
4407 <a class="link" href="#reverse-name" title="3.248. reverse_name">$reverse_name</a>. This variable is ignored if <a class="link" href="#use-from" title="3.298. use_from">$use_from</a> is <span class="emphasis"><em>unset</em></span>.
4409 This setting defaults to the contents of the environment variable <code class="literal">$EMAIL</code>.
4410 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="gecos-mask"></a>3.67. gecos_mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
4411 Default: “<span class="quote"><code class="literal">^[^,]*</code></span>”</p></div><p>
4412 A regular expression used by mutt to parse the GECOS field of a password
4413 entry when expanding the alias. The default value
4414 will return the string up to the first “<span class="quote">,</span>” encountered.
4415 If the GECOS field contains a string like “<span class="quote">lastname, firstname</span>” then you
4416 should set it to “<span class="quote"><code class="literal">.*</code></span>”.
4418 This can be useful if you see the following behavior: you address an e-mail
4419 to user ID “<span class="quote">stevef</span>” whose full name is “<span class="quote">Steve Franklin</span>”. If mutt expands
4420 “<span class="quote">stevef</span>” to “<span class="quote">"Franklin" stevef@foo.bar</span>” then you should set the <a class="link" href="#gecos-mask" title="3.67. gecos_mask">$gecos_mask</a> to
4421 a regular expression that will match the whole name so mutt will expand
4422 “<span class="quote">Franklin</span>” to “<span class="quote">Franklin, Steve</span>”.
4423 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hdrs"></a>3.68. hdrs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4424 Default: yes</p></div><p>
4425 When <span class="emphasis"><em>unset</em></span>, the header fields normally added by the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
4426 command are not created. This variable <span class="emphasis"><em>must</em></span> be unset before
4427 composing a new message or replying in order to take effect. If <span class="emphasis"><em>set</em></span>,
4428 the user defined header fields are added to every new message.
4429 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header"></a>3.69. header</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4430 Default: no</p></div><p>
4431 When <span class="emphasis"><em>set</em></span>, this variable causes Mutt to include the header
4432 of the message you are replying to into the edit buffer.
4433 The <a class="link" href="#weed" title="3.304. weed">$weed</a> setting applies.
4434 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="help"></a>3.70. help</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4435 Default: yes</p></div><p>
4436 When <span class="emphasis"><em>set</em></span>, help lines describing the bindings for the major functions
4437 provided by each menu are displayed on the first line of the screen.
4439 <span class="bold"><strong>Note:</strong></span> The binding will not be displayed correctly if the
4440 function is bound to a sequence rather than a single keystroke. Also,
4441 the help line may not be updated if a binding is changed while Mutt is
4442 running. Since this variable is primarily aimed at new users, neither
4443 of these should present a major problem.
4444 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hidden-host"></a>3.71. hidden_host</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4445 Default: no</p></div><p>
4446 When <span class="emphasis"><em>set</em></span>, mutt will skip the host name part of <a class="link" href="#hostname" title="3.80. hostname">$hostname</a> variable
4447 when adding the domain part to addresses. This variable does not
4448 affect the generation of Message-IDs, and it will not lead to the
4449 cut-off of first-level domains.
4450 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-limited"></a>3.72. hide_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4451 Default: no</p></div><p>
4452 When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
4453 by limiting, in the thread tree.
4454 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-missing"></a>3.73. hide_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4455 Default: yes</p></div><p>
4456 When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages in the
4458 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-thread-subject"></a>3.74. hide_thread_subject</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4459 Default: yes</p></div><p>
4460 When <span class="emphasis"><em>set</em></span>, mutt will not show the subject of messages in the thread
4461 tree that have the same subject as their parent or closest previously
4463 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-limited"></a>3.75. hide_top_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4464 Default: no</p></div><p>
4465 When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
4466 by limiting, at the top of threads in the thread tree. Note that when
4467 <a class="link" href="#hide-limited" title="3.72. hide_limited">$hide_limited</a> is <span class="emphasis"><em>set</em></span>, this option will have no effect.
4468 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-missing"></a>3.76. hide_top_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4469 Default: yes</p></div><p>
4470 When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages at the
4471 top of threads in the thread tree. Note that when <a class="link" href="#hide-missing" title="3.73. hide_missing">$hide_missing</a> is
4472 <span class="emphasis"><em>set</em></span>, this option will have no effect.
4473 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history"></a>3.77. history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4474 Default: 10</p></div><p>
4475 This variable controls the size (in number of strings remembered) of
4476 the string history buffer per category. The buffer is cleared each time the
4478 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history-file"></a>3.78. history_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4479 Default: “<span class="quote"><code class="literal">˜/.mutthistory</code></span>”</p></div><p>
4480 The file in which Mutt will save its history.
4481 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="honor-followup-to"></a>3.79. honor_followup_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4482 Default: yes</p></div><p>
4483 This variable controls whether or not a Mail-Followup-To header is
4484 honored when group-replying to a message.
4485 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hostname"></a>3.80. hostname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4486 Default: (empty)</p></div><p>
4487 Specifies the fully-qualified hostname of the system mutt is running on
4488 containing the host's name and the DNS domain it belongs to. It is used
4489 as the domain part (after “<span class="quote">@</span>”) for local email addresses as well as
4492 Its value is determined at startup as follows: If the node's name
4493 as returned by the <code class="literal">uname(3)</code> function contains the hostname and the
4494 domain, these are used to construct <a class="link" href="#hostname" title="3.80. hostname">$hostname</a>. If there is no
4495 domain part returned, Mutt will look for a “<span class="quote">domain</span>” or “<span class="quote">search</span>”
4496 line in <code class="literal">/etc/resolv.conf</code> to determine the domain. Optionally, Mutt
4497 can be compiled with a fixed domain name in which case a detected
4500 Also see <a class="link" href="#use-domain" title="3.296. use_domain">$use_domain</a> and <a class="link" href="#hidden-host" title="3.71. hidden_host">$hidden_host</a>.
4502 <span class="bold"><strong>Note:</strong></span> On Debian systems, the default for this variable is obtained
4503 from /etc/mailname when Mutt starts.
4504 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-linear-white-space"></a>3.81. ignore_linear_white_space</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4505 Default: no</p></div><p>
4506 This option replaces linear-white-space between encoded-word
4507 and text to a single space to prevent the display of MIME-encoded
4508 “<span class="quote">Subject:</span>” field from being divided into multiple lines.
4509 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-list-reply-to"></a>3.82. ignore_list_reply_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4510 Default: no</p></div><p>
4511 Affects the behaviour of the <code class="literal"><reply></code> function when replying to
4512 messages from mailing lists (as defined by the “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” or
4513 “<span class="quote"><a class="link" href="#lists" title="12. Mailing lists">lists</a></span>” commands). When <span class="emphasis"><em>set</em></span>, if the “<span class="quote">Reply-To:</span>” field is
4514 set to the same value as the “<span class="quote">To:</span>” field, Mutt assumes that the
4515 “<span class="quote">Reply-To:</span>” field was set by the mailing list to automate responses
4516 to the list, and will ignore this field. To direct a response to the
4517 mailing list when this option is <span class="emphasis"><em>set</em></span>, use the <code class="literal"><a class="link" href="#list-reply"><list-reply></a></code>
4518 function; <code class="literal"><group-reply></code> will reply to both the sender and the
4520 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authenticators"></a>3.83. imap_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4521 Default: (empty)</p></div><p>
4522 This is a colon-delimited list of authentication methods mutt may
4523 attempt to use to log in to an IMAP server, in the order mutt should
4524 try them. Authentication methods are either “<span class="quote">login</span>” or the right
4525 side of an IMAP “<span class="quote">AUTH=xxx</span>” capability string, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>”
4526 or “<span class="quote">cram-md5</span>”. This option is case-insensitive. If it's
4527 <span class="emphasis"><em>unset</em></span> (the default) mutt will try all available methods,
4528 in order from most-secure to least-secure.
4532 </p><pre class="screen">
4533 set imap_authenticators="gssapi:cram-md5:login"
4536 <span class="bold"><strong>Note:</strong></span> Mutt will only fall back to other authentication methods if
4537 the previous methods are unavailable. If a method is available but
4538 authentication fails, mutt will not connect to the IMAP server.
4539 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-check-subscribed"></a>3.84. imap_check_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4540 Default: no</p></div><p>
4541 When <span class="emphasis"><em>set</em></span>, mutt will fetch the set of subscribed folders from
4542 your server on connection, and add them to the set of mailboxes
4543 it polls for new mail just as if you had issued individual “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
4545 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-delim-chars"></a>3.85. imap_delim_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4546 Default: “<span class="quote"><code class="literal">/.</code></span>”</p></div><p>
4547 This contains the list of characters which you would like to treat
4548 as folder separators for displaying IMAP paths. In particular it
4549 helps in using the “<span class="quote">=</span>” shortcut for your <span class="emphasis"><em>folder</em></span> variable.
4550 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-headers"></a>3.86. imap_headers</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4551 Default: (empty)</p></div><p>
4552 Mutt requests these header fields in addition to the default headers
4553 (“<span class="quote">Date:</span>”, “<span class="quote">From:</span>”, “<span class="quote">Subject:</span>”, “<span class="quote">To:</span>”, “<span class="quote">Cc:</span>”, “<span class="quote">Message-Id:</span>”,
4554 “<span class="quote">References:</span>”, “<span class="quote">Content-Type:</span>”, “<span class="quote">Content-Description:</span>”, “<span class="quote">In-Reply-To:</span>”,
4555 “<span class="quote">Reply-To:</span>”, “<span class="quote">Lines:</span>”, “<span class="quote">List-Post:</span>”, “<span class="quote">X-Label:</span>”) from IMAP
4556 servers before displaying the index menu. You may want to add more
4557 headers for spam detection.
4559 <span class="bold"><strong>Note:</strong></span> This is a space separated list, items should be uppercase
4560 and not contain the colon, e.g. “<span class="quote">X-BOGOSITY X-SPAM-STATUS</span>” for the
4561 “<span class="quote">X-Bogosity:</span>” and “<span class="quote">X-Spam-Status:</span>” header fields.
4562 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-idle"></a>3.87. imap_idle</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4563 Default: no</p></div><p>
4564 When <span class="emphasis"><em>set</em></span>, mutt will attempt to use the IMAP IDLE extension
4565 to check for new mail in the current mailbox. Some servers
4566 (dovecot was the inspiration for this option) react badly
4567 to mutt's implementation. If your connection seems to freeze
4568 up periodically, try unsetting this.
4569 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-keepalive"></a>3.88. imap_keepalive</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4570 Default: 900</p></div><p>
4571 This variable specifies the maximum amount of time in seconds that mutt
4572 will wait before polling open IMAP connections, to prevent the server
4573 from closing them before mutt has finished with them. The default is
4574 well within the RFC-specified minimum amount of time (30 minutes) before
4575 a server is allowed to do this, but in practice the RFC does get
4576 violated every now and then. Reduce this number if you find yourself
4577 getting disconnected from your IMAP server due to inactivity.
4578 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-list-subscribed"></a>3.89. imap_list_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4579 Default: no</p></div><p>
4580 This variable configures whether IMAP folder browsing will look for
4581 only subscribed folders or all folders. This can be toggled in the
4582 IMAP browser with the <code class="literal"><toggle-subscribed></code> function.
4583 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-login"></a>3.90. imap_login</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4584 Default: (empty)</p></div><p>
4585 Your login name on the IMAP server.
4587 This variable defaults to the value of <a class="link" href="#imap-user" title="3.96. imap_user">$imap_user</a>.
4588 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pass"></a>3.91. imap_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4589 Default: (empty)</p></div><p>
4590 Specifies the password for your IMAP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
4591 prompt you for your password when you invoke the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function
4592 or try to open an IMAP folder.
4594 <span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
4595 fairly secure machine, because the superuser can read your muttrc even
4596 if you are the only one who can read the file.
4597 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-passive"></a>3.92. imap_passive</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4598 Default: yes</p></div><p>
4599 When <span class="emphasis"><em>set</em></span>, mutt will not open new IMAP connections to check for new
4600 mail. Mutt will only check for new mail over existing IMAP
4601 connections. This is useful if you don't want to be prompted to
4602 user/password pairs on mutt invocation, or if opening the connection
4604 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-peek"></a>3.93. imap_peek</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4605 Default: yes</p></div><p>
4606 When <span class="emphasis"><em>set</em></span>, mutt will avoid implicitly marking your mail as read whenever
4607 you fetch a message from the server. This is generally a good thing,
4608 but can make closing an IMAP folder somewhat slower. This option
4609 exists to appease speed freaks.
4610 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pipeline-depth"></a>3.94. imap_pipeline_depth</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4611 Default: 15</p></div><p>
4612 Controls the number of IMAP commands that may be queued up before they
4613 are sent to the server. A deeper pipeline reduces the amount of time
4614 mutt must wait for the server, and can make IMAP servers feel much
4615 more responsive. But not all servers correctly handle pipelined commands,
4616 so if you have problems you might want to try setting this variable to 0.
4618 <span class="bold"><strong>Note:</strong></span> Changes to this variable have no effect on open connections.
4619 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-servernoise"></a>3.95. imap_servernoise</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4620 Default: yes</p></div><p>
4621 When <span class="emphasis"><em>set</em></span>, mutt will display warning messages from the IMAP
4622 server as error messages. Since these messages are often
4623 harmless, or generated due to configuration problems on the
4624 server which are out of the users' hands, you may wish to suppress
4626 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-user"></a>3.96. imap_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4627 Default: (empty)</p></div><p>
4628 The name of the user whose mail you intend to access on the IMAP
4631 This variable defaults to your user name on the local machine.
4632 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="implicit-autoview"></a>3.97. implicit_autoview</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4633 Default: no</p></div><p>
4634 If set to “<span class="quote">yes</span>”, mutt will look for a mailcap entry with the
4635 “<span class="quote"><code class="literal">copiousoutput</code></span>” flag set for <span class="emphasis"><em>every</em></span> MIME attachment it doesn't have
4636 an internal viewer defined for. If such an entry is found, mutt will
4637 use the viewer defined in that entry to convert the body part to text
4639 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include"></a>3.98. include</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4640 Default: ask-yes</p></div><p>
4641 Controls whether or not a copy of the message(s) you are replying to
4642 is included in your reply.
4643 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include-onlyfirst"></a>3.99. include_onlyfirst</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4644 Default: no</p></div><p>
4645 Controls whether or not Mutt includes only the first attachment
4646 of the message you are replying.
4647 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="indent-string"></a>3.100. indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4648 Default: “<span class="quote"><code class="literal">> </code></span>”</p></div><p>
4649 Specifies the string to prepend to each line of text quoted in a
4650 message to which you are replying. You are strongly encouraged not to
4651 change this value, as it tends to agitate the more fanatical netizens.
4653 This option is a format string, please see the description of
4654 <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> for supported <code class="literal">printf(3)</code>-style sequences.
4656 Because for <code class="literal">format=lowed</code> style messages the quoting mechanism
4657 is strictly defined, this setting is ignored if <a class="link" href="#text-flowed" title="3.285. text_flowed">$text_flowed</a> is
4658 <span class="emphasis"><em>set</em></span>.
4659 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-format"></a>3.101. index_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4660 Default: “<span class="quote"><code class="literal">%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</code></span>”</p></div><p>
4661 This variable allows you to customize the message index display to
4662 your personal taste.
4664 “<span class="quote">Format strings</span>” are similar to the strings used in the C
4665 function <code class="literal">printf(3)</code> to format output (see the man page for more details).
4666 The following sequences are defined in Mutt:
4668 </p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>address of the author
4669 </p></dd><dt><span class="term">%A </span></dt><dd><p>reply-to address (if present; otherwise: address of author)
4670 </p></dd><dt><span class="term">%b </span></dt><dd><p>filename of the original message folder (think mailbox)
4671 </p></dd><dt><span class="term">%B </span></dt><dd><p>the list to which the letter was sent, or else the folder name (%b).
4672 </p></dd><dt><span class="term">%c </span></dt><dd><p>number of characters (bytes) in the message
4673 </p></dd><dt><span class="term">%C </span></dt><dd><p>current message number
4674 </p></dd><dt><span class="term">%d </span></dt><dd><p>date and time of the message in the format specified by
4675 <a class="link" href="#date-format" title="3.40. date_format">$date_format</a> converted to sender's time zone
4676 </p></dd><dt><span class="term">%D </span></dt><dd><p>date and time of the message in the format specified by
4677 <a class="link" href="#date-format" title="3.40. date_format">$date_format</a> converted to the local time zone
4678 </p></dd><dt><span class="term">%e </span></dt><dd><p>current message number in thread
4679 </p></dd><dt><span class="term">%E </span></dt><dd><p>number of messages in current thread
4680 </p></dd><dt><span class="term">%f </span></dt><dd><p>sender (address + real name), either From: or Return-Path:
4681 </p></dd><dt><span class="term">%F </span></dt><dd><p>author name, or recipient name if the message is from you
4682 </p></dd><dt><span class="term">%H </span></dt><dd><p>spam attribute(s) of this message
4683 </p></dd><dt><span class="term">%i </span></dt><dd><p>message-id of the current message
4684 </p></dd><dt><span class="term">%l </span></dt><dd><p>number of lines in the message (does not work with maildir,
4685 mh, and possibly IMAP folders)
4686 </p></dd><dt><span class="term">%L </span></dt><dd><p>If an address in the “<span class="quote">To:</span>” or “<span class="quote">Cc:</span>” header field matches an address
4687 defined by the users “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” command, this displays
4688 "To <list-name>", otherwise the same as %F.
4689 </p></dd><dt><span class="term">%m </span></dt><dd><p>total number of message in the mailbox
4690 </p></dd><dt><span class="term">%M </span></dt><dd><p>number of hidden messages if the thread is collapsed.
4691 </p></dd><dt><span class="term">%N </span></dt><dd><p>message score
4692 </p></dd><dt><span class="term">%n </span></dt><dd><p>author's real name (or address if missing)
4693 </p></dd><dt><span class="term">%O </span></dt><dd><p>original save folder where mutt would formerly have
4694 stashed the message: list name or recipient name
4695 if not sent to a list
4696 </p></dd><dt><span class="term">%P </span></dt><dd><p>progress indicator for the builtin pager (how much of the file has been displayed)
4697 </p></dd><dt><span class="term">%s </span></dt><dd><p>subject of the message
4698 </p></dd><dt><span class="term">%S </span></dt><dd><p>status of the message (“<span class="quote">N</span>”/“<span class="quote">D</span>”/“<span class="quote">d</span>”/“<span class="quote">!</span>”/“<span class="quote">r</span>”/*)
4699 </p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">To:</span>” field (recipients)
4700 </p></dd><dt><span class="term">%T </span></dt><dd><p>the appropriate character from the <a class="link" href="#to-chars" title="3.292. to_chars">$to_chars</a> string
4701 </p></dd><dt><span class="term">%u </span></dt><dd><p>user (login) name of the author
4702 </p></dd><dt><span class="term">%v </span></dt><dd><p>first name of the author, or the recipient if the message is from you
4703 </p></dd><dt><span class="term">%X </span></dt><dd><p>number of attachments
4704 (please see the “<span class="quote"><a class="link" href="#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
4705 </p></dd><dt><span class="term">%y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present
4706 </p></dd><dt><span class="term">%Y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present, and <span class="emphasis"><em>(1)</em></span> not at part of a thread tree,
4707 <span class="emphasis"><em>(2)</em></span> at the top of a thread, or <span class="emphasis"><em>(3)</em></span> “<span class="quote">X-Label:</span>” is different from
4708 preceding message's “<span class="quote">X-Label:</span>”.
4709 </p></dd><dt><span class="term">%Z </span></dt><dd><p>message status flags
4710 </p></dd><dt><span class="term">%{fmt} </span></dt><dd><p>the date and time of the message is converted to sender's
4711 time zone, and “<span class="quote">fmt</span>” is expanded by the library function
4712 <code class="literal">strftime(3)</code>; a leading bang disables locales
4713 </p></dd><dt><span class="term">%[fmt] </span></dt><dd><p>the date and time of the message is converted to the local
4714 time zone, and “<span class="quote">fmt</span>” is expanded by the library function
4715 <code class="literal">strftime(3)</code>; a leading bang disables locales
4716 </p></dd><dt><span class="term">%(fmt) </span></dt><dd><p>the local date and time when the message was received.
4717 “<span class="quote">fmt</span>” is expanded by the library function <code class="literal">strftime(3)</code>;
4718 a leading bang disables locales
4719 </p></dd><dt><span class="term">%<fmt> </span></dt><dd><p>the current local time. “<span class="quote">fmt</span>” is expanded by the library
4720 function <code class="literal">strftime(3)</code>; a leading bang disables locales.
4721 </p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
4722 </p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
4723 </p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
4724 </p></dd></dl></div><p>
4725 “<span class="quote">Soft-fill</span>” deserves some explanation: Normal right-justification
4726 will print everything to the left of the “<span class="quote">%></span>”, displaying padding and
4727 whatever lies to the right only if there's room. By contrast,
4728 soft-fill gives priority to the right-hand side, guaranteeing space
4729 to display it and showing padding only if there's still room. If
4730 necessary, soft-fill will eat text leftwards to make room for
4733 Note that these expandos are supported in
4734 “<span class="quote"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” and “<span class="quote"><a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></span>”, too.
4735 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ispell"></a>3.102. ispell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4736 Default: “<span class="quote"><code class="literal">ispell</code></span>”</p></div><p>
4737 How to invoke ispell (GNU's spell-checking software).
4738 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="keep-flagged"></a>3.103. keep_flagged</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4739 Default: no</p></div><p>
4740 If <span class="emphasis"><em>set</em></span>, read messages marked as flagged will not be moved
4741 from your spool mailbox to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
4742 a “<span class="quote"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
4743 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="locale"></a>3.104. locale</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4744 Default: “<span class="quote"><code class="literal">C</code></span>”</p></div><p>
4745 The locale used by <code class="literal">strftime(3)</code> to format dates. Legal values are
4746 the strings your system accepts for the locale environment variable <code class="literal">$LC_TIME</code>.
4747 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mail-check"></a>3.105. mail_check</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4748 Default: 5</p></div><p>
4749 This variable configures how often (in seconds) mutt should look for
4750 new mail. Also see the <a class="link" href="#timeout" title="3.290. timeout">$timeout</a> variable.
4751 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-path"></a>3.106. mailcap_path</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4752 Default: (empty)</p></div><p>
4753 This variable specifies which files to consult when attempting to
4754 display MIME bodies not directly supported by Mutt.
4755 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-sanitize"></a>3.107. mailcap_sanitize</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4756 Default: yes</p></div><p>
4757 If <span class="emphasis"><em>set</em></span>, mutt will restrict possible characters in mailcap % expandos
4758 to a well-defined set of safe characters. This is the safe setting,
4759 but we are not sure it doesn't break some more advanced MIME stuff.
4761 <span class="bold"><strong>DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
4762 DOING!</strong></span>
4763 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-mtime"></a>3.108. maildir_mtime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4764 Default: no</p></div><p>
4765 If set, the sort-by-date option in the browser will sort maildirs
4766 smartly, not using the mtime of the maildir itself but that of the
4767 newest message in the new subdirectory, making the sorting by
4768 reverse date much more useful. People with maildirs over NFS may
4769 wish to leave this option unset.
4770 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache"></a>3.109. header_cache</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4771 Default: (empty)</p></div><p>
4772 This variable points to the header cache database.
4773 If pointing to a directory Mutt will contain a header cache
4774 database file per folder, if pointing to a file that file will
4775 be a single global header cache. By default it is <span class="emphasis"><em>unset</em></span> so no header
4776 caching will be used.
4778 Header caching can greatly improve speed when opening POP, IMAP
4779 MH or Maildir folders, see “<span class="quote"><a class="link" href="#caching" title="7. Local caching">caching</a></span>” for details.
4780 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-header-cache-verify"></a>3.110. maildir_header_cache_verify</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4781 Default: yes</p></div><p>
4782 Check for Maildir unaware programs other than mutt having modified maildir
4783 files when the header cache is in use. This incurs one <code class="literal">stat(2)</code> per
4784 message every time the folder is opened (which can be very slow for NFS
4786 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache-pagesize"></a>3.111. header_cache_pagesize</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4787 Default: “<span class="quote"><code class="literal">16384</code></span>”</p></div><p>
4788 When mutt is compiled with either gdbm or bdb4 as the header cache backend,
4789 this option changes the database page size. Too large or too small
4790 values can waste space, memory, or CPU time. The default should be more
4791 or less optimal for most use cases.
4792 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-trash"></a>3.112. maildir_trash</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4793 Default: no</p></div><p>
4794 If <span class="emphasis"><em>set</em></span>, messages marked as deleted will be saved with the maildir
4795 trashed flag instead of unlinked. <span class="bold"><strong>Note:</strong></span> this only applies
4796 to maildir-style mailboxes. Setting it will have no effect on other
4798 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mark-old"></a>3.113. mark_old</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4799 Default: yes</p></div><p>
4800 Controls whether or not mutt marks <span class="emphasis"><em>new</em></span> <span class="bold"><strong>unread</strong></span>
4801 messages as <span class="emphasis"><em>old</em></span> if you exit a mailbox without reading them.
4802 With this option <span class="emphasis"><em>set</em></span>, the next time you start mutt, the messages
4803 will show up with an “<span class="quote">O</span>” next to them in the index menu,
4804 indicating that they are old.
4805 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="markers"></a>3.114. markers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4806 Default: yes</p></div><p>
4807 Controls the display of wrapped lines in the internal pager. If set, a
4808 “<span class="quote">+</span>” marker is displayed at the beginning of wrapped lines.
4810 Also see the <a class="link" href="#smart-wrap" title="3.267. smart_wrap">$smart_wrap</a> variable.
4811 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mask"></a>3.115. mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
4812 Default: “<span class="quote"><code class="literal">!^\.[^.]</code></span>”</p></div><p>
4813 A regular expression used in the file browser, optionally preceded by
4814 the <span class="emphasis"><em>not</em></span> operator “<span class="quote">!</span>”. Only files whose names match this mask
4815 will be shown. The match is always case-sensitive.
4816 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox"></a>3.116. mbox</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4817 Default: “<span class="quote"><code class="literal">˜/mbox</code></span>”</p></div><p>
4818 This specifies the folder into which read mail in your <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a>
4819 folder will be appended.
4821 Also see the <a class="link" href="#move" title="3.132. move">$move</a> variable.
4822 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox-type"></a>3.117. mbox_type</h3></div></div></div><div class="literallayout"><p>Type: folder magic<br />
4823 Default: mbox</p></div><p>
4824 The default mailbox type used when creating new folders. May be any of
4825 “<span class="quote">mbox</span>”, “<span class="quote">MMDF</span>”, “<span class="quote">MH</span>” and “<span class="quote">Maildir</span>”.
4826 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="metoo"></a>3.118. metoo</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4827 Default: no</p></div><p>
4828 If <span class="emphasis"><em>unset</em></span>, Mutt will remove your address (see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”
4829 command) from the list of recipients when replying to a message.
4830 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-context"></a>3.119. menu_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4831 Default: 0</p></div><p>
4832 This variable controls the number of lines of context that are given
4833 when scrolling through menus. (Similar to <a class="link" href="#pager-context" title="3.139. pager_context">$pager_context</a>.)
4834 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-move-off"></a>3.120. menu_move_off</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4835 Default: yes</p></div><p>
4836 When <span class="emphasis"><em>unset</em></span>, the bottom entry of menus will never scroll up past
4837 the bottom of the screen, unless there are less entries than lines.
4838 When <span class="emphasis"><em>set</em></span>, the bottom entry may move off the bottom.
4839 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-scroll"></a>3.121. menu_scroll</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4840 Default: no</p></div><p>
4841 When <span class="emphasis"><em>set</em></span>, menus will be scrolled up or down one line when you
4842 attempt to move across a screen boundary. If <span class="emphasis"><em>unset</em></span>, the screen
4843 is cleared and the next or previous page of the menu is displayed
4844 (useful for slow links to avoid many redraws).
4845 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="meta-key"></a>3.122. meta_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4846 Default: no</p></div><p>
4847 If <span class="emphasis"><em>set</em></span>, forces Mutt to interpret keystrokes with the high bit (bit 8)
4848 set as if the user had pressed the Esc key and whatever key remains
4849 after having the high bit removed. For example, if the key pressed
4850 has an ASCII value of <code class="literal">0xf8</code>, then this is treated as if the user had
4851 pressed Esc then “<span class="quote">x</span>”. This is because the result of removing the
4852 high bit from <code class="literal">0xf8</code> is <code class="literal">0x78</code>, which is the ASCII character
4853 “<span class="quote">x</span>”.
4854 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-purge"></a>3.123. mh_purge</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4855 Default: no</p></div><p>
4856 When <span class="emphasis"><em>unset</em></span>, mutt will mimic mh's behaviour and rename deleted messages
4857 to <span class="emphasis"><em>,<old file name></em></span> in mh folders instead of really deleting
4858 them. This leaves the message on disk but makes programs reading the folder
4859 ignore it. If the variable is <span class="emphasis"><em>set</em></span>, the message files will simply be
4862 This option is similar to <a class="link" href="#maildir-trash" title="3.112. maildir_trash">$maildir_trash</a> for Maildir folders.
4863 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-flagged"></a>3.124. mh_seq_flagged</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4864 Default: “<span class="quote"><code class="literal">flagged</code></span>”</p></div><p>
4865 The name of the MH sequence used for flagged messages.
4866 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-replied"></a>3.125. mh_seq_replied</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4867 Default: “<span class="quote"><code class="literal">replied</code></span>”</p></div><p>
4868 The name of the MH sequence used to tag replied messages.
4869 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-unseen"></a>3.126. mh_seq_unseen</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4870 Default: “<span class="quote"><code class="literal">unseen</code></span>”</p></div><p>
4871 The name of the MH sequence used for unseen messages.
4872 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward"></a>3.127. mime_forward</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4873 Default: no</p></div><p>
4874 When <span class="emphasis"><em>set</em></span>, the message you are forwarding will be attached as a
4875 separate <code class="literal">message/rfc822</code> MIME part instead of included in the main body of the
4876 message. This is useful for forwarding MIME messages so the receiver
4877 can properly view the message as it was delivered to you. If you like
4878 to switch between MIME and not MIME from mail to mail, set this
4879 variable to “<span class="quote">ask-no</span>” or “<span class="quote">ask-yes</span>”.
4881 Also see <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a>.
4882 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-decode"></a>3.128. mime_forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4883 Default: no</p></div><p>
4884 Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
4885 forwarding a message while <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span>. Otherwise
4886 <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> is used instead.
4887 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-rest"></a>3.129. mime_forward_rest</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4888 Default: yes</p></div><p>
4889 When forwarding multiple attachments of a MIME message from the attachment
4890 menu, attachments which cannot be decoded in a reasonable manner will
4891 be attached to the newly composed message if this option is <span class="emphasis"><em>set</em></span>.
4892 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix-entry-format"></a>3.130. mix_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4893 Default: “<span class="quote"><code class="literal">%4n %c %-16s %a</code></span>”</p></div><p>
4894 This variable describes the format of a remailer line on the mixmaster
4895 chain selection screen. The following <code class="literal">printf(3)</code>-like sequences are
4898 </p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>The running number on the menu.
4899 </p></dd><dt><span class="term">%c </span></dt><dd><p>Remailer capabilities.
4900 </p></dd><dt><span class="term">%s </span></dt><dd><p>The remailer's short name.
4901 </p></dd><dt><span class="term">%a </span></dt><dd><p>The remailer's e-mail address.
4902 </p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mixmaster"></a>3.131. mixmaster</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4903 Default: “<span class="quote"><code class="literal">mixmaster</code></span>”</p></div><p>
4904 This variable contains the path to the Mixmaster binary on your
4905 system. It is used with various sets of parameters to gather the
4906 list of known remailers, and to finally send a message through the
4909 <span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
4910 “<span class="quote">mixmaster-filter</span>” in /etc/Muttrc.
4911 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="move"></a>3.132. move</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
4912 Default: no</p></div><p>
4913 Controls whether or not Mutt will move read messages
4914 from your spool mailbox to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
4915 a “<span class="quote"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
4916 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cachedir"></a>3.133. message_cachedir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4917 Default: (empty)</p></div><p>
4918 Set this to a directory and mutt will cache copies of messages from
4919 your IMAP and POP servers here. You are free to remove entries at any
4922 When setting this variable to a directory, mutt needs to fetch every
4923 remote message only once and can perform regular expression searches
4924 as fast as for local folders.
4926 Also see the <a class="link" href="#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a> variable.
4927 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cache-clean"></a>3.134. message_cache_clean</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4928 Default: no</p></div><p>
4929 If <span class="emphasis"><em>set</em></span>, mutt will clean out obsolete entries from the message cache when
4930 the mailbox is synchronized. You probably only want to set it
4931 every once in a while, since it can be a little slow
4932 (especially for large folders).
4933 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-format"></a>3.135. message_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4934 Default: “<span class="quote"><code class="literal">%s</code></span>”</p></div><p>
4935 This is the string displayed in the “<span class="quote">attachment</span>” menu for
4936 attachments of type <code class="literal">message/rfc822</code>. For a full listing of defined
4937 <code class="literal">printf(3)</code>-like sequences see the section on <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
4938 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="narrow-tree"></a>3.136. narrow_tree</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4939 Default: no</p></div><p>
4940 This variable, when <span class="emphasis"><em>set</em></span>, makes the thread tree narrower, allowing
4941 deeper threads to fit on the screen.
4942 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="net-inc"></a>3.137. net_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4943 Default: 10</p></div><p>
4944 Operations that expect to transfer a large amount of data over the
4945 network will update their progress every <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> kilobytes.
4946 If set to 0, no progress messages will be displayed.
4948 See also <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a> and <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a>.
4949 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager"></a>3.138. pager</h3></div></div></div><div class="literallayout"><p>Type: path<br />
4950 Default: “<span class="quote"><code class="literal">builtin</code></span>”</p></div><p>
4951 This variable specifies which pager you would like to use to view
4952 messages. The value “<span class="quote">builtin</span>” means to use the builtin pager, otherwise this
4953 variable should specify the pathname of the external pager you would
4956 Using an external pager may have some disadvantages: Additional
4957 keystrokes are necessary because you can't call mutt functions
4958 directly from the pager, and screen resizes cause lines longer than
4959 the screen width to be badly formatted in the help menu.
4960 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-context"></a>3.139. pager_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4961 Default: 0</p></div><p>
4962 This variable controls the number of lines of context that are given
4963 when displaying the next or previous page in the internal pager. By
4964 default, Mutt will display the line after the last one on the screen
4965 at the top of the next page (0 lines of context).
4966 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-format"></a>3.140. pager_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
4967 Default: “<span class="quote"><code class="literal">-%Z- %C/%m: %-20.20n %s%* -- (%P)</code></span>”</p></div><p>
4968 This variable controls the format of the one-line message “<span class="quote">status</span>”
4969 displayed before each message in either the internal or an external
4970 pager. The valid sequences are listed in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>
4972 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-index-lines"></a>3.141. pager_index_lines</h3></div></div></div><div class="literallayout"><p>Type: number<br />
4973 Default: 0</p></div><p>
4974 Determines the number of lines of a mini-index which is shown when in
4975 the pager. The current message, unless near the top or bottom of the
4976 folder, will be roughly one third of the way down this mini-index,
4977 giving the reader the context of a few messages before and after the
4978 message. This is useful, for example, to determine how many messages
4979 remain to be read in the current thread. One of the lines is reserved
4980 for the status bar from the index, so a setting of 6
4981 will only show 5 lines of the actual index. A value of 0 results in
4982 no index being shown. If the number of messages in the current folder
4983 is less than <a class="link" href="#pager-index-lines" title="3.141. pager_index_lines">$pager_index_lines</a>, then the index will only use as
4984 many lines as it needs.
4985 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-stop"></a>3.142. pager_stop</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4986 Default: no</p></div><p>
4987 When <span class="emphasis"><em>set</em></span>, the internal-pager will <span class="bold"><strong>not</strong></span> move to the next message
4988 when you are at the end of a message and invoke the <code class="literal"><next-page></code>
4990 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosign"></a>3.143. crypt_autosign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
4991 Default: no</p></div><p>
4992 Setting this variable will cause Mutt to always attempt to
4993 cryptographically sign outgoing messages. This can be overridden
4994 by use of the pgp menu, when signing is not required or
4995 encryption is requested as well. If <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
4996 then OpenSSL is used instead to create S/MIME messages and settings can
4997 be overridden by use of the smime menu instead of the pgp menu.
4999 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autoencrypt"></a>3.144. crypt_autoencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5000 Default: no</p></div><p>
5001 Setting this variable will cause Mutt to always attempt to PGP
5002 encrypt outgoing messages. This is probably only useful in
5003 connection to the “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>” command. It can be overridden
5004 by use of the pgp menu, when encryption is not required or
5005 signing is requested as well. If <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
5006 then OpenSSL is used instead to create S/MIME messages and
5007 settings can be overridden by use of the smime menu instead.
5009 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-ignore-subkeys"></a>3.145. pgp_ignore_subkeys</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5010 Default: yes</p></div><p>
5011 Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
5012 the principal key will inherit the subkeys' capabilities. <span class="emphasis"><em>Unset</em></span> this
5013 if you want to play interesting key selection games.
5015 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replyencrypt"></a>3.146. crypt_replyencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5016 Default: yes</p></div><p>
5017 If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL encrypt replies to messages which are
5020 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysign"></a>3.147. crypt_replysign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5021 Default: no</p></div><p>
5022 If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages which are
5025 <span class="bold"><strong>Note:</strong></span> this does not work on messages that are encrypted
5026 <span class="emphasis"><em>and</em></span> signed!
5028 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysignencrypted"></a>3.148. crypt_replysignencrypted</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5029 Default: no</p></div><p>
5030 If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages
5031 which are encrypted. This makes sense in combination with
5032 <a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>, because it allows you to sign all
5033 messages which are automatically encrypted. This works around
5034 the problem noted in <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a>, that mutt is not able
5035 to find out whether an encrypted message is also signed.
5037 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-timestamp"></a>3.149. crypt_timestamp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5038 Default: yes</p></div><p>
5039 If <span class="emphasis"><em>set</em></span>, mutt will include a time stamp in the lines surrounding
5040 PGP or S/MIME output, so spoofing such lines is more difficult.
5041 If you are using colors to mark these lines, and rely on these,
5042 you may <span class="emphasis"><em>unset</em></span> this setting.
5044 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-delim"></a>3.150. sidebar_delim</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5045 Default: “<span class="quote"><code class="literal">|</code></span>”</p></div><p>
5046 This specifies the delimiter between the sidebar (if visible) and
5048 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-visible"></a>3.151. sidebar_visible</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5049 Default: no</p></div><p>
5050 This specifies whether or not to show sidebar (left-side list of folders).
5051 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-width"></a>3.152. sidebar_width</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5052 Default: 0</p></div><p>
5053 The width of the sidebar.
5054 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-use-gpg-agent"></a>3.153. pgp_use_gpg_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5055 Default: no</p></div><p>
5056 If <span class="emphasis"><em>set</em></span>, mutt will use a possibly-running <code class="literal">gpg-agent(1)</code> process.
5058 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-verify-sig"></a>3.154. crypt_verify_sig</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5059 Default: yes</p></div><p>
5060 If <span class="emphasis"><em>“<span class="quote">yes</span>”</em></span>, always attempt to verify PGP or S/MIME signatures.
5061 If <span class="emphasis"><em>“<span class="quote">ask-*</span>”</em></span>, ask whether or not to verify the signature.
5062 If \Fi“<span class="quote">no</span>”, never attempt to verify cryptographic signatures.
5064 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-is-default"></a>3.155. smime_is_default</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5065 Default: no</p></div><p>
5066 The default behaviour of mutt is to use PGP on all auto-sign/encryption
5067 operations. To override and to use OpenSSL instead this must be <span class="emphasis"><em>set</em></span>.
5068 However, this has no effect while replying, since mutt will automatically
5069 select the same application that was used to sign/encrypt the original
5070 message. (Note that this variable can be overridden by unsetting <a class="link" href="#crypt-autosmime" title="3.39. crypt_autosmime">$crypt_autosmime</a>.)
5072 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ask-cert-label"></a>3.156. smime_ask_cert_label</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5073 Default: yes</p></div><p>
5074 This flag controls whether you want to be asked to enter a label
5075 for a certificate about to be added to the database or not. It is
5076 <span class="emphasis"><em>set</em></span> by default.
5078 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-use-default-key"></a>3.157. smime_decrypt_use_default_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5079 Default: yes</p></div><p>
5080 If <span class="emphasis"><em>set</em></span> (default) this tells mutt to use the default key for decryption. Otherwise,
5081 if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address
5082 to determine the key to use. It will ask you to supply a key, if it can't find one.
5084 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-entry-format"></a>3.158. pgp_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5085 Default: “<span class="quote"><code class="literal">%4n %t%f %4l/0x%k %-4a %2c %u</code></span>”</p></div><p>
5086 This variable allows you to customize the PGP key selection menu to
5087 your personal taste. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but
5088 has its own set of <code class="literal">printf(3)</code>-like sequences:
5090 </p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>number
5091 </p></dd><dt><span class="term">%k </span></dt><dd><p>key id
5092 </p></dd><dt><span class="term">%u </span></dt><dd><p>user id
5093 </p></dd><dt><span class="term">%a </span></dt><dd><p>algorithm
5094 </p></dd><dt><span class="term">%l </span></dt><dd><p>key length
5095 </p></dd><dt><span class="term">%f </span></dt><dd><p>flags
5096 </p></dd><dt><span class="term">%c </span></dt><dd><p>capabilities
5097 </p></dd><dt><span class="term">%t </span></dt><dd><p>trust/validity of the key-uid association
5098 </p></dd><dt><span class="term">%[<s>] </span></dt><dd><p>date of the key where <s> is an <code class="literal">strftime(3)</code> expression
5099 </p></dd></dl></div><p>
5101 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-good-sign"></a>3.159. pgp_good_sign</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
5102 Default: (empty)</p></div><p>
5103 If you assign a text to this variable, then a PGP signature is only
5104 considered verified if the output from <a class="link" href="#pgp-verify-command" title="3.176. pgp_verify_command">$pgp_verify_command</a> contains
5105 the text. Use this variable if the exit code from the command is 0
5106 even for bad signatures.
5108 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-check-exit"></a>3.160. pgp_check_exit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5109 Default: yes</p></div><p>
5110 If <span class="emphasis"><em>set</em></span>, mutt will check the exit code of the PGP subprocess when
5111 signing or encrypting. A non-zero exit code means that the
5114 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-long-ids"></a>3.161. pgp_long_ids</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5115 Default: no</p></div><p>
5116 If <span class="emphasis"><em>set</em></span>, use 64 bit PGP key IDs, if <span class="emphasis"><em>unset</em></span> use the normal 32 bit key IDs.
5118 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-retainable-sigs"></a>3.162. pgp_retainable_sigs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5119 Default: no</p></div><p>
5120 If <span class="emphasis"><em>set</em></span>, signed and encrypted messages will consist of nested
5121 <code class="literal">multipart/signed</code> and <code class="literal">multipart/encrypted</code> body parts.
5123 This is useful for applications like encrypted and signed mailing
5124 lists, where the outer layer (<code class="literal">multipart/encrypted</code>) can be easily
5125 removed, while the inner <code class="literal">multipart/signed</code> part is retained.
5127 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-autoinline"></a>3.163. pgp_autoinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5128 Default: no</p></div><p>
5129 This option controls whether Mutt generates old-style inline
5130 (traditional) PGP encrypted or signed messages under certain
5131 circumstances. This can be overridden by use of the pgp menu,
5132 when inline is not required.
5134 Note that Mutt might automatically use PGP/MIME for messages
5135 which consist of more than a single MIME part. Mutt can be
5136 configured to ask before sending PGP/MIME messages when inline
5137 (traditional) would not work.
5139 Also see the <a class="link" href="#pgp-mime-auto" title="3.170. pgp_mime_auto">$pgp_mime_auto</a> variable.
5141 Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
5142 <span class="bold"><strong>deprecated</strong></span>.
5144 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-replyinline"></a>3.164. pgp_replyinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5145 Default: no</p></div><p>
5146 Setting this variable will cause Mutt to always attempt to
5147 create an inline (traditional) message when replying to a
5148 message which is PGP encrypted/signed inline. This can be
5149 overridden by use of the pgp menu, when inline is not
5150 required. This option does not automatically detect if the
5151 (replied-to) message is inline; instead it relies on Mutt
5152 internals for previously checked/flagged messages.
5154 Note that Mutt might automatically use PGP/MIME for messages
5155 which consist of more than a single MIME part. Mutt can be
5156 configured to ask before sending PGP/MIME messages when inline
5157 (traditional) would not work.
5159 Also see the <a class="link" href="#pgp-mime-auto" title="3.170. pgp_mime_auto">$pgp_mime_auto</a> variable.
5161 Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
5162 <span class="bold"><strong>deprecated</strong></span>.
5164 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-show-unusable"></a>3.165. pgp_show_unusable</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5165 Default: yes</p></div><p>
5166 If <span class="emphasis"><em>set</em></span>, mutt will display non-usable keys on the PGP key selection
5167 menu. This includes keys which have been revoked, have expired, or
5168 have been marked as “<span class="quote">disabled</span>” by the user.
5170 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-as"></a>3.166. pgp_sign_as</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5171 Default: (empty)</p></div><p>
5172 If you have more than one key pair, this option allows you to specify
5173 which of your private keys to use. It is recommended that you use the
5174 keyid form to specify your key (e.g. <code class="literal">0x00112233</code>).
5176 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-strict-enc"></a>3.167. pgp_strict_enc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5177 Default: yes</p></div><p>
5178 If <span class="emphasis"><em>set</em></span>, Mutt will automatically encode PGP/MIME signed messages as
5179 quoted-printable. Please note that unsetting this variable may
5180 lead to problems with non-verifyable PGP signatures, so only change
5181 this if you know what you are doing.
5183 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-timeout"></a>3.168. pgp_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5184 Default: 300</p></div><p>
5185 The number of seconds after which a cached passphrase will expire if
5188 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sort-keys"></a>3.169. pgp_sort_keys</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
5189 Default: address</p></div><p>
5190 Specifies how the entries in the pgp menu are sorted. The
5191 following are legal values:
5193 </p><div class="variablelist"><dl><dt><span class="term">address </span></dt><dd><p>sort alphabetically by user id
5194 </p></dd><dt><span class="term">keyid </span></dt><dd><p>sort alphabetically by key id
5195 </p></dd><dt><span class="term">date </span></dt><dd><p>sort by key creation date
5196 </p></dd><dt><span class="term">trust </span></dt><dd><p>sort by the trust of the key
5197 </p></dd></dl></div><p>
5198 If you prefer reverse order of the above values, prefix it with
5199 “<span class="quote">reverse-</span>”.
5201 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-auto"></a>3.170. pgp_mime_auto</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5202 Default: ask-yes</p></div><p>
5203 This option controls whether Mutt will prompt you for
5204 automatically sending a (signed/encrypted) message using
5205 PGP/MIME when inline (traditional) fails (for any reason).
5207 Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
5208 <span class="bold"><strong>deprecated</strong></span>.
5210 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-auto-decode"></a>3.171. pgp_auto_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5211 Default: no</p></div><p>
5212 If <span class="emphasis"><em>set</em></span>, mutt will automatically attempt to decrypt traditional PGP
5213 messages whenever the user performs an operation which ordinarily would
5214 result in the contents of the message being operated on. For example,
5215 if the user displays a pgp-traditional message which has not been manually
5216 checked with the <code class="literal"><a class="link" href="#check-traditional-pgp"><check-traditional-pgp></a></code> function, mutt will automatically
5217 check the message for traditional pgp.
5218 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-filename"></a>3.172. pgp_mime_signature_filename</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5219 Default: “<span class="quote"><code class="literal">signature.asc</code></span>”</p></div><p>
5220 This option sets the filename used for signature parts in PGP/MIME
5222 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-description"></a>3.173. pgp_mime_signature_description</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5223 Default: “<span class="quote"><code class="literal">Digital signature</code></span>”</p></div><p>
5224 This option sets the Content-Description used for signature parts in
5225 PGP/MIME signed messages.
5226 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decode-command"></a>3.174. pgp_decode_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5227 Default: (empty)</p></div><p>
5228 This format strings specifies a command which is used to decode
5229 application/pgp attachments.
5231 The PGP command formats have their own set of <code class="literal">printf(3)</code>-like sequences:
5233 </p><div class="variablelist"><dl><dt><span class="term">%p </span></dt><dd><p>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
5234 string otherwise. Note: This may be used with a %? construct.
5235 </p></dd><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
5236 </p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
5237 of a <code class="literal">multipart/signed</code> attachment when verifying it.
5238 </p></dd><dt><span class="term">%a </span></dt><dd><p>The value of <a class="link" href="#pgp-sign-as" title="3.166. pgp_sign_as">$pgp_sign_as</a>.
5239 </p></dd><dt><span class="term">%r </span></dt><dd><p>One or more key IDs.
5240 </p></dd></dl></div><p>
5241 For examples on how to configure these formats for the various versions
5242 of PGP which are floating around, see the pgp and gpg sample configuration files in
5243 the <code class="literal">samples/</code> subdirectory which has been installed on your system
5244 alongside the documentation.
5246 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-getkeys-command"></a>3.175. pgp_getkeys_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5247 Default: (empty)</p></div><p>
5248 This command is invoked whenever mutt will need public key information.
5249 Of the sequences supported by <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a>, %r is the only
5250 <code class="literal">printf(3)</code>-like sequence used with this format.
5252 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-command"></a>3.176. pgp_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5253 Default: (empty)</p></div><p>
5254 This command is used to verify PGP signatures.
5256 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5257 possible <code class="literal">printf(3)</code>-like sequences.
5259 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decrypt-command"></a>3.177. pgp_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5260 Default: (empty)</p></div><p>
5261 This command is used to decrypt a PGP encrypted message.
5263 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5264 possible <code class="literal">printf(3)</code>-like sequences.
5266 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-clearsign-command"></a>3.178. pgp_clearsign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5267 Default: (empty)</p></div><p>
5268 This format is used to create an old-style “<span class="quote">clearsigned</span>” PGP
5269 message. Note that the use of this format is <span class="bold"><strong>strongly</strong></span>
5270 <span class="bold"><strong>deprecated</strong></span>.
5272 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5273 possible <code class="literal">printf(3)</code>-like sequences.
5275 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-command"></a>3.179. pgp_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5276 Default: (empty)</p></div><p>
5277 This command is used to create the detached PGP signature for a
5278 <code class="literal">multipart/signed</code> PGP/MIME body part.
5280 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5281 possible <code class="literal">printf(3)</code>-like sequences.
5283 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-sign-command"></a>3.180. pgp_encrypt_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5284 Default: (empty)</p></div><p>
5285 This command is used to both sign and encrypt a body part.
5287 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5288 possible <code class="literal">printf(3)</code>-like sequences.
5290 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-only-command"></a>3.181. pgp_encrypt_only_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5291 Default: (empty)</p></div><p>
5292 This command is used to encrypt a body part without signing it.
5294 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5295 possible <code class="literal">printf(3)</code>-like sequences.
5297 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-import-command"></a>3.182. pgp_import_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5298 Default: (empty)</p></div><p>
5299 This command is used to import a key from a message into
5300 the user's public key ring.
5302 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5303 possible <code class="literal">printf(3)</code>-like sequences.
5305 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-export-command"></a>3.183. pgp_export_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5306 Default: (empty)</p></div><p>
5307 This command is used to export a public key from the user's
5310 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5311 possible <code class="literal">printf(3)</code>-like sequences.
5313 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-key-command"></a>3.184. pgp_verify_key_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5314 Default: (empty)</p></div><p>
5315 This command is used to verify key information from the key selection
5318 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5319 possible <code class="literal">printf(3)</code>-like sequences.
5321 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-secring-command"></a>3.185. pgp_list_secring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5322 Default: (empty)</p></div><p>
5323 This command is used to list the secret key ring's contents. The
5324 output format must be analogous to the one used by:
5326 </p><pre class="screen">
5327 gpg --list-keys --with-colons.
5330 This format is also generated by the <code class="literal">pgpring</code> utility which comes
5333 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5334 possible <code class="literal">printf(3)</code>-like sequences.
5336 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-pubring-command"></a>3.186. pgp_list_pubring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5337 Default: (empty)</p></div><p>
5338 This command is used to list the public key ring's contents. The
5339 output format must be analogous to the one used by
5341 </p><pre class="screen">
5342 gpg --list-keys --with-colons.
5345 This format is also generated by the <code class="literal">pgpring</code> utility which comes
5348 This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
5349 possible <code class="literal">printf(3)</code>-like sequences.
5351 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decrypt"></a>3.187. forward_decrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5352 Default: yes</p></div><p>
5353 Controls the handling of encrypted messages when forwarding a message.
5354 When <span class="emphasis"><em>set</em></span>, the outer layer of encryption is stripped off. This
5355 variable is only used if <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span> and
5356 <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is <span class="emphasis"><em>unset</em></span>.
5358 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-timeout"></a>3.188. smime_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5359 Default: 300</p></div><p>
5360 The number of seconds after which a cached passphrase will expire if
5363 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-with"></a>3.189. smime_encrypt_with</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5364 Default: (empty)</p></div><p>
5365 This sets the algorithm that should be used for encryption.
5366 Valid choices are “<span class="quote">des</span>”, “<span class="quote">des3</span>”, “<span class="quote">rc2-40</span>”, “<span class="quote">rc2-64</span>”, “<span class="quote">rc2-128</span>”.
5367 If <span class="emphasis"><em>unset</em></span>, “<span class="quote">3des</span>” (TripleDES) is used.
5369 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-keys"></a>3.190. smime_keys</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5370 Default: (empty)</p></div><p>
5371 Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
5372 storage and retrieval of keys/certs by itself. This is very basic right now,
5373 and stores keys and certificates in two different directories, both
5374 named as the hash-value retrieved from OpenSSL. There is an index file
5375 which contains mailbox-address keyid pair, and which can be manually
5376 edited. This option points to the location of the private keys.
5378 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ca-location"></a>3.191. smime_ca_location</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5379 Default: (empty)</p></div><p>
5380 This variable contains the name of either a directory, or a file which
5381 contains trusted certificates for use with OpenSSL.
5384 <span class="bold"><strong>Note:</strong></span> On Debian systems, this defaults to the first existing file in
5385 the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
5386 /etc/ssl/certs/ca-certificates.crt.
5387 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-certificates"></a>3.192. smime_certificates</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5388 Default: (empty)</p></div><p>
5389 Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
5390 storage and retrieval of keys by itself. This is very basic right
5391 now, and keys and certificates are stored in two different
5392 directories, both named as the hash-value retrieved from
5393 OpenSSL. There is an index file which contains mailbox-address
5394 keyid pairs, and which can be manually edited. This option points to
5395 the location of the certificates.
5397 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-command"></a>3.193. smime_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5398 Default: (empty)</p></div><p>
5399 This format string specifies a command which is used to decrypt
5400 <code class="literal">application/x-pkcs7-mime</code> attachments.
5402 The OpenSSL command formats have their own set of <code class="literal">printf(3)</code>-like sequences
5405 </p><div class="variablelist"><dl><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
5406 </p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
5407 of a <code class="literal">multipart/signed</code> attachment when verifying it.
5408 </p></dd><dt><span class="term">%k </span></dt><dd><p>The key-pair specified with <a class="link" href="#smime-default-key" title="3.204. smime_default_key">$smime_default_key</a>
5409 </p></dd><dt><span class="term">%c </span></dt><dd><p>One or more certificate IDs.
5410 </p></dd><dt><span class="term">%a </span></dt><dd><p>The algorithm used for encryption.
5411 </p></dd><dt><span class="term">%C </span></dt><dd><p>CA location: Depending on whether <a class="link" href="#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a>
5412 points to a directory or file, this expands to
5413 “<span class="quote">-CApath <a class="link" href="#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a></span>” or “<span class="quote">-CAfile <a class="link" href="#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a></span>”.
5414 </p></dd></dl></div><p>
5415 For examples on how to configure these formats, see the <code class="literal">smime.rc</code> in
5416 the <code class="literal">samples/</code> subdirectory which has been installed on your system
5417 alongside the documentation.
5419 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-command"></a>3.194. smime_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5420 Default: (empty)</p></div><p>
5421 This command is used to verify S/MIME signatures of type <code class="literal">multipart/signed</code>.
5423 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5424 possible <code class="literal">printf(3)</code>-like sequences.
5426 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-opaque-command"></a>3.195. smime_verify_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5427 Default: (empty)</p></div><p>
5428 This command is used to verify S/MIME signatures of type
5429 <code class="literal">application/x-pkcs7-mime</code>.
5431 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5432 possible <code class="literal">printf(3)</code>-like sequences.
5434 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-command"></a>3.196. smime_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5435 Default: (empty)</p></div><p>
5436 This command is used to created S/MIME signatures of type
5437 <code class="literal">multipart/signed</code>, which can be read by all mail clients.
5439 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5440 possible <code class="literal">printf(3)</code>-like sequences.
5442 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-opaque-command"></a>3.197. smime_sign_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5443 Default: (empty)</p></div><p>
5444 This command is used to created S/MIME signatures of type
5445 <code class="literal">application/x-pkcs7-signature</code>, which can only be handled by mail
5446 clients supporting the S/MIME extension.
5448 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5449 possible <code class="literal">printf(3)</code>-like sequences.
5451 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-command"></a>3.198. smime_encrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5452 Default: (empty)</p></div><p>
5453 This command is used to create encrypted S/MIME messages.
5455 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5456 possible <code class="literal">printf(3)</code>-like sequences.
5458 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-pk7out-command"></a>3.199. smime_pk7out_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5459 Default: (empty)</p></div><p>
5460 This command is used to extract PKCS7 structures of S/MIME signatures,
5461 in order to extract the public X509 certificate(s).
5463 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5464 possible <code class="literal">printf(3)</code>-like sequences.
5466 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-command"></a>3.200. smime_get_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5467 Default: (empty)</p></div><p>
5468 This command is used to extract X509 certificates from a PKCS7 structure.
5470 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5471 possible <code class="literal">printf(3)</code>-like sequences.
5473 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-signer-cert-command"></a>3.201. smime_get_signer_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5474 Default: (empty)</p></div><p>
5475 This command is used to extract only the signers X509 certificate from a S/MIME
5476 signature, so that the certificate's owner may get compared to the
5477 email's “<span class="quote">From:</span>” field.
5479 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5480 possible <code class="literal">printf(3)</code>-like sequences.
5482 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-import-cert-command"></a>3.202. smime_import_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5483 Default: (empty)</p></div><p>
5484 This command is used to import a certificate via smime_keys.
5486 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5487 possible <code class="literal">printf(3)</code>-like sequences.
5489 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-email-command"></a>3.203. smime_get_cert_email_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5490 Default: (empty)</p></div><p>
5491 This command is used to extract the mail address(es) used for storing
5492 X509 certificates, and for verification purposes (to check whether the
5493 certificate was issued for the sender's mailbox).
5495 This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
5496 possible <code class="literal">printf(3)</code>-like sequences.
5498 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-default-key"></a>3.204. smime_default_key</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5499 Default: (empty)</p></div><p>
5500 This is the default key-pair to use for signing. This must be set to the
5501 keyid (the hash-value that OpenSSL generates) to work properly
5503 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-client-cert"></a>3.205. ssl_client_cert</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5504 Default: (empty)</p></div><p>
5505 The file containing a client certificate and its associated private
5507 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-force-tls"></a>3.206. ssl_force_tls</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5508 Default: no</p></div><p>
5509 If this variable is <span class="emphasis"><em>set</em></span>, Mutt will require that all connections
5510 to remote servers be encrypted. Furthermore it will attempt to
5511 negotiate TLS even if the server does not advertise the capability,
5512 since it would otherwise have to abort the connection anyway. This
5513 option supersedes <a class="link" href="#ssl-starttls" title="3.207. ssl_starttls">$ssl_starttls</a>.
5514 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-starttls"></a>3.207. ssl_starttls</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5515 Default: yes</p></div><p>
5516 If <span class="emphasis"><em>set</em></span> (the default), mutt will attempt to use <code class="literal">STARTTLS</code> on servers
5517 advertising the capability. When <span class="emphasis"><em>unset</em></span>, mutt will not attempt to
5518 use <code class="literal">STARTTLS</code> regardless of the server's capabilities.
5519 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="certificate-file"></a>3.208. certificate_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5520 Default: “<span class="quote"><code class="literal">˜/.mutt_certificates</code></span>”</p></div><p>
5521 This variable specifies the file where the certificates you trust
5522 are saved. When an unknown certificate is encountered, you are asked
5523 if you accept it or not. If you accept it, the certificate can also
5524 be saved in this file and further connections are automatically
5527 You can also manually add CA certificates in this file. Any server
5528 certificate that is signed with one of these CA certificates is
5529 also automatically accepted.
5533 </p><pre class="screen">
5534 set certificate_file=~/.mutt/certificates
5536 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-sslv3"></a>3.209. ssl_use_sslv3</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5537 Default: yes</p></div><p>
5538 This variable specifies whether to attempt to use SSLv3 in the
5539 SSL authentication process.
5540 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-tlsv1"></a>3.210. ssl_use_tlsv1</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5541 Default: yes</p></div><p>
5542 This variable specifies whether to attempt to use TLSv1 in the
5543 SSL authentication process.
5544 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-min-dh-prime-bits"></a>3.211. ssl_min_dh_prime_bits</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5545 Default: 0</p></div><p>
5546 This variable specifies the minimum acceptable prime size (in bits)
5547 for use in any Diffie-Hellman key exchange. A value of 0 will use
5548 the default from the GNUTLS library.
5549 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-ca-certificates-file"></a>3.212. ssl_ca_certificates_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5550 Default: (empty)</p></div><p>
5551 This variable specifies a file containing trusted CA certificates.
5552 Any server certificate that is signed with one of these CA
5553 certificates is also automatically accepted.
5557 </p><pre class="screen">
5558 set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
5561 <span class="bold"><strong>Note:</strong></span> On Debian systems, this variable defaults to the example
5562 mentioned. This file is managed by the “<span class="quote">ca-certificates</span>” package.
5563 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-split"></a>3.213. pipe_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5564 Default: no</p></div><p>
5565 Used in connection with the <code class="literal"><pipe-message></code> function following
5566 <code class="literal"><tag-prefix></code>. If this variable is <span class="emphasis"><em>unset</em></span>, when piping a list of
5567 tagged messages Mutt will concatenate the messages and will pipe them
5568 all concatenated. When <span class="emphasis"><em>set</em></span>, Mutt will pipe the messages one by one.
5569 In both cases the messages are piped in the current sorted order,
5570 and the <a class="link" href="#pipe-sep" title="3.215. pipe_sep">$pipe_sep</a> separator is added after each message.
5571 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-decode"></a>3.214. pipe_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5572 Default: no</p></div><p>
5573 Used in connection with the <code class="literal"><pipe-message></code> command. When <span class="emphasis"><em>unset</em></span>,
5574 Mutt will pipe the messages without any preprocessing. When <span class="emphasis"><em>set</em></span>, Mutt
5575 will weed headers and will attempt to decode the messages
5577 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-sep"></a>3.215. pipe_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5578 Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
5579 The separator to add between messages when piping a list of tagged
5580 messages to an external Unix command.
5581 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-authenticators"></a>3.216. pop_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5582 Default: (empty)</p></div><p>
5583 This is a colon-delimited list of authentication methods mutt may
5584 attempt to use to log in to an POP server, in the order mutt should
5585 try them. Authentication methods are either “<span class="quote">user</span>”, “<span class="quote">apop</span>” or any
5586 SASL mechanism, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
5587 This option is case-insensitive. If this option is <span class="emphasis"><em>unset</em></span>
5588 (the default) mutt will try all available methods, in order from
5589 most-secure to least-secure.
5593 </p><pre class="screen">
5594 set pop_authenticators="digest-md5:apop:user"
5596 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-auth-try-all"></a>3.217. pop_auth_try_all</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5597 Default: yes</p></div><p>
5598 If <span class="emphasis"><em>set</em></span>, Mutt will try all available authentication methods.
5599 When <span class="emphasis"><em>unset</em></span>, Mutt will only fall back to other authentication
5600 methods if the previous methods are unavailable. If a method is
5601 available but authentication fails, Mutt will not connect to the POP server.
5602 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-checkinterval"></a>3.218. pop_checkinterval</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5603 Default: 60</p></div><p>
5604 This variable configures how often (in seconds) mutt should look for
5605 new mail in the currently selected mailbox if it is a POP mailbox.
5606 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-delete"></a>3.219. pop_delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5607 Default: ask-no</p></div><p>
5608 If <span class="emphasis"><em>set</em></span>, Mutt will delete successfully downloaded messages from the POP
5609 server when using the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function. When <span class="emphasis"><em>unset</em></span>, Mutt will
5610 download messages but also leave them on the POP server.
5611 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-host"></a>3.220. pop_host</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5612 Default: (empty)</p></div><p>
5613 The name of your POP server for the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function. You
5614 can also specify an alternative port, username and password, ie:
5616 </p><pre class="screen">
5617 [pop[s]://][username[:password]@]popserver[:port]
5620 where “<span class="quote">[...]</span>” denotes an optional part.
5621 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-last"></a>3.221. pop_last</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5622 Default: no</p></div><p>
5623 If this variable is <span class="emphasis"><em>set</em></span>, mutt will try to use the “<span class="quote"><code class="literal">LAST</code></span>” POP command
5624 for retrieving only unread messages from the POP server when using
5625 the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function.
5626 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-reconnect"></a>3.222. pop_reconnect</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5627 Default: ask-yes</p></div><p>
5628 Controls whether or not Mutt will try to reconnect to the POP server if
5629 the connection is lost.
5630 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-user"></a>3.223. pop_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5631 Default: (empty)</p></div><p>
5632 Your login name on the POP server.
5634 This variable defaults to your user name on the local machine.
5635 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-pass"></a>3.224. pop_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5636 Default: (empty)</p></div><p>
5637 Specifies the password for your POP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
5638 prompt you for your password when you open a POP mailbox.
5640 <span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
5641 fairly secure machine, because the superuser can read your muttrc
5642 even if you are the only one who can read the file.
5643 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="post-indent-string"></a>3.225. post_indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5644 Default: (empty)</p></div><p>
5645 Similar to the <a class="link" href="#attribution" title="3.16. attribution">$attribution</a> variable, Mutt will append this
5646 string after the inclusion of a message which is being replied to.
5647 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone"></a>3.226. postpone</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5648 Default: ask-yes</p></div><p>
5649 Controls whether or not messages are saved in the <a class="link" href="#postponed" title="3.227. postponed">$postponed</a>
5650 mailbox when you elect not to send immediately.
5652 Also see the <a class="link" href="#recall" title="3.241. recall">$recall</a> variable.
5653 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postponed"></a>3.227. postponed</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5654 Default: “<span class="quote"><code class="literal">˜/postponed</code></span>”</p></div><p>
5655 Mutt allows you to indefinitely “<span class="quote"><a class="link" href="#postpone" title="3.226. postpone">postpone</a> sending a message</span>” which
5656 you are editing. When you choose to postpone a message, Mutt saves it
5657 in the mailbox specified by this variable.
5659 Also see the <a class="link" href="#postpone" title="3.226. postpone">$postpone</a> variable.
5660 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="preconnect"></a>3.228. preconnect</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5661 Default: (empty)</p></div><p>
5662 If <span class="emphasis"><em>set</em></span>, a shell command to be executed if mutt fails to establish
5663 a connection to the server. This is useful for setting up secure
5664 connections, e.g. with <code class="literal">ssh(1)</code>. If the command returns a nonzero
5665 status, mutt gives up opening the server. Example:
5667 </p><pre class="screen">
5668 set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
5669 sleep 20 < /dev/null > /dev/null"
5672 Mailbox “<span class="quote">foo</span>” on “<span class="quote">mailhost.net</span>” can now be reached
5673 as “<span class="quote">{localhost:1234}foo</span>”.
5675 Note: For this example to work, you must be able to log in to the
5676 remote machine without having to enter a password.
5678 When set, Mutt uses the tunnel for all remote connections.
5679 Please see “<span class="quote"><a class="link" href="#account-hook" title="6. Managing multiple accounts">account-hook</a></span>” in the manual for how to use different
5680 tunnel commands per connection.
5681 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print"></a>3.229. print</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5682 Default: ask-no</p></div><p>
5683 Controls whether or not Mutt really prints messages.
5684 This is set to “<span class="quote">ask-no</span>” by default, because some people
5685 accidentally hit “<span class="quote">p</span>” often.
5686 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-command"></a>3.230. print_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5687 Default: “<span class="quote"><code class="literal">lpr</code></span>”</p></div><p>
5688 This specifies the command pipe that should be used to print messages.
5689 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-decode"></a>3.231. print_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5690 Default: yes</p></div><p>
5691 Used in connection with the <code class="literal"><print-message></code> command. If this
5692 option is <span class="emphasis"><em>set</em></span>, the message is decoded before it is passed to the
5693 external command specified by <a class="link" href="#print-command" title="3.230. print_command">$print_command</a>. If this option
5694 is <span class="emphasis"><em>unset</em></span>, no processing will be applied to the message when
5695 printing it. The latter setting may be useful if you are using
5696 some advanced printer filter which is able to properly format
5697 e-mail messages for printing.
5698 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-split"></a>3.232. print_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5699 Default: no</p></div><p>
5700 Used in connection with the <code class="literal"><print-message></code> command. If this option
5701 is <span class="emphasis"><em>set</em></span>, the command specified by <a class="link" href="#print-command" title="3.230. print_command">$print_command</a> is executed once for
5702 each message which is to be printed. If this option is <span class="emphasis"><em>unset</em></span>,
5703 the command specified by <a class="link" href="#print-command" title="3.230. print_command">$print_command</a> is executed only once, and
5704 all the messages are concatenated, with a form feed as the message
5707 Those who use the <code class="literal">enscript</code>(1) program's mail-printing mode will
5708 most likely want to <span class="emphasis"><em>set</em></span> this option.
5709 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="prompt-after"></a>3.233. prompt_after</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5710 Default: yes</p></div><p>
5711 If you use an <span class="emphasis"><em>external</em></span> <a class="link" href="#pager" title="3.138. pager">$pager</a>, setting this variable will
5712 cause Mutt to prompt you for a command when the pager exits rather
5713 than returning to the index menu. If <span class="emphasis"><em>unset</em></span>, Mutt will return to the
5714 index menu when the external pager exits.
5715 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-command"></a>3.234. query_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5716 Default: (empty)</p></div><p>
5717 This specifies the command that mutt will use to make external address
5718 queries. The string should contain a “<span class="quote">%s</span>”, which will be substituted
5719 with the query string the user types. See “<span class="quote"><a class="link" href="#query" title="5. External Address Queries">query</a></span>” for more
5721 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-format"></a>3.235. query_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5722 Default: “<span class="quote"><code class="literal">%4c %t %-25.25a %-25.25n %?e?(%e)?</code></span>”</p></div><p>
5723 This variable describes the format of the “<span class="quote">query</span>” menu. The
5724 following <code class="literal">printf(3)</code>-style sequences are understood:
5726 </p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>destination address
5727 </p></dd><dt><span class="term">%c </span></dt><dd><p>current entry number
5728 </p></dd><dt><span class="term">%e </span></dt><dd><p>extra information *
5729 </p></dd><dt><span class="term">%n </span></dt><dd><p>destination name
5730 </p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if current entry is tagged, a space otherwise
5731 </p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
5732 </p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
5733 </p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
5734 </p></dd></dl></div><p>
5735 For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
5737 * = can be optionally printed if nonzero, see the <a class="link" href="#status-format" title="3.281. status_format">$status_format</a> documentation.
5738 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quit"></a>3.236. quit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5739 Default: yes</p></div><p>
5740 This variable controls whether “<span class="quote">quit</span>” and “<span class="quote">exit</span>” actually quit
5741 from mutt. If this option is <span class="emphasis"><em>set</em></span>, they do quit, if it is <span class="emphasis"><em>unset</em></span>, they
5742 have no effect, and if it is set to <span class="emphasis"><em>ask-yes</em></span> or <span class="emphasis"><em>ask-no</em></span>, you are
5743 prompted for confirmation when you try to quit.
5744 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quote-regexp"></a>3.237. quote_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
5745 Default: “<span class="quote"><code class="literal">^([ \t]*[|>:}#])+</code></span>”</p></div><p>
5746 A regular expression used in the internal pager to determine quoted
5747 sections of text in the body of a message. Quoted text may be filtered
5748 out using the <code class="literal"><toggle-quoted></code> command, or colored according to the
5749 “<span class="quote">color quoted</span>” family of directives.
5751 Higher levels of quoting may be colored differently (“<span class="quote">color quoted1</span>”,
5752 “<span class="quote">color quoted2</span>”, etc.). The quoting level is determined by removing
5753 the last character from the matched text and recursively reapplying
5754 the regular expression until it fails to produce a match.
5756 Match detection may be overridden by the <a class="link" href="#smileys" title="3.268. smileys">$smileys</a> regular expression.
5757 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-inc"></a>3.238. read_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5758 Default: 10</p></div><p>
5759 If set to a value greater than 0, Mutt will display which message it
5760 is currently on when reading a mailbox or when performing search actions
5761 such as search and limit. The message is printed after
5762 this many messages have been read or searched (e.g., if set to 25, Mutt will
5763 print a message when it is at message 25, and then again when it gets
5764 to message 50). This variable is meant to indicate progress when
5765 reading or searching large mailboxes which may take some time.
5766 When set to 0, only a single message will appear before the reading
5769 Also see the <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a>, <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> variables and the
5770 “<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
5771 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-only"></a>3.239. read_only</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5772 Default: no</p></div><p>
5773 If <span class="emphasis"><em>set</em></span>, all folders are opened in read-only mode.
5774 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="realname"></a>3.240. realname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5775 Default: (empty)</p></div><p>
5776 This variable specifies what “<span class="quote">real</span>” or “<span class="quote">personal</span>” name should be used
5777 when sending messages.
5779 By default, this is the GECOS field from <code class="literal">/etc/passwd</code>. Note that this
5780 variable will <span class="emphasis"><em>not</em></span> be used when the user has set a real name
5781 in the <a class="link" href="#from" title="3.66. from">$from</a> variable.
5782 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="recall"></a>3.241. recall</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5783 Default: ask-yes</p></div><p>
5784 Controls whether or not Mutt recalls postponed messages
5785 when composing a new message.
5787 <span class="emphasis"><em>Setting</em></span> this variable to is not generally useful, and thus not
5790 Also see <a class="link" href="#postponed" title="3.227. postponed">$postponed</a> variable.
5791 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="record"></a>3.242. record</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5792 Default: “<span class="quote"><code class="literal">˜/sent</code></span>”</p></div><p>
5793 This specifies the file into which your outgoing messages should be
5794 appended. (This is meant as the primary method for saving a copy of
5795 your messages, but another way to do this is using the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
5796 command to create a “<span class="quote">Bcc:</span>” field with your email address in it.)
5798 The value of <span class="emphasis"><em><a class="link" href="#record" title="3.242. record">$record</a></em></span> is overridden by the <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> and
5799 <a class="link" href="#save-name" title="3.254. save_name">$save_name</a> variables, and the “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” command.
5800 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-regexp"></a>3.243. reply_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
5801 Default: “<span class="quote"><code class="literal">^(re([\[0-9\]+])*|aw):[ \t]*</code></span>”</p></div><p>
5802 A regular expression used to recognize reply messages when threading
5803 and replying. The default value corresponds to the English "Re:" and
5805 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-self"></a>3.244. reply_self</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5806 Default: no</p></div><p>
5807 If <span class="emphasis"><em>unset</em></span> and you are replying to a message sent by you, Mutt will
5808 assume that you want to reply to the recipients of that message rather
5811 Also see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>” command.
5812 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-to"></a>3.245. reply_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
5813 Default: ask-yes</p></div><p>
5814 If <span class="emphasis"><em>set</em></span>, when replying to a message, Mutt will use the address listed
5815 in the Reply-to: header as the recipient of the reply. If <span class="emphasis"><em>unset</em></span>,
5816 it will use the address in the From: header field instead. This
5817 option is useful for reading a mailing list that sets the Reply-To:
5818 header field to the list address and you want to send a private
5819 message to the author of a message.
5820 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="resolve"></a>3.246. resolve</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5821 Default: yes</p></div><p>
5822 When <span class="emphasis"><em>set</em></span>, the cursor will be automatically advanced to the next
5823 (possibly undeleted) message whenever a command that modifies the
5824 current message is executed.
5825 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-alias"></a>3.247. reverse_alias</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5826 Default: no</p></div><p>
5827 This variable controls whether or not Mutt will display the “<span class="quote">personal</span>”
5828 name from your aliases in the index menu if it finds an alias that
5829 matches the message's sender. For example, if you have the following
5832 </p><pre class="screen">
5833 alias juser abd30425@somewhere.net (Joe User)
5836 and then you receive mail which contains the following header:
5838 </p><pre class="screen">
5839 From: abd30425@somewhere.net
5842 It would be displayed in the index menu as “<span class="quote">Joe User</span>” instead of
5843 “<span class="quote">abd30425@somewhere.net.</span>” This is useful when the person's e-mail
5844 address is not human friendly.
5845 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-name"></a>3.248. reverse_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5846 Default: no</p></div><p>
5847 It may sometimes arrive that you receive mail to a certain machine,
5848 move the messages to another machine, and reply to some the messages
5849 from there. If this variable is <span class="emphasis"><em>set</em></span>, the default <span class="emphasis"><em>From:</em></span> line of
5850 the reply messages is built using the address where you received the
5851 messages you are replying to <span class="bold"><strong>if</strong></span> that address matches your
5852 “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”. If the variable is <span class="emphasis"><em>unset</em></span>, or the address that would be
5853 used doesn't match your “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”, the <span class="emphasis"><em>From:</em></span> line will use
5854 your address on the current machine.
5856 Also see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>” command.
5857 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-realname"></a>3.249. reverse_realname</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5858 Default: yes</p></div><p>
5859 This variable fine-tunes the behaviour of the <a class="link" href="#reverse-name" title="3.248. reverse_name">$reverse_name</a> feature.
5860 When it is <span class="emphasis"><em>set</em></span>, mutt will use the address from incoming messages as-is,
5861 possibly including eventual real names. When it is <span class="emphasis"><em>unset</em></span>, mutt will
5862 override any such real names with the setting of the <a class="link" href="#realname" title="3.240. realname">$realname</a> variable.
5863 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="rfc2047-parameters"></a>3.250. rfc2047_parameters</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5864 Default: no</p></div><p>
5865 When this variable is <span class="emphasis"><em>set</em></span>, Mutt will decode RFC2047-encoded MIME
5866 parameters. You want to set this variable when mutt suggests you
5867 to save attachments to files named like:
5869 </p><pre class="screen">
5870 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
5873 When this variable is <span class="emphasis"><em>set</em></span> interactively, the change won't be
5874 active until you change folders.
5876 Note that this use of RFC2047's encoding is explicitly
5877 prohibited by the standard, but nevertheless encountered in the
5880 Also note that setting this parameter will <span class="emphasis"><em>not</em></span> have the effect
5881 that mutt <span class="emphasis"><em>generates</em></span> this kind of encoding. Instead, mutt will
5882 unconditionally use the encoding specified in RFC2231.
5883 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-address"></a>3.251. save_address</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5884 Default: no</p></div><p>
5885 If <span class="emphasis"><em>set</em></span>, mutt will take the sender's full address when choosing a
5886 default folder for saving a mail. If <a class="link" href="#save-name" title="3.254. save_name">$save_name</a> or <a class="link" href="#force-name" title="3.61. force_name">$force_name</a>
5887 is <span class="emphasis"><em>set</em></span> too, the selection of the Fcc folder will be changed as well.
5888 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-empty"></a>3.252. save_empty</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5889 Default: yes</p></div><p>
5890 When <span class="emphasis"><em>unset</em></span>, mailboxes which contain no saved messages will be removed
5891 when closed (the exception is <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a> which is never removed).
5892 If <span class="emphasis"><em>set</em></span>, mailboxes are never removed.
5894 <span class="bold"><strong>Note:</strong></span> This only applies to mbox and MMDF folders, Mutt does not
5895 delete MH and Maildir directories.
5896 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-history"></a>3.253. save_history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5897 Default: 0</p></div><p>
5898 This variable controls the size of the history (per category) saved in the
5899 <a class="link" href="#history-file" title="3.78. history_file">$history_file</a> file.
5900 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-name"></a>3.254. save_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5901 Default: no</p></div><p>
5902 This variable controls how copies of outgoing messages are saved.
5903 When <span class="emphasis"><em>set</em></span>, a check is made to see if a mailbox specified by the
5904 recipient address exists (this is done by searching for a mailbox in
5905 the <a class="link" href="#folder" title="3.58. folder">$folder</a> directory with the <span class="emphasis"><em>username</em></span> part of the
5906 recipient address). If the mailbox exists, the outgoing message will
5907 be saved to that mailbox, otherwise the message is saved to the
5908 <a class="link" href="#record" title="3.242. record">$record</a> mailbox.
5910 Also see the <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> variable.
5911 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score"></a>3.255. score</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5912 Default: yes</p></div><p>
5913 When this variable is <span class="emphasis"><em>unset</em></span>, scoring is turned off. This can
5914 be useful to selectively disable scoring for certain folders when the
5915 <a class="link" href="#score-threshold-delete" title="3.256. score_threshold_delete">$score_threshold_delete</a> variable and related are used.
5916 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-delete"></a>3.256. score_threshold_delete</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5917 Default: -1</p></div><p>
5918 Messages which have been assigned a score equal to or lower than the value
5919 of this variable are automatically marked for deletion by mutt. Since
5920 mutt scores are always greater than or equal to zero, the default setting
5921 of this variable will never mark a message for deletion.
5922 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-flag"></a>3.257. score_threshold_flag</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5923 Default: 9999</p></div><p>
5924 Messages which have been assigned a score greater than or equal to this
5925 variable's value are automatically marked "flagged".
5926 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-read"></a>3.258. score_threshold_read</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5927 Default: -1</p></div><p>
5928 Messages which have been assigned a score equal to or lower than the value
5929 of this variable are automatically marked as read by mutt. Since
5930 mutt scores are always greater than or equal to zero, the default setting
5931 of this variable will never mark a message read.
5932 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="send-charset"></a>3.259. send_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5933 Default: “<span class="quote"><code class="literal">us-ascii:iso-8859-1:utf-8</code></span>”</p></div><p>
5934 A colon-delimited list of character sets for outgoing messages. Mutt will use the
5935 first character set into which the text can be converted exactly.
5936 If your <a class="link" href="#charset" title="3.25. charset">$charset</a> is not “<span class="quote">iso-8859-1</span>” and recipients may not
5937 understand “<span class="quote">UTF-8</span>”, it is advisable to include in the list an
5938 appropriate widely used standard character set (such as
5939 “<span class="quote">iso-8859-2</span>”, “<span class="quote">koi8-r</span>” or “<span class="quote">iso-2022-jp</span>”) either instead of or after
5940 “<span class="quote">iso-8859-1</span>”.
5942 In case the text cannot be converted into one of these exactly,
5943 mutt uses <a class="link" href="#charset" title="3.25. charset">$charset</a> as a fallback.
5944 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail"></a>3.260. sendmail</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5945 Default: “<span class="quote"><code class="literal">/usr/sbin/sendmail -oem -oi</code></span>”</p></div><p>
5946 Specifies the program and arguments used to deliver mail sent by Mutt.
5947 Mutt expects that the specified program interprets additional
5948 arguments as recipient addresses.
5949 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail-wait"></a>3.261. sendmail_wait</h3></div></div></div><div class="literallayout"><p>Type: number<br />
5950 Default: 0</p></div><p>
5951 Specifies the number of seconds to wait for the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> process
5952 to finish before giving up and putting delivery in the background.
5954 Mutt interprets the value of this variable as follows:
5956 </p><div class="variablelist"><dl><dt><span class="term">>0 </span></dt><dd><p>number of seconds to wait for sendmail to finish before continuing
5957 </p></dd><dt><span class="term">0 </span></dt><dd><p>wait forever for sendmail to finish
5958 </p></dd><dt><span class="term"><0 </span></dt><dd><p>always put sendmail in the background without waiting
5959 </p></dd></dl></div><p>
5960 Note that if you specify a value other than 0, the output of the child
5961 process will be put in a temporary file. If there is some error, you
5962 will be informed as to where to find the output.
5963 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="shell"></a>3.262. shell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5964 Default: (empty)</p></div><p>
5965 Command to use when spawning a subshell. By default, the user's login
5966 shell from <code class="literal">/etc/passwd</code> is used.
5967 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-dashes"></a>3.263. sig_dashes</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5968 Default: yes</p></div><p>
5969 If <span class="emphasis"><em>set</em></span>, a line containing “<span class="quote">-- </span>” (note the trailing space) will be inserted before your
5970 <a class="link" href="#signature" title="3.265. signature">$signature</a>. It is <span class="bold"><strong>strongly</strong></span> recommended that you not <span class="emphasis"><em>unset</em></span>
5971 this variable unless your signature contains just your name. The
5972 reason for this is because many software packages use “<span class="quote">-- \n</span>” to
5973 detect your signature. For example, Mutt has the ability to highlight
5974 the signature in a different color in the builtin pager.
5975 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-on-top"></a>3.264. sig_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5976 Default: no</p></div><p>
5977 If <span class="emphasis"><em>set</em></span>, the signature will be included before any quoted or forwarded
5978 text. It is <span class="bold"><strong>strongly</strong></span> recommended that you do not set this variable
5979 unless you really know what you are doing, and are prepared to take
5980 some heat from netiquette guardians.
5981 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="signature"></a>3.265. signature</h3></div></div></div><div class="literallayout"><p>Type: path<br />
5982 Default: “<span class="quote"><code class="literal">˜/.signature</code></span>”</p></div><p>
5983 Specifies the filename of your signature, which is appended to all
5984 outgoing messages. If the filename ends with a pipe (“<span class="quote">|</span>”), it is
5985 assumed that filename is a shell command and input should be read from
5986 its standard output.
5987 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-search"></a>3.266. simple_search</h3></div></div></div><div class="literallayout"><p>Type: string<br />
5988 Default: “<span class="quote"><code class="literal">˜f %s | ˜s %s</code></span>”</p></div><p>
5989 Specifies how Mutt should expand a simple search into a real search
5990 pattern. A simple search is one that does not contain any of the “<span class="quote">˜</span>” pattern
5991 operators. See “<span class="quote"><a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>” for more information on search patterns.
5993 For example, if you simply type “<span class="quote">joe</span>” at a search or limit prompt, Mutt
5994 will automatically expand it to the value specified by this variable by
5995 replacing “<span class="quote">%s</span>” with the supplied string.
5996 For the default value, “<span class="quote">joe</span>” would be expanded to: “<span class="quote">˜f joe | ˜s joe</span>”.
5997 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smart-wrap"></a>3.267. smart_wrap</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
5998 Default: yes</p></div><p>
5999 Controls the display of lines longer than the screen width in the
6000 internal pager. If <span class="emphasis"><em>set</em></span>, long lines are wrapped at a word boundary. If
6001 <span class="emphasis"><em>unset</em></span>, lines are simply wrapped at the screen edge. Also see the
6002 <a class="link" href="#markers" title="3.114. markers">$markers</a> variable.
6003 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smileys"></a>3.268. smileys</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
6004 Default: “<span class="quote"><code class="literal">(>From )|(:[-^]?[][)(><}{|/DP])</code></span>”</p></div><p>
6005 The <span class="emphasis"><em>pager</em></span> uses this variable to catch some common false
6006 positives of <a class="link" href="#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a>, most notably smileys and not consider
6007 a line quoted text if it also matches <a class="link" href="#smileys" title="3.268. smileys">$smileys</a>. This mostly
6008 happens at the beginning of a line.
6009 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sleep-time"></a>3.269. sleep_time</h3></div></div></div><div class="literallayout"><p>Type: number<br />
6010 Default: 1</p></div><p>
6011 Specifies time, in seconds, to pause while displaying certain informational
6012 messages, while moving from folder to folder and after expunging
6013 messages from the current folder. The default is to pause one second, so
6014 a value of zero for this option suppresses the pause.
6015 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-authenticators"></a>3.270. smtp_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6016 Default: (empty)</p></div><p>
6017 This is a colon-delimited list of authentication methods mutt may
6018 attempt to use to log in to an SMTP server, in the order mutt should
6019 try them. Authentication methods are any SASL mechanism, eg
6020 “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
6021 This option is case-insensitive. If it is “<span class="quote">unset</span>”
6022 (the default) mutt will try all available methods, in order from
6023 most-secure to least-secure.
6027 </p><pre class="screen">
6028 set smtp_authenticators="digest-md5:cram-md5"
6030 </pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-pass"></a>3.271. smtp_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6031 Default: (empty)</p></div><p>
6032 Specifies the password for your SMTP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
6033 prompt you for your password when you first send mail via SMTP.
6034 See <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a> to configure mutt to send mail via SMTP.
6036 <span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
6037 fairly secure machine, because the superuser can read your muttrc even
6038 if you are the only one who can read the file.
6039 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-url"></a>3.272. smtp_url</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6040 Default: (empty)</p></div><p>
6041 Defines the SMTP smarthost where sent messages should relayed for
6042 delivery. This should take the form of an SMTP URL, eg:
6044 </p><pre class="screen">
6045 smtp[s]://[user[:pass]@]host[:port]/
6048 \.\.\. where “<span class="quote">[...]</span>” denotes an optional part.
6049 Setting this variable overrides the value of the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a>
6051 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort"></a>3.273. sort</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
6052 Default: date</p></div><p>
6053 Specifies how to sort messages in the “<span class="quote">index</span>” menu. Valid values
6056 </p><div class="itemizedlist"><ul type="disc"><li><p>date or date-sent
6057 </p></li><li><p>date-received
6058 </p></li><li><p>from
6059 </p></li><li><p>mailbox-order (unsorted)
6060 </p></li><li><p>score
6061 </p></li><li><p>size
6062 </p></li><li><p>spam
6063 </p></li><li><p>subject
6064 </p></li><li><p>threads
6066 </p></li></ul></div><p>
6067 You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
6068 order (example: “<span class="quote"><code class="literal">set sort=reverse-date-sent</code></span>”).
6070 <span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
6071 “<span class="quote">threads</span>” in /etc/Muttrc.
6072 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-alias"></a>3.274. sort_alias</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
6073 Default: alias</p></div><p>
6074 Specifies how the entries in the “<span class="quote">alias</span>” menu are sorted. The
6075 following are legal values:
6077 </p><div class="itemizedlist"><ul type="disc"><li><p>address (sort alphabetically by email address)
6078 </p></li><li><p>alias (sort alphabetically by alias name)
6079 </p></li><li><p>unsorted (leave in order specified in .muttrc)
6080 </p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-aux"></a>3.275. sort_aux</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
6081 Default: date</p></div><p>
6082 When sorting by threads, this variable controls how threads are sorted
6083 in relation to other threads, and how the branches of the thread trees
6084 are sorted. This can be set to any value that <a class="link" href="#sort" title="3.273. sort">$sort</a> can, except
6085 “<span class="quote">threads</span>” (in that case, mutt will just use “<span class="quote">date-sent</span>”). You can also
6086 specify the “<span class="quote">last-</span>” prefix in addition to the “<span class="quote">reverse-</span>” prefix, but “<span class="quote">last-</span>”
6087 must come after “<span class="quote">reverse-</span>”. The “<span class="quote">last-</span>” prefix causes messages to be
6088 sorted against its siblings by which has the last descendant, using
6089 the rest of <a class="link" href="#sort-aux" title="3.275. sort_aux">$sort_aux</a> as an ordering. For instance,
6091 </p><pre class="screen">
6092 set sort_aux=last-date-received
6095 would mean that if a new message is received in a
6096 thread, that thread becomes the last one displayed (or the first, if
6097 you have “<span class="quote"><code class="literal">set sort=reverse-threads</code></span>”.)
6099 Note: For reversed <a class="link" href="#sort" title="3.273. sort">$sort</a>
6100 order <a class="link" href="#sort-aux" title="3.275. sort_aux">$sort_aux</a> is reversed again (which is not the right thing to do,
6101 but kept to not break any existing configuration setting).
6102 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-browser"></a>3.276. sort_browser</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
6103 Default: alpha</p></div><p>
6104 Specifies how to sort entries in the file browser. By default, the
6105 entries are sorted alphabetically. Valid values:
6107 </p><div class="itemizedlist"><ul type="disc"><li><p>alpha (alphabetically)
6108 </p></li><li><p>date
6109 </p></li><li><p>size
6110 </p></li><li><p>unsorted
6111 </p></li></ul></div><p>
6112 You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
6113 order (example: “<span class="quote"><code class="literal">set sort_browser=reverse-date</code></span>”).
6114 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-re"></a>3.277. sort_re</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6115 Default: yes</p></div><p>
6116 This variable is only useful when sorting by threads with
6117 <a class="link" href="#strict-threads" title="3.283. strict_threads">$strict_threads</a> <span class="emphasis"><em>unset</em></span>. In that case, it changes the heuristic
6118 mutt uses to thread messages by subject. With <a class="link" href="#sort-re" title="3.277. sort_re">$sort_re</a> <span class="emphasis"><em>set</em></span>, mutt will
6119 only attach a message as the child of another message by subject if
6120 the subject of the child message starts with a substring matching the
6121 setting of <a class="link" href="#reply-regexp" title="3.243. reply_regexp">$reply_regexp</a>. With <a class="link" href="#sort-re" title="3.277. sort_re">$sort_re</a> <span class="emphasis"><em>unset</em></span>, mutt will attach
6122 the message whether or not this is the case, as long as the
6123 non-<a class="link" href="#reply-regexp" title="3.243. reply_regexp">$reply_regexp</a> parts of both messages are identical.
6124 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spam-separator"></a>3.278. spam_separator</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6125 Default: “<span class="quote"><code class="literal">,</code></span>”</p></div><p>
6126 This variable controls what happens when multiple spam headers
6127 are matched: if <span class="emphasis"><em>unset</em></span>, each successive header will overwrite any
6128 previous matches value for the spam label. If <span class="emphasis"><em>set</em></span>, each successive
6129 match will append to the previous, using this variable's value as a
6131 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spoolfile"></a>3.279. spoolfile</h3></div></div></div><div class="literallayout"><p>Type: path<br />
6132 Default: (empty)</p></div><p>
6133 If your spool mailbox is in a non-default place where Mutt cannot find
6134 it, you can specify its location with this variable. Mutt will
6135 automatically set this variable to the value of the environment
6136 variable <code class="literal">$MAIL</code> if it is not set.
6137 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-chars"></a>3.280. status_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6138 Default: “<span class="quote"><code class="literal">-*%A</code></span>”</p></div><p>
6139 Controls the characters used by the “<span class="quote">%r</span>” indicator in
6140 <a class="link" href="#status-format" title="3.281. status_format">$status_format</a>. The first character is used when the mailbox is
6141 unchanged. The second is used when the mailbox has been changed, and
6142 it needs to be resynchronized. The third is used if the mailbox is in
6143 read-only mode, or if the mailbox will not be written when exiting
6144 that mailbox (You can toggle whether to write changes to a mailbox
6145 with the <code class="literal"><toggle-write></code> operation, bound by default to “<span class="quote">%</span>”). The fourth
6146 is used to indicate that the current folder has been opened in attach-
6147 message mode (Certain operations like composing a new mail, replying,
6148 forwarding, etc. are not permitted in this mode).
6149 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-format"></a>3.281. status_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6150 Default: “<span class="quote"><code class="literal">-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---</code></span>”</p></div><p>
6151 Controls the format of the status line displayed in the “<span class="quote">index</span>”
6152 menu. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but has its own
6153 set of <code class="literal">printf(3)</code>-like sequences:
6155 </p><div class="variablelist"><dl><dt><span class="term">%b </span></dt><dd><p>number of mailboxes with new mail *
6156 </p></dd><dt><span class="term">%d </span></dt><dd><p>number of deleted messages *
6157 </p></dd><dt><span class="term">%f </span></dt><dd><p>the full pathname of the current mailbox
6158 </p></dd><dt><span class="term">%F </span></dt><dd><p>number of flagged messages *
6159 </p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
6160 </p></dd><dt><span class="term">%l </span></dt><dd><p>size (in bytes) of the current mailbox *
6161 </p></dd><dt><span class="term">%L </span></dt><dd><p>size (in bytes) of the messages shown
6162 (i.e., which match the current limit) *
6163 </p></dd><dt><span class="term">%m </span></dt><dd><p>the number of messages in the mailbox *
6164 </p></dd><dt><span class="term">%M </span></dt><dd><p>the number of messages shown (i.e., which match the current limit) *
6165 </p></dd><dt><span class="term">%n </span></dt><dd><p>number of new messages in the mailbox *
6166 </p></dd><dt><span class="term">%o </span></dt><dd><p>number of old unread messages *
6167 </p></dd><dt><span class="term">%p </span></dt><dd><p>number of postponed messages *
6168 </p></dd><dt><span class="term">%P </span></dt><dd><p>percentage of the way through the index
6169 </p></dd><dt><span class="term">%r </span></dt><dd><p>modified/read-only/won't-write/attach-message indicator,
6170 according to <a class="link" href="#status-chars" title="3.280. status_chars">$status_chars</a>
6171 </p></dd><dt><span class="term">%s </span></dt><dd><p>current sorting mode (<a class="link" href="#sort" title="3.273. sort">$sort</a>)
6172 </p></dd><dt><span class="term">%S </span></dt><dd><p>current aux sorting method (<a class="link" href="#sort-aux" title="3.275. sort_aux">$sort_aux</a>)
6173 </p></dd><dt><span class="term">%t </span></dt><dd><p>number of tagged messages *
6174 </p></dd><dt><span class="term">%u </span></dt><dd><p>number of unread messages *
6175 </p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
6176 </p></dd><dt><span class="term">%V </span></dt><dd><p>currently active limit pattern, if any *
6177 </p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
6178 </p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
6179 </p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
6180 </p></dd></dl></div><p>
6181 For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
6183 * = can be optionally printed if nonzero
6185 Some of the above sequences can be used to optionally print a string
6186 if their value is nonzero. For example, you may only want to see the
6187 number of flagged messages if such messages exist, since zero is not
6188 particularly meaningful. To optionally print a string based upon one
6189 of the above sequences, the following construct is used:
6191 <code class="literal">%?<sequence_char>?<optional_string>?</code>
6193 where <span class="emphasis"><em>sequence_char</em></span> is a character from the table above, and
6194 <span class="emphasis"><em>optional_string</em></span> is the string you would like printed if
6195 <span class="emphasis"><em>sequence_char</em></span> is nonzero. <span class="emphasis"><em>optional_string</em></span> <span class="bold"><strong>may</strong></span> contain
6196 other sequences as well as normal text, but you may <span class="bold"><strong>not</strong></span> nest
6199 Here is an example illustrating how to optionally print the number of
6200 new messages in a mailbox:
6202 <code class="literal">%?n?%n new messages.?</code>
6204 You can also switch between two strings using the following construct:
6206 <code class="literal">%?<sequence_char>?<if_string>&<else_string>?</code>
6208 If the value of <span class="emphasis"><em>sequence_char</em></span> is non-zero, <span class="emphasis"><em>if_string</em></span> will
6209 be expanded, otherwise <span class="emphasis"><em>else_string</em></span> will be expanded.
6211 You can force the result of any <code class="literal">printf(3)</code>-like sequence to be lowercase
6212 by prefixing the sequence character with an underscore (“<span class="quote">_</span>”) sign.
6213 For example, if you want to display the local hostname in lowercase,
6214 you would use: “<span class="quote"><code class="literal">%_h</code></span>”.
6216 If you prefix the sequence character with a colon (“<span class="quote">:</span>”) character, mutt
6217 will replace any dots in the expansion by underscores. This might be helpful
6218 with IMAP folders that don't like dots in folder names.
6219 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-on-top"></a>3.282. status_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6220 Default: no</p></div><p>
6221 Setting this variable causes the “<span class="quote">status bar</span>” to be displayed on
6222 the first line of the screen rather than near the bottom. If <a class="link" href="#help" title="3.70. help">$help</a>
6223 is <span class="emphasis"><em>set</em></span>, too it'll be placed at the bottom.
6224 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="strict-threads"></a>3.283. strict_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6225 Default: no</p></div><p>
6226 If <span class="emphasis"><em>set</em></span>, threading will only make use of the “<span class="quote">In-Reply-To</span>” and
6227 “<span class="quote">References:</span>” fields when you <a class="link" href="#sort" title="3.273. sort">$sort</a> by message threads. By
6228 default, messages with the same subject are grouped together in
6229 “<span class="quote">pseudo threads.</span>”. This may not always be desirable, such as in a
6230 personal mailbox where you might have several unrelated messages with
6231 the subjects like “<span class="quote">hi</span>” which will get grouped together. See also
6232 <a class="link" href="#sort-re" title="3.277. sort_re">$sort_re</a> for a less drastic way of controlling this
6234 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="suspend"></a>3.284. suspend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6235 Default: yes</p></div><p>
6236 When <span class="emphasis"><em>unset</em></span>, mutt won't stop when the user presses the terminal's
6237 <span class="emphasis"><em>susp</em></span> key, usually “<span class="quote">^Z</span>”. This is useful if you run mutt
6238 inside an xterm using a command like “<span class="quote"><code class="literal">xterm -e mutt</code></span>”.
6239 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="text-flowed"></a>3.285. text_flowed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6240 Default: no</p></div><p>
6241 When <span class="emphasis"><em>set</em></span>, mutt will generate “<span class="quote">format=flowed</span>” bodies with a content type
6242 of “<span class="quote"><code class="literal">text/plain; format=flowed</code></span>”.
6243 This format is easier to handle for some mailing software, and generally
6244 just looks like ordinary text. To actually make use of this format's
6245 features, you'll need support in your editor.
6247 Note that <a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a> is ignored when this option is <span class="emphasis"><em>set</em></span>.
6248 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thread-received"></a>3.286. thread_received</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6249 Default: no</p></div><p>
6250 When <span class="emphasis"><em>set</em></span>, mutt uses the date received rather than the date sent
6251 to thread messages by subject.
6252 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thorough-search"></a>3.287. thorough_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6253 Default: no</p></div><p>
6254 Affects the <code class="literal">˜b</code> and <code class="literal">˜h</code> search operations described in
6255 section “<span class="quote"><a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>”. If <span class="emphasis"><em>set</em></span>, the headers and body/attachments of
6256 messages to be searched are decoded before searching. If <span class="emphasis"><em>unset</em></span>,
6257 messages are searched as they appear in the folder.
6259 Users searching attachments or for non-ASCII characters should <span class="emphasis"><em>set</em></span>
6260 this value because decoding also includes MIME parsing/decoding and possible
6261 character set conversions. Otherwise mutt will attempt to match against the
6262 raw message received (for example quoted-printable encoded or with encoded
6263 headers) which may lead to incorrect search results.
6264 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tilde"></a>3.288. tilde</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6265 Default: no</p></div><p>
6266 When <span class="emphasis"><em>set</em></span>, the internal-pager will pad blank lines to the bottom of the
6267 screen with a tilde (“<span class="quote">˜</span>”).
6268 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="time-inc"></a>3.289. time_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
6269 Default: 0</p></div><p>
6270 Along with <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a>, and <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a>, this
6271 variable controls the frequency with which progress updates are
6272 displayed. It suppresses updates less than <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> milliseconds
6273 apart. This can improve throughput on systems with slow terminals,
6274 or when running mutt on a remote system.
6276 Also see the “<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
6277 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="timeout"></a>3.290. timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
6278 Default: 600</p></div><p>
6279 When Mutt is waiting for user input either idleing in menus or
6280 in an interactive prompt, Mutt would block until input is
6281 present. Depending on the context, this would prevent certain
6282 operations from working, like checking for new mail or keeping
6283 an IMAP connection alive.
6285 This variable controls how many seconds Mutt will at most wait
6286 until it aborts waiting for input, performs these operations and
6287 continues to wait for input.
6289 A value of zero or less will cause Mutt to never time out.
6290 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tmpdir"></a>3.291. tmpdir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
6291 Default: (empty)</p></div><p>
6292 This variable allows you to specify where Mutt will place its
6293 temporary files needed for displaying and composing messages. If
6294 this variable is not set, the environment variable <code class="literal">$TMPDIR</code> is
6295 used. If <code class="literal">$TMPDIR</code> is not set then “<span class="quote"><code class="literal">/tmp</code></span>” is used.
6296 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="to-chars"></a>3.292. to_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6297 Default: “<span class="quote"><code class="literal"> +TCFL</code></span>”</p></div><p>
6298 Controls the character used to indicate mail addressed to you. The
6299 first character is the one used when the mail is <span class="emphasis"><em>not</em></span> addressed to your
6300 address. The second is used when you are the only
6301 recipient of the message. The third is when your address
6302 appears in the “<span class="quote">To:</span>” header field, but you are not the only recipient of
6303 the message. The fourth character is used when your
6304 address is specified in the “<span class="quote">Cc:</span>” header field, but you are not the only
6305 recipient. The fifth character is used to indicate mail that was sent
6306 by <span class="emphasis"><em>you</em></span>. The sixth character is used to indicate when a mail
6307 was sent to a mailing-list you subscribe to.
6308 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="trash"></a>3.293. trash</h3></div></div></div><div class="literallayout"><p>Type: path<br />
6309 Default: (empty)</p></div><p>
6310 If set, this variable specifies the path of the trash folder where the
6311 mails marked for deletion will be moved, instead of being irremediably
6314 NOTE: When you delete a message in the trash folder, it is really
6315 deleted, so that you have a way to clean the trash.
6316 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tunnel"></a>3.294. tunnel</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6317 Default: (empty)</p></div><p>
6318 Setting this variable will cause mutt to open a pipe to a command
6319 instead of a raw socket. You may be able to use this to set up
6320 preauthenticated connections to your IMAP/POP3/SMTP server. Example:
6322 </p><pre class="screen">
6323 set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
6326 Note: For this example to work you must be able to log in to the remote
6327 machine without having to enter a password.
6328 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-8bitmime"></a>3.295. use_8bitmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6329 Default: no</p></div><p>
6330 <span class="bold"><strong>Warning:</strong></span> do not set this variable unless you are using a version
6331 of sendmail which supports the <code class="literal">-B8BITMIME</code> flag (such as sendmail
6332 8.8.x) or you may not be able to send mail.
6334 When <span class="emphasis"><em>set</em></span>, Mutt will invoke <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> with the <code class="literal">-B8BITMIME</code>
6335 flag when sending 8-bit messages to enable ESMTP negotiation.
6336 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-domain"></a>3.296. use_domain</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6337 Default: yes</p></div><p>
6338 When <span class="emphasis"><em>set</em></span>, Mutt will qualify all local addresses (ones without the
6339 “<span class="quote">@host</span>” portion) with the value of <a class="link" href="#hostname" title="3.80. hostname">$hostname</a>. If <span class="emphasis"><em>unset</em></span>, no
6340 addresses will be qualified.
6341 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-envelope-from"></a>3.297. use_envelope_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6342 Default: no</p></div><p>
6343 When <span class="emphasis"><em>set</em></span>, mutt will set the <span class="emphasis"><em>envelope</em></span> sender of the message.
6344 If <a class="link" href="#envelope-from-address" title="3.53. envelope_from_address">$envelope_from_address</a> is <span class="emphasis"><em>set</em></span>, it will be used as the sender
6345 address. If <span class="emphasis"><em>unset</em></span>, mutt will attempt to derive the sender from the
6346 “<span class="quote">From:</span>” header.
6348 Note that this information is passed to sendmail command using the
6349 <code class="literal">-f</code> command line switch. Therefore setting this option is not useful
6350 if the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> variable already contains <code class="literal">-f</code> or if the
6351 executable pointed to by <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> doesn't support the <code class="literal">-f</code> switch.
6352 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-from"></a>3.298. use_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6353 Default: yes</p></div><p>
6354 When <span class="emphasis"><em>set</em></span>, Mutt will generate the “<span class="quote">From:</span>” header field when
6355 sending messages. If <span class="emphasis"><em>unset</em></span>, no “<span class="quote">From:</span>” header field will be
6356 generated unless the user explicitly sets one using the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
6358 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-idn"></a>3.299. use_idn</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6359 Default: yes</p></div><p>
6360 When <span class="emphasis"><em>set</em></span>, Mutt will show you international domain names decoded.
6361 Note: You can use IDNs for addresses even if this is <span class="emphasis"><em>unset</em></span>.
6362 This variable only affects decoding.
6363 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-ipv6"></a>3.300. use_ipv6</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6364 Default: yes</p></div><p>
6365 When <span class="emphasis"><em>set</em></span>, Mutt will look for IPv6 addresses of hosts it tries to
6366 contact. If this option is <span class="emphasis"><em>unset</em></span>, Mutt will restrict itself to IPv4 addresses.
6367 Normally, the default should work.
6368 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="user-agent"></a>3.301. user_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6369 Default: yes</p></div><p>
6370 When <span class="emphasis"><em>set</em></span>, mutt will add a “<span class="quote">User-Agent:</span>” header to outgoing
6371 messages, indicating which version of mutt was used for composing
6373 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="visual"></a>3.302. visual</h3></div></div></div><div class="literallayout"><p>Type: path<br />
6374 Default: (empty)</p></div><p>
6375 Specifies the visual editor to invoke when the “<span class="quote"><code class="literal">˜v</code></span>” command is
6376 given in the builtin editor.
6377 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wait-key"></a>3.303. wait_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6378 Default: yes</p></div><p>
6379 Controls whether Mutt will ask you to press a key after an external command
6380 has been invoked by these functions: <code class="literal"><shell-escape></code>,
6381 <code class="literal"><pipe-message></code>, <code class="literal"><pipe-entry></code>, <code class="literal"><print-message></code>,
6382 and <code class="literal"><print-entry></code> commands.
6384 It is also used when viewing attachments with “<span class="quote"><a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a></span>”, provided
6385 that the corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag,
6386 and the external program is interactive.
6388 When <span class="emphasis"><em>set</em></span>, Mutt will always ask for a key. When <span class="emphasis"><em>unset</em></span>, Mutt will wait
6389 for a key only if the external command returned a non-zero status.
6390 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="weed"></a>3.304. weed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6391 Default: yes</p></div><p>
6392 When <span class="emphasis"><em>set</em></span>, mutt will weed headers when displaying, forwarding,
6393 printing, or replying to messages.
6394 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap"></a>3.305. wrap</h3></div></div></div><div class="literallayout"><p>Type: number<br />
6395 Default: 0</p></div><p>
6396 When set to a positive value, mutt will wrap text at <a class="link" href="#wrap" title="3.305. wrap">$wrap</a> characters.
6397 When set to a negative value, mutt will wrap text so that there are <a class="link" href="#wrap" title="3.305. wrap">$wrap</a>
6398 characters of empty space on the right side of the terminal.
6399 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap-search"></a>3.306. wrap_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6400 Default: yes</p></div><p>
6401 Controls whether searches wrap around the end.
6403 When <span class="emphasis"><em>set</em></span>, searches will wrap around the first (or last) item. When
6404 <span class="emphasis"><em>unset</em></span>, incremental searches will not wrap.
6405 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrapmargin"></a>3.307. wrapmargin</h3></div></div></div><div class="literallayout"><p>Type: number<br />
6406 Default: 0</p></div><p>
6407 (DEPRECATED) Equivalent to setting <a class="link" href="#wrap" title="3.305. wrap">$wrap</a> with a negative value.
6408 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-inc"></a>3.308. write_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
6409 Default: 10</p></div><p>
6410 When writing a mailbox, a message will be printed every
6411 <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a> messages to indicate progress. If set to 0, only a
6412 single message will be displayed before writing a mailbox.
6414 Also see the <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> variables and the
6415 “<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
6416 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-bcc"></a>3.309. write_bcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6417 Default: yes</p></div><p>
6418 Controls whether mutt writes out the “<span class="quote">Bcc:</span>” header when preparing
6419 messages to be sent. Exim users may wish to unset this. If mutt
6420 is set to deliver directly via SMTP (see <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a>), this
6421 option does nothing: mutt will never write out the “<span class="quote">Bcc:</span>” header
6424 <span class="bold"><strong>Note:</strong></span> On Debian systems, exim4 and postfix strip BCC headers by
6425 default. The above warning applies to exim3 users, see /etc/Muttrc.
6426 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-icon"></a>3.310. xterm_icon</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6427 Default: “<span class="quote"><code class="literal">M%?n?AIL&ail?</code></span>”</p></div><p>
6428 Controls the format of the icon title, as long as xterm_set_titles
6429 is enabled. This string is identical in formatting to the one used by
6430 “<span class="quote"><a class="link" href="#status-format" title="3.281. status_format">$status_format</a></span>”.
6431 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-set-titles"></a>3.311. xterm_set_titles</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
6432 Default: no</p></div><p>
6433 Controls whether mutt sets the xterm title bar and icon name
6434 (as long as you are in an appropriate terminal).
6435 </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-title"></a>3.312. xterm_title</h3></div></div></div><div class="literallayout"><p>Type: string<br />
6436 Default: “<span class="quote"><code class="literal">Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</code></span>”</p></div><p>
6437 Controls the format of the title bar of the xterm provided that
6438 xterm_set_titles has been set. This string is identical in formatting
6439 to the one used by “<span class="quote"><a class="link" href="#status-format" title="3.281. status_format">$status_format</a></span>”.
6440 </p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="functions"></a>4. Functions</h2></div></div></div><p>
6441 The following is the list of available functions listed by the mapping
6442 in which they are available. The default key setting is given, and an
6443 explanation of what the function does. The key bindings of these
6444 functions can be changed with the <a class="link" href="#bind" title="5. Changing the default key bindings">bind</a>
6446 </p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="generic_map"></a>4.1. generic menu</h3></div></div></div><p>
6447 The <span class="emphasis"><em>generic</em></span> menu is not a real menu, but specifies common functions
6448 (such as movement) available in all menus except for <span class="emphasis"><em>pager</em></span> and
6449 <span class="emphasis"><em>editor</em></span>. Changing settings for this menu will affect the default
6450 bindings for all menus (except as noted).
6451 </p><div class="table"><a id="generic_table"></a><p class="title"><b>Table 8.2. Default generic function bindings</b></p><div class="table-contents"><table summary="Default generic function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><top-page></code></td><td>H</td><td>move to the top of the page</td></tr><tr><td><code class="literal"><next-entry></code></td><td>j</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>k</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><bottom-page></code></td><td>L</td><td>move to the bottom of the page</td></tr><tr><td><code class="literal"><refresh></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><middle-page></code></td><td>M</td><td>move to the middle of the page</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><tag-entry></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><next-page></code></td><td>z</td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>Z</td><td>move to the previous page</td></tr><tr><td><code class="literal"><last-entry></code></td><td>*</td><td>move to the last entry</td></tr><tr><td><code class="literal"><first-entry></code></td><td>=</td><td>move to the first entry</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><next-line></code></td><td>></td><td>scroll down one line</td></tr><tr><td><code class="literal"><previous-line></code></td><td><</td><td>scroll up one line</td></tr><tr><td><code class="literal"><half-up></code></td><td>[</td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td>]</td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><tag-prefix></code></td><td>;</td><td>apply next function to tagged messages</td></tr><tr><td><code class="literal"><tag-prefix-cond></code></td><td> </td><td>apply next function ONLY to tagged messages</td></tr><tr><td><code class="literal"><end-cond></code></td><td> </td><td>end of conditional execution (noop)</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><select-entry></code></td><td><Return></td><td>select the current entry</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><current-top></code></td><td> </td><td>move entry to top of screen</td></tr><tr><td><code class="literal"><current-middle></code></td><td> </td><td>move entry to middle of screen</td></tr><tr><td><code class="literal"><current-bottom></code></td><td> </td><td>move entry to bottom of screen</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index_map"></a>4.2. index menu</h3></div></div></div><div class="table"><a id="index_table"></a><p class="title"><b>Table 8.3. Default index function bindings</b></p><div class="table-contents"><table summary="Default index function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><collapse-thread></code></td><td>Esc v</td><td>collapse/uncollapse current thread</td></tr><tr><td><code class="literal"><collapse-all></code></td><td>Esc V</td><td>collapse/uncollapse all threads</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-pattern></code></td><td>D</td><td>delete messages matching a pattern</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><fetch-mail></code></td><td>G</td><td>retrieve mail from POP server</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><limit></code></td><td>l</td><td>show only messages matching a pattern</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><toggle-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><toggle-write></code></td><td>%</td><td>toggle whether the mailbox will be rewritten</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><quit></code></td><td>q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><show-limit></code></td><td>Esc l</td><td>show currently active limit pattern</td></tr><tr><td><code class="literal"><sort-mailbox></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><tag-pattern></code></td><td>T</td><td>tag messages matching a pattern</td></tr><tr><td><code class="literal"><tag-subthread></code></td><td> </td><td>tag the current subthread</td></tr><tr><td><code class="literal"><tag-thread></code></td><td>Esc t</td><td>tag the current thread</td></tr><tr><td><code class="literal"><untag-pattern></code></td><td>^T</td><td>untag messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-pattern></code></td><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><set-flag></code></td><td>w</td><td>set a status flag on a message</td></tr><tr><td><code class="literal"><clear-flag></code></td><td>W</td><td>clear a status flag from a message</td></tr><tr><td><code class="literal"><display-message></code></td><td><Return></td><td>display a message</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><next-new-then-unread></code></td><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-new-then-unread></code></td><td>Esc <Tab></td><td>jump to the previous new or unread message</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><sidebar-scroll-up></code></td><td> </td><td>scroll the mailbox pane up 1 page</td></tr><tr><td><code class="literal"><sidebar-scroll-down></code></td><td> </td><td>scroll the mailbox pane down 1 page</td></tr><tr><td><code class="literal"><sidebar-next></code></td><td> </td><td>go down to next mailbox</td></tr><tr><td><code class="literal"><sidebar-prev></code></td><td> </td><td>go to previous mailbox</td></tr><tr><td><code class="literal"><sidebar-open></code></td><td> </td><td>open hilighted mailbox</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager_map"></a>4.3. pager menu</h3></div></div></div><div class="table"><a id="pager_table"></a><p class="title"><b>Table 8.4. Default pager function bindings</b></p><div class="table-contents"><table summary="Default pager function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><next-entry></code></td><td>J</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>K</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><redraw-screen></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><mark-as-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><quit></code></td><td>Q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><skip-quoted></code></td><td>S</td><td>skip beyond quoted text</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><tag-message></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><toggle-quoted></code></td><td>T</td><td>toggle display of quoted text</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><search-toggle></code></td><td>\\</td><td>toggle search pattern coloring</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><next-page></code></td><td><Space></td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>-</td><td>move to the previous page</td></tr><tr><td><code class="literal"><top></code></td><td>^</td><td>jump to the top of the message</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><next-line></code></td><td><Return></td><td>scroll down one line</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><half-up></code></td><td> </td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td> </td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><previous-line></code></td><td> </td><td>scroll up one line</td></tr><tr><td><code class="literal"><bottom></code></td><td> </td><td>jump to the bottom of the message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr><tr><td><code class="literal"><sidebar-scroll-up></code></td><td> </td><td>scroll the mailbox pane up 1 page</td></tr><tr><td><code class="literal"><sidebar-scroll-down></code></td><td> </td><td>scroll the mailbox pane down 1 page</td></tr><tr><td><code class="literal"><sidebar-next></code></td><td> </td><td>go down to next mailbox</td></tr><tr><td><code class="literal"><sidebar-prev></code></td><td> </td><td>go to previous mailbox</td></tr><tr><td><code class="literal"><sidebar-open></code></td><td> </td><td>open hilighted mailbox</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias_map"></a>4.4. alias menu</h3></div></div></div><div class="table"><a id="alias_table"></a><p class="title"><b>Table 8.5. Default alias function bindings</b></p><div class="table-contents"><table summary="Default alias function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query_map"></a>4.5. query menu</h3></div></div></div><div class="table"><a id="query_table"></a><p class="title"><b>Table 8.6. Default query function bindings</b></p><div class="table-contents"><table summary="Default query function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><query-append></code></td><td>A</td><td>append new query results to current results</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach_map"></a>4.6. attach menu</h3></div></div></div><div class="table"><a id="attach_table"></a><p class="title"><b>Table 8.7. Default attach function bindings</b></p><div class="table-contents"><table summary="Default attach function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><print-entry></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><save-entry></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><view-mailcap></code></td><td>m</td><td>force viewing of attachment using mailcap</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><view-text></code></td><td>T</td><td>view attachment as text</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><collapse-parts></code></td><td>v</td><td>Toggle display of subparts</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose_map"></a>4.7. compose menu</h3></div></div></div><div class="table"><a id="compose_table"></a><p class="title"><b>Table 8.8. Default compose function bindings</b></p><div class="table-contents"><table summary="Default compose function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><attach-file></code></td><td>a</td><td>attach file(s) to this message</td></tr><tr><td><code class="literal"><attach-message></code></td><td>A</td><td>attach message(s) to this message</td></tr><tr><td><code class="literal"><edit-bcc></code></td><td>b</td><td>edit the BCC list</td></tr><tr><td><code class="literal"><edit-cc></code></td><td>c</td><td>edit the CC list</td></tr><tr><td><code class="literal"><copy-file></code></td><td>C</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><detach-file></code></td><td>D</td><td>delete the current entry</td></tr><tr><td><code class="literal"><toggle-disposition></code></td><td>^D</td><td>toggle disposition between inline/attachment</td></tr><tr><td><code class="literal"><edit-description></code></td><td>d</td><td>edit attachment description</td></tr><tr><td><code class="literal"><edit-message></code></td><td>e</td><td>edit the message</td></tr><tr><td><code class="literal"><edit-headers></code></td><td>E</td><td>edit the message with headers</td></tr><tr><td><code class="literal"><edit-file></code></td><td>^X e</td><td>edit the file to be attached</td></tr><tr><td><code class="literal"><edit-encoding></code></td><td>^E</td><td>edit attachment transfer-encoding</td></tr><tr><td><code class="literal"><edit-from></code></td><td>Esc f</td><td>edit the from field</td></tr><tr><td><code class="literal"><edit-fcc></code></td><td>f</td><td>enter a file to save a copy of this message in</td></tr><tr><td><code class="literal"><filter-entry></code></td><td>F</td><td>filter attachment through a shell command</td></tr><tr><td><code class="literal"><get-attachment></code></td><td>G</td><td>get a temporary copy of an attachment</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><ispell></code></td><td>i</td><td>run ispell on the message</td></tr><tr><td><code class="literal"><print-entry></code></td><td>l</td><td>print the current entry</td></tr><tr><td><code class="literal"><edit-mime></code></td><td>m</td><td>edit attachment using mailcap entry</td></tr><tr><td><code class="literal"><new-mime></code></td><td>n</td><td>compose new attachment using mailcap entry</td></tr><tr><td><code class="literal"><postpone-message></code></td><td>P</td><td>save this message to send later</td></tr><tr><td><code class="literal"><edit-reply-to></code></td><td>r</td><td>edit the Reply-To field</td></tr><tr><td><code class="literal"><rename-file></code></td><td>R</td><td>rename/move an attached file</td></tr><tr><td><code class="literal"><edit-subject></code></td><td>s</td><td>edit the subject of this message</td></tr><tr><td><code class="literal"><edit-to></code></td><td>t</td><td>edit the TO list</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^T</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><write-fcc></code></td><td>w</td><td>write the message to a folder</td></tr><tr><td><code class="literal"><toggle-unlink></code></td><td>u</td><td>toggle whether to delete file after sending it</td></tr><tr><td><code class="literal"><toggle-recode></code></td><td> </td><td>toggle recoding of this attachment</td></tr><tr><td><code class="literal"><update-encoding></code></td><td>U</td><td>update an attachment's encoding info</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><send-message></code></td><td>y</td><td>send the message</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><attach-key></code></td><td>Esc k</td><td>attach a PGP public key</td></tr><tr><td><code class="literal"><pgp-menu></code></td><td>p</td><td>show PGP options</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><smime-menu></code></td><td>S</td><td>show S/MIME options</td></tr><tr><td><code class="literal"><mix></code></td><td>M</td><td>send the message through a mixmaster remailer chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone_map"></a>4.8. postpone menu</h3></div></div></div><div class="table"><a id="postpone_table"></a><p class="title"><b>Table 8.9. Default postpone function bindings</b></p><div class="table-contents"><table summary="Default postpone function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="browser_map"></a>4.9. browser menu</h3></div></div></div><div class="table"><a id="browser_table"></a><p class="title"><b>Table 8.10. Default browser function bindings</b></p><div class="table-contents"><table summary="Default browser function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><change-dir></code></td><td>c</td><td>change directories</td></tr><tr><td><code class="literal"><display-filename></code></td><td>@</td><td>display the currently selected file's name</td></tr><tr><td><code class="literal"><enter-mask></code></td><td>m</td><td>enter a file mask</td></tr><tr><td><code class="literal"><sort></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><select-new></code></td><td>N</td><td>select a new file in this directory</td></tr><tr><td><code class="literal"><check-new></code></td><td> </td><td>check mailboxes for new mail</td></tr><tr><td><code class="literal"><toggle-mailboxes></code></td><td><Tab></td><td>toggle whether to browse mailboxes or all files</td></tr><tr><td><code class="literal"><view-file></code></td><td><Space></td><td>view file</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><create-mailbox></code></td><td>C</td><td>create a new mailbox (IMAP only)</td></tr><tr><td><code class="literal"><delete-mailbox></code></td><td>d</td><td>delete the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><rename-mailbox></code></td><td>r</td><td>rename the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><subscribe></code></td><td>s</td><td>subscribe to current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><unsubscribe></code></td><td>u</td><td>unsubscribe from current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><toggle-subscribed></code></td><td>T</td><td>toggle view all/subscribed mailboxes (IMAP only)</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp_map"></a>4.10. pgp menu</h3></div></div></div><div class="table"><a id="pgp_table"></a><p class="title"><b>Table 8.11. Default pgp function bindings</b></p><div class="table-contents"><table summary="Default pgp function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime_map"></a>4.11. smime menu</h3></div></div></div><div class="table"><a id="smime_table"></a><p class="title"><b>Table 8.12. Default smime function bindings</b></p><div class="table-contents"><table summary="Default smime function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix_map"></a>4.12. mix menu</h3></div></div></div><div class="table"><a id="mix_table"></a><p class="title"><b>Table 8.13. Default mix function bindings</b></p><div class="table-contents"><table summary="Default mix function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><accept></code></td><td><Return></td><td>Accept the chain constructed</td></tr><tr><td><code class="literal"><append></code></td><td>a</td><td>Append a remailer to the chain</td></tr><tr><td><code class="literal"><insert></code></td><td>i</td><td>Insert a remailer into the chain</td></tr><tr><td><code class="literal"><delete></code></td><td>d</td><td>Delete a remailer from the chain</td></tr><tr><td><code class="literal"><chain-prev></code></td><td><Left></td><td>Select the previous element of the chain</td></tr><tr><td><code class="literal"><chain-next></code></td><td><Right></td><td>Select the next element of the chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor_map"></a>4.13. editor menu</h3></div></div></div><div class="table"><a id="editor_table"></a><p class="title"><b>Table 8.14. Default editor function bindings</b></p><div class="table-contents"><table summary="Default editor function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bol></code></td><td>^A</td><td>jump to the beginning of the line</td></tr><tr><td><code class="literal"><backward-char></code></td><td>^B</td><td>move the cursor one character to the left</td></tr><tr><td><code class="literal"><backward-word></code></td><td>Esc b</td><td>move the cursor to the beginning of the word</td></tr><tr><td><code class="literal"><capitalize-word></code></td><td>Esc c</td><td>capitalize the word</td></tr><tr><td><code class="literal"><downcase-word></code></td><td>Esc l</td><td>convert the word to lower case</td></tr><tr><td><code class="literal"><upcase-word></code></td><td>Esc u</td><td>convert the word to upper case</td></tr><tr><td><code class="literal"><delete-char></code></td><td>^D</td><td>delete the char under the cursor</td></tr><tr><td><code class="literal"><eol></code></td><td>^E</td><td>jump to the end of the line</td></tr><tr><td><code class="literal"><forward-char></code></td><td>^F</td><td>move the cursor one character to the right</td></tr><tr><td><code class="literal"><forward-word></code></td><td>Esc f</td><td>move the cursor to the end of the word</td></tr><tr><td><code class="literal"><backspace></code></td><td><Backspace></td><td>delete the char in front of the cursor</td></tr><tr><td><code class="literal"><kill-eol></code></td><td>^K</td><td>delete chars from cursor to end of line</td></tr><tr><td><code class="literal"><kill-eow></code></td><td>Esc d</td><td>delete chars from the cursor to the end of the word</td></tr><tr><td><code class="literal"><kill-line></code></td><td>^U</td><td>delete all chars on the line</td></tr><tr><td><code class="literal"><quote-char></code></td><td>^V</td><td>quote the next typed key</td></tr><tr><td><code class="literal"><kill-word></code></td><td>^W</td><td>delete the word in front of the cursor</td></tr><tr><td><code class="literal"><complete></code></td><td><Tab></td><td>complete filename or alias</td></tr><tr><td><code class="literal"><complete-query></code></td><td>^T</td><td>complete address with query</td></tr><tr><td><code class="literal"><buffy-cycle></code></td><td><Space></td><td>cycle among incoming mailboxes</td></tr><tr><td><code class="literal"><history-up></code></td><td> </td><td>scroll up through the history list</td></tr><tr><td><code class="literal"><history-down></code></td><td> </td><td>scroll down through the history list</td></tr><tr><td><code class="literal"><transpose-chars></code></td><td> </td><td>transpose character under cursor with previous</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="miscellany"></a>Chapter 9. Miscellany</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="#about">2. About this document</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="acknowledgements"></a>1. Acknowledgements</h2></div></div></div><p>
6452 Kari Hurtta <code class="email"><<a class="email" href="mailto:kari.hurtta@fmi.fi">kari.hurtta@fmi.fi</a>></code>
6453 co-developed the original MIME parsing code back in the ELM-ME days.
6455 The following people have been very helpful to the development of Mutt:
6456 </p><div class="itemizedlist"><ul type="disc"><li><p>Vikas Agnihotri <code class="email"><<a class="email" href="mailto:vikasa@writeme.com">vikasa@writeme.com</a>></code></p></li><li><p>Francois Berjon <code class="email"><<a class="email" href="mailto:Francois.Berjon@aar.alcatel-alsthom.fr">Francois.Berjon@aar.alcatel-alsthom.fr</a>></code></p></li><li><p>Aric Blumer <code class="email"><<a class="email" href="mailto:aric@fore.com">aric@fore.com</a>></code></p></li><li><p>John Capo <code class="email"><<a class="email" href="mailto:jc@irbs.com">jc@irbs.com</a>></code></p></li><li><p>David Champion <code class="email"><<a class="email" href="mailto:dgc@uchicago.edu">dgc@uchicago.edu</a>></code></p></li><li><p>Brendan Cully <code class="email"><<a class="email" href="mailto:brendan@kublai.com">brendan@kublai.com</a>></code></p></li><li><p>Liviu Daia <code class="email"><<a class="email" href="mailto:daia@stoilow.imar.ro">daia@stoilow.imar.ro</a>></code></p></li><li><p>Thomas E. Dickey <code class="email"><<a class="email" href="mailto:dickey@herndon4.his.com">dickey@herndon4.his.com</a>></code></p></li><li><p>David DeSimone <code class="email"><<a class="email" href="mailto:fox@convex.hp.com">fox@convex.hp.com</a>></code></p></li><li><p>Nickolay N. Dudorov <code class="email"><<a class="email" href="mailto:nnd@wint.itfs.nsk.su">nnd@wint.itfs.nsk.su</a>></code></p></li><li><p>Ruslan Ermilov <code class="email"><<a class="email" href="mailto:ru@freebsd.org">ru@freebsd.org</a>></code></p></li><li><p>Edmund Grimley Evans <code class="email"><<a class="email" href="mailto:edmundo@rano.org">edmundo@rano.org</a>></code></p></li><li><p>Michael Finken <code class="email"><<a class="email" href="mailto:finken@conware.de">finken@conware.de</a>></code></p></li><li><p>Sven Guckes <code class="email"><<a class="email" href="mailto:guckes@math.fu-berlin.de">guckes@math.fu-berlin.de</a>></code></p></li><li><p>Lars Hecking <code class="email"><<a class="email" href="mailto:lhecking@nmrc.ie">lhecking@nmrc.ie</a>></code></p></li><li><p>Mark Holloman <code class="email"><<a class="email" href="mailto:holloman@nando.net">holloman@nando.net</a>></code></p></li><li><p>Andreas Holzmann <code class="email"><<a class="email" href="mailto:holzmann@fmi.uni-passau.de">holzmann@fmi.uni-passau.de</a>></code></p></li><li><p>Marco d'Itri <code class="email"><<a class="email" href="mailto:md@linux.it">md@linux.it</a>></code></p></li><li><p>Björn Jacke <code class="email"><<a class="email" href="mailto:bjacke@suse.com">bjacke@suse.com</a>></code></p></li><li><p>Byrial Jensen <code class="email"><<a class="email" href="mailto:byrial@image.dk">byrial@image.dk</a>></code></p></li><li><p>David Jeske <code class="email"><<a class="email" href="mailto:jeske@igcom.net">jeske@igcom.net</a>></code></p></li><li><p>Christophe Kalt <code class="email"><<a class="email" href="mailto:kalt@hugo.int-evry.fr">kalt@hugo.int-evry.fr</a>></code></p></li><li><p>Tommi Komulainen <code class="email"><<a class="email" href="mailto:Tommi.Komulainen@iki.fi">Tommi.Komulainen@iki.fi</a>></code></p></li><li><p>Felix von Leitner (a.k.a “<span class="quote">Fefe</span>”) <code class="email"><<a class="email" href="mailto:leitner@math.fu-berlin.de">leitner@math.fu-berlin.de</a>></code></p></li><li><p>Brandon Long <code class="email"><<a class="email" href="mailto:blong@fiction.net">blong@fiction.net</a>></code></p></li><li><p>Jimmy Mäkelä <code class="email"><<a class="email" href="mailto:jmy@flashback.net">jmy@flashback.net</a>></code></p></li><li><p>Lars Marowsky-Bree <code class="email"><<a class="email" href="mailto:lmb@pointer.in-minden.de">lmb@pointer.in-minden.de</a>></code></p></li><li><p>Thomas “<span class="quote">Mike</span>” Michlmayr <code class="email"><<a class="email" href="mailto:mike@cosy.sbg.ac.at">mike@cosy.sbg.ac.at</a>></code></p></li><li><p>Andrew W. Nosenko <code class="email"><<a class="email" href="mailto:awn@bcs.zp.ua">awn@bcs.zp.ua</a>></code></p></li><li><p>David O'Brien <code class="email"><<a class="email" href="mailto:obrien@Nuxi.cs.ucdavis.edu">obrien@Nuxi.cs.ucdavis.edu</a>></code></p></li><li><p>Clint Olsen <code class="email"><<a class="email" href="mailto:olsenc@ichips.intel.com">olsenc@ichips.intel.com</a>></code></p></li><li><p>Park Myeong Seok <code class="email"><<a class="email" href="mailto:pms@romance.kaist.ac.kr">pms@romance.kaist.ac.kr</a>></code></p></li><li><p>Thomas Parmelan <code class="email"><<a class="email" href="mailto:tom@ankh.fr.eu.org">tom@ankh.fr.eu.org</a>></code></p></li><li><p>Ollivier Robert <code class="email"><<a class="email" href="mailto:roberto@keltia.freenix.fr">roberto@keltia.freenix.fr</a>></code></p></li><li><p>Thomas Roessler <code class="email"><<a class="email" href="mailto:roessler@does-not-exist.org">roessler@does-not-exist.org</a>></code></p></li><li><p>Roland Rosenfeld <code class="email"><<a class="email" href="mailto:roland@spinnaker.de">roland@spinnaker.de</a>></code></p></li><li><p>Rocco Rutte <code class="email"><<a class="email" href="mailto:pdmef@gmx.net">pdmef@gmx.net</a>></code></p></li><li><p>TAKIZAWA Takashi <code class="email"><<a class="email" href="mailto:taki@luna.email.ne.jp">taki@luna.email.ne.jp</a>></code></p></li><li><p>Allain Thivillon <code class="email"><<a class="email" href="mailto:Allain.Thivillon@alma.fr">Allain.Thivillon@alma.fr</a>></code></p></li><li><p>Gero Treuner <code class="email"><<a class="email" href="mailto:gero@70t.de">gero@70t.de</a>></code></p></li><li><p>Vsevolod Volkov <code class="email"><<a class="email" href="mailto:vvv@lucky.net">vvv@lucky.net</a>></code></p></li><li><p>Ken Weinert <code class="email"><<a class="email" href="mailto:kenw@ihs.com">kenw@ihs.com</a>></code></p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="about"></a>2. About this document</h2></div></div></div><p>
6457 This document was written in <a class="ulink" href="http://docbook.sourceforge.net" target="_top">DocBook</a>,
6458 and then rendered using the <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">Gnome XSLT toolkit</a>.
6459 </p></div></div></div></body></html>
projects / software / mutt-debian.git / blob