+ 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)
+
+ %X
+
+ number of attachments
+
+ %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 newunread 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 0xf8, then this is treated as if the user had pressed ESC then
+ ``x''. This is because the result of removing the high bit from ``0xf8''
+ is ``0x78'', 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: 541
+
+ 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. $net_inc
+
+ Type: number
+
+ Default: 10
+
+ Operations that expect to transfer a large amount of data over the network
+ will update their progress every net_inc kilobytes. If set to 0, no
+ progress messages will be displayed.
+
+ See also ``$read_inc'' and ``$write_inc''.
+
+161. $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.
+
+162. $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.
+
+163. $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.
+
+164. $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.
+
+165. $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.
+
+166. $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.
+
+167. $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"
+
+
+168. $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.
+
+169. $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"
+
+170. $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.
+
+171. $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.).
+
+172. $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.
+
+173. $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
+
+
+174. $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.
+
+175. $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.
+
+176. $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.
+
+177. $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.
+
+178. $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.
+
+179. $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.
+
+180. $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.
+
+181. $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.
+
+182. $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)''.
+
+183. $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.
+
+184. $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).
+
+185. $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.
+
+186. $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.
+
+187. $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.
+
+188. $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.
+
+189. $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
+ stronglydeprecated. (PGP only)
+
+190. $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)
+
+191. $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 stronglydeprecated. (PGP only)
+
+192. $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)
+
+193. $pgp_decrypt_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to decrypt a PGP encrypted message. (PGP only)
+
+194. $pgp_encrypt_only_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to encrypt a body part without signing it. (PGP only)
+
+195. $pgp_encrypt_sign_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to both sign and encrypt a body part. (PGP only)
+
+196. $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)
+
+197. $pgp_export_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to export a public key from the user's key ring. (PGP
+ only)
+
+198. $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)
+
+199. $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)
+
+200. $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)
+
+201. $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)
+
+202. $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)
+
+203. $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)
+
+204. $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)
+
+205. $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
+ stronglydeprecated. (PGP only)
+
+206. $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
+ stronglydeprecated. (PGP only)
+
+207. $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)
+
+208. $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)
+
+209. $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)
+
+210. $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)
+
+211. $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)
+
+212. $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)
+
+213. $pgp_timeout
+
+ Type: number
+
+ Default: 300
+
+ The number of seconds after which a cached passphrase will expire if not
+ used. Default: 300. (PGP only)
+
+214. $pgp_use_gpg_agent
+
+ Type: boolean
+
+ Default: no
+
+ If set, Mutt-ng will use a possibly-running gpg-agent process. (PGP only)
+
+215. $pgp_verify_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to verify PGP signatures. (PGP only)
+
+216. $pgp_verify_key_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to verify key information from the key selection
+ menu. (PGP only)
+
+217. $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.
+
+218. $pipe_sep
+
+ Type: string
+
+ Default: "\n"
+
+ The separator to add between messages when piping a list of tagged
+ messages to an external Unix command.
+
+219. $pipe_split
+
+ Type: boolean
+
+ Default: no
+
+ Used in connection with the pipe-message command and the ``tag- prefix''
+ or ``tag-prefix-cond'' operators. If this variable is unset, when piping a
+ list of tagged messages Mutt-ng will concatenate the messages and will
+ pipe them as a single folder. When set, Mutt-ng will pipe the messages one
+ by one. In both cases the messages are piped in the current sorted order,
+ and the ``$pipe_sep'' separator is added after each message.
+
+220. $pop_auth_try_all
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: POP
+
+ If set, Mutt-ng will try all available methods. When unset, Mutt-ng will
+ only fall back to other authentication methods if the previous methods are
+ unavailable. If a method is available but authentication fails, Mutt-ng
+ will not connect to the POP server.
+
+221. $pop_authenticators
+
+ Type: string
+
+ Default: ""
+
+ Availability: POP
+
+ This is a colon-delimited list of authentication methods Mutt-ng may
+ attempt to use to log in to an POP server, in the order Mutt-ng should try
+ them. Authentication methods are either ``user'', ``apop'' or any SASL
+ mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''.
+
+ This parameter is case-insensitive. If this parameter is unset (the
+ default) Mutt-ng will try all available methods, in order from most-secure
+ to least-secure.
+
+ Example: set pop_authenticators="digest-md5:apop:user"
+
+222. $pop_delete
+
+ Type: quadoption
+
+ Default: ask-no
+
+ Availability: POP
+
+ If set, Mutt-ng will delete successfully downloaded messages from the POP
+ server when using the ``fetch-mail'' function. When unset, Mutt-ng will
+ download messages but also leave them on the POP server.
+
+223. $pop_host
+
+ Type: string
+
+ Default: ""
+
+ Availability: POP
+
+ The name of your POP server for the ``fetch-mail'' function. You can also
+ specify an alternative port, username and password, i.e.:
+
+ [pop[s]://][username[:password]@]popserver[:port]
+
+ 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.
+
+224. $pop_last
+
+ Type: boolean
+
+ Default: no
+
+ Availability: POP
+
+ If this variable is set, Mutt-ng will try to use the ``LAST'' POP command
+ for retrieving only unread messages from the POP server when using the
+ ``fetch-mail'' function.
+
+225. $pop_mail_check
+
+ Type: number
+
+ Default: 60
+
+ Availability: POP
+
+ This variable configures how often (in seconds) Mutt-ng should look for
+ new mail.
+
+226. $pop_pass
+
+ Type: string
+
+ Default: ""
+
+ Availability: POP
+
+ Specifies the password for your POP account. If unset, Mutt-ng will prompt
+ you for your password when you open POP mailbox.
+
+ 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.
+
+227. $pop_reconnect
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Availability: POP
+
+ Controls whether or not Mutt-ng will try to reconnect to a POP server if
+ the connection is lost.
+
+228. $pop_user
+
+ Type: string
+
+ Default: ""
+
+ Availability: POP
+
+ Your login name on the POP server.
+
+ This variable defaults to your user name on the local machine.
+
+229. $post_indent_string
+
+ Type: string
+
+ Default: ""
+
+ Similar to the ``$attribution'' variable, Mutt-ng will append this string
+ after the inclusion of a message which is being replied to.
+
+230. $postpone
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Controls whether or not messages are saved in the ``$postponed'' mailbox
+ when you elect not to send immediately.
+
+231. $postponed
+
+ Type: path
+
+ Default: "~/postponed"
+
+ Mutt-ng allows you to indefinitely ``postpone sending a message'' which
+ you are editing. When you choose to postpone a message, Mutt-ng saves it
+ in the mailbox specified by this variable. Also see the ``$postpone''
+ variable.
+
+232. $preconnect
+
+ Type: string
+
+ Default: ""
+
+ If set, a shell command to be executed if Mutt-ng fails to establish a
+ connection to the server. This is useful for setting up secure
+ connections, e.g. with ssh(1). If the command returns a nonzero status,
+ Mutt-ng gives up opening the server. Example:
+
+ preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 <
+ /dev/null > /dev/null"
+
+ Mailbox ``foo'' on mailhost.net can now be reached as
+ ``{localhost:1234}foo''.
+
+ Note: For this example to work, you must be able to log in to the remote
+ machine without having to enter a password.
+
+233. $print
+
+ Type: quadoption
+
+ Default: ask-no
+
+ Controls whether or not Mutt-ng really prints messages. This is set to
+ ask-no by default, because some people accidentally hit ``p'' often.
+
+234. $print_command
+
+ Type: path
+
+ Default: "lpr"
+
+ This specifies the command pipe that should be used to print messages.
+
+235. $print_decode
+
+ Type: boolean
+
+ Default: yes
+
+ Used in connection with the print-message command. If this option is set,
+ the message is decoded before it is passed to the external command
+ specified by $print_command. If this option is unset, no processing will
+ be applied to the message when printing it. The latter setting may be
+ useful if you are using some advanced printer filter which is able to
+ properly format e-mail messages for printing.
+
+236. $print_split
+
+ Type: boolean
+
+ Default: no
+
+ Used in connection with the print-message command. If this option is set,
+ the command specified by $print_command is executed once for each message
+ which is to be printed. If this option is unset, the command specified by
+ $print_command is executed only once, and all the messages are
+ concatenated, with a form feed as the message separator.
+
+ Those who use the enscript(1) program's mail-printing mode will most
+ likely want to set this option.
+
+237. $prompt_after
+
+ Type: boolean
+
+ Default: yes
+
+ If you use an external ``$pager'', setting this variable will cause
+ Mutt-ng to prompt you for a command when the pager exits rather than
+ returning to the index menu. If unset, Mutt-ng will return to the index
+ menu when the external pager exits.
+
+238. $query_command
+
+ Type: path
+
+ Default: ""
+
+ This specifies the command that Mutt-ng will use to make external address
+ queries. The string should contain a %s, which will be substituted with
+ the query string the user types. See ``query'' for more information.
+
+239. $quit
+
+ Type: quadoption
+
+ Default: yes
+
+ This variable controls whether ``quit'' and ``exit'' actually quit from
+ Mutt-ng. If it set to yes, they do quit, if it is set to no, they have no
+ effect, and if it is set to ask-yes or ask-no, you are prompted for
+ confirmation when you try to quit.
+
+240. $quote_empty
+
+ Type: boolean
+
+ Default: yes
+
+ Controls whether or not empty lines will be quoted using
+ ``indent_string''.
+
+241. $quote_quoted
+
+ Type: boolean
+
+ Default: no
+
+ Controls how quoted lines will be quoted. If set, one quote character will
+ be added to the end of existing prefix. Otherwise, quoted lines will be
+ prepended by ``indent_string''.
+
+242. $quote_regexp
+
+ Type: regular expression
+
+ Default: "^([ \t]*[|>:}#])+"
+
+ A regular expression used in the internal-pager to determine quoted
+ sections of text in the body of a message.
+
+ Note: In order to use the quotedx patterns in the internal pager, you need
+ to set this to a regular expression that matches exactly the quote
+ characters at the beginning of quoted lines.
+
+243. $read_inc
+
+ Type: number
+
+ Default: 10
+
+ If set to a value greater than 0, Mutt-ng will display which message it is
+ currently on when reading a mailbox. The message is printed after read_inc
+ messages have been read (e.g., if set to 25, Mutt-ng will print a message
+ when it reads message 25, and then again when it gets to message 50). This
+ variable is meant to indicate progress when reading large mailboxes which
+ may take some time. When set to 0, only a single message will appear
+ before the reading the mailbox.
+
+ Also see the ``$write_inc'' variable.
+
+244. $read_only
+
+ Type: boolean
+
+ Default: no
+
+ If set, all folders are opened in read-only mode.
+
+245. $realname
+
+ Type: string
+
+ Default: ""
+
+ This variable specifies what ``real'' or ``personal'' name should be used
+ when sending messages.
+
+ By default, this is the GECOS field from /etc/passwd.
+
+ Note: This variable will not be used when the user has set a real name in
+ the $from variable.
+
+246. $recall
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ Controls whether or not Mutt-ng recalls postponed messages when composing
+ a new message. Also see ``$postponed''.
+
+ Setting this variable to yes is not generally useful, and thus not
+ recommended.
+
+247. $record
+
+ Type: path
+
+ Default: ""
+
+ This specifies the file into which your outgoing messages should be
+ appended. (This is meant as the primary method for saving a copy of your
+ messages, but another way to do this is using the ``my_hdr'' command to
+ create a Bcc: header field with your email address in it.)
+
+ The value of $record is overridden by the ``$force_name'' and
+ ``$save_name'' variables, and the ``fcc-hook'' command.
+
+248. $reply_regexp
+
+ Type: regular expression
+
+ Default: "^(re([\[0-9\]+])*|aw):[ \t]*"
+
+ A regular expression used to recognize reply messages when threading and
+ replying. The default value corresponds to the English ``Re:'' and the
+ German ``Aw:''.
+
+249. $reply_self
+
+ Type: boolean
+
+ Default: no
+
+ If unset and you are replying to a message sent by you, Mutt-ng will
+ assume that you want to reply to the recipients of that message rather
+ than to yourself.
+
+250. $reply_to
+
+ Type: quadoption
+
+ Default: ask-yes
+
+ If set, when replying to a message, Mutt-ng will use the address listed in
+ the ``Reply-To:'' header field as the recipient of the reply. If unset, it
+ will use the address in the ``From:'' header field instead.
+
+ This option is useful for reading a mailing list that sets the
+ ``Reply-To:'' header field to the list address and you want to send a
+ private message to the author of a message.
+
+251. $resolve
+
+ Type: boolean
+
+ Default: yes
+
+ When set, the cursor will be automatically advanced to the next (possibly
+ undeleted) message whenever a command that modifies the current message is
+ executed.
+
+252. $reverse_alias
+
+ Type: boolean
+
+ Default: no
+
+ This variable controls whether or not Mutt-ng will display the
+ ``personal'' name from your aliases in the index menu if it finds an alias
+ that matches the message's sender. For example, if you have the following
+ alias:
+
+ alias juser abd30425@somewhere.net (Joe User)
+
+ and then you receive mail which contains the following header:
+
+ From: abd30425@somewhere.net
+
+ It would be displayed in the index menu as ``Joe User'' instead of
+ ``abd30425@somewhere.net.'' This is useful when the person's e-mail
+ address is not human friendly (like CompuServe addresses).
+
+253. $reverse_name
+
+ Type: boolean
+
+ Default: no
+
+ It may sometimes arrive that you receive mail to a certain machine, move
+ the messages to another machine, and reply to some the messages from
+ there. If this variable is set, the default From: line of the reply
+ messages is built using the address where you received the messages you
+ are replying to if that address matches your alternates. If the variable
+ is unset, or the address that would be used doesn't match your alternates,
+ the From: line will use your address on the current machine.
+
+254. $reverse_realname
+
+ Type: boolean
+
+ Default: yes
+
+ This variable fine-tunes the behaviour of the reverse_name feature. When
+ it is set, Mutt-ng will use the address from incoming messages as-is,
+ possibly including eventual real names. When it is unset, Mutt-ng will
+ override any such real names with the setting of the realname variable.
+
+255. $rfc2047_parameters
+
+ Type: boolean
+
+ Default: no
+
+ When this variable is set, Mutt-ng will decode RFC-2047-encoded MIME
+ parameters. You want to set this variable when Mutt-ng suggests you to
+ save attachments to files named like this:
+
+ =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
+
+ When this variable is set interactively, the change doesn't have the
+ desired effect before you have changed folders.
+
+ Note that this use of RFC 2047's encoding is explicitly, prohibited by the
+ standard, but nevertheless encountered in the wild.
+
+ Also note that setting this parameter will not have the effect that
+ Mutt-ng generates this kind of encoding. Instead, Mutt-ng will
+ unconditionally use the encoding specified in RFC 2231.
+
+256. $save_address
+
+ Type: boolean
+
+ Default: no
+
+ If set, Mutt-ng will take the sender's full address when choosing a
+ default folder for saving a mail. If ``$save_name'' or ``$force_name'' is
+ set too, the selection of the fcc folder will be changed as well.
+
+257. $save_empty
+
+ Type: boolean
+
+ Default: yes
+
+ When unset, mailboxes which contain no saved messages will be removed when
+ closed (the exception is ``$spoolfile'' which is never removed). If set,
+ mailboxes are never removed.
+
+ Note: This only applies to mbox and MMDF folders, Mutt-ng does not delete
+ MH and Maildir directories.
+
+258. $save_name
+
+ Type: boolean
+
+ Default: no
+
+ This variable controls how copies of outgoing messages are saved. When
+ set, a check is made to see if a mailbox specified by the recipient
+ address exists (this is done by searching for a mailbox in the ``$folder''
+ directory with the username part of the recipient address). If the mailbox
+ exists, the outgoing message will be saved to that mailbox, otherwise the
+ message is saved to the ``$record'' mailbox.
+
+ Also see the ``$force_name'' variable.
+
+259. $score
+
+ Type: boolean
+
+ Default: yes
+
+ When this variable is unset, scoring is turned off. This can be useful to
+ selectively disable scoring for certain folders when the
+ ``$score_threshold_delete'' variable and friends are used.
+
+260. $score_threshold_delete
+
+ Type: number
+
+ Default: -1
+
+ Messages which have been assigned a score equal to or lower than the value
+ of this variable are automatically marked for deletion by Mutt-ng. Since
+ Mutt-ng scores are always greater than or equal to zero, the default
+ setting of this variable will never mark a message for deletion.
+
+261. $score_threshold_flag
+
+ Type: number
+
+ Default: 9999
+
+ Messages which have been assigned a score greater than or equal to this
+ variable's value are automatically marked ``flagged''.
+
+262. $score_threshold_read
+
+ Type: number
+
+ Default: -1
+
+ Messages which have been assigned a score equal to or lower than the value
+ of this variable are automatically marked as read by Mutt-ng. Since
+ Mutt-ng scores are always greater than or equal to zero, the default
+ setting of this variable will never mark a message read.
+
+263. $send_charset
+
+ Type: string
+
+ Default: "us-ascii:iso-8859-1:utf-8"
+
+ A list of character sets for outgoing messages. Mutt-ng will use the first
+ character set into which the text can be converted exactly. If your
+ ``$charset'' is not iso-8859-1 and recipients may not understand UTF-8, it
+ is advisable to include in the list an appropriate widely used standard
+ character set (such as iso-8859-2, koi8-r or iso-2022-jp) either instead
+ of or after iso-8859-1.
+
+264. $sendmail
+
+ Type: path
+
+ Default: "/usr/sbin/sendmail -oem -oi"
+
+ Specifies the program and arguments used to deliver mail sent by Mutt-ng.
+ Mutt-ng expects that the specified program interprets additional arguments
+ as recipient addresses.
+
+265. $sendmail_wait
+
+ Type: number
+
+ Default: 0
+
+ Specifies the number of seconds to wait for the ``$sendmail'' process to
+ finish before giving up and putting delivery in the background.
+
+ Mutt-ng interprets the value of this variable as follows:
+
+ >0
+
+ number of seconds to wait for sendmail to finish before continuing
+
+ 0
+
+ wait forever for sendmail to finish
+
+ <0
+
+ always put sendmail in the background without waiting
+
+ Note that if you specify a value other than 0, the output of the child
+ process will be put in a temporary file. If there is some error, you will
+ be informed as to where to find the output.
+
+266. $shell
+
+ Type: path
+
+ Default: ""
+
+ Command to use when spawning a subshell. By default, the user's login
+ shell from /etc/passwd is used.
+
+267. $sidebar_boundary
+
+ Type: string
+
+ Default: "."
+
+ When the sidebar is displayed and $sidebar_shorten_hierarchy is set, this
+ variable specifies the characters at which to split a folder name into
+ ``hierarchy items.''
+
+268. $sidebar_delim
+
+ Type: string
+
+ Default: "|"
+
+ This specifies the delimiter between the sidebar (if visible) and other
+ screens.
+
+269. $sidebar_newmail_only
+
+ Type: boolean
+
+ Default: no
+
+ If set, only folders with new mail will be shown in the sidebar.
+
+270. $sidebar_number_format
+
+ Type: string
+
+ Default: "%m%?n?(%n)?%?f?[%f]?"
+
+ This variable controls how message counts are printed when the sidebar is
+ enabled. If this variable is empty (and only if), no numbers will be
+ printed and Mutt-ng won't frequently count mail (which may be a great
+ speedup esp. with mbox-style mailboxes.)
+
+ The following printf(3)-like sequences are supported all of which may be
+ printed non-zero:
+
+ %d
+
+ Number of deleted messages. 1)
+
+ %F
+
+ Number of flagged messages.
+
+ %m
+
+ Total number of messages.
+
+ %M
+
+ Total number of messages shown, i.e. not hidden by a limit. 1)
+
+ %n
+
+ Number of new messages.
+
+ %t
+
+ Number of tagged messages. 1)
+
+ 1) These expandos only have a non-zero value for the current mailbox and
+ will always be zero otherwise.
+
+271. $sidebar_shorten_hierarchy
+
+ Type: boolean
+
+ Default: no
+
+ When set, the ``hierarchy'' of the sidebar entries will be shortened only
+ if they cannot be printed in full length (because ``$sidebar_width'' is
+ set to a too low value). For example, if the newsgroup name
+ ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get
+ shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will
+ not get shortened.
+
+ At which characters this compression is done is controled via the
+ $sidebar_boundary variable.
+
+272. $sidebar_visible
+
+ Type: boolean
+
+ Default: no
+
+ This specifies whether or not to show the sidebar (a list of folders
+ specified with the ``mailboxes'' command).
+
+273. $sidebar_width
+
+ Type: number
+
+ Default: 0
+
+ The width of the sidebar.
+
+274. $sig_dashes
+
+ Type: boolean
+
+ Default: yes
+
+ If set, a line containing ``-- '' (dash, dash, space) will be inserted
+ before your ``$signature''. It is strongly recommended that you not unset
+ this variable unless your ``signature'' contains just your name. The
+ reason for this is because many software packages use ``-- \n'' to detect
+ your signature.
+
+ For example, Mutt-ng has the ability to highlight the signature in a
+ different color in the builtin pager.
+
+275. $sig_on_top
+
+ Type: boolean
+
+ Default: no
+
+ If set, the signature will be included before any quoted or forwarded
+ text. It is strongly recommended that you do not set this variable unless
+ you really know what you are doing, and are prepared to take some heat
+ from netiquette guardians.
+
+276. $signature
+
+ Type: path
+
+ Default: "~/.signature"
+
+ Specifies the filename of your signature, which is appended to all
+ outgoing messages. If the filename ends with a pipe (``|''), it is assumed
+ that filename is a shell command and input should be read from its stdout.
+
+277. $signoff_string
+
+ Type: string
+
+ Default: ""
+
+ If set, this string will be inserted before the signature. This is useful
+ for people that want to sign off every message they send with their name.
+
+ If you want to insert your website's URL, additional contact information
+ or witty quotes into your mails, better use a signature file instead of
+ the signoff string.
+
+278. $simple_search
+
+ Type: string
+
+ Default: "~f %s | ~s %s"
+
+ Specifies how Mutt-ng should expand a simple search into a real search
+ pattern. A simple search is one that does not contain any of the ~
+ operators. See ``patterns'' for more information on search patterns.
+
+ For example, if you simply type ``joe'' at a search or limit prompt,
+ Mutt-ng will automatically expand it to the value specified by this
+ variable. For the default value it would be:
+
+ ~f joe | ~s joe
+
+279. $sleep_time
+
+ Type: number
+
+ Default: 1
+
+ Specifies time, in seconds, to pause while displaying certain
+ informational messages, while moving from folder to folder and after
+ expunging messages from the current folder. The default is to pause one
+ second, so a value of zero for this option suppresses the pause.
+
+280. $smart_wrap
+
+ Type: boolean
+
+ Default: yes
+
+ Controls the display of lines longer than the screen width in the internal
+ pager. If set, long lines are wrapped at a word boundary. If unset, lines
+ are simply wrapped at the screen edge. Also see the ``$markers'' variable.
+
+281. $smileys
+
+ Type: regular expression
+
+ Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
+
+ The pager uses this variable to catch some common false positives of
+ ``$quote_regexp'', most notably smileys in the beginning of a line
+
+282. $smime_ask_cert_label
+
+ Type: boolean
+
+ Default: yes
+
+ This flag controls whether you want to be asked to enter a label for a
+ certificate about to be added to the database or not. It is set by
+ default. (S/MIME only)
+
+283. $smime_ca_location
+
+ Type: path
+
+ Default: ""
+
+ This variable contains the name of either a directory, or a file which
+ contains trusted certificates for use with OpenSSL. (S/MIME only)
+
+284. $smime_certificates
+
+ Type: path
+
+ Default: ""
+
+ Since there is no pubring/secring as with PGP, Mutt-ng has to handle
+ storage and retrieval of keys by itself. This is very basic right now, and
+ keys and certificates are stored in two different directories, both named
+ as the hash-value retrieved from OpenSSL. There is an index file which
+ contains mailbox-address keyid pairs, and which can be manually edited.
+ This one points to the location of the certificates. (S/MIME only)
+
+285. $smime_decrypt_command
+
+ Type: string
+
+ Default: ""
+
+ This format string specifies a command which is used to decrypt
+ application/x-pkcs7-mime attachments.
+
+ The OpenSSL command formats have their own set of printf(3)-like sequences
+ similar to PGP's:
+
+ %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.
+
+ %k
+
+ The key-pair specified with $smime_default_key
+
+ %c
+
+ One or more certificate IDs.
+
+ %a
+
+ The algorithm used for encryption.
+
+ %C
+
+ CA location: Depending on whether $smime_ca_location points to a
+ directory or file, this expands to "-CApath $smime_ca_location" or
+ "-CAfile $smime_ca_location".
+
+ For examples on how to configure these formats, see the smime.rc in the
+ samples/ subdirectory which has been installed on your system alongside
+ the documentation. (S/MIME only)
+
+286. $smime_decrypt_use_default_key
+
+ Type: boolean
+
+ Default: yes
+
+ If set (default) this tells Mutt-ng to use the default key for decryption.
+ Otherwise, if manage multiple certificate-key-pairs, Mutt-ng will try to
+ use the mailbox-address to determine the key to use. It will ask you to
+ supply a key, if it can't find one. (S/MIME only)
+
+287. $smime_default_key
+
+ Type: string
+
+ Default: ""
+
+ This is the default key-pair to use for signing. This must be set to the
+ keyid (the hash-value that OpenSSL generates) to work properly (S/MIME
+ only)
+
+288. $smime_encrypt_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to create encrypted S/MIME messages. (S/MIME only)
+
+289. $smime_encrypt_with
+
+ Type: string
+
+ Default: ""
+
+ This sets the algorithm that should be used for encryption. Valid choices
+ are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``\frc2-128''.
+
+ If unset ``3des'' (TripleDES) is used. (S/MIME only)
+
+290. $smime_get_cert_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to extract X509 certificates from a PKCS7 structure.
+ (S/MIME only)
+
+291. $smime_get_cert_email_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to extract the mail address(es) used for storing X509
+ certificates, and for verification purposes (to check whether the
+ certificate was issued for the sender's mailbox). (S/MIME only)
+
+292. $smime_get_signer_cert_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to extract only the signers X509 certificate from a
+ S/MIME signature, so that the certificate's owner may get compared to the
+ email's ``From:'' header field. (S/MIME only)
+
+293. $smime_import_cert_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to import a certificate via smime_keysng. (S/MIME
+ only)
+
+294. $smime_is_default
+
+ Type: boolean
+
+ Default: no
+
+ The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
+ operations. To override and to use OpenSSL instead this must be set.
+
+ However, this has no effect while replying, since Mutt-ng will
+ automatically select the same application that was used to sign/encrypt
+ the original message.
+
+ (Note that this variable can be overridden by unsetting $crypt_autosmime.)
+ (S/MIME only)
+
+295. $smime_keys
+
+ Type: path
+
+ Default: ""
+
+ Since there is no pubring/secring as with PGP, Mutt-ng has to handle
+ storage ad retrieval of keys/certs by itself. This is very basic right
+ now, and stores keys and certificates in two different directories, both
+ named as the hash-value retrieved from OpenSSL. There is an index file
+ which contains mailbox-address keyid pair, and which can be manually
+ edited. This one points to the location of the private keys. (S/MIME only)
+
+296. $smime_pk7out_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to extract PKCS7 structures of S/MIME signatures, in
+ order to extract the public X509 certificate(s). (S/MIME only)
+
+297. $smime_sign_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to created S/MIME signatures of type
+ multipart/signed, which can be read by all mail clients. (S/MIME only)
+
+298. $smime_sign_opaque_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to created S/MIME signatures of type
+ application/x-pkcs7-signature, which can only be handled by mail clients
+ supporting the S/MIME extension. (S/MIME only)
+
+299. $smime_timeout
+
+ Type: number
+
+ Default: 300
+
+ The number of seconds after which a cached passphrase will expire if not
+ used. (S/MIME only)
+
+300. $smime_verify_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to verify S/MIME signatures of type multipart/signed.
+ (S/MIME only)
+
+301. $smime_verify_opaque_command
+
+ Type: string
+
+ Default: ""
+
+ This command is used to verify S/MIME signatures of type
+ application/x-pkcs7-mime. (S/MIME only)
+
+302. $smtp_host
+
+ Type: string
+
+ Default: ""
+
+ Availability: SMTP
+
+ Defines the SMTP host which will be used to deliver mail, as opposed to
+ invoking the sendmail binary. Setting this variable overrides the value of
+ ``$sendmail'', and any associated variables.
+
+303. $smtp_pass
+
+ Type: string
+
+ Default: ""
+
+ Availability: SMTP
+
+ Defines the password to use with SMTP AUTH. If ``$smtp_user'' is set, but
+ this variable is not, you will be prompted for a password when sending.
+
+ 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.
+
+304. $smtp_port
+
+ Type: number
+
+ Default: 25
+
+ Availability: SMTP
+
+ Defines the port that the SMTP host is listening on for mail delivery.
+ Must be specified as a number.
+
+ Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
+ servers will probably desire 587, the mail submission port.
+
+305. $smtp_use_tls
+
+ Type: string
+
+ Default: ""
+
+ Availability: SMTP (and SSL)
+
+ Defines wether to use STARTTLS. If this option is set to ``required'' and
+ the server does not support STARTTLS or there is an error in the TLS
+ Handshake, the connection will fail. Setting this to ``enabled'' will try
+ to start TLS and continue without TLS in case of an error. Muttng still
+ needs to have SSL support enabled in order to use it.
+
+306. $smtp_user
+
+ Type: string
+
+ Default: ""
+
+ Availability: SMTP
+
+ Defines the username to use with SMTP AUTH. Setting this variable will
+ cause Mutt-ng to attempt to use SMTP AUTH when sending.
+
+307. $sort
+
+ Type: sort order
+
+ Default: date
+
+ Specifies how to sort messages in the index menu. Valid values are:
+
+ date or date-sent
+ date-received
+ from
+ mailbox-order (unsorted)
+ score
+ size
+ spam
+ subject
+ threads
+ to
+
+
+ You may optionally use the ``reverse-'' prefix to specify reverse sorting
+ order (example: set sort=reverse-date-sent).
+
+308. $sort_alias
+
+ Type: sort order
+
+ Default: alias
+
+ Specifies how the entries in the ``alias'' menu are sorted. The following
+ are legal values:
+
+ address (sort alphabetically by email address)
+ alias (sort alphabetically by alias name)
+ unsorted (leave in order specified in .muttrc)
+
+
+309. $sort_aux
+
+ Type: sort order
+
+ Default: date
+
+ When sorting by threads, this variable controls how threads are sorted in
+ relation to other threads, and how the branches of the thread trees are
+ sorted. This can be set to any value that ``$sort'' can, except threads
+ (in that case, Mutt-ng will just use date-sent). You can also specify the
+ ``last-'' prefix in addition to ``reverse-'' prefix, but last- must come
+ after reverse-. The last- prefix causes messages to be sorted against its
+ siblings by which has the last descendant, using the rest of sort_aux as
+ an ordering.
+
+ For instance, set sort_aux=last-date-received would mean that if a new
+ message is received in a thread, that thread becomes the last one
+ displayed (or the first, if you have set sort=reverse-threads.)
+
+ Note: For reversed ``$sort'' order $sort_aux is reversed again (which is
+ not the right thing to do, but kept to not break any existing
+ configuration setting).
+
+310. $sort_browser
+
+ Type: sort order
+
+ Default: alpha
+
+ Specifies how to sort entries in the file browser. By default, the entries
+ are sorted alphabetically. Valid values:
+
+ alpha (alphabetically)
+ date
+ size
+ unsorted
+
+
+ You may optionally use the ``reverse-'' prefix to specify reverse sorting
+ order (example: set sort_browser=reverse-date).
+
+311. $sort_re
+
+ Type: boolean
+
+ Default: yes
+
+ This variable is only useful when sorting by threads with
+ ``$strict_threads'' unset. In that case, it changes the heuristic Mutt-ng
+ uses to thread messages by subject. With $sort_reset, Mutt-ng will only
+ attach a message as the child of another message by subject if the subject
+ of the child message starts with a substring matching the setting of
+ ``$reply_regexp''. With $sort_reunset, Mutt-ng will attach the message
+ whether or not this is the case, as long as the non-``$reply_regexp''
+ parts of both messages are identical.
+
+312. $spam_separator
+
+ Type: string
+
+ Default: ","
+
+ ``spam_separator'' controls what happens when multiple spam headers are
+ matched: if unset, each successive header will overwrite any previous
+ matches value for the spam label. If set, each successive match will
+ append to the previous, using ``spam_separator'' as a separator.
+
+313. $spoolfile
+
+ Type: path
+
+ Default: ""
+
+ If your spool mailbox is in a non-default place where Mutt-ng cannot find
+ it, you can specify its location with this variable. Mutt-ng will
+ automatically set this variable to the value of the environment variable
+ $MAIL if it is not set.
+
+314. $ssl_ca_certificates_file
+
+ Type: path
+
+ Default: ""
+
+ This variable specifies a file containing trusted CA certificates. Any
+ server certificate that is signed with one of these CA certificates are
+ also automatically accepted.
+
+ Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
+
+315. $ssl_client_cert
+
+ Type: path
+
+ Default: ""
+
+ Availability: SSL
+
+ The file containing a client certificate and its associated private key.
+
+316. $ssl_force_tls
+
+ Type: boolean
+
+ Default: no
+
+ If this variable is set, Mutt-ng will require that all connections to
+ remote servers be encrypted. Furthermore it will attempt to negotiate TLS
+ even if the server does not advertise the capability, since it would
+ otherwise have to abort the connection anyway. This option supersedes
+ ``$ssl_starttls''.
+
+317. $ssl_min_dh_prime_bits
+
+ Type: number
+
+ Default: 0
+
+ Availability: GNUTLS
+
+ This variable specifies the minimum acceptable prime size (in bits) for
+ use in any Diffie-Hellman key exchange. A value of 0 will use the default
+ from the GNUTLS library.
+
+318. $ssl_starttls
+
+ Type: quadoption
+
+ Default: yes
+
+ Availability: SSL or GNUTLS
+
+ If set (the default), Mutt-ng will attempt to use STARTTLS on servers
+ advertising the capability. When unset, Mutt-ng will not attempt to use
+ STARTTLS regardless of the server's capabilities.
+
+319. $ssl_use_sslv2
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: SSL
+
+ This variables specifies whether to attempt to use SSLv2 in the SSL
+ authentication process.
+
+320. $ssl_use_sslv3
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: SSL or GNUTLS
+
+ This variables specifies whether to attempt to use SSLv3 in the SSL
+ authentication process.
+
+321. $ssl_use_tlsv1
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: SSL or GNUTLS
+
+ This variables specifies whether to attempt to use TLSv1 in the SSL
+ authentication process.
+
+322. $ssl_usesystemcerts
+
+ Type: boolean
+
+ Default: yes
+
+ Availability: SSL
+
+ If set to yes, Mutt-ng will use CA certificates in the system-wide
+ certificate store when checking if server certificate is signed by a
+ trusted CA.
+
+323. $status_chars
+
+ Type: string
+
+ Default: "-*%A"
+
+ Controls the characters used by the ``%r'' indicator in
+ ``$status_format''. The first character is used when the mailbox is
+ unchanged. The second is used when the mailbox has been changed, and it
+ needs to be resynchronized. The third is used if the mailbox is in
+ read-only mode, or if the mailbox will not be written when exiting that
+ mailbox (You can toggle whether to write changes to a mailbox with the
+ toggle-write operation, bound by default to ``%''). The fourth is used to
+ indicate that the current folder has been opened in attach-message mode
+ (Certain operations like composing a new mail, replying, forwarding, etc.
+ are not permitted in this mode).
+
+324. $status_format
+
+ Type: string
+
+ Default: "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d?
+ Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l?
+ %l?]---(%s/%S)-%>-(%P)---"
+
+ Controls the format of the status line displayed in the index menu. This
+ string is similar to ``$index_format'', but has its own set of
+ printf(3)-like sequences:
+
+ %b
+
+ number of mailboxes with new mail *
+
+ %B
+
+ the short pathname of the current mailbox
+
+ %d
+
+ number of deleted messages *
+
+ %f
+
+ the full pathname of the current mailbox
+
+ %F
+
+ number of flagged messages *
+
+ %h
+
+ local hostname
+
+ %l
+
+ size (in bytes) of the current mailbox *
+
+ %L
+
+ size (in bytes) of the messages shown (i.e., which match the
+ current limit) *
+
+ %m
+
+ the number of messages in the mailbox *
+
+ %M
+
+ the number of messages shown (i.e., which match the current limit)
+ *
+
+ %n
+
+ number of new messages in the mailbox *
+
+ %o
+
+ number of old unread messages *
+
+ %p
+
+ number of postponed messages *
+
+ %P
+
+ percentage of the way through the index
+
+ %r
+
+ modified/read-only/won't-write/attach-message indicator, according
+ to $status_chars
+
+ %s
+
+ current sorting mode ($sort)
+
+ %S
+
+ current aux sorting method ($sort_aux)
+
+ %t
+
+ number of tagged messages *
+
+ %u
+
+ number of unread messages *
+
+ %v
+
+ Mutt-ng version string
+
+ %V
+
+ currently active limit pattern, if any *
+
+ %>X
+
+ right justify the rest of the string and pad with "X"
+
+ %|X
+
+ pad to the end of the line with "X"
+
+ * = can be optionally printed if nonzero
+
+ Some of the above sequences can be used to optionally print a string if
+ their value is nonzero. For example, you may only want to see the number
+ of flagged messages if such messages exist, since zero is not particularly
+ meaningful. To optionally print a string based upon one of the above
+ sequences, the following construct is used
+
+ %?<sequence_char>?<optional_string>?
+
+ where sequence_char is a character from the table above, and
+ optional_string is the string you would like printed if sequence_char is
+ nonzero. optional_stringmay contain other sequences as well as normal
+ text, but you may not nest optional strings.
+
+ Here is an example illustrating how to optionally print the number of new
+ messages in a mailbox:
+
+ %?n?%n new messages.?
+
+ Additionally you can switch between two strings, the first one, if a value
+ is zero, the second one, if the value is nonzero, by using the following
+ construct:
+
+ %?<sequence_char>?<if_string>&<else_string>?
+
+ You can additionally force the result of any printf(3)-like sequence to be
+ lowercase by prefixing the sequence character with an underscore (_) sign.
+ For example, if you want to display the local hostname in lowercase, you
+ would use:
+
+ %_h
+
+ If you prefix the sequence character with a colon (:) character, Mutt-ng
+ will replace any dots in the expansion by underscores. This might be
+ helpful with IMAP folders that don't like dots in folder names.
+
+325. $status_on_top
+
+ Type: boolean
+
+ Default: no
+
+ Setting this variable causes the ``status bar'' to be displayed on the
+ first line of the screen rather than near the bottom.
+
+326. $strict_mailto
+
+ Type: boolean
+
+ Default: yes
+
+ With mailto: style links, a body as well as arbitrary header information
+ may be embedded. This may lead to (user) headers being overwriten without
+ note if ``$edit_headers'' is unset.
+
+ If this variable is set, Mutt-ng is strict and allows anything to be
+ changed. If it's unset, all headers given will be prefixed with
+ ``X-Mailto-'' and the message including headers will be shown in the
+ editor regardless of what ``$edit_headers'' is set to.
+
+327. $strict_mime
+
+ Type: boolean
+
+ Default: yes
+
+ When unset, non MIME-compliant messages that doesn't have any charset
+ indication in the ``Content-Type:'' header field can be displayed (non
+ MIME-compliant messages are often generated by old mailers or buggy
+ mailers like MS Outlook Express). See also $assumed_charset.
+
+ This option also replaces linear-white-space between encoded-word and
+ *text to a single space to prevent the display of MIME-encoded
+ ``Subject:'' header field from being devided into multiple lines.
+
+328. $strict_threads
+
+ Type: boolean
+
+ Default: no
+
+ If set, threading will only make use of the ``In-Reply-To:'' and
+ ``References:'' header fields when you ``$sort'' by message threads. By
+ default, messages with the same subject are grouped together in ``pseudo
+ threads.'' This may not always be desirable, such as in a personal mailbox
+ where you might have several unrelated messages with the subject ``hi''
+ which will get grouped together. See also ``$sort_re'' for a less drastic
+ way of controlling this behaviour.
+
+329. $strip_was
+
+ Type: boolean
+
+ Default: no
+
+ When set, Mutt-ng will remove the trailing part of the ``Subject:'' line
+ which matches $strip_was_regex when replying. This is useful to properly
+ react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
+
+330. $strip_was_regex
+
+ Type: regular expression
+
+ Default: "\([Ww][Aa][RrSs]: .*\)[ ]*$"
+
+ When non-empty and $strip_was is set, Mutt-ng will remove this trailing
+ part of the ``Subject'' line when replying if it won't be empty
+ afterwards.
+
+331. $stuff_quoted
+
+ Type: boolean
+
+ Default: no
+
+ If set, attachments with flowed format will have their quoting
+ ``stuffed'', i.e. a space will be inserted between the quote characters
+ and the actual text.
+
+332. $suspend
+
+ Type: boolean
+
+ Default: yes
+
+ When unset, Mutt-ng won't stop when the user presses the terminal's susp
+ key, usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm
+ using a command like ``xterm -e muttng.''
+
+333. $text_flowed
+
+ Type: boolean
+
+ Default: no
+
+ When set, Mutt-ng will generate text/plain; format=flowed attachments.
+ This format is easier to handle for some mailing software, and generally
+ just looks like ordinary text. To actually make use of this format's
+ features, you'll need support in your editor.
+
+ Note that $indent_string is ignored when this option is set.
+
+334. $thorough_search
+
+ Type: boolean
+
+ Default: no
+
+ Affects the ~b and ~h search operations described in section ``patterns''
+ above. If set, the headers and attachments of messages to be searched are
+ decoded before searching. If unset, messages are searched as they appear
+ in the folder.
+
+335. $thread_received
+
+ Type: boolean
+
+ Default: no
+
+ When set, Mutt-ng uses the date received rather than the date sent to
+ thread messages by subject.
+
+336. $tilde
+
+ Type: boolean
+
+ Default: no
+
+ When set, the internal-pager will pad blank lines to the bottom of the
+ screen with a tilde (~).
+
+337. $timeout
+
+ Type: number
+
+ Default: 600
+
+ This variable controls the number of seconds Mutt-ng will wait for a key
+ to be pressed in the main menu before timing out and checking for new
+ mail. A value of zero or less will cause Mutt-ng to never time out.
+
+338. $tmpdir
+
+ Type: path
+
+ Default: ""
+
+ This variable allows you to specify where Mutt-ng will place its temporary
+ files needed for displaying and composing messages. If this variable is
+ not set, the environment variable $TMPDIR is used. If $TMPDIR is not set
+ then "/tmp" is used.
+
+339. $to_chars
+
+ Type: string
+
+ Default: " +TCFL"
+
+ Controls the character used to indicate mail addressed to you. The first
+ character is the one used when the mail is NOT addressed to your address
+ (default: space). The second is used when you are the only recipient of
+ the message (default: +). The third is when your address appears in the
+ ``To:'' header field, but you are not the only recipient of the message
+ (default: T). The fourth character is used when your address is specified
+ in the ``Cc:'' header field, but you are not the only recipient. The fifth
+ character is used to indicate mail that was sent by you. The sixth
+ character is used to indicate when a mail was sent to a mailing-list
+ you're subscribe to (default: L).
+
+340. $trash
+
+ Type: path
+
+ Default: ""
+
+ If set, this variable specifies the path of the trash folder where the
+ mails marked for deletion will be moved, instead of being irremediably
+ purged.
+
+ Note: When you delete a message in the trash folder, it is really deleted,
+ so that there is no way to recover mail.
+
+341. $tunnel
+
+ Type: string
+
+ Default: ""
+
+ Setting this variable will cause Mutt-ng to open a pipe to a command
+ instead of a raw socket. You may be able to use this to set up
+ preauthenticated connections to your IMAP/POP3 server. Example:
+
+ tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"