+ When set, functions in the index menu which affect a message will be
+ applied to all tagged messages (if there are any). When unset, you must
+ first use the ``tag-prefix'' function (default: ";") to make the next
+ function apply to all tagged messages.
+
+20. autoedit
+
+ 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''.
+
+21. beep
+
+ Type: boolean
+
+ Default: yes
+
+ When this variable is set, Mutt-ng will beep when an error occurs.
+
+22. beep_new
+
+ Type: boolean
+
+ Default: no
+
+ 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.
+
+23. bounce
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Controls whether you will be asked to confirm bouncing messages. If set to
+ yes you don't get asked if you want to bounce a message. Setting this
+ variable to no is not generally useful, and thus not recommended, because
+ you are unable to bounce messages.
+
+24. bounce_delivered
+
+ Type: boolean
+
+ Default: yes
+
+ When this variable is set, Mutt-ng will include Delivered-To: header
+ fields when bouncing messages. Postfix users may wish to unset this
+ variable.
+
+25. braille_friendly
+
+ Type: boolean
+
+ Default: no
+
+ When this variable is set, mutt will place the cursor at the beginning of
+ the current line in menus, even when the arrow_cursor variable is unset,
+ making it easier for blind persons using Braille displays to follow these
+ menus. The option is disabled by default because many visual terminals
+ don't permit making the cursor invisible.
+
+26. certificate_file
+
+ Type: path
+
+ Default: "˜/.mutt_certificates"
+
+ Availability: SSL or GNUTLS
+
+ 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=˜/.muttng/certificates
+
+27. charset
+
+ Type: string
+
+ Default: ""
+
+ Character set your terminal uses to display and enter textual data.
+
+28. check_new
+
+ Type: boolean
+
+ Default: yes
+
+ Note: this option only affects maildir and MH style mailboxes.
+
+ When set, 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 it's unset, no check for new mail
+ is performed while the mailbox is open.
+
+29. collapse_unread
+
+ Type: boolean
+
+ Default: yes
+
+ When unset, Mutt-ng will not collapse a thread if it contains any unread
+ messages.
+
+30. compose_format
+
+ Type: string
+
+ Default: "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"
+
+ Controls the format of the status line displayed in the ``compose'' menu.
+ This string is similar to ``$status_format'', but has its own set of
+ printf(3)-like sequences:
+
+ %a
+
+ total number of attachments
+
+ %h
+
+ local hostname
+
+ %l
+
+ approximate size (in bytes) of the current message
+
+ %v
+
+ Mutt-ng version string
+
+ See the text describing the ``$status_format'' option for more information
+ on how to set ``$compose_format''.
+
+31. config_charset
+
+ Type: string
+
+ Default: ""
+
+ When defined, Mutt-ng will recode commands in rc files from this encoding.
+
+32. confirmappend
+
+ Type: boolean
+
+ Default: yes
+
+ When set, Mutt-ng will prompt for confirmation when appending messages to
+ an existing mailbox.
+
+33. confirmcreate
+
+ Type: boolean
+
+ Default: yes
+
+ When set, Mutt-ng will prompt for confirmation when saving messages to a
+ mailbox which does not yet exist before creating it.
+
+34. connect_timeout
+
+ Type: number
+
+ Default: 30
+
+ 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-ng to wait indefinitely for the connection to
+ succeed.
+
+35. content_type
+
+ Type: string
+
+ Default: "text/plain"
+
+ Sets the default Content-Type: header field for the body of newly composed
+ messages.
+
+36. copy
+
+ Type: quadoption
+
+ Default: yes
+
+ This variable controls whether or not copies of your outgoing messages
+ will be saved for later references. Also see ``$record'', ``$save_name'',
+ ``$force_name'' and ``fcc-hook''.
+
+37. crypt_autoencrypt
+
+ 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
+ send-hook command. It can be overridden by use of the pgp-menu, 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 smime-menu.
+ (Crypto only)
+
+38. crypt_autopgp
+
+ Type: boolean
+
+ Default: yes
+
+ 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''.
+
+39. crypt_autosign
+
+ 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 pgp-menu, 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
+ smime-menu. (Crypto only)
+
+40. crypt_autosmime
+
+ Type: boolean
+
+ Default: yes
+
+ 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''.
+
+41. crypt_replyencrypt
+
+ Type: boolean
+
+ Default: yes
+
+ If set, automatically PGP or OpenSSL encrypt replies to messages which are
+ encrypted. (Crypto only)
+
+42. crypt_replysign
+
+ Type: boolean
+
+ Default: no
+
+ If set, automatically PGP or OpenSSL sign replies to messages which are
+ signed.
+
+ Note: this does not work on messages that are encrypted and signed!
+ (Crypto only)
+
+43. crypt_replysignencrypted
+
+ 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)
+
+44. crypt_timestamp
+
+ 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)
+
+45. crypt_use_gpgme
+
+ 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: You need to use this option in your .muttngrc configuration file as
+ it won't have any effect when used interactively.
+
+46. crypt_verify_sig
+
+ 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)
+
+47. date_format
+
+ Type: string
+
+ Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
+
+ This variable controls the format of the date printed by the ``%d''
+ sequence in ``$index_format''. This is passed to strftime(3) to process
+ the date.
+
+ Unless the first character in the string is a bang (``!''), the month and
+ week day names are expanded according to the locale specified in the
+ variable ``$locale''. If the first character in the string is a bang, the
+ bang is discarded, and the month and week day names in the rest of the
+ string are expanded in the C locale (that is in US English).
+
+48. debug_level
+
+ Type: number
+
+ Default: 1
+
+ Availability: debug
+
+ This variable specifies the current debug level and may be used to
+ increase or decrease the verbosity level during runtime. It overrides the
+ level given with the -d command line option.
+
+ Currently, this number must be >= 0 and <= 5 and muttng must be started
+ with -d to enable debugging at all; enabling at runtime is not possible.
+
+49. default_hook
+
+ Type: string
+
+ Default: "˜f %s !˜P | (˜P ˜C %s)"
+
+ This variable controls how send-hooks, message-hooks, save-hooks, and
+ fcc-hooks will be interpreted if they are specified with only a simple
+ regexp, instead of a matching pattern. The hooks are expanded when they
+ are declared, so a hook will be interpreted according to the value of this
+ variable at the time the hook is declared. The default value matches if
+ the message is either from a user matching the regular expression given,
+ or if it is from you (if the from address matches ``alternates'') and is
+ to or cc'ed to a user matching the given regular expression.
+
+50. delete
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Controls whether or not messages are really deleted when closing or
+ synchronizing a mailbox. If set to yes, messages marked for deleting will
+ automatically be purged without prompting. If set to no, messages marked
+ for deletion will be kept in the mailbox.
+
+51. delete_space
+
+ Type: boolean
+
+ Default: no
+
+ When sending messages with format=flowed by setting the $text_flowed
+ variable, this variable specifies whether to also set the DelSp parameter
+ to yes. If this is unset, no additional parameter will be send as a value
+ of no already is the default behavior.
+
+ Note: this variable only has an effect on outgoing messages (if
+ $text_flowed is set) but not on incomming.
+
+52. delete_untag
+
+ Type: boolean
+
+ Default: yes
+
+ If this option is set, 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.
+
+53. digest_collapse
+
+ Type: boolean
+
+ Default: yes
+
+ If this option is set, 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.
+
+54. display_filter
+
+ Type: path
+
+ Default: ""
+
+ When set, specifies a command used to filter messages. When a message is
+ viewed it is passed as standard input to $display_filter, and the filtered
+ message is read from the standard output.
+
+55. dotlock_program
+
+ Type: path
+
+ Default: "$muttng_bindir/muttng_dotlock"
+
+ Availability: Standalone and Dotlock
+
+ Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng.
+
+56. dsn_notify
+
+ Type: string
+
+ Default: ""
+
+ Note: you should not enable this unless you are using Sendmail 8.8.x or
+ greater or in connection with the SMTP support via libESMTP.
+
+ This variable sets the request for when notification is returned. The
+ string consists of a comma separated list (no spaces!) of one or more of
+ the following: never, to never request notification, failure, to request
+ notification on transmission failure, delay, to be notified of message
+ delays, success, to be notified of successful transmission.
+
+ Example: set dsn_notify="failure,delay"
+
+57. dsn_return
+
+ Type: string
+
+ Default: ""
+
+ Note: you should not enable this unless you are using Sendmail 8.8.x or
+ greater or in connection with the SMTP support via libESMTP.
+
+ This variable controls how much of your message is returned in DSN
+ messages. It may be set to either hdrs to return just the message header,
+ or full to return the full message.
+
+ Example: set dsn_return=hdrs
+
+58. duplicate_threads
+
+ Type: boolean
+
+ Default: yes
+
+ This variable controls whether Mutt-ng, when sorting by threads, threads
+ messages with the same Message-Id: header field 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.
+
+59. edit_headers
+
+ Type: boolean
+
+ Default: no
+
+ This option allows you to edit the header of your outgoing messages along
+ with the body of your message.
+
+ Which empty header fields to show is controlled by the $editor_headers
+ option.
+
+60. editor
+
+ Type: path
+
+ Default: ""
+
+ 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.
+
+61. editor_headers
+
+ Type: string
+
+ Default: "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To:
+ X-Comment-To:"
+
+ If $edit_headers is set, this space-separated list specifies which
+ non-empty header fields to edit in addition to user-defined headers.
+
+ Note: if $edit_headers had to be turned on by force because $strict_mailto
+ is unset, this option has no effect.
+
+62. encode_from
+
+ Type: boolean
+
+ Default: no
+
+ When set, Mutt-ng will quoted-printable encode messages when they contain
+ the string ``From '' (note the trailing space) in the beginning of a line.
+ Useful to avoid the tampering certain mail delivery and transport agents
+ tend to do with messages.
+
+ Note: as mutt-ng currently violates RfC3676 defining format=flowed, it's
+ <em/strongly/ advised to set this option although discouraged by the
+ standard. Alternatively, you must take care of space-stuffing <tt/From /
+ lines (with a trailing space) yourself.
+
+63. entropy_file
+
+ Type: path
+
+ Default: ""
+
+ Availability: SSL
+
+ The file which includes random data that is used to initialize SSL library
+ functions.
+
+64. envelope_from
+
+ Type: boolean
+
+ Default: no
+
+ When set, Mutt-ng will try to derive the message's envelope sender from
+ the ``From:'' header field. Note that this information is passed to the
+ 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.
+
+65. escape
+
+ Type: string
+
+ Default: "˜"
+
+ Escape character to use for functions in the builtin editor.
+
+66. fast_reply
+
+ Type: boolean
+
+ Default: no
+
+ When set, the initial prompt for recipients and subject are skipped when
+ replying to messages, and the initial prompt for subject is skipped when
+ forwarding messages.
+
+ Note: this variable has no effect when the ``$autoedit'' variable is set.
+
+67. fcc_attach
+
+ Type: boolean
+
+ Default: yes
+
+ This variable controls whether or not attachments on outgoing messages are
+ saved along with the main body of your message.
+
+68. fcc_clear
+
+ Type: boolean
+
+ Default: no
+
+ When this variable is set, FCCs will be stored unencrypted and unsigned,
+ even when the actual message is encrypted and/or signed. (PGP only)
+
+69. file_charset
+
+ 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.
+
+70. folder
+
+ Type: path
+
+ Default: "˜/Mail"
+
+ Specifies the default location of your mailboxes. A ``+'' or ``='' at the
+ beginning of a pathname will be expanded to the value of this variable.
+ Note that if you change this variable from the default value you need to
+ make sure that the assignment occurs before you use ``+'' or ``='' for any
+ other variables since expansion takes place during the ``set'' command.
+
+71. folder_format
+
+ Type: string
+
+ Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
+
+ This variable allows you to customize the file browser display to your
+ personal taste. This string is similar to ``$index_format'', but has its
+ own set of printf(3)-like sequences:
+
+ %C
+
+ current file number
+
+ %d
+
+ date/time folder was last modified
+
+ %f
+
+ filename
+
+ %F
+
+ file permissions
+
+ %g
+
+ group name (or numeric gid, if missing)
+
+ %l
+
+ number of hard links
+
+ %N
+
+ N if folder has new mail, blank otherwise
+
+ %s
+
+ size in bytes
+
+ %t
+
+ * if the file is tagged, blank otherwise
+
+ %u
+
+ owner name (or numeric uid, if missing)
+
+ %>X
+
+ right justify the rest of the string and pad with character "X"
+
+ %|X
+
+ pad to the end of the line with character "X"
+
+72. followup_to
+
+ Type: boolean
+
+ Default: yes
+
+ Controls whether or not the Mail-Followup-To: header field is generated
+ when sending mail. When set, Mutt-ng will generate this field when you are
+ replying to a known mailing list, specified with the ``subscribe'' or
+ ``lists'' commands or detected by common mailing list headers.
+
+ This field has two purposes. First, preventing you from receiving
+ duplicate copies of replies to messages which you send to mailing lists.
+ Second, ensuring that you do get a reply separately for any messages sent
+ to known lists to which you are not subscribed. The header will contain
+ only the list's address for subscribed lists, and both the list address
+ and your own email address for unsubscribed lists. Without this header, a
+ group reply to your message sent to a subscribed list will be sent to both
+ the list and your address, resulting in two copies of the same email for
+ you.
+
+73. force_buffy_check
+
+ Type: boolean
+
+ Default: no
+
+ When set, it causes Mutt-ng to check for new mail when the buffy-list
+ command is invoked. When unset, buffy_list will just list all mailboxes
+ which are already known to have new mail.
+
+ Also see the following variables: ``$timeout'', ``$mail_check'' and
+ ``$imap_mail_check''.
+
+74. force_name
+
+ Type: boolean
+
+ Default: no
+
+ 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.
+
+75. forward_decode
+
+ Type: boolean
+
+ Default: yes
+
+ Controls the decoding of complex MIME messages into text/plain when
+ forwarding a message. The message header is also RFC2047 decoded. This
+ variable is only used, if ``$mime_forward'' is unset, otherwise
+ ``$mime_forward_decode'' is used instead.
+
+76. forward_decrypt
+
+ 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 set and ``$mime_forward_decode'' is
+ unset. (PGP only)
+
+77. forward_edit
+
+ Type: quadoption
+
+ Default: yes
+
+ This quadoption controls whether or not the user is automatically placed
+ in the editor when forwarding messages. For those who always want to
+ forward with no modification, use a setting of no.
+
+78. forward_format
+
+ Type: string
+
+ Default: "[%a: %s]"
+
+ This variable controls the default subject when forwarding a message. It
+ uses the same format sequences as the ``$index_format'' variable.
+
+79. forward_quote
+
+ Type: boolean
+
+ Default: no
+
+ When set forwarded messages included in the main body of the message (when
+ ``$mime_forward'' is unset) will be quoted using ``$indent_string''.
+
+80. from
+
+ Type: e-mail address
+
+ Default: ""
+
+ This variable contains a default from address. It can be overridden using
+ my_hdr (including from send-hooks) and ``$reverse_name''. This variable is
+ ignored if ``$use_from'' is unset.
+
+ E.g. you can use send-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From:
+ Foo Bar <foo@bar.fb>' when replying to the mutt-ng developer's mailing
+ list and Mutt-ng takes this email address.
+
+ Defaults to the contents of the environment variable $EMAIL.
+
+81. gecos_mask
+
+ Type: regular expression
+
+ Default: "^[^,]*"
+
+ 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 do: set 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-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-ng will
+ expand ``Franklin'' to ``Franklin, Steve''.
+
+82. hdrs
+
+ Type: boolean
+
+ Default: yes
+
+ When unset, the header fields normally added by the ``my_hdr'' command are
+ not created. This variable must be unset before composing a new message or
+ replying in order to take effect. If set, the user defined header fields
+ are added to every new message.
+
+83. header
+
+ Type: boolean
+
+ Default: no
+
+ 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.
+
+84. header_cache
+
+ Type: path
+
+ Default: ""
+
+ Availability: Header Cache
+
+ The $header_cache variable points to the header cache database.
+
+ If $header_cache points to a directory it will contain a header cache
+ database per folder. If $header_cache points to a file that file will be a
+ single global header cache. By default it is unset so no header caching
+ will be used.
+
+85. header_cache_compress
+
+ Type: boolean
+
+ Default: no
+
+ If enabled the header cache will be compressed. So only one fifth of the
+ usual diskspace is used, but the uncompression can result in a slower open
+ of the cached folder.
+
+86. help
+
+ Type: boolean
+
+ Default: yes
+
+ When set, help lines describing the bindings for the major functions
+ provided by each menu are displayed on the first line of the screen.
+
+ Note: 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-ng is running. Since this
+ variable is primarily aimed at new users, neither of these should present
+ a major problem.
+
+87. hidden_host
+
+ Type: boolean
+
+ Default: no
+
+ 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-ID: header fields, and it will not lead to the
+ cut-off of first-level domains.
+
+88. hide_limited
+
+ Type: boolean
+
+ Default: no
+
+ When set, Mutt-ng will not show the presence of messages that are hidden
+ by limiting, in the thread tree.
+
+89. hide_missing
+
+ Type: boolean
+
+ Default: yes
+
+ When set, Mutt-ng will not show the presence of missing messages in the
+ thread tree.
+
+90. hide_thread_subject
+
+ Type: boolean
+
+ Default: yes
+
+ 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.
+
+91. hide_top_limited
+
+ Type: boolean
+
+ Default: no
+
+ 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.
+
+92. hide_top_missing
+
+ Type: boolean
+
+ Default: yes
+
+ 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.
+
+93. history
+
+ Type: number
+
+ Default: 10
+
+ This variable controls the size (in number of strings remembered) of the
+ string history buffer. The buffer is cleared each time the variable is
+ changed.
+
+94. honor_followup_to
+
+ Type: quadoption
+
+ Default: yes
+
+ This variable controls whether or not a Mail-Followup-To: header field is
+ honored when group-replying to a message.
+
+95. hostname
+
+ Type: string
+
+ Default: ""
+
+ Specifies the hostname to use after the ``@'' in local e-mail addresses
+ and during generation of Message-Id: headers.
+
+ Please be sure to really know what you are doing when changing this
+ variable to configure a custom domain part of Message-IDs.
+
+96. ignore_list_reply_to
+
+ Type: boolean
+
+ Default: no
+
+ Affects the behaviour of the reply function when replying to messages from
+ mailing lists. When set, if the ``Reply-To:'' header field is set to the
+ same value as the ``To:'' header field, Mutt-ng assumes that the
+ ``Reply-To:'' header 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 list-reply function;
+ group-reply will reply to both the sender and the list.
+
+97. imap_authenticators
+
+ Type: string
+
+ Default: ""
+
+ Availability: IMAP
+
+ 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='' capability string, e.g. ``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"
+
+ Note: 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.
+
+98. imap_check_subscribed
+
+ Type: boolean
+
+ Default: no
+
+ When set, mutt will fetch the set of subscribed folders from your server
+ on connection, and add them to the set of mailboxes it polls for new mail.
+ See also the ``mailboxes'' command.
+
+99. imap_delim_chars
+
+ Type: string
+
+ Default: "/."
+
+ Availability: IMAP
+
+ This contains the list of characters which you would like to treat as
+ folder separators for displaying IMAP paths. In particular it helps in
+ using the '=' shortcut for your $folder variable.
+
+100. imap_headers
+
+ Type: string
+
+ Default: ""
+
+ Availability: IMAP
+
+ 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.
+
+ Note: This is a space separated list.
+
+101. imap_home_namespace
+
+ Type: string
+
+ Default: ""
+
+ Availability: IMAP
+
+ You normally want to see your personal folders alongside your INBOX in the
+ IMAP browser. If you see something else, you may set this variable to the
+ IMAP path to your folders.
+
+102. imap_keepalive
+
+ Type: number
+
+ Default: 900
+
+ Availability: IMAP
+
+ This variable specifies the maximum amount of time in seconds that 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.
+
+103. imap_list_subscribed
+
+ Type: boolean
+
+ Default: no
+
+ Availability: IMAP
+
+ This variable configures whether IMAP folder browsing will look for only
+ subscribed folders or all folders. This can be toggled in the IMAP browser
+ with the toggle-subscribed function.
+
+104. imap_login
+
+ Type: string
+
+ Default: ""
+
+ Availability: IMAP
+
+ Your login name on the IMAP server.
+
+ This variable defaults to the value of ``$imap_user.''
+
+105. imap_mail_check
+
+ Type: number
+
+ Default: 300
+
+ This variable configures how often (in seconds) Mutt-ng should look for
+ new mail in IMAP folders. This is split from the ``mail_check'' variable
+ to generate less traffic and get more accurate information for local
+ folders.
+
+106. imap_pass
+
+ Type: string
+
+ Default: ""
+
+ Availability: IMAP
+
+ Specifies the password for your IMAP account. If unset, Mutt-ng will
+ prompt you for your password when you invoke the fetch-mail function.
+
+ Warning: you should only use this option when you are on a fairly secure
+ machine, because the superuser can read your configuration even if you are
+ the only one who can read the file.
+
+107. imap_passive
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: 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-ng invocation, or if opening the connection is slow.
+
+108. imap_peek
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: IMAP
+
+ 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.
+
+109. imap_reconnect
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: IMAP
+
+ Controls whether or not Mutt-ng will try to reconnect to IMAP server when
+ the connection is lost.
+
+110. imap_servernoise
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: IMAP
+
+ 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.
+
+111. imap_user
+
+ Type: string
+
+ Default: ""
+
+ Availability: IMAP
+
+ The name of the user whose mail you intend to access on the IMAP server.
+
+ This variable defaults to your user name on the local machine.
+
+112. implicit_autoview
+
+ Type: boolean
+
+ Default: no
+
+ If set, Mutt-ng will look for a mailcap entry with the ``copiousoutput''
+ flag set for every MIME attachment it doesn't have an 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.
+
+113. include
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Controls whether or not a copy of the message(s) you are replying to is
+ included in your reply.
+
+114. include_onlyfirst
+
+ Type: boolean
+
+ Default: no
+
+ Controls whether or not Mutt-ng includes only the first attachment of the
+ message you are replying.
+
+115. indent_string
+
+ Type: string
+
+ Default: "> "
+
+ Specifies the string to prepend to each line of text quoted in a message
+ to which you are replying. You are strongly encouraged not to change this
+ value, as it tends to agitate the more fanatical netizens.
+
+116. index_format
+
+ Type: string
+
+ Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
+
+ This variable allows you to customize the message index display to your
+ personal taste.
+
+ ``Format strings'' are similar to the strings used in the ``C'' function
+ printf(3) to format output (see the man page for more detail). The
+ following sequences are defined in Mutt-ng:
+
+ %a
+
+ address of the author
+
+ %A
+
+ reply-to address (if present; otherwise: address of author)
+
+ %b
+
+ filename of the original message folder (think mailBox)
+
+ %B
+
+ the list to which the letter was sent, or else the folder name
+ (%b).
+
+ %c
+
+ number of characters (bytes) in the message
+
+ %C
+
+ current message number
+
+ %d
+
+ date and time of the message in the format specified by
+ ``date_format'' converted to sender's time zone
+
+ %D
+
+ date and time of the message in the format specified by
+ ``date_format'' converted to the local time zone
+
+ %e
+
+ current message number in thread
+
+ %E
+
+ number of messages in current thread
+
+ %f
+
+ entire From: line (address + real name)
+
+ %F
+
+ author name, or recipient name if the message is from you
+
+ %H
+
+ spam attribute(s) of this message
+
+ %g
+
+ newsgroup name (if compiled with nntp support)
+
+ %i
+
+ message-id of the current message
+
+ %l
+
+ number of lines in the message (does not work with maildir, mh,
+ and possibly IMAP folders)
+
+ %L
+
+ If an address in the To or CC header field matches an address
+ defined by the users ``subscribe'' command, this displays "To
+ <list-name>", otherwise the same as %F.
+
+ %m
+
+ total number of message in the mailbox
+
+ %M
+
+ number of hidden messages if the thread is collapsed.
+
+ %N
+
+ message score
+
+ %n
+
+ author's real name (or address if missing)
+
+ %O
+
+ (_O_riginal save folder) Where Mutt-ng would formerly have stashed
+ the message: list name or recipient name if no list
+
+ %s
+
+ subject of the message
+
+ %S
+
+ status of the message (N/D/d/!/r/*)
+
+ %t
+
+ `to:' field (recipients)
+
+ %T
+
+ the appropriate character from the $to_chars string
+
+ %u
+
+ user (login) name of the author
+
+ %v
+
+ first name of the author, or the recipient if the message is from
+ you
+
+ %W
+
+ name of organization of author (`organization:' field)
+
+ %y
+
+ `x-label:' field, if present
+
+ %Y
+
+ `x-label' field, if present, and (1) not at part of a thread tree,
+ (2) at the top of a thread, or (3) `x-label' is different from
+ preceding message's `x-label'.
+
+ %Z
+
+ message status flags
+
+ %{fmt}
+
+ the date and time of the message is converted to sender's time
+ zone, and ``fmt'' is expanded by the library function
+ ``strftime''; a leading bang disables locales
+
+ %[fmt]
+
+ the date and time of the message is converted to the local time
+ zone, and ``fmt'' is expanded by the library function
+ ``strftime''; a leading bang disables locales
+
+ %(fmt)
+
+ the local date and time when the message was received. ``fmt'' is
+ expanded by the library function ``strftime''; a leading bang
+ disables locales
+
+ %<fmt>
+
+ the current local time. ``fmt'' is expanded by the library
+ function ``strftime''; a leading bang disables locales.
+
+ %>X
+
+ right justify the rest of the string and pad with character "X"
+
+ %|X
+
+ pad to the end of the line with character "X"
+
+ See also: ``$to_chars''.
+
+117. ispell
+
+ Type: path
+
+ Default: "ispell"
+
+ How to invoke ispell (GNU's spell-checking software).
+
+118. keep_flagged
+
+ Type: boolean
+
+ Default: no
+
+ If set, read messages marked as flagged will not be moved from your spool
+ mailbox to your ``$mbox'' mailbox, or as a result of a ``mbox-hook''
+ command.
+
+119. list_reply
+
+ 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.
+
+120. locale
+
+ Type: string