X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.txt;h=6c8cec7993c17c968e09852573a2c04cb6afb7ff;hp=6b1b1e9450626c1584d1139c49ba466101ade04d;hb=fdf0986350bf8b49a817aaf53526904f8ed5b8de;hpb=6833ce8bdca2d64e14485118f2a4417b7e1cb1b1 diff --git a/doc/manual.txt b/doc/manual.txt index 6b1b1e9..6c8cec7 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -1,6 +1,6 @@ The Mutt E-Mail Client by Michael Elkins - version 1.5.6 + version 1.5.8 ``All mail clients suck. This one just sucks less.'' -me, circa 1995 ______________________________________________________________________ @@ -8,16 +8,15 @@ Table of Contents 1. Introduction - 1.1 Mutt Home Page - 1.2 Mailing Lists - 1.3 Software Distribution Sites - 1.4 IRC - 1.5 USENET - 1.6 Copyright + 1.2 Mutt-ng Home Page + 1.3 Mailing Lists + 1.4 Software Distribution Sites + 1.5 IRC + 1.6 Weblog + 1.7 Copyright 2. Getting Started - 2.1 Moving Around in Menus 2.2 Editing Input Fields 2.3 Reading Mail - The Index and Pager @@ -35,7 +34,6 @@ 2.7 Reading news via NNTP 3. Configuration - 3.1 Syntax of Initialization Files 3.2 Defining/Using aliases 3.3 Changing the default key bindings @@ -59,12 +57,12 @@ 3.21 Adding key sequences to the keyboard buffer 3.22 Executing functions 3.23 Message Scoring - 3.24 Setting variables - 3.25 Reading initialization commands from another file - 3.26 Removing hooks + 3.24 Spam detection + 3.25 Setting variables + 3.26 Reading initialization commands from another file + 3.27 Removing hooks 4. Advanced Usage - 4.1 Regular Expressions 4.2 Patterns 4.2.1 Pattern Modifier @@ -73,26 +71,34 @@ 4.3 Using Tags 4.4 Using Hooks 4.4.1 Message Matching in Hooks - 4.5 External Address Queries - 4.6 Mailbox Formats - 4.7 Mailbox Shortcuts - 4.8 Handling Mailing Lists - 4.9 Delivery Status Notification (DSN) Support - 4.10 POP3 Support (OPTIONAL) - 4.11 IMAP Support (OPTIONAL) - 4.11.1 The Folder Browser - 4.11.2 Authentication - 4.12 Managing multiple IMAP/POP accounts (OPTIONAL) - 4.13 Start a WWW Browser on URLs (EXTERNAL) + 4.5 Usingg the sidebar + 4.6 External Address Queries + 4.7 Mailbox Formats + 4.8 Mailbox Shortcuts + 4.9 Handling Mailing Lists + 4.10 Editing threads + 4.10.1 Linking threads + 4.10.2 Breaking threads + 4.11 Delivery Status Notification (DSN) Support + 4.12 POP3 Support (OPTIONAL) + 4.13 IMAP Support (OPTIONAL) + 4.13.1 The Folder Browser + 4.13.2 Authentication + 4.14 Managing multiple IMAP/POP accounts (OPTIONAL) + 4.15 Start a WWW Browser on URLs (EXTERNAL) + 4.16 Compressed folders Support (OPTIONAL) + 4.16.1 Open a compressed mailbox for reading + 4.16.2 Write a compressed mailbox + 4.16.3 Append a message to a compressed mailbox + 4.16.4 Encrypted folders 5. Mutt's MIME Support - 5.1 Using MIME in Mutt 5.1.1 Viewing MIME messages in the pager 5.1.2 The Attachment Menu 5.1.3 The Compose Menu - 5.2 MIME Type configuration with - 5.3 MIME Viewer configuration with + 5.2 MIME Type configuration with mime.types + 5.3 MIME Viewer configuration with mailcap 5.3.1 The Basics of the mailcap file 5.3.2 Secure use of mailcap 5.3.3 Advanced mailcap Usage @@ -105,7 +111,6 @@ 5.6 MIME Lookup 6. Reference - 6.1 Command line options 6.2 Configuration Commands 6.3 Configuration variables @@ -117,286 +122,319 @@ 6.3.6 allow_ansi 6.3.7 arrow_cursor 6.3.8 ascii_chars - 6.3.9 askbcc - 6.3.10 askcc - 6.3.11 ask_follow_up - 6.3.12 ask_x_comment_to - 6.3.13 attach_format - 6.3.14 attach_sep - 6.3.15 attach_split - 6.3.16 attribution - 6.3.17 autoedit + 6.3.9 ask_follow_up + 6.3.10 ask_x_comment_to + 6.3.11 askbcc + 6.3.12 askcc + 6.3.13 assumed_charset + 6.3.14 attach_format + 6.3.15 attach_sep + 6.3.16 attach_split + 6.3.17 attribution 6.3.18 auto_tag - 6.3.19 beep - 6.3.20 beep_new - 6.3.21 bounce - 6.3.22 bounce_delivered - 6.3.23 catchup_newsgroup - 6.3.24 charset - 6.3.25 check_new - 6.3.26 collapse_unread - 6.3.27 uncollapse_jump - 6.3.28 compose_format - 6.3.29 confirmappend - 6.3.30 confirmcreate - 6.3.31 connect_timeout - 6.3.32 content_type - 6.3.33 copy - 6.3.34 crypt_autopgp - 6.3.35 crypt_autosmime - 6.3.36 date_format - 6.3.37 default_hook - 6.3.38 delete - 6.3.39 delete_untag - 6.3.40 digest_collapse - 6.3.41 display_filter - 6.3.42 dotlock_program - 6.3.43 dsn_notify - 6.3.44 dsn_return - 6.3.45 duplicate_threads - 6.3.46 edit_headers - 6.3.47 editor - 6.3.48 encode_from - 6.3.49 envelope_from - 6.3.50 escape - 6.3.51 fast_reply - 6.3.52 fcc_attach - 6.3.53 fcc_clear - 6.3.54 folder - 6.3.55 folder_format - 6.3.56 followup_to - 6.3.57 followup_to_poster - 6.3.58 force_name - 6.3.59 forward_decode - 6.3.60 forward_edit - 6.3.61 forward_format - 6.3.62 forward_quote - 6.3.63 from - 6.3.64 gecos_mask - 6.3.65 group_index_format - 6.3.66 hdrs - 6.3.67 header - 6.3.68 help - 6.3.69 hidden_host - 6.3.70 hide_limited - 6.3.71 hide_missing - 6.3.72 hide_top_limited - 6.3.73 hide_top_missing - 6.3.74 history - 6.3.75 honor_followup_to - 6.3.76 hostname - 6.3.77 ignore_list_reply_to - 6.3.78 imap_authenticators - 6.3.79 imap_delim_chars - 6.3.80 imap_force_ssl - 6.3.81 imap_home_namespace - 6.3.82 imap_keepalive - 6.3.83 imap_list_subscribed - 6.3.84 imap_pass - 6.3.85 imap_passive - 6.3.86 imap_peek - 6.3.87 imap_servernoise - 6.3.88 imap_user - 6.3.89 implicit_autoview - 6.3.90 include - 6.3.91 indent_string - 6.3.92 index_format - 6.3.93 inews - 6.3.94 ispell - 6.3.95 keep_flagged - 6.3.96 locale - 6.3.97 mail_check - 6.3.98 mailcap_path - 6.3.99 mailcap_sanitize - 6.3.100 maildir_trash - 6.3.101 mark_old - 6.3.102 markers - 6.3.103 mask - 6.3.104 mbox - 6.3.105 mbox_type - 6.3.106 metoo - 6.3.107 menu_scroll - 6.3.108 meta_key - 6.3.109 mh_purge - 6.3.110 mh_seq_flagged - 6.3.111 mh_seq_replied - 6.3.112 mh_seq_unseen - 6.3.113 mime_forward - 6.3.114 mime_forward_decode - 6.3.115 mime_forward_rest - 6.3.116 mime_subject - 6.3.117 mix_entry_format - 6.3.118 mixmaster - 6.3.119 move - 6.3.120 message_format - 6.3.121 narrow_tree - 6.3.122 news_cache_dir - 6.3.123 news_server - 6.3.124 newsrc - 6.3.125 nntp_context - 6.3.126 nntp_load_description - 6.3.127 nntp_user - 6.3.128 nntp_pass - 6.3.129 nntp_poll - 6.3.130 nntp_reconnect - 6.3.131 pager - 6.3.132 pager_context - 6.3.133 pager_format - 6.3.134 pager_index_lines - 6.3.135 pager_stop - 6.3.136 crypt_autosign - 6.3.137 crypt_autoencrypt - 6.3.138 pgp_ignore_subkeys - 6.3.139 crypt_replyencrypt - 6.3.140 crypt_replysign - 6.3.141 crypt_replysignencrypted - 6.3.142 crypt_timestamp - 6.3.143 pgp_use_gpg_agent - 6.3.144 crypt_verify_sig - 6.3.145 smime_is_default - 6.3.146 smime_ask_cert_label - 6.3.147 smime_decrypt_use_default_key - 6.3.148 pgp_entry_format - 6.3.149 pgp_good_sign - 6.3.150 pgp_check_exit - 6.3.151 pgp_long_ids - 6.3.152 pgp_retainable_sigs - 6.3.153 pgp_show_unusable - 6.3.154 pgp_sign_as - 6.3.155 pgp_strict_enc - 6.3.156 pgp_timeout - 6.3.157 pgp_sort_keys - 6.3.158 pgp_create_traditional - 6.3.159 pgp_auto_traditional - 6.3.160 pgp_decode_command - 6.3.161 pgp_getkeys_command - 6.3.162 pgp_verify_command - 6.3.163 pgp_decrypt_command - 6.3.164 pgp_clearsign_command - 6.3.165 pgp_sign_command - 6.3.166 pgp_encrypt_sign_command - 6.3.167 pgp_encrypt_only_command - 6.3.168 pgp_import_command - 6.3.169 pgp_export_command - 6.3.170 pgp_verify_key_command - 6.3.171 pgp_list_secring_command - 6.3.172 pgp_list_pubring_command - 6.3.173 forward_decrypt - 6.3.174 smime_timeout - 6.3.175 smime_encrypt_with - 6.3.176 smime_keys - 6.3.177 smime_ca_location - 6.3.178 smime_certificates - 6.3.179 smime_decrypt_command - 6.3.180 smime_verify_command - 6.3.181 smime_verify_opaque_command - 6.3.182 smime_sign_command - 6.3.183 smime_sign_opaque_command - 6.3.184 smime_encrypt_command - 6.3.185 smime_pk7out_command - 6.3.186 smime_get_cert_command - 6.3.187 smime_get_signer_cert_command - 6.3.188 smime_import_cert_command - 6.3.189 smime_get_cert_email_command - 6.3.190 smime_default_key - 6.3.191 ssl_starttls - 6.3.192 certificate_file - 6.3.193 ssl_usesystemcerts - 6.3.194 entropy_file - 6.3.195 ssl_use_sslv2 - 6.3.196 ssl_use_sslv3 - 6.3.197 ssl_use_tlsv1 - 6.3.198 pipe_split - 6.3.199 pipe_decode - 6.3.200 pipe_sep - 6.3.201 pop_authenticators - 6.3.202 pop_auth_try_all - 6.3.203 pop_checkinterval - 6.3.204 pop_delete - 6.3.205 pop_host - 6.3.206 pop_last - 6.3.207 pop_reconnect - 6.3.208 pop_user - 6.3.209 pop_pass - 6.3.210 post_indent_string - 6.3.211 post_moderated - 6.3.212 postpone - 6.3.213 postponed - 6.3.214 preconnect - 6.3.215 print - 6.3.216 print_command - 6.3.217 print_decode - 6.3.218 print_split - 6.3.219 prompt_after - 6.3.220 query_command - 6.3.221 quit - 6.3.222 quote_regexp - 6.3.223 read_inc - 6.3.224 read_only - 6.3.225 realname - 6.3.226 recall - 6.3.227 record - 6.3.228 reply_regexp - 6.3.229 reply_self - 6.3.230 reply_to - 6.3.231 resolve - 6.3.232 reverse_alias - 6.3.233 reverse_name - 6.3.234 reverse_realname - 6.3.235 rfc2047_parameters - 6.3.236 save_address - 6.3.237 save_empty - 6.3.238 save_name - 6.3.239 score - 6.3.240 score_threshold_delete - 6.3.241 score_threshold_flag - 6.3.242 score_threshold_read - 6.3.243 send_charset - 6.3.244 sendmail - 6.3.245 sendmail_wait - 6.3.246 shell - 6.3.247 save_unsubscribed - 6.3.248 show_new_news - 6.3.249 show_only_unread - 6.3.250 sig_dashes - 6.3.251 sig_on_top - 6.3.252 signature - 6.3.253 simple_search - 6.3.254 smart_wrap - 6.3.255 smileys - 6.3.256 sleep_time - 6.3.257 sort - 6.3.258 sort_alias - 6.3.259 sort_aux - 6.3.260 sort_browser - 6.3.261 sort_re - 6.3.262 spoolfile - 6.3.263 status_chars - 6.3.264 status_format - 6.3.265 status_on_top - 6.3.266 strict_threads - 6.3.267 suspend - 6.3.268 text_flowed - 6.3.269 thread_received - 6.3.270 thorough_search - 6.3.271 tilde - 6.3.272 timeout - 6.3.273 tmpdir - 6.3.274 to_chars - 6.3.275 tunnel - 6.3.276 use_8bitmime - 6.3.277 use_domain - 6.3.278 use_from - 6.3.279 use_ipv6 - 6.3.280 user_agent - 6.3.281 visual - 6.3.282 wait_key - 6.3.283 weed - 6.3.284 wrap_search - 6.3.285 wrapmargin - 6.3.286 write_inc - 6.3.287 write_bcc - 6.3.288 x_comment_to + 6.3.19 autoedit + 6.3.20 beep + 6.3.21 beep_new + 6.3.22 bounce + 6.3.23 bounce_delivered + 6.3.24 catchup_newsgroup + 6.3.25 certificate_file + 6.3.26 charset + 6.3.27 check_new + 6.3.28 collapse_unread + 6.3.29 compose_format + 6.3.30 config_charset + 6.3.31 confirmappend + 6.3.32 confirmcreate + 6.3.33 connect_timeout + 6.3.34 content_type + 6.3.35 copy + 6.3.36 crypt_autoencrypt + 6.3.37 crypt_autopgp + 6.3.38 crypt_autosign + 6.3.39 crypt_autosmime + 6.3.40 crypt_replyencrypt + 6.3.41 crypt_replysign + 6.3.42 crypt_replysignencrypted + 6.3.43 crypt_timestamp + 6.3.44 crypt_use_gpgme + 6.3.45 crypt_verify_sig + 6.3.46 date_format + 6.3.47 default_hook + 6.3.48 delete + 6.3.49 delete_untag + 6.3.50 digest_collapse + 6.3.51 display_filter + 6.3.52 dotlock_program + 6.3.53 dsn_notify + 6.3.54 dsn_return + 6.3.55 duplicate_threads + 6.3.56 edit_headers + 6.3.57 editor + 6.3.58 encode_from + 6.3.59 envelope_from + 6.3.60 escape + 6.3.61 fast_reply + 6.3.62 fcc_attach + 6.3.63 fcc_clear + 6.3.64 file_charset + 6.3.65 folder + 6.3.66 folder_format + 6.3.67 followup_to + 6.3.68 followup_to_poster + 6.3.69 force_name + 6.3.70 forward_decode + 6.3.71 forward_decrypt + 6.3.72 forward_edit + 6.3.73 forward_format + 6.3.74 forward_quote + 6.3.75 from + 6.3.76 gecos_mask + 6.3.77 group_index_format + 6.3.78 hdrs + 6.3.79 header + 6.3.80 help + 6.3.81 hidden_host + 6.3.82 hide_limited + 6.3.83 hide_missing + 6.3.84 hide_thread_subject + 6.3.85 hide_top_limited + 6.3.86 hide_top_missing + 6.3.87 history + 6.3.88 honor_followup_to + 6.3.89 hostname + 6.3.90 ignore_list_reply_to + 6.3.91 imap_authenticators + 6.3.92 imap_delim_chars + 6.3.93 imap_force_ssl + 6.3.94 imap_headers + 6.3.95 imap_home_namespace + 6.3.96 imap_keepalive + 6.3.97 imap_list_subscribed + 6.3.98 imap_pass + 6.3.99 imap_passive + 6.3.100 imap_peek + 6.3.101 imap_reconnect + 6.3.102 imap_servernoise + 6.3.103 imap_user + 6.3.104 implicit_autoview + 6.3.105 include + 6.3.106 include_onlyfirst + 6.3.107 indent_string + 6.3.108 index_format + 6.3.109 inews + 6.3.110 ispell + 6.3.111 keep_flagged + 6.3.112 list_reply + 6.3.113 locale + 6.3.114 mail_check + 6.3.115 mailcap_path + 6.3.116 mailcap_sanitize + 6.3.117 maildir_trash + 6.3.118 mark_old + 6.3.119 markers + 6.3.120 mask + 6.3.121 max_line_length + 6.3.122 mbox + 6.3.123 mbox_type + 6.3.124 menu_context + 6.3.125 menu_scroll + 6.3.126 message_format + 6.3.127 meta_key + 6.3.128 metoo + 6.3.129 mh_purge + 6.3.130 mh_seq_flagged + 6.3.131 mh_seq_replied + 6.3.132 mh_seq_unseen + 6.3.133 mime_forward + 6.3.134 mime_forward_decode + 6.3.135 mime_forward_rest + 6.3.136 mime_subject + 6.3.137 mix_entry_format + 6.3.138 mixmaster + 6.3.139 move + 6.3.140 msgid_format + 6.3.141 narrow_tree + 6.3.142 news_cache_dir + 6.3.143 news_server + 6.3.144 newsrc + 6.3.145 nntp_context + 6.3.146 nntp_load_description + 6.3.147 nntp_pass + 6.3.148 nntp_poll + 6.3.149 nntp_reconnect + 6.3.150 nntp_user + 6.3.151 operating_system + 6.3.152 pager + 6.3.153 pager_context + 6.3.154 pager_format + 6.3.155 pager_index_lines + 6.3.156 pager_stop + 6.3.157 pgp_auto_decode + 6.3.158 pgp_autoinline + 6.3.159 pgp_check_exit + 6.3.160 pgp_clearsign_command + 6.3.161 pgp_decode_command + 6.3.162 pgp_decrypt_command + 6.3.163 pgp_encrypt_only_command + 6.3.164 pgp_encrypt_sign_command + 6.3.165 pgp_entry_format + 6.3.166 pgp_export_command + 6.3.167 pgp_getkeys_command + 6.3.168 pgp_good_sign + 6.3.169 pgp_ignore_subkeys + 6.3.170 pgp_import_command + 6.3.171 pgp_list_pubring_command + 6.3.172 pgp_list_secring_command + 6.3.173 pgp_long_ids + 6.3.174 pgp_mime_auto + 6.3.175 pgp_replyinline + 6.3.176 pgp_retainable_sigs + 6.3.177 pgp_show_unusable + 6.3.178 pgp_sign_as + 6.3.179 pgp_sign_command + 6.3.180 pgp_sort_keys + 6.3.181 pgp_strict_enc + 6.3.182 pgp_timeout + 6.3.183 pgp_use_gpg_agent + 6.3.184 pgp_verify_command + 6.3.185 pgp_verify_key_command + 6.3.186 pipe_decode + 6.3.187 pipe_sep + 6.3.188 pipe_split + 6.3.189 pop_auth_try_all + 6.3.190 pop_authenticators + 6.3.191 pop_checkinterval + 6.3.192 pop_delete + 6.3.193 pop_host + 6.3.194 pop_last + 6.3.195 pop_pass + 6.3.196 pop_reconnect + 6.3.197 pop_user + 6.3.198 post_indent_string + 6.3.199 post_moderated + 6.3.200 postpone + 6.3.201 postponed + 6.3.202 preconnect + 6.3.203 print + 6.3.204 print_command + 6.3.205 print_decode + 6.3.206 print_split + 6.3.207 prompt_after + 6.3.208 query_command + 6.3.209 quit + 6.3.210 quote_empty + 6.3.211 quote_quoted + 6.3.212 quote_regexp + 6.3.213 read_inc + 6.3.214 read_only + 6.3.215 realname + 6.3.216 recall + 6.3.217 record + 6.3.218 reply_regexp + 6.3.219 reply_self + 6.3.220 reply_to + 6.3.221 resolve + 6.3.222 reverse_alias + 6.3.223 reverse_name + 6.3.224 reverse_realname + 6.3.225 rfc2047_parameters + 6.3.226 save_address + 6.3.227 save_empty + 6.3.228 save_name + 6.3.229 save_unsubscribed + 6.3.230 score + 6.3.231 score_threshold_delete + 6.3.232 score_threshold_flag + 6.3.233 score_threshold_read + 6.3.234 send_charset + 6.3.235 sendmail + 6.3.236 sendmail_wait + 6.3.237 shell + 6.3.238 shorten_hierarchy + 6.3.239 show_new_news + 6.3.240 show_only_unread + 6.3.241 sidebar_delim + 6.3.242 sidebar_visible + 6.3.243 sidebar_width + 6.3.244 sig_dashes + 6.3.245 sig_on_top + 6.3.246 signature + 6.3.247 signoff_string + 6.3.248 simple_search + 6.3.249 sleep_time + 6.3.250 smart_wrap + 6.3.251 smileys + 6.3.252 smime_ask_cert_label + 6.3.253 smime_ca_location + 6.3.254 smime_certificates + 6.3.255 smime_decrypt_command + 6.3.256 smime_decrypt_use_default_key + 6.3.257 smime_default_key + 6.3.258 smime_encrypt_command + 6.3.259 smime_encrypt_with + 6.3.260 smime_get_cert_command + 6.3.261 smime_get_cert_email_command + 6.3.262 smime_get_signer_cert_command + 6.3.263 smime_import_cert_command + 6.3.264 smime_is_default + 6.3.265 smime_keys + 6.3.266 smime_pk7out_command + 6.3.267 smime_sign_command + 6.3.268 smime_sign_opaque_command + 6.3.269 smime_timeout + 6.3.270 smime_verify_command + 6.3.271 smime_verify_opaque_command + 6.3.272 smtp_auth_password + 6.3.273 smtp_auth_username + 6.3.274 smtp_host + 6.3.275 smtp_port + 6.3.276 sort + 6.3.277 sort_alias + 6.3.278 sort_aux + 6.3.279 sort_browser + 6.3.280 sort_re + 6.3.281 spam_separator + 6.3.282 spoolfile + 6.3.283 ssl_ca_certificates_file + 6.3.284 ssl_client_cert + 6.3.285 ssl_min_dh_prime_bits + 6.3.286 ssl_starttls + 6.3.287 ssl_use_sslv3 + 6.3.288 ssl_use_tlsv1 + 6.3.289 status_chars + 6.3.290 status_format + 6.3.291 status_on_top + 6.3.292 strict_mime + 6.3.293 strict_threads + 6.3.294 stuff_quoted + 6.3.295 suspend + 6.3.296 text_flowed + 6.3.297 thorough_search + 6.3.298 thread_received + 6.3.299 tilde + 6.3.300 timeout + 6.3.301 tmpdir + 6.3.302 to_chars + 6.3.303 trash + 6.3.304 tunnel + 6.3.305 umask + 6.3.306 uncollapse_jump + 6.3.307 use_8bitmime + 6.3.308 use_domain + 6.3.309 use_from + 6.3.310 user_agent + 6.3.311 visual + 6.3.312 wait_key + 6.3.313 weed + 6.3.314 wrap_search + 6.3.315 wrapmargin + 6.3.316 write_bcc + 6.3.317 write_inc + 6.3.318 x_comment_to + 6.3.319 xterm_icon + 6.3.320 xterm_set_titles + 6.3.321 xterm_title 6.4 Functions 6.4.1 generic 6.4.2 index @@ -411,7 +449,6 @@ 6.4.11 editor 7. Miscellany - 7.1 Acknowledgements 7.2 About this document @@ -425,41 +462,48 @@ regular expression searches and a powerful pattern matching language for selecting groups of messages. + This documentation additionaly contains documentation to MMuutttt--NNGG, a + fork from Mutt with the goal to fix all the little annoyances of Mutt, + to integrate all the Mutt patches that are floating around in the web, + and to add other new features. Features specific to Mutt-ng will be + discussed in an extra section. Don't be confused when most of the + documentation talk about Mutt and not Mutt-ng, Mutt-ng contains all + Mutt-ng features, plus many more. + 11..11.. MMuutttt HHoommee PPaaggee http://www.mutt.org/ - 11..22.. MMaaiilliinngg LLiissttss + 11..22.. MMuutttt--nngg HHoommee PPaaggee - To subscribe to one of the following mailing lists, send a message - with the word _s_u_b_s_c_r_i_b_e in the body to list-name_-_r_e_q_u_e_s_t@mutt.org. + http://mutt-ng.berlios.de/ - · mutt-announce@mutt.org -- low traffic list for announcements + 11..33.. MMaaiilliinngg LLiissttss - · mutt-users@mutt.org -- help, bug reports and feature requests + +o mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user + support happens. - · mutt-dev@mutt.org -- development mailing list + +o mutt-ng-devel@lists.berlios.de -- The development mailing list for + mutt-ng - NNoottee:: all messages posted to _m_u_t_t_-_a_n_n_o_u_n_c_e are automatically forwarded - to _m_u_t_t_-_u_s_e_r_s, so you do not need to be subscribed to both lists. + 11..44.. SSooffttwwaarree DDiissttrriibbuuttiioonn SSiitteess - 11..33.. SSooffttwwaarree DDiissttrriibbuuttiioonn SSiitteess + So far, there are no official releases of Mutt-ng, but you can + download daily snapshots from http://mutt-ng.berlios.de/snapshots/ - · ftp://ftp.mutt.org/mutt/ + 11..55.. IIRRCC - For a list of mirror sites, please refer to - http://www.mutt.org/download.html. + Visit channel _#_m_u_t_t_n_g on irc.freenode.net (www.freenode.net) to chat + with other people interested in Mutt-ng. - 11..44.. IIRRCC + 11..66.. WWeebblloogg - Visit channel _#_m_u_t_t on OpenProjects.Net (www.openprojects.net) to chat - with other people interested in Mutt. + If you want to read fresh news about the latest development in Mutt- + ng, and get informed about stuff like interesting, Mutt-ng-related + articles and packages for your favorite distribution, you can read + and/or subscribe to our Mutt-ng development weblog. - 11..55.. UUSSEENNEETT - - See the newsgroup comp.mail.mutt. - - 11..66.. CCooppyyrriigghhtt + 11..77.. CCooppyyrriigghhtt Mutt is Copyright (C) 1996-2000 Michael R. Elkins and others @@ -514,28 +558,28 @@ input textual data such as email addresses or filenames. The keys used to move around while editing are very similar to those of Emacs. - ^A or bol move to the start of the line - ^B or backward-char move back one char - Esc B backward-word move back one word - ^D or delete-char delete the char under the cursor - ^E or eol move to the end of the line - ^F or forward-char move forward one char - Esc F forward-word move forward one word - complete complete filename or alias - ^T complete-query complete address with query - ^K kill-eol delete to the end of the line - ESC d kill-eow delete to the end ot the word - ^W kill-word kill the word in front of the cursor - ^U kill-line delete entire line - ^V quote-char quote the next typed key - history-up recall previous string from history - history-down recall next string from history - backspace kill the char in front of the cursor - Esc u upcase-word convert word to upper case - Esc l downcase-word convert word to lower case - Esc c capitalize-word capitalize the word - ^G n/a abort - n/a finish editing + ^A or bol move to the start of the line + ^B or backward-char move back one char + Esc B backward-word move back one word + ^D or delete-char delete the char under the cursor + ^E or eol move to the end of the line + ^F or forward-char move forward one char + Esc F forward-word move forward one word + complete complete filename or alias + ^T complete-query complete address with query + ^K kill-eol delete to the end of the line + ESC d kill-eow delete to the end ot the word + ^W kill-word kill the word in front of the cursor + ^U kill-line delete entire line + ^V quote-char quote the next typed key + history-up recall previous string from history + history-down recall next string from history + backspace kill the char in front of the cursor + Esc u upcase-word convert word to upper case + Esc l downcase-word convert word to lower case + Esc c capitalize-word capitalize the word + ^G n/a abort + n/a finish editing You can remap the _e_d_i_t_o_r functions using the ``bind'' command. For example, to make the _D_e_l_e_t_e key delete the character in front of the @@ -616,9 +660,9 @@ Some of the status flags can be turned on or off using - · sseett--ffllaagg (default: w) + +o sseett--ffllaagg (default: w) - · cclleeaarr--ffllaagg (default: W) + +o cclleeaarr--ffllaagg (default: W) Furthermore, the following flags reflect who the message is addressed to. They can be customized with the ``$to_chars'' variable. @@ -789,11 +833,12 @@ lliisstt--rreeppllyy (default: L) Reply to the current or tagged message(s) by extracting any addresses - which match the addresses given by the ``lists or subscribe'' - commands, but also honor any Mail-Followup-To header(s) if the - ``$honor_followup_to'' configuration variable is set. Using this when - replying to messages posted to mailing lists helps avoid duplicate - copies being sent to the author of the message you are replying to. + which match the regular expressions given by the ``lists or + subscribe'' commands, but also honor any Mail-Followup-To header(s) if + the ``$honor_followup_to'' configuration variable is set. Using this + when replying to messages posted to mailing lists helps avoid + duplicate copies being sent to the author of the message you are + replying to. ppiippee--mmeessssaaggee (default: |) @@ -927,7 +972,7 @@ If you want to use PGP, you can specify - Pgp: [ E | S | S ] + Pgp: [ E | S | S_<_i_d_> ] ``E'' encrypts, ``S'' signs and ``S'' signs with the given key, setting ``$pgp_sign_as'' permanently. @@ -1079,18 +1124,21 @@ 33.. CCoonnffiigguurraattiioonn - While the default configuration (or ``preferences'') make Mutt usable - right out of the box, it is often desirable to tailor Mutt to suit - your own tastes. When Mutt is first invoked, it will attempt to read - the ``system'' configuration file (defaults set by your local system - administrator), unless the ``-n'' ``command line'' option is - specified. This file is typically /usr/local/share/mutt/Muttrc or - /etc/Muttrc. Mutt will next look for a file named .muttrc in your home - directory. If this file does not exist and your home directory has a - subdirectory named .mutt, mutt try to load a file named .mutt/muttrc. - - .muttrc is the file where you will usually place your ``commands'' to - configure Mutt. + While the default configuration (or ``preferences'') make Mutt-ng + usable right out of the box, it is often desirable to tailor Mutt to + suit your own tastes. When Mutt-ng is first invoked, it will attempt + to read the ``system'' configuration file (defaults set by your local + system administrator), unless the ``-n'' ``command line'' option is + specified. This file is typically /usr/local/share/muttng/Muttngrc or + /etc/Muttngrc, Mutt-ng users will find this file in + /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will next look + for a file named .muttrc in your home directory, Mutt-ng will look for + .muttngrc. If this file does not exist and your home directory has a + subdirectory named .mutt, mutt try to load a file named + .muttng/muttngrc. + + .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually + place your ``commands'' to configure Mutt. In addition, mutt supports version specific configuration files that are parsed instead of the default files as explained above. For @@ -1111,7 +1159,7 @@ set realname='Mutt user' ; ignore x- - The hash mark, or pound sign (``#''), is used as a ``comment'' charac­ + The hash mark, or pound sign (``#''), is used as a ``comment'' charac- ter. You can use it to annotate your initialization file. All text after the comment character to the end of the line is ignored. For example, @@ -1179,8 +1227,8 @@ unalias [ * | _k_e_y _._._. ] - alias muttdude me@cs.hmc.edu (Michael Elkins) - alias theguys manny, moe, jack + alias muttdude me@cs.hmc.edu (Michael Elkins) + alias theguys manny, moe, jack Unlike other mailers, Mutt doesn't require aliases to be defined in a special file. The alias command can appear anywhere in a @@ -1224,8 +1272,9 @@ This command allows you to change the default key bindings (operation invoked when pressing a key). - _m_a_p specifies in which menu the binding belongs. The currently - defined maps are: + _m_a_p specifies in which menu the binding belongs. Multiple maps may be + specified by separating them with commas (no additional whitespace is + allowed). The currently defined maps are: ggeenneerriicc This is not a real menu, but is used as a fallback for all of @@ -1273,7 +1322,7 @@ _k_e_y is the key (or key sequence) you wish to bind. To specify a control character, use the sequence _\_C_x, where _x is the letter of the control character (for example, to specify control-A use ``\Ca''). - Note that the case of _x as well as _\_C is ignored, so that _\_C_A_, _\_C_a_, + Note that the case of _x as well as _\_C is ignored, so that _\_C_A, _\_C_a, _\_c_A and _\_c_a are all equivalent. An alternative form is to specify the key as a three digit octal number prefixed with a ``\'' (for example _\_1_7_7 is equivalent to _\_c_?). @@ -1361,6 +1410,11 @@ you type, you can create a macro to execute those commands with a single key. + _m_e_n_u is the ``map'' which the macro will be bound. Multiple maps may + be specified by separating multiple menu arguments by commas. + Whitespace may not be used in between the menu arguments and the + commas separating them. + _k_e_y and _s_e_q_u_e_n_c_e are expanded by the same rules as the ``key bindings''. There are some additions however. The first is that control characters in _s_e_q_u_e_n_c_e can also be specified as _^_x. In order @@ -1387,7 +1441,6 @@ Usage: color _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] Usage: color index _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d _p_a_t_t_e_r_n Usage: uncolor index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - If your terminal supports color, you can spice up Mutt by creating your own color scheme. To define the color of an object (type of information), you must specify both a foreground color aanndd a @@ -1396,68 +1449,68 @@ _o_b_j_e_c_t can be one of: - · attachment + +o attachment - · body (match _r_e_g_e_x_p in the body of messages) + +o body (match _r_e_g_e_x_p in the body of messages) - · bold (hiliting bold patterns in the body of messages) + +o bold (hiliting bold patterns in the body of messages) - · error (error messages printed by Mutt) + +o error (error messages printed by Mutt) - · header (match _r_e_g_e_x_p in the message header) + +o header (match _r_e_g_e_x_p in the message header) - · hdrdefault (default color of the message header in the pager) + +o hdrdefault (default color of the message header in the pager) - · index (match _p_a_t_t_e_r_n in the message index) + +o index (match _p_a_t_t_e_r_n in the message index) - · indicator (arrow or bar used to indicate the current item in a + +o indicator (arrow or bar used to indicate the current item in a menu) - · markers (the ``+'' markers at the beginning of wrapped lines in the + +o markers (the ``+'' markers at the beginning of wrapped lines in the pager) - · message (informational messages) + +o message (informational messages) - · normal + +o normal - · quoted (text matching ``$quote_regexp'' in the body of a message) + +o quoted (text matching ``$quote_regexp'' in the body of a message) - · quoted1, quoted2, ..., quotedNN (higher levels of quoting) + +o quoted1, quoted2, ..., quotedNN (higher levels of quoting) - · search (hiliting of words in the pager) + +o search (hiliting of words in the pager) - · signature + +o signature - · status (mode lines used to display info about the mailbox or + +o status (mode lines used to display info about the mailbox or message) - · tilde (the ``~'' used to pad blank lines in the pager) + +o tilde (the ``~'' used to pad blank lines in the pager) - · tree (thread tree drawn in the message index and attachment menu) + +o tree (thread tree drawn in the message index and attachment menu) - · underline (hiliting underlined patterns in the body of messages) + +o underline (hiliting underlined patterns in the body of messages) _f_o_r_e_g_r_o_u_n_d and _b_a_c_k_g_r_o_u_n_d can be one of the following: - · white + +o white - · black + +o black - · green + +o green - · magenta + +o magenta - · blue + +o blue - · cyan + +o cyan - · yellow + +o yellow - · red + +o red - · default + +o default - · color_x + +o color_x _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make the foreground color boldfaced (e.g., brightred). @@ -1495,15 +1548,15 @@ where _a_t_t_r_i_b_u_t_e is one of the following: - · none + +o none - · bold + +o bold - · underline + +o underline - · reverse + +o reverse - · standout + +o standout 33..88.. IIggnnoorriinngg ((wweeeeddiinngg)) uunnwwaanntteedd mmeessssaaggee hheeaaddeerrss @@ -1550,8 +1603,16 @@ the alternates command: It takes a list of regular expressions, each of which can identify an address under which you receive e-mail. - To remove a regular expression from this list, use the unalternates - command. + The unalternates command can be used to write exceptions to alternates + patterns. If an address matches something in an alternates command, + but you nonetheless do not think it is from you, you can list a more + precise pattern under an unalternates command. + + To remove a regular expression from the alternates list, use the + unalternates command with exactly the same _r_e_g_e_x_p. Likewise, if the + _r_e_g_e_x_p for a alternates command matches an entry on the unalternates + list, that unalternates entry will be removed. If the _r_e_g_e_x_p for + unalternates is ``*'', _a_l_l _e_n_t_r_i_e_s on alternates will be removed. 33..1100.. MMaaiilliinngg lliissttss @@ -1589,8 +1650,8 @@ initialization file. To tell mutt that you are subscribed to it, add ``subscribe mutt-users'' to your initialization file instead. If you also happen to get mail from someone whose address is _m_u_t_t_- - _u_s_e_r_s_@_e_x_a_m_p_l_e_._c_o_m, you could use ``lists mutt-users@mutt.org'' or - ``subscribe mutt-users@mutt.org'' to match only mail from the actual + _u_s_e_r_s_@_e_x_a_m_p_l_e_._c_o_m, you could use ``lists mutt-users@mutt\\.org'' or + ``subscribe mutt-users@mutt\\.org'' to match only mail from the actual list. The ``unlists'' command is used to remove a token from the list of @@ -1723,7 +1784,7 @@ See ``Message Matching in Hooks'' for information on the exact format of _p_a_t_t_e_r_n. - Example: fcc-hook aol.com$ +spammers + Example: fcc-hook [@.]aol\\.com$ +spammers The above will save a copy of all messages going to the aol.com domain to the `+spammers' mailbox by default. Also see the ``fcc-save-hook'' @@ -1735,11 +1796,11 @@ This command is a shortcut, equivalent to doing both a ``fcc-hook'' and a ``save-hook'' with its arguments. - 33..1188.. CChhaannggee sseettttiinnggss bbaasseedd uuppoonn mmeessssaaggee rreecciippiieennttss Usage: reply-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d Usage: send-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d + Usage: send2-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d These commands can be used to execute arbitrary configuration commands based upon recipients of the message. _p_a_t_t_e_r_n is a regular expression @@ -1752,7 +1813,13 @@ the send-hook, rreeggaarrddlleessss of the order specified in the users's configuration file. - For each type of send-hook or reply-hook, When multiple matches occur, + send2-hook is matched every time a message is changed, either by + editing it, or by using the compose menu to change its recipients or + subject. send2-hook is executed after send-hook, and can, e.g., be + used to set parameters such as the ``$sendmail'' variable depending on + the message's sender address. + + For each type of send-hook or reply-hook, when multiple matches occur, commands are executed in the order they are specified in the muttrc (for that type of hook). @@ -1845,7 +1912,99 @@ removed. The pattern ``*'' is a special token which means to clear the list of all score entries. - 33..2244.. SSeettttiinngg vvaarriiaabblleess + 33..2244.. SSppaamm ddeetteeccttiioonn + + Usage: spam _p_a_t_t_e_r_n _f_o_r_m_a_t + Usage: nospam _p_a_t_t_e_r_n + + Mutt has generalized support for external spam-scoring filters. By + defining your spam patterns with the spam and nospam commands, you can + _l_i_m_i_t, _s_e_a_r_c_h, and _s_o_r_t your mail based on its spam attributes, as + determined by the external filter. You also can display the spam + attributes in your index display using the %H selector in the + ``$index_format'' variable. (Tip: try %?H?[%H] ? to display spam tags + only when they are defined for a given message.) + + Your first step is to define your external filter's spam patterns + using the spam command. _p_a_t_t_e_r_n should be a regular expression that + matches a header in a mail message. If any message in the mailbox + matches this regular expression, it will receive a ``spam tag'' or + ``spam attribute'' (unless it also matches a nospam pattern -- see + below.) The appearance of this attribute is entirely up to you, and is + governed by the _f_o_r_m_a_t parameter. _f_o_r_m_a_t can be any static text, but + it also can include back-references from the _p_a_t_t_e_r_n expression. (A + regular expression ``back-reference'' refers to a sub-expression + contained within parentheses.) %1 is replaced with the first back- + reference in the regex, %2 with the second, etc. + + If you're using multiple spam filters, a message can have more than + one spam-related header. You can define spam patterns for each filter + you use. If a message matches two or more of these patterns, and the + $spam_separator variable is set to a string, then the message's spam + tag will consist of all the _f_o_r_m_a_t strings joined together, with the + value of $spam_separator separating them. + + For example, suppose I use DCC, SpamAssassin, and PureMessage. I might + define these spam settings: + + spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1" + spam "X-Spam-Status: Yes" "90+/SA" + spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM" + set spam_separator=", " + + If I then received a message that DCC registered with ``many'' hits + under the ``Fuz2'' checksum, and that PureMessage registered with a + 97% probability of being spam, that message's spam tag would read + 90+/DCC-Fuz2, 97/PM. (The four characters before ``=many'' in a DCC + report indicate the checksum used -- in this case, ``Fuz2''.) + + If the $spam_separator variable is unset, then each spam pattern match + supercedes the previous one. Instead of getting joined _f_o_r_m_a_t strings, + you'll get only the last one to match. + + The spam tag is what will be displayed in the index when you use %H in + the $index_format variable. It's also the string that the ~H pattern- + matching expression matches against for _s_e_a_r_c_h and _l_i_m_i_t functions. + And it's what sorting by spam attribute will use as a sort key. + + That's a pretty complicated example, and most people's actual + environments will have only one spam filter. The simpler your + configuration, the more effective mutt can be, especially when it + comes to sorting. + + Generally, when you sort by spam tag, mutt will sort _l_e_x_i_c_a_l_l_y -- that + is, by ordering strings alphnumerically. However, if a spam tag begins + with a number, mutt will sort numerically first, and lexically only + when two numbers are equal in value. (This is like UNIX's sort -n.) A + message with no spam attributes at all -- that is, one that didn't + match _a_n_y of your spam patterns -- is sorted at lowest priority. + Numbers are sorted next, beginning with 0 and ranging upward. Finally, + non-numeric strings are sorted, with ``a'' taking lower priority than + ``z''. Clearly, in general, sorting by spam tags is most effective + when you can coerce your filter to give you a raw number. But in case + you can't, mutt can still do something useful. + + The nospam command can be used to write exceptions to spam patterns. + If a header pattern matches something in a spam command, but you + nonetheless do not want it to receive a spam tag, you can list a more + precise pattern under a nospam command. + + If the _p_a_t_t_e_r_n given to nospam is exactly the same as the _p_a_t_t_e_r_n on + an existing spam list entry, the effect will be to remove the entry + from the spam list, instead of adding an exception. Likewise, if the + _p_a_t_t_e_r_n for a spam command matches an entry on the nospam list, that + nospam entry will be removed. If the _p_a_t_t_e_r_n for nospam is ``*'', _a_l_l + _e_n_t_r_i_e_s _o_n _b_o_t_h _l_i_s_t_s will be removed. This might be the default + action if you use spam and nospam in conjunction with a folder-hook. + + You can have as many spam or nospam commands as you like. You can + even do your own primitive spam detection within mutt -- for example, + if you consider all mail from MAILER-DAEMON to be spam, you can use a + spam command like this: + + spam "^From: .*MAILER-DAEMON" "999" + + 33..2255.. SSeettttiinngg vvaarriiaabblleess Usage: set [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] Usage: toggle _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] @@ -1882,7 +2041,6 @@ The unset command automatically prepends the no prefix to all specified variables. - Using the enter-command function in the _i_n_d_e_x menu, you can query the value of a variable by prefixing the name of the variable with a question mark: @@ -1900,9 +2058,9 @@ With the reset command there exists the special variable ``all'', which allows you to reset all variables to their system defaults. - 33..2255.. RReeaaddiinngg iinniittiiaalliizzaattiioonn ccoommmmaannddss ffrroomm aannootthheerr ffiillee + 33..2266.. RReeaaddiinngg iinniittiiaalliizzaattiioonn ccoommmmaannddss ffrroomm aannootthheerr ffiillee - Usage: source _f_i_l_e_n_a_m_e + Usage: source _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] This command allows the inclusion of initialization commands from other files. For example, I place all of my aliases in @@ -1914,9 +2072,9 @@ If the filename ends with a vertical bar (|), then _f_i_l_e_n_a_m_e is considered to be an executable program from which to read input (eg. - source ~bin/myscript|/). + source ~/bin/myscript|). - 33..2266.. RReemmoovviinngg hhooookkss + 33..2277.. RReemmoovviinngg hhooookkss Usage: unhook [ * | _h_o_o_k_-_t_y_p_e ] @@ -1990,6 +2148,7 @@ [[::ddiiggiitt::]] Numeric characters. + [[::ggrraapphh::]] Characters that are both printable and visible. (A space is printable, but not visible, while an ``a'' is both.) @@ -2004,7 +2163,6 @@ [[::ppuunncctt::]] Punctuation characters (characters that are not letter, digits, control characters, or space characters). - [[::ssppaaccee::]] Space characters (such as space, tab and formfeed, to name a few). @@ -2038,8 +2196,8 @@ An equivalence class is a locale-specific name for a list of characters that are equivalent. The name is enclosed in ``[='' and ``=]''. For example, the name ``e'' might be used to - represent all of ``è'' ``é'' and ``e''. In this case, [[[[==ee==]]]] - is a regexp that matches any of ``è'', ``é'' and ``e''. + represent all of ``e'' ``e'' and ``e''. In this case, [[[[==ee==]]]] + is a regexp that matches any of ``e'', ``e'' and ``e''. A regular expression matching a single character may be followed by one of several repetition operators: @@ -2127,6 +2285,7 @@ ~f USER messages originating from USER ~g cryptographically signed messages ~G cryptographically encrypted messages + ~H EXPR messages with a spam attribute matching EXPR ~h EXPR messages which contain EXPR in the message header ~k message contains PGP key material ~i ID message which match ID in the ``Message-ID'' field @@ -2152,6 +2311,10 @@ ~y EXPR messages which contain EXPR in the `X-Label' field ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *) ~= duplicated messages (see $duplicate_threads) + ~$ unreferenced messages (requires threaded view) + ~* ``From'' contains realname and (syntactically) valid + address (excluded are addresses matching against + alternates or any alias) Where EXPR, USER, ID, and SUBJECT are ``regular expressions''. Special attention has to be made when using regular expressions inside @@ -2186,11 +2349,11 @@ Mutt also recognizes the following operators to create more complex search patterns: - · ! -- logical NOT operator + +o ! -- logical NOT operator - · | -- logical OR operator + +o | -- logical OR operator - · () -- logical grouping operator + +o () -- logical grouping operator Here is an example illustrating a complex search pattern. This pattern will select all messages which do not contain ``mutt'' in the @@ -2212,8 +2375,9 @@ ~f "me@(mutt\.org|cs\.hmc\.edu)" - Without the quotes, the parenthesis would truncate the regular - expression to simply _m_e_@, which is probably not what you want. + Without the quotes, the parenthesis wouldn't end. This would be + seperated to two OR'd patterns: _~_f _m_e_@_(_m_u_t_t_\_._o_r_g and _c_s_\_._h_m_c_\_._e_d_u_). + They are never what you want. 44..22..33.. SSeeaarrcchhiinngg bbyy DDaattee @@ -2251,11 +2415,11 @@ RReellaattiivvee. This type of date is relative to the current date, and may be specified as: - · >_o_f_f_s_e_t (messages older than _o_f_f_s_e_t units) + +o >_o_f_f_s_e_t (messages older than _o_f_f_s_e_t units) - · <_o_f_f_s_e_t (messages newer than _o_f_f_s_e_t units) + +o <_o_f_f_s_e_t (messages newer than _o_f_f_s_e_t units) - · =_o_f_f_s_e_t (messages exactly _o_f_f_s_e_t units old) + +o =_o_f_f_s_e_t (messages exactly _o_f_f_s_e_t units old) _o_f_f_s_e_t is specified as a positive number with one of the following units: @@ -2267,7 +2431,7 @@ Example: to select messages less than 1 month old, you would use - Limit to messages matching: ~d <1m + Limit to messages matching: ~d <1m NNoottee:: all dates used when searching are relative to the llooccaall time zone, so unless you change the setting of your ``$index_format'' to @@ -2293,6 +2457,12 @@ applies to the tagged messages automatically, without requiring the ``tag-prefix''. + In ``macros'' or ``push'' commands, you can use the ``tag-prefix- + cond'' operator. If there are no tagged messages, mutt will "eat" the + rest of the macro to abort it's execution. Mutt will stop "eating" + the macro when it encounters the ``end-cond'' operator; after this + operator the rest of the macro will be executed as normal. + 44..44.. UUssiinngg HHooookkss A _h_o_o_k is a concept borrowed from the EMACS editor which allows you to @@ -2302,19 +2472,19 @@ world, a _h_o_o_k consists of a ``regular expression'' or ``pattern'' along with a configuration option/command. See - · ``folder-hook'' + +o ``folder-hook'' - · ``send-hook'' + +o ``send-hook'' - · ``message-hook'' + +o ``message-hook'' - · ``save-hook'' + +o ``save-hook'' - · ``mbox-hook'' + +o ``mbox-hook'' - · ``fcc-hook'' + +o ``fcc-hook'' - · ``fcc-save-hook'' + +o ``fcc-save-hook'' for specific details on each type of _h_o_o_k available. @@ -2325,7 +2495,7 @@ send-hook and the my_hdr directive: send-hook . 'unmy_hdr From:' - send-hook ~Cb@b.b my_hdr from: c@c.c + send-hook ~C'^b@b\.b$' my_hdr from: c@c.c 44..44..11.. MMeessssaaggee MMaattcchhiinngg iinn HHooookkss @@ -2358,7 +2528,54 @@ time the hook is declared, so the value of ``$default_hook'' that is in effect at that time will be used. - 44..55.. EExxtteerrnnaall AAddddrreessss QQuueerriieess + 44..55.. UUssiinngggg tthhee ssiiddeebbaarr + + The sidebar, a feature specific to Mutt-ng, allows you to use a + mailbox listing which looks very similar to the ones you probably know + from GUI mail clients. The sidebar lists all specified mailboxes, + shows the number in each and highlights the ones with new email Use + the following configuration commands: + + set sidebar_visible="yes" + set sidebar_width=25 + + If you want to specify the mailboxes you can do so with: + + set mbox='=INBOX' + mailboxes INBOX \ + MBOX1 \ + MBOX2 \ + ... + + You can also specify the colors for mailboxes with new mails by using: + + color sidebar_new red black + + The available functions are: + + sidebar-scroll-up Scrolls the mailbox list up 1 page + sidebar-scroll-down Scrolls the mailbox list down 1 page + sidebar-next Hilights the next mailbox + sidebar-next-new Hilights the next mailbox with new mail + sidebar-previous Hilights the previous mailbox + sidebar-open Opens the currently hilighted mailbox + + Reasonable key bindings look e.g. like this: + + bind index \Cp sidebar-prev + bind index \Cn sidebar-next + bind index \Cb sidebar-open + bind pager \Cp sidebar-prev + bind pager \Cn sidebar-next + bind pager \Cb sidebar-open + + macro index B ':toggle sidebar_visible^M' + macro pager B ':toggle sidebar_visible^M' + + You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch + on and off the sidebar simply by pressing 'B'. + + 44..66.. EExxtteerrnnaall AAddddrreessss QQuueerriieess Mutt supports connecting to external directory databases such as LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to mutt @@ -2376,17 +2593,17 @@ An example multiple response output: - Searching database ... 20 entries ... 3 matching: - me@cs.hmc.edu Michael Elkins mutt dude - blong@fiction.net Brandon Long mutt and more - roessler@guug.de Thomas Roessler mutt pgp + Searching database ... 20 entries ... 3 matching: + me@cs.hmc.edu Michael Elkins mutt dude + blong@fiction.net Brandon Long mutt and more + roessler@guug.de Thomas Roessler mutt pgp There are two mechanisms for accessing the query function of mutt. One is to do a query from the index menu using the query function (default: Q). This will prompt for a query, then bring up the query menu which will list the matching responses. From the query menu, you can select addresses to create aliases, or to mail. You can tag - multiple messages to mail, start a new query, or have a new query + multiple addresses to mail, start a new query, or have a new query appended to the current responses. The other mechanism for accessing the query function is for address @@ -2399,7 +2616,7 @@ will activate the query menu. At the query menu, you can select one or more addresses to be added to the prompt. - 44..66.. MMaaiillbbooxx FFoorrmmaattss + 44..77.. MMaaiillbbooxx FFoorrmmaattss Mutt supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so @@ -2411,7 +2628,7 @@ messages are stored in a single file. Each message has a line of the form: - From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST + From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST to denote the start of a new message (this is often referred to as the ``From_'' line). @@ -2433,28 +2650,29 @@ messages are chosen in such a way they are unique, even when two programs are writing the mailbox over NFS, which means that no file locking is needed. - 44..77.. MMaaiillbbooxx SShhoorrttccuuttss + + 44..88.. MMaaiillbbooxx SShhoorrttccuuttss There are a number of built in shortcuts which refer to specific mailboxes. These shortcuts can be used anywhere you are prompted for a file or mailbox path. - · ! -- refers to your ``$spoolfile'' (incoming) mailbox + +o ! -- refers to your ``$spoolfile'' (incoming) mailbox - · > -- refers to your ``$mbox'' file + +o > -- refers to your ``$mbox'' file - · < -- refers to your ``$record'' file + +o < -- refers to your ``$record'' file - · - or !! -- refers to the file you've last visited + +o - or !! -- refers to the file you've last visited - · ~ -- refers to your home directory + +o ~ -- refers to your home directory - · = or + -- refers to your ``$folder'' directory + +o = or + -- refers to your ``$folder'' directory - · @_a_l_i_a_s -- refers to the ``default save folder'' as determined by + +o @_a_l_i_a_s -- refers to the ``default save folder'' as determined by the address of the alias - 44..88.. HHaannddlliinngg MMaaiilliinngg LLiissttss + 44..99.. HHaannddlliinngg MMaaiilliinngg LLiissttss Mutt has a few configuration options that make dealing with large amounts of mail easier. The first thing you must do is to let Mutt @@ -2510,10 +2728,11 @@ trying to reply directly to the author in private, since most mail clients will automatically reply to the address given in the ``Reply- To'' field. Mutt uses the ``$reply_to'' variable to help decide which - address to use. If set, you will be prompted as to whether or not you - would like to use the address given in the ``Reply-To'' field, or - reply directly to the address given in the ``From'' field. When - unset, the ``Reply-To'' field will be used when present. + address to use. If set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, you will be prompted as + to whether or not you would like to use the address given in the + ``Reply-To'' field, or reply directly to the address given in the + ``From'' field. When set to _y_e_s, the ``Reply-To'' field will be used + when present. The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages @@ -2532,7 +2751,39 @@ dealing with large volume mailing lists easier because you can easily delete uninteresting threads and quickly find topics of value. - 44..99.. DDeelliivveerryy SSttaattuuss NNoottiiffiiccaattiioonn ((DDSSNN)) SSuuppppoorrtt + 44..1100.. EEddiittiinngg tthhrreeaaddss + + Mutt has the ability to dynamically restructure threads that are + broken either by misconfigured software or bad behaviour from some + correspondents. This allows to clean your mailboxes formats) from + these annoyances which make it hard to follow a discussion. + + If you want to use these functions with IMAP, you need to compile Mutt + with the _-_-_e_n_a_b_l_e_-_i_m_a_p_-_e_d_i_t_-_t_h_r_e_a_d_s configure flag. + + 44..1100..11.. LLiinnkkiinngg tthhrreeaaddss + + Some mailers tend to "forget" to correctly set the "In-Reply-To:" and + "References:" headers when replying to a message. This results in + broken discussions because Mutt has not enough information to guess + the correct threading. You can fix this by tagging the reply, then + moving to the parent message and using the ``link-threads'' function + (bound to & by default). The reply will then be connected to this + "parent" message. + + You can also connect multiple childs at once, tagging them and using + the tag-prefix command (';') or the auto_tag option. + + 44..1100..22.. BBrreeaakkiinngg tthhrreeaaddss + + On mailing lists, some people are in the bad habit of starting a new + discussion by hitting "reply" to any message from the list and + changing the subject to a totally unrelated one. You can fix such + threads by using the ``break-thread'' function (bound by default to + #), which will turn the subthread starting from the current message + into a whole different thread. + + 44..1111.. DDeelliivveerryy SSttaattuuss NNoottiiffiiccaattiioonn ((DDSSNN)) SSuuppppoorrtt RFC1894 defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of @@ -2546,7 +2797,7 @@ message should be returned with the receipt (headers or full message). Refer to the man page on sendmail for more details on DSN. - 44..1100.. PPOOPP33 SSuuppppoorrtt ((OOPPTTIIOONNAALL)) + 44..1122.. PPOOPP33 SSuuppppoorrtt ((OOPPTTIIOONNAALL)) If Mutt was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to work with @@ -2580,7 +2831,7 @@ NNoottee:: If you only need to fetch all messages to local mailbox you should consider using a specialized program, such as fetchmail - 44..1111.. IIMMAAPP SSuuppppoorrtt ((OOPPTTIIOONNAALL)) + 44..1133.. IIMMAAPP SSuuppppoorrtt ((OOPPTTIIOONNAALL)) If Mutt was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_i_m_a_p flag), it has the ability to work with @@ -2631,28 +2882,30 @@ to v12.250, the server has been reported to disconnect a client if another client selects the same folder. - 44..1111..11.. TThhee FFoollddeerr BBrroowwsseerr + 44..1133..11.. TThhee FFoollddeerr BBrroowwsseerr As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is mostly the same as the local file browser, with the following differences: - · In lieu of file permissions, mutt displays the string "IMAP", + +o In lieu of file permissions, mutt displays the string "IMAP", possibly followed by the symbol "+", indicating that the entry contains both messages and subfolders. On Cyrus-like servers folders will often contain both messages and subfolders. - · For the case where an entry can contain both messages and + +o For the case where an entry can contain both messages and subfolders, the selection key (bound to enter by default) will choose to descend into the subfolder view. If you wish to view the messages in that folder, you must use view-file instead (bound to space by default). - · You can delete mailboxes with the delete-mailbox command (bound to - d by default. You may also subscribe and unsubscribe to mailboxes - (normally these are bound to s and u, respectively). + +o You can create, delete and rename mailboxes with the create- + mailbox, delete-mailbox, and rename-mailbox commands (default + bindings: C, d and r, respectively). You may also subscribe and + unsubscribe to mailboxes (normally these are bound to s and u, + respectively). - 44..1111..22.. AAuutthheennttiiccaattiioonn + 44..1133..22.. AAuutthheennttiiccaattiioonn Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add @@ -2677,19 +2930,20 @@ There are a few variables which control authentication: - · ``$imap_user'' - controls the username under which you request + +o ``$imap_user'' - controls the username under which you request authentication on the IMAP server, for all authenticators. This is overridden by an explicit username in the mailbox path (ie by using a mailbox name of the form {user@host}). - · ``$imap_pass'' - a password which you may preset, used by all + + +o ``$imap_pass'' - a password which you may preset, used by all authentication methods where a password is needed. - · ``$imap_authenticators'' - a colon-delimited list of IMAP + +o ``$imap_authenticators'' - a colon-delimited list of IMAP authentication methods to try, in the order you wish to try them. If specified, this overrides mutt's default (attempt everything, in the order listed above). - 44..1122.. MMaannaaggiinngg mmuullttiippllee IIMMAAPP//PPOOPP aaccccoouunnttss ((OOPPTTIIOONNAALL)) + 44..1144.. MMaannaaggiinngg mmuullttiippllee IIMMAAPP//PPOOPP aaccccoouunnttss ((OOPPTTIIOONNAALL)) If you happen to have accounts on multiple IMAP and/or POP servers, you may find managing all the authentication settings inconvenient and @@ -2704,9 +2958,9 @@ account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo' account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' - 44..1133.. SSttaarrtt aa WWWWWW BBrroowwsseerr oonn UURRLLss ((EEXXTTEERRNNAALL)) + 44..1155.. SSttaarrtt aa WWWWWW BBrroowwsseerr oonn UURRLLss ((EEXXTTEERRNNAALL)) - If a message contains URLs (_u_n_i_f_i_e_d _r_e_s_s_o_u_r_c_e _l_o_c_a_t_o_r = address in the + If a message contains URLs (_u_n_i_f_i_e_d _r_e_s_o_u_r_c_e _l_o_c_a_t_o_r = address in the WWW space like _h_t_t_p_:_/_/_w_w_w_._m_u_t_t_._o_r_g_/), it is efficient to get a menu with all the URLs and start a WWW browser on one of them. This functionality is provided by the external urlview program which can be @@ -2716,6 +2970,149 @@ macro index \cb |urlview\n macro pager \cb |urlview\n + 44..1166.. CCoommpprreesssseedd ffoollddeerrss SSuuppppoorrtt ((OOPPTTIIOONNAALL)) + + If Mutt was compiled with compressed folders support (by running the + _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d flag), Mutt can open + folders stored in an arbitrary format, provided that the user has a + script to convert from/to this format to one of the accepted. + + The most common use is to open compressed archived folders e.g. with + gzip. + + In addition, the user can provide a script that gets a folder in an + accepted format and appends its context to the folder in the user- + defined format, which may be faster than converting the entire folder + to the accepted format, appending to it and converting back to the + user-defined format. + + There are three hooks defined (``open-hook'', ``close-hook'' and + ``append-hook'') which define commands to uncompress and compress a + folder and to append messages to an existing compressed folder + respectively. + + For example: + + open-hook \\.gz$ "gzip -cd %f > %t" + close-hook \\.gz$ "gzip -c %t > %f" + append-hook \\.gz$ "gzip -c %t >> %f" + + You do not have to specify all of the commands. If you omit ``append- + hook'', the folder will be open and closed again each time you will + add to it. If you omit ``close-hook'' (or give empty command) , the + folder will be open in the mode. If you specify ``append-hook'' + though you'll be able to append to the folder. + + Note that Mutt will only try to use hooks if the file is not in one of + the accepted formats. In particular, if the file is empty, mutt + supposes it is not compressed. This is important because it allows the + use of programs that do not have well defined extensions. Just use "." + as a regexp. But this may be surprising if your compressing script + produces empty files. In this situation, unset ``$save_empty'', so + that the compressed file will be removed if you delete all of the + messages. + + 44..1166..11.. OOppeenn aa ccoommpprreesssseedd mmaaiillbbooxx ffoorr rreeaaddiinngg + + Usage: open-hook _r_e_g_e_x_p "_c_o_m_m_a_n_d" + + The _c_o_m_m_a_n_d is the command that can be used for opening the folders + whose names match _r_e_g_e_x_p. + + The _c_o_m_m_a_n_d string is the printf-like format string, and it should + accept two parameters: %f, which is replaced with the (compressed) + folder name, and %t which is replaced with the name of the temporary + folder to which to write. + + %f and %t can be repeated any number of times in the command string, + and all of the entries are replaced with the appropriate folder name. + In addition, %% is replaced by %, as in printf, and any other + %anything is left as is. + + The _c_o_m_m_a_n_d should nnoott remove the original compressed file. The + _c_o_m_m_a_n_d should return non-zero exit status if it fails, so mutt knows + something's wrong. + + Example: + + open-hook \\.gz$ "gzip -cd %f > %t" + + If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file + type. + 44..1166..22.. WWrriittee aa ccoommpprreesssseedd mmaaiillbbooxx + + Usage: close-hook _r_e_g_e_x_p "_c_o_m_m_a_n_d" + + This is used to close the folder that was open with the ``open-hook'' + command after some changes were made to it. + + The _c_o_m_m_a_n_d string is the command that can be used for closing the + folders whose names match _r_e_g_e_x_p. It has the same format as in the + ``open-hook'' command. Temporary folder in this case is the folder + previously produced by the <``open-hook'' command. + + The _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d + should return non-zero exit status if it fails, so mutt knows + something's wrong. + + Example: + + close-hook \\.gz$ "gzip -c %t > %f" + + If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file + type, and the file can only be open in the readonly mode. + + ``close-hook'' is not called when you exit from the folder if the + folder was not changed. + + 44..1166..33.. AAppppeenndd aa mmeessssaaggee ttoo aa ccoommpprreesssseedd mmaaiillbbooxx + + Usage: append-hook _r_e_g_e_x_p "_c_o_m_m_a_n_d" + + This command is used for saving to an existing compressed folder. The + _c_o_m_m_a_n_d is the command that can be used for appending to the folders + whose names match _r_e_g_e_x_p. It has the same format as in the ``open- + hook'' command. The temporary folder in this case contains the + messages that are being appended. + + The _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d + should return non-zero exit status if it fails, so mutt knows + something's wrong. + + Example: + + append-hook \\.gz$ "gzip -c %t >> %f" + + When ``append-hook'' is used, the folder is not opened, which saves + time, but this means that we can not find out what the folder type is. + Thus the default (``$mbox_type'') type is always supposed (i.e. this + is the format used for the temporary folder). + + If the file does not exist when you save to it, ``close-hook'' is + called, and not ``append-hook''. ``append-hook'' is only for appending + to existing folders. + + If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file + type. In this case, the folder will be open and closed again (using + ``open-hook'' and ``close-hook''respectively) each time you will add + to it. + + 44..1166..44.. EEnnccrryypptteedd ffoollddeerrss + + The compressed folders support can also be used to handle encrypted + folders. If you want to encrypt a folder with PGP, you may want to use + the following hooks: + + open-hook \\.pgp$ "pgp -f < %f > %t" + close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" + + Please note, that PGP does not support appending to an encrypted + folder, so there is no append-hook defined. + + NNoottee:: the folder is temporary stored decrypted in the /tmp directory, + where it can be read by your system administrator. So think about the + security aspects of this. + 55.. MMuutttt''ss MMIIMMEE SSuuppppoorrtt Quite a bit of effort has been made to make Mutt the premier text-mode @@ -2749,8 +3146,8 @@ [-- Type: text/plain, Encoding: 7bit, Size: 10000 --] Where the Description is the description or filename given for the - attachment, and the Encoding is one of 7bit/8bit/quoted-print­ - able/base64/binary. + attachment, and the Encoding is one of 7bit/8bit/quoted- + printable/base64/binary. If Mutt cannot deal with a MIME type, it will display a message like: @@ -3033,7 +3430,7 @@ In this example, Mutt will run the program RunningX which will return 0 if the X Window manager is running, and non-zero if it - isn't. If RunningX returns 0, then Mutt will call netscape to dis­ + isn't. If RunningX returns 0, then Mutt will call netscape to dis- play the text/html object. If RunningX doesn't return 0, then Mutt will go on to the next entry and use lynx to display the text/html object. @@ -3059,13 +3456,13 @@ can then use the test feature to determine which viewer to use interactively depending on your environment. - text/html; netscape -remote 'openURL(%s)' ; test=RunningX - text/html; lynx %s; nametemplate=%s.html - text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput + text/html; netscape -remote 'openURL(%s)' ; test=RunningX + text/html; lynx %s; nametemplate=%s.html + text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput For ``Autoview'', Mutt will choose the third entry because of the copiousoutput tag. For interactive viewing, Mutt will run the program - RunningX to determine if it should use the first entry. If the pro­ + RunningX to determine if it should use the first entry. If the pro- gram returns non-zero, Mutt will use the second entry for interactive viewing. @@ -3094,14 +3491,14 @@ Content-Type: text/plain; charset=iso-8859-1 - then Mutt will expand %{charset} to iso-8859-1. The default meta­ + then Mutt will expand %{charset} to iso-8859-1. The default meta- mail mailcap file uses this feature to test the charset to spawn an xterm using the right charset to view the message. \\%% This will be replaced by a % Mutt does not currently support the %F and %n keywords specified in - RFC 1524. The main purpose of these parameters is for multipart mes­ + RFC 1524. The main purpose of these parameters is for multipart mes- sages, which is handled internally by Mutt. 55..33..44.. EExxaammppllee mmaaiillccaapp ffiilleess @@ -3178,11 +3575,11 @@ Mutt could use the following mailcap entries to automatically view attachments of these types. - text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html - image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput - application/x-gunzip; gzcat; copiousoutput - application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput - application/postscript; ps2ascii %s; copiousoutput + text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html + image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput + application/x-gunzip; gzcat; copiousoutput + application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput + application/postscript; ps2ascii %s; copiousoutput ``unauto_view'' can be used to remove previous entries from the autoview list. This can be used with message-hook to autoview @@ -3220,7 +3617,7 @@ mailcap file and according to any other configuration options (such as auto_view) specified. Common usage would be: - mime-lookup application/octet-stream application/X-Lotus-Manuscript + mime_lookup application/octet-stream application/X-Lotus-Manuscript In addition, the unmime_lookup command may be used to disable this feature for any particular mime-type if it had been set, for example, @@ -3278,101 +3675,113 @@ The following are the commands understood by mutt. - · ``account-hook'' _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o ``account-hook'' _p_a_t_t_e_r_n _c_o_m_m_a_n_d - · ``alias'' _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] + +o ``alias'' _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] - · ``unalias'' [ * | _k_e_y ... ] + +o ``unalias'' [ * | _k_e_y ... ] - · ``alternates'' _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o ``alternates'' _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - · ``unalternates'' [ * | _r_e_g_e_x_p ... ] + +o ``unalternates'' [ * | _r_e_g_e_x_p ... ] - · ``alternative_order'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o ``alternative_order'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - · ``unalternative_order'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o ``unalternative_order'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - · ``auto_view'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o ``append-hook'' _r_e_g_e_x_p _c_o_m_m_a_n_d - · ``unauto_view'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o ``auto_view'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - · ``bind'' _m_a_p _k_e_y _f_u_n_c_t_i_o_n + +o ``unauto_view'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - · ``charset-hook'' _a_l_i_a_s _c_h_a_r_s_e_t + +o ``bind'' _m_a_p _k_e_y _f_u_n_c_t_i_o_n - · ``color'' _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] + +o ``charset-hook'' _a_l_i_a_s _c_h_a_r_s_e_t - · ``uncolor'' _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o ``close-hook'' _r_e_g_e_x_p _c_o_m_m_a_n_d - · ``exec'' _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] + +o ``color'' _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] - · ``fcc-hook'' _p_a_t_t_e_r_n _m_a_i_l_b_o_x + +o ``uncolor'' _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - · ``fcc-save-hook'' _p_a_t_t_e_r_n _m_a_i_l_b_o_x + +o ``exec'' _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] - · ``folder-hook'' _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o ``fcc-hook'' _p_a_t_t_e_r_n _m_a_i_l_b_o_x - · ``hdr_order'' _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] + +o ``fcc-save-hook'' _p_a_t_t_e_r_n _m_a_i_l_b_o_x - · ``unhdr_order'' _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] + +o ``folder-hook'' _p_a_t_t_e_r_n _c_o_m_m_a_n_d - · ``iconv-hook'' _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t + +o ``hdr_order'' _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] - · ``ignore'' _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o ``unhdr_order'' _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] - · ``unignore'' _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o ``iconv-hook'' _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t - · ``lists'' _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s ... ] + +o ``ignore'' _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - · ``unlists'' _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s ... ] + +o ``unignore'' _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - · ``macro'' _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] + +o ``lists'' _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - · ``mailboxes'' _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] + +o ``unlists'' _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - · ``mbox-hook'' _p_a_t_t_e_r_n _m_a_i_l_b_o_x + +o ``macro'' _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] - · ``message-hook'' _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o ``mailboxes'' _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] - · ``mime_lookup'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o ``mbox-hook'' _p_a_t_t_e_r_n _m_a_i_l_b_o_x - · ``unmime_lookup'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o ``message-hook'' _p_a_t_t_e_r_n _c_o_m_m_a_n_d - · ``mono'' _o_b_j_e_c_t _a_t_t_r_i_b_u_t_e [ _r_e_g_e_x_p ] + +o ``mime_lookup'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - · ``unmono'' _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o ``unmime_lookup'' _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - · ``my_hdr'' _s_t_r_i_n_g + +o ``mono'' _o_b_j_e_c_t _a_t_t_r_i_b_u_t_e [ _r_e_g_e_x_p ] - · ``unmy_hdr'' _f_i_e_l_d [ _f_i_e_l_d ... ] + +o ``unmono'' _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - · ``crypt-hook'' _p_a_t_t_e_r_n _k_e_y_-_i_d + +o ``my_hdr'' _s_t_r_i_n_g - · ``push'' _s_t_r_i_n_g + +o ``unmy_hdr'' _f_i_e_l_d [ _f_i_e_l_d ... ] - · ``reset'' _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + +o ``open-hook'' _r_e_g_e_x_p _c_o_m_m_a_n_d - · ``save-hook'' _r_e_g_e_x_p _f_i_l_e_n_a_m_e + +o ``crypt-hook'' _p_a_t_t_e_r_n _k_e_y_-_i_d - · ``score'' _p_a_t_t_e_r_n _v_a_l_u_e + +o ``push'' _s_t_r_i_n_g - · ``unscore'' _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o ``reset'' _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - · ``send-hook'' _r_e_g_e_x_p _c_o_m_m_a_n_d + +o ``save-hook'' _r_e_g_e_x_p _f_i_l_e_n_a_m_e - · ``set'' [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] + +o ``score'' _p_a_t_t_e_r_n _v_a_l_u_e - · ``unset'' _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + +o ``unscore'' _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - · ``source'' _f_i_l_e_n_a_m_e + +o ``send-hook'' _r_e_g_e_x_p _c_o_m_m_a_n_d - · ``subscribe'' _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s ... ] + +o ``reply-hook'' _r_e_g_e_x_p _c_o_m_m_a_n_d - · ``unsubscribe'' _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s ... ] + +o ``set'' [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] - · ``toggle'' _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + +o ``unset'' _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - · ``unhook'' _h_o_o_k_-_t_y_p_e + +o ``source'' _f_i_l_e_n_a_m_e + + +o ``spam'' _p_a_t_t_e_r_n _f_o_r_m_a_t + + +o ``nospam'' _p_a_t_t_e_r_n + + +o ``subscribe'' _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + + +o ``unsubscribe'' _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + + +o ``toggle'' _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + + +o ``unhook'' _h_o_o_k_-_t_y_p_e 66..33.. CCoonnffiigguurraattiioonn vvaarriiaabblleess @@ -3399,12 +3808,12 @@ 66..33..33.. aalliiaass__ffiillee Type: path - Default: "~/.muttrc" + Default: "~/.muttngrc" The default file in which to save aliases created by the ````create- alias'''' function. - NNoottee:: Mutt will not automatically source this file; you must + NNoottee:: Mutt-ng will not automatically source this file; you must explicitly use the ````source'''' command for it to be executed. 66..33..44.. aalliiaass__ffoorrmmaatt @@ -3462,41 +3871,61 @@ Type: boolean Default: no - If set, Mutt will use plain ASCII characters when displaying thread + If set, Mutt-ng will use plain ASCII characters when displaying thread and attachment trees, instead of the default _A_C_S characters. - 66..33..99.. aasskkbbcccc + 66..33..99.. aasskk__ffoollllooww__uupp Type: boolean Default: no - If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients - before editing an outgoing message. + If set, Mutt-ng will prompt you for follow-up groups before editing + the body of an outgoing message. - 66..33..1100.. aasskkcccc + 66..33..1100.. aasskk__xx__ccoommmmeenntt__ttoo Type: boolean Default: no - If set, Mutt will prompt you for carbon-copy (Cc) recipients before - editing the body of an outgoing message. + If set, Mutt-ng will prompt you for x-comment-to field before editing + the body of an outgoing message. - 66..33..1111.. aasskk__ffoollllooww__uupp + 66..33..1111.. aasskkbbcccc Type: boolean Default: no - If set, Mutt will prompt you for follow-up groups before editing the - body of an outgoing message. + If set, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients + before editing an outgoing message. - 66..33..1122.. aasskk__xx__ccoommmmeenntt__ttoo + 66..33..1122.. aasskkcccc Type: boolean Default: no - If set, Mutt will prompt you for x-comment-to field before editing the - body of an outgoing message. - 66..33..1133.. aattttaacchh__ffoorrmmaatt + If set, Mutt-ng will prompt you for carbon-copy (Cc) recipients before + editing the body of an outgoing message. + + 66..33..1133.. aassssuummeedd__cchhaarrsseett + + Type: string + Default: "us-ascii" + + This variable is a colon-separated list of character encoding schemes + for messages without character encoding indication. Header field + values and message body content without character encoding indication + would be assumed that they are written in one of this list. By + default, all the header fields and message body without any charset + indication are assumed to be in "us-ascii". + + For example, Japanese users might prefer this: + + set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8" + + However, only the first content is valid for the message body. This + variable is valid only if ``$strict_mime'' is unset. + + 66..33..1144.. aattttaacchh__ffoorrmmaatt Type: string Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] " @@ -3506,7 +3935,7 @@ %%CC charset - %%cc reqiures charset conversion (n or c) + %%cc requires charset conversion (n or c) %%DD deleted flag @@ -3538,7 +3967,7 @@ %%||XX pad to the end of the line with character "X" - 66..33..1144.. aattttaacchh__sseepp + 66..33..1155.. aattttaacchh__sseepp Type: string Default: "\n" @@ -3546,18 +3975,18 @@ The separator to add between attachments when operating (saving, printing, piping, etc) on a list of tagged attachments. - 66..33..1155.. aattttaacchh__sspplliitt + 66..33..1166.. aattttaacchh__sspplliitt Type: boolean Default: yes If this variable is unset, when operating (saving, printing, piping, - etc) on a list of tagged attachments, Mutt will concatenate the + etc) on a list of tagged attachments, Mutt-ng will concatenate the attachments and will operate on them as a single attachment. The ````$attach_sep'''' separator is added after each attachment. When - set, Mutt will operate on the attachments one by one. + set, Mutt-ng will operate on the attachments one by one. - 66..33..1166.. aattttrriibbuuttiioonn + 66..33..1177.. aattttrriibbuuttiioonn Type: string Default: "On %d, %n wrote:" @@ -3566,18 +3995,6 @@ in a reply. For a full listing of defined printf()-like sequences see the section on ````$index_format''''. - 66..33..1177.. aauuttooeeddiitt - - Type: boolean - Default: no - - When set along with ````$edit_headers'''', Mutt will skip the initial - send-menu and allow you to immediately begin editing the body of your - message. The send-menu may still be accessed once you have finished - editing the body of your message. - - Also see ````$fast_reply''''. - 66..33..1188.. aauuttoo__ttaagg Type: boolean @@ -3588,23 +4005,35 @@ must first use the tag-prefix function (default: ";") to make the next function apply to all tagged messages. - 66..33..1199.. bbeeeepp + 66..33..1199.. aauuttooeeddiitt + + Type: boolean + Default: no + + When set along with ````$edit_headers'''', Mutt-ng will skip the + initial send-menu and allow you to immediately begin editing the body + of your message. The send-menu may still be accessed once you have + finished editing the body of your message. + + Also see ````$fast_reply''''. + + 66..33..2200.. bbeeeepp Type: boolean Default: yes - When this variable is set, mutt will beep when an error occurs. + When this variable is set, mutt-ng will beep when an error occurs. - 66..33..2200.. bbeeeepp__nneeww + 66..33..2211.. bbeeeepp__nneeww Type: boolean Default: no - When this variable is set, mutt will beep whenever it prints a message - notifying you of new mail. This is independent of the setting of the - ````$beep'''' variable. + When this variable is set, mutt-ng will beep whenever it prints a + message notifying you of new mail. This is independent of the setting + of the ````$beep'''' variable. - 66..33..2211.. bboouunnccee + 66..33..2222.. bboouunnccee Type: quadoption Default: ask-yes @@ -3614,66 +4043,75 @@ Setting this variable to _n_o is not generally useful, and thus not recommended, because you are unable to bounce messages. - 66..33..2222.. bboouunnccee__ddeelliivveerreedd + 66..33..2233.. bboouunnccee__ddeelliivveerreedd Type: boolean Default: yes - When this variable is set, mutt will include Delivered-To headers when - bouncing messages. Postfix users may wish to unset this variable. + When this variable is set, mutt-ng will include Delivered-To headers + when bouncing messages. Postfix users may wish to unset this + variable. - 66..33..2233.. ccaattcchhuupp__nneewwssggrroouupp + 66..33..2244.. ccaattcchhuupp__nneewwssggrroouupp Type: quadoption Default: ask-yes - If this variable is _s_e_t, Mutt will mark all articles in newsgroup as - read when you quit the newsgroup (catchup newsgroup). + If this variable is _s_e_t, Mutt-ng will mark all articles in newsgroup + as read when you quit the newsgroup (catchup newsgroup). + + 66..33..2255.. cceerrttiiffiiccaattee__ffiillee + + Type: path + Default: "~/.mutt_certificates" + + This variable specifies the file where the certificates you trust are + saved. When an unknown certificate is encountered, you are asked if + you accept it or not. If you accept it, the certificate can also be + saved in this file and further connections are automatically accepted. + + You can also manually add CA certificates in this file. Any server + certificate that is signed with one of these CA certificates are also + automatically accepted. + + Example: set certificate_file=~/.mutt/certificates - 66..33..2244.. cchhaarrsseett + 66..33..2266.. cchhaarrsseett Type: string Default: "" Character set your terminal uses to display and enter textual data. - 66..33..2255.. cchheecckk__nneeww + 66..33..2277.. cchheecckk__nneeww Type: boolean Default: yes NNoottee:: this option only affects _m_a_i_l_d_i_r and _M_H style mailboxes. - When _s_e_t, Mutt will check for new mail delivered while the mailbox is - open. Especially with MH mailboxes, this operation can take quite + When _s_e_t, Mutt-ng will check for new mail delivered while the mailbox + is open. Especially with MH mailboxes, this operation can take quite some time since it involves scanning the directory and checking each file to see if it has already been looked at. If _c_h_e_c_k___n_e_w is _u_n_s_e_t, no check for new mail is performed while the mailbox is open. - 66..33..2266.. ccoollllaappssee__uunnrreeaadd + 66..33..2288.. ccoollllaappssee__uunnrreeaadd Type: boolean Default: yes - When _u_n_s_e_t, Mutt will not collapse a thread if it contains any unread - messages. - - 66..33..2277.. uunnccoollllaappssee__jjuummpp - - Type: boolean - Default: no - - When _s_e_t, Mutt will jump to the next unread message, if any, when the - current thread is _u_ncollapsed. + When _u_n_s_e_t, Mutt-ng will not collapse a thread if it contains any + unread messages. - 66..33..2288.. ccoommppoossee__ffoorrmmaatt + 66..33..2299.. ccoommppoossee__ffoorrmmaatt Type: string - Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-" + Default: "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-" - Controls the format of the status line displayed in the \fCompose - menu. This string is similar to ````$status_format'''', but has its - own set of printf()-like sequences: + Controls the format of the status line displayed in the _C_o_m_p_o_s_e menu. + This string is similar to ````$status_format'''', but has its own set + of printf()-like sequences: %%aa total number of attachments @@ -3681,45 +4119,53 @@ %%ll approximate size (in bytes) of the current message - %%vv Mutt version string + %%vv Mutt-ng version string See the text describing the ````$status_format'''' option for more information on how to set ````$compose_format''''. - 66..33..2299.. ccoonnffiirrmmaappppeenndd + 66..33..3300.. ccoonnffiigg__cchhaarrsseett + + Type: string + Default: "" + + When defined, Mutt-ng will recode commands in rc files from this + encoding. + + 66..33..3311.. ccoonnffiirrmmaappppeenndd Type: boolean Default: yes - When set, Mutt will prompt for confirmation when appending messages to - an existing mailbox. + When set, Mutt-ng will prompt for confirmation when appending messages + to an existing mailbox. - 66..33..3300.. ccoonnffiirrmmccrreeaattee + 66..33..3322.. ccoonnffiirrmmccrreeaattee Type: boolean Default: yes - When set, Mutt will prompt for confirmation when saving messages to a - mailbox which does not yet exist before creating it. + When set, Mutt-ng will prompt for confirmation when saving messages to + a mailbox which does not yet exist before creating it. - 66..33..3311.. ccoonnnneecctt__ttiimmeeoouutt + 66..33..3333.. ccoonnnneecctt__ttiimmeeoouutt Type: number Default: 30 - Causes Mutt to timeout a network connection (for IMAP or POP) after + Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this many seconds if the connection is not able to be established. A - negative value causes Mutt to wait indefinitely for the connection to - succeed. + negative value causes Mutt-ng to wait indefinitely for the connection + to succeed. - 66..33..3322.. ccoonntteenntt__ttyyppee + 66..33..3344.. ccoonntteenntt__ttyyppee Type: string Default: "text/plain" Sets the default Content-Type for the body of newly composed messages. - 66..33..3333.. ccooppyy + 66..33..3355.. ccooppyy Type: quadoption Default: yes @@ -3728,29 +4174,114 @@ will be saved for later references. Also see ````$record'''', ````$save_name'''', ````$force_name'''' and ````fcc-hook''''. - 66..33..3344.. ccrryypptt__aauuttooppggpp + 66..33..3366.. ccrryypptt__aauuttooeennccrryypptt + + Type: boolean + Default: no + + Setting this variable will cause Mutt-ng to always attempt to PGP + encrypt outgoing messages. This is probably only useful in connection + to the _s_e_n_d_-_h_o_o_k command. It can be overridden by use of the _p_g_p_- + _m_e_n_u, when encryption is not required or signing is requested as well. + IF ````$smime_is_default'''' is set, then OpenSSL is used instead to + create S/MIME messages and settings can be overridden by use of the + _s_m_i_m_e_-_m_e_n_u. (Crypto only) + + 66..33..3377.. ccrryypptt__aauuttooppggpp Type: boolean Default: yes - This variable controls whether or not mutt may automatically enable + This variable controls whether or not mutt-ng may automatically enable PGP encryption/signing for messages. See also ````$crypt_autoencrypt'''', ````$crypt_replyencrypt'''', ````$crypt_autosign'''', ````$crypt_replysign'''' and ````$smime_is_default''''. - 66..33..3355.. ccrryypptt__aauuttoossmmiimmee + 66..33..3388.. ccrryypptt__aauuttoossiiggnn + + Type: boolean + Default: no + + Setting this variable will cause Mutt-ng to always attempt to + cryptographically sign outgoing messages. This can be overridden by + use of the _p_g_p_-_m_e_n_u, when signing is not required or encryption is + requested as well. If ````$smime_is_default'''' is set, then OpenSSL + is used instead to create S/MIME messages and settings can be + overridden by use of the _s_m_i_m_e_-_m_e_n_u. (Crypto only) + + 66..33..3399.. ccrryypptt__aauuttoossmmiimmee Type: boolean Default: yes - This variable controls whether or not mutt may automatically enable + This variable controls whether or not mutt-ng may automatically enable S/MIME encryption/signing for messages. See also ````$crypt_autoencrypt'''', ````$crypt_replyencrypt'''', ````$crypt_autosign'''', ````$crypt_replysign'''' and ````$smime_is_default''''. - 66..33..3366.. ddaattee__ffoorrmmaatt + 66..33..4400.. ccrryypptt__rreeppllyyeennccrryypptt + + Type: boolean + Default: yes + + If set, automatically PGP or OpenSSL encrypt replies to messages which + are encrypted. (Crypto only) + + 66..33..4411.. ccrryypptt__rreeppllyyssiiggnn + + Type: boolean + Default: no + + If set, automatically PGP or OpenSSL sign replies to messages which + are signed. + NNoottee:: this does not work on messages that are encrypted aanndd signed! + (Crypto only) + + 66..33..4422.. ccrryypptt__rreeppllyyssiiggnneennccrryypptteedd + + Type: boolean + Default: no + + If set, automatically PGP or OpenSSL sign replies to messages which + are encrypted. This makes sense in combination with + ````$crypt_replyencrypt'''', because it allows you to sign all + messages which are automatically encrypted. This works around the + problem noted in ````$crypt_replysign'''', that mutt-ng is not able to + find out whether an encrypted message is also signed. (Crypto only) + + 66..33..4433.. ccrryypptt__ttiimmeessttaammpp + + Type: boolean + Default: yes + + If set, mutt-ng will include a time stamp in the lines surrounding PGP + or S/MIME output, so spoofing such lines is more difficult. If you + are using colors to mark these lines, and rely on these, you may unset + this setting. (Crypto only) + + 66..33..4444.. ccrryypptt__uussee__ggppggmmee + + Type: boolean + Default: no + + This variable controls the use the GPGME enabled crypto backends. If + it is set and Mutt-ng was build with gpgme support, the gpgme code for + S/MIME and PGP will be used instead of the classic code. Note, that + you need to use this option in .muttrc as it won't have any effect + when used interactively. + + 66..33..4455.. ccrryypptt__vveerriiffyy__ssiigg + + Type: quadoption + Default: yes + + If ``yes'', always attempt to verify PGP or S/MIME signatures. If + ``ask'', ask whether or not to verify the signature. If ``no'', never + attempt to verify cryptographic signatures. (Crypto only) + + 66..33..4466.. ddaattee__ffoorrmmaatt Type: string Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z" @@ -3767,7 +4298,7 @@ rest of the string are expanded in the _C locale (that is in US English). - 66..33..3377.. ddeeffaauulltt__hhooookk + 66..33..4477.. ddeeffaauulltt__hhooookk Type: string Default: "~f %s !~P | (~P ~C %s)" @@ -3782,7 +4313,7 @@ matches ``alternates'') and is to or cc'ed to a user matching the given regular expression. - 66..33..3388.. ddeelleettee + 66..33..4488.. ddeelleettee Type: quadoption Default: ask-yes @@ -3792,25 +4323,25 @@ will automatically be purged without prompting. If set to _n_o, messages marked for deletion will be kept in the mailbox. - 66..33..3399.. ddeelleettee__uunnttaagg + 66..33..4499.. ddeelleettee__uunnttaagg Type: boolean Default: yes - If this option is _s_e_t, mutt will untag messages when marking them for - deletion. This applies when you either explicitly delete a message, - or when you save it to another folder. + If this option is _s_e_t, mutt-ng will untag messages when marking them + for deletion. This applies when you either explicitly delete a + message, or when you save it to another folder. - 66..33..4400.. ddiiggeesstt__ccoollllaappssee + 66..33..5500.. ddiiggeesstt__ccoollllaappssee Type: boolean Default: yes - If this option is _s_e_t, mutt's revattach menu will not show the - subparts of individual messages in a digest. To see these subparts, - press 'v' on that menu. + If this option is _s_e_t, mutt-ng's received-attachments menu will not + show the subparts of individual messages in a multipart/digest. To + see these subparts, press 'v' on that menu. - 66..33..4411.. ddiissppllaayy__ffiilltteerr + 66..33..5511.. ddiissppllaayy__ffiilltteerr Type: path Default: "" @@ -3819,14 +4350,15 @@ is viewed it is passed as standard input to ``$display_filter'', and the filtered message is read from the standard output. - 66..33..4422.. ddoottlloocckk__pprrooggrraamm + 66..33..5522.. ddoottlloocckk__pprrooggrraamm Type: path - Default: "/usr/local/bin/mutt_dotlock" + Default: "/usr/local/bin/muttng_dotlock" - Contains the path of the mutt_dotlock (8) binary to be used by mutt. + Contains the path of the muttng_dotlock (1) binary to be used by mutt- + ng. - 66..33..4433.. ddssnn__nnoottiiffyy + 66..33..5533.. ddssnn__nnoottiiffyy Type: string Default: "" @@ -3842,31 +4374,30 @@ Example: set dsn_notify="failure,delay" - 66..33..4444.. ddssnn__rreettuurrnn + 66..33..5544.. ddssnn__rreettuurrnn Type: string Default: "" NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or greater. - This variable controls how much of your message is returned in DSN messages. It may be set to either _h_d_r_s to return just the message header, or _f_u_l_l to return the full message. Example: set dsn_return=hdrs - 66..33..4455.. dduupplliiccaattee__tthhrreeaaddss + 66..33..5555.. dduupplliiccaattee__tthhrreeaaddss Type: boolean Default: yes - This variable controls whether mutt, when sorting by threads, threads - messages with the same message-id together. If it is set, it will - indicate that it thinks they are duplicates of each other with an + This variable controls whether mutt-ng, when sorting by threads, + threads messages with the same message-id together. If it is set, it + will indicate that it thinks they are duplicates of each other with an equals sign in the thread diagram. - 66..33..4466.. eeddiitt__hheeaaddeerrss + 66..33..5566.. eeddiitt__hheeaaddeerrss Type: boolean Default: no @@ -3874,44 +4405,43 @@ This option allows you to edit the header of your outgoing messages along with the body of your message. - 66..33..4477.. eeddiittoorr + 66..33..5577.. eeddiittoorr Type: path Default: "" - This variable specifies which editor is used by mutt. It defaults to - the value of the VISUAL, or EDITOR, environment variable, or to the + This variable specifies which editor is used by mutt-ng. It defaults + to the value of the VISUAL, or EDITOR, environment variable, or to the string "vi" if neither of those are set. - 66..33..4488.. eennccooddee__ffrroomm + 66..33..5588.. eennccooddee__ffrroomm Type: boolean Default: no - When _s_e_t, mutt will quoted-printable encode messages when they contain - the string "From " in the beginning of a line. Useful to avoid the - tampering certain mail delivery and transport agents tend to do with - messages. + When _s_e_t, mutt-ng will quoted-printable encode messages when they + contain the string "From " in the beginning of a line. Useful to + avoid the tampering certain mail delivery and transport agents tend to + do with messages. - 66..33..4499.. eennvveellooppee__ffrroomm + 66..33..5599.. eennvveellooppee__ffrroomm Type: boolean Default: no + When _s_e_t, mutt-ng will try to derive the message's _e_n_v_e_l_o_p_e sender + from the "From:" header. Note that this information is passed to + sendmail command using the "-f" command line switch, so don't set this + option if you are using that switch in ``$sendmail'' yourself, or if + the sendmail on your machine doesn't support that command line switch. - When _s_e_t, mutt will try to derive the message's _e_n_v_e_l_o_p_e sender from - the "From:" header. Note that this information is passed to sendmail - command using the "-f" command line switch, so don't set this option - if you are using that switch in ``$sendmail'' yourself, or if the - sendmail on your machine doesn't support that command line switch. - - 66..33..5500.. eessccaappee + 66..33..6600.. eessccaappee Type: string Default: "~" Escape character to use for functions in the builtin editor. - 66..33..5511.. ffaasstt__rreeppllyy + 66..33..6611.. ffaasstt__rreeppllyy Type: boolean Default: no @@ -3923,7 +4453,7 @@ NNoottee:: this variable has no effect when the ````$autoedit'''' variable is set. - 66..33..5522.. ffcccc__aattttaacchh + 66..33..6622.. ffcccc__aattttaacchh Type: boolean Default: yes @@ -3931,7 +4461,7 @@ This variable controls whether or not attachments on outgoing messages are saved along with the main body of your message. - 66..33..5533.. ffcccc__cclleeaarr + 66..33..6633.. ffcccc__cclleeaarr Type: boolean Default: no @@ -3940,7 +4470,22 @@ unsigned, even when the actual message is encrypted and/or signed. (PGP only) - 66..33..5544.. ffoollddeerr + 66..33..6644.. ffiillee__cchhaarrsseett + + Type: string + Default: "" + + This variable is a colon-separated list of character encoding schemes + for text file attatchments. If unset, ``$charset'' value will be used + instead. For example, the following configuration would work for + Japanese text handling: + + set file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8" + + Note: "iso-2022-*" must be put at the head of the value as shown above + if included. + + 66..33..6655.. ffoollddeerr Type: path Default: "~/Mail" @@ -3952,7 +4497,7 @@ `+' or `=' for any other variables since expansion takes place during the `set' command. - 66..33..5555.. ffoollddeerr__ffoorrmmaatt + 66..33..6666.. ffoollddeerr__ffoorrmmaatt Type: string Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f" @@ -3986,16 +4531,15 @@ %%||XX pad to the end of the line with character "X" - - 66..33..5566.. ffoolllloowwuupp__ttoo + 66..33..6677.. ffoolllloowwuupp__ttoo Type: boolean Default: yes Controls whether or not the _M_a_i_l_-_F_o_l_l_o_w_u_p_-_T_o header field is generated - when sending mail. When _s_e_t, Mutt will generate this field when you - are replying to a known mailing list, specified with the ``subscribe'' - or ````lists'''' commands. + when sending mail. When _s_e_t, Mutt-ng will generate this field when + you are replying to a known mailing list, specified with the + ``subscribe'' or ````lists'''' commands. This field has two purposes. First, preventing you from receiving duplicate copies of replies to messages which you send to mailing @@ -4007,7 +4551,7 @@ subscribed list will be sent to both the list and your address, resulting in two copies of the same email for you. - 66..33..5577.. ffoolllloowwuupp__ttoo__ppoosstteerr + 66..33..6688.. ffoolllloowwuupp__ttoo__ppoosstteerr Type: quadoption Default: ask-yes @@ -4016,18 +4560,18 @@ _F_o_l_l_o_w_u_p_-_T_o header, follow-up to newsgroup function is not permitted. The message will be mailed to the submitter of the message via mail. - 66..33..5588.. ffoorrccee__nnaammee + 66..33..6699.. ffoorrccee__nnaammee Type: boolean Default: no - This variable is similar to ````$save_name'''', except that Mutt will - store a copy of your outgoing message by the username of the address - you are sending to even if that mailbox does not exist. + This variable is similar to ````$save_name'''', except that Mutt-ng + will store a copy of your outgoing message by the username of the + address you are sending to even if that mailbox does not exist. Also see the ````$record'''' variable. - 66..33..5599.. ffoorrwwaarrdd__ddeeccooddee + 66..33..7700.. ffoorrwwaarrdd__ddeeccooddee Type: boolean Default: yes @@ -4037,7 +4581,17 @@ This variable is only used, if ````$mime_forward'''' is _u_n_s_e_t, otherwise ````$mime_forward_decode'''' is used instead. - 66..33..6600.. ffoorrwwaarrdd__eeddiitt + 66..33..7711.. ffoorrwwaarrdd__ddeeccrryypptt + + Type: boolean + Default: yes + + Controls the handling of encrypted messages when forwarding a message. + When set, the outer layer of encryption is stripped off. This + variable is only used if ````$mime_forward'''' is _s_e_t and + ````$mime_forward_decode'''' is _u_n_s_e_t. (PGP only) + + 66..33..7722.. ffoorrwwaarrdd__eeddiitt Type: quadoption Default: yes @@ -4046,7 +4600,7 @@ placed in the editor when forwarding messages. For those who always want to forward with no modification, use a setting of ``no''. - 66..33..6611.. ffoorrwwaarrdd__ffoorrmmaatt + 66..33..7733.. ffoorrwwaarrdd__ffoorrmmaatt Type: string Default: "[%a: %s]" @@ -4055,7 +4609,7 @@ It uses the same format sequences as the ````$index_format'''' variable. - 66..33..6622.. ffoorrwwaarrdd__qquuoottee + 66..33..7744.. ffoorrwwaarrdd__qquuoottee Type: boolean Default: no @@ -4064,7 +4618,7 @@ (when ````$mime_forward'''' is _u_n_s_e_t) will be quoted using ````$indent_string''''. - 66..33..6633.. ffrroomm + 66..33..7755.. ffrroomm Type: e-mail address Default: "" @@ -4076,24 +4630,24 @@ Defaults to the contents of the environment variable EMAIL. - 66..33..6644.. ggeeccooss__mmaasskk + 66..33..7766.. ggeeccooss__mmaasskk Type: regular expression Default: "^[^,]*" - A regular expression used by mutt to parse the GECOS field of a + A regular expression used by mutt-ng to parse the GECOS field of a password entry when expanding the alias. By default the regular expression is set to "^[^,]*" which will return the string up to the first "," encountered. If the GECOS field contains a string like "lastname, firstname" then you should set the gecos_mask=".*". This can be useful if you see the following behavior: you address a e- - mail to user ID stevef whose full name is Steve Franklin. If mutt + mail to user ID stevef whose full name is Steve Franklin. If mutt-ng expands stevef to "Franklin" stevef@foo.bar then you should set the gecos_mask to a regular expression that will match the whole name so - mutt will expand "Franklin" to "Franklin, Steve". + mutt-ng will expand "Franklin" to "Franklin, Steve". - 66..33..6655.. ggrroouupp__iinnddeexx__ffoorrmmaatt + 66..33..7777.. ggrroouupp__iinnddeexx__ffoorrmmaatt Type: string Default: "%4C %M%N %5s %-45.45f %d" @@ -4102,17 +4656,17 @@ your personal taste. This string is similar to ````index_format'''', but has its own set of printf()-like sequences: - %C current newsgroup number - %d description of newsgroup (becomes from server) - %f newsgroup name - %M - if newsgroup not allowed for direct post (moderated for example) - %N N if newsgroup is new, u if unsubscribed, blank otherwise - %n number of new articles in newsgroup - %s number of unread articles in newsgroup - %>X right justify the rest of the string and pad with character "X" - %|X pad to the end of the line with character "X" + %C current newsgroup number + %d description of newsgroup (becomes from server) + %f newsgroup name + %M - if newsgroup not allowed for direct post (moderated for example) + %N N if newsgroup is new, u if unsubscribed, blank otherwise + %n number of new articles in newsgroup + %s number of unread articles in newsgroup + %>X right justify the rest of the string and pad with character "X" + %|X pad to the end of the line with character "X" - 66..33..6666.. hhddrrss + 66..33..7788.. hhddrrss Type: boolean Default: yes @@ -4122,16 +4676,16 @@ a new message or replying in order to take effect. If set, the user defined header fields are added to every new message. - 66..33..6677.. hheeaaddeerr + 66..33..7799.. hheeaaddeerr Type: boolean Default: no - When set, this variable causes Mutt to include the header of the + When set, this variable causes Mutt-ng to include the header of the message you are replying to into the edit buffer. The ````$weed'''' setting applies. - 66..33..6688.. hheellpp + 66..33..8800.. hheellpp Type: boolean Default: yes @@ -4141,54 +4695,64 @@ NNoottee:: The binding will not be displayed correctly if the function is bound to a sequence rather than a single keystroke. Also, the help - line may not be updated if a binding is changed while Mutt is running. - Since this variable is primarily aimed at new users, neither of these - should present a major problem. + line may not be updated if a binding is changed while Mutt-ng is + running. Since this variable is primarily aimed at new users, neither + of these should present a major problem. - 66..33..6699.. hhiiddddeenn__hhoosstt + 66..33..8811.. hhiiddddeenn__hhoosstt Type: boolean Default: no - When set, mutt will skip the host name part of ````$hostname'''' + When set, mutt-ng will skip the host name part of ````$hostname'''' variable when adding the domain part to addresses. This variable does not affect the generation of Message-IDs, and it will not lead to the cut-off of first-level domains. - 66..33..7700.. hhiiddee__lliimmiitteedd + + 66..33..8822.. hhiiddee__lliimmiitteedd Type: boolean Default: no - When set, mutt will not show the presence of messages that are hidden - by limiting, in the thread tree. + When set, mutt-ng will not show the presence of messages that are + hidden by limiting, in the thread tree. + + 66..33..8833.. hhiiddee__mmiissssiinngg + + Type: boolean + Default: yes - 66..33..7711.. hhiiddee__mmiissssiinngg + When set, mutt-ng will not show the presence of missing messages in + the thread tree. + + 66..33..8844.. hhiiddee__tthhrreeaadd__ssuubbjjeecctt Type: boolean Default: yes - When set, mutt will not show the presence of missing messages in the - thread tree. + When set, mutt-ng will not show the subject of messages in the thread + tree that have the same subject as their parent or closest previously + displayed sibling. - 66..33..7722.. hhiiddee__ttoopp__lliimmiitteedd + 66..33..8855.. hhiiddee__ttoopp__lliimmiitteedd Type: boolean Default: no - When set, mutt will not show the presence of messages that are hidden - by limiting, at the top of threads in the thread tree. Note that when - ``$hide_missing'' is set, this option will have no effect. + When set, mutt-ng will not show the presence of messages that are + hidden by limiting, at the top of threads in the thread tree. Note + that when ``$hide_missing'' is set, this option will have no effect. - 66..33..7733.. hhiiddee__ttoopp__mmiissssiinngg + 66..33..8866.. hhiiddee__ttoopp__mmiissssiinngg Type: boolean Default: yes - When set, mutt will not show the presence of missing messages at the - top of threads in the thread tree. Note that when ``$hide_limited'' - is set, this option will have no effect. + When set, mutt-ng will not show the presence of missing messages at + the top of threads in the thread tree. Note that when + ``$hide_limited'' is set, this option will have no effect. - 66..33..7744.. hhiissttoorryy + 66..33..8877.. hhiissttoorryy Type: number Default: 10 @@ -4197,14 +4761,15 @@ the string history buffer. The buffer is cleared each time the variable is set. - 66..33..7755.. hhoonnoorr__ffoolllloowwuupp__ttoo + 66..33..8888.. hhoonnoorr__ffoolllloowwuupp__ttoo Type: quadoption Default: yes This variable controls whether or not a Mail-Followup-To header is honored when group-replying to a message. - 66..33..7766.. hhoossttnnaammee + + 66..33..8899.. hhoossttnnaammee Type: string Default: "" @@ -4213,38 +4778,39 @@ addresses. This overrides the compile time definition obtained from /etc/resolv.conf. - 66..33..7777.. iiggnnoorree__lliisstt__rreeppllyy__ttoo + 66..33..9900.. iiggnnoorree__lliisstt__rreeppllyy__ttoo Type: boolean Default: no Affects the behaviour of the _r_e_p_l_y function when replying to messages from mailing lists. When set, if the ``Reply-To:'' field is set to - the same value as the ``To:'' field, Mutt assumes that the ``Reply- + the same value as the ``To:'' field, Mutt-ng assumes that the ``Reply- To:'' field was set by the mailing list to automate responses to the list, and will ignore this field. To direct a response to the mailing list when this option is set, use the _l_i_s_t_-_r_e_p_l_y function; _g_r_o_u_p_-_r_e_p_l_y will reply to both the sender and the list. - 66..33..7788.. iimmaapp__aauutthheennttiiccaattoorrss + 66..33..9911.. iimmaapp__aauutthheennttiiccaattoorrss Type: string Default: "" - This is a colon-delimited list of authentication methods mutt may - attempt to use to log in to an IMAP server, in the order mutt should - try them. Authentication methods are either 'login' or the right side - of an IMAP 'AUTH=xxx' capability string, eg 'digest-md5', parameter is - unset (the default) mutt will try all available methods, in order from - most-secure to least-secure. + This is a colon-delimited list of authentication methods mutt-ng may + attempt to use to log in to an IMAP server, in the order mutt-ng + should try them. Authentication methods are either 'login' or the + right side of an IMAP 'AUTH=xxx' capability string, eg 'digest-md5', + 'gssapi' or 'cram-md5'. This parameter is case-insensitive. If this + parameter is unset (the default) mutt-ng will try all available + methods, in order from most-secure to least-secure. Example: set imap_authenticators="gssapi:cram-md5:login" - NNoottee:: Mutt will only fall back to other authentication methods if the - previous methods are unavailable. If a method is available but - authentication fails, mutt will not connect to the IMAP server. + NNoottee:: Mutt-ng will only fall back to other authentication methods if + the previous methods are unavailable. If a method is available but + authentication fails, mutt-ng will not connect to the IMAP server. - 66..33..7799.. iimmaapp__ddeelliimm__cchhaarrss + 66..33..9922.. iimmaapp__ddeelliimm__cchhaarrss Type: string Default: "/." @@ -4253,15 +4819,26 @@ folder separators for displaying IMAP paths. In particular it helps in using the '=' shortcut for your _f_o_l_d_e_r variable. - 66..33..8800.. iimmaapp__ffoorrccee__ssssll + 66..33..9933.. iimmaapp__ffoorrccee__ssssll Type: boolean Default: no - If this variable is set, Mutt will always use SSL when connecting to - IMAP servers. + If this variable is set, Mutt-ng will always use SSL when connecting + to IMAP servers. + + 66..33..9944.. iimmaapp__hheeaaddeerrss + + Type: string + Default: "" + + Mutt-ng requests these header fields in addition to the default + headers ("DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE + CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL") from IMAP + servers before displaying the index menu. You may want to add more + headers for spam detection. NNoottee:: This is a space separated list. - 66..33..8811.. iimmaapp__hhoommee__nnaammeessppaaccee + 66..33..9955.. iimmaapp__hhoommee__nnaammeessppaaccee Type: string Default: "" @@ -4270,21 +4847,21 @@ the IMAP browser. If you see something else, you may set this variable to the IMAP path to your folders. - 66..33..8822.. iimmaapp__kkeeeeppaalliivvee + 66..33..9966.. iimmaapp__kkeeeeppaalliivvee Type: number Default: 900 This variable specifies the maximum amount of time in seconds that - mutt will wait before polling open IMAP connections, to prevent the - server from closing them before mutt has finished with them. The + mutt-ng will wait before polling open IMAP connections, to prevent the + server from closing them before mutt-ng has finished with them. The default is well within the RFC-specified minimum amount of time (30 minutes) before a server is allowed to do this, but in practice the RFC does get violated every now and then. Reduce this number if you find yourself getting disconnected from your IMAP server due to inactivity. - 66..33..8833.. iimmaapp__lliisstt__ssuubbssccrriibbeedd + 66..33..9977.. iimmaapp__lliisstt__ssuubbssccrriibbeedd Type: boolean Default: no @@ -4293,49 +4870,57 @@ only subscribed folders or all folders. This can be toggled in the IMAP browser with the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d function. - 66..33..8844.. iimmaapp__ppaassss + 66..33..9988.. iimmaapp__ppaassss Type: string Default: "" - Specifies the password for your IMAP account. If unset, Mutt will + Specifies the password for your IMAP account. If unset, Mutt-ng will prompt you for your password when you invoke the fetch-mail function. WWaarrnniinngg: you should only use this option when you are on a fairly - secure machine, because the superuser can read your muttrc even if you - are the only one who can read the file. + secure machine, because the superuser can read your muttngrc even if + you are the only one who can read the file. - 66..33..8855.. iimmaapp__ppaassssiivvee + 66..33..9999.. iimmaapp__ppaassssiivvee Type: boolean Default: yes - When set, mutt will not open new IMAP connections to check for new - mail. Mutt will only check for new mail over existing IMAP + When set, mutt-ng will not open new IMAP connections to check for new + mail. Mutt-ng will only check for new mail over existing IMAP connections. This is useful if you don't want to be prompted to - user/password pairs on mutt invocation, or if opening the connection - is slow. + user/password pairs on mutt-ng invocation, or if opening the + connection is slow. - 66..33..8866.. iimmaapp__ppeeeekk + 66..33..110000.. iimmaapp__ppeeeekk Type: boolean Default: yes - If set, mutt will avoid implicitly marking your mail as read whenever - you fetch a message from the server. This is generally a good thing, - but can make closing an IMAP folder somewhat slower. This option - exists to appease speed freaks. + If set, mutt-ng will avoid implicitly marking your mail as read + whenever you fetch a message from the server. This is generally a good + thing, but can make closing an IMAP folder somewhat slower. This + option exists to appease speed freaks. + + 66..33..110011.. iimmaapp__rreeccoonnnneecctt + + Type: quadoption + Default: ask-yes + + Controls whether or not Mutt-ng will try to reconnect to IMAP server + when the connection is lost. - 66..33..8877.. iimmaapp__sseerrvveerrnnooiissee + 66..33..110022.. iimmaapp__sseerrvveerrnnooiissee Type: boolean Default: yes - When set, mutt will display warning messages from the IMAP server as - error messages. Since these messages are often harmless, or generated - due to configuration problems on the server which are out of the - users' hands, you may wish to suppress them at some point. + When set, mutt-ng will display warning messages from the IMAP server + as error messages. Since these messages are often harmless, or + generated due to configuration problems on the server which are out of + the users' hands, you may wish to suppress them at some point. - 66..33..8888.. iimmaapp__uusseerr + 66..33..110033.. iimmaapp__uusseerr Type: string Default: "" @@ -4344,18 +4929,18 @@ This variable defaults to your user name on the local machine. - 66..33..8899.. iimmpplliicciitt__aauuttoovviieeww + 66..33..110044.. iimmpplliicciitt__aauuttoovviieeww Type: boolean Default: no - If set to ``yes'', mutt will look for a mailcap entry with the + If set to ``yes'', mutt-ng will look for a mailcap entry with the copiousoutput flag set for _e_v_e_r_y MIME attachment it doesn't have an - internal viewer defined for. If such an entry is found, mutt will use - the viewer defined in that entry to convert the body part to text + internal viewer defined for. If such an entry is found, mutt-ng will + use the viewer defined in that entry to convert the body part to text form. - 66..33..9900.. iinncclluuddee + 66..33..110055.. iinncclluuddee Type: quadoption Default: ask-yes @@ -4363,7 +4948,15 @@ Controls whether or not a copy of the message(s) you are replying to is included in your reply. - 66..33..9911.. iinnddeenntt__ssttrriinngg + 66..33..110066.. iinncclluuddee__oonnllyyffiirrsstt + + Type: boolean + Default: no + + Controls whether or not Mutt-ng includes only the first attachment of + the message you are replying. + + 66..33..110077.. iinnddeenntt__ssttrriinngg Type: string Default: "> " @@ -4372,7 +4965,7 @@ message to which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. - 66..33..9922.. iinnddeexx__ffoorrmmaatt + 66..33..110088.. iinnddeexx__ffoorrmmaatt Type: string Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s" @@ -4382,7 +4975,7 @@ ``Format strings'' are similar to the strings used in the ``C'' function printf to format output (see the man page for more detail). - The following sequences are defined in Mutt: + The following sequences are defined in Mutt-ng: %%aa address of the author @@ -4411,6 +5004,8 @@ %%FF author name, or recipient name if the message is from you + %%HH spam attribute(s) of this message + %%gg newsgroup name (if compiled with nntp support) %%ii message-id of the current message @@ -4430,8 +5025,8 @@ %%nn author's real name (or address if missing) - %%OO (_O_riginal save folder) Where mutt would formerly have stashed - the message: list name or recipient name if no list + %%OO (_O_riginal save folder) Where mutt-ng would formerly have + stashed the message: list name or recipient name if no list %%ss subject of the message @@ -4483,13 +5078,13 @@ See also: ````$to_chars''''. - 66..33..9933.. iinneewwss + 66..33..110099.. iinneewwss Type: path Default: "" If set, specifies the program and arguments used to deliver news - posted by Mutt. Otherwise, mutt posts article using current + posted by Mutt-ng. Otherwise, mutt-ng posts article using current connection to news server. The following printf-style sequence is understood: @@ -4497,14 +5092,14 @@ Example: set inews="/usr/local/bin/inews -hS" - 66..33..9944.. iissppeellll + 66..33..111100.. iissppeellll Type: path Default: "/usr/bin/ispell" How to invoke ispell (GNU's spell-checking software). - 66..33..9955.. kkeeeepp__ffllaaggggeedd + 66..33..111111.. kkeeeepp__ffllaaggggeedd Type: boolean Default: no @@ -4513,43 +5108,54 @@ spool mailbox to your ````$mbox'''' mailbox, or as a result of a ````mbox-hook'''' command. - 66..33..9966.. llooccaallee + 66..33..111122.. lliisstt__rreeppllyy - Type: string - Default: "C" + Type: quadoption + Default: no + + When set, address replies to the mailing list the original message + came from (instead to the author only). Setting this option to ``ask- + yes'' or ``ask-no'' will ask if you really intended to reply to the + author only. + + 66..33..111133.. llooccaallee + + Type: string + Default: "C" The locale used by _s_t_r_f_t_i_m_e_(_3_) to format dates. Legal values are the strings your system accepts for the locale variable _L_C___T_I_M_E. - 66..33..9977.. mmaaiill__cchheecckk + 66..33..111144.. mmaaiill__cchheecckk Type: number Default: 5 - This variable configures how often (in seconds) mutt should look for - new mail. + This variable configures how often (in seconds) mutt-ng should look + for new mail. - 66..33..9988.. mmaaiillccaapp__ppaatthh + 66..33..111155.. mmaaiillccaapp__ppaatthh Type: string Default: "" This variable specifies which files to consult when attempting to - display MIME bodies not directly supported by Mutt. + display MIME bodies not directly supported by Mutt-ng. - 66..33..9999.. mmaaiillccaapp__ssaanniittiizzee + 66..33..111166.. mmaaiillccaapp__ssaanniittiizzee Type: boolean Default: yes - If set, mutt will restrict possible characters in mailcap % expandos - to a well-defined set of safe characters. This is the safe setting, - but we are not sure it doesn't break some more advanced MIME stuff. + If set, mutt-ng will restrict possible characters in mailcap % + expandos to a well-defined set of safe characters. This is the safe + setting, but we are not sure it doesn't break some more advanced MIME + stuff. DDOONN''TT CCHHAANNGGEE TTHHIISS SSEETTTTIINNGG UUNNLLEESSSS YYOOUU AARREE RREEAALLLLYY SSUURREE WWHHAATT YYOOUU AARREE DDOOIINNGG!! - 66..33..110000.. mmaaiillddiirr__ttrraasshh + 66..33..111177.. mmaaiillddiirr__ttrraasshh Type: boolean Default: no @@ -4559,17 +5165,17 @@ maildir-style mailboxes. Setting it will have no effect on other mailbox types. - 66..33..110011.. mmaarrkk__oolldd + 66..33..111188.. mmaarrkk__oolldd Type: boolean Default: yes - Controls whether or not mutt marks _n_e_w uunnrreeaadd messages as _o_l_d if you - exit a mailbox without reading them. With this option set, the next - time you start mutt, the messages will show up with an "O" next to - them in the index menu, indicating that they are old. + Controls whether or not mutt-ng marks _n_e_w uunnrreeaadd messages as _o_l_d if + you exit a mailbox without reading them. With this option set, the + next time you start mutt-ng, the messages will show up with an "O" + next to them in the index menu, indicating that they are old. - 66..33..110022.. mmaarrkkeerrss + 66..33..111199.. mmaarrkkeerrss Type: boolean Default: yes @@ -4578,7 +5184,7 @@ ``+'' marker is displayed at the beginning of wrapped lines. Also see the ````$smart_wrap'''' variable. - 66..33..110033.. mmaasskk + 66..33..112200.. mmaasskk Type: regular expression Default: "!^\.[^.]" @@ -4587,7 +5193,17 @@ the _n_o_t operator ``!''. Only files whose names match this mask will be shown. The match is always case-sensitive. - 66..33..110044.. mmbbooxx + 66..33..112211.. mmaaxx__lliinnee__lleennggtthh + + Type: number + Default: 0 + + When set, the maximum line length for displaying f=f messages is + limited to this length. A value of 0 (which is also the default) means + that the maximum line length is determined by the terminal width and + ``$wrapmargin''. + + 66..33..112222.. mmbbooxx Type: path Default: "~/mbox" @@ -4595,7 +5211,7 @@ This specifies the folder into which read mail in your ````$spoolfile'''' folder will be appended. - 66..33..110055.. mmbbooxx__ttyyppee + 66..33..112233.. mmbbooxx__ttyyppee Type: folder magic Default: mbox @@ -4603,15 +5219,15 @@ The default mailbox type used when creating new folders. May be any of mbox, MMDF, MH and Maildir. - 66..33..110066.. mmeettoooo + 66..33..112244.. mmeennuu__ccoonntteexxtt - Type: boolean - Default: no + Type: number + Default: 0 - If unset, Mutt will remove your address (see the ``alternates'' - command) from the list of recipients when replying to a message. + This variable controls the number of lines of context that are given + when scrolling through menus. (Similar to ````$pager_context''''.) - 66..33..110077.. mmeennuu__ssccrroollll + 66..33..112255.. mmeennuu__ssccrroollll Type: boolean Default: no @@ -4621,50 +5237,68 @@ the next or previous page of the menu is displayed (useful for slow links to avoid many redraws). - 66..33..110088.. mmeettaa__kkeeyy + 66..33..112266.. mmeessssaaggee__ffoorrmmaatt + + Type: string + Default: "%s" + + This is the string displayed in the ``attachment'' menu for + attachments of type message/rfc822. For a full listing of defined + printf()-like sequences see the section on ````$index_format''''. + + 66..33..112277.. mmeettaa__kkeeyy Type: boolean Default: no - If set, forces Mutt to interpret keystrokes with the high bit (bit 8) - set as if the user had pressed the ESC key and whatever key remains + If set, forces Mutt-ng to interpret keystrokes with the high bit (bit + 8) set as if the user had pressed the ESC key and whatever key remains after having the high bit removed. For example, if the key pressed has an ASCII value of 0xf4, then this is treated as if the user had pressed ESC then ``x''. This is because the result of removing the high bit from ``0xf4'' is ``0x74'', which is the ASCII character ``x''. - 66..33..110099.. mmhh__ppuurrggee + 66..33..112288.. mmeettoooo + + Type: boolean + Default: no + + If unset, Mutt-ng will remove your address (see the ``alternates'' + command) from the list of recipients when replying to a message. + + 66..33..112299.. mmhh__ppuurrggee Type: boolean Default: no - When unset, mutt will mimic mh's behaviour and rename deleted messages - to _,_<_o_l_d _f_i_l_e _n_a_m_e_> in mh folders instead of really deleting them. If - the variable is set, the message files will simply be deleted. + When unset, mutt-ng will mimic mh's behaviour and rename deleted + messages to _,_<_o_l_d _f_i_l_e _n_a_m_e_> in mh folders instead of really deleting + them. If the variable is set, the message files will simply be + deleted. - 66..33..111100.. mmhh__sseeqq__ffllaaggggeedd + 66..33..113300.. mmhh__sseeqq__ffllaaggggeedd Type: string Default: "flagged" The name of the MH sequence used for flagged messages. - 66..33..111111.. mmhh__sseeqq__rreepplliieedd + 66..33..113311.. mmhh__sseeqq__rreepplliieedd Type: string Default: "replied" The name of the MH sequence used to tag replied messages. - 66..33..111122.. mmhh__sseeqq__uunnsseeeenn + 66..33..113322.. mmhh__sseeqq__uunnsseeeenn Type: string Default: "unseen" The name of the MH sequence used for unseen messages. - 66..33..111133.. mmiimmee__ffoorrwwaarrdd + 66..33..113333.. mmiimmee__ffoorrwwaarrdd Type: quadoption Default: no @@ -4678,7 +5312,7 @@ Also see ````$forward_decode'''' and ````$mime_forward_decode''''. - 66..33..111144.. mmiimmee__ffoorrwwaarrdd__ddeeccooddee + 66..33..113344.. mmiimmee__ffoorrwwaarrdd__ddeeccooddee Type: boolean Default: no @@ -4687,7 +5321,7 @@ forwarding a message while ````$mime_forward'''' is _s_e_t. Otherwise ````$forward_decode'''' is used instead. - 66..33..111155.. mmiimmee__ffoorrwwaarrdd__rreesstt + 66..33..113355.. mmiimmee__ffoorrwwaarrdd__rreesstt Type: quadoption Default: yes @@ -4697,7 +5331,7 @@ manner will be attached to the newly composed message if this option is set. - 66..33..111166.. mmiimmee__ssuubbjjeecctt + 66..33..113366.. mmiimmee__ssuubbjjeecctt Type: boolean Default: yes @@ -4706,7 +5340,7 @@ encoded according to RFC2047 to base64. This is useful when message is Usenet article, because MIME for news is nonstandard feature. - 66..33..111177.. mmiixx__eennttrryy__ffoorrmmaatt + 66..33..113377.. mmiixx__eennttrryy__ffoorrmmaatt Type: string Default: "%4n %c %-16s %a" @@ -4723,7 +5357,7 @@ %%aa The remailer's e-mail address. - 66..33..111188.. mmiixxmmaasstteerr + 66..33..113388.. mmiixxmmaasstteerr Type: path Default: "mixmaster" @@ -4733,25 +5367,55 @@ of known remailers, and to finally send a message through the mixmaster chain. - 66..33..111199.. mmoovvee + 66..33..113399.. mmoovvee Type: quadoption Default: ask-no - Controls whether you will be asked to confirm moving read messages - from your spool mailbox to your ````$mbox'''' mailbox, or as a result - of a ````mbox-hook'''' command. + Controls whether or not Mutt-ng will move read messages from your + spool mailbox to your ````$mbox'''' mailbox, or as a result of a + ````mbox-hook'''' command. - 66..33..112200.. mmeessssaaggee__ffoorrmmaatt + 66..33..114400.. mmssggiidd__ffoorrmmaatt Type: string - Default: "%s" + Default: "%Y%m%d%h%M%s.G%P%p" - This is the string displayed in the ``attachment'' menu for - attachments of type message/rfc822. For a full listing of defined - printf()-like sequences see the section on ````$index_format''''. + This is the format for the ``local part'' of the message-IDs generated + by Mutt-ng. The format string contains of one or more characters. The + '%' character marks that certain data will be added to the string, + similar to printf(). The following characters are allowed: + + %%dd the current day of month + + %%hh the current hour + + %%mm the current month + + %%MM the current minute + + %%OO the current UNIX timestamp (octal) + + %%pp the process ID + + %%PP the current message-ID prefix (a character rotating with every + message-ID being generated) + + %%rr a random integer value (decimal) + + %%RR a random integer value (hexadecimal) + + %%ss the current second + + %%TT the current UNIX timestamp (decimal) - 66..33..112211.. nnaarrrrooww__ttrreeee + %%XX the current UNIX timestamp (hexadecimal) + + %%YY the current year (Y2K compliant) + + %%%% the '%' character + + 66..33..114411.. nnaarrrrooww__ttrreeee Type: boolean Default: no @@ -4759,16 +5423,16 @@ This variable, when set, makes the thread tree narrower, allowing deeper threads to fit on the screen. - 66..33..112222.. nneewwss__ccaacchhee__ddiirr + 66..33..114422.. nneewwss__ccaacchhee__ddiirr Type: path Default: "~/.mutt" - This variable pointing to directory where Mutt will save cached news - articles headers in. If _u_n_s_e_t, headers will not be saved at all and - will be reloaded each time when you enter to newsgroup. + This variable pointing to directory where Mutt-ng will save cached + news articles headers in. If _u_n_s_e_t, headers will not be saved at all + and will be reloaded each time when you enter to newsgroup. - 66..33..112233.. nneewwss__sseerrvveerr + 66..33..114433.. nneewwss__sseerrvveerr Type: string Default: "" @@ -4780,7 +5444,7 @@ [nntp[s]://][username[:password]@]newsserver[:port] - 66..33..112244.. nneewwssrrcc + 66..33..114444.. nneewwssrrcc Type: path Default: "~/.newsrc" @@ -4791,7 +5455,7 @@ %s newsserver name - 66..33..112255.. nnnnttpp__ccoonntteexxtt + 66..33..114455.. nnnnttpp__ccoonntteexxtt Type: number Default: 1000 @@ -4801,7 +5465,7 @@ number, oldest articles will be ignored. Also controls how many articles headers will be saved in cache when you quit newsgroup. - 66..33..112266.. nnnnttpp__llooaadd__ddeessccrriippttiioonn + 66..33..114466.. nnnnttpp__llooaadd__ddeessccrriippttiioonn Type: boolean Default: yes @@ -4810,41 +5474,50 @@ must be loaded when newsgroup is added to list (first time list loading or new newsgroup adding). - 66..33..112277.. nnnnttpp__uusseerr - - Type: string - Default: "" - - Your login name on the NNTP server. If _u_n_s_e_t and NNTP server requires - authentification, Mutt will prompt you for your account name when you - connect to newsserver. - - 66..33..112288.. nnnnttpp__ppaassss + 66..33..114477.. nnnnttpp__ppaassss Type: string Default: "" Your password for NNTP account. - 66..33..112299.. nnnnttpp__ppoollll + 66..33..114488.. nnnnttpp__ppoollll Type: number Default: 60 The time in seconds until any operations on newsgroup except post new - article will cause recheck for new news. If set to 0, Mutt will + article will cause recheck for new news. If set to 0, Mutt-ng will recheck newsgroup on each operation in index (stepping, read article, etc.). - 66..33..113300.. nnnnttpp__rreeccoonnnneecctt + 66..33..114499.. nnnnttpp__rreeccoonnnneecctt Type: quadoption Default: ask-yes - Controls whether or not Mutt will try to reconnect to newsserver when - connection lost. + Controls whether or not Mutt-ng will try to reconnect to newsserver + when connection lost. + + 66..33..115500.. nnnnttpp__uusseerr + + Type: string + Default: "" + + Your login name on the NNTP server. If _u_n_s_e_t and NNTP server requires + authentification, Mutt-ng will prompt you for your account name when + you connect to newsserver. + + 66..33..115511.. ooppeerraattiinngg__ssyysstteemm - 66..33..113311.. ppaaggeerr + Type: string + Default: "" + + This specifies the operating system name for the User-Agent header. If + this is unset, it will be set to the operating system name that + uname(2) returns. If uname(2) fails, "UNIX" will be used. + + 66..33..115522.. ppaaggeerr Type: path Default: "builtin" @@ -4855,21 +5528,21 @@ like to use. Using an external pager may have some disadvantages: Additional - keystrokes are necessary because you can't call mutt functions + keystrokes are necessary because you can't call mutt-ng functions directly from the pager, and screen resizes cause lines longer than the screen width to be badly formatted in the help menu. - 66..33..113322.. ppaaggeerr__ccoonntteexxtt + 66..33..115533.. ppaaggeerr__ccoonntteexxtt Type: number Default: 0 This variable controls the number of lines of context that are given when displaying the next or previous page in the internal pager. By - default, Mutt will display the line after the last one on the screen - at the top of the next page (0 lines of context). + default, Mutt-ng will display the line after the last one on the + screen at the top of the next page (0 lines of context). - 66..33..113333.. ppaaggeerr__ffoorrmmaatt + 66..33..115544.. ppaaggeerr__ffoorrmmaatt Type: string Default: "-%Z- %C/%m: %-20.20n %s" @@ -4879,7 +5552,7 @@ pager. The valid sequences are listed in the ````$index_format'''' section. - 66..33..113344.. ppaaggeerr__iinnddeexx__lliinneess + 66..33..115555.. ppaaggeerr__iinnddeexx__lliinneess Type: number Default: 0 @@ -4896,7 +5569,7 @@ less than _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s, then the index will only use as many lines as it needs. - 66..33..113355.. ppaaggeerr__ssttoopp + 66..33..115566.. ppaaggeerr__ssttoopp Type: boolean Default: no @@ -4904,130 +5577,103 @@ When set, the internal-pager will nnoott move to the next message when you are at the end of a message and invoke the _n_e_x_t_-_p_a_g_e function. - 66..33..113366.. ccrryypptt__aauuttoossiiggnn + 66..33..115577.. ppggpp__aauuttoo__ddeeccooddee Type: boolean Default: no - Setting this variable will cause Mutt to always attempt to - cryptographically sign outgoing messages. This can be overridden by - use of the _p_g_p_-_m_e_n_u, when signing is not required or encryption is - requested as well. If ````$smime_is_default'''' is set, then OpenSSL - is used instead to create S/MIME messages and settings can be - overridden by use of the _s_m_i_m_e_-_m_e_n_u. (Crypto only) + If set, mutt-ng will automatically attempt to decrypt traditional PGP + messages whenever the user performs an operation which ordinarily + would result in the contents of the message being operated on. For + example, if the user displays a pgp-traditional message which has not + been manually checked with the check-traditional-pgp function, mutt-ng + will automatically check the message for traditional pgp. - 66..33..113377.. ccrryypptt__aauuttooeennccrryypptt + 66..33..115588.. ppggpp__aauuttooiinnlliinnee Type: boolean Default: no - Setting this variable will cause Mutt to always attempt to PGP encrypt - outgoing messages. This is probably only useful in connection to the - _s_e_n_d_-_h_o_o_k command. It can be overridden by use of the _p_g_p_-_m_e_n_u, when - encryption is not required or signing is requested as well. IF - ````$smime_is_default'''' is set, then OpenSSL is used instead to - create S/MIME messages and settings can be overridden by use of the - _s_m_i_m_e_-_m_e_n_u. (Crypto only) - 66..33..113388.. ppggpp__iiggnnoorree__ssuubbkkeeyyss + This option controls whether Mutt-ng generates old-style inline + (traditional) PGP encrypted or signed messages under certain + circumstances. This can be overridden by use of the _p_g_p_-_m_e_n_u, when + inline is not required. - Type: boolean - Default: yes + Note that Mutt-ng might automatically use PGP/MIME for messages which + consist of more than a single MIME part. Mutt-ng can be configured to + ask before sending PGP/MIME messages when inline (traditional) would + not work. See also: ````$pgp_mime_auto''''. - Setting this variable will cause Mutt to ignore OpenPGP subkeys. - Instead, the principal key will inherit the subkeys' capabilities. - Unset this if you want to play interesting key selection games. (PGP - only) + Also note that using the old-style PGP message format is ssttrroonnggllyy + ddeepprreeccaatteedd. (PGP only) - 66..33..113399.. ccrryypptt__rreeppllyyeennccrryypptt + 66..33..115599.. ppggpp__cchheecckk__eexxiitt Type: boolean Default: yes - If set, automatically PGP or OpenSSL encrypt replies to messages which - are encrypted. (Crypto only) - - 66..33..114400.. ccrryypptt__rreeppllyyssiiggnn - - Type: boolean - Default: no - - If set, automatically PGP or OpenSSL sign replies to messages which - are signed. + If set, mutt-ng will check the exit code of the PGP subprocess when + signing or encrypting. A non-zero exit code means that the subprocess + failed. (PGP only) - NNoottee:: this does not work on messages that are encrypted aanndd signed! - (Crypto only) + 66..33..116600.. ppggpp__cclleeaarrssiiggnn__ccoommmmaanndd - 66..33..114411.. ccrryypptt__rreeppllyyssiiggnneennccrryypptteedd + Type: string + Default: "" - Type: boolean - Default: no + This format is used to create a old-style "clearsigned" PGP message. + Note that the use of this format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - If set, automatically PGP or OpenSSL sign replies to messages which - are encrypted. This makes sense in combination with - ````$crypt_replyencrypt'''', because it allows you to sign all - messages which are automatically encrypted. This works around the - problem noted in ````$crypt_replysign'''', that mutt is not able to - find out whether an encrypted message is also signed. (Crypto only) + 66..33..116611.. ppggpp__ddeeccooddee__ccoommmmaanndd - 66..33..114422.. ccrryypptt__ttiimmeessttaammpp + Type: string + Default: "" - Type: boolean - Default: yes + This format strings specifies a command which is used to decode + application/pgp attachments. - If set, mutt will include a time stamp in the lines surrounding PGP or - S/MIME output, so spoofing such lines is more difficult. If you are - using colors to mark these lines, and rely on these, you may unset - this setting. (Crypto only) + The PGP command formats have their own set of printf-like sequences: - 66..33..114433.. ppggpp__uussee__ggppgg__aaggeenntt + %%pp Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty + string otherwise. Note: This may be used with a %? construct. - Type: boolean - Default: no + %%ff Expands to the name of a file containing a message. - If set, mutt will use a possibly-running gpg-agent process. (PGP - only) + %%ss Expands to the name of a file containing the signature part of a + multipart/signed attachment when verifying it. - 66..33..114444.. ccrryypptt__vveerriiffyy__ssiigg + %%aa The value of ``$pgp_sign_as''. - Type: quadoption - Default: yes + %%rr One or more key IDs. - If ``yes'', always attempt to verify PGP or S/MIME signatures. If - ``ask'', ask whether or not to verify the signature. If ``no'', never - attempt to verify cryptographic signatures. (Crypto only) + For examples on how to configure these formats for the various + versions of PGP which are floating around, see the pgp*.rc and gpg.rc + files in the samples/ subdirectory which has been installed on your + system alongside the documentation. (PGP only) - 66..33..114455.. ssmmiimmee__iiss__ddeeffaauulltt + 66..33..116622.. ppggpp__ddeeccrryypptt__ccoommmmaanndd - Type: boolean - Default: no + Type: string + Default: "" - The default behaviour of mutt is to use PGP on all auto- - sign/encryption operations. To override and to use OpenSSL instead - this must be set. However, this has no effect while replying, since - mutt will automatically select the same application that was used to - sign/encrypt the original message. (Note that this variable can be - overridden by unsetting ``$crypt_autosmime''.) (S/MIME only) + This command is used to decrypt a PGP encrypted message. (PGP only) - 66..33..114466.. ssmmiimmee__aasskk__cceerrtt__llaabbeell + 66..33..116633.. ppggpp__eennccrryypptt__oonnllyy__ccoommmmaanndd - Type: boolean - Default: yes + Type: string + Default: "" - This flag controls whether you want to be asked to enter a label for a - certificate about to be added to the database or not. It is set by - default. (S/MIME only) + This command is used to encrypt a body part without signing it. (PGP + only) - 66..33..114477.. ssmmiimmee__ddeeccrryypptt__uussee__ddeeffaauulltt__kkeeyy + 66..33..116644.. ppggpp__eennccrryypptt__ssiiggnn__ccoommmmaanndd - Type: boolean - Default: yes + Type: string + Default: "" - If set (default) this tells mutt to use the default key for - decryption. Otherwise, if manage multiple certificate-key-pairs, mutt - will try to use the mailbox-address to determine the key to use. It - will ask you to supply a key, if it can't find one. (S/MIME only) + This command is used to both sign and encrypt a body part. (PGP only) - 66..33..114488.. ppggpp__eennttrryy__ffoorrmmaatt + 66..33..116655.. ppggpp__eennttrryy__ffoorrmmaatt Type: string Default: "%4n %t%f %4l/0x%k %-4a %2c %u" @@ -5057,7 +5703,24 @@ (PGP only) - 66..33..114499.. ppggpp__ggoooodd__ssiiggnn + 66..33..116666.. ppggpp__eexxppoorrtt__ccoommmmaanndd + + Type: string + Default: "" + + This command is used to export a public key from the user's key ring. + (PGP only) + + 66..33..116677.. ppggpp__ggeettkkeeyyss__ccoommmmaanndd + + Type: string + Default: "" + + This command is invoked whenever mutt-ng will need public key + information. %r is the only printf-like sequence used with this + format. (PGP only) + + 66..33..116688.. ppggpp__ggoooodd__ssiiggnn Type: regular expression Default: "" @@ -5067,16 +5730,49 @@ contains the text. Use this variable if the exit code from the command is 0 even for bad signatures. (PGP only) - 66..33..115500.. ppggpp__cchheecckk__eexxiitt + 66..33..116699.. ppggpp__iiggnnoorree__ssuubbkkeeyyss Type: boolean Default: yes - If set, mutt will check the exit code of the PGP subprocess when - signing or encrypting. A non-zero exit code means that the subprocess - failed. (PGP only) + Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. + Instead, the principal key will inherit the subkeys' capabilities. + Unset this if you want to play interesting key selection games. (PGP + only) + + 66..33..117700.. ppggpp__iimmppoorrtt__ccoommmmaanndd + + Type: string + Default: "" + + This command is used to import a key from a message into the user's + public key ring. (PGP only) + + 66..33..117711.. ppggpp__lliisstt__ppuubbrriinngg__ccoommmmaanndd + + Type: string + Default: "" + + This command is used to list the public key ring's contents. The + output format must be analogous to the one used by gpg --list-keys + --with-colons. + + This format is also generated by the pgpring utility which comes with + mutt-ng. (PGP only) - 66..33..115511.. ppggpp__lloonngg__iiddss + 66..33..117722.. ppggpp__lliisstt__sseeccrriinngg__ccoommmmaanndd + + Type: string + Default: "" + + This command is used to list the secret key ring's contents. The + output format must be analogous to the one used by gpg --list-keys + --with-colons. + + This format is also generated by the pgpring utility which comes with + mutt-ng. (PGP only) + + 66..33..117733.. ppggpp__lloonngg__iiddss Type: boolean Default: no @@ -5084,7 +5780,39 @@ If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. (PGP only) - 66..33..115522.. ppggpp__rreettaaiinnaabbllee__ssiiggss + 66..33..117744.. ppggpp__mmiimmee__aauuttoo + + Type: quadoption + Default: ask-yes + + This option controls whether Mutt-ng will prompt you for automatically + sending a (signed/encrypted) message using PGP/MIME when inline + (traditional) fails (for any reason). + + Also note that using the old-style PGP message format is ssttrroonnggllyy + ddeepprreeccaatteedd. (PGP only) + + 66..33..117755.. ppggpp__rreeppllyyiinnlliinnee + + Type: boolean + Default: no + + Setting this variable will cause Mutt-ng to always attempt to create + an inline (traditional) message when replying to a message which is + PGP encrypted/signed inline. This can be overridden by use of the + _p_g_p_-_m_e_n_u, when inline is not required. This option does not + automatically detect if the (replied-to) message is inline; instead it + relies on Mutt-ng internals for previously checked/flagged messages. + + Note that Mutt-ng might automatically use PGP/MIME for messages which + consist of more than a single MIME part. Mutt-ng can be configured to + ask before sending PGP/MIME messages when inline (traditional) would + not work. See also: ````$pgp_mime_auto''''. + + Also note that using the old-style PGP message format is ssttrroonnggllyy + ddeepprreeccaatteedd. (PGP only) + + 66..33..117766.. ppggpp__rreettaaiinnaabbllee__ssiiggss Type: boolean Default: no @@ -5097,16 +5825,16 @@ removed, while the inner multipart/signed part is retained. (PGP only) - 66..33..115533.. ppggpp__sshhooww__uunnuussaabbllee + 66..33..117777.. ppggpp__sshhooww__uunnuussaabbllee Type: boolean Default: yes - If set, mutt will display non-usable keys on the PGP key selection + If set, mutt-ng will display non-usable keys on the PGP key selection menu. This includes keys which have been revoked, have expired, or have been marked as ``disabled'' by the user. (PGP only) - 66..33..115544.. ppggpp__ssiiggnn__aass + 66..33..117788.. ppggpp__ssiiggnn__aass Type: string Default: "" @@ -5115,24 +5843,15 @@ which of your private keys to use. It is recommended that you use the keyid form to specify your key (e.g., ``0x00112233''). (PGP only) - 66..33..115555.. ppggpp__ssttrriicctt__eenncc - - Type: boolean - Default: yes - - If set, Mutt will automatically encode PGP/MIME signed messages as - _q_u_o_t_e_d_-_p_r_i_n_t_a_b_l_e. Please note that unsetting this variable may lead - to problems with non-verifyable PGP signatures, so only change this if - you know what you are doing. (PGP only) + 66..33..117799.. ppggpp__ssiiggnn__ccoommmmaanndd - 66..33..115566.. ppggpp__ttiimmeeoouutt + Type: string + Default: "" - Type: number - Default: 300 + This command is used to create the detached PGP signature for a + multipart/signed PGP/MIME body part. (PGP only) - The number of seconds after which a cached passphrase will expire if - not used. (PGP only) - 66..33..115577.. ppggpp__ssoorrtt__kkeeyyss + 66..33..118800.. ppggpp__ssoorrtt__kkeeyyss Type: sort order Default: address @@ -5155,136 +5874,40 @@ If you prefer reverse order of the above values, prefix it with `reverse-'. (PGP only) - 66..33..115588.. ppggpp__ccrreeaattee__ttrraaddiittiioonnaall + 66..33..118811.. ppggpp__ssttrriicctt__eenncc - Type: quadoption - Default: no + Type: boolean + Default: yes + + If set, Mutt-ng will automatically encode PGP/MIME signed messages as + _q_u_o_t_e_d_-_p_r_i_n_t_a_b_l_e. Please note that unsetting this variable may lead + to problems with non-verifyable PGP signatures, so only change this if + you know what you are doing. (PGP only) - This option controls whether Mutt generates old-style inline PGP - encrypted or signed messages. + 66..33..118822.. ppggpp__ttiimmeeoouutt - Note that PGP/MIME will be used automatically for messages which have - a character set different from us-ascii, or which consist of more than - a single MIME part. + Type: number + Default: 300 - Also note that using the old-style PGP message format is ssttrroonnggllyy - ddeepprreeccaatteedd. (PGP only) + The number of seconds after which a cached passphrase will expire if + not used. (PGP only) - 66..33..115599.. ppggpp__aauuttoo__ttrraaddiittiioonnaall + 66..33..118833.. ppggpp__uussee__ggppgg__aaggeenntt Type: boolean Default: no - This option causes Mutt to generate an old-style inline PGP encrypted - or signed message when replying to an old-style message, and a - PGP/MIME message when replying to a PGP/MIME message. Note that this - option is only meaningful when using ````$crypt_replyencrypt'''', - ````$crypt_replysign'''', or ````$crypt_replysignencrypted''''. - - Also note that PGP/MIME will be used automatically for messages which - have a character set different from us-ascii, or which consist of more - than a single MIME part. - - This option overrides ````$pgp_create_traditional'''' (PGP only) + If set, mutt-ng will use a possibly-running gpg-agent process. (PGP + only) - 66..33..116600.. ppggpp__ddeeccooddee__ccoommmmaanndd + 66..33..118844.. ppggpp__vveerriiffyy__ccoommmmaanndd Type: string Default: "" - This format strings specifies a command which is used to decode - application/pgp attachments. + This command is used to verify PGP signatures. (PGP only) - The PGP command formats have their own set of printf-like sequences: - - %%pp Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty - string otherwise. Note: This may be used with a %? construct. - - %%ff Expands to the name of a file containing a message. - - %%ss Expands to the name of a file containing the signature part of a - multipart/signed attachment when verifying it. - - %%aa The value of ``$pgp_sign_as''. - - %%rr One or more key IDs. - - For examples on how to configure these formats for the various - versions of PGP which are floating around, see the pgp*.rc and gpg.rc - files in the samples/ subdirectory which has been installed on your - system alongside the documentation. (PGP only) - - 66..33..116611.. ppggpp__ggeettkkeeyyss__ccoommmmaanndd - - Type: string - Default: "" - - This command is invoked whenever mutt will need public key - information. %r is the only printf-like sequence used with this - format. (PGP only) - - 66..33..116622.. ppggpp__vveerriiffyy__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to verify PGP signatures. (PGP only) - - 66..33..116633.. ppggpp__ddeeccrryypptt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to decrypt a PGP encrypted message. (PGP only) - - 66..33..116644.. ppggpp__cclleeaarrssiiggnn__ccoommmmaanndd - - Type: string - Default: "" - - This format is used to create a old-style "clearsigned" PGP message. - Note that the use of this format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - - 66..33..116655.. ppggpp__ssiiggnn__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to create the detached PGP signature for a - multipart/signed PGP/MIME body part. (PGP only) - - 66..33..116666.. ppggpp__eennccrryypptt__ssiiggnn__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to both sign and encrypt a body part. (PGP only) - - 66..33..116677.. ppggpp__eennccrryypptt__oonnllyy__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to encrypt a body part without signing it. (PGP - only) - - 66..33..116688.. ppggpp__iimmppoorrtt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to import a key from a message into the user's - public key ring. (PGP only) - - 66..33..116699.. ppggpp__eexxppoorrtt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to export a public key from the user's key ring. - (PGP only) - - 66..33..117700.. ppggpp__vveerriiffyy__kkeeyy__ccoommmmaanndd + 66..33..118855.. ppggpp__vveerriiffyy__kkeeyy__ccoommmmaanndd Type: string Default: "" @@ -5292,334 +5915,63 @@ This command is used to verify key information from the key selection menu. (PGP only) - 66..33..117711.. ppggpp__lliisstt__sseeccrriinngg__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to list the secret key ring's contents. The - output format must be analogous to the one used by gpg --list-keys - --with-colons. - - This format is also generated by the pgpring utility which comes with - mutt. (PGP only) - - 66..33..117722.. ppggpp__lliisstt__ppuubbrriinngg__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to list the public key ring's contents. The - output format must be analogous to the one used by gpg --list-keys - --with-colons. - - This format is also generated by the pgpring utility which comes with - mutt. (PGP only) - - 66..33..117733.. ffoorrwwaarrdd__ddeeccrryypptt + 66..33..118866.. ppiippee__ddeeccooddee Type: boolean - Default: yes - - Controls the handling of encrypted messages when forwarding a message. - When set, the outer layer of encryption is stripped off. This - variable is only used if ````$mime_forward'''' is _s_e_t and - ````$mime_forward_decode'''' is _u_n_s_e_t. (PGP only) - - 66..33..117744.. ssmmiimmee__ttiimmeeoouutt - - Type: number - Default: 300 - - The number of seconds after which a cached passphrase will expire if - not used. (S/MIME only) - - 66..33..117755.. ssmmiimmee__eennccrryypptt__wwiitthh - - Type: string - Default: "" - - This sets the algorithm that should be used for encryption. Valid - choices are "des", "des3", "rc2-40", "rc2-64", "rc2-128". If unset - "3des" (TripleDES) is used. (S/MIME only) - - 66..33..117766.. ssmmiimmee__kkeeyyss - - Type: path - Default: "" - - Since there is no pubring/secring as with PGP, mutt has to handle - storage ad retrieval of keys/certs by itself. This is very basic right - now, and stores keys and certificates in two different directories, - both named as the hash-value retrieved from OpenSSL. There is an index - file which contains mailbox-address keyid pair, and which can be - manually edited. This one points to the location of the private keys. - (S/MIME only) - - 66..33..117777.. ssmmiimmee__ccaa__llooccaattiioonn - - Type: path - Default: "" - - This variable contains the name of either a directory, or a file which - contains trusted certificates for use with OpenSSL. (S/MIME only) - - 66..33..117788.. ssmmiimmee__cceerrttiiffiiccaatteess - - Type: path - Default: "" - - Since there is no pubring/secring as with PGP, mutt has to handle - storage and retrieval of keys by itself. This is very basic right now, - and keys and certificates are stored in two different directories, - both named as the hash-value retrieved from OpenSSL. There is an index - file which contains mailbox-address keyid pairs, and which can be - manually edited. This one points to the location of the certificates. - (S/MIME only) - - 66..33..117799.. ssmmiimmee__ddeeccrryypptt__ccoommmmaanndd - - Type: string - Default: "" - - This format string specifies a command which is used to decrypt - application/x-pkcs7-mime attachments. - - The OpenSSL command formats have their own set of printf-like - sequences similar to PGP's: - %%ff Expands to the name of a file containing a message. - - %%ss Expands to the name of a file containing the signature part of a - multipart/signed attachment when verifying it. - - %%kk The key-pair specified with ``$smime_default_key'' - - %%cc One or more certificate IDs. - - %%aa The algorithm used for encryption. - - %%CC CA location: Depending on whether ``$smime_ca_location'' points - to a directory or file, this expands to "-CApath - ``$smime_ca_location''" or "-CAfile ``$smime_ca_location''". - - For examples on how to configure these formats, see the smime.rc in - the samples/ subdirectory which has been installed on your system - alongside the documentation. (S/MIME only) - - 66..33..118800.. ssmmiimmee__vveerriiffyy__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to verify S/MIME signatures of type - multipart/signed. (S/MIME only) - - 66..33..118811.. ssmmiimmee__vveerriiffyy__ooppaaqquuee__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to verify S/MIME signatures of type - application/x-pkcs7-mime. (S/MIME only) - - 66..33..118822.. ssmmiimmee__ssiiggnn__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to created S/MIME signatures of type - multipart/signed, which can be read by all mail clients. (S/MIME - only) - - 66..33..118833.. ssmmiimmee__ssiiggnn__ooppaaqquuee__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to created S/MIME signatures of type - application/x-pkcs7-signature, which can only be handled by mail - clients supporting the S/MIME extension. (S/MIME only) - - 66..33..118844.. ssmmiimmee__eennccrryypptt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to create encrypted S/MIME messages. (S/MIME - only) - - 66..33..118855.. ssmmiimmee__ppkk77oouutt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to extract PKCS7 structures of S/MIME signatures, - in order to extract the public X509 certificate(s). (S/MIME only) - - 66..33..118866.. ssmmiimmee__ggeett__cceerrtt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to extract X509 certificates from a PKCS7 - structure. (S/MIME only) - - 66..33..118877.. ssmmiimmee__ggeett__ssiiggnneerr__cceerrtt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to extract only the signers X509 certificate from - a S/MIME signature, so that the certificate's owner may get compared - to the email's (S/MIME only) - - 66..33..118888.. ssmmiimmee__iimmppoorrtt__cceerrtt__ccoommmmaanndd - - Type: string - Default: "" - - This command is used to import a certificate via smime_keys. (S/MIME - only) - - 66..33..118899.. ssmmiimmee__ggeett__cceerrtt__eemmaaiill__ccoommmmaanndd - - Type: string - Default: "" + Default: no - This command is used to extract the mail address(es) used for storing - X509 certificates, and for verification purposes (to check whether the - certificate was issued for the sender's mailbox). (S/MIME only) + Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command. When unset, Mutt-ng + will pipe the messages without any preprocessing. When set, Mutt-ng + will weed headers and will attempt to PGP/MIME decode the messages + first. - 66..33..119900.. ssmmiimmee__ddeeffaauulltt__kkeeyy + 66..33..118877.. ppiippee__sseepp Type: string - Default: "" - - This is the default key-pair to use for signing. This must be set to - the keyid (the hash-value that OpenSSL generates) to work properly - (S/MIME only) - - 66..33..119911.. ssssll__ssttaarrttttllss - - Type: quadoption - Default: yes - - If set (the default), mutt will attempt to use STARTTLS on servers - advertising the capability. When unset, mutt will not attempt to use - STARTTLS regardless of the server's capabilities. - - 66..33..119922.. cceerrttiiffiiccaattee__ffiillee - - Type: path - Default: "" - - This variable specifies the file where the certificates you trust are - saved. When an unknown certificate is encountered, you are asked if - you accept it or not. If you accept it, the certificate can also be - saved in this file and further connections are automatically accepted. - - You can also manually add CA certificates in this file. Any server - certificate that is signed with one of these CA certificates are also - automatically accepted. - - Example: set certificate_file=~/.mutt/certificates - - 66..33..119933.. ssssll__uusseessyysstteemmcceerrttss - - Type: boolean - Default: yes - - If set to _y_e_s, mutt will use CA certificates in the system-wide - certificate store when checking if server certificate is signed by a - trusted CA. - - 66..33..119944.. eennttrrooppyy__ffiillee - - Type: path - Default: "" - - The file which includes random data that is used to initialize SSL - library functions. - - 66..33..119955.. ssssll__uussee__ssssllvv22 - - Type: boolean - Default: yes - - This variables specifies whether to attempt to use SSLv2 in the SSL - authentication process. - - 66..33..119966.. ssssll__uussee__ssssllvv33 - - Type: boolean - Default: yes - - This variables specifies whether to attempt to use SSLv3 in the SSL - authentication process. - - 66..33..119977.. ssssll__uussee__ttllssvv11 - - Type: boolean - Default: yes + Default: "\n" - This variables specifies whether to attempt to use TLSv1 in the SSL - authentication process. + The separator to add between messages when piping a list of tagged + messages to an external Unix command. - 66..33..119988.. ppiippee__sspplliitt + 66..33..118888.. ppiippee__sspplliitt Type: boolean Default: no Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command and the ``tag- prefix'' operator. If this variable is unset, when piping a list of - tagged messages Mutt will concatenate the messages and will pipe them - as a single folder. When set, Mutt will pipe the messages one by one. - In both cases the messages are piped in the current sorted order, and - the ````$pipe_sep'''' separator is added after each message. + tagged messages Mutt-ng will concatenate the messages and will pipe + them as a single folder. When set, Mutt-ng will pipe the messages one + by one. In both cases the messages are piped in the current sorted + order, and the ````$pipe_sep'''' separator is added after each + message. - 66..33..119999.. ppiippee__ddeeccooddee + 66..33..118899.. ppoopp__aauutthh__ttrryy__aallll Type: boolean - Default: no - - Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command. When unset, Mutt - will pipe the messages without any preprocessing. When set, Mutt will - weed headers and will attempt to PGP/MIME decode the messages first. - - 66..33..220000.. ppiippee__sseepp - - Type: string - Default: "\n" + Default: yes - The separator to add between messages when piping a list of tagged - messages to an external Unix command. + If set, Mutt-ng will try all available methods. When unset, Mutt-ng + will only fall back to other authentication methods if the previous + methods are unavailable. If a method is available but authentication + fails, Mutt-ng will not connect to the POP server. - 66..33..220011.. ppoopp__aauutthheennttiiccaattoorrss + 66..33..119900.. ppoopp__aauutthheennttiiccaattoorrss Type: string Default: "" - This is a colon-delimited list of authentication methods mutt may - attempt to use to log in to an POP server, in the order mutt should + This is a colon-delimited list of authentication methods mutt-ng may + attempt to use to log in to an POP server, in the order mutt-ng should try them. Authentication methods are either 'user', 'apop' or any SASL mechanism, eg 'digest-md5', 'gssapi' or 'cram-md5'. This parameter is case-insensitive. If this parameter is unset (the - default) mutt will try all available methods, in order from most- + default) mutt-ng will try all available methods, in order from most- secure to least-secure. Example: set pop_authenticators="digest-md5:apop:user" - 66..33..220022.. ppoopp__aauutthh__ttrryy__aallll - - Type: boolean - Default: yes - - If set, Mutt will try all available methods. When unset, Mutt will - only fall back to other authentication methods if the previous methods - are unavailable. If a method is available but authentication fails, - Mutt will not connect to the POP server. - - 66..33..220033.. ppoopp__cchheecckkiinntteerrvvaall + 66..33..119911.. ppoopp__cchheecckkiinntteerrvvaall Type: number Default: 60 @@ -5627,16 +5979,16 @@ This variable configures how often (in seconds) POP should look for new mail. - 66..33..220044.. ppoopp__ddeelleettee + 66..33..119922.. ppoopp__ddeelleettee Type: quadoption Default: ask-no - If set, Mutt will delete successfully downloaded messages from the POP - server when using the fetch-mail function. When unset, Mutt will - download messages but also leave them on the POP server. + If set, Mutt-ng will delete successfully downloaded messages from the + POP server when using the fetch-mail function. When unset, Mutt-ng + will download messages but also leave them on the POP server. - 66..33..220055.. ppoopp__hhoosstt + 66..33..119933.. ppoopp__hhoosstt Type: string Default: "" @@ -5646,24 +5998,35 @@ [pop[s]://][username[:password]@]popserver[:port] - 66..33..220066.. ppoopp__llaasstt + 66..33..119944.. ppoopp__llaasstt Type: boolean Default: no - If this variable is set, mutt will try to use the "LAST" POP command - for retrieving only unread messages from the POP server when using the - fetch-mail function. + If this variable is set, mutt-ng will try to use the "LAST" POP + command for retrieving only unread messages from the POP server when + using the fetch-mail function. + + 66..33..119955.. ppoopp__ppaassss + + Type: string + Default: "" + + Specifies the password for your POP account. If unset, Mutt-ng will + prompt you for your password when you open POP mailbox. WWaarrnniinngg: you + should only use this option when you are on a fairly secure machine, + because the superuser can read your muttngrc even if you are the only + one who can read the file. - 66..33..220077.. ppoopp__rreeccoonnnneecctt + 66..33..119966.. ppoopp__rreeccoonnnneecctt Type: quadoption Default: ask-yes - Controls whether or not Mutt will try to reconnect to POP server when - connection lost. + Controls whether or not Mutt-ng will try to reconnect to POP server + when connection lost. - 66..33..220088.. ppoopp__uusseerr + 66..33..119977.. ppoopp__uusseerr Type: string Default: "" @@ -5672,36 +6035,25 @@ This variable defaults to your user name on the local machine. - 66..33..220099.. ppoopp__ppaassss - - Type: string - Default: "" - - Specifies the password for your POP account. If unset, Mutt will - prompt you for your password when you open POP mailbox. WWaarrnniinngg: you - should only use this option when you are on a fairly secure machine, - because the superuser can read your muttrc even if you are the only - one who can read the file. - - 66..33..221100.. ppoosstt__iinnddeenntt__ssttrriinngg + 66..33..119988.. ppoosstt__iinnddeenntt__ssttrriinngg Type: string Default: "" - Similar to the ````$attribution'''' variable, Mutt will append this + Similar to the ````$attribution'''' variable, Mutt-ng will append this string after the inclusion of a message which is being replied to. - 66..33..221111.. ppoosstt__mmooddeerraatteedd + 66..33..119999.. ppoosstt__mmooddeerraatteedd Type: quadoption Default: ask-yes - If set to _y_e_s, Mutt will post article to newsgroup that have not + If set to _y_e_s, Mutt-ng will post article to newsgroup that have not permissions to posting (e.g. moderated). NNoottee:: if newsserver does not support posting to that newsgroup or totally read-only, that posting will not have an effect. - 66..33..221122.. ppoossttppoonnee + 66..33..220000.. ppoossttppoonnee Type: quadoption Default: ask-yes @@ -5709,25 +6061,25 @@ Controls whether or not messages are saved in the ````$postponed'''' mailbox when you elect not to send immediately. - 66..33..221133.. ppoossttppoonneedd + 66..33..220011.. ppoossttppoonneedd Type: path Default: "~/postponed" - Mutt allows you to indefinitely ````postpone'' sending a message'' - which you are editing. When you choose to postpone a message, Mutt + Mutt-ng allows you to indefinitely ````postpone'' sending a message'' + which you are editing. When you choose to postpone a message, Mutt-ng saves it in the mailbox specified by this variable. Also see the ````$postpone'''' variable. - 66..33..221144.. pprreeccoonnnneecctt + 66..33..220022.. pprreeccoonnnneecctt Type: string Default: "" - If set, a shell command to be executed if mutt fails to establish a + If set, a shell command to be executed if mutt-ng fails to establish a connection to the server. This is useful for setting up secure connections, e.g. with ssh(1). If the command returns a nonzero - status, mutt gives up opening the server. Example: + status, mutt-ng gives up opening the server. Example: preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 < /dev/null > /dev/null" @@ -5738,22 +6090,23 @@ NOTE: For this example to work, you must be able to log in to the remote machine without having to enter a password. - 66..33..221155.. pprriinntt + 66..33..220033.. pprriinntt Type: quadoption Default: ask-no - Controls whether or not Mutt asks for confirmation before printing. - This is useful for people (like me) who accidentally hit ``p'' often. + Controls whether or not Mutt-ng really prints messages. This is set + to _a_s_k_-_n_o by default, because some people accidentally hit ``p'' often + (like me). - 66..33..221166.. pprriinntt__ccoommmmaanndd + 66..33..220044.. pprriinntt__ccoommmmaanndd Type: path Default: "lpr" This specifies the command pipe that should be used to print messages. - 66..33..221177.. pprriinntt__ddeeccooddee + 66..33..220055.. pprriinntt__ddeeccooddee Type: boolean Default: yes @@ -5765,7 +6118,7 @@ latter setting may be useful if you are using some advanced printer filter which is able to properly format e-mail messages for printing. - 66..33..221188.. pprriinntt__sspplliitt + 66..33..220066.. pprriinntt__sspplliitt Type: boolean Default: no @@ -5780,37 +6133,54 @@ Those who use the eennssccrriipptt(1) program's mail-printing mode will most likely want to set this option. - 66..33..221199.. pprroommpptt__aafftteerr + 66..33..220077.. pprroommpptt__aafftteerr Type: boolean Default: yes If you use an _e_x_t_e_r_n_a_l ````$pager'''', setting this variable will - cause Mutt to prompt you for a command when the pager exits rather - than returning to the index menu. If unset, Mutt will return to the - index menu when the external pager exits. + cause Mutt-ng to prompt you for a command when the pager exits rather + than returning to the index menu. If unset, Mutt-ng will return to + the index menu when the external pager exits. - 66..33..222200.. qquueerryy__ccoommmmaanndd + 66..33..220088.. qquueerryy__ccoommmmaanndd Type: path Default: "" - This specifies the command that mutt will use to make external address - queries. The string should contain a %s, which will be substituted - with the query string the user types. See ````query'''' for more - information. + This specifies the command that mutt-ng will use to make external + address queries. The string should contain a %s, which will be + substituted with the query string the user types. See ````query'''' + for more information. - 66..33..222211.. qquuiitt + 66..33..220099.. qquuiitt Type: quadoption Default: yes This variable controls whether ``quit'' and ``exit'' actually quit - from mutt. If it set to yes, they do quit, if it is set to no, they - have no effect, and if it is set to ask-yes or ask-no, you are + from mutt-ng. If it set to yes, they do quit, if it is set to no, + they have no effect, and if it is set to ask-yes or ask-no, you are prompted for confirmation when you try to quit. - 66..33..222222.. qquuoottee__rreeggeexxpp + 66..33..221100.. qquuoottee__eemmppttyy + + Type: boolean + Default: yes + + Controls whether or not empty lines will be quoted using + ````indent_string''''. + + 66..33..221111.. qquuoottee__qquuootteedd + + Type: boolean + Default: no + + Controls how quoted lines will be quoted. If set, one quote character + will be added to the end of existing prefix. Otherwise, quoted lines + will be prepended by ````indent_string''''. + + 66..33..221122.. qquuoottee__rreeggeexxpp Type: regular expression Default: "^([ \t]*[|>:}#])+" @@ -5822,29 +6192,29 @@ need to set this to a regular expression that matches _e_x_a_c_t_l_y the quote characters at the beginning of quoted lines. - 66..33..222233.. rreeaadd__iinncc + 66..33..221133.. rreeaadd__iinncc Type: number Default: 10 - If set to a value greater than 0, Mutt will display which message it - is currently on when reading a mailbox. The message is printed after - _r_e_a_d___i_n_c messages have been read (e.g., if set to 25, Mutt will print - a message when it reads message 25, and then again when it gets to - message 50). This variable is meant to indicate progress when reading - large mailboxes which may take some time. When set to 0, only a - single message will appear before the reading the mailbox. + If set to a value greater than 0, Mutt-ng will display which message + it is currently on when reading a mailbox. The message is printed + after _r_e_a_d___i_n_c messages have been read (e.g., if set to 25, Mutt-ng + will print a message when it reads message 25, and then again when it + gets to message 50). This variable is meant to indicate progress when + reading large mailboxes which may take some time. When set to 0, only + a single message will appear before the reading the mailbox. Also see the ````$write_inc'''' variable. - 66..33..222244.. rreeaadd__oonnllyy + 66..33..221144.. rreeaadd__oonnllyy Type: boolean Default: no If set, all folders are opened in read-only mode. - 66..33..222255.. rreeaallnnaammee + 66..33..221155.. rreeaallnnaammee Type: string Default: "" @@ -5856,18 +6226,18 @@ variable will _n_o_t be used when the user has set a real name in the ``$from'' variable. - 66..33..222266.. rreeccaallll + 66..33..221166.. rreeccaallll Type: quadoption Default: ask-yes - Controls whether or not you are prompted to recall postponed messages - when composing a new message. Also see ````$postponed''''. + Controls whether or not Mutt-ng recalls postponed messages when + composing a new message. Also see ````$postponed''''. Setting this variable to ``yes'' is not generally useful, and thus not recommended. - 66..33..222277.. rreeccoorrdd + 66..33..221177.. rreeccoorrdd Type: path Default: "" @@ -5880,7 +6250,7 @@ The value of _`_`_$_r_e_c_o_r_d_'_' is overridden by the ````$force_name'''' and ````$save_name'''' variables, and the ````fcc-hook'''' command. - 66..33..222288.. rreeppllyy__rreeggeexxpp + 66..33..221188.. rreeppllyy__rreeggeexxpp Type: regular expression Default: "^(re([\[0-9\]+])*|aw):[ \t]*" @@ -5889,27 +6259,28 @@ and replying. The default value corresponds to the English "Re:" and the German "Aw:". - 66..33..222299.. rreeppllyy__sseellff + 66..33..221199.. rreeppllyy__sseellff Type: boolean Default: no - If unset and you are replying to a message sent by you, Mutt will + If unset and you are replying to a message sent by you, Mutt-ng will assume that you want to reply to the recipients of that message rather than to yourself. - 66..33..223300.. rreeppllyy__ttoo + + 66..33..222200.. rreeppllyy__ttoo Type: quadoption Default: ask-yes - If set, Mutt will ask you if you want to use the address listed in the - Reply-To: header field when replying to a message. If you answer no, - it will use the address in the From: header field instead. This - option is useful for reading a mailing list that sets the Reply-To: - header field to the list address and you want to send a private + If set, when replying to a message, Mutt-ng will use the address + listed in the Reply-to: header as the recipient of the reply. If + unset, it will use the address in the From: header field instead. + This option is useful for reading a mailing list that sets the Reply- + To: header field to the list address and you want to send a private message to the author of a message. - 66..33..223311.. rreessoollvvee + 66..33..222211.. rreessoollvvee Type: boolean Default: yes @@ -5918,15 +6289,15 @@ (possibly undeleted) message whenever a command that modifies the current message is executed. - 66..33..223322.. rreevveerrssee__aalliiaass + 66..33..222222.. rreevveerrssee__aalliiaass Type: boolean Default: no - This variable controls whether or not Mutt will display the "personal" - name from your aliases in the index menu if it finds an alias that - matches the message's sender. For example, if you have the following - alias: + This variable controls whether or not Mutt-ng will display the + "personal" name from your aliases in the index menu if it finds an + alias that matches the message's sender. For example, if you have the + following alias: alias juser abd30425@somewhere.net (Joe User) @@ -5938,35 +6309,38 @@ ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is not human friendly (like CompuServe addresses). - 66..33..223333.. rreevveerrssee__nnaammee + 66..33..222233.. rreevveerrssee__nnaammee Type: boolean Default: no + It may sometimes arrive that you receive mail to a certain machine, move the messages to another machine, and reply to some the messages from there. If this variable is set, the default _F_r_o_m_: line of the reply messages is built using the address where you received the - messages you are replying to. If the variable is unset, the _F_r_o_m_: - line will use your address on the current machine. + messages you are replying to iiff that address matches your alternates. + If the variable is unset, or the address that would be used doesn't + match your alternates, the _F_r_o_m_: line will use your address on the + current machine. - 66..33..223344.. rreevveerrssee__rreeaallnnaammee + 66..33..222244.. rreevveerrssee__rreeaallnnaammee Type: boolean Default: yes This variable fine-tunes the behaviour of the ``reverse_name'' - feature. When it is set, mutt will use the address from incoming + feature. When it is set, mutt-ng will use the address from incoming messages as-is, possibly including eventual real names. When it is - unset, mutt will override any such real names with the setting of the - ``realname'' variable. + unset, mutt-ng will override any such real names with the setting of + the ``realname'' variable. - 66..33..223355.. rrffcc22004477__ppaarraammeetteerrss + 66..33..222255.. rrffcc22004477__ppaarraammeetteerrss Type: boolean Default: no - When this variable is set, Mutt will decode RFC-2047-encoded MIME - parameters. You want to set this variable when mutt suggests you to + When this variable is set, Mutt-ng will decode RFC-2047-encoded MIME + parameters. You want to set this variable when mutt-ng suggests you to save attachments to files named like this: =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?= @@ -5975,21 +6349,21 @@ Note that this use of RFC 2047's encoding is explicitly, prohibited by the standard, but nevertheless encountered in the wild. Also note - that setting this parameter will _n_o_t have the effect that mutt - _g_e_n_e_r_a_t_e_s this kind of encoding. Instead, mutt will unconditionally - use the encoding specified in RFC 2231. + that setting this parameter will _n_o_t have the effect that mutt-ng + _g_e_n_e_r_a_t_e_s this kind of encoding. Instead, mutt-ng will + unconditionally use the encoding specified in RFC 2231. - 66..33..223366.. ssaavvee__aaddddrreessss + 66..33..222266.. ssaavvee__aaddddrreessss Type: boolean Default: no - If set, mutt will take the sender's full address when choosing a + If set, mutt-ng will take the sender's full address when choosing a default folder for saving a mail. If ````$save_name'''' or ````$force_name'''' is set too, the selection of the fcc folder will be changed as well. - 66..33..223377.. ssaavvee__eemmppttyy + 66..33..222277.. ssaavvee__eemmppttyy Type: boolean Default: yes @@ -5998,10 +6372,10 @@ when closed (the exception is ````$spoolfile'''' which is never removed). If set, mailboxes are never removed. - NNoottee:: This only applies to mbox and MMDF folders, Mutt does not delete - MH and Maildir directories. + NNoottee:: This only applies to mbox and MMDF folders, Mutt-ng does not + delete MH and Maildir directories. - 66..33..223388.. ssaavvee__nnaammee + 66..33..222288.. ssaavvee__nnaammee Type: boolean Default: no @@ -6016,7 +6390,15 @@ Also see the ````$force_name'''' variable. - 66..33..223399.. ssccoorree + 66..33..222299.. ssaavvee__uunnssuubbssccrriibbeedd + + Type: boolean + Default: no + + When _s_e_t, info about unsubscribed newsgroups will be saved into + ``newsrc'' file and into cache. + + 66..33..223300.. ssccoorree Type: boolean Default: yes @@ -6025,187 +6407,468 @@ useful to selectively disable scoring for certain folders when the ````$score_threshold_delete'''' variable and friends are used. - 66..33..224400.. ssccoorree__tthhrreesshhoolldd__ddeelleettee + 66..33..223311.. ssccoorree__tthhrreesshhoolldd__ddeelleettee Type: number Default: -1 Messages which have been assigned a score equal to or lower than the - value of this variable are automatically marked for deletion by mutt. - Since mutt scores are always greater than or equal to zero, the - default setting of this variable will never mark a message for + value of this variable are automatically marked for deletion by mutt- + ng. Since mutt-ng scores are always greater than or equal to zero, + the default setting of this variable will never mark a message for deletion. - 66..33..224411.. ssccoorree__tthhrreesshhoolldd__ffllaagg + 66..33..223322.. ssccoorree__tthhrreesshhoolldd__ffllaagg Type: number Default: 9999 - Messages which have been assigned a score greater than or equal to - this variable's value are automatically marked "flagged". + Messages which have been assigned a score greater than or equal to + this variable's value are automatically marked "flagged". + + 66..33..223333.. ssccoorree__tthhrreesshhoolldd__rreeaadd + + Type: number + Default: -1 + + Messages which have been assigned a score equal to or lower than the + value of this variable are automatically marked as read by mutt-ng. + Since mutt-ng scores are always greater than or equal to zero, the + default setting of this variable will never mark a message read. + + 66..33..223344.. sseenndd__cchhaarrsseett + + Type: string + Default: "us-ascii:iso-8859-1:utf-8" + + A list of character sets for outgoing messages. Mutt-ng will use the + first character set into which the text can be converted exactly. If + your ````$charset'''' is not iso-8859-1 and recipients may not + understand UTF-8, it is advisable to include in the list an + appropriate widely used standard character set (such as iso-8859-2, + koi8-r or iso-2022-jp) either instead of or after "iso-8859-1". + + 66..33..223355.. sseennddmmaaiill + + Type: path + Default: "/usr/sbin/sendmail -oem -oi" + + Specifies the program and arguments used to deliver mail sent by Mutt- + ng. Mutt-ng expects that the specified program interprets additional + arguments as recipient addresses. + + 66..33..223366.. sseennddmmaaiill__wwaaiitt + + Type: number + Default: 0 + + Specifies the number of seconds to wait for the ````$sendmail'''' + process to finish before giving up and putting delivery in the + background. + + Mutt-ng interprets the value of this variable as follows: + + >>00 number of seconds to wait for sendmail to finish before + continuing + + 00 wait forever for sendmail to finish + + <<00 always put sendmail in the background without waiting + + Note that if you specify a value other than 0, the output of the child + process will be put in a temporary file. If there is some error, you + will be informed as to where to find the output. + + 66..33..223377.. sshheellll + + Type: path + Default: "" + + Command to use when spawning a subshell. By default, the user's login + shell from /etc/passwd is used. + + 66..33..223388.. sshhoorrtteenn__hhiieerraarrcchhyy + + Type: boolean + Default: no + + When _s_e_t, the "hierarchy" of the sidebar entries will be shortened + only if they cannot be printed in full length (because + ````$sidebar_width'''' is set to a too low value). For example, if the + newsgroup name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, + it'll get shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would + and thus will not get shortened. + + 66..33..223399.. sshhooww__nneeww__nneewwss + + Type: boolean + Default: yes + + If _s_e_t, newsserver will be asked for new newsgroups on entering the + browser. Otherwise, it will be done only once for a newsserver. Also + controls whether or not number of new articles of subscribed + newsgroups will be then checked. + + 66..33..224400.. sshhooww__oonnllyy__uunnrreeaadd + + Type: boolean + Default: no + + If _s_e_t, only subscribed newsgroups that contain unread articles will + be displayed in browser. + + 66..33..224411.. ssiiddeebbaarr__ddeelliimm + + Type: string + Default: "|" + + This specifies the delimiter between the sidebar (if visible) and + other screens. + + 66..33..224422.. ssiiddeebbaarr__vviissiibbllee + + Type: boolean + Default: no + + This specifies whether or not to show the mailbox list pane. + + 66..33..224433.. ssiiddeebbaarr__wwiiddtthh + + Type: number + Default: 0 + + The width of the mailbox list pane (left sidebar like in GUIs). + + 66..33..224444.. ssiigg__ddaasshheess + + Type: boolean + Default: yes + + If set, a line containing ``-- '' will be inserted before your + ````$signature''''. It is ssttrroonnggllyy recommended that you not unset + this variable unless your ``signature'' contains just your name. The + reason for this is because many software packages use ``-- \n'' to + detect your signature. For example, Mutt-ng has the ability to + highlight the signature in a different color in the builtin pager. + + 66..33..224455.. ssiigg__oonn__ttoopp + + Type: boolean + Default: no + + If set, the signature will be included before any quoted or forwarded + text. It is ssttrroonnggllyy recommended that you do not set this variable + unless you really know what you are doing, and are prepared to take + some heat from netiquette guardians. + + 66..33..224466.. ssiiggnnaattuurree + + Type: path + Default: "~/.signature" + + Specifies the filename of your signature, which is appended to all + outgoing messages. If the filename ends with a pipe (``|''), it is + assumed that filename is a shell command and input should be read from + its stdout. + + 66..33..224477.. ssiiggnnooffff__ssttrriinngg + + Type: string + Default: "" + + If set, this string will be inserted before the signature. This is + useful for people that want to sign off every message they send with + their name. + + If you want to insert your website's URL, additional contact + information or witty quotes into your mails, better use a signature + file instead of the signoff string. + + 66..33..224488.. ssiimmppllee__sseeaarrcchh + + Type: string + Default: "~f %s | ~s %s" + + Specifies how Mutt-ng should expand a simple search into a real search + pattern. A simple search is one that does not contain any of the ~ + operators. See ````patterns'''' for more information on search + patterns. + + For example, if you simply type joe at a search or limit prompt, Mutt- + ng will automatically expand it to the value specified by this + variable. For the default value it would be: + + ~f joe | ~s joe + + 66..33..224499.. sslleeeepp__ttiimmee + + Type: number + Default: 1 + + Specifies time, in seconds, to pause while displaying certain + informational messages, while moving from folder to folder and after + expunging messages from the current folder. The default is to pause + one second, so a value of zero for this option suppresses the pause. + + 66..33..225500.. ssmmaarrtt__wwrraapp + + Type: boolean + Default: yes + + Controls the display of lines longer than the screen width in the + internal pager. If set, long lines are wrapped at a word boundary. If + unset, lines are simply wrapped at the screen edge. Also see the + ````$markers'''' variable. + + 66..33..225511.. ssmmiilleeyyss + + Type: regular expression + Default: "(>From )|(:[-^]?[][)(><}{|/DP])" + + The _p_a_g_e_r uses this variable to catch some common false positives of + ````$quote_regexp'''', most notably smileys in the beginning of a line + + 66..33..225522.. ssmmiimmee__aasskk__cceerrtt__llaabbeell + + Type: boolean + Default: yes + + This flag controls whether you want to be asked to enter a label for a + certificate about to be added to the database or not. It is set by + default. (S/MIME only) + + 66..33..225533.. ssmmiimmee__ccaa__llooccaattiioonn + + Type: path + Default: "" + This variable contains the name of either a directory, or a file which + contains trusted certificates for use with OpenSSL. (S/MIME only) + + 66..33..225544.. ssmmiimmee__cceerrttiiffiiccaatteess + + Type: path + Default: "" + + Since there is no pubring/secring as with PGP, mutt-ng has to handle + storage and retrieval of keys by itself. This is very basic right now, + and keys and certificates are stored in two different directories, + both named as the hash-value retrieved from OpenSSL. There is an index + file which contains mailbox-address keyid pairs, and which can be + manually edited. This one points to the location of the certificates. + (S/MIME only) + + 66..33..225555.. ssmmiimmee__ddeeccrryypptt__ccoommmmaanndd + + Type: string + Default: "" + + This format string specifies a command which is used to decrypt + application/x-pkcs7-mime attachments. + + The OpenSSL command formats have their own set of printf-like + sequences similar to PGP's: + + %%ff Expands to the name of a file containing a message. + + %%ss Expands to the name of a file containing the signature part of a + multipart/signed attachment when verifying it. + + %%kk The key-pair specified with ``$smime_default_key'' + + %%cc One or more certificate IDs. + + %%aa The algorithm used for encryption. + + %%CC CA location: Depending on whether ``$smime_ca_location'' points + to a directory or file, this expands to "-CApath + ``$smime_ca_location''" or "-CAfile ``$smime_ca_location''". + + For examples on how to configure these formats, see the smime.rc in + the samples/ subdirectory which has been installed on your system + alongside the documentation. (S/MIME only) + + 66..33..225566.. ssmmiimmee__ddeeccrryypptt__uussee__ddeeffaauulltt__kkeeyy + + Type: boolean + Default: yes + + If set (default) this tells mutt-ng to use the default key for + decryption. Otherwise, if manage multiple certificate-key-pairs, mutt- + ng will try to use the mailbox-address to determine the key to use. It + will ask you to supply a key, if it can't find one. (S/MIME only) + + 66..33..225577.. ssmmiimmee__ddeeffaauulltt__kkeeyy - 66..33..224422.. ssccoorree__tthhrreesshhoolldd__rreeaadd + Type: string + Default: "" - Type: number - Default: -1 - Messages which have been assigned a score equal to or lower than the - value of this variable are automatically marked as read by mutt. - Since mutt scores are always greater than or equal to zero, the - default setting of this variable will never mark a message read. + This is the default key-pair to use for signing. This must be set to + the keyid (the hash-value that OpenSSL generates) to work properly + (S/MIME only) - 66..33..224433.. sseenndd__cchhaarrsseett + 66..33..225588.. ssmmiimmee__eennccrryypptt__ccoommmmaanndd Type: string - Default: "us-ascii:iso-8859-1:utf-8" + Default: "" - A list of character sets for outgoing messages. Mutt will use the - first character set into which the text can be converted exactly. If - your ````$charset'''' is not iso-8859-1 and recipients may not - understand UTF-8, it is advisable to include in the list an - appropriate widely used standard character set (such as iso-8859-2, - koi8-r or iso-2022-jp) either instead of or after "iso-8859-1". + This command is used to create encrypted S/MIME messages. (S/MIME + only) - 66..33..224444.. sseennddmmaaiill + 66..33..225599.. ssmmiimmee__eennccrryypptt__wwiitthh - Type: path - Default: "/usr/sbin/sendmail -oem -oi" + Type: string + Default: "" - Specifies the program and arguments used to deliver mail sent by Mutt. - Mutt expects that the specified program interprets additional - arguments as recipient addresses. + This sets the algorithm that should be used for encryption. Valid + choices are "des", "des3", "rc2-40", "rc2-64", "rc2-128". If unset + "3des" (TripleDES) is used. (S/MIME only) - 66..33..224455.. sseennddmmaaiill__wwaaiitt + 66..33..226600.. ssmmiimmee__ggeett__cceerrtt__ccoommmmaanndd - Type: number - Default: 0 + Type: string + Default: "" - Specifies the number of seconds to wait for the ````$sendmail'''' - process to finish before giving up and putting delivery in the - background. + This command is used to extract X509 certificates from a PKCS7 + structure. (S/MIME only) - Mutt interprets the value of this variable as follows: + 66..33..226611.. ssmmiimmee__ggeett__cceerrtt__eemmaaiill__ccoommmmaanndd - >>00 number of seconds to wait for sendmail to finish before - continuing + Type: string + Default: "" - 00 wait forever for sendmail to finish + This command is used to extract the mail address(es) used for storing + X509 certificates, and for verification purposes (to check whether the + certificate was issued for the sender's mailbox). (S/MIME only) - <<00 always put sendmail in the background without waiting + 66..33..226622.. ssmmiimmee__ggeett__ssiiggnneerr__cceerrtt__ccoommmmaanndd - Note that if you specify a value other than 0, the output of the child - process will be put in a temporary file. If there is some error, you - will be informed as to where to find the output. + Type: string + Default: "" - 66..33..224466.. sshheellll + This command is used to extract only the signers X509 certificate from + a S/MIME signature, so that the certificate's owner may get compared + to the email's 'From'-field. (S/MIME only) - Type: path + 66..33..226633.. ssmmiimmee__iimmppoorrtt__cceerrtt__ccoommmmaanndd + + Type: string Default: "" - Command to use when spawning a subshell. By default, the user's login - shell from /etc/passwd is used. + This command is used to import a certificate via smime_keys. (S/MIME + only) - 66..33..224477.. ssaavvee__uunnssuubbssccrriibbeedd + 66..33..226644.. ssmmiimmee__iiss__ddeeffaauulltt Type: boolean Default: no - When _s_e_t, info about unsubscribed newsgroups will be saved into - ``newsrc'' file and into cache. + The default behaviour of mutt-ng is to use PGP on all auto- + sign/encryption operations. To override and to use OpenSSL instead + this must be set. However, this has no effect while replying, since + mutt-ng will automatically select the same application that was used + to sign/encrypt the original message. (Note that this variable can be + overridden by unsetting ``$crypt_autosmime''.) (S/MIME only) - 66..33..224488.. sshhooww__nneeww__nneewwss + 66..33..226655.. ssmmiimmee__kkeeyyss - Type: boolean - Default: yes + Type: path + Default: "" - If _s_e_t, newsserver will be asked for new newsgroups on entering the - browser. Otherwise, it will be done only once for a newsserver. Also - controls whether or not number of new articles of subscribed - newsgroups will be then checked. + Since there is no pubring/secring as with PGP, mutt-ng has to handle + storage ad retrieval of keys/certs by itself. This is very basic right + now, and stores keys and certificates in two different directories, + both named as the hash-value retrieved from OpenSSL. There is an index + file which contains mailbox-address keyid pair, and which can be + manually edited. This one points to the location of the private keys. + (S/MIME only) - 66..33..224499.. sshhooww__oonnllyy__uunnrreeaadd + 66..33..226666.. ssmmiimmee__ppkk77oouutt__ccoommmmaanndd - Type: boolean - Default: no + Type: string + Default: "" - If _s_e_t, only subscribed newsgroups that contain unread articles will - be displayed in browser. + This command is used to extract PKCS7 structures of S/MIME signatures, + in order to extract the public X509 certificate(s). (S/MIME only) - 66..33..225500.. ssiigg__ddaasshheess + 66..33..226677.. ssmmiimmee__ssiiggnn__ccoommmmaanndd - Type: boolean - Default: yes + Type: string + Default: "" - If set, a line containing ``-- '' will be inserted before your - ````$signature''''. It is ssttrroonnggllyy recommended that you not unset - this variable unless your ``signature'' contains just your name. The - reason for this is because many software packages use ``-- \n'' to - detect your signature. For example, Mutt has the ability to highlight - the signature in a different color in the builtin pager. + This command is used to created S/MIME signatures of type + multipart/signed, which can be read by all mail clients. (S/MIME + only) - 66..33..225511.. ssiigg__oonn__ttoopp + 66..33..226688.. ssmmiimmee__ssiiggnn__ooppaaqquuee__ccoommmmaanndd - Type: boolean - Default: no + Type: string + Default: "" - If set, the signature will be included before any quoted or forwarded - text. It is ssttrroonnggllyy recommended that you do not set this variable - unless you really know what you are doing, and are prepared to take - some heat from netiquette guardians. + This command is used to created S/MIME signatures of type + application/x-pkcs7-signature, which can only be handled by mail + clients supporting the S/MIME extension. (S/MIME only) - 66..33..225522.. ssiiggnnaattuurree + 66..33..226699.. ssmmiimmee__ttiimmeeoouutt - Type: path - Default: "~/.signature" + Type: number + Default: 300 - Specifies the filename of your signature, which is appended to all - outgoing messages. If the filename ends with a pipe (``|''), it is - assumed that filename is a shell command and input should be read from - its stdout. + The number of seconds after which a cached passphrase will expire if + not used. (S/MIME only) - 66..33..225533.. ssiimmppllee__sseeaarrcchh + 66..33..227700.. ssmmiimmee__vveerriiffyy__ccoommmmaanndd Type: string - Default: "~f %s | ~s %s" + Default: "" - Specifies how Mutt should expand a simple search into a real search - pattern. A simple search is one that does not contain any of the ~ - operators. See ````patterns'''' for more information on search - patterns. + This command is used to verify S/MIME signatures of type + multipart/signed. (S/MIME only) - For example, if you simply type joe at a search or limit prompt, Mutt - will automatically expand it to the value specified by this variable. - For the default value it would be: + 66..33..227711.. ssmmiimmee__vveerriiffyy__ooppaaqquuee__ccoommmmaanndd - ~f joe | ~s joe + Type: string + Default: "" + This command is used to verify S/MIME signatures of type + application/x-pkcs7-mime. (S/MIME only) - 66..33..225544.. ssmmaarrtt__wwrraapp + 66..33..227722.. ssmmttpp__aauutthh__ppaasssswwoorrdd - Type: boolean - Default: yes + Type: string + Default: "" - Controls the display of lines longer than the screen width in the - internal pager. If set, long lines are wrapped at a word boundary. If - unset, lines are simply wrapped at the screen edge. Also see the - ````$markers'''' variable. + Defines the password to use with SMTP AUTH. If + ````$smtp_auth_username'''' is set, but this variable is not, you will + be prompted for a password when sending. - 66..33..225555.. ssmmiilleeyyss + 66..33..227733.. ssmmttpp__aauutthh__uusseerrnnaammee - Type: regular expression - Default: "(>From )|(:[-^]?[][)(><}{|/DP])" + Type: string + Default: "" - The _p_a_g_e_r uses this variable to catch some common false positives of - ````$quote_regexp'''', most notably smileys in the beginning of a line + Defines the username to use with SMTP AUTH. Setting this variable + will cause mutt-ng to attempt to use SMTP AUTH when sending. + + 66..33..227744.. ssmmttpp__hhoosstt + + Type: string + Default: "" - 66..33..225566.. sslleeeepp__ttiimmee + Defines the SMTP host which will be used to deliver mail, as opposed + to invoking the sendmail binary. Setting this variable overrides the + value of ````$sendmail'''', and any associated variables. + + 66..33..227755.. ssmmttpp__ppoorrtt Type: number - Default: 1 + Default: 25 - Specifies time, in seconds, to pause while displaying certain - informational messages, while moving from folder to folder and after - expunging messages from the current folder. The default is to pause - one second, so a value of zero for this option suppresses the pause. - 66..33..225577.. ssoorrtt + Defines the port that the SMTP host is listening on for mail delivery. + Must be specified as a number. + + Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP + servers will probably desire 587, the mail submission port. + + 66..33..227766.. ssoorrtt Type: sort order Default: date @@ -6218,6 +6881,7 @@ mailbox-order (unsorted) score size + spam subject threads to @@ -6225,7 +6889,7 @@ You may optionally use the reverse- prefix to specify reverse sorting order (example: set sort=reverse-date-sent). - 66..33..225588.. ssoorrtt__aalliiaass + 66..33..227777.. ssoorrtt__aalliiaass Type: sort order Default: alias @@ -6237,7 +6901,7 @@ alias (sort alphabetically by alias name) unsorted (leave in order specified in .muttrc) - 66..33..225599.. ssoorrtt__aauuxx + 66..33..227788.. ssoorrtt__aauuxx Type: sort order Default: date @@ -6245,21 +6909,21 @@ When sorting by threads, this variable controls how threads are sorted in relation to other threads, and how the branches of the thread trees are sorted. This can be set to any value that ````$sort'''' can, - except threads (in that case, mutt will just use date-sent). You can - also specify the last- prefix in addition to the reverse- prefix, but - last- must come after reverse-. The last- prefix causes messages to - be sorted against its siblings by which has the last descendant, using - the rest of sort_aux as an ordering. For instance, set sort_aux=last- - date-received would mean that if a new message is received in a - thread, that thread becomes the last one displayed (or the first, if - you have set sort=reverse-threads.) Note: For reversed ````$sort'''' - order ``$sort_aux'' is reversed again (which is not the right thing to - do, but kept to not break any existing configuration setting). - - 66..33..226600.. ssoorrtt__bbrroowwsseerr + except threads (in that case, mutt-ng will just use date-sent). You + can also specify the last- prefix in addition to the reverse- prefix, + but last- must come after reverse-. The last- prefix causes messages + to be sorted against its siblings by which has the last descendant, + using the rest of sort_aux as an ordering. For instance, set + sort_aux=last- date-received would mean that if a new message is + received in a thread, that thread becomes the last one displayed (or + the first, if you have set sort=reverse-threads.) Note: For reversed + ````$sort'''' order ``$sort_aux'' is reversed again (which is not the + right thing to do, but kept to not break any existing configuration + setting). + 66..33..227799.. ssoorrtt__bbrroowwsseerr Type: sort order - Default: subject + Default: alpha Specifies how to sort entries in the file browser. By default, the entries are sorted alphabetically. Valid values: @@ -6272,31 +6936,95 @@ You may optionally use the reverse- prefix to specify reverse sorting order (example: set sort_browser=reverse-date). - 66..33..226611.. ssoorrtt__rree + 66..33..228800.. ssoorrtt__rree Type: boolean Default: yes This variable is only useful when sorting by threads with ````$strict_threads'''' unset. In that case, it changes the heuristic - mutt uses to thread messages by subject. With sort_re set, mutt will - only attach a message as the child of another message by subject if - the subject of the child message starts with a substring matching the - setting of ````$reply_regexp''''. With sort_re unset, mutt will - attach the message whether or not this is the case, as long as the - non-````$reply_regexp'''' parts of both messages are identical. + mutt-ng uses to thread messages by subject. With sort_re set, mutt-ng + will only attach a message as the child of another message by subject + if the subject of the child message starts with a substring matching + the setting of ````$reply_regexp''''. With sort_re unset, mutt-ng + will attach the message whether or not this is the case, as long as + the non-````$reply_regexp'''' parts of both messages are identical. + + 66..33..228811.. ssppaamm__sseeppaarraattoorr + + Type: string + Default: "," + + ````spam_separator'''' controls what happens when multiple spam + headers are matched: if unset, each successive header will overwrite + any previous matches value for the spam label. If set, each successive + match will append to the previous, using ````spam_separator'''' as a + separator. - 66..33..226622.. ssppoooollffiillee + 66..33..228822.. ssppoooollffiillee Type: path Default: "" - If your spool mailbox is in a non-default place where Mutt cannot find - it, you can specify its location with this variable. Mutt will - automatically set this variable to the value of the environment + If your spool mailbox is in a non-default place where Mutt-ng cannot + find it, you can specify its location with this variable. Mutt-ng + will automatically set this variable to the value of the environment variable $MAIL if it is not set. - 66..33..226633.. ssttaattuuss__cchhaarrss + 66..33..228833.. ssssll__ccaa__cceerrttiiffiiccaatteess__ffiillee + + Type: path + Default: "" + + This variable specifies a file containing trusted CA certificates. + Any server certificate that is signed with one of these CA + certificates are also automatically accepted. + + Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca- + certificates.crt + + 66..33..228844.. ssssll__cclliieenntt__cceerrtt + + Type: path + Default: "" + + The file containing a client certificate and its associated private + key. + + 66..33..228855.. ssssll__mmiinn__ddhh__pprriimmee__bbiittss + + Type: number + Default: 0 + + This variable specifies the minimum acceptable prime size (in bits) + for use in any Diffie-Hellman key exchange. A value of 0 will use the + default from the GNUTLS library. + + 66..33..228866.. ssssll__ssttaarrttttllss + + Type: quadoption + Default: yes + + If set (the default), mutt-ng will attempt to use STARTTLS on servers + advertising the capability. When unset, mutt-ng will not attempt to + use STARTTLS regardless of the server's capabilities. + + 66..33..228877.. ssssll__uussee__ssssllvv33 + + Type: boolean + Default: yes + This variables specifies whether to attempt to use SSLv3 in the SSL + authentication process. + + 66..33..228888.. ssssll__uussee__ttllssvv11 + + Type: boolean + Default: yes + + This variables specifies whether to attempt to use TLSv1 in the SSL + authentication process. + + 66..33..228899.. ssttaattuuss__cchhaarrss Type: string Default: "-*%A" @@ -6312,10 +7040,10 @@ message mode (Certain operations like composing a new mail, replying, forwarding, etc. are not permitted in this mode). - 66..33..226644.. ssttaattuuss__ffoorrmmaatt + 66..33..229900.. ssttaattuuss__ffoorrmmaatt Type: string - Default: "-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? + Default: "-%r-Mutt-ng: %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)---" @@ -6325,6 +7053,8 @@ %%bb number of mailboxes with new mail * + %%BB the short pathname of the current mailbox + %%dd number of deleted messages * %%ff the full pathname of the current mailbox @@ -6345,7 +7075,7 @@ %%nn number of new messages in the mailbox * - %%oo number of old unread messages + %%oo number of old unread messages * %%pp number of postponed messages * @@ -6362,7 +7092,7 @@ %%uu number of unread messages * - %%vv Mutt version string + %%vv Mutt-ng version string %%VV currently active limit pattern, if any * @@ -6383,9 +7113,9 @@ %??? where _s_e_q_u_e_n_c_e___c_h_a_r is a character from the table above, and - _o_p_t_i_o_n_a_l___s_t_r_i_n_g is the string you would like printed if _s_t_a_t_u_s___c_h_a_r is - nonzero. _o_p_t_i_o_n_a_l___s_t_r_i_n_g mmaayy contain other sequence as well as normal - text, but you may nnoott nest optional strings. + _o_p_t_i_o_n_a_l___s_t_r_i_n_g is the string you would like printed if _s_e_q_u_e_n_c_e___c_h_a_r + is nonzero. _o_p_t_i_o_n_a_l___s_t_r_i_n_g mmaayy contain other sequences as well as + normal text, but you may nnoott nest optional strings. Here is an example illustrating how to optionally print the number of new messages in a mailbox: %?n?%n new messages.? @@ -6399,11 +7129,11 @@ (_) sign. For example, if you want to display the local hostname in lowercase, you would use: %_h - If you prefix the sequence character with a colon (:) character, mutt - will replace any dots in the expansion by underscores. This might be - helpful with IMAP folders that don't like dots in folder names. + If you prefix the sequence character with a colon (:) character, mutt- + ng will replace any dots in the expansion by underscores. This might + be helpful with IMAP folders that don't like dots in folder names. - 66..33..226655.. ssttaattuuss__oonn__ttoopp + 66..33..229911.. ssttaattuuss__oonn__ttoopp Type: boolean Default: no @@ -6411,7 +7141,21 @@ Setting this variable causes the ``status bar'' to be displayed on the first line of the screen rather than near the bottom. - 66..33..226666.. ssttrriicctt__tthhrreeaaddss + 66..33..229922.. ssttrriicctt__mmiimmee + + Type: boolean + Default: yes + + When unset, non MIME-compliant messages that doesn't have any charset + indication in ``Content-Type'' field can be displayed (non MIME- + compliant messages are often generated by old mailers or buggy mailers + like MS Outlook Express). See also ``$assumed_charset''. + + This option also replaces linear-white-space between encoded-word and + *text to a single space to prevent the display of MIME-encoded + ``Subject'' field from being devided into multiple lines. + + 66..33..229933.. ssttrriicctt__tthhrreeaaddss Type: boolean Default: no @@ -6423,46 +7167,55 @@ personal mailbox where you might have several unrelated messages with the subject ``hi'' which will get grouped together. - 66..33..226677.. ssuussppeenndd + 66..33..229944.. ssttuuffff__qquuootteedd + + Type: boolean + Default: no + + If set, attachments with flowed format will have their quoting + ``stuffed'', i.e. a space will be inserted between the quote + characters and the actual text. + + 66..33..229955.. ssuussppeenndd Type: boolean Default: yes - When _u_n_s_e_t, mutt won't stop when the user presses the terminal's _s_u_s_p - key, usually ``control-Z''. This is useful if you run mutt inside an - xterm using a command like xterm -e mutt. + When _u_n_s_e_t, mutt-ng won't stop when the user presses the terminal's + _s_u_s_p key, usually ``control-Z''. This is useful if you run mutt-ng + inside an xterm using a command like xterm -e mutt-ng. - 66..33..226688.. tteexxtt__fflloowweedd + 66..33..229966.. tteexxtt__fflloowweedd Type: boolean Default: no - When set, mutt will generate text/plain; format=flowed attachments. + When set, mutt-ng will generate text/plain; format=flowed attachments. This format is easier to handle for some mailing software, and generally just looks like ordinary text. To actually make use of this format's features, you'll need support in your editor. Note that ``$indent_string'' is ignored when this option is set. - 66..33..226699.. tthhrreeaadd__rreecceeiivveedd + 66..33..229977.. tthhoorroouugghh__sseeaarrcchh Type: boolean Default: no - When set, mutt uses the date received rather than the date sent to - thread messages by subject. + Affects the _~_b and _~_h search operations described in section + ````patterns'''' above. If set, the headers and attachments of + messages to be searched are decoded before searching. If unset, + messages are searched as they appear in the folder. - 66..33..227700.. tthhoorroouugghh__sseeaarrcchh + 66..33..229988.. tthhrreeaadd__rreecceeiivveedd Type: boolean Default: no - Affects the _~_b and _~_h search operations described in section - ````patterns'''' above. If set, the headers and attachments of - messages to be searched are decoded before searching. If unset, - messages are searched as they appear in the folder. + When set, mutt-ng uses the date received rather than the date sent to + thread messages by subject. - 66..33..227711.. ttiillddee + 66..33..229999.. ttiillddee Type: boolean Default: no @@ -6470,26 +7223,27 @@ When set, the internal-pager will pad blank lines to the bottom of the screen with a tilde (~). - 66..33..227722.. ttiimmeeoouutt + 66..33..330000.. ttiimmeeoouutt Type: number Default: 600 - This variable controls the _n_u_m_b_e_r _o_f _s_e_c_o_n_d_s Mutt will wait for a key - to be pressed in the main menu before timing out and checking for new - mail. A value of zero or less will cause Mutt to never time out. + This variable controls the _n_u_m_b_e_r _o_f _s_e_c_o_n_d_s Mutt-ng will wait for a + key to be pressed in the main menu before timing out and checking for + new mail. A value of zero or less will cause Mutt-ng to never time + out. - 66..33..227733.. ttmmppddiirr + 66..33..330011.. ttmmppddiirr Type: path Default: "" - This variable allows you to specify where Mutt will place its + This variable allows you to specify where Mutt-ng will place its temporary files needed for displaying and composing messages. If this variable is not set, the environment variable TMPDIR is used. If TMPDIR is not set then "/tmp" is used. - 66..33..227744.. ttoo__cchhaarrss + 66..33..330022.. ttoo__cchhaarrss Type: string Default: " +TCFL" @@ -6505,12 +7259,24 @@ by _y_o_u. The sixth character is used to indicate when a mail was sent to a mailing-list you subscribe to (default: L). - 66..33..227755.. ttuunnnneell + 66..33..330033.. ttrraasshh + + Type: path + Default: "" + + If set, this variable specifies the path of the trash folder where the + mails marked for deletion will be moved, instead of being irremediably + purged. + + NOTE: When you delete a message in the trash folder, it is really + deleted, so that you have a way to clean the trash. + + 66..33..330044.. ttuunnnneell Type: string Default: "" - Setting this variable will cause mutt to open a pipe to a command + Setting this variable will cause mutt-ng to open a pipe to a command instead of a raw socket. You may be able to use this to set up preauthenticated connections to your IMAP/POP3 server. Example: @@ -6519,7 +7285,23 @@ NOTE: For this example to work you must be able to log in to the remote machine without having to enter a password. - 66..33..227766.. uussee__88bbiittmmiimmee + 66..33..330055.. uummaasskk + + Type: number + Default: 0077 + + This sets the umask that will be used by mutt-ng when creating all + kinds of files. If unset, the default value is 077. + + 66..33..330066.. uunnccoollllaappssee__jjuummpp + + Type: boolean + Default: no + + When _s_e_t, Mutt-ng will jump to the next unread message, if any, when + the current thread is _u_ncollapsed. + + 66..33..330077.. uussee__88bbiittmmiimmee Type: boolean Default: no @@ -6528,45 +7310,36 @@ sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be able to send mail. - When _s_e_t, Mutt will invoke ````$sendmail'''' with the -B8BITMIME flag - when sending 8-bit messages to enable ESMTP negotiation. + When _s_e_t, Mutt-ng will invoke ````$sendmail'''' with the -B8BITMIME + flag when sending 8-bit messages to enable ESMTP negotiation. - 66..33..227777.. uussee__ddoommaaiinn + 66..33..330088.. uussee__ddoommaaiinn Type: boolean Default: yes - When set, Mutt will qualify all local addresses (ones without the + When set, Mutt-ng will qualify all local addresses (ones without the @host portion) with the value of ````$hostname''''. If _u_n_s_e_t, no addresses will be qualified. - 66..33..227788.. uussee__ffrroomm + 66..33..330099.. uussee__ffrroomm Type: boolean Default: yes - When _s_e_t, Mutt will generate the `From:' header field when sending + When _s_e_t, Mutt-ng will generate the `From:' header field when sending messages. If _u_n_s_e_t, no `From:' header field will be generated unless the user explicitly sets one using the ````my_hdr'''' command. - 66..33..227799.. uussee__iippvv66 - - Type: boolean - Default: yes - - When _s_e_t, Mutt will look for IPv6 addresses of hosts it tries to - contact. If this option is unset, Mutt will restrict itself to IPv4 - addresses. Normally, the default should work. - - 66..33..228800.. uusseerr__aaggeenntt + 66..33..331100.. uusseerr__aaggeenntt Type: boolean Default: yes - When _s_e_t, mutt will add a "User-Agent" header to outgoing messages, - indicating which version of mutt was used for composing them. + When _s_e_t, mutt-ng will add a "User-Agent" header to outgoing messages, + indicating which version of mutt-ng was used for composing them. - 66..33..228811.. vviissuuaall + 66..33..331111.. vviissuuaall Type: path Default: "" @@ -6574,30 +7347,32 @@ Specifies the visual editor to invoke when the _~_v command is given in the builtin editor. - 66..33..228822.. wwaaiitt__kkeeyy + 66..33..331122.. wwaaiitt__kkeeyy Type: boolean Default: yes - Controls whether Mutt will ask you to press a key after _s_h_e_l_l_- _e_s_c_a_p_e, - _p_i_p_e_-_m_e_s_s_a_g_e, _p_i_p_e_-_e_n_t_r_y, _p_r_i_n_t_-_m_e_s_s_a_g_e, and _p_r_i_n_t_-_e_n_t_r_y commands. + Controls whether Mutt-ng will ask you to press a key after _s_h_e_l_l_- + _e_s_c_a_p_e, _p_i_p_e_-_m_e_s_s_a_g_e, _p_i_p_e_-_e_n_t_r_y, _p_r_i_n_t_-_m_e_s_s_a_g_e, and _p_r_i_n_t_-_e_n_t_r_y + commands. It is also used when viewing attachments with ````auto_view'''', provided that the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, and the external program is interactive. - When set, Mutt will always ask for a key. When unset, Mutt will wait - for a key only if the external command returned a non-zero status. + When set, Mutt-ng will always ask for a key. When unset, Mutt-ng will + wait for a key only if the external command returned a non-zero + status. - 66..33..228833.. wweeeedd + 66..33..331133.. wweeeedd Type: boolean Default: yes - When set, mutt will weed headers when when displaying, forwarding, + When set, mutt-ng will weed headers when displaying, forwarding, printing, or replying to messages. - 66..33..228844.. wwrraapp__sseeaarrcchh + 66..33..331144.. wwrraapp__sseeaarrcchh Type: boolean Default: yes @@ -6607,15 +7382,23 @@ When set, searches will wrap around the first (or last) message. When unset, searches will not wrap. - 66..33..228855.. wwrraappmmaarrggiinn + 66..33..331155.. wwrraappmmaarrggiinn Type: number Default: 0 Controls the size of the margin remaining at the right side of the - terminal when mutt's pager does smart wrapping. + terminal when mutt-ng's pager does smart wrapping. - 66..33..228866.. wwrriittee__iinncc + 66..33..331166.. wwrriittee__bbcccc + + Type: boolean + Default: yes + + Controls whether mutt-ng writes out the Bcc header when preparing + messages to be sent. Exim users may wish to unset this. + + 66..33..331177.. wwrriittee__iinncc Type: number Default: 10 @@ -6626,21 +7409,41 @@ Also see the ````$read_inc'''' variable. - 66..33..228877.. wwrriittee__bbcccc + 66..33..331188.. xx__ccoommmmeenntt__ttoo Type: boolean - Default: yes + Default: no + + If _s_e_t, Mutt-ng will add ``X-Comment-To:'' field (that contains full + name of original article author) to article that followuped to + newsgroup. - Controls whether mutt writes out the Bcc header when preparing - messages to be sent. Exim users may wish to use this. + 66..33..331199.. xxtteerrmm__iiccoonn - 66..33..228888.. xx__ccoommmmeenntt__ttoo + Type: string + Default: "M%?n?AIL&ail?" + + Controls the format of the icon title, as long as xterm_set_titles is + enabled. This string is identical in formatting to the one used by + ````$status_format''''. + + 66..33..332200.. xxtteerrmm__sseett__ttiittlleess Type: boolean Default: no - If _s_e_t, Mutt will add ``X-Comment-To:'' field (that contains full name - of original article author) to article that followuped to newsgroup. + Controls whether mutt-ng sets the xterm title bar and icon name (as + long as you're in an appropriate terminal). The default must be off to + force in the validity checking. + + 66..33..332211.. xxtteerrmm__ttiittllee + + Type: string + Default: "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?" + + Controls the format of the title bar of the xterm provided that + xterm_set_titles has been set. This string is identical in formatting + to the one used by ````$status_format''''. 66..44.. FFuunnccttiioonnss @@ -6655,7 +7458,6 @@ (such as movement) available in all menus except for _p_a_g_e_r and _e_d_i_t_o_r. Changing settings for this menu will affect the default bindings for all menus (except as noted). - bottom-page L move to the bottom of the page current-bottom not bound move current entry to bottom of page current-middle not bound move current entry to middle of page @@ -6684,7 +7486,9 @@ shell-escape ! run a program in a subshell tag-entry t toggle the tag on the current entry tag-prefix ; apply next command to tagged entries + tag-prefix-cond not bound apply next function ONLY to tagged messages top-page H move to the top of the page + what-key not bound display the keycode for a key press 66..44..22.. iinnddeexx @@ -6985,14 +7789,14 @@ Mark Holloman , Andreas Holzmann , Marco d'Itri , - Björn Jacke , + Bjrn Jacke , Byrial Jensen , David Jeske , Christophe Kalt , Tommi Komulainen , Felix von Leitner (a.k.a ``Fefe'') , Brandon Long , - Jimmy Mäkelä , + Jimmy Mkel , Lars Marowsky-Bree , Thomas ``Mike'' Michlmayr , Andrew W. Nosenko ,