+ %s
+ size
+
+ %t
+ tagged flag
+
+ %T
+ graphic tree characters
+
+ %u
+ unlink (=to delete) flag
+
+ %>X
+ right justify the rest of the string and pad with character "X"
+
+ %|X
+ pad to the end of the line with character "X"
+
+15. attach_remind_regexp
+
+ Type: regular expression
+
+ Default: "attach"
+
+ If this variable is non-empty, muttng will scan a message's contents before sending for this regular expression. If it is found, it will ask for what to do depending on the setting of $abort_noattach.
+
+ This variable and $abort_noattach are intended to remind the user to attach files if the message's text references them.
+
+16. attach_sep
+
+ Type: string
+
+ Default: "\n"
+
+ The separator to add between attachments when operating (saving, printing, piping, etc) on a list of tagged attachments.
+
+17. attach_split
+
+ Type: boolean
+
+ Default: yes
+
+ If this variable is unset, when operating (saving, printing, piping, 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-ng will operate on the attachments one by one.
+
+18. attribution
+
+ Type: string
+
+ Default: "On %d, %n wrote:"
+
+ This is the string that will precede a message which has been included in a reply. For a full listing of defined printf(3)-like sequences see the section on ``$index_format''.
+
+19. auto_tag
+
+ Type: boolean
+
+ Default: no
+
+ 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: 0
+
+ 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
+
+ Default: "C"
+
+ The locale used by strftime(3) to format dates. Legal values are the strings your system accepts for the locale variable LC_TIME.
+
+121. mail_check
+
+ Type: number
+
+ Default: 5
+
+ This variable configures how often (in seconds) Mutt-ng should look for new mail.
+
+ Note: This does not apply to IMAP mailboxes, see $imap_mail_check.
+
+122. mailcap_path
+
+ Type: string
+
+ Default: ""
+
+ This variable specifies which files to consult when attempting to display MIME bodies not directly supported by Mutt-ng.
+
+123. mailcap_sanitize
+
+ Type: boolean
+
+ Default: yes
+
+ 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.
+
+ DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING!
+
+124. maildir_header_cache_verify
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: Header Cache
+
+ Check for Maildir unaware programs other than Mutt-ng having modified maildir files when the header cache is in use. This incurs one stat(2) per message every time the folder is opened.
+
+125. maildir_trash
+
+ Type: boolean
+
+ Default: no
+
+ If set, messages marked as deleted will be saved with the maildir (T)rashed flag instead of physically deleted.
+
+ NOTE: this only applies to maildir-style mailboxes. Setting it will have no effect on other mailbox types.
+
+ It is similiar to the trash option.
+
+126. mark_old
+
+ Type: boolean
+
+ Default: yes
+
+ Controls whether or not Mutt-ng marks new unread messages as old 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.
+
+127. markers
+
+ Type: boolean
+
+ Default: yes
+
+ Controls the display of wrapped lines in the internal pager. If set, a ``+'' marker is displayed at the beginning of wrapped lines. Also see the ``$smart_wrap'' variable.
+
+128. mask
+
+ Type: regular expression
+
+ Default: "!^\.[^.]"
+
+ A regular expression used in the file browser, optionally preceded by the not operator ``!''. Only files whose names match this mask will be shown. The match is always case-sensitive.
+
+129. max_display_recips
+
+ Type: number
+
+ Default: 0
+
+ When set non-zero, this specifies the maximum number of recipient header lines (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In case the number of lines exeeds its value, the last line will have 3 dots appended.
+
+130. max_line_length
+
+ Type: number
+
+ Default: 0
+
+ When set, the maximum line length for displaying ``format = flowed'' 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.
+
+131. mbox
+
+ Type: path
+
+ Default: "˜/mbox"
+
+ This specifies the folder into which read mail in your ``$spoolfile'' folder will be appended.
+
+132. mbox_type
+
+ Type: folder magic
+
+ Default: mbox
+
+ The default mailbox type used when creating new folders. May be any of mbox, MMDF, MH and Maildir.
+
+133. menu_context
+
+ Type: number
+
+ Default: 0
+
+ This variable controls the number of lines of context that are given when scrolling through menus. (Similar to ``$pager_context''.)
+
+134. menu_move_off
+
+ Type: boolean
+
+ Default: yes
+
+ When unset, the bottom entry of menus will never scroll up past the bottom of the screen, unless there are less entries than lines. When set, the bottom entry may move off the bottom.
+
+135. menu_scroll
+
+ Type: boolean
+
+ Default: no
+
+ When set, menus will be scrolled up or down one line when you attempt to move across a screen boundary. If unset, the screen is cleared and the next or previous page of the menu is displayed (useful for slow links to avoid many redraws).
+
+136. message_format
+
+ 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(3)-like sequences see the section on ``$index_format''.
+
+137. meta_key
+
+ Type: boolean
+
+ Default: no
+
+ 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''.
+
+138. metoo
+
+ 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.
+
+139. mh_purge
+
+ Type: boolean
+
+ Default: no
+
+ When unset, Mutt-ng will mimic mh's behaviour and rename deleted messages to ,<old file name> in mh folders instead of really deleting them. If the variable is set, the message files will simply be deleted.
+
+140. mh_seq_flagged
+
+ Type: string
+
+ Default: "flagged"
+
+ The name of the MH sequence used for flagged messages.
+
+141. mh_seq_replied
+
+ Type: string
+
+ Default: "replied"
+
+ The name of the MH sequence used to tag replied messages.
+
+142. mh_seq_unseen
+
+ Type: string
+
+ Default: "unseen"
+
+ The name of the MH sequence used for unseen messages.
+
+143. mime_forward
+
+ Type: quadoption
+
+ Default: no
+
+ When set, the message you are forwarding will be attached as a separate MIME part instead of included in the main body of the message.
+
+ This is useful for forwarding MIME messages so the receiver can properly view the message as it was delivered to you. If you like to switch between MIME and not MIME from mail to mail, set this variable to ask-no or ask-yes.
+
+ Also see ``$forward_decode'' and ``$mime_forward_decode''.
+
+144. mime_forward_decode
+
+ Type: boolean
+
+ Default: no
+
+ Controls the decoding of complex MIME messages into text/plain when forwarding a message while ``$mime_forward'' is set. Otherwise ``$forward_decode'' is used instead.
+
+145. mime_forward_rest
+
+ Type: quadoption
+
+ Default: yes
+
+ When forwarding multiple attachments of a MIME message from the recvattach menu, attachments which cannot be decoded in a reasonable manner will be attached to the newly composed message if this option is set.
+
+146. mix_entry_format
+
+ Type: string
+
+ Default: "%4n %c %-16s %a"
+
+ Availability: Mixmaster
+
+ This variable describes the format of a remailer line on the mixmaster chain selection screen. The following printf(3)-like sequences are supported:
+
+ %n
+ The running number on the menu.
+
+ %c
+ Remailer capabilities.
+
+ %s
+ The remailer's short name.
+
+ %a
+ The remailer's e-mail address.
+
+147. mixmaster
+
+ Type: path
+
+ Default: "mixmaster"
+
+ Availability: Mixmaster
+
+ This variable contains the path to the Mixmaster binary on your system. It is used with various sets of parameters to gather the list of known remailers, and to finally send a message through the mixmaster chain.
+
+148. move
+
+ Type: quadoption
+
+ Default: ask-no
+
+ 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.
+
+149. msgid_format
+
+ Type: string
+
+ Default: "%Y%m%d%h%M%s.G%P%p"
+
+ This is the format for the ``local part'' of the Message-Id: header field generated by Mutt-ng. If this variable is empty, no Message-Id: headers will be generated. The '%' character marks that certain data will be added to the string, similar to printf(3). The following characters are allowed:
+
+ %d
+ the current day of month
+
+ %h
+ the current hour
+
+ %m
+ the current month
+
+ %M
+ the current minute
+
+ %O
+ the current UNIX timestamp (octal)
+
+ %p
+ the process ID
+
+ %P
+ the current Message-ID prefix (a character rotating with every Message-ID being generated)
+
+ %r
+ a random integer value (decimal)
+
+ %R
+ a random integer value (hexadecimal)
+
+ %s
+ the current second
+
+ %T
+ the current UNIX timestamp (decimal)
+
+ %X
+ the current UNIX timestamp (hexadecimal)
+
+ %Y
+ the current year (Y2K compliant)
+
+ %%
+ the '%' character
+
+ Note: Please only change this setting if you know what you are doing. Also make sure to consult RFC2822 to produce technically valid strings.
+
+150. muttng_bindir
+
+ Type: system property
+
+ Value: /opt/freebsd4/mutt-ng/bin
+
+ This is a read-only system property and specifies the directory containing the muttng binary.
+
+151. muttng_docdir
+
+ Type: system property
+
+ Value: /opt/freebsd4/mutt-ng/doc/muttng
+
+ This is a read-only system property and specifies the directory containing the muttng documentation.
+
+152. muttng_folder_name
+
+ Type: system property
+
+ Value:
+
+ This is a read-only system property and, at runtime, specifies the last part of the full path or URI of the folder currently open (if any), i.e. everything after the last ``/''.
+
+153. muttng_folder_path
+
+ Type: system property
+
+ Value:
+
+ This is a read-only system property and, at runtime, specifies the full path or URI of the folder currently open (if any).
+
+154. muttng_hcache_backend
+
+ Type: system property
+
+ Value: qdbm
+
+ This is a read-only system property and specifies the header chaching's database backend.
+
+155. muttng_pwd
+
+ Type: system property
+
+ Value:
+
+ This is a read-only system property and, at runtime, specifies the current working directory of the muttng binary.
+
+156. muttng_revision
+
+ Type: system property
+
+ Value: 473
+
+ This is a read-only system property and specifies muttng's subversion revision string.
+
+157. muttng_sysconfdir
+
+ Type: system property
+
+ Value: /opt/freebsd4/mutt-ng/etc
+
+ This is a read-only system property and specifies the directory containing the muttng system-wide configuration.
+
+158. muttng_version
+
+ Type: system property
+
+ Value: devel
+
+ This is a read-only system property and specifies muttng's version string.
+
+159. narrow_tree
+
+ Type: boolean
+
+ Default: no
+
+ This variable, when set, makes the thread tree narrower, allowing deeper threads to fit on the screen.
+
+160. nntp_ask_followup_to
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ If set, Mutt-ng will prompt you for the Followup-To: header field before editing the body of an outgoing news article.
+
+161. nntp_ask_x_comment_to
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ If set, Mutt-ng will prompt you for the X-Comment-To: header field before editing the body of an outgoing news article.
+
+162. nntp_cache_dir
+
+ Type: path
+
+ Default: "˜/.muttng"
+
+ Availability: NNTP
+
+ This variable points to directory where Mutt-ng will cache news article headers. If unset, headers will not be saved at all and will be reloaded each time when you enter a newsgroup.
+
+ As for the header caching in connection with IMAP and/or Maildir, this drastically increases speed and lowers traffic.
+
+163. nntp_catchup
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: NNTP
+
+ If this variable is set, Mutt-ng will mark all articles in a newsgroup as read when you leaving it.
+
+164. nntp_context
+
+ Type: number
+
+ Default: 1000
+
+ Availability: NNTP
+
+ This variable controls how many news articles to cache per newsgroup (if caching is enabled, see $nntp_cache_dir) and how many news articles to show in the ``index'' menu.
+
+ If there're more articles than defined with $nntp_context, all older ones will be removed/not shown in the index.
+
+165. nntp_followup_to_poster
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: NNTP
+
+ If this variable is set and the keyword "poster" is present in the Followup-To: header field, a follow-up to the newsgroup is not permitted. The message will be mailed to the submitter of the message via mail.
+
+166. nntp_group_index_format
+
+ Type: string
+
+ Default: "%4C %M%N %5s %-45.45f %d"
+
+ Availability: NNTP
+
+ This variable allows you to customize the newsgroup 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 newsgroup number
+%d description of newsgroup (retrieved 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"
+
+167. nntp_host
+
+ Type: string
+
+ Default: ""
+
+ Availability: NNTP
+
+ This variable specifies the name (or address) of the NNTP server to be used.
+
+ It defaults to the value specified via the environment variable $NNTPSERVER or contained in the file /etc/nntpserver.
+
+ You can also specify a username and an alternative port for each newsserver, e.g.
+
+ [nntp[s]://][username[:password]@]newsserver[:port]
+
+ Note: Using a password as shown and stored in a configuration file presents a security risk since the superuser of your machine may read it regardless of the file's permissions.
+
+168. nntp_inews
+
+ Type: path
+
+ Default: ""
+
+ Availability: NNTP
+
+ If set, specifies the program and arguments used to deliver news posted by Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The following printf(3)-style sequence is understood:
+%s newsserver name
+
+ Example: set inews="/usr/local/bin/inews -hS"
+
+169. nntp_load_description
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: NNTP
+
+ This variable controls whether or not descriptions for newsgroups are to be loaded when subscribing to a newsgroup.
+
+170. nntp_mail_check
+
+ Type: number
+
+ Default: 60
+
+ Availability: NNTP
+
+ The time in seconds until any operations on a newsgroup except posting a new article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on each operation in index (stepping, read article, etc.).
+
+171. nntp_mime_subject
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: NNTP
+
+ If unset, an 8-bit ``Subject:'' header field in a news article will not be encoded according to RFC2047.
+
+ Note: Only change this setting if you know what you are doing.
+
+172. nntp_newsrc
+
+ Type: path
+
+ Default: "˜/.newsrc"
+
+ Availability: NNTP
+
+ This file contains information about subscribed newsgroup and articles read so far.
+
+ To ease the use of multiple news servers, the following printf(3)-style sequence is understood:
+%s newsserver name
+
+173. nntp_pass
+
+ Type: string
+
+ Default: ""
+
+ Availability: NNTP
+
+ Your password for NNTP account.
+
+ Note: Storing passwords in a configuration file presents a security risk since the superuser of your machine may read it regardless of the file's permissions.
+
+174. nntp_post_moderated
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: NNTP
+
+ If set to yes, Mutt-ng will post articles to newsgroup that have not permissions to post (e.g. moderated).
+
+ Note: if the newsserver does not support posting to that newsgroup or a group is totally read-only, that posting will not have any effect.
+
+175. nntp_reconnect
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: NNTP
+
+ Controls whether or not Mutt-ng will try to reconnect to a newsserver when the was connection lost.
+
+176. nntp_save_unsubscribed
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ When set, info about unsubscribed newsgroups will be saved into the ``newsrc'' file and into the news cache.
+
+177. nntp_show_new_news
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: NNTP
+
+ If set, the 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 the number of new articles of subscribed newsgroups will be checked.
+
+178. nntp_show_only_unread
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ If set, only subscribed newsgroups that contain unread articles will be displayed in the newsgroup browser.
+
+179. nntp_user
+
+ Type: string
+
+ Default: ""
+
+ Availability: NNTP
+
+ Your login name on the NNTP server. If unset and the server requires authentification, Mutt-ng will prompt you for your account name.
+
+180. nntp_x_comment_to
+
+ Type: boolean
+
+ Default: no
+
+ Availability: NNTP
+
+ If set, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full name of the original article author) to articles that you followup to.
+
+181. operating_system
+
+ Type: string
+
+ Default: ""
+
+ This specifies the operating system name for the User-Agent: header field. 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.
+
+ It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''.
+
+182. pager
+
+ Type: path
+
+ Default: "builtin"
+
+ This variable specifies which pager you would like to use to view messages. ``builtin'' means to use the builtin pager, otherwise this variable should specify the pathname of the external pager you would like to use.
+
+ Using an external pager may have some disadvantages: Additional 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.
+
+183. pager_context
+
+ 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-ng will display the line after the last one on the screen at the top of the next page (0 lines of context).
+
+184. pager_format
+
+ Type: string
+
+ Default: "-%Z- %C/%m: %-20.20n %s"
+
+ This variable controls the format of the one-line message ``status'' displayed before each message in either the internal or an external pager. The valid sequences are listed in the ``$index_format'' section.
+
+185. pager_index_lines
+
+ Type: number
+
+ Default: 0
+
+ Determines the number of lines of a mini-index which is shown when in the pager. The current message, unless near the top or bottom of the folder, will be roughly one third of the way down this mini-index, giving the reader the context of a few messages before and after the message. This is useful, for example, to determine how many messages remain to be read in the current thread. One of the lines is reserved for the status bar from the index, so a pager_index_lines of 6 will only show 5 lines of the actual index. A value of 0 results in no index being shown. If the number of messages in the current folder is less than pager_index_lines, then the index will only use as many lines as it needs.
+
+186. pager_stop
+
+ Type: boolean
+
+ Default: no
+
+ When set, the internal-pager will not move to the next message when you are at the end of a message and invoke the next-page function.
+
+187. pgp_auto_decode
+
+ Type: boolean
+
+ Default: no
+
+ 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.
+
+188. pgp_autoinline
+
+ Type: boolean
+
+ Default: no
+
+ 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 pgp-menu, when inline is not required.
+
+ 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 strongly deprecated. (PGP only)
+
+189. pgp_check_exit
+
+ Type: boolean
+
+ Default: yes
+
+ 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)
+
+190. pgp_clearsign_command
+
+ Type: string
+
+ Default: ""
+
+ This format is used to create a old-style ``clearsigned'' PGP message.
+
+ Note that the use of this format is strongly deprecated. (PGP only)
+
+191. pgp_decode_command
+
+ Type: string
+
+ Default: ""
+
+ This format strings specifies a command which is used to decode application/pgp attachments.
+
+ The PGP command formats have their own set of printf(3)-like sequences:
+
+ %p
+ Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty string otherwise. Note: This may be used with a %? construct.
+
+ %f
+ Expands to the name of a file containing a message.
+
+ %s
+ Expands to the name of a file containing the signature part of a multipart/signed attachment when verifying it.
+
+ %a
+ The value of $pgp_sign_as.
+
+ %r
+ 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)
+
+192. pgp_decrypt_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to decrypt a PGP encrypted message. (PGP only)
+
+193. pgp_encrypt_only_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to encrypt a body part without signing it. (PGP only)
+
+194. pgp_encrypt_sign_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to both sign and encrypt a body part. (PGP only)
+
+195. pgp_entry_format
+
+ Type: string
+
+ Default: "%4n %t%f %4l/0x%k %-4a %2c %u"
+
+ This variable allows you to customize the PGP key selection menu to your personal taste. This string is similar to ``$index_format'', but has its own set of printf(3)-like sequences:
+
+ %n
+ number
+
+ %k
+ key id
+
+ %u
+ user id
+
+ %a
+ algorithm
+
+ %l
+ key length
+
+ %f
+ flags
+
+ %c
+ capabilities
+
+ %t
+ trust/validity of the key-uid association
+
+ %[<s>]
+ date of the key where <s> is an strftime(3) expression
+
+ (PGP only)
+
+196. pgp_export_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to export a public key from the user's key ring. (PGP only)
+
+197. pgp_getkeys_command
+
+ Type: string
+
+ Default: ""
+
+ This command is invoked whenever Mutt-ng will need public key information. %r is the only printf(3)-like sequence used with this format. (PGP only)
+
+198. pgp_good_sign
+
+ Type: regular expression
+
+ Default: ""
+
+ If you assign a text to this variable, then a PGP signature is only considered verified if the output from $pgp_verify_command contains the text. Use this variable if the exit code from the command is 0 even for bad signatures. (PGP only)
+
+199. pgp_ignore_subkeys
+
+ Type: boolean
+
+ Default: yes
+
+ 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)
+
+200. pgp_import_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to import a key from a message into the user's public key ring. (PGP only)
+
+201. pgp_list_pubring_command
+
+ 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)
+
+202. pgp_list_secring_command
+
+ 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)
+
+203. pgp_long_ids
+
+ Type: boolean
+
+ Default: no
+
+ If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. (PGP only)
+
+204. pgp_mime_auto
+
+ 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 strongly deprecated. (PGP only)
+
+205. pgp_replyinline
+
+ 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 pgp-menu, 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 strongly deprecated. (PGP only)
+
+206. pgp_retainable_sigs
+
+ Type: boolean
+
+ Default: no
+
+ If set, signed and encrypted messages will consist of nested multipart/signed and multipart/encrypted body parts.
+
+ This is useful for applications like encrypted and signed mailing lists, where the outer layer (multipart/encrypted) can be easily removed, while the inner multipart/signed part is retained. (PGP only)
+
+207. pgp_show_unusable
+
+ Type: boolean
+
+ Default: yes
+
+ 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)
+
+208. pgp_sign_as
+
+ Type: string
+
+ Default: ""
+
+ If you have more than one key pair, this option allows you to specify 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)
+
+209. pgp_sign_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to create the detached PGP signature for a multipart/signed PGP/MIME body part. (PGP only)
+
+210. pgp_sort_keys
+
+ Type: sort order
+
+ Default: address
+
+ Specifies how the entries in the ``pgp keys'' menu are sorted. The following are legal values:
+
+ address
+ sort alphabetically by user id
+
+ keyid
+ sort alphabetically by key id
+
+ date
+ sort by key creation date
+
+ trust
+ sort by the trust of the key
+
+ If you prefer reverse order of the above values, prefix it with ``reverse-''. (PGP only)
+
+211. pgp_strict_enc
+
+ Type: boolean
+
+ Default: yes
+
+ If set, Mutt-ng will automatically encode PGP/MIME signed messages as quoted-printable. 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)
+
+212. pgp_timeout
+
+ Type: number
+
+ Default: 300
+
+ The number of seconds after which a cached passphrase will expire if not used. Default: 300. (PGP only)
+
+213. pgp_use_gpg_agent
+
+ Type: boolean
+
+ Default: no
+
+ If set, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
+
+214. pgp_verify_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to verify PGP signatures. (PGP only)
+
+215. pgp_verify_key_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to verify key information from the key selection menu. (PGP only)
+
+216. pipe_decode
+
+ Type: boolean
+
+ Default: no
+
+ Used in connection with the pipe-message 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.
+
+217. pipe_sep
+
+ Type: string
+
+ Default: "\n"
+
+ The separator to add between messages when piping a list of tagged messages to an external Unix command.
+
+218. pipe_split
+
+ Type: boolean
+
+ Default: no